random crashes caused by Xen kernel bug (radix-tree.c)

The Hardy Heron kernel was recently uploaded for testing. We'd really appreciate it if you could try testing with this newer kernel and verify if this issue still exists. Unfortunately, the Hardy Heron Alpha1 LiveCD was released with the older 2.6.22 kernel. You'll have to manually install the newer Hardy Heron kernel in order to test. This should not be the case for Alpha2. However, here are the instructions to install (if you choose to do so):

1) edit the file /etc/apt/sources.list and add the following line:

deb http://archive.ubuntu.com/ubuntu hardy main restricted

2) sudo apt-get update
3) sudo apt-get install linux-image-2.6.24-1-generic
4) reboot and select the new kernel from the grub menu

After you've tested, please feel free to revert back - ie boot into the old kernel, sudo apt-get remove linux-image-2.6.24-1-generic, and remove the line from /etc/apt/sources.list . Please update this report with your results. Thanks in advance!

Similar oops with 2.6.22-14, in domU with XEN :

exact version of kernel :
kernel: [ 0.000000] Linux version 2.6.22-14-xen (buildd@palmer) (gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Mon Oct 15 00:35:38 GMT 2007 (Unofficial)

I do not see XEN kernel made for 2.6.24 ? , as requested in last comment

[245619.262174] BUG: unable to handle kernel paging request at virtual address 00100100
[245619.262191] printing eip:
[245619.262194] c019d6b1
[245619.262203] 0102e000 -> *pde = 00000000:1577f001
[245619.262207] 04338000 -> *pme = 00000000:00000000
[245619.262214] Oops: 0000 [#1]
[245619.262216] SMP
[245619.262223] Modules linked in: reiserfs dm_mirror dm_snapshot dm_mod fuse apparmor commoncap
[245619.262242] CPU: 0
[245619.262243] EIP: 0061:[<c019d6b1>] Not tainted VLI
[245619.262244] EFLAGS: 00010297 (2.6.22-14-xen #1)
[245619.262258] EIP is at __block_write_full_page+0xe1/0x360
[245619.262262] eax: c16a1180 ebx: 00100100 ecx: 00000000 edx: 0000000c
[245619.262266] esi: 00000ee1 edi: 00000000 ebp: c17963f0 esp: c46bfde4
[245619.262272] ds: 007b es: 007b fs: 00d8 gs: 0000 ss: 0069
[245619.262277] Process pdflush (pid: 26176, ti=c46be000 task=cae979f0 task.ti=c46be000)
[245619.262282] Stack: 00000110 00000110 c46bfe88 c745c6f0 c01a1d30 c16a1180 00000000 0013ffff
[245619.262298] 00000000 c162c2f4 00001000 00000001 c17963f0 c16a1180 00000000 c019da27
[245619.262313] c46bff70 00000000 c46bff70 c01a1d30 c16a1180 c1796494 0000000b c46bff70
[245619.262330] Call Trace:
[245619.262335] [<c01a1d30>] blkdev_get_block+0x0/0x70
[245619.262346] [<c019da27>] block_write_full_page+0xf7/0x100
[245619.262351] [<c01a1d30>] blkdev_get_block+0x0/0x70
[245619.262357] [<c0157a38>] __writepage+0x8/0x30
[245619.262364] [<c0157ef4>] write_cache_pages+0x214/0x310
[245619.262370] [<c0157a30>] __writepage+0x0/0x30
[245619.262377] [<c0158010>] generic_writepages+0x20/0x30
[245619.262384] [<c015804b>] do_writepages+0x2b/0x50
[245619.262389] [<c01980c3>] __writeback_single_inode+0x93/0x3c0
[245619.262401] [<c02ff1f6>] schedule+0x356/0x900
[245619.262410] [<c019877e>] sync_sb_inodes+0x17e/0x240
[245619.262416] [<c0198c49>] writeback_inodes+0x99/0xd0
[245619.262423] [<c0158715>] wb_kupdate+0x85/0xf0
[245619.262429] [<c0158ab0>] pdflush+0x0/0x260
[245619.262434] [<c0158bf8>] pdflush+0x148/0x260
[245619.262441] [<c0158690>] wb_kupdate+0x0/0xf0
[245619.262447] [<c0136312>] kthread+0x42/0x70
[245619.262454] [<c01362d0>] kthread+0x0/0x70
[245619.262461] [<c0105927>] kernel_thread_helper+0x7/0x10
[245619.262469] =======================
[245619.262471] Code: 24 24 eb 21 77 06 3b 74 24 1c 76 1f 90 0f ba 33 01 90 0f ba 2b 00 8b 5b 04 39 5c 24 24 74 68 83 c6 01 83 d7 0 0 3b 7c 24 20 73 d9 <8b> 03 a8 20 75 e5 8b 03 a8 02 74 df 8b 54 24 28 3b 53 14 0f 85
[245619.262563] EIP: [<c019d6b1>] __block_write_full_page+0xe1/0x360 SS:ESP 0069:c46bfde4

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

I had exactly the same bug on a 2.6.24-17-xen kernel, except error is at line 460
It seems that renaming /lib/tls in /lib/tls.disabled solved the problem, but after I had the
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/229033 bug
seem to be solved by "blacklist ipv6" in /etc/modprobe.d/blacklist .
I could reproduce the bug easily just by stressing the dom0 with 2 concurrents debuild, one on kernel package, one on xen-tools

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

This bug was reported a while ago but there hasn't been any recent comments or updates. Is this still an issue with the latest pre-release of Jaunty 9.04? Refer to http://www.ubuntu.com/testing/jaunty/beta . Please let us know.

Also, this seems to be specific to Xen.

The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
linux-source-2.6.22 kernel task. It would be helpful if you could test the
new Jaunty Jackalope 9.04 release and confirm if this issue remains -
http://www.ubuntu.com/getubuntu/releasenotes/904overview. If the issue still exists with the Jaunty
release, please update this report by changing the Status of the "linux (Ubuntu)"
task from "Incomplete" to "New". Also please be sure to run the command below
which will automatically gather and attach updated debug information to this
report. Thanks in advance.

apport-collect -p linux-image-2.6.28-11-generic 172632

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.