From: "Sebastian Piecha" <spi@gmxpro.de>
To: James Morris <jmorris@redhat.com>,
LK-net <linux-net@vger.kernel.org>, <netdev@oss.sgi.com>
Subject: Re: oops in skbuff.c
Date: Thu, 16 Oct 2003 23:11:54 +0200 [thread overview]
Message-ID: <3F8F25BA.16275.5B4D703@localhost> (raw)
In-Reply-To: <Xine.LNX.4.44.0310161635590.6371-100000@thoron.boston.redhat.com>
On 16 Oct 2003 at 16:37, James Morris wrote:
> On Thu, 16 Oct 2003, Sebastian Piecha wrote:
>
> > On 16 Oct 2003 at 15:15, James Morris wrote:
> > > On Thu, 16 Oct 2003, Sebastian Piecha wrote:
> > >
> > > Does the above cause a panic for the 2.6-test kernels?
> > > Do you have netfilter enabled, and if so, any iptables modules loaded?
> > >
> > No. Only in 2.4-kernels. No netfilter. No iptables. Just samba
> > sharing some reiserfs directories on a Promise attached ide harddisk.
>
> Are you able to test with a different NIC to the onboard 3C905B?
>
>
Unfortunately I only have 3com NICs. Do you think it's the adapter?
But why it's working in kernel 2.6? There are different changes in
skbuff.c between kernel 2.4.22-ac4 and 2.6.0-test7. Is there any
slight chance to port it back to 2.4.x?
Mit freundlichen Gruessen/Best regards,
Sebastian Piecha
EMail: spi@gmxpro.de
next prev parent reply other threads:[~2003-10-16 21:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3F8EF7B3.25278.5010BC6@localhost>
2003-10-16 19:15 ` oops in skbuff.c James Morris
2003-10-16 20:01 ` Sebastian Piecha
2003-10-16 20:37 ` James Morris
2003-10-16 21:11 ` Sebastian Piecha [this message]
2003-10-17 15:33 ` James Morris
2003-10-17 12:17 ` Sebastian Piecha
2003-10-17 8:37 Sebastian Piecha
-- strict thread matches above, loose matches on Subject: below --
2003-10-17 20:50 Sebastian Piecha
2003-10-26 22:08 Sebastian Piecha
2003-10-29 17:00 Sebastian Piecha
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=3F8F25BA.16275.5B4D703@localhost \
--to=spi@gmxpro.de \
--cc=jmorris@redhat.com \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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).