netdev - Re: [BUG or cosmic ray] WARNING: at net/sched/sch_generic.c:222 dev

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <E6FF208A16840D4EBAA31D261B15A506011CAF8B@ausx3mpc121.aus.amer.dell.com>
Date:	Tue, 24 Jun 2008 23:34:39 -0500
From:	<Mario_Limonciello@...l.com>
To:	<netdev@...r.kernel.org>
Subject: Re: [BUG or cosmic ray] WARNING: at net/sched/sch_generic.c:222 dev_watchdog+0xe8/0x100()

Unfortunately, I am running into the same problem on a RTL8102EL.  I
added it to the table locally to ensure it was identifying with the
correct mac_version, (mac_version=0x11).

> If lspci can not read the device registers correctly, chances are high
> that the device driver can not either.
Correct, in my case.

> 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.

Exact same behavior on this end.  It's reproducible in a variety of
ways:
* Randomly on startup, in an invalid state
* After a random resume from S3
* rmmod/modprobe r8169 over and over.  It's important to note that it
breaks on the "modprobe" not on the rmmod.  This can be verified by
checking
Lspci -vvv -nn -d 10ec:8136 in between rmmod and modprobe

If it happens after the  S3, rmmod will cause a kernel panic.

I'm not on 2.6.26-rc6 at this point, but 2.6.24 (the Ubuntu -19 variant)
with the r8169 module compiled out of tree.  If there are indeed other
fixes to the PCI subsystem that are relevant, I'll pull a 2.6.26 kernel,
but in the end need to be able to narrow this down to a small series of
fixes.

> 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.
These all give the same behavior.  I'm a bit doubtful that it is not
r8169 specific as I've not been able to ever produce this problem with
other network drivers.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html