[Kernel-packages] [Bug 1205827] Re: Regression: USB storage broken on 3.10.06-generic

2013-09-20 Thread TJ
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] scsi 8:0:0:0: Direct-Access 
JetFlash Transcend 16GB   1100 PQ: 0 ANSI: 4
Sep 20 19:57:42 XPSm1530 kernel: [  321.746678] sd 8:0:0:0: Attached scsi 
generic sg3 type 0
Sep 20 19:57:42 XPSm1530 kernel: [  321.872237] usb 2-3: reset high-speed USB 
device number 12 using ehci-pci
Sep 20 19:57:42 XPSm1530 kernel: [  322.328062] usb 2-3: reset high-speed USB 
device number 12 using ehci-pci
Sep 20 19:57:43 XPSm1530 kernel: [  322.675711] sd 8:0:0:0: [sdc] 31703040 
512-byte logical blocks: (16.2 GB/15.1 GiB)
Sep 20 19:57:43 XPSm1530 kernel: [  322.800060] usb 2-3: reset high-speed USB 
device number 12 using ehci-pci
Sep 20 19:57:43 XPSm1530 kernel: [  323.152320] sd 8:0:0:0: [sdc] Write Protect 
is off
Sep 20 19:57:43 XPSm1530 kernel: [  323.152329] sd 8:0:0:0: [sdc] Mode Sense: 
43 00 00 00
Sep 20 19:57:43 XPSm1530 kernel: [  323.280101] usb 2-3: reset high-speed USB 
device number 12 using ehci-pci
Sep 20 19:57:44 XPSm1530 kernel: [  323.548080] usb 2-3: reset high-speed USB 
device number 12 using ehci-pci
Sep 20 19:57:44 XPSm1530 kernel: [  323.980720] sd 8:0:0:0: [sdc] No Caching 
mode page present
Sep 20 19:57:44 XPSm1530 kernel: [  323.980726] sd 8:0:0:0: [sdc] Assuming 
drive cache: write through
Sep 20 19:57:44 XPSm1530 kernel: [  324.108094] usb 2-3: reset high-speed USB 
device number 12 using ehci-pci
Sep 20 19:57:45 XPSm1530 kernel: [  324.588064] usb 2-3: reset high-speed USB 
device number 12 using ehci-pci
Sep 20 19:57:45 XPSm1530 kernel: [  325.056254] usb 2-3: reset high-speed USB 
device number 12 using ehci-pci
Sep 20 19:57:46 XPSm1530 kernel: [  325.636093] usb 2-3: reset high-speed USB 
device number 12 using ehci-pci
Sep 20 19:57:46 XPSm1530 kernel: [  326.152092] usb 2-3: reset high-speed USB 
device number 12 using ehci-pci
Sep 20 19:57:46 XPSm1530 kernel: [  326.424092] usb 2-3: reset high-speed USB 
device number 12 using ehci-pci
Sep 20 19:57:47 XPSm1530 kernel: [  326.984073] usb 2-3: reset high-speed USB 
device number 12 using ehci-pci
Sep 20 19:57:47 XPSm1530 kernel: [  327.456089] usb 2-3: reset high-speed USB 
device number 12 using ehci-pci
Sep 20 19:57:48 XPSm1530 kernel: [  327.936083] usb 2-3: reset high-speed USB 
device number 12 using ehci-pci
Sep 20 19:57:48 XPSm1530 kernel: [  328.432067] usb 2-3: reset high-speed USB 
device number 12 using ehci-pci
...

-- 
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/1205827

Title:
  Regression: USB storage broken on 3.10.06-generic

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Saucy:
  Fix Released

Bug description:
  A Kingston 16GB DataTraveler G2 stick is timing out on 3.10.06-generic #17
  If I reboot back to 3.10.04-generic #13 this works
  It also works in another machine running OpenSLES

  [2.687510] scsi 8:0:0:0: Direct-Access Kingston DataTraveler G2  1.00 
PQ: 0 ANSI: 2
  [2.687808] sd 8:0:0:0: Attached scsi generic sg3 type 0
  [2.688665] sd 8:0:0:0: [sdc] 31367168 512-byte logical blocks: (16.0 
GB/14.9 GiB)
  [2.689579] sd 8:0:0:0: [sdc] Write Protect is off
  [2.689586] sd 8:0:0:0: [sdc] Mode Sense: 23 00 00 00
  [2.690455] sd 8:0:0:0: [sdc] No Caching mode page present
  [2.690462] sd 8:0:0:0: [sdc] Assuming drive cache: write through
  [   33.019256] usb 1-1.4: reset high-speed USB device number 3 using ehci-pci

  then later more timeouts:

  [   95.085902] usb 1-1.4: reset high-speed USB device number 3 using ehci-pci
  [  126.087228] usb 1-1.4: reset high-speed USB device number 3 using ehci-pci
  [  126.185164] sd 8:0:0:0: [sdc] No Caching mode page present
  [  126.185171] sd 8:0:0:0: [sdc] Assuming drive cache: write through
  [  157.152730] usb 1-1.4: reset high-speed USB device number 3 using ehci-pci
  [  188.218077] usb 1-1.4: reset high-speed USB device number 3 using ehci-pci

  and udevd hanging on it:
  [  219.219390] usb 1-1.4: reset high-speed USB device number 3 using ehci-pci
  [  240.960930] INFO: task systemd-udevd:156 blocked for more than 120 seconds.
  [  240.963953] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.
  [  240.966892] systemd-udevd   D 880237d54480 0   156  1 
0x0004

  this boot it did eventually make it into /proc/partitions, on the last
  boot it gave up and was only in /proc/scsi/scsi

  (Saucy+KDE)

  Dave

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.10.0-6-generic 3.10.0-6.17
  ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
  Uname: Linux 3.10.0-6-generic x86_64
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  

[Kernel-packages] [Bug 1229307] Re: paired device doesn't reconnect after suspend

2013-09-27 Thread TJ
*** 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, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1229307

Title:
  paired device doesn't reconnect after suspend

Status in “bluez” package in Ubuntu:
  New

Bug description:
  I use a bluetooth mouse. After I suspend/resume the system, I have
  issues using it.

  One workaround I found is to go into the bluetooth menu, select the
  menu Microsoft bluetooth mouse 5000, and click on the (already
  ticked!) Connection submenu.

  This causes the bluetooth menu to disappear entirely and reappear
  after an instant. THEN the mouse is actually connected and usable.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluez 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
  Uname: Linux 3.11.0-7-generic x86_64
  ApportVersion: 2.12.4-0ubuntu1
  Architecture: amd64
  Date: Mon Sep 23 19:10:12 2013
  InstallationDate: Installed on 2013-02-14 (220 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  InterestingModules: btusb rfcomm bnep bluetooth
  MachineType: FUJITSU SIEMENS LIFEBOOK P8010
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-7-generic 
root=UUID=a7c2748a-3784-49ab-aac1-ee1f5b62b769 ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to saucy on 2013-09-08 (15 days ago)
  dmi.bios.date: 08/20/2008
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.08
  dmi.board.name: FJNB1E3
  dmi.board.vendor: FUJITSU
  dmi.board.version: CP365186-01
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU SIEMENS
  dmi.chassis.version: P8010
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.08:bd08/20/2008:svnFUJITSUSIEMENS:pnLIFEBOOKP8010:pvr:rvnFUJITSU:rnFJNB1E3:rvrCP365186-01:cvnFUJITSUSIEMENS:ct10:cvrP8010:
  dmi.product.name: LIFEBOOK P8010
  dmi.sys.vendor: FUJITSU SIEMENS
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:03:7A:76:AE:F9  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:10084 acl:618 sco:0 events:57 errors:0
TX bytes:570 acl:12 sco:0 commands:23 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1229307/+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 1075478] Re: bluetooth keyboards and mice not working after suspend/resume

2013-10-18 Thread TJ
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 bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1075478

Title:
  bluetooth keyboards and mice not working after suspend/resume

Status in xserver-xorg-input-evdev:
  Unknown
Status in The Linux Kernel:
  Confirmed
Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  After upgrading to Ubuntu 12.10 I encountered the following problem:

  I have my apple wireless bluetooth keyboard paired up to Ubuntu, and
  it works fine when I boot up my laptop (HP EliteBook 8530w) as soon as
  I hit the login screen. However, if I then suspend and resume my
  laptop again, the bluetooth keyboard does not respond anymore.
  According to the bluetooth GUI applet it is still succesfully paired
  up and connected, and I see the green light on my keyboard blinking a
  few times when I hit a key for the first time after resume which is
  also the case when it _does_ work, but I get no response whatsoever
  from Ubuntu when typing on my keyboard.

  sudo service bluetooth restart does not work.

  Please let me know what additional information to provide.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evdev/+bug/1075478/+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 1235162] Re: Persistent net names via /etc/udev/rules.d/70-persistent-net.rules are ignored

2013-10-05 Thread TJ
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 *net, const char *name)
{
struct net_device *dev;
struct hlist_head *head = dev_name_hash(net, name);

hlist_for_each_entry_rcu(dev, head, name_hlist)
if (!strncmp(dev-name, name, IFNAMSIZ))
return dev;

return NULL;
}

static int dev_get_valid_name(struct net *net,
  struct net_device *dev,
  const char *name)
{
BUG_ON(!net);

if (!dev_valid_name(name))
return -EINVAL;

if (strchr(name, '%'))
return dev_alloc_name_ns(net, dev, name);
else if (__dev_get_by_name(net, name))
return -EEXIST;
else if (dev-name != name)
strlcpy(dev-name, name, IFNAMSIZ);

return 0;
}

So this seems to be where the IOCTL error originates, but there needs to
be an explanation.

Looking at the 'git damage' and commit history for 'net/core/dev.c' in
particular there are some control-group related changes that look like
they may be implicated. They certainly seem to be in the appropriate
time-frame since earlier kernels don't have the problem (I have another
server with 12.04 LTS and Linux 3.2.0 which has 10 Ethernet ports which
are renamed correctly).


** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- Persistent net names via /etc/udev/rules.d/70-persistent-net.rules are ignored
+ Persistent net names via /etc/udev/rules.d/70-persistent-net.rules fail

** Description changed:

  systemd-udev 204.
  
  Installing 13.10 amd64 on a multi-homed server. There are 5 ethernet
  interfaces, one on the mobo and four on a PCIe adapter.
  
  udev created /etc/udev/rules.d/70-persistent-net.rules and I later
  edited the NAME= assignments to match the device naming required.
  
- These rules are being ignored and I can't find any indication as to why.
+ These rules are apparently ignored but it transpires that the kernel is
+ returning -EEXIST from net/core/dev.c::dev_get_valid_name().
+ 
+ This renaming works in earlier versions, specifically on a 12.04 LTS
+ server with ten Ethernet interfaces, and is therefore a regression.

-- 
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:
  Persistent net names via /etc/udev/rules.d/70-persistent-net.rules
  fail

Status in “linux” package in Ubuntu:
  New
Status in “systemd” package in Ubuntu:
  New

Bug description:
  systemd-udev 204.

  Installing 13.10 amd64 on a multi-homed server. There are 5 ethernet
  interfaces, one on the mobo and four on a PCIe adapter.

  udev created /etc/udev/rules.d/70-persistent-net.rules and I later
  edited the NAME= assignments to match the device naming required.

  These rules are apparently ignored but it transpires that the kernel
  is returning -EEXIST from net/core/dev.c::dev_get_valid_name().

  This renaming works in earlier versions, specifically on a 12.04 LTS
  server with ten Ethernet interfaces, and is therefore a regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235162/+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 1235162] Re: Persistent net names via /etc/udev/rules.d/70-persistent-net.rules fail

2013-10-05 Thread TJ
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 97595710b77aa162ca5e20da57d0a1ed7355eaad
Author: Kay Sievers k...@vrfy.org
Date:   Thu Jul 5 17:40:50 2012 +0200

udev: network device renaming - immediately give up if the target
name isn't available


** Changed in: linux (Ubuntu)
   Status: Incomplete = Invalid

** Changed in: systemd (Ubuntu)
   Status: New = Triaged

** Summary changed:

- Persistent net names via /etc/udev/rules.d/70-persistent-net.rules fail
+ Regression: Persistent net names via 
/etc/udev/rules.d/70-persistent-net.rules fail

-- 
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-persistent-
  net.rules fail

Status in “linux” package in Ubuntu:
  Invalid
Status in “systemd” package in Ubuntu:
  Triaged

Bug description:
  systemd-udev 204.

  Installing 13.10 amd64 on a multi-homed server. There are 5 ethernet
  interfaces, one on the mobo and four on a PCIe adapter.

  udev created /etc/udev/rules.d/70-persistent-net.rules and I later
  edited the NAME= assignments to match the device naming required.

  These rules are apparently ignored but it transpires that the kernel
  is returning -EEXIST from net/core/dev.c::dev_get_valid_name().

  This renaming works in earlier versions, specifically on a 12.04 LTS
  server with ten Ethernet interfaces, and is therefore a regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235162/+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 1235162] Re: Regression: Persistent net names via /etc/udev/rules.d/70-persistent-net.rules fail

2013-10-05 Thread TJ
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.
https://bugs.launchpad.net/bugs/1235162

Title:
  Regression: Persistent net names via /etc/udev/rules.d/70-persistent-
  net.rules fail

Status in “linux” package in Ubuntu:
  Invalid
Status in “systemd” package in Ubuntu:
  Triaged

Bug description:
  systemd-udev 204.

  Installing 13.10 amd64 on a multi-homed server. There are 5 ethernet
  interfaces, one on the mobo and four on a PCIe adapter.

  udev created /etc/udev/rules.d/70-persistent-net.rules and I later
  edited the NAME= assignments to match the device naming required.

  These rules are apparently ignored but it transpires that the kernel
  is returning -EEXIST from net/core/dev.c::dev_get_valid_name().

  This renaming works in earlier versions, specifically on a 12.04 LTS
  server with ten Ethernet interfaces, and is therefore a regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235162/+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 1235162] Re: Regression: Persistent net names via /etc/udev/rules.d/70-persistent-net.rules fail

2013-10-05 Thread TJ
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.
https://bugs.launchpad.net/bugs/1235162

Title:
  Regression: Persistent net names via /etc/udev/rules.d/70-persistent-
  net.rules fail

Status in “linux” package in Ubuntu:
  Invalid
Status in “systemd” package in Ubuntu:
  Triaged

Bug description:
  systemd-udev 204.

  Installing 13.10 amd64 on a multi-homed server. There are 5 ethernet
  interfaces, one on the mobo and four on a PCIe adapter.

  udev created /etc/udev/rules.d/70-persistent-net.rules and I later
  edited the NAME= assignments to match the device naming required.

  These rules are apparently ignored but it transpires that the kernel
  is returning -EEXIST from net/core/dev.c::dev_get_valid_name().

  This renaming works in earlier versions, specifically on a 12.04 LTS
  server with ten Ethernet interfaces, and is therefore a regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235162/+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 1235162] Re: Regression: Persistent net names via /etc/udev/rules.d/70-persistent-net.rules fail

2013-10-05 Thread TJ
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 /devices/pci:00/:00:07.0/net/rename4 (net)
ACTION=move
DEVPATH=/devices/pci:00/:00:07.0/net/rename4
--
KERNEL[19.449910] move 
/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.1/net/rename6
 (net)
ACTION=move
DEVPATH=/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.1/net/rename6
--
KERNEL[19.472417] move 
/devices/pci:00/:00:09.0/:02:00.0/:03:00.0/:04:00.0/net/eth2
 (net)
ACTION=move
DEVPATH=/devices/pci:00/:00:09.0/:02:00.0/:03:00.0/:04:00.0/net/eth2
--
KERNEL[19.488425] move 
/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.0/net/eth4
 (net)
ACTION=move
DEVPATH=/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.0/net/eth4
--
KERNEL[19.504160] move /devices/pci:00/:00:07.0/net/eth0 (net)
ACTION=move
DEVPATH=/devices/pci:00/:00:07.0/net/eth0
--
KERNEL[19.528341] move 
/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.1/net/eth3
 (net)
ACTION=move
DEVPATH=/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.1/net/eth3
--
UDEV  [26.859211] move /devices/pci:00/:00:07.0/net/rename4 (net)
ACTION=move
DEVPATH=/devices/pci:00/:00:07.0/net/rename4
--
UDEV  [26.878494] move 
/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.1/net/rename6
 (net)
ACTION=move
DEVPATH=/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.1/net/rename6
--
UDEV  [26.880061] move 
/devices/pci:00/:00:09.0/:02:00.0/:03:00.0/:04:00.0/net/eth2
 (net)
ACTION=move
DEVPATH=/devices/pci:00/:00:09.0/:02:00.0/:03:00.0/:04:00.0/net/eth2
--
UDEV  [26.881605] move 
/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.0/net/eth4
 (net)
ACTION=move
DEVPATH=/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.0/net/eth4
--
UDEV  [26.883240] move /devices/pci:00/:00:07.0/net/eth0 (net)
ACTION=move
DEVPATH=/devices/pci:00/:00:07.0/net/eth0
--
UDEV  [26.884382] move 
/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.1/net/eth3
 (net)
ACTION=move
DEVPATH=/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.1/net/eth3

$ ifconfig -a | grep '^eth'
eth0  Link encap:Ethernet  HWaddr 00:25:22:75:e6:9e  
eth1  Link encap:Ethernet  HWaddr 00:15:17:8f:99:c0  
eth2  Link encap:Ethernet  HWaddr 00:15:17:8f:99:c1  
eth3  Link encap:Ethernet  HWaddr 00:15:17:8f:99:c2  
eth4  Link encap:Ethernet  HWaddr 00:15:17:8f:99:c3

$ sudo ifup -a 21 | tee /tmp/ifup.log
Reading directory /etc/network/interfaces.d
Parsing file /etc/network/interfaces.d/eth0
Parsing file /etc/network/interfaces.d/eth1
Parsing file /etc/network/interfaces.d/eth2
Parsing file /etc/network/interfaces.d/eth3
Parsing file /etc/network/interfaces.d/eth4
Parsing file /etc/network/interfaces.d/lo
run-parts --verbose /etc/network/if-pre-up.d
ip link set up dev lo 2/dev/null
Configuring interface lo=lo (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/000resolvconf
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/postfix
run-parts: executing /etc/network/if-up.d/upstart
Configuring interface lo=lo (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/000resolvconf
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/postfix
run-parts: executing /etc/network/if-up.d/upstart
Configuring interface eth0=eth0 (inet)
run-parts --verbose /etc/network/if-pre-up.d

dhclient -1 -v -pf /run/dhclient.eth0.pid -lf 
/var/lib/dhcp/dhclient.eth0.leases eth0   
Internet Systems Consortium DHCP Client 4.2.4
Copyright 2004-2012 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/00:25:22:75:e6:9e
Sending on   LPF/eth0/00:25:22:75:e6:9e
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0x4c6d33c1)
DHCPREQUEST of 10.254.251.3 on eth0 to 255.255.255.255 port 67 (xid=0x4c6d33c1)
DHCPOFFER of 10.254.251.3 from 10.254.251.1
DHCPACK of 10.254.251.3 from 10.254.251.1
bound to 10.254.251.3 -- renewal in 10401 seconds.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/000resolvconf
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/postfix
run-parts: executing /etc/network/if-up.d/upstart
Configuring interface eth1=eth1 

[Kernel-packages] [Bug 1235162] Re: Regression: Persistent net names via /etc/udev/rules.d/70-persistent-net.rules fail

2013-10-05 Thread TJ
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
DEVPATH_OLD=/devices/pci:00/:00:07.0/net/eth2
--
KERNEL[19.449910] move 
/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.1/net/rename6
 (net)
ACTION=move
DEVPATH=/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.1/net/rename6
DEVPATH_OLD=/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.1/net/eth4
--
KERNEL[19.472417] move 
/devices/pci:00/:00:09.0/:02:00.0/:03:00.0/:04:00.0/net/eth2
 (net)
ACTION=move
DEVPATH=/devices/pci:00/:00:09.0/:02:00.0/:03:00.0/:04:00.0/net/eth2
DEVPATH_OLD=/devices/pci:00/:00:09.0/:02:00.0/:03:00.0/:04:00.0/net/eth0
--
KERNEL[19.488425] move 
/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.0/net/eth4
 (net)
ACTION=move
DEVPATH=/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.0/net/eth4
DEVPATH_OLD=/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.0/net/eth3
--
KERNEL[19.504160] move /devices/pci:00/:00:07.0/net/eth0 (net)
ACTION=move
DEVPATH=/devices/pci:00/:00:07.0/net/eth0
DEVPATH_OLD=/devices/pci:00/:00:07.0/net/rename4
--
KERNEL[19.528341] move 
/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.1/net/eth3
 (net)
ACTION=move
DEVPATH=/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.1/net/eth3
DEVPATH_OLD=/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.1/net/rename6
--
UDEV  [26.859211] move /devices/pci:00/:00:07.0/net/rename4 (net)
ACTION=move
DEVPATH=/devices/pci:00/:00:07.0/net/rename4
DEVPATH_OLD=/devices/pci:00/:00:07.0/net/eth2
--
UDEV  [26.878494] move 
/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.1/net/rename6
 (net)
ACTION=move
DEVPATH=/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.1/net/rename6
DEVPATH_OLD=/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.1/net/eth4
--
UDEV  [26.880061] move 
/devices/pci:00/:00:09.0/:02:00.0/:03:00.0/:04:00.0/net/eth2
 (net)
ACTION=move
DEVPATH=/devices/pci:00/:00:09.0/:02:00.0/:03:00.0/:04:00.0/net/eth2
DEVPATH_OLD=/devices/pci:00/:00:09.0/:02:00.0/:03:00.0/:04:00.0/net/eth0
--
UDEV  [26.881605] move 
/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.0/net/eth4
 (net)
ACTION=move
DEVPATH=/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.0/net/eth4
DEVPATH_OLD=/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.0/net/eth3
--
UDEV  [26.883240] move /devices/pci:00/:00:07.0/net/eth0 (net)
ACTION=move
DEVPATH=/devices/pci:00/:00:07.0/net/eth0
DEVPATH_OLD=/devices/pci:00/:00:07.0/net/rename4
--
UDEV  [26.884382] move 
/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.1/net/eth3
 (net)
ACTION=move
DEVPATH=/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.1/net/eth3
DEVPATH_OLD=/devices/pci:00/:00:09.0/:02:00.0/:03:01.0/:05:00.1/net/rename6

-- 
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-persistent-
  net.rules fail

Status in “linux” package in Ubuntu:
  Invalid
Status in “systemd” package in Ubuntu:
  Triaged

Bug description:
  systemd-udev 204.

  Installing 13.10 amd64 on a multi-homed server. There are 5 ethernet
  interfaces, one on the mobo and four on a PCIe adapter.

  udev created /etc/udev/rules.d/70-persistent-net.rules and I later
  edited the NAME= assignments to match the device naming required.

  These rules are apparently ignored but it transpires that the kernel
  is returning -EEXIST from net/core/dev.c::dev_get_valid_name().

  This renaming works in earlier versions, specifically on a 12.04 LTS
  server with ten Ethernet interfaces, and is therefore a regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235162/+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 1235162] Re: Regression: Persistent net names via /etc/udev/rules.d/70-persistent-net.rules fail

2013-10-07 Thread TJ
** 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-persistent-
  net.rules fail

Status in “linux” package in Ubuntu:
  Invalid
Status in “systemd” package in Ubuntu:
  Triaged

Bug description:
  systemd-udev 204.

  Installing 13.10 amd64 on a multi-homed server. There are 5 ethernet
  interfaces, one on the mobo and four on a PCIe adapter.

  udev created /etc/udev/rules.d/70-persistent-net.rules and I later
  edited the NAME= assignments to match the device naming required.

  These rules are apparently ignored but it transpires that the kernel
  is returning -EEXIST from net/core/dev.c::dev_get_valid_name().

  This renaming works in earlier versions, specifically on a 12.04 LTS
  server with ten Ethernet interfaces, and is therefore a regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235162/+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 1063474] Re: System fails to connect to iHOS-104 DVD drive with nvidia MCP61 chipset.

2013-09-08 Thread tj
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 we don't know about, but it's hard to say what that
 might be. The fact that the default drivers used in the WinPE boot
 don't seem to work would tend to point toward some kind of hardware
 incompatibility issue.
 
 Tejun, think you poked with some of this stuff before - any ideas?

It has been years since I looked at MCP quirks, of which there are too
many.  It's likely another quirk on the controller side that nvidia
worked around somehow without telling anyone.  Given the history and
that nvidia is out of chipset market, I think it's highly unlikely to
learn what the issue and workaround are without reverse engineering
it.  So, um, no idea.

Thanks.

-- 
tejun

-- 
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/1063474

Title:
  System fails to connect to iHOS-104 DVD drive with nvidia MCP61
  chipset.

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  The computer fails to connect to the LG iHOS-104 DVD drive.
  The drive is working, as it will boot the Windows installer.

  I have seen similar bugs posted on the internet for the past 5 years.
  Here's a thread that shows the problem fixed for the MCP55 chipset.

  http://www.gossamer-
  threads.com/lists/linux/kernel/1234502?do=post_view_threaded#1234502

  WORKAROUND: Use the DVD drive with a USB-SATA adapter.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-17-generic 3.5.0-17.27
  ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  watchtv7366 F pulseaudio
   /dev/snd/controlC0:  watchtv4814 F alsamixer
    watchtv7366 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Sun Oct  7 19:34:10 2012
  HibernationDevice: RESUME=UUID=914386c4-84a9-4eb4-8382-cb6f877f7ef6
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 002 Device 006: ID 046d:c047 Logitech, Inc. Laser Mouse
   Bus 002 Device 005: ID 0e8f:0021 GreenAsia Inc. Multimedia Keyboard 
Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Gigabyte Technology Co., Ltd. M68M-S2P
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=81823799-2b15-4236-887b-e3497f3f6a46 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-17-generic N/A
   linux-backports-modules-3.5.0-17-generic  N/A
   linux-firmware1.94
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:

  dmi.bios.date: 07/15/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FCb
  dmi.board.name: M68M-S2P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFCb:bd07/15/2010:svnGigabyteTechnologyCo.,Ltd.:pnM68M-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM68M-S2P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: M68M-S2P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  ---
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  watchtv1305 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   [   55.165828] pool[1480]: segfault at 40 ip 7f3d05544f87 sp 
7f3d03653c50 error 4 in tumbler-gst-thumbnailer.so[7f3d05542000+4000]
   [  707.285402] python[6778]: segfault at 0 ip 7eff23bde2f7 sp 
7fffeba941f8 error 4 in libgtk-3.so.0.800.2[7eff23ade000+4c5000]
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=914386c4-84a9-4eb4-8382-cb6f877f7ef6
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e8f:0021 GreenAsia Inc. Multimedia Keyboard 
Controller
   Bus 002 Device 002: ID 045e:0719 Microsoft Corp. Xbox 360 Wireless Adapter
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Gigabyte Technology Co., Ltd. M68M-S2P
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 342926] Re: No PCI IOMEM space available below 4GB

2013-09-10 Thread TJ
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 remains a problem for the hardware out there still in use where
the user wants to install and use the maximum RAM possible but the
32-bit limitation prevents the PCIOMEM addresses being remapped above
the 4GB boundary.

** Changed in: linux (Ubuntu)
   Status: Incomplete = Triaged

-- 
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/342926

Title:
  No PCI IOMEM space available below 4GB

Status in The Linux Kernel:
  Confirmed
Status in “linux” package in Ubuntu:
  Triaged
Status in “nvidia-graphics-drivers-180” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: nvidia-glx-180

  This can affect almost all releases (6.10 7.04, 7.10, 8.04, 8.10,
  9.04+)

  It usually only shows up dramatically with video cards that have large
  memory (e.g. 256MB) and on systems that

  a) have 3GB or more RAM and/or
  b) have 64-bit CPUs on 32-bit north-bridge chipsets (e.g. Intel 945)

  Typical symptom: failed to load the nvidia kernel module

  This issue could affect all versions of the Nvidia proprietary drivers
  and others.

  Recently I've seen several users in IRC #ubuntu asking for help but
  without solving the issue. When I saw Keith Dewitt asking the same
  question on 2009-03-14 I arranged with him to access his system via
  SSH and a multiuser screen session to diagnose the issue. Keith was
  very patient and supportive and his assistance led directly to this
  discovery.

  There are also threads on the nvidia forums with the same issues.

  The symptoms are that users report that systems with Nvidia-based
  graphics cards won't start the X server successfully. There are a wide
  range of reports that don't immediately pin-point the cause.

  The fact the nvidia kernel module failed to load is the biggest clue.

  Check dmesg and /var/log/kern.log for something along these lines:

  [   20.137717] nvidia: module license 'NVIDIA' taints kernel. 
  
  [   20.412849] ACPI: PCI Interrupt Link [LNEB] enabled at IRQ 18  
  
  [   20.412858] nvidia :02:00.0: PCI INT A - Link[LNEB] - GSI 18 (level, 
low) - IRQ 18  
  
  [   20.412862] NVRM: This PCI I/O region assigned to your NVIDIA device is 
invalid:
  [   20.412862] NVRM: BAR1 is 256M @ 0x3000 (PCI:0002:00.0)
  
  [   20.412865] NVRM: This is a 64-bit BAR mapped above 4GB by the system BIOS 
or
  [   20.412865] NVRM: Linux kernel. The NVIDIA Linux graphics driver and other 
  
  [   20.412866] NVRM: system software do not currently support this 
configuration
  [   20.412867] NVRM: reliably.
  
  [   20.412872] nvidia: probe of :02:00.0 failed with error -1 
  
  [   20.412887] NVRM: The NVIDIA probe routine failed for 1 device(s). 
  
  [   20.412889] NVRM: None of the NVIDIA graphics adapters were initialized!   
  

  Also check /var/log/Xorg.0.log or /var/log/Xorg.0.log.old for this
  tell-tale:

  (--) PCI:*(0@2:0:0) nVidia Corporation GeForce 8400 GS rev 161, Mem @ 
0xfd00
  /16777216, 0x13000/268435456, 0xfa00/33554432, I/O @ 0xec00/128, 
BIO
  S @ 0x/131072

  (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
  (==) NVIDIA(0): RGB weight 888
  (==) NVIDIA(0): Default visual is TrueColor
  (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
  (**) NVIDIA(0): Enabling RENDER acceleration
  (II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
  (II) NVIDIA(0): enabled.
  (EE) NVIDIA(0): Failed to load the NVIDIA kernel module!
  (EE) NVIDIA(0):  *** Aborting ***
  (II) UnloadModule: nvidia

  Notice that the video card's IOMEM allocation is at 5GB
  (0x13000/268435456 = 5GB/256MB).

  /var/log/dmesg shows:

  [0.00]  BIOS-e820: 0001 - 00013000
  (usable)

  [0.477047] pci :00:0b.0: BAR 9: can't allocate resource
  [0.477047] pci :02:00.0: BAR 1: can't allocate resource 

  lspci -nn reveals:
  00:0b.0 PCI bridge [0604]: nVidia Corporation MCP73 PCI Express bridge 
[10de:056
  e] (rev a1)
  02:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 8400 GS 
[10
  de:0404] (rev a1)

  lspci -vvnn -s 02:00.0

  02:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 8400 GS 
[10
  de:0404] (rev a1) 
  
  Subsystem: eVga.com. Corp. Device [3842:c738] 
  
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Step
  ping- 

[Kernel-packages] [Bug 342926] Re: No PCI IOMEM space available below 4GB

2013-09-11 Thread TJ
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 subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/342926

Title:
  No PCI IOMEM space available below 4GB

Status in The Linux Kernel:
  Confirmed
Status in “linux” package in Ubuntu:
  Triaged
Status in “nvidia-graphics-drivers-180” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: nvidia-glx-180

  This can affect almost all releases (6.10 7.04, 7.10, 8.04, 8.10,
  9.04+)

  It usually only shows up dramatically with video cards that have large
  memory (e.g. 256MB) and on systems that

  a) have 3GB or more RAM and/or
  b) have 64-bit CPUs on 32-bit north-bridge chipsets (e.g. Intel 945)

  Typical symptom: failed to load the nvidia kernel module

  This issue could affect all versions of the Nvidia proprietary drivers
  and others.

  Recently I've seen several users in IRC #ubuntu asking for help but
  without solving the issue. When I saw Keith Dewitt asking the same
  question on 2009-03-14 I arranged with him to access his system via
  SSH and a multiuser screen session to diagnose the issue. Keith was
  very patient and supportive and his assistance led directly to this
  discovery.

  There are also threads on the nvidia forums with the same issues.

  The symptoms are that users report that systems with Nvidia-based
  graphics cards won't start the X server successfully. There are a wide
  range of reports that don't immediately pin-point the cause.

  The fact the nvidia kernel module failed to load is the biggest clue.

  Check dmesg and /var/log/kern.log for something along these lines:

  [   20.137717] nvidia: module license 'NVIDIA' taints kernel. 
  
  [   20.412849] ACPI: PCI Interrupt Link [LNEB] enabled at IRQ 18  
  
  [   20.412858] nvidia :02:00.0: PCI INT A - Link[LNEB] - GSI 18 (level, 
low) - IRQ 18  
  
  [   20.412862] NVRM: This PCI I/O region assigned to your NVIDIA device is 
invalid:
  [   20.412862] NVRM: BAR1 is 256M @ 0x3000 (PCI:0002:00.0)
  
  [   20.412865] NVRM: This is a 64-bit BAR mapped above 4GB by the system BIOS 
or
  [   20.412865] NVRM: Linux kernel. The NVIDIA Linux graphics driver and other 
  
  [   20.412866] NVRM: system software do not currently support this 
configuration
  [   20.412867] NVRM: reliably.
  
  [   20.412872] nvidia: probe of :02:00.0 failed with error -1 
  
  [   20.412887] NVRM: The NVIDIA probe routine failed for 1 device(s). 
  
  [   20.412889] NVRM: None of the NVIDIA graphics adapters were initialized!   
  

  Also check /var/log/Xorg.0.log or /var/log/Xorg.0.log.old for this
  tell-tale:

  (--) PCI:*(0@2:0:0) nVidia Corporation GeForce 8400 GS rev 161, Mem @ 
0xfd00
  /16777216, 0x13000/268435456, 0xfa00/33554432, I/O @ 0xec00/128, 
BIO
  S @ 0x/131072

  (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
  (==) NVIDIA(0): RGB weight 888
  (==) NVIDIA(0): Default visual is TrueColor
  (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
  (**) NVIDIA(0): Enabling RENDER acceleration
  (II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
  (II) NVIDIA(0): enabled.
  (EE) NVIDIA(0): Failed to load the NVIDIA kernel module!
  (EE) NVIDIA(0):  *** Aborting ***
  (II) UnloadModule: nvidia

  Notice that the video card's IOMEM allocation is at 5GB
  (0x13000/268435456 = 5GB/256MB).

  /var/log/dmesg shows:

  [0.00]  BIOS-e820: 0001 - 00013000
  (usable)

  [0.477047] pci :00:0b.0: BAR 9: can't allocate resource
  [0.477047] pci :02:00.0: BAR 1: can't allocate resource 

  lspci -nn reveals:
  00:0b.0 PCI bridge [0604]: nVidia Corporation MCP73 PCI Express bridge 
[10de:056
  e] (rev a1)
  02:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 8400 GS 
[10
  de:0404] (rev a1)

  lspci -vvnn -s 02:00.0

  02:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 8400 GS 
[10
  de:0404] (rev a1) 
  
  Subsystem: eVga.com. Corp. Device [3842:c738] 
  
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Step
  ping- SERR- FastB2B- DisINTx- 
  
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- 
TAbort- 
  MAbort- SERR- PERR- INTx-  
  
  Latency: 0, Cache Line Size: 64 bytes
  Interrupt: pin A routed to IRQ 18
  Region 0: Memory at fd00 (32-bit, 

[Kernel-packages] [Bug 342926] Re: No PCI IOMEM space available below 4GB

2013-09-12 Thread TJ
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 previously described.

Any updates should be posted to the linked mainline Linux bug-tracker.

** Tags removed: needs-kernel-logs

-- 
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/342926

Title:
  No PCI IOMEM space available below 4GB

Status in The Linux Kernel:
  Confirmed
Status in “linux” package in Ubuntu:
  Triaged
Status in “nvidia-graphics-drivers-180” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: nvidia-glx-180

  This can affect almost all releases (6.10 7.04, 7.10, 8.04, 8.10,
  9.04+)

  It usually only shows up dramatically with video cards that have large
  memory (e.g. 256MB) and on systems that

  a) have 3GB or more RAM and/or
  b) have 64-bit CPUs on 32-bit north-bridge chipsets (e.g. Intel 945)

  Typical symptom: failed to load the nvidia kernel module

  This issue could affect all versions of the Nvidia proprietary drivers
  and others.

  Recently I've seen several users in IRC #ubuntu asking for help but
  without solving the issue. When I saw Keith Dewitt asking the same
  question on 2009-03-14 I arranged with him to access his system via
  SSH and a multiuser screen session to diagnose the issue. Keith was
  very patient and supportive and his assistance led directly to this
  discovery.

  There are also threads on the nvidia forums with the same issues.

  The symptoms are that users report that systems with Nvidia-based
  graphics cards won't start the X server successfully. There are a wide
  range of reports that don't immediately pin-point the cause.

  The fact the nvidia kernel module failed to load is the biggest clue.

  Check dmesg and /var/log/kern.log for something along these lines:

  [   20.137717] nvidia: module license 'NVIDIA' taints kernel. 
  
  [   20.412849] ACPI: PCI Interrupt Link [LNEB] enabled at IRQ 18  
  
  [   20.412858] nvidia :02:00.0: PCI INT A - Link[LNEB] - GSI 18 (level, 
low) - IRQ 18  
  
  [   20.412862] NVRM: This PCI I/O region assigned to your NVIDIA device is 
invalid:
  [   20.412862] NVRM: BAR1 is 256M @ 0x3000 (PCI:0002:00.0)
  
  [   20.412865] NVRM: This is a 64-bit BAR mapped above 4GB by the system BIOS 
or
  [   20.412865] NVRM: Linux kernel. The NVIDIA Linux graphics driver and other 
  
  [   20.412866] NVRM: system software do not currently support this 
configuration
  [   20.412867] NVRM: reliably.
  
  [   20.412872] nvidia: probe of :02:00.0 failed with error -1 
  
  [   20.412887] NVRM: The NVIDIA probe routine failed for 1 device(s). 
  
  [   20.412889] NVRM: None of the NVIDIA graphics adapters were initialized!   
  

  Also check /var/log/Xorg.0.log or /var/log/Xorg.0.log.old for this
  tell-tale:

  (--) PCI:*(0@2:0:0) nVidia Corporation GeForce 8400 GS rev 161, Mem @ 
0xfd00
  /16777216, 0x13000/268435456, 0xfa00/33554432, I/O @ 0xec00/128, 
BIO
  S @ 0x/131072

  (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
  (==) NVIDIA(0): RGB weight 888
  (==) NVIDIA(0): Default visual is TrueColor
  (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
  (**) NVIDIA(0): Enabling RENDER acceleration
  (II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
  (II) NVIDIA(0): enabled.
  (EE) NVIDIA(0): Failed to load the NVIDIA kernel module!
  (EE) NVIDIA(0):  *** Aborting ***
  (II) UnloadModule: nvidia

  Notice that the video card's IOMEM allocation is at 5GB
  (0x13000/268435456 = 5GB/256MB).

  /var/log/dmesg shows:

  [0.00]  BIOS-e820: 0001 - 00013000
  (usable)

  [0.477047] pci :00:0b.0: BAR 9: can't allocate resource
  [0.477047] pci :02:00.0: BAR 1: can't allocate resource 

  lspci -nn reveals:
  00:0b.0 PCI bridge [0604]: nVidia Corporation MCP73 PCI Express bridge 
[10de:056
  e] (rev a1)
  02:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 8400 GS 
[10
  de:0404] (rev a1)

  lspci -vvnn -s 02:00.0

  02:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 8400 GS 
[10
  de:0404] (rev a1) 
  
  Subsystem: eVga.com. Corp. Device [3842:c738] 
  
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Step
  ping- SERR- FastB2B- DisINTx- 
  
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- 
TAbort- 
  

[Kernel-packages] [Bug 1341275] Re: [Gigabyte GB-BXi7-4470R] Kernel panic in rtl8821ae

2014-08-07 Thread TJ
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 module since there is nothing we can do downstream to make it work.

[   13.738475] rtl8821ae: module is from the staging directory, the
quality is unknown, you have been warned.

-- v3.16 kernel --
[   14.019892] WARNING: CPU: 0 PID: 321 at 
/home/apw/COD/linux/net/wireless/reg.c:1555 
wiphy_apply_custom_regulatory+0xbc/0xe0 [cfg80211]()
[   14.019894] wiphy should have REGULATORY_CUSTOM_REG
[   14.019896] Modules linked in: asus_nb_wmi(+) intel_soc_dts_thermal(-) 
intel_powerclamp asus_wmi sparse_keymap coretemp rtl8821ae(C+) kvm mac80211 
crct10dif_pclmul btusb crc32_pclmul ghash_clmulni_intel bluetooth uvcvideo 
cryptd cfg80211 videobuf2_vmalloc joydev videobuf2_memops videobuf2_core 
snd_soc_rt5640 v4l2_common snd_hda_intel(+) snd_soc_rl6231 serio_raw 
snd_hda_controller videodev snd_soc_core media snd_hda_codec snd_compress 
snd_pcm_dmaengine rtsx_pci_ms snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_hwdep 6lowpan_iphc lpc_ich(+) memstick snd_pcm snd_seq wmi i915(+) 
snd_seq_device snd_timer snd i2c_hid hid soundcore dw_dmac video dw_dmac_core 
drm_kms_helper drm i2c_designware_platform i2c_algo_bit i2c_designware_core 
parport_pc spi_pxa2xx_platform pwm_lpss ppdev mac_hid lp 8250_dw mei_txe 
parport mei snd_soc_sst_acpi iosf_mbi rtsx_pci_sdmmc psmouse r8169 mii ahci 
rtsx_pci libahci sdhci_acpi sdhci
[   14.019972] CPU: 0 PID: 321 Comm: systemd-udevd Tainted: G C
3.16.0-031600-generic #201408031935
[   14.019975] Hardware name: ASUSTeK COMPUTER INC. X551MA/X551MA, BIOS 
X551MA.402 02/08/2014
[   14.019978]  0613 8800b1633a18 82786525 
3f8a
[   14.019984]  8800b1633a68 8800b1633a58 8207207c 
c0a9bfb8
[   14.019988]  c0a8d1e0 8800aff00260 c0a48ab0 
8800aff01840
[   14.019993] Call Trace:
[   14.020003]  [82786525] dump_stack+0x46/0x58
[   14.020010]  [8207207c] warn_slowpath_common+0x8c/0xc0
[   14.020031]  [c0a48ab0] ? rtl_regd_init+0x310/0x310 [rtl8821ae]
[   14.020036]  [82072166] warn_slowpath_fmt+0x46/0x50
[   14.020053]  [c078327c] wiphy_apply_custom_regulatory+0xbc/0xe0 
[cfg80211]
[   14.020067]  [c0a48ab0] ? rtl_regd_init+0x310/0x310 [rtl8821ae]
[   14.020080]  [c0a488f2] rtl_regd_init+0x152/0x310 [rtl8821ae]
[   14.020095]  [c0a43c81] rtl_init_core+0x41/0x170 [rtl8821ae]
[   14.020110]  [c0a57cd9] rtl_pci_probe+0x289/0x910 [rtl8821ae]
[   14.020116]  [823d4c0e] local_pci_probe+0x4e/0xa0
[   14.020121]  [823d5d25] ? pci_match_device+0xe5/0x110
[   14.020126]  [823d5e49] __pci_device_probe+0xb9/0xf0
[   14.020131]  [823d5eba] pci_device_probe+0x3a/0x60
[   14.020137]  [824c4091] really_probe+0x91/0x380
[   14.020141]  [824c4507] driver_probe_device+0x47/0xa0
[   14.020146]  [824c460b] __driver_attach+0xab/0xb0
[   14.020150]  [824c4560] ? driver_probe_device+0xa0/0xa0
[   14.020155]  [824c241e] bus_for_each_dev+0x5e/0x90
[   14.020159]  [824c3c4e] driver_attach+0x1e/0x20
[   14.020163]  [824c37d4] bus_add_driver+0x124/0x260
[   14.020168]  [824c4f04] driver_register+0x64/0xf0
[   14.020172]  [823d4f8c] __pci_register_driver+0x4c/0x50
[   14.020184]  [c096a02b] rtl8821ae_module_init+0x2b/0x1000 
[rtl8821ae]
[   14.020192]  [c096a000] ? 0xc0969fff
[   14.020198]  [82002157] do_one_initcall+0xd7/0x200
[   14.020203]  [821c3684] ? kfree+0x134/0x170
[   14.020209]  [8277b6c1] do_init_module+0x30/0x181
[   14.020215]  [820f4a89] load_module+0x4b9/0x5f0
[   14.020219]  [820f20c0] ? show_initstate+0x50/0x50
[   14.020223]  [820f4d6e] SyS_finit_module+0xae/0xd0
[   14.020230]  [82793fad] system_call_fastpath+0x1a/0x1f
[   14.020233] ---[ end trace c3657046d4a5b2fe ]---

** Tags removed: needs-reverse-bisect

** Changed in: linux (Ubuntu)
   Status: Incomplete = Triaged

** Summary changed:

- [Gigabyte GB-BXi7-4470R] Kernel panic in rtl8821ae
+ Kernel panic in rtl8821ae with 3.13.0-30

-- 
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:
  Kernel panic in rtl8821ae with 3.13.0-30

Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  After updating the system to linux-image-3.13.0-30-generic (trusty-
  updates), the encounters a kernel panic during boot in the rtl8821ae
  module. This prevents the system from booting.

  This appears to be an issue relating to the mPCI WiFi+BT module
  (Realtek Semiconductor Co., Ltd. RTL8821AE 

Re: [Kernel-packages] [Bug 1341275] Re: Kernel panic in rtl8821ae with 3.13.0-30

2014-08-08 Thread TJ
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 on this in detail 
yesterday supporting another user with the identical 
failure on Asus X551MA.

As a kernel hacker I investigated the bug in detail and diagnosed the
cause.  My additions to this report are in light of my findings.

RIP [a042ffe5] rtl8821ae_rx_query_desc+0x1d5/0xa50 [rtl8821ae]

No changes were introduced in the rtl8821ae module between 3.13.0-24 and
3.13.0-30. The only changes were in mac80211, which rtl8821ae depends on
(along with cfg80211):

# check rtl8821ae
$ gitlog Ubuntu-3.13.0-24.47..Ubuntu-3.13.0-30.55 -- drivers/staging/rtl8821ae
# check mac80211
$ gitlog Ubuntu-3.13.0-24.47..Ubuntu-3.13.0-30.55 -- net/mac80211
7049ad3 Mon May 19 18:45:30 2014 +0100 Michael Braun mac80211: fix WPA with 
VLAN on AP side with ps-sta again
5d31275 Mon May 19 18:45:30 2014 +0100 Johannes Berg mac80211: fix suspend vs. 
authentication race
56f2ea4 Mon May 19 18:45:29 2014 +0100 Johannes Berg mac80211: fix potential 
use-after-free
22bf70f Tue Apr 15 15:27:46 2014 +0100 Johannes Berg mac80211: add length check 
in ieee80211_is_robust_mgmt_frame()
# check mac80211
$ gitlog Ubuntu-3.13.0-24.47..Ubuntu-3.13.0-30.55 -- net/wireless/
$

The faulting location is in function rx_query_desc() at offset 0x1d5.

$ objdump -d
/lib/modules/3.13.0-30-generic/kernel/drivers/staging/rtl8821ae/rtl8821ae.ko

00033e40 rtl8821ae_rx_query_desc:

Faulting instruction is at 0x33e40 + 0x1d5 = 0x34015

Now I examine the debug-symbols of the module with:

$ gdb -d drivers/staging/rtl8821ae -d
drivers/staging/rtl8821ae/rtl8821ae
/usr/lib/debug/modules/3.13.0-30-generic/kernel/drivers/staging/rtl8821ae/rtl8821ae.dbgsym.ko

(gdb) info line rtl8821ae_rx_query_desc
Line 539 of 
/build/buildd/linux-3.13.0/drivers/staging/rtl8821ae/rtl8821ae/trx.c starts 
at address 0x33e40 rtl8821ae_rx_query_desc
and ends at 0x33e65 rtl8821ae_rx_query_desc+37.
(gdb) x/i 0x34015
0x34015 rtl8821ae_rx_query_desc+469:   movzwl (%rdi),%esi
(gdb) disas rtl8821ae_rx_query_desc
...
0x00033ffe +446:   je 0x34641 rtl8821ae_rx_query_desc+2049
0x00034004 +452:   cmpl   $0x18,0x68(%rdx)
0x00034008 +456:   jbe0x34268 rtl8821ae_rx_query_desc+1064
0x0003400e +462:   mov0xd8(%rdx),%rdi   /* 
hdr-frame_control */
0x00034015 +469:   movzwl (%rdi),%esi   /* FAULT %rdi 
invalid */
0x00034018 +472:   mov%esi,%ecx
0x0003401a +474:   and$0xfc,%cx
0x0003401f +479:   cmp$0xa0,%cx
0x00034024 +484:   je 0x34068 rtl8821ae_rx_query_desc+552
...
(gdb) info line *0x34015
Line 2194 of /build/buildd/linux-3.13.0/include/linux/ieee80211.h starts at 
address 0x34015 rtl8821ae_rx_query_desc+469
and ends at 0x34018 rtl8821ae_rx_query_desc+472.

 include/linux/ieee80211.h -
/**
  * _ieee80211_is_robust_mgmt_frame - check if frame is a robust management 
frame
  * @hdr: the frame (buffer must include at least the first octet of payload)
  */
static inline bool _ieee80211_is_robust_mgmt_frame(struct ieee80211_hdr *hdr)
{
   if (ieee80211_is_disassoc(hdr-frame_control) ||  /* LINE 2194 */
   ieee80211_is_deauth(hdr-frame_control))
 return true;


/**
  * ieee80211_is_disassoc - check if IEEE80211_FTYPE_MGMT  
IEEE80211_STYPE_DISASSOC
  * @fc: frame control bytes in little-endian byteorder
  */
static inline int ieee80211_is_disassoc(__le16 fc)
{
   return (fc  cpu_to_le16(IEEE80211_FCTL_FTYPE | IEEE80211_FCTL_STYPE)) ==
  cpu_to_le16(IEEE80211_FTYPE_MGMT | IEEE80211_STYPE_DISASSOC);
}

- drivers/staging/rtl8821ae/rtl8821ae/trx.c::rtl8821ae_rx_query_desc() -
...
 if ((ieee80211_is_robust_mgmt_frame(hdr)) /* FAULT LOCATION */
   (ieee80211_has_protected(hdr-frame_control)))
   rx_status-flag = ~RX_FLAG_DECRYPTED;
 else
   rx_status-flag |= RX_FLAG_DECRYPTED;
   }
...
- 8- -

On investigation it appears that gdb may have an incorrect debug reference for 
the location of ieee80211_is_robust_mgmt_frame() since the
location it references is for the underscore-prefix function 
_ieee80211_is_robust_mgmt_frame(). This may be due to both functions being 
inline.

The changes introduced in commit:

22bf70f Tue Apr 15 15:27:46 2014 +0100 Johannes Berg mac80211: add
length check in ieee80211_is_robust_mgmt_frame()

include renaming the existing

ieee80211_is_robust_mgmt_frame(struct ieee80211_hdr *hdr)

to

_ieee80211_is_robust_mgmt_frame(struct ieee80211_hdr *hdr)

and replacing the original function with one taking an skb, not
ieee80211_hdr:

+ * ieee80211_is_robust_mgmt_frame - check if skb contains a robust mgmt frame
+ * @skb: the skb containing the frame

[Kernel-packages] [Bug 1354469] [NEW] [3.13.0-30.55] rtl8821ae Kernel PANIC due to calling incorrect function

2014-08-08 Thread TJ
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 diagnosed the cause to commit
22bf70f which modifies a function prototype called by the RTL8821ae
driver but does not update the driver to call the alternative function.

Corrective patch attached.

RIP [a042ffe5] rtl8821ae_rx_query_desc+0x1d5/0xa50 [rtl8821ae]

No changes were introduced in the rtl8821ae module between 3.13.0-24 and
3.13.0-30. The only changes were in mac80211, which rtl8821ae depends on
(along with cfg80211):

# check rtl8821ae
$ gitlog Ubuntu-3.13.0-24.47..Ubuntu-3.13.0-30.55 -- drivers/staging/rtl8821ae
# check mac80211
$ gitlog Ubuntu-3.13.0-24.47..Ubuntu-3.13.0-30.55 -- net/mac80211
7049ad3 Mon May 19 18:45:30 2014 +0100 Michael Braun mac80211: fix WPA with 
VLAN on AP side with ps-sta again
5d31275 Mon May 19 18:45:30 2014 +0100 Johannes Berg mac80211: fix suspend vs. 
authentication race
56f2ea4 Mon May 19 18:45:29 2014 +0100 Johannes Berg mac80211: fix potential 
use-after-free
22bf70f Tue Apr 15 15:27:46 2014 +0100 Johannes Berg mac80211: add length check 
in ieee80211_is_robust_mgmt_frame()
# check mac80211
$ gitlog Ubuntu-3.13.0-24.47..Ubuntu-3.13.0-30.55 -- net/wireless/
$

The faulting location is in function rx_query_desc() at offset 0x1d5.

$ objdump -d
/lib/modules/3.13.0-30-generic/kernel/drivers/staging/rtl8821ae/rtl8821ae.ko

00033e40 rtl8821ae_rx_query_desc:

Faulting instruction is at 0x33e40 + 0x1d5 = 0x34015

Now I examine the debug-symbols of the module with:

$ gdb -d drivers/staging/rtl8821ae -d
drivers/staging/rtl8821ae/rtl8821ae
/usr/lib/debug/modules/3.13.0-30-generic/kernel/drivers/staging/rtl8821ae/rtl8821ae.dbgsym.ko

(gdb) info line rtl8821ae_rx_query_desc
Line 539 of 
/build/buildd/linux-3.13.0/drivers/staging/rtl8821ae/rtl8821ae/trx.c starts 
at address 0x33e40 rtl8821ae_rx_query_desc
and ends at 0x33e65 rtl8821ae_rx_query_desc+37.
(gdb) x/i 0x34015
0x34015 rtl8821ae_rx_query_desc+469:   movzwl (%rdi),%esi
(gdb) disas rtl8821ae_rx_query_desc
...
0x00033ffe +446:   je 0x34641 rtl8821ae_rx_query_desc+2049
0x00034004 +452:   cmpl   $0x18,0x68(%rdx)
0x00034008 +456:   jbe0x34268 rtl8821ae_rx_query_desc+1064
0x0003400e +462:   mov0xd8(%rdx),%rdi   /* 
hdr-frame_control */
0x00034015 +469:   movzwl (%rdi),%esi   /* FAULT %rdi 
invalid */
0x00034018 +472:   mov%esi,%ecx
0x0003401a +474:   and$0xfc,%cx
0x0003401f +479:   cmp$0xa0,%cx
0x00034024 +484:   je 0x34068 rtl8821ae_rx_query_desc+552
...
(gdb) info line *0x34015
Line 2194 of /build/buildd/linux-3.13.0/include/linux/ieee80211.h starts at 
address 0x34015 rtl8821ae_rx_query_desc+469
and ends at 0x34018 rtl8821ae_rx_query_desc+472.

 include/linux/ieee80211.h -
/**
  * _ieee80211_is_robust_mgmt_frame - check if frame is a robust management 
frame
  * @hdr: the frame (buffer must include at least the first octet of payload)
  */
static inline bool _ieee80211_is_robust_mgmt_frame(struct ieee80211_hdr *hdr)
{
   if (ieee80211_is_disassoc(hdr-frame_control) ||  /* LINE 2194 */
   ieee80211_is_deauth(hdr-frame_control))
 return true;


/**
  * ieee80211_is_disassoc - check if IEEE80211_FTYPE_MGMT  
IEEE80211_STYPE_DISASSOC
  * @fc: frame control bytes in little-endian byteorder
  */
static inline int ieee80211_is_disassoc(__le16 fc)
{
   return (fc  cpu_to_le16(IEEE80211_FCTL_FTYPE | IEEE80211_FCTL_STYPE)) ==
  cpu_to_le16(IEEE80211_FTYPE_MGMT | IEEE80211_STYPE_DISASSOC);
}

- drivers/staging/rtl8821ae/rtl8821ae/trx.c::rtl8821ae_rx_query_desc() -
...
 if ((ieee80211_is_robust_mgmt_frame(hdr)) /* FAULT LOCATION */
   (ieee80211_has_protected(hdr-frame_control)))
   rx_status-flag = ~RX_FLAG_DECRYPTED;
 else
   rx_status-flag |= RX_FLAG_DECRYPTED;
   }
...
- 8- -

On investigation it appears that gdb may have an incorrect debug reference for 
the location of ieee80211_is_robust_mgmt_frame() since the
location it references is for the underscore-prefix function 
_ieee80211_is_robust_mgmt_frame(). This may be due to both functions being 
inline.

The changes introduced in commit:

22bf70f Tue Apr 15 15:27:46 2014 +0100 Johannes Berg mac80211: add
length check in ieee80211_is_robust_mgmt_frame()

include renaming the existing

ieee80211_is_robust_mgmt_frame(struct ieee80211_hdr *hdr)

to

_ieee80211_is_robust_mgmt_frame(struct ieee80211_hdr *hdr)

and replacing the original function with one taking an skb, not
ieee80211_hdr:

+ * ieee80211_is_robust_mgmt_frame - check if skb contains a robust mgmt frame
+ * @skb: the skb containing the frame, length will be checked
+ */
+static 

[Kernel-packages] [Bug 1341275] Re: 10ec:8821 [Gigabyte GB-BXi7-4470R] Kernel panic in rtl8821ae

2014-08-08 Thread TJ
*** 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
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1341275

Title:
  10ec:8821 [Gigabyte GB-BXi7-4470R] Kernel panic in rtl8821ae

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  After updating the system to linux-image-3.13.0-30-generic (trusty-
  updates), the encounters a kernel panic during boot in the rtl8821ae
  module. This prevents the system from booting.

  This appears to be an issue relating to the mPCI WiFi+BT module
  (Realtek Semiconductor Co., Ltd. RTL8821AE 802.11ac PCIe Wireless
  Network Adapter) included with the system.

  A workaround is to boot using the older linux-image-3.13.0-24-generic
  (trusty).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-30-generic 3.13.0-30.55
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dcoles 2324 F pulseaudio
   /dev/snd/pcmC1D0p:   dcoles 2324 F...m pulseaudio
   /dev/snd/controlC0:  dcoles 2324 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Jul 13 20:35:13 2014
  HibernationDevice: RESUME=UUID=489d6aeb-add6-485d-8056-de392a8591b7
  InstallationDate: Installed on 2014-03-14 (120 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140310)
  MachineType: GIGABYTE M4HM87P-00
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127.4
  SourcePackage: linux
  StagingDrivers: rtl8821ae
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M4HM87P-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd02/06/2014:svnGIGABYTE:pnM4HM87P-00:pvr1.x:rvnGIGABYTE:rnM4HM87P-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: M4HM87P-00
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1341275/+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 1354469] Re: [3.13.0-30.55] rtl8821ae Kernel PANIC due to calling incorrect function

2014-08-08 Thread TJ
** 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 in detail and diagnosed the cause to commit
+  I investigated the bug in detail and diagnosed the cause to commit
  22bf70f which modifies a function prototype called by the RTL8821ae
  driver but does not update the driver to call the alternative function.
  
  Corrective patch attached.
  
  RIP [a042ffe5] rtl8821ae_rx_query_desc+0x1d5/0xa50 [rtl8821ae]
  
  No changes were introduced in the rtl8821ae module between 3.13.0-24 and
  3.13.0-30. The only changes were in mac80211, which rtl8821ae depends on
  (along with cfg80211):
  
  # check rtl8821ae
  $ gitlog Ubuntu-3.13.0-24.47..Ubuntu-3.13.0-30.55 -- drivers/staging/rtl8821ae
  # check mac80211
  $ gitlog Ubuntu-3.13.0-24.47..Ubuntu-3.13.0-30.55 -- net/mac80211
  7049ad3 Mon May 19 18:45:30 2014 +0100 Michael Braun mac80211: fix WPA with 
VLAN on AP side with ps-sta again
  5d31275 Mon May 19 18:45:30 2014 +0100 Johannes Berg mac80211: fix suspend 
vs. authentication race
  56f2ea4 Mon May 19 18:45:29 2014 +0100 Johannes Berg mac80211: fix potential 
use-after-free
  22bf70f Tue Apr 15 15:27:46 2014 +0100 Johannes Berg mac80211: add length 
check in ieee80211_is_robust_mgmt_frame()
- # check mac80211
+ # check cfg80211
  $ gitlog Ubuntu-3.13.0-24.47..Ubuntu-3.13.0-30.55 -- net/wireless/
  $
  
  The faulting location is in function rx_query_desc() at offset 0x1d5.
  
  $ objdump -d
  /lib/modules/3.13.0-30-generic/kernel/drivers/staging/rtl8821ae/rtl8821ae.ko
  
  00033e40 rtl8821ae_rx_query_desc:
  
  Faulting instruction is at 0x33e40 + 0x1d5 = 0x34015
  
  Now I examine the debug-symbols of the module with:
  
  $ gdb -d drivers/staging/rtl8821ae -d
  drivers/staging/rtl8821ae/rtl8821ae
  
/usr/lib/debug/modules/3.13.0-30-generic/kernel/drivers/staging/rtl8821ae/rtl8821ae.dbgsym.ko
  
  (gdb) info line rtl8821ae_rx_query_desc
  Line 539 of 
/build/buildd/linux-3.13.0/drivers/staging/rtl8821ae/rtl8821ae/trx.c starts 
at address 0x33e40 rtl8821ae_rx_query_desc
- and ends at 0x33e65 rtl8821ae_rx_query_desc+37.
+ and ends at 0x33e65 rtl8821ae_rx_query_desc+37.
  (gdb) x/i 0x34015
- 0x34015 rtl8821ae_rx_query_desc+469:   movzwl (%rdi),%esi
+ 0x34015 rtl8821ae_rx_query_desc+469:   movzwl (%rdi),%esi
  (gdb) disas rtl8821ae_rx_query_desc
  ...
- 0x00033ffe +446:   je 0x34641 rtl8821ae_rx_query_desc+2049
- 0x00034004 +452:   cmpl   $0x18,0x68(%rdx)
- 0x00034008 +456:   jbe0x34268 rtl8821ae_rx_query_desc+1064
- 0x0003400e +462:   mov0xd8(%rdx),%rdi   /* 
hdr-frame_control */
- 0x00034015 +469:   movzwl (%rdi),%esi   /* FAULT %rdi 
invalid */
- 0x00034018 +472:   mov%esi,%ecx
- 0x0003401a +474:   and$0xfc,%cx
- 0x0003401f +479:   cmp$0xa0,%cx
- 0x00034024 +484:   je 0x34068 rtl8821ae_rx_query_desc+552
+ 0x00033ffe +446:   je 0x34641 rtl8821ae_rx_query_desc+2049
+ 0x00034004 +452:   cmpl   $0x18,0x68(%rdx)
+ 0x00034008 +456:   jbe0x34268 rtl8821ae_rx_query_desc+1064
+ 0x0003400e +462:   mov0xd8(%rdx),%rdi   /* 
hdr-frame_control */
+ 0x00034015 +469:   movzwl (%rdi),%esi   /* FAULT %rdi 
invalid */
+ 0x00034018 +472:   mov%esi,%ecx
+ 0x0003401a +474:   and$0xfc,%cx
+ 0x0003401f +479:   cmp$0xa0,%cx
+ 0x00034024 +484:   je 0x34068 rtl8821ae_rx_query_desc+552
  ...
  (gdb) info line *0x34015
  Line 2194 of /build/buildd/linux-3.13.0/include/linux/ieee80211.h starts at 
address 0x34015 rtl8821ae_rx_query_desc+469
- and ends at 0x34018 rtl8821ae_rx_query_desc+472.
+ and ends at 0x34018 rtl8821ae_rx_query_desc+472.
  
   include/linux/ieee80211.h -
  /**
-   * _ieee80211_is_robust_mgmt_frame - check if frame is a robust management 
frame
-   * @hdr: the frame (buffer must include at least the first octet of payload)
-   */
+   * _ieee80211_is_robust_mgmt_frame - check if frame is a robust management 
frame
+   * @hdr: the frame (buffer must include at least the first octet of payload)
+   */
  static inline bool _ieee80211_is_robust_mgmt_frame(struct ieee80211_hdr *hdr)
  {
-if (ieee80211_is_disassoc(hdr-frame_control) ||  /* LINE 2194 */
-ieee80211_is_deauth(hdr-frame_control))
-  return true;
- 
+    if (ieee80211_is_disassoc(hdr-frame_control) ||  /* LINE 2194 */
+    ieee80211_is_deauth(hdr-frame_control))
+  return true;
  
  /**
-   * ieee80211_is_disassoc - check if IEEE80211_FTYPE_MGMT  
IEEE80211_STYPE_DISASSOC
-   * @fc: frame control bytes in little-endian byteorder
-   */
+   * 

[Kernel-packages] [Bug 22096] Re: toshiba_acpi does not work on Toshiba Tecra M2 laptop

2014-08-10 Thread TJ
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 is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/22096

Title:
  toshiba_acpi does not work on Toshiba Tecra M2 laptop

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux-source-2.6.20” package in Ubuntu:
  Won't Fix
Status in “linux” source package in Intrepid:
  Fix Released
Status in “linux-source-2.6.20” source package in Intrepid:
  Invalid

Bug description:
  This is regarding a Canonical-supplied Toshiba Tecra M2.

  Fn+F9 is used to enable/disable the touchpad. However, nothing happens when I
  try to turn it on. The Tecra M2 has dual pointing devices: Alps touchpad and
  Accupoint.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/22096/+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 22575] Re: ISAPNP grabbing I/O region reserved for PCI device on 2.6.12 (regression from 2.6.10)

2014-08-10 Thread TJ
As there has been no new activity by the original reporter on this
report in several years, and as the reported release is no longer
supported, I am closing this bug as Won'tFix for the linux (Ubuntu)
task.

If you are experiencing this or a similar issue with a supported Ubuntu
version please 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 is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/22575

Title:
  ISAPNP grabbing I/O region reserved for PCI device on 2.6.12
  (regression from 2.6.10)

Status in “linux” package in Ubuntu:
  Won't Fix
Status in “linux-source-2.6.15” package in Ubuntu:
  Won't Fix

Bug description:
  The Kernel 2.6.12.x don't work with RLT-8139/8139C/8139C+ network
  interface

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/22575/+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 1341275] Re: 10ec:8821 [Gigabyte GB-BXi7-4470R] Kernel panic in rtl8821ae

2014-08-12 Thread TJ
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:
  10ec:8821 [Gigabyte GB-BXi7-4470R] Kernel panic in rtl8821ae

Status in “linux” package in Ubuntu:
  Fix Committed

Bug description:
  After updating the system to linux-image-3.13.0-30-generic (trusty-
  updates), the encounters a kernel panic during boot in the rtl8821ae
  module. This prevents the system from booting.

  This appears to be an issue relating to the mPCI WiFi+BT module
  (Realtek Semiconductor Co., Ltd. RTL8821AE 802.11ac PCIe Wireless
  Network Adapter) included with the system.

  A workaround is to boot using the older linux-image-3.13.0-24-generic
  (trusty).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-30-generic 3.13.0-30.55
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dcoles 2324 F pulseaudio
   /dev/snd/pcmC1D0p:   dcoles 2324 F...m pulseaudio
   /dev/snd/controlC0:  dcoles 2324 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Jul 13 20:35:13 2014
  HibernationDevice: RESUME=UUID=489d6aeb-add6-485d-8056-de392a8591b7
  InstallationDate: Installed on 2014-03-14 (120 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140310)
  MachineType: GIGABYTE M4HM87P-00
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127.4
  SourcePackage: linux
  StagingDrivers: rtl8821ae
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M4HM87P-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd02/06/2014:svnGIGABYTE:pnM4HM87P-00:pvr1.x:rvnGIGABYTE:rnM4HM87P-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: M4HM87P-00
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1341275/+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 1356526] Re: [HP Elitebook 755] wifi and brightness on 14.04 LTS (with solution)

2014-08-13 Thread TJ
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: broadcom-sta (Ubuntu)
   Status: New = Invalid

** Changed in: linux (Ubuntu)
   Status: New = Triaged

** Changed in: linux (Ubuntu)
   Importance: Undecided = Low

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) = TJ (tj)

** Changed in: linux (Ubuntu)
   Status: Triaged = 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.net/bugs/1356526

Title:
  [HP Elitebook 755] wifi and brightness on 14.04 LTS (with solution)

Status in “broadcom-sta” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  In Progress

Bug description:
  For the HP Elitebook 755 (SKU J0X38AW#ABD with BIOS Version M84
  Ver. 01.01) I found the following kernel parameters were needed to
  make the wireless controller and brightness control work properly:

  acpi_osi=!Windows 2013
  acpi_osi=!Windows 2012
  intremap=off

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/1356526/+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 1358491] Re: [Trusty] fails to boot with kernels later than v3.11: systemd-udevd[133]: conflicting device node

2014-08-18 Thread TJ
** 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.
https://bugs.launchpad.net/bugs/1358491

Title:
  [Trusty] fails to boot with kernels later than v3.11: systemd-
  udevd[133]: conflicting device node

Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  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 the upgrade the server
  fails to boot using kernel version 3.13.0-24-generic during early udev
  whilst still in the initrd. Errors of the form:

  [6.989549] systemd-udevd[137]: inotify_add_watch(7, /dev/sdi2, 10) 
failed: No such file or directory
  ...
  [7.092733] systemd-udevd[133]: conflicting device node 
'/dev/mapper/pdc_ecjaiecgch1' found, link to '/dev/dm-2' will not be created

  are reported for some devices, usually the Promise 'fake' RAID
  devices.

  The system hangs at that point without ever dropping to a busybox
  shell.

  Starting with an earlier Saucy kernel version 3.11.0-12-generic allows
  the server to start successfully.

  After some research it appears that maybe this is due to an
  incompatibility between systemd-udevd and device-mapper and/or dmraid-
  activate. I read in a similar Fedora bug report a comment by Kay
  Seivers:

  https://bugzilla.redhat.com/show_bug.cgi?id=867593#c11

  Device-mapper seems to mknod() things in /dev, which just can not work
  correctly today.

  There is nothing udev can fix here, it will never touch any device
  node, which should not exist in the first place, that is in the way.

  I've tried breaking initrd, but unless it is done at 'top' udevd
  starts and the system hits this problem.

  Serial console logs of the failed and successful boot attempts are
  attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358491/+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 1358491] [NEW] [Trusty] fails to boot with kernels later than v3.11: systemd-udevd[133]: conflicting device node

2014-08-18 Thread TJ
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 the upgrade the server fails
to boot using kernel version 3.13.0-24-generic during early udev whilst
still in the initrd. Errors of the form:

[6.989549] systemd-udevd[137]: inotify_add_watch(7, /dev/sdi2, 10) failed: 
No such file or directory
...
[7.092733] systemd-udevd[133]: conflicting device node 
'/dev/mapper/pdc_ecjaiecgch1' found, link to '/dev/dm-2' will not be created

are reported for some devices, usually the Promise 'fake' RAID devices.

The system hangs at that point without ever dropping to a busybox shell.

Starting with an earlier Saucy kernel version 3.11.0-12-generic allows
the server to start successfully.

After some research it appears that maybe this is due to an
incompatibility between systemd-udevd and device-mapper and/or dmraid-
activate. I read in a similar Fedora bug report a comment by Kay
Seivers:

https://bugzilla.redhat.com/show_bug.cgi?id=867593#c11

Device-mapper seems to mknod() things in /dev, which just can not work
correctly today.

There is nothing udev can fix here, it will never touch any device
node, which should not exist in the first place, that is in the way.

I've tried breaking initrd, but unless it is done at 'top' udevd starts
and the system hits this problem.

Serial console logs of the failed and successful boot attempts are
attached

** Affects: linux (Ubuntu)
 Importance: High
 Status: Triaged

** Attachment added: Failed boot with kernel 3.13.0-24-generic
   
https://bugs.launchpad.net/bugs/1358491/+attachment/418/+files/caddy-bad.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/1358491

Title:
  [Trusty] fails to boot with kernels later than v3.11: systemd-
  udevd[133]: conflicting device node

Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  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 the upgrade the server
  fails to boot using kernel version 3.13.0-24-generic during early udev
  whilst still in the initrd. Errors of the form:

  [6.989549] systemd-udevd[137]: inotify_add_watch(7, /dev/sdi2, 10) 
failed: No such file or directory
  ...
  [7.092733] systemd-udevd[133]: conflicting device node 
'/dev/mapper/pdc_ecjaiecgch1' found, link to '/dev/dm-2' will not be created

  are reported for some devices, usually the Promise 'fake' RAID
  devices.

  The system hangs at that point without ever dropping to a busybox
  shell.

  Starting with an earlier Saucy kernel version 3.11.0-12-generic allows
  the server to start successfully.

  After some research it appears that maybe this is due to an
  incompatibility between systemd-udevd and device-mapper and/or dmraid-
  activate. I read in a similar Fedora bug report a comment by Kay
  Seivers:

  https://bugzilla.redhat.com/show_bug.cgi?id=867593#c11

  Device-mapper seems to mknod() things in /dev, which just can not work
  correctly today.

  There is nothing udev can fix here, it will never touch any device
  node, which should not exist in the first place, that is in the way.

  I've tried breaking initrd, but unless it is done at 'top' udevd
  starts and the system hits this problem.

  Serial console logs of the failed and successful boot attempts are
  attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358491/+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 1358491] Re: [Trusty] fails to boot with kernels later than v3.11: systemd-udevd[133]: conflicting device node

2014-08-18 Thread TJ
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

Title:
  [Trusty] fails to boot with kernels later than v3.11: systemd-
  udevd[133]: conflicting device node

Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  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 the upgrade the server
  fails to boot using kernel version 3.13.0-24-generic during early udev
  whilst still in the initrd. Errors of the form:

  [6.989549] systemd-udevd[137]: inotify_add_watch(7, /dev/sdi2, 10) 
failed: No such file or directory
  ...
  [7.092733] systemd-udevd[133]: conflicting device node 
'/dev/mapper/pdc_ecjaiecgch1' found, link to '/dev/dm-2' will not be created

  are reported for some devices, usually the Promise 'fake' RAID
  devices.

  The system hangs at that point without ever dropping to a busybox
  shell.

  Starting with an earlier Saucy kernel version 3.11.0-12-generic allows
  the server to start successfully.

  After some research it appears that maybe this is due to an
  incompatibility between systemd-udevd and device-mapper and/or dmraid-
  activate. I read in a similar Fedora bug report a comment by Kay
  Seivers:

  https://bugzilla.redhat.com/show_bug.cgi?id=867593#c11

  Device-mapper seems to mknod() things in /dev, which just can not work
  correctly today.

  There is nothing udev can fix here, it will never touch any device
  node, which should not exist in the first place, that is in the way.

  I've tried breaking initrd, but unless it is done at 'top' udevd
  starts and the system hits this problem.

  Serial console logs of the failed and successful boot attempts are
  attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358491/+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 1358491] Re: [Trusty] fails to boot with kernels later than v3.11: systemd-udevd[133]: conflicting device node

2014-08-18 Thread TJ
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)

** Changed in: linux (Ubuntu)
   Status: Triaged = 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.net/bugs/1358491

Title:
  [Trusty] fails to boot with kernels later than v3.11: systemd-
  udevd[133]: conflicting device node

Status in “linux” package in Ubuntu:
  In Progress

Bug description:
  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 the upgrade the server
  fails to boot using kernel version 3.13.0-24-generic during early udev
  whilst still in the initrd. Errors of the form:

  [6.989549] systemd-udevd[137]: inotify_add_watch(7, /dev/sdi2, 10) 
failed: No such file or directory
  ...
  [7.092733] systemd-udevd[133]: conflicting device node 
'/dev/mapper/pdc_ecjaiecgch1' found, link to '/dev/dm-2' will not be created

  are reported for some devices, usually the Promise 'fake' RAID
  devices.

  The system hangs at that point without ever dropping to a busybox
  shell.

  Starting with an earlier Saucy kernel version 3.11.0-12-generic allows
  the server to start successfully.

  After some research it appears that maybe this is due to an
  incompatibility between systemd-udevd and device-mapper and/or dmraid-
  activate. I read in a similar Fedora bug report a comment by Kay
  Seivers:

  https://bugzilla.redhat.com/show_bug.cgi?id=867593#c11

  Device-mapper seems to mknod() things in /dev, which just can not work
  correctly today.

  There is nothing udev can fix here, it will never touch any device
  node, which should not exist in the first place, that is in the way.

  I've tried breaking initrd, but unless it is done at 'top' udevd
  starts and the system hits this problem.

  Serial console logs of the failed and successful boot attempts are
  attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358491/+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 1358491] Re: [Trusty] fails to boot with kernels later than v3.11: systemd-udevd[133]: conflicting device node

2014-08-19 Thread 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 created since the VG's
container partition /dev/mapper/pdc_ecjaiecgch4 does not get created:

(initramfs) cat /proc/version
Linux version 3.13.0-24-generic (buildd@panlong) (gcc version 4.8.2 (Ubuntu 
4.8.2-19ubuntu1) ) #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014

(initramfs) cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/VG_CADDY-rootfs ro debug 
bootdegraded=true libata.force=noncq console=tty0 console=ttyS0,115200n8 
netconsole=@10.254.1.3/eth0,@10.254.1.51/ --debug --verbose break=top 
nomdmonddf nomdmonisw

(initramfs) dmesg | grep -C2 sdb
[   97.610562] scsi 11:0:1:0: Direct-Access ATA  ST380011A3.06 
PQ: 0 ANSI: 5
[   97.610762] sd 11:0:1:0: [sdb] 156299375 512-byte logical blocks: (80.0 
GB/74.5 GiB)
[   97.610786] sd 11:0:1:0: Attached scsi generic sg2 type 0
[   97.610893] sd 11:0:1:0: [sdb] Write Protect is off
[   97.610895] sd 11:0:1:0: [sdb] Mode Sense: 00 3a 00 00
[   97.610942] sd 11:0:1:0: [sdb] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[   97.675153]  sdb: sdb1 sdb2 sdb3 sdb4
[   97.675669] sd 11:0:1:0: [sdb] Attached SCSI disk
--
27[  100.196769] systemd-udevd[176]: inotify_add_watch(7, /dev/sdb3, 10) 
failed: No such file or directory
27[  100.196845] systemd-udevd[168]: inotify_add_watch(7, /dev/sdb1, 10) 
failed: No such file or directory
27[  100.197798] systemd-udevd[177]: inotify_add_watch(7, /dev/sdb4, 10) 
failed: No such file or directory
27[  100.198351] systemd-udevd[175]: inotify_add_watch(7, /dev/sdb2, 10) 
failed: No such file or directory
27[  100.198375] systemd-udevd[179]: inotify_add_watch(7, /dev/sdc2, 10) 
failed: No such file or directory
27[  100.198911] systemd-udevd[180]: inotify_add_watch(7, /dev/sdc3, 10) 
failed: No such file or directory

(initramfs) dmesg | grep 'too small'
[  100.346794] device-mapper: table: 252:13: dm-0 too small for target: 
start=13574144, len=142725198, dev_size=156298401

# fake RAID raw device
(initramfs) kpartx -l /dev/sdb
sdb1 : 0 2014 /dev/sdb 34
sdb2 : 0 1024000 /dev/sdb 2048
sdb3 : 0 12023809 /dev/sdb 1288192
sdb4 : 0 142725198 /dev/sdb 13574144

# same device through the device-mapper viewpoint
(initramfs) kpartx -l /dev/mapper/pdc_ecjaiecgch
Alternate GPT is invalid, using primary GPT.
pdc_ecjaiecgch1 : 0 2014 /dev/mapper/pdc_ecjaiecgch 34
pdc_ecjaiecgch2 : 0 1024000 /dev/mapper/pdc_ecjaiecgch 2048
pdc_ecjaiecgch3 : 0 12023809 /dev/mapper/pdc_ecjaiecgch 1288192
pdc_ecjaiecgch4 : 0 142725198 /dev/mapper/pdc_ecjaiecgch 13574144


I've moved the VG to another disk on a plain PATA controller for now. I'll 
investigate more when I have time.

-- 
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

Title:
  [Trusty] fails to boot with kernels later than v3.11: systemd-
  udevd[133]: conflicting device node

Status in “linux” package in Ubuntu:
  In Progress

Bug description:
  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 the upgrade the server
  fails to boot using kernel version 3.13.0-24-generic during early udev
  whilst still in the initrd. Errors of the form:

  [6.989549] systemd-udevd[137]: inotify_add_watch(7, /dev/sdi2, 10) 
failed: No such file or directory
  ...
  [7.092733] systemd-udevd[133]: conflicting device node 
'/dev/mapper/pdc_ecjaiecgch1' found, link to '/dev/dm-2' will not be created

  are reported for some devices, usually the Promise 'fake' RAID
  devices.

  The system hangs at that point without ever dropping to a busybox
  shell.

  Starting with an earlier Saucy kernel version 3.11.0-12-generic allows
  the server to start successfully.

  After some research it appears that maybe this is due to an
  incompatibility between systemd-udevd and device-mapper and/or dmraid-
  activate. I read in a similar Fedora bug report a comment by Kay
  Seivers:

  https://bugzilla.redhat.com/show_bug.cgi?id=867593#c11

  Device-mapper seems to mknod() things in /dev, which just can not work
  correctly today.

  There is nothing udev can fix here, it will never touch any device
  node, which should not exist in the first place, that is in the way.

  I've tried breaking initrd, but unless it is done at 'top' udevd
  starts and the system hits this problem.

  Serial console logs of the failed and successful boot attempts are
  attached

To manage notifications about this bug go to:

[Kernel-packages] [Bug 23251] Re: Synaptics tap-and-drag not functioning by default

2014-08-19 Thread TJ
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 Intellimouse Explorer
protocol (PSMOUSE_IMEX). Without this the device detection identifies it
as a standard Intellimouse (PSMOUSE_IMPS) during auto-detect.

Device detection works through a list of protocols, starting with the
most basic (safest) and working through to more sophisticated protocols.
The order of detecting these protocols is fixed in the driver since
probing for an incorrect protocol can cause the device to lock-up if it
receives commands it does not understand.

drivers/input/mouse/psmouse-base.c::psmouse_extensions() is responsible
for detecting the connected device by calling a series of device-
specific detect() functions. The order of detection is:

Lifebook (lifebook)
Kensington ThinkingMouse (thinkps)
Synaptics TouchPad (synaptics)
Cypress TrackPad (cypress)
ALPS TouchPad (alps)
OLPC HGPK touchpad (hgpk)
Elantech touchpad (elantech)
Genius mouse (genius)
Logitech PS2++ (logitech)
Trackpoint (trackpoint)
TouchKit PS/2 (touchkit)
Finger Sensing Pad (fsp)
Intellimouse Explorer PS/2 (imex)
default: Intellimouse PS/2 (imps)


** Changed in: linux (Ubuntu)
   Status: Incomplete = Won't Fix

-- 
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/23251

Title:
  Synaptics tap-and-drag not functioning by default

Status in “linux” package in Ubuntu:
  Won't Fix

Bug description:
  My laptop is a Fujitsu S2010 with a Synaptic Alps touchpad.

  After upgrading to Breezy the tap-to-drag feature doesn't seem to work 
anymore.
  I read the xorg-driver-synaptics README and added the options to my xorg.conf
  but they didn't seem to produce any change.

  Any other functionality, like side scroll or corner tap was not enabled by
  default in Hoary and it is still not present.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/23251/+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 1292118] Re: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module failed to build [error: incompatible types when returning type ‘kuid_t’ but ‘RTUID’ was expected]

2014-08-29 Thread TJ
** 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 of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1292118

Title:
  virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module
  failed to build [error: incompatible types when returning type
  ‘kuid_t’ but ‘RTUID’ was expected]

Status in “linux” package in Ubuntu:
  Triaged
Status in “virtualbox” package in Ubuntu:
  Triaged

Bug description:
  The virtualbox module does not build with the newer HWE kernels found
  in Ubuntu Precise/12.04

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.5
  ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
  Uname: Linux 3.13.0-14-generic i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  DKMSKernelVersion: 3.13.0-17-generic
  Date: Thu Mar 13 12:40:09 2014
  DuplicateSignature: 
dkms:virtualbox-dkms:4.1.12-dfsg-2ubuntu0.5:/var/lib/dkms/virtualbox/4.1.12/build/vboxdrv/linux/SUPDrv-linux.c:226:5:
 error: incompatible types when returning type ‘kuid_t’ but ‘RTUID’ was expected
  InstallationDate: Installed on 2012-04-29 (682 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 
(20120423)
  PackageArchitecture: all
  PackageVersion: 4.1.12-dfsg-2ubuntu0.5
  SourcePackage: virtualbox
  Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.5: virtualbox kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  VirtualBox.ModInfo:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1292118/+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 1356526] Re: [HP Elitebook 755] wifi not working in 14.04 LTS

2014-08-31 Thread TJ
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 are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1356526

Title:
  [HP Elitebook 755] wifi not working in 14.04 LTS

Status in “linux” package in Ubuntu:
  In Progress

Bug description:
  For the HP Elitebook 755 (SKU J0X38AW#ABD with BIOS Version M84
  Ver. 01.01) I found the following kernel parameters were needed to
  make the wireless controller work properly:

  acpi_osi=!Windows 2013
  acpi_osi=!Windows 2012
  intremap=off

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1356526/+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 1292118] Re: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module failed to build [error: incompatible types when returning type ‘kuid_t’ but ‘RTUID’ was expected]

2014-08-31 Thread TJ
** 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/bugs/1292118

Title:
  virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module
  failed to build [error: incompatible types when returning type
  ‘kuid_t’ but ‘RTUID’ was expected]

Status in “linux” package in Ubuntu:
  Triaged
Status in “virtualbox” package in Ubuntu:
  In Progress

Bug description:
  The virtualbox module does not build with the newer HWE kernels found
  in Ubuntu Precise/12.04

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.5
  ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
  Uname: Linux 3.13.0-14-generic i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  DKMSKernelVersion: 3.13.0-17-generic
  Date: Thu Mar 13 12:40:09 2014
  DuplicateSignature: 
dkms:virtualbox-dkms:4.1.12-dfsg-2ubuntu0.5:/var/lib/dkms/virtualbox/4.1.12/build/vboxdrv/linux/SUPDrv-linux.c:226:5:
 error: incompatible types when returning type ‘kuid_t’ but ‘RTUID’ was expected
  InstallationDate: Installed on 2012-04-29 (682 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 
(20120423)
  PackageArchitecture: all
  PackageVersion: 4.1.12-dfsg-2ubuntu0.5
  SourcePackage: virtualbox
  Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.5: virtualbox kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  VirtualBox.ModInfo:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1292118/+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 1368301] [NEW] 12.04 missing rtlwifi/rtl8188efw.bin when HWE is installed

2014-09-11 Thread TJ
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
firmware:   rtlwifi/rtl8188efw.bin

12.04:

/lib/firmware/rtlwifi/rtl8192cfw.bin
/lib/firmware/rtlwifi/rtl8192cfwU.bin
/lib/firmware/rtlwifi/rtl8192cfwU_B.bin
/lib/firmware/rtlwifi/rtl8192cufw.bin
/lib/firmware/rtlwifi/rtl8192defw.bin
/lib/firmware/rtlwifi/rtl8192sefw.bin
/lib/firmware/rtlwifi/rtl8712u.bin
/lib/firmware/rtlwifi/rtl8723fw.bin
/lib/firmware/rtlwifi/rtl8723fw_B.bin

13.04:

/lib/firmware/rtlwifi/rtl8188efw.bin
/lib/firmware/rtlwifi/rtl8192cfw.bin
/lib/firmware/rtlwifi/rtl8192cfwU.bin
/lib/firmware/rtlwifi/rtl8192cfwU_B.bin
/lib/firmware/rtlwifi/rtl8192cufw.bin
/lib/firmware/rtlwifi/rtl8192defw.bin
/lib/firmware/rtlwifi/rtl8192sefw.bin
/lib/firmware/rtlwifi/rtl8712u.bin
/lib/firmware/rtlwifi/rtl8723fw.bin
/lib/firmware/rtlwifi/rtl8723fw_B.bin

** Affects: linux-firmware (Ubuntu)
 Importance: High
 Status: Triaged

** Changed in: linux-firmware (Ubuntu)
   Status: New = Triaged

** Changed in: linux-firmware (Ubuntu)
   Importance: Undecided = High

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1368301

Title:
  12.04 missing rtlwifi/rtl8188efw.bin when HWE is installed

Status in “linux-firmware” package in Ubuntu:
  Triaged

Bug description:
  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
  firmware:   rtlwifi/rtl8188efw.bin

  12.04:

  /lib/firmware/rtlwifi/rtl8192cfw.bin
  /lib/firmware/rtlwifi/rtl8192cfwU.bin
  /lib/firmware/rtlwifi/rtl8192cfwU_B.bin
  /lib/firmware/rtlwifi/rtl8192cufw.bin
  /lib/firmware/rtlwifi/rtl8192defw.bin
  /lib/firmware/rtlwifi/rtl8192sefw.bin
  /lib/firmware/rtlwifi/rtl8712u.bin
  /lib/firmware/rtlwifi/rtl8723fw.bin
  /lib/firmware/rtlwifi/rtl8723fw_B.bin

  13.04:

  /lib/firmware/rtlwifi/rtl8188efw.bin
  /lib/firmware/rtlwifi/rtl8192cfw.bin
  /lib/firmware/rtlwifi/rtl8192cfwU.bin
  /lib/firmware/rtlwifi/rtl8192cfwU_B.bin
  /lib/firmware/rtlwifi/rtl8192cufw.bin
  /lib/firmware/rtlwifi/rtl8192defw.bin
  /lib/firmware/rtlwifi/rtl8192sefw.bin
  /lib/firmware/rtlwifi/rtl8712u.bin
  /lib/firmware/rtlwifi/rtl8723fw.bin
  /lib/firmware/rtlwifi/rtl8723fw_B.bin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1368301/+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 1356526] Re: [HP Elitebook 755] wifi not working in 14.04 LTS

2014-12-12 Thread TJ
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

Title:
  [HP Elitebook 755] wifi not working in 14.04 LTS

Status in linux package in Ubuntu:
  In Progress

Bug description:
  For the HP Elitebook 755 (SKU J0X38AW#ABD with BIOS Version M84
  Ver. 01.01) I found the following kernel parameters were needed to
  make the wireless controller work properly:

  acpi_osi=!Windows 2013
  acpi_osi=!Windows 2012
  intremap=off

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1356526/+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 1358491] Re: [Trusty] fails to boot with kernels later than v3.11: systemd-udevd[133]: conflicting device node

2015-02-05 Thread TJ
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 you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1358491

Title:
  [Trusty] fails to boot with kernels later than v3.11: systemd-
  udevd[133]: conflicting device node

Status in linux package in Ubuntu:
  In Progress

Bug description:
  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 the upgrade the server
  fails to boot using kernel version 3.13.0-24-generic during early udev
  whilst still in the initrd. Errors of the form:

  [6.989549] systemd-udevd[137]: inotify_add_watch(7, /dev/sdi2, 10) 
failed: No such file or directory
  ...
  [7.092733] systemd-udevd[133]: conflicting device node 
'/dev/mapper/pdc_ecjaiecgch1' found, link to '/dev/dm-2' will not be created

  are reported for some devices, usually the Promise 'fake' RAID
  devices.

  The system hangs at that point without ever dropping to a busybox
  shell.

  Starting with an earlier Saucy kernel version 3.11.0-12-generic allows
  the server to start successfully.

  After some research it appears that maybe this is due to an
  incompatibility between systemd-udevd and device-mapper and/or dmraid-
  activate. I read in a similar Fedora bug report a comment by Kay
  Seivers:

  https://bugzilla.redhat.com/show_bug.cgi?id=867593#c11

  Device-mapper seems to mknod() things in /dev, which just can not work
  correctly today.

  There is nothing udev can fix here, it will never touch any device
  node, which should not exist in the first place, that is in the way.

  I've tried breaking initrd, but unless it is done at 'top' udevd
  starts and the system hits this problem.

  Serial console logs of the failed and successful boot attempts are
  attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358491/+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 1358491] Re: [Trusty] fails to boot with kernels later than v3.11: systemd-udevd[133]: conflicting device node

2015-06-10 Thread TJ
** 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/1358491

Title:
  [Trusty] fails to boot with kernels later than v3.11: systemd-
  udevd[133]: conflicting device node

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  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 the upgrade the server
  fails to boot using kernel version 3.13.0-24-generic during early udev
  whilst still in the initrd. Errors of the form:

  [6.989549] systemd-udevd[137]: inotify_add_watch(7, /dev/sdi2, 10) 
failed: No such file or directory
  ...
  [7.092733] systemd-udevd[133]: conflicting device node 
'/dev/mapper/pdc_ecjaiecgch1' found, link to '/dev/dm-2' will not be created

  are reported for some devices, usually the Promise 'fake' RAID
  devices.

  The system hangs at that point without ever dropping to a busybox
  shell.

  Starting with an earlier Saucy kernel version 3.11.0-12-generic allows
  the server to start successfully.

  After some research it appears that maybe this is due to an
  incompatibility between systemd-udevd and device-mapper and/or dmraid-
  activate. I read in a similar Fedora bug report a comment by Kay
  Seivers:

  https://bugzilla.redhat.com/show_bug.cgi?id=867593#c11

  Device-mapper seems to mknod() things in /dev, which just can not work
  correctly today.

  There is nothing udev can fix here, it will never touch any device
  node, which should not exist in the first place, that is in the way.

  I've tried breaking initrd, but unless it is done at 'top' udevd
  starts and the system hits this problem.

  Serial console logs of the failed and successful boot attempts are
  attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358491/+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 1314787] Re: Memory leak

2015-07-04 Thread TJ
** 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 notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1314787

Title:
  Memory leak

Status in fglrx-installer package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  I upgraded my PC from Ubuntu 13.10 to 14.04 (released one). After
  upgrade I found the PC slows down soon even without apps running on
  it. When checking with system monitor I found all the physical memory
  was full and the swap file was in use (which never happened with
  13.10). I restarted the PC and left it alone. After six hours memory
  consumption of xorg went from original 250MB to 1,3GB. I guess there
  is a memory leak in the process.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6
  Uname: Linux 3.11.0-20-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr 30 23:05:47 2014
  DistUpgraded: 2014-04-26 21:44:20,660 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: fglrx, 13.350.1, 3.11.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Device [1787:2291]
  InstallationDate: Installed on 2013-10-29 (183 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 002: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-20-generic 
root=UUID=a4de809d-e263-4318-8bf0-1bd1422076e3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (4 days ago)
  dmi.bios.date: 09/11/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1105
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4N78 SE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1105:bd09/11/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N78SE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Apr 30 22:53:24 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB Optical Mouse MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
   AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or 

[Kernel-packages] [Bug 1486581] Re: Automatic resume from suspend

2015-08-20 Thread TJ
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 (Ubuntu)
   Status: Incomplete = Invalid

** Summary changed:

- Automatic resume from suspend
+ Removed USB3 device from USB3 port causes S3 Resume to Fail

-- 
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/1486581

Title:
  Removed USB3 device from USB3 port causes S3 Resume to Fail

Status in acpid package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am using Ubuntu 15.04 with Mainline Kernel 4.2 RC7 on a Lenovo B5400
  laptop.

  When I plug an USB3 flash drive into either of the USB3 ports, then
  remove the flash drive and try to suspend (using the GUI), the
  computer will resume automatically from suspend in a second.

  The problem is not present when using a USB2 device in USB3 ports or when 
using a USB3 device in the USB2 port.
  If I do not remove the flash drive from the USB3 port suspend will work as 
expected.

  I've googled for this bug and found some guides in fixing a similar
  problem, but none of them worked.

  I'm not _sure_ what package is the cause of this problem, so acpid
  might be the wrong choice.

  Below is attached /proc/acpi/wakeup as suggested by the
  DebuggingKernelSuspend, please tell me if more information or logs are
  needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1486581/+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 1477587] Re: One black screen of two when both on 1080p60

2015-07-23 Thread TJ
Attached is IRC log of report and diagnosis

** Attachment added: IRC log of report and diagnosis
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477587/+attachment/4433051/+files/irc.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/1477587

Title:
  One black screen of two when both on 1080p60

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed

Bug description:
  One display turns off when both outputs are set to 1920x1080@60.0. They both 
still work separately on that rate.
  Forcing the one to 1920x1080@59.9 is functioning as a work-around.

  The good kernel version was linux_3.19.0-21.21.
  This Problem occurred in kernel linux_3.19.0-22.22 and linux_3.19.0-23.24.

  GPU is: Radeon HD 6670 using the radeon open source driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-23-generic 3.19.0-23.24
  ProcVersionSignature: Ubuntu 3.19.0-23.24-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-23-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andreas3695 F pulseaudio
   /dev/snd/controlC1:  andreas3695 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul 23 15:12:26 2015
  HibernationDevice: RESUME=UUID=4f0d7a88-5c8d-41c5-a44c-d195a257fd4e
  InstallationDate: Installed on 2012-04-11 (1198 days ago)
  InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 755
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-23-generic 
root=UUID=4acbdc21-f685-460d-a0dc-f86e6f346bf3 ro plymouth:debug splash quiet 
drm.debug=0xe
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-23-generic N/A
   linux-backports-modules-3.19.0-23-generic  N/A
   linux-firmware 1.143.2
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-04-27 (87 days ago)
  dmi.bios.date: 04/30/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0GM819
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  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 connected primary 1680x1050+0+0 (normal left inverted right x axis y 
axis) 477mm x 268mm
     1920x1080  60.0 *+  50.0 59.9 60.0
     1920x1080i 60.1 50.0 60.0
     1600x1200  60.0
     1680x1050  59.9
     1280x1024  75.0 60.0
     1440x900   59.9
     1280x960   60.0
     1366x768   59.8
     1152x864   75.0
     1280x720   60.0 50.0 59.9
     1024x768   75.1 70.1 60.0
     832x62474.6
     800x60072.2 75.0 60.3 56.2
     720x57650.0
     720x48060.0 59.9
     640x48075.0 72.8 66.7 60.0 59.9
     720x40070.1
  DVI-0 connected 1920x1080+1680+0 (normal left inverted right x axis y axis) 
477mm x 268mm
     1920x1080  60.0*+
     1280x1024  75.0 60.0
     1152x864   75.0
     1024x768   75.1 60.0
     800x60075.0 60.3
     640x48075.0 60.0
     720x40070.1
  VGA-0 disconnected (normal left inverted right x axis y axis)

  # workaround
  $ xrandr --output HDMI-0 --mode 1920x1080 --rate 59.9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477587/+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 1477587] Re: One black screen of two when both on 1080p60

2015-07-23 Thread TJ
** Description changed:

  One display turns off when both outputs are set to 1920x1080@60.0. They both 
still work separately on that rate.
  Forcing the one to 1920x1080@59.9 is functioning as a work-around.
  
  The good kernel version was linux_3.19.0-21.21.
  This Problem occurred in kernel linux_3.19.0-22.22 and linux_3.19.0-23.24.
  
  GPU is: Radeon HD 6670 using the radeon open source driver.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-23-generic 3.19.0-23.24
  ProcVersionSignature: Ubuntu 3.19.0-23.24-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-23-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  andreas3695 F pulseaudio
-  /dev/snd/controlC1:  andreas3695 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  andreas3695 F pulseaudio
+  /dev/snd/controlC1:  andreas3695 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul 23 15:12:26 2015
  HibernationDevice: RESUME=UUID=4f0d7a88-5c8d-41c5-a44c-d195a257fd4e
  InstallationDate: Installed on 2012-04-11 (1198 days ago)
  InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  IwConfig:
-  eth0  no wireless extensions.
-  
-  lono wireless extensions.
+  eth0  no wireless extensions.
+ 
+  lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 755
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-23-generic 
root=UUID=4acbdc21-f685-460d-a0dc-f86e6f346bf3 ro plymouth:debug splash quiet 
drm.debug=0xe
  RelatedPackageVersions:
-  linux-restricted-modules-3.19.0-23-generic N/A
-  linux-backports-modules-3.19.0-23-generic  N/A
-  linux-firmware 1.143.2
+  linux-restricted-modules-3.19.0-23-generic N/A
+  linux-backports-modules-3.19.0-23-generic  N/A
+  linux-firmware 1.143.2
  RfKill:
-  
+ 
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-04-27 (87 days ago)
  dmi.bios.date: 04/30/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0GM819
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  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 connected primary 1680x1050+0+0 (normal left inverted right x axis y 
axis) 477mm x 268mm
+1920x1080  60.0 +   50.0 59.9 60.0  
+1920x1080i 60.1 50.0 60.0  
+1600x1200  60.0  
+1680x1050  59.9* 
+1280x1024  75.0 60.0  
+1440x900   59.9  
+1280x960   60.0  
+1366x768   59.8  
+1152x864   75.0  
+1280x720   60.0 50.0 59.9  
+1024x768   75.1 70.1 60.0  
+832x62474.6  
+800x60072.2 75.0 60.3 56.2  
+720x57650.0  
+720x48060.0 59.9  
+640x48075.0 72.8 66.7 60.0 59.9  
+720x40070.1  
+ DVI-0 connected 1920x1080+1680+0 (normal left inverted right x axis y axis) 
477mm x 268mm
+1920x1080  60.0*+
+1280x1024  75.0 60.0  
+1152x864   75.0  
+1024x768   75.1 60.0  
+800x60075.0 60.3  
+640x48075.0 60.0  
+720x40070.1  
+ VGA-0 disconnected (normal left inverted right x axis y axis)
+ 
+ # workaround
+ $ xrandr --output HDMI-0 --mode 1920x1080 --rate 59.9

** Changed in: linux (Ubuntu)
   Status: New = Confirmed

** Changed in: linux (Ubuntu)
   Importance: Undecided = High

** Description changed:

  One display turns off when both outputs are set to 1920x1080@60.0. They both 
still work separately on that rate.
  Forcing the one to 1920x1080@59.9 is functioning as a work-around.
  
  The good kernel version was linux_3.19.0-21.21.
  This Problem occurred in kernel linux_3.19.0-22.22 and linux_3.19.0-23.24.
  
  GPU is: Radeon HD 6670 using the radeon open source driver.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-23-generic 3.19.0-23.24
  ProcVersionSignature: Ubuntu 3.19.0-23.24-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-23-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andreas3695 F pulseaudio
   /dev/snd/controlC1:  andreas3695 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul 23 15:12:26 2015
  HibernationDevice: RESUME=UUID=4f0d7a88-5c8d-41c5-a44c-d195a257fd4e
  InstallationDate: Installed on 2012-04-11 (1198 days ago)
  InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  IwConfig

[Kernel-packages] [Bug 1513477] Re: PCI device has incorrect Vendor:Device ID when Southbridge used 0 wait reads

2015-11-10 Thread TJ
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 configuration changes and the device is
now correctly identified.

The solution is to alter the BIOS settings. In this case the "LDT and
PCI Bus Control", and set "PCI1/PCI2 Master 0 WS Write" to Disabled to
enforce 1 wait state. The device also had to be in ports PC1 or PCI2
(nearest the AGP slot) on this Abit KV8-MAX3 mobo.

** Summary changed:

- PCI device has incorrect Vendor:Device ID when Southbridge used 0 wait reads
+ PCI device has incorrect Vendor:Device ID when Southbridge used 0 wait writes

-- 
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

Title:
  PCI device has incorrect Vendor:Device ID when Southbridge used 0 wait
  writes

Status in linux package in Ubuntu:
  Invalid

Bug description:
  No wifi connection showing, wifi network card is unclaimed

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.2.0.16.18
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.2-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lotuspsychje   1410 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Nov  5 14:57:40 2015
  HibernationDevice: RESUME=UUID=c391bf39-6cd0-4357-89f6-46b8c496b553
  InstallationDate: Installed on 2015-10-28 (8 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp0s14   no wireless extensions.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=c53d01a4-d573-4ab2-ad75-f2c8bd8645c3 ro pci=realloc
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.152
  RfKill:
   
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Bestand of map bestaat niet: '/var/log/udev'
  UpgradeStatus: Upgraded to xenial on 2015-10-28 (8 days ago)
  dmi.bios.date: 06/29/2004
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: KV8-MAX3 (VIA K8T800-8237)
  dmi.board.vendor: http://www.abit.com.tw/
  dmi.board.version: 1.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/29/2004:svn:pn:pvr:rvnhttp//www.abit.com.tw/:rnKV8-MAX3(VIAK8T800-8237):rvr1.x:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1513477/+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 1513477] Re: PCI device has incorrect Vendor:Device ID when Southbridge used 0 wait reads

2015-11-10 Thread TJ
** 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, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1513477

Title:
  PCI device has incorrect Vendor:Device ID when Southbridge used 0 wait
  reads

Status in linux package in Ubuntu:
  Invalid

Bug description:
  No wifi connection showing, wifi network card is unclaimed

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.2.0.16.18
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.2-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lotuspsychje   1410 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Nov  5 14:57:40 2015
  HibernationDevice: RESUME=UUID=c391bf39-6cd0-4357-89f6-46b8c496b553
  InstallationDate: Installed on 2015-10-28 (8 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp0s14   no wireless extensions.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=c53d01a4-d573-4ab2-ad75-f2c8bd8645c3 ro pci=realloc
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.152
  RfKill:
   
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Bestand of map bestaat niet: '/var/log/udev'
  UpgradeStatus: Upgraded to xenial on 2015-10-28 (8 days ago)
  dmi.bios.date: 06/29/2004
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: KV8-MAX3 (VIA K8T800-8237)
  dmi.board.vendor: http://www.abit.com.tw/
  dmi.board.version: 1.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/29/2004:svn:pn:pvr:rvnhttp//www.abit.com.tw/:rnKV8-MAX3(VIAK8T800-8237):rvr1.x:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1513477/+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 1513477] Re: PCI device has incorrect Vendor:Device ID when Southbridge used 0 wait writes

2015-11-10 Thread TJ
** 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

Title:
  PCI device has incorrect Vendor:Device ID when Southbridge used 0 wait
  writes

Status in linux package in Ubuntu:
  Invalid

Bug description:
  No wifi connection showing, wifi network card is unclaimed

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.2.0.16.18
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.2-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lotuspsychje   1410 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Nov  5 14:57:40 2015
  HibernationDevice: RESUME=UUID=c391bf39-6cd0-4357-89f6-46b8c496b553
  InstallationDate: Installed on 2015-10-28 (8 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp0s14   no wireless extensions.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=c53d01a4-d573-4ab2-ad75-f2c8bd8645c3 ro pci=realloc
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.152
  RfKill:
   
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Bestand of map bestaat niet: '/var/log/udev'
  UpgradeStatus: Upgraded to xenial on 2015-10-28 (8 days ago)
  dmi.bios.date: 06/29/2004
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: KV8-MAX3 (VIA K8T800-8237)
  dmi.board.vendor: http://www.abit.com.tw/
  dmi.board.version: 1.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/29/2004:svn:pn:pvr:rvnhttp//www.abit.com.tw/:rnKV8-MAX3(VIAK8T800-8237):rvr1.x:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1513477/+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 1513477] Re: Ralink RT2800pci doesnt work by default

2015-11-08 Thread TJ
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 64-bit kernel:

00:0c.0 Network controller [0280]: IBM Device [1014:0601]
Subsystem: Linksys Device [1737:0067]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/bugs/1513477

Title:
  Ralink RT2800pci doesnt work by default

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No wifi connection showing, wifi network card is unclaimed

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.2.0.16.18
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.2-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lotuspsychje   1410 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Nov  5 14:57:40 2015
  HibernationDevice: RESUME=UUID=c391bf39-6cd0-4357-89f6-46b8c496b553
  InstallationDate: Installed on 2015-10-28 (8 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp0s14   no wireless extensions.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=c53d01a4-d573-4ab2-ad75-f2c8bd8645c3 ro pci=realloc
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.152
  RfKill:
   
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Bestand of map bestaat niet: '/var/log/udev'
  UpgradeStatus: Upgraded to xenial on 2015-10-28 (8 days ago)
  dmi.bios.date: 06/29/2004
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: KV8-MAX3 (VIA K8T800-8237)
  dmi.board.vendor: http://www.abit.com.tw/
  dmi.board.version: 1.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/29/2004:svn:pn:pvr:rvnhttp//www.abit.com.tw/:rnKV8-MAX3(VIAK8T800-8237):rvr1.x:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1513477/+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 1490347] [NEW] [Regresision] 15:10 - Cannot pair with devices using PIN codes

2015-08-30 Thread TJ
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
(that statement dated April 2013) but I've not yet identified them.

The agent's implementation in bt_console/bluetoothctl upstream is
incomplete, missing some functions like DisplayPincode.

https://code.google.com/p/chromium/issues/detail?id=222661

Along with the loss of Headset profiles meaning VoIP applications can no
longer use HSP/HFP profiles (requiring functionality yet to land in
Ofono) this cripples the use of Bluetooth for much else than A2DP or
mouse input.

Attempting to pair with, for example, an Apple Wireless Keyboard that
pairs and works correctly with 14.04 LTS, fails totally on 15.10.

The mouse shown below is already paired, connected, and working.

$ 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]# agent on
Agent registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:1F:3A:E0:0A:AF Discovering: yes
[CHG] Device 00:0A:95:4B:BD:C2 LegacyPairing: yes
[CHG] Device 00:0A:95:4B:BD:C2 RSSI: -48
[bluetooth]# pair 00:0A:95:4B:BD:C2
Attempting to pair with 00:0A:95:4B:BD:C2

 at this point nothing is happening

 so I press Enter on the keyboard and...
[agent] PIN code: 791166
 I type 791166 Enter and ...
[agent] PIN code: 237744
 I type 237744 Enter and...
[agent] PIN code: 358866
 I type 358866 Enter and...
Request PIN code
[agent] Enter PIN code: 1234
 I type 1234 Enter on the keyboard and 1234 at the prompt...
Failed to pair: org.bluez.Error.AuthenticationFailed

This cycle repeats in various permuations. Sometimes the final Request
PIN code does not appear.

** Affects: bluez (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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] 15:10 - Cannot pair with devices using PIN codes

Status in bluez package in Ubuntu:
  New

Bug description:
  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
  (that statement dated April 2013) but I've not yet identified them.

  The agent's implementation in bt_console/bluetoothctl upstream is
  incomplete, missing some functions like DisplayPincode.

  https://code.google.com/p/chromium/issues/detail?id=222661

  Along with the loss of Headset profiles meaning VoIP applications can
  no longer use HSP/HFP profiles (requiring functionality yet to land in
  Ofono) this cripples the use of Bluetooth for much else than A2DP or
  mouse input.

  Attempting to pair with, for example, an Apple Wireless Keyboard that
  pairs and works correctly with 14.04 LTS, fails totally on 15.10.

  The mouse shown below is already paired, connected, and working.

  $ 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]# agent on
  Agent registered
  [bluetooth]# default-agent
  Default agent request successful
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller 00:1F:3A:E0:0A:AF Discovering: yes
  [CHG] Device 00:0A:95:4B:BD:C2 LegacyPairing: yes
  [CHG] Device 00:0A:95:4B:BD:C2 RSSI: -48
  [bluetooth]# pair 00:0A:95:4B:BD:C2
  Attempting to pair with 00:0A:95:4B:BD:C2

   at this point nothing is happening

   so I press Enter on the keyboard and...
  [agent] PIN code: 791166
   I type 791166 Enter and ...
  [agent] PIN code: 237744
   I type 237744 Enter and...
  [agent] PIN code: 358866
   I type 358866 Enter and...
  Request PIN code
  [agent] Enter PIN code: 1234
   I type 1234 Enter on the keyboard and 1234 at the prompt...
  Failed to pair: org.bluez.Error.AuthenticationFailed

  This cycle repeats in various permuations. Sometimes the final
  Request PIN code does not appear.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490347/+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] [NEW] 15:10: bluetoothd reports Not enough handles to register service at start

2015-08-30 Thread TJ
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 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

** Affects: bluez (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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:
  New

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 1490347] Re: [Regresision] 15:10 - Cannot pair with devices using PIN codes

2015-08-30 Thread TJ
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] 15:10 - Cannot pair with devices using PIN codes

Status in bluez package in Ubuntu:
  New

Bug description:
  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
  (that statement dated April 2013) but I've not yet identified them.

  The agent's implementation in bt_console/bluetoothctl upstream is
  incomplete, missing some functions like DisplayPincode.

  https://code.google.com/p/chromium/issues/detail?id=222661

  Along with the loss of Headset profiles meaning VoIP applications can
  no longer use HSP/HFP profiles (requiring functionality yet to land in
  Ofono) this cripples the use of Bluetooth for much else than A2DP or
  mouse input.

  Attempting to pair with, for example, an Apple Wireless Keyboard that
  pairs and works correctly with 14.04 LTS, fails totally on 15.10.

  The mouse shown below is already paired, connected, and working.

  $ 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]# agent on
  Agent registered
  [bluetooth]# default-agent
  Default agent request successful
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller 00:1F:3A:E0:0A:AF Discovering: yes
  [CHG] Device 00:0A:95:4B:BD:C2 LegacyPairing: yes
  [CHG] Device 00:0A:95:4B:BD:C2 RSSI: -48
  [bluetooth]# pair 00:0A:95:4B:BD:C2
  Attempting to pair with 00:0A:95:4B:BD:C2

   at this point nothing is happening

   so I press Enter on the keyboard and...
  [agent] PIN code: 791166
   I type 791166 Enter and ...
  [agent] PIN code: 237744
   I type 237744 Enter and...
  [agent] PIN code: 358866
   I type 358866 Enter and...
  Request PIN code
  [agent] Enter PIN code: 1234
   I type 1234 Enter on the keyboard and 1234 at the prompt...
  Failed to pair: org.bluez.Error.AuthenticationFailed

  This cycle repeats in various permuations. Sometimes the final
  Request PIN code does not appear.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490347/+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

2015-08-30 Thread TJ
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 hephaestion.lan.iam.tj bluetoothd[793]: Bluetooth management 
interface 1.9 initialized
Aug 30 23:42:21 hephaestion.lan.iam.tj systemd[1]: Started Bluetooth service.
Aug 30 23:42:21 hephaestion.lan.iam.tj bluetoothd[793]: Failed to obtain 
handles for Service Changed characteristic
Aug 30 23:42:21 hephaestion.lan.iam.tj bluetoothd[793]: Not enough free handles 
to register service
Aug 30 23:42:21 hephaestion.lan.iam.tj bluetoothd[793]: Error adding Link Loss 
service
Aug 30 23:42:21 hephaestion.lan.iam.tj bluetoothd[793]: Not enough free handles 
to register service
Aug 30 23:42:21 hephaestion.lan.iam.tj bluetoothd[793]: Not enough free handles 
to register service
Aug 30 23:42:21 hephaestion.lan.iam.tj bluetoothd[793]: Not enough free handles 
to register service
Aug 30 23:42:21 hephaestion.lan.iam.tj bluetoothd[793]: Current Time Service 
could not be registered
Aug 30 23:42:21 hephaestion.lan.iam.tj bluetoothd[793]: gatt-time-server: 
Input/output error (5)
Aug 30 23:42:21 hephaestion.lan.iam.tj bluetoothd[793]: Not enough free handles 
to register service
Aug 30 23:42:21 hephaestion.lan.iam.tj bluetoothd[793]: Not enough free handles 
to register service
Aug 30 23:42:21 hephaestion.lan.iam.tj bluetoothd[793]: Sap driver 
initialization failed.
Aug 30 23:42:21 hephaestion.lan.iam.tj bluetoothd[793]: sap-server: Operation 
not permitted (1)
Aug 30 23:42:25 hephaestion.lan.iam.tj bluetoothd[793]: Endpoint registered: 
sender=:1.33 path=/MediaEndpoint/A2DPSource
Aug 30 23:42:25 hephaestion.lan.iam.tj bluetoothd[793]: Endpoint registered: 
sender=:1.33 path=/MediaEndpoint/A2DPSink
Aug 30 23:43:06 hephaestion.lan.iam.tj bluetoothd[793]: Endpoint registered: 
sender=:1.68 path=/MediaEndpoint/A2DPSource
Aug 30 23:43:06 hephaestion.lan.iam.tj bluetoothd[793]: Endpoint registered: 
sender=:1.68 path=/MediaEndpoint/A2DPSink
Aug 30 23:43:06 hephaestion.lan.iam.tj bluetoothd[793]: RFCOMM server failed 
for Headset Voice gateway: rfcomm_bind: Address already in use (98)
Aug 30 23:43:15 hephaestion.lan.iam.tj bluetoothd[793]: Endpoint unregistered: 
sender=:1.33 path=/MediaEndpoint/A2DPSource
Aug 30 23:43:15 hephaestion.lan.iam.tj bluetoothd[793]: Endpoint unregistered: 
sender=:1.33 path=/MediaEndpoint/A2DPSink

-- 
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:
  New

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

[Kernel-packages] [Bug 1490347] Re: [Regresision] 15:10 - Cannot pair with devices using PIN codes

2015-08-30 Thread TJ
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
[bluetooth]# devices
Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
[bluetooth]# paired-devices
Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
[bluetooth]# agent on
Agent registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:1F:3A:E0:0A:AF Discovering: yes
[CHG] Device 00:07:61:3B:86:98 Connected: yes
[CHG] Device 00:0A:95:4B:BD:C2 LegacyPairing: yes
[CHG] Device 00:0A:95:4B:BD:C2 RSSI: -50
[Bluetooth Travel Mouse]# pair 00:0A:95:4B:BD:C2
Attempting to pair with 00:0A:95:4B:BD:C2
[agent] PIN code: 614003
[agent] PIN code: 201404
[agent] PIN code: 653338
Request PIN code
[agent] Enter PIN code: 1234
Failed to pair: org.bluez.Error.AuthenticationFailed


** Attachment added: bluetoothd -nd log trying to pair with pin code
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490347/+attachment/4454724/+files/bluetoohd.log

-- 
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] 15:10 - Cannot pair with devices using PIN codes

Status in bluez package in Ubuntu:
  New

Bug description:
  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
  (that statement dated April 2013) but I've not yet identified them.

  The agent's implementation in bt_console/bluetoothctl upstream is
  incomplete, missing some functions like DisplayPincode.

  https://code.google.com/p/chromium/issues/detail?id=222661

  Along with the loss of Headset profiles meaning VoIP applications can
  no longer use HSP/HFP profiles (requiring functionality yet to land in
  Ofono) this cripples the use of Bluetooth for much else than A2DP or
  mouse input.

  Attempting to pair with, for example, an Apple Wireless Keyboard that
  pairs and works correctly with 14.04 LTS, fails totally on 15.10.

  The mouse shown below is already paired, connected, and working.

  $ 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]# agent on
  Agent registered
  [bluetooth]# default-agent
  Default agent request successful
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller 00:1F:3A:E0:0A:AF Discovering: yes
  [CHG] Device 00:0A:95:4B:BD:C2 LegacyPairing: yes
  [CHG] Device 00:0A:95:4B:BD:C2 RSSI: -48
  [bluetooth]# pair 00:0A:95:4B:BD:C2
  Attempting to pair with 00:0A:95:4B:BD:C2

   at this point nothing is happening

   so I press Enter on the keyboard and...
  [agent] PIN code: 791166
   I type 791166 Enter and ...
  [agent] PIN code: 237744
   I type 237744 Enter and...
  [agent] PIN code: 358866
   I type 358866 Enter and...
  Request PIN code
  [agent] Enter PIN code: 1234
   I type 1234 Enter on the keyboard and 1234 at the prompt...
  Failed to pair: org.bluez.Error.AuthenticationFailed

  This cycle repeats in various permuations. Sometimes the final
  Request PIN code does not appear.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490347/+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 1490551] Re: Wily: hidinput_disconnect BUG: unable to handle kernel NULL pointer derefernce at (null)

2015-08-31 Thread TJ
** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1490551

Title:
  Wily: hidinput_disconnect BUG: unable to handle kernel NULL pointer
  derefernce at (null)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  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 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
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  MachineType: Dell Inc. XPS M1530
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-lowlatency 
root=/dev/mapper/VG_OS-ubuntu_14.04_rootfs ro debug
  ProcVersionSignature: Ubuntu 4.1.0-3.3-lowlatency 4.1.3
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-lowlatency N/A
   linux-backports-modules-4.1.0-3-lowlatency  N/A
   linux-firmware  1.147
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.1.0-3-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True
  dmi.bios.date: 11/19/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: XPS M1530
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490551/+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 1437988] Re: 10ec:8179 wireless network and browser issues

2015-08-31 Thread TJ
** 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.net/bugs/1437988

Title:
  10ec:8179 wireless network and browser issues

Status in linux package in Ubuntu:
  In Progress

Bug description:
  My wireless adapter connecting to my Linsksys wrt120N (firmware
  version 1.0.07) that constantly drops, only when running Ubuntu. Also
  no matter which browser I use it will arbitrarily max out the CPU
  usage and lock me up at times.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-48-generic 3.13.0-48.80
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  Uname: Linux 3.13.0-48-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  karl   2708 F pulseaudio
   /dev/snd/controlC1:  karl   2708 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar 29 22:45:34 2015
  HibernationDevice: RESUME=UUID=e720cd76-77cb-4087-bfcc-876f10ecb858
  InstallationDate: Installed on 2015-02-13 (44 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 001 Device 002: ID 8087:8000 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 0c45:6516 Microdia
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-48-generic.efi.signed 
root=UUID=fd43416e-9f3d-47f8-826d-37ffc7fdf565 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-48-generic N/A
   linux-backports-modules-3.13.0-48-generic  N/A
   linux-firmware 1.127.11
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8014
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 10.02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.04:bd08/25/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn8014:rvr10.02:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 097412405F0620180
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1437988/+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 1437988] Re: 10ec:8179 wireless network and browser issues

2015-08-31 Thread TJ
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 from the GRUB boot manager menu). It is
just possible that memory corruption is the root cause of both issues.

However, when the signal is lost capturing recent entries in the syslog
and kern.log might be helpful here:

sudo tail -n 300 /var/log/syslog /var/log/kern.log | tee /tmp/rtl8188ee-
lost-signal.log

And then attach "/tmp/rtl8188ee-lost-signal.log" to this bug report.

The issue could well be caused by some power-saving feature. The
rtl8188ee kernel module has several PARaMeters that can affect power
state so it might be worth doing some tests with different values. To
see the parameters the module supports use the "modinfo "
command. The range of supported PARMs may differ for different versions
of the Linux kernel.

For v4.1.6 I see:

$ modinfo rtl8188ee
filename:   
/lib/modules/4.1.0-3-lowlatency/kernel/drivers/net/wireless/rtlwifi/rtl8188ee/rtl8188ee.ko
firmware:   rtlwifi/rtl8188efw.bin
description:Realtek 8188E 802.11n PCI wireless
license:GPL
author: Larry Finger
author: Realtek WlanFAE 
author: zhiyuan_yang
srcversion: 14A7C9ABC9B1C044E6EBB43
alias:  pci:v10ECd8179sv*sd*bc*sc*i*
depends:rtlwifi,rtl_pci,mac80211
intree: Y
vermagic:   4.1.0-3-lowlatency SMP preempt mod_unload modversions 
signer: Build time autogenerated kernel key
sig_key:B5:F9:90:FB:D3:8C:30:BA:EA:DB:EF:46:F8:6E:90:E1:9C:A7:5B:14
sig_hashalgo:   sha512
parm:   swenc:Set to 1 for software crypto (default 0)
 (bool)
parm:   ips:Set to 0 to not use link power save (default 1)
 (bool)
parm:   swlps:Set to 1 to use SW control power save (default 0)
 (bool)
parm:   fwlps:Set to 1 to use FW control power save (default 1)
 (bool)
parm:   msi:Set to 1 to use MSI interrupts mode (default 1)
 (bool)
parm:   debug:Set debug level (0-5) (default 0) (int)
parm:   disable_watchdog:Set to 1 to disable the watchdog (default 0)
 (bool)

In order of preference I'd try "ips=0" then "fwlps=0" since both default
to enabling power-save features.

It is best to test these options manually before adding them to the
system configuration. This can be done by disabling the Wireless
Networking then in a terminal unloading the module and re-loading it
with the parameter, e.g:

sudo modprobe --remove rtl8188ee

sudo modprobe rtl8188ee ips=0

Re-enable Wireless Networking and test. If the failure still occurs
repeat the process with another param. Multiple params can be added to
the modprobe options separated by spaces, e.g.

sudo modprobe rtl8188ee ips=0 fwlps=0


You can check the module has loaded correctly with:

sudo tail  /var/log/kern.log


If none of these tests offer improvements with the Ubuntu kernel versions then 
testing with the latest v4.2 mainline kernel from the Kernel Team's PPA would 
be the next step.

-- 
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/1437988

Title:
  10ec:8179 wireless network and browser issues

Status in linux package in Ubuntu:
  In Progress

Bug description:
  My wireless adapter connecting to my Linsksys wrt120N (firmware
  version 1.0.07) that constantly drops, only when running Ubuntu. Also
  no matter which browser I use it will arbitrarily max out the CPU
  usage and lock me up at times.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-48-generic 3.13.0-48.80
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  Uname: Linux 3.13.0-48-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  karl   2708 F pulseaudio
   /dev/snd/controlC1:  karl   2708 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar 29 22:45:34 2015
  HibernationDevice: RESUME=UUID=e720cd76-77cb-4087-bfcc-876f10ecb858
  InstallationDate: Installed on 2015-02-13 (44 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 001 Device 002: ID 8087:8000 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 0c45:6516 Microdia
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-48-generic.efi.signed 
root=UUID=fd43416e-9f3d-47f8-826d-37ffc7fdf565 ro quiet 

[Kernel-packages] [Bug 1490551] [NEW] Wily: hidinput_disconnect BUG: unable to handle kernel NULL pointer derefernce at (null)

2015-08-31 Thread TJ
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 attached:

$ journalctl  -n 48 | awk '{$1="";$2="";$4="";print $0}'

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

** Attachment added: "kernel BUG report"
   
https://bugs.launchpad.net/bugs/1490551/+attachment/4455081/+files/kernel-bt-crash.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/1490551

Title:
  Wily: hidinput_disconnect BUG: unable to handle kernel NULL pointer
  derefernce at (null)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  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 attached:

  $ journalctl  -n 48 | awk '{$1="";$2="";$4="";print $0}'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490551/+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 1490551] ProcCpuinfo.txt

2015-08-31 Thread TJ
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1490551/+attachment/4455112/+files/ProcCpuinfo.txt

-- 
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/1490551

Title:
  Wily: hidinput_disconnect BUG: unable to handle kernel NULL pointer
  derefernce at (null)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  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 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
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  MachineType: Dell Inc. XPS M1530
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-lowlatency 
root=/dev/mapper/VG_OS-ubuntu_14.04_rootfs ro debug
  ProcVersionSignature: Ubuntu 4.1.0-3.3-lowlatency 4.1.3
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-lowlatency N/A
   linux-backports-modules-4.1.0-3-lowlatency  N/A
   linux-firmware  1.147
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.1.0-3-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True
  dmi.bios.date: 11/19/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: XPS M1530
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490551/+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 1490551] Lspci.txt

2015-08-31 Thread TJ
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1490551/+attachment/4455110/+files/Lspci.txt

-- 
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/1490551

Title:
  Wily: hidinput_disconnect BUG: unable to handle kernel NULL pointer
  derefernce at (null)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  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 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
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  MachineType: Dell Inc. XPS M1530
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-lowlatency 
root=/dev/mapper/VG_OS-ubuntu_14.04_rootfs ro debug
  ProcVersionSignature: Ubuntu 4.1.0-3.3-lowlatency 4.1.3
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-lowlatency N/A
   linux-backports-modules-4.1.0-3-lowlatency  N/A
   linux-firmware  1.147
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.1.0-3-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True
  dmi.bios.date: 11/19/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: XPS M1530
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490551/+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 1490551] Lsusb.txt

2015-08-31 Thread TJ
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1490551/+attachment/4455111/+files/Lsusb.txt

-- 
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/1490551

Title:
  Wily: hidinput_disconnect BUG: unable to handle kernel NULL pointer
  derefernce at (null)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  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 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
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  MachineType: Dell Inc. XPS M1530
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-lowlatency 
root=/dev/mapper/VG_OS-ubuntu_14.04_rootfs ro debug
  ProcVersionSignature: Ubuntu 4.1.0-3.3-lowlatency 4.1.3
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-lowlatency N/A
   linux-backports-modules-4.1.0-3-lowlatency  N/A
   linux-firmware  1.147
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.1.0-3-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True
  dmi.bios.date: 11/19/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: XPS M1530
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490551/+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 1490551] CurrentDmesg.txt

2015-08-31 Thread TJ
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1490551/+attachment/4455107/+files/CurrentDmesg.txt

-- 
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/1490551

Title:
  Wily: hidinput_disconnect BUG: unable to handle kernel NULL pointer
  derefernce at (null)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  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 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
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  MachineType: Dell Inc. XPS M1530
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-lowlatency 
root=/dev/mapper/VG_OS-ubuntu_14.04_rootfs ro debug
  ProcVersionSignature: Ubuntu 4.1.0-3.3-lowlatency 4.1.3
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-lowlatency N/A
   linux-backports-modules-4.1.0-3-lowlatency  N/A
   linux-firmware  1.147
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.1.0-3-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True
  dmi.bios.date: 11/19/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: XPS M1530
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490551/+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 1490551] ProcEnviron.txt

2015-08-31 Thread TJ
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1490551/+attachment/4455113/+files/ProcEnviron.txt

-- 
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/1490551

Title:
  Wily: hidinput_disconnect BUG: unable to handle kernel NULL pointer
  derefernce at (null)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  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 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
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  MachineType: Dell Inc. XPS M1530
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-lowlatency 
root=/dev/mapper/VG_OS-ubuntu_14.04_rootfs ro debug
  ProcVersionSignature: Ubuntu 4.1.0-3.3-lowlatency 4.1.3
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-lowlatency N/A
   linux-backports-modules-4.1.0-3-lowlatency  N/A
   linux-firmware  1.147
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.1.0-3-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True
  dmi.bios.date: 11/19/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: XPS M1530
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490551/+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 1490551] Re: Wily: hidinput_disconnect BUG: unable to handle kernel NULL pointer derefernce at (null)

2015-08-31 Thread TJ
apport information

** Tags added: apport-collected wily

** Description changed:

  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 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
+ DistroRelease: Ubuntu 15.10
+ EcryptfsInUse: Yes
+ MachineType: Dell Inc. XPS M1530
+ NonfreeKernelModules: nvidia
+ Package: linux (not installed)
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-lowlatency 
root=/dev/mapper/VG_OS-ubuntu_14.04_rootfs ro debug
+ ProcVersionSignature: Ubuntu 4.1.0-3.3-lowlatency 4.1.3
+ RelatedPackageVersions:
+  linux-restricted-modules-4.1.0-3-lowlatency N/A
+  linux-backports-modules-4.1.0-3-lowlatency  N/A
+  linux-firmware  1.147
+ Tags:  wily
+ UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
+ Uname: Linux 4.1.0-3-lowlatency x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm sudo
+ _MarkForUpload: True
+ dmi.bios.date: 11/19/2008
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: A12
+ dmi.board.vendor: Dell Inc.
+ dmi.chassis.type: 8
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
+ dmi.product.name: XPS M1530
+ dmi.sys.vendor: Dell Inc.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1490551/+attachment/4455106/+files/AlsaInfo.txt

-- 
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/1490551

Title:
  Wily: hidinput_disconnect BUG: unable to handle kernel NULL pointer
  derefernce at (null)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  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 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
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  MachineType: Dell Inc. XPS M1530
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-lowlatency 
root=/dev/mapper/VG_OS-ubuntu_14.04_rootfs ro debug
  ProcVersionSignature: Ubuntu 4.1.0-3.3-lowlatency 4.1.3
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-lowlatency N/A
   linux-backports-modules-4.1.0-3-lowlatency  N/A
   linux-firmware  1.147
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.1.0-3-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True
  dmi.bios.date: 11/19/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: XPS M1530
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490551/+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 1490551] UdevDb.txt

2015-08-31 Thread TJ
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1490551/+attachment/4455118/+files/UdevDb.txt

-- 
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/1490551

Title:
  Wily: hidinput_disconnect BUG: unable to handle kernel NULL pointer
  derefernce at (null)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  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 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
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  MachineType: Dell Inc. XPS M1530
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-lowlatency 
root=/dev/mapper/VG_OS-ubuntu_14.04_rootfs ro debug
  ProcVersionSignature: Ubuntu 4.1.0-3.3-lowlatency 4.1.3
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-lowlatency N/A
   linux-backports-modules-4.1.0-3-lowlatency  N/A
   linux-firmware  1.147
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.1.0-3-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True
  dmi.bios.date: 11/19/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: XPS M1530
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490551/+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 1490551] WifiSyslog.txt

2015-08-31 Thread TJ
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1490551/+attachment/4455119/+files/WifiSyslog.txt

-- 
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/1490551

Title:
  Wily: hidinput_disconnect BUG: unable to handle kernel NULL pointer
  derefernce at (null)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  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 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
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  MachineType: Dell Inc. XPS M1530
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-lowlatency 
root=/dev/mapper/VG_OS-ubuntu_14.04_rootfs ro debug
  ProcVersionSignature: Ubuntu 4.1.0-3.3-lowlatency 4.1.3
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-lowlatency N/A
   linux-backports-modules-4.1.0-3-lowlatency  N/A
   linux-firmware  1.147
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.1.0-3-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True
  dmi.bios.date: 11/19/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: XPS M1530
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490551/+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 1490551] IwConfig.txt

2015-08-31 Thread TJ
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1490551/+attachment/4455108/+files/IwConfig.txt

-- 
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/1490551

Title:
  Wily: hidinput_disconnect BUG: unable to handle kernel NULL pointer
  derefernce at (null)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  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 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
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  MachineType: Dell Inc. XPS M1530
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-lowlatency 
root=/dev/mapper/VG_OS-ubuntu_14.04_rootfs ro debug
  ProcVersionSignature: Ubuntu 4.1.0-3.3-lowlatency 4.1.3
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-lowlatency N/A
   linux-backports-modules-4.1.0-3-lowlatency  N/A
   linux-firmware  1.147
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.1.0-3-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True
  dmi.bios.date: 11/19/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: XPS M1530
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490551/+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 1490551] JournalErrors.txt

2015-08-31 Thread TJ
apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1490551/+attachment/4455109/+files/JournalErrors.txt

-- 
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/1490551

Title:
  Wily: hidinput_disconnect BUG: unable to handle kernel NULL pointer
  derefernce at (null)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  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 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
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  MachineType: Dell Inc. XPS M1530
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-lowlatency 
root=/dev/mapper/VG_OS-ubuntu_14.04_rootfs ro debug
  ProcVersionSignature: Ubuntu 4.1.0-3.3-lowlatency 4.1.3
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-lowlatency N/A
   linux-backports-modules-4.1.0-3-lowlatency  N/A
   linux-firmware  1.147
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.1.0-3-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True
  dmi.bios.date: 11/19/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: XPS M1530
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490551/+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 1490551] ProcInterrupts.txt

2015-08-31 Thread TJ
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1490551/+attachment/4455114/+files/ProcInterrupts.txt

-- 
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/1490551

Title:
  Wily: hidinput_disconnect BUG: unable to handle kernel NULL pointer
  derefernce at (null)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  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 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
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  MachineType: Dell Inc. XPS M1530
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-lowlatency 
root=/dev/mapper/VG_OS-ubuntu_14.04_rootfs ro debug
  ProcVersionSignature: Ubuntu 4.1.0-3.3-lowlatency 4.1.3
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-lowlatency N/A
   linux-backports-modules-4.1.0-3-lowlatency  N/A
   linux-firmware  1.147
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.1.0-3-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True
  dmi.bios.date: 11/19/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: XPS M1530
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490551/+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 1490551] ProcModules.txt

2015-08-31 Thread TJ
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1490551/+attachment/4455115/+files/ProcModules.txt

-- 
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/1490551

Title:
  Wily: hidinput_disconnect BUG: unable to handle kernel NULL pointer
  derefernce at (null)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  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 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
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  MachineType: Dell Inc. XPS M1530
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-lowlatency 
root=/dev/mapper/VG_OS-ubuntu_14.04_rootfs ro debug
  ProcVersionSignature: Ubuntu 4.1.0-3.3-lowlatency 4.1.3
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-lowlatency N/A
   linux-backports-modules-4.1.0-3-lowlatency  N/A
   linux-firmware  1.147
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.1.0-3-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True
  dmi.bios.date: 11/19/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: XPS M1530
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490551/+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 1490551] RfKill.txt

2015-08-31 Thread TJ
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1490551/+attachment/4455117/+files/RfKill.txt

-- 
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/1490551

Title:
  Wily: hidinput_disconnect BUG: unable to handle kernel NULL pointer
  derefernce at (null)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  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 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
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  MachineType: Dell Inc. XPS M1530
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-lowlatency 
root=/dev/mapper/VG_OS-ubuntu_14.04_rootfs ro debug
  ProcVersionSignature: Ubuntu 4.1.0-3.3-lowlatency 4.1.3
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-lowlatency N/A
   linux-backports-modules-4.1.0-3-lowlatency  N/A
   linux-firmware  1.147
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.1.0-3-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True
  dmi.bios.date: 11/19/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: XPS M1530
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490551/+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 1490551] PulseList.txt

2015-08-31 Thread TJ
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1490551/+attachment/4455116/+files/PulseList.txt

-- 
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/1490551

Title:
  Wily: hidinput_disconnect BUG: unable to handle kernel NULL pointer
  derefernce at (null)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  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 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
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  MachineType: Dell Inc. XPS M1530
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-lowlatency 
root=/dev/mapper/VG_OS-ubuntu_14.04_rootfs ro debug
  ProcVersionSignature: Ubuntu 4.1.0-3.3-lowlatency 4.1.3
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-lowlatency N/A
   linux-backports-modules-4.1.0-3-lowlatency  N/A
   linux-firmware  1.147
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.1.0-3-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True
  dmi.bios.date: 11/19/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: XPS M1530
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490551/+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 1490551] Re: Wily: hidinput_disconnect BUG: unable to handle kernel NULL pointer derefernce at (null)

2015-09-01 Thread TJ
Unfortunately, no, due to the GPL symbol change for flush_workqueue,
which prevents DKMS from building the nvidia driver. Looks like mainline
won't get that fix until 4.3:

http://lkml.iu.edu/hypermail/linux/kernel/1508.0/02260.html

WARNING: could not find /var/lib/dkms/nvidia-340/340.76/build/.nv-kernel.o.cmd 
for /var/lib/dkms/nvidia-340/340.76/build/nv-kernel.o
FATAL: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 
'flush_workqueue'

-- 
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/1490551

Title:
  Wily: hidinput_disconnect BUG: unable to handle kernel NULL pointer
  derefernce at (null)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  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 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
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  MachineType: Dell Inc. XPS M1530
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-lowlatency 
root=/dev/mapper/VG_OS-ubuntu_14.04_rootfs ro debug
  ProcVersionSignature: Ubuntu 4.1.0-3.3-lowlatency 4.1.3
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-lowlatency N/A
   linux-backports-modules-4.1.0-3-lowlatency  N/A
   linux-firmware  1.147
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.1.0-3-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True
  dmi.bios.date: 11/19/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: XPS M1530
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490551/+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 1491988] [NEW] 15.10: Multiple Bluetooth controllers not found

2015-09-03 Thread TJ
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 
Sep 03 19:39:12 hephaestion.lan.iam.tj bluetoothd[3973]: 
src/adapter.c:adapter_service_add() /org/bluez/hci0

$ 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
[NEW] Device 00:19:15:29:83:14 Think Outside Keyboard
[bluetooth]# list
Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]

** Affects: bluez (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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 in bluez package in Ubuntu:
  New

Bug description:
  $ 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 
  Sep 03 19:39:12 hephaestion.lan.iam.tj bluetoothd[3973]: 
src/adapter.c:adapter_service_add() /org/bluez/hci0

  $ 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
  [NEW] Device 00:19:15:29:83:14 Think Outside Keyboard
  [bluetooth]# list
  Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1491988/+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 1437988] Re: 10ec:8179 wireless network and browser issues

2015-09-03 Thread TJ
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: 3=DEAUTH_LEAVING)

-- 
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/1437988

Title:
  10ec:8179 wireless network and browser issues

Status in linux package in Ubuntu:
  In Progress

Bug description:
  My wireless adapter connecting to my Linsksys wrt120N (firmware
  version 1.0.07) that constantly drops, only when running Ubuntu. Also
  no matter which browser I use it will arbitrarily max out the CPU
  usage and lock me up at times.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-48-generic 3.13.0-48.80
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  Uname: Linux 3.13.0-48-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  karl   2708 F pulseaudio
   /dev/snd/controlC1:  karl   2708 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar 29 22:45:34 2015
  HibernationDevice: RESUME=UUID=e720cd76-77cb-4087-bfcc-876f10ecb858
  InstallationDate: Installed on 2015-02-13 (44 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 001 Device 002: ID 8087:8000 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 0c45:6516 Microdia
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-48-generic.efi.signed 
root=UUID=fd43416e-9f3d-47f8-826d-37ffc7fdf565 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-48-generic N/A
   linux-backports-modules-3.13.0-48-generic  N/A
   linux-firmware 1.127.11
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8014
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 10.02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.04:bd08/25/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn8014:rvr10.02:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 097412405F0620180
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1437988/+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 876520] Re: mouse cursor gone

2015-09-05 Thread TJ
** 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 the
  following command in the terminal: "sudo /etc/init.d/lightdm restart".
  Mouse cursor is suddenly visible again.
+ 
+ -
+ 
+ Expanded Workaround confirmed by several users courtesy of Mark Kirkwood
+ (mark-kirkwood-k) in comment 2:
+ 
+ A. TEST
+ 
+ 1. hold down shift immediately at boot until the GRUB boot manager menu shows
+ 2. highlight the 'Ubuntu' entry and press 'e' to Edit it
+ 3. navigate to the line that begins "linux ..."
+ 4. navigate to the word "splash" and delete it
+ 5. boot using the modified setting by pressing Ctrl+X or F10
+ 
+ 
+ B. If the test change caused the cursor to show:
+ 
+ 1. edit "/etc/default/grub/" (will need sudo/gksudo/kdesudo for elevated 
privileges); remove "splash" from the variable GRUB_CMDLINE_LINUX_DEFAULT=. 
Save the file.
+ 2. "sudo update-grub". This will make the change to the kernel command-line 
that was done manually in TEST A.
+ 3. Reboot and test
+ 
+ 
+ I've added the 'plymouth' package as a possible cause of the issue. It is 
likely more a case of the console being put into the wrong graphics mode to 
support the graphical splash.
+ -
  
  I am using an old ASUS A6000 A6V laptop with the following hardware
  information (obtained via "lspci")
  
  00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express 
Processor to DRAM Controller (rev 04)
  00:01.0 PCI bridge: Intel Corporation Mobile 915GM/PM Express PCI Express 
Root Port (rev 04)
  00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
High Definition Audio Controller (rev 04)
  00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB UHCI #1 (rev 04)
  00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB UHCI #2 (rev 04)
  00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB UHCI #3 (rev 04)
  00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB UHCI #4 (rev 04)
  00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB2 EHCI Controller (rev 04)
  00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d4)
  00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge 
(rev 04)
  00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
IDE Controller (rev 04)
  00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus 
Controller (rev 04)
  01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X700 
(PCIE)
  02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit 
Ethernet Controller (rev 13)
  02:01.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev b3)
  02:01.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C552 IEEE 1394 Controller (rev 
08)
  02:01.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host 
Adapter (rev 17)
  02:01.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter 
(rev 08)
  02:03.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] 
Network Connection (rev 05)
  
  I appreciate any help on this matter to get this small bug fixed.
  
  Dennis

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
   Status: New => Triaged

** Changed in: plymouth (Ubuntu)
   Status: New => Triaged

-- 
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/876520

Title:
  mouse cursor gone

Status in linux package in Ubuntu:
  Triaged
Status in plymouth package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  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 the
  following command in the terminal: "sudo /etc/init.d/lightdm restart".
  Mouse cursor is suddenly visible again.

  -

  Expanded Workaround confirmed by several users courtesy of Mark
  Kirkwood (mark-kirkwood-k) in comment 2:

  A. TEST

  1. hold down shift immediately at boot until the GRUB boot manager menu shows
  2. highlight the 'Ubuntu' entry and press 'e' to Edit it
  3. navigate to the line that begins "linux ..."
  4. navigate to the word "splash" and delete it
  5. boot using the modified setting by pressing Ctrl+X or F10

  
  B. If the test change caused the cursor to show:

  1. edit "/etc/default/grub/" (will need sudo/gksudo/kdesudo for elevated 
privileges); remove "splash" from the variable GRUB_CMDLINE_LINUX_DEFAULT=. 
Save the file.
  2. 

[Kernel-packages] [Bug 1490551] Re: Wily: hidinput_disconnect BUG: unable to handle kernel NULL pointer derefernce at (null)

2015-09-02 Thread TJ
Currently testing with the v4.2 from wily-proposed with additional
patches for:

PCI: check pref compatible bit for mem64 resource of pcie device
PCI: get new realloc size for bridge that does not have children
workqueue: Make flush_workqueue() available again to non GPL modules

-- 
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/1490551

Title:
  Wily: hidinput_disconnect BUG: unable to handle kernel NULL pointer
  derefernce at (null)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  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 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
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  MachineType: Dell Inc. XPS M1530
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-lowlatency 
root=/dev/mapper/VG_OS-ubuntu_14.04_rootfs ro debug
  ProcVersionSignature: Ubuntu 4.1.0-3.3-lowlatency 4.1.3
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-lowlatency N/A
   linux-backports-modules-4.1.0-3-lowlatency  N/A
   linux-firmware  1.147
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.1.0-3-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True
  dmi.bios.date: 11/19/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: XPS M1530
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490551/+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 1491988] Re: 15.10: Multiple Bluetooth controllers not found

2015-09-04 Thread TJ
$ 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 23:46:32 hephaestion.lan.iam.tj bluetoothd[23908]: 
src/rfkill.c:rfkill_event() RFKILL event idx 5 type 2 op 0 soft 0 hard 0


$ 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
[NEW] Device 00:19:15:29:83:14 Think Outside Keyboard
[bluetooth]# list
Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
[CHG] Device 00:07:61:3B:86:98 Connected: yes


$ hcitool dev
Devices:
hci100:10:7A:4D:15:33
hci000:1F:3A:E0:0A:AF

$ lsusb
# Built-in (hci0)
Bus 007 Device 003: ID 413c:8126 Dell Computer Corp. Wireless 355 Bluetooth
# Hot-plugged (hci1)
Bus 006 Device 011: ID 0bdb:1002 Ericsson Business Mobile Networks BV Bluetooth 
Device 1.2


** Attachment added: "bluetoothd debug log whilst connecting 2nd adapter"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1491988/+attachment/4457687/+files/bluetooth-multiple-adapters.log

-- 
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 in bluez package in Ubuntu:
  Incomplete

Bug description:
  $ 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 
  Sep 03 19:39:12 hephaestion.lan.iam.tj bluetoothd[3973]: 
src/adapter.c:adapter_service_add() /org/bluez/hci0

  $ 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
  [NEW] Device 00:19:15:29:83:14 Think Outside Keyboard
  [bluetooth]# list
  Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1491988/+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 989191] Re: Asus Zenbook UX31E powers off on plugin in/out AC adapter

2015-08-25 Thread TJ
Feedback and discussion with sclimans on IRC #ubuntu suggests that the
battery disconnect 'trick' does solve the problem for a while, but one
or maybe more suspend/resume cycles causes it to recur.

That tends to suggest that the UHCI fix of writing 0 to the PCI command
register at suspend might 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.
https://bugs.launchpad.net/bugs/989191

Title:
  Asus Zenbook UX31E powers off on plugin in/out AC adapter

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  In Progress

Bug description:
  When I have logged in to Unity and plug in or out AC adapter to Asus
  Zenbook UX31E, computer powers off. Sometimes this needs couple of
  tries (waiting or not waiting in between) when plugin in or out AC
  adapter.

  This problem doesn't occur when I have switched to console or when in LightDM 
login screen. Problem doesn't happen with MS Windows either.
  And yes, there's enough power in my battery too, I can boot up and use the 
computer without AC adapter.

  syslog prints these lines to stdout in console, when plugin AC adapter first 
out and then in:
    [  869.521396] asus_wmi: Unknown key 57 pressed
    [  874.704525] asus_wmi: Unknown key 58 pressed
    [  876.993295] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id

  What you also need:

  1) lsb_release -rd
    Description:Ubuntu 12.04 LTS
    Release:12.04

  2) I could guess kernel, but it happens _only_ when I have logged in
  to Unity (or Unity 2D)...

  3) I expect that my computer doesn't power off.

  4) Computer powers off.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/989191/+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 989191] Re: Asus Zenbook UX31E powers off on plugin in/out AC adapter

2015-08-25 Thread TJ
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 PC is shutdown and therefore never does a cold reset.

-- 
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/989191

Title:
  Asus Zenbook UX31E powers off on plugin in/out AC adapter

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  When I have logged in to Unity and plug in or out AC adapter to Asus
  Zenbook UX31E, computer powers off. Sometimes this needs couple of
  tries (waiting or not waiting in between) when plugin in or out AC
  adapter.

  This problem doesn't occur when I have switched to console or when in LightDM 
login screen. Problem doesn't happen with MS Windows either.
  And yes, there's enough power in my battery too, I can boot up and use the 
computer without AC adapter.

  syslog prints these lines to stdout in console, when plugin AC adapter first 
out and then in:
    [  869.521396] asus_wmi: Unknown key 57 pressed
    [  874.704525] asus_wmi: Unknown key 58 pressed
    [  876.993295] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id

  What you also need:

  1) lsb_release -rd
    Description:Ubuntu 12.04 LTS
    Release:12.04

  2) I could guess kernel, but it happens _only_ when I have logged in
  to Unity (or Unity 2D)...

  3) I expect that my computer doesn't power off.

  4) Computer powers off.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/989191/+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 989191] Re: Asus Zenbook UX31E powers off on plugin in/out AC adapter

2015-08-25 Thread TJ
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 received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/989191

Title:
  Asus Zenbook UX31E powers off on plugin in/out AC adapter

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  When I have logged in to Unity and plug in or out AC adapter to Asus
  Zenbook UX31E, computer powers off. Sometimes this needs couple of
  tries (waiting or not waiting in between) when plugin in or out AC
  adapter.

  This problem doesn't occur when I have switched to console or when in LightDM 
login screen. Problem doesn't happen with MS Windows either.
  And yes, there's enough power in my battery too, I can boot up and use the 
computer without AC adapter.

  syslog prints these lines to stdout in console, when plugin AC adapter first 
out and then in:
    [  869.521396] asus_wmi: Unknown key 57 pressed
    [  874.704525] asus_wmi: Unknown key 58 pressed
    [  876.993295] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id

  What you also need:

  1) lsb_release -rd
    Description:Ubuntu 12.04 LTS
    Release:12.04

  2) I could guess kernel, but it happens _only_ when I have logged in
  to Unity (or Unity 2D)...

  3) I expect that my computer doesn't power off.

  4) Computer powers off.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/989191/+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 989191] Re: Asus Zenbook UX31E powers off on plugin in/out AC adapter

2015-08-25 Thread TJ
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 received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/989191

Title:
  Asus Zenbook UX31E powers off on plugin in/out AC adapter

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  When I have logged in to Unity and plug in or out AC adapter to Asus
  Zenbook UX31E, computer powers off. Sometimes this needs couple of
  tries (waiting or not waiting in between) when plugin in or out AC
  adapter.

  This problem doesn't occur when I have switched to console or when in LightDM 
login screen. Problem doesn't happen with MS Windows either.
  And yes, there's enough power in my battery too, I can boot up and use the 
computer without AC adapter.

  syslog prints these lines to stdout in console, when plugin AC adapter first 
out and then in:
    [  869.521396] asus_wmi: Unknown key 57 pressed
    [  874.704525] asus_wmi: Unknown key 58 pressed
    [  876.993295] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id

  What you also need:

  1) lsb_release -rd
    Description:Ubuntu 12.04 LTS
    Release:12.04

  2) I could guess kernel, but it happens _only_ when I have logged in
  to Unity (or Unity 2D)...

  3) I expect that my computer doesn't power off.

  4) Computer powers off.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/989191/+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 1491988] Re: 15.10: BT Command List not created: bluetooth:__hci_req_sync:298: hci1 end: err -ETIMEDOUT

2015-09-10 Thread TJ
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 created: bluetooth:__hci_req_sync:298: hci1
  end: err -ETIMEDOUT

Status in bluez package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  $ 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 
  Sep 03 19:39:12 hephaestion.lan.iam.tj bluetoothd[3973]: 
src/adapter.c:adapter_service_add() /org/bluez/hci0

  $ 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
  [NEW] Device 00:19:15:29:83:14 Think Outside Keyboard
  [bluetooth]# list
  Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1491988/+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 1491988] Re: 15.10: Multiple Bluetooth controllers not found

2015-09-09 Thread TJ
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 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 in bluez package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  $ 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 
  Sep 03 19:39:12 hephaestion.lan.iam.tj bluetoothd[3973]: 
src/adapter.c:adapter_service_add() /org/bluez/hci0

  $ 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
  [NEW] Device 00:19:15:29:83:14 Think Outside Keyboard
  [bluetooth]# list
  Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1491988/+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 1491988] Re: 15.10: Multiple Bluetooth controllers not found

2015-09-09 Thread TJ
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 00:52:54 hephaestion kernel: [23633.012115] 
bluetooth:__hci_req_sync:298: hci1 end: err -110


** Attachment added: "kern.log with fuller BT_DBG() output"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491988/+attachment/4460105/+files/kern.2.log

-- 
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 in bluez package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  $ 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 
  Sep 03 19:39:12 hephaestion.lan.iam.tj bluetoothd[3973]: 
src/adapter.c:adapter_service_add() /org/bluez/hci0

  $ 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
  [NEW] Device 00:19:15:29:83:14 Think Outside Keyboard
  [bluetooth]# list
  Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1491988/+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 1496027] [NEW] iwlwifi: Intel 7260 poor performance and disconnects

2015-09-15 Thread TJ
Public bug reported:

This report is a condensation of an extended IRC support session for a
user with ongoing problems with Intel 7260 performance on 14.04.3. It
gathers together the investigative results of the apparent
module/firmware mismatch for iwlwifi.

** Affects: linux (Ubuntu)
 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)

** Changed in: linux (Ubuntu)
   Status: New => In Progress

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

** Description changed:

  This report is a condensation of an extended IRC support session for a
  user with ongoing problems with Intel 7260 performance on 14.04.3. It
- gather together the investigation of the apparent module/firmware
- mismatch for iwlwifi.
+ gathers together the investigative results of the apparent
+ module/firmware mismatch for iwlwifi.

-- 
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/1496027

Title:
  iwlwifi: Intel 7260 poor performance and disconnects

Status in linux package in Ubuntu:
  In Progress

Bug description:
  This report is a condensation of an extended IRC support session for a
  user with ongoing problems with Intel 7260 performance on 14.04.3. It
  gathers together the investigative results of the apparent
  module/firmware mismatch for iwlwifi.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1496027/+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 1491988] Re: 15.10: Multiple Bluetooth controllers not found

2015-09-09 Thread 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>   

 
   

$ hciconfig hci1 commands 
Can't read support commands on hci1: Input/output error (5)


I enabled dynamic_debug to get the BT_DBG() output:

echo 'file drivers/bluetooth/* +p' | sudo tee 
/sys/kernel/debug/dynamic_debug/control
echo 'file net/bluetooth/* +p' | sudo tee 
/sys/kernel/debug/dynamic_debug/control

The attached extract is from the kernel log when connecting the external
USB Bluetooth device.


** Attachment added: "kern.log with captured BT_DBG() a.k.a. pr_debug()"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491988/+attachment/4460097/+files/kern.log

-- 
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 in bluez package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  $ 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 
  Sep 03 19:39:12 hephaestion.lan.iam.tj bluetoothd[3973]: 
src/adapter.c:adapter_service_add() /org/bluez/hci0

  $ 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
  [NEW] Device 00:19:15:29:83:14 Think Outside Keyboard
  [bluetooth]# list
  Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1491988/+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 1490347] Re: [Regresision] 15:10 - Cannot pair with devices using PIN codes

2015-09-09 Thread TJ
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: bluez (Ubuntu)
   Importance: Undecided => High

-- 
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] 15:10 - Cannot pair with devices using PIN codes

Status in bluez package in Ubuntu:
  Triaged

Bug description:
  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
  (that statement dated April 2013) but I've not yet identified them.

  "The agent's implementation in bt_console/bluetoothctl upstream is
  incomplete, missing some functions like DisplayPincode."

  https://code.google.com/p/chromium/issues/detail?id=222661

  Along with the loss of Headset profiles meaning VoIP applications can
  no longer use HSP/HFP profiles (requiring functionality yet to land in
  Ofono) this cripples the use of Bluetooth for much else than A2DP or
  mouse input.

  Attempting to pair with, for example, an Apple Wireless Keyboard that
  pairs and works correctly with 14.04 LTS, fails totally on 15.10.

  The mouse shown below is already paired, connected, and working.

  $ 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]# agent on
  Agent registered
  [bluetooth]# default-agent
  Default agent request successful
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller 00:1F:3A:E0:0A:AF Discovering: yes
  [CHG] Device 00:0A:95:4B:BD:C2 LegacyPairing: yes
  [CHG] Device 00:0A:95:4B:BD:C2 RSSI: -48
  [bluetooth]# pair 00:0A:95:4B:BD:C2
  Attempting to pair with 00:0A:95:4B:BD:C2

  >>> at this point nothing is happening

  >>> so I press Enter on the keyboard and...
  [agent] PIN code: 791166
  >>> I type 791166 Enter and ...
  [agent] PIN code: 237744
  >>> I type 237744 Enter and...
  [agent] PIN code: 358866
  >>> I type 358866 Enter and...
  Request PIN code
  [agent] Enter PIN code: 1234
  >>> I type 1234 Enter on the keyboard and 1234 at the prompt...
  Failed to pair: org.bluez.Error.AuthenticationFailed

  This cycle repeats in various permuations. Sometimes the final
  "Request PIN code" does not appear.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490347/+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 1491988] Re: 15.10: BT Command List not created: bluetooth:__hci_req_sync:298: hci1 end: err -ETIMEDOUT

2015-09-09 Thread TJ
** 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.
https://bugs.launchpad.net/bugs/1491988

Title:
  15.10: BT Command List not created: bluetooth:__hci_req_sync:298: hci1
  end: err -ETIMEDOUT

Status in bluez package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  $ 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 
  Sep 03 19:39:12 hephaestion.lan.iam.tj bluetoothd[3973]: 
src/adapter.c:adapter_service_add() /org/bluez/hci0

  $ 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
  [NEW] Device 00:19:15:29:83:14 Think Outside Keyboard
  [bluetooth]# list
  Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1491988/+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 1491988] Re: 15.10: Multiple Bluetooth controllers not found

2015-09-09 Thread TJ
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 4.98-2ubuntu7 (shows up as an 
adapter after doing 'hciconfig hci1 up')

-- 
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 in bluez package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  $ 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 
  Sep 03 19:39:12 hephaestion.lan.iam.tj bluetoothd[3973]: 
src/adapter.c:adapter_service_add() /org/bluez/hci0

  $ 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
  [NEW] Device 00:19:15:29:83:14 Think Outside Keyboard
  [bluetooth]# list
  Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1491988/+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 1491988] Re: 15.10: Multiple Bluetooth controllers not found

2015-09-09 Thread TJ
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, 2 BT (type 2) and 1 WiFi.

src/main.c:main() Entering main loop
src/rfkill.c:rfkill_event() RFKILL event idx 0 type 2 op 0 soft 0 hard 0
Bluetooth management interface 1.10 initialized
src/adapter.c:read_version_complete() sending read supported commands command
src/adapter.c:read_version_complete() sending read index list command
src/rfkill.c:rfkill_event() RFKILL event idx 1 type 1 op 0 soft 0 hard 0
src/rfkill.c:rfkill_event() RFKILL event idx 2 type 2 op 0 soft 0 hard 0
src/adapter.c:read_commands_complete() Number of commands: 61
src/adapter.c:read_commands_complete() Number of events: 34
src/adapter.c:read_commands_complete() enabling kernel-side connection control
src/adapter.c:read_index_list_complete() Number of controllers: 1

-- 
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 in bluez package in Ubuntu:
  Triaged

Bug description:
  $ 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 
  Sep 03 19:39:12 hephaestion.lan.iam.tj bluetoothd[3973]: 
src/adapter.c:adapter_service_add() /org/bluez/hci0

  $ 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
  [NEW] Device 00:19:15:29:83:14 Think Outside Keyboard
  [bluetooth]# list
  Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1491988/+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 1491988] Re: 15.10: Multiple Bluetooth controllers not found

2015-09-09 Thread TJ
** 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 in bluez package in Ubuntu:
  Triaged

Bug description:
  $ 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 
  Sep 03 19:39:12 hephaestion.lan.iam.tj bluetoothd[3973]: 
src/adapter.c:adapter_service_add() /org/bluez/hci0

  $ 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
  [NEW] Device 00:19:15:29:83:14 Think Outside Keyboard
  [bluetooth]# list
  Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1491988/+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 1491988] Re: 15.10: Multiple Bluetooth controllers not found

2015-09-09 Thread TJ
This looks to be a kernel issue in
net/bluetooth/mgmt.c::read_index_list().  rp->num_controllers, etc., is
set as hci_dev_list is iterated over. Some devices are not added due to
test flags or quirk bits.

I'll check how 'hcitool dev' gathers its list of adapters.

** Changed in: bluez (Ubuntu)
   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)
   Status: New => In Progress

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

** 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 bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1491988

Title:
  15.10: Multiple Bluetooth controllers not found

Status in bluez package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  $ 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 
  Sep 03 19:39:12 hephaestion.lan.iam.tj bluetoothd[3973]: 
src/adapter.c:adapter_service_add() /org/bluez/hci0

  $ 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
  [NEW] Device 00:19:15:29:83:14 Think Outside Keyboard
  [bluetooth]# list
  Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1491988/+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 1318111] Re: Adds more and more copies of ‘crashkernel=384M-:128M’ in /etc/default/grub when upgrading or reinstalling grub-pc

2015-11-22 Thread TJ
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 received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1318111

Title:
  Adds more and more copies of ‘crashkernel=384M-:128M’ in
  /etc/default/grub when upgrading or reinstalling grub-pc

Status in kexec-tools package in Ubuntu:
  Confirmed

Bug description:
  # grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash crashkernel=384M-:128M"
  # apt-get install --reinstall grub-pc
  …
  # grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash crashkernel=384M-:128M 
crashkernel=384M-:128M"
  # apt-get install --reinstall grub-pc
  …
  # grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M"
  # apt-get install --reinstall grub-pc
  …
  # grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M"

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: kexec-tools 1:2.0.6-0ubuntu2
  Uname: Linux 3.15.0-031500rc4-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.14.2-0ubuntu2
  Architecture: amd64
  Date: Fri May  9 22:39:32 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-12-05 (1251 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202)
  SourcePackage: kexec-tools
  UpgradeStatus: Upgraded to utopic on 2013-10-31 (190 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1318111/+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 1488719] Re: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!"

2016-01-24 Thread TJ
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 in Ubuntu.
https://bugs.launchpad.net/bugs/1488719

Title:
  dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control
  interrupt lied (SDE)!"

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a recent intel NUC using i915 graphics, I get the following errors
  in dmesg:

  [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt
  lied (SDE)!

  There are two monitors connected to this box, one with mini-
  HDMI->HDMI, one with mini-DP->HDMI cable.

  Maybe related:

  https://bugs.freedesktop.org/show_bug.cgi?id=80896

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-generic 3.19.0.26.25
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  Date: Wed Aug 26 10:07:31 2015
  InstallationDate: Installed on 2015-08-01 (24 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-26-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1488719/+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 1259861] Re: 5-10 second delay in kernel boot with kernel command line ip=

2016-03-20 Thread TJ
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 Whitcroft 


$ git show 301b4bb | awk '/^\+\+\+/{FILE=$0} /^[-+]CONFIG_IP_PNP=/ {print FILE; 
print}'
+++ b/debian.master/config/config.common.ubuntu
+CONFIG_IP_PNP=y

-- 
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 kernel boot with kernel command line ip=

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Wily:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  In Trusty I see a big delay while the kernel boots that I did not see back in 
Precise.
  Some people have been experiencing this in Saucy too, so I don't know exactly 
when it started happening.
  Excerpt from dmesg:
  [3.740100] Switched to clocksource tsc
  [   14.208118] PM: Hibernation image not present or could not be loaded.
  [   14.208885] Freeing unused kernel memory: 864K (c19ac000 - c1a84000)

  The exact messages above don't matter, they are different on different boots 
or on different machines.
  It even happens with e.g. 
  $ sudo kvm -m 768 -cdrom trusty-desktop-i386.iso

  My current kernel is
  Linux server 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:42:09 UTC 2013 i686 
i686 i686 GNU/Linux
  ...but the exact version, maybe from 3.8 to 3.12+, shouldn't matter, just run 
`dmesg` yourself and check if there's a big delay there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259861/+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 1259861] Re: 5-10 second delay in kernel boot

2016-03-19 Thread TJ
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 kernel boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In Trusty I see a big delay while the kernel boots that I did not see back in 
Precise.
  Some people have been experiencing this in Saucy too, so I don't know exactly 
when it started happening.
  Excerpt from dmesg:
  [3.740100] Switched to clocksource tsc
  [   14.208118] PM: Hibernation image not present or could not be loaded.
  [   14.208885] Freeing unused kernel memory: 864K (c19ac000 - c1a84000)

  The exact messages above don't matter, they are different on different boots 
or on different machines.
  It even happens with e.g. 
  $ sudo kvm -m 768 -cdrom trusty-desktop-i386.iso

  My current kernel is
  Linux server 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:42:09 UTC 2013 i686 
i686 i686 GNU/Linux
  ...but the exact version, maybe from 3.8 to 3.12+, shouldn't matter, just run 
`dmesg` yourself and check if there's a big delay there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259861/+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 1490347] Re: [Regresision] 15:10 - Cannot pair with devices using PIN codes

2016-04-24 Thread TJ
In reply to Simon Fels (sorry for the long delay - I put the keyboards
aside to focus on other things).

The "Apple Wireless Keyboard" are model A1016 105-key, including a
numeric keypad.

Issue still affects 16.04.

>From 16.04 attaching a bluetoothd debug log whilst trying to pair with
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 agent request successful
[bluetooth]# scan on
Discovery started
[CHG] Controller 34:02:86:FC:AD:59 Discovering: yes
[NEW] Device 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj
[CHG] Device 00:0A:95:44:37:11 LegacyPairing: yes
[CHG] Device 00:0A:95:44:37:11 RSSI: -43
[bluetooth]# pair 00:0A:95:44:37:11
Attempting to pair with 00:0A:95:44:37:11
[agent] PIN code: 412054
Failed to pair: org.bluez.Error.ConnectionAttemptFailed
[CHG] Device 00:1F:3A:E0:0A:AF RSSI: -66

Notice that the "[agent] PIN code: 412054" message doesn't appear until
I press the A1016 keyboard's Enter key once. I then type the prompted
PIN followed by Enter on the A1016 keyboard.

Sometimes I get three prompts to enter PIN codes (each PIN different)
before it fails.

** Attachment added: "bluetoothd debug log trying to pair A1016"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490347/+attachment/4645819/+files/bluetoothd-debug-A1016-pair-attempt.log

** Summary changed:

- [Regresision] 15:10 - Cannot pair with devices using PIN codes
+ [Regresision] 16:04 + 15:10 - Cannot pair with devices using (Legacy) PIN 
codes

-- 
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] 16:04 + 15:10 - Cannot pair with devices using (Legacy)
  PIN codes

Status in Bluez Utilities:
  New
Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Wily:
  Triaged

Bug description:
  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
  (that statement dated April 2013) but I've not yet identified them.

  "The agent's implementation in bt_console/bluetoothctl upstream is
  incomplete, missing some functions like DisplayPincode."

  https://code.google.com/p/chromium/issues/detail?id=222661

  Along with the loss of Headset profiles meaning VoIP applications can
  no longer use HSP/HFP profiles (requiring functionality yet to land in
  Ofono) this cripples the use of Bluetooth for much else than A2DP or
  mouse input.

  Attempting to pair with, for example, an Apple Wireless Keyboard that
  pairs and works correctly with 14.04 LTS, fails totally on 15.10.

  The mouse shown below is already paired, connected, and working.

  $ 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]# agent on
  Agent registered
  [bluetooth]# default-agent
  Default agent request successful
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller 00:1F:3A:E0:0A:AF Discovering: yes
  [CHG] Device 00:0A:95:4B:BD:C2 LegacyPairing: yes
  [CHG] Device 00:0A:95:4B:BD:C2 RSSI: -48
  [bluetooth]# pair 00:0A:95:4B:BD:C2
  Attempting to pair with 00:0A:95:4B:BD:C2

  >>> at this point nothing is happening

  >>> so I press Enter on the keyboard and...
  [agent] PIN code: 791166
  >>> I type 791166 Enter and ...
  [agent] PIN code: 237744
  >>> I type 237744 Enter and...
  [agent] PIN code: 358866
  >>> I type 358866 Enter and...
  Request PIN code
  [agent] Enter PIN code: 1234
  >>> I type 1234 Enter on the keyboard and 1234 at the prompt...
  Failed to pair: org.bluez.Error.AuthenticationFailed

  This cycle repeats in various permuations. Sometimes the final
  "Request PIN code" does not appear.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1490347/+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 1576571] Re: S3 suspend resume cycle every 30 minutes

2016-04-29 Thread TJ
** 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.
https://bugs.launchpad.net/bugs/1576571

Title:
  S3 suspend resume cycle every 30 minutes

Status in linux package in Ubuntu:
  New

Bug description:
  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 logs and noticed that
  overnight the PC appears to have been in a cycle of suspend/resume
  every 30 minutes until around 06:49 when it wrote a hibernation image,
  suspended, woke, and ran out of power.

  Due to the timestamps in kern.log not being accurate (some resume
  messages are timestamped with the suspend time until the system clock
  is corrected) its proving hard to understand the precise sequence of
  events, and even whether the PC truly did go into S3 suspend.

  The battery was fully charged before the PC was commanded to suspend
  and when running idle should last ~6 hours or more.

  I wondered about some ACPI interrupts waking it up but it has very few
  devices that might do that. It has a single USB3 port and no device
  was connected. It only has an iwlwifi PCI network device (no wired
  Ethernet). ethtool indicates there is no WoL for the WiFi  adapter. It
  only has a Bluetooth connected keyboard so there is no possibility of
  a keyboard wakeup.

  It has a touchscreen digitizer but nothing entered the room during the
  night an there are no secret stray cats, or mice!

  It does have IIO sensors for ambient light and accelerometer but there
  is currently no software accessing them although the kernel drivers
  are loaded.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576571/+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 1576571] Re: S3 suspend resume cycle every 30 minutes

2016-04-29 Thread TJ
** 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

Title:
  S3 suspend resume cycle every 30 minutes

Status in linux package in Ubuntu:
  New

Bug description:
  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 logs and noticed that
  overnight the PC appears to have been in a cycle of suspend/resume
  every 30 minutes until around 06:49 when it wrote a hibernation image,
  suspended, woke, and ran out of power.

  Due to the timestamps in kern.log not being accurate (some resume
  messages are timestamped with the suspend time until the system clock
  is corrected) its proving hard to understand the precise sequence of
  events, and even whether the PC truly did go into S3 suspend.

  The battery was fully charged before the PC was commanded to suspend
  and when running idle should last ~6 hours or more.

  I wondered about some ACPI interrupts waking it up but it has very few
  devices that might do that. It has a single USB3 port and no device
  was connected. It only has an iwlwifi PCI network device (no wired
  Ethernet). ethtool indicates there is no WoL for the WiFi  adapter. It
  only has a Bluetooth connected keyboard so there is no possibility of
  a keyboard wakeup.

  It has a touchscreen digitizer but nothing entered the room during the
  night an there are no secret stray cats, or mice!

  It does have IIO sensors for ambient light and accelerometer but there
  is currently no software accessing them although the kernel drivers
  are loaded.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576571/+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 1576571] [NEW] S3 suspend resume cycle every 30 minutes

2016-04-29 Thread TJ
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 logs and noticed that
overnight the PC appears to have been in a cycle of suspend/resume every
30 minutes until around 06:49 when it wrote a hibernation image,
suspended, woke, and ran out of power.

Due to the timestamps in kern.log not being accurate (some resume
messages are timestamped with the suspend time until the system clock is
corrected) its proving hard to understand the precise sequence of
events, and even whether the PC truly did go into S3 suspend.

The battery was fully charged before the PC was commanded to suspend and
when running idle should last ~6 hours or more.

I wondered about some ACPI interrupts waking it up but it has very few
devices that might do that. It has a single USB3 port and no device was
connected. It only has an iwlwifi PCI network device (no wired
Ethernet). ethtool indicates there is no WoL for the WiFi  adapter. It
only has a Bluetooth connected keyboard so there is no possibility of a
keyboard wakeup.

It has a touchscreen digitizer but nothing entered the room during the
night an there are no secret stray cats, or mice!

It does have IIO sensors for ambient light and accelerometer but there
is currently no software accessing them although the kernel drivers are
loaded.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "kern.log starting from a cold boot just before commanded 
suspend"
   https://bugs.launchpad.net/bugs/1576571/+attachment/4651152/+files/kern.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

Title:
  S3 suspend resume cycle every 30 minutes

Status in linux package in Ubuntu:
  New

Bug description:
  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 logs and noticed that
  overnight the PC appears to have been in a cycle of suspend/resume
  every 30 minutes until around 06:49 when it wrote a hibernation image,
  suspended, woke, and ran out of power.

  Due to the timestamps in kern.log not being accurate (some resume
  messages are timestamped with the suspend time until the system clock
  is corrected) its proving hard to understand the precise sequence of
  events, and even whether the PC truly did go into S3 suspend.

  The battery was fully charged before the PC was commanded to suspend
  and when running idle should last ~6 hours or more.

  I wondered about some ACPI interrupts waking it up but it has very few
  devices that might do that. It has a single USB3 port and no device
  was connected. It only has an iwlwifi PCI network device (no wired
  Ethernet). ethtool indicates there is no WoL for the WiFi  adapter. It
  only has a Bluetooth connected keyboard so there is no possibility of
  a keyboard wakeup.

  It has a touchscreen digitizer but nothing entered the room during the
  night an there are no secret stray cats, or mice!

  It does have IIO sensors for ambient light and accelerometer but there
  is currently no software accessing them although the kernel drivers
  are loaded.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576571/+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 1576571] Re: S3 suspend resume cycle every 30 minutes

2016-04-29 Thread TJ
$ 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  S4*disabled
RP04  S4*disabled  pci::00:1c.3
RP05  S4*disabled
RP06  S4*disabled
RP07  S4*disabled
RP08  S4*disabled
GLAN  S4*disabled
EHC1  S3*disabled
EHC2  S3*disabled
XHC   S3*enabled   pci::00:14.0
HDEF  S4*disabled  pci::00:1b.0
SLPB  S4*enabled   platform:PNP0C0E:00

-- 
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

Title:
  S3 suspend resume cycle every 30 minutes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  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 logs and noticed that
  overnight the PC appears to have been in a cycle of suspend/resume
  every 30 minutes until around 06:49 when it wrote a hibernation image,
  suspended, woke, and ran out of power.

  Due to the timestamps in kern.log not being accurate (some resume
  messages are timestamped with the suspend time until the system clock
  is corrected) its proving hard to understand the precise sequence of
  events, and even whether the PC truly did go into S3 suspend.

  The battery was fully charged before the PC was commanded to suspend
  and when running idle should last ~6 hours or more.

  I wondered about some ACPI interrupts waking it up but it has very few
  devices that might do that. It has a single USB3 port and no device
  was connected. It only has an iwlwifi PCI network device (no wired
  Ethernet). ethtool indicates there is no WoL for the WiFi  adapter. It
  only has a Bluetooth connected keyboard so there is no possibility of
  a keyboard wakeup.

  It has a touchscreen digitizer but nothing entered the room during the
  night an there are no secret stray cats, or mice!

  It does have IIO sensors for ambient light and accelerometer but there
  is currently no software accessing them although the kernel drivers
  are loaded.

  $ grep -Ea 'PM: (Prepar|Finish)' kern.log
  Apr 28 21:36:54 T300CHI kernel: [82469.274147] PM: Preparing system for sleep 
(mem)
  Apr 28 21:36:54 T300CHI kernel: [82471.096890] PM: Finishing wakeup.
  Apr 28 21:37:31 T300CHI kernel: [82507.808915] PM: Preparing system for sleep 
(mem)
  Apr 28 21:37:35 T300CHI kernel: [82509.203304] PM: Finishing wakeup.
  Apr 28 22:07:45 T300CHI kernel: [84319.706320] PM: Preparing system for sleep 
(mem)
  Apr 28 22:07:49 T300CHI kernel: [84321.104263] PM: Finishing wakeup.
  Apr 28 22:38:01 T300CHI kernel: [86131.634214] PM: Preparing system for sleep 
(mem)
  Apr 28 22:38:04 T300CHI kernel: [86133.021188] PM: Finishing wakeup.
  Apr 28 23:08:19 T300CHI kernel: [87943.507350] PM: Preparing system for sleep 
(mem)
  Apr 28 23:08:19 T300CHI kernel: [87944.923894] PM: Finishing wakeup.
  Apr 28 23:38:34 T300CHI kernel: [89755.366961] PM: Preparing system for sleep 
(mem)
  Apr 28 23:38:34 T300CHI kernel: [89756.786890] PM: Finishing wakeup.
  Apr 29 00:08:48 T300CHI kernel: [91567.020044] PM: Preparing system for sleep 
(mem)
  Apr 29 00:08:48 T300CHI kernel: [91568.436456] PM: Finishing wakeup.
  Apr 29 00:38:59 T300CHI kernel: [93378.844871] PM: Preparing system for sleep 
(mem)
  Apr 29 00:39:03 T300CHI kernel: [93380.256574] PM: Finishing wakeup.
  Apr 29 01:09:13 T300CHI kernel: [95190.641618] PM: Preparing system for sleep 
(mem)
  Apr 29 01:09:17 T300CHI kernel: [95192.030272] PM: Finishing wakeup.
  Apr 29 01:39:28 T300CHI kernel: [97002.442841] PM: Preparing system for sleep 
(mem)
  Apr 29 01:39:32 T300CHI kernel: [97003.826499] PM: Finishing wakeup.
  Apr 29 02:09:42 T300CHI kernel: [98814.281002] PM: Preparing system for sleep 
(mem)
  Apr 29 02:09:46 T300CHI kernel: [98815.670863] PM: Finishing wakeup.
  Apr 29 02:40:01 T300CHI kernel: [100626.106115] PM: Preparing system for 
sleep (mem)
  Apr 29 02:40:01 T300CHI kernel: [100627.499669] PM: Finishing wakeup.
  Apr 29 03:10:11 T300CHI kernel: [102437.773451] PM: Preparing system for 
sleep (mem)
  Apr 29 03:10:15 T300CHI kernel: [102439.159921] PM: Finishing wakeup.
  Apr 29 03:40:30 T300CHI kernel: [104249.563211] PM: Preparing system for 
sleep (mem)
  Apr 29 03:40:30 T300CHI kernel: [104250.977264] PM: Finishing wakeup.
  Apr 29 04:10:44 T300CHI kernel: [106061.409233] PM: Preparing system for 
sleep (mem)
  Apr 29 04:10:44 T300CHI kernel: [106062.798963] PM: Finishing wakeup.
  Apr 29 04:40:59 T300CHI kernel: [107873.214783] PM: 

[Kernel-packages] [Bug 1576571] Re: S3 suspend resume cycle every 30 minutes

2016-04-29 Thread TJ
** 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"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576571/+attachment/4651162/+files/kern.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

Title:
  S3 suspend resume cycle every 30 minutes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  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 logs and noticed that
  overnight the PC appears to have been in a cycle of suspend/resume
  every 30 minutes until around 06:49 when it wrote a hibernation image,
  suspended, woke, and ran out of power.

  Due to the timestamps in kern.log not being accurate (some resume
  messages are timestamped with the suspend time until the system clock
  is corrected) its proving hard to understand the precise sequence of
  events, and even whether the PC truly did go into S3 suspend.

  The battery was fully charged before the PC was commanded to suspend
  and when running idle should last ~6 hours or more.

  I wondered about some ACPI interrupts waking it up but it has very few
  devices that might do that. It has a single USB3 port and no device
  was connected. It only has an iwlwifi PCI network device (no wired
  Ethernet). ethtool indicates there is no WoL for the WiFi  adapter. It
  only has a Bluetooth connected keyboard so there is no possibility of
  a keyboard wakeup.

  It has a touchscreen digitizer but nothing entered the room during the
  night an there are no secret stray cats, or mice!

  It does have IIO sensors for ambient light and accelerometer but there
  is currently no software accessing them although the kernel drivers
  are loaded.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576571/+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 1576571] Re: S3 suspend resume cycle every 30 minutes

2016-04-29 Thread TJ
** 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 investigated the logs and noticed that
  overnight the PC appears to have been in a cycle of suspend/resume every
  30 minutes until around 06:49 when it wrote a hibernation image,
  suspended, woke, and ran out of power.
  
  Due to the timestamps in kern.log not being accurate (some resume
  messages are timestamped with the suspend time until the system clock is
  corrected) its proving hard to understand the precise sequence of
  events, and even whether the PC truly did go into S3 suspend.
  
  The battery was fully charged before the PC was commanded to suspend and
  when running idle should last ~6 hours or more.
  
  I wondered about some ACPI interrupts waking it up but it has very few
  devices that might do that. It has a single USB3 port and no device was
  connected. It only has an iwlwifi PCI network device (no wired
  Ethernet). ethtool indicates there is no WoL for the WiFi  adapter. It
  only has a Bluetooth connected keyboard so there is no possibility of a
  keyboard wakeup.
  
  It has a touchscreen digitizer but nothing entered the room during the
  night an there are no secret stray cats, or mice!
  
  It does have IIO sensors for ambient light and accelerometer but there
  is currently no software accessing them although the kernel drivers are
  loaded.
+ 
+ $ grep -Ea 'PM: (Prepar|Finish)' kern.log
+ Apr 28 21:36:54 T300CHI kernel: [82469.274147] PM: Preparing system for sleep 
(mem)
+ Apr 28 21:36:54 T300CHI kernel: [82471.096890] PM: Finishing wakeup.
+ Apr 28 21:37:31 T300CHI kernel: [82507.808915] PM: Preparing system for sleep 
(mem)
+ Apr 28 21:37:35 T300CHI kernel: [82509.203304] PM: Finishing wakeup.
+ Apr 28 22:07:45 T300CHI kernel: [84319.706320] PM: Preparing system for sleep 
(mem)
+ Apr 28 22:07:49 T300CHI kernel: [84321.104263] PM: Finishing wakeup.
+ Apr 28 22:38:01 T300CHI kernel: [86131.634214] PM: Preparing system for sleep 
(mem)
+ Apr 28 22:38:04 T300CHI kernel: [86133.021188] PM: Finishing wakeup.
+ Apr 28 23:08:19 T300CHI kernel: [87943.507350] PM: Preparing system for sleep 
(mem)
+ Apr 28 23:08:19 T300CHI kernel: [87944.923894] PM: Finishing wakeup.
+ Apr 28 23:38:34 T300CHI kernel: [89755.366961] PM: Preparing system for sleep 
(mem)
+ Apr 28 23:38:34 T300CHI kernel: [89756.786890] PM: Finishing wakeup.
+ Apr 29 00:08:48 T300CHI kernel: [91567.020044] PM: Preparing system for sleep 
(mem)
+ Apr 29 00:08:48 T300CHI kernel: [91568.436456] PM: Finishing wakeup.
+ Apr 29 00:38:59 T300CHI kernel: [93378.844871] PM: Preparing system for sleep 
(mem)
+ Apr 29 00:39:03 T300CHI kernel: [93380.256574] PM: Finishing wakeup.
+ Apr 29 01:09:13 T300CHI kernel: [95190.641618] PM: Preparing system for sleep 
(mem)
+ Apr 29 01:09:17 T300CHI kernel: [95192.030272] PM: Finishing wakeup.
+ Apr 29 01:39:28 T300CHI kernel: [97002.442841] PM: Preparing system for sleep 
(mem)
+ Apr 29 01:39:32 T300CHI kernel: [97003.826499] PM: Finishing wakeup.
+ Apr 29 02:09:42 T300CHI kernel: [98814.281002] PM: Preparing system for sleep 
(mem)
+ Apr 29 02:09:46 T300CHI kernel: [98815.670863] PM: Finishing wakeup.
+ Apr 29 02:40:01 T300CHI kernel: [100626.106115] PM: Preparing system for 
sleep (mem)
+ Apr 29 02:40:01 T300CHI kernel: [100627.499669] PM: Finishing wakeup.
+ Apr 29 03:10:11 T300CHI kernel: [102437.773451] PM: Preparing system for 
sleep (mem)
+ Apr 29 03:10:15 T300CHI kernel: [102439.159921] PM: Finishing wakeup.
+ Apr 29 03:40:30 T300CHI kernel: [104249.563211] PM: Preparing system for 
sleep (mem)
+ Apr 29 03:40:30 T300CHI kernel: [104250.977264] PM: Finishing wakeup.
+ Apr 29 04:10:44 T300CHI kernel: [106061.409233] PM: Preparing system for 
sleep (mem)
+ Apr 29 04:10:44 T300CHI kernel: [106062.798963] PM: Finishing wakeup.
+ Apr 29 04:40:59 T300CHI kernel: [107873.214783] PM: Preparing system for 
sleep (mem)
+ Apr 29 04:40:59 T300CHI kernel: [107874.612422] PM: Finishing wakeup.
+ Apr 29 05:11:09 T300CHI kernel: [109684.937138] PM: Preparing system for 
sleep (mem)
+ Apr 29 05:11:13 T300CHI kernel: [109686.330386] PM: Finishing wakeup.
+ Apr 29 05:41:28 T300CHI kernel: [111496.747318] PM: Preparing system for 
sleep (mem)
+ Apr 29 05:41:28 T300CHI kernel: [111498.140735] PM: Finishing wakeup.
+ Apr 29 06:11:29 T300CHI kernel: [113298.690266] PM: Preparing system for 
sleep (mem)
+ Apr 29 06:11:33 T300CHI kernel: [113300.102234] PM: Finishing wakeup.
+ Apr 29 06:41:34 T300CHI kernel: [115101.410436] PM: Preparing system for 
sleep (mem)
+ Apr 29 06:41:38 T300CHI kernel: [115102.820245] PM: Finishing wakeup.

-- 
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

Title:
  S3 

[Kernel-packages] [Bug 1576571] Re: S3 suspend resume cycle every 30 minutes

2016-04-29 Thread TJ
>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 systemd[11323]: systemd-suspend.service: Executing: 
/lib/systemd/systemd-sleep suspend
Apr 28 21:37:30 T300CHI systemd[11750]: systemd-suspend.service: Executing: 
/lib/systemd/systemd-sleep suspend
Apr 28 22:07:35 T300CHI systemd[12199]: systemd-suspend.service: Executing: 
/lib/systemd/systemd-sleep suspend
Apr 28 22:37:51 T300CHI systemd[12720]: systemd-suspend.service: Executing: 
/lib/systemd/systemd-sleep suspend
Apr 28 23:08:05 T300CHI systemd[13231]: systemd-suspend.service: Executing: 
/lib/systemd/systemd-sleep suspend
Apr 28 23:38:20 T300CHI systemd[13738]: systemd-suspend.service: Executing: 
/lib/systemd/systemd-sleep suspend
Apr 29 00:08:34 T300CHI systemd[14250]: systemd-suspend.service: Executing: 
/lib/systemd/systemd-sleep suspend
Apr 29 00:38:49 T300CHI systemd[14760]: systemd-suspend.service: Executing: 
/lib/systemd/systemd-sleep suspend
Apr 29 01:09:03 T300CHI systemd[15271]: systemd-suspend.service: Executing: 
/lib/systemd/systemd-sleep suspend
Apr 29 01:39:18 T300CHI systemd[15778]: systemd-suspend.service: Executing: 
/lib/systemd/systemd-sleep suspend
Apr 29 02:09:32 T300CHI systemd[16280]: systemd-suspend.service: Executing: 
/lib/systemd/systemd-sleep suspend
Apr 29 02:39:47 T300CHI systemd[16797]: systemd-suspend.service: Executing: 
/lib/systemd/systemd-sleep suspend
Apr 29 03:10:01 T300CHI systemd[17297]: systemd-suspend.service: Executing: 
/lib/systemd/systemd-sleep suspend
Apr 29 03:40:16 T300CHI systemd[17797]: systemd-suspend.service: Executing: 
/lib/systemd/systemd-sleep suspend
Apr 29 04:10:30 T300CHI systemd[18300]: systemd-suspend.service: Executing: 
/lib/systemd/systemd-sleep suspend
Apr 29 04:40:45 T300CHI systemd[18804]: systemd-suspend.service: Executing: 
/lib/systemd/systemd-sleep suspend
Apr 29 05:10:59 T300CHI systemd[19302]: systemd-suspend.service: Executing: 
/lib/systemd/systemd-sleep suspend
Apr 29 05:41:14 T300CHI systemd[19811]: systemd-suspend.service: Executing: 
/lib/systemd/systemd-sleep suspend
Apr 29 06:11:29 T300CHI systemd[20317]: systemd-suspend.service: Executing: 
/lib/systemd/systemd-sleep suspend
Apr 29 06:41:34 T300CHI systemd[20846]: systemd-suspend.service: Executing: 
/lib/systemd/systemd-sleep suspend

-- 
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

Title:
  S3 suspend resume cycle every 30 minutes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  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 logs and noticed that
  overnight the PC appears to have been in a cycle of suspend/resume
  every 30 minutes until around 06:49 when it wrote a hibernation image,
  suspended, woke, and ran out of power.

  Due to the timestamps in kern.log not being accurate (some resume
  messages are timestamped with the suspend time until the system clock
  is corrected) its proving hard to understand the precise sequence of
  events, and even whether the PC truly did go into S3 suspend.

  The battery was fully charged before the PC was commanded to suspend
  and when running idle should last ~6 hours or more.

  I wondered about some ACPI interrupts waking it up but it has very few
  devices that might do that. It has a single USB3 port and no device
  was connected. It only has an iwlwifi PCI network device (no wired
  Ethernet). ethtool indicates there is no WoL for the WiFi  adapter. It
  only has a Bluetooth connected keyboard so there is no possibility of
  a keyboard wakeup.

  It has a touchscreen digitizer but nothing entered the room during the
  night an there are no secret stray cats, or mice!

  It does have IIO sensors for ambient light and accelerometer but there
  is currently no software accessing them although the kernel drivers
  are loaded.

  $ grep -Ea 'PM: (Prepar|Finish)' kern.log
  Apr 28 21:36:54 T300CHI kernel: [82469.274147] PM: Preparing system for sleep 
(mem)
  Apr 28 21:36:54 T300CHI kernel: [82471.096890] PM: Finishing wakeup.
  Apr 28 21:37:31 T300CHI kernel: [82507.808915] PM: Preparing system for sleep 
(mem)
  Apr 28 21:37:35 T300CHI kernel: [82509.203304] PM: Finishing wakeup.
  Apr 28 22:07:45 T300CHI kernel: [84319.706320] PM: Preparing system for sleep 
(mem)
  Apr 28 22:07:49 T300CHI kernel: [84321.104263] PM: Finishing wakeup.
  Apr 28 22:38:01 T300CHI kernel: [86131.634214] PM: Preparing system for sleep 
(mem)
  Apr 28 22:38:04 T300CHI kernel: 

  1   2   3   >