Bug 199166 - kernel: setitimer: hcid (pid = 1733) provided invalid timeval it_interval: tv_sec = 0 tv_usec = 5000000
Summary: kernel: setitimer: hcid (pid = 1733) provided invalid timeval it_interval: tv...
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: bluez-utils
Version: 5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Woodhouse
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-07-17 17:25 UTC by Andre Robatino
Modified: 2007-11-30 22:11 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2007-07-21 09:53:46 UTC


Attachments (Terms of Use)

Description Andre Robatino 2006-07-17 17:25:43 UTC
Description of problem:
  On shutdown, the following is written to /var/log/messages and also appears in
the console shutdown messages:

Jul 17 05:31:31 localhost hcid[1733]: Got disconnected from the system message bus
Jul 17 05:31:31 localhost kernel: setitimer: hcid (pid = 1733) provided invalid
timeval it_value: tv_sec = 0 tv_usec = 5000000
Jul 17 05:31:31 localhost kernel: setitimer: hcid (pid = 1733) provided invalid
timeval it_interval: tv_sec = 0 tv_usec = 5000000

These messages started appearing with the 2.6.17 kernel.

Version-Release number of selected component (if applicable):
bluez-utils-2.25-4

How reproducible:
always

Steps to Reproduce:
1.  Shutdown while running one of the 2.6.17 kernels.

Comment 1 Fedora Update System 2006-10-26 16:19:57 UTC
bluez-utils-3.7-2 bluez-gnome-0.6-1.fc6 has been pushed for fc6, which should resolve this issue.  If these problems are still present in this version, then please make note of it in this bug report.

Comment 2 Andre Robatino 2006-10-26 22:05:24 UTC
  I haven't seen this error message in FC6, so it should be fixed in FC6.

Comment 3 Andre Robatino 2006-10-26 22:06:45 UTC
  Just to clarify, I haven't seen it with the release versions of these
packages.  Haven't tried the new ones yet.

Comment 4 Andre Robatino 2006-10-27 07:42:26 UTC
  The error doesn't appear on shutdown with the new packages, either.


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