All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Frantisek Hanzlik <franta@hanzlici.cz>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Andrea Merello <andreamrl@tiscali.it>,
	Michael Wu <flamingice@sourmilk.net>
Subject: Re: rtl8180 freeze some i386 systems
Date: Wed, 24 Nov 2010 10:25:07 -0500	[thread overview]
Message-ID: <20101124152506.GA7435@tuxdriver.com> (raw)
In-Reply-To: <4CEBA51C.5010604@hanzlici.cz>

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@tuxdriver.com			might be all we have.  Be ready.

      parent reply	other threads:[~2010-11-24 15:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-23 11:27 rtl8180 freeze some i386 systems Frantisek Hanzlik
2010-11-23 12:25 ` Dan Carpenter
2010-11-24  9:42   ` Frantisek Hanzlik
2010-11-24 15:25 ` John W. Linville [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101124152506.GA7435@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=andreamrl@tiscali.it \
    --cc=flamingice@sourmilk.net \
    --cc=franta@hanzlici.cz \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.