All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: gene.heskett@verizon.net, linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.9-rc1-mm2
Date: Tue, 31 Aug 2004 12:45:53 -0700	[thread overview]
Message-ID: <238460000.1093981553@flay> (raw)
In-Reply-To: <200408311516.07980.gene.heskett@verizon.net>



--On Tuesday, August 31, 2004 15:16:07 -0400 Gene Heskett <gene.heskett@verizon.net> wrote:

> On Tuesday 31 August 2004 14:53, Martin J. Bligh wrote:
>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.9-
>> rc1/2.6.9-rc1-mm2/
>> 
>>> Nothing particularly noteworthy here.  Some seriously bad
>>> scheduler performance with SMT and HT was fixed up, as was the
>>> fails-to-read-the-last-4k-of-a-file brown bag.
>> 
>> Something is borked in ACPI:
>> 
>> drivers/built-in.o(.text+0x1cf2c): In function `acpi_pci_root_add':
>> /root/linux/2.6.9-rc1-mm2/drivers/acpi/pci_root.c:270: undefined
>> reference to `pci_acpi_scan_root'
>> 
>> Didn't actually realise I had ACPI config'ed in, so will just get
>> rid of it, but though you might want to know.
>> 
>> M.
> 
> I think the borken is maybe in the .config interpretor.  I don't have 
> any ACPI stuff turned on at all, but I've got these lines in my dmesg 
> I've never seen before:
> 
> CPI: RSDP (v000 Nvidia                                ) @ 0x000f7220
> ACPI: RSDT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 
> 0x3fff3000
> ACPI: FADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 
> 0x3fff3040
> ACPI: DSDT (v001 NVIDIA AWRDACPI 0x00001000 MSFT 0x0100000e) @ 
> 0x00000000
> ---
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
> ACPI: Power Resource [ISAV] (on)
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT]
> ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, 
> disabled.
> ACPI: PCI Interrupt Link [LNK2] (IRQs 3 4 5 6 7 10 *11 12 14 15)
> ACPI: PCI Interrupt Link [LNK3] (IRQs 3 4 5 6 7 10 11 *12 14 15)
> ACPI: PCI Interrupt Link [LNK4] (IRQs 3 4 *5 6 7 10 11 12 14 15)
> ACPI: PCI Interrupt Link [LNK5] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, 
> disabled.
> ACPI: PCI Interrupt Link [LUBA] (IRQs 3 4 5 6 7 10 11 *12 14 15)
> ACPI: PCI Interrupt Link [LUBB] (IRQs 3 4 5 6 7 10 *11 12 14 15)
> ACPI: PCI Interrupt Link [LMAC] (IRQs 3 4 5 6 7 10 *11 12 14 15)
> ACPI: PCI Interrupt Link [LAPU] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, 
> disabled.
> ACPI: PCI Interrupt Link [LACI] (IRQs 3 4 5 6 7 10 11 *12 14 15)
> ACPI: PCI Interrupt Link [LMCI] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, 
> disabled.
> ACPI: PCI Interrupt Link [LSMB] (IRQs 3 4 *5 6 7 10 11 12 14 15)
> ACPI: PCI Interrupt Link [LUB2] (IRQs 3 4 *5 6 7 10 11 12 14 15)
> ACPI: PCI Interrupt Link [LFIR] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, 
> disabled.
> ACPI: PCI Interrupt Link [L3CM] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, 
> disabled.
> ACPI: PCI Interrupt Link [LIDE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, 
> disabled.
> ACPI: PCI Interrupt Link [APC1] (IRQs *16), disabled.
> ACPI: PCI Interrupt Link [APC2] (IRQs *17), disabled.
> ACPI: PCI Interrupt Link [APC3] (IRQs *18), disabled.
> ACPI: PCI Interrupt Link [APC4] (IRQs *19), disabled.
> ACPI: PCI Interrupt Link [APC5] (IRQs *16), disabled.
> ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22) *0, disabled.
> ACPI: PCI Interrupt Link [APCG] (IRQs 20 21 22) *0, disabled.
> ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22) *0, disabled.
> ACPI: PCI Interrupt Link [APCI] (IRQs 20 21 22) *0, disabled.
> ACPI: PCI Interrupt Link [APCJ] (IRQs 20 21 22) *0, disabled.
> ACPI: PCI Interrupt Link [APCK] (IRQs 20 21 22) *0, disabled.
> ACPI: PCI Interrupt Link [APCS] (IRQs *23), disabled.
> ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22) *0, disabled.
> ACPI: PCI Interrupt Link [APCM] (IRQs 20 21 22) *0, disabled.
> ACPI: PCI Interrupt Link [AP3C] (IRQs 20 21 22) *0, disabled.
> ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22) *0, disabled.
> ---
> PCI: Using ACPI for IRQ routing
> ** PCI interrupts are no longer routed automatically.  If this
> ** causes a device to stop working, it is probably because the
> ** driver failed to call pci_enable_device().  As a temporary
> ** workaround, the "pci=routeirq" argument restores the old
> ** behavior.  If this argument makes the device work again,
> ** please email the output of "lspci" to bjorn.helgaas@hp.com
> ** so I can fix the driver.
> ---
> ACPI: PCI Interrupt Link [LNK4] enabled at IRQ 5
> ACPI: PCI interrupt 0000:02:00.0[A] -> GSI 5 (level, low) -> IRQ 5
> -ACPI: PCI Interrupt Link [LUB2] enabled at IRQ 5
> ACPI: PCI interrupt 0000:00:02.2[C] -> GSI 5 (level, low) -> IRQ 5
> ---
> ACPI: PCI Interrupt Link [LUBA] enabled at IRQ 12
> ACPI: PCI interrupt 0000:00:02.0[A] -> GSI 12 (level, low) -> IRQ 12
> ---
> ACPI: PCI Interrupt Link [LUBB] enabled at IRQ 11
> ACPI: PCI interrupt 0000:00:02.1[B] -> GSI 11 (level, low) -> IRQ 11
> ---
> ACPI: PCI Interrupt Link [LNK3] enabled at IRQ 12
> ACPI: PCI interrupt 0000:01:08.0[A] -> GSI 12 (level, low) -> IRQ 12
> eth0: RealTek RTL8139 at 0xf883a000, 00:50:ba:5d:eb:7d, IRQ 12
> ---
> eth0:  IdentiCPI: PCI Interrupt Link [LACI] enabled at IRQ 12
> ACPI: PCI interrupt 0000:00:06.0[A] -> GSI 12 (level, low) -> IRQ 12
> fied 8139 chip type 'RTL-8139C'
> ---
> 
> I don't know if this is going to screw me over or not.  But I am sure 
> that ACPI is turned off as shown in a make xconfig. And I just 
> double-checked, its off,
> 
> But: #>grep ACPI .config
> 
># Power management options (ACPI, APM)
># ACPI (Advanced Configuration and Power Interface) Support
> CONFIG_ACPI=y
># CONFIG_ACPI_SLEEP is not set
># CONFIG_ACPI_AC is not set
># CONFIG_ACPI_BATTERY is not set
># CONFIG_ACPI_BUTTON is not set
># CONFIG_ACPI_FAN is not set
># CONFIG_ACPI_PROCESSOR is not set
># CONFIG_ACPI_ASUS is not set
># CONFIG_ACPI_TOSHIBA is not set
># CONFIG_ACPI_DEBUG is not set
> CONFIG_ACPI_EC=y
> CONFIG_ACPI_PCI=y
> 
> Not sure whats going on, can someone turn on the lights?

See other thread ... basically, if you force-remove the "select ACPI"s
it works around it.

M.


  reply	other threads:[~2004-08-31 19:50 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-31  6:54 2.6.9-rc1-mm2 Andrew Morton
2004-08-31  8:51 ` 2.6.9-rc1-mm2 Inconsistent kallsyms Helge Hafting
2004-08-31  9:02   ` Andrew Morton
2004-09-01 10:45     ` Helge Hafting
2004-08-31 11:05   ` Paulo Marques
2004-08-31 12:04 ` 2.6.9-rc1-mm2: tdfxfb_lib causes compile error Adrian Bunk
2004-08-31 17:21 ` 2.6.9-rc1-mm2 (compile stats) John Cherry
2004-08-31 17:41 ` [patch] 2.6.9-rc1-mm2: char/pcxx.c doesn't compile Adrian Bunk
2004-08-31 20:18   ` Jesper Juhl
2004-08-31 20:17     ` Adrian Bunk
2004-08-31 20:27       ` Jesper Juhl
2004-08-31 17:47 ` 2.6.9-rc1-mm2: why is DIGIEPCA marked BROKEN? Adrian Bunk
2004-08-31 19:57   ` Christoph Hellwig
2004-08-31 19:59     ` Adrian Bunk
2004-08-31 18:53 ` 2.6.9-rc1-mm2 Martin J. Bligh
2004-08-31 19:16   ` 2.6.9-rc1-mm2 Gene Heskett
2004-08-31 19:45     ` Martin J. Bligh [this message]
2004-08-31 19:26   ` 2.6.9-rc1-mm2 Andrew Morton
2004-08-31 18:54 ` 2.6.9-rc1-mm2 Gene Heskett
2004-08-31 19:41   ` 2.6.9-rc1-mm2 Sam Ravnborg
2004-09-01 17:35     ` 2.6.9-rc1-mm2 Tom Rini
2004-09-01 19:23       ` 2.6.9-rc1-mm2 Sam Ravnborg
2004-08-31 22:13 ` 2.6.9-rc1-mm2 Rick Lindsley
2004-09-01 21:07   ` 2.6.9-rc1-mm2: IP_NF_COMPAT_IPCHAINS compilation broken Adrian Bunk
2004-09-01  7:15 ` 2.6.9-rc1-mm2 Andre Eisenbach
2004-09-01  7:25   ` 2.6.9-rc1-mm2 William Lee Irwin III
2004-09-01  9:15     ` 2.6.9-rc1-mm2 Andre Eisenbach
  -- strict thread matches above, loose matches on Subject: below --
2004-08-31 17:01 2.6.9-rc1-mm2 Bill Davidsen
2004-08-31 19:42 ` 2.6.9-rc1-mm2 William Lee Irwin III
     [not found] <2zaWg-4Yj-1@gated-at.bofh.it>
     [not found] ` <2zxzF-4pS-19@gated-at.bofh.it>
     [not found]   ` <2zxJk-4vm-29@gated-at.bofh.it>
2004-09-03  9:50     ` 2.6.9-rc1-mm2 Martin Wilck

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=238460000.1093981553@flay \
    --to=mbligh@aracnet.com \
    --cc=akpm@osdl.org \
    --cc=gene.heskett@verizon.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 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.