[parisc-linux] Kernel panic with -pa48

[parisc-linux] Kernel panic with -pa48

[joel.soete]

Hi Grant,

I met following problem with pa48 (on a 712/80):

...
VFS: Cannot open root device "sda3" or "08:03"
Please append a correct "root=" boot option
Kernel panic: vfs Unable to mount root fs on "08:03"

(I check if the fs is still correct. And I can still boot with 2.4.9-pa45.
So it could not any more recognise ext2fs)

Is it in relation with your mail:
http://lists.parisc-linux.org/pipermail/parisc-linux/2001-October/014100.html

Thanks in adavance for advice,
        joel

PS: I had the same problem with or without LASI700 support

-------------------------------------------------
This mail sent through Tiscalinet Webmail (http://webmail.tiscali.be)

Re: [parisc-linux] Kernel panic with -pa48

[Matthew Wilcox]

On Fri, Oct 12, 2001 at 05:03:36PM +0200, joel.soete@freebel.net wrote:
> I met following problem with pa48 (on a 712/80):
> 
> ...
> VFS: Cannot open root device "sda3" or "08:03"
> Please append a correct "root=" boot option
> Kernel panic: vfs Unable to mount root fs on "08:03"
> 
> (I check if the fs is still correct. And I can still boot with 2.4.9-pa45.
> So it could not any more recognise ext2fs)

Umm.. I doubt your diagnosis is correct.  Can you send your kernel messages
that pertain to SCSI?  I have a 712/80 here which boots -pa48 just fine.

Linux 15.1.54.8 2.4.9-pa48 #125 Thu Oct 11 20:55:54 MDT 2001 parisc unknown

SCSI subsystem driver Revision: 1.00
53c700: Version 2.6 By James.Bottomley@HansenPartnership.com
scsi0: 53c710 rev 2
scsi0 : LASI SCSI 53c700
scsi0: (6:0) Synchronous at offset 8, period 100ns
  Vendor: SEAGATE   Model: ST31230N          Rev: HP04
  Type:   Direct-Access                      ANSI SCSI revision: 02
Attached scsi disk sda at scsi0, channel 0, id 6, lun 0
scsi0: (6:0) Enabling Tag Command Queuing
SCSI device sda: 2051460 512-byte hdwr sectors (1050 MB)
Partition check:
 sda: sda1 sda2

I can fsck, mount sda2 without any trouble.

> Is it in relation with your mail:
> http://lists.parisc-linux.org/pipermail/parisc-linux/2001-October/014100.html

No, that's to do with SuperIO on B1000 - J7000 workstations.  Plus,
-pa48 fixed that problem :-)

-- 
Revolutions do not require corporate support.

Re: [parisc-linux] Kernel panic with -pa48

[joel.soete]

Here is my kernel messages that pertain to SCSI (with pa42, sorry I have to made
some place):

Oct 12 15:42:52 palinux2 kernel: SCSI subsystem driver Revision: 1.00
Oct 12 15:42:52 palinux2 kernel: sim700: Configuring 53c710 (SCSI-ID 7) at
f0106100, IRQ 86, options 0
Oct 12 15:42:52 palinux2 kernel: scsi0: Revision 0x2
Oct 12 15:42:52 palinux2 kernel: scsi0: test 1 completed ok.
Oct 12 15:42:52 palinux2 kernel: scsi0 : LASI/Simple 53c7xx
Oct 12 15:42:52 palinux2 kernel:   Vendor: SEAGATE   Model: ST34572N         
Rev: HP03
Oct 12 15:42:52 palinux2 kernel:   Type:   Direct-Access                     
ANSI SCSI revision: 02
Oct 12 15:42:52 palinux2 kernel:   Vendor: HP        Model: C3325A           
Rev: HP08
Oct 12 15:42:52 palinux2 kernel:   Type:   Direct-Access                     
ANSI SCSI revision: 02
Oct 12 15:42:52 palinux2 kernel: Attached scsi disk sda at scsi0, channel 0, id
3, lun 0
Oct 12 15:42:52 palinux2 kernel: Attached scsi disk sdb at scsi0, channel 0, id
6, lun 0
Oct 12 15:42:52 palinux2 kernel: SCSI device sda: 8388314 512-byte hdwr sectors
(4295 MB)
Oct 12 15:42:52 palinux2 kernel: Partition check:
Oct 12 15:42:52 palinux2 kernel:  sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
Oct 12 15:42:52 palinux2 kernel: SCSI device sdb: 4194685 512-byte hdwr sectors
(2148 MB)
Oct 12 15:42:52 palinux2 kernel:  sdb: unknown partition table
Oct 12 15:42:52 palinux2 kernel: Lasi Harmony Audio rev. 18 at 0xf0104000, using
IRQ 82

Is it enough help?

        joel


Quoting Matthew Wilcox <willy@debian.org>:

> On Fri, Oct 12, 2001 at 05:03:36PM +0200, joel.soete@freebel.net wrote:
> > I met following problem with pa48 (on a 712/80):
> > 
> > ...
> > VFS: Cannot open root device "sda3" or "08:03"
> > Please append a correct "root=" boot option
> > Kernel panic: vfs Unable to mount root fs on "08:03"
> > 
> > (I check if the fs is still correct. And I can still boot with
> 2.4.9-pa45.
> > So it could not any more recognise ext2fs)
> 
> Umm.. I doubt your diagnosis is correct.  Can you send your kernel
> messages
> that pertain to SCSI?  I have a 712/80 here which boots -pa48 just
> fine.
> 
> Linux 15.1.54.8 2.4.9-pa48 #125 Thu Oct 11 20:55:54 MDT 2001 parisc
> unknown
> 
> SCSI subsystem driver Revision: 1.00
> 53c700: Version 2.6 By James.Bottomley@HansenPartnership.com
> scsi0: 53c710 rev 2
> scsi0 : LASI SCSI 53c700
> scsi0: (6:0) Synchronous at offset 8, period 100ns
>   Vendor: SEAGATE   Model: ST31230N          Rev: HP04
>   Type:   Direct-Access                      ANSI SCSI revision: 02
> Attached scsi disk sda at scsi0, channel 0, id 6, lun 0
> scsi0: (6:0) Enabling Tag Command Queuing
> SCSI device sda: 2051460 512-byte hdwr sectors (1050 MB)
> Partition check:
>  sda: sda1 sda2
> 
> I can fsck, mount sda2 without any trouble.
> 
> > Is it in relation with your mail:
> >
> http://lists.parisc-linux.org/pipermail/parisc-linux/2001-October/014100.html
> 
> No, that's to do with SuperIO on B1000 - J7000 workstations.  Plus,
> -pa48 fixed that problem :-)
> 
> -- 
> Revolutions do not require corporate support.
> 
> 


-------------------------------------------------
This mail sent through Tiscalinet Webmail (http://webmail.tiscali.be)

Re: [parisc-linux] Kernel panic with -pa48

[joel.soete]

Hi Matt,

Just co -pa49 and boot again but strange behaviour (as with pa45).
Here the SCSI kernel messages:

>>> it tacks a long time (15s) before displaying the LOGO
....
Oct 12 17:22:34 palinux2 kernel: SCSI subsystem driver Revision: 1.00
Oct 12 17:22:34 palinux2 kernel: 53c700: Version 2.6 By
James.Bottomley@HansenPartnership.com
Oct 12 17:22:34 palinux2 kernel: scsi0: 53c710 rev 2
Oct 12 17:22:34 palinux2 kernel: scsi0 : LASI SCSI 53c700
Oct 12 17:22:34 palinux2 kernel: scsi0: (3:0) Synchronous at offset 8, period 100ns
Oct 12 17:22:34 palinux2 kernel:   Vendor: SEAGATE   Model: ST34572N         
Rev: HP03
Oct 12 17:22:34 palinux2 kernel:   Type:   Direct-Access                     
ANSI SCSI revision: 02
Oct 12 17:22:34 palinux2 kernel: scsi0: (6:0) Synchronous at offset 8, period 100ns
Oct 12 17:22:34 palinux2 kernel: scsi0 (6:0) New error handler wants to abort
command
Oct 12 17:22:34 palinux2 kernel: ^I0x12 00 00 00 ff 00
Oct 12 17:22:34 palinux2 kernel: scsi0 (6:0) New error handler wants device reset
Oct 12 17:22:34 palinux2 kernel: ^I0x12 00 00 00 ff 00
Oct 12 17:22:34 palinux2 kernel: scsi0 (6:0) New error handler wants BUS reset,
cmd 1006e800
Oct 12 17:22:34 palinux2 kernel: ^I0x12 00 00 00 ff 00
Oct 12 17:22:34 palinux2 kernel: scsi0: Bus Reset detected, executing command
1006e800, slot 00010520, dsp 00070528[0528]
Oct 12 17:22:34 palinux2 kernel:  failing command because of reset, slot
00010520, cmnd 1006e800
Oct 12 17:22:34 palinux2 kernel: scsi0: (6:0) Synchronous at offset 8, period 100ns
Oct 12 17:22:34 palinux2 kernel: scsi0 (6:0) New error handler wants to abort
command
Oct 12 17:22:34 palinux2 kernel: ^I0x03 00 00 00 40 00
Oct 12 17:22:34 palinux2 kernel: scsi: device set offline - not ready or command
retry failed after bus reset: host 0 chan
nel 0 id 6 lun 0

>>> here it takes a long time (about 30 seconds) before continuing?


Oct 12 17:22:34 palinux2 kernel: Attached scsi disk sda at scsi0, channel 0, id
3, lun 0
Oct 12 17:22:34 palinux2 kernel: scsi0: (3:0) Enabling Tag Command Queuing
Oct 12 17:22:34 palinux2 kernel: scsi0 (3:0) New error handler wants to abort
command
Oct 12 17:22:34 palinux2 kernel: ^I0x00 00 00 00 00 00
Oct 12 17:22:34 palinux2 kernel: scsi0: Bus Reset detected, executing command
1006e800, slot 00010520, dsp 00070528[0528]
Oct 12 17:22:34 palinux2 kernel:  failing command because of reset, slot
00010520, cmnd 1006e800
Oct 12 17:22:34 palinux2 kernel:  failing command because of reset, slot
00010654, cmnd 1005e800
Oct 12 17:22:34 palinux2 kernel: scsi0 (3:0) New error handler wants device reset
Oct 12 17:22:34 palinux2 kernel: ^I0x00 00 00 00 00 00
Oct 12 17:22:34 palinux2 kernel: scsi0 (3:0) New error handler wants BUS reset,
cmd 1005e800
Oct 12 17:22:34 palinux2 kernel: ^I0x00 00 00 00 00 00
Oct 12 17:22:34 palinux2 kernel: scsi0: Bus Reset detected, executing command
00000000, slot 00000000, dsp 00070528[0528]
Oct 12 17:22:34 palinux2 kernel: scsi0: (3:0) Synchronous at offset 8, period 100ns
Oct 12 17:22:34 palinux2 kernel: SCSI device sda: 8388314 512-byte hdwr sectors
(4295 MB)
Oct 12 17:22:34 palinux2 kernel: Partition check:
Oct 12 17:22:34 palinux2 kernel:  sda: sda1 sda2 sda3 sda4 < sda5 sda6 >

I hope it will be more helpfull.
      joel

PS: Now I have to leave office. Have a nice week-end.

Quoting Matthew Wilcox <willy@debian.org>:

> On Fri, Oct 12, 2001 at 05:03:36PM +0200, joel.soete@freebel.net wrote:
> > I met following problem with pa48 (on a 712/80):
> > 
> > ...
> > VFS: Cannot open root device "sda3" or "08:03"
> > Please append a correct "root=" boot option
> > Kernel panic: vfs Unable to mount root fs on "08:03"
> > 
> > (I check if the fs is still correct. And I can still boot with
> 2.4.9-pa45.
> > So it could not any more recognise ext2fs)
> 
> Umm.. I doubt your diagnosis is correct.  Can you send your kernel
> messages
> that pertain to SCSI?  I have a 712/80 here which boots -pa48 just
> fine.
> 
> Linux 15.1.54.8 2.4.9-pa48 #125 Thu Oct 11 20:55:54 MDT 2001 parisc
> unknown
> 
> SCSI subsystem driver Revision: 1.00
> 53c700: Version 2.6 By James.Bottomley@HansenPartnership.com
> scsi0: 53c710 rev 2
> scsi0 : LASI SCSI 53c700
> scsi0: (6:0) Synchronous at offset 8, period 100ns
>   Vendor: SEAGATE   Model: ST31230N          Rev: HP04
>   Type:   Direct-Access                      ANSI SCSI revision: 02
> Attached scsi disk sda at scsi0, channel 0, id 6, lun 0
> scsi0: (6:0) Enabling Tag Command Queuing
> SCSI device sda: 2051460 512-byte hdwr sectors (1050 MB)
> Partition check:
>  sda: sda1 sda2
> 
> I can fsck, mount sda2 without any trouble.
> 
> > Is it in relation with your mail:
> >
> http://lists.parisc-linux.org/pipermail/parisc-linux/2001-October/014100.html
> 
> No, that's to do with SuperIO on B1000 - J7000 workstations.  Plus,
> -pa48 fixed that problem :-)
> 
> -- 
> Revolutions do not require corporate support.
> 
> 


-------------------------------------------------
This mail sent through Tiscalinet Webmail (http://webmail.tiscali.be)

Re: [parisc-linux] Kernel panic with -pa48

[Matthew Wilcox]

On Fri, Oct 12, 2001 at 07:42:15PM +0200, joel.soete@freebel.net wrote:
> Oct 12 17:22:34 palinux2 kernel: scsi0: (6:0) Synchronous at offset 8, period 100ns
> Oct 12 17:22:34 palinux2 kernel: scsi0 (6:0) New error handler wants to abort
> command
> Oct 12 17:22:34 palinux2 kernel: ^I0x12 00 00 00 ff 00
> Oct 12 17:22:34 palinux2 kernel: scsi0 (6:0) New error handler wants device reset
> Oct 12 17:22:34 palinux2 kernel: ^I0x12 00 00 00 ff 00
> Oct 12 17:22:34 palinux2 kernel: scsi0 (6:0) New error handler wants BUS reset,
> cmd 1006e800
> Oct 12 17:22:34 palinux2 kernel: ^I0x12 00 00 00 ff 00
> Oct 12 17:22:34 palinux2 kernel: scsi0: Bus Reset detected, executing command
> 1006e800, slot 00010520, dsp 00070528[0528]
> Oct 12 17:22:34 palinux2 kernel:  failing command because of reset, slot
> 00010520, cmnd 1006e800

Last time I saw output like this was on a machine whose disc was making
very painful noises as it attempted to spin up.  Could this be the case
for your machine?

-- 
Revolutions do not require corporate support.

Re: [parisc-linux] Kernel panic with -pa48

[Soete Joel]

Matthew Wilcox wrote:
> 
> On Fri, Oct 12, 2001 at 07:42:15PM +0200, joel.soete@freebel.net wrote:
> > Oct 12 17:22:34 palinux2 kernel: scsi0: (6:0) Synchronous at offset 8, period 100ns
> > Oct 12 17:22:34 palinux2 kernel: scsi0 (6:0) New error handler wants to abort
> > command
> > Oct 12 17:22:34 palinux2 kernel: ^I0x12 00 00 00 ff 00
> > Oct 12 17:22:34 palinux2 kernel: scsi0 (6:0) New error handler wants device reset
> > Oct 12 17:22:34 palinux2 kernel: ^I0x12 00 00 00 ff 00
> > Oct 12 17:22:34 palinux2 kernel: scsi0 (6:0) New error handler wants BUS reset,
> > cmd 1006e800
> > Oct 12 17:22:34 palinux2 kernel: ^I0x12 00 00 00 ff 00
> > Oct 12 17:22:34 palinux2 kernel: scsi0: Bus Reset detected, executing command
> > 1006e800, slot 00010520, dsp 00070528[0528]
> > Oct 12 17:22:34 palinux2 kernel:  failing command because of reset, slot
> > 00010520, cmnd 1006e800
> 
> Last time I saw output like this was on a machine whose disc was making
> very painful noises as it attempted to spin up.  Could this be the case
> for your machine?

No, neither the internal (scsi0 (6:0)) neither the external (scsi (3:0)
my hppa linux disk) do not made any noise.
But you have right: it is a long time ago that I boot on this disk (on
which I install the old mklinux for the curiosity), it may be failed
now? I will test it and let you inform.

Joel

[parisc-linux] Re: Kernel panic with -pa48

[Grant Grundler]

joel.soete@freebel.net wrote:
> Hi Grant,
> 
> I met following problem with pa48 (on a 712/80):

You might try -pa49.
712/80 doesn't have eisa either.
But I don't expect any devices on 712 to care which HBA they live under
since they are all "GSC" (mostly under LASI) devices.

grant

[parisc-linux] Re: Kernel panic with -pa48

[Soete Joel]

Grant Grundler wrote:
> 
> joel.soete@freebel.net wrote:
> > Hi Grant,
> >
> > I met following problem with pa48 (on a 712/80):
> 
> You might try -pa49.
> 712/80 doesn't have eisa either.
> But I don't expect any devices on 712 to care which HBA they live under
> since they are all "GSC" (mostly under LASI) devices.
> 
> grant

Grant,

Thanks a lot.
May be have you also read my email:
http://lists.parisc-linux.org/pipermail/parisc-linux/2001-October/014108.html

and the strange results I encountered with this -pa49

Thanks again,
	Joel

Re: [parisc-linux] Kernel panic with -pa48

[James Bottomley]

[-- Attachment #1: Type: text/plain, Size: 955 bytes --]

> Just co -pa49 and boot again but strange behaviour (as with pa45). Here
> the SCSI kernel messages:

I suspect this is probably a cabling/termination problem.  The new driver does 
fast scsi via synchronous negotiation which is much less tolerant of harware 
setup than the old asynchronous SCSI.  You can test this theory out by turning 
off async negotiation in the driver: by recompiling, I'm afraid, I haven't 
made it a config option.

If you apply the attached patch it will suppress the synchronous negotiation.  
If the driver boots your machine with no issues then it's a safe bet you have 
a cabling or termination problem.

Your next problem will be the C3325A drive:  I have one of these and it seems 
to drop tagged commands under heavy load (which annoys the SCSI error handler 
no end).  I was going to ask for it to be added to the SCSI mid-layer black 
list as being unable to handle tags, but I haven't got around to it yet.

James 



[-- Attachment #2: 53c700-no-fast.diff --]
[-- Type: text/plain , Size: 630 bytes --]

Index: drivers/scsi/53c700.c
===================================================================
RCS file: /home/jejb/CVSROOT/linux/2.4/drivers/scsi/53c700.c,v
retrieving revision 1.1.1.3.6.4
diff -u -r1.1.1.3.6.4 53c700.c
--- drivers/scsi/53c700.c	2001/09/30 15:04:17	1.1.1.3.6.4
+++ drivers/scsi/53c700.c	2001/10/13 19:46:33
@@ -720,6 +720,7 @@
 		NCR_700_writeb(BTB_TIMER_DISABLE, host, CTEST0_REG);
 		NCR_700_writeb(FULL_ARBITRATION | ENABLE_PARITY | PARITY
 			       | AUTO_ATN, host, SCNTL0_REG);
+		hostdata->fast = 0;
 	} else {
 		NCR_700_writeb(BURST_LENGTH_8 | hostdata->dmode_extra,
 			       host, DMODE_700_REG);

Re: [parisc-linux] Kernel panic with -pa48

[Grant Grundler]

James Bottomley wrote:
> Your next problem will be the C3325A drive:  I have one of these and it seems
> to drop tagged commands under heavy load (which annoys the SCSI error handler
> no end).  I was going to ask for it to be added to the SCSI mid-layer black 
> list as being unable to handle tags, but I haven't got around to it yet.

Many of the older drives for workstations have issues like this.
Workstation folks couldn't wait for the server folks to finish
testing and issues like this weren't found. That stopped being true
about 5 years ago when 1 and 2 GB (5400rpm) drives came on the market.

In general, drives smaller than 1GB are not reprogammable
and thus can't be upgraded. I don't know if C3325A is upgradeable.
If it is, the firmware for it *might* be on the same ftp site
as platform firmware - see the www.parisc-linux.org FAQ for the URL.
And not sure if there is a utility for linux to download
SCSI device firmware.

grant

Re: [parisc-linux] Kernel panic with -pa48

[James Bottomley]

grundler@puffin.external.hp.com said:
> In general, drives smaller than 1GB are not reprogammable and thus
> can't be upgraded. I don't know if C3325A is upgradeable. If it is,
> the firmware for it *might* be on the same ftp site as platform
> firmware - see the www.parisc-linux.org FAQ for the URL. And not sure
> if there is a utility for linux to download SCSI device firmware. 

I believe the fw is upgradeable (if you can find it, it's not on the ftp 
site).  Although, for a SCSI device driver writer, having misbehaving drives 
around to test with can be useful...it's a lot easier than trying to do 
sofware error injection.

Perhaps you could answer some configuration questions I have (which is why I 
was thinking the reported errors were termination or cabling related).  
Richard Hirst got LinuxCare to send me a 712/60 and a 715/50.  Both of these 
appear to have a SCSI bus running through the motherbord to a 50pin ribbon 
cable on one end and an external D50 SCSI-2 connector on the case.  There 
appears to be no termination at all on the motherboard, is that correct?

The 715/50 has slots for 3 SCSI drives along a ribbon cable which is 
terminated at one end.  However, I don't believe the other end would be 
terminated unless I put a D50 SE terminator on the external connector.   Was 
this the way they were usually delivered?

The 712/60 is even stranger: It has one SCSI drive housing and a short ribbon 
cable with no termination.  It looks like the correct configuration for this 
one would be to activate the drive's termination and also put a D50 terminator 
on the external connector?  Unfortunately, the Micropolis drive it came with 
expired in a cloud of smoke when I turned it on.  However, I was able to 
determine that the Micropolis was unterminated, so the internal bus was 
completely unterminated.

What I'm hoping is that they didn't ship this way, they just evolved into 
these anomalous configurations over time as bits fell off and drives were 
replaced.  The problem is that the new lasi700 driver is going to drive the 
SCSI bus (at least for the 53c710 based lasi subsystems) at about twice times 
the speed of the old one and with high REQ/ACK offsets, so what were marginal 
configurations may suddenly become non-functional ones.

At the very least, I suppose I need to add sync and tag disable options to the 
driver.

James

Re: [parisc-linux] Kernel panic with -pa48

[Andreas Deresch]

> The 712/60 is even stranger: It has one SCSI drive housing and a short ribbon
> cable with no termination.  It looks like the correct configuration for this
> one would be to activate the drive's termination and also put a D50 terminator
> on the external connector?  Unfortunately, the Micropolis drive it came with
> expired in a cloud of smoke when I turned it on.  However, I was able to
> determine that the Micropolis was unterminated, so the internal bus was
> completely unterminated.
I don't know about 715, but 712 is supposed to be terminated onboard =>
internal drive not terminated, external branch only terminated when drive
present. (That's what the docs say, too)

ad

Re: [parisc-linux] Kernel panic with -pa48

[Grant Grundler]

James Bottomley wrote:
> Both of these appear to have a SCSI bus running through the motherbord
> to a 50pin ribbon cable on one end and an external D50 SCSI-2 connector
> on the case.  There appears to be no termination at all on the motherboard,
> is that correct?

AFAIK, yes - that's correct. The 50-pin (narrow SE SCSI) should be terminated
on the external 50-pin high-density connecter. The 50-in ribbon cable has a
terminator at the "internal" end. It's all one bus.

> The 715/50 has slots for 3 SCSI drives along a ribbon cable which is 
> terminated at one end.

It's intended for 2 HDs and a CD-ROM or SCSI FLoppy.

>  However, I don't believe the other end would be 
> terminated unless I put a D50 SE terminator on the external connector.   Was 
> this the way they were usually delivered?

I think so.

> The 712/60 is even stranger: It has one SCSI drive housing and a short ribbon
> cable with no termination.  It looks like the correct configuration for this 
> one would be to activate the drive's termination and also put a D50 terminato
>   r 
> on the external connector?

Yes. But it works w/o termination too since the cable is vry short
if nothing external is connected.

grant