Kernel Oops - BUG: unable to handle kernel NULL pointer dereference at (null); RIP: 0010:[<ffffffff8107f22e>] [<ffffffff8107f22e>] kfifo_alloc+0x2e/0xb0

Bug #601229 reported by Roman Yepishev
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

During startup sequence before plymouth is started the Oops information appears on the screen (included by the apport).

Reproducible: always with Maverick 2.6.35-{5,6}-generic
Latest known kernel version w/o the bug - lucid 2.6.32-22

Will be extremely happy to provide any additional information you may require.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-6-generic 2.6.35-6.9
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-6.9-generic 2.6.35-rc3
Uname: Linux 2.6.35-6-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: NVidia [HDA NVidia], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: NVidia [HDA NVidia], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: rtg 1861 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xd0880000 irq 21'
   Mixer name : 'Realtek ALC268'
   Components : 'HDA:10ec0268,10250126,00100003 HDA:14f12c06,10250126,00100000'
   Controls : 11
   Simple ctrls : 8
Date: Sat Jul 3 00:22:53 2010
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=d0764a47-1776-4dfa-b8ee-4e1774d9d828
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
Lsusb:
 Bus 004 Device 002: ID 0a5c:2101 Broadcom Corp. Bluetooth Controller
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire 5520
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-6-generic root=UUID=799e9cf3-ccb9-48e0-ba0e-22b50bb09faf ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.37
SourcePackage: linux
dmi.bios.date: 05/06/2008
dmi.bios.vendor: Acer
dmi.bios.version: V1.33
dmi.board.name: Fuquene
dmi.board.vendor: Acer
dmi.board.version: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAcer:bvrV1.33:bd05/06/2008:svnAcer:pnAspire5520:pvrV1.33:rvnAcer:rnFuquene:rvrN/A:cvnAcer:ct10:cvrN/A:
dmi.product.name: Aspire 5520
dmi.product.version: V1.33
dmi.sys.vendor: Acer

Revision history for this message
Roman Yepishev (rye) wrote :
Revision history for this message
Roman Yepishev (rye) wrote :
Download full text (3.4 KiB)

Looks like this thread is related:
http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/22152/

And here are the entries from patchwork:
https://patchwork.kernel.org/patch/119206/

OOPS message is:
[ 6.171529] Oops: 0002 [#1] SMP
[ 6.171689] last sysfs file: /sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/name
[ 6.171753] CPU 1
[ 6.171808] Modules linked in: lirc_ene0100(+) lirc_dev lp parport ahci sdhci_pci firewire_ohci firewire_core sdhci led_class libahci crc_itu_t pata_amd forcedeth
[ 6.172709]
[ 6.172766] Pid: 511, comm: modprobe Not tainted 2.6.35-6-generic #9-Ubuntu Fuquene/Aspire 5520
[ 6.172830] RIP: 0010:[<ffffffff8107f22e>] [<ffffffff8107f22e>] kfifo_alloc+0x2e/0xb0
[ 6.172946] RSP: 0018:ffff88009a579d08 EFLAGS: 00010286
[ 6.173005] RAX: ffff8800b9477000 RBX: 0000000000000000 RCX: ffffffff8107f229
[ 6.173067] RDX: 0000000000000000 RSI: 00000000000000d0 RDI: 0000000000000246
[ 6.173128] RBP: ffff88009a579d18 R08: 0000000000000000 R09: 0000000000000246
[ 6.173189] R10: 0000000000000030 R11: 0000000000000000 R12: 0000000000001000
[ 6.173251] R13: ffff88003787d800 R14: ffff8800bbc44c00 R15: 00000000fffffff4
[ 6.173313] FS: 00007f3022b1c700(0000) GS:ffff880001f00000(0000) knlGS:0000000000000000
[ 6.173376] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 6.173435] CR2: 0000000000000000 CR3: 000000009a43d000 CR4: 00000000000006e0
[ 6.173506] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 6.173578] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 6.173649] Process modprobe (pid: 511, threadinfo ffff88009a578000, task ffff88009b2edb80)
[ 6.173730] Stack:
[ 6.173795] ffff88009abc7b40 ffff8800bbc58660 ffff88009a579d58 ffffffffa009ee4f
[ 6.174020] <0> ffff88009a579d38 ffffffffa009f060 ffff88003787d800 ffffffffa009f580
[ 6.174357] <0> ffffffffa009f540 00000000fffffff4 ffff88009a579d98 ffffffff8132a475
[ 6.174755] Call Trace:
[ 6.174825] [<ffffffffa009ee4f>] ene_probe+0x17f/0x350 [lirc_ene0100]
[ 6.174899] [<ffffffff8132a475>] pnp_device_probe+0x95/0x100
[ 6.174971] [<ffffffff813899b2>] ? driver_sysfs_add+0x62/0x90
[ 6.175041] [<ffffffff81389ad8>] really_probe+0x68/0x190
[ 6.175111] [<ffffffff81389c45>] driver_probe_device+0x45/0x70
[ 6.175182] [<ffffffff81389d0b>] __driver_attach+0x9b/0xa0
[ 6.175252] [<ffffffff81389c70>] ? __driver_attach+0x0/0xa0
[ 6.175322] [<ffffffff81388f18>] bus_for_each_dev+0x68/0x90
[ 6.175392] [<ffffffff8138994e>] driver_attach+0x1e/0x20
[ 6.175461] [<ffffffff8138920e>] bus_add_driver+0xde/0x280
[ 6.175531] [<ffffffff8138a050>] driver_register+0x80/0x150
[ 6.175603] [<ffffffffa00a2000>] ? ene_init+0x0/0x3e [lirc_ene0100]
[ 6.175675] [<ffffffff8132a1f1>] pnp_register_driver+0x21/0x30
[ 6.175746] [<ffffffffa00a203c>] ene_init+0x3c/0x3e [lirc_ene0100]
[ 6.175819] [<ffffffff8100204c>] do_one_initcall+0x3c/0x1a0
[ 6.175890] [<ffffffff8109abfb>] sys_init_module+0xbb/0x200
[ 6.175962] [<ffffffff8100a0f2>] system_call_fastpath+0x16/0x1b
[ 6.176032] Code: e5 41 54 53 0f 1f 44 00 00 48 89 fb 89 f7 41 89 f4 48 85 ...

Read more...

Brad Figg (brad-figg)
tags: added: acpi
tags: added: acpi-method-return
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
tags: removed: regression-potential
penalvch (penalvch)
tags: added: regression-release
summary: - [maverick] Kernel OOPS during startup due to lirc_ene0100
+ Kernel Oops - BUG: unable to handle kernel NULL pointer dereference at
+ (null); RIP: 0010:[<ffffffff8107f22e>] [<ffffffff8107f22e>]
+ kfifo_alloc+0x2e/0xb0
tags: added: kernel-oops
Revision history for this message
penalvch (penalvch) wrote :

Roman Yepishev, thank you for reporting this bug and helping make Ubuntu better. Maverick reached EOL on April 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

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 in a supported release? 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 <replace-with-bug-number>

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.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Roman Yepishev (rye) wrote :

This is definitely fixed in maveric onwards and was seen only in the development version. Setting Fix Released.

Changed in linux (Ubuntu):
status: Incomplete → Fix Released
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.