linux-kernel - Re: rtl8180 freeze some i386 systems

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

Date:	Wed, 24 Nov 2010 10:25:07 -0500
From:	"John W. Linville" <linville@...driver.com>
To:	Frantisek Hanzlik <franta@...zlici.cz>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Andrea Merello <andreamrl@...cali.it>,
	Michael Wu <flamingice@...rmilk.net>
Subject: Re: rtl8180 freeze some i386 systems

On Tue, Nov 23, 2010 at 12:27:24PM +0100, Frantisek Hanzlik wrote:
> On two PCs with Fedora 14/i386 these systems freezes just after command
> "ip link set wlan0 up" was entered.
> "freezes" meant system is totally unuseable, ping to LAN interface
> hasn't reply, kbd/mouse not work, only way is HW reset/power off.
> 
> This hang occurs always independently on system runlevel: when switch to
> runlevel 1, when only kernel threads + udev + root bash are active,
> system still hangs.
> Systems hangs on all tested kernels 2.6.34, 2.6.35.9 and 2.6.36.
> Systems hangs with implicit cmdline and too when using "nomodeset",
> "acpi=noirq", "acpi=off", "pci=biosirq", "pci=routeirq", "pci=noacpi"
> parameters.
> 
> I have two Zyxel "G-302 v3" wifi adapters reported as RTL 8185 rev 20
> (10ec:8185), which on other two PCs with F1{3,4}/i386 and same config
> works well.
> 
> Can someone help with? Is some general method for solving this issue?

Sorry for the late reply -- I wanted to attempt to recreate the issue.
Unfortunately(?) I am not seeing any such problem.  My card is a PCCard
apparently sold by CompUSA, but the chipset reported in dmesg matches
yours (i.e. RTL8185vD + rtl8225).

I have tried vanilla 2.6.34 and 2.6.35 as well as the Fedora-provided
2.6.35.6-48.fc14 -- all seem to work equally well, despite the annoying
warning that continues to pop-up during scans.  (I need to get that
fixed in Fedora!)

Could you try using netconsole to capture a backtrace over an ethernet
connection?

If that doesn't work, you might try doing a git bisect from the last
working kernel (2.6.33?) to the first broken one (2.6.34?).

Thanks,

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@...driver.com			might be all we have.  Be ready.
--
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/