From: Matt Bernstein <mb--lkml@dcs.qmul.ac.uk>
Cc: Andi Kleen <ak@muc.de>, Andrew Morton <akpm@digeo.com>,
elenstev@mesatop.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: 2.5.68-mm4
Date: Tue, 6 May 2003 15:15:55 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.55.0305061511020.3237@r2-pc.dcs.qmul.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.55.0305030800140.1304@jester.mews>
On May 3 Matt Bernstein wrote:
>>> > Bizarrely I have a nasty crash on modprobing e100 *without* kexec (having
>>> > previously modprobed unix, af_packet and mii) and then trying to modprobe
>>> > serio (which then deadlocks the machine).
>>> >
>>> > http://www.dcs.qmul.ac.uk/~mb/oops/
>>>
>>> Andi, it died in the middle of modprobe->apply_alternatives()
>>
>>The important part of the oops - the first lines are missing in the .png.
>>
>>What is the failing address? And can you send me your e100.o ?
>
>I'm sorry I can't get to the machine now till Tuesday. I'll try to get it
>into a smaller font, or failing that a serial console if you like.
I've now built 2.5.69-mm1 and it gives a very similar oops--and it wasn't
related to e100; it would oops on the third modprobe!
So, I built a load of my modules into the monolith: leaving just uhci and
e100, and now the first modprobe oopses and the second deadlocks..
However, the trace is a little deeper this time:
http://www.dcs.qmul.ac.uk/~mb/oops/oops2small.jpeg
Is this helpful?
Matt
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-05-06 14:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-02 9:01 2.5.68-mm4 Andrew Morton
2003-05-02 13:18 ` 2.5.68-mm4 William Lee Irwin III
2003-05-02 16:47 ` 2.5.68-mm4 Dave Hansen
2003-05-02 14:45 ` 2.5.68-mm4 Steven Cole
2003-05-02 15:00 ` 2.5.68-mm4 Steven Cole
2003-05-02 15:35 ` 2.5.68-mm4 Anton Blanchard
2003-05-02 21:12 ` 2.5.68-mm4 Andrew Morton
2003-05-03 14:12 ` 2.5.68-mm4 Eric W. Biederman
2003-05-02 16:54 ` 2.5.68-mm4 Martin J. Bligh
2003-05-02 20:04 ` 2.5.68-mm4 Steven Cole
2003-05-02 20:34 ` 2.5.68-mm4 Andrew Morton
2003-05-02 20:49 ` 2.5.68-mm4 Steven Cole
2003-05-02 21:01 ` 2.5.68-mm4 Steven Cole
2003-05-02 21:05 ` 2.5.68-mm4 Andrew Morton
2003-05-02 21:20 ` 2.5.68-mm4 Steven Cole
2003-05-02 21:49 ` 2.5.68-mm4 Andy Pfiffer
2003-05-02 22:00 ` 2.5.68-mm4 Steven Cole
2003-05-02 23:22 ` 2.5.68-mm4 Matt Bernstein
2003-05-02 23:41 ` 2.5.68-mm4 Andrew Morton
2003-05-03 2:53 ` 2.5.68-mm4 Andi Kleen
2003-05-03 7:08 ` 2.5.68-mm4 Matt Bernstein
2003-05-06 14:15 ` Matt Bernstein [this message]
2003-05-06 14:35 ` 2.5.68-mm4 Andi Kleen
2003-05-06 15:50 ` 2.5.68-mm4 Matt Bernstein
2003-05-07 10:27 ` 2.5.68-mm4 Matt Bernstein
2003-05-07 12:35 ` 2.5.68-mm4 Andi Kleen
2003-05-07 15:45 ` 2.5.68-mm4 Matt Bernstein
2003-05-03 3:14 ` 2.5.68-mm4 Andi Kleen
2003-05-05 3:46 ` 2.5.68-mm4 && kexec Eric W. Biederman
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=Pine.LNX.4.55.0305061511020.3237@r2-pc.dcs.qmul.ac.uk \
--to=mb--lkml@dcs.qmul.ac.uk \
--cc=ak@muc.de \
--cc=akpm@digeo.com \
--cc=elenstev@mesatop.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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