Ian P. Christian
2005-Nov-19 18:28 UTC
[Xen-users] correct procedure for reporting kernel problems?
I''ve had domU''s hickup a few times with latest unstable, and I
guess this can
be expected. Is there a procedure in place to report these problems?
For exampe:
Unable to handle kernel paging request at virtual address c12b46c0
printing eip: cpanel cpanel.mydomain
c02555f7
*pde = ma 7e9fc067 pa 00002067
*pte = ma 00000000 pa 55555000
Oops: 0002 [#1]
PREEMPT SMP
Modules linked in:
CPU: 0
EIP: 0061:[<c02555f7>] Not tainted VLI
EFLAGS: 00010212 (2.6.12.6-xenU)
EIP is at netif_poll+0x337/0x760
eax: c12b46c0 ebx: c11ba580 ecx: c12b405e edx: c12b46c0
esi: c033fecc edi: c12b4000 ebp: c11ba580 esp: c033fe9c
ds: 007b es: 007b ss: 0069
Process swapper (pid: 0, threadinfo=c033e000 task=c0302200)
Stack: ffffffff 00000119 c010cc1c 00000001 00000000 00000001 00000040 00000001
00000001 000016af 000016af c127a240 c033fecc c033fecc 00000000 00000001
00000000 c127a2bc c127a240 00000000 c127a104 c127a000 c033e000 c033e000
Call Trace:
[<c010cc1c>] timer_interrupt+0x1ac/0x2b0
[<c026288d>] net_rx_action+0x14d/0x230
[<c012599a>] __do_softirq+0xaa/0x160
[<c0125ad5>] do_softirq+0x85/0xa0 1,1
All
[<c0125be5>] irq_exit+0x45/0x50
[<c010eb52>] do_IRQ+0x22/0x30
[<c0104a10>] evtchn_do_upcall+0x90/0x100
[<c010a310>] hypervisor_callback+0x2c/0x34
[<c0107b86>] xen_idle+0x56/0xd0
[<c0107c63>] cpu_idle+0x63/0xc0
[<c03409e8>] start_kernel+0x1b8/0x210
[<c0340320>] unknown_bootoption+0x0/0x240
Code: 8b 95 94 00 00 00 39 d1 0f 87 b1 01 00 00 8b 85 8c 00 00 00 8b bd 88 00
00 00 29 f8 83 f8 0f 0f 8e 9a 01 00 00 8b 83 94 00 00 00 <c7> 00 01 00 00
00
8b 83 94 00 00 00 c7 40 04 00 00 00 00 8b 83
<0>Kernel panic - not syncing: Fatal exception in interrupt
Kind Regards,
--
Ian P. Christian ~ http://pookey.co.uk
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Charles Duffy
2005-Nov-19 19:53 UTC
[Xen-users] Re: correct procedure for reporting kernel problems?
Ian P. Christian wrote:> I''ve had domU''s hickup a few times with latest unstable, and I guess this can > be expected. Is there a procedure in place to report these problems?This mailing list isn''t an entirely bad place to ask about issues (though there''s a bugzilla as well). One request -- please specify a changeset number instead of just saying "the latest unstable". I''ve seen an issue much like you''re reporting, but it was fixed for me some time ago. Knowing exactly how current the "latest unstable" you''re using is is useful in such cases. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ian P. Christian
2005-Nov-19 20:32 UTC
Re: [Xen-users] Re: correct procedure for reporting kernel problems?
On Saturday 19 November 2005 19:53, Charles Duffy wrote:> One request -- please specify a changeset number instead of just saying > "the latest unstable". I''ve seen an issue much like you''re reporting, > but it was fixed for me some time ago. Knowing exactly how current the > "latest unstable" you''re using is is useful in such cases.appologies, I''m not at all familiar with the versioning control program, how do I tell? ''hg status'' seemed like the most likely command in the man page, but that does''t show me anyhting of help. I checked it out earlier today. -- Ian P. Christian ~ http://pookey.co.uk _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ian Pratt
2005-Nov-19 20:42 UTC
RE: [Xen-users] correct procedure for reporting kernel problems?
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Ian P. Christian > Sent: 19 November 2005 18:28 > To: xen-users@lists.xensource.com > Subject: [Xen-users] correct procedure for reporting kernel problems? > > I''ve had domU''s hickup a few times with latest unstable, and > I guess this can > be expected. Is there a procedure in place to report these problems?This issue is already logged on bugzilla, but we''re struggling to reroduce it. It would be good if your bug report could include: * What xen/linux version you''re using (e.g. output of xm info) * what were you doing on the machine at the time? What domains were running? * have you modified the kernel config? (or otherwise modified the source) * please post the output of ''xm dmesg'' as well as the oops message * what kind of machine is this? how many CPUs, how much memory? Thanks, Ian> Unable to handle kernel paging request at virtual address c12b46c0 > printing eip: cpanel cpanel.mydomain > c02555f7 > *pde = ma 7e9fc067 pa 00002067 > *pte = ma 00000000 pa 55555000 > Oops: 0002 [#1] > PREEMPT SMP > Modules linked in: > CPU: 0 > EIP: 0061:[<c02555f7>] Not tainted VLI > EFLAGS: 00010212 (2.6.12.6-xenU) > EIP is at netif_poll+0x337/0x760 > eax: c12b46c0 ebx: c11ba580 ecx: c12b405e edx: c12b46c0 > esi: c033fecc edi: c12b4000 ebp: c11ba580 esp: c033fe9c > ds: 007b es: 007b ss: 0069 > Process swapper (pid: 0, threadinfo=c033e000 task=c0302200) > Stack: ffffffff 00000119 c010cc1c 00000001 00000000 00000001 > 00000040 00000001 > 00000001 000016af 000016af c127a240 c033fecc c033fecc > 00000000 00000001 > 00000000 c127a2bc c127a240 00000000 c127a104 c127a000 > c033e000 c033e000 > Call Trace: > [<c010cc1c>] timer_interrupt+0x1ac/0x2b0 > [<c026288d>] net_rx_action+0x14d/0x230 > [<c012599a>] __do_softirq+0xaa/0x160 > [<c0125ad5>] do_softirq+0x85/0xa0 > 1,1 > All > [<c0125be5>] irq_exit+0x45/0x50 > [<c010eb52>] do_IRQ+0x22/0x30 > [<c0104a10>] evtchn_do_upcall+0x90/0x100 > [<c010a310>] hypervisor_callback+0x2c/0x34 > [<c0107b86>] xen_idle+0x56/0xd0 > [<c0107c63>] cpu_idle+0x63/0xc0 > [<c03409e8>] start_kernel+0x1b8/0x210 > [<c0340320>] unknown_bootoption+0x0/0x240 > Code: 8b 95 94 00 00 00 39 d1 0f 87 b1 01 00 00 8b 85 8c 00 > 00 00 8b bd 88 00 > 00 00 29 f8 83 f8 0f 0f 8e 9a 01 00 00 8b 83 94 00 00 00 <c7> > 00 01 00 00 00 > 8b 83 94 00 00 00 c7 40 04 00 00 00 00 8b 83 > <0>Kernel panic - not syncing: Fatal exception in interrupt > > Kind Regards, > > -- > Ian P. Christian ~ http://pookey.co.uk >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Charles Duffy
2005-Nov-19 20:45 UTC
Re: [Xen-users] Re: correct procedure for reporting kernel problems?
Ian P. Christian wrote:> On Saturday 19 November 2005 19:53, Charles Duffy wrote: > >> One request -- please specify a changeset number instead of just saying >> "the latest unstable". I''ve seen an issue much like you''re reporting, >> but it was fixed for me some time ago. Knowing exactly how current the >> "latest unstable" you''re using is is useful in such cases. >> > > appologies, I''m not at all familiar with the versioning control program, how > do I tell? ''hg status'' seemed like the most likely command in the man page, > but that does''t show me anyhting of help. >"hg identify" will show precisely the changeset you''re using (though by its hash value rather than by number). The output of "hg log" will start with the most recent known changeset, and by searching for the hash from "hg identify" in the "hg log" output you can determine exactly what you''re running. So long as you did an update after your pull, you should generally be on the first changeset in the "hg log" output. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ian P. Christian
2005-Nov-19 21:13 UTC
Re: [Xen-users] correct procedure for reporting kernel problems?
On Saturday 19 November 2005 20:42, Ian Pratt wrote:> This issue is already logged on bugzilla, but we''re struggling to > reroduce it.I hope this will be of help.. sorry for the missing details though.> It would be good if your bug report could include: > * What xen/linux version you''re using (e.g. output of xm info)I''m using gentoo , setup as described in http://gentoo-wiki.com/HOWTO_Xen_and_Gentoo. I am not using the gentoo ebuilds for Xen though. # xm info system : Linux host : bb3 release : 2.6.12.6-xen0 version : #3 SMP Sat Nov 19 16:41:08 GMT 2005 machine : i686 nr_cpus : 4 nr_nodes : 1 sockets_per_node : 2 cores_per_socket : 1 threads_per_core : 2 cpu_mhz : 2800 hw_caps : bfebfbff:20100000:00000000:00000080:0000641d memory : 2047 free_memory : 1667 xen_major : 3 xen_minor : 0 xen_extra : -devel xen_caps : xen-3.0-x86_32 platform_params : virt_start=0xfc000000 xen_changeset : Sat Nov 19 09:37:14 2005 +0100 7901:aad88a902892 cc_compiler : gcc version 3.4.4 (Gentoo 3.4.4-r1, ssp-3.4.4-1.0, pie-8.7.8) cc_compile_by : root cc_compile_domain : (none) cc_compile_date : Sat Nov 19 16:36:29 GMT 2005> * what were you doing on the machine at the time? What domains were > running?I did a ''cat /etc/hosts'' in one of the domains. There was a second domain running - both crashed at the same time (atleast, I think, when I switched to the second one it had also crashed).> * have you modified the kernel config? (or otherwise modified the > source)I have. I added support for my SATA RAID controller, and my intel gigabit ethernet card. Set the CPU type to Xeon too. Unfortunatly I managed to trash the .config, and didn''t enable /proc/config support, so the exact kernel config is lost. SMP would have been enabled, the HT schedular would have been disabled... Of the top of my head I can''t think of much more I would have changed.> * what kind of machine is this? how many CPUs, how much memory?It''s a Dell 1425, Dual Xeon 2.8 with Hyperthreading. 2 gig of RAM, 3ware 9xxx SATA controller.> * please post the output of ''xm dmesg'' as well as the oops messageThe opps was in the previous message (anything not there I''m afarid is now lost). # xm dmesg __ __ _____ ___ _ _ \ \/ /___ _ __ |___ / / _ \ __| | _____ _____| | \ // _ \ ''_ \ |_ \| | | |__ / _` |/ _ \ \ / / _ \ | / \ __/ | | | ___) | |_| |__| (_| | __/\ V / __/ | /_/\_\___|_| |_| |____(_)___/ \__,_|\___| \_/ \___|_| http://www.cl.cam.ac.uk/netos/xen University of Cambridge Computer Laboratory Xen version 3.0-devel (root@) (gcc version 3.4.4 (Gentoo 3.4.4-r1, ssp-3.4.4-1.0, pie-8.7.8)) Sat Nov 19 16:36:29 GMT 2005 Latest ChangeSet: Sat Nov 19 09:37:14 2005 +0100 7901:aad88a902892 (XEN) Physical RAM map: (XEN) 0000000000000000 - 00000000000a0000 (usable) (XEN) 0000000000100000 - 000000007ffc0000 (usable) (XEN) 000000007ffc0000 - 000000007ffcfc00 (ACPI data) (XEN) 000000007ffcfc00 - 000000007ffff000 (reserved) (XEN) 00000000e0000000 - 00000000fec90000 (reserved) (XEN) 00000000fed00000 - 00000000fed00400 (reserved) (XEN) 00000000fee00000 - 00000000fee10000 (reserved) (XEN) 00000000ffb00000 - 0000000100000000 (reserved) (XEN) System RAM: 2047MB (2096512kB) (XEN) Xen heap: 10MB (10616kB) (XEN) PAE disabled. (XEN) found SMP MP-table at 000fe710 (XEN) DMI 2.3 present. (XEN) Using APIC driver default (XEN) ACPI: RSDP (v000 DELL ) @ 0x000fd650 (XEN) ACPI: RSDT (v001 DELL PESC1425 0x00000001 MSFT 0x0100000a) @ 0x000fd664 (XEN) ACPI: FADT (v001 DELL PESC1425 0x00000001 MSFT 0x0100000a) @ 0x000fd6b0 (XEN) ACPI: MADT (v001 DELL PESC1425 0x00000001 MSFT 0x0100000a) @ 0x000fd724 (XEN) ACPI: SPCR (v001 DELL PESC1425 0x00000001 MSFT 0x0100000a) @ 0x000fd7c0 (XEN) ACPI: HPET (v001 DELL PESC1425 0x00000001 MSFT 0x0100000a) @ 0x000fd810 (XEN) ACPI: MCFG (v001 DELL PESC1425 0x00000001 MSFT 0x0100000a) @ 0x000fd848 (XEN) ACPI: DSDT (v001 DELL PESC1425 0x00000001 MSFT 0x0100000e) @ 0x00000000 (XEN) ACPI: Local APIC address 0xfee00000 (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) (XEN) Processor #0 15:4 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x06] enabled) (XEN) Processor #6 15:4 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled) (XEN) Processor #1 15:4 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] enabled) (XEN) Processor #7 15:4 APIC version 20 (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) (XEN) ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0]) (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 (XEN) ACPI: IOAPIC (id[0x09] address[0xfec80000] gsi_base[32]) (XEN) IOAPIC[1]: apic_id 9, version 32, address 0xfec80000, GSI 32-55 (XEN) ACPI: IOAPIC (id[0x0a] address[0xfec80800] gsi_base[64]) (XEN) IOAPIC[2]: apic_id 10, version 32, address 0xfec80800, GSI 64-87 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) (XEN) ACPI: IRQ0 used by override. (XEN) ACPI: IRQ2 used by override. (XEN) ACPI: IRQ9 used by override. (XEN) Enabling APIC mode: Flat. Using 3 I/O APICs (XEN) ACPI: HPET id: 0xffffffff base: 0xfed00000 (XEN) Using ACPI (MADT) for SMP configuration information (XEN) Initializing CPU#0 (XEN) Detected 2800.217 MHz processor. (XEN) Using scheduler: Simple EDF Scheduler (sedf) (XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K (XEN) CPU: L2 cache: 1024K (XEN) CPU: Physical Processor ID: 0 (XEN) CPU0: Intel(R) Xeon(TM) CPU 2.80GHz stepping 01 (XEN) Booting processor 1/1 eip 90000 (XEN) Initializing CPU#1 (XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K (XEN) CPU: L2 cache: 1024K (XEN) CPU: Physical Processor ID: 0 (XEN) CPU1: Intel(R) Xeon(TM) CPU 2.80GHz stepping 01 (XEN) Booting processor 2/6 eip 90000 (XEN) Initializing CPU#2 (XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K (XEN) CPU: L2 cache: 1024K (XEN) CPU: Physical Processor ID: 3 (XEN) CPU2: Intel(R) Xeon(TM) CPU 2.80GHz stepping 01 (XEN) Booting processor 3/7 eip 90000 (XEN) Initializing CPU#3 (XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K (XEN) CPU: L2 cache: 1024K (XEN) CPU: Physical Processor ID: 3 (XEN) CPU3: Intel(R) Xeon(TM) CPU 2.80GHz stepping 01 (XEN) Total of 4 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) ..TIMER: vector=0x31 pin1=2 pin2=-1 (XEN) checking TSC synchronization across 4 CPUs: passed. (XEN) Platform timer is 14.318MHz HPET (XEN) Brought up 4 CPUs (XEN) mtrr: v2.0 (20020519) (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen-ELF header found: ''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xC0000000,PAE=no,LOADER=generic'' (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 7f000000->7f800000 (30720 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: c0100000->c043acd0 (XEN) Init. ramdisk: c043b000->c043b000 (XEN) Phys-Mach map: c043b000->c045b000 (XEN) Start info: c045b000->c045c000 (XEN) Page tables: c045c000->c045f000 (XEN) Boot stack: c045f000->c0460000 (XEN) TOTAL: c0000000->c0800000 (XEN) ENTRY ADDRESS: c0100000 (XEN) Scrubbing Free RAM: .....................done. (XEN) Xen trace buffers: disabled (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen). -- Ian P. Christian ~ http://pookey.co.uk _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ian Pratt
2005-Nov-19 21:13 UTC
RE: [Xen-users] Re: correct procedure for reporting kernel problems?
> > appologies, I''m not at all familiar with the versioning control > > program, how do I tell? ''hg status'' seemed like the most likely > > command in the man page, but that does''t show me anyhting of help. > > > "hg identify" will show precisely the changeset you''re using > (though by its hash value rather than by number). The output > of "hg log" will start with the most recent known changeset, > and by searching for the hash from "hg identify" in the "hg > log" output you can determine exactly what you''re running. So > long as you did an update after your pull, you should > generally be on the first changeset in the "hg log" output.''xm info'' will give us the information too. Ian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users