All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: linux-kernel@vger.kernel.org
Cc: Zwane Mwaikambo <zwane@linuxpower.ca>, Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.9-mm1: NForce3 problem (IRQ sharing issue?)
Date: Mon, 25 Oct 2004 17:31:11 +0200	[thread overview]
Message-ID: <200410251731.11445.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.61.0410251740060.3029@musoma.fsmlabs.com>

On Monday 25 of October 2004 16:45, Zwane Mwaikambo wrote:
> On Mon, 25 Oct 2004, Rafael J. Wysocki wrote:
> 
> > > So did the system still misbehave? What happened?
> > 
> > So far, so good.  The problem has not happened yet, so I think it won't.  
> > Still, I have no such problems with 2.6.9*, although I do not boot them 
with 
> > noapic ...
> > 
> > Thanks for your help anyway,
> 
> Ok, perhaps you shouldn't thank me ;) I actually sortof kinda broke your 
> box... The reason why it worked before was because the kernel defaulted to 
> disabling the IOAPIC on all nforce3 based systems but we found out that 
> most nforce3 systems are actually work with the IOAPIC if we just ignore 
> some bogus ACPI BIOS information. Your system happens to be one of the 
> more broken ones, i'd actually like to try debug your problem a bit 
> further, could you open up a bugzilla entry at bugzilla.kernel.org and 
> email me when you're done. In the meantime, just keep booting with 
> 'noapic'

OK
The bugzilla entry is at:
http://bugzilla.kernel.org/show_bug.cgi?id=3639

Greets,
RJW

-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"

  reply	other threads:[~2004-10-25 15:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-22 21:54 2.6.9-mm1: NForce3 problem (IRQ sharing issue?) Rafael J. Wysocki
2004-10-22 23:26 ` Andrew Morton
     [not found]   ` <Pine.LNX.4.61.0410231424330.3073@musoma.fsmlabs.com>
2004-10-23 11:41     ` Zwane Mwaikambo
     [not found]     ` <200410231928.43049.rjw@sisk.pl>
2004-10-24 16:27       ` Zwane Mwaikambo
2004-10-24 21:08         ` Rafael J. Wysocki
2004-10-25 14:13           ` Zwane Mwaikambo
2004-10-25 14:27             ` Rafael J. Wysocki
2004-10-25 14:45               ` Zwane Mwaikambo
2004-10-25 15:31                 ` Rafael J. Wysocki [this message]
2004-10-28 15:44                   ` Zwane Mwaikambo
2004-10-23 17:13   ` Rafael J. Wysocki
     [not found]   ` <200410231909.09931.rjw@sisk.pl>
2004-10-23 17:55     ` 2.6.9-mm1: NForce3 problem (update) Rafael J. Wysocki
2004-10-24 16:36       ` Zwane Mwaikambo
2004-10-24 20:19         ` Rafael J. Wysocki
2004-10-24 16:19     ` 2.6.9-mm1: NForce3 problem (IRQ sharing issue?) Zwane Mwaikambo
2004-10-23 22:14 ` Allan Sandfeld Jensen
2004-10-23 23:05   ` Rafael J. Wysocki

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=200410251731.11445.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zwane@linuxpower.ca \
    /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.