From: Rafal Bujnowski <bujnor@go2.pl>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [BUG] kernel BUG at kernel/timer.c 2.6.0-test1
Date: Tue, 15 Jul 2003 10:23:39 +0200 [thread overview]
Message-ID: <20030715102339.1ff31f77.bujnor@go2.pl> (raw)
Hello!
I have something like that in my kernel-log. I had the same on 2.5.75.
It happens during cd burning (cd audio).
kernel: ------------[ cut here ]------------
kernel: kernel BUG at kernel/timer.c:166!
kernel: invalid operand: 0000 [#1]
kernel: CPU: 0
kernel: EIP: 0060:[add_timer+151/176] Not tainted
kernel: EFLAGS: 00010002
kernel: EIP is at add_timer+0x97/0xb0
kernel: eax: 00000001 ebx: e3c74000 ecx: c0361b00 edx: c040470c
kernel: esi: 00000000 edi: e3cee2a4 ebp: e3c75ed0 esp: e3c75ebc
kernel: ds: 007b es: 007b ss: 0068
kernel: Process scsi_eh_0 (pid: 9, threadinfo=e3c74000 task=e3ccc680)
kernel: Stack: 00000046 00000032 e3c74000 00000000 c040470c e3c75f00
c02755a7 e3cee2a4
kernel: c0274f80 00000032 00000000 e3cee280 c0404660 00000096
00000000 c040470c
bujnor kernel: c040471c e3c75f10 c02755e9 c040470c 00000000
e3c75f30 c0290f1f c040470c
kernel: Call Trace:
kernel: [do_reset1+567/608] do_reset1+0x237/0x260
kernel: [atapi_reset_pollfunc+0/288] atapi_reset_pollfunc+0x0/0x120
kernel: [ide_do_reset+25/32] ide_do_reset+0x19/0x20
kernel: [idescsi_reset+223/288] idescsi_reset+0xdf/0x120
kernel: [scsi_try_bus_device_reset+84/144]
scsi_try_bus_device_reset+0x54/0x90
kernel: [scsi_eh_bus_device_reset+102/288]
scsi_eh_bus_device_reset+0x66/0x120
kernel: [scsi_eh_ready_devs+40/112] scsi_eh_ready_devs+0x28/0x70
kernel: [scsi_unjam_host+192/208] scsi_unjam_host+0xc0/0xd0
kernel: [scsi_error_handler+218/288] scsi_error_handler+0xda/0x120
kernel: [scsi_error_handler+0/288] scsi_error_handler+0x0/0x120
kernel: [kernel_thread_helper+5/12] kernel_thread_helper+0x5/0xc
kernel:
kernel: Code: 0f 0b a6 00 cb 38 31 c0 eb 8e eb 0d 90 90 90 90 90 90 90
90
kernel: <6>note: scsi_eh_0[9] exited with preempt_count 3
kernel: hdc: ATAPI reset timed-out, status=0xd0
kernel: hdd: DMA disabled
And from cdrecord 2.0:
Starting new track at sector: 0
Track 01: 50 of 50 MB written (fifo 100%) [buf 99%] 4.2x.
Track 01: Total bytes read/written: 53404512/53404512 (22706 sectors).
Starting new track at sector: 22858
Track 02: 29 of 31 MB written (fifo 100%) [buf 99%]
4.2x.cdrecord: faio_wait_on_buffer for writer timed out.
Regards,
rafal
--
[ Rafal Bujnowski ][ e-mail: bujnor<at>go2.pl ]
[ http://www.bujnor.iq.pl/ ][ e-mail: bujnor<at>poczta.onet.pl ]
[ ICQ: 85602025 GG: 4174829 ][ Jabber: bujnor<at>jabberpl.org ]
next reply other threads:[~2003-07-15 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 8:23 Rafal Bujnowski [this message]
2003-07-16 6:06 ` Paul Rolland
2003-07-17 8:06 ` Rafal Bujnowski
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=20030715102339.1ff31f77.bujnor@go2.pl \
--to=bujnor@go2.pl \
--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®