Kernel Oops - BUG: unable to handle kernel NULL pointer dereference at 0000000000000060; RIP: 0010:[<ffffffffa00f41b8>] [<ffffffffa00f41b8>] store_protocols+0x188/0x3e0 [ir_core]

Bug #670272 reported by Shock
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

When I connect a Canon Powershot A620 via usb on Maverick, nothing happens. I would have expected nautilus to pop up as it did in Lucid. dmesg shows lirc crashing after I connect the camera (?!!?!) -- this happens consistently.

I tried reporting the bug using ubuntu-bug storage but apport stays indefinitely (15+minutes) at the "Collecting problem information" screen.

"gphoto-2 --auto-detect" stalls indefinitely.

Revision history for this message
Shock (mmiron) wrote :
Revision history for this message
Shock (mmiron) wrote :
Revision history for this message
Shock (mmiron) wrote :
Revision history for this message
Shock (mmiron) wrote :
tags: added: regression-release
Revision history for this message
Shock (mmiron) wrote :

After lots of minutes (15+) I get an error:

Unable to mount Canon Digital Camera

DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

By then the camera has self shut down.

Revision history for this message
Shock (mmiron) wrote :

Using linux-image-2.6.37-020637rc1-generic_2.6.37-020637rc1.201011020905_amd64.deb the camera works but other things don't (like network). I'm attaching the dmesg.

Revision history for this message
Shock (mmiron) wrote :

Turns out, that without the camera connected simply starting shotwell causes the crash. Attaching dmesg.

summary: - canon camera is not detected/mounted; causes lirc crash?
+ connecting canon camera _or_ starting shotwell causes lirc/ir_core crash
+ => camera and shotwell not functioning
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Shock, thank you for reporting this 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

We were wondering if this is still an issue in a supported release? If so, 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 in a supported release 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.

summary: - connecting canon camera _or_ starting shotwell causes lirc/ir_core crash
- => camera and shotwell not functioning
+ Kernel Oops - BUG: unable to handle kernel NULL pointer dereference at
+ 0000000000000060; RIP: 0010:[<ffffffffa00f41b8>] [<ffffffffa00f41b8>]
+ store_protocols+0x188/0x3e0 [ir_core]
tags: added: kernel-oops maverick
tags: added: needs-bisect
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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.