[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201001112104.54141.rjw@sisk.pl>
Date: Mon, 11 Jan 2010 21:04:54 +0100
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: sboyce@...eyonder.co.uk
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kernel Testers List <kernel-testers@...r.kernel.org>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>
Subject: Re: [Bug #14946] All kernels after 2.6.32-git10 show only 1 CPU
On Monday 11 January 2010, Sid Boyce wrote:
> On 10/01/10 22:32, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.32. Please verify if it still should be listed and let me know
> > (either way).
> >
> >
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14946
> > Subject : All kernels after 2.6.32-git10 show only 1 CPU
> > Submitter : Sid Boyce <sboyce@...eyonder.co.uk>
> > Date : 2009-12-23 16:55 (19 days old)
> > References : http://marc.info/?l=linux-kernel&m=126158734326801&w=4
> >
> >
> >
> >
>
> With 2.6.33-rc3-git3 I now see 2 CPU's every on a normal boot, but its
> locking up solid at this part of the boot process as usual.
> ACPI: PCI Interrupt Link [AAZA] enabled at IRQ 22
> HDA Intel 0000:00:0e.1: PCI INT B -> Link[AAZA] -> GSI 22 (level, low)
> -> IRQ 22.
> With acpi=noirq (2 CPU's)
> ================
> kvm: Nested Virtualization enabled.
> IT8716 Super IO detected
> Parport_PC 00:0a: reported by plug and Play ACPI
> Parport 0: PC-Style at 0x378, irq 7 [PCSPP, TRISTATE,EPP]
> parport: irq 7 in use, resorting to polled operation
> HDA Intel 0000:00:0e.1: PCI -> APIC IRQ transform: INT B -> IRQ 11
>
> With acpi=ht (1 CPU)
> =============
> Hangs at:-
> Loading drivees, configuring devices do_IRQ: 0.65 No irq handler for
> vector (irq -1)
>
> With acpi=off (2 CPU's)
> ========================
> Hangs at same point as with acpi=noirq.
Thanks for the update.
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists