From: Andrew Morton <akpm@linux-foundation.org>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: davem@davemloft.net, shemminger@linux-foundation.org,
netdev@vger.kernel.org, rjw@sisk.pl,
"bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@bugzilla.kernel.org>
Subject: [Bug 10238] Re: [PATCH] Re: netconsole still hangs
Date: Tue, 18 Mar 2008 01:50:06 -0700 [thread overview]
Message-ID: <20080318015006.3f0efb8e.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080318080439.GA3965@ff.dom.local>
On Tue, 18 Mar 2008 08:04:39 +0000 Jarek Poplawski <jarkao2@gmail.com> wrote:
> On Mon, Mar 17, 2008 at 04:12:22PM -0700, Andrew Morton wrote:
> ...
> > I retested. This patch doesn't appear to make anything worse, but the hang
> > is still there.
>
> Yes, but since this doesn't look like something very common, and we
> don't even know if this OOPS and the hangs are the same bug, there is
> needed more information e.g.:
>
> - is it reproducible with e1000E only and no wlan?
Yes. Both the machines I can reproduce this on have both E1000=y and
E1000E=y. From the dmesg (below), one uses e1000 and the other uses
e1000e. Both crash.
http://userweb.kernel.org/~akpm/config-akpm2.txt
http://userweb.kernel.org/~akpm/dmesg-akpm2.txt
http://userweb.kernel.org/~akpm/config-t61p.txt
http://userweb.kernel.org/~akpm/dmesg-t61p.txt
I used to be able to reproduce the problems with a 2-way i386 e100 system,
but that seems to be fixed now, perhaps from David's revert.
I also used to be able to reproduce the problem on a one-way i386 e100
machine but that also seem to have gone away.
> - is there a possibility to check this with some other card
> (even wlan while e1000E is off)?
err, dunno. Perhaps I could try e1000 on the e1000e-using machine and vice
versa, but for that some PCI ID table hacking might be needed.
I cc'ed bugzilla on this thread.
> - could you add .config to the bugzilla report:
> http://bugzilla.kernel.org/show_bug.cgi?id=10238
See above.
> - is it acceptable to send you some patches for debugging this?
As a last resort. But it'd surely be better if a net developer could
reproduce this and do some work on it. It's bog-trivial to reproduce here
and afaik nobody has even tried. Perhaps you have...
service syslog stop
while true
do
echo t > /proc/sysrq-trigger
done
and that's it.
next prev parent reply other threads:[~2008-03-18 8:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 23:14 netconsole still hangs Andrew Morton
2008-03-12 23:16 ` Andrew Morton
2008-03-12 23:30 ` Andrew Morton
2008-03-12 23:57 ` Andrew Morton
2008-03-13 6:10 ` David Miller
2008-03-13 6:52 ` Andrew Morton
2008-03-13 7:12 ` David Miller
2008-03-13 7:25 ` Andrew Morton
2008-03-13 7:48 ` Jike Song
2008-03-14 23:47 ` [PATCH] " Jarek Poplawski
2008-03-17 23:12 ` Andrew Morton
2008-03-18 8:04 ` Jarek Poplawski
2008-03-18 8:50 ` Andrew Morton [this message]
2008-03-18 21:05 ` [Bug 10238] " Jarek Poplawski
2008-03-18 21:47 ` Andrew Morton
2008-03-18 22:47 ` Jarek Poplawski
2008-03-19 19:17 ` Jarek Poplawski
2008-03-19 21:20 ` Andrew Morton
2008-03-19 21:31 ` David Miller
2008-03-19 21:54 ` Jarek Poplawski
2008-03-20 23:08 ` David Miller
2008-03-13 7:59 ` Andrew Morton
2008-03-13 15:09 ` Stephen Hemminger
2008-03-13 15:52 ` Andrew Morton
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=20080318015006.3f0efb8e.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=davem@davemloft.net \
--cc=jarkao2@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=shemminger@linux-foundation.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).