From: walt <wa1ter@myrealbox.com>
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.1] Kernel panic with ppa driver updates
Date: Sat, 07 Feb 2004 15:10:57 -0800 [thread overview]
Message-ID: <40257081.50706@myrealbox.com> (raw)
In-Reply-To: <20040206182844.GJ21151@parcelfarce.linux.theplanet.co.uk>
viro@parcelfarce.linux.theplanet.co.uk wrote:
> On Fri, Feb 06, 2004 at 09:36:24AM -0800, walt wrote:
>
>>This panic started with the bk changesets applied by Linus yesterday.
>>
>>The ppa driver works fine when compiled as a module, but when compiled in
>>I get this during boot:
(panic message snipped)
> Could you post the actual oops?...
Whew! I had to relearn everything I was happy to forget about
serial communications to get this! I even stopped to repair a
broken RS-232 break-out box that I haven't used in years ;0)
I hope this helps:
ppa: Version 2.07 (for Linux 2.4.x)
Unable to handle kernel paging request at virtual address 7232b403
printing eip:
c027bc25
*pde = 00000000
Oops: 0002 [#1]
CPU: 0
EIP: 0060:[<c027bc25>] Not tainted
EFLAGS: 00010002
EIP is at got_it+0x15/0x40
eax: 7232b2df ebx: dff92000 ecx: 00000778 edx: dfd67940
esi: dfd67940 edi: 00000286 ebp: 00000000 esp: dff93f10
ds: 007b es: 007b ss: 0068
Process swapper (pid: 1, threadinfo=dff92000 task=dff918c0)
Stack: c027bd3b dfd67940 dfd67940 dff93f8c dff93f6c fffffff0 c027d577 dfd67940
c03b1a06 00000000 c027bc50 00000000 00000000 dfd67940 00001c70 00000000
dff918c0 c011aa40 dff93f78 dff93f78 00001c70 dff92000 00001c70 00000000
Call Trace:
[<c027bd3b>] ppa_pb_claim+0x7b/0x80
[<c027d577>] __ppa_attach+0x127/0x350
[<c027bc50>] ppa_wakeup+0x0/0x70
[<c011aa40>] autoremove_wake_function+0x0/0x50
[<c011aa40>] autoremove_wake_function+0x0/0x50
[<c023a746>] parport_register_driver+0x36/0x70
[<c0485b83>] ppa_driver_init+0x23/0x30
[<c046e74c>] do_initcalls+0x2c/0xa0
[<c012c9ff>] init_workqueues+0xf/0x30
[<c01050d2>] init+0x32/0x140
[<c01050a0>] init+0x0/0x140
[<c0106fe9>] kernel_thread_helper+0x5/0xc
Code: c7 80 24 01 00 00 01 00 00 00 c3 8b 42 50 b9 01 00 00 00 ba
<0>Kernel panic: Attempted to kill init!
next prev parent reply other threads:[~2004-02-07 23:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 17:36 [2.6.1] Kernel panic with ppa driver updates walt
2004-02-06 18:28 ` viro
2004-02-06 20:45 ` walt
2004-02-07 0:06 ` viro
2004-02-07 23:10 ` walt [this message]
2004-02-08 1:12 ` viro
[not found] <fa.db71fu4.1gju7jo@ifi.uio.no>
[not found] ` <fa.n1cha2m.1hhep3a@ifi.uio.no>
2004-02-08 3:35 ` walt
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=40257081.50706@myrealbox.com \
--to=wa1ter@myrealbox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.