From: Chris Clayton <chris2553@googlemail.com>
To: Mattias Nissler <mattias.nissler@gmx.de>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Silent crash witk 2-6.24-rc8-git4
Date: Sat, 26 Jan 2008 20:23:19 +0000 [thread overview]
Message-ID: <200801262023.19918.chris2553@googlemail.com> (raw)
In-Reply-To: <1201165422.7472.8.camel@localhost>
On Thursday 24 January 2008, Mattias Nissler wrote:
>
> On Thu, 2008-01-24 at 00:03 +0000, Chris Clayton wrote:
> > Thanks for the reply, John.
> >
> > On Wednesday 23 January 2008, John W. Linville wrote:
> > > 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?
> > >
> >
> > I've reverted the patch by hand - the original patch on linux-wireless doesn't match the present state of the code
> > in rt61pci.c and I'm not a git user. I'm pretty sure I've got it right, however.
> >
> > Problem now is that we are back where we were a few weeks ago because my wireless connection dies
> > almost immediately after I start the download and from dmesg I see:
> >
> > phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 2.
> > Please file bug report to http://rt2x00.serialmonkey.com.
>
> As the patches author, I'm not very surprised :-) The patch just adds
> additional processing that should have happened in a different call of
> the interrupt handler. I don't think it can be related at all to the
> trouble you're seeing.
>
> When I find time, I'll try the Linus tree on my rt61 to see what
> happens.
>
OK, thanks. I look forward to seeing how things go. In the meantime, I'll use the out-of-tree module from serialmonkey.
Chris
> Mattias
>
>
--
Beer is proof that God loves us and wants us to be happy - Benjamin Franklin
next prev parent reply other threads:[~2008-01-26 20:23 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
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 [this message]
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=200801262023.19918.chris2553@googlemail.com \
--to=chris2553@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mattias.nissler@gmx.de \
/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).