linux-kernel - 2.6.31-rc2: Possible regression in rt61pci driver

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]

Date:	Mon, 13 Jul 2009 09:27:43 +0100
From:	Chris Clayton <chris2553@...glemail.com>
To:	linux-wireless@...r.kernel.org
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: 2.6.31-rc2: Possible regression in rt61pci driver

Hi,

Please cc me on any reply because I'm not subscribed.

I've been testing 2.6.31 development kernels on my laptop and find
that I can induce a complete lock-up more or less at will. To do so,
all I have to do is generate some network traffic on my wireless LAN
(I've been using wget to transfer a file from another box on my LAN)
and then wait. If I run netstat repeatedly while waiting, I see a TCP
connection to port 21 on another box on my LAN in a TIME_WAIT state.
It seems that when that connection disappears, the laptop locks up
hard and I can only recover by powering off and on again. I think the
problem is related to the rt61pci driver because I haven't been able
to induce the lock-up when using a wireless card that's supported by
the ath5k driver. I started bisecting, but a couple of times I arrived
at points where although the kernel builds OK, I have no network
connectivity. I guessed at good, but the bisection process finished at
a change that can't be the culprit (because it's for a different
architecture).

I attach the best diagnostics I can think of at this point in time
(but am more than happy to provide any others that are requested). It
includes the output from dmesg from a boot that locked up and the
syslog journal from that boot; a description of the wireless card from
lspci -v and the output from netstat that shows the connection I think
is involved. As I say, feel free to ask for any other diagnostics that
will help track the problem down.

I have confirmed that the problem is still present in a kernel built
after a 'git pull' this morning, although it was somewhere around the
time that -rc2 was released that I first came across it. I cannot
induce the problem with 2.6.30.1.

Thanks

Chris

-- 
No, Sir; there is nothing which has yet been contrived by man, by
which so much happiness is produced as by a good tavern or inn -
Doctor Samuel Johnson

View attachment "dmesg.txt" of type "text/plain" (30345 bytes)

Download attachment "syslog" of type "application/octet-stream" (87725 bytes)

View attachment "lspci.txt" of type "text/plain" (345 bytes)

View attachment "netstat.txt" of type "text/plain" (1543 bytes)