From: Pavel Roskin <proski@gnu.org>
To: Chris Clayton <chris2553@googlemail.com>
Cc: linux-wireless@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
linville@tuxdriver.com
Subject: Re: 2.6.31-rc2: Possible regression in rt61pci driver
Date: Sun, 26 Jul 2009 16:10:13 -0400 [thread overview]
Message-ID: <1248639013.32168.15.camel@mj> (raw)
In-Reply-To: <c6b1100b0907261215l71ada148y8a15f6595d939192@mail.gmail.com>
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
next prev parent reply other threads:[~2009-07-26 20:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 8:27 2.6.31-rc2: Possible regression in rt61pci driver Chris Clayton
2009-07-14 11:04 ` Chris Clayton
2009-07-21 11:39 ` Chris Clayton
2009-07-26 19:15 ` Chris Clayton
2009-07-26 20:10 ` Pavel Roskin [this message]
2009-07-26 21:33 ` Chris Clayton
2009-07-27 0:06 ` Pavel Roskin
2009-07-27 9:35 ` Chris Clayton
2009-07-27 14:27 ` Pavel Roskin
2009-07-27 19:35 ` Chris Clayton
2009-07-27 20:07 ` Pavel Roskin
2009-07-27 20:22 ` Chris Clayton
2009-07-27 20:30 ` Pavel Roskin
2009-07-27 20:32 ` Johannes Berg
2009-07-28 11:03 ` Chris Clayton
2009-07-28 11:11 ` Luis Correia
2009-07-28 13:34 ` Chris Clayton
2009-07-28 13:38 ` Luis Correia
2009-07-28 14:15 ` Chris Clayton
2009-07-29 7:03 ` Chris Clayton
2009-07-29 7:21 ` Johannes Berg
2009-07-29 7:45 ` Kalle Valo
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=1248639013.32168.15.camel@mj \
--to=proski@gnu.org \
--cc=chris2553@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).