All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ayaz Abdulla <aabdulla@nvidia.com>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
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: Sun, 14 May 2006 03:57:28 -0400	[thread overview]
Message-ID: <4466E2E8.7090801@nvidia.com> (raw)
In-Reply-To: <200605122219.37626.s0348365@sms.ed.ac.uk>



Alistair John Strachan wrote:
> On Friday 12 May 2006 00:44, Linus Torvalds wrote:
> 
>>Ok, I've let the release time between -rc's slide a bit too much again,
>>but -rc4 is out there, and this is the time to hunker down for 2.6.17.
>>
>>If you know of any regressions, please holler now, so that we don't miss
>>them.
>>
>>-rc4 itself is mainly random driver fixes (sound, infiniband, scsi,
>>network drivers), but some splice fixes too and some arch (arm, powerpc,
>>mips) updates. Shortlog follows,
> 
> 
> Linus,
> 
> I've got an oops in the forcedeth driver on shutdown. Sorry for the crappy 
> camera phone pictures, this board doesn't have RS232 ports:
> 
> http://devzero.co.uk/~alistair/oops-20060512/
> 
> It was initially difficult to reproduce, but I found I could do so reliably if 
> I ssh'ed into the box and halted it remotely, then it would always oops on 
> shutdown. I assume this is because the driver is still active when something 
> happens to it during halt.
> 
> 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).


  reply	other threads:[~2006-05-15  4:10 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-11 23:44 Linux v2.6.17-rc4 Linus Torvalds
2006-05-12  6:39 ` Andrew Morton
2006-05-12 11:39   ` Stefan Schweizer
2006-05-15  5:57   ` Benjamin Herrenschmidt
2006-05-12 10:24 ` 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 12:50 ` Andi Kleen
2006-05-12 13:04 ` Johannes Stezenbach
2006-05-12 17:45 ` Jan Engelhardt
2006-05-12 21:19 ` Alistair John Strachan
2006-05-14  7:57   ` Ayaz Abdulla [this message]
2006-05-15  5:27     ` Alistair John Strachan
2006-05-20 19:11       ` Alistair John Strachan
2006-05-15 17:49 ` Alan Cox
2006-05-15 18:41   ` [PATCH] slab: Fix kmem_cache_destroy() on NUMA Roland Dreier
2006-05-15 21:47     ` Christoph Lameter
2006-05-16  4:22       ` Pekka Enberg
2006-05-16 11:57     ` Or Gerlitz
2006-05-16 17:09 ` Linux v2.6.17-rc4 Jan Engelhardt
2006-05-16 17:25 ` Jan Engelhardt
2006-05-17  7:53 ` Avuton Olrich
2006-05-17  8:33 ` Avuton Olrich
2006-05-17  9:37   ` Con Kolivas

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=4466E2E8.7090801@nvidia.com \
    --to=aabdulla@nvidia.com \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=netdev@vger.kernel.org \
    --cc=s0348365@sms.ed.ac.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.