tech-kern archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: pckbc_acpi_attach: couldn't map



On Wed, May 25, 2011 at 10:57:43PM +0200, Edgar Fuß wrote:
> I have an amd64 machine which runs the 4.0.1 INSTALL kernel, but fails to run 
> the 4.0.1 GENERIC one.
> 5.1 works OK (but I wnt to try 4.0.1 for my fs-performance-on-RAID issues).
> 
> For GENERIC, it's:
> [...]
> cpu0: ITLB 32 4 KB entries fully associative, 8 4 MB entries fully associative
> cpu0: DTLB 32 4 KB entries fully associative, 8 4 MB entries fully associative
> cpu0: AMD Power Management features: 7f<STC,TM,TTP,VID,FID,TS>
> cpu0: calibrating local timer
> cpu0: apic clock running at 200 MHz
> cpu0: 8 page colors
> cpu1 at mainbus0: apid 1 (application processor)
> cpu1: not started
> ioapic0 at mainbus0 apid 2 (I/O APIC)
> ioapic0: pa 0xfec00000, version 21, 24 pins
> acpi0 at mainbus0: Advanced Configuration and Power Interface
> acpi0: using Intel ACPI CA subsystem version 20060217
> acpi0: X/RSDT: OemId <012411,OEMXSDT ,20110124>, AslId <MSFT,00000097>
> acpi0: SCI interrupting at int 9
> acpi0: fixed-feature power button present
> timecounter: Timecounter "ACPI-Safe" frequency 3579545 Hz quality 900
> ACPI-Safe 32-bit timer
> ACPI Object Type 'Processor' (0x0c) at acpi0 not configured
> ACPI Object Type 'Processor' (0x0c) at acpi0 not configured
> ACPI Object Type 'Processor' (0x0c) at acpi0 not configured
> ACPI Object Type 'Processor' (0x0c) at acpi0 not configured
> ACPI Object Type 'Processor' (0x0c) at acpi0 not configured
> ACPI Object Type 'Processor' (0x0c) at acpi0 not configured
> ACPI Object Type 'Processor' (0x0c) at acpi0 not configured
> ACPI Object Type 'Processor' (0x0c) at acpi0 not configured
> ACPI Object Type 'Processor' (0x0c) at acpi0 not configured
> ACPI Object Type 'Processor' (0x0c) at acpi0 not configured
> ACPI Object Type 'Processor' (0x0c) at acpi0 not configured
> ACPI Object Type 'Processor' (0x0c) at acpi0 not configured
> PNP0A03 [PCI/PCI-X Host Bridge] at acpi0 not configured
> PNP0C02 [Plug and Play motherboard register resources] at acpi0 not configured
> pckbc1 at acpi0 (PNP0303): kbd port
> pckbc1: io 0x60,0x64 irq 1
> pckbc2 at acpi0 (PNP0F03): aux port
> pckbc2: irq 12
> PNP0000 [AT Interrupt Controller] at acpi0 not configured
> PNP0200 [AT DMA Controller] at acpi0 not configured
> attimer1 at acpi0 (PNP0100): AT Timer
> attimer1: io 0x40-0x43 irq 0
> PNP0B00 [AT Real-Time Clock] at acpi0 not configured
> pcppi1 at acpi0 (PNP0800)
> pcppi1: io 0x61
> pcppi1: children must have an explicit unit
> midi0 at pcppi1: PC speaker (CPU-intensive output)
> sysbeep0 at pcppi1
> PNP0C04 [Math Coprocessor] at acpi0 not configured
> PNP0700 [PC standard floppy disk controller] at acpi0 not configured
> ATK0110 at acpi0 not configured
> PNP0103 [HPET Timer] at acpi0 not configured
> PNP0C02 [Plug and Play motherboard register resources] at acpi0 not configured
> PNP0C02 [Plug and Play motherboard register resources] at acpi0 not configured
> pckbc3 at acpi0 (PNP0303): kbd port
> pckbc3: io 0x60,0x64 irq 1
> panic: pckbc_acpi_attach: couldn't map

It already has found a pckbc at io 0x60 (pckbc1). Not sure why it find PNP0303
twice, but it can easily be worked around by removing
pckbc at acpi from the kernel config (the pckbc at isa will then match,
as with the INSTALL kernel).

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--


Home | Main Index | Thread Index | Old Index