Re: Tulip driver broken on Cobalt RaQ1 in 2.6

[Peter Horton <phorton@bitbox.co.uk>]

Martin Michlmayr wrote:
> * Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp> [2007-08-24 13:36]:
> > What error occurs on Raq1?
> There is no error, but I never get a DHCP response:
>
> Listening on LPF/eth0/00:10:e0:00:27:5c
> Sending on   LPF/eth0/00:10:e0:00:27:5c
> Sending on   Socket/fallback/fallback-net
> DHCPREQUEST on eth0 to 255.255.255.255 port 67
> eth0: Setting full-duplex based on MII#1 link partner capability of 45e1.
> DHCPREQUEST on eth0 to 255.255.255.255 port 67
> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17
> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
> No DHCPOFFERS received.
What does /proc/interrupts show after this ?

Does the networking work in CoLo ?

The "PCI retry count" thing is a red herring. There's no device at 06.0 
so that's why you get the message. The kernel used to explicitly skip 
this device when PCI retries were disabled otherwise it would hang. When 
I enabled the PCI retry counter there was no need to skip it, you just 
get the debug.
P.