In the 2.6.21 kernel the sym53c8xx_2 SCSI controller changed in a way that QEMU's virtual SCSI controller doesn't handle this properly:
Here's what 2.6.20 does during boot: > Loading iSCSI transport class v2.0-724. > PCI: enabling device 0000:00:0c.0 (0140 -> 0143) > sym0: <895a> rev 0x0 at pci 0000:00:0c.0 irq 27 > sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking > sym0: SCSI BUS has been reset. > scsi0 : sym-2.2.3 > scsi 0:0:0:0: Direct-Access QEMU QEMU HARDDISK 0.9. PQ: 0 ANSI: > 3 target0:0:0: tagged command queuing enabled, command queue depth 16. > target0:0:0: Beginning Domain Validation > target0:0:0: Domain Validation skipping write tests > target0:0:0: Ending Domain Validation > scsi 0:0:2:0: CD-ROM QEMU QEMU CD-ROM 0.9. PQ: 0 ANSI: > 3 target0:0:2: tagged command queuing enabled, command queue depth 16. > target0:0:2: Beginning Domain Validation > target0:0:2: Domain Validation skipping write tests > target0:0:2: Ending Domain Validation > SCSI device sda: 524288 512-byte hdwr sectors (268 MB) > sda: Write Protect is off > SCSI device sda: write cache: enabled, read cache: enabled, doesn't support > DPO or FUA SCSI device sda: 524288 512-byte hdwr sectors (268 MB) > sda: Write Protect is off > SCSI device sda: write cache: enabled, read cache: enabled, doesn't support > DPO or FUA sda: unknown partition table > sd 0:0:0:0: Attached scsi disk sda > sr0: scsi3-mmc drive: 16x/50x cd/rw xa/form2 cdda tray > Uniform CD-ROM driver Revision: 3.20 > mice: PS/2 mouse device common for all mice > TCP cubic registered > NET: Registered protocol family 1 > NET: Registered protocol family 17 > NET: Registered protocol family 15 > 802.1Q VLAN Support v1.8 Ben Greear <[EMAIL PROTECTED]> > All bugs added by David S. Miller <[EMAIL PROTECTED]> > VFS: Mounted root (ext2 filesystem). > Freeing init memory: 100K > sh-2.05b# And here's what 2.6.21 does: > Loading iSCSI transport class v2.0-724. > PCI: enabling device 0000:00:0c.0 (0140 -> 0143) > sym0: <895a> rev 0x0 at pci 0000:00:0c.0 irq 0 > sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking > sym0: SCSI BUS has been reset. > scsi0 : sym-2.2.3 > scsi 0:0:0:0: ABORT operation started. > scsi 0:0:0:0: ABORT operation timed-out. > scsi 0:0:0:0: DEVICE RESET operation started. > scsi 0:0:0:0: DEVICE RESET operation timed-out. > scsi 0:0:0:0: BUS RESET operation started. > scsi 0:0:0:0: BUS RESET operation timed-out. > scsi 0:0:0:0: HOST RESET operation started. > sym0: SCSI BUS has been reset. > scsi 0:0:0:0: HOST RESET operation timed-out. > scsi 0:0:0:0: scsi: Device offlined - not ready after error recovery > scsi 0:0:1:0: ABORT operation started. > scsi 0:0:1:0: ABORT operation timed-out. > scsi 0:0:1:0: DEVICE RESET operation started. > scsi 0:0:1:0: DEVICE RESET operation timed-out. > scsi 0:0:1:0: BUS RESET operation started. > scsi 0:0:1:0: BUS RESET operation timed-out. > scsi 0:0:1:0: HOST RESET operation started. > sym0: SCSI BUS has been reset. [ Skip lots of the same... ] > scsi 0:0:14:0: HOST RESET operation started. > sym0: SCSI BUS has been reset. > scsi 0:0:14:0: HOST RESET operation timed-out. > scsi 0:0:14:0: scsi: Device offlined - not ready after error recovery > scsi 0:0:15:0: ABORT operation started. > scsi 0:0:15:0: ABORT operation timed-out. > scsi 0:0:15:0: DEVICE RESET operation started. > scsi 0:0:15:0: DEVICE RESET operation timed-out. > scsi 0:0:15:0: BUS RESET operation started. > scsi 0:0:15:0: BUS RESET operation timed-out. > scsi 0:0:15:0: HOST RESET operation started. > sym0: SCSI BUS has been reset. > scsi 0:0:15:0: HOST RESET operation timed-out. > scsi 0:0:15:0: scsi: Device offlined - not ready after error recovery > mice: PS/2 mouse device common for all mice > TCP cubic registered > NET: Registered protocol family 1 > NET: Registered protocol family 17 > NET: Registered protocol family 15 > 802.1Q VLAN Support v1.8 Ben Greear <[EMAIL PROTECTED]> > All bugs added by David S. Miller <[EMAIL PROTECTED]> > VFS: Cannot open root device "sda" or unknown-block(0,0) > Please append a correct "root=" boot option; here are the available > partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(0,0) Rebooting in 1 seconds.. I am _totally_ out of my depth trying to debug this. I continue to poke at it, but it was brought to my attention that the list doesn't know about it... Rob -- The Google cluster became self-aware at 2:14am EDT August 29, 2007...
