From: Krzysztof Halasa <khc@pm.waw.pl>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org,
Stephen Hemminger <shemminger@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Russell King <rmk+lkml@arm.linux.org.uk>
Subject: Re: [bisected] kernel panic 2.6.22 -> 2.6.26-rc9+
Date: Sun, 13 Jul 2008 12:48:15 +0200 [thread overview]
Message-ID: <m3abgmcb68.fsf@maximus.localdomain> (raw)
In-Reply-To: <20080713013107.23f060f2.akpm@linux-foundation.org> (Andrew Morton's message of "Sun\, 13 Jul 2008 01\:31\:07 -0700")
Andrew Morton <akpm@linux-foundation.org> writes:
> (cc's added)
(cc added) :-)
> I guess you're referring to this:
> http://linux.derkeiler.com/Mailing-Lists/Kernel/2008-07/msg04754.html
Right.
>> PPP over ATM connection (Thomson/Alcatel
>> Speedtouch). It doesn't seem to occur on the same IXP4xx with Ethernet
>> or V.35 WAN, and it doesn't occur on i386 + the same Speedtouch ADSL.
>> The kernel is basically unpatched, the only extra patch applied is the
>> platform support (nothing magic).
>>
>> Generally to trigger the panic one has to request a TCP data stream
>> over that PPPoATM connection.
I see what's wrong now: that's the ARM fls() problem, the call in
fls64() to be precise. It seems it was already discussed: the patch in
http://lkml.org/lkml/2008/5/4/233 makes the problem disappear.
Perhaps it's time to fix it definitely?
--
Krzysztof Halasa
next prev parent reply other threads:[~2008-07-13 10:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-13 0:28 [bisected] kernel panic 2.6.22 -> 2.6.26-rc9+ Krzysztof Halasa
2008-07-13 8:31 ` Andrew Morton
2008-07-13 10:48 ` Krzysztof Halasa [this message]
2008-07-13 18:22 ` Andrew Morton
2008-07-13 21:51 ` Krzysztof Halasa
2008-07-13 21:55 ` Andrew Morton
2008-07-23 4:52 ` Willy Tarreau
2008-07-23 5:00 ` Andrew Morton
2008-07-23 5:06 ` Willy Tarreau
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=m3abgmcb68.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
--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).