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

Date:	Sun, 26 Jul 2009 16:10:13 -0400
From:	Pavel Roskin <proski@....org>
To:	Chris Clayton <chris2553@...glemail.com>
Cc:	linux-wireless@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>, linville@...driver.com
Subject: Re: 2.6.31-rc2: Possible regression in rt61pci driver

On Sun, 2009-07-26 at 20:15 +0100, Chris Clayton wrote:

> One more data point. I wondered whether the freeze would "time out" if
> I just left the laptop frozen, but my testing shows that it probably
> does not (or if it does it takes more than 27 minutes to do so.

I suggest that you run it on the text console after "dmesg -n 8", so
that all kernel messages are seen.

I'm using rt61pci with wireless-testing, and I don't see any freezes.

> I've also tried to bisect again, but, as last time, once I got to the
> batch of network-related changes that went into -rc1, I get a series
> of kernels that build but either won't boot or have inoperable
> wireless networking.

You can use "git bisect skip" to skip those revisions.

You can specify the paths in "git bisect start" so that only changes to
the interesting places (like drivers/net wireless, net/mac80211 and
net/wireless) are considered when calculating the next commit.  This
will probably help you avoid the bad place.

Also, please try the current wireless-testing.  The problem may be fixed
there.

> Finally, since I haven't had a single reply to the regression report I
> posted almost two weeks ago, I now give up. I'll switch to using the
> card supported by the ath5k driver.

Perhaps there was not enough material for others to comment on, and
nobody was experiencing anything similar.

If I had such problem, I would try to bisect it, but I cannot reproduce
it.

-- 
Regards,
Pavel Roskin
--
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/