2.2.0pre2 SCSI problems, more (fwd)

2.2.0pre2 SCSI problems, more (fwd)

[Geert Uytterhoeven]

---------- Forwarded message ----------
Date: Thu, 31 Dec 1998 15:03:02 -0800 (PST)
From: Peter Abrahamsen <p1rabbit@halcyon.com>
To: Tom Rini <tmrini@ntplx.net>,
     Geert Uytterhoeven <Geert.Uytterhoeven@cs.kuleuven.ac.be>
Subject: 2.2.0pre2 SCSI problems, more

Hallo!

  I have been having troubles with SCSI on all kernels after 2.1.130.
Actually, the 2.1.130 I'm using is prebuilt so that may have something to do
with it. 2.1.127 (built by myself) worked fine. Here is an excerpt from my
boot log for 2.2.0pre2:

scsi0: MESH
scsi1: 53c94
scsi: 2 hosts
mesh: target 0 aborted        <-- ??? this is my problem...
mesh: target 2 synchronous at 5 MB/s
Vendor: QUANTUM Model: FIREBALL SE2.1s
[followed by normal scsi information on the rest of my busses]

  Booting from 2.1.130, the /proc/scsi/scsi entry for the device skipped
above is:

Host: scsi0 Channel: 00 Id: 00 Lun: 00
   Vendor: QUANTUM Model: FIREBALL1280S Rev: 630G
   Type: Direct-Access

  On the boot previous to that one, it seemed to go fine, until the
following:

Machine check in kernel mode.
Caused by (from msr) : regs cba7dbf0 Machine check signam - probably due to
mm fault with mmu off
NIP: D0832290 XER: E000BE6F CR: D0832238 REGS: cba7dbf0 TRAP: 0200
NSR: 00001030 TASK: cba7c000 [76] 'insmod' mm -> pgd cbc9000

  that's copied down from a stickie, so maybe a number or formatting is wrong
somewhere... So are the boot messages for SCSI stuff above, for that matter.
  Normally (I only got that Machine check thing once) it drops me to single
user mode, and gives me a prompt. Mount lists /dev/sdb5 mounted at / (which
is as it should be, except that it had told me earlier that my ZIP drive had
become sdb since my first drive wasn't detected).

I am using debian-powerpc potato, libc6 2.0.100... Please tell me if there
is any more information I can give you.

Thanks,

Peter

--
Peter Abrahamsen
p1rabbit@halcyon.com
http://www.halcyon.com/p1rabbit
PGP: 0xC279D219: C080 6D6F 4492 C63D 20B7 8D41 8B17 C781 C279 D219



[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: 2.2.0pre2 SCSI problems, more (fwd)

[Brad Midgley]

hey!

that's the SAME drive that aborts for me in 2.2.0p4. mine is also
connected to mesh. my 2.1.30 identifies it as: 

Vendor: QUANTUM   Model: FIREBALL1280S     Rev: 630G

i don't see it blacklisted. something just makes it want to abort now. the
scary thing about this is this drive ships STANDARD in 1gig 7500's. that's
a lot of computers that suddenly can't run linux. 

peter, did you ever try booting mklinux? it always got an abort when it
came across that drive... 

brad

On Mon, 4 Jan 1999, Geert Uytterhoeven wrote:

> 
> ---------- Forwarded message ----------
> Date: Thu, 31 Dec 1998 15:03:02 -0800 (PST)
> From: Peter Abrahamsen <p1rabbit@halcyon.com>
> To: Tom Rini <tmrini@ntplx.net>,
>      Geert Uytterhoeven <Geert.Uytterhoeven@cs.kuleuven.ac.be>
> Subject: 2.2.0pre2 SCSI problems, more
> 
> Hallo!
> 
>   I have been having troubles with SCSI on all kernels after 2.1.130.
> Actually, the 2.1.130 I'm using is prebuilt so that may have something to do
> with it. 2.1.127 (built by myself) worked fine. Here is an excerpt from my
> boot log for 2.2.0pre2:
> 
> scsi0: MESH
> scsi1: 53c94
> scsi: 2 hosts
> mesh: target 0 aborted        <-- ??? this is my problem...
> mesh: target 2 synchronous at 5 MB/s
> Vendor: QUANTUM Model: FIREBALL SE2.1s
> [followed by normal scsi information on the rest of my busses]
> 
>   Booting from 2.1.130, the /proc/scsi/scsi entry for the device skipped
> above is:
> 
> Host: scsi0 Channel: 00 Id: 00 Lun: 00
>    Vendor: QUANTUM Model: FIREBALL1280S Rev: 630G
>    Type: Direct-Access
> 
>   On the boot previous to that one, it seemed to go fine, until the
> following:
> 
> Machine check in kernel mode.
> Caused by (from msr) : regs cba7dbf0 Machine check signam - probably due to
> mm fault with mmu off
> NIP: D0832290 XER: E000BE6F CR: D0832238 REGS: cba7dbf0 TRAP: 0200
> NSR: 00001030 TASK: cba7c000 [76] 'insmod' mm -> pgd cbc9000
> 
>   that's copied down from a stickie, so maybe a number or formatting is wrong
> somewhere... So are the boot messages for SCSI stuff above, for that matter.
>   Normally (I only got that Machine check thing once) it drops me to single
> user mode, and gives me a prompt. Mount lists /dev/sdb5 mounted at / (which
> is as it should be, except that it had told me earlier that my ZIP drive had
> become sdb since my first drive wasn't detected).
> 
> I am using debian-powerpc potato, libc6 2.0.100... Please tell me if there
> is any more information I can give you.
> 
> Thanks,
> 
> Peter
> 
> --
> Peter Abrahamsen
> p1rabbit@halcyon.com
> http://www.halcyon.com/p1rabbit
> PGP: 0xC279D219: C080 6D6F 4492 C63D 20B7 8D41 8B17 C781 C279 D219
> 
> 
> 


[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: 2.2.0pre2 SCSI problems, more (fwd)

[Peter Abrahamsen]

On Mon, 4 Jan 1999, Brad Midgley wrote:

> that's the SAME drive that aborts for me in 2.2.0p4. mine is also
> connected to mesh. my 2.1.30 identifies it as: 
> Vendor: QUANTUM   Model: FIREBALL1280S     Rev: 630G

Yep, that's the one.

> i don't see it blacklisted. something just makes it want to abort now. the
> scary thing about this is this drive ships STANDARD in 1gig 7500's. that's
> a lot of computers that suddenly can't run linux. 

As well as 7600s :)

> peter, did you ever try booting mklinux? it always got an abort when it
> came across that drive... 

Nope, never tried. Vger 2.1.130 from CVS a/o a few days ago works fine.
I've found that the other problem I had was caused by having a serial.o
module, which my system automatically loaded when it ran setserial.
Please address or cc responses to me personally, i am not on the
linuxppc-dev list.

Thanks,

Peter

--
Peter Abrahamsen
p1rabbit@halcyon.com
http://www.halcyon.com/p1rabbit
PGP: 0xC279D219: C080 6D6F 4492 C63D 20B7 8D41 8B17 C781 C279 D219


[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: 2.2.0pre2 SCSI problems, more (fwd)

[Paul Mackerras]

> that's the SAME drive that aborts for me in 2.2.0p4. mine is also
> connected to mesh. my 2.1.30 identifies it as: 
> 
> Vendor: QUANTUM   Model: FIREBALL1280S     Rev: 630G
> 
> i don't see it blacklisted. something just makes it want to abort now. the
> scary thing about this is this drive ships STANDARD in 1gig 7500's. that's
> a lot of computers that suddenly can't run linux. 

I have a 7600 but it no longer has this disk in it (it's in another
machine).  Could somebody with a 7600 and this disk and the kernel
sources do the following: change drivers/scsi/mesh.c to #define
MESH_DBG and to initialize mesh_debug_targets to 1, and send me the
resulting debug log?

I may be able to take my fireball1280S out of the machine it's in if
we can't resolve the problem soon.

Paul.

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: 2.2.0pre2 SCSI problems, more (fwd)

[Brad Midgley]

paul,

i removed all devices from the second bus except for an 80M quantum drive
that i used to boot from.  (everyone should be warned that you should boot
from a non-mesh device when mesh debugging is on! :) 

a strange thing, and maybe bad news for debugging: the drive is discovered
properly by the debugging kernel. maybe it's a timing issue. i hope the
logs can tell you something. 

the problem drive is on scsi id 1.

brad

AWACS: error, status = 40210f
...
scsi0 : MESH
scsi1 : 53C94
scsi : 2 hosts.
mesh_start: c2fbce00 ser=1 tgt=0 cmd= 0 0 0 0 0 0 use_sg=0 buffer=c2ffbd70 bufflen=256
mesh: sending 6 msg bytes: c0 1 3 1 32 f
got 5 message bytes: 1 3 1 32 f
mesh: target 0 synchronous at 5.0 MB/s
mesh: status is 0
got 1 message bytes: 0
mesh_done: result = 0, data_ptr=0, buflen=256
buffer = c2 ff bd 80 c0 20 5b a4
mesh_start: c2fbce00 ser=2 tgt=0 cmd= 12 0 0 0 ff 0 use_sg=0 buffer=c2ffbd70 bufflen=256
mesh: sending 1 msg bytes: c0
mesh: status is 0
got 1 message bytes: 0
mesh_done: result = 0, data_ptr=132, buflen=256
buffer = 0 0 2 2 7f 0 0 12
  Vendor: QUANTUM   Model: PD1225S           Rev: 3110
  Type:   Direct-Access                      ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
mesh: target 1 synchronous at 5.0 MB/s
  Vendor: QUANTUM   Model: FIREBALL1280S     Rev: 630G
  Type:   Direct-Access                      ANSI SCSI revision: 02
Detected scsi disk sdb at scsi0, channel 0, id 1, lun 0
mesh: target 3 synchronous at 4.2 MB/s
  Vendor: SONY      Model: CD-ROM CDU-8005   Rev: 1.0j
  Type:   CD-ROM                             ANSI SCSI revision: 02
Detected scsi CD-ROM sr0 at scsi0, channel 0, id 3, lun 0
  Vendor: QUANTUM   Model: CTS80S            Rev: 4.2 
  Type:   Direct-Access                      ANSI SCSI revision: 02
Detected scsi disk sdc at scsi1, channel 0, id 4, lun 0
scsi : detected 1 SCSI cdrom 3 SCSI disks total.
sr0: disc change detected.
Uniform CDROM driver Revision: 2.51
mesh_start: c2fbc600 ser=24 tgt=0 cmd= 0 0 0 0 0 0 use_sg=0 buffer=c2fb2000 bufflen=512
mesh: sending 1 msg bytes: c0
mesh: status is 0
got 1 message bytes: 0
mesh_done: result = 0, data_ptr=0, buflen=512
buffer = 0 0 0 0 0 0 0 0
mesh_start: c2fbc600 ser=25 tgt=0 cmd= 25 0 0 0 0 0 0 0 0 0 use_sg=0 buffer=c2fb2000 bufflen=8
mesh: sending 1 msg bytes: c0
mesh: status is 0
got 1 message bytes: 0
mesh_done: result = 0, data_ptr=8, buflen=8
SCSI device sda: hdwr sector= 512 bytes. Sectors= 2395980 [1169 MB] [1.2 GB]
SCSI device sdb: hdwr sector= 512 bytes. Sectors= 2503872 [1222 MB] [1.2 GB]
SCSI device sdc: hdwr sector= 512 bytes. Sectors= 166200 [81 MB] [0.1 GB]
eth0: MACE at 00:05:02:e0:03:4f
Partition check:
 sda:<4>mesh_start: c2fbc600 ser=30 tgt=0 cmd= 8 0 0 0 2 0 use_sg=1 buffer=c2fb2000 bufflen=1024
mesh: sending 1 msg bytes: c0
got 1 message bytes: 4
mesh: reselected by target 0
mesh: saved_ptr=0 goes_out=0 cmd=c2fbc600
got 1 message bytes: 80
mesh: status is 0
got 1 message bytes: 0
mesh_done: result = 0, data_ptr=1024, buflen=1024
mesh_start: c2fbc600 ser=31 tgt=0 cmd= 8 0 0 0 2 0 use_sg=1 buffer=c2fb2000 bufflen=1024
mesh: sending 1 msg bytes: c0
mesh: status is 0
got 1 message bytes: 0
mesh_done: result = 0, data_ptr=1024, buflen=1024
 sda1<4>mesh_start: c2fbc600 ser=32 tgt=0 cmd= 8 0 0 2 2 0 use_sg=1 buffer=c2fb2000 bufflen=1024
mesh: sending 1 msg bytes: c0
mesh: status is 0
got 1 message bytes: 0
mesh_done: result = 0, data_ptr=1024, buflen=1024
 sda2 sda3<4>mesh_start: c2fbc600 ser=33 tgt=0 cmd= 8 0 0 4 2 0 use_sg=1 buffer=c2fb2000 bufflen=1024
mesh: sending 1 msg bytes: c0
mesh: status is 0
got 1 message bytes: 0
mesh_done: result = 0, data_ptr=1024, buflen=1024
 sda4 sda5
 sdb: sdb1 sdb2 sdb3 sdb4
 sdc: sdc1 sdc2 sdc3 sdc4 sdc5
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 124k init 32k prep
NET4: AppleTalk 0.18 for Linux NET4.0


[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: 2.2.0pre2 SCSI problems, more (fwd)

[Paul Mackerras]

Brad Midgley <brad@pht.com> wrote:

> i removed all devices from the second bus except for an 80M quantum drive
> that i used to boot from.  (everyone should be warned that you should boot
> from a non-mesh device when mesh debugging is on! :) 
> 
> a strange thing, and maybe bad news for debugging: the drive is discovered
> properly by the debugging kernel. maybe it's a timing issue. i hope the
> logs can tell you something. 

A timing issue sounds likely, as nothing much has changed in the mesh
driver (or the rest of the SCSI code AFAIK) lately.  If you set
mesh_debug_targets back to 0 but still have MESH_DBG defined, it won't
print all that debugging info but it will still record all the log
information (which is a relatively lightweight thing to do), and if
you get the target aborting, it will print the log.

Paul.

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: 2.2.0pre2 SCSI problems, more (fwd)

[Brad Midgley]

turning off the target debugging "allowed" the drive to abort again.  log
is appended. 

brad

DB mouse driver installed.
AWACS: error, status = 40210f
DMA sound driver installed, using 4 buffers of 32k.
RAM disk driver initialized:  16 RAM disks of 4096K size
loop: registered device at major 7
fd0: SWIM3 floppy controller 
scsi0 : MESH
scsi1 : 53C94
scsi : 2 hosts.
mesh: target 0 synchronous at 5.0 MB/s
  Vendor: QUANTUM   Model: PD1225S           Rev: 3110
  Type:   Direct-Access                      ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
mesh: target 1 aborted
mesh log 1: bs=0000 ph=01 start cmd=c2fdbe00
mesh log 1: bs=0000 ph=01 about to arb, intr/exc/err/fc=00000000
mesh log 1: bs=6000 ph=01 after arb, intr/exc/err/fc=01000000
mesh log 1: bs=6000 ph=01 interrupt intr/err/exc/seq=01000001
mesh log 1: bs=6000 ph=01 cmd_complete fc=0
mesh log 1: bs=6000 ph=02 start_phase err/exc/fc/seq = 00000001
mesh log 1: bs=4008 ph=02 interrupt intr/err/exc/seq=01000022
mesh log 1: bs=4008 ph=02 cmd_complete fc=0
mesh log 1: bs=4008 ph=02 Selecting phase at command completion
mesh log 1: bs=4008 ph=03 start_phase err/exc/fc/seq = 00000022
mesh log 1: bs=0000 ph=03 interrupt intr/err/exc/seq=05400000
mesh log 1: bs=0000 ph=03 error err/exc/fc/cl=40000600
mesh log: bs=4013 ph=46 t0 start_phase err/exc/fc/seq = 00000014
mesh log: bs=4017 ph=46 t0 interrupt intr/err/exc/seq=01000018
mesh log: bs=4017 ph=46 t0 cmd_complete fc=1
mesh log: bs=4017 ph=06 t0 msgin msg=01000301
mesh log: bs=4017 ph=06 t0 start_phase err/exc/fc/seq = 00000018
mesh log: bs=4017 ph=06 t0 enbresel intr/exc/err/fc=00000000
mesh log: bs=0000 ph=06 t0 interrupt intr/err/exc/seq=01000009
mesh log: bs=0000 ph=06 t0 cmd_complete fc=0
mesh log: bs=0000 ph=01 t1 start cmd=c2fdbe00
mesh log: bs=0000 ph=01 t1 about to arb, intr/exc/err/fc=00000000
mesh log: bs=6000 ph=01 t1 after arb, intr/exc/err/fc=01000000
mesh log: bs=6000 ph=01 t1 interrupt intr/err/exc/seq=01000001
mesh log: bs=6000 ph=01 t1 cmd_complete fc=0
mesh log: bs=6000 ph=02 t1 start_phase err/exc/fc/seq = 00000001
mesh log: bs=4008 ph=02 t1 interrupt intr/err/exc/seq=01000022
mesh log: bs=4008 ph=02 t1 cmd_complete fc=0
mesh log: bs=4008 ph=02 t1 Selecting phase at command completion
mesh log: bs=4008 ph=03 t1 start_phase err/exc/fc/seq = 00000022
mesh log: bs=0000 ph=03 t1 interrupt intr/err/exc/seq=05400000
mesh log: bs=0000 ph=03 t1 error err/exc/fc/cl=40000600
mesh: target 3 synchronous at 4.2 MB/s
  Vendor: SONY      Model: CD-ROM CDU-8005   Rev: 1.0j
  Type:   CD-ROM                             ANSI SCSI revision: 02
Detected scsi CD-ROM sr0 at scsi0, channel 0, id 3, lun 0
  Vendor: QUANTUM   Model: CTS80S            Rev: 4.2 
  Type:   Direct-Access                      ANSI SCSI revision: 02
Detected scsi disk sdb at scsi1, channel 0, id 4, lun 0
scsi : detected 1 SCSI cdrom 2 SCSI disks total.
sr0: disc change detected.
Uniform CDROM driver Revision: 2.51
SCSI device sda: hdwr sector= 512 bytes. Sectors= 2395980 [1169 MB] [1.2 GB]
SCSI device sdb: hdwr sector= 512 bytes. Sectors= 166200 [81 MB] [0.1 GB]
eth0: MACE at 00:05:02:e0:03:4f
Partition check:
 sda: sda1 sda2 sda3 sda4 sda5
 sdb: sdb1 sdb2 sdb3 sdb4 sdb5



[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: 2.2.0pre2 SCSI problems, more (fwd)

[Brad Midgley]

paul,

i'd like to try fixing this by inserting delays into the mesh target
discovery. could you point me to the right place to do this and the
correct way to introduce a delay in the kernel? 

(i can't check to see if you've already done this in vger--it's refusing
cvs connections)

thanks
brad

> 
> turning off the target debugging "allowed" the drive to abort again.  log
> is appended. 
> 
> brad
> 
> DB mouse driver installed.
> AWACS: error, status = 40210f
> DMA sound driver installed, using 4 buffers of 32k.
> RAM disk driver initialized:  16 RAM disks of 4096K size
> loop: registered device at major 7
> fd0: SWIM3 floppy controller 
> scsi0 : MESH
> scsi1 : 53C94
> scsi : 2 hosts.
> mesh: target 0 synchronous at 5.0 MB/s
>   Vendor: QUANTUM   Model: PD1225S           Rev: 3110
>   Type:   Direct-Access                      ANSI SCSI revision: 02
> Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
> mesh: target 1 aborted
> mesh log 1: bs=0000 ph=01 start cmd=c2fdbe00
> mesh log 1: bs=0000 ph=01 about to arb, intr/exc/err/fc=00000000
> mesh log 1: bs=6000 ph=01 after arb, intr/exc/err/fc=01000000
> mesh log 1: bs=6000 ph=01 interrupt intr/err/exc/seq=01000001
> mesh log 1: bs=6000 ph=01 cmd_complete fc=0
> mesh log 1: bs=6000 ph=02 start_phase err/exc/fc/seq = 00000001
> mesh log 1: bs=4008 ph=02 interrupt intr/err/exc/seq=01000022
> mesh log 1: bs=4008 ph=02 cmd_complete fc=0
> mesh log 1: bs=4008 ph=02 Selecting phase at command completion
> mesh log 1: bs=4008 ph=03 start_phase err/exc/fc/seq = 00000022
> mesh log 1: bs=0000 ph=03 interrupt intr/err/exc/seq=05400000
> mesh log 1: bs=0000 ph=03 error err/exc/fc/cl=40000600
> mesh log: bs=4013 ph=46 t0 start_phase err/exc/fc/seq = 00000014
> mesh log: bs=4017 ph=46 t0 interrupt intr/err/exc/seq=01000018
> mesh log: bs=4017 ph=46 t0 cmd_complete fc=1
> mesh log: bs=4017 ph=06 t0 msgin msg=01000301
> mesh log: bs=4017 ph=06 t0 start_phase err/exc/fc/seq = 00000018
> mesh log: bs=4017 ph=06 t0 enbresel intr/exc/err/fc=00000000
> mesh log: bs=0000 ph=06 t0 interrupt intr/err/exc/seq=01000009
> mesh log: bs=0000 ph=06 t0 cmd_complete fc=0
> mesh log: bs=0000 ph=01 t1 start cmd=c2fdbe00
> mesh log: bs=0000 ph=01 t1 about to arb, intr/exc/err/fc=00000000
> mesh log: bs=6000 ph=01 t1 after arb, intr/exc/err/fc=01000000
> mesh log: bs=6000 ph=01 t1 interrupt intr/err/exc/seq=01000001
> mesh log: bs=6000 ph=01 t1 cmd_complete fc=0
> mesh log: bs=6000 ph=02 t1 start_phase err/exc/fc/seq = 00000001
> mesh log: bs=4008 ph=02 t1 interrupt intr/err/exc/seq=01000022
> mesh log: bs=4008 ph=02 t1 cmd_complete fc=0
> mesh log: bs=4008 ph=02 t1 Selecting phase at command completion
> mesh log: bs=4008 ph=03 t1 start_phase err/exc/fc/seq = 00000022
> mesh log: bs=0000 ph=03 t1 interrupt intr/err/exc/seq=05400000
> mesh log: bs=0000 ph=03 t1 error err/exc/fc/cl=40000600
> mesh: target 3 synchronous at 4.2 MB/s
>   Vendor: SONY      Model: CD-ROM CDU-8005   Rev: 1.0j
>   Type:   CD-ROM                             ANSI SCSI revision: 02
> Detected scsi CD-ROM sr0 at scsi0, channel 0, id 3, lun 0
>   Vendor: QUANTUM   Model: CTS80S            Rev: 4.2 
>   Type:   Direct-Access                      ANSI SCSI revision: 02
> Detected scsi disk sdb at scsi1, channel 0, id 4, lun 0
> scsi : detected 1 SCSI cdrom 2 SCSI disks total.
> sr0: disc change detected.
> Uniform CDROM driver Revision: 2.51
> SCSI device sda: hdwr sector= 512 bytes. Sectors= 2395980 [1169 MB] [1.2 GB]
> SCSI device sdb: hdwr sector= 512 bytes. Sectors= 166200 [81 MB] [0.1 GB]
> eth0: MACE at 00:05:02:e0:03:4f
> Partition check:
>  sda: sda1 sda2 sda3 sda4 sda5
>  sdb: sdb1 sdb2 sdb3 sdb4 sdb5
> 
> 
> 




[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]