from:"axel"

Running an apt upgrade rather than apt-get upgrade installed the new kernel now.
Just installed on testserver and tried CIFS mounts with a short test.
It seems working now, thanks !
I'll install as soon as possible this kernel on 2 more productive servers and 
try what's happen  
Bye
Axel

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

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released

Bug description:
  Hi,

  updated some Ubuntu 22.04 systems to lastest available state this
  morning, which caused CIFS mounts (from various fileservers) to stop
  working. Kernel was updated to version 5.15.0-102-generic.

  I can mount the shares without problems (mount -t cifs), but then, df for 
example tells me: df: /mnt: Resource temporarily unavailable.
  I'm able to list and browse all the files, but accessing them (even readonly) 
is very unstable. Sometimes it works and sometimes it just gives me i/o errors. 

  Switching back to  5.15.0-101-generic or 5.15.0-100-generic solves the
  problem and everything works again as expected.

  Seems like some bug has been implemented in 5.15.0-102-generic...

  To reproduce the problem, I started a while loop on one server to
  write to some file on a specific mounted CIFS share and read it from
  another one

  root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; 
sleep 1 ; done
  -bash: /mnt/hallo.txt: Input/output error
  -bash: /mnt/hallo.txt: Input/output error
  ^C

  root@:~$ tail -f /mnt/hallo.txt
  Tue Apr  9 04:10:52 PM CEST 2024 hallo
  Tue Apr  9 04:10:53 PM CEST 2024 hallo
  Tue Apr  9 04:10:54 PM CEST 2024 hallo
  Tue Apr  9 04:10:55 PM CEST 2024 hallo
  Tue Apr  9 04:10:56 PM CEST 2024 hallo
  Tue Apr  9 04:10:57 PM CEST 2024 hallo
  Tue Apr  9 04:10:58 PM CEST 2024 hallo
  Tue Apr  9 04:10:59 PM CEST 2024 hallo
  Tue Apr  9 04:11:00 PM CEST 2024 hallo
  Tue Apr  9 04:11:01 PM CEST 2024 hallo
  tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: 
Resource temporarily unavailable
  Tue Apr  9 04:11:04 PM CEST 2024 hallo
  Tue Apr  9 04:11:05 PM CEST 2024 hallo
  Tue Apr  9 04:11:06 PM CEST 2024 hallo
  Tue Apr  9 04:11:07 PM CEST 2024 hallo
  Tue Apr  9 04:11:08 PM CEST 2024 hallo
  Tue Apr  9 04:11:09 PM CEST 2024 hallo
  Tue Apr  9 04:11:10 PM CEST 2024 hallo

  While doing this, both servers tell me, the resource is unavailable

  root@:~# df -h /mnt
  df: /mnt: Resource temporarily unavailable

  root@:~$ df -h /mnt
  df: /mnt: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

Seems apt-upgrade will not download new kernel:
Die folgenden Pakete sind zurückgehalten worden:
  linux-generic linux-headers-generic linux-image-generic 
ubuntu-advantage-tools ubuntu-pro-client-l10n

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

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released

Bug description:
  Hi,

  updated some Ubuntu 22.04 systems to lastest available state this
  morning, which caused CIFS mounts (from various fileservers) to stop
  working. Kernel was updated to version 5.15.0-102-generic.

  I can mount the shares without problems (mount -t cifs), but then, df for 
example tells me: df: /mnt: Resource temporarily unavailable.
  I'm able to list and browse all the files, but accessing them (even readonly) 
is very unstable. Sometimes it works and sometimes it just gives me i/o errors. 

  Switching back to  5.15.0-101-generic or 5.15.0-100-generic solves the
  problem and everything works again as expected.

  Seems like some bug has been implemented in 5.15.0-102-generic...

  To reproduce the problem, I started a while loop on one server to
  write to some file on a specific mounted CIFS share and read it from
  another one

  root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; 
sleep 1 ; done
  -bash: /mnt/hallo.txt: Input/output error
  -bash: /mnt/hallo.txt: Input/output error
  ^C

  root@:~$ tail -f /mnt/hallo.txt
  Tue Apr  9 04:10:52 PM CEST 2024 hallo
  Tue Apr  9 04:10:53 PM CEST 2024 hallo
  Tue Apr  9 04:10:54 PM CEST 2024 hallo
  Tue Apr  9 04:10:55 PM CEST 2024 hallo
  Tue Apr  9 04:10:56 PM CEST 2024 hallo
  Tue Apr  9 04:10:57 PM CEST 2024 hallo
  Tue Apr  9 04:10:58 PM CEST 2024 hallo
  Tue Apr  9 04:10:59 PM CEST 2024 hallo
  Tue Apr  9 04:11:00 PM CEST 2024 hallo
  Tue Apr  9 04:11:01 PM CEST 2024 hallo
  tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: 
Resource temporarily unavailable
  Tue Apr  9 04:11:04 PM CEST 2024 hallo
  Tue Apr  9 04:11:05 PM CEST 2024 hallo
  Tue Apr  9 04:11:06 PM CEST 2024 hallo
  Tue Apr  9 04:11:07 PM CEST 2024 hallo
  Tue Apr  9 04:11:08 PM CEST 2024 hallo
  Tue Apr  9 04:11:09 PM CEST 2024 hallo
  Tue Apr  9 04:11:10 PM CEST 2024 hallo

  While doing this, both servers tell me, the resource is unavailable

  root@:~# df -h /mnt
  df: /mnt: Resource temporarily unavailable

  root@:~$ df -h /mnt
  df: /mnt: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

I'm totally confused now. Last note her says you're wating for confirmation, 
but I got 2 emails telling me, that the fixed kernel has been released now. But 
when I do a apt-get update and apt-get upgrade still 104 will be installed? Did 
I misunderstood something?
Axel

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

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released

Bug description:
  Hi,

  updated some Ubuntu 22.04 systems to lastest available state this
  morning, which caused CIFS mounts (from various fileservers) to stop
  working. Kernel was updated to version 5.15.0-102-generic.

  I can mount the shares without problems (mount -t cifs), but then, df for 
example tells me: df: /mnt: Resource temporarily unavailable.
  I'm able to list and browse all the files, but accessing them (even readonly) 
is very unstable. Sometimes it works and sometimes it just gives me i/o errors. 

  Switching back to  5.15.0-101-generic or 5.15.0-100-generic solves the
  problem and everything works again as expected.

  Seems like some bug has been implemented in 5.15.0-102-generic...

  To reproduce the problem, I started a while loop on one server to
  write to some file on a specific mounted CIFS share and read it from
  another one

  root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; 
sleep 1 ; done
  -bash: /mnt/hallo.txt: Input/output error
  -bash: /mnt/hallo.txt: Input/output error
  ^C

  root@:~$ tail -f /mnt/hallo.txt
  Tue Apr  9 04:10:52 PM CEST 2024 hallo
  Tue Apr  9 04:10:53 PM CEST 2024 hallo
  Tue Apr  9 04:10:54 PM CEST 2024 hallo
  Tue Apr  9 04:10:55 PM CEST 2024 hallo
  Tue Apr  9 04:10:56 PM CEST 2024 hallo
  Tue Apr  9 04:10:57 PM CEST 2024 hallo
  Tue Apr  9 04:10:58 PM CEST 2024 hallo
  Tue Apr  9 04:10:59 PM CEST 2024 hallo
  Tue Apr  9 04:11:00 PM CEST 2024 hallo
  Tue Apr  9 04:11:01 PM CEST 2024 hallo
  tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: 
Resource temporarily unavailable
  Tue Apr  9 04:11:04 PM CEST 2024 hallo
  Tue Apr  9 04:11:05 PM CEST 2024 hallo
  Tue Apr  9 04:11:06 PM CEST 2024 hallo
  Tue Apr  9 04:11:07 PM CEST 2024 hallo
  Tue Apr  9 04:11:08 PM CEST 2024 hallo
  Tue Apr  9 04:11:09 PM CEST 2024 hallo
  Tue Apr  9 04:11:10 PM CEST 2024 hallo

  While doing this, both servers tell me, the resource is unavailable

  root@:~# df -h /mnt
  df: /mnt: Resource temporarily unavailable

  root@:~$ df -h /mnt
  df: /mnt: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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] Antw: [Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

Thanks a lot !
Axel
>>> engaging374 <2060...@bugs.launchpad.net> 19.04.2024 10:16 >>>
@Alex

Well it's officially released now. It's up to you to install the patch.
:-)

I think someone needs to verify the patch as soon as it's in -proposed
state. Without verification it will be dropped from the source code. (
-> no official fix will be provided in -updates.)

Normally it's not the case if multiple users are affected. Someone just
needs to do the verification work.

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/2060780


Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released

Bug description:
  Hi,

  updated some Ubuntu 22.04 systems to lastest available state this
  morning, which caused CIFS mounts (from various fileservers) to stop
  working. Kernel was updated to version 5.15.0-102-generic.

  I can mount the shares without problems (mount -t cifs), but then, df for 
example tells me: df: /mnt: Resource temporarily unavailable.
  I'm able to list and browse all the files, but accessing them (even readonly) 
is very unstable. Sometimes it works and sometimes it just gives me i/o errors. 

  Switching back to  5.15.0-101-generic or 5.15.0-100-generic solves the
  problem and everything works again as expected.

  Seems like some bug has been implemented in 5.15.0-102-generic...

  To reproduce the problem, I started a while loop on one server to
  write to some file on a specific mounted CIFS share and read it from
  another one

  root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; 
sleep 1 ; done
  -bash: /mnt/hallo.txt: Input/output error
  -bash: /mnt/hallo.txt: Input/output error
  ^C

  root@:~$ tail -f /mnt/hallo.txt
  Tue Apr  9 04:10:52 PM CEST 2024 hallo
  Tue Apr  9 04:10:53 PM CEST 2024 hallo
  Tue Apr  9 04:10:54 PM CEST 2024 hallo
  Tue Apr  9 04:10:55 PM CEST 2024 hallo
  Tue Apr  9 04:10:56 PM CEST 2024 hallo
  Tue Apr  9 04:10:57 PM CEST 2024 hallo
  Tue Apr  9 04:10:58 PM CEST 2024 hallo
  Tue Apr  9 04:10:59 PM CEST 2024 hallo
  Tue Apr  9 04:11:00 PM CEST 2024 hallo
  Tue Apr  9 04:11:01 PM CEST 2024 hallo
  tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: 
Resource temporarily unavailable
  Tue Apr  9 04:11:04 PM CEST 2024 hallo
  Tue Apr  9 04:11:05 PM CEST 2024 hallo
  Tue Apr  9 04:11:06 PM CEST 2024 hallo
  Tue Apr  9 04:11:07 PM CEST 2024 hallo
  Tue Apr  9 04:11:08 PM CEST 2024 hallo
  Tue Apr  9 04:11:09 PM CEST 2024 hallo
  Tue Apr  9 04:11:10 PM CEST 2024 hallo

  While doing this, both servers tell me, the resource is unavailable

  root@:~# df -h /mnt
  df: /mnt: Resource temporarily unavailable

  root@:~$ df -h /mnt
  df: /mnt: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+subscriptions

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

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released

Bug description:
  Hi,

  updated some Ubuntu 22.04 systems to lastest available state this
  morning, which caused CIFS mounts (from various fileservers) to stop
  working. Kernel was updated to version 5.15.0-102-generic.

  I can mount the shares without problems (mount -t cifs), but then, df for 
example tells me: df: /mnt: Resource temporarily unavailable.
  I'm able to list and browse all the files, but accessing them (even readonly) 
is very unstable. Sometimes it works and sometimes it just gives me i/o errors. 

  Switching back to  5.15.0-101-generic or 5.15.0-100-generic solves the
  problem and everything works again as expected.

  Seems like some bug has been implemented in 5.15.0-102-generic...

  To reproduce the problem, I started a while loop on one server to
  write to some file on a specific mounted CIFS share and read it from
  another one

  root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; 
sleep 1 ; done
  -bash: /mnt/hallo.txt: Input/output error
  -bash: /mnt/hallo.txt: Input/output error
  ^C

  root@:~$ tail -f /mnt/hallo.txt
  Tue Apr  9 04:10:52 PM CEST 2024 hallo
  Tue Apr  9 04:10:53 PM CEST 2024 hallo
  Tue Apr  9 04:10:54 PM CEST 2024 hallo
  Tue Apr  9 04:10:55 PM CEST 2024 hallo
  Tue Apr  9 04:10:56 PM CEST 2024 hallo
  Tue Apr  9 04:10:57 PM CEST 2024 hallo
  Tue Apr  9 04:10:58 PM CEST 2024 hallo
  Tue Apr  9 04:10:59 PM CEST 2024 hallo
  Tue Apr  9 04:11:00 PM CEST 2024 hallo
  Tue Apr  9 04:11:01 PM CEST 2024 hallo
  tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: 
Resource tempo

[Kernel-packages] [Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

This bug was the first time I came into this forum, so sorry if this a dumb 
question:
today I got 3 emails that that a fix might be available and I have to test it. 
If I do nbot the fix will be removed from kernel?
Really? Is it really needed that I do some tests after so many already did? 
Currently I'm out of office so it's complicated to test anything.
As far as I understand it is already fixed and 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/2060780

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released

Bug description:
  Hi,

  updated some Ubuntu 22.04 systems to lastest available state this
  morning, which caused CIFS mounts (from various fileservers) to stop
  working. Kernel was updated to version 5.15.0-102-generic.

  I can mount the shares without problems (mount -t cifs), but then, df for 
example tells me: df: /mnt: Resource temporarily unavailable.
  I'm able to list and browse all the files, but accessing them (even readonly) 
is very unstable. Sometimes it works and sometimes it just gives me i/o errors. 

  Switching back to  5.15.0-101-generic or 5.15.0-100-generic solves the
  problem and everything works again as expected.

  Seems like some bug has been implemented in 5.15.0-102-generic...

  To reproduce the problem, I started a while loop on one server to
  write to some file on a specific mounted CIFS share and read it from
  another one

  root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; 
sleep 1 ; done
  -bash: /mnt/hallo.txt: Input/output error
  -bash: /mnt/hallo.txt: Input/output error
  ^C

  root@:~$ tail -f /mnt/hallo.txt
  Tue Apr  9 04:10:52 PM CEST 2024 hallo
  Tue Apr  9 04:10:53 PM CEST 2024 hallo
  Tue Apr  9 04:10:54 PM CEST 2024 hallo
  Tue Apr  9 04:10:55 PM CEST 2024 hallo
  Tue Apr  9 04:10:56 PM CEST 2024 hallo
  Tue Apr  9 04:10:57 PM CEST 2024 hallo
  Tue Apr  9 04:10:58 PM CEST 2024 hallo
  Tue Apr  9 04:10:59 PM CEST 2024 hallo
  Tue Apr  9 04:11:00 PM CEST 2024 hallo
  Tue Apr  9 04:11:01 PM CEST 2024 hallo
  tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: 
Resource temporarily unavailable
  Tue Apr  9 04:11:04 PM CEST 2024 hallo
  Tue Apr  9 04:11:05 PM CEST 2024 hallo
  Tue Apr  9 04:11:06 PM CEST 2024 hallo
  Tue Apr  9 04:11:07 PM CEST 2024 hallo
  Tue Apr  9 04:11:08 PM CEST 2024 hallo
  Tue Apr  9 04:11:09 PM CEST 2024 hallo
  Tue Apr  9 04:11:10 PM CEST 2024 hallo

  While doing this, both servers tell me, the resource is unavailable

  root@:~# df -h /mnt
  df: /mnt: Resource temporarily unavailable

  root@:~$ df -h /mnt
  df: /mnt: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

2024-04-11 Thread Axel Schneck

Hello,

I just tested your suggestion wit 104
It's working here with this kernel
Dont understand why you will still provide a faulty kernel until end of month?
We have a lot of servers here using CIFS mounts and we have to prevent all of 
them now from getting a faulty kernel.
bye
Axel

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

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  Hi,

  updated some Ubuntu 22.04 systems to lastest available state this
  morning, which caused CIFS mounts (from various fileservers) to stop
  working. Kernel was updated to version 5.15.0-102-generic.

  I can mount the shares without problems (mount -t cifs), but then, df for 
example tells me: df: /mnt: Resource temporarily unavailable.
  I'm able to list and browse all the files, but accessing them (even readonly) 
is very unstable. Sometimes it works and sometimes it just gives me i/o errors. 

  Switching back to  5.15.0-101-generic or 5.15.0-100-generic solves the
  problem and everything works again as expected.

  Seems like some bug has been implemented in 5.15.0-102-generic...

  To reproduce the problem, I started a while loop on one server to
  write to some file on a specific mounted CIFS share and read it from
  another one

  root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; 
sleep 1 ; done
  -bash: /mnt/hallo.txt: Input/output error
  -bash: /mnt/hallo.txt: Input/output error
  ^C

  root@:~$ tail -f /mnt/hallo.txt
  Tue Apr  9 04:10:52 PM CEST 2024 hallo
  Tue Apr  9 04:10:53 PM CEST 2024 hallo
  Tue Apr  9 04:10:54 PM CEST 2024 hallo
  Tue Apr  9 04:10:55 PM CEST 2024 hallo
  Tue Apr  9 04:10:56 PM CEST 2024 hallo
  Tue Apr  9 04:10:57 PM CEST 2024 hallo
  Tue Apr  9 04:10:58 PM CEST 2024 hallo
  Tue Apr  9 04:10:59 PM CEST 2024 hallo
  Tue Apr  9 04:11:00 PM CEST 2024 hallo
  Tue Apr  9 04:11:01 PM CEST 2024 hallo
  tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: 
Resource temporarily unavailable
  Tue Apr  9 04:11:04 PM CEST 2024 hallo
  Tue Apr  9 04:11:05 PM CEST 2024 hallo
  Tue Apr  9 04:11:06 PM CEST 2024 hallo
  Tue Apr  9 04:11:07 PM CEST 2024 hallo
  Tue Apr  9 04:11:08 PM CEST 2024 hallo
  Tue Apr  9 04:11:09 PM CEST 2024 hallo
  Tue Apr  9 04:11:10 PM CEST 2024 hallo

  While doing this, both servers tell me, the resource is unavailable

  root@:~# df -h /mnt
  df: /mnt: Resource temporarily unavailable

  root@:~$ df -h /mnt
  df: /mnt: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

2024-04-10 Thread Axel Schneck

Same problems here. Get error messages like "Too many symlinks" and exactly the 
same as in this description. 
Found also, that CIFS mounts to Netapp mostly works, but df -h doesnt show them 
and mounts to other CIFS shares doesnt work.
Verified it on 5 Linux Boxes, all started failing after patch and working again 
when go back to snapshot from yesterday (before kernel patch): These patches 
are he "bad ones":

Start-Date: 2024-04-09  06:21:54
Commandline: /usr/bin/unattended-upgrade
Install: linux-image-5.15.0-102-generic:amd64 (5.15.0-102.112, automatic), 
linux-modules-5.15.0-102-generic:amd64 (5.15.0-102.112, automatic), 
linux-headers-5.15.0-102:amd64 (5.15.0-102.112, automatic), 
linux-modules-extra-5.15.0-102-generic:amd64 (5.15.0-102.112, automatic), 
linux-headers-5.15.0-102-generic:amd64 (5.15.0-102.112, automatic)
Upgrade: linux-headers-generic:amd64 (5.15.0.101.98, 5.15.0.102.99), 
linux-generic:amd64 (5.15.0.101.98, 5.15.0.102.99), linux-image-generic:amd64 
(5.15.0.101.98, 5.15.0.102.99)
End-Date: 2024-04-09  06:22:23

Start-Date: 2024-04-09  06:22:26
Commandline: /usr/bin/unattended-upgrade
Remove: linux-modules-5.15.0-101-generic:amd64 (5.15.0-101.111), 
linux-modules-extra-5.15.0-101-generic:amd64 (5.15.0-101.111), 
linux-image-5.15.0-101-generic:amd64 (5.15.0-101.111)
End-Date: 2024-04-09  06:22:30

Start-Date: 2024-04-09  06:22:33
Commandline: /usr/bin/unattended-upgrade
Remove: linux-headers-5.15.0-101-generic:amd64 (5.15.0-101.111)
End-Date: 2024-04-09  06:22:34

Start-Date: 2024-04-09  06:22:36
Commandline: /usr/bin/unattended-upgrade
Remove: linux-headers-5.15.0-101:amd64 (5.15.0-101.111)
End-Date: 2024-04-09  06:22:37

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

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,

  updated some Ubuntu 22.04 systems to lastest available state this
  morning, which caused CIFS mounts (from various fileservers) to stop
  working. Kernel was updated to version 5.15.0-102-generic.

  I can mount the shares without problems (mount -t cifs), but then, df for 
example tells me: df: /mnt: Resource temporarily unavailable.
  I'm able to list and browse all the files, but accessing them (even readonly) 
is very unstable. Sometimes it works and sometimes it just gives me i/o errors. 

  Switching back to  5.15.0-101-generic or 5.15.0-100-generic solves the
  problem and everything works again as expected.

  Seems like some bug has been implemented in 5.15.0-102-generic...

  To reproduce the problem, I started a while loop on one server to
  write to some file on a specific mounted CIFS share and read it from
  another one

  root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; 
sleep 1 ; done
  -bash: /mnt/hallo.txt: Input/output error
  -bash: /mnt/hallo.txt: Input/output error
  ^C

  root@:~$ tail -f /mnt/hallo.txt
  Tue Apr  9 04:10:52 PM CEST 2024 hallo
  Tue Apr  9 04:10:53 PM CEST 2024 hallo
  Tue Apr  9 04:10:54 PM CEST 2024 hallo
  Tue Apr  9 04:10:55 PM CEST 2024 hallo
  Tue Apr  9 04:10:56 PM CEST 2024 hallo
  Tue Apr  9 04:10:57 PM CEST 2024 hallo
  Tue Apr  9 04:10:58 PM CEST 2024 hallo
  Tue Apr  9 04:10:59 PM CEST 2024 hallo
  Tue Apr  9 04:11:00 PM CEST 2024 hallo
  Tue Apr  9 04:11:01 PM CEST 2024 hallo
  tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: 
Resource temporarily unavailable
  Tue Apr  9 04:11:04 PM CEST 2024 hallo
  Tue Apr  9 04:11:05 PM CEST 2024 hallo
  Tue Apr  9 04:11:06 PM CEST 2024 hallo
  Tue Apr  9 04:11:07 PM CEST 2024 hallo
  Tue Apr  9 04:11:08 PM CEST 2024 hallo
  Tue Apr  9 04:11:09 PM CEST 2024 hallo
  Tue Apr  9 04:11:10 PM CEST 2024 hallo

  While doing this, both servers tell me, the resource is unavailable

  root@:~# df -h /mnt
  df: /mnt: Resource temporarily unavailable

  root@:~$ df -h /mnt
  df: /mnt: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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 2056743] [NEW] Keyboard stops working after suspend on Dell XPS 13

2024-03-11 Thread Axel G. Rossberg

Public bug reported:

The problem occurs with the 5.15.0-102 kernel but not with 5.15.0-100.

The issue seems to be identical to the problem reported for 6.7.0 here:
https://bbs.archlinux.org/viewtopic.php?id=292203

On the page linked above is says a patch was submitted 2024-01-26 and
the problem solved 2024-03-04 in linux 6.7.5 or linux-lts 6.6.17.

I'm concerned that this still needs fixing in the 5.xxx kernel branch.

Touchpad does not freeze and mouse-control of windows still works, so
it's different from a bug reported elsewhere.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-102-generic 5.15.0-102.112
ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143
Uname: Linux 5.15.0-100-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  axel   2494 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 11 09:54:23 2024
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
HibernationDevice: RESUME=UUID=461ac6d0-c7ab-4f93-b97d-4d7b3f14f378
InstallationDate: Installed on 2018-08-31 (2018 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai 
 Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9370
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-100-generic 
root=UUID=fb8af021-9abd-4e95-9458-7a78ac12bb46 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-100-generic N/A
 linux-backports-modules-5.15.0-100-generic  N/A
 linux-firmware  20220329.git681281e4-0ubuntu3.29
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/06/2022
dmi.bios.release: 1.21
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.21.0
dmi.board.name: 0W970W
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.21.0:bd07/06/2022:br1.21:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr:sku07E6:
dmi.product.family: XPS
dmi.product.name: XPS 13 9370
dmi.product.sku: 07E6
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2018-09-08T10:23:15.468001

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


** Tags: amd64 apport-bug jammy package-from-proposed

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

Title:
  Keyboard stops working after suspend on Dell XPS 13

Status in linux package in Ubuntu:
  New

Bug description:
  The problem occurs with the 5.15.0-102 kernel but not with 5.15.0-100.

  The issue seems to be identical to the problem reported for 6.7.0
  here: https://bbs.archlinux.org/viewtopic.php?id=292203

  On the page linked above is says a patch was submitted 2024-01-26 and
  the problem solved 2024-03-04 in linux 6.7.5 or linux-lts 6.6.17.

  I'm concerned that this still needs fixing in the 5.xxx kernel branch.

  Touchpad does not freeze and mouse-control of windows still works, so
  it's different from a bug reported elsewhere.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-102-generic 5.15.0-102.112
  ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143
  Uname: Linux 5.15.0-100-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  axel   2494 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 11 09:54:23 2024
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=461ac6d0-c7ab-4f93-b97d-4d7b3f14f378
  InstallationDate: Installed on 2018-08-31 (2018 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp.

[Kernel-packages] [Bug 2043493] Re: Logitech StreamCam driver broken with update

2023-11-14 Thread Axel G. Rossberg

** Attachment added: "Extract of syslog after plugging in Logitech StreamCam"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043493/+attachment/5719317/+files/syslog-extract.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/2043493

Title:
  Logitech StreamCam driver broken with update

Status in linux package in Ubuntu:
  New

Bug description:
  My Logitech StreamCam works with linux-image-5.15.0-88.

  With linux-image-5.15.0-90 it does not work and instead I get the
  syslog messages when plugging in such as that below (a longer extract
  is attached).

  Nov 14 16:02:12 mylaptop kernel: [  482.608545] pci_bus :04: Allocating 
resources
  Nov 14 16:02:12 mylaptop kernel: [  482.608572] pcieport :04:02.0: bridge 
window [mem 0x0010-0x000f 64bit pref] to [bus 39] add_size 20 
add_align 10
  Nov 14 16:02:12 mylaptop kernel: [  482.608584] pcieport :04:02.0: BAR 
15: no space for [mem size 0x0020 64bit pref]
  Nov 14 16:02:12 mylaptop kernel: [  482.608586] pcieport :04:02.0: BAR 
15: failed to assign [mem size 0x0020 64bit pref]
  Nov 14 16:02:12 mylaptop kernel: [  482.608590] pcieport :04:02.0: BAR 
15: no space for [mem size 0x0020 64bit pref]
  Nov 14 16:02:12 mylaptop kernel: [  482.608591] pcieport :04:02.0: BAR 
15: failed to assign [mem size 0x0020 64bit pref]
  Nov 14 16:02:12 mylaptop kernel: [  482.608594] pcieport :00:1c.4: PCI 
bridge to [bus 03-6d]
  Nov 14 16:02:12 mylaptop kernel: [  482.608597] pcieport :00:1c.4:   
bridge window [io  0x2000-0x5fff]
  Nov 14 16:02:12 mylaptop kernel: [  482.608601] pcieport :00:1c.4:   
bridge window [mem 0xac00-0xda0f]
  Nov 14 16:02:12 mylaptop kernel: [  482.608604] pcieport :00:1c.4:   
bridge window [mem 0x6000-0xa9ff 64bit pref]
  Nov 14 16:02:12 mylaptop kernel: [  482.948297] usb 4-2: new SuperSpeed USB 
device number 2 using xhci_hcd
  Nov 14 16:02:12 mylaptop kernel: [  482.972432] usb 4-2: device descriptor 
read/8, error -71

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-90-generic 5.15.0-90.100
  ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131
  Uname: Linux 5.15.0-90-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  axel   2917 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 14 15:57:47 2023
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=461ac6d0-c7ab-4f93-b97d-4d7b3f14f378
  InstallationDate: Installed on 2018-08-31 (1900 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. XPS 13 9370
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic 
root=UUID=fb8af021-9abd-4e95-9458-7a78ac12bb46 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-90-generic N/A
   linux-backports-modules-5.15.0-90-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.22
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2022
  dmi.bios.release: 1.21
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.21.0
  dmi.board.name: 0W970W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.21.0:bd07/06/2022:br1.21:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr:sku07E6:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2018-09-08T10:23:15.468001

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043493/+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 2043493] [NEW] Logitech StreamCam driver broken with update

2023-11-14 Thread Axel G. Rossberg

Public bug reported:

My Logitech StreamCam works with linux-image-5.15.0-88.

With linux-image-5.15.0-90 it does not work and instead I get the syslog
messages when plugging in such as that below (a longer extract is
attached).

Nov 14 16:02:12 mylaptop kernel: [  482.608545] pci_bus :04: Allocating 
resources
Nov 14 16:02:12 mylaptop kernel: [  482.608572] pcieport :04:02.0: bridge 
window [mem 0x0010-0x000f 64bit pref] to [bus 39] add_size 20 
add_align 10
Nov 14 16:02:12 mylaptop kernel: [  482.608584] pcieport :04:02.0: BAR 15: 
no space for [mem size 0x0020 64bit pref]
Nov 14 16:02:12 mylaptop kernel: [  482.608586] pcieport :04:02.0: BAR 15: 
failed to assign [mem size 0x0020 64bit pref]
Nov 14 16:02:12 mylaptop kernel: [  482.608590] pcieport :04:02.0: BAR 15: 
no space for [mem size 0x0020 64bit pref]
Nov 14 16:02:12 mylaptop kernel: [  482.608591] pcieport :04:02.0: BAR 15: 
failed to assign [mem size 0x0020 64bit pref]
Nov 14 16:02:12 mylaptop kernel: [  482.608594] pcieport :00:1c.4: PCI 
bridge to [bus 03-6d]
Nov 14 16:02:12 mylaptop kernel: [  482.608597] pcieport :00:1c.4:   bridge 
window [io  0x2000-0x5fff]
Nov 14 16:02:12 mylaptop kernel: [  482.608601] pcieport :00:1c.4:   bridge 
window [mem 0xac00-0xda0f]
Nov 14 16:02:12 mylaptop kernel: [  482.608604] pcieport :00:1c.4:   bridge 
window [mem 0x6000-0xa9ff 64bit pref]
Nov 14 16:02:12 mylaptop kernel: [  482.948297] usb 4-2: new SuperSpeed USB 
device number 2 using xhci_hcd
Nov 14 16:02:12 mylaptop kernel: [  482.972432] usb 4-2: device descriptor 
read/8, error -71

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-90-generic 5.15.0-90.100
ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131
Uname: Linux 5.15.0-90-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  axel   2917 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 14 15:57:47 2023
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
HibernationDevice: RESUME=UUID=461ac6d0-c7ab-4f93-b97d-4d7b3f14f378
InstallationDate: Installed on 2018-08-31 (1900 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
MachineType: Dell Inc. XPS 13 9370
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic 
root=UUID=fb8af021-9abd-4e95-9458-7a78ac12bb46 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-90-generic N/A
 linux-backports-modules-5.15.0-90-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.22
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/06/2022
dmi.bios.release: 1.21
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.21.0
dmi.board.name: 0W970W
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.21.0:bd07/06/2022:br1.21:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr:sku07E6:
dmi.product.family: XPS
dmi.product.name: XPS 13 9370
dmi.product.sku: 07E6
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2018-09-08T10:23:15.468001

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


** Tags: amd64 apport-bug jammy package-from-proposed

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

Title:
  Logitech StreamCam driver broken with update

Status in linux package in Ubuntu:
  New

Bug description:
  My Logitech StreamCam works with linux-image-5.15.0-88.

  With linux-image-5.15.0-90 it does not work and instead I get the
  syslog messages when plugging in such as that below (a longer extract
  is attached).

  Nov 14 16:02:12 mylaptop kernel: [  482.608545] pci_bus :04: Allocating 
resources
  Nov 14 16:02:12 mylaptop kernel: [  482.608572] pcieport :04:02.0: bridge 
window [mem 0x0010-0x000f 64bit pref] to [bus 39] add_size 20 
add_align 10
  Nov 14 16:02:12 mylaptop kernel: [  482.608584] pcieport :04:02.0: BAR 
15: no space for [mem size 0x0020 64bit pref]
  Nov 14 16:02:12 mylaptop kernel: [  482.608586] pcieport :04:02.0: BAR 
15: failed to assign [mem size 0x0020 64bit pref]
  Nov 14 16:02:12 mylaptop kernel: [  482.608590] pcieport :04:02.0: BAR 
15: no space for

[Kernel-packages] [Bug 2013204] [NEW] Laptop not waking from second suspend

2023-03-29 Thread Axel Ahlin

Public bug reported:

My laptop does not wake up after I've suspended it, except for the first
time. This is incredibly annoying and has just recently been introduced
to my system.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: linux-image-5.19.0-38-generic 5.19.0-38.39
ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17
Uname: Linux 5.19.0-38-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 29 15:05:53 2023
InstallationDate: Installed on 2022-12-30 (88 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: Acer Aspire A515-47
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic 
root=UUID=efd657c9-1d70-4b19-8b66-fa6aa21bb0fc ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.19.0-38-generic N/A
 linux-backports-modules-5.19.0-38-generic  N/A
 linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/07/2022
dmi.bios.release: 1.1
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.01
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Ganymede_BCU
dmi.board.vendor: BC
dmi.board.version: V1.01
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.01
dmi.ec.firmware.release: 1.1
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.01:bd04/07/2022:br1.1:efr1.1:svnAcer:pnAspireA515-47:pvrV1.01:rvnBC:rnGanymede_BCU:rvrV1.01:cvnAcer:ct10:cvrV1.01:sku:
dmi.product.family: Aspire 5
dmi.product.name: Aspire A515-47
dmi.product.sku: 
dmi.product.version: V1.01
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug kinetic wayland-session

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

Title:
  Laptop not waking from second suspend

Status in linux package in Ubuntu:
  New

Bug description:
  My laptop does not wake up after I've suspended it, except for the
  first time. This is incredibly annoying and has just recently been
  introduced to my system.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-38-generic 5.19.0-38.39
  ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 29 15:05:53 2023
  InstallationDate: Installed on 2022-12-30 (88 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: Acer Aspire A515-47
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic 
root=UUID=efd657c9-1d70-4b19-8b66-fa6aa21bb0fc ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-38-generic N/A
   linux-backports-modules-5.19.0-38-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2022
  dmi.bios.release: 1.1
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.01
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Ganymede_BCU
  dmi.board.vendor: BC
  dmi.board.version: V1.01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.01
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.01:bd04/07/2022:br1.1:efr1.1:svnAcer:pnAspireA515-47:pvrV1.01:rvnBC:rnGanymede_BCU:rvrV1.01:cvnAcer:ct10:cvrV1.01:sku:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-47
  dmi.product.sku: 
  dmi.product.version: V1.01
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013204/+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 1951424] Re: No audio after install ubuntu 21.10 on Acer swift 3

2021-12-16 Thread Axel Lin

hda-dsp HDMI/DP,pcm=4 as 
/devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input19
  [3.707769] input: sof-hda-dsp HDMI/DP,pcm=5 as 
/devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input20
  [4.195918] Bluetooth: hci0: Waiting for firmware download to complete
  [4.197511] Bluetooth: hci0: Firmware loaded in 1706912 usecs
  [4.197548] Bluetooth: hci0: Waiting for device to boot
  [4.212520] Bluetooth: hci0: Device booted in 14633 usecs
  [4.212604] Bluetooth: hci0: Found Intel DDC parameters: 
intel/ibt-19-0-4.ddc
  [4.214524] Bluetooth: hci0: Applying Intel DDC parameters completed
  [4.217520] Bluetooth: hci0: Firmware revision 0.4 build 164 week 35 2021
  [4.277577] Bluetooth: hci0: MSFT filter_enable is already on
  [4.282349] NET: Registered protocol family 38
  [4.417930] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [4.509512] rfkill: input handler disabled
  [6.839147] intel-sdw intel-sdw.1: Clock stop failed -110
  [6.839152] intel-sdw intel-sdw.1: cannot enable clock stop on suspend
  [6.839160] intel-sdw intel-sdw.0: Clock stop failed -110
  [6.839161] intel-sdw intel-sdw.0: cannot enable clock stop on suspend

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-modules-5.13.0-21-generic 5.13.0-21.21
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  axel   1389 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 18 21:45:07 2021
  InstallationDate: Installed on 2021-11-17 (1 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Acer Swift SF314-511
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic 
root=UUID=7ff3fa96-2956-40c5-8019-34ad3e574c1c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-21-generic N/A
   linux-backports-modules-5.13.0-21-generic  N/A
   linux-firmware 1.201.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2021
  dmi.bios.release: 1.9
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Sake_TL
  dmi.board.vendor: TGL
  dmi.board.version: V1.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.09
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd09/03/2021:br1.9:efr1.5:svnAcer:pnSwiftSF314-511:pvrV1.09:rvnTGL:rnSake_TL:rvrV1.09:cvnAcer:ct10:cvrV1.09:sku:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-511
  dmi.product.sku: 
  dmi.product.version: V1.09
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951424/+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 1951424] Re: No audio after install ubuntu 21.10 on Acer swift 3

2021-12-13 Thread Axel Lin

/input18
  [3.707715] input: sof-hda-dsp HDMI/DP,pcm=4 as 
/devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input19
  [3.707769] input: sof-hda-dsp HDMI/DP,pcm=5 as 
/devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input20
  [4.195918] Bluetooth: hci0: Waiting for firmware download to complete
  [4.197511] Bluetooth: hci0: Firmware loaded in 1706912 usecs
  [4.197548] Bluetooth: hci0: Waiting for device to boot
  [4.212520] Bluetooth: hci0: Device booted in 14633 usecs
  [4.212604] Bluetooth: hci0: Found Intel DDC parameters: 
intel/ibt-19-0-4.ddc
  [4.214524] Bluetooth: hci0: Applying Intel DDC parameters completed
  [4.217520] Bluetooth: hci0: Firmware revision 0.4 build 164 week 35 2021
  [4.277577] Bluetooth: hci0: MSFT filter_enable is already on
  [4.282349] NET: Registered protocol family 38
  [4.417930] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [4.509512] rfkill: input handler disabled
  [6.839147] intel-sdw intel-sdw.1: Clock stop failed -110
  [6.839152] intel-sdw intel-sdw.1: cannot enable clock stop on suspend
  [6.839160] intel-sdw intel-sdw.0: Clock stop failed -110
  [6.839161] intel-sdw intel-sdw.0: cannot enable clock stop on suspend

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-modules-5.13.0-21-generic 5.13.0-21.21
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  axel   1389 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 18 21:45:07 2021
  InstallationDate: Installed on 2021-11-17 (1 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Acer Swift SF314-511
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic 
root=UUID=7ff3fa96-2956-40c5-8019-34ad3e574c1c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-21-generic N/A
   linux-backports-modules-5.13.0-21-generic  N/A
   linux-firmware 1.201.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2021
  dmi.bios.release: 1.9
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Sake_TL
  dmi.board.vendor: TGL
  dmi.board.version: V1.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.09
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd09/03/2021:br1.9:efr1.5:svnAcer:pnSwiftSF314-511:pvrV1.09:rvnTGL:rnSake_TL:rvrV1.09:cvnAcer:ct10:cvrV1.09:sku:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-511
  dmi.product.sku: 
  dmi.product.version: V1.09
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951424/+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 1951424] [NEW] No audio after install ubuntu 21.10 on Acer swift 3

2021-11-18 Thread Axel Lin

: hci0: Device booted in 14633 usecs
[4.212604] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
[4.214524] Bluetooth: hci0: Applying Intel DDC parameters completed
[4.217520] Bluetooth: hci0: Firmware revision 0.4 build 164 week 35 2021
[4.277577] Bluetooth: hci0: MSFT filter_enable is already on
[4.282349] NET: Registered protocol family 38
[4.417930] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
[4.509512] rfkill: input handler disabled
[6.839147] intel-sdw intel-sdw.1: Clock stop failed -110
[6.839152] intel-sdw intel-sdw.1: cannot enable clock stop on suspend
[6.839160] intel-sdw intel-sdw.0: Clock stop failed -110
[6.839161] intel-sdw intel-sdw.0: cannot enable clock stop on suspend

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-modules-5.13.0-21-generic 5.13.0-21.21
ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
Uname: Linux 5.13.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  axel   1389 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 18 21:45:07 2021
InstallationDate: Installed on 2021-11-17 (1 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: Acer Swift SF314-511
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic 
root=UUID=7ff3fa96-2956-40c5-8019-34ad3e574c1c ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-21-generic N/A
 linux-backports-modules-5.13.0-21-generic  N/A
 linux-firmware 1.201.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/03/2021
dmi.bios.release: 1.9
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.09
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Sake_TL
dmi.board.vendor: TGL
dmi.board.version: V1.09
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.09
dmi.ec.firmware.release: 1.5
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd09/03/2021:br1.9:efr1.5:svnAcer:pnSwiftSF314-511:pvrV1.09:rvnTGL:rnSake_TL:rvrV1.09:cvnAcer:ct10:cvrV1.09:sku:
dmi.product.family: Swift 3
dmi.product.name: Swift SF314-511
dmi.product.sku: 
dmi.product.version: V1.09
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug impish wayland-session

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

Title:
  No audio after install ubuntu 21.10 on Acer swift 3

Status in linux package in Ubuntu:
  New

Bug description:
  dmesg shows below errors: (see intel-sdw lines)

  [3.428920] i915 :00:02.0: [drm] fb0: i915drmfb frame buffer device
  [3.461588] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode
  [3.482055] sof-audio-pci-intel-tgl :00:1f.3: No SoundWire machine 
driver found
  [3.482059] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 5
  [3.482061] sof-audio-pci-intel-tgl :00:1f.3: using HDA machine driver 
skl_hda_dsp_generic now
  [3.482066] sof-audio-pci-intel-tgl :00:1f.3: DMICs detected in NHLT 
tables: 2
  [3.584389] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 
1:6:0-18fab
  [3.584392] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:17:0 
Kernel ABI 3:18:0
  [3.586144] intel-sdw intel-sdw.0: Bus clash for control word
  [3.586147] intel-sdw intel-sdw.0: Bus clash for data word
  [3.586169] intel-sdw intel-sdw.1: Bus clash for control word
  [3.586171] intel-sdw intel-sdw.1: Bus clash for data word
  [3.586227] intel-sdw intel-sdw.0: Bus clash for control word
  [3.586230] intel-sdw intel-sdw.1: Bus clash for control word
  [3.586275] intel-sdw intel-sdw.0: Bus clash for control word
  [3.586279] intel-sdw intel-sdw.1: Bus clash for control word
  [3.586342] intel-sdw intel-sdw.0: Bus clash for control word
  [3.586346] intel-sdw intel-sdw.1: Bus clash for control word
  [3.586395] intel-sdw intel-sdw.0: Bus clash for control word
  [3.586398] intel-sdw intel-sdw.1: Bus clash for control word
  [3.593087] sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 3:17:0 
Kernel ABI 3:18:0
  [3.610615] sof-audio-pci-intel-tgl :00:1f.3: ASoC: Parent card not 
yet available, widget card binding deferred
  [3.640221] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.640226] snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.640228] snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.640229] snd_hda_codec_realtek ehdaudio0D

[Kernel-packages] [Bug 1906131] Re: No rule to make target 'scripts/module.lds' while building out-of-tree modules

2021-02-01 Thread Axel Siebenwirth

This is happening to my NVIDIA module build with kernel 5.10.12 as well.

root@jaxel:~# dpkg-reconfigure nvidia-dkms-460 
Removing all DKMS Modules
Done.
update-initramfs: deferring update (trigger activated)
update-initramfs: Generating /boot/initrd.img-5.9.16-050916-generic
INFO:Enable nvidia
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
Loading new nvidia-460.39 DKMS files...
Building for 5.9.16-050916-generic 5.10.12-051012-generic
Building for architecture x86_64
Building initial module for 5.9.16-050916-generic
Secure Boot not enabled on this system.
Done.

nvidia.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.9.16-050916-generic/updates/dkms/

nvidia-modeset.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.9.16-050916-generic/updates/dkms/

nvidia-drm.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.9.16-050916-generic/updates/dkms/

nvidia-uvm.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.9.16-050916-generic/updates/dkms/

depmod...

DKMS: install completed.
Building initial module for 5.10.12-051012-generic
ERROR (dkms apport): kernel package linux-headers-5.10.12-051012-generic is not 
supported
Error! Bad return status for module build on kernel: 5.10.12-051012-generic 
(x86_64)
Consult /var/lib/dkms/nvidia/460.39/build/make.log for more information.

--- /var/lib/dkms/nvidia/460.39/build/make.log

make -f ./scripts/Makefile.modpost
  sed 's/ko$/o/' /var/lib/dkms/nvidia/460.39/build/modules.order | 
scripts/mod/modpost  -a   -o /var/lib/dkms/nvidia/460.39/build/Module.symvers 
-e -i Module.symvers   -T -
make -f ./scripts/Makefile.modfinal
make[3]: *** No rule to make target 'scripts/module.lds', needed by 
'/var/lib/dkms/nvidia/460.39/build/nvidia-drm.ko'.  Stop.
make[3]: *** Waiting for unfinished jobs
  cc -Wp,-MMD,/var/lib/dkms/nvidia/460.39/build/.nvidia-drm.mod.o.d  -nostdinc 
-isystem /usr/lib/gcc/x86_64-linux-gnu/9/include -I./arch/x86/include 
-I./arch/x86/include/generated  -I./include -I./arch/x86/include/uapi 
-I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi 
-include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h 
-D__KERNEL__ -fmacro-prefix-map=./= -Wall -Wundef -Werror=strict-prototypes 
-Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE 
-Werror=implicit-function-declaration -Werror=implicit-int -Werror=return-type 
-Wno-format-security -std=gnu89 -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx 
-m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 
-mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone 
-mcmodel=kernel -DCONFIG_X86_X32_ABI -Wno-sign-compare 
-fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern 
-mindirect-branch-register -fno-jump-tables -fno-delete-null-pointer-checks 
-Wno-frame-address -Wno-format-truncation -Wno-format-overflow 
-Wno-address-of-packed-member -O2 --param=allow-store-data-races=0 
-Wframe-larger-than=1024 -fstack-protector-strong -Wno-unused-but-set-variable 
-Wimplicit-fallthrough -Wno-unused-const-variable -fno-omit-frame-pointer 
-fno-optimize-sibling-calls -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY 
-Wdeclaration-after-statement -Wvla -Wno-pointer-sign -Wno-stringop-truncation 
-Wno-array-bounds -Wno-stringop-overflow -Wno-restrict -Wno-maybe-uninitialized 
-fno-strict-overflow -fno-stack-check -fconserve-stack -Werror=date-time 
-Werror=incompatible-pointer-types -Werror=designated-init -fcf-protection=none 
-Wno-packed-not-aligned  -DMODULE  -DKBUILD_BASENAME='"nvidia_drm.mod"' 
-DKBUILD_MODNAME='"nvidia_drm"' -c -o 
/var/lib/dkms/nvidia/460.39/build/nvidia-drm.mod.o 
/var/lib/dkms/nvidia/460.39/build/nvidia-drm.mod.c
make[2]: *** [scripts/Makefile.modpost:117: __modpost] Error 2
make[1]: *** [Makefile:1709: modules] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-5.10.12-051012-generic'

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

Title:
  No rule to make target 'scripts/module.lds' while building out-of-tree
  modules

Status in linux package in Ubuntu:
  Fix Released
Status in linux package in Debian:
  Unknown

Bug description:
  kernel v5.10-rc1 introduced a change ( 596b0474d3d9 "kbuild:
  preprocess module linker script" ) that affects where and how
  scripts/module.lds is

[Kernel-packages] [Bug 1849917] Re: [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI stuttering in kernel 5.3 (but 5.0 has no problem)

2019-11-06 Thread Axel Meunier

Additional dmesg output, right after the problem appears for the first
time (sometime after booting, definitely not related to suspend as I
supposed in my first message).


** Attachment added: "dmesg-2.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849917/+attachment/5303375/+files/dmesg-2.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/1849917

Title:
  [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause
  GUI stuttering in kernel 5.3 (but 5.0 has no problem)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 19.10 from 19.04 I noticed the mouse moves 
unequally/choppy. I did a fresh install (deleting and overwriting 19.04 with 
19.10).
  For example: When I want to go to a button the cursor sometimes stops on the 
way to it and moves on milliseconds later.
  In Ubuntu Ubuntu 19.04 (which is my daily driver for now) this behavior is 
not present.

  Please let me now if I can add some further information.

  lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  All available system updates were installed. No extensions added
  additionally.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 26 06:23:01 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-10-20 (5 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849917/+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 1849917] Re: [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI stuttering in kernel 5.3 (but 5.0 has no problem)

2019-11-06 Thread Axel Meunier

And the dmesg.

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849917/+attachment/5303370/+files/dmesg.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/1849917

Title:
  [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause
  GUI stuttering in kernel 5.3 (but 5.0 has no problem)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 19.10 from 19.04 I noticed the mouse moves 
unequally/choppy. I did a fresh install (deleting and overwriting 19.04 with 
19.10).
  For example: When I want to go to a button the cursor sometimes stops on the 
way to it and moves on milliseconds later.
  In Ubuntu Ubuntu 19.04 (which is my daily driver for now) this behavior is 
not present.

  Please let me now if I can add some further information.

  lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  All available system updates were installed. No extensions added
  additionally.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 26 06:23:01 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-10-20 (5 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849917/+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 1849917] Re: [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI stuttering in kernel 5.3 (but 5.0 has no problem)

2019-11-06 Thread Axel Meunier

I'm affected by what seems to be the same bug or a very similar one.
Also Ubuntu 19.10 fresh install.
Additional information from what I have observed on my machine :
- It's not only the cursor that stutters but the whole machine freezes for an
instant. It's most noticeable while scrolling or watching videos.
- it does not start right away. Maybe after suspend ? I'm not yet sure.
- I have the same information re the Inter wireless 8260 driver than mentioned
by the other user (namely that it does not function).
- On the other hand, I have tried disabling Wifi but it did not seem to have
any effect (I will check again).
Here are the dmesg and lpsci text files.
Thanks for your help.

** Attachment added: "lspcik.txt"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849917/+attachment/5303369/+files/lspcik.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/1849917

Title:
[iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause
GUI stuttering in kernel 5.3 (but 5.0 has no problem)

Status in linux package in Ubuntu:
Confirmed

Bug description:
After upgrading to Ubuntu 19.10 from 19.04 I noticed the mouse moves
unequally/choppy. I did a fresh install (deleting and overwriting 19.04 with
19.10).
For example: When I want to go to a button the cursor sometimes stops on the
way to it and moves on milliseconds later.
In Ubuntu Ubuntu 19.04 (which is my daily driver for now) this behavior is
not present.

Please let me now if I can add some further information.

lsb_release -rd
Description: Ubuntu 19.10
Release: 19.10

All available system updates were installed. No extensions added
additionally.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 26 06:23:01 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-10-20 (5 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849917/+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 1803600] Re: Elantech - Touchpad not working after upgrading to 18.10 from 18.04

2018-12-14 Thread axel

P52:
"cat /sys/bus/serio/devices/serio1/firmware_id":
PNP: LEN2132 PNP0f13

Confirming a fresh install of ubuntu 18.10 works yields a fully functional 
touchpad but updating (tested with current kernel 4.18.0-12-generic) renders 
the touchpad unusable.
Issuing "sudo sh -c 'echo -n "elantech"> 
/sys/bus/serio/devices/serio1/protocol'" restores the trackpads functionality 
for the current session as already described.

"dmesg | grep -i elan" yields:
[3.167455] psmouse serio1: elantech: assuming hardware version 4 (with 
firmware version 0x5f2001)
[3.179490] psmouse serio1: elantech: Synaptics capabilities query result 
0x90, 0x18, 0x0e.
[3.191246] psmouse serio1: elantech: Elan sample query result 00, 28, 96
[3.202881] psmouse serio1: elantech: Trying to set up SMBus access
[4.032146] elan_i2c 0-0015: 0-0015 supply vcc not found, using dummy 
regulator
[4.048144] elan_i2c 0-0015: failed to get resolution: -5
[4.048168] elan_i2c: probe of 0-0015 failed with error -5

after echoing "elantech", dmesg shows
[ 2185.669979] input: ETPS/2 Elantech TrackPoint as 
/devices/platform/i8042/serio1/input/input17
[ 2185.683258] input: ETPS/2 Elantech Touchpad as 
/devices/platform/i8042/serio1/input/input16
instead of the former last three lines.

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

Title:
  Elantech - Touchpad not working after upgrading to 18.10 from 18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Confirmed affected laptops:
  ThinkPad: 
  L480
  L580
  P72
  P52

  
  When updating from 18.04 to 18.10 on a ThinkPad L480 the Elantech touchpad 
stopped working. This means it is not recognized at all. This problem occured 
after the first boot in 18.10

  `dmesg | grep -i elantech` shows the following errors:

  [3.409043] psmouse serio1: elantech: assuming hardware version 4 
(with firmware version 0x5f3001)
  [3.427372] psmouse serio1: elantech: Synaptics capabilities query 
result 0x90, 0x18, 0x10.
  [3.447275] psmouse serio1: elantech: Elan sample query result 00, 23, 
c8
  [3.464905] psmouse serio1: elantech: Trying to set up SMBus access
  [5.576149] elan_i2c 0-0015: 0-0015 supply vcc not found, using dummy 
regulator
  [5.586505] elan_i2c 0-0015: failed to get resolution: -71
  [5.586527] elan_i2c: probe of 0-0015 failed with error -71

  uname:

  $ uname -a
  Linux test 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  I found the following thread which solves the problem temporarly (and reports 
the same problem in Arch):
  https://bugs.archlinux.org/task/59714

  Running the following command enables it again for the current
  session:

  sudo sh -c 'echo -n "elantech">
  /sys/bus/serio/devices/serio1/protocol'

  dmesg afterwards:

  [  569.522490] psmouse serio1: elantech: assuming hardware version 4 
(with firmware version 0x5f3001)
  [  569.544584] psmouse serio1: elantech: Synaptics capabilities query 
result 0x90, 0x18, 0x10.
  [  569.565939] psmouse serio1: elantech: Elan sample query result 00, 23, 
c8

  Before running the fix:

  $ cat /sys/bus/serio/devices/serio1/protocol
  ETSMBus

  and after:

  $ cat /sys/bus/serio/devices/serio1/protocol
  ETPS/2

  After reboot the command has to be run again, of course.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu Nov 15 20:59:36 2018
  DistUpgraded: 2018-11-10 09:56:53,358 DEBUG icon theme changed, re-reading
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.15.0-38-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-10-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo UHD Graphics 620 [17aa:506a]
  InstallationDate: Installed on 2018-08-06 (101 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20LS001AGE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=a1f97298-a2b8-469d-80ed-7497c6e6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-11-10 (5 days ago)
  dmi.bios.date: 02/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0QET37W (1.14 )
  dmi.board.asset.tag:

[Kernel-packages] [Bug 1729030] Re: [regression] Kernel crash in bluetooth with Bose QC35

2018-01-08 Thread Axel Meunier

I also comment on this bug although it is tagged as "expired" :
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718864

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

Title:
  [regression] Kernel crash in bluetooth with Bose QC35

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bose QC35 with latest firmware
  Ubuntu 17.10

  This is a regression from 17.04 Ubuntu Gnome. In 17.04, you had to
  temporarily disable `le` mode to pair but after pairing, everything
  worked flawlessly. In 17.10, pairing works out of the box, but the
  following issue appears:

  After a few hours of being connected, the connection between bose qc35
  and Ubuntu seemingly breaks: the headphones don't play any sound
  anymore. re-pairing fails and restarting the headphones doesn't fix
  the issue. It seems bluetoothd crashed conmpletely since
  `bluetoothctl` doesn't work anymore.. Restarting Ubuntu fixes the
  issue.

  syslog contains a bunch of kernel stacktraces including a nullpointer
  dereference..

  Oct 31 16:41:06 travers dbus-daemon[3888]: Activating via systemd: service 
name='org.bluez.obex' unit='dbus-org.bluez.obex.service'
  Oct 31 16:41:06 travers systemd[3874]: Starting Bluetooth OBEX service...
  Oct 31 16:41:06 travers bluetoothd[1128]: Failed to set mode: Busy (0x0a)
  Oct 31 16:41:06 travers obexd[29587]: OBEX daemon 5.46
  Oct 31 16:41:06 travers dbus-daemon[3888]: Successfully activated service 
'org.bluez.obex'
  Oct 31 16:41:06 travers systemd[3874]: Started Bluetooth OBEX service.
  Oct 31 16:41:06 travers bluetoothd[1128]: Failed to set mode: Busy (0x0a)
  Oct 31 16:41:06 travers bluetoothd[1128]: Failed to set mode: Busy (0x0a)
  Oct 31 16:41:12 travers kernel: Bluetooth: hci0 link tx timeout
  Oct 31 16:41:12 travers kernel: Bluetooth: hci0 killing stalled connection 
04:52:c7:60:d6:2c
  Oct 31 16:41:12 travers acpid[1126]: input device has been disconnected, fd 24
  Oct 31 16:41:12 travers kernel: Bluetooth: hci0 link tx timeout
  Oct 31 16:41:12 travers kernel: Bluetooth: hci0 killing stalled connection 
04:52:c7:60:d6:2c
  Oct 31 16:41:14 travers bluetoothd[1128]: Disconnecting failed: already 
disconnected
  Oct 31 16:41:18 travers bluetoothd[1128]: Close: Connection timed out (110)
  Oct 31 16:41:18 travers kernel: Bluetooth: hci0 link tx timeout
  Oct 31 16:41:18 travers kernel: Bluetooth: hci0 killing stalled connection 
04:52:c7:60:d6:2c
  Oct 31 16:41:20 travers bluetoothd[1128]: Abort: Connection timed out (110)
  Oct 31 16:41:20 travers kernel: Bluetooth: hci0 link tx timeout
  Oct 31 16:41:20 travers kernel: Bluetooth: hci0 killing stalled connection 
04:52:c7:60:d6:2c
  Oct 31 16:41:20 travers kernel: Bluetooth: hci0 link tx timeout
  Oct 31 16:41:20 travers kernel: Bluetooth: hci0 killing stalled connection 
04:52:c7:60:d6:2c
  Oct 31 16:41:20 travers dbus[1074]: [system] Rejected send message, 3 matched 
rules; type="method_return", sender=":1.86" (uid=1000 pid=3997 
comm="/usr/bin/pulseaudio --start --log-target=syslog ") interface="(unset)" 
member="(unset)" error name="(unset)" requested_reply="0" destination=":1.7" 
(uid=0 pid=1128 comm="/usr/lib/bluetooth/bluetoothd ")
  Oct 31 16:41:20 travers gsd-media-keys[4157]: Unable to get default sink
  Oct 31 16:41:32 travers kernel: sysfs: cannot create duplicate filename 
'/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:256'
  Oct 31 16:41:32 travers kernel: [ cut here ]
  Oct 31 16:41:32 travers kernel: WARNING: CPU: 2 PID: 19117 at 
/build/linux-XO_uEE/linux-4.13.0/fs/sysfs/dir.c:31 sysfs_warn_dup+0x56/0x70
  Oct 31 16:41:32 travers kernel: Modules linked in: rfcomm ip6t_MASQUERADE 
nf_nat_masquerade_ipv6 ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 
nf_nat_ipv6 xt_comment zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) 
spl(O) pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm cmac 
xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack 
libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter 
ebtables ip6table_filter ip6_tables iptable_filter bnep nls_iso8859_1 arc4 
hid_alps snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel kvm dell_rbtn dell_laptop iwlmvm irqbypass dell_smm_hwmon 
mac80211 crct10dif_pclmul crc32_pclmul snd_hda_codec_realtek 
snd_hda_codec_generic
  Oct 31 16:41:32 travers kernel:  ghash_clmulni_intel pcbc iwlwifi rtsx_pci_ms 
uvcvideo cfg80211 memstick videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev media aesni_intel aes_x86_64 crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_intel snd_hda_codec joydev 
snd_hda_core snd_hwdep snd_pcm btusb btrtl snd_seq_midi snd_seq_midi_event 
snd_rawmidi snd_seq

[Kernel-packages] [Bug 1729030] Re: [regression] Kernel crash in bluetooth with Bose QC35

2018-01-08 Thread Axel Meunier

Here is full dmesg.
In it there is this bug :

BUG: unable to handle kernel NULL pointer dereference at
0020


** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729030/+attachment/5032718/+files/dmesg.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/1729030

Title:
  [regression] Kernel crash in bluetooth with Bose QC35

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bose QC35 with latest firmware
  Ubuntu 17.10

  This is a regression from 17.04 Ubuntu Gnome. In 17.04, you had to
  temporarily disable `le` mode to pair but after pairing, everything
  worked flawlessly. In 17.10, pairing works out of the box, but the
  following issue appears:

  After a few hours of being connected, the connection between bose qc35
  and Ubuntu seemingly breaks: the headphones don't play any sound
  anymore. re-pairing fails and restarting the headphones doesn't fix
  the issue. It seems bluetoothd crashed conmpletely since
  `bluetoothctl` doesn't work anymore.. Restarting Ubuntu fixes the
  issue.

  syslog contains a bunch of kernel stacktraces including a nullpointer
  dereference..

  Oct 31 16:41:06 travers dbus-daemon[3888]: Activating via systemd: service 
name='org.bluez.obex' unit='dbus-org.bluez.obex.service'
  Oct 31 16:41:06 travers systemd[3874]: Starting Bluetooth OBEX service...
  Oct 31 16:41:06 travers bluetoothd[1128]: Failed to set mode: Busy (0x0a)
  Oct 31 16:41:06 travers obexd[29587]: OBEX daemon 5.46
  Oct 31 16:41:06 travers dbus-daemon[3888]: Successfully activated service 
'org.bluez.obex'
  Oct 31 16:41:06 travers systemd[3874]: Started Bluetooth OBEX service.
  Oct 31 16:41:06 travers bluetoothd[1128]: Failed to set mode: Busy (0x0a)
  Oct 31 16:41:06 travers bluetoothd[1128]: Failed to set mode: Busy (0x0a)
  Oct 31 16:41:12 travers kernel: Bluetooth: hci0 link tx timeout
  Oct 31 16:41:12 travers kernel: Bluetooth: hci0 killing stalled connection 
04:52:c7:60:d6:2c
  Oct 31 16:41:12 travers acpid[1126]: input device has been disconnected, fd 24
  Oct 31 16:41:12 travers kernel: Bluetooth: hci0 link tx timeout
  Oct 31 16:41:12 travers kernel: Bluetooth: hci0 killing stalled connection 
04:52:c7:60:d6:2c
  Oct 31 16:41:14 travers bluetoothd[1128]: Disconnecting failed: already 
disconnected
  Oct 31 16:41:18 travers bluetoothd[1128]: Close: Connection timed out (110)
  Oct 31 16:41:18 travers kernel: Bluetooth: hci0 link tx timeout
  Oct 31 16:41:18 travers kernel: Bluetooth: hci0 killing stalled connection 
04:52:c7:60:d6:2c
  Oct 31 16:41:20 travers bluetoothd[1128]: Abort: Connection timed out (110)
  Oct 31 16:41:20 travers kernel: Bluetooth: hci0 link tx timeout
  Oct 31 16:41:20 travers kernel: Bluetooth: hci0 killing stalled connection 
04:52:c7:60:d6:2c
  Oct 31 16:41:20 travers kernel: Bluetooth: hci0 link tx timeout
  Oct 31 16:41:20 travers kernel: Bluetooth: hci0 killing stalled connection 
04:52:c7:60:d6:2c
  Oct 31 16:41:20 travers dbus[1074]: [system] Rejected send message, 3 matched 
rules; type="method_return", sender=":1.86" (uid=1000 pid=3997 
comm="/usr/bin/pulseaudio --start --log-target=syslog ") interface="(unset)" 
member="(unset)" error name="(unset)" requested_reply="0" destination=":1.7" 
(uid=0 pid=1128 comm="/usr/lib/bluetooth/bluetoothd ")
  Oct 31 16:41:20 travers gsd-media-keys[4157]: Unable to get default sink
  Oct 31 16:41:32 travers kernel: sysfs: cannot create duplicate filename 
'/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:256'
  Oct 31 16:41:32 travers kernel: [ cut here ]
  Oct 31 16:41:32 travers kernel: WARNING: CPU: 2 PID: 19117 at 
/build/linux-XO_uEE/linux-4.13.0/fs/sysfs/dir.c:31 sysfs_warn_dup+0x56/0x70
  Oct 31 16:41:32 travers kernel: Modules linked in: rfcomm ip6t_MASQUERADE 
nf_nat_masquerade_ipv6 ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 
nf_nat_ipv6 xt_comment zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) 
spl(O) pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm cmac 
xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack 
libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter 
ebtables ip6table_filter ip6_tables iptable_filter bnep nls_iso8859_1 arc4 
hid_alps snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel kvm dell_rbtn dell_laptop iwlmvm irqbypass dell_smm_hwmon 
mac80211 crct10dif_pclmul crc32_pclmul snd_hda_codec_realtek 
snd_hda_codec_generic
  Oct 31 16:41:32 travers kernel:  ghash_clmulni_intel pcbc iwlwifi rtsx_pci_ms 
uvcvideo cfg80211 memstick videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev media aesni_intel aes_x86_64 crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf

[Kernel-packages] [Bug 1718864] Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000020

dmesg output

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718864/+attachment/5032431/+files/dmesg.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/1718864

Title:
  BUG: unable to handle kernel NULL pointer dereference at
  0020

Status in linux package in Ubuntu:
  Expired

Bug description:
  Ubuntu Artful Aardvark (development branch)
  Release:  17.10
  Bluez 5.46

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 22 15:11:53 2017
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location RIP: klist_next+0x16/0xb0 RSP: abf7c40f3c70
  Failure: oops
  InstallationDate: Installed on 2017-09-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170914)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic.efi.signed 
root=UUID=23f296e8-85c6-49c5-8040-17830fef017b ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at 
0020
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/03/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: KYSKLi70.86A.0037.2016.0603.1032
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-405
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0037.2016.0603.1032:bd06/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-405:cvnIntelCorporation:ct3:cvr1.0:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718864/+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 1718864] Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000020

kernel information :
4.13.0-21-generic

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

Title:
  BUG: unable to handle kernel NULL pointer dereference at
  0020

Status in linux package in Ubuntu:
  Expired

Bug description:
  Ubuntu Artful Aardvark (development branch)
  Release:  17.10
  Bluez 5.46

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 22 15:11:53 2017
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location RIP: klist_next+0x16/0xb0 RSP: abf7c40f3c70
  Failure: oops
  InstallationDate: Installed on 2017-09-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170914)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic.efi.signed 
root=UUID=23f296e8-85c6-49c5-8040-17830fef017b ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at 
0020
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/03/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: KYSKLi70.86A.0037.2016.0603.1032
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-405
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0037.2016.0603.1032:bd06/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-405:cvnIntelCorporation:ct3:cvr1.0:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718864/+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 1718864] Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000020

I woulf like to reopen this bug since I am affected.
Fresh install of Ubuntu 17.10 (actuall Pop!_OS).
What information shoud I provide ?

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

Title:
  BUG: unable to handle kernel NULL pointer dereference at
  0020

Status in linux package in Ubuntu:
  Expired

Bug description:
  Ubuntu Artful Aardvark (development branch)
  Release:  17.10
  Bluez 5.46

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 22 15:11:53 2017
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location RIP: klist_next+0x16/0xb0 RSP: abf7c40f3c70
  Failure: oops
  InstallationDate: Installed on 2017-09-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170914)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic.efi.signed 
root=UUID=23f296e8-85c6-49c5-8040-17830fef017b ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at 
0020
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/03/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: KYSKLi70.86A.0037.2016.0603.1032
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-405
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0037.2016.0603.1032:bd06/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-405:cvnIntelCorporation:ct3:cvr1.0:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718864/+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 1729030] Re: [regression] Kernel crash in bluetooth with Bose QC35

My computer (Depp Precision 5510 with Ubuntu 17.10 - actually Pop!_OS -
fresh install) is affected by the same kind of bug.

Connection to bluetooth speakers sometimes works, sometimes does not,
sometimes works well at boot then stops. I am not able to reproduce the
issue consistently. When bluetooth stops working, it can not be
desactivated/reactivated from panel, system settings stalls, shutdown
fails => hard reset.

What information should I provide ?
I have this :

axel@pop-os:~$ dmesg |grep -i bluetooth

[4.253605] Bluetooth: Core ver 2.22
[4.253617] Bluetooth: HCI device and connection manager initialized
[4.253618] Bluetooth: HCI socket layer initialized
[4.253619] Bluetooth: L2CAP socket layer initialized
[4.253622] Bluetooth: SCO socket layer initialized
[4.263362] Bluetooth: HCI UART driver ver 2.3
[4.263364] Bluetooth: HCI UART protocol H4 registered
[4.263364] Bluetooth: HCI UART protocol BCSP registered
[4.263378] Bluetooth: HCI UART protocol LL registered
[4.263379] Bluetooth: HCI UART protocol ATH3K registered
[4.263379] Bluetooth: HCI UART protocol Three-wire (H5) registered
[4.263401] Bluetooth: HCI UART protocol Intel registered
[4.263412] Bluetooth: HCI UART protocol Broadcom registered
[4.263413] Bluetooth: HCI UART protocol QCA registered
[4.263413] Bluetooth: HCI UART protocol AG6XX registered
[4.263414] Bluetooth: HCI UART protocol Marvell registered
[4.265026] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[4.269822] Bluetooth: hci0: Device revision is 5
[4.269823] Bluetooth: hci0: Secure boot is enabled
[4.269823] Bluetooth: hci0: OTP lock is enabled
[4.269824] Bluetooth: hci0: API lock is enabled
[4.269824] Bluetooth: hci0: Debug lock is disabled
[4.269825] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[4.271430] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[4.442885] Bluetooth: hci0: Failed to send firmware data (-38)
[4.606250] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[4.606251] Bluetooth: BNEP filters: protocol multicast
[4.606253] Bluetooth: BNEP socket layer initialized
[   11.766887] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[   11.771866] Bluetooth: hci0: Device revision is 5
[   11.771868] Bluetooth: hci0: Secure boot is enabled
[   11.771868] Bluetooth: hci0: OTP lock is enabled
[   11.771869] Bluetooth: hci0: API lock is enabled
[   11.771870] Bluetooth: hci0: Debug lock is disabled
[   11.771871] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   11.772112] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[   13.478350] Bluetooth: hci0: Waiting for firmware download to complete
[   13.478830] Bluetooth: hci0: Firmware loaded in 1672625 usecs
[   13.478898] Bluetooth: hci0: Waiting for device to boot
[   13.489968] Bluetooth: hci0: Device booted in 10838 usecs
[   13.490206] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
[   13.494923] Bluetooth: hci0: Applying Intel DDC parameters completed
[   18.880056] Bluetooth: RFCOMM TTY layer initialized
[   18.880062] Bluetooth: RFCOMM socket layer initialized
[   18.880069] Bluetooth: RFCOMM ver 1.11
[   52.107012] Bluetooth: Failed to disable LE scan: status 0x0c
[   87.544907] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[   87.549869] Bluetooth: hci0: Device revision is 5
[   87.549870] Bluetooth: hci0: Secure boot is enabled
[   87.549871] Bluetooth: hci0: OTP lock is enabled
[   87.549871] Bluetooth: hci0: API lock is enabled
[   87.549872] Bluetooth: hci0: Debug lock is disabled
[   87.549873] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   87.550036] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[   88.945581] Bluetooth: hci0: Waiting for firmware download to complete
[   88.945817] Bluetooth: hci0: Firmware loaded in 1369302 usecs
[   88.945906] Bluetooth: hci0: Waiting for device to boot
[   88.956872] Bluetooth: hci0: Device booted in 10777 usecs
[   88.956903] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
[   88.960896] Bluetooth: hci0: Applying Intel DDC parameters completed
[   94.305008] Bluetooth: Failed to disable LE scan: status 0x0c
[  220.089843] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[  220.094856] Bluetooth: hci0: Device revision is 5
[  220.094859] Bluetooth: hci0: Secure boot is enabled
[  220.094861] Bluetooth: hci0: OTP lock is enabled
[  220.094862] Bluetooth: hci0: API lock is enabled
[  220.094863] Bluetooth: hci0: Debug lock is disabled
[  220.094866] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[  220.095185] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[  221.569374] Bluetooth: hci0: Waiting for firmware download to complete
[  221.569812] Bluetooth: hci0: Firmware loaded in 1445665 usecs
[  221.569897] Bluetooth: hci0: Waiting for device to boot
[  221.580971] Bluetooth: hci0: Dev

[Kernel-packages] [Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react

2018-01-05 Thread Axel Schmidt

Sorry but with firmware 1.169.2 doesn't fixed the bluetooth issue at all.
Because only the keyboard worked but not the mouse.
So i must also use the workarround #17

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

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Confirmed
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Confirmed
Status in linux-firmware source package in Artful:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Bluetooth peripherals work initially but stop working shortly
  with Linux 4.13.

  Fix: Updated firmware from Intel containing a fix for the issue.

  Regression Potential: Any firmware updates may bring regressions,
  however this is a bug fix update and therefore regression potential is
  expected to be minimal.

  ---

  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  ---
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp.
   Bus 001 Device 005: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 13d3:5664 IMC Networks
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
    UP RUNNING PSCAN ISCAN INQUIRY
    RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
    TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729389/+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 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04

2017-05-06 Thread Axel Schmidt

Thanks to Ruslan Gol, this worked for me too!

I have a lenovo thinkpad p51s with a SAMSUNG MZVLW512HMJP-000L7 512gb ssd and 
kubuntu 16.10.
After update the kernel to 4.9.0-040900-generic, shutdown only need some 
seconds and not minutes like before! And no cfs-unmount timeout errors 
anymore...

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

Title:
  Poweroff or reboot hangs. Laptop won't shutdown. 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is about a fresh Ubuntu 16.04 install on a new laptop (asus
  x540sa). After pressing the shutdown button in the start menu; the
  shutdown procedure starts and in the final splash screen the system
  just hangs. Tried a second time by pressing Esc once the splash screen
  showed up and I saw that it reaches the line "Reached target shutdown"
  and just stops there, no matter how long I leave it there the machine
  won't turn off.

  I also tried a Kubuntu 16.04 fresh install on the same machine and it
  hanged too at the final splash screen where the pulsating logo
  stopped. Then I tried with Esc only to see the exact same line in the
  end.

  The issue seems to affect lately quite many users as shown by the
  google results of the past month / week or so.

  I have also tried shutting down from the console with shutdown -and
  all the parameters after that suggested online- and sudo poweroff but
  unfortunately they didn't do the trick. The exact same situation
  occurred.

  Unmounting the swap as suggested online doesn't work.

  Also rebooting the system is not working either due to the same issue.

  So right now the only way for me to poweroff the machine is to press
  the power button on the keyboard continuously.

  Reproducible: Always

  Steps to Reproduce:
  1.Install OS
  2.Do something, anything or nothing
  3.Try to shutdown or reboot

  Actual Results:
  The computer is not shutting down: "Reached target shutdown" and hangs there.

  Expected Results:
  Powering off the machine.

  For what it's worth, closing the lid won't suspend the system, but
  using the menu buttons for suspension will do it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594023/+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 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

2017-04-24 Thread Axel H.

Confirm: Released fix resolves 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/1666421

Title:
  kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic:
  Grub works, entering full disk encryption passphrase works, but when the 
desktop comes up mouse and keyboard (via USB) are dead and the desktop also.

  booting the PC without the stick attached works fine, but as soon as
  it is attached (see syslog) mouse, keyboard and the desktop itself are
  dead (checked by opening terminal and "watch date" - freezes, with
  desktop still visible).

  problem is resolved by booting former kernel 4.4.0-59-generic.

  syslog upon attaching stick 
---
  Feb 21 07:17:02 orin kernel: [  188.998338] usb 8-2: new high-speed USB 
device number 2 using xhci_hcd
  Feb 21 07:17:02 orin kernel: [  189.129674] usb 8-2: New USB device found, 
idVendor=0bda, idProduct=8178
  Feb 21 07:17:02 orin kernel: [  189.129682] usb 8-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Feb 21 07:17:02 orin kernel: [  189.129687] usb 8-2: Product: USB WLAN
  Feb 21 07:17:02 orin kernel: [  189.129691] usb 8-2: Manufacturer: Realtek
  Feb 21 07:17:02 orin kernel: [  189.129694] usb 8-2: SerialNumber: 
00e04c01
  Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: 
"/sys/devices/pci:00/:00:10.1/usb8/8-2"
  Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device
  Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service 
name='org.freedesktop.UDisks2' unit='udisks2.service'
  Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager...
  Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting
  Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 
'org.freedesktop.UDisks2'
  Feb 21 07:17:02 orin systemd[1]: Started Disk Manager.
  Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 
on the system message bus
  Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive
  Feb 21 07:17:03 orin kernel: [  190.200286] cfg80211: World regulatory domain 
updated:
  Feb 21 07:17:03 orin kernel: [  190.200294] cfg80211:  DFS Master region: 
unset
  Feb 21 07:17:03 orin kernel: [  190.200297] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Feb 21 07:17:03 orin kernel: [  190.200303] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200308] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200312] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200317] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200321] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200325] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200329] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200333] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.223081] rtl8192cu: Chip version 0x11
  Feb 21 07:17:03 orin kernel: [  190.625235] rtl8192cu: MAC address: 
14:cc:20:10:43:98
  Feb 21 07:17:03 orin kernel: [  190.625241] rtl8192cu: Board Type 0
  Feb 21 07:17:03 orin kernel: [  190.626355] rtl_usb: rx_max_size 15360, 
rx_urb_num 8, in_ep 1
  Feb 21 07:17:03 orin kernel: [  190.626408] rtl8192cu: Loading firmware 
rtlwifi/rtl8192cufw_TMSC.bin
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7698] (wlan0): 
using nl80211 for WiFi device control
  Feb 21 07:17:03 orin kernel: [  190.636625] ieee80211 phy0: Selected rate 
control algorithm 'rtl_rc'
  Feb 21 07:17:03 orin kernel: [  190.637211] usbcore: registered new interface 
driver rtl8192cu
  Feb 21 07:17:03 orin systemd[1]: Starting Load/Save RF Kill Switch Status...
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7780] device 
(wlan0): driver supports Access Point (AP) mode
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7798] manager: 
(wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/4)
  Feb 21 07:17:03 orin kernel: [  190.648972] usbcore: registered new interface 
driver rtl8xxxu
  Feb 21 07:17:03 orin

[Kernel-packages] [Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

2017-04-14 Thread Axel Holzinger

Hi Frans, thanx for your comment.

Well I think it's not about forgetting, because I never heard of it :-(
As "sudo apt-get install linux-image-extra" did not help, I tried "sudo apt-get 
install linux-image-extra-4.4.0-74-generic" (I got already 4.4.0-74.95 when 
updating).

That brought back wireless and it's working!!!

Thank you all of you!!!

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

Title:
  kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic:
  Grub works, entering full disk encryption passphrase works, but when the 
desktop comes up mouse and keyboard (via USB) are dead and the desktop also.

  booting the PC without the stick attached works fine, but as soon as
  it is attached (see syslog) mouse, keyboard and the desktop itself are
  dead (checked by opening terminal and "watch date" - freezes, with
  desktop still visible).

  problem is resolved by booting former kernel 4.4.0-59-generic.

  syslog upon attaching stick 
---
  Feb 21 07:17:02 orin kernel: [  188.998338] usb 8-2: new high-speed USB 
device number 2 using xhci_hcd
  Feb 21 07:17:02 orin kernel: [  189.129674] usb 8-2: New USB device found, 
idVendor=0bda, idProduct=8178
  Feb 21 07:17:02 orin kernel: [  189.129682] usb 8-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Feb 21 07:17:02 orin kernel: [  189.129687] usb 8-2: Product: USB WLAN
  Feb 21 07:17:02 orin kernel: [  189.129691] usb 8-2: Manufacturer: Realtek
  Feb 21 07:17:02 orin kernel: [  189.129694] usb 8-2: SerialNumber: 
00e04c01
  Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: 
"/sys/devices/pci:00/:00:10.1/usb8/8-2"
  Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device
  Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service 
name='org.freedesktop.UDisks2' unit='udisks2.service'
  Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager...
  Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting
  Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 
'org.freedesktop.UDisks2'
  Feb 21 07:17:02 orin systemd[1]: Started Disk Manager.
  Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 
on the system message bus
  Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive
  Feb 21 07:17:03 orin kernel: [  190.200286] cfg80211: World regulatory domain 
updated:
  Feb 21 07:17:03 orin kernel: [  190.200294] cfg80211:  DFS Master region: 
unset
  Feb 21 07:17:03 orin kernel: [  190.200297] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Feb 21 07:17:03 orin kernel: [  190.200303] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200308] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200312] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200317] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200321] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200325] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200329] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200333] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.223081] rtl8192cu: Chip version 0x11
  Feb 21 07:17:03 orin kernel: [  190.625235] rtl8192cu: MAC address: 
14:cc:20:10:43:98
  Feb 21 07:17:03 orin kernel: [  190.625241] rtl8192cu: Board Type 0
  Feb 21 07:17:03 orin kernel: [  190.626355] rtl_usb: rx_max_size 15360, 
rx_urb_num 8, in_ep 1
  Feb 21 07:17:03 orin kernel: [  190.626408] rtl8192cu: Loading firmware 
rtlwifi/rtl8192cufw_TMSC.bin
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7698] (wlan0): 
using nl80211 for WiFi device control
  Feb 21 07:17:03 orin kernel: [  190.636625] ieee80211 phy0: Selected rate 
control algorithm 'rtl_rc'
  Feb 21 07:17:03 orin kernel: [  190.637211] usbcore: registered new interface 
driver rtl8192cu
  Feb 21 07:17:03 orin systemd[1]: Starting Load/Save RF Kill Switch Status...
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7780] device 
(wlan0): driver

[Kernel-packages] [Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

2017-04-14 Thread Axel Holzinger

The reason might be that in
"/lib/modules/4.4.0-73-generic/kernel/drivers/net" there is no folder
"wireless" at all.

In "/lib/modules/4.4.0-73-generic/kernel/drivers/net/wireless" there is
the folder "realtek" with all the needed (but unfortunately not
correctly working) drivers.

How do I get back the realtek wireless drivers with 4.4.0-73.94?

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

Title:
  kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic:
  Grub works, entering full disk encryption passphrase works, but when the 
desktop comes up mouse and keyboard (via USB) are dead and the desktop also.

  booting the PC without the stick attached works fine, but as soon as
  it is attached (see syslog) mouse, keyboard and the desktop itself are
  dead (checked by opening terminal and "watch date" - freezes, with
  desktop still visible).

  problem is resolved by booting former kernel 4.4.0-59-generic.

  syslog upon attaching stick 
---
  Feb 21 07:17:02 orin kernel: [  188.998338] usb 8-2: new high-speed USB 
device number 2 using xhci_hcd
  Feb 21 07:17:02 orin kernel: [  189.129674] usb 8-2: New USB device found, 
idVendor=0bda, idProduct=8178
  Feb 21 07:17:02 orin kernel: [  189.129682] usb 8-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Feb 21 07:17:02 orin kernel: [  189.129687] usb 8-2: Product: USB WLAN
  Feb 21 07:17:02 orin kernel: [  189.129691] usb 8-2: Manufacturer: Realtek
  Feb 21 07:17:02 orin kernel: [  189.129694] usb 8-2: SerialNumber: 
00e04c01
  Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: 
"/sys/devices/pci:00/:00:10.1/usb8/8-2"
  Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device
  Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service 
name='org.freedesktop.UDisks2' unit='udisks2.service'
  Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager...
  Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting
  Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 
'org.freedesktop.UDisks2'
  Feb 21 07:17:02 orin systemd[1]: Started Disk Manager.
  Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 
on the system message bus
  Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive
  Feb 21 07:17:03 orin kernel: [  190.200286] cfg80211: World regulatory domain 
updated:
  Feb 21 07:17:03 orin kernel: [  190.200294] cfg80211:  DFS Master region: 
unset
  Feb 21 07:17:03 orin kernel: [  190.200297] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Feb 21 07:17:03 orin kernel: [  190.200303] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200308] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200312] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200317] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200321] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200325] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200329] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200333] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.223081] rtl8192cu: Chip version 0x11
  Feb 21 07:17:03 orin kernel: [  190.625235] rtl8192cu: MAC address: 
14:cc:20:10:43:98
  Feb 21 07:17:03 orin kernel: [  190.625241] rtl8192cu: Board Type 0
  Feb 21 07:17:03 orin kernel: [  190.626355] rtl_usb: rx_max_size 15360, 
rx_urb_num 8, in_ep 1
  Feb 21 07:17:03 orin kernel: [  190.626408] rtl8192cu: Loading firmware 
rtlwifi/rtl8192cufw_TMSC.bin
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7698] (wlan0): 
using nl80211 for WiFi device control
  Feb 21 07:17:03 orin kernel: [  190.636625] ieee80211 phy0: Selected rate 
control algorithm 'rtl_rc'
  Feb 21 07:17:03 orin kernel: [  190.637211] usbcore: registered new interface 
driver rtl8192cu
  Feb 21 07:17:03 orin systemd[1]: Starting Load/Save RF Kill Switch Status...
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7780] device 
(wlan0): driver

[Kernel-packages] [Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

2017-04-14 Thread Axel Holzinger

Xenial's 4.4.0-73.94 does NOT work for me.

Reason: USB WiFi adapter 7392:7822 based on RTL8192SU chipset is not
detected/loaded anymore, so no WiFi at all.

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

Title:
  kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic:
  Grub works, entering full disk encryption passphrase works, but when the 
desktop comes up mouse and keyboard (via USB) are dead and the desktop also.

  booting the PC without the stick attached works fine, but as soon as
  it is attached (see syslog) mouse, keyboard and the desktop itself are
  dead (checked by opening terminal and "watch date" - freezes, with
  desktop still visible).

  problem is resolved by booting former kernel 4.4.0-59-generic.

  syslog upon attaching stick 
---
  Feb 21 07:17:02 orin kernel: [  188.998338] usb 8-2: new high-speed USB 
device number 2 using xhci_hcd
  Feb 21 07:17:02 orin kernel: [  189.129674] usb 8-2: New USB device found, 
idVendor=0bda, idProduct=8178
  Feb 21 07:17:02 orin kernel: [  189.129682] usb 8-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Feb 21 07:17:02 orin kernel: [  189.129687] usb 8-2: Product: USB WLAN
  Feb 21 07:17:02 orin kernel: [  189.129691] usb 8-2: Manufacturer: Realtek
  Feb 21 07:17:02 orin kernel: [  189.129694] usb 8-2: SerialNumber: 
00e04c01
  Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: 
"/sys/devices/pci:00/:00:10.1/usb8/8-2"
  Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device
  Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service 
name='org.freedesktop.UDisks2' unit='udisks2.service'
  Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager...
  Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting
  Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 
'org.freedesktop.UDisks2'
  Feb 21 07:17:02 orin systemd[1]: Started Disk Manager.
  Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 
on the system message bus
  Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive
  Feb 21 07:17:03 orin kernel: [  190.200286] cfg80211: World regulatory domain 
updated:
  Feb 21 07:17:03 orin kernel: [  190.200294] cfg80211:  DFS Master region: 
unset
  Feb 21 07:17:03 orin kernel: [  190.200297] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Feb 21 07:17:03 orin kernel: [  190.200303] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200308] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200312] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200317] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200321] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200325] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200329] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200333] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.223081] rtl8192cu: Chip version 0x11
  Feb 21 07:17:03 orin kernel: [  190.625235] rtl8192cu: MAC address: 
14:cc:20:10:43:98
  Feb 21 07:17:03 orin kernel: [  190.625241] rtl8192cu: Board Type 0
  Feb 21 07:17:03 orin kernel: [  190.626355] rtl_usb: rx_max_size 15360, 
rx_urb_num 8, in_ep 1
  Feb 21 07:17:03 orin kernel: [  190.626408] rtl8192cu: Loading firmware 
rtlwifi/rtl8192cufw_TMSC.bin
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7698] (wlan0): 
using nl80211 for WiFi device control
  Feb 21 07:17:03 orin kernel: [  190.636625] ieee80211 phy0: Selected rate 
control algorithm 'rtl_rc'
  Feb 21 07:17:03 orin kernel: [  190.637211] usbcore: registered new interface 
driver rtl8192cu
  Feb 21 07:17:03 orin systemd[1]: Starting Load/Save RF Kill Switch Status...
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7780] device 
(wlan0): driver supports Access Point (AP) mode
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7798] manager: 
(wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/4)
  Feb 21

[Kernel-packages] [Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

2017-04-11 Thread Axel H.

** Tags removed: verification-failed-xenial
** Tags added: verification-done-xenial

** Changed in: linux (Ubuntu Xenial)
   Status: Confirmed => Fix Committed

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1666421

Title:
  kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic:
  Grub works, entering full disk encryption passphrase works, but when the 
desktop comes up mouse and keyboard (via USB) are dead and the desktop also.

  booting the PC without the stick attached works fine, but as soon as
  it is attached (see syslog) mouse, keyboard and the desktop itself are
  dead (checked by opening terminal and "watch date" - freezes, with
  desktop still visible).

  problem is resolved by booting former kernel 4.4.0-59-generic.

  syslog upon attaching stick 
---
  Feb 21 07:17:02 orin kernel: [  188.998338] usb 8-2: new high-speed USB 
device number 2 using xhci_hcd
  Feb 21 07:17:02 orin kernel: [  189.129674] usb 8-2: New USB device found, 
idVendor=0bda, idProduct=8178
  Feb 21 07:17:02 orin kernel: [  189.129682] usb 8-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Feb 21 07:17:02 orin kernel: [  189.129687] usb 8-2: Product: USB WLAN
  Feb 21 07:17:02 orin kernel: [  189.129691] usb 8-2: Manufacturer: Realtek
  Feb 21 07:17:02 orin kernel: [  189.129694] usb 8-2: SerialNumber: 
00e04c01
  Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: 
"/sys/devices/pci:00/:00:10.1/usb8/8-2"
  Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device
  Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service 
name='org.freedesktop.UDisks2' unit='udisks2.service'
  Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager...
  Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting
  Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 
'org.freedesktop.UDisks2'
  Feb 21 07:17:02 orin systemd[1]: Started Disk Manager.
  Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 
on the system message bus
  Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive
  Feb 21 07:17:03 orin kernel: [  190.200286] cfg80211: World regulatory domain 
updated:
  Feb 21 07:17:03 orin kernel: [  190.200294] cfg80211:  DFS Master region: 
unset
  Feb 21 07:17:03 orin kernel: [  190.200297] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Feb 21 07:17:03 orin kernel: [  190.200303] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200308] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200312] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200317] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200321] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200325] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200329] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200333] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.223081] rtl8192cu: Chip version 0x11
  Feb 21 07:17:03 orin kernel: [  190.625235] rtl8192cu: MAC address: 
14:cc:20:10:43:98
  Feb 21 07:17:03 orin kernel: [  190.625241] rtl8192cu: Board Type 0
  Feb 21 07:17:03 orin kernel: [  190.626355] rtl_usb: rx_max_size 15360, 
rx_urb_num 8, in_ep 1
  Feb 21 07:17:03 orin kernel: [  190.626408] rtl8192cu: Loading firmware 
rtlwifi/rtl8192cufw_TMSC.bin
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7698] (wlan0): 
using nl80211 for WiFi device control
  Feb 21 07:17:03 orin kernel: [  190.636625] ieee80211 phy0: Selected rate 
control algorithm 'rtl_rc'
  Feb 21 07:17:03 orin kernel: [  190.637211] usbcore: registered new interface 
driver rtl8192cu
  Feb 21 07:17:03 orin systemd[1]: Starting Load/Save RF Kill Switch Status...
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7780] device 
(wlan0): driver supports Access Point (AP) mode
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7798] manager:

[Kernel-packages] [Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

2017-04-07 Thread Axel H.

@jsalisbury

There is no new Kernel in xenial-proposed to test.
Your proposed fix in Kernel 4.4.0-69 did work and solve the issue, but this fix 
was removed with Kernel 4.4.0-70 and it is broken again since then.

Even though you had committed a fix, it is now, for unknown reasons,
removed and the status "Fix committed" is simply false.

** Changed in: linux (Ubuntu Xenial)
   Status: Fix Committed => Confirmed

** Changed in: linux (Ubuntu)
   Status: Fix Committed => 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/1666421

Title:
  kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic:
  Grub works, entering full disk encryption passphrase works, but when the 
desktop comes up mouse and keyboard (via USB) are dead and the desktop also.

  booting the PC without the stick attached works fine, but as soon as
  it is attached (see syslog) mouse, keyboard and the desktop itself are
  dead (checked by opening terminal and "watch date" - freezes, with
  desktop still visible).

  problem is resolved by booting former kernel 4.4.0-59-generic.

  syslog upon attaching stick 
---
  Feb 21 07:17:02 orin kernel: [  188.998338] usb 8-2: new high-speed USB 
device number 2 using xhci_hcd
  Feb 21 07:17:02 orin kernel: [  189.129674] usb 8-2: New USB device found, 
idVendor=0bda, idProduct=8178
  Feb 21 07:17:02 orin kernel: [  189.129682] usb 8-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Feb 21 07:17:02 orin kernel: [  189.129687] usb 8-2: Product: USB WLAN
  Feb 21 07:17:02 orin kernel: [  189.129691] usb 8-2: Manufacturer: Realtek
  Feb 21 07:17:02 orin kernel: [  189.129694] usb 8-2: SerialNumber: 
00e04c01
  Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: 
"/sys/devices/pci:00/:00:10.1/usb8/8-2"
  Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device
  Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service 
name='org.freedesktop.UDisks2' unit='udisks2.service'
  Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager...
  Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting
  Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 
'org.freedesktop.UDisks2'
  Feb 21 07:17:02 orin systemd[1]: Started Disk Manager.
  Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 
on the system message bus
  Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive
  Feb 21 07:17:03 orin kernel: [  190.200286] cfg80211: World regulatory domain 
updated:
  Feb 21 07:17:03 orin kernel: [  190.200294] cfg80211:  DFS Master region: 
unset
  Feb 21 07:17:03 orin kernel: [  190.200297] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Feb 21 07:17:03 orin kernel: [  190.200303] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200308] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200312] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200317] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200321] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200325] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200329] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200333] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.223081] rtl8192cu: Chip version 0x11
  Feb 21 07:17:03 orin kernel: [  190.625235] rtl8192cu: MAC address: 
14:cc:20:10:43:98
  Feb 21 07:17:03 orin kernel: [  190.625241] rtl8192cu: Board Type 0
  Feb 21 07:17:03 orin kernel: [  190.626355] rtl_usb: rx_max_size 15360, 
rx_urb_num 8, in_ep 1
  Feb 21 07:17:03 orin kernel: [  190.626408] rtl8192cu: Loading firmware 
rtlwifi/rtl8192cufw_TMSC.bin
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7698] (wlan0): 
using nl80211 for WiFi device control
  Feb 21 07:17:03 orin kernel: [  190.636625] ieee80211 phy0: Selected rate 
control algorithm 'rtl_rc'
  Feb 21 07:17:03 orin kernel: [  190.637211] usbcore: registered new interface 
driver rtl8192cu
  Feb 21 07:17:03 orin systemd[1]:

[Kernel-packages] [Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

2017-03-28 Thread Axel H.

Confim:

4.4.0-69 worked
4.4.0-70 broken again in Xenial

** Tags removed: verification-needed-xenial
** Tags added: verification-failed-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/1666421

Title:
  kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic:
  Grub works, entering full disk encryption passphrase works, but when the 
desktop comes up mouse and keyboard (via USB) are dead and the desktop also.

  booting the PC without the stick attached works fine, but as soon as
  it is attached (see syslog) mouse, keyboard and the desktop itself are
  dead (checked by opening terminal and "watch date" - freezes, with
  desktop still visible).

  problem is resolved by booting former kernel 4.4.0-59-generic.

  syslog upon attaching stick 
---
  Feb 21 07:17:02 orin kernel: [  188.998338] usb 8-2: new high-speed USB 
device number 2 using xhci_hcd
  Feb 21 07:17:02 orin kernel: [  189.129674] usb 8-2: New USB device found, 
idVendor=0bda, idProduct=8178
  Feb 21 07:17:02 orin kernel: [  189.129682] usb 8-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Feb 21 07:17:02 orin kernel: [  189.129687] usb 8-2: Product: USB WLAN
  Feb 21 07:17:02 orin kernel: [  189.129691] usb 8-2: Manufacturer: Realtek
  Feb 21 07:17:02 orin kernel: [  189.129694] usb 8-2: SerialNumber: 
00e04c01
  Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: 
"/sys/devices/pci:00/:00:10.1/usb8/8-2"
  Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device
  Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service 
name='org.freedesktop.UDisks2' unit='udisks2.service'
  Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager...
  Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting
  Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 
'org.freedesktop.UDisks2'
  Feb 21 07:17:02 orin systemd[1]: Started Disk Manager.
  Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 
on the system message bus
  Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive
  Feb 21 07:17:03 orin kernel: [  190.200286] cfg80211: World regulatory domain 
updated:
  Feb 21 07:17:03 orin kernel: [  190.200294] cfg80211:  DFS Master region: 
unset
  Feb 21 07:17:03 orin kernel: [  190.200297] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Feb 21 07:17:03 orin kernel: [  190.200303] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200308] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200312] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200317] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200321] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200325] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200329] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200333] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.223081] rtl8192cu: Chip version 0x11
  Feb 21 07:17:03 orin kernel: [  190.625235] rtl8192cu: MAC address: 
14:cc:20:10:43:98
  Feb 21 07:17:03 orin kernel: [  190.625241] rtl8192cu: Board Type 0
  Feb 21 07:17:03 orin kernel: [  190.626355] rtl_usb: rx_max_size 15360, 
rx_urb_num 8, in_ep 1
  Feb 21 07:17:03 orin kernel: [  190.626408] rtl8192cu: Loading firmware 
rtlwifi/rtl8192cufw_TMSC.bin
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7698] (wlan0): 
using nl80211 for WiFi device control
  Feb 21 07:17:03 orin kernel: [  190.636625] ieee80211 phy0: Selected rate 
control algorithm 'rtl_rc'
  Feb 21 07:17:03 orin kernel: [  190.637211] usbcore: registered new interface 
driver rtl8192cu
  Feb 21 07:17:03 orin systemd[1]: Starting Load/Save RF Kill Switch Status...
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7780] device 
(wlan0): driver supports Access Point (AP) mode
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7798] manager: 
(wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/4)
  Feb 21 07:17:03 orin

[Kernel-packages] [Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

2017-03-21 Thread Axel H.

Proposed fix works for xenial

** Tags removed: verification-needed-xenial
** Tags added: verification-done-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/1666421

Title:
  kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic:
  Grub works, entering full disk encryption passphrase works, but when the 
desktop comes up mouse and keyboard (via USB) are dead and the desktop also.

  booting the PC without the stick attached works fine, but as soon as
  it is attached (see syslog) mouse, keyboard and the desktop itself are
  dead (checked by opening terminal and "watch date" - freezes, with
  desktop still visible).

  problem is resolved by booting former kernel 4.4.0-59-generic.

  syslog upon attaching stick 
---
  Feb 21 07:17:02 orin kernel: [  188.998338] usb 8-2: new high-speed USB 
device number 2 using xhci_hcd
  Feb 21 07:17:02 orin kernel: [  189.129674] usb 8-2: New USB device found, 
idVendor=0bda, idProduct=8178
  Feb 21 07:17:02 orin kernel: [  189.129682] usb 8-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Feb 21 07:17:02 orin kernel: [  189.129687] usb 8-2: Product: USB WLAN
  Feb 21 07:17:02 orin kernel: [  189.129691] usb 8-2: Manufacturer: Realtek
  Feb 21 07:17:02 orin kernel: [  189.129694] usb 8-2: SerialNumber: 
00e04c01
  Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: 
"/sys/devices/pci:00/:00:10.1/usb8/8-2"
  Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device
  Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service 
name='org.freedesktop.UDisks2' unit='udisks2.service'
  Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager...
  Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting
  Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 
'org.freedesktop.UDisks2'
  Feb 21 07:17:02 orin systemd[1]: Started Disk Manager.
  Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 
on the system message bus
  Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive
  Feb 21 07:17:03 orin kernel: [  190.200286] cfg80211: World regulatory domain 
updated:
  Feb 21 07:17:03 orin kernel: [  190.200294] cfg80211:  DFS Master region: 
unset
  Feb 21 07:17:03 orin kernel: [  190.200297] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Feb 21 07:17:03 orin kernel: [  190.200303] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200308] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200312] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200317] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200321] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200325] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200329] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200333] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.223081] rtl8192cu: Chip version 0x11
  Feb 21 07:17:03 orin kernel: [  190.625235] rtl8192cu: MAC address: 
14:cc:20:10:43:98
  Feb 21 07:17:03 orin kernel: [  190.625241] rtl8192cu: Board Type 0
  Feb 21 07:17:03 orin kernel: [  190.626355] rtl_usb: rx_max_size 15360, 
rx_urb_num 8, in_ep 1
  Feb 21 07:17:03 orin kernel: [  190.626408] rtl8192cu: Loading firmware 
rtlwifi/rtl8192cufw_TMSC.bin
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7698] (wlan0): 
using nl80211 for WiFi device control
  Feb 21 07:17:03 orin kernel: [  190.636625] ieee80211 phy0: Selected rate 
control algorithm 'rtl_rc'
  Feb 21 07:17:03 orin kernel: [  190.637211] usbcore: registered new interface 
driver rtl8192cu
  Feb 21 07:17:03 orin systemd[1]: Starting Load/Save RF Kill Switch Status...
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7780] device 
(wlan0): driver supports Access Point (AP) mode
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7798] manager: 
(wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/4)
  Feb 21 07:17:03 orin kernel: [  190.648972]

[Kernel-packages] [Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

2017-03-02 Thread Axel H.

Still exists with 4.4.0-65 in Ubuntu 16.04 here as well

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

Title:
  kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic:
  Grub works, entering full disk encryption passphrase works, but when the 
desktop comes up mouse and keyboard (via USB) are dead and the desktop also.

  booting the PC without the stick attached works fine, but as soon as
  it is attached (see syslog) mouse, keyboard and the desktop itself are
  dead (checked by opening terminal and "watch date" - freezes, with
  desktop still visible).

  problem is resolved by booting former kernel 4.4.0-59-generic.

  syslog upon attaching stick 
---
  Feb 21 07:17:02 orin kernel: [  188.998338] usb 8-2: new high-speed USB 
device number 2 using xhci_hcd
  Feb 21 07:17:02 orin kernel: [  189.129674] usb 8-2: New USB device found, 
idVendor=0bda, idProduct=8178
  Feb 21 07:17:02 orin kernel: [  189.129682] usb 8-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Feb 21 07:17:02 orin kernel: [  189.129687] usb 8-2: Product: USB WLAN
  Feb 21 07:17:02 orin kernel: [  189.129691] usb 8-2: Manufacturer: Realtek
  Feb 21 07:17:02 orin kernel: [  189.129694] usb 8-2: SerialNumber: 
00e04c01
  Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: 
"/sys/devices/pci:00/:00:10.1/usb8/8-2"
  Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device
  Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service 
name='org.freedesktop.UDisks2' unit='udisks2.service'
  Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager...
  Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting
  Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 
'org.freedesktop.UDisks2'
  Feb 21 07:17:02 orin systemd[1]: Started Disk Manager.
  Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 
on the system message bus
  Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive
  Feb 21 07:17:03 orin kernel: [  190.200286] cfg80211: World regulatory domain 
updated:
  Feb 21 07:17:03 orin kernel: [  190.200294] cfg80211:  DFS Master region: 
unset
  Feb 21 07:17:03 orin kernel: [  190.200297] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Feb 21 07:17:03 orin kernel: [  190.200303] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200308] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200312] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200317] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200321] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200325] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200329] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200333] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.223081] rtl8192cu: Chip version 0x11
  Feb 21 07:17:03 orin kernel: [  190.625235] rtl8192cu: MAC address: 
14:cc:20:10:43:98
  Feb 21 07:17:03 orin kernel: [  190.625241] rtl8192cu: Board Type 0
  Feb 21 07:17:03 orin kernel: [  190.626355] rtl_usb: rx_max_size 15360, 
rx_urb_num 8, in_ep 1
  Feb 21 07:17:03 orin kernel: [  190.626408] rtl8192cu: Loading firmware 
rtlwifi/rtl8192cufw_TMSC.bin
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7698] (wlan0): 
using nl80211 for WiFi device control
  Feb 21 07:17:03 orin kernel: [  190.636625] ieee80211 phy0: Selected rate 
control algorithm 'rtl_rc'
  Feb 21 07:17:03 orin kernel: [  190.637211] usbcore: registered new interface 
driver rtl8192cu
  Feb 21 07:17:03 orin systemd[1]: Starting Load/Save RF Kill Switch Status...
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7780] device 
(wlan0): driver supports Access Point (AP) mode
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7798] manager: 
(wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/4)
  Feb 21 07:17:03 orin kernel: [  190.648972] usbcore: registered new interface 
driver rtl8xxxu
  Feb 21

[Kernel-packages] [Bug 1669577] Re: Kernel 4.4.0-64-generic freezes on gui

2017-03-02 Thread Axel H.

*** This bug is a duplicate of bug 1666421 ***
https://bugs.launchpad.net/bugs/1666421

** This bug has been marked a duplicate of bug 1666421
   kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

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

Title:
  Kernel 4.4.0-64-generic freezes on gui

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating Ubuntu with apt which includes a kernel update to
  4.4.0-64-generic, the system freezes shortly after it boots into the
  gui. There are no issues booting with kernel 4.4.0-62

  It might be caused by WiFi. I have an USB wifi module. When i remove
  it, Ubuntu with kernel 4.4.0-64 starts without freezing. As soon as I
  plug it in the system Freezes instantly.

  It seems theat I'm not the only one experiencing freezes with this new
  kernel update. Maybe the security patch is breaking something
  essential:
  http://askubuntu.com/questions/886374/ubuntu-16-04-kernel-4-4-0-64
  -generic-freezes-after-login-screen/886799

  Unfortunately Launchpad does not allow to file bugs for Ubuntu
  directly. It only redirects to wiki page which assumes the OS is still
  in operational state - major fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1669577/+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 1562076] Re: Ubuntu freezes a few seconds after plugin a screen

2016-06-26 Thread Axel Leroy

Hello,

Sorry for the absence of update for the past month, I finally had time
to try Linux 4.4.8 and I can confirm it fixes the freezes.

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

Title:
  Ubuntu freezes a few seconds after plugin a screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I'm running the latest beta of Ubuntu 16.04 Xenial on an ASUS UX303LA (Intel 
i5 6200U, Intel HD 520) and each time I plug a screen, using either HDMI or 
Mini DisplayPort, my laptop freezes after a few seconds.
  Alt + Function keys doesn't work, sound stops and I'm forced to shutdown the 
computer by long-pressing its Power button.

  I attached syslog, kern.log and Xorg.0.log for further information.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-15-generic 4.4.0-15.31
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  axel   1632 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Mar 25 17:34:54 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2acdb9a2-2923-4550-9019-32e79d136c4d
  InstallationDate: Installed on 2016-02-25 (29 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57cb Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX303UA
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed 
root=UUID=de727ab1-db17-453b-a371-4a143f37dcad ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-02-25 (28 days ago)
  dmi.bios.date: 08/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303UA.202
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303UA.202:bd08/27/2015:svnASUSTeKCOMPUTERINC.:pnUX303UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX303UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1562076/+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 1510344] Re: Keyboard Backlight Turns on at boot

2016-04-24 Thread Axel G. Rossberg

If it annoys me too much, I do three times

echo 0|sudo tee /sys/class/leds/dell\:\:kbd_backlight/brightness

This tends to keep the backlight off for a while.

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

Title:
  Keyboard Backlight Turns on at boot

Status in Dell Sputnik:
  Confirmed
Status in One Hundred Papercuts:
  Confirmed
Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System: Dell XPS 13 9343

  Action: Boot computer

  Expected Behavior: Keyboard backlight would be off when computer is
  booted

  Actual Behavior: Keyboard backlight is on at boot

  This did not happen with Ubuntu 15.04

  There are new files in Ubuntu 15.10 -
  /sys/class/leds/dell::kbd_backlight$

  cat stop_timeout
  60s

   cat start_triggers 
  +keyboard +touchpad

  cat trigger 
  [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full 
BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 
rfkill0

  cat brightness 
  2

  ---

  Unsure if these files are important, but included in the report

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.1.0-2-generic 4.1.0-2.2
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2488 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2488 F pulseaudio
  CasperVersion: 1.362
  CurrentDesktop: Unity
  Date: Tue Oct 27 01:29:47 2015
  IwConfig:
   enx00249b0981e3  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-2-generic N/A
   linux-backports-modules-4.1.0-2-generic  N/A
   linux-firmware   1.145
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+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 1562076] Re: Ubuntu freezes a few seconds after plugin a screen

2016-04-23 Thread Axel "Black Eco" Leroy

I did a clean install of the final Xenial release to rule out any faulty 
configuration files and the issue still happens.
Something to note is that when I boot with a second screen plugged in it does 
not freezes until I am on the desktop.

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

Title:
  Ubuntu freezes a few seconds after plugin a screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I'm running the latest beta of Ubuntu 16.04 Xenial on an ASUS UX303LA (Intel 
i5 6200U, Intel HD 520) and each time I plug a screen, using either HDMI or 
Mini DisplayPort, my laptop freezes after a few seconds.
  Alt + Function keys doesn't work, sound stops and I'm forced to shutdown the 
computer by long-pressing its Power button.

  I attached syslog, kern.log and Xorg.0.log for further information.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-15-generic 4.4.0-15.31
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  axel   1632 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Mar 25 17:34:54 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2acdb9a2-2923-4550-9019-32e79d136c4d
  InstallationDate: Installed on 2016-02-25 (29 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57cb Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX303UA
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed 
root=UUID=de727ab1-db17-453b-a371-4a143f37dcad ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-02-25 (28 days ago)
  dmi.bios.date: 08/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303UA.202
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303UA.202:bd08/27/2015:svnASUSTeKCOMPUTERINC.:pnUX303UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX303UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1562076/+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 1562076] Re: Ubuntu freezes a few seconds after plugin a screen

2016-03-28 Thread Axel "Black Eco" Leroy

I do not know if an update brought this issue because I did not plugged any 
monitors since I updated from wily. 
I installed kernel 4.5 but the bug is still present. I wonder if the issue 
comes from Xorg instead of the kernel.

** Tags added: kernel-bug-exists-upstream

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

Title:
  Ubuntu freezes a few seconds after plugin a screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I'm running the latest beta of Ubuntu 16.04 Xenial on an ASUS UX303LA (Intel 
i5 6200U, Intel HD 520) and each time I plug a screen, using either HDMI or 
Mini DisplayPort, my laptop freezes after a few seconds.
  Alt + Function keys doesn't work, sound stops and I'm forced to shutdown the 
computer by long-pressing its Power button.

  I attached syslog, kern.log and Xorg.0.log for further information.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-15-generic 4.4.0-15.31
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  axel   1632 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Mar 25 17:34:54 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2acdb9a2-2923-4550-9019-32e79d136c4d
  InstallationDate: Installed on 2016-02-25 (29 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57cb Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX303UA
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed 
root=UUID=de727ab1-db17-453b-a371-4a143f37dcad ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-02-25 (28 days ago)
  dmi.bios.date: 08/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303UA.202
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303UA.202:bd08/27/2015:svnASUSTeKCOMPUTERINC.:pnUX303UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX303UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1562076/+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 1562076] Re: Ubuntu freezes a few seconds after plugin a screen

2016-03-25 Thread Axel "Black Eco" Leroy

** Attachment added: "kern.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1562076/+attachment/4611427/+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/1562076

Title:
  Ubuntu freezes a few seconds after plugin a screen

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  I'm running the latest beta of Ubuntu 16.04 Xenial on an ASUS UX303LA (Intel 
i5 6200U, Intel HD 520) and each time I plug a screen, using either HDMI or 
Mini DisplayPort, my laptop freezes after a few seconds.
  Alt + Function keys doesn't work, sound stops and I'm forced to shutdown the 
computer by long-pressing its Power button.

  I attached syslog, kern.log and Xorg.0.log for further information.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-15-generic 4.4.0-15.31
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  axel   1632 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Mar 25 17:34:54 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2acdb9a2-2923-4550-9019-32e79d136c4d
  InstallationDate: Installed on 2016-02-25 (29 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57cb Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX303UA
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed 
root=UUID=de727ab1-db17-453b-a371-4a143f37dcad ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-02-25 (28 days ago)
  dmi.bios.date: 08/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303UA.202
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303UA.202:bd08/27/2015:svnASUSTeKCOMPUTERINC.:pnUX303UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX303UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1562076/+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 1562076] [NEW] Ubuntu freezes a few seconds after plugin a screen

2016-03-25 Thread Axel "Black Eco" Leroy

Public bug reported:

Hello,

I'm running the latest beta of Ubuntu 16.04 Xenial on an ASUS UX303LA (Intel i5 
6200U, Intel HD 520) and each time I plug a screen, using either HDMI or Mini 
DisplayPort, my laptop freezes after a few seconds.
Alt + Function keys doesn't work, sound stops and I'm forced to shutdown the 
computer by long-pressing its Power button.

I attached syslog, kern.log and Xorg.0.log for further information.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-15-generic 4.4.0-15.31
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  axel   1632 F pulseaudio
CurrentDesktop: GNOME
Date: Fri Mar 25 17:34:54 2016
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=2acdb9a2-2923-4550-9019-32e79d136c4d
InstallationDate: Installed on 2016-02-25 (29 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 0bda:57cb Realtek Semiconductor Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX303UA
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed 
root=UUID=de727ab1-db17-453b-a371-4a143f37dcad ro noprompt persistent quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-15-generic N/A
 linux-backports-modules-4.4.0-15-generic  N/A
 linux-firmware1.157
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-02-25 (28 days ago)
dmi.bios.date: 08/27/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX303UA.202
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX303UA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303UA.202:bd08/27/2015:svnASUSTeKCOMPUTERINC.:pnUX303UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX303UA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug xenial

** Attachment added: "syslog"
   https://bugs.launchpad.net/bugs/1562076/+attachment/4611412/+files/syslog

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

Title:
  Ubuntu freezes a few seconds after plugin a screen

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  I'm running the latest beta of Ubuntu 16.04 Xenial on an ASUS UX303LA (Intel 
i5 6200U, Intel HD 520) and each time I plug a screen, using either HDMI or 
Mini DisplayPort, my laptop freezes after a few seconds.
  Alt + Function keys doesn't work, sound stops and I'm forced to shutdown the 
computer by long-pressing its Power button.

  I attached syslog, kern.log and Xorg.0.log for further information.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-15-generic 4.4.0-15.31
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  axel   1632 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Mar 25 17:34:54 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2acdb9a2-2923-4550-9019-32e79d136c4d
  InstallationDate: Installed on 2016-02-25 (29 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57cb Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX303UA
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed 
root=UUID=de727ab1-db17-453b-a371-4a143f37dcad ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-02-25 (28 days ago)
  dmi.bios.date: 08/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303UA.202
  dmi.board.a

[Kernel-packages] [Bug 1528976] [NEW] LXDE freeze temporary

2015-12-23 Thread axel

Public bug reported:

I just install Lubuntu 1404 LTE om my desktop.
When i open some application, YouTube in Firefox or just spotify-client the GUI 
freeze. I can use the mouse, but it recognize only the clicks in the window of 
the application opened the LXDE menu and the resize/close are not working (they 
are obviously out of the application). I opened a terminal with the keyboard 
shortcut (ctrl+alt+T) and check if there is a frozen process with top, but 
everything is normal (low cpu usage). When i open the terminal i remain stucked 
in the terminal application. I can jump from one application to other with the 
keyboard shortcuts and use them, but not use LXDE until i close all the 
application (I'm killing them with the terminal). Two or tree seconds after 
that LXDE works find...

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


** Tags: gui lubuntu lxde

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

Title:
  LXDE freeze temporary

Status in linux package in Ubuntu:
  New

Bug description:
  I just install Lubuntu 1404 LTE om my desktop.
  When i open some application, YouTube in Firefox or just spotify-client the 
GUI freeze. I can use the mouse, but it recognize only the clicks in the window 
of the application opened the LXDE menu and the resize/close are not working 
(they are obviously out of the application). I opened a terminal with the 
keyboard shortcut (ctrl+alt+T) and check if there is a frozen process with top, 
but everything is normal (low cpu usage). When i open the terminal i remain 
stucked in the terminal application. I can jump from one application to other 
with the keyboard shortcuts and use them, but not use LXDE until i close all 
the application (I'm killing them with the terminal). Two or tree seconds after 
that LXDE works find...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1528976/+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 1519298] Re: btusb.ko preferred over ath3k.ko for Atheros AR3012 Bluetooth 4.0

2015-11-26 Thread Axel G. Rossberg

[noting happens]
  while, if I remove the generic module
  # modprobe -r btusb
  the entire bluetooth architechture breaks down, my headphone goes silent, and 
sound now comes out of the built-in speakers.

  I'd hope that if ath3k was actually used, my bluetooth would be less
  buggy. What can I do?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  axel   3114 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Nov 24 10:20:54 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  HibernationDevice: RESUME=UUID=39fd7402-c630-4457-b2aa-6cfd16a1f97a
  InstallationDate: Installed on 2013-08-01 (844 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  MachineType: Dell Inc. Dell System XPS L322X
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=ff211774-a9b8-42ab-896c-c542fb10c871 ro quiet splash pcie_aspm=force 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L322X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1519298/+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 1519298] [NEW] btusb.ko preferred over ath3k.ko for Atheros AR3012 Bluetooth 4.0

2015-11-24 Thread Axel G. Rossberg

Public bug reported:

Since upgrading from 14.10 to 15.04 and then 15.10, my Bluetooth is
buggy (e.g., it does not automatically connect to my headphone, needs
manual "turning on" in the indicator applet and some good luck to do
this).

My bluetooth device is

# lsusb | grep Blue
Bus 004 Device 014: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth 
4.0

I think this device should be handled by ath3k.ko:
# modinfo /lib/modules/$(uname -r)/kernel/drivers/bluetooth/ath3k.ko| grep 3004
alias:  usb:v0CF3p3004d*dc*dsc*dp*ic*isc*ip*in*
alias:  usb:v04CAp3004d*dc*dsc*dp*ic*isc*ip*in*

# uname -r
4.2.0-18-generic

Indeed, ath3k.ko is loaded

# lsmod | grep 'ath3k\|btusb'
ath3k  20480  0
btusb  45056  0
btrtl  16384  1 btusb
btbcm  16384  1 btusb
btintel16384  1 btusb
bluetooth 516096  48 bnep,ath3k,btbcm,btrtl,btusb,rfcomm,btintel

However, if I remove ath3k, bluetooth keeps streaming sound to my headphone:
# modprobe -r ath3k
[noting happens]
while, if I remove the generic module
# modprobe -r btusb
the entire bluetooth architechture breaks down, my headphone goes silent, and 
sound now comes out of the built-in speakers.

I'd hope that if ath3k was actually used, my bluetooth would be less
buggy. What can I do?

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-18-generic 4.2.0-18.22
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  axel   3114 F pulseaudio
CurrentDesktop: Unity
Date: Tue Nov 24 10:20:54 2015
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-precise-amd64-20120703-2
HibernationDevice: RESUME=UUID=39fd7402-c630-4457-b2aa-6cfd16a1f97a
InstallationDate: Installed on 2013-08-01 (844 days ago)
InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
MachineType: Dell Inc. Dell System XPS L322X
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=ff211774-a9b8-42ab-896c-c542fb10c871 ro quiet splash pcie_aspm=force 
vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-18-generic N/A
 linux-backports-modules-4.2.0-18-generic  N/A
 linux-firmware1.149.2
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/18/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0PJHXN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Dell System XPS L322X
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug wily

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

Title:
  btusb.ko preferred over ath3k.ko for Atheros  AR3012 Bluetooth 4.0

Status in linux package in Ubuntu:
  New

Bug description:
  Since upgrading from 14.10 to 15.04 and then 15.10, my Bluetooth is
  buggy (e.g., it does not automatically connect to my headphone, needs
  manual "turning on" in the indicator applet and some good luck to do
  this).

  My bluetooth device is

  # lsusb | grep Blue
  Bus 004 Device 014: ID 0cf3:3004 Atheros Communications, Inc. AR3012 
Bluetooth 4.0

  I think this device should be handled by ath3k.ko:
  # modinfo /lib/modules/$(uname -r)/kernel/drivers/bluetooth/ath3k.ko| grep 
3004
  alias:  usb:v0CF3p3004d*dc*dsc*dp*ic*isc*ip*in*
  alias:  usb:v04CAp3004d*dc*dsc*dp*ic*isc*ip*in*

  # uname -r
  4.2.0-18-generic

  Indeed, ath3k.ko is loaded

  # lsmod | grep 'ath3k\|btusb'
  ath3k  20480  0
  btusb  45056  0
  btrtl  16384  1 btusb
  btbcm  16384  1 btusb
  btintel16384  1 btusb
  bluetooth 516096  48 bnep,ath3k,btbcm,btrtl,btusb,rfcomm,btintel

  However, if I remove ath3k, bluetooth keeps streaming sound to my headphone:
  # modprobe -r ath3k
  [noting happens]
  while, if I remove the generic module
  # modprobe -r btusb
  the entire bluetooth architechture breaks down, my headphone goes silent, and 
sound now comes out of the built-in speakers.

  I'd hope that if ath3k was actually used, my bluetooth would be less
  buggy. What can I do?

  ProblemType: Bug
  DistroRelease:

[Kernel-packages] [Bug 1519298] Re: btusb.ko preferred over ath3k.ko for Atheros AR3012 Bluetooth 4.0

2015-11-24 Thread Axel G. Rossberg

This page https://wireless.wiki.kernel.org/en/users/drivers/ath3k gives
some instructions for making the AR3012 work. My understanding is that
this all built into the recent kernels already, but this might be worth
checking anyway.

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

Title:
  btusb.ko preferred over ath3k.ko for Atheros  AR3012 Bluetooth 4.0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading from 14.10 to 15.04 and then 15.10, my Bluetooth is
  buggy (e.g., it does not automatically connect to my headphone, needs
  manual "turning on" in the indicator applet and some good luck to do
  this).

  My bluetooth device is

  # lsusb | grep Blue
  Bus 004 Device 014: ID 0cf3:3004 Atheros Communications, Inc. AR3012 
Bluetooth 4.0

  I think this device should be handled by ath3k.ko:
  # modinfo /lib/modules/$(uname -r)/kernel/drivers/bluetooth/ath3k.ko| grep 
3004
  alias:  usb:v0CF3p3004d*dc*dsc*dp*ic*isc*ip*in*
  alias:  usb:v04CAp3004d*dc*dsc*dp*ic*isc*ip*in*

  # uname -r
  4.2.0-18-generic

  Indeed, ath3k.ko is loaded

  # lsmod | grep 'ath3k\|btusb'
  ath3k  20480  0
  btusb  45056  0
  btrtl  16384  1 btusb
  btbcm  16384  1 btusb
  btintel16384  1 btusb
  bluetooth 516096  48 bnep,ath3k,btbcm,btrtl,btusb,rfcomm,btintel

  However, if I remove ath3k, bluetooth keeps streaming sound to my headphone:
  # modprobe -r ath3k
  [noting happens]
  while, if I remove the generic module
  # modprobe -r btusb
  the entire bluetooth architechture breaks down, my headphone goes silent, and 
sound now comes out of the built-in speakers.

  I'd hope that if ath3k was actually used, my bluetooth would be less
  buggy. What can I do?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  axel   3114 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Nov 24 10:20:54 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  HibernationDevice: RESUME=UUID=39fd7402-c630-4457-b2aa-6cfd16a1f97a
  InstallationDate: Installed on 2013-08-01 (844 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  MachineType: Dell Inc. Dell System XPS L322X
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=ff211774-a9b8-42ab-896c-c542fb10c871 ro quiet splash pcie_aspm=force 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L322X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1519298/+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 1448519] Re: Logitech K400 cannot type in LUKS passphrase at boot

2015-08-18 Thread Axel Pospischil

Hi,

I had the same problem with a K800 Keyboard from Logitech.

a better way would be to edit the file

/etc/initramfs-tools/modules

and add

hid-logitech-hidpp

there.

Then it is sufficiant to to

sudo update-initramfs -c -k $(uname -r)

for the running kernel (or -k all for all kernels).

Confirmed with Logitech K800, Ubuntu 14.04.3, 3.19.0-26-generic (64bit)

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

Title:
  Logitech K400 cannot type in LUKS passphrase at boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Xubuntu 15.04 (which uses the linux-
  image-3.19.0-15-generic kernel), I can no longer type in my LUKS
  passphrase (or even press Control-Alt-Delete to reboot the machine) at
  boot using my Logitech K400 wireless USB keyboard.

  Thankfully, the linux-image-3.16.0-34-generic kernel (which does not
  suffer from this problem) still existed on my machine from my previous
  Xubuntu 14.10 installation.  So I am using that kernel as a
  workaround:

  1. Boot the computer.
  2. Wait for the BIOS splash screen to pass.
  2. Quickly press the Escape key repeatedly until the GRUB boot menu appears.  
If I don't do this quickly enough, I encounter the LUKS passphrase screen where 
my Logitech K400 wireless USB keyboard does not work.
  3. Press the Down arrow key to choose the second menu item called Advanced 
Ubuntu Options.
  4. Press the Down arrow key several times to choose the menu item called 
linux-image-3.16.0-34-generic.
  5. Press the Enter key.
  6. Now the LUKS passphrase screen will appear where my Logitech K400 wireless 
USB keyboard will work correctly because the linux-image-3.16.0-34-generic 
kernel was booted instead of the problematic linux-image-3.19.0-15-generic 
kernel.

  Please fix the linux-image-3.19.0-15-generic kernel's build recipe to
  include support for the Logitech K400 wireless USB keyboard.

  Thanks for your consideration.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-15-generic 3.19.0-15.15
  ProcVersionSignature: Ubuntu 3.16.0-34.47-generic 3.16.7-ckt8
  Uname: Linux 3.16.0-34-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  manillu1474 F pulseaudio
   /dev/snd/controlC0:  manillu1474 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Apr 25 11:19:01 2015
  HibernationDevice: RESUME=UUID=d26576da-66da-4d47-85de-4cd8782e43c5
  InstallationDate: Installed on 2015-02-28 (55 days ago)
  InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-34-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-34-generic N/A
   linux-backports-modules-3.16.0-34-generic  N/A
   linux-firmware 1.143
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (0 days ago)
  dmi.bios.date: 02/17/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.01
  dmi.board.name: H81M-ITX
  dmi.board.vendor: ASRock
  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.:bvrP2.01:bd02/17/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH81M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1448519/+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 1481621] [NEW] [LENOVO 27326FG] late resume failure

2015-08-05 Thread Axel Hack

Public bug reported:

no

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-57-generic 3.13.0-57.95
ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
Uname: Linux 3.13.0-57-generic x86_64
Annotation: This occured during a previous suspend and prevented it from 
resuming properly.  The resume processing hung very near the end and will have 
appeared to have completed normally.
ApportVersion: 2.14.4-0ubuntu1~ubuntu14.04.1~c42.ppa1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  axel   2111 F pulseaudio
 /dev/snd/controlC0:  axel   2111 F pulseaudio
CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw'
Date: Wed Aug  5 09:28:40 2015
DuplicateSignature: late resume:LENOVO 27326FG:7YET71WW (3.01 )
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: late resume
HibernationDevice: RESUME=UUID=c67a594d-f738-48ef-bf05-a3ed1a999c63
InstallationDate: Installed on 2014-08-07 (362 days ago)
InstallationMedia: Lubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
InterpreterPath: /usr/bin/python3.4
MachineType: LENOVO 27326FG
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-57-generic 
root=UUID=a497e91b-9c74-4bf5-bdcf-728154b0d3c1 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-57-generic N/A
 linux-backports-modules-3.13.0-57-generic  N/A
 linux-firmware 1.127.13
SourcePackage: linux
Title: [LENOVO 27326FG] late resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 05/14/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 7YET71WW (3.01 )
dmi.board.name: 27326FG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr7YET71WW(3.01):bd05/14/2009:svnLENOVO:pn27326FG:pvrThinkPadR500:rvnLENOVO:rn27326FG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 27326FG
dmi.product.version: ThinkPad R500
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-kerneloops resume resume-late-hang suspend 
third-party-packages trusty

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

Title:
  [LENOVO 27326FG] late resume failure

Status in linux package in Ubuntu:
  New

Bug description:
  no

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-57-generic 3.13.0-57.95
  ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
  Uname: Linux 3.13.0-57-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.  The resume processing hung very near the end and will have 
appeared to have completed normally.
  ApportVersion: 2.14.4-0ubuntu1~ubuntu14.04.1~c42.ppa1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  axel   2111 F pulseaudio
   /dev/snd/controlC0:  axel   2111 F pulseaudio
  CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw'
  Date: Wed Aug  5 09:28:40 2015
  DuplicateSignature: late resume:LENOVO 27326FG:7YET71WW (3.01 )
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: late resume
  HibernationDevice: RESUME=UUID=c67a594d-f738-48ef-bf05-a3ed1a999c63
  InstallationDate: Installed on 2014-08-07 (362 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  InterpreterPath: /usr/bin/python3.4
  MachineType: LENOVO 27326FG
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-57-generic 
root=UUID=a497e91b-9c74-4bf5-bdcf-728154b0d3c1 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-57-generic N/A
   linux-backports-modules-3.13.0-57-generic  N/A
   linux-firmware 1.127.13
  SourcePackage: linux
  Title: [LENOVO 27326FG] late resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 05/14/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7YET71WW (3.01 )
  dmi.board.name: 27326FG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available

[Kernel-packages] [Bug 1394368] Re: Bluetooth with AR9462 doesn't work (New ID /Firmware)

2015-05-19 Thread Axel

Hi, I've followed all the steps and bluetooth is still idle. I've set up
the second kernel. Any help? Thanks!

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

Title:
  Bluetooth with AR9462 doesn't work (New ID /Firmware)

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  This is (kind of) a duplicate of:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1024884
  (please read)

  I can't use Bluetooth with my AR9462 WLAN/BT-Combo.
  In the link above, it has been fixed, but not for my Adapter ID/Firmware:

  System:
  Ubuntu 14.10 utopic 64bit - 3.16.0-24-generic x86_64

  lspci -nnk
  02:00.0 Network controller [0280]: Qualcomm Atheros AR9462
  Wireless Network Adapter [168c:0034] (rev 01)
   Subsystem: Lite-On Communications Inc Device [11ad:0802]
   Kernel driver in use: ath9k

  lsusb (identified Bluetooth Device)
  Bus 002 Device 003: ID 04ca:300d Lite-On Technology Corp.

  ath9k.conf
  options ath9k btcoex_enable=1

  The 04ca:300d ID is not in the Kernel, so i added it via dkms.

  I took ath3k.c and btusb.c out of the 3.16.0-24-generic source files
  and changed them:

  diff -urN ./linux-3.16.0/drivers/bluetooth/ath3k.c 
/usr/src/ar9462-1.5.1/ath3k.c
  --- ./linux-3.16.0/drivers/bluetooth/ath3k.c  2014-08-04 00:25:02.0 
+0200
  +++ /usr/src/ar9462-1.5.1/ath3k.c 2014-11-19 21:12:46.646265890 +0100
  @@ -85,6 +85,7 @@
    { USB_DEVICE(0x04CA, 0x3007) },
    { USB_DEVICE(0x04CA, 0x3008) },
    { USB_DEVICE(0x04CA, 0x300b) },
  + { USB_DEVICE(0x04CA, 0x300d) },
    { USB_DEVICE(0x0930, 0x0219) },
    { USB_DEVICE(0x0930, 0x0220) },
    { USB_DEVICE(0x0b05, 0x17d0) },
  @@ -134,6 +135,7 @@
    { USB_DEVICE(0x04ca, 0x3007), .driver_info = BTUSB_ATH3012 },
    { USB_DEVICE(0x04ca, 0x3008), .driver_info = BTUSB_ATH3012 },
    { USB_DEVICE(0x04ca, 0x300b), .driver_info = BTUSB_ATH3012 },
  + { USB_DEVICE(0x04ca, 0x300d), .driver_info = BTUSB_ATH3012 },
    { USB_DEVICE(0x0930, 0x0219), .driver_info = BTUSB_ATH3012 },
    { USB_DEVICE(0x0930, 0x0220), .driver_info = BTUSB_ATH3012 },
    { USB_DEVICE(0x0b05, 0x17d0), .driver_info = BTUSB_ATH3012 },

  diff -urN ./linux-3.16.0/drivers/bluetooth/btusb.c 
/usr/src/ar9462-1.5.1/btusb.c
  --- ./linux-3.16.0/drivers/bluetooth/btusb.c  2014-08-04 00:25:02.0 
+0200
  +++ /usr/src/ar9462-1.5.1/btusb.c 2014-11-19 21:12:46.646265890 +0100
  @@ -157,6 +157,7 @@
    { USB_DEVICE(0x04ca, 0x3007), .driver_info = BTUSB_ATH3012 },
    { USB_DEVICE(0x04ca, 0x3008), .driver_info = BTUSB_ATH3012 },
    { USB_DEVICE(0x04ca, 0x300b), .driver_info = BTUSB_ATH3012 },
  + { USB_DEVICE(0x04ca, 0x300d), .driver_info = BTUSB_ATH3012 },
    { USB_DEVICE(0x0930, 0x0219), .driver_info = BTUSB_ATH3012 },
    { USB_DEVICE(0x0930, 0x0220), .driver_info = BTUSB_ATH3012 },
    { USB_DEVICE(0x0b05, 0x17d0), .driver_info = BTUSB_ATH3012 },

  sudo dkms add -m ar9462 -v 1.5.1
  sudo dkms build -m ar9462 -v 1.5.1
  sudo dkms install -m ar9462 -v 1.5.1

  (DKMS package in the same style/versioning as in the bug report above)

  dkms status
  ar9462, 1.5.1, 3.16.0-24-generic, x86_64: installed

  Now the new output:

  dmesg | egrep 'ath3|ar3|Bluet'
  [2.787819] Bluetooth: Core ver 2.19
  [2.787833] Bluetooth: HCI device and connection manager initialized
  [2.787839] Bluetooth: HCI socket layer initialized
  [2.787842] Bluetooth: L2CAP socket layer initialized
  [2.787848] Bluetooth: SCO socket layer initialized
  [2.793551] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [2.793554] Bluetooth: BNEP filters: protocol multicast
  [2.793561] Bluetooth: BNEP socket layer initialized
  [3.130779] Bluetooth: Patch file not found ar3k/AthrBT_0x11020100.dfu
  [3.130783] Bluetooth: Loading patch file failed
  [3.130788] ath3k: probe of 2-5:1.0 failed with error -12
  [3.130823] usbcore: registered new interface driver ath3k
  [9.776503] Bluetooth: RFCOMM TTY layer initialized
  [9.776512] Bluetooth: RFCOMM socket layer initialized
  [9.776517] Bluetooth: RFCOMM ver 1.11

  My patch works, but just like in the bug report above, a Firmware file is 
missing:
  AthrBT_0x11020100.dfu

  I found it neither in linux-firmware 
(http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/ar3k)
  nor elsewhere.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1394368/+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 1440618] Re: BUG: unable to handle kernel paging request at 00007f4c3ab447c0

2015-05-08 Thread Axel Beckert

** Bug watch added: Debian Bug tracker #783142
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783142

** Also affects: virtualbox (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783142
   Importance: Unknown
   Status: Unknown

** Bug watch added: Virtualbox Trac #13820
   http://www.virtualbox.org/ticket/13820

** Also affects: virtualbox via
   http://www.virtualbox.org/ticket/13820
   Importance: Unknown
   Status: Unknown

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

Title:
  BUG: unable to handle kernel paging request at 7f4c3ab447c0

Status in Virtualbox:
  Unknown
Status in linux package in Ubuntu:
  Incomplete
Status in virtualbox package in Debian:
  Unknown

Bug description:
  Freeze when i use virtual machine on virtualbox after few minutes

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-12-generic 3.19.0-12.12
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  Annotation: Your system might become unstablenow and might need to be 
restarted.
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lightdm1336 F pulseaudio
futex  1750 F pulseaudio
   /dev/snd/controlC0:  lightdm1336 F pulseaudio
futex  1750 F pulseaudio
  Date: Mon Apr  6 01:02:40 2015
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: 0010:location  location 0xc001d415
  Failure: oops
  HibernationDevice: RESUME=UUID=e929b771-de16-42ca-aca5-f1af14d69c6e
  InstallationDate: Installed on 2015-04-04 (1 days ago)
  InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150224)
  MachineType: LENOVO 20BX000TML
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-12-generic 
root=/dev/mapper/rootvg-rootlv ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at 7f4c3ab447c0
  UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET46WW (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BX000TML
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET46WW(1.11):bd03/02/2015:svnLENOVO:pn20BX000TML:pvrThinkPadT450s:rvnLENOVO:rn20BX000TML:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BX000TML
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/virtualbox/+bug/1440618/+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 1288726] Re: MicMute key on lenovo w510 thinkpad doesn't work

2014-11-16 Thread Axel Pospischil

Hi,

on Ubuntu 14.04 according to this thread:

* http://askubuntu.com/questions/125367/enabling-mic-mute-button-and-
light-on-lenovo-thinkpads

I cannot see
/sys/devices/platform/thinkpad_acpi/leds/tpacpi::micmute/brightness as a
link in /sys/devices/platform/thinkpad_acpi/leds:

 # ls /sys/devices/platform/thinkpad_acpi/leds/tpacpi\:\: [TAB]
 tpacpi::power/tpacpi::standby/  tpacpi::thinklight/   
tpacpi::thinkvantage/

Also acpi_listen does not give any value, when pressing the mic button.

From tlp-stat (tlp 0.6):
-

+++ System Info
System = LENOVO ThinkPad W510 4391E46
BIOS   = 6NET84WW (1.45 )
Release= Ubuntu 14.04.1 LTS
Kernel = 3.13.0-39-generic x86_64
/proc/cmdline  = BOOT_IMAGE=/vmlinuz-3.13.0-39-generic 
root=/dev/mapper/madagaskar--vg-root ro quiet splash


Greets
Axel

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

Title:
  MicMute key on lenovo w510 thinkpad doesn't work

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  Starting with linux-kernel 3.11.0-17 (linux-image-
  extra-3.11.0-17-generic), on a Lenovo ThinkPad W510 the LED within the
  MicMute key is working in the way that it is on by default (meaning
  mic is 'mute'/off). It turns off when activating the microphone via
  'settings'/Internal Microphone 'on' and lights up again when the mic
  is turned off, correctly.

  But the key itself (MicMute, KEY_MICMUTE) isn't showing any function; 
especially it is not turning the microphone on or off.
  The change apparently comes form the thinkpad_acpi kernel module. It seems, 
that the MicMute-key press/release isn't registered at all, as I couldn't 
successfully detect an acpi key 'event'.

  This is for notification, mainly, but thanks for any activity to
  repair that behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-extra-3.11.0-17-generic 3.11.0-17.31 [modified: 
lib/modules/3.11.0-17-generic/kernel/drivers/net/usb/qmi_wwan.ko 
lib/modules/3.11.0-17-generic/kernel/drivers/usb/serial/option.ko]
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  me 3938 F pulseaudio
   /dev/snd/controlC0:  me 3938 F pulseaudio
  Date: Thu Mar  6 13:35:53 2014
  HibernationDevice: RESUME=UUID=1d10886c-db7f-450d-8dbb-96e685779dd1
  InstallationDate: Installed on 2011-03-05 (1096 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007.1)
  MachineType: LENOVO 4389W1B
  MarkForUpload: True
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=Linux ro root=LABEL=Linux_root_Ubu splash
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-17-generic N/A
   linux-backports-modules-3.11.0-17-generic  N/A
   linux-firmware 1.116.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-10-18 (138 days ago)
  dmi.bios.date: 10/27/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6NET74WW (1.34 )
  dmi.board.name: 4389W1B
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6NET74WW(1.34):bd10/27/2010:svnLENOVO:pn4389W1B:pvrThinkPadW510:rvnLENOVO:rn4389W1B:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4389W1B
  dmi.product.version: ThinkPad W510
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1288726/+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 759725] Re: The kernel is no longer readable by non-root users

2014-05-14 Thread Axel Beckert

** Also affects: hobbit-plugins (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  The kernel is no longer readable by non-root users

Status in “hobbit-plugins” package in Ubuntu:
  Confirmed
Status in “linux” package in Ubuntu:
  Won't Fix

Bug description:
  The mode of the latest kernel has changed so it is no longer readable
  by non-root users:

  -rw-r--r-- 1 root root 4336016 2010-10-17 01:37 
/boot/vmlinuz-2.6.35-22-generic
  -rw-r--r-- 1 root root 4336912 2010-11-24 12:46 
/boot/vmlinuz-2.6.35-23-generic
  -rw-r--r-- 1 root root 4523072 2011-03-08 18:47 /boot/vmlinuz-2.6.38-6-generic
  -rw--- 1 root root 4523936 2011-04-11 05:24 /boot/vmlinuz-2.6.38-8-generic

  This prevents people from using this kernel to boot qemu
  virtual machines as non-root.

  Please change the mode back to make the kernel readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: linux-image-2.6.38-8-generic 2.6.38-8.42
  Regression: Yes
  Reproducible: Yes
  ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: aplay: device_list:240: no soundcards found...
  Architecture: amd64
  ArecordDevices: arecord: device_list:240: no soundcards found...
  CRDA: Error: [Errno 2] No such file or directory
  Date: Wed Apr 13 13:05:01 2011
  HibernationDevice: RESUME=UUID=112bf9c4-620e-441f-abb3-aeac6aa15294
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Red Hat KVM
  PciMultimedia:
   
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic 
root=UUID=1efa0b67-17df-484e-980c-8544fa2149fe ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-2.6.35-22-generic N/A
   linux-backports-modules-2.6.35-22-generic  N/A
   linux-firmware 1.50
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/01/2007
  dmi.bios.vendor: Seabios
  dmi.bios.version: 0.5.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: Red Hat
  dmi.modalias: 
dmi:bvnSeabios:bvr0.5.1:bd01/01/2007:svnRedHat:pnKVM:pvrRHEL6.0.0PC:cvnRedHat:ct1:cvr:
  dmi.product.name: KVM
  dmi.product.version: RHEL 6.0.0 PC
  dmi.sys.vendor: Red Hat

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hobbit-plugins/+bug/759725/+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 759725] Re: The kernel is no longer readable by non-root users

2014-05-14 Thread Axel Beckert

** Changed in: hobbit-plugins (Ubuntu)
   Status: Confirmed = In Progress

** Changed in: hobbit-plugins (Ubuntu)
 Assignee: (unassigned) = Axel Beckert (xtaran)

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

Title:
  The kernel is no longer readable by non-root users

Status in “hobbit-plugins” package in Ubuntu:
  In Progress
Status in “linux” package in Ubuntu:
  Won't Fix

Bug description:
  The mode of the latest kernel has changed so it is no longer readable
  by non-root users:

  -rw-r--r-- 1 root root 4336016 2010-10-17 01:37 
/boot/vmlinuz-2.6.35-22-generic
  -rw-r--r-- 1 root root 4336912 2010-11-24 12:46 
/boot/vmlinuz-2.6.35-23-generic
  -rw-r--r-- 1 root root 4523072 2011-03-08 18:47 /boot/vmlinuz-2.6.38-6-generic
  -rw--- 1 root root 4523936 2011-04-11 05:24 /boot/vmlinuz-2.6.38-8-generic

  This prevents people from using this kernel to boot qemu
  virtual machines as non-root.

  Please change the mode back to make the kernel readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: linux-image-2.6.38-8-generic 2.6.38-8.42
  Regression: Yes
  Reproducible: Yes
  ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: aplay: device_list:240: no soundcards found...
  Architecture: amd64
  ArecordDevices: arecord: device_list:240: no soundcards found...
  CRDA: Error: [Errno 2] No such file or directory
  Date: Wed Apr 13 13:05:01 2011
  HibernationDevice: RESUME=UUID=112bf9c4-620e-441f-abb3-aeac6aa15294
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Red Hat KVM
  PciMultimedia:
   
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic 
root=UUID=1efa0b67-17df-484e-980c-8544fa2149fe ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-2.6.35-22-generic N/A
   linux-backports-modules-2.6.35-22-generic  N/A
   linux-firmware 1.50
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/01/2007
  dmi.bios.vendor: Seabios
  dmi.bios.version: 0.5.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: Red Hat
  dmi.modalias: 
dmi:bvnSeabios:bvr0.5.1:bd01/01/2007:svnRedHat:pnKVM:pvrRHEL6.0.0PC:cvnRedHat:ct1:cvr:
  dmi.product.name: KVM
  dmi.product.version: RHEL 6.0.0 PC
  dmi.sys.vendor: Red Hat

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hobbit-plugins/+bug/759725/+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 759725] Re: The kernel is no longer readable by non-root users

2014-05-13 Thread Axel Beckert

This also affects monitoring tools like e.g. the libs test in hobbit-
plugins which compare the running kernel version to the one on disk.
These tests don't run as root as they don't need to. Now they need
elevated privileges just do this check... :-/

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

Title:
  The kernel is no longer readable by non-root users

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

Bug description:
  The mode of the latest kernel has changed so it is no longer readable
  by non-root users:

  -rw-r--r-- 1 root root 4336016 2010-10-17 01:37 
/boot/vmlinuz-2.6.35-22-generic
  -rw-r--r-- 1 root root 4336912 2010-11-24 12:46 
/boot/vmlinuz-2.6.35-23-generic
  -rw-r--r-- 1 root root 4523072 2011-03-08 18:47 /boot/vmlinuz-2.6.38-6-generic
  -rw--- 1 root root 4523936 2011-04-11 05:24 /boot/vmlinuz-2.6.38-8-generic

  This prevents people from using this kernel to boot qemu
  virtual machines as non-root.

  Please change the mode back to make the kernel readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: linux-image-2.6.38-8-generic 2.6.38-8.42
  Regression: Yes
  Reproducible: Yes
  ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: aplay: device_list:240: no soundcards found...
  Architecture: amd64
  ArecordDevices: arecord: device_list:240: no soundcards found...
  CRDA: Error: [Errno 2] No such file or directory
  Date: Wed Apr 13 13:05:01 2011
  HibernationDevice: RESUME=UUID=112bf9c4-620e-441f-abb3-aeac6aa15294
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Red Hat KVM
  PciMultimedia:
   
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic 
root=UUID=1efa0b67-17df-484e-980c-8544fa2149fe ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-2.6.35-22-generic N/A
   linux-backports-modules-2.6.35-22-generic  N/A
   linux-firmware 1.50
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/01/2007
  dmi.bios.vendor: Seabios
  dmi.bios.version: 0.5.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: Red Hat
  dmi.modalias: 
dmi:bvnSeabios:bvr0.5.1:bd01/01/2007:svnRedHat:pnKVM:pvrRHEL6.0.0PC:cvnRedHat:ct1:cvr:
  dmi.product.name: KVM
  dmi.product.version: RHEL 6.0.0 PC
  dmi.sys.vendor: Red Hat

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725/+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 1265309] Re: [Lenovo W510 - SSD Samsung EVO] Sudden Read-Only Filesystems

2014-03-09 Thread Axel Pospischil

*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305


[UPDATE 05th March 2014]

The lenovo service was here and changed the mainboard.
No problems any more with a Crucial M500 480 GB and therefore
I think witch any other SSD on the W510.

So the problem turned out a real hardware problem.
The lenovo diagnostic cd however did not turn out any problem.
So to make a long story short: If you encounter any problems like in
this thread, don't heasitate to contact the lenovo service and insist for
a repair. In my case, I had to contact the service twice because I am using
hardware that is not part of the supported lenovo device list.



** Description changed:

+ 
+ [UPDATE 05th March 2014]
+ 
+ The lenovo service was here and changed the mainboard.
+ No problems any more with a Crucial M500 480 GB and therefore
+ I think witch any other SSD on the W510.
+ 
+ So the problem turned out a real hardware problem.
+ The lenovo diagnostic cd however did not turn out any problem.
+ So to make a long story short: If you encounter any problems like in
+ this thread, don't heasitate to contact the lenovo service and insist for
+ a repair. In my case, I had to contact the service twice because I am using
+ hardware that is not part of the supported lenovo device list.
+ 
+ 
+ 
+ 
  After a while of running the system, the SSD goes into a readonly file system 
mode. I am running Ubuntu 12.04 LTS linux-image-generic-lts-saucy, lvm2 in a 
version that supports trim and are encrypted on three machines, with the only 
one affected is 3.:
  1. An intel xeon with an asus motherboard, 32GB RAM, SSD (SAMSUNG older model)
  2. An Lenovo Thinkpad 201s i7, 8GB RAM, SSD (Crucial)
  3. An Lenovo Thinkpad W510 i7 720, 8GB RAM, SSD (Samsung EVO)
  
  ii lvm2 2.02.95-4ubuntu1.1~p Linux Logical Volume Manager
  
  /etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT=quiet splash
  
  /etc/modprobe.d/options: EMPTY
  
  The #3 (W510) randomly freezes with the following errors:
  
   dmesg | grep ata1
  ata1: SATA max UDMA/133 abar m2048@0xf2627000 port 0xf2627100 irq 54
  ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
  ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
  ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
  ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
  ata1.00: ATA-9: Samsung SSD 840 EVO 500GB, EXT0BB0Q, max UDMA/133
  ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
  ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
  ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
  ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
  ata1.00: configured for UDMA/133
  [...]
  
  These errors occur up to 5-10 times, then the SSD is set to readonly
  state like this:
  
   demsg | grep ata1
  ata1: EH complete
  ata1: limiting SATA link speed to 1.5 Gbps
  ata1.00: exception Emask 0x52 SAct 0x1 SErr 0x1a80d00 action 0x6 frozen
  ata1.00: irq_stat 0x0800, interface fatal error
  ata1: SError: { UnrecovData Proto HostInt 10B8B BadCRC LinkSeq TrStaTrns }
  ata1.00: failed command: READ FPDMA QUEUED
  ata1.00: cmd 60/08:00:d8:b9:27/00:00:05:00:00/40 tag 0 ncq 4096 in
  ata1.00: status: { DRDY }
  ata1: hard resetting link
  ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  
  -
  
  i am now trying the following settings:
  
  /etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT=quiet splash
  libata.force=noncq
  
  /etc/modprobe.d/options: options libata noacpi=1
  
  /etc/default/tlp (which was on standard setting until now)
  
  # Hard disk advanced power management level: 1(max saving)..254(off)
  # Levels 1..127 may spin down the disk.
  # Separate values for multiple devices with spaces.
  DISK_APM_LEVEL_ON_AC=254 254
  DISK_APM_LEVEL_ON_BAT=254 254
  
  # SATA aggressive link power management (ALPM):
  # min_power/medium_power/max_performance
  SATA_LINKPWR_ON_AC=max_performance
  SATA_LINKPWR_ON_BAT=max_performance
  
  I will write ... after further testing.
  
  Please note: system #1. and #2. are running without any problems!
  
  ---
  AFTER 2 DAYS
  ---
  
  Unfortunetely with the settings from above i was not lucky this morning.
  When I turned on the W510 notebook (#3.) it stuck like before. I really
  think, this is system specific for this laptop, because the other
  computers with itdentical software are running flawlessly ... 24/7 (via
  suspend / resume).
  
  I also have to add, that all disks run on lvm based cryptsetup!
  
cat /var/log/syslog.1 | grep ata1 | cut -d [ -f2
  
  1.419360] ata1: SATA max

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO 512GB] Sudden Read-Only Filesystem

2014-02-20 Thread Axel Pospischil

Hi,

[Crucial M500 - a hope? - NO]
---

after returning the Samsung and found this thread in the lenovo forum:

http://forums.lenovo.com/t5/W-Series-ThinkPad-Laptops/W510-SSD-My-
Story/m-p/1402387

my hope was the Crucial M500 should be compatible to the W510:

http://www.crucial.com/store/mpartspecs.aspx?mtbpoid=AC617B31A5CA7304

Unfortunately, I encounterd the very same problems like with the other SSD's.
The ata port hard resets and the SSD goes into read-only state after a certain
amount of time.

More or less stable I could get things running with turning PCIe
powermanagement off in the BIOS an using libata.force=noncq as kernel
boot parameters. Nevertheless the system freezes from time to time.

I will open a new bug report for this drive as soon as the

[Contacting Lenovo support]
---

The lenovo support stated, that only very special SSDs from Intel with a
capacity of 160GB are compatible with this device.
So no help from lenovo.

[FURTHER TESTING]
-

Since the fact, that an older drive, the Samsung 830 is running fine in
a laptop (Lenovo X201, i7) with the same laptop, I tested all drives
(Samsung 840 EVO, PRO and the Crucial M500 480) in the X201. Same
problem there. So it IS DEFINITELY an incompatibility with the drive and
the machine / chipset / kernel.

Within the next weeks, I will try an older Crucial M4 256GB in the W510.
This is an older drive model like the Samsung 830 and probably will work.

[OPINION]
---

Comming across certain threads, this problem is very common an occurs here and
there with certain chipsets.
I don't think it is a problem of the linux kernel, but probably could be fixed?

I will post my results about the Crucial M4 and the problems with the
Crucial M500 and link here.

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

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO 512GB] Sudden Read-
Only Filesystem

Status in “linux” package in Ubuntu:
Opinion

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

- Ubuntu 14 04 LTS (acutal development branch)
- linux-image-generic v. 3.13.x, mainline kernel 3.13.x (first testing the
standard kernel), last 3.12 mainline kernel
- lvm with trim support (batched discard)
- tlp (currently disabled for testing purpose)

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 Pro (former Samsung 840 EVO, was changed in hope that the
problem disapears)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

The SSD randomly freezes with the following errors:
ata1: EH complete
ata1: limiting SATA link speed to 1.5 Gbps
ata1.00: exception Emask 0x52 SAct 0x1 SErr 0x1a80d00 action 0x6 frozen
ata1.00: irq_stat 0x0800, interface fatal error
ata1: SError: { UnrecovData Proto HostInt 10B8B BadCRC LinkSeq TrStaTrns }
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/08:00:d8:b9:27/00:00:05:00:00/40 tag 0 ncq 4096 in
ata1.00: status: { DRDY }
ata1: hard resetting link
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Probably affect other Thinkpad models too:

-
http://www.sevenforums.com/bsod-help-support/309288-bsod-after-few-minutes-5-55-minutes-samsung-ssd-840-evo.html
- [GERMAN]
http://thinkpad-forum.de/threads/168841-Freezes-nach-Einbau-einer-neuen-SSD?p=1698795#post1698795
-
http://www.howtoeverything.net/linux/hardware/ubuntu-freeze-issue-after-ssd-upgrade

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO 512GB] Sudden Read-Only Filesystem

2014-01-24 Thread Axel Pospischil

Fri, 24 Jan 2014 08:54:15 +0100
08:54:15 up 1 day, 20:49, 4 users, load average: 0,90, 2,21, 1,61

Hi again,

as said in comment #50, I put a clone of the SSD, Seagate Momentus XT Hypbrid
into the laptop.
As you can see, the system is running without any problems: no NCQ warnings, no
problems after supspend, hibernation, docking.
And this this tlp enabled and ACPI powermanagement in the bios.

I also tested the SSD in a Thinkpad X201 yesterday evening which has the the
same chipset.
There I had exact the same problems!

I filed a question in lenovos forum and the answer is clear:
nothing but trouble with the Samsung 840 series with this Cipset!
People did not have trouble with the 830 series and capacities of 256 GB:

- http://forums.lenovo.com/t5/W-Series-ThinkPad-Laptops/W510-SSD-My-
Story/td-p/1401955/highlight/false

The only drive which is guarantied by manufactor to run with the
Thinkpad W510 with a capacity of more than 256GB (!) - there is none of
this size in the hardware specifications mentioned by lenovo - is the
crucial M500 480GB.

- http://www.crucial.com/store/mpartspecs.aspx?mtbpoid=AC617B31A5CA7304

#
CONCLUSION
--

I have to return the Samsung 840 Pro 512 GB (as I did with the Samsung
840 EVO) and have to state that it is not compatible with the Thinkpad
W510 and the Intel 5/3400 Chipset and the BIOS 6NET84WW (1.45 )
10/03/2012.

All efforts to get things running stable where - in the end - not
successfull.

Probably this bug report might help to fix things in future kernels or lenovo
will fix this.
Sorry that I can't wait until this will happen ;-)

Cheers, over and out.
Closing bug.

Axel

** Attachment added: dmesg running Seagate Momentus XT 512GB for 2 days

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3955572/+files/dmesg_MomentusXT_512GB.log

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

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

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO 512GB] Sudden Read-
Only Filesystem

Status in “linux” package in Ubuntu:
Opinion

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 Pro (former Samsung 840 EVO, was changed in hope that the
problem disapears)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

Probably affect other Thinkpad models too:

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO] Sudden Read-Only Filesystem

##

DIARY since Wed, 15 Jan 2014
-
Please see the attached log of this post for the last 6 days.

##
CONCLUSION (mainline kernel)

Wed, 22 Jan 2014 10:58:57 +0100
 10:58:57 up 23:45,  4 users,  load average: 0,11, 0,12, 0,19

Finally got quite stable system with some error remaining.


A. What DID solve the problem:
--

1. Disabling the POWER: PCIe / PCI powermanagementin the bios.
I seemed to work, but did not in the end. After a while a hard reset occured 
and the system freezed.

That's why additional tasks are necessary:

2. The usage of the tlp package seams to force PCIe powermangement, at least 
with my settings (see formerly attached files).
Since freezes also occured with ubuntu 12.04, it should not be a problem with 
the tlp package itself, but the machine.
Removing tlp seems to work.

3. Additionally disabling PCIe powermanagement by adding the boot
parameter libata.noacpi=1 seams to be crucial.

4. Adding options libata noacpi=1 in /etc/modprobe.conf is also
crucial for getting a stable system after supsend or resume.

5. I also applied the Thinkpad dock / undock scripts from comment #34 
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/comments/34).
Without this, I enountered various problems when docking / undocking the 
machine.


B. What did NOT solve the problem:
---

1. Using a different SSD (Samsung 840 Pro instead of 840 EVO) is not the point.
The same problems did occur with both type of hardware.

2. Using the mainline, the standard or an older kernel lead to the same
problems.

3. Adding the libata.noncq=1 kernel option is not necessay and not advised due 
to performance (see comment #44)
Nevertheless: the error messages in dmesg failed to get NCQ Send/Recv Log 
Emask 0x1 remain.

4. Using the SATA/Compatibility mode in bios.

5. I also applied the kernel parameters  
libata.force=1:3.0Gbps,2:1,5Gbps,2:80c modprobe.blacklist=pata_acpi which 
lead to the same results: ata1 was limited to 1,5 Gbps after a while.
Also created an /etc/modprobe.conf with this content: options libata noacpi=1 
force=1:3.0Gbps,2:1.5Gbps,2:40c

C. What causes still problems:
---

1. Hibernation: seams to force upcoming of hard resets. In the end this
forces the kernel to set the ata1 device to a limit of 1,5 Gbps (when
libata.noacpi=1 is applied)

2. After a while ata1 is limited to 1,5 Gbps.

2. Setting modprobe.conf and kernel parameters is far from perfect.


D. FURTHER TESTING
---

1. Apply the SSD of another Tinkpad (X201 / Samsung EVO 830) to this machine 
for testing purpose.
Just to see if this is really a problem with the Samsung 840 series SSD.

2. Test safe settings the Trusty mainline kernel.

3. Talking to the maintainer of the tlp package - this might solve
interferences with PCIe powermangement.

4. Testing a normal harddisk with PCIe on, without libata kernel boot
options and tlp and see if it works.

Please be patient, this could take a few days, if not weeks.


E. SUMMARY
--

The problem occur with PCIe powermanagement ENABLED in bios and NOT applying 
the libata.noacpi=1 kernel parameter.
Also the tlp package seems to force the usage of PCIe powermanagement and 
should not be used with this machine / bios.

At January 15th, I had a running system (see at the beginning the attached log 
to this post) with kernel 3.12.7.
This had been exact the same settings from [1. - 3.], except with 3.12.7 kernel.
So I think this are the minimum requirements getting things done.

F. QUESTIONS
-

1. Is there any chance that this might be a problem that can be fixed by
the kernel?

2. Does anybody know how to report this to lenovo?

3. Probably this might be a hardware problem, not just firmware / biso
related?


F. ATTACHMENTS:


Attached you'll find dmesg.log for the actual uptime since last boot on
Sun, 19 Jan 2014 12:32:45 +0100.


** Attachment added: dmesg_egrep_ata_scsi_BOOT.log
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3954221/+files/dmesg_egrep_ata_scsi_BOOT.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/1269777

Title:
  [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO] Sudden Read-Only
  Filesystem

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Like mentioned in bug #1266305 (and before in bug #1265309) the
  following problem occured:

  1. System
  --

  - Ubuntu 14 04 LTS (acutal development branch)
  - linux-image-generic v. 3.13.x,  mainline kernel 3.13.x (first testing the 
standard kernel), last 3.12 mainline kernel
  - lvm with trim support (batched discard)
  - tlp

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO] Sudden Read-Only Filesystem

dmesg since 2014-01-21 with

/etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT=quiet splash
libata.noacpi=1 libata.force=1:3.0Gbps,2:1,5Gbps,2:40c
modprobe.blacklist=pata_acpi

/etc/modprobe.d/blacklist-pata_acpi.conf
blacklist pata_acpi

/etc/modprobe.conf
options libata noacpi=1 force=1:3.0Gbps,2:1.5Gbps

** Attachment added: dmesg.log

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3954223/+files/dmesg.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/1269777

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO] Sudden Read-Only
Filesystem

Status in “linux” package in Ubuntu:
Confirmed

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 Pro (former Samsung 840 EVO, was changed in hope that the
problem disapears)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

Probably affect other Thinkpad models too:

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

Wed, 15 Jan 2014 18:00:00 +0100

- installed mainline kernel 3.13.0-031300rc8-generic
- BIOS:
SATA: Compatibility,
POWER: pci / pcie power management OFF (!)
- no tlp

No problems until the next day (switched POWER management for pci and
pcie on)

Thu, 16 Jan 2014 13:18:45 +0100

- installed linux-image-generic - 3.13.0-3-generic
- BIOS:
SATA: AHCI,
POWER: pci/pcie power management AUTOMATIC
- Reboot with new standard kernel
- no tlp yet!

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO] Sudden Read-Only Filesystem

Duplicate bug?

- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/984127

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

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO] Sudden Read-Only
Filesystem

Status in “linux” package in Ubuntu:
Confirmed

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 Pro (former Samsung 840 EVO, was changed in hope that the
problem disapears)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

Probably affect other Thinkpad models too:

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

Wed, 15 Jan 2014 18:00:00 +0100

- installed mainline kernel 3.13.0-031300rc8-generic
- BIOS:
SATA: Compatibility,
POWER: pci / pcie power management OFF (!)
- no tlp

No problems until the next day (switched POWER management for pci and
pcie on)

Thu, 16 Jan 2014 13:18:45 +0100

- installed linux-image-generic - 3.13.0-3-generic
- BIOS:
SATA: AHCI,
POWER: pci/pcie power management AUTOMATIC
- Reboot with new standard kernel
- no tlp yet!

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-generic 3.13.0.3.6
ProcVersionSignature: Ubuntu 3.13.0-3.18-generic 3.13.0-rc8
Uname: Linux 3.13.0-3-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: apos 3069 F pulseaudio
/dev/snd/controlC0: apos 3069 F pulseaudio
CurrentDesktop: Unity
Date: Thu Jan 16 12:35:13 2014
HibernationDevice: RESUME=UUID=7290992b-11df-4d5c-a9bc-579dafe5eb61
InstallationDate: Installed on 2014-01-08 (7 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140105)
MachineType: LENOVO 4391E46
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-3-generic
root=/dev/mapper/ubuntu--vg-root ro

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO 512GB] Sudden Read-Only Filesystem

** Summary changed:

- [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO] Sudden Read-Only
Filesystem
+ [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO 512GB] Sudden Read-Only
Filesystem

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

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO 512GB] Sudden Read-
Only Filesystem

Status in “linux” package in Ubuntu:
Confirmed

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 Pro (former Samsung 840 EVO, was changed in hope that the
problem disapears)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

Probably affect other Thinkpad models too:

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

Wed, 15 Jan 2014 18:00:00 +0100

- installed mainline kernel 3.13.0-031300rc8-generic
- BIOS:
SATA: Compatibility,
POWER: pci / pcie power management OFF (!)
- no tlp

No problems until the next day (switched POWER management for pci and
pcie on)

Thu, 16 Jan 2014 13:18:45 +0100

- installed linux-image-generic - 3.13.0-3-generic
- BIOS:
SATA: AHCI,
POWER: pci/pcie power management AUTOMATIC
- Reboot with new standard kernel
- no tlp yet!

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO] Sudden Read-Only Filesystem

** Summary changed:

- [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only
Filesystem
+ [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO] Sudden Read-Only
Filesystem

** Description changed:

Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- - SSD Samsung 840 EVO Pro (former Samsung 840 EVO, was changed in hope that
the problem disapears)
+ - SSD Samsung 840 Pro (former Samsung 840 EVO, was changed in hope that the
problem disapears)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

Probably affect other Thinkpad models too:

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no additional
kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

Wed, 15 Jan 2014 18:00:00 +0100

- installed mainline kernel 3.13.0-031300rc8-generic
- BIOS:
SATA: Compatibility,
POWER: pci / pcie power management OFF (!)
- no tlp

No problems until the next day (switched POWER management for pci and
pcie on)

Thu, 16 Jan 2014 13:18:45 +0100

- installed linux-image-generic - 3.13.0-3-generic
- BIOS:
SATA: AHCI,
POWER: pci/pcie power management AUTOMATIC
- Reboot with new standard kernel
- no tlp yet!

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-3-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO] Sudden Read-Only Filesystem

** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-3.13.0-031300rc8-generic

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

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO] Sudden Read-Only
Filesystem

Status in “linux” package in Ubuntu:
Confirmed

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 Pro (former Samsung 840 EVO, was changed in hope that the
problem disapears)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

Probably affect other Thinkpad models too:

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

Wed, 15 Jan 2014 18:00:00 +0100

- installed mainline kernel 3.13.0-031300rc8-generic
- BIOS:
SATA: Compatibility,
POWER: pci / pcie power management OFF (!)
- no tlp

No problems until the next day (switched POWER management for pci and
pcie on)

Thu, 16 Jan 2014 13:18:45 +0100

- installed linux-image-generic - 3.13.0-3-generic
- BIOS:
SATA: AHCI,
POWER: pci/pcie power management AUTOMATIC
- Reboot with new standard kernel
- no tlp yet!

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-3-generic

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO] Sudden Read-Only Filesystem

** Tags removed: needs-upstream-testing

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

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO] Sudden Read-Only
Filesystem

Status in “linux” package in Ubuntu:
Confirmed

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 Pro (former Samsung 840 EVO, was changed in hope that the
problem disapears)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

Probably affect other Thinkpad models too:

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

Wed, 15 Jan 2014 18:00:00 +0100

- installed mainline kernel 3.13.0-031300rc8-generic
- BIOS:
SATA: Compatibility,
POWER: pci / pcie power management OFF (!)
- no tlp

No problems until the next day (switched POWER management for pci and
pcie on)

Thu, 16 Jan 2014 13:18:45 +0100

- installed linux-image-generic - 3.13.0-3-generic
- BIOS:
SATA: AHCI,
POWER: pci/pcie power management AUTOMATIC
- Reboot with new standard kernel
- no tlp yet!

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-3-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO] Sudden Read-Only Filesystem


Fri, 17 Jan 2014 12:54:39 +0100

hard link reset ata1 - readonly filesystem

= Booting now with PCI-Express powermanagement disabled in BIOS !


Some comments:


NCQ 
-

When I am diving into the subject, I see this NCQ kernel error appear

[2.184511] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[2.185682] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[2.185685] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) 
filtered out
[2.185688] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered 
out
[2.186097] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
[2.186104] ata1.00: ATA-9: Samsung SSD 840 PRO Series, DXM05B0Q, max 
UDMA/133
[2.186109] ata1.00: 1000215216 sectors, multi 16: LBA48 NCQ (depth 31/32), 
AA
[2.187422] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[2.187432] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) 
filtered out
[2.187438] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered 
out

- [2.187860] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1

[2.188017] ata1.00: configured for UDMA/133

There is a good article about NCQ here. According to this it is no good
idea to disable this within the kernel command line:

* http://blog.disksurvey.org/blog/2013/10/28/ncq-disabled


###
SATA and PCIE Power Management
-

In gentoo forums I found an article with this error caused by LAPTOP
MODE:

*
http://forums.gentoo.org/viewtopic-t-980628.html?sid=7b7a7aadcd0e124cafc3f54a07049799

For my system I get:

$ for no in 0 1 2 3 4 5; do echo -n host${no}: ; cat 
/sys/class/scsi_host/host${no}/link_power_management_policy ; done
host0: max_performance
host1: max_performance
host2: max_performance
host3: max_performance
host4: max_performance
host5: max_performance

With tlp I can alter this by the following settings int /etc/default/tlp
(this are my actual settings):

[...]

# SATA aggressive link power management (ALPM):
# min_power/medium_power/max_performance
SATA_LINKPWR_ON_AC=max_performance
SATA_LINKPWR_ON_BAT=min_power

# PCI Express Active State Power Management (PCIe ASPM):
# default/performance/powersave
# Hint: needs kernel boot option pcie_aspm=force on some machines
PCIE_ASPM_ON_AC=performance
PCIE_ASPM_ON_BAT=powersave

[...]

Probably altering these settings will solve the problem?

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

Title:
  [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO] Sudden Read-Only
  Filesystem

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Like mentioned in bug #1266305 (and before in bug #1265309) the
  following problem occured:

  1. System
  --

  - Ubuntu 14 04 LTS (acutal development branch)
  - linux-image-generic v. 3.13.x,  mainline kernel 3.13.x (first testing the 
standard kernel), last 3.12 mainline kernel
  - lvm with trim support (batched discard)
  - tlp (currently disabled for testing purpose)

  2. Hardware:
  ---
  - Lenovo W510 i7 quad core
  - SSD Samsung 840 Pro (former Samsung 840 EVO, was changed in hope that the 
problem disapears)
  - nvidia graphics

  BIOS (defaults F9) and:

  - BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management 
AUTOMATIC
  - BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

  - BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power 
management AUTOMATIC
  - BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power 
management OFF

  3. Problem descripton
  ---

  The SSD randomly freezes with the following errors:
  ata1: EH complete
  ata1: limiting SATA link speed to 1.5 Gbps
  ata1.00: exception Emask 0x52 SAct 0x1 SErr 0x1a80d00 action 0x6 frozen
  ata1.00: irq_stat 0x0800, interface fatal error
  ata1: SError: { UnrecovData Proto HostInt 10B8B BadCRC LinkSeq TrStaTrns }
  ata1.00: failed command: READ FPDMA QUEUED
  ata1.00: cmd 60/08:00:d8:b9:27/00:00:05:00:00/40 tag 0 ncq 4096 in
  ata1.00: status: { DRDY }
  ata1: hard resetting link
  ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

  Probably affect other Thinkpad models too:

  - 
http://www.sevenforums.com/bsod-help-support/309288-bsod-after-few-minutes-5-55-minutes-samsung-ssd-840-evo.html
  - [GERMAN] 
http://thinkpad-forum.de/threads/168841-Freezes-nach-Einbau-einer-neuen-SSD?p=1698795#post1698795
  - 
http://www.howtoeverything.net/linux/hardware/ubuntu-freeze-issue-after-ssd-upgrade

  4. Troubleshooting so far
  
  4.1. Kernel boot parameters:

  libata.force=1:3.0G,2:1,5G libata.force=noncq

  - not

[Kernel-packages] [Bug 1269777] [NEW] [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystems

*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305

Public bug reported:

Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

- Ubuntu 14 04 LTS (acutal development branch)
- linux-image-generic v. 3.13.x,  mainline kernel 3.13.x (first testing the 
standard kernel), last 3.12 mainline kernel
- lvm with trim support (batched discard)
- tlp (currently disabled for testing purpose)


2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 EVO Pro (was changed, former Samsung 840 EVO)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management 
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power 
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power 
management OFF


3. Problem descripton
---

The SSD randomly freezes with the following errors:
ata1: EH complete
ata1: limiting SATA link speed to 1.5 Gbps
ata1.00: exception Emask 0x52 SAct 0x1 SErr 0x1a80d00 action 0x6 frozen
ata1.00: irq_stat 0x0800, interface fatal error
ata1: SError: { UnrecovData Proto HostInt 10B8B BadCRC LinkSeq TrStaTrns }
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/08:00:d8:b9:27/00:00:05:00:00/40 tag 0 ncq 4096 in
ata1.00: status: { DRDY }
ata1: hard resetting link
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no additional
kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage without 
any problems.
I did some suspend/ resume cycles: no problems.


5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic) 
5.1.1.  with all BIOS modes.
5.1.2.  eventually kernel boot parameters

5.2. Testing the latest mainline kernel  with all BIOS modes.
5.2.1.  with all BIOS modes.
5.2.2.  eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-generic 3.13.0.3.6
ProcVersionSignature: Ubuntu 3.13.0-3.18-generic 3.13.0-rc8
Uname: Linux 3.13.0-3-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  apos   3069 F pulseaudio
 /dev/snd/controlC0:  apos   3069 F pulseaudio
CurrentDesktop: Unity
Date: Thu Jan 16 12:35:13 2014
HibernationDevice: RESUME=UUID=7290992b-11df-4d5c-a9bc-579dafe5eb61
InstallationDate: Installed on 2014-01-08 (7 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140105)
MachineType: LENOVO 4391E46
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-3-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-3-generic N/A
 linux-backports-modules-3.13.0-3-generic  N/A
 linux-firmware1.121
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/03/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 6NET84WW (1.45 )
dmi.board.name: 4391E46
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4391E46:pvrThinkPadW510:rvnLENOVO:rn4391E46:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4391E46
dmi.product.version: ThinkPad W510
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug third-party-packages trusty

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

Title:
  [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
  Only Filesystems

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Like mentioned in bug #1266305 (and before in bug #1265309) the
  following problem occured:

  1. System
  --

  - Ubuntu 14 04 LTS (acutal development branch)
  - linux-image-generic v. 3.13.x,  mainline kernel 3.13.x (first testing the

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystems

*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305

** Attachment added: dmesg.log

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950025/+files/dmesg.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/1269777

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
Only Filesystems

Status in “linux” package in Ubuntu:
Incomplete

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 EVO Pro (was changed, former Samsung 840 EVO)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-3-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash
RelatedPackageVersions:
linux-restricted-modules-3.13.0-3-generic N/A
linux-backports-modules-3.13.0-3-generic N/A
linux-firmware1.121
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/03/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 6NET84WW (1.45 )
dmi.board.name: 4391E46
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4391E46:pvrThinkPadW510:rvnLENOVO:rn4391E46:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4391E46
dmi.product.version: ThinkPad W510
dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystems

*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305

** Attachment added: uname-a.log

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950028/+files/uname-a.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/1269777

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
Only Filesystems

Status in “linux” package in Ubuntu:
Incomplete

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 EVO Pro (was changed, former Samsung 840 EVO)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystems

*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305

** Attachment added: lspci-vvnn.log

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950027/+files/lspci-vvnn.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/1269777

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
Only Filesystems

Status in “linux” package in Ubuntu:
Incomplete

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 EVO Pro (was changed, former Samsung 840 EVO)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystems

*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305

** Attachment added: lsb_release-rd.log

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950026/+files/lsb_release-rd.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/1269777

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
Only Filesystems

Status in “linux” package in Ubuntu:
Incomplete

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 EVO Pro (was changed, former Samsung 840 EVO)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystems

*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305

** Attachment added: BIOS Mode Compat 2 - SATA

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950030/+files/20140116_45.jpg

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

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
Only Filesystems

Status in “linux” package in Ubuntu:
Incomplete

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 EVO Pro (was changed, former Samsung 840 EVO)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystems

*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305

** Attachment added: BIOS Mode Compat 2 - POWER

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950031/+files/20140116_28.jpg

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

** This bug has been marked a duplicate of bug 1266305
[Lenovo ThinkPad W510] Sudden Read-Only Filesystems

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

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
Only Filesystems

Status in “linux” package in Ubuntu:
Incomplete

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 EVO Pro (was changed, former Samsung 840 EVO)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystems

*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305



Thu, 16 Jan 2014 13:18:45 +0100
- installed linux-image-generic - 3.13.0-3-generic
- BIOS: switched AHCI, and pci/pcie power management on
- Reboot with new kernel
- no tlp yet!

Thu, 16 Jan 2014 13:28:13 +0100
Doing a supend/resume cylce ...

After some seconds:
System is going to slow down a little bit and shows the following messages

dmesg | grep ata1
Jan 16 13:22:18 madagaskar kernel: [ 3053.312643] ata1: SATA link up 3.0 Gbps 
(SStatus 123 SControl 300)
Jan 16 13:22:18 madagaskar kernel: [ 3053.313348] ata1.00: ACPI cmd 
ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
Jan 16 13:22:18 madagaskar kernel: [ 3053.313350] ata1.00: ACPI cmd 
f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
Jan 16 13:22:18 madagaskar kernel: [ 3053.313352] ata1.00: ACPI cmd 
ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
Jan 16 13:22:18 madagaskar kernel: [ 3053.313599] ata1.00: failed to get NCQ 
Send/Recv Log Emask 0x1
Jan 16 13:22:18 madagaskar kernel: [ 3053.473847] ata1.00: ACPI cmd 
ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
Jan 16 13:22:18 madagaskar kernel: [ 3053.473853] ata1.00: ACPI cmd 
f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
Jan 16 13:22:18 madagaskar kernel: [ 3053.473855] ata1.00: ACPI cmd 
ef/10:03:00:00:00:a0 (SET FEATURES) filtered out

 Jan 16 13:22:18 madagaskar kernel: [ 3053.474168] ata1.00: failed to
get NCQ Send/Recv Log Emask 0x1

Jan 16 13:22:18 madagaskar kernel: [ 3053.474251] ata1.00: configured
for UDMA/133


Thu, 16 Jan 2014 14:41:29 +0100

Hard resetting link and readonly filesystem

dmesg | egrep ata|scsi|BOOT see attached picture



Rebootig with BIOS Mode Standard and Kernel 3.13.0-3-generic.

** Attachment added: dmesg | egrep ata|scsi|BOOT
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950078/+files/dmesg_egrep_ata_scsi_BOOT.jpg

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

Title:
  [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
  Only Filesystems

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Like mentioned in bug #1266305 (and before in bug #1265309) the
  following problem occured:

  1. System
  --

  - Ubuntu 14 04 LTS (acutal development branch)
  - linux-image-generic v. 3.13.x,  mainline kernel 3.13.x (first testing the 
standard kernel), last 3.12 mainline kernel
  - lvm with trim support (batched discard)
  - tlp (currently disabled for testing purpose)

  
  2. Hardware:
  ---
  - Lenovo W510 i7 quad core
  - SSD Samsung 840 EVO Pro (was changed, former Samsung 840 EVO)
  - nvidia graphics

  BIOS (defaults F9) and:

  - BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management 
AUTOMATIC
  - BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

  - BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power 
management AUTOMATIC
  - BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power 
management OFF

  
  3. Problem descripton
  ---

  The SSD randomly freezes with the following errors:
  ata1: EH complete
  ata1: limiting SATA link speed to 1.5 Gbps
  ata1.00: exception Emask 0x52 SAct 0x1 SErr 0x1a80d00 action 0x6 frozen
  ata1.00: irq_stat 0x0800, interface fatal error
  ata1: SError: { UnrecovData Proto HostInt 10B8B BadCRC LinkSeq TrStaTrns }
  ata1.00: failed command: READ FPDMA QUEUED
  ata1.00: cmd 60/08:00:d8:b9:27/00:00:05:00:00/40 tag 0 ncq 4096 in
  ata1.00: status: { DRDY }
  ata1: hard resetting link
  ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

  4. Troubleshooting so far
  
  4.1. Kernel boot parameters:

  libata.force=1:3.0G,2:1,5G libata.force=noncq

  - not working. DRDY, hard restting link.

  4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
  additional kernel boot parameters.

  System ran with standard generic kernel 3.13.x for over 12 hours usage 
without any problems.
  I did some suspend/ resume cycles: no problems.

  
  5. Further testing:
  
  Testing scenarios will be applied in the follwowing structure (if necessary)

  5.1 Testing the standard trusty kernel (linux-image-generic) 
  5.1.1.  with all BIOS modes.
  5.1.2.  eventually kernel boot parameters

  5.2. Testing the latest mainline kernel  with all BIOS modes.
  5.2.1.  with all BIOS modes.
  5.2.2.  eventually kernel boot parameters

  This could take a few days, so be patient.

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystems

*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305

** Attachment added: dmesg_egrep_ata_scsi_BOOT.jpg

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950081/+files/dmesg_egrep_ata_scsi_BOOT.jpg

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

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
Only Filesystems

Status in “linux” package in Ubuntu:
Incomplete

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 EVO Pro (was changed, former Samsung 840 EVO)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystem

*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305

** Summary changed:

- [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only
Filesystems
+ [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only
Filesystem

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

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
Only Filesystem

Status in “linux” package in Ubuntu:
Incomplete

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 EVO Pro (was changed, former Samsung 840 EVO)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

To manage notifications about this bug go

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystem

** Description changed:

+ Like mentioned in bug #1266305 (and before in bug #1265309) the
+ following problem occured:
+ 
+ 1. System
+ --
+ 
+ - Ubuntu 14 04 LTS (acutal development branch)
  - linux-image-generic v. 3.13.x,  mainline kernel 3.13.x (first testing the 
standard kernel), last 3.12 mainline kernel
  - lvm with trim support (batched discard)
  - tlp (currently disabled for testing purpose)
- - SSD Samsung 840 EVO Pro (was changed, former Samsung 840 EVO)
+ 
+ 2. Hardware:
+ ---
+ - Lenovo W510 i7 quad core
+ - SSD Samsung 840 EVO Pro (former Samsung 840 EVO, was changed in hope that 
the problem disapears)
+ - nvidia graphics
  
  BIOS (defaults F9) and:
+ 
  - BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management 
AUTOMATIC
  - BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF
+ 
  - BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power 
management AUTOMATIC
  - BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power 
management OFF
-  BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no additional kernel 
boot parameters.
+ 
+ 3. Problem descripton
+ ---
  
  The SSD randomly freezes with the following errors:
  ata1: EH complete
  ata1: limiting SATA link speed to 1.5 Gbps
  ata1.00: exception Emask 0x52 SAct 0x1 SErr 0x1a80d00 action 0x6 frozen
  ata1.00: irq_stat 0x0800, interface fatal error
  ata1: SError: { UnrecovData Proto HostInt 10B8B BadCRC LinkSeq TrStaTrns }
  ata1.00: failed command: READ FPDMA QUEUED
  ata1.00: cmd 60/08:00:d8:b9:27/00:00:05:00:00/40 tag 0 ncq 4096 in
  ata1.00: status: { DRDY }
  ata1: hard resetting link
  ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  
- Tried the following kernel boot parameters but DRDY, hard resetting link:
+ 4. Troubleshooting so far
+ 
+ 4.1. Kernel boot parameters:
+ 
  libata.force=1:3.0G,2:1,5G libata.force=noncq
  
- WORKAROUND: BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no 
additional kernel boot parameters.
- System ran with standard generic kernel 3.13.x for over 12 hours usage 
without any problems. I did some suspend/ resume cycles: no problems.
+ - not working. DRDY, hard restting link.
  
- Testing the standard trusty kernel (linux-image-generic) with all BIOS modes.
- Testing the latest mainline kernel with all BIOS modes.
+ 4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no additional
+ kernel boot parameters.
+ 
+ System ran with standard generic kernel 3.13.x for over 12 hours usage 
without any problems.
+ I did some suspend/ resume cycles: no problems.
+ 
+ 5. Further testing:
+ 
+ Testing scenarios will be applied in the follwowing structure (if necessary)
+ 
+ 5.1 Testing the standard trusty kernel (linux-image-generic)
+ 5.1.1.  with all BIOS modes.
+ 5.1.2.  eventually kernel boot parameters
+ 
+ 5.2. Testing the latest mainline kernel  with all BIOS modes.
+ 5.2.1.  with all BIOS modes.
+ 5.2.2.  eventually kernel boot parameters
+ 
+ This could take a few days, so be patient.
+ 
+ Keeping fingers crossed ;-)
+ 
+ P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
+ assistance so far!
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-generic 3.13.0.3.6
  ProcVersionSignature: Ubuntu 3.13.0-3.18-generic 3.13.0-rc8
  Uname: Linux 3.13.0-3-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  apos   3069 F pulseaudio
   /dev/snd/controlC0:  apos   3069 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jan 16 12:35:13 2014
  HibernationDevice: RESUME=UUID=7290992b-11df-4d5c-a9bc-579dafe5eb61
  InstallationDate: Installed on 2014-01-08 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140105)
  MachineType: LENOVO 4391E46
  ProcFB:
  
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-3-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-3-generic N/A
   linux-backports-modules-3.13.0-3-generic  N/A
   linux-firmware1.121
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6NET84WW (1.45 )
  dmi.board.name: 4391E46
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4391E46:pvrThinkPadW510:rvnLENOVO:rn4391E46:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4391E46

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystem

** Description changed:

  Like mentioned in bug #1266305 (and before in bug #1265309) the
  following problem occured:
  
  1. System
  --
  
  - Ubuntu 14 04 LTS (acutal development branch)
  - linux-image-generic v. 3.13.x,  mainline kernel 3.13.x (first testing the 
standard kernel), last 3.12 mainline kernel
  - lvm with trim support (batched discard)
  - tlp (currently disabled for testing purpose)
  
  2. Hardware:
  ---
  - Lenovo W510 i7 quad core
  - SSD Samsung 840 EVO Pro (former Samsung 840 EVO, was changed in hope that 
the problem disapears)
  - nvidia graphics
  
  BIOS (defaults F9) and:
  
  - BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management 
AUTOMATIC
  - BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF
  
  - BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power 
management AUTOMATIC
  - BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power 
management OFF
  
  3. Problem descripton
  ---
  
  The SSD randomly freezes with the following errors:
  ata1: EH complete
  ata1: limiting SATA link speed to 1.5 Gbps
  ata1.00: exception Emask 0x52 SAct 0x1 SErr 0x1a80d00 action 0x6 frozen
  ata1.00: irq_stat 0x0800, interface fatal error
  ata1: SError: { UnrecovData Proto HostInt 10B8B BadCRC LinkSeq TrStaTrns }
  ata1.00: failed command: READ FPDMA QUEUED
  ata1.00: cmd 60/08:00:d8:b9:27/00:00:05:00:00/40 tag 0 ncq 4096 in
  ata1.00: status: { DRDY }
  ata1: hard resetting link
  ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  
  4. Troubleshooting so far
  
  4.1. Kernel boot parameters:
  
  libata.force=1:3.0G,2:1,5G libata.force=noncq
  
  - not working. DRDY, hard restting link.
  
  4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no additional
  kernel boot parameters.
  
  System ran with standard generic kernel 3.13.x for over 12 hours usage 
without any problems.
  I did some suspend/ resume cycles: no problems.
  
  5. Further testing:
  
  Testing scenarios will be applied in the follwowing structure (if necessary)
  
  5.1 Testing the standard trusty kernel (linux-image-generic)
  5.1.1.  with all BIOS modes.
  5.1.2.  eventually kernel boot parameters
  
  5.2. Testing the latest mainline kernel  with all BIOS modes.
  5.2.1.  with all BIOS modes.
  5.2.2.  eventually kernel boot parameters
  
  This could take a few days, so be patient.
  
  Keeping fingers crossed ;-)
  
  P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
  assistance so far!
  
+ ##
+ 
+ Wed, 15 Jan 2014 18:00:00 +0100
+ 
+ - installed mainline kernel 3.13.0-031300rc8-generic
+ - BIOS: 
+   SATA: Compatibility, 
+   POWER: pci / pcie power management OFF (!)
+ - no tlp
+ 
+ No problems until today
+ 
+ ##
+ 
+ Thu, 16 Jan 2014 13:18:45 +0100
+ 
+ - installed linux-image-generic - 3.13.0-3-generic
+ - BIOS: 
+   SATA: AHCI,
+   POWER:  pci/pcie power management AUTOMATIC
+ - Reboot with new standard kernel
+ - no tlp yet!
+ 
+ 
+ ##
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-generic 3.13.0.3.6
  ProcVersionSignature: Ubuntu 3.13.0-3.18-generic 3.13.0-rc8
  Uname: Linux 3.13.0-3-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  apos   3069 F pulseaudio
   /dev/snd/controlC0:  apos   3069 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jan 16 12:35:13 2014
  HibernationDevice: RESUME=UUID=7290992b-11df-4d5c-a9bc-579dafe5eb61
  InstallationDate: Installed on 2014-01-08 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140105)
  MachineType: LENOVO 4391E46
  ProcFB:
  
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-3-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-3-generic N/A
   linux-backports-modules-3.13.0-3-generic  N/A
   linux-firmware1.121
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6NET84WW (1.45 )
  dmi.board.name: 4391E46
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias:

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystem

Hi Christopher,

I am now still in AHCI mode with PCI(e) powermanagement off in bios.
The system is absolutely stable.

hdparm -I /dev/sda attached

Do you need this with PCI(e) powermanagement enabled?

** Attachment added: hdparm -I /dev/sda

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950185/+files/hdparm-I.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/1269777

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
Only Filesystem

Status in “linux” package in Ubuntu:
Incomplete

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 EVO Pro (former Samsung 840 EVO, was changed in hope that
the problem disapears)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

Probably affect other Thinkpad models too:

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

Wed, 15 Jan 2014 18:00:00 +0100

- installed mainline kernel 3.13.0-031300rc8-generic
- BIOS:
SATA: Compatibility,
POWER: pci / pcie power management OFF (!)
- no tlp

No problems until the next day (switched POWER management for pci and
pcie on)

Thu, 16 Jan 2014 13:18:45 +0100

- installed linux-image-generic - 3.13.0-3-generic
- BIOS:
SATA: AHCI,
POWER: pci/pcie power management AUTOMATIC
- Reboot with new standard kernel
- no tlp yet!

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystem

** Attachment added: dmesg_egrep_ata_scsi_BOOT.log

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950214/+files/dmesg_egrep_ata_scsi_BOOT.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/1269777

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
Only Filesystem

Status in “linux” package in Ubuntu:
Confirmed

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 EVO Pro (former Samsung 840 EVO, was changed in hope that
the problem disapears)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

Probably affect other Thinkpad models too:

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

Wed, 15 Jan 2014 18:00:00 +0100

- installed mainline kernel 3.13.0-031300rc8-generic
- BIOS:
SATA: Compatibility,
POWER: pci / pcie power management OFF (!)
- no tlp

No problems until the next day (switched POWER management for pci and
pcie on)

Thu, 16 Jan 2014 13:18:45 +0100

- installed linux-image-generic - 3.13.0-3-generic
- BIOS:
SATA: AHCI,
POWER: pci/pcie power management AUTOMATIC
- Reboot with new standard kernel
- no tlp yet!

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystem

** Attachment added: dmesg.log

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950215/+files/dmesg.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/1269777

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
Only Filesystem

Status in “linux” package in Ubuntu:
Confirmed

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 EVO Pro (former Samsung 840 EVO, was changed in hope that
the problem disapears)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

Probably affect other Thinkpad models too:

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

Wed, 15 Jan 2014 18:00:00 +0100

- installed mainline kernel 3.13.0-031300rc8-generic
- BIOS:
SATA: Compatibility,
POWER: pci / pcie power management OFF (!)
- no tlp

No problems until the next day (switched POWER management for pci and
pcie on)

Thu, 16 Jan 2014 13:18:45 +0100

- installed linux-image-generic - 3.13.0-3-generic
- BIOS:
SATA: AHCI,
POWER: pci/pcie power management AUTOMATIC
- Reboot with new standard kernel
- no tlp yet!

ProcKernelCmdLine:

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystem

** Attachment added: hdparm-I.log

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950213/+files/hdparm-I.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/1269777

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
Only Filesystem

Status in “linux” package in Ubuntu:
Confirmed

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 EVO Pro (former Samsung 840 EVO, was changed in hope that
the problem disapears)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

Probably affect other Thinkpad models too:

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

Wed, 15 Jan 2014 18:00:00 +0100

- installed mainline kernel 3.13.0-031300rc8-generic
- BIOS:
SATA: Compatibility,
POWER: pci / pcie power management OFF (!)
- no tlp

No problems until the next day (switched POWER management for pci and
pcie on)

Thu, 16 Jan 2014 13:18:45 +0100

- installed linux-image-generic - 3.13.0-3-generic
- BIOS:
SATA: AHCI,
POWER: pci/pcie power management AUTOMATIC
- Reboot with new standard kernel
- no tlp yet!

ProcKernelCmdLine:

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystem

** Attachment added: uname-a.log

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950234/+files/uname-a.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/1269777

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
Only Filesystem

Status in “linux” package in Ubuntu:
Confirmed

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 EVO Pro (former Samsung 840 EVO, was changed in hope that
the problem disapears)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

Probably affect other Thinkpad models too:

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

Wed, 15 Jan 2014 18:00:00 +0100

- installed mainline kernel 3.13.0-031300rc8-generic
- BIOS:
SATA: Compatibility,
POWER: pci / pcie power management OFF (!)
- no tlp

No problems until the next day (switched POWER management for pci and
pcie on)

Thu, 16 Jan 2014 13:18:45 +0100

- installed linux-image-generic - 3.13.0-3-generic
- BIOS:
SATA: AHCI,
POWER: pci/pcie power management AUTOMATIC
- Reboot with new standard kernel
- no tlp yet!

ProcKernelCmdLine:

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystem

Sorry the last dmesg.log was the wrong for this bios settings ...

** Attachment added: dmesg.log

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950227/+files/dmesg.log

** Attachment removed: dmesg_egrep_ata_scsi_BOOT.log

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950214/+files/dmesg_egrep_ata_scsi_BOOT.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/1269777

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
Only Filesystem

Status in “linux” package in Ubuntu:
Confirmed

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 EVO Pro (former Samsung 840 EVO, was changed in hope that
the problem disapears)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

Probably affect other Thinkpad models too:

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

Wed, 15 Jan 2014 18:00:00 +0100

- installed mainline kernel 3.13.0-031300rc8-generic
- BIOS:
SATA: Compatibility,
POWER: pci / pcie power management OFF (!)
- no tlp

No problems until the next day (switched POWER management for pci and
pcie on)

Thu, 16 Jan 2014 13:18:45 +0100

- installed linux-image-generic - 3.13.0-3-generic
- BIOS:
SATA: AHCI,
POWER: pci/pcie power management AUTOMATIC
- Reboot with new standard kernel
- no tlp yet!

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystem

** Attachment added: ls_proc.log

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950235/+files/ls_proc.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/1269777

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
Only Filesystem

Status in “linux” package in Ubuntu:
Confirmed

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 EVO Pro (former Samsung 840 EVO, was changed in hope that
the problem disapears)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

Probably affect other Thinkpad models too:

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

Wed, 15 Jan 2014 18:00:00 +0100

- installed mainline kernel 3.13.0-031300rc8-generic
- BIOS:
SATA: Compatibility,
POWER: pci / pcie power management OFF (!)
- no tlp

No problems until the next day (switched POWER management for pci and
pcie on)

Thu, 16 Jan 2014 13:18:45 +0100

- installed linux-image-generic - 3.13.0-3-generic
- BIOS:
SATA: AHCI,
POWER: pci/pcie power management AUTOMATIC
- Reboot with new standard kernel
- no tlp yet!

ProcKernelCmdLine:

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystem

** Attachment added: proc_scsi_scsi.log

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950240/+files/proc_scsi_scsi.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/1269777

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
Only Filesystem

Status in “linux” package in Ubuntu:
Confirmed

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 EVO Pro (former Samsung 840 EVO, was changed in hope that
the problem disapears)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

Probably affect other Thinkpad models too:

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

Wed, 15 Jan 2014 18:00:00 +0100

- installed mainline kernel 3.13.0-031300rc8-generic
- BIOS:
SATA: Compatibility,
POWER: pci / pcie power management OFF (!)
- no tlp

No problems until the next day (switched POWER management for pci and
pcie on)

Thu, 16 Jan 2014 13:18:45 +0100

- installed linux-image-generic - 3.13.0-3-generic
- BIOS:
SATA: AHCI,
POWER: pci/pcie power management AUTOMATIC
- Reboot with new standard kernel
- no tlp yet!

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystem

** Attachment added: proc_modules.log

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950239/+files/proc_modules.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/1269777

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
Only Filesystem

Status in “linux” package in Ubuntu:
Confirmed

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 EVO Pro (former Samsung 840 EVO, was changed in hope that
the problem disapears)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

Probably affect other Thinkpad models too:

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

Wed, 15 Jan 2014 18:00:00 +0100

- installed mainline kernel 3.13.0-031300rc8-generic
- BIOS:
SATA: Compatibility,
POWER: pci / pcie power management OFF (!)
- no tlp

No problems until the next day (switched POWER management for pci and
pcie on)

Thu, 16 Jan 2014 13:18:45 +0100

- installed linux-image-generic - 3.13.0-3-generic
- BIOS:
SATA: AHCI,
POWER: pci/pcie power management AUTOMATIC
- Reboot with new standard kernel
- no tlp yet!

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystem

** Attachment added: proc_ioports.log

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950238/+files/proc_ioports.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/1269777

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
Only Filesystem

Status in “linux” package in Ubuntu:
Confirmed

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 EVO Pro (former Samsung 840 EVO, was changed in hope that
the problem disapears)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

Probably affect other Thinkpad models too:

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

Wed, 15 Jan 2014 18:00:00 +0100

- installed mainline kernel 3.13.0-031300rc8-generic
- BIOS:
SATA: Compatibility,
POWER: pci / pcie power management OFF (!)
- no tlp

No problems until the next day (switched POWER management for pci and
pcie on)

Thu, 16 Jan 2014 13:18:45 +0100

- installed linux-image-generic - 3.13.0-3-generic
- BIOS:
SATA: AHCI,
POWER: pci/pcie power management AUTOMATIC
- Reboot with new standard kernel
- no tlp yet!

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystem

** Attachment added: usr_src_3.13.0-031300rc8-generic_scripts_ver_linux

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950241/+files/usr_src_3.13.0-031300rc8-generic_scripts_ver_linux

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

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
Only Filesystem

Status in “linux” package in Ubuntu:
Confirmed

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 EVO Pro (former Samsung 840 EVO, was changed in hope that
the problem disapears)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

Probably affect other Thinkpad models too:

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

Wed, 15 Jan 2014 18:00:00 +0100

- installed mainline kernel 3.13.0-031300rc8-generic
- BIOS:
SATA: Compatibility,
POWER: pci / pcie power management OFF (!)
- no tlp

No problems until the next day (switched POWER management for pci and
pcie on)

Thu, 16 Jan 2014 13:18:45 +0100

- installed linux-image-generic - 3.13.0-3-generic
- BIOS:
SATA: AHCI,
POWER: pci/pcie power management AUTOMATIC
- Reboot with new standard kernel
- no tlp yet!

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystem

Running the mainline kernel for 3 hours now.

PCI(e) powermanagement is enabled and SATA is  working in AHCI mode.
Started virtualbox, worked a lot with the system, ... no problems occured ...

Under the same conditions, the standard kernel 3.13.0-3-generic caused
the system to freeze.

I' investigate further and keep the system running ...

##
DATE: Thu, 16 Jan 2014 22:31:11 +0100
UPTIME:  22:31:11 up  2:58,  4 users,  load average: 0,13, 0,29, 0,27
STATUS: dmesg | egrep ata|scsi|BOOT
[0.00] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-031300rc8-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
[0.00] BIOS-e820: [mem 0xc3f7a000-0xc3f7cfff] ACPI data
[0.00] BIOS-e820: [mem 0xc3f81000-0xc3f81fff] ACPI data
[0.00] BIOS-e820: [mem 0xc3f8b000-0xc3f8bfff] ACPI data
[0.00] BIOS-e820: [mem 0xc3f9f000-0xc3ffefff] ACPI data
[0.00] ACPI: BOOT c3ffefd8 28 (v01 LENOVO TP-6N1450 
 LTP 0001)
[0.00] Kernel command line: 
BOOT_IMAGE=/vmlinuz-3.13.0-031300rc8-generic root=/dev/mapper/ubuntu--vg-root 
ro quiet splash
[0.00] Memory: 8076940K/8318476K available (7476K kernel code, 1128K 
rwdata, 3500K rodata, 1344K init, 1436K bss, 241536K reserved)
[0.532393] ACPI : EC: GPE = 0x11, I/O: command/status = 0x66, data = 0x62
[0.532809] libata version 3.00 loaded.
[1.563008] Write protecting the kernel read-only data: 12288k
[1.666129] scsi0 : ahci
[1.666590] scsi1 : ahci
[1.667004] scsi2 : ahci
[1.667416] scsi3 : ahci
[1.667756] scsi4 : ahci
[1.668144] scsi5 : ahci
[1.668269] ata1: SATA max UDMA/133 abar m2048@0xf2627000 port 0xf2627100 
irq 53
[1.668280] ata2: SATA max UDMA/133 abar m2048@0xf2627000 port 0xf2627180 
irq 53
[1.668283] ata3: DUMMY
[1.668286] ata4: DUMMY
[1.668295] ata5: SATA max UDMA/133 abar m2048@0xf2627000 port 0xf2627300 
irq 53
[1.668304] ata6: SATA max UDMA/133 abar m2048@0xf2627000 port 0xf2627380 
irq 53
[1.985559] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[1.986404] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[1.986407] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) 
filtered out
[1.986410] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered 
out
[1.986936] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
[1.986943] ata1.00: ATA-9: Samsung SSD 840 PRO Series, DXM05B0Q, max 
UDMA/133
[1.986948] ata1.00: 1000215216 sectors, multi 16: LBA48 NCQ (depth 31/32), 
AA
[1.988299] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[1.988308] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) 
filtered out
[1.988315] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered 
out
[1.988803] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
[1.988995] ata1.00: configured for UDMA/133
[1.989365] scsi 0:0:0:0: Direct-Access ATA  Samsung SSD 840  DXM0 
PQ: 0 ANSI: 5
[1.989628] sd 0:0:0:0: Attached scsi generic sg0 type 0
[2.309623] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[2.312424] ata2.00: ACPI cmd e3/00:1f:00:00:00:a0 (IDLE) succeeded
[2.312714] ata2.00: ACPI cmd e3/00:02:00:00:00:a0 (IDLE) succeeded
[2.314314] ata2.00: ATAPI: HL-DT-STDVDRAM GT33N, LT20, max UDMA/66
[2.317168] ata2.00: ACPI cmd e3/00:1f:00:00:00:a0 (IDLE) succeeded
[2.317471] ata2.00: ACPI cmd e3/00:02:00:00:00:a0 (IDLE) succeeded
[2.319073] ata2.00: configured for UDMA/66
[2.321196] scsi 1:0:0:0: CD-ROMHL-DT-ST DVDRAM GT33N LT20 
PQ: 0 ANSI: 5
[2.324571] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda 
tray
[2.324979] sr 1:0:0:0: Attached scsi CD-ROM sr0
[2.325109] sr 1:0:0:0: Attached scsi generic sg1 type 5
[2.645804] ata5: SATA link down (SStatus 0 SControl 300)
[2.965915] ata6: SATA link down (SStatus 0 SControl 300)
[   17.185041] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: 
(null)
##

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

Title:
  [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
  Only Filesystem

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Like mentioned in bug #1266305 (and before in bug #1265309) the
  following problem occured:

  1. System
  --

  - Ubuntu 14 04 LTS (acutal development branch)
  - linux-image-generic v. 3.13.x,  mainline kernel 3.13.x (first testing the 
standard kernel), last 3.12 mainline kernel
  - lvm with trim support (batched discard)
  - tlp (currently disabled for testing purpose)

  2. Hardware:

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystem

Running the mainline kernel for 3 hours now. PCI(e) powermanagement is
enabled and SATA is  working in AHCI mode. This caused the standard
kernel 3.13.0-3-generic

##
DATE: Thu, 16 Jan 2014 22:31:11 +0100
UPTIME:  22:31:11 up  2:58,  4 users,  load average: 0,13, 0,29, 0,27
STATUS: dmesg | egrep ata|scsi|BOOT
[0.00] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-031300rc8-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
[0.00] BIOS-e820: [mem 0xc3f7a000-0xc3f7cfff] ACPI data
[0.00] BIOS-e820: [mem 0xc3f81000-0xc3f81fff] ACPI data
[0.00] BIOS-e820: [mem 0xc3f8b000-0xc3f8bfff] ACPI data
[0.00] BIOS-e820: [mem 0xc3f9f000-0xc3ffefff] ACPI data
[0.00] ACPI: BOOT c3ffefd8 28 (v01 LENOVO TP-6N1450 
 LTP 0001)
[0.00] Kernel command line: 
BOOT_IMAGE=/vmlinuz-3.13.0-031300rc8-generic root=/dev/mapper/ubuntu--vg-root 
ro quiet splash
[0.00] Memory: 8076940K/8318476K available (7476K kernel code, 1128K 
rwdata, 3500K rodata, 1344K init, 1436K bss, 241536K reserved)
[0.532393] ACPI : EC: GPE = 0x11, I/O: command/status = 0x66, data = 0x62
[0.532809] libata version 3.00 loaded.
[1.563008] Write protecting the kernel read-only data: 12288k
[1.666129] scsi0 : ahci
[1.666590] scsi1 : ahci
[1.667004] scsi2 : ahci
[1.667416] scsi3 : ahci
[1.667756] scsi4 : ahci
[1.668144] scsi5 : ahci
[1.668269] ata1: SATA max UDMA/133 abar m2048@0xf2627000 port 0xf2627100 
irq 53
[1.668280] ata2: SATA max UDMA/133 abar m2048@0xf2627000 port 0xf2627180 
irq 53
[1.668283] ata3: DUMMY
[1.668286] ata4: DUMMY
[1.668295] ata5: SATA max UDMA/133 abar m2048@0xf2627000 port 0xf2627300 
irq 53
[1.668304] ata6: SATA max UDMA/133 abar m2048@0xf2627000 port 0xf2627380 
irq 53
[1.985559] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[1.986404] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[1.986407] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) 
filtered out
[1.986410] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered 
out
[1.986936] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
[1.986943] ata1.00: ATA-9: Samsung SSD 840 PRO Series, DXM05B0Q, max 
UDMA/133
[1.986948] ata1.00: 1000215216 sectors, multi 16: LBA48 NCQ (depth 31/32), 
AA
[1.988299] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[1.988308] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) 
filtered out
[1.988315] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered 
out
[1.988803] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
[1.988995] ata1.00: configured for UDMA/133
[1.989365] scsi 0:0:0:0: Direct-Access ATA  Samsung SSD 840  DXM0 
PQ: 0 ANSI: 5
[1.989628] sd 0:0:0:0: Attached scsi generic sg0 type 0
[2.309623] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[2.312424] ata2.00: ACPI cmd e3/00:1f:00:00:00:a0 (IDLE) succeeded
[2.312714] ata2.00: ACPI cmd e3/00:02:00:00:00:a0 (IDLE) succeeded
[2.314314] ata2.00: ATAPI: HL-DT-STDVDRAM GT33N, LT20, max UDMA/66
[2.317168] ata2.00: ACPI cmd e3/00:1f:00:00:00:a0 (IDLE) succeeded
[2.317471] ata2.00: ACPI cmd e3/00:02:00:00:00:a0 (IDLE) succeeded
[2.319073] ata2.00: configured for UDMA/66
[2.321196] scsi 1:0:0:0: CD-ROMHL-DT-ST DVDRAM GT33N LT20 
PQ: 0 ANSI: 5
[2.324571] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda 
tray
[2.324979] sr 1:0:0:0: Attached scsi CD-ROM sr0
[2.325109] sr 1:0:0:0: Attached scsi generic sg1 type 5
[2.645804] ata5: SATA link down (SStatus 0 SControl 300)
[2.965915] ata6: SATA link down (SStatus 0 SControl 300)
[   17.185041] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: 
(null)
##

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

Title:
  [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
  Only Filesystem

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Like mentioned in bug #1266305 (and before in bug #1265309) the
  following problem occured:

  1. System
  --

  - Ubuntu 14 04 LTS (acutal development branch)
  - linux-image-generic v. 3.13.x,  mainline kernel 3.13.x (first testing the 
standard kernel), last 3.12 mainline kernel
  - lvm with trim support (batched discard)
  - tlp (currently disabled for testing purpose)

  2. Hardware:
  ---
  - Lenovo W510 i7 quad core
  - SSD Samsung 840 EVO Pro (former Samsung 840 EVO, was changed in hope that 
the problem disapears)
  - nvidia graphics

  BIOS (defaults F9)

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystem

What I did was taking the PC from the docking station, switch of LAN and
switch on WLAN.

Started a program to whatch TV (mythfrontend).

** Attachment added: dmesg.log

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950407/+files/dmesg.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/1269777

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
Only Filesystem

Status in “linux” package in Ubuntu:
Confirmed

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 EVO Pro (former Samsung 840 EVO, was changed in hope that
the problem disapears)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

Probably affect other Thinkpad models too:

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

Wed, 15 Jan 2014 18:00:00 +0100

- installed mainline kernel 3.13.0-031300rc8-generic
- BIOS:
SATA: Compatibility,
POWER: pci / pcie power management OFF (!)
- no tlp

No problems until the next day (switched POWER management for pci and
pcie on)

Thu, 16 Jan 2014 13:18:45 +0100

- installed linux-image-generic - 3.13.0-3-generic
- BIOS:
SATA: AHCI,
POWER: pci/pcie power management AUTOMATIC
- Reboot with new standard kernel
- no tlp yet!

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystem

Booting now the mainline kernel.

BIOS: turned powermanagement for PCI to AUTOMATIC, for PCIE (!) to
Disable

Thu, 16 Jan 2014 22:43:27 +0100

- Booting now with last mainline kernel linux-image-generic
3.13.0-031300rc8-generic #201401120535 SMP Sun Jan 12 10:36:21 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux

- BIOS:
SATA: AHCI,
POWER: PCI AUTOMATIC
PCIE power management DISABLE

- no tlp

** Attachment added: dmesg.log

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950410/+files/dmesg.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/1269777

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
Only Filesystem

Status in “linux” package in Ubuntu:
Confirmed

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 EVO Pro (former Samsung 840 EVO, was changed in hope that
the problem disapears)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

Probably affect other Thinkpad models too:

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

Wed, 15 Jan 2014 18:00:00 +0100

- installed mainline kernel 3.13.0-031300rc8-generic
- BIOS:
SATA: Compatibility,
POWER: pci / pcie power management OFF (!)
- no tlp

No problems until the next day (switched POWER management for pci and
pcie on)

Thu, 16 Jan 2014 13:18:45 +0100

- installed linux-image-generic - 3.13.0-3-generic
- BIOS:
SATA: AHCI,
POWER: pci/pcie power management AUTOMATIC
- Reboot with new standard kernel
- no tlp yet!

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystem

ANALYTICS:
---

If you look at comment #31
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/comments/31),
you will notice in dmesg.log (which I could safe at runntime to /tmp and
copy it over to another pc), that the freeze occurs right after taking
the system from the series 3 docking station.

[10053.907277] thinkpad_acpi: undocked from hotplug port replicator
[10894.439599] ata2.00: exception Emask 0x40 SAct 0x0 SErr 0x880800 action 0x6
frozen
[10894.439610] ata2: SError: { HostInt 10B8B LinkSeq }
[10894.439618] sr 1:0:0:0: CDB:
[...]

According to an article about docking solutions in Think-Wiki, this might be a
problem with the hotplugging of this device and newer kernel series:
* http://www.thinkwiki.org/wiki/Docking_Solutions#Newer_series_3_docks
* http://phihag.de/2012/thinkpad-docking.html

I am investigating in this!

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

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
Only Filesystem

Status in “linux” package in Ubuntu:
Confirmed

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 EVO Pro (former Samsung 840 EVO, was changed in hope that
the problem disapears)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

Probably affect other Thinkpad models too:

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

Wed, 15 Jan 2014 18:00:00 +0100

- installed mainline kernel 3.13.0-031300rc8-generic
- BIOS:
SATA: Compatibility,
POWER: pci / pcie power management OFF (!)
- no tlp

No problems until the next day (switched POWER management for pci and
pcie on)

Thu, 16 Jan 2014 13:18:45 +0100

- installed linux-image-generic - 3.13.0-3-generic
- BIOS:
SATA: AHCI,
POWER: pci/pcie power management AUTOMATIC
- Reboot with new standard kernel
- no tlp yet!

ProblemType: Bug
DistroRelease:

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystem

I rebooted with the paramters of comment #33 (
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/comments/33).
PCIE powermanagement is DISABLED in the BIOS.

Then I did the undocking operation:
It  is working like expected without any problem!

[ 1866.096092] thinkpad_acpi: undocked from hotplug port replicator
[ 1866.816786] thinkpad_acpi: undocked from hotplug port replicator
[ 1868.539250] thinkpad_acpi: undocked from hotplug port replicator
[ 1869.262918] thinkpad_acpi: undocked from hotplug port replicator
[ 1871.740846] usb 1-1.5: new high-speed USB device number 5 using ehci-pci
[ 1871.837436] usb 1-1.5: New USB device found, idVendor=17ef, idProduct=100a
[ 1871.837446] usb 1-1.5: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
[ 1871.838073] hub 1-1.5:1.0: USB hub found
[ 1871.838218] hub 1-1.5:1.0: 6 ports detected
[ 1872.205253] e1000e :00:19.0: irq 54 for MSI/MSI-X
[ 1872.237244] thinkpad_acpi: docked into hotplug port replicator
[ 1875.306042] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: 
Rx
[ 1875.306084] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1886.197392] wlan0: deauthenticating from 00:15:0c:25:3a:20 by local choice 
(reason=3)
[ 1886.209324] cfg80211: Calling CRDA to update world regulatory domain
[ 1886.213833] cfg80211: World regulatory domain updated:
[ 1886.213838] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
[ 1886.213840] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[ 1886.213843] cfg80211:   (2457000 KHz - 2482000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[ 1886.213845] cfg80211:   (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[ 1886.213847] cfg80211:   (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[ 1886.213849] cfg80211:   (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[ 2278.442035] usb 1-1.5: USB disconnect, device number 5
[ 2278.715642] e1000e: eth0 NIC Link is Down
[ 2279.131886] thinkpad_acpi: undocked from hotplug port replicator
[ 2463.374118] usb 1-1.5: new high-speed USB device number 6 using ehci-pci
[ 2463.466471] usb 1-1.5: New USB device found, idVendor=17ef, idProduct=100a
[ 2463.466483] usb 1-1.5: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
[ 2463.467060] hub 1-1.5:1.0: USB hub found
[ 2463.467211] hub 1-1.5:1.0: 6 ports detected
[ 2463.814673] e1000e :00:19.0: irq 54 for MSI/MSI-X
[ 2463.838596] thinkpad_acpi: docked into hotplug port replicator

I will try this again, after the system worked a few hours, e.g.
tomorrow morning.

** Attachment added: dmesg.log
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950470/+files/dmesg.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/1269777

Title:
  [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
  Only Filesystem

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Like mentioned in bug #1266305 (and before in bug #1265309) the
  following problem occured:

  1. System
  --

  - Ubuntu 14 04 LTS (acutal development branch)
  - linux-image-generic v. 3.13.x,  mainline kernel 3.13.x (first testing the 
standard kernel), last 3.12 mainline kernel
  - lvm with trim support (batched discard)
  - tlp (currently disabled for testing purpose)

  2. Hardware:
  ---
  - Lenovo W510 i7 quad core
  - SSD Samsung 840 EVO Pro (former Samsung 840 EVO, was changed in hope that 
the problem disapears)
  - nvidia graphics

  BIOS (defaults F9) and:

  - BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management 
AUTOMATIC
  - BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

  - BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power 
management AUTOMATIC
  - BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power 
management OFF

  3. Problem descripton
  ---

  The SSD randomly freezes with the following errors:
  ata1: EH complete
  ata1: limiting SATA link speed to 1.5 Gbps
  ata1.00: exception Emask 0x52 SAct 0x1 SErr 0x1a80d00 action 0x6 frozen
  ata1.00: irq_stat 0x0800, interface fatal error
  ata1: SError: { UnrecovData Proto HostInt 10B8B BadCRC LinkSeq TrStaTrns }
  ata1.00: failed command: READ FPDMA QUEUED
  ata1.00: cmd 60/08:00:d8:b9:27/00:00:05:00:00/40 tag 0 ncq 4096 in
  ata1.00: status: { DRDY }
  ata1: hard resetting link
  ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

  
  Probably affect other Thinkpad models too:

  - 
http://www.sevenforums.com/bsod-help-support/309288-bsod-after-few-minutes-5-55-minutes-samsung-ssd-840-evo.html
  - [GERMAN] 
http://thinkpad-forum.de/threads/168841-Freezes-nach-Einbau-einer-neuen-SSD?p=1698795#post1698795
  -

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystem

** Attachment added: dmesg_egrep_ata_scsi_BOOT.log

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950612/+files/dmesg_egrep_ata_scsi_BOOT.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/1269777

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
Only Filesystem

Status in “linux” package in Ubuntu:
Confirmed

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 EVO Pro (former Samsung 840 EVO, was changed in hope that
the problem disapears)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

Probably affect other Thinkpad models too:

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

Wed, 15 Jan 2014 18:00:00 +0100

- installed mainline kernel 3.13.0-031300rc8-generic
- BIOS:
SATA: Compatibility,
POWER: pci / pcie power management OFF (!)
- no tlp

No problems until the next day (switched POWER management for pci and
pcie on)

Thu, 16 Jan 2014 13:18:45 +0100

- installed linux-image-generic - 3.13.0-3-generic
- BIOS:
SATA: AHCI,
POWER: pci/pcie power management AUTOMATIC
- Reboot with new standard kernel
- no tlp yet!

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystem

Yesterday evening I applied the Thinkpad dock / undock scripts from
comment #34
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/comments/34).

I also installed tlp, which cares mainly for network interface switching
upon dock / undock evnets (see config attached).

I rebooted the pc with the mainline kernel and switched the BIOS
powermanagement on:

- BIOS:
SATA: AHCI,
POWER: PCI AUTOMATIC
PCIE power management AUTOMATIC

A couple of docking / undocking, suspend / resumes, hibernates which worked
right away.
The computer was running the whole night.

When I analysed the syslog this mornning, there occured some hard
resettings of the ata2 device (dvd) within the night:

- The DVD cannot mount any devices.
- Network interface eth0 is dead
- Ata1 is living (SSD).

But I think it is just a matter of time, when the SSD becomes
unavailable.

- Suspend / resume

Worked, but did not change anything.

- Eject of the ultrabay (which I do with this script:
http://www.thinkwiki.org/wiki/How_to_hotswap_Ultrabay_devices#Script_for_Ultrabay_eject)

This brought back
- the ata2 device
- AND the network interface as well.

** Attachment added: dmesg_status_ata.log

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950590/+files/dmesg_status_ata.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/1269777

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
Only Filesystem

Status in “linux” package in Ubuntu:
Confirmed

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 EVO Pro (former Samsung 840 EVO, was changed in hope that
the problem disapears)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

Probably affect other Thinkpad models too:

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

Wed, 15 Jan 2014 18:00:00 +0100

- installed mainline kernel 3.13.0-031300rc8-generic
- BIOS:
SATA: Compatibility,
POWER: pci / pcie power management OFF (!)
- no tlp

No problems until the next day (switched

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystem

** Attachment added: proc_modules.log

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950623/+files/proc_modules.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/1269777

Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-
Only Filesystem

Status in “linux” package in Ubuntu:
Confirmed

Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:

1. System
--

2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 EVO Pro (former Samsung 840 EVO, was changed in hope that
the problem disapears)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF

3. Problem descripton
---

Probably affect other Thinkpad models too:

4. Troubleshooting so far

4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

- not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:

Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent
assistance so far!

Wed, 15 Jan 2014 18:00:00 +0100

- installed mainline kernel 3.13.0-031300rc8-generic
- BIOS:
SATA: Compatibility,
POWER: pci / pcie power management OFF (!)
- no tlp

No problems until the next day (switched POWER management for pci and
pcie on)

Thu, 16 Jan 2014 13:18:45 +0100

- installed linux-image-generic - 3.13.0-3-generic
- BIOS:
SATA: AHCI,
POWER: pci/pcie power management AUTOMATIC
- Reboot with new standard kernel
- no tlp yet!

[Kernel-packages] [Bug 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystem