Having just installed
$ uname -a
Linux XPSm1530 3.11.1-031101-generic #201309141102 SMP Sat Sep 14 15:02:49 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux
I'm seeing the issue:
Sep 20 19:57:41 XPSm1530 kernel: [ 320.549143] scsi8 : usb-storage 2-3:1.0
Sep 20 19:57:42 XPSm1530 kernel: [ 321.743247]
*** This bug is a duplicate of bug 1075478 ***
https://bugs.launchpad.net/bugs/1075478
** This bug has been marked a duplicate of bug 1075478
bluetooth keyboards and mice not working after suspend/resume
--
You received this bug notification because you are a member of Kernel
Packages,
Ubuntu 13.04 and 13.10, up to and including kernel 3.12rc5, are affected
by this and the work-around of disconnecting connected devices during
suspend (from comment #10) does not solve the issue. Bluetooth has to be
disabled and re-enabled to recognise any bluetooth devices.
--
You received this
Following ioctl(sk, SIOCSIFNAME, ifr) through the kernel:
net/core/dev_ioctl::dev_ioctl()
net/core/dev_ioctl.c::dev_ifsioc()
net/core/dev.c::dev_change_name()
net/core/dev.c::dev_get_valid_name()
net/core/dev.c::__dev_get_by_name()
struct net_device *dev_get_by_name_rcu(struct net
This is confirmed as a systemd-udev regression.
Code that previously existed in rename_netif() to support a temporary
interface name (rename%u) has been removed. As a result, the '70
-persistent-net.rules' actions that try to shuffle existing names will
now fail.
systemd commit log:
commit
The systemd-udev commit first appears in Ubuntu 13.10.
git describe --contains 97595710b7
v187~162
Raring: udev (175-0ubuntu26)
Saucy: udev (204-0ubuntu15)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Nominated for Saucy since this will break multi-homed server upgrades in
nasty ways especially if they're headless and remotely located.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I've linked a proposed patch which reverts commit 97595710b7. Revert
doesn't apply cleanly so I massaged the patch to fit.
Here is confirmation that it works as expected:
$ egrep -A 2 'move.*(eth|rename)[[:digit:]]' /var/log/udev
KERNEL[19.167867] move
Improved extract from udev.log showing the DEVPATH_OLD values:
$ egrep -A 3 'move.*(eth|rename)[[:digit:]]' /var/log/udev
KERNEL[19.167867] move /devices/pci:00/:00:07.0/net/rename4 (net)
ACTION=move
DEVPATH=/devices/pci:00/:00:07.0/net/rename4
** Branch linked: lp:~tj/ubuntu/saucy/systemd/lp1235162
--
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/1235162
Title:
Regression: Persistent net names via /etc/udev/rules.d/70
Hello,
On Fri, Sep 06, 2013 at 07:53:49PM -0600, Robert Hancock wrote:
Is there any more information I can supply that would be helpful?
I'm not quite sure what the next step would be. It's quite possible
that the NVIDIA driver in Windows is doing some magic to work around
the problem that
I did some work upstream but it became too complicated. Others have also
tried but nothing has changed. In the meantime the hardware out there
that has a 32-bit limit imposed by its southbridge on 64-bit CPUs is all
now old legacy gear so I don't foresee the kernel fixing this, ever.
It still
No point. All work - if any - will be upstream not in Ubuntu and the
information required is already available in the initial comment I
created for this bug report.
** Tags removed: needs-kernel-logs
--
You received this bug notification because you are a member of Kernel
Packages, which is
Christopher, please leave the bug status as it is now. I was the
original reporter *and* member of the Ubuntu Kernel team and I created
this bug specifically to track the issue against the mainline kernel.
There is no work to be done nor data collection required against Ubuntu,
as I have
The latest kernel 3.16 driver doesn't Panic but it still has driver
failures that render the driver and device unable to scan and find
networks.
No need for a bisect since this driver is in staging, and is a work-in-
progress. For Trusty 3.13 kernel it may be necessary to disable building
the
On 08/08/14 11:00, Christopher M. Penalver wrote:
TJ, thank you for your comment. Unfortunately, this is scoped to the original
reporter David Coles, not you...
Christopher. I was triaging the bug as it affects other users, it is not
specific to the original reporters motherboard. I worked
Public bug reported:
I had a support incident with a user of an Asus X551MA containing a
Realtek RTL8821AE WiFi card. After the kernel update from 3.13.0-24 to
3.13.0-30 there was a kernel Panic as soon as the wifi card began
scanning (photograph attached).
I investigated the bug in detail and
*** This bug is a duplicate of bug 1354469 ***
https://bugs.launchpad.net/bugs/1354469
** This bug has been marked a duplicate of bug 1354469
[3.13.0-30.55] rtl8821ae Kernel PANIC due to calling incorrect function
--
You received this bug notification because you are a member of Kernel
** Description changed:
I had a support incident with a user of an Asus X551MA containing a
Realtek RTL8821AE WiFi card. After the kernel update from 3.13.0-24 to
3.13.0-30 there was a kernel Panic as soon as the wifi card began
scanning (photograph attached).
- I investigated the bug
Mainline kernel's toshiba_acpi supports KEY_TOUCHPAD_TOGGLE since v.34
(commit af502837a). As such I'm closing the Linux task as Fixed.
** Changed in: linux (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which
create a new bug report against that version using:
apport-bug linux
** Changed in: linux (Ubuntu)
Status: Incomplete = Won't Fix
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = TJ (tj)
--
You received this bug notification because you are a member of Kernel
Packages, which
This bug has now been fixed via bug #1354469
** Changed in: linux (Ubuntu)
Status: Incomplete = Fix Committed
--
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/1341275
Title:
** Attachment added: Successful boot with kernel 3.11.0-12-generic
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358491/+attachment/4181112/+files/caddy-good.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
I have a lab server named 'caddy' that is used for data recovery and
forensics of disk drives. It has hot-swap drive bays for various disk
interface types. Amongst others it has a Promise FasTrak TX2000 IDE
'fake' RAID controller.
It was upgraded from Saucy to Trusty. After
Due to bug 560246 Launchpad requires the REFERER header on form
submission... apport-collect cannot send the system diagnostic data.
--
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/1358491
Looking closer, the reason 3.11.x starts is that there are no dmraid
device-mapper nodes created at all. I'm modifying the /init script so I
can break in early, and re-run it to break-points of my choice, to do
more diagnosis.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = TJ (tj
The 'fake' RAID controller has two disks attached. Each is configured as
separate RAID-0 stripe arrays - this is because the controller doesn't
support JBOD pass-through.
This issue is caused by the LVM volumes on a fake-RAID device failing to
be ready because the LVM VG_CADDY/rootfs is not
I am closing this bug as Won't fix since it is caused by a bug in the
hardware+firmware of the PC, whereby the device identifies itself
incorrectly.
The workaround
echo options psmouse proto=exps | sudo tee -a
/etc/modprobe.d/psmouse.conf
manually tells the driver to use the Microsoft
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New = Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Tags added: regression-release
--
You received this bug notification because you are a member
This report is in progress and being worked on; please do not change the
assignment without consultation.
** Changed in: linux (Ubuntu)
Status: Incomplete = In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = TJ (tj)
--
You received this bug notification because you
** Changed in: virtualbox (Ubuntu)
Status: Triaged = In Progress
** Changed in: virtualbox (Ubuntu)
Assignee: (unassigned) = TJ (tj)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
Public bug reported:
A user with 12.04 + Trusty HWE to support RTL8188 is missing the
matching firmware since it is not included in the 12.04 linux-firmware
package; It is in the 13.04 and later packages.
modinfo $(awk '/10EC.*8179/{print $3}' /lib/modules/`uname -r`/modules.*) |
grep ^firmware
Phil: comments can't be deleted but don't worry about it. A fix for the
original issue should be coming down the pipeline soon.
--
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/1356526
blausand, I'm afraid I've not spent much time on this issue since I
developed the work-around of moving the rootfs. As it only affected the
forensics server when hot-swap disks with dmraid metadata were attached
I've not re-visited this issue so far.
--
You received this bug notification because
** Changed in: linux (Ubuntu)
Assignee: TJ (tj) = (unassigned)
** Changed in: linux (Ubuntu)
Status: In Progress = Confirmed
--
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
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New = Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Changed in: linux (Ubuntu)
Milestone: None = ubuntu-14.04.3
--
You received this bug
Please report what happens with the stock kernel installed by Ubuntu.
** Changed in: acpid (Ubuntu)
Status: New = Incomplete
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New = Incomplete
** Changed in: acpid
.
dmi.modalias:
dmi:bvnDellInc.:bvrA10:bd04/30/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0GM819:rvr:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 755
dmi.sys.vendor: Dell Inc.
-
(From TJ):
$ xrandr -q
Screen 0: minimum 320 x 200, current 3600 x 1080, maximum 16384 x 16384
HDMI-0
:
dmi.product.name: OptiPlex 755
dmi.sys.vendor: Dell Inc.
+
+ -
+
+ (From TJ):
+
+ $ xrandr -q
+ Screen 0: minimum 320 x 200, current 3600 x 1080, maximum 16384 x 16384
+ HDMI-0 connected primary 1680x1050+0+0 (normal left inverted right x axis y
axis) 477mm x 268mm
+1920x1080 60.0
As I suspected the cause was in hardware, and specifically due to the
motherboard using Master Write 0-wait state access, which meant the
device had not completed mapping its registers into the PCI Config
address space when the kernel probed for the Vendor ID.
User applied my recommended BIOS
** Summary changed:
- Ralink RT2800pci doesnt work by default
+ PCI device has incorrect Vendor:Device ID when Southbridge used 0 wait reads
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
** Tags removed: amd64 apport-bug kernel-bug-exists-upstream kernel-bug-
exists-upstream-4.3 needs-bisect regression-release xenial
--
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/1513477
The problem here is that the PCI bus probe is returning a corrupted PCI
Vendor ID. Querying the PCI config registers after the system has
started shows the correct Vendor ID, but the kernel seems to 'lose' the
2nd nibble of byte 0, turning 0x18 into 0x10:
This is from the problem PC booted with a
Public bug reported:
Bluez 5.3 does not have support for pairing with devices (such as
keyboards) that use a PIN code for pairing.
A mouse pairs correctly.
From my research it seems as if the ChromeOS project developed patches
to fix this and they are supposed to have been included in Bluez 5.4
Public bug reported:
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
This may be caused by bug #1490349 15:10: bluetoothd reports Not
enough handles to register service at start
--
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/1490347
Title:
[Regresision]
This also occurs from a fresh boot:
Aug 30 23:42:21 hephaestion.lan.iam.tj systemd[1]: Starting Bluetooth service...
Aug 30 23:42:21 hephaestion.lan.iam.tj bluetoothd[793]: Bluetooth daemon 5.33
Aug 30 23:42:21 hephaestion.lan.iam.tj bluetoothd[793]: Starting SDP server
Aug 30 23:42:21
Another attempt, this time with
$ sudo /usr/sbin/bluetoothd -nd
and the log-file is attached.
$ 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
ncy #3-Ubuntu SMP PREEMPT Tue Jul
28 13:11:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Log attached:
$ journalctl -n 48 | awk '{$1="";$2="";$4="";print $0}'
---
ApportVersion: 2.18-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS C
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => TJ (tj)
** Changed in: linux (Ubuntu)
Status: Expired => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
Your IRC conversation indicates the PC also experiences intermittent
issues with the Ps/2 connected Synaptic Touchpad. Hopefully that issue
can be solved with some i8042.XXX kernel parameter.
If not, and combined with this issue, I would suggest a boot-time RAM
test using memtest86+ (available
Public bug reported:
15.10 amd64, kernel BUG when a Bluetooth mouse disconnected due to
battery failure - in other words, an uncommanded disconnect.
$ uname -a
Linux hephaestion.lan.iam.tj 4.1.0-3-lowlatency #3-Ubuntu SMP PREEMPT Tue Jul
28 13:11:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Log
ion: 2.18-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: tj 1733 F pulseaudio
CRDA: N/A
CurrentDesktop: LXDE
DistroRelease: Ubuntu 15.10
EcryptfsInUse: Yes
MachineType: Dell Inc. XPS M1530
NonfreeKernelModules: nvidia
ion: 2.18-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: tj 1733 F pulseaudio
CRDA: N/A
CurrentDesktop: LXDE
DistroRelease: Ubuntu 15.10
EcryptfsInUse: Yes
MachineType: Dell Inc. XPS M1530
NonfreeKernelModules: nvidia
ion: 2.18-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: tj 1733 F pulseaudio
CRDA: N/A
CurrentDesktop: LXDE
DistroRelease: Ubuntu 15.10
EcryptfsInUse: Yes
MachineType: Dell Inc. XPS M1530
NonfreeKernelModules: nvidia
ion: 2.18-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: tj 1733 F pulseaudio
CRDA: N/A
CurrentDesktop: LXDE
DistroRelease: Ubuntu 15.10
EcryptfsInUse: Yes
MachineType: Dell Inc. XPS M1530
NonfreeKernelModules: nvidia
ion: 2.18-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: tj 1733 F pulseaudio
CRDA: N/A
CurrentDesktop: LXDE
DistroRelease: Ubuntu 15.10
EcryptfsInUse: Yes
MachineType: Dell Inc. XPS M1530
NonfreeKernelModules: nvidia
PREEMPT Tue Jul
28 13:11:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Log attached:
$ journalctl -n 48 | awk '{$1="";$2="";$4="";print $0}'
+ ---
+ ApportVersion: 2.18-0ubuntu7
+ Architecture: amd64
+ AudioDevicesInUse:
+ USER PID ACCESS COMMAND
+ /dev/snd
ion: 2.18-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: tj 1733 F pulseaudio
CRDA: N/A
CurrentDesktop: LXDE
DistroRelease: Ubuntu 15.10
EcryptfsInUse: Yes
MachineType: Dell Inc. XPS M1530
NonfreeKernelModules: nvidia
ion: 2.18-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: tj 1733 F pulseaudio
CRDA: N/A
CurrentDesktop: LXDE
DistroRelease: Ubuntu 15.10
EcryptfsInUse: Yes
MachineType: Dell Inc. XPS M1530
NonfreeKernelModules: nvidia
ion: 2.18-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: tj 1733 F pulseaudio
CRDA: N/A
CurrentDesktop: LXDE
DistroRelease: Ubuntu 15.10
EcryptfsInUse: Yes
MachineType: Dell Inc. XPS M1530
NonfreeKernelModules: nvidia
ion: 2.18-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: tj 1733 F pulseaudio
CRDA: N/A
CurrentDesktop: LXDE
DistroRelease: Ubuntu 15.10
EcryptfsInUse: Yes
MachineType: Dell Inc. XPS M1530
NonfreeKernelModules: nvidia
ortVersion: 2.18-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: tj 1733 F pulseaudio
CRDA: N/A
CurrentDesktop: LXDE
DistroRelease: Ubuntu 15.10
EcryptfsInUse: Yes
MachineType: Dell Inc. XPS M1530
NonfreeKernelModules
ion: 2.18-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: tj 1733 F pulseaudio
CRDA: N/A
CurrentDesktop: LXDE
DistroRelease: Ubuntu 15.10
EcryptfsInUse: Yes
MachineType: Dell Inc. XPS M1530
NonfreeKernelModules: nvidia
ion: 2.18-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: tj 1733 F pulseaudio
CRDA: N/A
CurrentDesktop: LXDE
DistroRelease: Ubuntu 15.10
EcryptfsInUse: Yes
MachineType: Dell Inc. XPS M1530
NonfreeKernelModules: nvidia
ion: 2.18-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: tj 1733 F pulseaudio
CRDA: N/A
CurrentDesktop: LXDE
DistroRelease: Ubuntu 15.10
EcryptfsInUse: Yes
MachineType: Dell Inc. XPS M1530
NonfreeKernelModules: nvidia
ApportVersion: 2.18-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: tj 1733 F pulseaudio
CRDA: N/A
CurrentDesktop: LXDE
DistroRelease: Ubuntu 15.10
EcryptfsInUse: Yes
MachineType: Dell Inc. XPS M1530
NonfreeKernelModules: nvidia
Public bug reported:
$ hcitool dev
Devices:
hci100:10:7A:4D:15:33
hci000:1F:3A:E0:0A:AF
$ hcitool -i hci1 scan
Scanning ...
00:0A:95:4B:BD:C2 Apple Wireless Keyboard
$ sudo systemctl restart bluetooth
$ journalctl -u bluetooth | grep adapter_service_add
So it seems since reconfiguring the Access Point to use mode 'auto' and
channel 'auto' the poor performace has been cured?
The disconnect you report looks to be isolated:
Aug 31 18:00:00 Saria-Lin kernel: [ 7467.759694] wlan0: deauthenticating
from 00:25:9c:9d:47:37 by local choice (Reason:
** Description changed:
- The mouse cursor is gone when Oneiric starts. The mouse itself is
+ The mouse cursor is gone when the GUI starts. The mouse itself is
responding, but the pointer is invisible. Very annoying. I do have a
workaround. One must simply restart the lightdm interface with
attached:
$ journalctl -n 48 | awk '{$1="";$2="";$4="";print $0}'
---
ApportVersion: 2.18-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: tj 1733 F pulseaudio
CRDA: N/A
CurrentDesktop: LXDE
$ cat /etc/systemd/system/bluetooth.service
.include /lib/systemd/service/bluetooth.service
[Service]
ExecStart=/usr/lib/bluetooth/bluetoothd -d
$ journalctl -fu bluetooth | tee /tmp/bluetooth-multiple-adapters.log
...
Stop/Start bluetooth service
...
Insert 2nd USB adapter
Sep 04
be required for other PCI devices.
** Changed in: linux (Ubuntu)
Status: Triaged = In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = TJ (tj)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
There are several reports that the model works fine as far back as 12.04
However, there are several confirmed reports that disconnecting the
internal battery and/or re-insulating its leads, solves the issue. That
suggests a power starvation issue, or that some component remains
powered when the
Useful investigation and follow-up comments from Matthew Garrett's at
his site:
http://mjg59.dreamwidth.org/11750.html
Several users confirm opening the case and disconnecting the battery for
a short time (a couple of minutes) and reconnecting appears to
permanently resolve the issue.
--
You
Returning status to Triaged since there are multiple reports that this
issue is not fixed, and commit dbf0e4c7257f8d6 referred to in comment
#34 is a USB suspend/resume issue, not a power-profile when on battery
issue.
** Changed in: linux (Ubuntu)
Status: Fix Released = Triaged
--
You
The actual problem is -ETIMEDOUT.
I'm doing git-bisect to find the offending commit(s).
--
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/1491988
Title:
15.10: BT Command List not
Extract from the kern.log:
Sep 10 00:17:36 hephaestion kernel: [21515.251265] hci1 end: err -110
-110 == -ETIMEDOUT
There are 2 functions that print the message "end: err %d":
net/bluetooth/hci_core.c::__hci_cmd_sync_ev()
net/bluetooth/hci_core.c::__hci_req_sync()
--
You received this bug
Another log, this time capturing the module, function, line-number and
message.
Sep 10 00:52:44 hephaestion kernel: [23623.022036] bluetooth:hci_cmd_work:4358:
hci1 cmd_cnt 1 cmd queued 4
Sep 10 00:52:44 hephaestion kernel: [23623.022044]
bluetooth:hci_send_frame:3494: hci1 type 1 len 3
Sep 10
)
Importance: Low
Assignee: TJ (tj)
Status: In Progress
** Attachment added: "Investigation report"
https://bugs.launchpad.net/bugs/1496027/+attachment/4465250/+files/Dell_Precision_M3800_iwlwifi_7260.txt
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => TJ (tj
I believe I've identified the root-cause:
$ hciconfig hci1 features
hci1: Type: BR/EDR Bus: USB
BD Address: 00:10:7A:4D:15:33 ACL MTU: 672:8 SCO MTU: 255:255
Features: 0xff 0xfb 0x01 0x00 0x00 0x00 0x00 0x00
<3-slot packets> <5-slot packets>
Tested the keyboards successfully with Lubuntu 12.04 Precise and Ubuntu
13.04 Raring which confirms this is a regression.
linux 3.2.0-30-generic-pae, bluez 4.98-2ubuntu7
linux 3.8.0-35-generic, bluez 4.101-0ubuntu8b1
** Changed in: bluez (Ubuntu)
Status: New => Triaged
** Changed in:
** Summary changed:
- 15.10: Multiple Bluetooth controllers not found
+ 15.10: BT Command List not created: bluetooth:__hci_req_sync:298: hci1 end:
err -ETIMEDOUT
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
I've now tested the device on two other systems with older releases; the
results seem to point to a regression somewhere between v3.2 and v3.8:
FAILS: linux 3.8.0-35-generic, bluez 4.101-0ubuntu8b1 (same
failure mode as Linux v4.2)
WORKS: linux 3.2.0-30-generic-pae, bluez
I've been working on this some more. I noticed that even when both
adapters are connected before bluetoothd starts, it does not find the
2nd adapter.
The problem appears to be in the read_index_list_complete() call-back,
which sees only 1 controller despite the RFkill events reporting 3
devices,
** Changed in: bluez (Ubuntu)
Status: Incomplete => Triaged
--
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/1491988
Title:
15.10: Multiple Bluetooth controllers not found
Status
ntu)
Status: Triaged => In Progress
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => TJ (tj)
** Changed in: bluez (Ubuntu)
Importance: Undecided => High
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
replace the content of /etc/default/grub.d/kexec-tools.cfg with:
KEXEC_TOAPPEND="crashkernel=384M-:128M"
case "$GRUB_CMDLINE_LINUX_DEFAULT" in
*$KEXEC_TOAPPEND*)
;;
*)
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT $KEXEC_TOAPPEND"
;;
esac
--
You
The fix has made its way into the v4.5 merge window and has the mainline
commit ID:
ccda3a7 2016-01-13 10:48:11 +0200 N Jani Nikula drm/i915: shut up gen8+
SDE irq dmesg noise, again
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Originally introduced into the Ubuntu 13.10 (Saucy) configuration with
commit 301b4bb
commit 301b4bb24cf60f339643ffddbd630169e488adf2
Author: Leann Ogasawara
Date: Fri Mar 12 17:13:25 2010 -0800
UBUNTU: rebase to v3.10-rc4
Signed-off-by: Andy
Try adding kernel command-line dynamic debug option:
... "dyndbg=file net/ipv4/ipconfig.c +pflm" ...
--
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/1259861
Title:
5-10 second delay in
ith
the A1016. It reflects using
tj@T300CHI:~$ bluetoothctl
[NEW] Controller 34:02:86:FC:AD:59 T300CHI [default]
[NEW] Device 00:0A:95:44:37:11 Apple Wireless Keyboard
[NEW] Device 1C:B7:2C:04:C7:FE ASUS T300CHI DOCKING
[bluetooth]# agent on
Agent registered
[bluetooth]# default-agent
Default
** Attachment added: "lspci -knn"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576571/+attachment/4651153/+files/lspci-nnk.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "lsusb"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576571/+attachment/4651154/+files/lsusb.log
--
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/1576571
Public bug reported:
16.04 amd64 on an Asus T300 CHI.
I commanded the PC to S3 suspend around 21:30 last evening. Returned to
the PC around 08:00 this morning and discovered the PC wouldn't resume
from suspend and had fully discharged its battery.
After a cold boot restart I investigated the
$ cat /proc/acpi/wakeup
Device S-state Status Sysfs node
PEG0 S4*disabled
PEGP S4*disabled
PEG1 S4*disabled
PEGP S4*disabled
PEG2 S4*disabled
PEGP S4*disabled
RP01 S4*disabled pci::00:1c.0
RP02 S4*disabled
RP03
** Attachment removed: "kern.log starting from a cold boot just before
commanded suspend"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576571/+attachment/4651152/+files/kern.log
** Attachment added: "kern.log starting from a cold boot just before commanded
suspend"
** Description changed:
16.04 amd64 on an Asus T300 CHI.
I commanded the PC to S3 suspend around 21:30 last evening. Returned to
the PC around 08:00 this morning and discovered the PC wouldn't resume
from suspend and had fully discharged its battery.
After a cold boot restart I
>From syslog some associated suspicious systemd-suspend messages with
>correlating timestamps:
$ grep 'systemd-suspend.service: Executing' /var/log/syslog.1
Apr 28 21:34:56 T300CHI systemd[10799]: systemd-suspend.service: Executing:
/lib/systemd/systemd-sleep suspend
Apr 28 21:36:49 T300CHI
** Attachment added: "syslog showing the system seems to remain awake"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576571/+attachment/4651194/+files/syslog
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1 - 100 of 280 matches
Mail list logo