Bug 20482 - A wrong bluetooth mode block the startup system. Impossible to stop the frozen booting procedure.
Summary: A wrong bluetooth mode block the startup system. Impossible to stop the froze...
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: High major
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-14 20:09 CET by Jybz
Modified: 2023-04-24 17:26 CEST (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Jybz 2017-03-14 20:09:30 CET
Description of problem:

The laptop refuse to start if the Bluetooth is desactivated (and the Wifi activated).

The interesting line of the journalctl :
[...]
mars 14 07:14:22 localhost kernel: Bluetooth: hci0: read Intel version: 3707100180012d0d00
[...]
mars 14 07:14:22 localhost kernel: Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq
[...]
mars 14 07:14:22 localhost systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
[...]
mars 14 07:14:22 localhost systemd[1]: Starting Load/Save RF Kill Switch Status...
[...]
mars 14 07:14:22 localhost systemd[1]: Started Load/Save RF Kill Switch Status.
[...]
mars 14 07:14:24 localhost kernel: Bluetooth: hci0 command 0xfc8e tx timeout
[...]
mars 14 07:14:32 localhost kernel: Bluetooth: hci0 sending Intel patch command (0xfc8e) failed (-110)
mars 14 07:14:32 localhost kernel: Bluetooth: hci0 sending frame failed (-19)
mars 14 07:14:33 localhost kernel: iwlwifi 0000:03:00.0: RF_KILL bit toggled to disable radio.
mars 14 07:14:33 localhost systemd[1]: Starting Load/Save RF Kill Switch Status...
mars 14 07:14:33 localhost systemd[1]: Started Load/Save RF Kill Switch Status.
mars 14 07:14:33 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 14 07:14:33 localhost kernel: audit: type=1130 audit(1489472073.256:39): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 14 07:14:35 localhost kernel: Bluetooth: hci0 command 0xfc11 tx timeout
mars 14 07:14:35 localhost kernel: Bluetooth: hci0: Exiting manufacturer mode failed (-110)
mars 14 07:14:40 localhost audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mars 14 07:14:40 localhost kernel: audit: type=1131 audit(1489472080.296:40): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

The only one way to "exit" is a hard-shutdown, 8seconds on the power button.

mars 14 07:32:51 localhost systemd[1]: Ctrl-Alt-Del was pressed more than 7 times within 2s, rebooting immediately.
mars 14 07:32:51 localhost systemd[1]: Shutting down.
mars 14 07:32:51 localhost systemd[1]: Hardware watchdog 'iTCO_wdt', version 0
mars 14 07:32:51 localhost systemd[1]: Set hardware watchdog to 10min.
mars 14 07:32:51 localhost kernel: watchdog: watchdog0: watchdog did not stop!

The system don't stop in all other way.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Disable the Bluetooth and let enable the Wifi
2. reboot the computer.
3. nothing more !
Rémi Verschelde 2017-03-14 20:12:40 CET

Priority: Normal => High
Target Milestone: --- => Mageia 6

Comment 1 Marja Van Waes 2017-03-15 12:03:51 CET
Not sure this is the right assignee :-/


@ kernel & drivers maintainers:

  Please reassign if needed :-)

Assignee: bugsquad => kernel
CC: (none) => marja11

Comment 2 Aurelien Oudelet 2021-01-23 11:15:38 CET
status ?

Target Milestone: Mageia 6 => ---
CC: (none) => ouaurelien

Rio Tokyo 2023-04-24 14:16:04 CEST

CC: (none) => venomdoli4


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