From: "Olivier B." <xen.list@daevel.fr>
To: xen-devel@lists.xensource.com
Subject: Re: Xen 4.0.1 & kernel Oops: 0000 [#1] SMP
Date: Sun, 11 Jul 2010 00:46:29 +0200 [thread overview]
Message-ID: <4C38F845.3050903@daevel.fr> (raw)
In-Reply-To: <4C38F752.2000007@daevel.fr>
Sorry, here is the full trace :
Jul 11 00:34:38 keron kernel: [10801.850551] alloc irq_desc for 1198
on node 0
Jul 11 00:34:38 keron kernel: [10801.850554] alloc kstat_irqs on node 0
Jul 11 00:34:38 keron kernel: [10802.030686] BUG: unable to handle
kernel NULL pointer dereference at 0000000000000110
Jul 11 00:34:38 keron kernel: [10802.031365] IP: [<ffffffff8121d070>]
netback_uevent+0x90/0xb9
Jul 11 00:34:38 keron kernel: [10802.031721] PGD 3880e067 PUD 3ef5c067
PMD 0
Jul 11 00:34:38 keron kernel: [10802.032082] Oops: 0000 [#1] SMP
Jul 11 00:34:38 keron kernel: [10802.032442] last sysfs file:
/sys/devices/vif-1-0/uevent
Jul 11 00:34:38 keron kernel: [10802.032772] CPU 1
Jul 11 00:34:38 keron kernel: [10802.033093] Modules linked in: 8021q
garp [last unloaded: scsi_wait_scan]
Jul 11 00:34:38 keron kernel: [10802.033459] Pid: 4998, comm: udevd Not
tainted 2.6.32.16-dae-dom0-gb97a312 #1 S5520HC
Jul 11 00:34:38 keron kernel: [10802.034113] RIP:
e030:[<ffffffff8121d070>] [<ffffffff8121d070>] netback_uevent+0x90/0xb9
Jul 11 00:34:38 keron kernel: [10802.034816] RSP: e02b:ffff88003773de08
EFLAGS: 00010246
Jul 11 00:34:38 keron kernel: [10802.035156] RAX: 0000000000000000 RBX:
ffff8800370ad200 RCX: ffff880038809154
Jul 11 00:34:38 keron kernel: [10802.035500] RDX: 000000000000002f RSI:
ffff8800377e5620 RDI: ffff880038809000
Jul 11 00:34:38 keron kernel: [10802.035848] RBP: ffff880038809000 R08:
000000000000000a R09: ffff880038809904
Jul 11 00:34:38 keron kernel: [10802.036190] R10: ffff880038809154 R11:
00c0ade35678d607 R12: 0000000000000000
Jul 11 00:34:38 keron kernel: [10802.036534] R13: ffff8800377e5620 R14:
ffff88003d123000 R15: ffffffff81618590
Jul 11 00:34:38 keron kernel: [10802.036884] FS: 00007fd3004287a0(0000)
GS:ffff880002134000(0000) knlGS:0000000000000000
Jul 11 00:34:38 keron kernel: [10802.037561] CS: e033 DS: 0000 ES: 0000
CR0: 000000008005003b
Jul 11 00:34:38 keron kernel: [10802.037906] CR2: 0000000000000110 CR3:
0000000038b2e000 CR4: 0000000000002660
Jul 11 00:34:38 keron kernel: [10802.038265] DR0: 0000000000000000 DR1:
0000000000000000 DR2: 0000000000000000
Jul 11 00:34:38 keron kernel: [10802.038626] DR3: 0000000000000000 DR6:
00000000ffff0ff0 DR7: 0000000000000400
Jul 11 00:34:38 keron kernel: [10802.038966] Process udevd (pid: 4998,
threadinfo ffff88003773c000, task ffff880037232240)
Jul 11 00:34:38 keron kernel: [10802.039632] Stack:
Jul 11 00:34:38 keron kernel: [10802.039969] 0000000000000001
ffff8800370ad240 ffff880038809000 ffff88003fc47340
Jul 11 00:34:38 keron kernel: [10802.040345] <0> ffff8800370ad250
ffffffff81245d22 ffffffff8100e1ff ffffffff810a0d4b
Jul 11 00:34:38 keron kernel: [10802.041024] <0> ffffffff81618560
0000000000000000 ffff880038809000 ffffffff812469d5
Jul 11 00:34:38 keron kernel: [10802.042070] Call Trace:
Jul 11 00:34:38 keron kernel: [10802.042406] [<ffffffff81245d22>] ?
dev_uevent+0xff/0x141
Jul 11 00:34:38 keron kernel: [10802.042764] [<ffffffff8100e1ff>] ?
xen_restore_fl_direct_end+0x0/0x1
Jul 11 00:34:38 keron kernel: [10802.043126] [<ffffffff810a0d4b>] ?
__kmalloc+0xac/0xce
Jul 11 00:34:38 keron kernel: [10802.043467] [<ffffffff812469d5>] ?
show_uevent+0x7e/0xd1
Jul 11 00:34:38 keron kernel: [10802.043813] [<ffffffff81245a08>] ?
dev_attr_show+0x1e/0x44
Jul 11 00:34:38 keron kernel: [10802.044157] [<ffffffff8107c0b2>] ?
__get_free_pages+0x9/0x46
Jul 11 00:34:38 keron kernel: [10802.044506] [<ffffffff810eb4f2>] ?
sysfs_read_file+0xab/0x131
Jul 11 00:34:38 keron kernel: [10802.044873] [<ffffffff810a696a>] ?
vfs_read+0xa1/0xfc
Jul 11 00:34:38 keron kernel: [10802.045219] [<ffffffff810a6a78>] ?
sys_read+0x45/0x6b
Jul 11 00:34:38 keron kernel: [10802.045561] [<ffffffff81010a02>] ?
system_call_fastpath+0x16/0x1b
Jul 11 00:34:38 keron kernel: [10802.045916] Code: 81 31 c0 48 89 ef e8
50 93 f9 ff 85 c0 74 0f 4c 89 ef bd f4 ff ff ff e8 49 2d e8 ff eb 2c 4c
89 ef e8 3f 2d e8 ff 48 89 ef 31 c0 <49> 8b 94 24 10 01 00 00 48 c7 c6
6c 0b 55 81 bd f4 ff ff ff e8
Jul 11 00:34:38 keron kernel: [10802.047250] RIP [<ffffffff8121d070>]
netback_uevent+0x90/0xb9
Jul 11 00:34:38 keron kernel: [10802.047597] RSP <ffff88003773de08>
Jul 11 00:34:38 keron kernel: [10802.047918] CR2: 0000000000000110
Jul 11 00:34:38 keron kernel: [10802.048551] ---[ end trace
0461e99cbca015f5 ]---
Jul 11 00:34:38 keron kernel: [10802.067905] alloc irq_desc for 1197
on node 0
Jul 11 00:34:38 keron kernel: [10802.068277] alloc kstat_irqs on node 0
Jul 11 00:34:38 keron kernel: [10802.119171] device vif1.0 entered
promiscuous mode
Jul 11 00:34:38 keron kernel: [10802.119071] eth0: port 2(vif1.0)
entering forwarding state
Le 11/07/2010 00:42, Olivier B. a écrit :
> Hi,
>
> I'm using Xen 4 (version 4.0.1~rc3-1 from Debian sid), with a
> 2.6.32.16-*-gb97a312 pv-ops kernel (the stable-2.6.32 branch) ; on a
> Debian Squeeze amd64 system, with udev version 158.
>
> When I try to create a DomU, with a bridge setup, I obtain that :
>
> # time xm create /etc/xen/slhoka.cfg
> Using config file "/etc/xen/slhoka.cfg".
>
> Message from syslogd@keron at Jul 11 00:34:38 ...
> kernel:[10802.032082] Oops: 0000 [#1] SMP
>
> Message from syslogd@keron at Jul 11 00:34:38 ...
> kernel:[10802.032442] last sysfs file: /sys/devices/vif-1-0/uevent
>
> Message from syslogd@keron at Jul 11 00:34:38 ...
> kernel:[10802.039632] Stack:
>
> Message from syslogd@keron at Jul 11 00:34:38 ...
> kernel:[10802.042070] Call Trace:
>
> Message from syslogd@keron at Jul 11 00:34:38 ...
> kernel:[10802.045916] Code: 81 31 c0 48 89 ef e8 50 93 f9 ff 85 c0 74
> 0f 4c 89 ef bd f4 ff ff ff e8 49 2d e8 ff eb 2c 4c 89 ef e8 3f 2d e8
> ff 48 89 ef 31 c0 <49> 8b 94 24 10 01 00 00 48 c7 c6 6c 0b 55 81 bd f4
> ff ff ff e8
>
> Message from syslogd@keron at Jul 11 00:34:38 ...
> kernel:[10802.047918] CR2: 0000000000000110
>
> Error: Device 2048 (vbd) could not be connected. Hotplug scripts not
> working.
>
> real 1m41.546s
> user 0m0.084s
> sys 0m0.040s
>
> The "hotplug" error is probably thrown because of my udev version
> (158), no ? But the kernel oops seem strange to me.
> If that can help, it's a "recent" CPU :
>
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 44
> model name : Intel(R) Xeon(R) CPU X5650 @ 2.67GHz
> stepping : 2
> cpu MHz : 2666.700
> cache size : 12288 KB
> fpu : yes
> fpu_exception : yes
> cpuid level : 11
> wp : yes
> flags : fpu de tsc msr pae mce cx8 apic sep mtrr mca cmov pat
> clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc
> rep_good nonstop_tsc aperfmperf pni pclmulqdq est ssse3 cx16 sse4_1
> sse4_2 popcnt aes hypervisor lahf_lm ida arat
> bogomips : 5333.40
> clflush size : 64
> cache_alignment : 64
> address sizes : 40 bits physical, 48 bits virtual
> power management:
>
>
> Thanks for any advice,
> Olivier B.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-07-10 22:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-10 22:42 Xen 4.0.1 & kernel Oops: 0000 [#1] SMP Olivier B.
2010-07-10 22:46 ` Olivier B. [this message]
2010-07-12 16:37 ` Konrad Rzeszutek Wilk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C38F845.3050903@daevel.fr \
--to=xen.list@daevel.fr \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).