From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Eran Mann <emann@mrv.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [OOPS] paport related OOPS since 2.6.11-bk7
Date: Mon, 28 Mar 2005 20:01:04 +0100 [thread overview]
Message-ID: <20050328200104.B2222@flint.arm.linux.org.uk> (raw)
In-Reply-To: <42483C84.6000700@mrv.com>; from emann@mrv.com on Mon, Mar 28, 2005 at 07:19:00PM +0200
On Mon, Mar 28, 2005 at 07:19:00PM +0200, Eran Mann wrote:
> Mar 28 17:13:44 eran kernel: EIP is at parport_pc_pci_remove+0x18/0x40 [parport_pc]
Are you sure you reinstalled the kernel modules after rebuilding?
parport_pc_pci_remove() was 0x40 bytes long before, and still seems
to be. Also, the Code: lines are identical. This means you're
running the same (unpatched) code as you were before, so you aren't
actually running my fix.
Can you double-check please?
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-03-28 19:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 16:45 [OOPS] paport related OOPS since 2.6.11-bk7 Eran Mann
2005-03-28 16:58 ` Russell King
2005-03-28 17:19 ` Eran Mann
2005-03-28 19:01 ` Russell King [this message]
2005-03-28 20:44 ` Eran Mann
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=20050328200104.B2222@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@osdl.org \
--cc=emann@mrv.com \
--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;
as well as URLs for NNTP newsgroup(s).