From: Rob Landley <rob@landley.net>
To: linux-kernel@vger.kernel.org
Cc: linux-mips@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>,
Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: 2.6.24 panics initializing ne2k in mips.
Date: Mon, 28 Jan 2008 23:51:00 -0600 [thread overview]
Message-ID: <200801282351.01776.rob@landley.net> (raw)
In-Reply-To: <200801280217.38273.rob@landley.net>
On Monday 28 January 2008 02:17:37 Rob Landley wrote:
> The 2.6.23 kernel built for mips with the attached .config works fine for
> me under qemu (both big endian and little endian), but a 2.6.24 mips kernel
> segfaults initializing the ne2k driver (again when run under qemu).
>
> I've traced it to this commit:
>
> http://kernel.org/hg/linux-2.6/rev/74258
>
> Version 74257 works, 74258 does not.
For the git users in the audience, that's commit
30e748a507919a41f9eb4d10b4954f453325a37d
I just confirmed that:
A) today's -git still exhibits this bug.
B) Backing out the above irq-twiddling patch makes it stop exhibiting the bug
for me. (Boots to a shell prompt, it can use the network, etc.)
So that patch is definitely the trigger for the panic, and reverting the patch
is one way to fix it. (And probably the best way to make it work for
2.6.24.1.)
Rob
--
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
next prev parent reply other threads:[~2008-01-29 5:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 8:17 2.6.24 panics initializing ne2k in mips Rob Landley
2008-01-29 5:51 ` Rob Landley [this message]
2008-01-29 11:16 ` Ralf Baechle
2008-01-29 11:20 ` [PATCH 1/2] IRQ_NOPROBE helper functions Ralf Baechle
2008-01-29 11:21 ` [PATCH 2/2] MIPS: Mark all but i8259 interrupts as no-probe Ralf Baechle
2008-01-31 7:56 ` [PATCH 1/2] IRQ_NOPROBE helper functions Rob Landley
2008-02-22 14:17 ` 2.6.24 panics initializing ne2k in mips Samuel Masham
2008-02-22 22:19 ` Rob Landley
2008-02-23 7:56 ` Samuel Masham
2008-02-23 21:43 ` Rob Landley
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=200801282351.01776.rob@landley.net \
--to=rob@landley.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=ralf@linux-mips.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