[arch-general] [signoff] kernel26-2.6.37.3-1 BUG: unable to handle kernel paging request

[David C. Rankin]

On 03/08/2011 06:25 AM, Tobias Powalowski wrote:
> Hi guys,
> - bump to latest version
>
> greetings
> tpowa

tpowa I am seeing a kernel bug with 2.6.37.3-1. I can't read these things, but 
here is what I got:

00:08 nirvana:/srv/http/dl/dt/trinity/arch> cat ~/tmp/Documents/kernel-bug.txt
Mar 11 23:32:26 trinity kernel: BUG: unable to handle kernel paging request at 
00f4ea92
Mar 11 23:32:26 trinity kernel: IP: [<fa01eab2>] vboxCallCreate+0x42/0x90 [vboxsf]
Mar 11 23:32:26 trinity kernel: *pde = 00000000
Mar 11 23:32:26 trinity kernel: Oops: 0000 [#4] PREEMPT SMP
Mar 11 23:32:26 trinity kernel: last sysfs file: 
/sys/devices/virtual/vtconsole/vtcon1/uevent
Mar 11 23:32:26 trinity kernel: Modules linked in: ipv6 vboxsf ext2 joydev 
usbhid hid snd_seq_dummy snd_seq_oss ohci_hcd snd_seq_midi_event snd_seq 
snd_seq_device snd_pcm_oss snd_intel8x0 snd_mixer_oss snd_ac97_codec ac97_bus 
ppdev ehci_hcd snd_pcm parport_pc snd_timer usbcore i2c_piix4 e1000 snd battery 
lp ac soundcore button sg psmouse i2c_core evdev snd_page_alloc parport pcspkr 
serio_raw vboxguest ext3 jbd mbcache sd_mod sr_mod cdrom pata_acpi ahci libahci 
ata_piix libata scsi_mod
Mar 11 23:32:26 trinity kernel:
Mar 11 23:32:26 trinity kernel: Pid: 1432, comm: pacman Tainted: G      D W 
2.6.37-ARCH #1 innotek GmbH VirtualBox
Mar 11 23:32:26 trinity kernel: EIP: 0060:[<fa01eab2>] EFLAGS: 00010202 CPU: 0
Mar 11 23:32:26 trinity kernel: EIP is at vboxCallCreate+0x42/0x90 [vboxsf]
Mar 11 23:32:26 trinity kernel: EAX: 00f4ea92 EBX: 00f4ea92 ECX: 00000000 EDX: 
fa020b00
Mar 11 23:32:26 trinity kernel: ESI: f5fadc00 EDI: f4e25da8 EBP: f4e25d24 ESP: 
f4e25ce4
Mar 11 23:32:26 trinity kernel: DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Mar 11 23:32:26 trinity kernel: Process pacman (pid: 1432, ti=f4e24000 
task=f4d3af70 task.ti=f4e24000)
Mar 11 23:32:26 trinity kernel: Stack:
Mar 11 23:32:26 trinity kernel: fa020cc8 f4e25cf0 00000034 00000000 0000000a 
00000003 00000003 00000001
Mar 11 23:32:26 trinity kernel: 00000000 f60880b0 00000004 0000000e f548b9d0 
00000004 0000006c f4e25d3c
Mar 11 23:32:26 trinity kernel: f4e25db4 fa01cae3 fa020b00 f5fadc00 00f4ea92 
f4e25d3c 00000000 00000000
Mar 11 23:32:26 trinity kernel: Call Trace:
Mar 11 23:32:26 trinity kernel: [<fa01cae3>] ? sf_stat+0x43/0xe0 [vboxsf]
Mar 11 23:32:26 trinity kernel: [<fa01cc04>] ? sf_inode_revalidate+0x84/0xb0 
[vboxsf]
Mar 11 23:32:26 trinity kernel: [<c1116af7>] ? __d_lookup+0x117/0x130
Mar 11 23:32:26 trinity kernel: [<fa01cc38>] ? sf_dentry_revalidate+0x8/0x20 
[vboxsf]
Mar 11 23:32:26 trinity kernel: [<c110d0c9>] ? do_lookup+0x59/0x110
Mar 11 23:32:26 trinity kernel: [<c110cc78>] ? acl_permission_check+0x48/0xa0
Mar 11 23:32:26 trinity kernel: [<c110e879>] ? link_path_walk+0xe9/0x8f0
Mar 11 23:32:26 trinity kernel: [<c110ff61>] ? do_filp_open+0x111/0x510
Mar 11 23:32:26 trinity kernel: [<c1028530>] ? do_page_fault+0x0/0x430
Mar 11 23:32:26 trinity kernel: [<c111a2eb>] ? alloc_fd+0x9b/0xe0
Mar 11 23:32:26 trinity kernel: [<c11031a5>] ? do_sys_open+0x55/0xf0
Mar 11 23:32:26 trinity kernel: [<c1103269>] ? sys_open+0x29/0x40
Mar 11 23:32:26 trinity kernel: [<c100391f>] ? sysenter_do_call+0x12/0x28
Mar 11 23:32:26 trinity kernel: Code: 00 00 00 8b 0a c7 45 d8 03 00 00 00 c7 45 
dc 01 00 00 00 c7 45 e8 04 00 00 00 89 4d d0 8b 4d 0c 8b 09 89 4d e0 31 c9 85 c0 
74 06 <0f> b7 08 83 c1 04 89 45 f0 8b 45 14 c7 44 24 08 34 00 00 00 89
Mar 11 23:32:26 trinity kernel: EIP: [<fa01eab2>] vboxCallCreate+0x42/0x90 
[vboxsf] SS:ESP 0068:f4e25ce4
Mar 11 23:32:26 trinity kernel: CR2: 0000000000f4ea92
Mar 11 23:32:26 trinity kernel: ---[ end trace 6cb72bf9a72b8e7a ]---

This is Arch i686 running as a guest in the latest virtualbox. This crash seems 
to occur when you try any type of I/O that goes out of the machine. Like rsync 
or trying to access one of the shared folders.

I downgraded the guest VM to -2.6.37.2-1 and the problem is gone. Let me know 
what other information you want to see.

I have also seen some strange behavior in x86_64 dmraid. I thought it might be a 
disk problem, but it started about the time of the kernel upgrade as well.

Cheers.

-- 
David C. Rankin, J.D.,P.E.