All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Jeff Garzik <jeff@garzik.org>, Doug Chapman <doug.chapman@hp.com>,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	"e1000-devel@lists.sourceforge.net >> e1000-list" 
	<e1000-devel@lists.sourceforge.net>
Subject: Re: 2.6.21-gitX: known regressions
Date: Thu, 10 May 2007 18:24:35 -0700	[thread overview]
Message-ID: <4643C5D3.3060303@intel.com> (raw)
In-Reply-To: <20070510181044.d0f24e51.akpm@linux-foundation.org>

Andrew Morton wrote:
> On Thu, 10 May 2007 14:04:13 +0200
> Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:
> 
>> Hi all,
>>
>> Here is a list of some known regressions in 2.6.21-gitX.
>>
>> Feel free to add new regressions/remove fixed etc.
>> http://kernelnewbies.org/known_regressions
>>
>>
>> Networking:
>>
>> Subject    : panic with e1000 driver on HP Integrity servers
>> References : http://bugzilla.kernel.org/show_bug.cgi?id=8455
>> Submitter  : Doug Chapman <doug.chapman@hp.com>
>> Caused-By  : Auke Kok <auke-jan.h.kok@intel.com>
>>              commit e0aac5a289b1dacbc94bd9ae8c449bcdf9ab508c
>> Status     : Unknown

We're trying to reproduce this in our labs here but that piece of code has been 
extensively tested on various platforms and architectures, so I'm a bit 
surprised about it. I've asked for more info on the bugzilla as well.

So, this is being worked on actively.

Cheers,

Auke

  reply	other threads:[~2007-05-11  1:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10 12:04 2.6.21-gitX: known regressions Michal Piotrowski
2007-05-11  1:10 ` Andrew Morton
2007-05-11  1:10   ` Andrew Morton
2007-05-11  1:24   ` Kok, Auke [this message]
2007-05-11  1:10 ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2007-05-10 12:04 Michal Piotrowski

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=4643C5D3.3060303@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=doug.chapman@hp.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=jeff@garzik.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@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 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.