hald segfaults on kernel 2.6.29-rc

Bug #322649 reported by crys
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
hal (Ubuntu)
Fix Released
Medium
Chris Coulson

Bug Description

Binary package hint: hal

Ubuntu version: 9.04 Jaunty Jackalope amd64
Package version: 0.5.12~rc1+git20090120-0ubuntu1

hald segfaults on vanilla kernel 2.6.29-rc2 and -rc3 (-rc1 not tested) with the following kernel error:
hald[2957]: segfault at 80 ip 000000000042f63b sp 00007fff635a57e0 error 4 in hald[400000+57000]

After a manual restart of hal it works as expected.

If you need further information please let me know.

crys (schaefec)
description: updated
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in hal:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
crys (schaefec) wrote :

Here it is.

Revision history for this message
crys (schaefec) wrote :

I further examined this problem. It's related to this reported regression on lkml:
http://marc.info/?t=123139972800002&r=1&w=2

As a consequence, if CONFIG_MMC is disabled in 2.6.29-rc3, the problem vanishs and jaunty boots correctly.

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Thanks Christian

Could you please provide another backtrace with the following packages installed: libglib2.0-0-dbg and libdbus-glib-1-2-dbg

Changed in hal:
status: Incomplete → Triaged
Changed in hal:
assignee: nobody → chrisccoulson
status: Triaged → In Progress
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

I was going to apply the patch that fixes this from the current GIT tree, but I noticed we're already running a GIT snapshot of HAL, so I just did another snapshot (which has the fix for this)

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Here's the tarball of the snapshot I took

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

<Snapshot deleted>

It still had the (quite large) .git folder

Revision history for this message
Chris Coulson (chrisccoulson) wrote :
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Note to sponsor - I put the changes in to my bzr branch too, for merging.

Changed in hal:
status: In Progress → Triaged
Revision history for this message
Martin Pitt (pitti) wrote :

Thanks a lot Chris! I merged your branch into the ubuntu branch and prepared the package for upload. However, I'll wait with that until Alpha-4 gets released tomorrow (soft freeze ATM).

Changed in hal:
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package hal - 0.5.12~rc1+git20090204-0ubuntu1

---------------
hal (0.5.12~rc1+git20090204-0ubuntu1) jaunty; urgency=low

  * Update to latest upstream git snapshot:
    - Fix buffer overrun with incorrectly formatted LED
      devices (LP: #322649).

 -- Chris Coulson <email address hidden> Wed, 04 Feb 2009 23:18:31 +0100

Changed in hal:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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