public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: Manuel Metz <mmetz@astro.uni-bonn.de>
Cc: linux-kernel@vger.kernel.org, nappers@gmail.com,
	Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Subject: Re: PROBLEM: oops in 2.6.21.1 after bringing up the network
Date: Mon, 30 Apr 2007 17:23:11 -0400	[thread overview]
Message-ID: <46365E3F.9070109@redhat.com> (raw)
In-Reply-To: <4635D7B1.2040001@astro.uni-bonn.de>

Manuel Metz wrote:
> Brett Ryland wrote:
>> Hi,
>> I am consistently getting a kernel oops from a vanilla 2.6.21.1 kernel. It 
>> also occurs in vanilla 2.6.21, but not in 2.6.20.8. The relevant section of 
>> the kernel is networking, in particular the sis900 module (I think).
>> The attached file contains the oops and the information asked for on the site 
>> http://www.kernel.org/pub/linux/docs/lkml/reporting-bugs.html for reporting 
>> kernel oopses. The oops fully crashes my computer and leaves the capslock and 
>> numlock leds flashing, so the oops is transcribed by hand from a photo 
>> (hopefully I haven't made a mistake, I do still have the photo if it's 
>> needed).
>>
>> I'm not subscribed to the mailing list so please CC any questions/solutions to 
>> me.
>>
>> Regards,
>> Nappers.
> 
> Hi, I have the same problem here on an ASUS laptop with sis network
> card. The system worked fine with kernel 2.6.21-rc7-mm2 and 2.6.20.7,
> but crashes with 2.6.21.1.
> 

Fixed by this:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=dc5a144991ba803bc8afded105c9db1dea0e57ab

Look here before reporting bugs to linux-kernel:
http://kernelnewbies.org/known_regressions

  reply	other threads:[~2007-04-30 21:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8fgo8-1wP-9@gated-at.bofh.it>
2007-04-30 11:49 ` PROBLEM: oops in 2.6.21.1 after bringing up the network Manuel Metz
2007-04-30 21:23   ` Chuck Ebbert [this message]
2007-05-01  9:44     ` Manuel Metz
2007-04-29 12:00 Brett Ryland
2007-04-29 12:15 ` Michal Piotrowski
2007-04-29 12:33   ` Brett Ryland

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=46365E3F.9070109@redhat.com \
    --to=cebbert@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=mmetz@astro.uni-bonn.de \
    --cc=nappers@gmail.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