mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Clayton <andrew@digital-domain.net>
To: linux-kernel@vger.kernel.org
Subject: ACPI error with 2.4.26-pre5
Date: Sat, 20 Mar 2004 18:48:38 +0000	[thread overview]
Message-ID: <1079808518.1120.25.camel@alpha.digital-domain.net> (raw)

Hello,

With 2.4.26-pre5 I am seeing the following error at boot up.


ACPI: Subsystem revision 20040311
PCI: PCI BIOS revision 2.10 entry at 0xe8964, last bus=1
PCI: Using configuration type 1
    ACPI-0433: *** Warning: Existing references (4) on node being
deleted (c129e
660)
    ACPI-0433: *** Warning: Existing references (9) on node being
deleted (c12ae
da0)
ACPI: IRQ9 SCI: Edge set to Level Trigger.
    ACPI-0097: *** Error: Unable to initialize general purpose events,
AE_NOT_FO
UND
ACPI: Unable to start the ACPI Interpreter
    ACPI-0433: *** Warning: Existing references (65419) on node being
deleted (c
129e4e0)
PCI: Probing PCI hardware
PCI: ACPI tables contain no PCI IRQ routing entries
PCI: Probing PCI hardware (bus 00)
PCI: Using IRQ router VIA [1106/3074] at 00:11.0



2.4.26-pre4 works fine. This is on a Fujitsu-Siemens C-1020 laptop
running Fedora Core 1


To keep the size of this email down I have provided links to relevant
bits of information.

2.4.26-pre5 .config
http://digital-domain.net/kernel/config

2.4.26-pre5 kernel boot messages
http://digital-domain.net/kernel/2.4.26-pre5.dmesg

2.4.26.-pre4 kernel boot messages (for comparison)
http://digital-domain.net/kernel/2.4.26-pre4.dmesg

Output of lspci -vv
http://digital-domain.net/kernel/lspci-vv


If you would like any extra info please CC me...


Cheers,

Andrew Clayton



             reply	other threads:[~2004-03-20 18:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-20 18:48 Andrew Clayton [this message]
     [not found] <A6974D8E5F98D511BB910002A50A6647615F5EB1@hdsmsx402.hd.intel.com>
2004-03-21  2:55 ` Len Brown

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=1079808518.1120.25.camel@alpha.digital-domain.net \
    --to=andrew@digital-domain.net \
    --cc=linux-kernel@vger.kernel.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®