Bug 12607 - Restarting tasks ... <6>hcid[18084]: segfault at 7 ip b7d44e93 sp bfd9f274 error 4 in libc-2.7.so[b7cd6000+155000]
Restarting tasks ... <6>hcid[18084]: segfault at 7 ip b7d44e93 sp bfd9f274 er...
Status: REJECTED INSUFFICIENT_DATA
Product: Power Management
Classification: Unclassified
Component: Hibernation/Suspend
All Linux
: P1 blocking
Assigned To: drivers_bluetooth@kernel-bugs.osdl.org
:
Depends on:
Blocks: 7216
  Show dependency treegraph
 
Reported: 2009-02-01 15:16 UTC by Cijoml Cijomlovic Cijomlov
Modified: 2011-04-19 07:45 UTC (History)
4 users (show)

See Also:
Kernel Version: 2.6.27.X - 2.6.32.X
Tree: Mainline
Regression: Yes


Attachments

Description Cijoml Cijomlovic Cijomlov 2009-02-01 15:16:45 UTC
Latest working kernel version: 2.6.26?
Earliest failing kernel version: 2.6.27
Distribution: Debian testing
Hardware Environment: All BT enabled devices
Software Environment: vanilla kernel
Problem Description:

hcid dies after resume resulting to not working BT connection. If PAN is used, device remains unreachable => BLOCKING

Steps to reproduce:

suspend/resume ram/disk doesn't matter
Comment 1 ykzhao 2009-09-29 07:05:53 UTC
hi, Cijomel
    Why is this bug created under the Power management?
    Do you mean that this issue happens after suspend/resuming?
    Please attach the output of dmesg after the issue happens.
    IMO this is a bluetooth bug rather than a power management bug.
    Thanks.
Comment 2 Zhang Rui 2009-10-15 07:52:51 UTC
does the problem still exists in the latest kernel?
Comment 3 Cijoml Cijomlovic Cijomlov 2009-10-15 16:58:44 UTC
yes at least for me
Comment 4 Cijoml Cijomlovic Cijomlov 2010-02-27 06:57:18 UTC
2.6.32:

Restarting tasks ...
hcid[12313]: segfault at 7 ip b756de93 sp bfa05294 error 4 in libc-2.7.so[b74ff000+155000]
done.
Comment 5 Len Brown 2011-01-18 06:19:09 UTC
is this still a problem in the latest 2.6.32.stable,
and in the latest stable release -- 2.6.37?
Comment 6 Zhang Rui 2011-04-19 07:45:04 UTC
bug closed as there is no response from the bug reporter.
please re-open it if the problem still exists in the latest upstream kernel.

Note You need to log in before you can comment on or make changes to this bug.