calls above register_netdevice so the
> stack starts out how we expect it to be.
>
> Signed-off-by: Auke Kok <[EMAIL PROTECTED]>
> Cc: Herbert Xu <[EMAIL PROTECTED]>
> Cc: Doug Chapman <[EMAIL PROTECTED]>
I tested this on my HP Integrity systems and it looks good.
On Fri, 2007-06-01 at 08:10 +1000, Herbert Xu wrote:
> On Thu, May 31, 2007 at 11:16:09AM -0400, Doug Chapman wrote:
> >
> > # dmesg | grep e1000
> > e1000: :01:02.0: e1000_probe: (PCI-X:66MHz:64-bit) 00:15:60:04:d7:f8
> > e1000: eth0: e1000_probe: Intel(R)
On Thu, 2007-05-31 at 11:08 +1000, Herbert Xu wrote:
> On Wed, May 30, 2007 at 05:22:30PM -0400, Doug Chapman wrote:
> >
> > but once again broken just yesterday by the following commit. I have
> > backed just this commit out and verified I no longer panic.
>
> Hmm,
On Wed, 2007-05-30 at 15:57 -0700, Kok, Auke wrote:
> Doug Chapman wrote:
> > All,
> >
> > I reported this a few weeks ago and it was fixed but it appears the
> > offending code was again re-submitted. This causes a panic on HP
> > Integrity servers and from
All,
I reported this a few weeks ago and it was fixed but it appears the
offending code was again re-submitted. This causes a panic on HP
Integrity servers and from what I hear many other platforms using e1000
as well.
My original report was via kernel.org BZ:
http://bugzilla.kernel.org/show_bug
