Bug#502849: Possible fix
I installed r12453 sid snapshot xen kernel. It works: xen dom0 boots on all my 3 test PCs. Attached to this message you can find Gigabyte P35-DS3L motherboard PC boot log. Thanks for your support. Original Message Subject: Bug#502849: Possible fix From: Ian Campbell [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: 27/11/2008 9.01 Executive summary: please try the r12453 sid snapshot once it appears. (XEN) Xen version 3.2-1 (Debian 3.2.1-2) ([EMAIL PROTECTED]) (gcc version 4.3.1 (Debian 4.3.1-2) ) Sat Jun 28 09:32:18 UTC 2008 (XEN) Command line: console=com1,vga com1=115200,8n1 (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds (XEN) EDID info not retrieved because no DDC retrieval method detected (XEN) Disc information: (XEN) Found 1 MBR signatures (XEN) Found 1 EDD information structures (XEN) Xen-e820 RAM map: (XEN) - 0009f800 (usable) (XEN) 0009f800 - 000a (reserved) (XEN) 000f - 0010 (reserved) (XEN) 0010 - 7fee (usable) (XEN) 7fee - 7fee3000 (ACPI NVS) (XEN) 7fee3000 - 7fef (ACPI data) (XEN) 7fef - 7ff0 (reserved) (XEN) f000 - f400 (reserved) (XEN) fec0 - 0001 (reserved) (XEN) System RAM: 2046MB (2095612kB) (XEN) Xen heap: 14MB (15012kB) (XEN) Domain heap initialised: DMA width 32 bits (XEN) Processor #0 6:15 APIC version 20 (XEN) Processor #1 6:15 APIC version 20 (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec0, GSI 0-23 (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 2400.048 MHz processor. (XEN) CPU0: Intel(R) Core(TM)2 Duo CPU E4600 @ 2.40GHz stepping 0d (XEN) Booting processor 1/1 eip 8c000 (XEN) CPU1: Intel(R) Core(TM)2 Duo CPU E4600 @ 2.40GHz stepping 0d (XEN) Total of 2 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) - Using new ACK method (XEN) Platform timer overflows in 14998 jiffies. (XEN) Platform timer is 14.318MHz HPET (XEN) Brought up 2 CPUs (XEN) AMD IOMMU: Disabled (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, lsb, paddr 0x20 - 0x631918 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 7800-7a00 (472725 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: 8020-80631918 (XEN) Init. ramdisk: 80632000-81857e00 (XEN) Phys-Mach map: 81858000-81c034a8 (XEN) Start info:81c04000-81c044a4 (XEN) Page tables: 81c05000-81c18000 (XEN) Boot stack:81c18000-81c19000 (XEN) TOTAL: 8000-8200 (XEN) ENTRY ADDRESS: 8020 (XEN) Dom0 has maximum 2 VCPUs (XEN) Initrd len 0x1225e00, start at 0x80632000 (XEN) Scrubbing Free RAM: .done. (XEN) Xen trace buffers: disabled (XEN) Std. Loglevel: Errors and warnings (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) (XEN) Xen is relinquishing VGA console. (XEN) *** Serial input - DOM0 (type 'CTRL-a' three times to switch input to Xen) (XEN) Freed 104kB init memory. Kernel alive kernel direct mapping tables up to 75e95000 @ 1c18000-1fcb000 [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.26-1-xen-amd64 (Debian 2.6.26-12~snapshot.12453) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23+1)) #1 SMP Fri Nov 28 04:06:47 UTC 2008 [0.00] Command line: root=/dev/sda7 ro console=tty0 [0.00] BIOS-provided physical RAM map: [0.00] Xen: - 75e95000 (usable) [0.00] max_pfn_mapped = 482965 [0.00] init_memory_mapping [0.00] DMI 2.4 present. [0.00] early res: 0 [20-631917] TEXT DATA BSS [0.00] early res: 1 [632000-1c17fff] Xen provided [0.00] early res: 2 [1c18000-1fcbfff] PGTABLE [0.00] Zone PFN ranges: [0.00] DMA 0 - 4096 [0.00] DMA324096 - 1048576 [0.00] Normal1048576 - 1048576 [0.00] Movable zone start PFN for each node [0.00] early_node_map[1] active PFN ranges [0.00] 0:0 - 482965 [0.00] ACPI: RSDP 000F6A60, 0014 (r0 GBT ) [0.00] ACPI: RSDT 7FEE3040, 0038 (r1 GBTGBTUACPI 42302E31 GBTU 1010101) [0.00] ACPI: FACP 7FEE30C0, 0074 (r1 GBTGBTUACPI 42302E31 GBTU 1010101) [0.00] ACPI: DSDT 7FEE3180, 4B27 (r1 GBTGBTUACPI 1000 MSFT 10C) [0.00] ACPI: FACS 7FEE, 0040 [0.00] ACPI: HPET 7FEE7E00, 0038 (r1 GBTGBTUACPI 42302E31 GBTU 98) [0.00] ACPI: MCFG 7FEE7E80, 003C (r1
Bug#502849: Possible fix
Executive summary: please try the r12453 sid snapshot once it appears.
apt repo lines are available on http://wiki.debian.org/DebianKernel
In the later report (Paul Hedderly) the erroring rip
(0x80227fe2) which corresponds to set_cpus_allowed_ptr+31 (or
0x1f out of 0xe0) is:
0x80227fda set_cpus_allowed_ptr+23: callq 0x8022493b
task_rq_lock
0x80227fdf set_cpus_allowed_ptr+28: mov%rax,%r13
0x80227fe2 set_cpus_allowed_ptr+31: mov(%rbx),%rax
0x80227fe5 set_cpus_allowed_ptr+34: and$0x,%eax
0x80227fe8 set_cpus_allowed_ptr+37: test %rax,0x3e5819(%rip)
# 0x8060d808 cpu_online_map
The fault is on the address in %rbx (0xff5f7000).
0x80227fe2 is in set_cpus_allowed_ptr (kernel/sched.c:5628).
5623unsigned long flags;
5624struct rq *rq;
5625int ret = 0;
5626
5627rq = task_rq_lock(p, flags);
5628if (!cpus_intersects(*new_mask, cpu_online_map)) {
5629ret = -EINVAL;
5630goto out;
5631}
5632
I believe %rbx is new_mask. In the earlier two reports (both Andrea
Janna's) the erroring rip (0x80228045) doesn't precisely match
this but says it set_cpus_allowed_ptr+0x1f/0xe0 which is the same as in
Paul's report so I think it safe to say the versions we're simply linked
slightly differently and it's the same instruction.
The caller of set_cpus_allowed_ptr was
:processor:acpi_processor_get_throttling+0x45/0x6a which is
0x04fa acpi_processor_get_throttling+64: callq 0x4ff
acpi_processor_get_throttling+69
0x04ff acpi_processor_get_throttling+69: mov%rbx,%rdi
(odd address since this is an unlinked .ko file)
0x4fa is in acpi_processor_get_throttling
(drivers/acpi/processor_throttling.c:841).
836 return -ENODEV;
837 /*
838 * Migrate task to the cpu pointed by pr.
839 */
840 saved_mask = current-cpus_allowed;
841 set_cpus_allowed_ptr(current, cpumask_of_cpu(pr-id));
842 ret = pr-throttling.acpi_processor_get_throttling(pr);
843 /* restore the previous state */
844 set_cpus_allowed_ptr(current, saved_mask);
845
So this suggests that cpumask_of_cpu(pr-id) is somehow bogus.
pr came from acpi_processor_start() via
acpi_processor_get_throttling_info(). Just before the call to
acpi_processor_get_throttling_info() in acpi_processor_start() we see:
#ifdef CONFIG_XEN
BUG_ON(pr-acpi_id = NR_ACPI_CPUS);
if (processor_device_array[pr-acpi_id] != NULL
processor_device_array[pr-acpi_id] != device) {
#else
if (processor_device_array[pr-id] != NULL
processor_device_array[pr-id] != device) {
#endif /* CONFIG_XEN */
printk(KERN_WARNING BIOS reported wrong ACPI id
for the processor\n);
return -ENODEV;
}
#ifdef CONFIG_XEN
processor_device_array[pr-acpi_id] = device;
if (pr-id != -1)
processors[pr-id] = pr;
#else
processor_device_array[pr-id] = device;
processors[pr-id] = pr;
#endif /* CONFIG_XEN */
This code is fairly recent in the linux-2.6.18-xen.hg tree and comes
from a combination of two changesets (one adds the feature, the other
unbreaks native build resulting in the ifdef'ery seen above):
http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/d62d60eaba6e
http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/e39cf97647af
There are bunch of changes subsequent to these but
http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/de7f94bd650b looks
pretty interesting:
changeset: 713:de7f94bd650b
user:Keir Fraser [EMAIL PROTECTED]
date:Tue Oct 28 10:39:11 2008 +
files: drivers/acpi/processor_core.c
description:
dom0: Fix for throttling while pr-id == -1
Signed-off-by: Wei Gang [EMAIL PROTECTED]
This changeset is not present in our current kernel tree. I have added
it and it will show up in the snapshot builds shortly.
Ian.
--
Ian Campbell
No passing.
signature.asc
Description: This is a digitally signed message part
Bug#502849:
Up to now I tested xen kernel linux-image-2.6.26-1-xen-amd64 on 3 different PCs. 1- Gigabyte GA-965P-DS4 rev 2 motherboard, Intel P965 Express Chipset, Intel Core 2 Duo CPU. - kernel crashes at boot (boot log available at http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=10;filename=Gigabyte+GA-965P-DS4.log;att=1;bug=502849) 2- Gigabyte P35-DS3L motherboard, Intel P35 Express Chipset, Intel E4600 CPU. - kernel crashes at boot (boot log available at http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=boot.log;att=1;bug=502849) 3- Asus A8V-E-SE motherboard, VIA K8T890 chipset, Athlon64 3000+ CPU. - kernel starts normally Original Message Subject: Re: Bug#502849: From: Bastian Blank [EMAIL PROTECTED] To: Andrea Janna [EMAIL PROTECTED], [EMAIL PROTECTED] Date: 14/11/2008 17.01 Please provide complete message, this is just the generic Oops header without any additional information. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#502849: Me too!
I'm having the same issue here - can't boot a 64 bit kernel with xen: It's a Supermicro X7DVL-E with an Intel L5410 xeon. The problem is the same with xen 3.2 and unstable but only affects amd64 kernels. 686 kernel boots fine (even with amd64 hypervisor) Tried several -10 and now -11 kernels. The trace with below with: 2.6.26-1-xen-amd64 = 2.6.26-11~snapshot.12382 -- Regards, Paul root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /xen-3.2-1-amd64.gz com1=115200,8n1 console=com2,vga [Multiboot-elf, 0x10:0xe6648:0x609b8, shtab=0x247078, entry=0x10] module /vmlinuz-2.6.26-1-xen-amd64 root=/dev/mapper/jack--r5a-j32 ro panic=60 xencons=ttyS0 console=tty0 console=ttyS1,115200n8 [Multiboot-module @ 0x248000, 0x79eba0 bytes] module /initrd.img-2.6.26-1-xen-amd64 [Multiboot-module @ 0x9e7000, 0x1818800 bytes](XEN) Xen version 3.2-1 (Debian 3.2.1-2) ([EMAIL PROTECTED]) (gcc version 4.3.1 (Debian 4.3.1-2) ) Sat Jun 28 09:32:18 UTC 2008 (XEN) Command line: com1=115200,8n1 console=com2,vga (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: none; EDID transfer time: 2 seconds (XEN) EDID info not retrieved because no DDC retrieval method detected (XEN) Disc information: (XEN) Found 3 MBR signatures (XEN) Found 3 EDD information structures (XEN) Xen-e820 RAM map: (XEN) - 0009cc00 (usable) (XEN) 0009cc00 - 000a (reserved) (XEN) 000e4000 - 0010 (reserved) (XEN) 0010 - cff6 (usable) (XEN) cff6 - cff69000 (ACPI data) (XEN) cff69000 - cff8 (ACPI NVS) (XEN) cff8 - d000 (reserved) (XEN) e000 - f000 (reserved) (XEN) fec0 - fec1 (reserved) (XEN) fee0 - fee01000 (reserved) (XEN) ff00 - 0001 (reserved) (XEN) 0001 - 00013000 (usable) (XEN) System RAM: 4094MB (4193264kB) (XEN) Xen heap: 14MB (14920kB) (XEN) Domain heap initialised: DMA width 32 bits (XEN) Processor #0 7:7 APIC version 20 (XEN) Processor #1 7:7 APIC version 20 (XEN) Processor #2 7:7 APIC version 20 (XEN) Processor #3 7:7 APIC version 20 (XEN) IOAPIC[0]: apic_id 4, version 32, address 0xfec0, GSI 0-23 (XEN) IOAPIC[1]: apic_id 5, version 32, address 0xfec8, GSI 24-47 (XEN) Enabling APIC mode: Flat. Using 2 I/O APICs (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 2333.504 MHz processor. (XEN) HVM: VMX enabled (XEN) CPU0: Intel(R) Xeon(R) CPU L5410 @ 2.33GHz stepping 06 (XEN) Booting processor 1/1 eip 8c000 (XEN) CPU1: Intel(R) Xeon(R) CPU L5410 @ 2.33GHz stepping 06 (XEN) Booting processor 2/2 eip 8c000 (XEN) CPU2: Intel(R) Xeon(R) CPU L5410 @ 2.33GHz stepping 06 (XEN) Booting processor 3/3 eip 8c000 (XEN) CPU3: Intel(R) Xeon(R) CPU L5410 @ 2.33GHz stepping 06 (XEN) Total of 4 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) - Using new ACK method (XEN) Platform timer overflows in 14998 jiffies. (XEN) Platform timer is 14.318MHz HPET (XEN) Brought up 4 CPUs (XEN) xenoprof: Initialization failed. Intel processor model 23 for P6 class family is not supported (XEN) AMD IOMMU: Disabled (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, lsb, paddr 0x20 - 0x631918 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 00012800-00012c00 (978639 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: 8020-80631918 (XEN) Init. ramdisk: 80632000-81e4a800 (XEN) Phys-Mach map: 81e4b000-825e2678 (XEN) Start info:825e3000-825e34a4 (XEN) Page tables: 825e4000-825fb000 (XEN) Boot stack:825fb000-825fc000 (XEN) TOTAL: 8000-8280 (XEN) ENTRY ADDRESS: 8020 (XEN) Dom0 has maximum 4 VCPUs (XEN) Initrd len 0x1818800, start at 0x80632000 (XEN) Scrubbing Free RAM: .done. (XEN) Xen trace buffers: disabled (XEN) Std. Loglevel: Errors and warnings (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) (XEN) Xen is relinquishing VGA console. (XEN) *** Serial input - DOM0 (type 'CTRL-a' three times to switch input to Xen) (XEN) Freed 104kB init memory. Kernel alive kernel direct mapping tables up to f36cf000 @ 25fe000-2d9f000 [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.26-1-xen-amd64 (Debian 2.6.26-11~snapshot.12382) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23+1)) #1 SMP Fri Nov 14 04:00:36 UTC 2008 [0.00] Command line: root=/dev/mapper/jack--r5a-j32 ro panic=60 xencons=ttyS0 console=tty0 console=ttyS1,115200n8 [0.00] BIOS-provided physical RAM map: [
Bug#502849:
I installed Debian Lenny on another PC with motherboard Asus A8V-E-SE, chipset VIA K8T890 and VT8237R, CPU Athlon64 3000+. I installed xen-linux-system-2.6.26-1-xen-amd64 package and rebooted. The system started up without kernel Oops: [1] SMP error. So up to now I tested xen kernel linux-image-2.6.26-1-xen-amd64 on 3 different PCs. 1- Gigabyte GA-965P-DS4 rev 2 motherboard, Intel P965 Express Chipset, Intel Core 2 Duo CPU. - kernel crashes at boot (Oops: [1] SMP) 2- Gigabyte P35-DS3L motherboard, Intel P35 Express Chipset, Intel E4600 CPU. - kernel crashes at boot (Oops: [1] SMP) 3- Asus A8V-E-SE motherboard, VIA K8T890 chipset, Athlon64 3000+ CPU. - kernel starts normally Original Message Subject: Bug#502849: Acknowledgement (linux-image-2.6.26-1-xen-amd64: unable to handle kernel paging request) From: [EMAIL PROTECTED] (Debian Bug Tracking System) To: Andrea Janna [EMAIL PROTECTED] Date: 20/10/2008 11.42 Thank you for filing a new Bug report with Debian. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Debian Kernel Team [EMAIL PROTECTED] If you wish to submit further information on this problem, please send it to [EMAIL PROTECTED], as before. Please do not send mail to [EMAIL PROTECTED] unless you wish to report a problem with the Bug-tracking system. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#502849:
On Fri, Nov 14, 2008 at 10:36:50AM +0100, Andrea Janna wrote: 1- Gigabyte GA-965P-DS4 rev 2 motherboard, Intel P965 Express Chipset, Intel Core 2 Duo CPU. - kernel crashes at boot (Oops: [1] SMP) Please provide complete message, this is just the generic Oops header without any additional information. -- A Vulcan can no sooner be disloyal than he can exist without breathing. -- Kirk, The Menagerie, stardate 3012.4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
