From: "Sérgio Monteiro Basto" <sergiomb@netcabo.pt>
To: "Georg C. F. Greve" <greve@gnu.org>
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: 21 Jan 2004 23:31:43 +0000 [thread overview]
Message-ID: <1074727903.3667.49.camel@darkstar.portugal> (raw)
In-Reply-To: <m34qupdj94.fsf@reason.gnu-hamburg>
So you are another APIC victim :)
The funny thing, is that I thought that because,
Linus has write :
"It's entirely possible that the SCI is just horribly broken, and can't
be level-triggered" about "ACPI: IRQ 9 was Edge Triggered, setting to
Level Triggerd".
And thinking, can be true ? that, if SCI can't be level-triggered (like
my laptop and yours), kernel with APIC (loapic or smp) options will hang
on boot !
On Wed, 2004-01-21 at 22:33, Georg C. F. Greve wrote:
> || On 21 Jan 2004 21:51:27 +0000
> || Sérgio Monteiro Basto <sergiomb@netcabo.pt> wrote:
>
> smb> And disable apic (lopic and io-pic) options from kernel compilation ?
>
> Funny -- we seemed to have had the same idea.
>
> Yes, this makes it boot (see my other mail).
>
> Regards,
> Georg
>
> --
> Georg C. F. Greve <greve@gnu.org>
> Free Software Foundation Europe (http://fsfeurope.org)
> Brave GNU World (http://brave-gnu-world.org)
--
Sérgio M B
next prev parent reply other threads:[~2004-01-21 23:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-21 11:12 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 [this message]
2004-01-22 10:32 ` Georg C. F. Greve
2004-01-21 22:18 ` Linus Torvalds
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=1074727903.3667.49.camel@darkstar.portugal \
--to=sergiomb@netcabo.pt \
--cc=acpi-devel@lists.sourceforge.net \
--cc=greve@gnu.org \
--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
all inboxes | Powered by JetHome®