[Kernel-packages] [Bug 1503731] Re: 8086:0f31 Ubuntu 15.04-15.10 freezes totally
I've been following these freeze issues since kernel 4.2. cstate is no
longer as effective since 4.6-rc7+ and 4.5.4+.
The known relevant commits are (from bugzilla #109051):
Freezing started after 3.16.7 with commit
31685c258e0b0ad6aa486c5ec001382cf8a64212
freezing worsened again between 4.1 and 4.2 with commit
8fb55197e64d5988ec57b54e973daeea72c3f2ff
Reverting these commits in later kernels does not solve the problem. But for
some users, it extends run time before the next freeze, sometimes
substantially. intel_idle.max_cstate={0,1} has helped the most users the most,
but it is a just a bandaid, not always effective.
The most recent kernels have rendered the ..cstate argument ineffective.
Other improvements in the kernel have reduced my freeze rate from < 30
minutes to about 10 hours. At those rates, it could take a month to
bisect.
Freezing only seems to occur on Intel processors (atom and later). The
freeze rates vary widely from minutes to weeks. It has dependencies on
the particular Intel processor & revision, the hardware platform and the
kernel version. Linux distro does not seem to matter much. I have
experienced freezes with Ubuntu, Mint, Manjaro, and Android_x86 on
multiple platforms (Asus T100CHI & 2 Dell laptops) For me, cstate worked
to prevent freezes until very recent kernels.
As an intermittent problem, most freeze reports have been dismissed with
"It's not in my arena". I believe this a cluster of problems requiring
concurrent fixes. I'm not sure what Ubuntu can do to solve what seems
to be obvious upstream kernel problems.
Maybe Canonical can exert some influence on kernel.org to work on these
freezes rather than breaking features that work while they push the
bleeding edge outward. Many thousands of systems are affected, some of
which belong to IT professions who influence equipment purchase and
configuration for large corporations. An 18 month old fatal bug is a PR
disaster waiting to happen. By fatal I mean that the freeze can
irreparably corrupt an installed system (and I've had to re-install
twice so far.)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1503731
Title:
8086:0f31 Ubuntu 15.04-15.10 freezes totally
Status in linux package in Ubuntu:
Incomplete
Bug description:
Ever since I first installed 15.04 back in April/May on my new DELL
Inspiron 3646 I have experienced frequent(daily/every-other-
day)complete lockups(cannot even switch to console(Alt-F1,F2,etc.).
I have determined that the issue is related to the 'i915' driver in
relation to my GPU.
I'm currently using intel-linux-graphics-
installer_1.2.0-0intel1_amd64.deb from https://01.org/linuxgraphics
with similar results (maybe a little better than the stock i915 stack
in 15.04).
WORKAROUND: Use kernel boot parameter:
intel_idle.max_cstate=1
I have gained _significant_ improvements in reliability / stability by
using parameters in the i915 module:
/etc/modprobe.d/i915.conf:
options i915 semaphores=1
and / or
/etc/default/grub:
GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_pstate=disable"
and / or
/usr/share/X11/xorg.conf.d/20-intel.conf:
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "TearFree" "1"
EndSection
and / or
Disable "Intel Virtualization Technologies" in the BIOS.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
CompositorRunning: None
Date: Wed Oct 7 09:32:47 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
Subsystem: Dell Device [1028:068d]
InstallationDate: Installed on 2015-09-17 (19 days ago)
InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64
(20150422)
LightdmGreeterLog:
** (lightdm-gtk-greeter:1005): WARNING **: [PIDs] Failed to execute command:
upstart
** (lightdm-gtk-greeter:1005): WARNING **: Failed to load user image: Failed
to open file '/home/chris/.face': No such file or directory
MachineType: Dell Inc. Inspiron 3646
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic.efi.signed
root=UUID=ef22be35-6f79-4356-be42-2689d1de0378 ro quiet
SourcePackage: xorg
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/17/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 0V6D8J
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
[Kernel-packages] [Bug 1490349] Re: 15:10: bluetoothd reports "Not enough handles to register service" at start
@Brian Burch - You might get more run time if you minimize the bt device
manager window instead of closing it after pairing (assuming that you
are using blueman device manager.) I find kernel 4.5 works a little bit
better with bluetooth. kernel 4.3.6 works like I'd expect with
bluetooth, if you don't need the newer kernel features.
We are describing is a kernel bug. I have the same bt connectivity
issues using Manjaro.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1490349
Title:
15:10: bluetoothd reports "Not enough handles to register service" at
start
Status in bluez package in Ubuntu:
Confirmed
Bug description:
On 15:10 after the bluetooth service has been stopped and restarted it
is not possible to scan or connect to devices:
$ sudo systemctl start bluetooth
$ journalctl --unit=bluetooth | tail -n 19 | awk '{$1="";$2="";$4="";print
$0}'
23:31:53 systemd[1]: Starting Bluetooth service...
23:31:53 bluetoothd[16647]: Bluetooth daemon 5.33
23:31:53 systemd[1]: Started Bluetooth service.
23:31:53 bluetoothd[16647]: Starting SDP server
23:31:53 bluetoothd[16647]: Bluetooth management interface 1.9 initialized
23:31:53 bluetoothd[16647]: Failed to obtain handles for "Service Changed"
characteristic
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Error adding Link Loss service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Current Time Service could not be registered
23:31:53 bluetoothd[16647]: gatt-time-server: Input/output error (5)
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Sap driver initialization failed.
23:31:53 bluetoothd[16647]: sap-server: Operation not permitted (1)
23:31:53 bluetoothd[16647]: Endpoint registered: sender=:1.440
path=/MediaEndpoint/A2DPSource
23:31:53 bluetoothd[16647]: Endpoint registered: sender=:1.440
path=/MediaEndpoint/A2DPSink
And
$ bluetoothctl
[NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
[NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
[NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.NotReady
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1490349] Re: 15:10: bluetoothd reports "Not enough handles to register service" at start
2 updates: 4.5.0-next-20160321: bluetooth self-starts like 4.3.6 used
to. I still need to open device manager to maintain connections, but I
no longer have to manually search for already paired devices.
The "failed to obtain..." messages are in journalctl not dmesg. Sorry
for any confusion that may have caused.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1490349
Title:
15:10: bluetoothd reports "Not enough handles to register service" at
start
Status in bluez package in Ubuntu:
Confirmed
Bug description:
On 15:10 after the bluetooth service has been stopped and restarted it
is not possible to scan or connect to devices:
$ sudo systemctl start bluetooth
$ journalctl --unit=bluetooth | tail -n 19 | awk '{$1="";$2="";$4="";print
$0}'
23:31:53 systemd[1]: Starting Bluetooth service...
23:31:53 bluetoothd[16647]: Bluetooth daemon 5.33
23:31:53 systemd[1]: Started Bluetooth service.
23:31:53 bluetoothd[16647]: Starting SDP server
23:31:53 bluetoothd[16647]: Bluetooth management interface 1.9 initialized
23:31:53 bluetoothd[16647]: Failed to obtain handles for "Service Changed"
characteristic
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Error adding Link Loss service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Current Time Service could not be registered
23:31:53 bluetoothd[16647]: gatt-time-server: Input/output error (5)
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Sap driver initialization failed.
23:31:53 bluetoothd[16647]: sap-server: Operation not permitted (1)
23:31:53 bluetoothd[16647]: Endpoint registered: sender=:1.440
path=/MediaEndpoint/A2DPSource
23:31:53 bluetoothd[16647]: Endpoint registered: sender=:1.440
path=/MediaEndpoint/A2DPSink
And
$ bluetoothctl
[NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
[NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
[NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.NotReady
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1490349] Re: 15:10: bluetoothd reports "Not enough handles to register service" at start
I have these errors in my dmesg with kernel 4.5.0 but not in 4.3.6 where
bluetooth works great. Kernel 4.4.x bluetooth behaves the same as 4.5.0
but I hadn't noticed if there are "failed to obtain..." messages.
When I boot in 4.3.6 bluetooth (bluez 5.35 and blueman, and a command
btattach... in /etc/rc.local) starts fine and I don't have to do much to
wake-up my bluetooth mouse and keyboard. In 4.4+ I have to manually
search for the devices, but I don't have to pair them again. I then
have to leave the blueman device manager running (minimized.) If
anything times out from inactivity, I have to search again to reconnect.
Asus T100-CHI Ubuntu 15.10-i386. Minimally patch kernel supports a lot
of the hardware of the T100, except sound, cameras, mic... Bluetooth
started working in kernel 4.3.3+ but regressed starting with
4.4-rc1->4.5.0.
I see a reference to a udev workaround, but that is a new area to me.
The example seems aimed at audio - how would I adapt that to
mouse/keyboard?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1490349
Title:
15:10: bluetoothd reports "Not enough handles to register service" at
start
Status in bluez package in Ubuntu:
Confirmed
Bug description:
On 15:10 after the bluetooth service has been stopped and restarted it
is not possible to scan or connect to devices:
$ sudo systemctl start bluetooth
$ journalctl --unit=bluetooth | tail -n 19 | awk '{$1="";$2="";$4="";print
$0}'
23:31:53 systemd[1]: Starting Bluetooth service...
23:31:53 bluetoothd[16647]: Bluetooth daemon 5.33
23:31:53 systemd[1]: Started Bluetooth service.
23:31:53 bluetoothd[16647]: Starting SDP server
23:31:53 bluetoothd[16647]: Bluetooth management interface 1.9 initialized
23:31:53 bluetoothd[16647]: Failed to obtain handles for "Service Changed"
characteristic
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Error adding Link Loss service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Current Time Service could not be registered
23:31:53 bluetoothd[16647]: gatt-time-server: Input/output error (5)
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Sap driver initialization failed.
23:31:53 bluetoothd[16647]: sap-server: Operation not permitted (1)
23:31:53 bluetoothd[16647]: Endpoint registered: sender=:1.440
path=/MediaEndpoint/A2DPSource
23:31:53 bluetoothd[16647]: Endpoint registered: sender=:1.440
path=/MediaEndpoint/A2DPSink
And
$ bluetoothctl
[NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
[NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
[NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.NotReady
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
