[Kernel-packages] [Bug 1594002] [NEW] On Ubuntu touch, when receiving call while handsfree is connected, system behaves erratically and freezes

2016-06-18 Thread AlainKnaff
Public bug reported:

This evening, I received a call in my car (Toyota Prius), while my
Aquaris E5 (Ubuntu touch) phone was connected via bluetooth handsfree
mode.

Ring tone sounded all right over the car's audio system, and call pick
up UI was displayed on central console.

However, the buttons would not react.

Buttons on the phone itself where reactive at first, but call still
wasn't connected. A short time after this phone's UI froze... and then
unfroze after a minute. Eventually two calls were shown, one being
active, and one "on hold". However, neither was connected (could not
hear other party / other party could not hear me). Eventually, other
party gave up, and tried again a minute later.

On that second call, I picked it up right on the phone's UI, and this
time it worked, with audio through car's system.

I found the following in my log:

Jun 18 12:57:18 localhost pulseaudio[2198]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile
Jun 18 12:58:20 localhost bluetoothd[667]: Unable to get io data for Phone Book 
Access: getpeername: Transport endpoint is not connected (107)

=> start of unrelated trip in the morning.


Jun 18 13:20:35 localhost bluetoothd[667]: Unable to get io data for hfp_ag: 
getpeername: Transport endpoint is not connected (107)

=> end of unrelated trip in the morning

Jun 18 17:47:34 localhost bluetoothd[667]: Unable to get io data for Phone Book 
Access: getpeername: Transport endpoint is not connected (107)
Jun 18 17:47:19 localhost pulseaudio[2198]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile

=> start of trip in the evening, during which I received the call.


Jun 18 17:49:27 localhost pulseaudio[2198]: [pulseaudio] 
module-bluez5-device.c: SCO stream went down
Jun 18 17:50:07 localhost bluetoothd[667]: Unable to get io data for hfp_ag: 
getpeername: Transport endpoint is not connected (107)
Jun 18 17:50:07 localhost pulseaudio[2198]: message repeated 622601 times: [ 
[pulseaudio] module-bluez5-device.c: SCO stream went down]
Jun 18 17:50:12 localhost pulseaudio[2198]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile
Jun 18 17:50:45 localhost bluetoothd[667]: Unable to get io data for Phone Book 
Access: getpeername: Transport endpoint is not connected (107)
Jun 18 17:51:11 localhost pulseaudio[2198]: [pulseaudio] 
module-bluez5-device.c: Can't resume SCO over PCM

=> the call

Jun 18 18:16:01 localhost bluetoothd[667]: Unable to get io data for
hfp_ag: getpeername: Transport endpoint is not connected (107)

=> end of trip

/var/log/auth.log had the following messages about bluez (a
...
auth.log:Jun 18 17:15:49 localhost dbus[621]: message repeated 7 times: [ 
[system] Rejected send message, 4 matched rules; type="method_return", 
sender=":1.21" (uid=0 pid=1910 comm="ofonod -P 
provision,udev*,dun*,smart*,hfp_bluez5,s") interface="(unset)" member="(unset)" 
error name="(unset)" requested_reply="0" destination=":1.6" (uid=0 pid=761 
comm="/usr/bin/powerd ")]
auth.log:Jun 18 17:19:40 localhost dbus[621]: [system] Rejected send message, 4 
matched rules; type="method_return", sender=":1.21" (uid=0 pid=1910 
comm="ofonod -P provision,udev*,dun*,smart*,hfp_bluez5,s") interface="(unset)" 
member="(unset)" error name="(unset)" requested_reply="0" destination=":1.6" 
(uid=0 pid=761 comm="/usr/bin/powerd ")
auth.log:Jun 18 17:19:40 localhost dbus[621]: [system] Rejected send message, 4 
matched rules; type="method_return", sender=":1.21" (uid=0 pid=1910 
comm="ofonod -P provision,udev*,dun*,smart*,hfp_bluez5,s") interface="(unset)" 
member="(unset)" error name="(unset)" requested_reply="0" destination=":1.6" 
(uid=0 pid=761 comm="/usr/bin/powerd ")
auth.log:Jun 18 17:49:07 localhost dbus[621]: [system] Rejected send message, 5 
matched rules; type="method_return", sender=":1.51" (uid=32011 pid=2198 
comm="pulseaudio --start --log-target=syslog ") interface="(unset)" 
member="(unset)" error name="(unset)" requested_reply="0" destination=":1.21" 
(uid=0 pid=1910 comm="ofonod -P provision,udev*,dun*,smart*,hfp_bluez5,s")
auth.log:Jun 18 17:49:27 localhost dbus[621]: [system] Rejected send message, 5 
matched rules; type="method_return", sender=":1.51" (uid=32011 pid=2198 
comm="pulseaudio --start --log-target=syslog ") interface="(unset)" 
member="(unset)" error name="(unset)" requested_reply="0" destination=":1.21" 
(uid=0 pid=1910 comm="ofonod -P provision,udev*,dun*,smart*,hfp_bluez5,s")
auth.log:Jun 18 17:49:46 localhost dbus[621]: [system] Rejected send message, 4 
matched rules; type="method_return", sender=":1.21" (uid=0 pid=1910 
comm="ofonod -P provision,udev*,dun*,smart*,hfp_bluez5,s") interface="(unset)" 
member="(unset)" error name="(unset)" requested_reply="0" destination=":1.6" 
(uid=0 pid=761 comm="/usr/bin/powerd ")
auth.log:Jun 18 17:49:46 localhost dbus[621]: [system] Rejected send message, 4 
matched rules; type="method_return", 

[Kernel-packages] [Bug 1562269] [NEW] On Ubuntu touch start bluetooth / stop bluetooth hangs

2016-03-26 Thread AlainKnaff
Public bug reported:

When trying to start or stop the bluetooth subsystem, the start or stop
command just hangs.

A couple of upgrades back, we already *had* a similar situation, now it
re-appeared.

However, when Control-C'ing the start command, and then trying it again,
it says "start: Job is already running: bluetooth"

Likewise, when Control-C'ing the stop command and then trying it again,
it says:  "stop: Job has already been stopped: bluetooth"


root@alains-pocket-penguin:~# lsb_release -rd
Description:Ubuntu 15.04
Release:15.04
root@alains-pocket-penguin:~# apt-cache policy bluez
bluez:
  Installed: 5.37-0ubuntu5~overlay1
  Candidate: 5.37-0ubuntu5~overlay1
  Version table:
 *** 5.37-0ubuntu5~overlay1 0
   1001 
http://ppa.launchpad.net/ci-train-ppa-service/emergency-snapshot/ubuntu/ 
vivid/main armhf Packages
100 /var/lib/dpkg/status
 4.101-0ubuntu25 0
500 http://ports.ubuntu.com/ubuntu-ports/ vivid/main armhf Packages

What I expected to happen
 start bluetooth should start the bluetooth subsystem, and then return as 
quickly as possible
 stop bluetooth should stop the bluetooth subsystem, and then return as quickly 
as possible

What happened instead
  start bluetooth hangs... and after control-C'ing it, status bluetooth is 
"bluetooth start/starting"
  stop bluetooth hangs... and after control-C'ing it, status bluetooth is 
"bluetooth stop/starting"

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


** Tags: bluetooth-touch

** Tags added: bluetooth-touch

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

Title:
  On Ubuntu touch start bluetooth / stop bluetooth hangs

Status in bluez package in Ubuntu:
  New

Bug description:
  When trying to start or stop the bluetooth subsystem, the start or
  stop command just hangs.

  A couple of upgrades back, we already *had* a similar situation, now
  it re-appeared.

  However, when Control-C'ing the start command, and then trying it
  again, it says "start: Job is already running: bluetooth"

  Likewise, when Control-C'ing the stop command and then trying it
  again, it says:  "stop: Job has already been stopped: bluetooth"

  
  root@alains-pocket-penguin:~# lsb_release -rd
  Description:Ubuntu 15.04
  Release:15.04
  root@alains-pocket-penguin:~# apt-cache policy bluez
  bluez:
Installed: 5.37-0ubuntu5~overlay1
Candidate: 5.37-0ubuntu5~overlay1
Version table:
   *** 5.37-0ubuntu5~overlay1 0
 1001 
http://ppa.launchpad.net/ci-train-ppa-service/emergency-snapshot/ubuntu/ 
vivid/main armhf Packages
  100 /var/lib/dpkg/status
   4.101-0ubuntu25 0
  500 http://ports.ubuntu.com/ubuntu-ports/ vivid/main armhf Packages

  What I expected to happen
   start bluetooth should start the bluetooth subsystem, and then return as 
quickly as possible
   stop bluetooth should stop the bluetooth subsystem, and then return as 
quickly as possible

  What happened instead
start bluetooth hangs... and after control-C'ing it, status bluetooth is 
"bluetooth start/starting"
stop bluetooth hangs... and after control-C'ing it, status bluetooth is 
"bluetooth stop/starting"

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

2015-12-05 Thread AlainKnaff
apport information

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

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

Title:
  Kernel modules of first necessity in linux-image-extra rather than
  linux-image

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently, after upgrading a machine from 12.04 to 14.04 I noticed that
  neither keyboard nor network would work, making it rather hard to
  resolve the situation.

  Upon further investigation, it turned out that this was because the
  linux-image-extra package was missing, and that 14.04 has some rather
  critical kernel modules, such as usbhid (keyboard and mouse) and r8169
  (my network card).

  Please make sure in the future that the basic necessities to interact
  with a system are in linux-image-generic, rather than extra.

  root@hitchhiker:~# lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04
  root@hitchhiker:~# apt-cache policy linux-image-generic
  linux-image-generic:
Installed: 3.13.0.71.77
Candidate: 3.13.0.71.77
Version table:
   *** 3.13.0.71.77 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.13.0.24.28 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  What I expected to happen:
  - After an upgrade, I expect the computer to react when I enter keys, move 
the mouse, or attempt to connect to it over the network

  What happened instead
  - the system was completely unreactive, and needed a boot from a live CD to 
revive it again
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  alain 20052 F pulseaudio
   /dev/snd/controlC0:  alain 20052 F pulseaudio
   /dev/snd/controlC1:  alain 20052 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c38c446b-65ae-46d8-8a18-be3d0ec158ba
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=e3f4a5e0-198c-44c3-82dd-529645435d71 ro quiet splash nomodeset 
console=tty0 libata.force=nosrst nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M
  ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-71-generic N/A
   linux-backports-modules-3.13.0-71-generic  N/A
   linux-firmware 1.127.19
  RfKill: Error: [Errno 2] No such file or directory
  StagingDrivers: keucr
  Tags:  trusty staging
  Uname: Linux 3.13.0-71-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2015-08-26 (101 days ago)
  UserGroups: adm admin audio cdrom cvs dialout dip disk floppy kqemu kvm 
libvirtd lpadmin netdev plugdev powerdev sbuild scanner video voice
  WpaSupplicantLog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/04/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 5001
  dmi.board.name: M2A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision5001:bd02/04/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

2015-12-05 Thread AlainKnaff
apport information

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

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

Title:
  Kernel modules of first necessity in linux-image-extra rather than
  linux-image

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently, after upgrading a machine from 12.04 to 14.04 I noticed that
  neither keyboard nor network would work, making it rather hard to
  resolve the situation.

  Upon further investigation, it turned out that this was because the
  linux-image-extra package was missing, and that 14.04 has some rather
  critical kernel modules, such as usbhid (keyboard and mouse) and r8169
  (my network card).

  Please make sure in the future that the basic necessities to interact
  with a system are in linux-image-generic, rather than extra.

  root@hitchhiker:~# lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04
  root@hitchhiker:~# apt-cache policy linux-image-generic
  linux-image-generic:
Installed: 3.13.0.71.77
Candidate: 3.13.0.71.77
Version table:
   *** 3.13.0.71.77 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.13.0.24.28 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  What I expected to happen:
  - After an upgrade, I expect the computer to react when I enter keys, move 
the mouse, or attempt to connect to it over the network

  What happened instead
  - the system was completely unreactive, and needed a boot from a live CD to 
revive it again
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  alain 20052 F pulseaudio
   /dev/snd/controlC0:  alain 20052 F pulseaudio
   /dev/snd/controlC1:  alain 20052 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c38c446b-65ae-46d8-8a18-be3d0ec158ba
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=e3f4a5e0-198c-44c3-82dd-529645435d71 ro quiet splash nomodeset 
console=tty0 libata.force=nosrst nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M
  ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-71-generic N/A
   linux-backports-modules-3.13.0-71-generic  N/A
   linux-firmware 1.127.19
  RfKill: Error: [Errno 2] No such file or directory
  StagingDrivers: keucr
  Tags:  trusty staging
  Uname: Linux 3.13.0-71-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2015-08-26 (101 days ago)
  UserGroups: adm admin audio cdrom cvs dialout dip disk floppy kqemu kvm 
libvirtd lpadmin netdev plugdev powerdev sbuild scanner video voice
  WpaSupplicantLog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/04/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 5001
  dmi.board.name: M2A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision5001:bd02/04/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

2015-12-05 Thread AlainKnaff
apport information

** Attachment added: "UdevLog.txt"
   
https://bugs.launchpad.net/bugs/1523125/+attachment/4530254/+files/UdevLog.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/1523125

Title:
  Kernel modules of first necessity in linux-image-extra rather than
  linux-image

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently, after upgrading a machine from 12.04 to 14.04 I noticed that
  neither keyboard nor network would work, making it rather hard to
  resolve the situation.

  Upon further investigation, it turned out that this was because the
  linux-image-extra package was missing, and that 14.04 has some rather
  critical kernel modules, such as usbhid (keyboard and mouse) and r8169
  (my network card).

  Please make sure in the future that the basic necessities to interact
  with a system are in linux-image-generic, rather than extra.

  root@hitchhiker:~# lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04
  root@hitchhiker:~# apt-cache policy linux-image-generic
  linux-image-generic:
Installed: 3.13.0.71.77
Candidate: 3.13.0.71.77
Version table:
   *** 3.13.0.71.77 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.13.0.24.28 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  What I expected to happen:
  - After an upgrade, I expect the computer to react when I enter keys, move 
the mouse, or attempt to connect to it over the network

  What happened instead
  - the system was completely unreactive, and needed a boot from a live CD to 
revive it again
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  alain 20052 F pulseaudio
   /dev/snd/controlC0:  alain 20052 F pulseaudio
   /dev/snd/controlC1:  alain 20052 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c38c446b-65ae-46d8-8a18-be3d0ec158ba
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=e3f4a5e0-198c-44c3-82dd-529645435d71 ro quiet splash nomodeset 
console=tty0 libata.force=nosrst nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M
  ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-71-generic N/A
   linux-backports-modules-3.13.0-71-generic  N/A
   linux-firmware 1.127.19
  RfKill: Error: [Errno 2] No such file or directory
  StagingDrivers: keucr
  Tags:  trusty staging
  Uname: Linux 3.13.0-71-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2015-08-26 (101 days ago)
  UserGroups: adm admin audio cdrom cvs dialout dip disk floppy kqemu kvm 
libvirtd lpadmin netdev plugdev powerdev sbuild scanner video voice
  WpaSupplicantLog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/04/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 5001
  dmi.board.name: M2A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision5001:bd02/04/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523125/+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 1523125] [NEW] Kernel modules of first necessity in linux-image-extra rather than linux-image

2015-12-05 Thread AlainKnaff
Public bug reported:

Recently, after upgrading a machine from 12.04 to 14.04 I noticed that
neither keyboard nor network would work, making it rather hard to
resolve the situation.

Upon further investigation, it turned out that this was because the
linux-image-extra package was missing, and that 14.04 has some rather
critical kernel modules, such as usbhid (keyboard and mouse) and r8169
(my network card).

Please make sure in the future that the basic necessities to interact
with a system are in linux-image-generic, rather than extra.

root@hitchhiker:~# lsb_release -rd
Description:Ubuntu 14.04.3 LTS
Release:14.04
root@hitchhiker:~# apt-cache policy linux-image-generic
linux-image-generic:
  Installed: 3.13.0.71.77
  Candidate: 3.13.0.71.77
  Version table:
 *** 3.13.0.71.77 0
500 http://fr.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
100 /var/lib/dpkg/status
 3.13.0.24.28 0
500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

What I expected to happen:
- After an upgrade, I expect the computer to react when I enter keys, move the 
mouse, or attempt to connect to it over the network

What happened instead
- the system was completely unreactive, and needed a boot from a live CD to 
revive it again

** Affects: linux (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/1523125

Title:
  Kernel modules of first necessity in linux-image-extra rather than
  linux-image

Status in linux package in Ubuntu:
  New

Bug description:
  Recently, after upgrading a machine from 12.04 to 14.04 I noticed that
  neither keyboard nor network would work, making it rather hard to
  resolve the situation.

  Upon further investigation, it turned out that this was because the
  linux-image-extra package was missing, and that 14.04 has some rather
  critical kernel modules, such as usbhid (keyboard and mouse) and r8169
  (my network card).

  Please make sure in the future that the basic necessities to interact
  with a system are in linux-image-generic, rather than extra.

  root@hitchhiker:~# lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04
  root@hitchhiker:~# apt-cache policy linux-image-generic
  linux-image-generic:
Installed: 3.13.0.71.77
Candidate: 3.13.0.71.77
Version table:
   *** 3.13.0.71.77 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.13.0.24.28 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  What I expected to happen:
  - After an upgrade, I expect the computer to react when I enter keys, move 
the mouse, or attempt to connect to it over the network

  What happened instead
  - the system was completely unreactive, and needed a boot from a live CD to 
revive it again

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

2015-12-05 Thread AlainKnaff
apport information

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

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

Title:
  Kernel modules of first necessity in linux-image-extra rather than
  linux-image

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently, after upgrading a machine from 12.04 to 14.04 I noticed that
  neither keyboard nor network would work, making it rather hard to
  resolve the situation.

  Upon further investigation, it turned out that this was because the
  linux-image-extra package was missing, and that 14.04 has some rather
  critical kernel modules, such as usbhid (keyboard and mouse) and r8169
  (my network card).

  Please make sure in the future that the basic necessities to interact
  with a system are in linux-image-generic, rather than extra.

  root@hitchhiker:~# lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04
  root@hitchhiker:~# apt-cache policy linux-image-generic
  linux-image-generic:
Installed: 3.13.0.71.77
Candidate: 3.13.0.71.77
Version table:
   *** 3.13.0.71.77 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.13.0.24.28 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  What I expected to happen:
  - After an upgrade, I expect the computer to react when I enter keys, move 
the mouse, or attempt to connect to it over the network

  What happened instead
  - the system was completely unreactive, and needed a boot from a live CD to 
revive it again
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  alain 20052 F pulseaudio
   /dev/snd/controlC0:  alain 20052 F pulseaudio
   /dev/snd/controlC1:  alain 20052 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c38c446b-65ae-46d8-8a18-be3d0ec158ba
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=e3f4a5e0-198c-44c3-82dd-529645435d71 ro quiet splash nomodeset 
console=tty0 libata.force=nosrst nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M
  ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-71-generic N/A
   linux-backports-modules-3.13.0-71-generic  N/A
   linux-firmware 1.127.19
  RfKill: Error: [Errno 2] No such file or directory
  StagingDrivers: keucr
  Tags:  trusty staging
  Uname: Linux 3.13.0-71-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2015-08-26 (101 days ago)
  UserGroups: adm admin audio cdrom cvs dialout dip disk floppy kqemu kvm 
libvirtd lpadmin netdev plugdev powerdev sbuild scanner video voice
  WpaSupplicantLog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/04/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 5001
  dmi.board.name: M2A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision5001:bd02/04/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

2015-12-05 Thread AlainKnaff
apport information

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

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

Title:
  Kernel modules of first necessity in linux-image-extra rather than
  linux-image

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently, after upgrading a machine from 12.04 to 14.04 I noticed that
  neither keyboard nor network would work, making it rather hard to
  resolve the situation.

  Upon further investigation, it turned out that this was because the
  linux-image-extra package was missing, and that 14.04 has some rather
  critical kernel modules, such as usbhid (keyboard and mouse) and r8169
  (my network card).

  Please make sure in the future that the basic necessities to interact
  with a system are in linux-image-generic, rather than extra.

  root@hitchhiker:~# lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04
  root@hitchhiker:~# apt-cache policy linux-image-generic
  linux-image-generic:
Installed: 3.13.0.71.77
Candidate: 3.13.0.71.77
Version table:
   *** 3.13.0.71.77 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.13.0.24.28 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  What I expected to happen:
  - After an upgrade, I expect the computer to react when I enter keys, move 
the mouse, or attempt to connect to it over the network

  What happened instead
  - the system was completely unreactive, and needed a boot from a live CD to 
revive it again
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  alain 20052 F pulseaudio
   /dev/snd/controlC0:  alain 20052 F pulseaudio
   /dev/snd/controlC1:  alain 20052 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c38c446b-65ae-46d8-8a18-be3d0ec158ba
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=e3f4a5e0-198c-44c3-82dd-529645435d71 ro quiet splash nomodeset 
console=tty0 libata.force=nosrst nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M
  ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-71-generic N/A
   linux-backports-modules-3.13.0-71-generic  N/A
   linux-firmware 1.127.19
  RfKill: Error: [Errno 2] No such file or directory
  StagingDrivers: keucr
  Tags:  trusty staging
  Uname: Linux 3.13.0-71-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2015-08-26 (101 days ago)
  UserGroups: adm admin audio cdrom cvs dialout dip disk floppy kqemu kvm 
libvirtd lpadmin netdev plugdev powerdev sbuild scanner video voice
  WpaSupplicantLog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/04/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 5001
  dmi.board.name: M2A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision5001:bd02/04/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

2015-12-05 Thread AlainKnaff
apport information

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

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

Title:
  Kernel modules of first necessity in linux-image-extra rather than
  linux-image

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently, after upgrading a machine from 12.04 to 14.04 I noticed that
  neither keyboard nor network would work, making it rather hard to
  resolve the situation.

  Upon further investigation, it turned out that this was because the
  linux-image-extra package was missing, and that 14.04 has some rather
  critical kernel modules, such as usbhid (keyboard and mouse) and r8169
  (my network card).

  Please make sure in the future that the basic necessities to interact
  with a system are in linux-image-generic, rather than extra.

  root@hitchhiker:~# lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04
  root@hitchhiker:~# apt-cache policy linux-image-generic
  linux-image-generic:
Installed: 3.13.0.71.77
Candidate: 3.13.0.71.77
Version table:
   *** 3.13.0.71.77 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.13.0.24.28 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  What I expected to happen:
  - After an upgrade, I expect the computer to react when I enter keys, move 
the mouse, or attempt to connect to it over the network

  What happened instead
  - the system was completely unreactive, and needed a boot from a live CD to 
revive it again
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  alain 20052 F pulseaudio
   /dev/snd/controlC0:  alain 20052 F pulseaudio
   /dev/snd/controlC1:  alain 20052 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c38c446b-65ae-46d8-8a18-be3d0ec158ba
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=e3f4a5e0-198c-44c3-82dd-529645435d71 ro quiet splash nomodeset 
console=tty0 libata.force=nosrst nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M
  ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-71-generic N/A
   linux-backports-modules-3.13.0-71-generic  N/A
   linux-firmware 1.127.19
  RfKill: Error: [Errno 2] No such file or directory
  StagingDrivers: keucr
  Tags:  trusty staging
  Uname: Linux 3.13.0-71-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2015-08-26 (101 days ago)
  UserGroups: adm admin audio cdrom cvs dialout dip disk floppy kqemu kvm 
libvirtd lpadmin netdev plugdev powerdev sbuild scanner video voice
  WpaSupplicantLog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/04/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 5001
  dmi.board.name: M2A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision5001:bd02/04/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

2015-12-05 Thread AlainKnaff
apport information

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

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

Title:
  Kernel modules of first necessity in linux-image-extra rather than
  linux-image

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently, after upgrading a machine from 12.04 to 14.04 I noticed that
  neither keyboard nor network would work, making it rather hard to
  resolve the situation.

  Upon further investigation, it turned out that this was because the
  linux-image-extra package was missing, and that 14.04 has some rather
  critical kernel modules, such as usbhid (keyboard and mouse) and r8169
  (my network card).

  Please make sure in the future that the basic necessities to interact
  with a system are in linux-image-generic, rather than extra.

  root@hitchhiker:~# lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04
  root@hitchhiker:~# apt-cache policy linux-image-generic
  linux-image-generic:
Installed: 3.13.0.71.77
Candidate: 3.13.0.71.77
Version table:
   *** 3.13.0.71.77 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.13.0.24.28 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  What I expected to happen:
  - After an upgrade, I expect the computer to react when I enter keys, move 
the mouse, or attempt to connect to it over the network

  What happened instead
  - the system was completely unreactive, and needed a boot from a live CD to 
revive it again
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  alain 20052 F pulseaudio
   /dev/snd/controlC0:  alain 20052 F pulseaudio
   /dev/snd/controlC1:  alain 20052 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c38c446b-65ae-46d8-8a18-be3d0ec158ba
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=e3f4a5e0-198c-44c3-82dd-529645435d71 ro quiet splash nomodeset 
console=tty0 libata.force=nosrst nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M
  ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-71-generic N/A
   linux-backports-modules-3.13.0-71-generic  N/A
   linux-firmware 1.127.19
  RfKill: Error: [Errno 2] No such file or directory
  StagingDrivers: keucr
  Tags:  trusty staging
  Uname: Linux 3.13.0-71-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2015-08-26 (101 days ago)
  UserGroups: adm admin audio cdrom cvs dialout dip disk floppy kqemu kvm 
libvirtd lpadmin netdev plugdev powerdev sbuild scanner video voice
  WpaSupplicantLog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/04/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 5001
  dmi.board.name: M2A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision5001:bd02/04/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

2015-12-05 Thread AlainKnaff
apport information

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

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

Title:
  Kernel modules of first necessity in linux-image-extra rather than
  linux-image

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently, after upgrading a machine from 12.04 to 14.04 I noticed that
  neither keyboard nor network would work, making it rather hard to
  resolve the situation.

  Upon further investigation, it turned out that this was because the
  linux-image-extra package was missing, and that 14.04 has some rather
  critical kernel modules, such as usbhid (keyboard and mouse) and r8169
  (my network card).

  Please make sure in the future that the basic necessities to interact
  with a system are in linux-image-generic, rather than extra.

  root@hitchhiker:~# lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04
  root@hitchhiker:~# apt-cache policy linux-image-generic
  linux-image-generic:
Installed: 3.13.0.71.77
Candidate: 3.13.0.71.77
Version table:
   *** 3.13.0.71.77 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.13.0.24.28 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  What I expected to happen:
  - After an upgrade, I expect the computer to react when I enter keys, move 
the mouse, or attempt to connect to it over the network

  What happened instead
  - the system was completely unreactive, and needed a boot from a live CD to 
revive it again
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  alain 20052 F pulseaudio
   /dev/snd/controlC0:  alain 20052 F pulseaudio
   /dev/snd/controlC1:  alain 20052 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c38c446b-65ae-46d8-8a18-be3d0ec158ba
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=e3f4a5e0-198c-44c3-82dd-529645435d71 ro quiet splash nomodeset 
console=tty0 libata.force=nosrst nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M
  ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-71-generic N/A
   linux-backports-modules-3.13.0-71-generic  N/A
   linux-firmware 1.127.19
  RfKill: Error: [Errno 2] No such file or directory
  StagingDrivers: keucr
  Tags:  trusty staging
  Uname: Linux 3.13.0-71-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2015-08-26 (101 days ago)
  UserGroups: adm admin audio cdrom cvs dialout dip disk floppy kqemu kvm 
libvirtd lpadmin netdev plugdev powerdev sbuild scanner video voice
  WpaSupplicantLog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/04/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 5001
  dmi.board.name: M2A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision5001:bd02/04/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

2015-12-05 Thread AlainKnaff
apport information

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

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

Title:
  Kernel modules of first necessity in linux-image-extra rather than
  linux-image

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently, after upgrading a machine from 12.04 to 14.04 I noticed that
  neither keyboard nor network would work, making it rather hard to
  resolve the situation.

  Upon further investigation, it turned out that this was because the
  linux-image-extra package was missing, and that 14.04 has some rather
  critical kernel modules, such as usbhid (keyboard and mouse) and r8169
  (my network card).

  Please make sure in the future that the basic necessities to interact
  with a system are in linux-image-generic, rather than extra.

  root@hitchhiker:~# lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04
  root@hitchhiker:~# apt-cache policy linux-image-generic
  linux-image-generic:
Installed: 3.13.0.71.77
Candidate: 3.13.0.71.77
Version table:
   *** 3.13.0.71.77 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.13.0.24.28 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  What I expected to happen:
  - After an upgrade, I expect the computer to react when I enter keys, move 
the mouse, or attempt to connect to it over the network

  What happened instead
  - the system was completely unreactive, and needed a boot from a live CD to 
revive it again
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  alain 20052 F pulseaudio
   /dev/snd/controlC0:  alain 20052 F pulseaudio
   /dev/snd/controlC1:  alain 20052 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c38c446b-65ae-46d8-8a18-be3d0ec158ba
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=e3f4a5e0-198c-44c3-82dd-529645435d71 ro quiet splash nomodeset 
console=tty0 libata.force=nosrst nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M
  ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-71-generic N/A
   linux-backports-modules-3.13.0-71-generic  N/A
   linux-firmware 1.127.19
  RfKill: Error: [Errno 2] No such file or directory
  StagingDrivers: keucr
  Tags:  trusty staging
  Uname: Linux 3.13.0-71-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2015-08-26 (101 days ago)
  UserGroups: adm admin audio cdrom cvs dialout dip disk floppy kqemu kvm 
libvirtd lpadmin netdev plugdev powerdev sbuild scanner video voice
  WpaSupplicantLog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/04/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 5001
  dmi.board.name: M2A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision5001:bd02/04/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

2015-12-05 Thread AlainKnaff
apport information

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

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

Title:
  Kernel modules of first necessity in linux-image-extra rather than
  linux-image

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently, after upgrading a machine from 12.04 to 14.04 I noticed that
  neither keyboard nor network would work, making it rather hard to
  resolve the situation.

  Upon further investigation, it turned out that this was because the
  linux-image-extra package was missing, and that 14.04 has some rather
  critical kernel modules, such as usbhid (keyboard and mouse) and r8169
  (my network card).

  Please make sure in the future that the basic necessities to interact
  with a system are in linux-image-generic, rather than extra.

  root@hitchhiker:~# lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04
  root@hitchhiker:~# apt-cache policy linux-image-generic
  linux-image-generic:
Installed: 3.13.0.71.77
Candidate: 3.13.0.71.77
Version table:
   *** 3.13.0.71.77 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.13.0.24.28 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  What I expected to happen:
  - After an upgrade, I expect the computer to react when I enter keys, move 
the mouse, or attempt to connect to it over the network

  What happened instead
  - the system was completely unreactive, and needed a boot from a live CD to 
revive it again
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  alain 20052 F pulseaudio
   /dev/snd/controlC0:  alain 20052 F pulseaudio
   /dev/snd/controlC1:  alain 20052 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c38c446b-65ae-46d8-8a18-be3d0ec158ba
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=e3f4a5e0-198c-44c3-82dd-529645435d71 ro quiet splash nomodeset 
console=tty0 libata.force=nosrst nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M
  ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-71-generic N/A
   linux-backports-modules-3.13.0-71-generic  N/A
   linux-firmware 1.127.19
  RfKill: Error: [Errno 2] No such file or directory
  StagingDrivers: keucr
  Tags:  trusty staging
  Uname: Linux 3.13.0-71-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2015-08-26 (101 days ago)
  UserGroups: adm admin audio cdrom cvs dialout dip disk floppy kqemu kvm 
libvirtd lpadmin netdev plugdev powerdev sbuild scanner video voice
  WpaSupplicantLog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/04/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 5001
  dmi.board.name: M2A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision5001:bd02/04/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

2015-12-05 Thread AlainKnaff
apport information

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

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

Title:
  Kernel modules of first necessity in linux-image-extra rather than
  linux-image

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently, after upgrading a machine from 12.04 to 14.04 I noticed that
  neither keyboard nor network would work, making it rather hard to
  resolve the situation.

  Upon further investigation, it turned out that this was because the
  linux-image-extra package was missing, and that 14.04 has some rather
  critical kernel modules, such as usbhid (keyboard and mouse) and r8169
  (my network card).

  Please make sure in the future that the basic necessities to interact
  with a system are in linux-image-generic, rather than extra.

  root@hitchhiker:~# lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04
  root@hitchhiker:~# apt-cache policy linux-image-generic
  linux-image-generic:
Installed: 3.13.0.71.77
Candidate: 3.13.0.71.77
Version table:
   *** 3.13.0.71.77 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.13.0.24.28 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  What I expected to happen:
  - After an upgrade, I expect the computer to react when I enter keys, move 
the mouse, or attempt to connect to it over the network

  What happened instead
  - the system was completely unreactive, and needed a boot from a live CD to 
revive it again
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  alain 20052 F pulseaudio
   /dev/snd/controlC0:  alain 20052 F pulseaudio
   /dev/snd/controlC1:  alain 20052 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c38c446b-65ae-46d8-8a18-be3d0ec158ba
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=e3f4a5e0-198c-44c3-82dd-529645435d71 ro quiet splash nomodeset 
console=tty0 libata.force=nosrst nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M
  ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-71-generic N/A
   linux-backports-modules-3.13.0-71-generic  N/A
   linux-firmware 1.127.19
  RfKill: Error: [Errno 2] No such file or directory
  StagingDrivers: keucr
  Tags:  trusty staging
  Uname: Linux 3.13.0-71-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2015-08-26 (101 days ago)
  UserGroups: adm admin audio cdrom cvs dialout dip disk floppy kqemu kvm 
libvirtd lpadmin netdev plugdev powerdev sbuild scanner video voice
  WpaSupplicantLog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/04/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 5001
  dmi.board.name: M2A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision5001:bd02/04/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

2015-12-05 Thread AlainKnaff
apport information

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

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

Title:
  Kernel modules of first necessity in linux-image-extra rather than
  linux-image

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently, after upgrading a machine from 12.04 to 14.04 I noticed that
  neither keyboard nor network would work, making it rather hard to
  resolve the situation.

  Upon further investigation, it turned out that this was because the
  linux-image-extra package was missing, and that 14.04 has some rather
  critical kernel modules, such as usbhid (keyboard and mouse) and r8169
  (my network card).

  Please make sure in the future that the basic necessities to interact
  with a system are in linux-image-generic, rather than extra.

  root@hitchhiker:~# lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04
  root@hitchhiker:~# apt-cache policy linux-image-generic
  linux-image-generic:
Installed: 3.13.0.71.77
Candidate: 3.13.0.71.77
Version table:
   *** 3.13.0.71.77 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.13.0.24.28 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  What I expected to happen:
  - After an upgrade, I expect the computer to react when I enter keys, move 
the mouse, or attempt to connect to it over the network

  What happened instead
  - the system was completely unreactive, and needed a boot from a live CD to 
revive it again
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  alain 20052 F pulseaudio
   /dev/snd/controlC0:  alain 20052 F pulseaudio
   /dev/snd/controlC1:  alain 20052 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c38c446b-65ae-46d8-8a18-be3d0ec158ba
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=e3f4a5e0-198c-44c3-82dd-529645435d71 ro quiet splash nomodeset 
console=tty0 libata.force=nosrst nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M
  ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-71-generic N/A
   linux-backports-modules-3.13.0-71-generic  N/A
   linux-firmware 1.127.19
  RfKill: Error: [Errno 2] No such file or directory
  StagingDrivers: keucr
  Tags:  trusty staging
  Uname: Linux 3.13.0-71-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2015-08-26 (101 days ago)
  UserGroups: adm admin audio cdrom cvs dialout dip disk floppy kqemu kvm 
libvirtd lpadmin netdev plugdev powerdev sbuild scanner video voice
  WpaSupplicantLog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/04/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 5001
  dmi.board.name: M2A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision5001:bd02/04/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523125/+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 1523125] Re: Kernel modules of first necessity in linux-image-extra rather than linux-image

2015-12-05 Thread AlainKnaff
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Kernel modules of first necessity in linux-image-extra rather than
  linux-image

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Recently, after upgrading a machine from 12.04 to 14.04 I noticed that
  neither keyboard nor network would work, making it rather hard to
  resolve the situation.

  Upon further investigation, it turned out that this was because the
  linux-image-extra package was missing, and that 14.04 has some rather
  critical kernel modules, such as usbhid (keyboard and mouse) and r8169
  (my network card).

  Please make sure in the future that the basic necessities to interact
  with a system are in linux-image-generic, rather than extra.

  root@hitchhiker:~# lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04
  root@hitchhiker:~# apt-cache policy linux-image-generic
  linux-image-generic:
Installed: 3.13.0.71.77
Candidate: 3.13.0.71.77
Version table:
   *** 3.13.0.71.77 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.13.0.24.28 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  What I expected to happen:
  - After an upgrade, I expect the computer to react when I enter keys, move 
the mouse, or attempt to connect to it over the network

  What happened instead
  - the system was completely unreactive, and needed a boot from a live CD to 
revive it again
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  alain 20052 F pulseaudio
   /dev/snd/controlC0:  alain 20052 F pulseaudio
   /dev/snd/controlC1:  alain 20052 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c38c446b-65ae-46d8-8a18-be3d0ec158ba
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=e3f4a5e0-198c-44c3-82dd-529645435d71 ro quiet splash nomodeset 
console=tty0 libata.force=nosrst nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M
  ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-71-generic N/A
   linux-backports-modules-3.13.0-71-generic  N/A
   linux-firmware 1.127.19
  RfKill: Error: [Errno 2] No such file or directory
  StagingDrivers: keucr
  Tags:  trusty staging
  Uname: Linux 3.13.0-71-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2015-08-26 (101 days ago)
  UserGroups: adm admin audio cdrom cvs dialout dip disk floppy kqemu kvm 
libvirtd lpadmin netdev plugdev powerdev sbuild scanner video voice
  WpaSupplicantLog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/04/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 5001
  dmi.board.name: M2A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision5001:bd02/04/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523125/+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 1523125] Re: Kernel modules of first necessity in linux-image-extra rather than linux-image

2015-12-05 Thread AlainKnaff
apport information

** Tags added: apport-collected staging

** Description changed:

  Recently, after upgrading a machine from 12.04 to 14.04 I noticed that
  neither keyboard nor network would work, making it rather hard to
  resolve the situation.
  
  Upon further investigation, it turned out that this was because the
  linux-image-extra package was missing, and that 14.04 has some rather
  critical kernel modules, such as usbhid (keyboard and mouse) and r8169
  (my network card).
  
  Please make sure in the future that the basic necessities to interact
  with a system are in linux-image-generic, rather than extra.
  
  root@hitchhiker:~# lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04
  root@hitchhiker:~# apt-cache policy linux-image-generic
  linux-image-generic:
Installed: 3.13.0.71.77
Candidate: 3.13.0.71.77
Version table:
   *** 3.13.0.71.77 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.13.0.24.28 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  
  What I expected to happen:
  - After an upgrade, I expect the computer to react when I enter keys, move 
the mouse, or attempt to connect to it over the network
  
  What happened instead
  - the system was completely unreactive, and needed a boot from a live CD to 
revive it again
+ --- 
+ ApportVersion: 2.14.1-0ubuntu3.19
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC2:  alain 20052 F pulseaudio
+  /dev/snd/controlC0:  alain 20052 F pulseaudio
+  /dev/snd/controlC1:  alain 20052 F pulseaudio
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 14.04
+ HibernationDevice: RESUME=UUID=c38c446b-65ae-46d8-8a18-be3d0ec158ba
+ MachineType: System manufacturer System Product Name
+ NonfreeKernelModules: nvidia
+ Package: linux (not installed)
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=e3f4a5e0-198c-44c3-82dd-529645435d71 ro quiet splash nomodeset 
console=tty0 libata.force=nosrst nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M
+ ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
+ RelatedPackageVersions:
+  linux-restricted-modules-3.13.0-71-generic N/A
+  linux-backports-modules-3.13.0-71-generic  N/A
+  linux-firmware 1.127.19
+ RfKill: Error: [Errno 2] No such file or directory
+ StagingDrivers: keucr
+ Tags:  trusty staging
+ Uname: Linux 3.13.0-71-generic x86_64
+ UpgradeStatus: Upgraded to trusty on 2015-08-26 (101 days ago)
+ UserGroups: adm admin audio cdrom cvs dialout dip disk floppy kqemu kvm 
libvirtd lpadmin netdev plugdev powerdev sbuild scanner video voice
+ WpaSupplicantLog:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 02/04/2010
+ dmi.bios.vendor: Phoenix Technologies, LTD
+ dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 5001
+ dmi.board.name: M2A-VM
+ dmi.board.vendor: ASUSTeK Computer INC.
+ dmi.board.version: 1.XX
+ dmi.chassis.asset.tag: 123456789000
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Chassis Manufacture
+ dmi.chassis.version: Chassis Version
+ dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision5001:bd02/04/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
+ dmi.product.name: System Product Name
+ dmi.product.version: System Version
+ dmi.sys.vendor: System manufacturer

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

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

Title:
  Kernel modules of first necessity in linux-image-extra rather than
  linux-image

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently, after upgrading a machine from 12.04 to 14.04 I noticed that
  neither keyboard nor network would work, making it rather hard to
  resolve the situation.

  Upon further investigation, it turned out that this was because the
  linux-image-extra package was missing, and that 14.04 has some rather
  critical kernel modules, such as usbhid (keyboard and mouse) and r8169
  (my network card).

  Please make sure in the future that the basic necessities to interact
  with a system are in linux-image-generic, rather than extra.

  root@hitchhiker:~# lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04
  root@hitchhiker:~# apt-cache policy linux-image-generic
  linux-image-generic:
Installed: 3.13.0.71.77
Candidate: 3.13.0.71.77
Version table:
   *** 3.13.0.71.77 0
  500 http://fr.archive.ubuntu.com/ubuntu/ 

[Kernel-packages] [Bug 1523125] CRDA.txt

2015-12-05 Thread AlainKnaff
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1523125/+attachment/4530243/+files/CRDA.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/1523125

Title:
  Kernel modules of first necessity in linux-image-extra rather than
  linux-image

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently, after upgrading a machine from 12.04 to 14.04 I noticed that
  neither keyboard nor network would work, making it rather hard to
  resolve the situation.

  Upon further investigation, it turned out that this was because the
  linux-image-extra package was missing, and that 14.04 has some rather
  critical kernel modules, such as usbhid (keyboard and mouse) and r8169
  (my network card).

  Please make sure in the future that the basic necessities to interact
  with a system are in linux-image-generic, rather than extra.

  root@hitchhiker:~# lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04
  root@hitchhiker:~# apt-cache policy linux-image-generic
  linux-image-generic:
Installed: 3.13.0.71.77
Candidate: 3.13.0.71.77
Version table:
   *** 3.13.0.71.77 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.13.0.24.28 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  What I expected to happen:
  - After an upgrade, I expect the computer to react when I enter keys, move 
the mouse, or attempt to connect to it over the network

  What happened instead
  - the system was completely unreactive, and needed a boot from a live CD to 
revive it again
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  alain 20052 F pulseaudio
   /dev/snd/controlC0:  alain 20052 F pulseaudio
   /dev/snd/controlC1:  alain 20052 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c38c446b-65ae-46d8-8a18-be3d0ec158ba
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=e3f4a5e0-198c-44c3-82dd-529645435d71 ro quiet splash nomodeset 
console=tty0 libata.force=nosrst nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M
  ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-71-generic N/A
   linux-backports-modules-3.13.0-71-generic  N/A
   linux-firmware 1.127.19
  RfKill: Error: [Errno 2] No such file or directory
  StagingDrivers: keucr
  Tags:  trusty staging
  Uname: Linux 3.13.0-71-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2015-08-26 (101 days ago)
  UserGroups: adm admin audio cdrom cvs dialout dip disk floppy kqemu kvm 
libvirtd lpadmin netdev plugdev powerdev sbuild scanner video voice
  WpaSupplicantLog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/04/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 5001
  dmi.board.name: M2A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision5001:bd02/04/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

2015-12-05 Thread AlainKnaff
apport information

** Attachment added: "BootDmesg.txt"
   
https://bugs.launchpad.net/bugs/1523125/+attachment/4530242/+files/BootDmesg.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/1523125

Title:
  Kernel modules of first necessity in linux-image-extra rather than
  linux-image

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently, after upgrading a machine from 12.04 to 14.04 I noticed that
  neither keyboard nor network would work, making it rather hard to
  resolve the situation.

  Upon further investigation, it turned out that this was because the
  linux-image-extra package was missing, and that 14.04 has some rather
  critical kernel modules, such as usbhid (keyboard and mouse) and r8169
  (my network card).

  Please make sure in the future that the basic necessities to interact
  with a system are in linux-image-generic, rather than extra.

  root@hitchhiker:~# lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04
  root@hitchhiker:~# apt-cache policy linux-image-generic
  linux-image-generic:
Installed: 3.13.0.71.77
Candidate: 3.13.0.71.77
Version table:
   *** 3.13.0.71.77 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.13.0.24.28 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  What I expected to happen:
  - After an upgrade, I expect the computer to react when I enter keys, move 
the mouse, or attempt to connect to it over the network

  What happened instead
  - the system was completely unreactive, and needed a boot from a live CD to 
revive it again
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  alain 20052 F pulseaudio
   /dev/snd/controlC0:  alain 20052 F pulseaudio
   /dev/snd/controlC1:  alain 20052 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c38c446b-65ae-46d8-8a18-be3d0ec158ba
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=e3f4a5e0-198c-44c3-82dd-529645435d71 ro quiet splash nomodeset 
console=tty0 libata.force=nosrst nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M
  ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-71-generic N/A
   linux-backports-modules-3.13.0-71-generic  N/A
   linux-firmware 1.127.19
  RfKill: Error: [Errno 2] No such file or directory
  StagingDrivers: keucr
  Tags:  trusty staging
  Uname: Linux 3.13.0-71-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2015-08-26 (101 days ago)
  UserGroups: adm admin audio cdrom cvs dialout dip disk floppy kqemu kvm 
libvirtd lpadmin netdev plugdev powerdev sbuild scanner video voice
  WpaSupplicantLog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/04/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 5001
  dmi.board.name: M2A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision5001:bd02/04/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523125/+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 666828] Re: task jbd2/cciss!c0d0:258 blocked for more than 120 seconds

2015-11-27 Thread AlainKnaff
Just saw this one as well today, on a 12.04.5 with a 3.13 kernel

Ssh, and serial console were unresponsive.

Console displayed message about jbd2 being blocked for more than 120
seconds, and then loads of other processes (apache2) blocked for 120
seconds as well (but jbd2 was the first such message chronologically)

Scrolling up and down virtual console worked.

Changing virtual consoles worked as well, login prompts were displayed
on the other virtual consoles, but after entering user name and pressing
return there would just hang (no output, apart user name itself)

After reboot (by killing the kvm process handling this virtual machine),
logfiles showed a bunch of NUL characters (^@) before the reboot
messages, and last message before these NULs was approx 2 hours before
the crash.

We've been running this virtual machine for a while, and this is the
first time this happened.

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

Title:
  task jbd2/cciss!c0d0:258 blocked for more than 120 seconds

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Lucid:
  Fix Released
Status in linux source package in Maverick:
  Fix Released
Status in linux source package in Natty:
  Fix Released

Bug description:
  Machine became unreachble via ssh. Logging in via the console switch we saw
  task jbd2/cciss!c0d0:258 blocked for more than 120 seconds

  The machine was completely unresponsive, all I could do was scroll up
  and down. ctrl-alt-del wouldn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: linux-image-server 2.6.35.22.23
  Regression: Yes
  Reproducible: No
  ProcVersionSignature: Ubuntu 2.6.35-22.35-server 2.6.35.4
  Uname: Linux 2.6.35-22-server 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: Error: [Errno 2] No such file or directory
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  Date: Tue Oct 26 17:03:00 2010
  Frequency: Once every few days.
  InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.2)
  Lsusb:
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP ProLiant DL360 G4
  PciMultimedia:
   
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-server 
root=UUID=4cc50c45-22ab-445d-a812-bd88e377aa86 ro noquiet panic=30
  ProcEnviron:
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/tcsh
  SourcePackage: linux
  dmi.bios.date: 04/14/2005
  dmi.bios.vendor: HP
  dmi.bios.version: P52
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP52:bd04/14/2005:svnHP:pnProLiantDL360G4:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL360 G4
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/666828/+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 1397649] [NEW] remounting root read-only in private mount namespace affects main namespace

2014-11-30 Thread AlainKnaff
Public bug reported:

When remounting root read-only in a private mount namespace, then also
the real root (in default namespace) is read-only.

However, it is then possible to remount the real root read-write, and
this doesn't (fortunately...) affect the other namespace.

How to reproduce:
-
(in one console):
# unshare --mount /bin/bash
# mount -o remount -r /

(in other console)
# touch /x
touch: cannot touch `/x': Read-only file system
# mount -o remount -w /
# touch /x

(in first console)
# touch /x
touch: cannot touch `/x': Read-only file system

What happened:
--
Read-only mount performed in private mount namespace affected main (default) 
namespace

What should have happened:
---
The read-only mount should not have affected the main namespace

(this has been seen in 3.0.0 and also 3.4.0 on precise)

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

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

Title:
  remounting root read-only in private mount namespace affects main
  namespace

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When remounting root read-only in a private mount namespace, then also
  the real root (in default namespace) is read-only.

  However, it is then possible to remount the real root read-write, and
  this doesn't (fortunately...) affect the other namespace.

  How to reproduce:
  -
  (in one console):
  # unshare --mount /bin/bash
  # mount -o remount -r /

  (in other console)
  # touch /x
  touch: cannot touch `/x': Read-only file system
  # mount -o remount -w /
  # touch /x

  (in first console)
  # touch /x
  touch: cannot touch `/x': Read-only file system

  What happened:
  --
  Read-only mount performed in private mount namespace affected main (default) 
namespace

  What should have happened:
  ---
  The read-only mount should not have affected the main namespace

  (this has been seen in 3.0.0 and also 3.4.0 on precise)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397649/+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 1397649] Re: remounting root read-only in private mount namespace affects main namespace

2014-11-30 Thread AlainKnaff
apport information

** Tags added: apport-collected precise

** Description changed:

  When remounting root read-only in a private mount namespace, then also
  the real root (in default namespace) is read-only.
  
  However, it is then possible to remount the real root read-write, and
  this doesn't (fortunately...) affect the other namespace.
  
  How to reproduce:
  -
  (in one console):
  # unshare --mount /bin/bash
  # mount -o remount -r /
  
  (in other console)
  # touch /x
  touch: cannot touch `/x': Read-only file system
  # mount -o remount -w /
  # touch /x
  
  (in first console)
  # touch /x
  touch: cannot touch `/x': Read-only file system
  
  What happened:
  --
  Read-only mount performed in private mount namespace affected main (default) 
namespace
  
  What should have happened:
  ---
  The read-only mount should not have affected the main namespace
  
  (this has been seen in 3.0.0 and also 3.4.0 on precise)
+ --- 
+ ApportVersion: 2.0.1-0ubuntu17.7
+ Architecture: amd64
+ DistroRelease: Ubuntu 12.04
+ MarkForUpload: True
+ NonfreeKernelModules: nvidia
+ Package: linux (not installed)
+ Tags:  precise
+ Uname: Linux 3.4.0-030400-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: Upgraded to precise on 2012-10-06 (784 days ago)
+ UserGroups:

** Attachment added: ProcEnviron.txt
   
https://bugs.launchpad.net/bugs/1397649/+attachment/4271128/+files/ProcEnviron.txt

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

Title:
  remounting root read-only in private mount namespace affects main
  namespace

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When remounting root read-only in a private mount namespace, then also
  the real root (in default namespace) is read-only.

  However, it is then possible to remount the real root read-write, and
  this doesn't (fortunately...) affect the other namespace.

  How to reproduce:
  -
  (in one console):
  # unshare --mount /bin/bash
  # mount -o remount -r /

  (in other console)
  # touch /x
  touch: cannot touch `/x': Read-only file system
  # mount -o remount -w /
  # touch /x

  (in first console)
  # touch /x
  touch: cannot touch `/x': Read-only file system

  What happened:
  --
  Read-only mount performed in private mount namespace affected main (default) 
namespace

  What should have happened:
  ---
  The read-only mount should not have affected the main namespace

  (this has been seen in 3.0.0 and also 3.4.0 on precise)
  --- 
  ApportVersion: 2.0.1-0ubuntu17.7
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  MarkForUpload: True
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  Tags:  precise
  Uname: Linux 3.4.0-030400-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to precise on 2012-10-06 (784 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397649/+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 1397649] Re: remounting root read-only in private mount namespace affects main namespace

2014-11-30 Thread AlainKnaff
** Changed in: linux (Ubuntu)
   Status: Incomplete = Confirmed

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

Title:
  remounting root read-only in private mount namespace affects main
  namespace

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When remounting root read-only in a private mount namespace, then also
  the real root (in default namespace) is read-only.

  However, it is then possible to remount the real root read-write, and
  this doesn't (fortunately...) affect the other namespace.

  How to reproduce:
  -
  (in one console):
  # unshare --mount /bin/bash
  # mount -o remount -r /

  (in other console)
  # touch /x
  touch: cannot touch `/x': Read-only file system
  # mount -o remount -w /
  # touch /x

  (in first console)
  # touch /x
  touch: cannot touch `/x': Read-only file system

  What happened:
  --
  Read-only mount performed in private mount namespace affected main (default) 
namespace

  What should have happened:
  ---
  The read-only mount should not have affected the main namespace

  (this has been seen in 3.0.0 and also 3.4.0 on precise)
  --- 
  ApportVersion: 2.0.1-0ubuntu17.7
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  MarkForUpload: True
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  Tags:  precise
  Uname: Linux 3.4.0-030400-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to precise on 2012-10-06 (784 days ago)
  UserGroups:

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