Re: [BUG or cosmic ray] WARNING: at net/sched/sch_generic.c:222dev_watchdog+0xe8/0x100()

[Francois Romieu]

c4p7n1@xxxxxxxxxxxxx <c4p7n1@xxxxxxxxxxxxx> :
[...]
> > > [  125.682725] r8169: eth0: link up
> > > ...
> > > [ 1337.654531] NETDEV WATCHDOG: eth0: transmit timed out
> > > [ 1338.333962] r8169: eth0: link up
> ...
> 
> Definitely a bug. I've got the same lock-up a second time on a rc5.
> 
> It may be related to a patch:
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=21e197f231343201368338603cb0909a13961bac

Short answer: no.

With this patch the device driver can at least try to initialize. Without it,
you are bust.

> Before that patch on this chip [10ec:8136] the r8169 driver crashed with a null pointer exception.
> Strangely, on a .22  kernel came out (at that time always) the same lspci error:
> 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E PCI Express Fast Ethernet controller (rev ff) (prog-if ff)
>  !!! Unknown header type 7f
> 
> ... just my observations ;-) 

They are welcome.

If lspci can not read the device registers correctly, chances are high
that the device driver can not either.

If you can reproduce the "!!! Unknown header type 7f" error with lspci
on 2.6.26-rc6 we have a problem which goes beyond the sole r8169 device
driver. linux-kernel or linux-pci will probably be more helpful than
netdev then.

Playing with the pci=nommconf , noapic or nomsi options at boot time
can make a difference with relation to lspci behavior. It is possible
(or almost certain given Murphy's grip) that the r8169 driver will
still not behave correctly. I have not received a lot of success/failure
reports for this chipset ([10ec:8136]) so things can surely improve.

-- 
Ueimor
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/