linux-kernel - Re: staging/et131x Driver Transmits but does not Receive Packets

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100111102620.732b574f@lxorguk.ukuu.org.uk>
Date:	Mon, 11 Jan 2010 10:26:20 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Daniel Goller <morfic@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: staging/et131x Driver Transmits but does not Receive Packets

> I then blacklisted iwlagn and r8169 and rebooted, retrying 2.6.29.6
> and 2.6.30.10 but was no longer able to ping anything. So when it
> works and when not is still intermittent. (And the only interfaces up
> were eth1 and lo, not eth0 (r8169) or wlan0 (iwlagn) in case someone
> wonders)

That looks like an interrupt problem. With iwlagn and r8169 blacklisted
see what interrupt number the et131x gets (cat /proc/interrupts) and see
if it goes up whenever you send/receive stuff.

If not then I don't think its an et131x problem but an IRQ routing
problem (eg a bad BIOS table, or a kernel bug elsewhere)

> I do not think i am yet at a point where git bisect would be useful.

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