From: viro@parcelfarce.linux.theplanet.co.uk
To: walt <wa1ter@myrealbox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.1] Kernel panic with ppa driver updates
Date: Sun, 8 Feb 2004 01:12:25 +0000 [thread overview]
Message-ID: <20040208011225.GB21151@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <40257081.50706@myrealbox.com>
On Sat, Feb 07, 2004 at 03:10:57PM -0800, walt wrote:
> [<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!
Ouch. So we somehow got the call of ppa_pb_claim() with dev->cur_cmd being
0x7232b2df, which wasn't a valid address. Better yet, we've got it from
ppa_attach() and that bugger had just explicitly zeroed *dev out. And that
bites us only in the built-in case.
Very interesting... Could you add
printk("dev = %p, dev->cur_cmd = %p\n", dev, dev->cur_cmd);
right before the call of ppa_pb_claim() call in __ppa_attach(), the
same - right before if (dev->wanted) in the same function and
printk("dev = %p, dev->cur_cmd set to %p\n", dev, dev->cur_cmd);
right after dev->cur_cmd = cmd; in ppa_queuecommand()?
next prev parent reply other threads:[~2004-02-08 1:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 17:36 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
2004-02-08 1:12 ` viro [this message]
[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=20040208011225.GB21151@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=wa1ter@myrealbox.com \
/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®