From: David R <spam.david.trap@unsolicited.net>
To: linux-kernel@vger.kernel.org
Subject: 2.6.8.1 Oops after raid1 disk failure
Date: Sun, 15 Aug 2004 22:17:59 +0100 [thread overview]
Message-ID: <411FD307.4000102@unsolicited.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 167 bytes --]
I got the following Oops (attached) after a drive failed in my raid1
pair. I'm assuming the kernel shouldn't really do this as the other
drive was ok?
Cheers
David
[-- Attachment #2: oops.txt --]
[-- Type: text/plain, Size: 1372 bytes --]
Aug 15 21:30:35 server kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Aug 15 21:30:35 server kernel: hdc: dma_intr: error=0x40 { Uncorrectable Error } LBAsect=100651832, sector=100651832
Aug 15 21:30:35 server kernel: end_request: I/O error, dev hdc, sector 100651832
Aug 15 21:30:35 server kernel: raid1: Disk failure on hdc3, disabling device
Oops: 0000 [#1]
PREEMPT
Modules linked in: thermal processor fan button battery ac binfmt_misc
CPU: 0
EIP: 0060:[<c0318200>] Not tainted
EFLAGS: 00010002 (2.6.8.1)
EIP is at read_intr+0x60/0x190
eax: dff8f240 ebx: 00000000 ecx: 00000000 edx: c063b10c
esi: fffffff8 edi: 00000008 ebp: 00000008 esp: ddee9f38
ds: 007b es: 007b ss: 0068
Process klogd (pid: 1778, threadinfo=ddee8000 task=dde12dd0)
Stack: c063b10c 00000001 00000008 dde12dd0 ddee8000 c063b10c 00000286 dff8f240
c030e59c c063b10c 00515380 c03181a0 c063b060 dfd0af60 04000001 00000000
ddee9fc4 c010850a 0000000e dff8f240 ddee9fc4 ddee8000 0000000e c05b4100
Call Trace:
[<c030e59c>] ide_intr+0x11c/0x1e0
[<c03181a0>] read_intr+0x0/0x190
[<c010850a>] handle_IRQ_event+0x3a/0x70
[<c01088d3>] do_IRQ+0xa3/0x170
[<c0106b28>] common_interrupt+0x18/0x20
Code: 8b 73 18 89 ef 39 ee 0f 46 fe 29 fd 8b 53 38 0f b7 42 1a 8b
<0>Kernel panic: Fatal exception in interrupt
In interrupt handler - not syncing
next reply other threads:[~2004-08-15 21:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-15 21:17 David R [this message]
2004-08-16 11:04 ` 2.6.8.1 Oops after raid1 disk failure Erik Tews
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=411FD307.4000102@unsolicited.net \
--to=spam.david.trap@unsolicited.net \
--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