public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Creswell <dan@dcrdev.demon.co.uk>
To: Linus Torvalds <torvalds@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hard lock on 2.6-test9 (More Info)
Date: Mon, 17 Nov 2003 16:46:34 +0000	[thread overview]
Message-ID: <3FB8FB6A.8070609@dcrdev.demon.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0311170829000.8840-100000@home.osdl.org>

Thanks for the advice Linus - I'll give that a go.

As an aside, I've tried both the nvidia drivers and the out-of-the-box 
Xfree ones with the same results (2.4 stable, 2.6 not).

I'll get back to the list with more info once I've done the testing.

Thanks again for your time,

Dan.

Linus Torvalds wrote:

>On Mon, 17 Nov 2003, Dan Creswell wrote:
>  
>
>> 17:       5267       3420   IO-APIC-level  ohci1394, Intel ICH4, nvidia
>>
>>When I boot X under kernel 2.6, I see the additional nvidia interrupt 
>>path as per the 2.4 output (which was taken whilst I was running X).
>>
>>But, within seconds of this additional interrupt assignment appearing, 
>>2.6 dies a horrible death whilst 2.4 just keeps on rolling.
>>    
>>
>
>Two potential reasons:
> - the nvidia driver is just broken under 2.6.x
> - or a driver bug in ohci1394 _or_ the Intel ICH4 driver, which could 
>   become unhappy if they see a lot of interrupts that aren't for them 
>   (maybe it uncovers a race).
>
>You can test for the latter by just disabling those drivers, and seeing 
>what happens. If it still breaks, it's nvidia. If the crashes stop, it 
>might _still_ be nvidia, but at that point somebody else might start being 
>interested in it.
>
>		Linus
>
>
>
>  
>



      reply	other threads:[~2003-11-17 16:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-17 13:32 Hard lock on 2.6-test9 (More Info) Dan Creswell
2003-11-17 16:32 ` Linus Torvalds
2003-11-17 16:46   ` Dan Creswell [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=3FB8FB6A.8070609@dcrdev.demon.co.uk \
    --to=dan@dcrdev.demon.co.uk \
    --cc=linux-kernel@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