From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: 2.5.64-mm6: kernel BUG at kernel/timer.c:155!
Date: 13 Mar 2003 09:22:47 -0800 [thread overview]
Message-ID: <1047576167.1318.4.camel@ixodes.goop.org> (raw)
I was reading back a freshly burned CD from my shiny new Plexwriter
48/24/48A. I'm using ide-scsi, so this is an iso9660 filesystem mounted
from /dev/scd0. After reading for a while, apparently successfully, it
started failing with the messages below:
spurious 8259A interrupt: IRQ7.
hdc: lost interrupt
ide-scsi: CoD != 0 in idescsi_pc_intr
ide-scsi: abort called for 9677
ide-scsi: abort called for 9674
hdc: ATAPI reset complete
hdc: irq timeout: status=0x80 { Busy }
hdc: ATAPI reset complete
hdc: irq timeout: status=0x80 { Busy }
hdc: ATAPI reset complete
hdc: irq timeout: status=0x80 { Busy }
hdc: status timeout: status=0x80 { Busy }
hdc: drive not ready for command
hdc: ATAPI reset complete
hdc: irq timeout: status=0x80 { Busy }
hdc: ATAPI reset complete
hdc: irq timeout: status=0x80 { Busy }
hdc: status timeout: status=0x80 { Busy }
hdc: drive not ready for command
hdc: ATAPI reset complete
hdc: irq timeout: status=0x80 { Busy }
hdc: ATAPI reset complete
hdc: irq timeout: status=0x80 { Busy }
hdc: status timeout: status=0x80 { Busy }
hdc: drive not ready for command
hdc: ATAPI reset complete
hdc: irq timeout: status=0x80 { Busy }
hdc: ATAPI reset complete
hdc: irq timeout: status=0x80 { Busy }
hdc: status timeout: status=0x80 { Busy }
hdc: drive not ready for command
hdc: ATAPI reset complete
ide-scsi: abort called for 9674
ide-scsi: abort called for 9675
ide-scsi: abort called for 9676
ide-scsi: reset called for 9677
------------[ cut here ]------------
kernel BUG at kernel/timer.c:155!
invalid operand: 0000 [#1]
CPU: 0
EIP: 0060:[<c011fc41>] Tainted: PF
EFLAGS: 00010002
EIP is at add_timer+0xdb/0xe8
eax: 00000001 ebx: c1b3b5e4 ecx: c0322820 edx: c03d33fc
esi: 00000096 edi: c020b506 ebp: f7d8feac esp: f7d8fea4
ds: 007b es: 007b ss: 0068
Process scsi_eh_0 (pid: 9, threadinfo=f7d8e000 task=c1b7cd00)
Stack: 00000001 c1b3b5c0 f7d8fed0 c020b44c c1b3b5e4 00000000 00000082 00000000
00000000 c03d33fc c03d33fc f7d8ff00 c020baf4 c03d33fc c020b506 00000032
00000000 c1b3b5c0 c03d3350 00000096 00000000 c03d33fc c03d340c f7d8ff18
Call Trace:
[<c020b44c>] ide_set_handler+0x48/0x74
[<c020baf4>] do_reset1+0x214/0x232
[<c020b506>] atapi_reset_pollfunc+0x0/0x11a
[<c020bb40>] ide_do_reset+0x2e/0x62
[<c02267b4>] idescsi_reset+0xc0/0xf6
[<c0220a36>] scsi_try_bus_device_reset+0x46/0x66
[<c0220abb>] scsi_eh_bus_device_reset+0x65/0x108
[<c0221224>] scsi_eh_ready_devs+0x28/0x74
[<c022137f>] scsi_unjam_host+0xa1/0xa4
[<c022142f>] scsi_error_handler+0xad/0xdc
[<c0221382>] scsi_error_handler+0x0/0xdc
[<c0107209>] kernel_thread_helper+0x5/0xc
Code: 0f 0b 9b 00 62 11 2e c0 e9 41 ff ff ff 55 31 c0 89 e5 83 ec
next reply other threads:[~2003-03-13 17:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 17:22 Jeremy Fitzhardinge [this message]
2003-03-13 17:45 ` 2.5.64-mm6: kernel BUG at kernel/timer.c:155! Jeremy Fitzhardinge
2003-03-13 17:54 ` Jens Axboe
2003-03-13 18:04 ` Jeremy Fitzhardinge
2003-03-13 19:02 ` Jens Axboe
2003-03-14 9:24 ` 2.5.64-mm6: oops in elv_remove_request Jeremy Fitzhardinge
2003-03-14 10:42 ` Jens Axboe
2003-03-14 10:06 ` Jeremy Fitzhardinge
2003-03-14 10:31 ` Jeremy Fitzhardinge
2003-03-14 11:37 ` Jens Axboe
2003-03-14 17:59 ` Jeremy Fitzhardinge
2003-03-14 18:07 ` Jens Axboe
2003-03-14 22:19 ` Jeremy Fitzhardinge
2003-03-15 8:15 ` Jens Axboe
2003-03-16 2:54 ` Jeremy Fitzhardinge
2003-03-17 8:05 ` Jens Axboe
2003-03-17 16:56 ` Jeremy Fitzhardinge
2003-03-24 13:14 ` Jens Axboe
2003-03-14 20:33 ` Jens Axboe
2003-03-14 22:15 ` Jeremy Fitzhardinge
2003-03-15 8:15 ` Jens Axboe
2003-03-13 20:52 ` 2.5.64-mm6: kernel BUG at kernel/timer.c:155! Aravind
-- strict thread matches above, loose matches on Subject: below --
2003-03-13 18:28 Felipe Alfaro Solana
2003-03-13 19:04 ` Jens Axboe
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=1047576167.1318.4.camel@ixodes.goop.org \
--to=jeremy@goop.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