From: Daniel Egger <degger@fhm.edu>
To: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: 2.5.64-ac3: Crash in ide_init_queue
Date: 14 Mar 2003 22:13:30 +0100 [thread overview]
Message-ID: <1047676410.7452.34.camel@sonja> (raw)
[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]
Hija,
my new motherboard with KT400 chipset oopses in ide_init_queue on bootup
with the follow output:
Oops: 0000
CPU: 0
EIP: 0060:[<00000000>] Not tainted
EFLAGS: 00010282
EIP is at 0x0
eax: c044af44 ebx: c044aff0 ecx: 00000000 edx: 00000000
esi: c044b000 edi: c044af44 ebp: c151dee8 esp: c151ded0
ds: 007b es: 007b ss: 0068
Process swapper (pid: 1, threadinfo=c151c000 task=dff8e040)
Stack: c0263dff c044aff0 00000001 c03cd660 c044aff0 c1527ef4 c151df30 c0264006
c044aff0 c0262b10
Call Trace:
[<c0263dff>] ide_init_queue+0x9f/0xb0
[<c0264006>] init_irq+0x1f6/0x3d0
[<c0262b10>] ide_intr+0x0/0x180
[<c0264658>] hwif_init+0xe8/0x290
[<c0264924>] ideprobe_init+0xf4/0x110
[<c02209d1>] driver_register+0x31/0x40
[<c010507d>] init+0x3d/0x160
[<c0105040>] init+0x0/0x160
[<c010740d>] kernel_thread_helper+0x5/0x18
Code: Bad EIP value.
The system doesn't have a harddrive, both channels are enabled,
the second bus has a TOSHIBA Combo DVD/CD-R SD-R1002 conntected
as master device. Disabling the secondary channel channel fixes
the problem.
Should I bugzill it?
--
Servus,
Daniel
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-03-14 21:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-14 21:13 Daniel Egger [this message]
2003-03-14 21:25 ` 2.5.64-ac3: Crash in ide_init_queue Jens Axboe
2003-03-15 15:25 ` Daniel Egger
2003-03-15 15:33 ` Daniel Egger
2003-03-15 16:31 ` Jens Axboe
2003-03-15 17:31 ` Daniel Egger
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=1047676410.7452.34.camel@sonja \
--to=degger@fhm.edu \
--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