Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 521911[details]
Call trace recorded from the core file
Description of problem:
In Huawei's Hardware testing Lab, the testing engineer can emulating the behaviors of disconnecting/connecting the usb keyboard/mouse by continuously rebooting the BMC console (integated in their Blade Board). After many times of
disconnecting/connecting the usb keyboard/mouse, the "hald" daemon will disappear
left no information. By starting the "hald" with option "--daemon=yes --use-syslog --retain-privileges", the core information can be collected.
A call trace recorded from the core is attached.
From a simple analysis of the codes following the call trace, we can see that the "DBusError" local variable used in reply_from_singleton_device_changed() is not initialized, and this will cause the hald process to abort with the call path:
"reply_from_singleton_device_changed" => "dbus_set_error_from_message" => "_dbus_return_val_if_error_is_set" => "_dbus_return_val_if_fail" =>
"_dbus_warn_check_failed" => "_dbus_abort" => "abort"
The issue occurs on both RHEL6.1 for i686 and x86-64 with the following packages:
hal-0.5.14-11.el6
dbus-1.2.24-4
glibc-2.12-1.25
kernel-2.6.32-131.0.15.el6
How reproducible:
It is very hard to reproduce the issue in ordinary Linux server/Thinkpad environment. But very ease to reproduce the issue in Huawei's environment since
the BMC console is able to emulating the disconnecting/connecting of the USB devices while rebooting and the BMC console can be rebooted by a script calling "ipmitool" frequently
Solving:
The attached patch has been tested to be able to solve the issue
Comment 3RHEL Program Management
2011-09-07 15:38:28 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 6RHEL Program Management
2012-07-10 06:19:56 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 7RHEL Program Management
2012-07-10 23:23:17 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Comment 8RHEL Program Management
2012-09-07 05:17:38 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Comment 9RHEL Program Management
2013-10-14 01:00:10 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Created attachment 521911 [details] Call trace recorded from the core file Description of problem: In Huawei's Hardware testing Lab, the testing engineer can emulating the behaviors of disconnecting/connecting the usb keyboard/mouse by continuously rebooting the BMC console (integated in their Blade Board). After many times of disconnecting/connecting the usb keyboard/mouse, the "hald" daemon will disappear left no information. By starting the "hald" with option "--daemon=yes --use-syslog --retain-privileges", the core information can be collected. A call trace recorded from the core is attached. From a simple analysis of the codes following the call trace, we can see that the "DBusError" local variable used in reply_from_singleton_device_changed() is not initialized, and this will cause the hald process to abort with the call path: "reply_from_singleton_device_changed" => "dbus_set_error_from_message" => "_dbus_return_val_if_error_is_set" => "_dbus_return_val_if_fail" => "_dbus_warn_check_failed" => "_dbus_abort" => "abort" The issue occurs on both RHEL6.1 for i686 and x86-64 with the following packages: hal-0.5.14-11.el6 dbus-1.2.24-4 glibc-2.12-1.25 kernel-2.6.32-131.0.15.el6 How reproducible: It is very hard to reproduce the issue in ordinary Linux server/Thinkpad environment. But very ease to reproduce the issue in Huawei's environment since the BMC console is able to emulating the disconnecting/connecting of the USB devices while rebooting and the BMC console can be rebooted by a script calling "ipmitool" frequently Solving: The attached patch has been tested to be able to solve the issue