Unable to handle kernel paging request

Bug #711681 reported by Cabalbl4
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux-lts-backport-maverick (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

Binary package hint: linux-image-2.6.35-22-generic

Once or twice a day my brand new acer aspire 3820TG with latest Maverick kernel hangs at random time (caps lock flashing). I have found the following traces in syslog:
The memory should be OK, it seems to be a kernel bug.
Exert from syslog:

Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426744] BUG: unable to handle kernel paging request at ffffffff00000080
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426747] IP: [<ffffffff81143bc5>] __kmalloc_node_track_caller+0xc5/0x1f0
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426751] PGD 1a2c067 PUD 0
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426753] Oops: 0000 [#12] SMP
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426754] last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426756] CPU 2
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426757] Modules linked in: binfmt_misc parport_pc ppdev dm_crypt joydev fglrx(P) snd_hda_codec_atihdmi snd_hda_codec_realtek arc4 snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event uvcvideo snd_seq videodev v4l1_compat ath9k ath9k_common v4l2_compat_ioctl32 ath9k_hw ath snd_timer snd_seq_device mac80211 snd intel_ips cfg80211 psmouse serio_raw led_class soundcore snd_page_alloc lp parport ahci libahci atl1c video output intel_agp
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426775]
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426777] Pid: 1235, comm: dbus-daemon Tainted: P D 2.6.35-25-generic #44-Ubuntu JM31_CP/Aspire 3820
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426778] RIP: 0010:[<ffffffff81143bc5>] [<ffffffff81143bc5>] __kmalloc_node_track_caller+0xc5/0x1f0
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426781] RSP: 0018:ffff88012e2ef9f8 EFLAGS: 00010046
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426783] RAX: ffff880001f12950 RBX: 00000000000004d0 RCX: ffffffff8148c654
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426784] RDX: 0000000000000000 RSI: 00000000000004d0 RDI: 000000000000000a
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426786] RBP: ffff88012e2efa58 R08: 00000000000000c0 R09: 0000000000000246
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426787] R10: 0000000000000000 R11: 0000000000000246 R12: ffffffff81a25d70
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426788] R13: 0000000000000218 R14: ffffffff00000080 R15: 00000000000004d0
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426790] FS: 00007fbbd4b797a0(0000) GS:ffff880001f00000(0000) knlGS:0000000000000000
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426792] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426793] CR2: ffffffff00000080 CR3: 000000012f573000 CR4: 00000000000006e0
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426795] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426796] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426798] Process dbus-daemon (pid: 1235, threadinfo ffff88012e2ee000, task ffff880131e7db80)
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426799] Stack:
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426800] ffff88012e2efa58 0000000000000246 ffff88012e2efa18 ffffffff81036db9
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426802] <0> ffffffff8148c654 ffffffff8149081f 0000000000000286 ffff880120408900
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426804] <0> 00000000000000c0 00000000ffffffff 0000000000000000 00000000000004d0
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426807] Call Trace:
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426810] [<ffffffff81036db9>] ? default_spin_lock_flags+0x9/0x10
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426813] [<ffffffff8148c654>] ? sock_alloc_send_pskb+0x1d4/0x340
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426815] [<ffffffff8149081f>] ? __alloc_skb+0x4f/0x170
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426817] [<ffffffff81490853>] __alloc_skb+0x83/0x170
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426819] [<ffffffff8148c654>] sock_alloc_send_pskb+0x1d4/0x340
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426822] [<ffffffff81525369>] ? unix_stream_recvmsg+0x2e9/0x580
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426825] [<ffffffff8148c7d5>] sock_alloc_send_skb+0x15/0x20
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426827] [<ffffffff81526075>] unix_stream_sendmsg+0x275/0x3e0
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426829] [<ffffffff81488eb3>] sock_sendmsg+0xf3/0x120
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426832] [<ffffffff811650f0>] ? pollwake+0x0/0x60
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426834] [<ffffffff811650f0>] ? pollwake+0x0/0x60
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426836] [<ffffffff81036db9>] ? default_spin_lock_flags+0x9/0x10
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426838] [<ffffffff81493c85>] ? verify_iovec+0x85/0xf0
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426840] [<ffffffff814899a0>] sys_sendmsg+0x240/0x3a0
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426843] [<ffffffff8116639f>] ? __d_free+0x3f/0x60
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426845] [<ffffffff81154899>] ? __fput+0x199/0x210
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426847] [<ffffffff81154935>] ? fput+0x25/0x30
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426849] [<ffffffff81150e7d>] ? filp_close+0x5d/0x90
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426852] [<ffffffff8100a0f2>] system_call_fastpath+0x16/0x1b
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426853] Code: 4d c0 8b 55 cc 49 89 c0 44 89 fe 4c 89 e7 4c 89 4d b8 e8 9f ee ff ff 4c 8b 4d b8 49 89 c6 eb 12 eb 04 90 90 90 90 49 63 54 24 18 <49> 8b 14 16 48 89 10 4c 89 cf 57 9d 0f 1f 44 00 00 4d 85 f6 75
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426873] RIP [<ffffffff81143bc5>] __kmalloc_node_track_caller+0xc5/0x1f0
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426876] RSP <ffff88012e2ef9f8>
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426877] CR2: ffffffff00000080
Feb 2 00:00:01 hagel-Aspire-3820 kernel: [ 5017.426878] ---[ end trace e4924d41a355c81e ]---

Other data:

lsb_release -rd
Description: Ubuntu 10.10
Release: 10.10

uname -a
Linux hagel-Aspire-3820 2.6.35-25-generic #44-Ubuntu SMP Fri Jan 21 17:40:44 UTC 2011 x86_64 GNU/Linux

cat /proc/version_signature
Ubuntu 2.6.35-25.44-generic 2.6.35.10

more traces included in file syslog_exert.txt (attached)

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-22-generic 2.6.35-22.35
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
Uname: Linux 2.6.35-25-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC271X Analog [ALC271X Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: hagel 1828 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf0600000 irq 44'
   Mixer name : 'Realtek ALC271X'
   Components : 'HDA:10ec0269,10250364,00100100'
   Controls : 18
   Simple ctrls : 10
Card1.Amixer.info:
 Card hw:1 'Generic'/'HD-Audio Generic at 0xcfedc000 irq 45'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100200'
   Controls : 4
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Wed Feb 2 09:56:52 2011
Frequency: Once a day.
HibernationDevice: RESUME=UUID=c0a6ace0-5c83-4db1-871a-473dbafa39f5
Lsusb:
 Bus 002 Device 003: ID 0402:9665 ALi Corp.
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire 3820
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-25-generic root=UUID=1beb932e-6dc6-456a-bbbe-8758066c6a7b ro quiet splash acpi_osi=Linux
ProcEnviron:
 LANG=ru_RU.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38.3
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
StagingDrivers: ramzswap
Title: [STAGING]
dmi.bios.date: 10/27/2010
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.19
dmi.board.asset.tag: No Asset Tag
dmi.board.name: JM31_CP
dmi.board.vendor: Acer
dmi.board.version: V1.19
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.19
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.19:bd10/27/2010:svnAcer:pnAspire3820:pvrV1.19:rvnAcer:rnJM31_CP:rvrV1.19:cvnAcer:ct10:cvrV1.19:
dmi.product.name: Aspire 3820
dmi.product.version: V1.19
dmi.sys.vendor: Acer

Revision history for this message
Cabalbl4 (i-vohmin) wrote :
Revision history for this message
Cabalbl4 (i-vohmin) wrote :

It seems that this bug is somehow connected to the ath9k wireless driver. It is not appearing when wireless is disabled. I will try to build a driver from compat section of linux wireless and report if it will do the trick.

Revision history for this message
Cabalbl4 (i-vohmin) wrote :

Recompiled ath9k and disabled AHCI HDD mode in bios (known Bug #539467).

No more freezes for now.

Brad Figg (brad-figg)
Changed in linux-lts-backport-maverick (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
tags: added: regression-update
removed: regression-potential
Changed in linux-lts-backport-maverick (Ubuntu):
importance: Medium → Low
Revision history for this message
Brad Figg (brad-figg) wrote :

Please make sure this issue exists with the latest lts-backport-maverick kernel currently in -proposed. This kernel contains the most up-to-date set of patches for the 2.6.35 kernel.

Once you test with the -proposed kernel and if the issue still exists, set the status of this bug back to "Confirmed".

Thanks for the help.

Changed in linux-lts-backport-maverick (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Cabalbl4 (i-vohmin) wrote :

Upgraged kernel to proposed. No issues for now, will also try to install wireless backports.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux-lts-backport-maverick (Ubuntu) because there has been no activity for 60 days.]

Changed in linux-lts-backport-maverick (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Sebastian (slovdahl) wrote :

I can confirm this bug still exists. I'm running linux-image-2.6.35-30-generic and I have experienced the same crash (BUG: unable to handle kernel paging request at ffffffff00000080) 4 times in the last 2 days. I have a Asus U35JC laptop.

I started sharing internet from eth0 to wlan0 with UbuntuAdhoc. Could this be related to the crash?

Changed in linux-lts-backport-maverick (Ubuntu):
status: Expired → Confirmed
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.