From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Ayaz Abdulla <aabdulla@nvidia.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
jeff@garzik.org, netdev@vger.kernel.org,
Manfred Spraul <manfred@colorfullife.com>
Subject: Re: Linux v2.6.17-rc4
Date: Sat, 20 May 2006 20:11:11 +0100 [thread overview]
Message-ID: <200605202011.11685.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <200605150627.19498.s0348365@sms.ed.ac.uk>
On Monday 15 May 2006 06:27, Alistair John Strachan wrote:
> On Sunday 14 May 2006 08:57, Ayaz Abdulla wrote:
> > Alistair John Strachan wrote:
>
> [snip]
>
> > > There's been just a single commit since -rc3:
> > >
> > > forcedeth: fix multi irq issues
> > > ebf34c9b6fcd22338ef764b039b3ac55ed0e297b
> > >
> > > However, it could have just been hidden since before -rc3, so I'll try
> > > to work backwards if nobody has any immediate ideas..
> >
> > The interrupt handler could be called during the same time (on different
> > cpu) the dev->stop function is clearing out the rings (nv_txrx_reset).
>
> FWIW, I can't reproduce the fault with the commitdiff
> ebf34c9b6fcd22338ef764b039b3ac55ed0e297b reverted.
Manfred located the fault and Andrew's holding a fix for it in -mm. Hopefully
it'll end up in mainline before 2.6.17.
--
Cheers,
Alistair.
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
prev parent reply other threads:[~2006-05-20 19:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0605111640010.3866@g5.osdl.org>
2006-05-12 10:24 ` Linux v2.6.17-rc4 Erik Mouw
2006-05-12 10:44 ` Michael Buesch
2006-05-12 11:23 ` Olaf Hering
2006-05-12 20:54 ` Michael Buesch
2006-05-12 11:47 ` Erik Mouw
2006-05-12 20:58 ` Michael Buesch
2006-05-12 21:19 ` Alistair John Strachan
2006-05-14 7:57 ` Ayaz Abdulla
2006-05-15 5:27 ` Alistair John Strachan
2006-05-20 19:11 ` Alistair John Strachan [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=200605202011.11685.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=aabdulla@nvidia.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=netdev@vger.kernel.org \
--cc=torvalds@osdl.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).