public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Georg C. F. Greve" <greve@gnu.org>
To: "Sérgio Monteiro Basto" <sergiomb@netcabo.pt>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	acpi-devel <acpi-devel@lists.sourceforge.net>,
	Linus Torvalds <torvalds@osdl.org>
Subject: Re: [ACPI] Re: PROBLEM: ACPI freezes 2.6.1 on boot
Date: Thu, 22 Jan 2004 11:32:01 +0100	[thread overview]
Message-ID: <m3oesw9sv2.fsf@reason.gnu-hamburg> (raw)
In-Reply-To: <1074727903.3667.49.camel@darkstar.portugal>  (Sérgio Monteiro Basto's message of "21 Jan 2004 23:31:43 +0000")

 || On 21 Jan 2004 23:31:43 +0000
 || Sérgio Monteiro Basto <sergiomb@netcabo.pt> wrote: 

 smb> So you are another APIC victim :)

Seems that way. :)


 smb> [...]

 smb> And thinking, can be true ? that, if SCI can't be
 smb> level-triggered (like my laptop and yours), kernel with APIC
 smb> (loapic or smp) options will hang on boot !

But can it really not be level triggered? 

My dmesg output tells me explicitly that it switched to level
triggered successfully when APIC is disabled.

So is that message wrong or is there a problem between APIC/ACPI?

Should we not be able to resolve that problem anytime soon, I would
suggest to add some information about this to the Kernel help for both
ACPI and APIC, like:

"
 CAUTION: 
 On some laptops, enabling both local APIC and ACPI can cause
 problems.  Should your system hang during boot with a message like
  'ACPI: IRQ X was Edge Triggered, setting to Level Triggerd'
 you should disable either local APIC (recommended) or ACPI. 
 See http://bugzilla.kernel.org/show_bug.cgi?id=1774 for details.
"

that could save people a lot of time in the future hunting down that
bug again -- also it should limit the amount of mails sent around on
the topic. :)

Regards,
Georg

-- 
Georg C. F. Greve                                       <greve@gnu.org>
Free Software Foundation Europe	                 (http://fsfeurope.org)
Brave GNU World	                           (http://brave-gnu-world.org)

  reply	other threads:[~2004-01-22 10:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-21 11:12 PROBLEM: ACPI freezes 2.6.1 on boot Georg C. F. Greve
2004-01-21 15:35 ` Martin Loschwitz
2004-01-21 16:12   ` Georg C. F. Greve
2004-01-21 18:56 ` Linus Torvalds
2004-01-21 21:15   ` Georg C. F. Greve
2004-01-21 21:51     ` [ACPI] " Sérgio Monteiro Basto
2004-01-21 22:33       ` Georg C. F. Greve
2004-01-21 23:31         ` Sérgio Monteiro Basto
2004-01-22 10:32           ` Georg C. F. Greve [this message]
2004-01-21 22:18     ` Linus Torvalds
  -- strict thread matches above, loose matches on Subject: below --
2004-01-21 16:32 Nakajima, Jun
2004-01-21 21:21 ` Georg C. F. Greve
2004-01-21 22:29   ` Georg C. F. Greve
2004-01-22 12:08     ` [ACPI] " Karol Kozimor
2004-01-22 13:59       ` Mikael Pettersson
2004-01-22 14:05         ` Karol Kozimor
2004-01-22 17:15         ` Linus Torvalds
2004-01-22 17:49           ` Mikael Pettersson
2004-01-22 14:08       ` Georg C. F. Greve
2004-01-22 14:26         ` Georg C. F. Greve
2004-01-22 14:16 Yu, Luming
2004-01-22 18:23 Pallipadi, Venkatesh
2004-01-22 18:37 ` Mikael Pettersson
2004-01-22 19:05   ` Linus Torvalds
2004-01-23 13:19     ` Maciej W. Rozycki

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=m3oesw9sv2.fsf@reason.gnu-hamburg \
    --to=greve@gnu.org \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sergiomb@netcabo.pt \
    --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