From: Krzysztof Halasa <khc@pm.waw.pl>
To: <netdev@vger.kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Kernel panic 2.6.25.10 IXP4xx
Date: Fri, 11 Jul 2008 20:14:51 +0200 [thread overview]
Message-ID: <m3skug1e5g.fsf@maximus.localdomain> (raw)
In-Reply-To: <m3y7481wbo.fsf@maximus.localdomain> (Krzysztof Halasa's message of "Fri\, 11 Jul 2008 13\:42\:19 +0200")
Krzysztof Halasa <khc@pm.waw.pl> writes:
> I'm told this is reproducible. The kernel in question is a (patched a
> bit) 2.6.25.10. ARM, Intel IXP425 CPU, big-endian. The exact
> patch set is available.
It seems the extra patches aren't really used, though. The
configuration is basically:
ifconfig eth0 192.168.0.1/24 (ixp4xx_eth driver, without the last fix
correcting the device eth_poll() (NAPI) return value applied)
modprobe speedtch (USB ADSL, PPP over ATM)
iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -d 0/0 -o ppp0 -j
MASQUERADE (seems unrelated)
/sbin/pppd call speedtch (plugin pppoatm.so)
I'm going to try to recreate it on my machine.
--
Krzysztof Halasa
prev parent reply other threads:[~2008-07-11 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 11:42 Kernel panic 2.6.25.10 IXP4xx Krzysztof Halasa
2008-07-11 18:14 ` Krzysztof Halasa [this message]
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=m3skug1e5g.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--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