netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ayaz Abdulla <aabdulla@nvidia.com>,
	e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
	Adrian Bunk <bunk@stusta.de>, Greg KH <greg@kroah.com>,
	Dave Jones <davej@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jeff Garzik <jgarzik@pobox.com>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [1/3] 2.6.21-rc6: known regressions
Date: Fri, 20 Apr 2007 15:46:27 +0200	[thread overview]
Message-ID: <20070420134627.GA18195@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.64.0704131821020.28042@woody.linux-foundation.org>


* Linus Torvalds <torvalds@linux-foundation.org> wrote:

> [...] I think the hangs that Ingo sees with forcedeth were preceded by 
> mysterious and "impossible" NULL pointer oopses. Ingo?

update: the 'forcedeth NULL pointer oops' problem got resolved by one of 
these commits:

 commit 3ba4d093fe8a26f5f2da94411bf8732fa6e9da86
 Author: Ayaz Abdulla <aabdulla@nvidia.com>
 Date:   Fri Mar 23 05:50:02 2007 -0500

     forcedeth: fix tx timeout

 commit fcc5f2665c81e087fb95143325ed769a41128d50
 Author: Ayaz Abdulla <aabdulla@nvidia.com>
 Date:   Fri Mar 23 05:49:37 2007 -0500

     forcedeth: fix nic poll

it never reoccured since this went upstream - so i'd close the NULL 
dereference bug.

furthermore, i havent seen the 'forcedeth interface hangs' problem 
trigger with recent kernels (havent seen it trigger for the past 2 
weeks), but no forcedeth specific change went into the kernel since i 
last reproduced a hang so either it got fixed by something else, or the 
hang is very rare. We could lower its priority for v2.6.21. If it ever 
happens again i'll send another ethtool dump to Ayaz.

	Ingo

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

      parent reply	other threads:[~2007-04-20 13:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.64.0704051944230.6730@woody.linux-foundation.org>
2007-04-06 21:40 ` tg3: unable to handle null pointer dereference [Re: Linux 2.6.21-rc6] Nishanth Aravamudan
2007-04-06 22:57   ` Michael Chan
2007-04-07  0:36     ` tg3: unable to handle null pointer dereference David Miller
2007-04-07  1:53       ` Nishanth Aravamudan
2007-04-14  0:36 ` [1/3] 2.6.21-rc6: known regressions Adrian Bunk
2007-04-14  1:34   ` Linus Torvalds
2007-04-14  1:49     ` Brandeburg, Jesse
2007-04-14  4:25     ` David Miller
2007-04-14  5:07     ` Ian McDonald
2007-04-14  5:29     ` David Miller
2007-04-14  6:21     ` Ingo Molnar
2007-04-14  7:25       ` Greg KH
2007-04-20 13:39       ` Ingo Molnar
2007-04-20 13:46     ` Ingo Molnar [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=20070420134627.GA18195@elte.hu \
    --to=mingo@elte.hu \
    --cc=aabdulla@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@stusta.de \
    --cc=davej@redhat.com \
    --cc=davem@davemloft.net \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=greg@kroah.com \
    --cc=jgarzik@pobox.com \
    --cc=netdev@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 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).