linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Chris Clayton <chris2553@googlemail.com>
Cc: linux-wireless@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Silent crash witk 2-6.24-rc8-git4
Date: Wed, 23 Jan 2008 14:02:07 -0500	[thread overview]
Message-ID: <20080123190207.GB3129@tuxdriver.com> (raw)
In-Reply-To: <200801231642.58782.chris2553@googlemail.com>

On Wed, Jan 23, 2008 at 04:42:58PM +0000, Chris Clayton wrote:
> On Wednesday 23 January 2008, Chris Clayton wrote:
> > Hi again.
> > 
> > On Tuesday 22 January 2008, Chris Clayton wrote:
> > > Hi,
> 
> and here's another, slightly more complete, one, this time from 2.6.24-rc8-git6
> (the none I sent earlier was from -git4, by the way)
> 
> Call Trace:
> [<c011440a>] __update_rq_clock+0x1a/0xf0
> [<e08ff59d>] rt2x00lib_txdone+0x9d/0xd0 [rt2x00lib]
> [<e0909573>] rt61pci_txdone+0x153/0x1f0 [rt61pci]
> [<e09096ad>] rt61pci_interrupt+0x9d/0xb0 [rt61pci]

I suspect this could relate to this commit:

commit 62bc060b8ed5fcdafd87da5ab17bdd59a39ebcc9
Author: Mattias Nissler <mattias.nissler@gmx.de>
Date:   Mon Nov 12 15:03:12 2007 +0100

    rt2x00: Allow rt61 to catch up after a missing tx report

Could you revert that patch, rebuild, and try to recreate the problem?

Thanks!

John
-- 
John W. Linville
linville@tuxdriver.com

  reply	other threads:[~2008-01-23 19:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-22  6:03 Silent crash witk 2-6.24-rc8-git4 Chris Clayton
2008-01-23 15:21 ` Chris Clayton
2008-01-23 16:42   ` Chris Clayton
2008-01-23 19:02     ` John W. Linville [this message]
2008-01-24  0:03       ` Chris Clayton
2008-01-24  8:49         ` Chris Clayton
2008-01-24  9:03         ` Mattias Nissler
2008-01-26 20:23           ` Chris Clayton
2008-01-31 20:13       ` Chris Clayton
2008-01-31 21:03         ` John W. Linville
2008-01-31 22:26           ` Chris Clayton

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=20080123190207.GB3129@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=chris2553@googlemail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@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 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).