From: Meelis Roos <mroos@linux.ee>
To: netdev@vger.kernel.org
Subject: Re: 3.3-rc3+ Crash in __neigh_for_each_release
Date: Mon, 20 Feb 2012 14:04:14 +0200 (EET) [thread overview]
Message-ID: <alpine.SOC.1.00.1202201403000.8004@math.ut.ee> (raw)
In-Reply-To: <alpine.SOC.1.00.1202201359190.8004@math.ut.ee>
> Just tried 3.3-rc3+git and 3.3-rc4 on a generic i815+P3+e100 PC. It
> crashes consistently during the end of bootup, getning oops in
> __neigh_for_each_release during timer softirq. 3.2 works fine.
Hit send too fast - the first post-3.2 kernel I tried was
3.3.0-rc3-00278-g4903062 and that failed, and 3.3-rc4 too.
--
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2012-02-20 12:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 12:02 3.3-rc3+ Crash in __neigh_for_each_release Meelis Roos
2012-02-20 12:04 ` Meelis Roos [this message]
2012-02-21 19:03 ` Eric Dumazet
2012-02-21 19:07 ` David Miller
2012-02-21 19:15 ` Eric Dumazet
2012-02-21 20:46 ` Eric Dumazet
2012-02-21 22:46 ` David Miller
2012-02-22 7:19 ` mroos
2012-02-22 7:21 ` Eric Dumazet
2012-02-22 7:24 ` David Miller
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=alpine.SOC.1.00.1202201403000.8004@math.ut.ee \
--to=mroos@linux.ee \
--cc=netdev@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).