BUG: unable to handle kernel NULL pointer dereference at 0000000000000080

Bug #1022351 reported by Leon on 2012-07-08
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Linux
Fix Released
Medium
linux (Ubuntu)
Medium
Leann Ogasawara
Quantal
Medium
Leann Ogasawara

Bug Description

ProblemType: KernelOops
DistroRelease: Ubuntu 12.10/Mint13 (when using a 3.5 kernel)
Package: linux-image-3.2.0-23-generic 3.2.0-23.36
ProcVersionSignature: Ubuntu 3.5.0-3.3-generic 3.5.0-rc5
Uname: Linux ubuntu 3.5.0-3-generic #3-Ubuntu SMP Mon Jul 2 16:49:22 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

This bug happens during the boot process with the Linux kernel 3.5 with the daily build of Ubuntu 12.10 as well as Ubuntu 12.04 based Mint 13 when using a 3.5 kernel from the Ubuntu mainline repo. The most recent version I have tested is the daily build from today 08-Jul-2012 10:32, which still has this issue.

I can only attach lspci -vvnn without sudo, as sudo itself hangs without output of any kind. I tried "ubuntu-bug linux", but it has been running for about 15 minutes without any signs of progress so I can only assume that it won't be of much use either.

I don not believe this bug is related to #979402, #979404, or Bug #981877.

CVE References

Leon (lehjr) wrote :
Leon (lehjr) wrote :
Leon (lehjr) wrote :
Brad Figg (brad-figg) on 2012-07-08
Changed in linux (Ubuntu):
status: New → Confirmed
tags: added: quantal
Dave Gilbert (ubuntu-treblig) wrote :
Download full text (5.8 KiB)

Looks wifi related:

[ 26.171255] cfg80211: Updating information on frequency 2484 MHz for a 20 MHz width channel with regulatory rule:
[ 26.171257] cfg80211: 2474000 KHz - 2494000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
[ 26.246994] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 26.247240] Registered led device: rt2500pci-phy0::radio
[ 26.247257] Registered led device: rt2500pci-phy0::quality
[ 27.287367] BUG: unable to handle kernel NULL pointer dereference at 0000000000000080
[ 27.288011] IP: [<ffffffff8156056e>] __netif_schedule+0xe/0x70
[ 27.288011] PGD 3927f067 PUD 37fed067 PMD 0
[ 27.288011] Oops: 0002 [#1] SMP
[ 27.288011] CPU 0
[ 27.288011] Modules linked in:
[ 27.288011] snd_via82xx_modem(+) gameport(+) snd_ac97_codec ac97_bus snd_pcm snd_mpu401_uart arc4 snd_seq_midi rt2500pci rt2x00pci snd_rawmidi rt2x00lib snd_seq_midi_event mac80211 snd_seq snd_timer snd_seq_device snd cfg80211 amd64_edac_mod dm_multipath edac_core serio_raw scsi_dh eeprom_93cx6 i2c_viapro k8temp edac_mce_amd snd_page_alloc soundcore shpchp mac_hid parport_pc bnep ppdev bluetooth lp parport squashfs overlayfs nls_utf8 isofs dm_raid45 xor dm_mirror dm_region_hash dm_log hid_generic radeon usbhid ttm drm_kms_helper hid usb_storage drm floppy i2c_algo_bit pata_via sata_via skge
[ 27.288011]
[ 27.288011] Pid: 1730, comm: NetworkManager Not tainted 3.5.0-3-generic #3-Ubuntu To Be Filled By O.E.M. To Be Filled By O.E.M./A8V Deluxe
[ 27.288011] RIP: 0010:[<ffffffff8156056e>] [<ffffffff8156056e>] __netif_schedule+0xe/0x70
[ 27.288011] RSP: 0018:ffff8800374b54d8 EFLAGS: 00010096
[ 27.288011] RAX: ffff880039506140 RBX: ffff88003a5c07c0 RCX: ffff88003be74580
[ 27.288011] RDX: 00000000ffffffff RSI: 0000000000000086 RDI: 0000000000000000
[ 27.288011] RBP: ffff8800374b54e8 R08: ffff88003ee13980 R09: 0000000000000000
[ 27.288011] R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000140
[ 27.288011] R13: ffff88003a5c07c1 R14: 0000000000000000 R15: ffff88003be752b8
[ 27.288011] FS: 00007f2565a85800(0000) GS:ffff88003ee00000(0000) knlGS:0000000000000000
[ 27.288011] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 27.288011] CR2: 0000000000000080 CR3: 0000000039230000 CR4: 00000000000007f0
[ 27.288011] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 27.288011] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 27.288011] Process NetworkManager (pid: 1730, threadinfo ffff8800374b4000, task ffff880038695c00)
[ 27.288011] Stack:
[ 27.288011] ffff8800374b5508 ffff88003a5c07c0 ffff8800374b5548 ffffffffa0354675
[ 27.288011] ffff88003cb81cec ffff88003be74580 ffff8800374b5528 ffff88003a5c07c0
[ 27.288011] 0000000000000086 ffff88003be746f8 0000000000000000 0000000000000286
[ 27.288011] Call Trace:
[ 27.288011] [<ffffffffa0354675>] ieee80211_propagate_queue_wake+0x105/0x110 [mac80211]
[ 27.288011] [<ffffffffa0354772>] __ieee80211_wake_queue+0xf2/0x110 [mac80211]
[ 27.288011] [<ffffffffa03547da>] ieee80211_wake_queue_by_reason+0x4a/0x70 [mac80211]
[ 27.288011] [<ffffffffa0354810>] ieee80211_wake_queue+0x10/0x20 [mac80211]
[ 27.288011] [<ff...

Read more...

Leon (lehjr) wrote :

The attached file here is the output of lspci-vnn.log from an almost identical machine (same motherboard and network card) running kernel 3.2. The issue goes away when the card is not present.

The card is the ASUSTeK Computer Inc. WL-130g, which was packaged with the A8V Deluxe.

From a the machine running the 3.2 kernel:
00:09.0 Network controller [0280]: Ralink corp. RT2500 Wireless 802.11bg [1814:0201] (rev 01)
 Subsystem: ASUSTeK Computer Inc. WL-130g [1043:130f]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 64, Cache Line Size: 64 bytes
 Interrupt: pin A routed to IRQ 16
 Region 0: Memory at fb900000 (32-bit, non-prefetchable) [size=8K]
 Capabilities: [40] Power Management version 2
  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
 Kernel driver in use: rt2500pci
 Kernel modules: rt2500pci

Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.5kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). 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.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc6-quantal/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: needs-upstream-testing netif-schedule
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Leon (lehjr) wrote :

The issue still remains. Since the initial report was done using a live USB session, I did an install on a spare hard drive so I could try the latest mainline kernel, RC6, but the error still remains. In addition to sudo hanging when this issue is present, shutdown also fails. With the wifi card removed things work as expected.

tags: added: kernel-bug-exists-upstream
removed: needs-upstream-testing
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[1] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Changed in linux (Ubuntu):
status: Incomplete → Triaged
Leon (lehjr) wrote :

Upstream bug report filed (stretching the boundaries of my noob skills)

Changed in linux:
importance: Unknown → Medium
status: Unknown → Confirmed
Changed in linux:
status: Confirmed → Fix Released
Leon (lehjr) wrote :

bug is still in RC7

Joseph Salisbury (jsalisbury) wrote :

Fix not applied to RC7. Upstream aware.

Leon (lehjr) wrote :

Not fixed in 3.5, upstream dropped the ball on this one, which means not suitable for any embedded devices which use the effected hardware or where the hardware is not removable since the bug hinders the ability to shutdown, reboot, or even use root access.

Changed in linux (Ubuntu Quantal):
assignee: nobody → Leann Ogasawara (leannogasawara)
status: Triaged → In Progress

Hi Leon,

I've posted a Quantal test kernel with the upstream patch applied. Could you give it a test and let me know your results?

http://people.canonical.com/~ogasawara/lp1022351/amd64/

Note: Please be sure to install both the linux-image and linux-image-extra packages when testing. Thanks.

Leon (lehjr) wrote :

This is the result of a quick test run in Ubuntu based Mint 13. I did get some errors during installation, something about driver modules. I will include the actual error when I test with a Quantal installation, should be within the hour.

Leon (lehjr) wrote :

I'm not sure what the mint errors were, I suspect it may have been related to using the fglrx-beta-legacy driver, I didn't expect it to work with the 3.5 kernel anyway. But it did install without errors on my Ubuntu installation, and the effected wireless device and everything else that I can tell appears to be working. There was an error with the onboard audio in the attatched dmesg output, but it seems to be working.

Anyway, thanks for this kernel. Now I can get back to testing other things without having to wear out my PCI slot.

Pushed to the Quantal kernel git repo. I'll also submit this to upstream stable. Thanks.

Changed in linux (Ubuntu Quantal):
status: In Progress → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 3.5.0-7.7

---------------
linux (3.5.0-7.7) quantal-proposed; urgency=low

  [ Andy Whitcroft ]

  * [Config] CONFIG_X86_POWERNOW_K6=m
  * [Config] CONFIG_X86_POWERNOW_K7=m
  * [Config] CONFIG_X86_LONGHAUL=m
  * [Config] CONFIG_X86_LONGRUN=m
  * [Config] CONFIG_X86_GX_SUSPMOD=m
  * [Config] CONFIG_X86_CPUFREQ_NFORCE2=m
  * SAUCE: rds_ib_send() -- prevent local pings triggering BUG_ON()
    - LP: #1016299
    - CVE-2012-2372
  * [Config] enable CONFIG_VFAT_FS=y for EFI systems
  * [Config] CONFIG_USB_G_MULTI=n on highbank
  * [Config] annotate: CONFIG_USB_INVENTRA_DMA OMAP2 specific
  * [Config] CONFIG_WAN_ROUTER disable for arm
  * add support for generating binary device trees and install them in
    /lib/firmware
    - LP: #1030600
  * [Config] add dtb_file configuration for highbank
    - LP: #1030600

  [ Tim Gardner ]

  * SAUCE: ene_ub6250: Use macros for firmware names
  * SAUCE: s2255drv: Add MODULE_FIRMWARE statement
  * SAUCE: xc5000: Add MODULE_FIRMWARE statements
  * SAUCE: firmware: remove computone driver firmware and documentation
  * SAUCE: lgs8gxx: Declare MODULE_FIRMWARE usage
  * SAUCE: firmware: Remove obsolete Myricom firmware
  * SAUCE: staging rtl8192e: Declare MODULE_FIRMWARE usage
  * SAUCE: tlg2300: Declare MODULE_FIRMWARE usage
  * SAUCE: ueagle-atm: Declare MODULE_FIRMWARE usage
  * SAUCE: usbduxfast: Declare MODULE_FIRMWARE usage
  * SAUCE: usbdux: Declare MODULE_FIRMWARE usage
  * SAUCE: usbduxsigma: Declare MODULE_FIRMWARE usage
  * SAUCE: cx25840: Declare MODULE_FIRMWARE usage
  * SAUCE: cx18: Declare MODULE_FIRMWARE usage
  * SAUCE: ivtv: Declare MODULE_FIRMWARE usage
  * SAUCE: cx231xx: Declare MODULE_FIRMWARE usage
  * SAUCE: cx23885: Declare MODULE_FIRMWARE usage
  * SAUCE: pvrusb2: Declare MODULE_FIRMWARE usage
  * SAUCE: vxge: Declare MODULE_FIRMWARE usage

  [ Upstream Kernel Changes ]

  * mac80211: fix crash with single-queue drivers
    - LP: #1022351
 -- Leann Ogasawara <email address hidden> Mon, 30 Jul 2012 11:11:05 -0700

Changed in linux (Ubuntu Quantal):
status: Fix Committed → Fix Released

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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