b2k 64bit kernel failled to boot [Was: [parisc-linux-cvs] linux-2.6 willy]

Wed Jan 5 09:24:11 MST 2005

> -- Original Message --
> Date: Wed, 5 Jan 2005 14:55:40 +0000
> From: Matthew Wilcox <matthew at wil.cx>
> To: Joel Soete <soete.joel at tiscali.be>
> Cc: parisc-linux-cvs at lists.parisc-linux.org,
> 	Matthew Wilcox <willy at parisc-linux.org>
> Subject: Re: b2k 64bit kernel failled to boot [Was: [parisc-linux-cvs]
linux-2.6
> willy]
> 
> 
> On Wed, Jan 05, 2005 at 09:45:51AM +0100, Joel Soete wrote:
> > sym0: <895a> rev 0x1 at pci 0000:00:0f.0 irq 129
> > sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking
> > sym0: SCSI BUS has been reset.
> > scsi0 : sym-2.1.18n
> > sym0:0:0: ABORT operation started.
> > sym0:0:0: ABORT operation timed-out.
> > sym0:0:0: DEVICE RESET operation started.
> > sym0:0:0: DEVICE RESET operation timed-out.
> > sym0:0:0: BUS RESET operation started.
> > sym0:0:0: BUS RESET operation timed-out.
> > sym0:0:0: HOST RESET operation started.
> > sym0: SCSI BUS has been reset.
> 
> This is symptomatic of the sym2 driver not
> receiving an interrupt.
I hoping to find some diff related to this driver too but nothing?

>  I believe I've tracked it down to
> http://lists.parisc-linux.org/pipermail/parisc-linux-cvs/2005-January/035115.html
> but that was *before* -pa4.  Are you really sure that was upstream -pa4
> that booted on your b2k?
> 
Yes, I just do a diff between my pa4 and pa5 and it match exactely the patch
available <http://cvs.parisc-linux.org/download/linux-2.6/patch-2.6.10-pa4-pa5.gz>
As I couldn't reboot pa5, to do some more test,  i also apply grant's pacache.S
patch to pa4 tree, rebuild this kernel and reboot it without pb?

btw: no pb to boot pa5 on b180 but similar pb on n4k (not exactely the same:
where b2k hang after: the last "sym0: SCSI BUS has been reset."
the n4k continue to scan all devices on all ctrl:
eth1: Digital DS21143 Tulip rev 65 at ffffffff8a040000, 00:30:6E:21:14:B4,
IRQ 384.
sym0: <895> rev 0x1 at pci 0000:00:01.0 irq 129
sym0: No NVRAM, ID 7, Fast-40, SE, parity checking
sym0: SCSI BUS has been reset.
scsi0 : sym-2.1.18n
elevator: using anticipatory as default io scheduler
sym0:0:0: ABORT operation started.
sym0:0:0: ABORT operation timed-out.
sym0:0:0: DEVICE RESET operation started.
sym0:0:0: DEVICE RESET operation timed-out.
sym0:0:0: BUS RESET operation started.
sym0:0:0: BUS RESET operation timed-out.
sym0:0:0: HOST RESET operation started.
sym0: SCSI BUS has been reset.
sym0:0:0: HOST RESET operation timed-out.
scsi: Device offlined - not ready after error recovery: host 0 channel 0
id 0 lun 0
sym0:1:0: ABORT operation started.
[...]
sym0:14:0: HOST RESET operation timed-out.
scsi: Device offlined - not ready after error recovery: host 0 channel 0
id 14 lun 0
sym0:15:0: ABORT operation started.
sym0:15:0: ABORT operation timed-out.
sym0:15:0: DEVICE RESET operation started.
sym0:15:0: DEVICE RESET operation timed-out.
sym0:15:0: BUS RESET operation started.
sym0:15:0: BUS RESET operation timed-out.
sym0:15:0: HOST RESET operation started.
sym0: SCSI BUS has been reset.
sym0:15:0: HOST RESET operation timed-out.
scsi: Device offlined - not ready after error recovery: host 0 channel 0
id 15 lun 0
sym1: <875> rev 0x37 at pci 0000:00:02.0 irq 130
sym1: No NVRAM, ID 7, Fast-20, SE, parity checking
sym1: SCSI BUS has been reset.
scsi1 : sym-2.1.18n
sym1:0:0: ABORT operation started.
sym1:0:0: ABORT operation timed-out.
sym1:0:0: DEVICE RESET operation started.
sym1:0:0: DEVICE RESET operation timed-out.
sym1:0:0: BUS RESET operation started.
sym1:0:0: BUS RESET operation timed-out.
sym1:0:0: HOST RESET operation started.
sym1: SCSI BUS has been reset.
sym1:0:0: HOST RESET operation timed-out.
scsi: Device offlined - not ready after error recovery: host 1 channel 0
id 0 lun 0
sym1:1:0: ABORT operation started.
[...]
sym1:14:0: HOST RESET operation timed-out.
scsi: Device offlined - not ready after error recovery: host 1 channel 0
id 14 lun 0
sym1:15:0: ABORT operation started.
sym1:15:0: ABORT operation timed-out.
sym1:15:0: DEVICE RESET operation started.
sym1:15:0: DEVICE RESET operation timed-out.
sym1:15:0: BUS RESET operation started.
sym1:15:0: BUS RESET operation timed-out.
sym1:15:0: HOST RESET operation started.
sym1: SCSI BUS has been reset.
sym1:15:0: HOST RESET operation timed-out.
scsi: Device offlined - not ready after error recovery: host 1 channel 0
id 15 lun 0
sym2: <875> rev 0x37 at pci 0000:00:02.1 irq 131
sym2: No NVRAM, ID 7, Fast-20, SE, parity checking
sym2: SCSI BUS has been reset.
scsi2 : sym-2.1.18n
sym2:0:0: ABORT operation started.
sym2:0:0: ABORT operation timed-out.
sym2:0:0: DEVICE RESET operation started.
sym2:0:0: DEVICE RESET operation timed-out.
sym2:0:0: BUS RESET operation started.
sym2:0:0: BUS RESET operation timed-out.
sym2:0:0: HOST RESET operation started.
sym2: SCSI BUS has been reset.
sym2:0:0: HOST RESET operation timed-out.
scsi: Device offlined - not ready after error recovery: host 2 channel 0
id 0 lun 0
sym2:1:0: ABORT operation started.
[...]
sym2:15:0: ABORT operation started.
sym2:15:0: ABORT operation timed-out.
sym2:15:0: DEVICE RESET operation started.
sym2:15:0: DEVICE RESET operation timed-out.
sym2:15:0: BUS RESET operation started.
sym2:15:0: BUS RESET operation timed-out.
sym2:15:0: HOST RESET operation started.
sym2: SCSI BUS has been reset.
sym2:15:0: HOST RESET operation timed-out.
scsi: Device offlined - not ready after error recovery: host 2 channel 0
id 15 lun 0
st: Version 20041025, fixed bufsize 32768, s/g segs 256
md: linear personality registered as nr 1
md: raid0 personality registered as nr 2
md: raid1 personality registered as nr 3
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
NET: Registered protocol family 2
IP: routing cache hash table of 8192 buckets, 192Kbytes
TCP: Hash tables configured (established 131072 bind 43690)
NET: Registered protocol family 1
NET: Registered protocol family 17
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "sda5" or unknown-block(2,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
 <0>Rebooting in 120 seconds..

even missed what pa4 well seen:
eth1: Digital DS21143 Tulip rev 65 at ffffffff8a040000, 00:30:6E:21:14:B4,
IRQ 384.
sym0: <895> rev 0x1 at pci 0000:00:01.0 irq 129
sym0: No NVRAM, ID 7, Fast-40, SE, parity checking
sym0: SCSI BUS has been reset.
scsi0 : sym-2.1.18n
sym0: SCSI BUS mode change from SE to SE.
sym0: SCSI BUS has been reset.
elevator: using anticipatory as default io scheduler
  Vendor: SEAGATE   Model: ST39103LW         Rev: HP04
  Type:   Direct-Access                      ANSI SCSI revision: 02
sym0:8:0: tagged command queuing enabled, command queue depth 16.
 target0:0:8: Beginning Domain Validation
sym0:8: wide asynchronous.
sym0:8: FAST-20 WIDE SCSI 40.0 MB/s ST (50.0 ns, offset 15)
 target0:0:8: Domain Validation skipping write tests
 target0:0:8: Ending Domain Validation
sym1: <875> rev 0x37 at pci 0000:00:02.0 irq 130
sym1: No NVRAM, ID 7, Fast-20, SE, parity checking
sym1: SCSI BUS has been reset.
scsi1 : sym-2.1.18n
sym2: <875> rev 0x37 at pci 0000:00:02.1 irq 131
sym2: No NVRAM, ID 7, Fast-20, SE, parity checking
sym2: SCSI BUS has been reset.
scsi2 : sym-2.1.18n
st: Version 20041025, fixed bufsize 32768, s/g segs 256
SCSI device sda: 17783112 512-byte hdwr sectors (9105 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 17783112 512-byte hdwr sectors (9105 MB)
SCSI device sda: drive cache: write back
 sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 >
Attached scsi disk sda at scsi0, channel 0, id 8, lun 0
Attached scsi generic sg0 at scsi0, channel 0, id 8, lun 0,  type 0

hth anyway,
    Joel

---------------------------------------------------------------------------
Tiscali vous offre 3 mois d'ADSL et 3 mois de DVD gratuits...profitez-en...
http://reg.tiscali.be/adsl/default.asp?lg=FR