All of lore.kernel.org
 help / color / mirror / Atom feed
* tulip (was RE: Kernel 2.4.3 fails to compile)
  2001-03-30 23:14 Kernel 2.4.3 fails to compile Manuel A. McLure
@ 2001-03-31  0:38 ` Jeff Garzik
  0 siblings, 0 replies; 4+ messages in thread
From: Jeff Garzik @ 2001-03-31  0:38 UTC (permalink / raw)
  To: Manuel A. McLure; +Cc: 'linux-kernel@vger.kernel.org'

On Fri, 30 Mar 2001, Manuel A. McLure wrote:
> It looks like the tulip driver isn't as up-to-date as the one from
> 2.4.2-ac20 - when is 2.4.3-ac1 due? :-) I got NETDEV WATCHDOG errors shortly
> after rebooting with 2.4.3, although these were of the "slow/packet lossy"
> type I got with 2.4.2-ac20 instead of the "network completely unusable" type
> I got with 2.4.2-ac11 and earlier.

I'm betting that the latest ac (ac28?) is broken for you, too.

I had to revert the changes in 'ac' tulip -- they fixed Comet and 21041
cards, but broke some others.  sigh.

sigh.  More testing and debugging for Jeffro...  Comet (your chip, I
am guessing?) should be fixed ASAP, it's pretty easy.  21041 is not as
easy, but should be fixed quickly as well.

	Jeff




^ permalink raw reply	[flat|nested] 4+ messages in thread

* RE: tulip (was RE: Kernel 2.4.3 fails to compile)
@ 2001-03-31  0:42 Manuel A. McLure
  2001-04-05 16:57 ` Jeff Garzik
  0 siblings, 1 reply; 4+ messages in thread
From: Manuel A. McLure @ 2001-03-31  0:42 UTC (permalink / raw)
  To: 'Jeff Garzik'; +Cc: 'linux-kernel@vger.kernel.org'

Jeff Garzik wrote:
> On Fri, 30 Mar 2001, Manuel A. McLure wrote:
> > It looks like the tulip driver isn't as up-to-date as the one from
> > 2.4.2-ac20 - when is 2.4.3-ac1 due? :-) I got NETDEV 
> WATCHDOG errors shortly
> > after rebooting with 2.4.3, although these were of the 
> "slow/packet lossy"
> > type I got with 2.4.2-ac20 instead of the "network 
> completely unusable" type
> > I got with 2.4.2-ac11 and earlier.
> 
> I'm betting that the latest ac (ac28?) is broken for you, too.
> 
> I had to revert the changes in 'ac' tulip -- they fixed Comet 
> and 21041
> cards, but broke some others.  sigh.
> 
> sigh.  More testing and debugging for Jeffro...  Comet (your chip, I
> am guessing?) should be fixed ASAP, it's pretty easy.  21041 is not as
> easy, but should be fixed quickly as well.

Yes, mine is a Comet - here's the exact detection message:

Mar 30 13:09:06 ulthar kernel: Linux Tulip driver version 0.9.14 (February
20, 2
001)
Mar 30 13:09:06 ulthar kernel: PCI: Found IRQ 5 for device 00:0c.0
Mar 30 13:09:06 ulthar kernel: eth0: ADMtek Comet rev 17 at 0xb000,
00:20:78:0D:
D2:E1, IRQ 5.

I must say that I really appreciate the effort that all of the kernel
developers put in...

Thanks,
--
Manuel A. McLure - Unify Corp. Technical Support <mmt@unify.com>
Space Ghost: "Hey, what happened to the-?" Moltar: "It's out." SG: "What
about-?" M: "It's fixed." SG: "Eh, good. Good."

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: tulip (was RE: Kernel 2.4.3 fails to compile)
  2001-03-31  0:42 tulip (was RE: Kernel 2.4.3 fails to compile) Manuel A. McLure
@ 2001-04-05 16:57 ` Jeff Garzik
  0 siblings, 0 replies; 4+ messages in thread
From: Jeff Garzik @ 2001-04-05 16:57 UTC (permalink / raw)
  To: Manuel A. McLure; +Cc: 'linux-kernel@vger.kernel.org'

"Manuel A. McLure" wrote:
> 
> Jeff Garzik wrote:
> > On Fri, 30 Mar 2001, Manuel A. McLure wrote:
> > > It looks like the tulip driver isn't as up-to-date as the one from
> > > 2.4.2-ac20 - when is 2.4.3-ac1 due? :-) I got NETDEV
> > WATCHDOG errors shortly
> > > after rebooting with 2.4.3, although these were of the
> > "slow/packet lossy"
> > > type I got with 2.4.2-ac20 instead of the "network
> > completely unusable" type
> > > I got with 2.4.2-ac11 and earlier.
> >
> > I'm betting that the latest ac (ac28?) is broken for you, too.
> >
> > I had to revert the changes in 'ac' tulip -- they fixed Comet
> > and 21041
> > cards, but broke some others.  sigh.
> >
> > sigh.  More testing and debugging for Jeffro...  Comet (your chip, I
> > am guessing?) should be fixed ASAP, it's pretty easy.  21041 is not as
> > easy, but should be fixed quickly as well.
> 
> Yes, mine is a Comet - here's the exact detection message:
> 
> Mar 30 13:09:06 ulthar kernel: Linux Tulip driver version 0.9.14 (February
> 20, 2
> 001)
> Mar 30 13:09:06 ulthar kernel: PCI: Found IRQ 5 for device 00:0c.0
> Mar 30 13:09:06 ulthar kernel: eth0: ADMtek Comet rev 17 at 0xb000,
> 00:20:78:0D:
> D2:E1, IRQ 5.

Ok, this should be fixed in the latest patches sent to Alan and Linus.

-- 
Jeff Garzik       | Sam: "Mind if I drive?"
Building 1024     | Max: "Not if you don't mind me clawing at the dash
MandrakeSoft      |       and shrieking like a cheerleader."

^ permalink raw reply	[flat|nested] 4+ messages in thread

* RE: tulip (was RE: Kernel 2.4.3 fails to compile)
@ 2001-04-09 16:04 Manuel A. McLure
  0 siblings, 0 replies; 4+ messages in thread
From: Manuel A. McLure @ 2001-04-09 16:04 UTC (permalink / raw)
  To: 'Jeff Garzik'; +Cc: 'linux-kernel@vger.kernel.org'

Jeff Garzik said:
[snip conversation about NETDEV WATCHDOG errors on ADMTek Comet tulip clone
card]
> 
> Ok, this should be fixed in the latest patches sent to Alan and Linus.

Testing with 2.4.3-ac3 and so far, so good. Thanks!

--
Manuel A. McLure - Unify Corp. Technical Support <mmt@unify.com>
Space Ghost: "Hey, what happened to the-?" Moltar: "It's out." SG: "What
about-?" M: "It's fixed." SG: "Eh, good. Good."

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2001-04-09 16:06 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-03-31  0:42 tulip (was RE: Kernel 2.4.3 fails to compile) Manuel A. McLure
2001-04-05 16:57 ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2001-04-09 16:04 Manuel A. McLure
2001-03-30 23:14 Kernel 2.4.3 fails to compile Manuel A. McLure
2001-03-31  0:38 ` tulip (was RE: Kernel 2.4.3 fails to compile) Jeff Garzik

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.