[Xenomai-help] Kernel panic on boot with 2.5.6

[Xenomai-help] Kernel panic on boot with 2.5.6

[VEYSSIERE Nicolas]

[-- Attachment #1: Type: text/plain, Size: 1626 bytes --]

Hello,

I succesfully build a 2.6.38.8 kernel with the latest adeos patch and Xenomai 2.5.6, but it kernel panic :

[    1.195878] Pid: 1, comm: swapper Tainted: G         D W     2.6.38-xenomai-r6 #1
[    1.196878] Call Trace:
[    1.196878]  [<c14ae979>] ? panic+0x50/0x145
[    1.197878]  [<c1031250>] ? do_exit+0x5c/0x6be
[    1.198877]  [<c14b071c>] ? _raw_spin_unlock_irqrestore+0xe/0x10
[    1.199877]  [<c102e487>] ? kmsg_dump+0x35/0xb5
[    1.200877]  [<c14b1b32>] ? oops_end+0xa0/0xa8
[    1.201877]  [<c101b448>] ? no_context+0x110/0x11a
[    1.201877]  [<c101b570>] ? __bad_area_nosemaphore+0x11e/0x126
[    1.202877]  [<c101b585>] ? bad_area_nosemaphore+0xd/0x10
[    1.203877]  [<c14b32c1>] ? do_page_fault+0x1c0/0x36b
[    1.203877]  [<c10144da>] ? __ipipe_handle_exception+0x24f/0x288
[    1.203877]  [<c14b11af>] ? error_code+0x5f/0x70
[    1.204876]  [<c10736fe>] ? __xirq_end+0x12/0x2e
[    1.205876]  [<c107472a>] ? ipipe_register_domain+0x1d8/0x1e4
[    1.205876]  [<c108e46e>] ? rthal_init+0x17d/0x20c
[    1.206876]  [<c139e098>] ? rthal_domain_entry+0x0/0x39
[    1.207876]  [<c1706c3d>] ? __xeno_sys_init+0x41/0x261
[    1.208876]  [<c108a4a2>] ? pmu_dev_alloc+0x64/0x7d
[    1.208876]  [<c1001076>] ? do_one_initcall+0x71/0x133
[    1.209876]  [<c1706bfc>] ? __xeno_sys_init+0x0/0x261
[    1.210876]  [<c16f4382>] ? kernel_init+0x128/0x1a4
[    1.211875]  [<c16f425a>] ? kernel_init+0x0/0x1a4
[    1.212875]  [<c1002d06>] ? kernel_thread_helper+0x6/0x10


Could it be a problem with the fact that this system is a virtual box VM ?


Thanks.

--
Nicolas VEYSSIERE

[-- Attachment #2: Type: text/html, Size: 6705 bytes --]

Re: [Xenomai-help] Kernel panic on boot with 2.5.6

[Gilles Chanteperdrix]

On 06/22/2011 12:44 PM, VEYSSIERE Nicolas wrote:
> Hello,
> 
> I succesfully build a 2.6.38.8 kernel with the latest adeos patch and Xenomai 2.5.6, but it kernel panic :
> 
> [    1.195878] Pid: 1, comm: swapper Tainted: G         D W     2.6.38-xenomai-r6 #1
> [    1.196878] Call Trace:
> [    1.196878]  [<c14ae979>] ? panic+0x50/0x145
> [    1.197878]  [<c1031250>] ? do_exit+0x5c/0x6be
> [    1.198877]  [<c14b071c>] ? _raw_spin_unlock_irqrestore+0xe/0x10
> [    1.199877]  [<c102e487>] ? kmsg_dump+0x35/0xb5
> [    1.200877]  [<c14b1b32>] ? oops_end+0xa0/0xa8
> [    1.201877]  [<c101b448>] ? no_context+0x110/0x11a
> [    1.201877]  [<c101b570>] ? __bad_area_nosemaphore+0x11e/0x126
> [    1.202877]  [<c101b585>] ? bad_area_nosemaphore+0xd/0x10
> [    1.203877]  [<c14b32c1>] ? do_page_fault+0x1c0/0x36b
> [    1.203877]  [<c10144da>] ? __ipipe_handle_exception+0x24f/0x288
> [    1.203877]  [<c14b11af>] ? error_code+0x5f/0x70
> [    1.204876]  [<c10736fe>] ? __xirq_end+0x12/0x2e
> [    1.205876]  [<c107472a>] ? ipipe_register_domain+0x1d8/0x1e4
> [    1.205876]  [<c108e46e>] ? rthal_init+0x17d/0x20c
> [    1.206876]  [<c139e098>] ? rthal_domain_entry+0x0/0x39
> [    1.207876]  [<c1706c3d>] ? __xeno_sys_init+0x41/0x261
> [    1.208876]  [<c108a4a2>] ? pmu_dev_alloc+0x64/0x7d
> [    1.208876]  [<c1001076>] ? do_one_initcall+0x71/0x133
> [    1.209876]  [<c1706bfc>] ? __xeno_sys_init+0x0/0x261
> [    1.210876]  [<c16f4382>] ? kernel_init+0x128/0x1a4
> [    1.211875]  [<c16f425a>] ? kernel_init+0x0/0x1a4
> [    1.212875]  [<c1002d06>] ? kernel_thread_helper+0x6/0x10
> 
> 
> Could it be a problem with the fact that this system is a virtual box VM ?

It is hard to tell, we do not have the error message, which should be
right above this stack trace. Please post the full logs, as there may be
other interesting details in the logs.

> 
> 
> Thanks.
> 
> --
> Nicolas VEYSSIERE
> 
> 
> 
> 
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help


-- 
                                                                Gilles.

Re: [Xenomai-help] Kernel panic on boot with 2.5.6

[VEYSSIERE Nicolas]

[-- Attachment #1: Type: text/plain, Size: 2646 bytes --]

Ok, I managed to have a few more trace, if you want more, I will have to enable framebuffer.

Because it is quite long, I will not copy it, I will send a screenshot.



-- 
Nicolas VEYSSIERE


-----Message d'origine-----
De : Gilles Chanteperdrix [mailto:gilles.chanteperdrix@xenomai.org] 
Envoyé : mercredi 22 juin 2011 12:58
À : VEYSSIERE Nicolas
Cc : xenomai-help@gna.org
Objet : Re: [Xenomai-help] Kernel panic on boot with 2.5.6

On 06/22/2011 12:44 PM, VEYSSIERE Nicolas wrote:
> Hello,
> 
> I succesfully build a 2.6.38.8 kernel with the latest adeos patch and Xenomai 2.5.6, but it kernel panic :
> 
> [    1.195878] Pid: 1, comm: swapper Tainted: G         D W     2.6.38-xenomai-r6 #1
> [    1.196878] Call Trace:
> [    1.196878]  [<c14ae979>] ? panic+0x50/0x145
> [    1.197878]  [<c1031250>] ? do_exit+0x5c/0x6be
> [    1.198877]  [<c14b071c>] ? _raw_spin_unlock_irqrestore+0xe/0x10
> [    1.199877]  [<c102e487>] ? kmsg_dump+0x35/0xb5
> [    1.200877]  [<c14b1b32>] ? oops_end+0xa0/0xa8
> [    1.201877]  [<c101b448>] ? no_context+0x110/0x11a
> [    1.201877]  [<c101b570>] ? __bad_area_nosemaphore+0x11e/0x126
> [    1.202877]  [<c101b585>] ? bad_area_nosemaphore+0xd/0x10
> [    1.203877]  [<c14b32c1>] ? do_page_fault+0x1c0/0x36b
> [    1.203877]  [<c10144da>] ? __ipipe_handle_exception+0x24f/0x288
> [    1.203877]  [<c14b11af>] ? error_code+0x5f/0x70
> [    1.204876]  [<c10736fe>] ? __xirq_end+0x12/0x2e
> [    1.205876]  [<c107472a>] ? ipipe_register_domain+0x1d8/0x1e4
> [    1.205876]  [<c108e46e>] ? rthal_init+0x17d/0x20c
> [    1.206876]  [<c139e098>] ? rthal_domain_entry+0x0/0x39
> [    1.207876]  [<c1706c3d>] ? __xeno_sys_init+0x41/0x261
> [    1.208876]  [<c108a4a2>] ? pmu_dev_alloc+0x64/0x7d
> [    1.208876]  [<c1001076>] ? do_one_initcall+0x71/0x133
> [    1.209876]  [<c1706bfc>] ? __xeno_sys_init+0x0/0x261
> [    1.210876]  [<c16f4382>] ? kernel_init+0x128/0x1a4
> [    1.211875]  [<c16f425a>] ? kernel_init+0x0/0x1a4
> [    1.212875]  [<c1002d06>] ? kernel_thread_helper+0x6/0x10
> 
> 
> Could it be a problem with the fact that this system is a virtual box VM ?

It is hard to tell, we do not have the error message, which should be
right above this stack trace. Please post the full logs, as there may be
other interesting details in the logs.

> 
> 
> Thanks.
> 
> --
> Nicolas VEYSSIERE
> 
> 
> 
> 
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@gna.org
> https://mail.gna.org/listinfo/xenomai-help


-- 
                                                                Gilles.

[-- Attachment #2: screenshot.80.png --]
[-- Type: image/png, Size: 12972 bytes --]

Re: [Xenomai-help] Kernel panic on boot with 2.5.6

[Gilles Chanteperdrix]

On 06/22/2011 01:10 PM, VEYSSIERE Nicolas wrote:
> Ok, I managed to have a few more trace, if you want more, I will have to enable framebuffer.
> 
> Because it is quite long, I will not copy it, I will send a screenshot.

Full kernel logs please, use serial port or netconsole to have it.


-- 
                                                                Gilles.

Re: [Xenomai-help] Kernel panic on boot with 2.5.6

[VEYSSIERE Nicolas]

[-- Attachment #1: Type: text/plain, Size: 721 bytes --]

First time for me here.

The log are in the attachement.

-- 
Nicolas VEYSSIERE

-----Message d'origine-----
De : Gilles Chanteperdrix [mailto:gilles.chanteperdrix@xenomai.org] 
Envoyé : mercredi 22 juin 2011 13:13
À : VEYSSIERE Nicolas
Cc : xenomai-help@gna.org
Objet : Re: [Xenomai-help] Kernel panic on boot with 2.5.6

On 06/22/2011 01:10 PM, VEYSSIERE Nicolas wrote:
> Ok, I managed to have a few more trace, if you want more, I will have to enable framebuffer.
> 
> Because it is quite long, I will not copy it, I will send a screenshot.

Full kernel logs please, use serial port or netconsole to have it.


-- 
                                                                Gilles.

[-- Attachment #2: serial.log --]
[-- Type: application/octet-stream, Size: 12654 bytes --]

[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.38-xenomai-r6 (root@xenomai) (gcc version 4.4.5 (Gentoo 4.4.5 p1.2, pie-0.4.5) ) #1 SMP Wed Jun 22 10:07:35 CEST 2011
[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[    0.000000]  BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[    0.000000]  BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[    0.000000]  BIOS-e820: 0000000000100000 - 000000003fff0000 (usable)
[    0.000000]  BIOS-e820: 000000003fff0000 - 0000000040000000 (ACPI data)
[    0.000000]  BIOS-e820: 00000000fffc0000 - 0000000100000000 (reserved)
[    0.000000] Notice: NX (Execute Disable) protection missing in CPU!
[    0.000000] DMI 2.5 present.
[    0.000000] last_pfn = 0x3fff0 max_arch_pfn = 0x100000
[    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[    0.000000] CPU MTRRs all blank - virtualized system.
[    0.000000] init_memory_mapping: 0000000000000000-00000000377fe000
[    0.000000] 135MB HIGHMEM available.
[    0.000000] 887MB LOWMEM available.
[    0.000000]   mapped low ram: 0 - 377fe000
[    0.000000]   low ram: 0 - 377fe000
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA      0x00000010 -> 0x00001000
[    0.000000]   Normal   0x00001000 -> 0x000377fe
[    0.000000]   HighMem  0x000377fe -> 0x0003fff0
[    0.000000] Movable zone start PFN for each node
[    0.000000] early_node_map[2] active PFN ranges
[    0.000000]     0: 0x00000010 -> 0x0000009f
[    0.000000]     0: 0x00000100 -> 0x0003fff0
[    0.000000] Using APIC driver default
[    0.000000] SMP: Allowing 1 CPUs, 0 hotplug CPUs
[    0.000000] Found and enabled local APIC!
[    0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
[    0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000
[    0.000000] PM: Registered nosave memory: 00000000000f0000 - 0000000000100000
[    0.000000] Allocating PCI resources starting at 40000000 (gap: 40000000:bffc0000)
[    0.000000] setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:1 nr_node_ids:1
[    0.000000] PERCPU: Embedded 22 pages/cpu @f6800000 s66688 r0 d23424 u4194304
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 259967
[    0.000000] Kernel command line: root=/dev/sda3 console=tty0 console=ttyS0,115200
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Initializing CPU#0
[    0.000000] Initializing HighMem for node 0 (000377fe:0003fff0)
[    0.000000] Memory: 1029880k/1048512k available (4825k kernel code, 18180k reserved, 2293k data, 412k init, 139208k highmem)
[    0.000000] virtual kernel memory layout:
[    0.000000]     fixmap  : 0xfff16000 - 0xfffff000   ( 932 kB)
[    0.000000]     pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
[    0.000000]     vmalloc : 0xf7ffe000 - 0xff7fe000   ( 120 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xf77fe000   ( 887 MB)
[    0.000000]       .init : 0xc16f4000 - 0xc175b000   ( 412 kB)
[    0.000000]       .data : 0xc14b67b4 - 0xc16f3f80   (2293 kB)
[    0.000000]       .text : 0xc1000000 - 0xc14b67b4   (4825 kB)
[    0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok.
[    0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] 	RCU-based detection of stalled CPUs is disabled.
[    0.000000] NR_IRQS:2304 nr_irqs:256 16
[    0.000000] I-pipe 2.10-00: pipeline enabled.
[    0.000000] Console: colour VGA+ 80x25
[    0.000000] console [tty0] enabled
[    0.000000] console [ttyS0] enabled
[    0.000000] Fast TSC calibration failed
[    0.000000] TSC: Unable to calibrate against PIT
[    0.000000] TSC: No reference (HPET/PMTIMER) available
[    0.000000] Marking TSC unstable due to could not calculate TSC khz
[    0.013998] Calibrating delay loop... 2605.05 BogoMIPS (lpj=1302528)
[    0.037997] pid_max: default: 32768 minimum: 301
[    0.039997] Security Framework initialized
[    0.040997] SELinux:  Initializing.
[    0.042996] Mount-cache hash table entries: 512
[    0.048996] Initializing cgroup subsys ns
[    0.049996] ns_cgroup deprecated: consider using the 'clone_children' flag without the ns_cgroup.
[    0.050995] Initializing cgroup subsys cpuacct
[    0.051995] Initializing cgroup subsys freezer
[    0.052995] mce: CPU supports 0 MCE banks
[    0.068993] SMP alternatives: switching to UP code
[    0.375952] Freeing SMP alternatives: 24k freed
[    0.379951] weird, boot CPU (#0) not listed by the BIOS.
[    0.380951] SMP motherboard not detected.
[    0.381951] Enabling APIC mode:  Flat.  Using 0 I/O APICs
[    0.383950] ------------[ cut here ]------------
[    0.384950] WARNING: at arch/x86/kernel/apic/apic.c:1289 setup_local_APIC+0x1e1/0x2cb()
[    0.385950] Hardware name: VirtualBox
[    0.386950] Modules linked in:
[    0.389949] Pid: 1, comm: swapper Not tainted 2.6.38-xenomai-r6 #1
[    0.390949] Call Trace:
[    0.391949]  [<c102e201>] ? warn_slowpath_common+0x65/0x7a
[    0.392949]  [<c14acc61>] ? setup_local_APIC+0x1e1/0x2cb
[    0.393949]  [<c102e225>] ? warn_slowpath_null+0xf/0x13
[    0.394949]  [<c14acc61>] ? setup_local_APIC+0x1e1/0x2cb
[    0.395949]  [<c16fe8dd>] ? APIC_init_uniprocessor+0xa2/0xf9
[    0.396948]  [<c16fd049>] ? native_smp_prepare_cpus+0x1d2/0x36c
[    0.397948]  [<c16f42bb>] ? kernel_init+0x61/0x1a4
[    0.398948]  [<c16f425a>] ? kernel_init+0x0/0x1a4
[    0.399948]  [<c1002d06>] ? kernel_thread_helper+0x6/0x10
[    0.400948] ---[ end trace 4eaa2a86a8e2da22 ]---
[    0.495933] APIC timer disabled due to verification failure
[    0.497933] SMP disabled
[    0.498933] Performance Events: unsupported p6 CPU model 15 no PMU driver, software events only.
[    0.504932] Brought up 1 CPUs
[    0.505932] Total of 1 processors activated (2605.05 BogoMIPS).
[    0.507931] devtmpfs: initialized
[    0.509931] kworker/u:0 used greatest stack depth: 7128 bytes left
[    0.517930] Time: 11:28:05  Date: 06/22/11
[    0.518930] NET: Registered protocol family 16
[    0.556924] PCI: PCI BIOS revision 2.10 entry at 0xfc090, last bus=0
[    0.557924] PCI: Using configuration type 1 for base access
[    0.581920] kworker/u:0 used greatest stack depth: 6872 bytes left
[    0.704901] bio: create slab <bio-0> at 0
[    0.709901] vgaarb: loaded
[    0.713900] SCSI subsystem initialized
[    0.721899] usbcore: registered new interface driver usbfs
[    0.724898] usbcore: registered new interface driver hub
[    0.726898] usbcore: registered new device driver usb
[    0.732897] Advanced Linux Sound Architecture Driver Version 1.0.23.
[    0.733897] PCI: Probing PCI hardware
[    0.827882] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
[    0.835881] pci 0000:00:01.0: PIIX/ICH IRQ router [8086:7000]
[    0.848879] cfg80211: Calling CRDA to update world regulatory domain
[    0.851879] NetLabel: Initializing
[    0.852879] NetLabel:  domain hash size = 128
[    0.853878] NetLabel:  protocols = UNLABELED CIPSOv4
[    0.854878] NetLabel:  unlabeled traffic allowed by default
[    0.857878] Switching to clocksource pit
[    1.144894] NET: Registered protocol family 2
[    1.146898] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[    1.150776] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[    1.157085] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[    1.159006] TCP: Hash tables configured (established 131072 bind 65536)
[    1.160436] TCP reno registered
[    1.161190] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    1.162057] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    1.163909] NET: Registered protocol family 1
[    1.166911] RPC: Registered udp transport module.
[    1.168162] RPC: Registered tcp transport module.
[    1.169474] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    1.171084] pci 0000:00:00.0: Limiting direct PCI/PCI transfers
[    1.172143] pci 0000:00:01.0: Activating ISA DMA hang workarounds
[    1.175887] platform rtc_cmos: registered platform RTC device (no PNP device found)
[    1.184906] microcode: CPU0 sig=0x6fd, pf=0x1, revision=0x0
[    1.185925] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
[    1.208896] audit: initializing netlink socket (disabled)
[    1.210042] type=2000 audit(1308742085.209:1): initialized
[    1.245230] I-pipe: Domain Xenomai registered.
[    1.246230] Xenomai: hal/i386 started.
[    1.246230] BUG: unable to handle kernel NULL pointer dereference at 00000920
[    1.246230] IP: [<c10736fe>] __xirq_end+0x12/0x2e
[    1.246230] *pde = 00000000 
[    1.246230] Oops: 0000 [#1] SMP 
[    1.246230] last sysfs file: 
[    1.246230] Modules linked in:
[    1.246230] 
[    1.246230] Pid: 1, comm: swapper Tainted: G        W   2.6.38-xenomai-r6 #1 innotek GmbH VirtualBox
[    1.246230] EIP: 0060:[<c10736fe>] EFLAGS: 00010093 CPU: 0
[    1.246230] EIP is at __xirq_end+0x12/0x2e
[    1.246230] EAX: f6448000 EBX: 00000920 ECX: f6448000 EDX: 00000000
[    1.246230] ESI: c1806940 EDI: 00000924 EBP: f6445f54 ESP: f6445f1c
[    1.246230]  DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0069
[    1.246230] Process swapper (pid: 1, ti=f6444000 task=f6448000 task.ti=f6444000)
[    1.246230] I-pipe domain Linux
[    1.246230] Stack:
[    1.246230]  ffffff9c 00010246 c1806940 f6445f40 c1756f84 c174d1d4 00000920 c1806944
[    1.246230]  f68031d8 f68031dc f68031e8 00000286 f6445f74 c1756f84 f6445f6c c107472a
[    1.246230]  00000282 f6445f74 00000001 00000008 f6445f90 c108e46e 58454e4f c15cefab
[    1.246230] Call Trace:
[    1.246230]  [<c107472a>] ipipe_register_domain+0x1d8/0x1e4
[    1.246230]  [<c108e46e>] rthal_init+0x17d/0x20c
[    1.246230]  [<c139e098>] ? rthal_domain_entry+0x0/0x39
[    1.246230]  [<c1706c3d>] __xeno_sys_init+0x41/0x261
[    1.246230]  [<c108a4a2>] ? pmu_dev_alloc+0x64/0x7d
[    1.246230]  [<c1001076>] do_one_initcall+0x71/0x133
[    1.246230]  [<c1706bfc>] ? __xeno_sys_init+0x0/0x261
[    1.246230]  [<c16f4382>] kernel_init+0x128/0x1a4
[    1.246230]  [<c16f425a>] ? kernel_init+0x0/0x1a4
[    1.246230]  [<c1002d06>] kernel_thread_helper+0x6/0x10
[    1.246230] Code: 07 c1 50 0f a8 0f a0 06 1e 50 55 57 56 52 51 53 89 f8 ff d2 e9 64 d2 43 00 e9 47 6a 9c 3d 8b 5d d8 64 8b 15 04 c0 74 c1 8d 04 0a <8b> 14 1a 69 12 6c 27 00 00 01 d0 e9 9e fe ff ff 0f ba 30 00 83 
[    1.246230] EIP: [<c10736fe>] __xirq_end+0x12/0x2e SS:ESP 0069:f6445f1c
[    1.246230] CR2: 0000000000000920
[    1.246230] ---[ end trace 4eaa2a86a8e2da23 ]---
[    1.247230] swapper used greatest stack depth: 6540 bytes left
[    1.248229] Kernel panic - not syncing: Attempted to kill init!
[    1.249229] Pid: 1, comm: swapper Tainted: G      D W   2.6.38-xenomai-r6 #1
[    1.250229] Call Trace:
[    1.251229]  [<c14ae979>] ? panic+0x50/0x145
[    1.252229]  [<c1031250>] ? do_exit+0x5c/0x6be
[    1.253229]  [<c14b071c>] ? _raw_spin_unlock_irqrestore+0xe/0x10
[    1.254229]  [<c102e487>] ? kmsg_dump+0x35/0xb5
[    1.255228]  [<c14b1b32>] ? oops_end+0xa0/0xa8
[    1.256228]  [<c101b448>] ? no_context+0x110/0x11a
[    1.257228]  [<c101b570>] ? __bad_area_nosemaphore+0x11e/0x126
[    1.258228]  [<c121865a>] ? vt_console_print+0x25e/0x26c
[    1.259228]  [<c101b585>] ? bad_area_nosemaphore+0xd/0x10
[    1.260228]  [<c14b32c1>] ? do_page_fault+0x1c0/0x36b
[    1.261227]  [<c10144da>] ? __ipipe_handle_exception+0x24f/0x288
[    1.262227]  [<c14b11af>] ? error_code+0x5f/0x70
[    1.263227]  [<c10736fe>] ? __xirq_end+0x12/0x2e
[    1.264227]  [<c107472a>] ? ipipe_register_domain+0x1d8/0x1e4
[    1.265227]  [<c108e46e>] ? rthal_init+0x17d/0x20c
[    1.266227]  [<c139e098>] ? rthal_domain_entry+0x0/0x39
[    1.267227]  [<c1706c3d>] ? __xeno_sys_init+0x41/0x261
[    1.268226]  [<c108a4a2>] ? pmu_dev_alloc+0x64/0x7d
[    1.269226]  [<c1001076>] ? do_one_initcall+0x71/0x133
[    1.270226]  [<c1706bfc>] ? __xeno_sys_init+0x0/0x261
[    1.271226]  [<c16f4382>] ? kernel_init+0x128/0x1a4
[    1.272226]  [<c16f425a>] ? kernel_init+0x0/0x1a4
[    1.273226]  [<c1002d06>] ? kernel_thread_helper+0x6/0x10

Re: [Xenomai-help] Kernel panic on boot with 2.5.6

[Jan Kiszka]

On 2011-06-22 13:24, VEYSSIERE Nicolas wrote:
> First time for me here.
> 
> The log are in the attachement.
> 

...

> [    0.383950] ------------[ cut here ]------------
> [    0.384950] WARNING: at arch/x86/kernel/apic/apic.c:1289 setup_local_APIC+0x1e1/0x2cb()
> [    0.385950] Hardware name: VirtualBox
> [    0.386950] Modules linked in:
> [    0.389949] Pid: 1, comm: swapper Not tainted 2.6.38-xenomai-r6 #1

What's your host system, Windows? If it's Linux, don't use VBox, use
QEMU/KVM (it's know to host Xenomai x86 without major problems, it's my
primary test platform for years).

What may help if you can't avoid VBox is to provide the host's CPU
frequency statically to Xenomai (xeno_hal.cpufreq=...) and enforce the
tsc as clocksource (clocksource=tsc). Timekeeping may go mad in the
guest, but it's for testing purposes only anyway.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

Re: [Xenomai-help] Kernel panic on boot with 2.5.6

[VEYSSIERE Nicolas]

Yes, my host is Windows, I can't change anything about that, and yes it is only for testing.

I changed my boot line : [    0.000000] Kernel command line: root=/dev/sda3 xeno_hal.cpufreq=1200 clocksource=tsc console=tty0 console=ttyS0,115200 noapic acpi=noirq video=vesafb:mtrr:3,ywrap vga=6

But I didn't find the range or the unit for cpufreq, and maybe I had to prefix clocksource with xeno_hal ?

But I noticed this in the log : 

[    1.202694] BUG: unable to handle kernel NULL pointer dereference at 00000920
[    1.202694] IP: [<c10736fe>] __xirq_end+0x12/0x2e
[    1.202694] *pde = 00000000 
[    1.202694] Oops: 0000 [#1] SMP

Can it be because SMP is activated and that virtualbox is enabling only 1 processor with 1 core ?


-- 
Nicolas VEYSSIERE


-----Message d'origine-----
De : Jan Kiszka [mailto:jan.kiszka@siemens.com] 
Envoyé : mercredi 22 juin 2011 14:33
À : VEYSSIERE Nicolas
Cc : Gilles Chanteperdrix; xenomai-help@gna.org
Objet : Re: Kernel panic on boot with 2.5.6

On 2011-06-22 13:24, VEYSSIERE Nicolas wrote:
> First time for me here.
> 
> The log are in the attachement.
> 

...

> [    0.383950] ------------[ cut here ]------------
> [    0.384950] WARNING: at arch/x86/kernel/apic/apic.c:1289 setup_local_APIC+0x1e1/0x2cb()
> [    0.385950] Hardware name: VirtualBox
> [    0.386950] Modules linked in:
> [    0.389949] Pid: 1, comm: swapper Not tainted 2.6.38-xenomai-r6 #1

What's your host system, Windows? If it's Linux, don't use VBox, use
QEMU/KVM (it's know to host Xenomai x86 without major problems, it's my
primary test platform for years).

What may help if you can't avoid VBox is to provide the host's CPU
frequency statically to Xenomai (xeno_hal.cpufreq=...) and enforce the
tsc as clocksource (clocksource=tsc). Timekeeping may go mad in the
guest, but it's for testing purposes only anyway.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

Re: [Xenomai-help] Kernel panic on boot with 2.5.6

[Jan Kiszka]

On 2011-06-22 14:47, VEYSSIERE Nicolas wrote:
> Yes, my host is Windows, I can't change anything about that, and yes it is only for testing.
> 
> I changed my boot line : [    0.000000] Kernel command line: root=/dev/sda3 xeno_hal.cpufreq=1200 clocksource=tsc console=tty0 console=ttyS0,115200 noapic acpi=noirq video=vesafb:mtrr:3,ywrap vga=6
> 
> But I didn't find the range or the unit for cpufreq, and maybe I had to prefix clocksource with xeno_hal ?

Unit is HZ.

> 
> But I noticed this in the log : 
> 
> [    1.202694] BUG: unable to handle kernel NULL pointer dereference at 00000920
> [    1.202694] IP: [<c10736fe>] __xirq_end+0x12/0x2e
> [    1.202694] *pde = 00000000 
> [    1.202694] Oops: 0000 [#1] SMP
> 
> Can it be because SMP is activated and that virtualbox is enabling only 1 processor with 1 core ?

I don't know what vbox emulates in UP mode. We are only using it (for
Windows hosts) in SMP mode.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

Re: [Xenomai-help] Kernel panic on boot with 2.5.6

[VEYSSIERE Nicolas]

Found the problem !

It works on an Intel E5400 processor (for the host) but not on an Intel E2140


thanks for all.


Regards,

-- 
Nicolas VEYSSIERE

Re: [Xenomai-help] Kernel panic on boot with 2.5.6

[varname]

VEYSSIERE Nicolas wrote:
> Found the problem !
> 
> It works on an Intel E5400 processor (for the host) but not on an Intel E2140

So what was the problem? Looking at [1], I guess support for VT-x?



[1] http://ark.intel.com/Compare.aspx?ids=29738,40478,

Re: [Xenomai-help] Kernel panic on boot with 2.5.6

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 517 bytes --]

On 2011-06-23 11:53, varname wrote:
> VEYSSIERE Nicolas wrote:
>> Found the problem !
>>
>> It works on an Intel E5400 processor (for the host) but not on an
>> Intel E2140
> 
> So what was the problem? Looking at [1], I guess support for VT-x?
> 

Running without VT-x means that vbox emulates a CPU. And that may be a
different type than what your guest kernel expects. Or that the modeling
is incomplete or buggy.

Virtualization without VT-x/AMD-V is no good idea anyway (way too slow).

Jan



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]

Re: [Xenomai-help] Kernel panic on boot with 2.5.6

[Sambasiva Rao Manchili]

[-- Attachment #1: Type: text/plain, Size: 2460 bytes --]

HI Nicolas,
For me similar panic was solved by adding
noapic and acpi=noirq options in Kernel Boot parameters while booting edit and add them and  please see if it helps.

Samba


________________________________
From: xenomai-help-bounces@domain.hid [mailto:xenomai-help-bounces@domain.hid] On Behalf Of VEYSSIERE Nicolas
Sent: Wednesday, 22. June, 2011 12:44
To: xenomai@xenomai.org
Subject: [Xenomai-help] Kernel panic on boot with 2.5.6

Hello,

I succesfully build a 2.6.38.8 kernel with the latest adeos patch and Xenomai 2.5.6, but it kernel panic :

[    1.195878] Pid: 1, comm: swapper Tainted: G         D W     2.6.38-xenomai-r6 #1
[    1.196878] Call Trace:
[    1.196878]  [<c14ae979>] ? panic+0x50/0x145
[    1.197878]  [<c1031250>] ? do_exit+0x5c/0x6be
[    1.198877]  [<c14b071c>] ? _raw_spin_unlock_irqrestore+0xe/0x10
[    1.199877]  [<c102e487>] ? kmsg_dump+0x35/0xb5
[    1.200877]  [<c14b1b32>] ? oops_end+0xa0/0xa8
[    1.201877]  [<c101b448>] ? no_context+0x110/0x11a
[    1.201877]  [<c101b570>] ? __bad_area_nosemaphore+0x11e/0x126
[    1.202877]  [<c101b585>] ? bad_area_nosemaphore+0xd/0x10
[    1.203877]  [<c14b32c1>] ? do_page_fault+0x1c0/0x36b
[    1.203877]  [<c10144da>] ? __ipipe_handle_exception+0x24f/0x288
[    1.203877]  [<c14b11af>] ? error_code+0x5f/0x70
[    1.204876]  [<c10736fe>] ? __xirq_end+0x12/0x2e
[    1.205876]  [<c107472a>] ? ipipe_register_domain+0x1d8/0x1e4
[    1.205876]  [<c108e46e>] ? rthal_init+0x17d/0x20c
[    1.206876]  [<c139e098>] ? rthal_domain_entry+0x0/0x39
[    1.207876]  [<c1706c3d>] ? __xeno_sys_init+0x41/0x261
[    1.208876]  [<c108a4a2>] ? pmu_dev_alloc+0x64/0x7d
[    1.208876]  [<c1001076>] ? do_one_initcall+0x71/0x133
[    1.209876]  [<c1706bfc>] ? __xeno_sys_init+0x0/0x261
[    1.210876]  [<c16f4382>] ? kernel_init+0x128/0x1a4
[    1.211875]  [<c16f425a>] ? kernel_init+0x0/0x1a4
[    1.212875]  [<c1002d06>] ? kernel_thread_helper+0x6/0x10


Could it be a problem with the fact that this system is a virtual box VM ?


Thanks.

--
Nicolas VEYSSIERE

________________________________
This email and any attachment may contain confidential information which is intended for use only by the addressee(s) named above. If you received this email by mistake, please notify the sender immediately, and delete the email from your system. You are prohibited from copying, disseminating or otherwise using the email or any attachment.

[-- Attachment #2: Type: text/html, Size: 8822 bytes --]

Re: [Xenomai-help] Kernel panic on boot with 2.5.6

[Sambasiva Rao Manchili]

[-- Attachment #1: Type: text/plain, Size: 3282 bytes --]

Hi Nicolas,
The following link helped in my case....
<http://ubuntuforums.org/archive/index.php/t-148761.html>

Please have a look.
Samba.

________________________________
From: xenomai-help-bounces@domain.hid [mailto:xenomai-help-bounces@domain.hid] On Behalf Of Sambasiva Rao Manchili
Sent: Wednesday, 22. June, 2011 12:59
To: VEYSSIERE Nicolas; xenomai@xenomai.org
Subject: Re: [Xenomai-help] Kernel panic on boot with 2.5.6

HI Nicolas,
For me similar panic was solved by adding
noapic and acpi=noirq options in Kernel Boot parameters while booting edit and add them and  please see if it helps.

Samba


________________________________
From: xenomai-help-bounces@domain.hid [mailto:xenomai-help-bounces@domain.hid] On Behalf Of VEYSSIERE Nicolas
Sent: Wednesday, 22. June, 2011 12:44
To: xenomai@xenomai.org
Subject: [Xenomai-help] Kernel panic on boot with 2.5.6

Hello,

I succesfully build a 2.6.38.8 kernel with the latest adeos patch and Xenomai 2.5.6, but it kernel panic :

[    1.195878] Pid: 1, comm: swapper Tainted: G         D W     2.6.38-xenomai-r6 #1
[    1.196878] Call Trace:
[    1.196878]  [<c14ae979>] ? panic+0x50/0x145
[    1.197878]  [<c1031250>] ? do_exit+0x5c/0x6be
[    1.198877]  [<c14b071c>] ? _raw_spin_unlock_irqrestore+0xe/0x10
[    1.199877]  [<c102e487>] ? kmsg_dump+0x35/0xb5
[    1.200877]  [<c14b1b32>] ? oops_end+0xa0/0xa8
[    1.201877]  [<c101b448>] ? no_context+0x110/0x11a
[    1.201877]  [<c101b570>] ? __bad_area_nosemaphore+0x11e/0x126
[    1.202877]  [<c101b585>] ? bad_area_nosemaphore+0xd/0x10
[    1.203877]  [<c14b32c1>] ? do_page_fault+0x1c0/0x36b
[    1.203877]  [<c10144da>] ? __ipipe_handle_exception+0x24f/0x288
[    1.203877]  [<c14b11af>] ? error_code+0x5f/0x70
[    1.204876]  [<c10736fe>] ? __xirq_end+0x12/0x2e
[    1.205876]  [<c107472a>] ? ipipe_register_domain+0x1d8/0x1e4
[    1.205876]  [<c108e46e>] ? rthal_init+0x17d/0x20c
[    1.206876]  [<c139e098>] ? rthal_domain_entry+0x0/0x39
[    1.207876]  [<c1706c3d>] ? __xeno_sys_init+0x41/0x261
[    1.208876]  [<c108a4a2>] ? pmu_dev_alloc+0x64/0x7d
[    1.208876]  [<c1001076>] ? do_one_initcall+0x71/0x133
[    1.209876]  [<c1706bfc>] ? __xeno_sys_init+0x0/0x261
[    1.210876]  [<c16f4382>] ? kernel_init+0x128/0x1a4
[    1.211875]  [<c16f425a>] ? kernel_init+0x0/0x1a4
[    1.212875]  [<c1002d06>] ? kernel_thread_helper+0x6/0x10


Could it be a problem with the fact that this system is a virtual box VM ?


Thanks.

--
Nicolas VEYSSIERE

________________________________
This email and any attachment may contain confidential information which is intended for use only by the addressee(s) named above. If you received this email by mistake, please notify the sender immediately, and delete the email from your system. You are prohibited from copying, disseminating or otherwise using the email or any attachment.

________________________________
This email and any attachment may contain confidential information which is intended for use only by the addressee(s) named above. If you received this email by mistake, please notify the sender immediately, and delete the email from your system. You are prohibited from copying, disseminating or otherwise using the email or any attachment.

[-- Attachment #2: Type: text/html, Size: 10726 bytes --]

Re: [Xenomai-help] Kernel panic on boot with 2.5.6

[VEYSSIERE Nicolas]

[-- Attachment #1: Type: text/plain, Size: 2740 bytes --]

This doesn't seems to work for me :(


thanks anyway.

--
Nicolas VEYSSIERE

De : Sambasiva Rao Manchili [mailto:sambasiva.manchili@domain.hid]
Envoyé : mercredi 22 juin 2011 12:59
À : VEYSSIERE Nicolas; xenomai@xenomai.org
Objet : RE: Kernel panic on boot with 2.5.6

HI Nicolas,
For me similar panic was solved by adding
noapic and acpi=noirq options in Kernel Boot parameters while booting edit and add them and  please see if it helps.

Samba


________________________________
From: xenomai-help-bounces@domain.hid [mailto:xenomai-help-bounces@domain.hid] On Behalf Of VEYSSIERE Nicolas
Sent: Wednesday, 22. June, 2011 12:44
To: xenomai@xenomai.org
Subject: [Xenomai-help] Kernel panic on boot with 2.5.6
Hello,

I succesfully build a 2.6.38.8 kernel with the latest adeos patch and Xenomai 2.5.6, but it kernel panic :

[    1.195878] Pid: 1, comm: swapper Tainted: G         D W     2.6.38-xenomai-r6 #1
[    1.196878] Call Trace:
[    1.196878]  [<c14ae979>] ? panic+0x50/0x145
[    1.197878]  [<c1031250>] ? do_exit+0x5c/0x6be
[    1.198877]  [<c14b071c>] ? _raw_spin_unlock_irqrestore+0xe/0x10
[    1.199877]  [<c102e487>] ? kmsg_dump+0x35/0xb5
[    1.200877]  [<c14b1b32>] ? oops_end+0xa0/0xa8
[    1.201877]  [<c101b448>] ? no_context+0x110/0x11a
[    1.201877]  [<c101b570>] ? __bad_area_nosemaphore+0x11e/0x126
[    1.202877]  [<c101b585>] ? bad_area_nosemaphore+0xd/0x10
[    1.203877]  [<c14b32c1>] ? do_page_fault+0x1c0/0x36b
[    1.203877]  [<c10144da>] ? __ipipe_handle_exception+0x24f/0x288
[    1.203877]  [<c14b11af>] ? error_code+0x5f/0x70
[    1.204876]  [<c10736fe>] ? __xirq_end+0x12/0x2e
[    1.205876]  [<c107472a>] ? ipipe_register_domain+0x1d8/0x1e4
[    1.205876]  [<c108e46e>] ? rthal_init+0x17d/0x20c
[    1.206876]  [<c139e098>] ? rthal_domain_entry+0x0/0x39
[    1.207876]  [<c1706c3d>] ? __xeno_sys_init+0x41/0x261
[    1.208876]  [<c108a4a2>] ? pmu_dev_alloc+0x64/0x7d
[    1.208876]  [<c1001076>] ? do_one_initcall+0x71/0x133
[    1.209876]  [<c1706bfc>] ? __xeno_sys_init+0x0/0x261
[    1.210876]  [<c16f4382>] ? kernel_init+0x128/0x1a4
[    1.211875]  [<c16f425a>] ? kernel_init+0x0/0x1a4
[    1.212875]  [<c1002d06>] ? kernel_thread_helper+0x6/0x10


Could it be a problem with the fact that this system is a virtual box VM ?


Thanks.

--
Nicolas VEYSSIERE

________________________________
This email and any attachment may contain confidential information which is intended for use only by the addressee(s) named above. If you received this email by mistake, please notify the sender immediately, and delete the email from your system. You are prohibited from copying, disseminating or otherwise using the email or any attachment.

[-- Attachment #2: Type: text/html, Size: 11634 bytes --]