Bug 6088 - ACPI Troubles on new Intel iMac's
Summary: ACPI Troubles on new Intel iMac's
Status: REJECTED INSUFFICIENT_DATA
Alias: None
Product: ACPI
Classification: Unclassified
Component: Config-Interrupts (show other bugs)
Hardware: i386 Linux
: P2 blocking
Assignee: ykzhao
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-16 15:02 UTC by Edgar Hucek
Modified: 2007-12-06 18:57 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.16-rc2 2.6.16-rc3 2.6.15.4
Subsystem:
Regression: ---
Bisected commit-id:


Attachments
Dmesg output (26.99 KB, text/plain)
2006-02-16 15:03 UTC, Edgar Hucek
Details
lspci output (19.76 KB, text/plain)
2006-02-16 15:03 UTC, Edgar Hucek
Details
/proc/interrupts output (522 bytes, text/plain)
2006-02-16 15:04 UTC, Edgar Hucek
Details

Description Edgar Hucek 2006-02-16 15:02:38 UTC
Hi.

I'm sitting here with a new Intel iMac. I got the kernel booting and was able to
get video through an hacked vesa FB driver. The kernel is started throug elilo.
The ntel iMac is powered by a new Yonah dualcore notebookchip.
When i try to load at lest 2 driver i get the following error :

ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:02:00.0 to 64
sky2 0000:02:00.0: can't access PCI config space
ACPI: PCI interrupt for device 0000:02:00.0 disabled
sky2: probe of 0000:02:00.0 failed with error -22

PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 18
bcm43xx_d80211: 0000:03:00.0: invalid PCI mem region size(s), aborting
ACPI: PCI interrupt for device 0000:03:00.0 disabled

hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01)
hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01)
hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01)
hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01)
hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01)
hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01)
hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01)
irq 21: nobody cared (try booting with the "irqpoll" option)
 [<c013e6d4>] __report_bad_irq+0x24/0x90
 [<c013e7d3>] note_interrupt+0x93/0x250
 [<c013dffd>] handle_IRQ_event+0x3d/0x70
 [<c013e11d>] __do_IRQ+0xed/0x100
 [<c01055e9>] do_IRQ+0x19/0x30
 [<c010390a>] common_interrupt+0x1a/0x20
 [<c025f252>] acpi_processor_idle+0x15a/0x330
 [<c025007b>] acpi_ps_get_next_namepath+0x71/0x182
 [<c042a630>] unknown_bootoption+0x0/0x250
 [<c0101d29>] cpu_idle+0x69/0x80
 [<c042a572>] start_kernel+0x302/0x3c0
 [<c042a630>] unknown_bootoption+0x0/0x250

I attach sever lags to show you the problem at the init of the kernel and the CPU's.
Comment 1 Edgar Hucek 2006-02-16 15:03:31 UTC
Created attachment 7375 [details]
Dmesg output
Comment 2 Edgar Hucek 2006-02-16 15:03:59 UTC
Created attachment 7376 [details]
lspci output
Comment 3 Edgar Hucek 2006-02-16 15:04:30 UTC
Created attachment 7377 [details]
/proc/interrupts output
Comment 4 Edgar Hucek 2006-02-16 15:05:22 UTC
One thing i forgot to mention. On the Intel iMac is no bios. All is done through
EFI.
Comment 5 ykzhao 2007-10-18 02:21:07 UTC
Hi, Edgar
Will you please upload the acpidump info? 
Thanks.
Comment 6 Fu Michael 2007-12-06 18:57:26 UTC
reject the bug due to no response from bug reporter. please reopen with required info if this bug still bothers you... thanks.

Note You need to log in before you can comment on or make changes to this bug.