All of lore.kernel.org
 help / color / mirror / Atom feed
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: Fri, 17 Oct 2003 22:50:58 +0200	[thread overview]
Message-ID: <3F907252.1538.AC80B30@localhost> (raw)

> > On Thu, 16 Oct 2003, Sebastian Piecha wrote:
> > 
> > >  panics. Copying more than 4 GB to the samba share also lets the 
> > > kernel panic with an OOPS.
> > 
> > Does the above cause a panic for the 2.6-test kernels?
> > Do you have netfilter enabled, and if so, any iptables modules loaded?
> > 
> > 
> I did a mistake. iptables is installed but no rules added. I'll 
> remove iptables and rerun the check.

For being sure I removed iptables but again the oops happened. I also 
tried kernel 2.4.18 without success.

Does anybody have a clue how to go on?

--
Mit freundlichen Gruessen/Best regards,
Sebastian Piecha

EMail: spi@gmxpro.de


             reply	other threads:[~2003-10-17 20:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-17 20:50 Sebastian Piecha [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-29 17:00 oops in skbuff.c Sebastian Piecha
2003-10-26 22:08 Sebastian Piecha
2003-10-17  8:37 Sebastian Piecha
     [not found] <3F8EF7B3.25278.5010BC6@localhost>
2003-10-16 19:15 ` James Morris
2003-10-16 20:01   ` Sebastian Piecha
2003-10-16 20:37     ` James Morris
2003-10-16 21:11       ` Sebastian Piecha
2003-10-17 15:33         ` James Morris
2003-10-17 12:17   ` Sebastian Piecha
2001-08-03 21:40 Stefan Burkei
2001-08-04  9:30 ` Martin Josefsson

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=3F907252.1538.AC80B30@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.