Quartexx
2011-May-27 13:46 UTC
[Xen-devel] BUG: unable to handle kernel NULL pointer dereference (4.0.1 w/2.6.32.36)
Hi. xen 4.0.1 with kernel 2.6.32.36. I noticed in the last 2 days two kernel panics in the night (and two reboots thanks to sysctl value kernel.panic) This is the output I captured from netconsole: [491154.766766] BUG: unable to handle kernel NULL pointer dereference at 0000000000000320 [491154.767477] IP: [<ffffffff8128cbc3>] blktap_device_end_request+0x4a/0x71 [491154.767844] PGD 3db17067 PUD 3cebe067 PMD 0 [491154.768219] Oops: 0000 [#1] SMP [491154.768572] last sysfs file: /sys/devices/vbd-4-51713/statistics/wr_sect [491154.768942] CPU 3 [491154.769295] Modules linked in: netconsole [last unloaded: scsi_wait_scan] [491154.769683] Pid: 4392, comm: tapdisk2 Not tainted 2.6.32.36 #4 S3420GP [491154.770056] RIP: e030:[<ffffffff8128cbc3>] [<ffffffff8128cbc3>] blktap_device_end_request+0x4a/0x71 [491154.770767] RSP: e02b:ffff88003cd33ca8 EFLAGS: 00010046 [491154.771133] RAX: 0000000000000000 RBX: ffff88003df60d20 RCX: 0000000000000000 [491154.771824] RDX: 00000000000000a1 RSI: 0000000000000001 RDI: 0000000000000004 [491154.772524] RBP: ffff88003cd33cc8 R08: 0000000000000000 R09: ffff88003cd33b08 [491154.773222] R10: 0000000000000001 R11: ffffffff00001000 R12: ffff88003ccadb20 [491154.773915] R13: ffff88003d8e3c00 R14: 0000000000000000 R15: 0000000000000002 [491154.774622] FS: 00007f152f810740(0000) GS:ffff88002808f000(0000) knlGS:0000000000000000 [491154.775325] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b [491154.775683] CR2: 0000000000000320 CR3: 000000003b095000 CR4: 0000000000002660 [491154.776380] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [491154.777079] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [491154.777770] Process tapdisk2 (pid: 4392, threadinfo ffff88003cd32000, task ffff88003d833c80) [491154.778476] Stack: [491154.778821] ffff88003d8e3c00 0000000000000000 ffff88003ccadb20 0000000000e5386f [491154.779220] <0> ffff88003cd33e58 ffffffff8128beab 000000003cd33ce8 ffffffff81aab128 [491154.779956] <0> 000000013d743ac0 ffff88003d7439a0 000000019681a000 ffff88003fffc800 [491154.780987] Call Trace: [491154.781334] [<ffffffff8128beab>] blktap_ring_ioctl+0x12d/0x23f [491154.781676] [<ffffffff811d503b>] ? avc_has_perm+0x57/0x69 [491154.782017] [<ffffffff811d6322>] ? inode_has_perm+0x5f/0x61 [491154.782368] [<ffffffff810e13b3>] ? generic_file_aio_write+0x8c/0xa9 [491154.782718] [<ffffffff8111fd46>] vfs_ioctl+0x6a/0x82 [491154.783072] [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9 [491154.783426] [<ffffffff811202df>] sys_ioctl+0x51/0x74 [491154.783781] [<ffffffff8103ccc2>] system_call_fastpath+0x16/0x1b [491154.784142] Code: e6 4c 89 [491154.795155] [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9 There are 4 pv guest running using tap2:aio backend. Any hint or workaround to avoid this condition? And why this happen? Thanks in advance _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Quartexx
2011-May-27 14:26 UTC
[Xen-devel] Re: BUG: unable to handle kernel NULL pointer dereference (4.0.1 w/2.6.32.36)
adding: this of course happens on dom0 (I forgot to specify) and I see these messages in log at boot: # grep interr /var/log/messages May 26 01:03:14 xenhost-rack1 kernel: [ 3.552913] ACPI: Using IOAPIC for interrupt routing May 26 01:03:47 xenhost-rack1 kernel: [ 53.087139] hrtimer: interrupt took 189967875 ns May 27 06:08:43 xenhost-rack1 kernel: [ 3.571617] ACPI: Using IOAPIC for interrupt routing May 27 06:09:16 xenhost-rack1 kernel: [ 66.241242] hrtimer: interrupt took 149989194 ns Maybe it''s not related to BUG that I hit. (but that hrtimer line does not seem good.) Some hardware info: description: System product: S3420GP vendor: Intel Corporation version: .................... serial: ............ width: 64 bits capabilities: smbios-2.5 dmi-2.5 vsyscall64 vsyscall32 configuration: administrator_password=disabled boot=normal chassis=server fr ontpanel_password=disabled keyboard_password=disabled power-on_password=disabled uuid=0FD8E440-1952-11E0-B578-001E6702C2CA *-core description: Motherboard product: S3420GP vendor: Intel Corporation physical id: 0 *-memory description: System Memory physical id: 2e slot: System board or motherboard size: 16GiB *-cpu:0 description: CPU product: Intel(R) Xeon(R) CPU X3430 @ 2.40GHz vendor: Intel Corp. physical id: 3b bus info: cpu@0 version: Intel(R) Xeon(R) CPU X3430 @ 2.40GHz slot: CPU1 size: 2400MHz capacity: 4GHz width: 64 bits clock: 133MHz *-storage description: RAID bus controller product: 9690SA SAS/SATA-II RAID PCIe vendor: 3ware Inc physical id: 0 bus info: pci@0000:01:00.0 logical name: scsi0 version: 01 width: 64 bits clock: 33MHz capabilities: storage pm msi pciexpress bus_master cap_list rom emulated configuration: driver=3w-9xxx latency=0 resources: irq:16 memory:b0000000-b1ffffff(prefetchable) memory: b3a00000-b3a00fff ioport:2000(size=256) memory:b3a20000-b3a3ffff(prefetchable) I experienced controller reset but last lsi firmware seems to fix that _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
quartex
2011-Jun-11 11:17 UTC
[Xen-devel] Re: BUG: unable to handle kernel NULL pointer dereference (4.0.1 w/2.6.32.36)
I have updated to 2.6.32.41 but it happened again. [491154.766766] BUG: unable to handle kernel NULL pointer dereference at 0000000000000320 [491154.767477] IP: [<ffffffff8128cbc3>] blktap_device_end_request+0x4a/0x71 [491154.767844] PGD 3db17067 PUD 3cebe067 PMD 0 [491154.768219] Oops: 0000 [#1] SMP [491154.768572] last sysfs file: /sys/devices/vbd-4-51713/statistics/wr_sect [491154.768942] CPU 3 [491154.769295] Modules linked in: netconsole [last unloaded: scsi_wait_scan] [491154.769683] Pid: 4392, comm: tapdisk2 Not tainted 2.6.32.36 #4 S3420GP [491154.770056] RIP: e030:[<ffffffff8128cbc3>] [<ffffffff8128cbc3>] blktap_device_end_request+0x4a/0x71 [491154.770767] RSP: e02b:ffff88003cd33ca8 EFLAGS: 00010046 [491154.771133] RAX: 0000000000000000 RBX: ffff88003df60d20 RCX: 0000000000000000 [491154.771824] RDX: 00000000000000a1 RSI: 0000000000000001 RDI: 0000000000000004 [491154.772524] RBP: ffff88003cd33cc8 R08: 0000000000000000 R09: ffff88003cd33b08 [491154.773222] R10: 0000000000000001 R11: ffffffff00001000 R12: ffff88003ccadb20 [491154.773915] R13: ffff88003d8e3c00 R14: 0000000000000000 R15: 0000000000000002 [491154.774622] FS: 00007f152f810740(0000) GS:ffff88002808f000(0000) knlGS:0000000000000000 [491154.775325] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b [491154.775683] CR2: 0000000000000320 CR3: 000000003b095000 CR4: 0000000000002660 [491154.776380] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [491154.777079] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [491154.777770] Process tapdisk2 (pid: 4392, threadinfo ffff88003cd32000, task ffff88003d833c80) [491154.778476] Stack: [491154.778821] ffff88003d8e3c00 0000000000000000 ffff88003ccadb20 0000000000e5386f [491154.779220] <0> ffff88003cd33e58 ffffffff8128beab 000000003cd33ce8 ffffffff81aab128 [491154.779956] <0> 000000013d743ac0 ffff88003d7439a0 000000019681a000 ffff88003fffc800 [491154.780987] Call Trace: [491154.781334] [<ffffffff8128beab>] blktap_ring_ioctl+0x12d/0x23f [491154.781676] [<ffffffff811d503b>] ? avc_has_perm+0x57/0x69 [491154.782017] [<ffffffff811d6322>] ? inode_has_perm+0x5f/0x61 [491154.782368] [<ffffffff810e13b3>] ? generic_file_aio_write+0x8c/0xa9 [491154.782718] [<ffffffff8111fd46>] vfs_ioctl+0x6a/0x82 [491154.783072] [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9 [491154.783426] [<ffffffff811202df>] sys_ioctl+0x51/0x74 [491154.783781] [<ffffffff8103ccc2>] system_call_fastpath+0x16/0x1b [491154.784142] Code: e6 4c 89 [491154.795155] [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9 -- View this message in context: http://xen.1045712.n5.nabble.com/BUG-unable-to-handle-kernel-NULL-pointer-dereference-4-0-1-w-2-6-32-36-tp4432056p4478572.html Sent from the Xen - Dev mailing list archive at Nabble.com. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2011-Jun-11 11:26 UTC
Re: [Xen-devel] blktap problem: Re: BUG: unable to handle kernel NULL pointer dereference (4.0.1 w/2.6.32.36)
Hello, I added Daniel as CC, maybe he has some ideas about this one. What do you do when this crash happens? How to reproduce it? -- Pasi On Sat, Jun 11, 2011 at 04:17:44AM -0700, quartex wrote:> I have updated to 2.6.32.41 but it happened again. > > [491154.766766] BUG: unable to handle kernel NULL pointer dereference > at 0000000000000320 > [491154.767477] IP: [<ffffffff8128cbc3>] blktap_device_end_request+0x4a/0x71 > [491154.767844] PGD 3db17067 PUD 3cebe067 PMD 0 > [491154.768219] Oops: 0000 [#1] SMP > [491154.768572] last sysfs file: /sys/devices/vbd-4-51713/statistics/wr_sect > [491154.768942] CPU 3 > [491154.769295] Modules linked in: netconsole [last unloaded: > scsi_wait_scan] > [491154.769683] Pid: 4392, comm: tapdisk2 Not tainted 2.6.32.36 #4 S3420GP > [491154.770056] RIP: e030:[<ffffffff8128cbc3>] [<ffffffff8128cbc3>] > blktap_device_end_request+0x4a/0x71 > [491154.770767] RSP: e02b:ffff88003cd33ca8 EFLAGS: 00010046 > [491154.771133] RAX: 0000000000000000 RBX: ffff88003df60d20 RCX: > 0000000000000000 > [491154.771824] RDX: 00000000000000a1 RSI: 0000000000000001 RDI: > 0000000000000004 > [491154.772524] RBP: ffff88003cd33cc8 R08: 0000000000000000 R09: > ffff88003cd33b08 > [491154.773222] R10: 0000000000000001 R11: ffffffff00001000 R12: > ffff88003ccadb20 > [491154.773915] R13: ffff88003d8e3c00 R14: 0000000000000000 R15: > 0000000000000002 > [491154.774622] FS: 00007f152f810740(0000) GS:ffff88002808f000(0000) > knlGS:0000000000000000 > [491154.775325] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b > [491154.775683] CR2: 0000000000000320 CR3: 000000003b095000 CR4: > 0000000000002660 > [491154.776380] DR0: 0000000000000000 DR1: 0000000000000000 DR2: > 0000000000000000 > [491154.777079] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: > 0000000000000400 > [491154.777770] Process tapdisk2 (pid: 4392, threadinfo > ffff88003cd32000, task ffff88003d833c80) > [491154.778476] Stack: > [491154.778821] ffff88003d8e3c00 0000000000000000 ffff88003ccadb20 > 0000000000e5386f > [491154.779220] <0> ffff88003cd33e58 ffffffff8128beab 000000003cd33ce8 > ffffffff81aab128 > [491154.779956] <0> 000000013d743ac0 ffff88003d7439a0 000000019681a000 > ffff88003fffc800 > [491154.780987] Call Trace: > [491154.781334] [<ffffffff8128beab>] blktap_ring_ioctl+0x12d/0x23f > [491154.781676] [<ffffffff811d503b>] ? avc_has_perm+0x57/0x69 > [491154.782017] [<ffffffff811d6322>] ? inode_has_perm+0x5f/0x61 > [491154.782368] [<ffffffff810e13b3>] ? generic_file_aio_write+0x8c/0xa9 > [491154.782718] [<ffffffff8111fd46>] vfs_ioctl+0x6a/0x82 > [491154.783072] [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9 > [491154.783426] [<ffffffff811202df>] sys_ioctl+0x51/0x74 > [491154.783781] [<ffffffff8103ccc2>] system_call_fastpath+0x16/0x1b > [491154.784142] Code: e6 4c 89 > [491154.795155] [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9 > > > > > > -- > View this message in context: http://xen.1045712.n5.nabble.com/BUG-unable-to-handle-kernel-NULL-pointer-dereference-4-0-1-w-2-6-32-36-tp4432056p4478572.html > Sent from the Xen - Dev mailing list archive at Nabble.com. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Quartexx
2011-Jun-11 11:35 UTC
Re: [Xen-devel] blktap problem: Re: BUG: unable to handle kernel NULL pointer dereference (4.0.1 w/2.6.32.36)
2011/6/11 Pasi Kärkkäinen <pasik@iki.fi>:> Hello, > I added Daniel as CC, maybe he has some ideas about this one. > What do you do when this crash happens? How to reproduce it?It''s the third time and all times it happened in the night. I have set kernel.panic=20 so when this happen, the box simply reboot. I would say it''s random. The output I post was captured with netconsole Some hardware info: description: System product: S3420GP vendor: Intel Corporation version: .................... serial: ............ width: 64 bits capabilities: smbios-2.5 dmi-2.5 vsyscall64 vsyscall32 configuration: administrator_password=disabled boot=normal chassis=server fr ontpanel_password=disabled keyboard_password=disabled power-on_password=disabled uuid=0FD8E440-1952-11E0-B578-001E6702C2CA *-core description: Motherboard product: S3420GP vendor: Intel Corporation physical id: 0 *-memory description: System Memory physical id: 2e slot: System board or motherboard size: 16GiB *-cpu:0 description: CPU product: Intel(R) Xeon(R) CPU X3430 @ 2.40GHz vendor: Intel Corp. physical id: 3b bus info: cpu@0 version: Intel(R) Xeon(R) CPU X3430 @ 2.40GHz slot: CPU1 size: 2400MHz capacity: 4GHz width: 64 bits clock: 133MHz *-storage description: RAID bus controller product: 9690SA SAS/SATA-II RAID PCIe vendor: 3ware Inc physical id: 0 bus info: pci@0000:01:00.0 logical name: scsi0 version: 01 width: 64 bits clock: 33MHz capabilities: storage pm msi pciexpress bus_master cap_list rom emulated configuration: driver=3w-9xxx latency=0 resources: irq:16 memory:b0000000-b1ffffff(prefetchable) memory: b3a00000-b3a00fff ioport:2000(size=256) memory:b3a20000-b3a3ffff(prefetchable) In the beginning I experienced controller reset but last lsi firmware seems to fix that. Maybe it''s related to this bug..> > -- Pasi > > On Sat, Jun 11, 2011 at 04:17:44AM -0700, quartex wrote: >> I have updated to 2.6.32.41 but it happened again. >> >> [491154.766766] BUG: unable to handle kernel NULL pointer dereference >> at 0000000000000320 >> [491154.767477] IP: [<ffffffff8128cbc3>] blktap_device_end_request+0x4a/0x71 >> [491154.767844] PGD 3db17067 PUD 3cebe067 PMD 0 >> [491154.768219] Oops: 0000 [#1] SMP >> [491154.768572] last sysfs file: /sys/devices/vbd-4-51713/statistics/wr_sect >> [491154.768942] CPU 3 >> [491154.769295] Modules linked in: netconsole [last unloaded: >> scsi_wait_scan] >> [491154.769683] Pid: 4392, comm: tapdisk2 Not tainted 2.6.32.36 #4 S3420GP >> [491154.770056] RIP: e030:[<ffffffff8128cbc3>] [<ffffffff8128cbc3>] >> blktap_device_end_request+0x4a/0x71 >> [491154.770767] RSP: e02b:ffff88003cd33ca8 EFLAGS: 00010046 >> [491154.771133] RAX: 0000000000000000 RBX: ffff88003df60d20 RCX: >> 0000000000000000 >> [491154.771824] RDX: 00000000000000a1 RSI: 0000000000000001 RDI: >> 0000000000000004 >> [491154.772524] RBP: ffff88003cd33cc8 R08: 0000000000000000 R09: >> ffff88003cd33b08 >> [491154.773222] R10: 0000000000000001 R11: ffffffff00001000 R12: >> ffff88003ccadb20 >> [491154.773915] R13: ffff88003d8e3c00 R14: 0000000000000000 R15: >> 0000000000000002 >> [491154.774622] FS: 00007f152f810740(0000) GS:ffff88002808f000(0000) >> knlGS:0000000000000000 >> [491154.775325] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b >> [491154.775683] CR2: 0000000000000320 CR3: 000000003b095000 CR4: >> 0000000000002660 >> [491154.776380] DR0: 0000000000000000 DR1: 0000000000000000 DR2: >> 0000000000000000 >> [491154.777079] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: >> 0000000000000400 >> [491154.777770] Process tapdisk2 (pid: 4392, threadinfo >> ffff88003cd32000, task ffff88003d833c80) >> [491154.778476] Stack: >> [491154.778821] ffff88003d8e3c00 0000000000000000 ffff88003ccadb20 >> 0000000000e5386f >> [491154.779220] <0> ffff88003cd33e58 ffffffff8128beab 000000003cd33ce8 >> ffffffff81aab128 >> [491154.779956] <0> 000000013d743ac0 ffff88003d7439a0 000000019681a000 >> ffff88003fffc800 >> [491154.780987] Call Trace: >> [491154.781334] [<ffffffff8128beab>] blktap_ring_ioctl+0x12d/0x23f >> [491154.781676] [<ffffffff811d503b>] ? avc_has_perm+0x57/0x69 >> [491154.782017] [<ffffffff811d6322>] ? inode_has_perm+0x5f/0x61 >> [491154.782368] [<ffffffff810e13b3>] ? generic_file_aio_write+0x8c/0xa9 >> [491154.782718] [<ffffffff8111fd46>] vfs_ioctl+0x6a/0x82 >> [491154.783072] [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9 >> [491154.783426] [<ffffffff811202df>] sys_ioctl+0x51/0x74 >> [491154.783781] [<ffffffff8103ccc2>] system_call_fastpath+0x16/0x1b >> [491154.784142] Code: e6 4c 89 >> [491154.795155] [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9 >> >> >> >> >> >> -- >> View this message in context: http://xen.1045712.n5.nabble.com/BUG-unable-to-handle-kernel-NULL-pointer-dereference-4-0-1-w-2-6-32-36-tp4432056p4478572.html >> Sent from the Xen - Dev mailing list archive at Nabble.com. >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Quartexx
2011-Jun-11 12:53 UTC
Re: [Xen-devel] blktap problem: Re: BUG: unable to handle kernel NULL pointer dereference (4.0.1 w/2.6.32.36)
2011/6/11 Quartexx <quartex73@gmail.com>:> 2011/6/11 Pasi Kärkkäinen <pasik@iki.fi>: >> Hello, >> I added Daniel as CC, maybe he has some ideas about this one. >> What do you do when this crash happens? How to reproduce it?Absolutely nothing. 4 guests (all pvops) are running. It happens in the night when load is very low. I disabled C-states too from bios and I set max_cstate=1 as a kernel boot option. Still, no luck. As I said this happened always in the night. The only scheduled thing running in the night is the 3ware Check S.M.A.R.T. Thresholds self-test (it runs every day at 12.00 am. Crashes happened at 01:06 am and 02:17 am. Other info: Xen dom0 dedicated memory and preventing dom0 memory ballooning and more CPU time than the guests (credit scheduler). So I really don''t know how to reproduce it..but it happens :\ Thanks for your help _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Daniel Stodden
2011-Jun-13 00:17 UTC
Re: [Xen-devel] Re: BUG: unable to handle kernel NULL pointer dereference (4.0.1 w/2.6.32.36)
Can you all pull in this one? http://xenbits.xen.org/gitweb/?p=people/dstodden/linux.git;a=commit;h=a765257af7e28c41bd776c3e03615539597eb592 Likely the one, but let me absolutely know if not. Daniel On Sat, 2011-06-11 at 07:17 -0400, quartex wrote:> I have updated to 2.6.32.41 but it happened again. > > [491154.766766] BUG: unable to handle kernel NULL pointer dereference > at 0000000000000320 > [491154.767477] IP: [<ffffffff8128cbc3>] blktap_device_end_request+0x4a/0x71 > [491154.767844] PGD 3db17067 PUD 3cebe067 PMD 0 > [491154.768219] Oops: 0000 [#1] SMP > [491154.768572] last sysfs file: /sys/devices/vbd-4-51713/statistics/wr_sect > [491154.768942] CPU 3 > [491154.769295] Modules linked in: netconsole [last unloaded: > scsi_wait_scan] > [491154.769683] Pid: 4392, comm: tapdisk2 Not tainted 2.6.32.36 #4 S3420GP > [491154.770056] RIP: e030:[<ffffffff8128cbc3>] [<ffffffff8128cbc3>] > blktap_device_end_request+0x4a/0x71 > [491154.770767] RSP: e02b:ffff88003cd33ca8 EFLAGS: 00010046 > [491154.771133] RAX: 0000000000000000 RBX: ffff88003df60d20 RCX: > 0000000000000000 > [491154.771824] RDX: 00000000000000a1 RSI: 0000000000000001 RDI: > 0000000000000004 > [491154.772524] RBP: ffff88003cd33cc8 R08: 0000000000000000 R09: > ffff88003cd33b08 > [491154.773222] R10: 0000000000000001 R11: ffffffff00001000 R12: > ffff88003ccadb20 > [491154.773915] R13: ffff88003d8e3c00 R14: 0000000000000000 R15: > 0000000000000002 > [491154.774622] FS: 00007f152f810740(0000) GS:ffff88002808f000(0000) > knlGS:0000000000000000 > [491154.775325] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b > [491154.775683] CR2: 0000000000000320 CR3: 000000003b095000 CR4: > 0000000000002660 > [491154.776380] DR0: 0000000000000000 DR1: 0000000000000000 DR2: > 0000000000000000 > [491154.777079] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: > 0000000000000400 > [491154.777770] Process tapdisk2 (pid: 4392, threadinfo > ffff88003cd32000, task ffff88003d833c80) > [491154.778476] Stack: > [491154.778821] ffff88003d8e3c00 0000000000000000 ffff88003ccadb20 > 0000000000e5386f > [491154.779220] <0> ffff88003cd33e58 ffffffff8128beab 000000003cd33ce8 > ffffffff81aab128 > [491154.779956] <0> 000000013d743ac0 ffff88003d7439a0 000000019681a000 > ffff88003fffc800 > [491154.780987] Call Trace: > [491154.781334] [<ffffffff8128beab>] blktap_ring_ioctl+0x12d/0x23f > [491154.781676] [<ffffffff811d503b>] ? avc_has_perm+0x57/0x69 > [491154.782017] [<ffffffff811d6322>] ? inode_has_perm+0x5f/0x61 > [491154.782368] [<ffffffff810e13b3>] ? generic_file_aio_write+0x8c/0xa9 > [491154.782718] [<ffffffff8111fd46>] vfs_ioctl+0x6a/0x82 > [491154.783072] [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9 > [491154.783426] [<ffffffff811202df>] sys_ioctl+0x51/0x74 > [491154.783781] [<ffffffff8103ccc2>] system_call_fastpath+0x16/0x1b > [491154.784142] Code: e6 4c 89 > [491154.795155] [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9 > > > > > > -- > View this message in context: http://xen.1045712.n5.nabble.com/BUG-unable-to-handle-kernel-NULL-pointer-dereference-4-0-1-w-2-6-32-36-tp4432056p4478572.html > Sent from the Xen - Dev mailing list archive at Nabble.com. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Quartexx
2011-Jun-13 15:46 UTC
Re: [Xen-devel] Re: BUG: unable to handle kernel NULL pointer dereference (4.0.1 w/2.6.32.36)
2011/6/13 Daniel Stodden <daniel.stodden@citrix.com>:>> Can you all pull in this one? >> http://xenbits.xen.org/gitweb/?p=people/dstodden/linux.git;a=commit;h=a765257af7e28c41bd776c3e03615539597eb592 >> Likely the one, but let me absolutely know if not.ok, thanks Daniel. I''ve applied the patch. I will report you if this issue happen again (hope not). Thanks all> > Daniel > > > On Sat, 2011-06-11 at 07:17 -0400, quartex wrote: >> I have updated to 2.6.32.41 but it happened again. >> >> [491154.766766] BUG: unable to handle kernel NULL pointer dereference >> at 0000000000000320 >> [491154.767477] IP: [<ffffffff8128cbc3>] blktap_device_end_request+0x4a/0x71 >> [491154.767844] PGD 3db17067 PUD 3cebe067 PMD 0 >> [491154.768219] Oops: 0000 [#1] SMP >> [491154.768572] last sysfs file: /sys/devices/vbd-4-51713/statistics/wr_sect >> [491154.768942] CPU 3 >> [491154.769295] Modules linked in: netconsole [last unloaded: >> scsi_wait_scan] >> [491154.769683] Pid: 4392, comm: tapdisk2 Not tainted 2.6.32.36 #4 S3420GP >> [491154.770056] RIP: e030:[<ffffffff8128cbc3>] [<ffffffff8128cbc3>] >> blktap_device_end_request+0x4a/0x71 >> [491154.770767] RSP: e02b:ffff88003cd33ca8 EFLAGS: 00010046 >> [491154.771133] RAX: 0000000000000000 RBX: ffff88003df60d20 RCX: >> 0000000000000000 >> [491154.771824] RDX: 00000000000000a1 RSI: 0000000000000001 RDI: >> 0000000000000004 >> [491154.772524] RBP: ffff88003cd33cc8 R08: 0000000000000000 R09: >> ffff88003cd33b08 >> [491154.773222] R10: 0000000000000001 R11: ffffffff00001000 R12: >> ffff88003ccadb20 >> [491154.773915] R13: ffff88003d8e3c00 R14: 0000000000000000 R15: >> 0000000000000002 >> [491154.774622] FS: 00007f152f810740(0000) GS:ffff88002808f000(0000) >> knlGS:0000000000000000 >> [491154.775325] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b >> [491154.775683] CR2: 0000000000000320 CR3: 000000003b095000 CR4: >> 0000000000002660 >> [491154.776380] DR0: 0000000000000000 DR1: 0000000000000000 DR2: >> 0000000000000000 >> [491154.777079] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: >> 0000000000000400 >> [491154.777770] Process tapdisk2 (pid: 4392, threadinfo >> ffff88003cd32000, task ffff88003d833c80) >> [491154.778476] Stack: >> [491154.778821] ffff88003d8e3c00 0000000000000000 ffff88003ccadb20 >> 0000000000e5386f >> [491154.779220] <0> ffff88003cd33e58 ffffffff8128beab 000000003cd33ce8 >> ffffffff81aab128 >> [491154.779956] <0> 000000013d743ac0 ffff88003d7439a0 000000019681a000 >> ffff88003fffc800 >> [491154.780987] Call Trace: >> [491154.781334] [<ffffffff8128beab>] blktap_ring_ioctl+0x12d/0x23f >> [491154.781676] [<ffffffff811d503b>] ? avc_has_perm+0x57/0x69 >> [491154.782017] [<ffffffff811d6322>] ? inode_has_perm+0x5f/0x61 >> [491154.782368] [<ffffffff810e13b3>] ? generic_file_aio_write+0x8c/0xa9 >> [491154.782718] [<ffffffff8111fd46>] vfs_ioctl+0x6a/0x82 >> [491154.783072] [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9 >> [491154.783426] [<ffffffff811202df>] sys_ioctl+0x51/0x74 >> [491154.783781] [<ffffffff8103ccc2>] system_call_fastpath+0x16/0x1b >> [491154.784142] Code: e6 4c 89 >> [491154.795155] [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9 >> >> >> >> >> >> -- >> View this message in context: http://xen.1045712.n5.nabble.com/BUG-unable-to-handle-kernel-NULL-pointer-dereference-4-0-1-w-2-6-32-36-tp4432056p4478572.html >> Sent from the Xen - Dev mailing list archive at Nabble.com. >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jan Beulich
2011-Jun-14 08:36 UTC
Re: [Xen-devel] Re: BUG: unable to handle kernel NULL pointer dereference (4.0.1 w/2.6.32.36)
>>> On 13.06.11 at 02:17, Daniel Stodden <daniel.stodden@citrix.com> wrote:> Can you all pull in this one? > > http://xenbits.xen.org/gitweb/?p=people/dstodden/linux.git;a=commit;h=a76525 > 7af7e28c41bd776c3e03615539597eb592Any reason why after several months this still doesn''t appear to be in stable-2.6.32, which is what people are generally directed to use? Jan> Likely the one, but let me absolutely know if not. > > Daniel > > > On Sat, 2011-06-11 at 07:17 -0400, quartex wrote: >> I have updated to 2.6.32.41 but it happened again. >> >> [491154.766766] BUG: unable to handle kernel NULL pointer dereference >> at 0000000000000320 >> [491154.767477] IP: [<ffffffff8128cbc3>] blktap_device_end_request+0x4a/0x71 >> [491154.767844] PGD 3db17067 PUD 3cebe067 PMD 0 >> [491154.768219] Oops: 0000 [#1] SMP >> [491154.768572] last sysfs file: /sys/devices/vbd-4-51713/statistics/wr_sect >> [491154.768942] CPU 3 >> [491154.769295] Modules linked in: netconsole [last unloaded: >> scsi_wait_scan] >> [491154.769683] Pid: 4392, comm: tapdisk2 Not tainted 2.6.32.36 #4 S3420GP >> [491154.770056] RIP: e030:[<ffffffff8128cbc3>] [<ffffffff8128cbc3>] >> blktap_device_end_request+0x4a/0x71 >> [491154.770767] RSP: e02b:ffff88003cd33ca8 EFLAGS: 00010046 >> [491154.771133] RAX: 0000000000000000 RBX: ffff88003df60d20 RCX: >> 0000000000000000 >> [491154.771824] RDX: 00000000000000a1 RSI: 0000000000000001 RDI: >> 0000000000000004 >> [491154.772524] RBP: ffff88003cd33cc8 R08: 0000000000000000 R09: >> ffff88003cd33b08 >> [491154.773222] R10: 0000000000000001 R11: ffffffff00001000 R12: >> ffff88003ccadb20 >> [491154.773915] R13: ffff88003d8e3c00 R14: 0000000000000000 R15: >> 0000000000000002 >> [491154.774622] FS: 00007f152f810740(0000) GS:ffff88002808f000(0000) >> knlGS:0000000000000000 >> [491154.775325] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b >> [491154.775683] CR2: 0000000000000320 CR3: 000000003b095000 CR4: >> 0000000000002660 >> [491154.776380] DR0: 0000000000000000 DR1: 0000000000000000 DR2: >> 0000000000000000 >> [491154.777079] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: >> 0000000000000400 >> [491154.777770] Process tapdisk2 (pid: 4392, threadinfo >> ffff88003cd32000, task ffff88003d833c80) >> [491154.778476] Stack: >> [491154.778821] ffff88003d8e3c00 0000000000000000 ffff88003ccadb20 >> 0000000000e5386f >> [491154.779220] <0> ffff88003cd33e58 ffffffff8128beab 000000003cd33ce8 >> ffffffff81aab128 >> [491154.779956] <0> 000000013d743ac0 ffff88003d7439a0 000000019681a000 >> ffff88003fffc800 >> [491154.780987] Call Trace: >> [491154.781334] [<ffffffff8128beab>] blktap_ring_ioctl+0x12d/0x23f >> [491154.781676] [<ffffffff811d503b>] ? avc_has_perm+0x57/0x69 >> [491154.782017] [<ffffffff811d6322>] ? inode_has_perm+0x5f/0x61 >> [491154.782368] [<ffffffff810e13b3>] ? generic_file_aio_write+0x8c/0xa9 >> [491154.782718] [<ffffffff8111fd46>] vfs_ioctl+0x6a/0x82 >> [491154.783072] [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9 >> [491154.783426] [<ffffffff811202df>] sys_ioctl+0x51/0x74 >> [491154.783781] [<ffffffff8103ccc2>] system_call_fastpath+0x16/0x1b >> [491154.784142] Code: e6 4c 89 >> [491154.795155] [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9 >> >> >> >> >> >> -- >> View this message in context: > http://xen.1045712.n5.nabble.com/BUG-unable-to-handle-kernel-NULL-pointer-dere > ference-4-0-1-w-2-6-32-36-tp4432056p4478572.html >> Sent from the Xen - Dev mailing list archive at Nabble.com. >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Daniel Stodden
2011-Jun-14 19:44 UTC
Re: [Xen-devel] Re: BUG: unable to handle kernel NULL pointer dereference (4.0.1 w/2.6.32.36)
On Tue, 2011-06-14 at 04:36 -0400, Jan Beulich wrote:> >>> On 13.06.11 at 02:17, Daniel Stodden <daniel.stodden@citrix.com> wrote: > > > Can you all pull in this one? > > > > http://xenbits.xen.org/gitweb/?p=people/dstodden/linux.git;a=commit;h=a76525 > > 7af7e28c41bd776c3e03615539597eb592 > > Any reason why after several months this still doesn''t appear to be in > stable-2.6.32, which is what people are generally directed to use?Presumably no, it''s a no-brainer. Who''s maintaining 2.6.32 right now? I thought that''s still Jeremy. Sorry if keep ccing the wrong people, it''s the second time this came up. Daniel> Jan > > > Likely the one, but let me absolutely know if not. > > > > Daniel > > > > > > On Sat, 2011-06-11 at 07:17 -0400, quartex wrote: > >> I have updated to 2.6.32.41 but it happened again. > >> > >> [491154.766766] BUG: unable to handle kernel NULL pointer dereference > >> at 0000000000000320 > >> [491154.767477] IP: [<ffffffff8128cbc3>] blktap_device_end_request+0x4a/0x71 > >> [491154.767844] PGD 3db17067 PUD 3cebe067 PMD 0 > >> [491154.768219] Oops: 0000 [#1] SMP > >> [491154.768572] last sysfs file: /sys/devices/vbd-4-51713/statistics/wr_sect > >> [491154.768942] CPU 3 > >> [491154.769295] Modules linked in: netconsole [last unloaded: > >> scsi_wait_scan] > >> [491154.769683] Pid: 4392, comm: tapdisk2 Not tainted 2.6.32.36 #4 S3420GP > >> [491154.770056] RIP: e030:[<ffffffff8128cbc3>] [<ffffffff8128cbc3>] > >> blktap_device_end_request+0x4a/0x71 > >> [491154.770767] RSP: e02b:ffff88003cd33ca8 EFLAGS: 00010046 > >> [491154.771133] RAX: 0000000000000000 RBX: ffff88003df60d20 RCX: > >> 0000000000000000 > >> [491154.771824] RDX: 00000000000000a1 RSI: 0000000000000001 RDI: > >> 0000000000000004 > >> [491154.772524] RBP: ffff88003cd33cc8 R08: 0000000000000000 R09: > >> ffff88003cd33b08 > >> [491154.773222] R10: 0000000000000001 R11: ffffffff00001000 R12: > >> ffff88003ccadb20 > >> [491154.773915] R13: ffff88003d8e3c00 R14: 0000000000000000 R15: > >> 0000000000000002 > >> [491154.774622] FS: 00007f152f810740(0000) GS:ffff88002808f000(0000) > >> knlGS:0000000000000000 > >> [491154.775325] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b > >> [491154.775683] CR2: 0000000000000320 CR3: 000000003b095000 CR4: > >> 0000000000002660 > >> [491154.776380] DR0: 0000000000000000 DR1: 0000000000000000 DR2: > >> 0000000000000000 > >> [491154.777079] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: > >> 0000000000000400 > >> [491154.777770] Process tapdisk2 (pid: 4392, threadinfo > >> ffff88003cd32000, task ffff88003d833c80) > >> [491154.778476] Stack: > >> [491154.778821] ffff88003d8e3c00 0000000000000000 ffff88003ccadb20 > >> 0000000000e5386f > >> [491154.779220] <0> ffff88003cd33e58 ffffffff8128beab 000000003cd33ce8 > >> ffffffff81aab128 > >> [491154.779956] <0> 000000013d743ac0 ffff88003d7439a0 000000019681a000 > >> ffff88003fffc800 > >> [491154.780987] Call Trace: > >> [491154.781334] [<ffffffff8128beab>] blktap_ring_ioctl+0x12d/0x23f > >> [491154.781676] [<ffffffff811d503b>] ? avc_has_perm+0x57/0x69 > >> [491154.782017] [<ffffffff811d6322>] ? inode_has_perm+0x5f/0x61 > >> [491154.782368] [<ffffffff810e13b3>] ? generic_file_aio_write+0x8c/0xa9 > >> [491154.782718] [<ffffffff8111fd46>] vfs_ioctl+0x6a/0x82 > >> [491154.783072] [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9 > >> [491154.783426] [<ffffffff811202df>] sys_ioctl+0x51/0x74 > >> [491154.783781] [<ffffffff8103ccc2>] system_call_fastpath+0x16/0x1b > >> [491154.784142] Code: e6 4c 89 > >> [491154.795155] [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9 > >> > >> > >> > >> > >> > >> -- > >> View this message in context: > > http://xen.1045712.n5.nabble.com/BUG-unable-to-handle-kernel-NULL-pointer-dere > > ference-4-0-1-w-2-6-32-36-tp4432056p4478572.html > >> Sent from the Xen - Dev mailing list archive at Nabble.com. > >> > >> _______________________________________________ > >> Xen-devel mailing list > >> Xen-devel@lists.xensource.com > >> http://lists.xensource.com/xen-devel > > > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2011-Jun-24 18:25 UTC
Re: [Xen-devel] Re: BUG: unable to handle kernel NULL pointer dereference (4.0.1 w/2.6.32.36)
On 06/14/2011 01:36 AM, Jan Beulich wrote:>>>> On 13.06.11 at 02:17, Daniel Stodden <daniel.stodden@citrix.com> wrote: >> Can you all pull in this one? >> >> http://xenbits.xen.org/gitweb/?p=people/dstodden/linux.git;a=commit;h=a76525 >> 7af7e28c41bd776c3e03615539597eb592 > Any reason why after several months this still doesn''t appear to be in > stable-2.6.32, which is what people are generally directed to use?Daniel? Should I merge this? Thanks, J> Jan > >> Likely the one, but let me absolutely know if not. >> >> Daniel >> >> >> On Sat, 2011-06-11 at 07:17 -0400, quartex wrote: >>> I have updated to 2.6.32.41 but it happened again. >>> >>> [491154.766766] BUG: unable to handle kernel NULL pointer dereference >>> at 0000000000000320 >>> [491154.767477] IP: [<ffffffff8128cbc3>] blktap_device_end_request+0x4a/0x71 >>> [491154.767844] PGD 3db17067 PUD 3cebe067 PMD 0 >>> [491154.768219] Oops: 0000 [#1] SMP >>> [491154.768572] last sysfs file: /sys/devices/vbd-4-51713/statistics/wr_sect >>> [491154.768942] CPU 3 >>> [491154.769295] Modules linked in: netconsole [last unloaded: >>> scsi_wait_scan] >>> [491154.769683] Pid: 4392, comm: tapdisk2 Not tainted 2.6.32.36 #4 S3420GP >>> [491154.770056] RIP: e030:[<ffffffff8128cbc3>] [<ffffffff8128cbc3>] >>> blktap_device_end_request+0x4a/0x71 >>> [491154.770767] RSP: e02b:ffff88003cd33ca8 EFLAGS: 00010046 >>> [491154.771133] RAX: 0000000000000000 RBX: ffff88003df60d20 RCX: >>> 0000000000000000 >>> [491154.771824] RDX: 00000000000000a1 RSI: 0000000000000001 RDI: >>> 0000000000000004 >>> [491154.772524] RBP: ffff88003cd33cc8 R08: 0000000000000000 R09: >>> ffff88003cd33b08 >>> [491154.773222] R10: 0000000000000001 R11: ffffffff00001000 R12: >>> ffff88003ccadb20 >>> [491154.773915] R13: ffff88003d8e3c00 R14: 0000000000000000 R15: >>> 0000000000000002 >>> [491154.774622] FS: 00007f152f810740(0000) GS:ffff88002808f000(0000) >>> knlGS:0000000000000000 >>> [491154.775325] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b >>> [491154.775683] CR2: 0000000000000320 CR3: 000000003b095000 CR4: >>> 0000000000002660 >>> [491154.776380] DR0: 0000000000000000 DR1: 0000000000000000 DR2: >>> 0000000000000000 >>> [491154.777079] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: >>> 0000000000000400 >>> [491154.777770] Process tapdisk2 (pid: 4392, threadinfo >>> ffff88003cd32000, task ffff88003d833c80) >>> [491154.778476] Stack: >>> [491154.778821] ffff88003d8e3c00 0000000000000000 ffff88003ccadb20 >>> 0000000000e5386f >>> [491154.779220] <0> ffff88003cd33e58 ffffffff8128beab 000000003cd33ce8 >>> ffffffff81aab128 >>> [491154.779956] <0> 000000013d743ac0 ffff88003d7439a0 000000019681a000 >>> ffff88003fffc800 >>> [491154.780987] Call Trace: >>> [491154.781334] [<ffffffff8128beab>] blktap_ring_ioctl+0x12d/0x23f >>> [491154.781676] [<ffffffff811d503b>] ? avc_has_perm+0x57/0x69 >>> [491154.782017] [<ffffffff811d6322>] ? inode_has_perm+0x5f/0x61 >>> [491154.782368] [<ffffffff810e13b3>] ? generic_file_aio_write+0x8c/0xa9 >>> [491154.782718] [<ffffffff8111fd46>] vfs_ioctl+0x6a/0x82 >>> [491154.783072] [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9 >>> [491154.783426] [<ffffffff811202df>] sys_ioctl+0x51/0x74 >>> [491154.783781] [<ffffffff8103ccc2>] system_call_fastpath+0x16/0x1b >>> [491154.784142] Code: e6 4c 89 >>> [491154.795155] [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9 >>> >>> >>> >>> >>> >>> -- >>> View this message in context: >> http://xen.1045712.n5.nabble.com/BUG-unable-to-handle-kernel-NULL-pointer-dere >> ference-4-0-1-w-2-6-32-36-tp4432056p4478572.html >>> Sent from the Xen - Dev mailing list archive at Nabble.com. >>> >>> _______________________________________________ >>> Xen-devel mailing list >>> Xen-devel@lists.xensource.com >>> http://lists.xensource.com/xen-devel >> >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Daniel Stodden
2011-Jun-24 20:01 UTC
Re: [Xen-devel] Re: BUG: unable to handle kernel NULL pointer dereference (4.0.1 w/2.6.32.36)
On Fri, 2011-06-24 at 14:25 -0400, Jeremy Fitzhardinge wrote:> On 06/14/2011 01:36 AM, Jan Beulich wrote: > >>>> On 13.06.11 at 02:17, Daniel Stodden <daniel.stodden@citrix.com> wrote: > >> Can you all pull in this one? > >> > >> http://xenbits.xen.org/gitweb/?p=people/dstodden/linux.git;a=commit;h=a76525 > >> 7af7e28c41bd776c3e03615539597eb592 > > Any reason why after several months this still doesn''t appear to be in > > stable-2.6.32, which is what people are generally directed to use? > > Daniel? Should I merge this?Yes! The diff is against drivers/block but it should apply cleanly to device.c. Thanks! Daniel> Thanks, > J > > > Jan > > > >> Likely the one, but let me absolutely know if not. > >> > >> Daniel > >> > >> > >> On Sat, 2011-06-11 at 07:17 -0400, quartex wrote: > >>> I have updated to 2.6.32.41 but it happened again. > >>> > >>> [491154.766766] BUG: unable to handle kernel NULL pointer dereference > >>> at 0000000000000320 > >>> [491154.767477] IP: [<ffffffff8128cbc3>] blktap_device_end_request+0x4a/0x71 > >>> [491154.767844] PGD 3db17067 PUD 3cebe067 PMD 0 > >>> [491154.768219] Oops: 0000 [#1] SMP > >>> [491154.768572] last sysfs file: /sys/devices/vbd-4-51713/statistics/wr_sect > >>> [491154.768942] CPU 3 > >>> [491154.769295] Modules linked in: netconsole [last unloaded: > >>> scsi_wait_scan] > >>> [491154.769683] Pid: 4392, comm: tapdisk2 Not tainted 2.6.32.36 #4 S3420GP > >>> [491154.770056] RIP: e030:[<ffffffff8128cbc3>] [<ffffffff8128cbc3>] > >>> blktap_device_end_request+0x4a/0x71 > >>> [491154.770767] RSP: e02b:ffff88003cd33ca8 EFLAGS: 00010046 > >>> [491154.771133] RAX: 0000000000000000 RBX: ffff88003df60d20 RCX: > >>> 0000000000000000 > >>> [491154.771824] RDX: 00000000000000a1 RSI: 0000000000000001 RDI: > >>> 0000000000000004 > >>> [491154.772524] RBP: ffff88003cd33cc8 R08: 0000000000000000 R09: > >>> ffff88003cd33b08 > >>> [491154.773222] R10: 0000000000000001 R11: ffffffff00001000 R12: > >>> ffff88003ccadb20 > >>> [491154.773915] R13: ffff88003d8e3c00 R14: 0000000000000000 R15: > >>> 0000000000000002 > >>> [491154.774622] FS: 00007f152f810740(0000) GS:ffff88002808f000(0000) > >>> knlGS:0000000000000000 > >>> [491154.775325] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b > >>> [491154.775683] CR2: 0000000000000320 CR3: 000000003b095000 CR4: > >>> 0000000000002660 > >>> [491154.776380] DR0: 0000000000000000 DR1: 0000000000000000 DR2: > >>> 0000000000000000 > >>> [491154.777079] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: > >>> 0000000000000400 > >>> [491154.777770] Process tapdisk2 (pid: 4392, threadinfo > >>> ffff88003cd32000, task ffff88003d833c80) > >>> [491154.778476] Stack: > >>> [491154.778821] ffff88003d8e3c00 0000000000000000 ffff88003ccadb20 > >>> 0000000000e5386f > >>> [491154.779220] <0> ffff88003cd33e58 ffffffff8128beab 000000003cd33ce8 > >>> ffffffff81aab128 > >>> [491154.779956] <0> 000000013d743ac0 ffff88003d7439a0 000000019681a000 > >>> ffff88003fffc800 > >>> [491154.780987] Call Trace: > >>> [491154.781334] [<ffffffff8128beab>] blktap_ring_ioctl+0x12d/0x23f > >>> [491154.781676] [<ffffffff811d503b>] ? avc_has_perm+0x57/0x69 > >>> [491154.782017] [<ffffffff811d6322>] ? inode_has_perm+0x5f/0x61 > >>> [491154.782368] [<ffffffff810e13b3>] ? generic_file_aio_write+0x8c/0xa9 > >>> [491154.782718] [<ffffffff8111fd46>] vfs_ioctl+0x6a/0x82 > >>> [491154.783072] [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9 > >>> [491154.783426] [<ffffffff811202df>] sys_ioctl+0x51/0x74 > >>> [491154.783781] [<ffffffff8103ccc2>] system_call_fastpath+0x16/0x1b > >>> [491154.784142] Code: e6 4c 89 > >>> [491154.795155] [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9 > >>> > >>> > >>> > >>> > >>> > >>> -- > >>> View this message in context: > >> http://xen.1045712.n5.nabble.com/BUG-unable-to-handle-kernel-NULL-pointer-dere > >> ference-4-0-1-w-2-6-32-36-tp4432056p4478572.html > >>> Sent from the Xen - Dev mailing list archive at Nabble.com. > >>> > >>> _______________________________________________ > >>> Xen-devel mailing list > >>> Xen-devel@lists.xensource.com > >>> http://lists.xensource.com/xen-devel > >> > >> > >> _______________________________________________ > >> Xen-devel mailing list > >> Xen-devel@lists.xensource.com > >> http://lists.xensource.com/xen-devel > > > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2011-Jul-01 11:13 UTC
Re: [Xen-devel] Re: BUG: unable to handle kernel NULL pointer dereference (4.0.1 w/2.6.32.36)
On Fri, Jun 24, 2011 at 01:01:54PM -0700, Daniel Stodden wrote:> On Fri, 2011-06-24 at 14:25 -0400, Jeremy Fitzhardinge wrote: > > On 06/14/2011 01:36 AM, Jan Beulich wrote: > > >>>> On 13.06.11 at 02:17, Daniel Stodden <daniel.stodden@citrix.com> wrote: > > >> Can you all pull in this one? > > >> > > >> http://xenbits.xen.org/gitweb/?p=people/dstodden/linux.git;a=commit;h=a76525 > > >> 7af7e28c41bd776c3e03615539597eb592 > > > Any reason why after several months this still doesn''t appear to be in > > > stable-2.6.32, which is what people are generally directed to use? > > > > Daniel? Should I merge this? > > Yes! The diff is against drivers/block but it should apply cleanly to > device.c. Thanks! >Hello, It seems the patch is not yet in xen/next-2.6.32 or xen/stable-2.6.32.x .. -- Pasi> Daniel > > > Thanks, > > J > > > > > Jan > > > > > >> Likely the one, but let me absolutely know if not. > > >> > > >> Daniel > > >> > > >> > > >> On Sat, 2011-06-11 at 07:17 -0400, quartex wrote: > > >>> I have updated to 2.6.32.41 but it happened again. > > >>> > > >>> [491154.766766] BUG: unable to handle kernel NULL pointer dereference > > >>> at 0000000000000320 > > >>> [491154.767477] IP: [<ffffffff8128cbc3>] blktap_device_end_request+0x4a/0x71 > > >>> [491154.767844] PGD 3db17067 PUD 3cebe067 PMD 0 > > >>> [491154.768219] Oops: 0000 [#1] SMP > > >>> [491154.768572] last sysfs file: /sys/devices/vbd-4-51713/statistics/wr_sect > > >>> [491154.768942] CPU 3 > > >>> [491154.769295] Modules linked in: netconsole [last unloaded: > > >>> scsi_wait_scan] > > >>> [491154.769683] Pid: 4392, comm: tapdisk2 Not tainted 2.6.32.36 #4 S3420GP > > >>> [491154.770056] RIP: e030:[<ffffffff8128cbc3>] [<ffffffff8128cbc3>] > > >>> blktap_device_end_request+0x4a/0x71 > > >>> [491154.770767] RSP: e02b:ffff88003cd33ca8 EFLAGS: 00010046 > > >>> [491154.771133] RAX: 0000000000000000 RBX: ffff88003df60d20 RCX: > > >>> 0000000000000000 > > >>> [491154.771824] RDX: 00000000000000a1 RSI: 0000000000000001 RDI: > > >>> 0000000000000004 > > >>> [491154.772524] RBP: ffff88003cd33cc8 R08: 0000000000000000 R09: > > >>> ffff88003cd33b08 > > >>> [491154.773222] R10: 0000000000000001 R11: ffffffff00001000 R12: > > >>> ffff88003ccadb20 > > >>> [491154.773915] R13: ffff88003d8e3c00 R14: 0000000000000000 R15: > > >>> 0000000000000002 > > >>> [491154.774622] FS: 00007f152f810740(0000) GS:ffff88002808f000(0000) > > >>> knlGS:0000000000000000 > > >>> [491154.775325] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b > > >>> [491154.775683] CR2: 0000000000000320 CR3: 000000003b095000 CR4: > > >>> 0000000000002660 > > >>> [491154.776380] DR0: 0000000000000000 DR1: 0000000000000000 DR2: > > >>> 0000000000000000 > > >>> [491154.777079] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: > > >>> 0000000000000400 > > >>> [491154.777770] Process tapdisk2 (pid: 4392, threadinfo > > >>> ffff88003cd32000, task ffff88003d833c80) > > >>> [491154.778476] Stack: > > >>> [491154.778821] ffff88003d8e3c00 0000000000000000 ffff88003ccadb20 > > >>> 0000000000e5386f > > >>> [491154.779220] <0> ffff88003cd33e58 ffffffff8128beab 000000003cd33ce8 > > >>> ffffffff81aab128 > > >>> [491154.779956] <0> 000000013d743ac0 ffff88003d7439a0 000000019681a000 > > >>> ffff88003fffc800 > > >>> [491154.780987] Call Trace: > > >>> [491154.781334] [<ffffffff8128beab>] blktap_ring_ioctl+0x12d/0x23f > > >>> [491154.781676] [<ffffffff811d503b>] ? avc_has_perm+0x57/0x69 > > >>> [491154.782017] [<ffffffff811d6322>] ? inode_has_perm+0x5f/0x61 > > >>> [491154.782368] [<ffffffff810e13b3>] ? generic_file_aio_write+0x8c/0xa9 > > >>> [491154.782718] [<ffffffff8111fd46>] vfs_ioctl+0x6a/0x82 > > >>> [491154.783072] [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9 > > >>> [491154.783426] [<ffffffff811202df>] sys_ioctl+0x51/0x74 > > >>> [491154.783781] [<ffffffff8103ccc2>] system_call_fastpath+0x16/0x1b > > >>> [491154.784142] Code: e6 4c 89 > > >>> [491154.795155] [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9 > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> -- > > >>> View this message in context: > > >> http://xen.1045712.n5.nabble.com/BUG-unable-to-handle-kernel-NULL-pointer-dere > > >> ference-4-0-1-w-2-6-32-36-tp4432056p4478572.html > > >>> Sent from the Xen - Dev mailing list archive at Nabble.com. > > >>> > > >>> _______________________________________________ > > >>> Xen-devel mailing list > > >>> Xen-devel@lists.xensource.com > > >>> http://lists.xensource.com/xen-devel > > >> > > >> > > >> _______________________________________________ > > >> Xen-devel mailing list > > >> Xen-devel@lists.xensource.com > > >> http://lists.xensource.com/xen-devel > > > > > > > > > > > > _______________________________________________ > > > Xen-devel mailing list > > > Xen-devel@lists.xensource.com > > > http://lists.xensource.com/xen-devel > > > > > > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Daniel Stodden
2011-Jul-01 18:08 UTC
Re: [Xen-devel] Re: BUG: unable to handle kernel NULL pointer dereference (4.0.1 w/2.6.32.36)
On Fri, 2011-07-01 at 07:13 -0400, Pasi Kärkkäinen wrote:> On Fri, Jun 24, 2011 at 01:01:54PM -0700, Daniel Stodden wrote: > > On Fri, 2011-06-24 at 14:25 -0400, Jeremy Fitzhardinge wrote: > > > On 06/14/2011 01:36 AM, Jan Beulich wrote: > > > >>>> On 13.06.11 at 02:17, Daniel Stodden <daniel.stodden@citrix.com> wrote: > > > >> Can you all pull in this one? > > > >> > > > >> http://xenbits.xen.org/gitweb/?p=people/dstodden/linux.git;a=commit;h=a76525 > > > >> 7af7e28c41bd776c3e03615539597eb592 > > > > Any reason why after several months this still doesn''t appear to be in > > > > stable-2.6.32, which is what people are generally directed to use? > > > > > > Daniel? Should I merge this? > > > > Yes! The diff is against drivers/block but it should apply cleanly to > > device.c. Thanks! > > > > Hello, > > It seems the patch is not yet in xen/next-2.6.32 or xen/stable-2.6.32.x ..Yeah, Jeremy asked for a merge request against that tree... Daniel> -- Pasi > > > > Daniel > > > > > Thanks, > > > J > > > > > > > Jan > > > > > > > >> Likely the one, but let me absolutely know if not. > > > >> > > > >> Daniel > > > >> > > > >> > > > >> On Sat, 2011-06-11 at 07:17 -0400, quartex wrote: > > > >>> I have updated to 2.6.32.41 but it happened again. > > > >>> > > > >>> [491154.766766] BUG: unable to handle kernel NULL pointer dereference > > > >>> at 0000000000000320 > > > >>> [491154.767477] IP: [<ffffffff8128cbc3>] blktap_device_end_request+0x4a/0x71 > > > >>> [491154.767844] PGD 3db17067 PUD 3cebe067 PMD 0 > > > >>> [491154.768219] Oops: 0000 [#1] SMP > > > >>> [491154.768572] last sysfs file: /sys/devices/vbd-4-51713/statistics/wr_sect > > > >>> [491154.768942] CPU 3 > > > >>> [491154.769295] Modules linked in: netconsole [last unloaded: > > > >>> scsi_wait_scan] > > > >>> [491154.769683] Pid: 4392, comm: tapdisk2 Not tainted 2.6.32.36 #4 S3420GP > > > >>> [491154.770056] RIP: e030:[<ffffffff8128cbc3>] [<ffffffff8128cbc3>] > > > >>> blktap_device_end_request+0x4a/0x71 > > > >>> [491154.770767] RSP: e02b:ffff88003cd33ca8 EFLAGS: 00010046 > > > >>> [491154.771133] RAX: 0000000000000000 RBX: ffff88003df60d20 RCX: > > > >>> 0000000000000000 > > > >>> [491154.771824] RDX: 00000000000000a1 RSI: 0000000000000001 RDI: > > > >>> 0000000000000004 > > > >>> [491154.772524] RBP: ffff88003cd33cc8 R08: 0000000000000000 R09: > > > >>> ffff88003cd33b08 > > > >>> [491154.773222] R10: 0000000000000001 R11: ffffffff00001000 R12: > > > >>> ffff88003ccadb20 > > > >>> [491154.773915] R13: ffff88003d8e3c00 R14: 0000000000000000 R15: > > > >>> 0000000000000002 > > > >>> [491154.774622] FS: 00007f152f810740(0000) GS:ffff88002808f000(0000) > > > >>> knlGS:0000000000000000 > > > >>> [491154.775325] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b > > > >>> [491154.775683] CR2: 0000000000000320 CR3: 000000003b095000 CR4: > > > >>> 0000000000002660 > > > >>> [491154.776380] DR0: 0000000000000000 DR1: 0000000000000000 DR2: > > > >>> 0000000000000000 > > > >>> [491154.777079] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: > > > >>> 0000000000000400 > > > >>> [491154.777770] Process tapdisk2 (pid: 4392, threadinfo > > > >>> ffff88003cd32000, task ffff88003d833c80) > > > >>> [491154.778476] Stack: > > > >>> [491154.778821] ffff88003d8e3c00 0000000000000000 ffff88003ccadb20 > > > >>> 0000000000e5386f > > > >>> [491154.779220] <0> ffff88003cd33e58 ffffffff8128beab 000000003cd33ce8 > > > >>> ffffffff81aab128 > > > >>> [491154.779956] <0> 000000013d743ac0 ffff88003d7439a0 000000019681a000 > > > >>> ffff88003fffc800 > > > >>> [491154.780987] Call Trace: > > > >>> [491154.781334] [<ffffffff8128beab>] blktap_ring_ioctl+0x12d/0x23f > > > >>> [491154.781676] [<ffffffff811d503b>] ? avc_has_perm+0x57/0x69 > > > >>> [491154.782017] [<ffffffff811d6322>] ? inode_has_perm+0x5f/0x61 > > > >>> [491154.782368] [<ffffffff810e13b3>] ? generic_file_aio_write+0x8c/0xa9 > > > >>> [491154.782718] [<ffffffff8111fd46>] vfs_ioctl+0x6a/0x82 > > > >>> [491154.783072] [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9 > > > >>> [491154.783426] [<ffffffff811202df>] sys_ioctl+0x51/0x74 > > > >>> [491154.783781] [<ffffffff8103ccc2>] system_call_fastpath+0x16/0x1b > > > >>> [491154.784142] Code: e6 4c 89 > > > >>> [491154.795155] [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9 > > > >>> > > > >>> > > > >>> > > > >>> > > > >>> > > > >>> -- > > > >>> View this message in context: > > > >> http://xen.1045712.n5.nabble.com/BUG-unable-to-handle-kernel-NULL-pointer-dere > > > >> ference-4-0-1-w-2-6-32-36-tp4432056p4478572.html > > > >>> Sent from the Xen - Dev mailing list archive at Nabble.com. > > > >>> > > > >>> _______________________________________________ > > > >>> Xen-devel mailing list > > > >>> Xen-devel@lists.xensource.com > > > >>> http://lists.xensource.com/xen-devel > > > >> > > > >> > > > >> _______________________________________________ > > > >> Xen-devel mailing list > > > >> Xen-devel@lists.xensource.com > > > >> http://lists.xensource.com/xen-devel > > > > > > > > > > > > > > > > _______________________________________________ > > > > Xen-devel mailing list > > > > Xen-devel@lists.xensource.com > > > > http://lists.xensource.com/xen-devel > > > > > > > > > > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2011-Jul-19 12:47 UTC
Re: [Xen-devel] Re: BUG: unable to handle kernel NULL pointer dereference (4.0.1 w/2.6.32.36)
On Fri, Jul 01, 2011 at 02:13:14PM +0300, Pasi Kärkkäinen wrote:> On Fri, Jun 24, 2011 at 01:01:54PM -0700, Daniel Stodden wrote: > > On Fri, 2011-06-24 at 14:25 -0400, Jeremy Fitzhardinge wrote: > > > On 06/14/2011 01:36 AM, Jan Beulich wrote: > > > >>>> On 13.06.11 at 02:17, Daniel Stodden <daniel.stodden@citrix.com> wrote: > > > >> Can you all pull in this one? > > > >> > > > >> http://xenbits.xen.org/gitweb/?p=people/dstodden/linux.git;a=commit;h=a76525 > > > >> 7af7e28c41bd776c3e03615539597eb592 > > > > Any reason why after several months this still doesn''t appear to be in > > > > stable-2.6.32, which is what people are generally directed to use? > > > > > > Daniel? Should I merge this? > > > > Yes! The diff is against drivers/block but it should apply cleanly to > > device.c. Thanks! > > > > Hello, > > It seems the patch is not yet in xen/next-2.6.32 or xen/stable-2.6.32.x .. >Jeremy: ping? -- Pasi> > > > Daniel > > > > > Thanks, > > > J > > > > > > > Jan > > > > > > > >> Likely the one, but let me absolutely know if not. > > > >> > > > >> Daniel > > > >> > > > >> > > > >> On Sat, 2011-06-11 at 07:17 -0400, quartex wrote: > > > >>> I have updated to 2.6.32.41 but it happened again. > > > >>> > > > >>> [491154.766766] BUG: unable to handle kernel NULL pointer dereference > > > >>> at 0000000000000320 > > > >>> [491154.767477] IP: [<ffffffff8128cbc3>] blktap_device_end_request+0x4a/0x71 > > > >>> [491154.767844] PGD 3db17067 PUD 3cebe067 PMD 0 > > > >>> [491154.768219] Oops: 0000 [#1] SMP > > > >>> [491154.768572] last sysfs file: /sys/devices/vbd-4-51713/statistics/wr_sect > > > >>> [491154.768942] CPU 3 > > > >>> [491154.769295] Modules linked in: netconsole [last unloaded: > > > >>> scsi_wait_scan] > > > >>> [491154.769683] Pid: 4392, comm: tapdisk2 Not tainted 2.6.32.36 #4 S3420GP > > > >>> [491154.770056] RIP: e030:[<ffffffff8128cbc3>] [<ffffffff8128cbc3>] > > > >>> blktap_device_end_request+0x4a/0x71 > > > >>> [491154.770767] RSP: e02b:ffff88003cd33ca8 EFLAGS: 00010046 > > > >>> [491154.771133] RAX: 0000000000000000 RBX: ffff88003df60d20 RCX: > > > >>> 0000000000000000 > > > >>> [491154.771824] RDX: 00000000000000a1 RSI: 0000000000000001 RDI: > > > >>> 0000000000000004 > > > >>> [491154.772524] RBP: ffff88003cd33cc8 R08: 0000000000000000 R09: > > > >>> ffff88003cd33b08 > > > >>> [491154.773222] R10: 0000000000000001 R11: ffffffff00001000 R12: > > > >>> ffff88003ccadb20 > > > >>> [491154.773915] R13: ffff88003d8e3c00 R14: 0000000000000000 R15: > > > >>> 0000000000000002 > > > >>> [491154.774622] FS: 00007f152f810740(0000) GS:ffff88002808f000(0000) > > > >>> knlGS:0000000000000000 > > > >>> [491154.775325] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b > > > >>> [491154.775683] CR2: 0000000000000320 CR3: 000000003b095000 CR4: > > > >>> 0000000000002660 > > > >>> [491154.776380] DR0: 0000000000000000 DR1: 0000000000000000 DR2: > > > >>> 0000000000000000 > > > >>> [491154.777079] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: > > > >>> 0000000000000400 > > > >>> [491154.777770] Process tapdisk2 (pid: 4392, threadinfo > > > >>> ffff88003cd32000, task ffff88003d833c80) > > > >>> [491154.778476] Stack: > > > >>> [491154.778821] ffff88003d8e3c00 0000000000000000 ffff88003ccadb20 > > > >>> 0000000000e5386f > > > >>> [491154.779220] <0> ffff88003cd33e58 ffffffff8128beab 000000003cd33ce8 > > > >>> ffffffff81aab128 > > > >>> [491154.779956] <0> 000000013d743ac0 ffff88003d7439a0 000000019681a000 > > > >>> ffff88003fffc800 > > > >>> [491154.780987] Call Trace: > > > >>> [491154.781334] [<ffffffff8128beab>] blktap_ring_ioctl+0x12d/0x23f > > > >>> [491154.781676] [<ffffffff811d503b>] ? avc_has_perm+0x57/0x69 > > > >>> [491154.782017] [<ffffffff811d6322>] ? inode_has_perm+0x5f/0x61 > > > >>> [491154.782368] [<ffffffff810e13b3>] ? generic_file_aio_write+0x8c/0xa9 > > > >>> [491154.782718] [<ffffffff8111fd46>] vfs_ioctl+0x6a/0x82 > > > >>> [491154.783072] [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9 > > > >>> [491154.783426] [<ffffffff811202df>] sys_ioctl+0x51/0x74 > > > >>> [491154.783781] [<ffffffff8103ccc2>] system_call_fastpath+0x16/0x1b > > > >>> [491154.784142] Code: e6 4c 89 > > > >>> [491154.795155] [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9 > > > >>> > > > >>> > > > >>> > > > >>> > > > >>> > > > >>> -- > > > >>> View this message in context: > > > >> http://xen.1045712.n5.nabble.com/BUG-unable-to-handle-kernel-NULL-pointer-dere > > > >> ference-4-0-1-w-2-6-32-36-tp4432056p4478572.html > > > >>> Sent from the Xen - Dev mailing list archive at Nabble.com. > > > >>> > > > >>> _______________________________________________ > > > >>> Xen-devel mailing list > > > >>> Xen-devel@lists.xensource.com > > > >>> http://lists.xensource.com/xen-devel > > > >> > > > >> > > > >> _______________________________________________ > > > >> Xen-devel mailing list > > > >> Xen-devel@lists.xensource.com > > > >> http://lists.xensource.com/xen-devel > > > > > > > > > > > > > > > > _______________________________________________ > > > > Xen-devel mailing list > > > > Xen-devel@lists.xensource.com > > > > http://lists.xensource.com/xen-devel > > > > > > > > > > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Daniel Stodden
2011-Jul-19 17:01 UTC
Re: [Xen-devel] Re: BUG: unable to handle kernel NULL pointer dereference (4.0.1 w/2.6.32.36)
On Tue, 2011-07-19 at 08:47 -0400, Pasi Kärkkäinen wrote:> On Fri, Jul 01, 2011 at 02:13:14PM +0300, Pasi Kärkkäinen wrote: > > On Fri, Jun 24, 2011 at 01:01:54PM -0700, Daniel Stodden wrote: > > > On Fri, 2011-06-24 at 14:25 -0400, Jeremy Fitzhardinge wrote: > > > > On 06/14/2011 01:36 AM, Jan Beulich wrote: > > > > >>>> On 13.06.11 at 02:17, Daniel Stodden <daniel.stodden@citrix.com> wrote: > > > > >> Can you all pull in this one? > > > > >> > > > > >> http://xenbits.xen.org/gitweb/?p=people/dstodden/linux.git;a=commit;h=a76525 > > > > >> 7af7e28c41bd776c3e03615539597eb592 > > > > > Any reason why after several months this still doesn''t appear to be in > > > > > stable-2.6.32, which is what people are generally directed to use? > > > > > > > > Daniel? Should I merge this? > > > > > > Yes! The diff is against drivers/block but it should apply cleanly to > > > device.c. Thanks! > > > > > > > Hello, > > > > It seems the patch is not yet in xen/next-2.6.32 or xen/stable-2.6.32.x .. > > > > Jeremy: ping?...Pong. Jeremy: please pull upstream/xen/dom0/backend/blktap2 from git://xenbits.xensource.com/people/dstodden/linux.git Daniel> -- Pasi > > > > > > > > Daniel > > > > > > > Thanks, > > > > J > > > > > > > > > Jan > > > > > > > > > >> Likely the one, but let me absolutely know if not. > > > > >> > > > > >> Daniel > > > > >> > > > > >> > > > > >> On Sat, 2011-06-11 at 07:17 -0400, quartex wrote: > > > > >>> I have updated to 2.6.32.41 but it happened again. > > > > >>> > > > > >>> [491154.766766] BUG: unable to handle kernel NULL pointer dereference > > > > >>> at 0000000000000320 > > > > >>> [491154.767477] IP: [<ffffffff8128cbc3>] blktap_device_end_request+0x4a/0x71 > > > > >>> [491154.767844] PGD 3db17067 PUD 3cebe067 PMD 0 > > > > >>> [491154.768219] Oops: 0000 [#1] SMP > > > > >>> [491154.768572] last sysfs file: /sys/devices/vbd-4-51713/statistics/wr_sect > > > > >>> [491154.768942] CPU 3 > > > > >>> [491154.769295] Modules linked in: netconsole [last unloaded: > > > > >>> scsi_wait_scan] > > > > >>> [491154.769683] Pid: 4392, comm: tapdisk2 Not tainted 2.6.32.36 #4 S3420GP > > > > >>> [491154.770056] RIP: e030:[<ffffffff8128cbc3>] [<ffffffff8128cbc3>] > > > > >>> blktap_device_end_request+0x4a/0x71 > > > > >>> [491154.770767] RSP: e02b:ffff88003cd33ca8 EFLAGS: 00010046 > > > > >>> [491154.771133] RAX: 0000000000000000 RBX: ffff88003df60d20 RCX: > > > > >>> 0000000000000000 > > > > >>> [491154.771824] RDX: 00000000000000a1 RSI: 0000000000000001 RDI: > > > > >>> 0000000000000004 > > > > >>> [491154.772524] RBP: ffff88003cd33cc8 R08: 0000000000000000 R09: > > > > >>> ffff88003cd33b08 > > > > >>> [491154.773222] R10: 0000000000000001 R11: ffffffff00001000 R12: > > > > >>> ffff88003ccadb20 > > > > >>> [491154.773915] R13: ffff88003d8e3c00 R14: 0000000000000000 R15: > > > > >>> 0000000000000002 > > > > >>> [491154.774622] FS: 00007f152f810740(0000) GS:ffff88002808f000(0000) > > > > >>> knlGS:0000000000000000 > > > > >>> [491154.775325] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b > > > > >>> [491154.775683] CR2: 0000000000000320 CR3: 000000003b095000 CR4: > > > > >>> 0000000000002660 > > > > >>> [491154.776380] DR0: 0000000000000000 DR1: 0000000000000000 DR2: > > > > >>> 0000000000000000 > > > > >>> [491154.777079] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: > > > > >>> 0000000000000400 > > > > >>> [491154.777770] Process tapdisk2 (pid: 4392, threadinfo > > > > >>> ffff88003cd32000, task ffff88003d833c80) > > > > >>> [491154.778476] Stack: > > > > >>> [491154.778821] ffff88003d8e3c00 0000000000000000 ffff88003ccadb20 > > > > >>> 0000000000e5386f > > > > >>> [491154.779220] <0> ffff88003cd33e58 ffffffff8128beab 000000003cd33ce8 > > > > >>> ffffffff81aab128 > > > > >>> [491154.779956] <0> 000000013d743ac0 ffff88003d7439a0 000000019681a000 > > > > >>> ffff88003fffc800 > > > > >>> [491154.780987] Call Trace: > > > > >>> [491154.781334] [<ffffffff8128beab>] blktap_ring_ioctl+0x12d/0x23f > > > > >>> [491154.781676] [<ffffffff811d503b>] ? avc_has_perm+0x57/0x69 > > > > >>> [491154.782017] [<ffffffff811d6322>] ? inode_has_perm+0x5f/0x61 > > > > >>> [491154.782368] [<ffffffff810e13b3>] ? generic_file_aio_write+0x8c/0xa9 > > > > >>> [491154.782718] [<ffffffff8111fd46>] vfs_ioctl+0x6a/0x82 > > > > >>> [491154.783072] [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9 > > > > >>> [491154.783426] [<ffffffff811202df>] sys_ioctl+0x51/0x74 > > > > >>> [491154.783781] [<ffffffff8103ccc2>] system_call_fastpath+0x16/0x1b > > > > >>> [491154.784142] Code: e6 4c 89 > > > > >>> [491154.795155] [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9 > > > > >>> > > > > >>> > > > > >>> > > > > >>> > > > > >>> > > > > >>> -- > > > > >>> View this message in context: > > > > >> http://xen.1045712.n5.nabble.com/BUG-unable-to-handle-kernel-NULL-pointer-dere > > > > >> ference-4-0-1-w-2-6-32-36-tp4432056p4478572.html > > > > >>> Sent from the Xen - Dev mailing list archive at Nabble.com. > > > > >>> > > > > >>> _______________________________________________ > > > > >>> Xen-devel mailing list > > > > >>> Xen-devel@lists.xensource.com > > > > >>> http://lists.xensource.com/xen-devel > > > > >> > > > > >> > > > > >> _______________________________________________ > > > > >> Xen-devel mailing list > > > > >> Xen-devel@lists.xensource.com > > > > >> http://lists.xensource.com/xen-devel > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > Xen-devel mailing list > > > > > Xen-devel@lists.xensource.com > > > > > http://lists.xensource.com/xen-devel > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Xen-devel mailing list > > > Xen-devel@lists.xensource.com > > > http://lists.xensource.com/xen-devel > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Daniel Stodden
2011-Jul-19 17:03 UTC
Re: [Xen-devel] Re: BUG: unable to handle kernel NULL pointer dereference (4.0.1 w/2.6.32.36)
On Tue, 2011-07-19 at 13:01 -0400, Daniel Stodden wrote:> On Tue, 2011-07-19 at 08:47 -0400, Pasi Kärkkäinen wrote: > > On Fri, Jul 01, 2011 at 02:13:14PM +0300, Pasi Kärkkäinen wrote: > > > On Fri, Jun 24, 2011 at 01:01:54PM -0700, Daniel Stodden wrote: > > > > On Fri, 2011-06-24 at 14:25 -0400, Jeremy Fitzhardinge wrote: > > > > > On 06/14/2011 01:36 AM, Jan Beulich wrote: > > > > > >>>> On 13.06.11 at 02:17, Daniel Stodden <daniel.stodden@citrix.com> wrote: > > > > > >> Can you all pull in this one? > > > > > >> > > > > > >> http://xenbits.xen.org/gitweb/?p=people/dstodden/linux.git;a=commit;h=a76525 > > > > > >> 7af7e28c41bd776c3e03615539597eb592 > > > > > > Any reason why after several months this still doesn''t appear to be in > > > > > > stable-2.6.32, which is what people are generally directed to use? > > > > > > > > > > Daniel? Should I merge this? > > > > > > > > Yes! The diff is against drivers/block but it should apply cleanly to > > > > device.c. Thanks! > > > > > > > > > > Hello, > > > > > > It seems the patch is not yet in xen/next-2.6.32 or xen/stable-2.6.32.x .. > > > > > > > Jeremy: ping? > > ...Pong. > > Jeremy: please pull upstream/xen/dom0/backend/blktap2 from > git://xenbits.xensource.com/people/dstodden/linux.git > > Daniel[Following up, just to get that Pasi@citrix.com out of the CC list, :-)] Excuse me, Daniel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel