From: "Christian Kujau" <evil@g-house.de>
To: linux-kernel@vger.kernel.org
Cc: akpm@osdl.org
Subject: SCSI ABORT with 2.6.17-rc4-mm1
Date: Fri, 19 May 2006 21:49:44 +0100 (BST) [thread overview]
Message-ID: <62331.192.18.1.5.1148071784.squirrel@housecafe.dyndns.org> (raw)
[sorry for repost, local MTA problems here...]
Hi list, Hi Andrew,
I cannot boot 2.6.17-rc4-mm1 because my rootdisk is a scsi disk and upon
scsi-init (SYM53C8XX_2) I'm getting:
May 19 15:39:55 prinz sym0: <895> rev 0x1 at pci 0000:02:09.0 irq 161
May 19 15:39:55 prinz sym0: Tekram NVRAM, ID 7, Fast-40, LVD, parity checking
May 19 15:39:55 prinz sym0: SCSI BUS has been reset.
May 19 15:39:55 prinz scsi0 : sym-2.2.3
May 19 15:40:08 prinz 0:0:0:0: ABORT operation started.
May 19 15:40:13 prinz 0:0:0:0: ABORT operation timed-out.
May 19 15:40:13 prinz 0:0:0:0: DEVICE RESET operation started.
May 19 15:40:18 prinz 0:0:0:0: DEVICE RESET operation timed-out.
May 19 15:40:18 prinz 0:0:0:0: BUS RESET operation started.
May 19 15:40:23 prinz 0:0:0:0: BUS RESET operation timed-out.
May 19 15:40:23 prinz 0:0:0:0: HOST RESET operation started.
May 19 15:40:23 prinz sym0: SCSI BUS has been reset.
May 19 15:40:28 prinz 0:0:0:0: HOST RESET operation timed-out.
May 19 15:40:28 prinz 0:0:0:0: scsi: Device offlined - not ready after
error recovery
May 19 15:40:33 prinz 0:0:1:0: ABORT operation started.
May 19 15:40:38 prinz 0:0:1:0: ABORT operation timed-out.
May 19 15:40:38 prinz 0:0:1:0: DEVICE RESET operation started.
May 19 15:40:43 prinz 0:0:1:0: DEVICE RESET operation timed-out.
May 19 15:40:43 prinz 0:0:1:0: BUS RESET operation started.
I have backed out drivers-scsi-use-array_size-macro.patch, but to no
avail. There are other scsi-related patches in the broken-out
mm-directory, any hint which one to try first? Sometimes they're dependent
on each other, so I find it not easy to just "patch -R" all "*scsi*.patch"
files.
Please see http://www.nerdbynature.de/bits/2.6.17-rc4-mm1/ for a
netsconsole-dmesg for 2.6.17-rc4 (working fine) and a the -mm1.
I've tried different .configs for -mm1, created with:
- yes '' | make oldconfig (config-2.6-mm.2.6.17-rc4-mm1.oldconfig_default)
- yes 'N' | make oldconfig (config-2.6-mm.2.6.17-rc4-mm1.oldconfig_no)
- make oldlconfig (interactive, config-2.6-mm.2.6.17-rc4-mm1.oldconfig_my)
Thanks,
Christian.
--
BOFH excuse #442:
Trojan horse ran out of hay
--
BOFH excuse #442:
Trojan horse ran out of hay
next reply other threads:[~2006-05-19 20:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-19 20:49 Christian Kujau [this message]
2006-05-19 21:10 ` Andrew Morton
2006-05-19 22:57 ` Mel Gorman
2006-05-19 23:30 ` Andrew Morton
2006-05-20 0:35 ` Mel Gorman
2006-05-20 3:54 ` Christian Kujau
2006-05-20 0:28 ` Christian Kujau
2006-05-20 0:08 ` Christian Kujau
2006-05-20 0:40 ` Christian Kujau
2006-05-26 18:26 ` Christian Kujau
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=62331.192.18.1.5.1148071784.squirrel@housecafe.dyndns.org \
--to=evil@g-house.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®