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: <13bb8ce11001102040j37e061fn976ec74595f30232@mail.gmail.com>
Date:	Sun, 10 Jan 2010 22:40:46 -0600
From:	Daniel Goller <morfic@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	alan@...rguk.ukuu.org.uk
Subject: Re: staging/et131x Driver Transmits but does not Receive Packets

>
> Going to get 2.6.29 and 2.6.30 now.

This is going to be a lot of fun...

2.6.29.6 did nothing, but TX Packets count ever so slightly
increasing, all attempts ended in a "Destination host unreachable"
2.6.30.10 actually allowed me to ping another host in the network,
(the restarted by kde) xchat meanwhile reconnected to the znc instance
on the host i was pinging.
I got replies to pings 4, 13 and all else was lost by the time i
pinged the host.

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)

2.6.29.6 and 2.6.30.10 would allow me to modprobe et131x with
additional debugging info, if you let me know what debug level you
need and what i should be trying on the interface to produce useful
info.

[ 1386.009039] et131x.ko:WARNING:et131x_ioctl Unhandled IOCTL Code: 0x8b27
[ 1386.009859] et131x.ko:WARNING:et131x_ioctl Unhandled IOCTL Code: 0x8b14
[ 1386.010994] et131x.ko:WARNING:et131x_ioctl Unhandled IOCTL Code: 0x8b1a
[ 1386.011943] et131x.ko:WARNING:et131x_ioctl Unhandled IOCTL Code: 0x8b26

I see this repeating a few times now in 2.6.30.6

The one time i did get a reply on my pings and xchat, was just after
trying to switch network cables around. But i have not been able to
reproduce anything in subsequent attempts of replugging/restarting the
interface.

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

Thanks,

Daniel
--
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/