Ubuntu
linux-source-2.6.20 package

kernel bug: unable to handle kernel paging request

Bug #120842 reported by Ruben Garcia
124
This bug affects 27 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6.20-16-generic

I'm getting some oopses under memory pressure.

[44736.452000] BUG: unable to handle kernel paging request at virtual address fadb0f0c
[44736.452000] printing eip:
[44736.452000] c01601e3
[44736.452000] *pde = 00000000
[44736.452000] Oops: 0000 [#1]
[44736.452000] SMP
[44736.452000] Modules linked in: snd_rtctimer cbc blkcipher binfmt_misc rfcomm l2cap bluetooth ppdev powernow_k8 cpufreq_conservative cpufreq_ondemand cpufreq_userspace cpufreq_stats cpufreq_powersave freq_table dev_acpi pcc_acpi sony_acpi tc1100_wmi sbs i2c_ec asus_acpi container ac button battery dock video backlight af_packet dm_crypt dm_mod aes lp fuse snd_via82xx_modem snd_via82xx gameport snd_ac97_codec ac97_bus snd_mpu401_uart snd_bt87x snd_pcm_oss snd_mixer_oss psmouse serio_raw snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_seq_device snd_pcm snd_timer bt878 pcspkr parport_pc parport i2c_viapro k8temp snd shpchp sk98lin tuner bttv soundcore snd_page_alloc video_buf ir_common compat_ioctl32 i2c_algo_bit btcx_risc tveeprom i2c_core pci_hotplug amd64_agp agpgart videodev v4l2_common v4l1_compat tsdev evdev ipv6 ext3 jbd mbcache ide_cd cdrom ide_disk via82cxxx generic ehci_hcd skge uhci_hcd usbcore ata_generic sata_via libata scsi_mod thermal processor fan fbcon tileblit font bitblit softcursor vesafb capability commoncap
[44736.452000] CPU: 0
[44736.452000] EIP: 0060:[<c01601e3>] Not tainted VLI
[44736.452000] EFLAGS: 00010282 (2.6.20-16-generic #2)
[44736.452000] EIP is at shrink_inactive_list+0x733/0x870
[44736.452000] eax: 40000809 ebx: c1508660 ecx: fadb0ef4 edx: fadb0ef4
[44736.452000] esi: c03aa280 edi: 00000001 ebp: c1508678 esp: c1931e10
[44736.452000] ds: 007b es: 007b ss: 0068
[44736.452000] Process kswapd0 (pid: 154, ti=c1930000 task=df88d030 task.ti=c1930000)
[44736.452000] Stack: c1931f08 c0429ce0 c1931ef8 c1931f00 c03aa80c c03aa800 c1931f78 00000020
[44736.452000] 00000000 00000000 00000020 00000007 00000001 dadb0ef4 00000000 00000020
[44736.452000] 00000007 00000001 c1056760 c1328520 c12b1d20 c1595280 c136e3a0 c121ec00
[44736.452000] Call Trace:
[44736.452000] [<c015e995>] __pagevec_release+0x15/0x20
[44736.452000] [<c015f817>] shrink_active_list+0x377/0x420
[44736.452000] [<c01603bc>] shrink_zone+0x9c/0x100
[44736.452000] [<c0160988>] kswapd+0x328/0x430
[44736.452000] [<c013ae00>] autoremove_wake_function+0x0/0x50
[44736.452000] [<c0160660>] kswapd+0x0/0x430
[44736.452000] [<c013ac4a>] kthread+0xba/0xf0
[44736.452000] [<c013ab90>] kthread+0x0/0xf0
[44736.452000] [<c01044c7>] kernel_thread_helper+0x7/0x10
[44736.452000] =======================
[44736.452000] Code: ff ff 8b 53 10 e9 4b fd ff ff 8b 03 8b 53 10 66 85 c0 89 d1 0f 88 b0 00 00 00 f6 c2 01 0f 85 22 fd ff ff 85 d2 0f 84 1a fd ff ff <8b> 79 18 85 ff 0f 85 c0 fa ff ff 8d 41 20 3b 41 20 0f 85 b4 fa
[44736.452000] EIP: [<c01601e3>] shrink_inactive_list+0x733/0x870 SS:ESP 0068:c1931e10

Revision history for this message
Ruben Garcia (rubengarciahernandez) wrote :
Revision history for this message
Ruben Garcia (rubengarciahernandez) wrote :

Same machine as bug 119740, lspci -vv can be seen in that bug.

Revision history for this message
Ruben Garcia (rubengarciahernandez) wrote :

I got today another oops, similar back trace, this one mentions a couple more functions

 Call Trace:
[58506.820000] [<c0169d27>] page_referenced_one+0x87/0xf0
[58506.820000] [<c016a78d>] page_referenced+0x6d/0x120
[58506.820000] [<c015e995>] __pagevec_release+0x15/0x20

the rest of the trace is the same as above.

Same machine as above, as well. The code is the same also.

I hope this helps to debug the problem

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

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.

Revision history for this message
Ruben Garcia (rubengarciahernandez) wrote :

My machine has been stable for quite some time. Please close this bug. I'll open another one if needed.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Thanks for the update. This bug report is being closed per your last comment. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thanks again and please continue to report any future bugs that you may find.

Changed in linux:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.