public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Marcus Hall <mhall@coraccess.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux-arm-2.5.59 problem connecting from win 98
Date: Wed, 27 Aug 2003 09:22:54 +0100	[thread overview]
Message-ID: <20030827092254.A22441@flint.arm.linux.org.uk> (raw)
In-Reply-To: <3F4BD073.6020105@coraccess.com>; from mhall@coraccess.com on Tue, Aug 26, 2003 at 03:26:11PM -0600

On Tue, Aug 26, 2003 at 03:26:11PM -0600, Marcus Hall wrote:
> Things work just fine with http/ftp/telnet from a linux box, but if I
> try to connect from a win 98 system, linux panics (don't really blame
> it..) with the error message 'kernel BUG at net/core/skbuff.c:323',
> which appears to say that an skbuff is being freed while still on a
> list.

Please supply the full backtrace - it may be a driver doing something it
shouldn't.

> I don't believe that there are any changes in the core networking in
> the arm/xscale patches applied to the base 2.5.59 kernel, just some
> tweaking of the smc9194 and cs89x0 modules.  It seems unlikely that this
> problem would exist in the "official" kernel for long, but it also seems
> unlikely to be particular to the arm either...  Is it a known bug
> (hopefully with a patch somewhere)?

The best I can advise is to upgrade to something more recent (eg, a
2.6.0-test kernel.)

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


      reply	other threads:[~2003-08-27  8:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-26 21:26 linux-arm-2.5.59 problem connecting from win 98 Marcus Hall
2003-08-27  8:22 ` Russell King [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=20030827092254.A22441@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhall@coraccess.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