Re: ahc driver now borked in -current?

• Previous message: Simon L. Nielsen: "Re: Typo in UPDATING"
• In reply to: Jordan K. Hubbard: "ahc driver now borked in -current?"
• Next in thread: Scott Long: "Re: ahc driver now borked in -current?"
• Reply: Scott Long: "Re: ahc driver now borked in -current?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Date: Sun, 11 Jul 2004 10:16:51 -0400 (EDT)
To: "Jordan K. Hubbard" <jkh@queasyweasel.com>

Jordan,

I have seen something similar on one of my systems just a few days ago.
ACPI turned out to be the culprit. It would boot with it disabled, and
wouldn't with until I upgraded the BIOS.

Since you have all of this "vintage" hardware around, you still have one
of those pesky 3.5" floppy drives, right? ;-)

Regards,
Andy

> Andre Guibert de Bruet | Enterprise Software Consultant >
> Silicon Landmark, LLC. | http://siliconlandmark.com/ >

On Sat, 10 Jul 2004, Jordan K. Hubbard wrote:

> OK, this is going to be a little hard to give all the right information for
> given that the symptoms I'm reporting don't even allow the box in question to
> get up far enough to generate useful debugging info, but I'll give it my best
> shot anyway.
>
> In short, this is an older dual PIII box with the on-board Adaptec Ultra/Wide
> controller (one of the older ASUS motherboards we all used to covet when they
> cost $600 a pop). Plugged into that controller are two IBM LVD drives, a
> CDROM drive and an iomega Jaz drive (remember those? :).
>
> Running a -current kernel from May 1st, the box works just fine albeit with
> one warning when it tries to probe the Jaz drive, which has no media in it.
> If you like, I can try stuffing a Jaz disk in there for giggles, but the
> error in question is benign in any case (see below). Using a kernel compiled
> on July 6th, however, I can't get any farther than the "Waiting 2 seconds for
> SCSI devices to settle" message you see below, then there's a long delay
> followed by a dump of the card state (sadly, to the screen rather than some
> non-perishable medium) and lots of whining about the number of SCBs which
> were just aborted. It continues looping in that way, resetting the
> controller and whining, forever.
>
> Unfortunately, the only other machine in this room is a Mac and those are
> notorious for not having serial cards, so it's not even going to be easy to
> wire up a serial console to this baby, but I can always give it a shot if
> someone thinks that data will be really helpful - I'll have to go get a USB
> serial adaptor or something.
>
> Anyway, here's the relevant boot messages from a *functioning* (May 1st)
> kernel. That's the last time the ahc driver worked on my system. Like I
> said, with the non-functioning kernel, we don't get any further than waiting
> for the SCSI devices to settle and then abort/looping:
>
> ahc0: <Adaptec aic7890/91 Ultra2 SCSI adapter> port 0xb000-0xb0ff mem
> 0xdd800000
> -0xdd800fff irq 14 at device 6.0 on pci0
> ahc0: Reserved 0x100 bytes for rid 0x10 type 4 at 0xb000
> ahc0: [GIANT-LOCKED]
> aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs
> ...
> Waiting 2 seconds for SCSI devices to settle
> SMP: AP CPU #1 Launched!
> da2 at ahc0 bus 0 target 5 lun 0
> da2: <iomega jaz 2GB E.17> Removable Direct Access SCSI-2 device
> da2: 20.000MB/s transfers (20.000MHz, offset 15)
> da2: Attempt to query device size failed: NOT READY, Medium not present
> cd0 at ahc0 bus 0 target 4 lun 0
> cd0: <TOSHIBA CD-ROM XM-6401TA 1009> Removable CD-ROM SCSI-2 device
> cd0: 20.000MB/s transfers (20.000MHz, offset 16)
> cd0: Attempt to query device size failed: NOT READY, Medium not present
> da0 at ahc0 bus 0 target 0 lun 0
> da0: <IBM DDRS-39130D DC1B> Fixed Direct Access SCSI-2 device
> da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing
> Enabled
> da0: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C)
> da1 at ahc0 bus 0 target 2 lun 0
> da1: <IBM DDRS-39130D DC1B> Fixed Direct Access SCSI-2 device
> da1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing
> Enabled
> da1: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C)
> (da2:ahc0:0:5:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
> (da2:ahc0:0:5:0): CAM Status: SCSI Status Error
> (da2:ahc0:0:5:0): SCSI Status: Check Condition
> (da2:ahc0:0:5:0): NOT READY asc:3a,0
> (da2:ahc0:0:5:0): Medium not present
> (da2:ahc0:0:5:0): Unretryable error
> Opened disk da2 -> 6
> (da2:ahc0:0:5:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
> (da2:ahc0:0:5:0): CAM Status: SCSI Status Error
> (da2:ahc0:0:5:0): SCSI Status: Check Condition
> (da2:ahc0:0:5:0): NOT READY asc:3a,0
> (da2:ahc0:0:5:0): Medium not present
> (da2:ahc0:0:5:0): Unretryable error
> Opened disk da2 -> 6
> Mounting root from ufs:/dev/da0s1a
>
> --
> Jordan K. Hubbard
> Engineering Manager, BSD technology group
> Apple Computer
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

• Previous message: Simon L. Nielsen: "Re: Typo in UPDATING"
• In reply to: Jordan K. Hubbard: "ahc driver now borked in -current?"
• Next in thread: Scott Long: "Re: ahc driver now borked in -current?"
• Reply: Scott Long: "Re: ahc driver now borked in -current?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]