All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Dave Jones <davej@redhat.com>
Cc: - <kd6lvw@yahoo.com>, Neil Horman <nhorman@tuxdriver.com>,
	Jeff Garzik <jeff@garzik.org>,
	netdev@vger.kernel.org, Daniele Venzano <venza@brownhat.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	stable@kernel.org
Subject: Re: [stable] PROBLEM: SIS900 Driver change in Linux Kernel 2.6.21 causes kernel panic.
Date: Wed, 16 May 2007 16:12:32 -0700	[thread overview]
Message-ID: <20070516231232.GA9047@kroah.com> (raw)
In-Reply-To: <20070516221704.GC16810@redhat.com>

On Wed, May 16, 2007 at 06:17:04PM -0400, Dave Jones wrote:
> On Wed, May 16, 2007 at 02:33:18PM -0700, - wrote:
>  > Kernel version 2.6.20.4 works.  What I'm experiencing is a kernel panic as
>  > soon as the first received packet comes in via the sis900 ethernet
>  > interface.  The machine is locked up and part of the kernel panic message
>  > is lost as it has scrolled off the screen and the virtual terminal has
>  > crashed as well (the kernel appears to have done a permanent halt - the
>  > keyboard LEDs are flashing).  The only way I could get the machine to boot
>  > without this problem was to unplug the ethernet cable - but it would
>  > appear as soon as the the first packet was received after plugging the
>  > cable back in.  That's not good since the machine in question is a server
>  > in a co-location facility (I can't print the screen either).  The kernel
>  > panic was repeatable without fail.  As this usually happens before "init"
>  > is called, the only "program" running is the kernel itself.  I don't have
>  > any syslog/dmesg message recorded to disk for the event.  I've rolled back
>  > to version 2.6.20.4 in the meantime.
> 
> You need this..
> 
> http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Ftorvalds%2Flinux-2.6.git;a=commitdiff_plain;h=dc5a144991ba803bc8afded105c9db1dea0e57ab
> 
> Which is queued for -stable afaik, but no sign of 2.6.21.2 yet. Greg/Chris?

I have a large queue backing up, will try to flush it out by tomorrow
and get a review cycle started.

thanks,

greg "i'm starting to hate travelling" k-h

  reply	other threads:[~2007-05-16 23:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-16 21:33 PROBLEM: SIS900 Driver change in Linux Kernel 2.6.21 causes kernel panic -
2007-05-16 22:17 ` Dave Jones
2007-05-16 23:12   ` Greg KH [this message]
2007-05-17  1:42   ` [stable] " Chris Wright

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=20070516231232.GA9047@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=davej@redhat.com \
    --cc=jeff@garzik.org \
    --cc=kd6lvw@yahoo.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=stable@kernel.org \
    --cc=venza@brownhat.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 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.