* [parisc-linux] Bug in kernel 2.4.23 concerning use of SCSI
@ 2004-04-26 14:08 JKonrad
2004-04-26 16:36 ` Joel Soete
0 siblings, 1 reply; 3+ messages in thread
From: JKonrad @ 2004-04-26 14:08 UTC (permalink / raw)
To: parisc-linux
Hi,
using kernel 2.4.23-pa3, which I downloaded from http://parisc-linux.org/~rbrad/vmlinux-2.4.23-pa3.bz2 because I needed MUX support.
Machine is a HP K-200 with three CPUs (although, since this is not an smp kernel, should not be important);
I have a 50 GB SCSI-drive attached to SCSI1 (the Low Voltage Controller where the CD-Rom is attached to); Whenever I try to format the partition (50GB, the whole disk) I get the following:
> Writing superblocks and filesystem accounting information: scsi1 (0:0)
> Target is suffering from tag starvation.
> SCSI disk error : host 1 channel 0 id 0 lun 0 return code = 8
> I/O error: dev 08:41, sector 34078720
> SCSI disk error : host 1 channel 0 id 0 lun 0 return code = 8
> I/O error: dev 08:41, sector 34078722
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 04 90 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 04 7c 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 05 c4 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 05 ac 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 05 10 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 05 9c 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 04 00 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 04 80 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 05 c4 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 05 ac 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 05 10 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 05 9c 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 04 00 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 04 80 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 02 04 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 01 d0 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 01 fc 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 02 00 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 04 8c 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 04 f4 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants device reset
> 0x2a 00 04 90 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants BUS reset, cmd 21e46e00
> 0x2a 00 04 90 00 28 00 00 08 00
> scsi1: Bus Reset detected, executing command 00000000, slot 00000000,
> dsp 001704a8[04a8]
> failing command because of reset, slot 21e88654, cmnd 21e46e00
> failing command because of reset, slot 21e88788, cmnd 21e47e00
> failing command because of reset, slot 21e888bc, cmnd 21e47800
> failing command because of reset, slot 21e889f0, cmnd 21e46200
> failing command because of reset, slot 21e88b24, cmnd 21e46000
> failing command because of reset, slot 21e88c58, cmnd 21e46400
> failing command because of reset, slot 21e88d8c, cmnd 21e46600
> failing command because of reset, slot 21e88ec0, cmnd 21e46a00
> failing command because of reset, slot 21e88ff4, cmnd 21e47c00
> failing command because of reset, slot 21e89128, cmnd 21e47a00
> failing command because of reset, slot 21e8925c, cmnd 21e47600
> failing command because of reset, slot 21e894c4, cmnd 21e47400
> failing command because of reset, slot 21e895f8, cmnd 21e47200
> failing command because of reset, slot 21e8972c, cmnd 21e47000
>
> Stack Dump:
> 21e90740: 0004ff0e 00000000 21e90670 21e90650
> 21e90730: 00000000 10228630 00000000 21e90000
> 21e90720: 00000000 00000000 00000000 21e90000
> 21e90710: 00000001 00000002 21f36000 00000002
> 21e90700: 21f3c040 1006c000 103aa010 103aa010
> 21e906f0: 1032b010 1020e448 103cd000 00000001
>
> Kernel addresses on the stack:
> Kernel Fault: Code=26 regs=21e90740 (Addr=00000048)
>
> YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
> PSW: 00000000000001001111111100001110 Not tainted
> r00-03 00000000 103ebab8 10228630 21e8972c
> r04-07 21e46e00 1020de94 21f60400 00002000
> r08-11 000003e8 0000ffff 00002000 00001000
> r12-15 00001002 21f61ea0 000000fd f0100000
> r16-19 f0000fe0 f0000074 f000006c 00000080
> r20-23 00000000 21e889f0 10065860 00000000
> r24-27 00000000 00000000 21f60404 10316010
> r28-31 21f60404 10326c00 21e90740 1020e51c
> sr0-3 00000000 00000003 00000000 00000003
> sr4-7 00000000 00000000 00000000 00000000
>
> IASQ: 00000000 00000000 IAOQ: 102286bc 102286c0
> IIR: 4a930090 ISR: 00000000 IOR: 00000048
> CPU: 0 CR30: 21e90000 CR31: 103d8000
> ORIG_R28: 00000000
Then the machine freezes, I need to reboot. When I make a partition with 40GB and format it, I get an error message very much the same, but I get a prompt and can continue to work. When I use a
partition of 30GB, it works. What seems to be the problem here?
Greets,
Jay
^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: [parisc-linux] Bug in kernel 2.4.23 concerning use of SCSI
2004-04-26 14:08 [parisc-linux] Bug in kernel 2.4.23 concerning use of SCSI JKonrad
@ 2004-04-26 16:36 ` Joel Soete
2004-04-30 19:22 ` Joel Soete
0 siblings, 1 reply; 3+ messages in thread
From: Joel Soete @ 2004-04-26 16:36 UTC (permalink / raw)
To: JKonrad, parisc-linux
Hello,
Just for curiosity, can you join a dmesg file.
Thanks,
Joel
> -- Original Message --
> To: parisc-linux@lists.parisc-linux.org
> From: JKonrad@linotype.com
> Date: Mon, 26 Apr 2004 16:08:58 +0200
> Subject: [parisc-linux] Bug in kernel 2.4.23 concerning use of SCSI
>
>
> Hi,
using kernel 2.4.23-pa3, which I downloaded from http://parisc-linux.org/~rbrad/vmlinux-2.4.23-pa3.bz2
because I needed MUX support.
Machine is a HP K-200 with three CPUs (although, since this is not an smp
kernel, should not be important);
>
I have a 50 GB SCSI-drive attached to SCSI1 (the Low Voltage Controller where
the CD-Rom is attached to); Whenever I try to format the partition (50GB,
the whole disk) I get the following:
> Writing superblocks and filesystem accounting information
> scsi1 (0:0)
> Target is suffering from tag starvation.
> SCSI disk error : host 1 channel 0 id 0 lun 0 return code = 8
> I/O error: dev 08:41, sector 34078720
> SCSI disk error : host 1 channel 0 id 0 lun 0 return code = 8
> I/O error: dev 08:41,
> sector 34078722
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 04 90 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 04 7c 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants t
> abort command
> 0x2a 00 05 c4 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 05 ac 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 05 10 00 28 00 00 08 00
>
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 05 9c 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 04 00 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> > 0x2a 00 04 80 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 05 c4 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 05 ac 00 28 00 00 08 00
> scsi1 (0:0)
> ew error handler wants to abort command
> 0x2a 00 05 10 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 05 9c 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 0
> 04 00 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 04 80 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 02 04 00 28 00 00 08 00
> scsi1 (0:0) New error handle
> wants to abort command
> 0x2a 00 01 d0 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 01 fc 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 02 00 00 28 00
> 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 04 8c 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants to abort command
> 0x2a 00 04 f4 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants device r
> set
> 0x2a 00 04 90 00 28 00 00 08 00
> scsi1 (0:0) New error handler wants BUS reset, cmd 21e46e00
> 0x2a 00 04 90 00 28 00 00 08 00
> scsi1: Bus Reset detected, executing command 00000000, slot 00000000,
> dsp 001704a8[04a8]
> fai
> ing command because of reset, slot 21e88654, cmnd 21e46e00
> failing command because of reset, slot 21e88788, cmnd 21e47e00
> failing command because of reset, slot 21e888bc, cmnd 21e47800
> failing command because of reset, slot 21e889f0, cmnd 21e4
> 200
> failing command because of reset, slot 21e88b24, cmnd 21e46000
> failing command because of reset, slot 21e88c58, cmnd 21e46400
> failing command because of reset, slot 21e88d8c, cmnd 21e46600
> failing command because of reset, slot 21e88ec0
> cmnd 21e46a00
> failing command because of reset, slot 21e88ff4, cmnd 21e47c00
> failing command because of reset, slot 21e89128, cmnd 21e47a00
> failing command because of reset, slot 21e8925c, cmnd 21e47600
> failing command because of reset, sl
> t 21e894c4, cmnd 21e47400
> failing command because of reset, slot 21e895f8, cmnd 21e47200
> failing command because of reset, slot 21e8972c, cmnd 21e47000
>
> Stack Dump:
> 21e90740: 0004ff0e 00000000 21e90670 21e90650
> 21e90730: 00000000 102
> 8630 00000000 21e90000
> 21e90720: 00000000 00000000 00000000 21e90000
> 21e90710: 00000001 00000002 21f36000 00000002
> 21e90700: 21f3c040 1006c000 103aa010 103aa010
> 21e906f0: 1032b010 1020e448 103cd000 00000001
>
> Kernel addresses on the
> stack:
> Kernel Fault: Code=26 regs=21e90740 (Addr=00000048)
>
> YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
> PSW: 00000000000001001111111100001110 Not tainted
> r00-03 00000000 103ebab8 10228630 21e8972c
> r04-07 21e46e00 1020de94 21f60400 000020
> 0
> r08-11 000003e8 0000ffff 00002000 00001000
> r12-15 00001002 21f61ea0 000000fd f0100000
> r16-19 f0000fe0 f0000074 f000006c 00000080
> r20-23 00000000 21e889f0 10065860 00000000
> r24-27 00000000 00000000 21f60404 10316010
> r28-31 21f6
> 404 10326c00 21e90740 1020e51c
> sr0-3 00000000 00000003 00000000 00000003
> sr4-7 00000000 00000000 00000000 00000000
>
> IASQ: 00000000 00000000 IAOQ: 102286bc 102286c0
> IIR: 4a930090 ISR: 00000000 IOR: 00000048
> CPU: 0 CR30:
> 21e90000 CR31: 103d8000
> ORIG_R28: 00000000
Then the machine freezes, I need to reboot. When I make a partition with
40GB and format it, I get an error message very much the same, but I get
a prompt and can continue to work. When I use a
partitio
> of 30GB, it works. What seems to be the problem here?
Greets,
Jay
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-lin
> x
----------------------------------------------------------------------------------------
Tiscali ADSL: 35 €/mois, la meilleure offre du marché!
http://reg.tiscali.be/default.asp?lg=fr
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [parisc-linux] Bug in kernel 2.4.23 concerning use of SCSI
2004-04-26 16:36 ` Joel Soete
@ 2004-04-30 19:22 ` Joel Soete
0 siblings, 0 replies; 3+ messages in thread
From: Joel Soete @ 2004-04-30 19:22 UTC (permalink / raw)
To: Joel Soete; +Cc: JKonrad, parisc-linux
Hello Jay,
Do you find a solution?
Joel Soete wrote:
> Hello,
>
> Just for curiosity, can you join a dmesg file.
>
> Thanks,
> Joel
>
>
>>-- Original Message --
>>To: parisc-linux@lists.parisc-linux.org
>>From: JKonrad@linotype.com
>>Date: Mon, 26 Apr 2004 16:08:58 +0200
>>Subject: [parisc-linux] Bug in kernel 2.4.23 concerning use of SCSI
>>
>>
>>Hi,
>
>
> using kernel 2.4.23-pa3, which I downloaded from http://parisc-linux.org/~rbrad/vmlinux-2.4.23-pa3.bz2
> because I needed MUX support.
>
> Machine is a HP K-200 with three CPUs (although, since this is not an smp
> kernel, should not be important);
>
>
> I have a 50 GB SCSI-drive attached to SCSI1 (the Low Voltage Controller where
> the CD-Rom is attached to); Whenever I try to format the partition (50GB,
> the whole disk) I get the following:
>
My question was in fact to confirm me that you are using the same driver then the one I used on my c110:
[snip]
53c700: Version 2.8 By James.Bottomley@HansenPartnership.com
scsi1: 53c710 rev 2
scsi1 : LASI SCSI 53c700
on which I only connected a SE (single ended) rw cdrom drive which works perfectly but also I never tested so big disk on this
controler.
Is your 50Gb disk is also a single ended one, a low or high voltage?
Doesn't it need some special hw config (jumper) to be a single ended scsi device?
Is your chain is well terminated?
Cheers,
Joel
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-04-30 19:22 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-04-26 14:08 [parisc-linux] Bug in kernel 2.4.23 concerning use of SCSI JKonrad
2004-04-26 16:36 ` Joel Soete
2004-04-30 19:22 ` Joel Soete
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.