Eee PC 1201 (Nvidia ION chipset) generates kernel oops

Bug #496674 reported by Gyorgy Nemeth
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

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

The system generates lot of kernel oops messages. Here is a snippet from dmesg:

[ 17.239000] BUG: unable to handle kernel paging request at f80ca2cc
[ 17.239014] IP: [<c03a02b6>] dev_uevent+0x46/0x120
[ 17.239030] *pde = 37011067 *pte = 00000000
[ 17.239038] Oops: 0000 [#1] SMP
[ 17.239044] last sysfs file: /sys/devices/LNXSYSTM:00/device:00/ASUS010:00/uevent
[ 17.239051] Modules linked in: snd_hda_codec_nvhdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer joydev snd_seq_device nvidia(P) snd agpgart soundcore snd_page_alloc i2c_nforce2 shpchp uvcvideo atl1c videodev psmouse btusb v4l1_compat serio_raw usb_storage video output
[ 17.239109]
[ 17.239117] Pid: 1016, comm: udevadm Tainted: P (2.6.31-16-generic #53-Ubuntu) 1201N
[ 17.239124] EIP: 0060:[<c03a02b6>] EFLAGS: 00010286 CPU: 1
[ 17.239131] EIP is at dev_uevent+0x46/0x120
[ 17.239136] EAX: f80ca2cc EBX: f71519fc ECX: d628e000 EDX: f7151a04
[ 17.239142] ESI: d628e000 EDI: d628e000 EBP: d5a61ee4 ESP: d5a61ecc
[ 17.239148] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[ 17.239155] Process udevadm (pid: 1016, ti=d5a60000 task=d5a99920 task.ti=d5a60000)
[ 17.239160] Stack:
[ 17.239164] 00000246 fffffff4 f7001ac0 c03a0da0 c076b320 f7001ac0 d5a61f0c c03a0e1c
[ 17.239178] <0> 00000001 00000041 c0784e40 d5aa2000 f7151a04 c076b34c fffffffb c03a0da0
[ 17.239193] <0> d5a61f20 c03a0054 d60f0d00 f7125840 c076b360 d5a61f3c c023983d f6b53200
[ 17.239209] Call Trace:
[ 17.239219] [<c03a0da0>] ? show_uevent+0x0/0xc0
[ 17.239227] [<c03a0e1c>] ? show_uevent+0x7c/0xc0
[ 17.239235] [<c03a0da0>] ? show_uevent+0x0/0xc0
[ 17.239243] [<c03a0054>] ? dev_attr_show+0x24/0x50
[ 17.239254] [<c023983d>] ? fill_read_buffer+0x4d/0xc0
[ 17.239262] [<c0239922>] ? sysfs_read_file+0x72/0x80
[ 17.239272] [<c01e7d57>] ? vfs_read+0x97/0x190
[ 17.239280] [<c02398b0>] ? sysfs_read_file+0x0/0x80
[ 17.239288] [<c01e836d>] ? sys_read+0x3d/0x70
[ 17.239297] [<c010336c>] ? syscall_call+0x7/0xb
[ 17.239302] Code: 00 00 00 8b 43 30 85 c0 74 1a 8b 00 85 c0 74 14 89 44 24 08 c7 44 24 04 a4 a1 6d c0 89 34 24 e8 71 28 f7 ff 8b 43 48 85 c0 74 16 <8b> 00 c7 44 24 04 af a1 6d c0 89 34 24 89 44 24 08 e8 54 28 f7
[ 17.239384] EIP: [<c03a02b6>] dev_uevent+0x46/0x120 SS:ESP 0068:d5a61ecc
[ 17.239395] CR2: 00000000f80ca2cc
[ 17.239401] ---[ end trace 6002a8a671d4e5b3 ]---
[ 17.437786] alloc irq_desc for 27 on node -1
[ 17.437797] alloc kstat_irqs on node -1
[ 17.437822] atl1c 0000:09:00.0: irq 27 for MSI/MSI-X
[ 17.437943] atl1c 0000:09:00.0: atl1c: eth0 NIC Link is Up<100 Mbps Full Duplex>
[ 20.948171] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 20.948180] Bluetooth: BNEP filters: protocol multicast
[ 20.995224] lp: driver loaded but no devices found
[ 21.031213] ppdev: user-space parallel port driver
[ 21.141204] Bridge firewalling registered
[ 27.444019] eth0: no IPv6 routers present
[ 29.795451] BUG: unable to handle kernel paging request at f80ca2cc
[ 29.795467] IP: [<c03a02b6>] dev_uevent+0x46/0x120
[ 29.795485] *pde = 37011067 *pte = 00000000
[ 29.795494] Oops: 0000 [#2] SMP
[ 29.795500] last sysfs file: /sys/devices/LNXSYSTM:00/device:00/ASUS010:00/uevent
[ 29.795508] Modules linked in: binfmt_misc bridge ppdev lp stp parport bnep snd_hda_codec_nvhdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer joydev snd_seq_device nvidia(P) snd agpgart soundcore snd_page_alloc i2c_nforce2 shpchp uvcvideo atl1c videodev psmouse btusb v4l1_compat serio_raw usb_storage video output
[ 29.795577]
[ 29.795586] Pid: 1408, comm: udev-acl.ck Tainted: P D (2.6.31-16-generic #53-Ubuntu) 1201N
[ 29.795593] EIP: 0060:[<c03a02b6>] EFLAGS: 00010286 CPU: 1
[ 29.795600] EIP is at dev_uevent+0x46/0x120
[ 29.795606] EAX: f80ca2cc EBX: f71519fc ECX: d5046000 EDX: f7151a04
[ 29.795612] ESI: d5046000 EDI: d5046000 EBP: d603fee4 ESP: d603fecc
[ 29.795618] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[ 29.795625] Process udev-acl.ck (pid: 1408, ti=d603e000 task=f69bd7f0 task.ti=d603e000)
[ 29.795630] Stack:
[ 29.795634] 00000246 fffffff4 f7001ac0 c03a0da0 c076b320 f7001ac0 d603ff0c c03a0e1c
[ 29.795649] <0> 00000001 00000041 c0784e40 d61fc000 f7151a04 c076b34c fffffffb c03a0da0
[ 29.795664] <0> d603ff20 c03a0054 d60f08c0 f7125840 c076b360 d603ff3c c023983d d6129280
[ 29.795680] Call Trace:
[ 29.795690] [<c03a0da0>] ? show_uevent+0x0/0xc0
[ 29.795699] [<c03a0e1c>] ? show_uevent+0x7c/0xc0
[ 29.795707] [<c03a0da0>] ? show_uevent+0x0/0xc0
[ 29.795714] [<c03a0054>] ? dev_attr_show+0x24/0x50
[ 29.795726] [<c023983d>] ? fill_read_buffer+0x4d/0xc0
[ 29.795734] [<c0239922>] ? sysfs_read_file+0x72/0x80
[ 29.795745] [<c01e7d57>] ? vfs_read+0x97/0x190
[ 29.795753] [<c02398b0>] ? sysfs_read_file+0x0/0x80
[ 29.795761] [<c01e836d>] ? sys_read+0x3d/0x70
[ 29.795771] [<c010336c>] ? syscall_call+0x7/0xb
[ 29.795776] Code: 00 00 00 8b 43 30 85 c0 74 1a 8b 00 85 c0 74 14 89 44 24 08 c7 44 24 04 a4 a1 6d c0 89 34 24 e8 71 28 f7 ff 8b 43 48 85 c0 74 16 <8b> 00 c7 44 24 04 af a1 6d c0 89 34 24 89 44 24 08 e8 54 28 f7
[ 29.795860] EIP: [<c03a02b6>] dev_uevent+0x46/0x120 SS:ESP 0068:d603fecc
[ 29.795870] CR2: 00000000f80ca2cc
[ 29.795877] ---[ end trace 6002a8a671d4e5b4 ]---

When I try to read /sys/devices/LNXSYSTM:00/device:00/ASUS010:00/uevent file, the message similar to the above generates in the log.

When I boot with acpi=off, there is no error (though the system doesn't work as expected e.g. no mouse becaouse the lack of acpi).

I use Karmic with the current kernel (2.6.31-16-generic).

Andy Whitcroft (apw)
tags: added: karmic
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Gyorgy,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 496674

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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