From: Helge Deller <deller@gmx.de>
To: James.Bottomley@HansenPartnership.com
Cc: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] 53c700 (LASI SCSI 53c700) hang
Date: Sun, 3 Feb 2002 18:29:12 +0100 [thread overview]
Message-ID: <200202031829.12429.deller@gmx.de> (raw)
Hi James,
today my 715/64 completely stopped after some "dpkg -i"-ing.
According to the following lines from the serial console the new
SCSI driver stopped talking to my harddisk.
I'm sending this bug report now, after that this has happened
~3 times in the last 2 months.
Any ideas ?
TIA,
Helge
This is what I got on my serial console. Sadly some things before it
are missing:
scsi0 (6:0) New error handler wants to abort command
0x00 00 00 00 00 00
scsi: device set offline - not ready or command retry failed after bus reset:
host 0 channel 0 id 6 lun 0
scsi0 (6:0) New error handler wants to abort command
0x00 00 00 00 00 00
scsi: device set offline - not ready or command retry failed after bus reset:
host 0 channel 0 id 6 lun 0
scsi0 (6:0) New error handler wants to abort command
0x00 00 00 00 00 00
scsi: device set offline - not ready or command retry failed after bus reset:
host 0 channel 0 id 6 lun 0
from the dmesg:
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: QUANTUM Model: FIREBALL_TM3200S Rev: 300X
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: 6281856 512-byte hdwr sectors (3216 MB)
Partition check:
sda: sda1 sda2 sda3 sda4
next reply other threads:[~2002-02-03 17:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-03 17:29 Helge Deller [this message]
2002-02-03 18:29 ` [parisc-linux] Re: 53c700 (LASI SCSI 53c700) hang Helge Deller
2002-02-04 19:50 ` James Bottomley
2002-02-05 1:27 ` Carlos O'Donell Jr.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200202031829.12429.deller@gmx.de \
--to=deller@gmx.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=parisc-linux@lists.parisc-linux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.