date:20130820

apport information

** Tags added: apport-collected saucy

** Description changed:

  I don't know if it is the right package for report but anyways.
  
  I have a keyboard and mouse connected to a base plattaform for laptops
  with a fan and a usb hub (4 spaces) (it helps to avoid hot restarts by
  heat on summer and get more usb spaces for plug gadgets).
  
  $ lsusb
  Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 036: ID 0a05:7220
  Bus 001 Device 008: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
  Bus 001 Device 004: ID 1c7a:0801 LighTuning Technology Inc. Fingerprint Reader
  Bus 002 Device 004: ID 064e:a219 Suyin Corp. 1.3M WebCam (notebook emachines 
E730, Acer sub-brand)
  Bus 001 Device 038: ID 046d:c045 Logitech, Inc. Optical Mouse
  Bus 001 Device 037: ID 046d:c315 Logitech, Inc. Classic New Touch Keyboard
  
  If I plug/unplug the only difference line is for 0a05:7220:
  
  $ lsusb -D 0a05:7220
  Cannot open 0a05:7220
  
  When I plug/unplug the base always show the same on dmesg:
  
  [1003500.857258] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.858251] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.861183] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.865210] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.865301] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.869430] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.873579] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.877580] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.880567] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.881931] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.884565] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.888711] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.888963] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.892914] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.896927] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.897546] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.900893] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.905018] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.912665] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.913567] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.916630] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.920766] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.920942] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.924914] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.928902] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.929516] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.932865] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.937209] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.941012] usb 2-1.1: USB disconnect, device number 21
  [1003500.941018] usb 2-1.1.1: USB disconnect, device number 22
  [1003500.944612] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.944621] usb 2-1.1: clear tt 1 (0160) error -19
  [1003500.956250] usb 2-1.1.4: USB disconnect, device number 23
  [1003505.051309] usb 2-1.1: new high-speed USB device number 24 using ehci_hcd
  [1003505.143985] hub 2-1.1:1.0: USB hub found
  [1003505.144253] hub 2-1.1:1.0: 4 ports detected
  [1003505.506884] usb 2-1.1.1: new low-speed USB device number 25 using 
ehci_hcd
  [1003505.609274] input: Logitech USB-PS/2 Optical Mouse as 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.1/2-1.1.1:1.0/input/input43
  [1003505.609896] hid-generic 0003:046D:C045.001F: input,hidraw0: USB HID 
v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-:00:1d.0-1.1.1/input0
  [1003505.874539] usb 2-1.1.4: new low-speed USB device number 26 using 
ehci_hcd
  [1003505.977134] input: Logitech Logitech USB Keyboard as 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.4/2-1.1.4:1.0/input/input44
  [1003505.977663] hid-generic 0003:046D:C315.0020: input,hidraw1: USB HID 
v1.10 Keyboard [Logitech Logitech USB Keyboard] on usb-:00:1d.0-1.1.4/input0
  
  It could be a issue detecting wrong propertie

[Kernel-packages] [Bug 1028137] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1028137/+attachment/3779436/+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/1028137

Title:
  hid-generic 0003:046D:C315.001E: can't reset device, status -71

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I don't know if it is the right package for report but anyways.

  I have a keyboard and mouse connected to a base plattaform for laptops
  with a fan and a usb hub (4 spaces) (it helps to avoid hot restarts by
  heat on summer and get more usb spaces for plug gadgets).

  $ lsusb
  Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 036: ID 0a05:7220
  Bus 001 Device 008: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
  Bus 001 Device 004: ID 1c7a:0801 LighTuning Technology Inc. Fingerprint Reader
  Bus 002 Device 004: ID 064e:a219 Suyin Corp. 1.3M WebCam (notebook emachines 
E730, Acer sub-brand)
  Bus 001 Device 038: ID 046d:c045 Logitech, Inc. Optical Mouse
  Bus 001 Device 037: ID 046d:c315 Logitech, Inc. Classic New Touch Keyboard

  If I plug/unplug the only difference line is for 0a05:7220:

  $ lsusb -D 0a05:7220
  Cannot open 0a05:7220

  When I plug/unplug the base always show the same on dmesg:

  [1003500.857258] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.858251] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.861183] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.865210] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.865301] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.869430] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.873579] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.877580] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.880567] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.881931] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.884565] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.888711] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.888963] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.892914] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.896927] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.897546] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.900893] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.905018] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.912665] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.913567] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.916630] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.920766] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.920942] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.924914] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.928902] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.929516] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.932865] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.937209] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.941012] usb 2-1.1: USB disconnect, device number 21
  [1003500.941018] usb 2-1.1.1: USB disconnect, device number 22
  [1003500.944612] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.944621] usb 2-1.1: clear tt 1 (0160) error -19
  [1003500.956250] usb 2-1.1.4: USB disconnect, device number 23
  [1003505.051309] usb 2-1.1: new high-speed USB device number 24 using ehci_hcd
  [1003505.143985] hub 2-1.1:1.0: USB hub found
  [1003505.144253] hub 2-1.1:1.0: 4 ports detected
  [1003505.506884] usb 2-1.1.1: new low-speed USB device number 25 using 
ehci_hcd
  [1003505.609274] input: Logitech USB-PS/2 Optical Mouse as 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.1/2-1.1.1:1.0/input/input43
  [1003505.609896] hid-generic 0003:046D:C045.001F: input,hidraw0: USB HID 
v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-:00:1d.0-1.1.1/input0
  [1003505.874539] usb 2-1.1.4: new low-speed USB device number 26 using 
ehc

[Kernel-packages] [Bug 1028137] RfKill.txt

apport information

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

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

Title:
  hid-generic 0003:046D:C315.001E: can't reset device, status -71

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I don't know if it is the right package for report but anyways.

  I have a keyboard and mouse connected to a base plattaform for laptops
  with a fan and a usb hub (4 spaces) (it helps to avoid hot restarts by
  heat on summer and get more usb spaces for plug gadgets).

  $ lsusb
  Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 036: ID 0a05:7220
  Bus 001 Device 008: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
  Bus 001 Device 004: ID 1c7a:0801 LighTuning Technology Inc. Fingerprint Reader
  Bus 002 Device 004: ID 064e:a219 Suyin Corp. 1.3M WebCam (notebook emachines 
E730, Acer sub-brand)
  Bus 001 Device 038: ID 046d:c045 Logitech, Inc. Optical Mouse
  Bus 001 Device 037: ID 046d:c315 Logitech, Inc. Classic New Touch Keyboard

  If I plug/unplug the only difference line is for 0a05:7220:

  $ lsusb -D 0a05:7220
  Cannot open 0a05:7220

  When I plug/unplug the base always show the same on dmesg:

  [1003500.857258] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.858251] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.861183] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.865210] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.865301] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.869430] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.873579] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.877580] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.880567] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.881931] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.884565] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.888711] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.888963] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.892914] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.896927] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.897546] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.900893] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.905018] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.912665] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.913567] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.916630] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.920766] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.920942] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.924914] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.928902] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.929516] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.932865] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.937209] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.941012] usb 2-1.1: USB disconnect, device number 21
  [1003500.941018] usb 2-1.1.1: USB disconnect, device number 22
  [1003500.944612] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.944621] usb 2-1.1: clear tt 1 (0160) error -19
  [1003500.956250] usb 2-1.1.4: USB disconnect, device number 23
  [1003505.051309] usb 2-1.1: new high-speed USB device number 24 using ehci_hcd
  [1003505.143985] hub 2-1.1:1.0: USB hub found
  [1003505.144253] hub 2-1.1:1.0: 4 ports detected
  [1003505.506884] usb 2-1.1.1: new low-speed USB device number 25 using 
ehci_hcd
  [1003505.609274] input: Logitech USB-PS/2 Optical Mouse as 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.1/2-1.1.1:1.0/input/input43
  [1003505.609896] hid-generic 0003:046D:C045.001F: input,hidraw0: USB HID 
v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-:00:1d.0-1.1.1/input0
  [1003505.874539] usb 2-1.1.4: new low-speed USB device number 26 using 
ehci_hcd
  [

[Kernel-packages] [Bug 1028137] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1028137/+attachment/3779426/+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/1028137

Title:
  hid-generic 0003:046D:C315.001E: can't reset device, status -71

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I don't know if it is the right package for report but anyways.

  I have a keyboard and mouse connected to a base plattaform for laptops
  with a fan and a usb hub (4 spaces) (it helps to avoid hot restarts by
  heat on summer and get more usb spaces for plug gadgets).

  $ lsusb
  Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 036: ID 0a05:7220
  Bus 001 Device 008: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
  Bus 001 Device 004: ID 1c7a:0801 LighTuning Technology Inc. Fingerprint Reader
  Bus 002 Device 004: ID 064e:a219 Suyin Corp. 1.3M WebCam (notebook emachines 
E730, Acer sub-brand)
  Bus 001 Device 038: ID 046d:c045 Logitech, Inc. Optical Mouse
  Bus 001 Device 037: ID 046d:c315 Logitech, Inc. Classic New Touch Keyboard

  If I plug/unplug the only difference line is for 0a05:7220:

  $ lsusb -D 0a05:7220
  Cannot open 0a05:7220

  When I plug/unplug the base always show the same on dmesg:

  [1003500.857258] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.858251] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.861183] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.865210] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.865301] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.869430] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.873579] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.877580] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.880567] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.881931] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.884565] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.888711] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.888963] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.892914] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.896927] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.897546] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.900893] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.905018] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.912665] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.913567] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.916630] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.920766] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.920942] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.924914] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.928902] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.929516] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.932865] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.937209] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.941012] usb 2-1.1: USB disconnect, device number 21
  [1003500.941018] usb 2-1.1.1: USB disconnect, device number 22
  [1003500.944612] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.944621] usb 2-1.1: clear tt 1 (0160) error -19
  [1003500.956250] usb 2-1.1.4: USB disconnect, device number 23
  [1003505.051309] usb 2-1.1: new high-speed USB device number 24 using ehci_hcd
  [1003505.143985] hub 2-1.1:1.0: USB hub found
  [1003505.144253] hub 2-1.1:1.0: 4 ports detected
  [1003505.506884] usb 2-1.1.1: new low-speed USB device number 25 using 
ehci_hcd
  [1003505.609274] input: Logitech USB-PS/2 Optical Mouse as 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.1/2-1.1.1:1.0/input/input43
  [1003505.609896] hid-generic 0003:046D:C045.001F: input,hidraw0: USB HID 
v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-:00:1d.0-1.1.1/input0
  [1003505.874539] usb 2-1.1.4: new low-speed USB device number 26 using 
ehci_hcd
  [10

[Kernel-packages] [Bug 1028137] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1028137/+attachment/3779431/+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/1028137

Title:
  hid-generic 0003:046D:C315.001E: can't reset device, status -71

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I don't know if it is the right package for report but anyways.

  I have a keyboard and mouse connected to a base plattaform for laptops
  with a fan and a usb hub (4 spaces) (it helps to avoid hot restarts by
  heat on summer and get more usb spaces for plug gadgets).

  $ lsusb
  Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 036: ID 0a05:7220
  Bus 001 Device 008: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
  Bus 001 Device 004: ID 1c7a:0801 LighTuning Technology Inc. Fingerprint Reader
  Bus 002 Device 004: ID 064e:a219 Suyin Corp. 1.3M WebCam (notebook emachines 
E730, Acer sub-brand)
  Bus 001 Device 038: ID 046d:c045 Logitech, Inc. Optical Mouse
  Bus 001 Device 037: ID 046d:c315 Logitech, Inc. Classic New Touch Keyboard

  If I plug/unplug the only difference line is for 0a05:7220:

  $ lsusb -D 0a05:7220
  Cannot open 0a05:7220

  When I plug/unplug the base always show the same on dmesg:

  [1003500.857258] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.858251] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.861183] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.865210] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.865301] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.869430] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.873579] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.877580] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.880567] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.881931] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.884565] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.888711] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.888963] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.892914] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.896927] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.897546] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.900893] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.905018] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.912665] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.913567] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.916630] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.920766] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.920942] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.924914] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.928902] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.929516] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.932865] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.937209] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.941012] usb 2-1.1: USB disconnect, device number 21
  [1003500.941018] usb 2-1.1.1: USB disconnect, device number 22
  [1003500.944612] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.944621] usb 2-1.1: clear tt 1 (0160) error -19
  [1003500.956250] usb 2-1.1.4: USB disconnect, device number 23
  [1003505.051309] usb 2-1.1: new high-speed USB device number 24 using ehci_hcd
  [1003505.143985] hub 2-1.1:1.0: USB hub found
  [1003505.144253] hub 2-1.1:1.0: 4 ports detected
  [1003505.506884] usb 2-1.1.1: new low-speed USB device number 25 using 
ehci_hcd
  [1003505.609274] input: Logitech USB-PS/2 Optical Mouse as 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.1/2-1.1.1:1.0/input/input43
  [1003505.609896] hid-generic 0003:046D:C045.001F: input,hidraw0: USB HID 
v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-:00:1d.0-1.1.1/input0
  [1003505.874539] usb 2-1.1.4: new low-speed USB device number 26 using 
e

[Kernel-packages] [Bug 1028137] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1028137/+attachment/3779427/+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/1028137

Title:
  hid-generic 0003:046D:C315.001E: can't reset device, status -71

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I don't know if it is the right package for report but anyways.

  I have a keyboard and mouse connected to a base plattaform for laptops
  with a fan and a usb hub (4 spaces) (it helps to avoid hot restarts by
  heat on summer and get more usb spaces for plug gadgets).

  $ lsusb
  Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 036: ID 0a05:7220
  Bus 001 Device 008: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
  Bus 001 Device 004: ID 1c7a:0801 LighTuning Technology Inc. Fingerprint Reader
  Bus 002 Device 004: ID 064e:a219 Suyin Corp. 1.3M WebCam (notebook emachines 
E730, Acer sub-brand)
  Bus 001 Device 038: ID 046d:c045 Logitech, Inc. Optical Mouse
  Bus 001 Device 037: ID 046d:c315 Logitech, Inc. Classic New Touch Keyboard

  If I plug/unplug the only difference line is for 0a05:7220:

  $ lsusb -D 0a05:7220
  Cannot open 0a05:7220

  When I plug/unplug the base always show the same on dmesg:

  [1003500.857258] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.858251] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.861183] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.865210] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.865301] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.869430] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.873579] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.877580] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.880567] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.881931] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.884565] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.888711] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.888963] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.892914] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.896927] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.897546] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.900893] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.905018] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.912665] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.913567] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.916630] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.920766] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.920942] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.924914] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.928902] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.929516] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.932865] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.937209] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.941012] usb 2-1.1: USB disconnect, device number 21
  [1003500.941018] usb 2-1.1.1: USB disconnect, device number 22
  [1003500.944612] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.944621] usb 2-1.1: clear tt 1 (0160) error -19
  [1003500.956250] usb 2-1.1.4: USB disconnect, device number 23
  [1003505.051309] usb 2-1.1: new high-speed USB device number 24 using ehci_hcd
  [1003505.143985] hub 2-1.1:1.0: USB hub found
  [1003505.144253] hub 2-1.1:1.0: 4 ports detected
  [1003505.506884] usb 2-1.1.1: new low-speed USB device number 25 using 
ehci_hcd
  [1003505.609274] input: Logitech USB-PS/2 Optical Mouse as 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.1/2-1.1.1:1.0/input/input43
  [1003505.609896] hid-generic 0003:046D:C045.001F: input,hidraw0: USB HID 
v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-:00:1d.0-1.1.1/input0
  [1003505.874539] usb 2-1.1.4: new low-speed USB device number 26 using 
ehci_hcd
  [10

[Kernel-packages] [Bug 1028137] BootDmesg.txt

apport information

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

Title:
  hid-generic 0003:046D:C315.001E: can't reset device, status -71

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I don't know if it is the right package for report but anyways.

  I have a keyboard and mouse connected to a base plattaform for laptops
  with a fan and a usb hub (4 spaces) (it helps to avoid hot restarts by
  heat on summer and get more usb spaces for plug gadgets).

  $ lsusb
  Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 036: ID 0a05:7220
  Bus 001 Device 008: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
  Bus 001 Device 004: ID 1c7a:0801 LighTuning Technology Inc. Fingerprint Reader
  Bus 002 Device 004: ID 064e:a219 Suyin Corp. 1.3M WebCam (notebook emachines 
E730, Acer sub-brand)
  Bus 001 Device 038: ID 046d:c045 Logitech, Inc. Optical Mouse
  Bus 001 Device 037: ID 046d:c315 Logitech, Inc. Classic New Touch Keyboard

  If I plug/unplug the only difference line is for 0a05:7220:

  $ lsusb -D 0a05:7220
  Cannot open 0a05:7220

  When I plug/unplug the base always show the same on dmesg:

  [1003500.857258] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.858251] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.861183] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.865210] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.865301] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.869430] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.873579] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.877580] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.880567] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.881931] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.884565] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.888711] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.888963] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.892914] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.896927] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.897546] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.900893] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.905018] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.912665] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.913567] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.916630] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.920766] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.920942] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.924914] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.928902] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.929516] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.932865] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.937209] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.941012] usb 2-1.1: USB disconnect, device number 21
  [1003500.941018] usb 2-1.1.1: USB disconnect, device number 22
  [1003500.944612] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.944621] usb 2-1.1: clear tt 1 (0160) error -19
  [1003500.956250] usb 2-1.1.4: USB disconnect, device number 23
  [1003505.051309] usb 2-1.1: new high-speed USB device number 24 using ehci_hcd
  [1003505.143985] hub 2-1.1:1.0: USB hub found
  [1003505.144253] hub 2-1.1:1.0: 4 ports detected
  [1003505.506884] usb 2-1.1.1: new low-speed USB device number 25 using 
ehci_hcd
  [1003505.609274] input: Logitech USB-PS/2 Optical Mouse as 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.1/2-1.1.1:1.0/input/input43
  [1003505.609896] hid-generic 0003:046D:C045.001F: input,hidraw0: USB HID 
v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-:00:1d.0-1.1.1/input0
  [1003505.874539] usb 2-1.1.4: new low-speed USB device number 26 using 
ehci_

[Kernel-packages] [Bug 1028137] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1028137/+attachment/3779424/+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/1028137

Title:
  hid-generic 0003:046D:C315.001E: can't reset device, status -71

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I don't know if it is the right package for report but anyways.

  I have a keyboard and mouse connected to a base plattaform for laptops
  with a fan and a usb hub (4 spaces) (it helps to avoid hot restarts by
  heat on summer and get more usb spaces for plug gadgets).

  $ lsusb
  Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 036: ID 0a05:7220
  Bus 001 Device 008: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
  Bus 001 Device 004: ID 1c7a:0801 LighTuning Technology Inc. Fingerprint Reader
  Bus 002 Device 004: ID 064e:a219 Suyin Corp. 1.3M WebCam (notebook emachines 
E730, Acer sub-brand)
  Bus 001 Device 038: ID 046d:c045 Logitech, Inc. Optical Mouse
  Bus 001 Device 037: ID 046d:c315 Logitech, Inc. Classic New Touch Keyboard

  If I plug/unplug the only difference line is for 0a05:7220:

  $ lsusb -D 0a05:7220
  Cannot open 0a05:7220

  When I plug/unplug the base always show the same on dmesg:

  [1003500.857258] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.858251] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.861183] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.865210] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.865301] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.869430] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.873579] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.877580] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.880567] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.881931] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.884565] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.888711] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.888963] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.892914] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.896927] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.897546] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.900893] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.905018] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.912665] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.913567] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.916630] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.920766] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.920942] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.924914] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.928902] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.929516] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.932865] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.937209] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.941012] usb 2-1.1: USB disconnect, device number 21
  [1003500.941018] usb 2-1.1.1: USB disconnect, device number 22
  [1003500.944612] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.944621] usb 2-1.1: clear tt 1 (0160) error -19
  [1003500.956250] usb 2-1.1.4: USB disconnect, device number 23
  [1003505.051309] usb 2-1.1: new high-speed USB device number 24 using ehci_hcd
  [1003505.143985] hub 2-1.1:1.0: USB hub found
  [1003505.144253] hub 2-1.1:1.0: 4 ports detected
  [1003505.506884] usb 2-1.1.1: new low-speed USB device number 25 using 
ehci_hcd
  [1003505.609274] input: Logitech USB-PS/2 Optical Mouse as 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.1/2-1.1.1:1.0/input/input43
  [1003505.609896] hid-generic 0003:046D:C045.001F: input,hidraw0: USB HID 
v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-:00:1d.0-1.1.1/input0
  [1003505.874539] usb 2-1.1.4: new low-speed USB device number 26 using

[Kernel-packages] [Bug 1028137] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1028137/+attachment/3779425/+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/1028137

Title:
  hid-generic 0003:046D:C315.001E: can't reset device, status -71

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I don't know if it is the right package for report but anyways.

  I have a keyboard and mouse connected to a base plattaform for laptops
  with a fan and a usb hub (4 spaces) (it helps to avoid hot restarts by
  heat on summer and get more usb spaces for plug gadgets).

  $ lsusb
  Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 036: ID 0a05:7220
  Bus 001 Device 008: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
  Bus 001 Device 004: ID 1c7a:0801 LighTuning Technology Inc. Fingerprint Reader
  Bus 002 Device 004: ID 064e:a219 Suyin Corp. 1.3M WebCam (notebook emachines 
E730, Acer sub-brand)
  Bus 001 Device 038: ID 046d:c045 Logitech, Inc. Optical Mouse
  Bus 001 Device 037: ID 046d:c315 Logitech, Inc. Classic New Touch Keyboard

  If I plug/unplug the only difference line is for 0a05:7220:

  $ lsusb -D 0a05:7220
  Cannot open 0a05:7220

  When I plug/unplug the base always show the same on dmesg:

  [1003500.857258] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.858251] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.861183] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.865210] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.865301] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.869430] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.873579] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.877580] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.880567] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.881931] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.884565] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.888711] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.888963] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.892914] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.896927] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.897546] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.900893] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.905018] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.912665] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.913567] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.916630] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.920766] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.920942] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.924914] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.928902] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.929516] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.932865] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.937209] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.941012] usb 2-1.1: USB disconnect, device number 21
  [1003500.941018] usb 2-1.1.1: USB disconnect, device number 22
  [1003500.944612] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.944621] usb 2-1.1: clear tt 1 (0160) error -19
  [1003500.956250] usb 2-1.1.4: USB disconnect, device number 23
  [1003505.051309] usb 2-1.1: new high-speed USB device number 24 using ehci_hcd
  [1003505.143985] hub 2-1.1:1.0: USB hub found
  [1003505.144253] hub 2-1.1:1.0: 4 ports detected
  [1003505.506884] usb 2-1.1.1: new low-speed USB device number 25 using 
ehci_hcd
  [1003505.609274] input: Logitech USB-PS/2 Optical Mouse as 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.1/2-1.1.1:1.0/input/input43
  [1003505.609896] hid-generic 0003:046D:C045.001F: input,hidraw0: USB HID 
v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-:00:1d.0-1.1.1/input0
  [1003505.874539] usb 2-1.1.4: new low-speed USB device number 26 using 
ehci_hc

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

apport information

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

Title:
  hid-generic 0003:046D:C315.001E: can't reset device, status -71

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I don't know if it is the right package for report but anyways.

  I have a keyboard and mouse connected to a base plattaform for laptops
  with a fan and a usb hub (4 spaces) (it helps to avoid hot restarts by
  heat on summer and get more usb spaces for plug gadgets).

  $ lsusb
  Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 036: ID 0a05:7220
  Bus 001 Device 008: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
  Bus 001 Device 004: ID 1c7a:0801 LighTuning Technology Inc. Fingerprint Reader
  Bus 002 Device 004: ID 064e:a219 Suyin Corp. 1.3M WebCam (notebook emachines 
E730, Acer sub-brand)
  Bus 001 Device 038: ID 046d:c045 Logitech, Inc. Optical Mouse
  Bus 001 Device 037: ID 046d:c315 Logitech, Inc. Classic New Touch Keyboard

  If I plug/unplug the only difference line is for 0a05:7220:

  $ lsusb -D 0a05:7220
  Cannot open 0a05:7220

  When I plug/unplug the base always show the same on dmesg:

  [1003500.857258] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.858251] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.861183] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.865210] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.865301] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.869430] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.873579] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.877580] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.880567] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.881931] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.884565] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.888711] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.888963] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.892914] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.896927] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.897546] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.900893] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.905018] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.912665] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.913567] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.916630] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.920766] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.920942] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.924914] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.928902] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.929516] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.932865] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.937209] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.941012] usb 2-1.1: USB disconnect, device number 21
  [1003500.941018] usb 2-1.1.1: USB disconnect, device number 22
  [1003500.944612] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.944621] usb 2-1.1: clear tt 1 (0160) error -19
  [1003500.956250] usb 2-1.1.4: USB disconnect, device number 23
  [1003505.051309] usb 2-1.1: new high-speed USB device number 24 using ehci_hcd
  [1003505.143985] hub 2-1.1:1.0: USB hub found
  [1003505.144253] hub 2-1.1:1.0: 4 ports detected
  [1003505.506884] usb 2-1.1.1: new low-speed USB device number 25 using 
ehci_hcd
  [1003505.609274] input: Logitech USB-PS/2 Optical Mouse as 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.1/2-1.1.1:1.0/input/input43
  [1003505.609896] hid-generic 0003:046D:C045.001F: input,hidraw0: USB HID 
v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-:00:1d.0-1.1.1/input0
  [1003505.874539] usb 2-1.1.4: new low-speed USB device number 26 using 
ehci_hcd
  [1003

[Kernel-packages] [Bug 1028137] UdevLog.txt

apport information

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

Title:
  hid-generic 0003:046D:C315.001E: can't reset device, status -71

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I don't know if it is the right package for report but anyways.

  I have a keyboard and mouse connected to a base plattaform for laptops
  with a fan and a usb hub (4 spaces) (it helps to avoid hot restarts by
  heat on summer and get more usb spaces for plug gadgets).

  $ lsusb
  Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 036: ID 0a05:7220
  Bus 001 Device 008: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
  Bus 001 Device 004: ID 1c7a:0801 LighTuning Technology Inc. Fingerprint Reader
  Bus 002 Device 004: ID 064e:a219 Suyin Corp. 1.3M WebCam (notebook emachines 
E730, Acer sub-brand)
  Bus 001 Device 038: ID 046d:c045 Logitech, Inc. Optical Mouse
  Bus 001 Device 037: ID 046d:c315 Logitech, Inc. Classic New Touch Keyboard

  If I plug/unplug the only difference line is for 0a05:7220:

  $ lsusb -D 0a05:7220
  Cannot open 0a05:7220

  When I plug/unplug the base always show the same on dmesg:

  [1003500.857258] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.858251] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.861183] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.865210] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.865301] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.869430] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.873579] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.877580] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.880567] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.881931] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.884565] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.888711] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.888963] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.892914] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.896927] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.897546] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.900893] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.905018] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.912665] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.913567] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.916630] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.920766] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.920942] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.924914] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.928902] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.929516] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.932865] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.937209] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.941012] usb 2-1.1: USB disconnect, device number 21
  [1003500.941018] usb 2-1.1.1: USB disconnect, device number 22
  [1003500.944612] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.944621] usb 2-1.1: clear tt 1 (0160) error -19
  [1003500.956250] usb 2-1.1.4: USB disconnect, device number 23
  [1003505.051309] usb 2-1.1: new high-speed USB device number 24 using ehci_hcd
  [1003505.143985] hub 2-1.1:1.0: USB hub found
  [1003505.144253] hub 2-1.1:1.0: 4 ports detected
  [1003505.506884] usb 2-1.1.1: new low-speed USB device number 25 using 
ehci_hcd
  [1003505.609274] input: Logitech USB-PS/2 Optical Mouse as 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.1/2-1.1.1:1.0/input/input43
  [1003505.609896] hid-generic 0003:046D:C045.001F: input,hidraw0: USB HID 
v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-:00:1d.0-1.1.1/input0
  [1003505.874539] usb 2-1.1.4: new low-speed USB device number 26 using 
ehci_hcd

[Kernel-packages] [Bug 1212455] Re: 8086:2562 Flash 11.2 content displays in shades of green and purple only, and in a horizontally compressed space

2013-08-20 Thread John Hupp

In an off-Launchpad direct exchange, I received some direction that "You
would want to bisect the mainline kernel instead of the Ubuntu kernel."

I should say more directly that I have never done kernel bisection until
now, though I'm game for the effort.  Nonetheless, very little can be
taken for granted.

Does the above direction mean that when I get to the procedure "Commit
bisecting Ubuntu kernel versions" at
https://wiki.ubuntu.com/Kernel/KernelBisection, I should use it only as
some sort of a general guideline and switch to commit bisecting mainline
kernels?

If so, I'm not seeing how.  Still assuming that I should use git bisect,
I'm not seeing an identifiable *mainline* git repo at
http://kernel.ubuntu.com/git, and alternatively I'm not seeing *git*
repos at http://kernel.ubuntu.com/~kernel-ppa/mainline/.  Perhaps there
are non-Ubuntu-related mainline git repos somewhere that I should be
using.

I'm sure this is all laughably self-evident to any developer reading
this, but I'm just a somewhat experienced user trying to work in the
higher realms where bugs are fixed, so kindly indulge me.

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

Title:
  8086:2562 Flash 11.2 content displays in shades of green and purple
  only, and in a horizontally compressed space

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  In my testing with the Intel driver using its default acceleration, what 
works:
  - Flash 11.2 works on Quantal with the 3.5 kernel
  - Flash 11.2 works on Raring with the 3.5.0-17 kernel (though it boots to a 
low-res desktop with a frozen pointer)
  - Flash 11.2 works on Raring also with the 3.6.11-030611 or 3.7.10-030710 
mainline kernels
  - Flash 11.2 works on Raring with the 3.8 kernel (in Chrome)

  what fails:
  - Flash 11.2 fails on Raring with the 3.8 kernel
  - Flash 11.2 fails on Raring with the latest mainline kernel, 3.11.0-031100rc5
  - Flash 11.2 fails on Saucy alpha 2 with its default kernel

  Disabling Flash *hardware* acceleration altogether (via R-click in the
  Flash display window: Settings: General tab) did not fix the problem.

  WORKAROUND: Setting the Intel driver's acceleration method to UXA
  rather than its default SNA *always* fixes the Flash problem, but
  causes a garbled login screen under LightDM that so far has no
  workaround.

  I also tried one possible fix for the default Intel SNA acceleration using 
the TearFree option.   I created /etc/X11/xorg.conf.d/20-intel.conf with 
contents:
  Section "Device"
     Identifier  "Intel Graphics"
     Driver  "intel"
     Option  "AccelMethod"  "sna"
     Option  "TearFree""true"
  EndSection
  But this had no effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-27-generic 3.8.0-27.40
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic i686
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user1  1467 F lxpanel
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  CurrentDmesg:
   [   72.390428] serial8250: too much work for irq17
   [   72.401696] serial8250: too much work for irq17
   [   72.411724] serial8250: too much work for irq17
   [   82.046726] serial8250: too much work for irq17
  Date: Wed Aug 14 17:39:10 2013
  HibernationDevice: RESUME=UUID=8adf1633-c1a8-4392-8fc3-44369bc85692
  IwConfig:
   lono wireless extensions.

   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Dell Computer Corporation Dimension 2400
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic 
root=UUID=a41f2f68-7642-46f9-88d8-08a656c1c40d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-27-generic N/A
   linux-backports-modules-3.8.0-27-generic  N/A
   linux-firmware1.106
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2003
  dmi.bios.vendor: Dell Computer Corporation
  dmi.bios.version: A05
  dmi.board.name: 0F5949
  dmi.board.vendor: Dell Computer Corp.
  dmi.board.version: A01
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Computer Corporation
  dmi.modalias: 
dmi:bvnDellComputerCorporation:bvrA05:bd12/02/2003:svnDellComputerCorporation:pnDimension2400:pvr:rvnDellComputerCorp.:rn0F5949:rvrA01:cvnDellComputerCorporation:ct15:cvr:
  dmi.product.name: Dimension 2400
  dmi.sys.vendor: Dell Computer Corporation

To manage

[Kernel-packages] [Bug 1028137] Re: hid-generic 0003:046D:C315.001E: can't reset device, status -71

** Tags removed: needs-upstream-testing
** Tags added: kernel-bug-exists-upstream-v3.11-rc5-saucy

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

Title:
  hid-generic 0003:046D:C315.001E: can't reset device, status -71

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I don't know if it is the right package for report but anyways.

  I have a keyboard and mouse connected to a base plattaform for laptops
  with a fan and a usb hub (4 spaces) (it helps to avoid hot restarts by
  heat on summer and get more usb spaces for plug gadgets).

  $ lsusb
  Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 036: ID 0a05:7220
  Bus 001 Device 008: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
  Bus 001 Device 004: ID 1c7a:0801 LighTuning Technology Inc. Fingerprint Reader
  Bus 002 Device 004: ID 064e:a219 Suyin Corp. 1.3M WebCam (notebook emachines 
E730, Acer sub-brand)
  Bus 001 Device 038: ID 046d:c045 Logitech, Inc. Optical Mouse
  Bus 001 Device 037: ID 046d:c315 Logitech, Inc. Classic New Touch Keyboard

  If I plug/unplug the only difference line is for 0a05:7220:

  $ lsusb -D 0a05:7220
  Cannot open 0a05:7220

  When I plug/unplug the base always show the same on dmesg:

  [1003500.857258] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.858251] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.861183] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.865210] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.865301] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.869430] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.873579] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.877580] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.880567] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.881931] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.884565] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.888711] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.888963] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.892914] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.896927] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.897546] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.900893] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.905018] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.912665] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.913567] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.916630] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.920766] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.920942] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.924914] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.928902] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.929516] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.932865] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.937209] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.941012] usb 2-1.1: USB disconnect, device number 21
  [1003500.941018] usb 2-1.1.1: USB disconnect, device number 22
  [1003500.944612] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.944621] usb 2-1.1: clear tt 1 (0160) error -19
  [1003500.956250] usb 2-1.1.4: USB disconnect, device number 23
  [1003505.051309] usb 2-1.1: new high-speed USB device number 24 using ehci_hcd
  [1003505.143985] hub 2-1.1:1.0: USB hub found
  [1003505.144253] hub 2-1.1:1.0: 4 ports detected
  [1003505.506884] usb 2-1.1.1: new low-speed USB device number 25 using 
ehci_hcd
  [1003505.609274] input: Logitech USB-PS/2 Optical Mouse as 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.1/2-1.1.1:1.0/input/input43
  [1003505.609896] hid-generic 0003:046D:C045.001F: input,hidraw0: USB HID 
v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-:00:1d.0-1.1.1/input0
  [1003505.874539] usb 2-1.1.4: new low-speed USB device number 26 using 
ehci_hcd
  [1003505.977134] input: Logitech Logit

[Kernel-packages] [Bug 1212977] Re: saucy daily-live images are unbootable on Dell Optiplex 990; stuck in BusyBox shell

One thing we could do would be to install Raring, but then boot some
Saucy kernels on it, to identify the earliest kernel that did boot and
the first that didn't boot.  Do you think this is something you could
try?

** Tags removed: kernel-key
** Tags added: kernel-da-key

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

Title:
  saucy daily-live images are unbootable on Dell Optiplex 990; stuck in
  BusyBox shell

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  saucy daily-live images are unbootable on Dell Optiplex 990. I just get a 
BusyBox shell.
  I have tried the latest live images for the past few days without any luck. 
And the bug persists regardless of which graphics card (or none) I have in.

  Tried at least:
  http://cdimage.ubuntu.com/daily-live/20130814/
  http://cdimage.ubuntu.com/daily-live/20130815/

  and the Optiplex 990 cannot boot them.

  Interestingly, the same USB images do boot successfully on a Thinkpad X220.
  --- 
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan2083 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  DistroRelease: Ubuntu 13.04
  HibernationDevice: RESUME=UUID=9e3dac8a-8fa4-4da5-b4d2-52b2ee5fd022
  InstallationDate: Installed on 2013-06-03 (76 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 990
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic 
root=UUID=416f5f80-6d98-4208-a3f5-ef272b12e5c6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-25-generic N/A
   linux-backports-modules-3.8.0-25-generic  N/A
   linux-firmware1.106
  RfKill:
   
  Tags:  raring
  Uname: Linux 3.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 09/10/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0D6H9T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/10/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn0D6H9T:rvrA00:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212977/+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 1028137] Re: hid-generic 0003:046D:C315.001E: can't reset device, status -71

Testing with Linux 3.11.0-1-generic (really v3.11-rc5-saucy) I get a
massive failure of hardware support.

USB keyboard and USB mouse keyboard are not detected. No ethernet
wireless or cable devices detected. I even have to launch "onboard"
application (assistive keyboard on screen) for try to fill this bug.

I test too with 3.8.0-13 generic that it doesn't have this massive
failure harware support, and I still get the same errors in dmesg.

I attach the dmesg for 3.11 that I think that contains traces for fix
the problems. For example this BIOS bug message:

[0.467862] ACPI FADT declares the system doesn't support PCIe ASPM, so 
disable it
[0.467865] ACPI: bus type PCI registered
[0.467868] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[0.467951] PCI: MMCONFIG for domain  [bus 00-ff] at [mem 
0xe000-0xefff] (base 0xe000)
[0.467954] PCI: MMCONFIG at [mem 0xe000-0xefff] reserved in E820
[0.467956] PCI: Using MMCONFIG for extended config space
[0.467958] PCI: Using configuration type 1 for base access
[0.469390] bio: create slab  at 0
[0.469616] ACPI: Added _OSI(Module Device)
[0.469619] ACPI: Added _OSI(Processor Device)
[0.469621] ACPI: Added _OSI(3.0 _SCP Extensions)
[0.469624] ACPI: Added _OSI(Processor Aggregator Device)
[0.473466] ACPI: EC: Look up EC in DSDT
[0.477336] ACPI: Executed 1 blocks of module-level executable AML code
[0.499958] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[0.500577] ACPI: SSDT bbe91a98 002E8 (v01  PmRef  Cpu0Ist 3000 INTL 
20051117)
[0.501530] ACPI: Dynamic OEM Table Load:
[0.501533] ACPI: SSDT   (null) 002E8 (v01  PmRef  Cpu0Ist 3000 INTL 
20051117)
[0.501742] ACPI: SSDT bbe90018 00891 (v01  PmRef  Cpu0Cst 3001 INTL 
20051117)
[0.502659] ACPI: Dynamic OEM Table Load:
[0.502662] ACPI: SSDT   (null) 00891 (v01  PmRef  Cpu0Cst 3001 INTL 
20051117)
[0.522855] ACPI: SSDT bbe91718 00303 (v01  PmRefApIst 3000 INTL 
20051117)
[0.523891] ACPI: Dynamic OEM Table Load:
[0.523894] ACPI: SSDT   (null) 00303 (v01  PmRefApIst 3000 INTL 
20051117)
[0.532856] ACPI: SSDT bbe8fd98 00119 (v01  PmRefApCst 3000 INTL 
20051117)
[0.533826] ACPI: Dynamic OEM Table Load:
[0.533829] ACPI: SSDT   (null) 00119 (v01  PmRefApCst 3000 INTL 
20051117)
[0.560849] ACPI: Interpreter enabled
[0.560869] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State 
[\_S1_] (20130517/hwxface-571)
[0.560876] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State 
[\_S2_] (20130517/hwxface-571)
[0.560901] ACPI: (supports S0 S3 S4 S5)
[0.560903] ACPI: Using IOAPIC for interrupt routing
[0.560945] PCI: Using host bridge windows from ACPI; if necessary, use 
"pci=nocrs" and report a bug

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

Title:
  hid-generic 0003:046D:C315.001E: can't reset device, status -71

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I don't know if it is the right package for report but anyways.

  I have a keyboard and mouse connected to a base plattaform for laptops
  with a fan and a usb hub (4 spaces) (it helps to avoid hot restarts by
  heat on summer and get more usb spaces for plug gadgets).

  $ lsusb
  Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 036: ID 0a05:7220
  Bus 001 Device 008: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
  Bus 001 Device 004: ID 1c7a:0801 LighTuning Technology Inc. Fingerprint Reader
  Bus 002 Device 004: ID 064e:a219 Suyin Corp. 1.3M WebCam (notebook emachines 
E730, Acer sub-brand)
  Bus 001 Device 038: ID 046d:c045 Logitech, Inc. Optical Mouse
  Bus 001 Device 037: ID 046d:c315 Logitech, Inc. Classic New Touch Keyboard

  If I plug/unplug the only difference line is for 0a05:7220:

  $ lsusb -D 0a05:7220
  Cannot open 0a05:7220

  When I plug/unplug the base always show the same on dmesg:

  [1003500.857258] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.858251] hid-generic 0003:046D:C315.001E: can't reset device, 
:00:1d.0-1.1.4/input0, status -71
  [1003500.861183] usb 2-1.1: clear tt 1 (0160) error -71
  [1003500.865210] hid-generic 0003:046D:C045.001D: can't reset device, 
:00:1d.0-1.1.1/input0, status -71
  [1003500.865301] usb 2-1.1: clear tt 1 (0170) error -71
  [1003500.869430] usb 2-1.1: clear tt 1 (0160) error -71
  [100350

[Kernel-packages] [Bug 1181755] Re: aufs include is broken

2013-08-20 Thread Tim Gardner

** Also affects: linux (Ubuntu Saucy)
   Importance: Undecided
   Status: Confirmed

** Also affects: aufs-tools (Ubuntu Saucy)
   Importance: High
   Status: Confirmed

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

** Changed in: linux (Ubuntu Saucy)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  aufs include is broken

Status in “aufs-tools” package in Ubuntu:
  Confirmed
Status in “linux” package in Ubuntu:
  Fix Committed
Status in “aufs-tools” source package in Saucy:
  Confirmed
Status in “linux” source package in Saucy:
  Fix Committed

Bug description:
  aufs-tools fails to build from source on Saucy but works on Raring.

  make[1]: Entering directory `/«BUILDDIR»/aufs-tools-3.0+20130111'
  cc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
-Werror=format-security -I./libau -O -Wall -D_FORTIFY_SOURCE=2 
-DMOUNT_CMD_PATH=\"\" -Wl,-Bsymbolic-functions -Wl,-z,relro  ver.c   -o ver
  In file included from ver.c:19:0:
  /usr/include/linux/aufs_type.h:19:34: fatal error: uapi/linux/aufs_type.h: No 
such file or directory
   #include 
     ^
  compilation terminated.

  I then looked at /usr/include/linux/aufs_type.h and I see that it only 
contains one line:
  #include 

  But there isn't a /usr/include/uapi/linux/aufs_type.h

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.9.0-2-generic 3.9.0-2.6
  ProcVersionSignature: Ubuntu 3.9.0-2.6-generic 3.9.2
  Uname: Linux 3.9.0-2-generic x86_64
  ApportVersion: 2.10.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeremy 7559 F pulseaudio
  Date: Sun May 19 09:36:58 2013
  HibernationDevice: RESUME=UUID=8a987d31-1e7f-4075-9eb9-3d8f865d69e5
  MachineType: TOSHIBA Satellite L745
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-2-generic 
root=UUID=da074346-bf87-4cf5-a9ec-8589cb501c4e ro quiet splash 
usbcore.autosuspend=-1 vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions:
   linux-restricted-modules-3.9.0-2-generic N/A
   linux-backports-modules-3.9.0-2-generic  N/A
   linux-firmware   1.108
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-05-07 (11 days ago)
  WifiSyslog:

  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1181755/+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 1166442] Re: Elantech clickpad/touchpad lacks multitouch features.

2013-08-20 Thread plangeard

Hi,
I using a Samsung NP530U4E, after updating last version (3.8.0-29-generic 
#42-Ubuntu) , it still not works !
After checking "Two finger scroll" in mouse settings, it works fine.

Many thanks to solve that issue.
Cheers,

Paul

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

Title:
  Elantech clickpad/touchpad lacks multitouch features.

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Precise:
  Fix Released
Status in “linux” source package in Quantal:
  Fix Released
Status in “linux” source package in Raring:
  Fix Released
Status in “linux” source package in Saucy:
  Fix Released
Status in “linux” package in Arch Linux:
  New

Bug description:
  Newer versions of the Elantech multitouch trackpad are not fully
  supported in Linux.  These appear in many of the newer Samsung
  laptops, for example.  elantech.c in the kernel needs to be updated to
  support these models (up to v7 perhaps?)

  This bug is confirmed to affect a range of samsung laptops running
  Ubuntu 12.04 and newer, ArchLinux, Fedora and also affects the current
  (3.9) upstream kernel.

  A dkms package was produced in 2011 (see
  https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
  intel/+bug/681904/comments/64) which may fix certain older laptops
  affected by this issue, but doesn't fix newer models.

  == Original Report ==

  Hello,

  So far I've been having a problem with my Elantech multitouch trackpad in 
Linux. Basically all i get is right click, left click, and tap to click, along 
with basic  movement. The problem seems to be rooted in improper detection of 
the trackpad, likely b/c its a new revision or whatnot. Of note is that working 
elantech trackpads of the past in forums i scouted through show up as "ETPS/2 
Elantech Touchpad". Mine just shows up in xinput as "PS/2 Elantech Touchpad". I 
think this might be a simple fix in the end, just improper detection, I hope. 
For reference, I've tried kernel 3.5 on Ubuntu 12.10 and kernel 3.8.0-17 on 
Ubuntu 13.04 thus far, with all combinations of psmouse.
  
--
  What's expected: touchpad multitouch support
  What happened: basic touchpad support
  Laptop mode: Samsung Series 7 NP780 series
  Ubuntu distro(s) tested: Ubuntu 12.10, Ubuntu 13.04
  Kernels used: 3.5 signed (Ubuntu 12.10 default), 3.8.0-16, 3.8.0-17 signed
  Other tests: Attempted using psmouse-elantech-v6, psmouse-alps, and 
psmouse-alps-dst. No improvements so removed.

  synclient -l reports "Couldn't find synaptics properties. No synaptics driver 
loaded?"
  
--
  See attached for more info. Ask anything you need!
  ---
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gscoppino   2272 F pulseaudio
  DistroRelease: Ubuntu 13.04
  HibernationDevice: RESUME=UUID=f683852c-7aa0-4f32-8b86-56f0a018989d
  InstallationDate: Installed on 2013-04-06 (3 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 770Z5E/780Z5E/870Z5E/880Z5E
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic.efi.signed 
root=UUID=cf39fbe5-c8ff-4d16-b11e-a41a4f3ae955 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-17-generic N/A
   linux-backports-modules-3.8.0-17-generic  N/A
   linux-firmware1.104
  StagingDrivers: rts5139
  Tags:  raring staging
  Uname: Linux 3.8.0-17-generic x86_64
  UpgradeStatus: Upgraded to raring on 2013-04-06 (3 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 02/26/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P03ABU.139.130226.SK
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP780Z5E-S01UB
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP03ABU.139.130226.SK:bd02/26/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn770Z5E/780Z5E/870Z5E/880Z5E:pvrP03ABU:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP780Z5E-S01UB:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 770Z5E/780Z5E/870Z5E/880Z5E
  dmi.product.version: P03ABU
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

[Kernel-packages] [Bug 1214287] Re: [Dell Inspiron 15R 5521] suspend/resume failure

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.11 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc6-saucy/


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

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

Title:
  [Dell Inspiron 15R 5521] suspend/resume failure

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Dell Inc. Inspiron 5521 often crash when resuming.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-2-generic 3.11.0-2.5
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas2763 F pulseaudio
  Date: Tue Aug 20 10:02:28 2013
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=173db09c-bffc-4da9-ab42-7ca73f84e71f
  InstallationDate: Installed on 2013-04-08 (133 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  InterpreterPath: /usr/bin/python3.3
  MachineType: Dell Inc. Inspiron 5521
  MarkForUpload: True
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic 
root=UUID=09af3e13-8004-48fa-b0fe-116acbf8d3d7 ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash acpi_osi=Linux 
acpi_backlight=vendor vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-2-generic N/A
   linux-backports-modules-3.11.0-2-generic  N/A
   linux-firmware1.113
  SourcePackage: linux
  StagingDrivers: rts5139
  Title: [Dell Inc. Inspiron 5521] suspend/resume failure
  UpgradeStatus: Upgraded to saucy on 2013-06-24 (56 days ago)
  UserGroups:
   
  dmi.bios.date: 05/20/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0HK2KG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd05/20/2013:svnDellInc.:pnInspiron5521:pvrA08:rvnDellInc.:rn0HK2KG:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 5521
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214287/+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 1214285] Re: package linux-image-3.2.0-52-generic 3.2.0-52.78 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)

You may need to run the following:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package.

If that does not resolve your issue, please mark the bug as "Confirmed"

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

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

Title:
  package linux-image-3.2.0-52-generic 3.2.0-52.78 failed to
  install/upgrade: subprocess installed post-installation script was
  killed by signal (Terminated)

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  The postinstall script hanged and had to be terminated manually.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-52-generic 3.2.0-52.78
  ProcVersionSignature: Ubuntu 3.2.0-51.77-generic 3.2.48
  Uname: Linux 3.2.0-51-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  simon  2684 F pulseaudio
   /dev/snd/controlC0:  simon  2684 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xdcb6 irq 45'
 Mixer name : 'Realtek ALC269VB'
 Components : 'HDA:10ec0269,102804ad,00100100'
 Controls  : 26
 Simple ctrls  : 14
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xdc08 irq 17'
 Mixer name : 'Nvidia GPU 14 HDMI/DP'
 Components : 'HDA:10de0014,10de0101,00100100'
 Controls  : 24
 Simple ctrls  : 4
  Date: Tue Aug 20 10:04:47 2013
  DuplicateSignature: 
package:linux-image-3.2.0-52-generic:3.2.0-52.78:subprocess installed 
post-installation script was killed by signal (Terminated)
  ErrorMessage: subprocess installed post-installation script was killed by 
signal (Terminated)
  HibernationDevice: RESUME=UUID=72a5788c-f177-4e43-b9d8-c0f36a8b15e1
  InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 
(20110720.1)
  MachineType: Dell Inc. OptiPlex 790
  MarkForUpload: True
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-51-generic 
root=UUID=ad0856ea-a889-40c5-b0ab-0638c3d5f3be ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 1.99-21ubuntu3.10
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: mei
  Title: package linux-image-3.2.0-52-generic 3.2.0-52.78 failed to 
install/upgrade: subprocess installed post-installation script was killed by 
signal (Terminated)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0HY9JP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/10/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 790
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214285/+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 1214191] Re: [Hewlett-Packard HP Pavilion g6 Notebook PC] suspend/resume failure [non-free: wl]

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

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

Title:
  [Hewlett-Packard HP Pavilion g6 Notebook PC] suspend/resume failure
  [non-free: wl]

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  :(

  ProblemType: KernelOops
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-2-generic 3.11.0-2.5
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  NonfreeKernelModules: wl
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mohamed1757 F pulseaudio
  CurrentDmesg: [   36.404114] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link 
becomes ready
  Date: Tue Aug 20 03:03:26 2013
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=2e8bdb7e-7c4d-42e7-9ed7-0fb5dbb2df9f
  InstallationDate: Installed on 2013-07-27 (23 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterpreterPath: /usr/bin/python3.3
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  MarkForUpload: True
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic 
root=UUID=c3500337-471d-4bee-bcbc-fc91bc5e1e72 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-2-generic N/A
   linux-backports-modules-3.11.0-2-generic  N/A
   linux-firmware1.113
  SourcePackage: linux
  Title: [Hewlett-Packard HP Pavilion g6 Notebook PC] suspend/resume failure 
[non-free: wl]
  UpgradeStatus: Upgraded to saucy on 2013-08-04 (15 days ago)
  UserGroups:
   
  dmi.bios.date: 05/04/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1670
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 09.24
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.14:bd05/04/2011:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr0597110047160:rvnHewlett-Packard:rn1670:rvr09.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.version: 0597110047160
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214191/+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 1214129] Re: [Microsoft Corporation Surface with Windows 8 Pro] suspend/resume failure

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.11 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc6-saucy/


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

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

Title:
  [Microsoft Corporation Surface with Windows 8 Pro] suspend/resume
  failure

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  After going to suspend mode, the surface didn't start up again. I
  think it has something to do with the new method for hybernation mode
  to reduce power consumption and the lack of support for that in the
  linux kernel?

  ProblemType: KernelOops
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-2-generic 3.11.0-2.5
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lukas  1725 F pulseaudio
  Date: Mon Aug 19 22:34:55 2013
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=9912aa63-45a1-4224-b83a-9f2d8280c4dc
  InstallationDate: Installed on 2013-08-06 (13 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterpreterPath: /usr/bin/python3.3
  MachineType: Microsoft Corporation Surface with Windows 8 Pro
  MarkForUpload: True
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic 
root=UUID=f84ce05f-9146-4c97-8438-72b8f37dafad ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-2-generic N/A
   linux-backports-modules-3.11.0-2-generic  N/A
   linux-firmware1.113
  SourcePackage: linux
  Title: [Microsoft Corporation Surface with Windows 8 Pro] suspend/resume 
failure
  UpgradeStatus: Upgraded to saucy on 2013-08-07 (11 days ago)
  UserGroups:
   
  dmi.bios.date: 03/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.0450
  dmi.board.asset.tag: 0
  dmi.board.name: Surface with Windows 8 Pro
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: 0
  dmi.chassis.type: 17
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.0450:bd03/29/2013:svnMicrosoftCorporation:pnSurfacewithWindows8Pro:pvr1:rvnMicrosoftCorporation:rnSurfacewithWindows8Pro:rvr1:cvnMicrosoftCorporation:ct17:cvr1:
  dmi.product.name: Surface with Windows 8 Pro
  dmi.product.version: 1
  dmi.sys.vendor: Microsoft Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214129/+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 1214319] Re: 046d:c52b USB Mouse and keyboard freezes randomly but often

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.11 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc6-saucy/


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

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

Title:
  046d:c52b USB Mouse and keyboard freezes randomly but often

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Using UBS mouse and/or keyboard let my Ubuntu freezing very often. Not
  everytime it occures, but quite often. Then only a reboot is possible.
  Also, when Ubuntu freezes, only the usb is affected. So actually
  ubuntu is still working, but the usb system is off. There is also not
  a single event about that in the kernel log.

  BIOS:
  
http://www.ecs.com.tw/ECSWebSite/Product/Product_Detail.aspx?DetailID=911&CategoryID=1&DetailName=Feature&MenuID=20&LanID=0

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-52-generic 3.2.0-52.78
  ProcVersionSignature: Ubuntu 3.2.0-52.78-generic 3.2.48
  Uname: Linux 3.2.0-52-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: amd64
  ArecordDevices:  List of CAPTURE Hardware Devices 
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philipp2187 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xfcd78000 irq 20'
     Mixer name : 'Nvidia MCP77/78 HDMI'
     Components : 'HDA:83847645,10192980,00100402 
HDA:10de0002,10de0101,0010'
     Controls  : 6
     Simple ctrls  : 3
  Date: Tue Aug 20 11:44:11 2013
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=ae5ac87e-fb5b-4da2-914d-19b2a8477561
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120423)
  IwConfig:
   lono wireless extensions.

   eth1  no wireless extensions.

   eth0  no wireless extensions.
  MachineType: ECS GeForce 8000 series
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-52-generic 
root=UUID=a1918270-22c3-49df-a193-fb46777d0781 ro acpi=force irqpoll quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-52-generic N/A
   linux-backports-modules-3.2.0-52-generic  N/A
   linux-firmware1.79.6
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.name: GeForce 8000 series
  dmi.board.vendor: ECS
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: ECS
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/06/2009:svnECS:pnGeForce8000series:pvr1.0:rvnECS:rnGeForce8000series:rvr1.0:cvnECS:ct3:cvr:
  dmi.product.name: GeForce 8000 series
  dmi.product.version: 1.0
  dmi.sys.vendor: ECS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214319/+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 1214180] Re: Toshiba Portege Z935-ST4N03 will not suspend again after suspend/resume

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

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

Title:
  Toshiba Portege Z935-ST4N03 will not suspend again after
  suspend/resume

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  After suspending my Toshiba Portege Z935-ST4N03 laptop once and
  resuming, I am unable to suspend the second time. When I attempt a
  second suspend, the suspend does not complete.

  I have tried to suspend via right-clicking on the Power Manager applet, and I 
also tried (as suggested at 
https://wiki.ubuntu.com/KernelTeam/SuspendResumeTesting):
  sudo apt-get install checkbox
  sudo bash /usr/share/checkbox/scripts/suspend_test --full

  When running that script, the first time the computer suspended and
  resumed itself, but the second time, the suspend didn't succeed. I
  eventually hit the power off button and held it down until the
  computer shut down, then rebooted. I got a "crash report" and
  attempted to report an issue, but it didn't (as far as I can tell)
  actually send the data anywhere, although I clicked Continue, so I am
  instead trying this route.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-27-generic 3.8.0-27.40
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jhodgdon   2187 F pulseaudio
  Date: Mon Aug 19 16:08:14 2013
  HibernationDevice: RESUME=UUID=83309235-54d3-42b7-92d8-7fac594f6e68
  InstallationDate: Installed on 2013-06-17 (63 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  MachineType: TOSHIBA PORTEGE Z935
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-27-generic 
root=UUID=cc61d39a-8b97-457b-88b2-710d49656f9f ro acpi_backlight=vendor
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-27-generic N/A
   linux-backports-modules-3.8.0-27-generic  N/A
   linux-firmware1.106
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/04/2013
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 6.70
  dmi.board.asset.tag: 00
  dmi.board.name: PORTEGE Z935
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion6.70:bd04/04/2013:svnTOSHIBA:pnPORTEGEZ935:pvrPT234U-07101X:rvnTOSHIBA:rnPORTEGEZ935:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE Z935
  dmi.product.version: PT234U-07101X
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214180/+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 1214348] Re: package linux-image-3.8.0-19-generic 3.8.0-19.30 failed to install/upgrade

You may need to run the following:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package.

If that does not resolve your issue, please mark the bug as "Confirmed"


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

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

Title:
  package linux-image-3.8.0-19-generic 3.8.0-19.30 failed to
  install/upgrade

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I get this error every time I turn on the computer.

  ProblemType: Package
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-19-generic
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marco  2198 F pulseaudio
   /dev/snd/pcmC0D0p:   marco  2198 F...m pulseaudio
  CRDA:
   country BN:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5735 - 5835 @ 40), (N/A, 30)
  Date: Sun Aug 18 17:51:50 2013
  DuplicateSignature: package:linux-image-3.8.0-19-generic:3.8.0-19.30:
  ErrorMessage:
   
  HibernationDevice: RESUME=UUID=cce8dc62-c1cf-40fb-a2db-3378f4d619c1
  InstallationDate: Installed on 2012-10-23 (300 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: Dell Inc. Vostro 1500
  MarkForUpload: True
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic 
root=UUID=04987d58-eccb-4118-869d-0631c949d080 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.00-13ubuntu3
  SourcePackage: linux
  Title: package linux-image-3.8.0-19-generic 3.8.0-19.30 failed to 
install/upgrade
  UpgradeStatus: Upgraded to raring on 2013-04-27 (114 days ago)
  dmi.bios.date: 08/02/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 0WY040
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd08/02/2007:svnDellInc.:pnVostro1500:pvr:rvnDellInc.:rn0WY040:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Vostro 1500
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214348/+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 996369] Re: bond slave interface sometimes does not come up on boot

** Tags removed: kernel-key

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

Title:
  bond slave interface sometimes does not come up on boot

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” source package in Precise:
  Confirmed
Status in “linux” source package in Quantal:
  Confirmed
Status in “linux” source package in Raring:
  Confirmed
Status in “linux” source package in Saucy:
  Confirmed

Bug description:
  bug report:
  Hi guys,

  I'm running ubuntu12.04 server on a HP DL380G7. 
  server01 ~ # lsb_release -rd
  Description:  Ubuntu 12.04 LTS
  Release:  12.04

  I've got 2 ethernet cards with 4x 10G interfaces.
  I've got a bond on 4x10G where only eth4 and eth6 are patched.

  server01 ~ # ethtool -i eth4
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :0e:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  server01 ~ # ethtool -i eth6
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :15:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  After a reboot I expect to see a bond0 interface with 2 RUNNING SLAVE
  interfaces.

  However, sometimes I only see 1 interface coming up in the bond after
  a reboot and when I manually bring the other interface up (ifconfig
  eth6 up) it works:

  # cat /proc/net/bonding/bond0 
  Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

  Bonding Mode: IEEE 802.3ad Dynamic link aggregation
  Transmit Hash Policy: layer2 (0)
  MII Status: up
  MII Polling Interval (ms): 100
  Up Delay (ms): 0
  Down Delay (ms): 0

  802.3ad info
  LACP rate: slow
  Min links: 0
  Aggregator selection policy (ad_select): stable
  Active Aggregator Info:
Aggregator ID: 2
Number of ports: 1
Actor Key: 33
Partner Key: 32773
Partner Mac Address: 00:23:04:ee:be:01

  Slave Interface: eth6
  MII Status: down   SHOULD BE UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 1
  Permanent HW addr: 00:9c:02:3c:c9:70
  Aggregator ID: 1
  Slave queue ID: 0

  Slave Interface: eth4
  MII Status: up ONLY INTERFACE THAT IS UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:98
  Aggregator ID: 2
  Slave queue ID: 0

  Slave Interface: eth7
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:c9:74
  Aggregator ID: 3
  Slave queue ID: 0

  Slave Interface: eth5
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:9c
  Aggregator ID: 4
  Slave queue ID: 0

  server01 ~ # ifconfig
  bond0 Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
inet6 addr: fe80::29c:2ff:fe3c:c970/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:54 overruns:0 frame:0
TX packets:1236 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:18435358 (18.4 MB)  TX bytes:174727 (174.7 KB)

  eth4  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:45 overruns:0 frame:0
TX packets:1235 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:18435358 (18.4 MB)  TX bytes:174637 (174.6 KB)

  eth5  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  eth7  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  loLink encap:Local Loopback  
inet addr:127.0.0.1  Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING  MTU:16436  Metric:1
RX packets:1333 errors:0 dropped:0 overruns:0 frame:0
TX packets:1333 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:102784 (102.7 KB)  TX bytes:102784 (102.7 KB)

  vlan888   Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
inet addr:1.1.0.50  Bcast:1.1.0.63  Mask:255.255.255.240
inet6 addr:

[Kernel-packages] [Bug 1207326] Re: linux-image-generic-lts-quantal does not have proper Provides fields

** Tags removed: kernel-key

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

Title:
  linux-image-generic-lts-quantal does not have proper Provides fields

Status in “linux” package in Ubuntu:
  Invalid
Status in “linux” source package in Precise:
  Fix Committed

Bug description:
  The package does not have a proper Provides: field for linux-image, 
linux-headers, and linux-debug.
  This works fine in precise/quantal/raring and precise-lts-raring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1207326/+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 892538] Re: USB device is recognized but not automounted anymore

2013-08-20 Thread G.C. Hassink

** Tags removed: needs-upstream-testing

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

Title:
  USB device is recognized but not automounted anymore

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 10.04
  I have made a couple of changes to the system after which I discovered the 
mounting problem:
  I have swiched form madfwifi atheros drive to ndiswrapper
  I have installed the nautilus action tool
  I have changed startup options from standard to nomodeset
  switching back to madwifi, uninstall nautilus did not solve the problem
  sudo modprobe usb_storage fixes the problem but why is this service? not 
started anymore?
  (newbie)

  addition: in the mean time I used a workaround:
  gksudo gedit /etc/modules
  and add the following line
  usb_storage

  
  kernel 3.2 does not have this problem but than I do not have wifi at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: linux-image-2.6.32-34-generic 2.6.32-34.77
  Regression: No
  Reproducible: No
  ProcVersionSignature: Ubuntu 2.6.32-34.77-generic 2.6.32.44+drm33.19
  Uname: Linux 2.6.32-34-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gchassink   1497 F pulseaudio
   /dev/snd/pcmC0D0p:   gchassink   1497 F...m pulseaudio
  CRDA: Error: [Errno 2] Bestand of map bestaat niet
  Card0.Amixer.info:
   Card hw:0 'IXP'/'ATI IXP rev 2 with Cx20468-31 at 0xc0003400, irq 17'
     Mixer name : 'Conexant Cx20468-31'
     Components : 'AC97a:43585430'
     Controls  : 23
     Simple ctrls  : 16
  Card1.Amixer.info:
   Card hw:1 'Modem'/'ATI IXP Modem rev 2 at 0xc0003800, irq 17'
     Mixer name : 'Conexant Cx20468-31'
     Components : 'AC97m:43585430'
     Controls  : 2
     Simple ctrls  : 2
  Card1.Codecs.codec97.0.mc97.0.0:
   0-0/0: Conexant Cx20468-31

   Extended modem ID: codec=0 LIN1
   Modem status : GPIO
   Line1 rate   : 48000Hz
  Date: Sat Nov 19 17:38:34 2011
  Frequency: I don't know.
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=7efe3a4d-e540-414b-8f3a-947755595fdf
  HotplugNewDevices:

  HotplugNewMounts:

  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
  Lsusb:
   Bus 003 Device 002: ID 0461:4d03 Primax Electronics, Ltd Kensington 
Mouse-in-a-box
   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 004: ID 090c:1000 Feiya Technology Corp. Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA Satellite L20
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-34-generic 
root=UUID=0d475b1a-ff91-4f26-85bd-e16558abaafc ro quiet splash nomodeset
  ProcEnviron:
   LANGUAGE=nl:nl_NL:en
   LANG=nl_NL.utf8
   SHELL=/bin/bash
  RelatedPackageVersions: linux-firmware 1.34.7
  RfKill:

  SourcePackage: linux
  Symptom: storage
  UdisksMonitorLog: Monitoring activity from the disks daemon. Press Ctrl+C to 
cancel.
  dmi.bios.date: 12/25/08
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V2.50
  dmi.board.name: Satellite L20
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV2.50:bd12/25/08:svnTOSHIBA:pnSatelliteL20:pvrPSL2XE-01400WDU:rvnTOSHIBA:rnSatelliteL20:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.name: Satellite L20
  dmi.product.version: PSL2XE-01400WDU
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/892538/+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 1201869] Re: poor networking throughput across an OpenStack Neutron router on 3.5/3.8 kernels

** Tags removed: kernel-key

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

Title:
  poor networking throughput across an OpenStack Neutron router on
  3.5/3.8 kernels

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Quantal:
  In Progress
Status in “linux” source package in Raring:
  Fix Released

Bug description:
  SRU Justification:

  Impact:
  Users of the 3.5/3.8 kernel will have poor network throughput when using 
OpenStack Neutron depending on their setup.

  Fix:
  These patches are all in Ubuntu-3.9.0-7.15 / v3.9-rc1:
  2681128f0ced8aa4e66f221197e183cc16d244fe
  8093315a91340bca52549044975d8c7f673b28a1
  d0e2c55e7c940a3ee91e9e23a2683b593690f1e9

  Testcase:
  Setup OpenStack Neutron. Test throughput between internal and external nodes.

  The following explains an example vlan+namespace configuration: 
  Internal Node: [10.x.x.2]->eth2.123->br123->tap123->qr-123[10.x.x.1] <--- 
netns: qrouter-123 
  netns: qrouter-123 ---> qg-234[10.x.y.1]->tap234->br234->eth2.234->External 
Node[10.x.y.2] 
  Where:
  1) tap123+qr-123 and tap234+qg-234 are veth pairs
  2) qr-123 and qg-234 reside inside the qrouter-123 namespace

  --

  OpenStack Neutron does IP forwarding through a network namespace. A
  veth pair is used to connect into the namespace. The veth pair appears
  to be the bottleneck, independent of network namespace. In newer
  versions of Linux (Ubuntu-3.9.0-7.15 / v3.9-rc1 and greater)
  throughput is much higher by almost 3 times. For example with some
  testing throughput is 3.5 Gbps in pre 3.9-rc1 versions and 9.1 Gbps
  with these patches applied.

  This has been confirmed on kernels from 3.5.x-3.8.x. (Quantal and
  Raring lts backports)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1201869/+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 1214287] Re: [Dell Inspiron 15R 5521] suspend/resume failure

2013-08-20 Thread Nicolas Devillers

Hi,

I already patched my bios to A09 and upgraded today to the kernel:

linux-meta (3.11.0.3.4) saucy; urgency=low
  * linux ABI 3.11.0-3
 -- Tim Gardner   Mon, 19 Aug 2013 14:42:28 +

I'll wait to see if I can reproduce with this configuration and try
mainline kernel in such case.

Nicolas

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

Title:
  [Dell Inspiron 15R 5521] suspend/resume failure

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Dell Inc. Inspiron 5521 often crash when resuming.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-2-generic 3.11.0-2.5
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas2763 F pulseaudio
  Date: Tue Aug 20 10:02:28 2013
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=173db09c-bffc-4da9-ab42-7ca73f84e71f
  InstallationDate: Installed on 2013-04-08 (133 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  InterpreterPath: /usr/bin/python3.3
  MachineType: Dell Inc. Inspiron 5521
  MarkForUpload: True
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic 
root=UUID=09af3e13-8004-48fa-b0fe-116acbf8d3d7 ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash acpi_osi=Linux 
acpi_backlight=vendor vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-2-generic N/A
   linux-backports-modules-3.11.0-2-generic  N/A
   linux-firmware1.113
  SourcePackage: linux
  StagingDrivers: rts5139
  Title: [Dell Inc. Inspiron 5521] suspend/resume failure
  UpgradeStatus: Upgraded to saucy on 2013-06-24 (56 days ago)
  UserGroups:
   
  dmi.bios.date: 05/20/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0HK2KG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd05/20/2013:svnDellInc.:pnInspiron5521:pvrA08:rvnDellInc.:rn0HK2KG:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 5521
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214287/+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 892538] Re: USB device is recognized but not automounted anymore

2013-08-20 Thread G.C. Hassink

** Tags added: kernel-fixed-upstream-v3.9 rc6

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

Title:
  USB device is recognized but not automounted anymore

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 10.04
  I have made a couple of changes to the system after which I discovered the 
mounting problem:
  I have swiched form madfwifi atheros drive to ndiswrapper
  I have installed the nautilus action tool
  I have changed startup options from standard to nomodeset
  switching back to madwifi, uninstall nautilus did not solve the problem
  sudo modprobe usb_storage fixes the problem but why is this service? not 
started anymore?
  (newbie)

  addition: in the mean time I used a workaround:
  gksudo gedit /etc/modules
  and add the following line
  usb_storage

  
  kernel 3.2 does not have this problem but than I do not have wifi at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: linux-image-2.6.32-34-generic 2.6.32-34.77
  Regression: No
  Reproducible: No
  ProcVersionSignature: Ubuntu 2.6.32-34.77-generic 2.6.32.44+drm33.19
  Uname: Linux 2.6.32-34-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gchassink   1497 F pulseaudio
   /dev/snd/pcmC0D0p:   gchassink   1497 F...m pulseaudio
  CRDA: Error: [Errno 2] Bestand of map bestaat niet
  Card0.Amixer.info:
   Card hw:0 'IXP'/'ATI IXP rev 2 with Cx20468-31 at 0xc0003400, irq 17'
     Mixer name : 'Conexant Cx20468-31'
     Components : 'AC97a:43585430'
     Controls  : 23
     Simple ctrls  : 16
  Card1.Amixer.info:
   Card hw:1 'Modem'/'ATI IXP Modem rev 2 at 0xc0003800, irq 17'
     Mixer name : 'Conexant Cx20468-31'
     Components : 'AC97m:43585430'
     Controls  : 2
     Simple ctrls  : 2
  Card1.Codecs.codec97.0.mc97.0.0:
   0-0/0: Conexant Cx20468-31

   Extended modem ID: codec=0 LIN1
   Modem status : GPIO
   Line1 rate   : 48000Hz
  Date: Sat Nov 19 17:38:34 2011
  Frequency: I don't know.
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=7efe3a4d-e540-414b-8f3a-947755595fdf
  HotplugNewDevices:

  HotplugNewMounts:

  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
  Lsusb:
   Bus 003 Device 002: ID 0461:4d03 Primax Electronics, Ltd Kensington 
Mouse-in-a-box
   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 004: ID 090c:1000 Feiya Technology Corp. Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA Satellite L20
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-34-generic 
root=UUID=0d475b1a-ff91-4f26-85bd-e16558abaafc ro quiet splash nomodeset
  ProcEnviron:
   LANGUAGE=nl:nl_NL:en
   LANG=nl_NL.utf8
   SHELL=/bin/bash
  RelatedPackageVersions: linux-firmware 1.34.7
  RfKill:

  SourcePackage: linux
  Symptom: storage
  UdisksMonitorLog: Monitoring activity from the disks daemon. Press Ctrl+C to 
cancel.
  dmi.bios.date: 12/25/08
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V2.50
  dmi.board.name: Satellite L20
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV2.50:bd12/25/08:svnTOSHIBA:pnSatelliteL20:pvrPSL2XE-01400WDU:rvnTOSHIBA:rnSatelliteL20:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.name: Satellite L20
  dmi.product.version: PSL2XE-01400WDU
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/892538/+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 1214462] [NEW] Kernel Description doesn't explain its a PAE-Kernel _ since 3.4.0.1.1 _ Linus would not smile _.

Public bug reported:

Dear Developers and maintainers,

trying not to make a big fuzz about it:

Let me just quote
https://bugs.launchpad.net/baltix/+bug/930447/comments/97 from
2012-06-05:

> The non-PAE version of the Linux kernel will be dropped completely
following the 12.04 release.

Pls correct me and mark as invalid, if Ubuntu doesnt have to follow
naming conventions given on Linux-Kernel.

Trying to find appropiate information in the package change-log:

linux-meta (3.4.0.1.1) quantal; urgency=low

  * Open Quantal Quetzal 12.10
  * Temporarily disable LBM
  * Remove non-PAE i386 references

 -- mail adress hid...@canonical.com>  Wed, 02 May 2012 06:21:45 -0700

Pls clarify this and correct Ubuntus Kernel-nming on i386 package if
appropriate

Personally I think Linus wouldn't smile, even though if I thought the
index-finger to Nvidia was a bit to rough. Personally I think this bug
has security-potential.

Thanks for helping to make Ubuntu better every day.

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


** Tags: precise quantal raring saucy

** Description changed:

  Dear Developers and maintainers,
  
  trying not to make a big fuzz about it:
  
  Let me just quote
  https://bugs.launchpad.net/baltix/+bug/930447/comments/97 from
  2012-06-05:
  
  > The non-PAE version of the Linux kernel will be dropped completely
  following the 12.04 release.
  
  Pls correct me and mark as invalid, if Ubuntu doesnt have to follow
  naming conventions given on Linux-Kernel.
  
- Trying to find appropiate inormation in the package change-log:
+ Trying to find appropiate information in the package change-log:
  
  linux-meta (3.4.0.1.1) quantal; urgency=low
  
-   * Open Quantal Quetzal 12.10
-   * Temporarily disable LBM
-   * Remove non-PAE i386 references
+   * Open Quantal Quetzal 12.10
+   * Temporarily disable LBM
+   * Remove non-PAE i386 references
  
-  -- mail adress hid...@canonical.com>  Wed, 02 May 2012 06:21:45 -0700
+  -- mail adress hid...@canonical.com>  Wed, 02 May 2012 06:21:45 -0700
  
  Pls clarify this and correct Ubuntus Kernel-nming on i386 package if
  appropriate
  
  Personally I think Linus wouldn't smile, even though if I thought the
  index-finger to Nvidia was a bit to rough. Personally I think this bug
  has security-potential.
  
  Thanks for helping to make Ubuntu better every day.

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

Title:
  Kernel Description doesn't explain its a PAE-Kernel _ since 3.4.0.1.1
  _ Linus would not smile _.

Status in “linux-meta” package in Ubuntu:
  New

Bug description:
  Dear Developers and maintainers,

  trying not to make a big fuzz about it:

  Let me just quote
  https://bugs.launchpad.net/baltix/+bug/930447/comments/97 from
  2012-06-05:

  > The non-PAE version of the Linux kernel will be dropped completely
  following the 12.04 release.

  Pls correct me and mark as invalid, if Ubuntu doesnt have to follow
  naming conventions given on Linux-Kernel.

  Trying to find appropiate information in the package change-log:

  linux-meta (3.4.0.1.1) quantal; urgency=low

    * Open Quantal Quetzal 12.10
    * Temporarily disable LBM
    * Remove non-PAE i386 references

   -- mail adress hid...@canonical.com>  Wed, 02 May 2012 06:21:45 -0700

  Pls clarify this and correct Ubuntus Kernel-nming on i386 package if
  appropriate

  Personally I think Linus wouldn't smile, even though if I thought the
  index-finger to Nvidia was a bit to rough. Personally I think this bug
  has security-potential.

  Thanks for helping to make Ubuntu better every day.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1214462/+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 1214285] Re: package linux-image-3.2.0-52-generic 3.2.0-52.78 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)

2013-08-20 Thread el_calavera

I assume the NVidia driver I got from the NVidia homepage caused the
problem when it was superseded by the latest drivers from the
repository.

System was without graphics at reboot, but "sudo apt-get install -f"
resolved everything peacefully. Now everything works. Thanks!

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

Title:
  package linux-image-3.2.0-52-generic 3.2.0-52.78 failed to
  install/upgrade: subprocess installed post-installation script was
  killed by signal (Terminated)

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  The postinstall script hanged and had to be terminated manually.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-52-generic 3.2.0-52.78
  ProcVersionSignature: Ubuntu 3.2.0-51.77-generic 3.2.48
  Uname: Linux 3.2.0-51-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  simon  2684 F pulseaudio
   /dev/snd/controlC0:  simon  2684 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xdcb6 irq 45'
 Mixer name : 'Realtek ALC269VB'
 Components : 'HDA:10ec0269,102804ad,00100100'
 Controls  : 26
 Simple ctrls  : 14
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xdc08 irq 17'
 Mixer name : 'Nvidia GPU 14 HDMI/DP'
 Components : 'HDA:10de0014,10de0101,00100100'
 Controls  : 24
 Simple ctrls  : 4
  Date: Tue Aug 20 10:04:47 2013
  DuplicateSignature: 
package:linux-image-3.2.0-52-generic:3.2.0-52.78:subprocess installed 
post-installation script was killed by signal (Terminated)
  ErrorMessage: subprocess installed post-installation script was killed by 
signal (Terminated)
  HibernationDevice: RESUME=UUID=72a5788c-f177-4e43-b9d8-c0f36a8b15e1
  InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 
(20110720.1)
  MachineType: Dell Inc. OptiPlex 790
  MarkForUpload: True
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-51-generic 
root=UUID=ad0856ea-a889-40c5-b0ab-0638c3d5f3be ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 1.99-21ubuntu3.10
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: mei
  Title: package linux-image-3.2.0-52-generic 3.2.0-52.78 failed to 
install/upgrade: subprocess installed post-installation script was killed by 
signal (Terminated)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0HY9JP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/10/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 790
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214285/+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 1213422] [NEW] L Ctrl + Up produces no udev event

2013-08-20 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Pressing the L Ctrl + Up button produces no event visible in xev or in
/lib/udev/keymap -i input/eventX. R Ctrl + Up produces events, Ctrl
produces events and Up produces events. Even L Ctrl + Right, L Ctrl +
Left and L Ctrl + Down produce events.

This started a few days ago, I don't recall any event that precipitated
it.

For a while, it seemed to be working sporadically, i.e. if you pressed L
Ctrl + Up enough times, it would work once. But it has not worked at all
lately.

I expect the L Ctrl + Up keypress to move me to the next workspace

Description:Ubuntu 12.04.2 LTS
Release:12.04


udev:
  Installed: 175-0ubuntu9.4
  Candidate: 175-0ubuntu9.4

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: udev 175-0ubuntu9.4
ProcVersionSignature: Ubuntu 3.2.0-51.77-generic 3.2.48
Uname: Linux 3.2.0-51-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
Date: Sat Aug 17 10:17:41 2013
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
MachineType: ASUSTeK COMPUTER INC. UX31A
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-51-generic 
root=UUID=13cbc7a8-e358-4f4a-b323-4516ceeff6da ro quiet splash vt.handoff=7
SourcePackage: udev
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/05/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX31A.206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX31A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX31A.206:bd06/05/2012:svnASUSTeKCOMPUTERINC.:pnUX31A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX31A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX31A
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug precise
-- 
L Ctrl + Up produces no udev event
https://bugs.launchpad.net/bugs/1213422
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
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 1214180] Re: Toshiba Portege Z935-ST4N03 will not suspend again after suspend/resume

2013-08-20 Thread JenniferHodgdon

I downloaded the AMD 64 ISO image from http://cdimage.ubuntu.com/daily-
live/current/ and used the Startup Disk Creator utility to make a
bootalbe USB stick. Then I hit F12 on bootup, went into setup, and made
sure the USB stick was first in the bootup order. Then I tried several
times to boot off the USB.

However, even though when I hit F12 to see the USB stick its identifier
is there in the list, my system is not booting off the USB stick. I keep
getting through to the regular hard disk Grub menu instead. There is
some error message flashing on the screen but it is too fast to read.

I also tried re-making the USB drive, this time making sure to erase the
disk first.

Following the instructions on
https://help.ubuntu.com/community/UEFI
(because I do have UEFI on this computer), I also verified that I have Secure
Boot disabled in the BIOS (that was already the case) and that RapidStart
Technology is disabled (that was also already the case).

So, I am not sure how to proceed with testing the latest mainline image.
Obviously, I don't want to reinstall the O/S on my computer. And it does
not have a CD/DVD rom drive, so I cannot try booting from that.

HOWEVER, I was able to boot from the mainstream kernel labeled
v3.11-rc6-saucy from the URL suggested above (AMD-64 version). I was
also going to try the 3.9 RC8 Raring kernel, but the .deb file I
downloaded (twice, just to be sure) would not install with dpkg -i
(message said "... is not a debian format archive"). The specific kernel
I booted from says 3.22.0-031100rc6-generic.

And, when I booted from this kernel, I was able to suspend repeatedly.
So I would say this is fixed upstream.

I will try mark this bug accordingly after saving this comment. (not
sure if I can do both at the same time and I don't want to lose the
comment)

If bisecting to figure out which kernel it is first fixed in would help,
let me know and I would be happy to do so.

** Tags removed: needs-upstream-testing
** Tags added: kernel-fixed-upstream kernel-fixed-upstream-v3.11-rc6

** 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/1214180

Title:
Toshiba Portege Z935-ST4N03 will not suspend again after
suspend/resume

Status in “linux” package in Ubuntu:
Confirmed

Bug description:
After suspending my Toshiba Portege Z935-ST4N03 laptop once and
resuming, I am unable to suspend the second time. When I attempt a
second suspend, the suspend does not complete.

I have tried to suspend via right-clicking on the Power Manager applet, and I
also tried (as suggested at
https://wiki.ubuntu.com/KernelTeam/SuspendResumeTesting):
sudo apt-get install checkbox
sudo bash /usr/share/checkbox/scripts/suspend_test --full

When running that script, the first time the computer suspended and
resumed itself, but the second time, the suspend didn't succeed. I
eventually hit the power off button and held it down until the
computer shut down, then rebooted. I got a "crash report" and
attempted to report an issue, but it didn't (as far as I can tell)
actually send the data anywhere, although I clicked Continue, so I am
instead trying this route.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-27-generic 3.8.0-27.40
ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
Uname: Linux 3.8.0-27-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jhodgdon 2187 F pulseaudio
Date: Mon Aug 19 16:08:14 2013
HibernationDevice: RESUME=UUID=83309235-54d3-42b7-92d8-7fac594f6e68
InstallationDate: Installed on 2013-06-17 (63 days ago)
InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64
(20130423.1)
MachineType: TOSHIBA PORTEGE Z935
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-27-generic
root=UUID=cc61d39a-8b97-457b-88b2-710d49656f9f ro acpi_backlight=vendor
RelatedPackageVersions:
linux-restricted-modules-3.8.0-27-generic N/A
linux-backports-modules-3.8.0-27-generic N/A
linux-firmware1.106
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/04/2013
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 6.70
dmi.board.asset.tag: 00
dmi.board.name: PORTEGE Z935
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 00
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias:
dmi:bvnTOSHIBA:bvrVersion6.70:bd04/04/2013:svnTOSHIBA:pnPORTEGEZ935:pvrPT234U-07101X:rvnTOSHIBA:rnPORTEGEZ935:rvrVersionA0:cvnTOSHIBA

[Kernel-packages] [Bug 1214180] Re: Toshiba Portege Z935-ST4N03 will not suspend again after suspend/resume

2013-08-20 Thread JenniferHodgdon

Can I ask here (sorry if inappropriate forum!) -- do you think it is
safe to just continue to use the kernel that I downloaded for general
purposes? I see that it was built for Saucy and I'm on Raring, but it
does appear (at first glance anyway) to work. Thoughts?

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

Title:
  Toshiba Portege Z935-ST4N03 will not suspend again after
  suspend/resume

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  After suspending my Toshiba Portege Z935-ST4N03 laptop once and
  resuming, I am unable to suspend the second time. When I attempt a
  second suspend, the suspend does not complete.

  I have tried to suspend via right-clicking on the Power Manager applet, and I 
also tried (as suggested at 
https://wiki.ubuntu.com/KernelTeam/SuspendResumeTesting):
  sudo apt-get install checkbox
  sudo bash /usr/share/checkbox/scripts/suspend_test --full

  When running that script, the first time the computer suspended and
  resumed itself, but the second time, the suspend didn't succeed. I
  eventually hit the power off button and held it down until the
  computer shut down, then rebooted. I got a "crash report" and
  attempted to report an issue, but it didn't (as far as I can tell)
  actually send the data anywhere, although I clicked Continue, so I am
  instead trying this route.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-27-generic 3.8.0-27.40
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jhodgdon   2187 F pulseaudio
  Date: Mon Aug 19 16:08:14 2013
  HibernationDevice: RESUME=UUID=83309235-54d3-42b7-92d8-7fac594f6e68
  InstallationDate: Installed on 2013-06-17 (63 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  MachineType: TOSHIBA PORTEGE Z935
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-27-generic 
root=UUID=cc61d39a-8b97-457b-88b2-710d49656f9f ro acpi_backlight=vendor
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-27-generic N/A
   linux-backports-modules-3.8.0-27-generic  N/A
   linux-firmware1.106
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/04/2013
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 6.70
  dmi.board.asset.tag: 00
  dmi.board.name: PORTEGE Z935
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion6.70:bd04/04/2013:svnTOSHIBA:pnPORTEGEZ935:pvrPT234U-07101X:rvnTOSHIBA:rnPORTEGEZ935:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE Z935
  dmi.product.version: PT234U-07101X
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214180/+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 1214462] Re: Kernel Description doesn't explain its a PAE-Kernel _ since 3.4.0.1.1 _ Linus would not smile _.

** Description changed:

  Dear Developers and maintainers,
  
  trying not to make a big fuzz about it:
  
  Let me just quote
  https://bugs.launchpad.net/baltix/+bug/930447/comments/97 from
  2012-06-05:
  
- > The non-PAE version of the Linux kernel will be dropped completely
- following the 12.04 release.
+ > The non-PAE version of the Linux kernel will be dropped completely 
+ > following the 12.04 release.
  
- Pls correct me and mark as invalid, if Ubuntu doesnt have to follow
- naming conventions given on Linux-Kernel.
+ Pls correct me and mark as invalid, if Ubuntu doesn't have to follow
+ naming conventions given on the Linux-Kernel.
  
  Trying to find appropiate information in the package change-log:
  
  linux-meta (3.4.0.1.1) quantal; urgency=low
  
    * Open Quantal Quetzal 12.10
    * Temporarily disable LBM
    * Remove non-PAE i386 references
  
   -- mail adress hid...@canonical.com>  Wed, 02 May 2012 06:21:45 -0700
  
- Pls clarify this and correct Ubuntus Kernel-nming on i386 package if
- appropriate
+ Pls clarify this and correct Ubuntus Kernel-naming on i386 package if
+ appropriate.
  
  Personally I think Linus wouldn't smile, even though if I thought the
  index-finger to Nvidia was a bit to rough. Personally I think this bug
  has security-potential.
  
  Thanks for helping to make Ubuntu better every day.

** Description changed:

  Dear Developers and maintainers,
  
  trying not to make a big fuzz about it:
  
  Let me just quote
  https://bugs.launchpad.net/baltix/+bug/930447/comments/97 from
- 2012-06-05:
+ 2012-06-05 (referencing the release-notes on 12.04.2):
  
- > The non-PAE version of the Linux kernel will be dropped completely 
+ > The non-PAE version of the Linux kernel will be dropped completely
  > following the 12.04 release.
  
  Pls correct me and mark as invalid, if Ubuntu doesn't have to follow
  naming conventions given on the Linux-Kernel.
  
  Trying to find appropiate information in the package change-log:
  
  linux-meta (3.4.0.1.1) quantal; urgency=low
  
    * Open Quantal Quetzal 12.10
    * Temporarily disable LBM
    * Remove non-PAE i386 references
  
   -- mail adress hid...@canonical.com>  Wed, 02 May 2012 06:21:45 -0700
  
  Pls clarify this and correct Ubuntus Kernel-naming on i386 package if
  appropriate.
  
  Personally I think Linus wouldn't smile, even though if I thought the
  index-finger to Nvidia was a bit to rough. Personally I think this bug
  has security-potential.
  
  Thanks for helping to make Ubuntu better every day.

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

Title:
  Kernel Description doesn't explain its a PAE-Kernel _ since 3.4.0.1.1
  _ Linus would not smile _.

Status in “linux” package in Ubuntu:
  New

Bug description:
  Dear Developers and maintainers,

  trying not to make a big fuzz about it:

  Let me just quote
  https://bugs.launchpad.net/baltix/+bug/930447/comments/97 from
  2012-06-05 (referencing the release-notes on 12.04.2):

  > The non-PAE version of the Linux kernel will be dropped completely
  > following the 12.04 release.

  Pls correct me and mark as invalid, if Ubuntu doesn't have to follow
  naming conventions given on the Linux-Kernel.

  Trying to find appropiate information in the package change-log:

  linux-meta (3.4.0.1.1) quantal; urgency=low

    * Open Quantal Quetzal 12.10
    * Temporarily disable LBM
    * Remove non-PAE i386 references

   -- mail adress hid...@canonical.com>  Wed, 02 May 2012 06:21:45 -0700

  Pls clarify this and correct Ubuntus Kernel-naming on i386 package if
  appropriate.

  Personally I think Linus wouldn't smile, even though if I thought the
  index-finger to Nvidia was a bit to rough. Personally I think this bug
  has security-potential.

  Thanks for helping to make Ubuntu better every day.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214462/+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 1169376] Re: XPS13 backlight stopped working after update 3.8.0-18.28

2013-08-20 Thread Francisco Cribari

Still broke in kernel 3.8.0-29.

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

Title:
  XPS13 backlight stopped working after update 3.8.0-18.28

Status in Dell Sputnik:
  Confirmed
Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I'm on 13.04 beta 2 and I've been updating daily. After today's
  update, I was asked to restart and, after the restart, the backlight
  stopped working. What's worse is that the backlight is stuck in the
  lowest possible setting. I can barely see enough to type out this bug
  report. This is not a hardware problem. When I restart the computer
  the backlight turns on property  but burns off when the Ubuntu
  encryption screen comes up (I'm using full disk encryption). Please
  fix this as soon as possible.

  XPS 13 version: L322x
  Display version: FHD (1080p)
  --- 
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cr45h  1901 F pulseaudio
  DistroRelease: Ubuntu 13.04
  HibernationDevice: RESUME=UUID=a5d2ab8b-a068-4a69-95a6-b4e955b290f5
  InstallationDate: Installed on 2013-04-08 (9 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MachineType: Dell Inc. Dell System XPS L322X
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-18-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-18-generic N/A
   linux-backports-modules-3.8.0-18-generic  N/A
   linux-firmware1.105
  Tags:  raring
  Uname: Linux 3.8.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 01/22/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd01/22/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L322X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1169376/+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 954661] Re: backlight brightness not adjustable by default on Dell XPS 13

2013-08-20 Thread Francisco Cribari

Still broken in kernel 3.8.0-29.

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

Title:
  backlight brightness not adjustable by default on Dell XPS 13

Status in Dell Sputnik:
  New
Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Precise:
  In Progress
Status in “linux” source package in Quantal:
  In Progress
Status in “linux” source package in Raring:
  Fix Released

Bug description:
  The backlight brightness is not changeable by default on a Dell XPS 13 
running Precise beta 1 (or later). If I run the following command as root, I 
can adjust the brightness:
  /bin/echo 0 > /sys/class/baclight/intel_backlight/brightness
  However, I must do this whenever I turn on the computer or resume it from 
suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: None
  Date: Tue Mar 13 20:56:36 2012
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:052e]
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  MachineType: Dell Inc. Dell System XPS L321X
  ProcEnviron:
   TERM=xterm
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic 
root=UUID=6a0a6c9c-fb29-446a-8806-e431d38c95e8 ro quiet splash 
i915.i915_enable_fbc=1 i915.i915_enable_rc6=1 pcie_aspm=force vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/30/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 085X6F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd01/30/2012:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn085X6F:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L321X
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.7.0+bzr3035-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.30-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.1-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 
1:2.6.99.901+git20120126-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/954661/+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 1169376] Re: XPS13 backlight stopped working after update 3.8.0-18.28

2013-08-20 Thread Francisco Cribari

Still broken in kernel 3.8.0-29.

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

Title:
  XPS13 backlight stopped working after update 3.8.0-18.28

Status in Dell Sputnik:
  Confirmed
Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I'm on 13.04 beta 2 and I've been updating daily. After today's
  update, I was asked to restart and, after the restart, the backlight
  stopped working. What's worse is that the backlight is stuck in the
  lowest possible setting. I can barely see enough to type out this bug
  report. This is not a hardware problem. When I restart the computer
  the backlight turns on property  but burns off when the Ubuntu
  encryption screen comes up (I'm using full disk encryption). Please
  fix this as soon as possible.

  XPS 13 version: L322x
  Display version: FHD (1080p)
  --- 
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cr45h  1901 F pulseaudio
  DistroRelease: Ubuntu 13.04
  HibernationDevice: RESUME=UUID=a5d2ab8b-a068-4a69-95a6-b4e955b290f5
  InstallationDate: Installed on 2013-04-08 (9 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MachineType: Dell Inc. Dell System XPS L322X
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-18-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-18-generic N/A
   linux-backports-modules-3.8.0-18-generic  N/A
   linux-firmware1.105
  Tags:  raring
  Uname: Linux 3.8.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 01/22/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd01/22/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L322X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1169376/+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 1213422] Re: L Ctrl + Up produces no udev event

2013-08-20 Thread Martin Pitt

Thanks. That sounds like a bug in the keyboard driver, reassigning to
kernel.

** Package changed: udev (Ubuntu) => linux (Ubuntu)

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

Title:
  L Ctrl + Up produces no udev event

Status in “linux” package in Ubuntu:
  New

Bug description:
  Pressing the L Ctrl + Up button produces no event visible in xev or in
  /lib/udev/keymap -i input/eventX. R Ctrl + Up produces events, Ctrl
  produces events and Up produces events. Even L Ctrl + Right, L Ctrl +
  Left and L Ctrl + Down produce events.

  This started a few days ago, I don't recall any event that
  precipitated it.

  For a while, it seemed to be working sporadically, i.e. if you pressed
  L Ctrl + Up enough times, it would work once. But it has not worked at
  all lately.

  I expect the L Ctrl + Up keypress to move me to the next workspace

  Description:  Ubuntu 12.04.2 LTS
  Release:  12.04

  
  udev:
Installed: 175-0ubuntu9.4
Candidate: 175-0ubuntu9.4

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: udev 175-0ubuntu9.4
  ProcVersionSignature: Ubuntu 3.2.0-51.77-generic 3.2.48
  Uname: Linux 3.2.0-51-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: amd64
  Date: Sat Aug 17 10:17:41 2013
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: ASUSTeK COMPUTER INC. UX31A
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-51-generic 
root=UUID=13cbc7a8-e358-4f4a-b323-4516ceeff6da ro quiet splash vt.handoff=7
  SourcePackage: udev
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX31A.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX31A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX31A.206:bd06/05/2012:svnASUSTeKCOMPUTERINC.:pnUX31A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX31A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX31A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

This change was made by a bot.

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

Title:
  L Ctrl + Up produces no udev event

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Pressing the L Ctrl + Up button produces no event visible in xev or in
  /lib/udev/keymap -i input/eventX. R Ctrl + Up produces events, Ctrl
  produces events and Up produces events. Even L Ctrl + Right, L Ctrl +
  Left and L Ctrl + Down produce events.

  This started a few days ago, I don't recall any event that
  precipitated it.

  For a while, it seemed to be working sporadically, i.e. if you pressed
  L Ctrl + Up enough times, it would work once. But it has not worked at
  all lately.

  I expect the L Ctrl + Up keypress to move me to the next workspace

  Description:  Ubuntu 12.04.2 LTS
  Release:  12.04

  
  udev:
Installed: 175-0ubuntu9.4
Candidate: 175-0ubuntu9.4

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: udev 175-0ubuntu9.4
  ProcVersionSignature: Ubuntu 3.2.0-51.77-generic 3.2.48
  Uname: Linux 3.2.0-51-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: amd64
  Date: Sat Aug 17 10:17:41 2013
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: ASUSTeK COMPUTER INC. UX31A
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-51-generic 
root=UUID=13cbc7a8-e358-4f4a-b323-4516ceeff6da ro quiet splash vt.handoff=7
  SourcePackage: udev
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX31A.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX31A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX31A.206:bd06/05/2012:svnASUSTeKCOMPUTERINC.:pnUX31A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX31A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX31A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213422/+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 1214462] Re: Kernel Description doesn't explain its a PAE-Kernel _ since 3.4.0.1.1 _ Linus would not smile _.

** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)

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

Title:
  Kernel Description doesn't explain its a PAE-Kernel _ since 3.4.0.1.1
  _ Linus would not smile _.

Status in “linux” package in Ubuntu:
  New

Bug description:
  Dear Developers and maintainers,

  trying not to make a big fuzz about it:

  Let me just quote
  https://bugs.launchpad.net/baltix/+bug/930447/comments/97 from
  2012-06-05 (referencing the release-notes on 12.04.2):

  > The non-PAE version of the Linux kernel will be dropped completely
  > following the 12.04 release.

  Pls correct me and mark as invalid, if Ubuntu doesn't have to follow
  naming conventions given on the Linux-Kernel.

  Trying to find appropiate information in the package change-log:

  linux-meta (3.4.0.1.1) quantal; urgency=low

    * Open Quantal Quetzal 12.10
    * Temporarily disable LBM
    * Remove non-PAE i386 references

   -- mail adress hid...@canonical.com>  Wed, 02 May 2012 06:21:45 -0700

  Pls clarify this and correct Ubuntus Kernel-naming on i386 package if
  appropriate.

  Personally I think Linus wouldn't smile, even though if I thought the
  index-finger to Nvidia was a bit to rough. Personally I think this bug
  has security-potential.

  Thanks for helping to make Ubuntu better every day.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214462/+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 1197451] Re: Ubuntu fails to properly boot on Macbook Air 2013 6, 1 & 6, 2

2013-08-20 Thread Orm-Ancalagon

Hi Anibal,

I downloaded Kernel 3.11.0 from Linus' tree. I copied .config from
kernel 3.8 (i.e. a configuration that let the Mac boot) to the directory
with the new kernel makefiles and compiled from source.

With 3.11.0-rc5 I still have to append nosmp and libata.force=noncq but
it's stable thereafter.

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

Title:
  Ubuntu fails to properly boot on Macbook Air 2013 6,1 & 6,2

Status in The Linux Kernel:
  Unknown
Status in “linux” package in Ubuntu:
  Triaged
Status in “linux” source package in Precise:
  Triaged
Status in “linux” source package in Quantal:
  Triaged
Status in “linux” source package in Raring:
  Triaged
Status in “linux” source package in Saucy:
  Triaged

Bug description:
  Ubuntu fails to properly boot on Macbook Air 2013 6,1

  Ubuntu fails to boot the 13.10 live image from usb without specifying
  acpi-off as a boot parameter.

  After installation is complete the boot process hangs at a purple
  screen. Booting into recovery mode shows that the process stops at the
  following:

  smpboot: Booting Node 0, #1

  I've tried 12.04.2, 13.04, and 13.10. I've also tried booting with
  kernel ver 3.9.8-030908-generic and the result is the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.10.0-2-generic 3.10.0-2.9
  ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0
  Uname: Linux 3.10.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2885 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2885 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CasperVersion: 1.335
  Date: Wed Jul  3 15:31:42 2013
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64+mac (20130703)
  MachineType: Apple Inc. MacBookAir6,1
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/username.seed 
boot=casper  quiet splash acpi=off BOOT_IMAGE=/casper/vmlinuz
  RelatedPackageVersions:
   linux-restricted-modules-3.10.0-2-generic N/A
   linux-backports-modules-3.10.0-2-generic  N/A
   linux-firmware1.110
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2013
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA61.88Z.0099.B00.1305241529
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-35C1E88140C3E6CF
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir6,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-35C1E88140C3E6CF
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B00.1305241529:bd05/24/2013:svnAppleInc.:pnMacBookAir6,1:pvr1.0:rvnAppleInc.:rnMac-35C1E88140C3E6CF:rvrMacBookAir6,1:cvnAppleInc.:ct10:cvrMac-35C1E88140C3E6CF:
  dmi.product.name: MacBookAir6,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1197451/+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 1165433] Re: Kernel 3.8.x panics on bluetooth DUN disconnect

2013-08-20 Thread Sergio Callegari

Apparently the patches do not include the cc tag for
sta...@vger.kernel.org in the sign-off area which assures that when
applied to the stable tree they are applied also to the stable kernels
without anything else needing to be done by the author or subsystem
maintainer.

Should Gianluca Anzolin or Gustavo Padovan be kindly asked to assure
that these patched are also forwarded to Greg KH for consideration in
3.10.8 and other post 3.8 stable series?

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

Title:
  Kernel 3.8.x panics on bluetooth DUN disconnect

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Issue is obviously in the kernel that should not panic in any circumnstances.
  This bug is seen on quantal using the kernel from PPA mainline. Tested with 
3.8.0 to 3.8.6.
  Since 3.8.x is going to be the raring kernel I believe that this should 
definitely be fixed before raring is shipped.

  Seen on:

  DELL E6500 with kubuntu quantal 12.10 64 bit and as said, kernel 3.8.6 from 
the mainline ppa.
  The machine has a Dell Computer Corp. Wireless 370 Bluetooth Mini-card 
(connected via an internal usb connection).

  The issue is shown when connecting to the internet via a Samsung Galaxy S 
plus phone, using a bluetooth DUN connection.
  It is reproducible every time.

  How to reproduce:

  1) Use the bluetooth applet to discover the phone and associate to it.
  2) Use network manager to setup a DUN connection with the phone through your 
APN
  3) Connect to the internet via bluetooth DUN (connection works perfectly)
  4) Disconnect from the network manager.

  At the same time you disconnect, the GUI session is terminated and the
  kernel panics, briefly showing a panic log on the screen.

  Note that:

  a) The issue is not present using the standard ubuntu quantal kernel
  b) The issue is not present using kernels from the mainline ppa before 3.8 
(e.g., 3.7.x is fine for all x)
  c) The issue is not present when connecting to the internet using a USB 
mobile dongle (e.g. Huawei usb key)

  This looks pretty serious to me: kernel does not sync when panicing
  and there is a serious risk of data loss; connecting to the internet
  via a smart phone using bluetooth DUN seems to be something that one
  should take for granted on any modern OS. Furthermore, points a) and
  b) above show that this is a *regression* over previous kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1165433/+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 1214462] Re: Kernel Description doesn't explain its a PAE-Kernel _ since 3.4.0.1.1 _ Linus would not smile _.

** Description changed:

  Dear Developers and maintainers,
  
  trying not to make a big fuzz about it:
  
  Let me just quote
  https://bugs.launchpad.net/baltix/+bug/930447/comments/97 from
  2012-06-05 (referencing the release-notes on 12.04.2):
  
  > The non-PAE version of the Linux kernel will be dropped completely
  > following the 12.04 release.
  
  Pls correct me and mark as invalid, if Ubuntu doesn't have to follow
  naming conventions given on the Linux-Kernel.
  
  Trying to find appropiate information in the package change-log:
  
  linux-meta (3.4.0.1.1) quantal; urgency=low
  
    * Open Quantal Quetzal 12.10
    * Temporarily disable LBM
    * Remove non-PAE i386 references
  
   -- mail adress hid...@canonical.com>  Wed, 02 May 2012 06:21:45 -0700
  
  Pls clarify this and correct Ubuntus Kernel-naming on i386 package if
- appropriate.
+ appropriate.If the leftovers in the package are PAE, the package-names
+ are meant to say so Clear & Loud.
  
  Personally I think Linus wouldn't smile, even though if I thought the
  index-finger to Nvidia was a bit to rough. Personally I think this bug
  has security-potential.
  
  Thanks for helping to make Ubuntu better every day.

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

Title:
  Kernel Description doesn't explain its a PAE-Kernel _ since 3.4.0.1.1
  _ Linus would not smile _.

Status in “linux” package in Ubuntu:
  New

Bug description:
  Dear Developers and maintainers,

  trying not to make a big fuzz about it:

  Let me just quote
  https://bugs.launchpad.net/baltix/+bug/930447/comments/97 from
  2012-06-05 (referencing the release-notes on 12.04.2):

  > The non-PAE version of the Linux kernel will be dropped completely
  > following the 12.04 release.

  Pls correct me and mark as invalid, if Ubuntu doesn't have to follow
  naming conventions given on the Linux-Kernel.

  Trying to find appropiate information in the package change-log:

  linux-meta (3.4.0.1.1) quantal; urgency=low

    * Open Quantal Quetzal 12.10
    * Temporarily disable LBM
    * Remove non-PAE i386 references

   -- mail adress hid...@canonical.com>  Wed, 02 May 2012 06:21:45 -0700

  Pls clarify this and correct Ubuntus Kernel-naming on i386 package if
  appropriate.If the leftovers in the package are PAE, the package-names
  are meant to say so Clear & Loud.

  Personally I think Linus wouldn't smile, even though if I thought the
  index-finger to Nvidia was a bit to rough. Personally I think this bug
  has security-potential.

  Thanks for helping to make Ubuntu better every day.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214462/+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 1169376] Re: XPS13 backlight stopped working after update 3.8.0-18.28

2013-08-20 Thread Nikki1993

Daniel, I am using Ubuntu 13.04 64 bit right now. So far no issues with
the brightness. I am on the 3.8.0-29 kernel.

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

Title:
  XPS13 backlight stopped working after update 3.8.0-18.28

Status in Dell Sputnik:
  Confirmed
Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I'm on 13.04 beta 2 and I've been updating daily. After today's
  update, I was asked to restart and, after the restart, the backlight
  stopped working. What's worse is that the backlight is stuck in the
  lowest possible setting. I can barely see enough to type out this bug
  report. This is not a hardware problem. When I restart the computer
  the backlight turns on property  but burns off when the Ubuntu
  encryption screen comes up (I'm using full disk encryption). Please
  fix this as soon as possible.

  XPS 13 version: L322x
  Display version: FHD (1080p)
  --- 
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cr45h  1901 F pulseaudio
  DistroRelease: Ubuntu 13.04
  HibernationDevice: RESUME=UUID=a5d2ab8b-a068-4a69-95a6-b4e955b290f5
  InstallationDate: Installed on 2013-04-08 (9 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MachineType: Dell Inc. Dell System XPS L322X
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-18-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-18-generic N/A
   linux-backports-modules-3.8.0-18-generic  N/A
   linux-firmware1.105
  Tags:  raring
  Uname: Linux 3.8.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 01/22/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd01/22/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L322X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1169376/+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 1201470] Re: 8086:0085 Intel wireless microcode driver failure in Saucy causes disconnects

** No longer affects: linux (Ubuntu Saucy)

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

Title:
  8086:0085 Intel wireless microcode driver failure in Saucy causes
  disconnects

Status in “linux” package in Ubuntu:
  Incomplete
Status in “network-manager” package in Ubuntu:
  Incomplete
Status in “network-manager” source package in Saucy:
  Incomplete

Bug description:
  The connection slowly degrades until dropping.  Disabling 11n seems to
  workaround the issue.  With the last disconnect, the following
  messages were in dmesg:

  [ 2458.121218] iwlwifi :03:00.0: Microcode SW error detected.  Restarting 
0x200.
  [ 2458.121229] iwlwifi :03:00.0: CSR values:
  [ 2458.121234] iwlwifi :03:00.0: (2nd byte of CSR_INT_COALESCING is 
CSR_INT_PERIODIC_REG)
  [ 2458.121265] iwlwifi :03:00.0:CSR_HW_IF_CONFIG_REG: 0X00488700
  [ 2458.121296] iwlwifi :03:00.0:  CSR_INT_COALESCING: 0Xff40
  [ 2458.121328] iwlwifi :03:00.0: CSR_INT: 0X
  [ 2458.121361] iwlwifi :03:00.0:CSR_INT_MASK: 0X
  [ 2458.121393] iwlwifi :03:00.0:   CSR_FH_INT_STATUS: 0X
  [ 2458.121426] iwlwifi :03:00.0: CSR_GPIO_IN: 0X0030
  [ 2458.121455] iwlwifi :03:00.0:   CSR_RESET: 0X
  [ 2458.121486] iwlwifi :03:00.0:CSR_GP_CNTRL: 0X080403c5
  [ 2458.121516] iwlwifi :03:00.0:  CSR_HW_REV: 0X00b0
  [ 2458.121547] iwlwifi :03:00.0:  CSR_EEPROM_REG: 0X62390ffd
  [ 2458.121576] iwlwifi :03:00.0:   CSR_EEPROM_GP: 0X9001
  [ 2458.121609] iwlwifi :03:00.0:  CSR_OTP_GP_REG: 0X00030001
  [ 2458.121641] iwlwifi :03:00.0: CSR_GIO_REG: 0X00080042
  [ 2458.121674] iwlwifi :03:00.0:CSR_GP_UCODE_REG: 0X71af
  [ 2458.121706] iwlwifi :03:00.0:   CSR_GP_DRIVER_REG: 0X
  [ 2458.121735] iwlwifi :03:00.0:   CSR_UCODE_DRV_GP1: 0X
  [ 2458.121767] iwlwifi :03:00.0:   CSR_UCODE_DRV_GP2: 0X
  [ 2458.121796] iwlwifi :03:00.0: CSR_LED_REG: 0X0040
  [ 2458.121828] iwlwifi :03:00.0:CSR_DRAM_INT_TBL_REG: 0X88210a3e
  [ 2458.121860] iwlwifi :03:00.0:CSR_GIO_CHICKEN_BITS: 0X27800200
  [ 2458.121893] iwlwifi :03:00.0: CSR_ANA_PLL_CFG: 0X
  [ 2458.121925] iwlwifi :03:00.0:   CSR_HW_REV_WA_REG: 0X0001001a
  [ 2458.121955] iwlwifi :03:00.0:CSR_DBG_HPET_MEM_REG: 0X
  [ 2458.121959] iwlwifi :03:00.0: FH register values:
  [ 2458.122019] iwlwifi :03:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 
0X210f5200
  [ 2458.122077] iwlwifi :03:00.0:FH_RSCSR_CHNL0_RBDCB_BASE_REG: 
0X02115ed0
  [ 2458.122138] iwlwifi :03:00.0:  FH_RSCSR_CHNL0_WPTR: 
0X
  [ 2458.122196] iwlwifi :03:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 
0X80801114
  [ 2458.122257] iwlwifi :03:00.0:  FH_MEM_RSSR_SHARED_CTRL_REG: 
0X00fc
  [ 2458.122315] iwlwifi :03:00.0:FH_MEM_RSSR_RX_STATUS_REG: 
0X0703
  [ 2458.122376] iwlwifi :03:00.0:FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 
0X
  [ 2458.122435] iwlwifi :03:00.0:FH_TSSR_TX_STATUS_REG: 
0X07ff0001
  [ 2458.122495] iwlwifi :03:00.0: FH_TSSR_TX_ERROR_REG: 
0X
  [ 2458.122504] iwlwifi :03:00.0: Loaded firmware version: 18.168.6.1
  [ 2458.122902] iwlwifi :03:00.0: Start IWL Error Log Dump:
  [ 2458.122907] iwlwifi :03:00.0: Status: 0x004C, count: 6
  [ 2458.122912] iwlwifi :03:00.0: 0x19A8 | ADVANCED_SYSASSERT  
  [ 2458.122917] iwlwifi :03:00.0: 0x000166CC | uPc
  [ 2458.122921] iwlwifi :03:00.0: 0x962A | branchlink1
  [ 2458.122925] iwlwifi :03:00.0: 0x962A | branchlink2
  [ 2458.122929] iwlwifi :03:00.0: 0xD6BE | interruptlink1
  [ 2458.122933] iwlwifi :03:00.0: 0x | interruptlink2
  [ 2458.122937] iwlwifi :03:00.0: 0x0001 | data1
  [ 2458.122941] iwlwifi :03:00.0: 0x20ED7F5E | data2
  [ 2458.122946] iwlwifi :03:00.0: 0x0138 | line
  [ 2458.122950] iwlwifi :03:00.0: 0x00018EAD | beacon time
  [ 2458.122954] iwlwifi :03:00.0: 0x0153 | tsf low
  [ 2458.122958] iwlwifi :03:00.0: 0x | tsf hi
  [ 2458.122962] iwlwifi :03:00.0: 0x | time gp1
  [ 2458.122966] iwlwifi :03:00.0: 0x8F09138F | time gp2
  [ 2458.122970] iwlwifi :03:00.0: 0x | time gp3
  [ 2458.122974] iwlwifi :03:00.0: 0x754312A8 | uCode version
  [ 2458.122979] iwlwifi :03:00.0: 0x00B0 | hw version
  [ 2458.122983] iwlwifi :03:00.0: 0x00488700 | board version
  [ 2458.122987] iwlwifi :03:00.0: 0x094E | hcmd
  [ 2458.122991] iwlwifi 0

[Kernel-packages] [Bug 1169376] Re: XPS13 backlight stopped working after update 3.8.0-18.28

2013-08-20 Thread Kent Baxley

@Francisco and others,

Please check here for the latest status on what's going on upstream:

https://bugzilla.kernel.org/show_bug.cgi?id=47941

Some users have popped out of the woodwork to declare that the most recent 
patches that went in  *breaks* the backlight completely (black screen on boot) 
for one particular XPS13 configuration:  IvyBridge with UEFI enabled
along with Legacy BIOS enabled.  (Those same users also say that backlight 
control *always* worked for them, even without _any_ patch).

To complicate things further, a couple of other users with the same UEFI
+Legacy configuration say the exact opposite:  That the quirk patch
fixes their never-before-working backlight control (same as for all the
other non-UEFI users).

If anyone with an affected machine is willing to pitch in and help with
the latest patches being worked on please do so.

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

Title:
  XPS13 backlight stopped working after update 3.8.0-18.28

Status in Dell Sputnik:
  Confirmed
Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I'm on 13.04 beta 2 and I've been updating daily. After today's
  update, I was asked to restart and, after the restart, the backlight
  stopped working. What's worse is that the backlight is stuck in the
  lowest possible setting. I can barely see enough to type out this bug
  report. This is not a hardware problem. When I restart the computer
  the backlight turns on property  but burns off when the Ubuntu
  encryption screen comes up (I'm using full disk encryption). Please
  fix this as soon as possible.

  XPS 13 version: L322x
  Display version: FHD (1080p)
  --- 
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cr45h  1901 F pulseaudio
  DistroRelease: Ubuntu 13.04
  HibernationDevice: RESUME=UUID=a5d2ab8b-a068-4a69-95a6-b4e955b290f5
  InstallationDate: Installed on 2013-04-08 (9 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MachineType: Dell Inc. Dell System XPS L322X
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-18-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-18-generic N/A
   linux-backports-modules-3.8.0-18-generic  N/A
   linux-firmware1.105
  Tags:  raring
  Uname: Linux 3.8.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 01/22/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd01/22/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L322X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1169376/+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 978891] Re: ubuntu 12.04 doesn't boot when usb device plugged in (except usb mouse)

2013-08-20 Thread Wojtek Zabołotny

Does your system hangs also if you power-up with a device connected to
USB-3.0 port and disconnect it when BIOS asks for power-upp password
(this would suggest that the error is associated with the information
about state of the system prepared by BIOS)?

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

Title:
  ubuntu 12.04 doesn't boot when usb device plugged in (except usb
  mouse)

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” source package in Precise:
  Confirmed
Status in “linux” source package in Quantal:
  Confirmed
Status in “linux” source package in Raring:
  Confirmed
Status in “linux” source package in Saucy:
  Confirmed

Bug description:
  On DELL Vostro 3750 with Ubuntu 12.04 beta 64bit, boot stops with black 
screen is in one of USB ports is plugged USB device that is not USB mouse. I 
have tried USB HDD and laptop cooler USB and in both cases Ubuntu does not 
boot. It gets till grub and after that it loads for few seconds and then stops 
not even showing logo screen.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
 Subdevices: 0/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu2
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  djbacon1993 F pulseaudio
   /dev/snd/pcmC0D0p:   djbacon1993 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf2b0 irq 54'
 Mixer name : 'Realtek ALC269VB'
 Components : 'HDA:10ec0269,102804c6,00100100'
 Controls  : 19
 Simple ctrls  : 11
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=099b65c3-d636-4ada-9e1b-0e9984c79454
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: Dell Inc. Dell System Vostro 3750
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic 
root=UUID=eb98f17b-648a-4a2e-85cb-462736e19441 ro quiet splash pcie_aspm=force 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-23-generic N/A
   linux-backports-modules-3.2.0-23-generic  N/A
   linux-firmware1.78
  SourcePackage: linux
  StagingDrivers: mei zram
  Tags:  precise staging precise staging
  Uname: Linux 3.2.0-23-generic x86_64
  UpgradeStatus: Upgraded to precise on 2012-04-06 (6 days ago)
  UserGroups: adm admin lpadmin sambashare vboxusers
  dmi.bios.date: 05/19/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0VP036
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/19/2011:svnDellInc.:pnDellSystemVostro3750:pvr:rvnDellInc.:rn0VP036:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System Vostro 3750
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/978891/+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 1213422] Re: L Ctrl + Up produces no udev event

Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v3.2 stable kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.50-precise

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

Title:
  L Ctrl + Up produces no udev event

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Pressing the L Ctrl + Up button produces no event visible in xev or in
  /lib/udev/keymap -i input/eventX. R Ctrl + Up produces events, Ctrl
  produces events and Up produces events. Even L Ctrl + Right, L Ctrl +
  Left and L Ctrl + Down produce events.

  This started a few days ago, I don't recall any event that
  precipitated it.

  For a while, it seemed to be working sporadically, i.e. if you pressed
  L Ctrl + Up enough times, it would work once. But it has not worked at
  all lately.

  I expect the L Ctrl + Up keypress to move me to the next workspace

  Description:  Ubuntu 12.04.2 LTS
  Release:  12.04

  
  udev:
Installed: 175-0ubuntu9.4
Candidate: 175-0ubuntu9.4

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: udev 175-0ubuntu9.4
  ProcVersionSignature: Ubuntu 3.2.0-51.77-generic 3.2.48
  Uname: Linux 3.2.0-51-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: amd64
  Date: Sat Aug 17 10:17:41 2013
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: ASUSTeK COMPUTER INC. UX31A
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-51-generic 
root=UUID=13cbc7a8-e358-4f4a-b323-4516ceeff6da ro quiet splash vt.handoff=7
  SourcePackage: udev
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX31A.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX31A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX31A.206:bd06/05/2012:svnASUSTeKCOMPUTERINC.:pnUX31A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX31A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX31A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213422/+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 1213422] Re: L Ctrl + Up produces no udev event

Did this issue start happening even though you didn't apply any updates
or upgrade?

** Tags added: kernel-da-key

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

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

Title:
  L Ctrl + Up produces no udev event

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Pressing the L Ctrl + Up button produces no event visible in xev or in
  /lib/udev/keymap -i input/eventX. R Ctrl + Up produces events, Ctrl
  produces events and Up produces events. Even L Ctrl + Right, L Ctrl +
  Left and L Ctrl + Down produce events.

  This started a few days ago, I don't recall any event that
  precipitated it.

  For a while, it seemed to be working sporadically, i.e. if you pressed
  L Ctrl + Up enough times, it would work once. But it has not worked at
  all lately.

  I expect the L Ctrl + Up keypress to move me to the next workspace

  Description:  Ubuntu 12.04.2 LTS
  Release:  12.04

  
  udev:
Installed: 175-0ubuntu9.4
Candidate: 175-0ubuntu9.4

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: udev 175-0ubuntu9.4
  ProcVersionSignature: Ubuntu 3.2.0-51.77-generic 3.2.48
  Uname: Linux 3.2.0-51-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: amd64
  Date: Sat Aug 17 10:17:41 2013
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: ASUSTeK COMPUTER INC. UX31A
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-51-generic 
root=UUID=13cbc7a8-e358-4f4a-b323-4516ceeff6da ro quiet splash vt.handoff=7
  SourcePackage: udev
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX31A.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX31A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX31A.206:bd06/05/2012:svnASUSTeKCOMPUTERINC.:pnUX31A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX31A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX31A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213422/+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 1214462] Re: Kernel Description doesn't explain its a PAE-Kernel _ since 3.4.0.1.1 _ Linus would not smile _.

I'm not sure I understand the description of this bug.  Can you clarify
some more?

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

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

Title:
  Kernel Description doesn't explain its a PAE-Kernel _ since 3.4.0.1.1
  _ Linus would not smile _.

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Dear Developers and maintainers,

  trying not to make a big fuzz about it:

  Let me just quote
  https://bugs.launchpad.net/baltix/+bug/930447/comments/97 from
  2012-06-05 (referencing the release-notes on 12.04.2):

  > The non-PAE version of the Linux kernel will be dropped completely
  > following the 12.04 release.

  Pls correct me and mark as invalid, if Ubuntu doesn't have to follow
  naming conventions given on the Linux-Kernel.

  Trying to find appropiate information in the package change-log:

  linux-meta (3.4.0.1.1) quantal; urgency=low

    * Open Quantal Quetzal 12.10
    * Temporarily disable LBM
    * Remove non-PAE i386 references

   -- mail adress hid...@canonical.com>  Wed, 02 May 2012 06:21:45 -0700

  Pls clarify this and correct Ubuntus Kernel-naming on i386 package if
  appropriate.If the leftovers in the package are PAE, the package-names
  are meant to say so Clear & Loud.

  Personally I think Linus wouldn't smile, even though if I thought the
  index-finger to Nvidia was a bit to rough. Personally I think this bug
  has security-potential.

  Thanks for helping to make Ubuntu better every day.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214462/+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 1214174] Re: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1: bcmwl kernel module failed to build

2013-08-20 Thread Budo Zindovic

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

The bug report you've smarked orginally addresses Ubuntu 13.04 64bit. It
was only visible in the comments that this problem exists in LTS
version. I've encountered this problem while installing Quantal kernel
some time ago and it seems that this problem may persists with
subsequent kernels due to the LTS Enablement Stack philosophy. I merely
wanted to open topic where we can address subsequent issues.

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

Title:
  bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1: bcmwl kernel module
  failed to build

Status in “bcmwl” package in Ubuntu:
  New

Bug description:
  This error occurs every time I try to install kernel from Raring. This
  kind of bug occured for the first time when Quantal was launched (bug
  report https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1169306
  describes my problem with my 64bit Ubuntu 12.04) so I presume that
  this error is somewhat similar.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1
  ProcVersionSignature: Ubuntu 3.2.0-52.78-generic 3.2.48
  Uname: Linux 3.2.0-52-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: amd64
  DKMSKernelVersion: 3.8.0-27-generic
  Date: Tue Aug 20 00:50:53 2013
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  PackageVersion: 6.20.155.1+bdcom-0ubuntu0.0.1
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1: bcmwl kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1214174/+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 912866] Re: 1002:9710 No more audio in 12.04

2013-08-20 Thread madbiologist

ELD stands for EDID-Like Data.  eld_valid=0 is a known issue in ALSA
which has just been fixed upstream, but should only result in Radeon's
multichannel audio being unavailable over HDMI.  Stereo audio should
still work with the radeon.audio=1 kernel boot parameter.  If you have
no audio with the proprietary driver then you definitely have a
different bug.  Isn't the ION an NVIDIA platform?  Are you sure you were
using the open-source Radeon driver and not the open source nouveau
driver?  Which proprietary driver did you try?

** Summary changed:

- 1002:9710 No more audio in 12.04
+ 1002:9710 No more HDMI audio in 12.04

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

Title:
  1002:9710 No more HDMI audio in 12.04

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I no longer have sound in 12.04. Maybe unrelated, but movie player
  plays videos sped up, with no sound. vlc plays thevideo at normal
  sped, but stilll no sound.

  WORKAROUND: I had the computer connected via HDMI, and after
  installing ATI's proprietary drivers, I now have sound again.

  WORKAROUND: With open source drivers kernel parmeter radeon.audio=1

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: pulseaudio 1:1.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7
  Uname: Linux 3.2.0-7-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.90-0ubuntu1
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: SB [HDA ATI SB], device 0: VT1708S Analog [VT1708S Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xfe6f4000 irq 16'
     Mixer name : 'VIA VT1708S'
     Components : 'HDA:11060397,1043836c,0010'
     Controls  : 35
     Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfe8e8000 irq 19'
     Mixer name : 'ATI RS690/780 HDMI'
     Components : 'HDA:1002791a,00791a00,0010'
     Controls  : 4
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined penum
     Playback channels: Mono
     Mono: Playback [on]
  Date: Fri Jan  6 14:58:21 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to precise on 2012-01-04 (1 days ago)
  dmi.bios.date: 01/07/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0918
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A785TD-M EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0918:bd01/07/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-MEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.91-0ubuntu1
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: SB [HDA ATI SB], device 0: VT1708S Analog [VT1708S Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tele   1861 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xfe6f4000 irq 16'
     Mixer name : 'VIA VT1708S'
     Components : 'HDA:11060397,1043836c,0010'
     Controls  : 44
     Simple ctrls  : 21
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfe8e8000 irq 19'
     Mixer name : 'ATI RS690/780 HDMI'
     Components : 'HDA:1002791a,00791a00,0010'
     Controls  : 4
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined penum
     Playback channels: Mono
     Mono: Playback [on]
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=507f61f8-1905-4704-808c-3edf3bbabfbb
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MachineType: System manufacturer System Product Name
  Package: linux

Re: [Kernel-packages] [Bug 1169376] Re: XPS13 backlight stopped working after update 3.8.0-18.28

2013-08-20 Thread Luis Angel Vicente Sanchez

I have a full hd xps13... that is, IvyBridge and I didn't change the UEFI
configuration of my laptop and my brightness control; I will provide the
exact details when I arrive at home today.

The work around somebody posted here is working for my so I were not
willing to reinstall UEFI version before 13.10 is released but I would do
it this weekend to verify if that works in my laptop or I could try any
patch if anybody post a simple guide on how to do it.


2013/8/20 Kent Baxley <1169...@bugs.launchpad.net>

> @Francisco and others,
>
> Please check here for the latest status on what's going on upstream:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=47941
>
> Some users have popped out of the woodwork to declare that the most recent
> patches that went in  *breaks* the backlight completely (black screen on
> boot) for one particular XPS13 configuration:  IvyBridge with UEFI enabled
> along with Legacy BIOS enabled.  (Those same users also say that backlight
> control *always* worked for them, even without _any_ patch).
>
> To complicate things further, a couple of other users with the same UEFI
> +Legacy configuration say the exact opposite:  That the quirk patch
> fixes their never-before-working backlight control (same as for all the
> other non-UEFI users).
>
> If anyone with an affected machine is willing to pitch in and help with
> the latest patches being worked on please do so.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1169376
>
> Title:
>   XPS13 backlight stopped working after update 3.8.0-18.28
>
> Status in Dell Sputnik:
>   Confirmed
> Status in “linux” package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I'm on 13.04 beta 2 and I've been updating daily. After today's
>   update, I was asked to restart and, after the restart, the backlight
>   stopped working. What's worse is that the backlight is stuck in the
>   lowest possible setting. I can barely see enough to type out this bug
>   report. This is not a hardware problem. When I restart the computer
>   the backlight turns on property  but burns off when the Ubuntu
>   encryption screen comes up (I'm using full disk encryption). Please
>   fix this as soon as possible.
>
>   XPS 13 version: L322x
>   Display version: FHD (1080p)
>   ---
>   ApportVersion: 2.9.2-0ubuntu8
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  cr45h  1901 F pulseaudio
>   DistroRelease: Ubuntu 13.04
>   HibernationDevice: RESUME=UUID=a5d2ab8b-a068-4a69-95a6-b4e955b290f5
>   InstallationDate: Installed on 2013-04-08 (9 days ago)
>   InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64
> (20130402.1)
>   MachineType: Dell Inc. Dell System XPS L322X
>   MarkForUpload: True
>   Package: linux (not installed)
>   ProcEnviron:
>TERM=xterm
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-18-generic
> root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
>   ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
>   RelatedPackageVersions:
>linux-restricted-modules-3.8.0-18-generic N/A
>linux-backports-modules-3.8.0-18-generic  N/A
>linux-firmware1.105
>   Tags:  raring
>   Uname: Linux 3.8.0-18-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   dmi.bios.date: 01/22/2013
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: A07
>   dmi.board.name: 0PJHXN
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 8
>   dmi.chassis.vendor: Dell Inc.
>   dmi.chassis.version: 0.1
>   dmi.modalias:
> dmi:bvnDellInc.:bvrA07:bd01/22/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
>   dmi.product.name: Dell System XPS L322X
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/dell-sputnik/+bug/1169376/+subscriptions
>

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

Title:
  XPS13 backlight stopped working after update 3.8.0-18.28

Status in Dell Sputnik:
  Confirmed
Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I'm on 13.04 beta 2 and I've been updating daily. After today's
  update, I was asked to restart and, after the restart, the backlight
  stopped working. What's worse is that the backlight is stuck in the
  lowest possible setting. I can barely see enough to type out this bug
  report. This is not a hardware problem. When I restart the computer
  the backlight turns on property  but burns off when the Ubuntu
  encryption screen comes up (I'm using full disk encryption). Please
  fix this

[Kernel-packages] [Bug 911924] Re: Wifi disconnect after some time of work

2013-08-20 Thread Leo

Christopher, this issue resolved for me with 3.5 kernel.

** Tags removed: needs-upstream-testing

** Changed in: linux (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  Wifi disconnect after some time of work

Status in “linux” package in Ubuntu:
  Fix Released

Bug description:
  After some time (from 1 to 6 hours) wifi disconnected. Network
  indicator scan networks. After 1 minute popup dialog box with wifi
  password request, I check password and click 'connect'. Connection not
  established.

  After system reboot wifi work fine some time, but then disconnect
  repeated.

  kern.log and syslog - contain error messages right after disconnect.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image-3.0.0-15-generic 3.0.0-15.25
  ProcVersionSignature: Ubuntu 3.0.0-15.25-generic 3.0.13
  Uname: Linux 3.0.0-15-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  leo1827 F pulseaudio
  CRDA: Error: [Errno 2] Нет такого файла или каталога
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xf840 irq 16'
 Mixer name : 'Realtek ALC883'
 Components : 'HDA:10ec0883,1025009f,0012 
HDA:14f12bfa,1025009f,0009'
 Controls  : 23
 Simple ctrls  : 13
  CheckboxSubmission: e1d6cfd7cfad9746af8d0d65e47e6ef8
  CheckboxSystem: 2954e74ba17fb0e37fc942cd1d9fab4e
  Date: Wed Jan  4 22:34:44 2012
  HibernationDevice: RESUME=UUID=beea3ede-0fa3-4a61-bd55-6bed04a9507d
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 003: ID 0402:5602 ALi Corp. M5602 Video Camera Controller
   Bus 003 Device 002: ID 046d:c526 Logitech, Inc. Nano Receiver
  MachineType: Acer Aspire 5110
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-15-generic 
root=UUID=0b7722d5-3ef3-433a-984e-fb9b40f829ac ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-15-generic N/A
   linux-backports-modules-3.0.0-15-generic  N/A
   linux-firmware1.60
  SourcePackage: linux
  UpgradeStatus: Upgraded to oneiric on 2011-10-23 (73 days ago)
  dmi.bios.date: 08/22/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: V3.13
  dmi.board.name: Navarro
  dmi.board.vendor: Acer
  dmi.board.version: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrV3.13:bd08/22/2008:svnAcer:pnAspire5110:pvrV3.13:rvnAcer:rnNavarro:rvrN/A:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 5110
  dmi.product.version: V3.13
  dmi.sys.vendor: Acer

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

Re: [Kernel-packages] [Bug 910151] Re: Canon PIXMA network printer discovery fails

2013-08-20 Thread Randy Allen

Sorry so long responding, but just to let you know, I resorted to enabling
LAN instead of WLAN  on the printer, installed USB cable and successfully
installed my Canon Pixma MX860 printer. It seems the only possible bug that
exist is the inability of the software to locate on the network the printer
in wireless mode. Haven't checked yet to see how this will effect my
ability to use the printer in Win 7 but more than likely it will install
drivers and be ok. Sorry I couldn't be of any more help. I'm working on my
knowledge of command line usage. Thank you for your quick responses and I
must say the support appears to me to be incredible. I have been and
continue to be very excited about the learning opportunities I appear to
have been given since deciding to install Ubuntu.
Sincerely,
Randy Allen


On Sun, Aug 18, 2013 at 11:11 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:

> Josh, this bug report is being closed due to your last comment
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/910151/comments/32
> regarding you no longer have the hardware. For future reference you can
> manage the status of your own bugs by clicking on the current status in
> the yellow line and then choosing a new status in the revealed drop down
> box. You can learn more about bug statuses at
> https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
> to report this bug and helping to make Ubuntu better. Please submit any
> future bugs you may find.
>
> ** Changed in: linux (Ubuntu)
>Status: Incomplete => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/910151
>
> Title:
>   Canon PIXMA network printer discovery fails
>
> Status in “linux” package in Ubuntu:
>   Invalid
>
> Bug description:
>   I'm sorry if this is redundant, since I have already posted
>   information about it here: http://askubuntu.com/questions/75887/how-
>   do-i-add-a-canon-pixma-mx860-network-printer.
>
>   I am running Ubuntu Oneiric 11.10 on two computers, one is AMD-64bit
>   architecture, the other i386--same problem on both. In 11.04 I could
>   setup printing and scanning just fine, but after a fresh install of
>   11.10, adding ppa:michael-gruz/canon, and installing cnijfilter-
>   mx860series version 3.10-2ubuntu4 and scangearmp-common from the PPA,
>   Ubuntu's system-config-printer cannot detect my network printer.
>
>   In the previous installation it appeared as cnijnet://printers-mac-
>   address. I know it should be able to see it because I can ping the
>   printer at its IP address, I can browse the printer's web admin page
>   from the computer, and my Windows guest in VirtualBox on the computer
>   has no problem detecting and installing it. It seems like this problem
>   is new to Oneiric.
>
>   I found the following work around. The network printer can be
>   installed if you enter the URI manually. When adding a new printer,
>   select 'EnterURI' from the devices list and enter
>   'cnijnet:/01-23-45-67-89-AB' where 01-23-45-67-89-AB is the MAC
>   address of the printer. You have to manually select the printer model
>   for the driver, but everything prints as it should.
>
>   If that doesn't work, follow the manual instructions from
>   http://linux.wikia.com/wiki/Getting_Canon_PIXMA_to_work_on_Linux:
>
>   $ cnijnetprn --search auto
>   <...Wait for system search...>
>   network cnijnet:/00-1E-8F-B6-E0-1A "Canon MX860 series"
> "Canon-MX860-series_00-1E-8F-B6-E0-1A"
>
>   $ locate mx860.ppd
>   /usr/share/cups/model/cnmx860.ppd
>   /usr/share/ppd/cnmx860.ppd
>   $ sudo /usr/sbin/lpadmin -p CanonMX860 -m cnmx860.ppd -v
> cnijnet:/00-1E-8F-B6-E0-1A -E
>
>   the '-p' option specifies printer name, the '-m' option specified ppd
>   file, the ppd file for your printer should be included in your binary
>   driver package and at this point should have been installed in
>   /usr/share/ppd, the '-v' option specifies device uri (copy it from
>   cnijnetprn's output).
>
>   Scanning
>
>   For scanning, edit /etc/saned/pixma.conf and add the line
>   'bjnp://10.0.0.20' (the Pixma's IP address). Test to make sure Ubuntu
>   can found it with
>
>   $ scanimage -L
>   device `pixma:MX860_10.0.0.20' is a CANON Canon PIXMA MX860
> multi-Function peripheral
>
>   You can additionally edit out unnecessary backends (all but pixma)
>   from /etc/sane.d/dll.conf. That should speed the discovery up a bit.
>   For more details, check out 'man sane-pixma'.
>
>   Although I couldn't find any documentation as to why or how, the Canon
> network printer discovery protocol doesn't work right in 11.10 as it does
> in previous versions--perhaps a discovery timeout issue? Still, everything
> is up and running now, but it would be nice to work out of box in future
> releases.
>   ---
>   AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
>   ApportVersion: 1.23-0ubuntu4
>   Architecture: amd64
>   AudioDevicesI

[Kernel-packages] [Bug 1172447] Re: AMD video card in my Dell Studio 1557 doesn't work correctly after upgrading to 13.04

2013-08-20 Thread JR

sorry, this is my production environment and I cannot upgrade now. I
could try using a live cd, but as you can read in comment #4, my system
worked well with the 13.04 live cd.

I intend to upgrade my system to 13.10, and I will maybe do it before
the official release, so after that I'll give an update if everything
works in the new system.

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

Title:
  AMD video card in my Dell Studio 1557 doesn't work correctly after
  upgrading to 13.04

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  When I boot the upgraded system with my old kernel (3.5.0-27),
  everything works as before. When I boot my notebook with the default
  kernel (some 3.8.x) I do see the boot logo, and afterwards I see a
  completely mess. In that case, even switching to a text console
  doesn't always work.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-19-generic 3.8.0-19.29
  ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
  Uname: Linux 3.5.0-27-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  CurrentDmesg:
   [   10.692646] input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio1/input/input13
   [   11.444250] init: plymouth-stop pre-start process (1927) terminated with 
status 1
   [   13.528577] r8169 :0b:00.0: eth0: link up
   [   13.529103] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  Date: Wed Apr 24 21:32:57 2013
  InstallationDate: Installed on 2012-11-08 (167 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-27-generic 
root=UUID=f5384d48-b43e-473b-a67d-2b0ced15f617 ro quiet splash vt.handoff=7
  SourcePackage: linux
  UpgradeStatus: Upgraded to raring on 2013-04-24 (0 days ago)
  dmi.board.name: 0KM426
  dmi.product.name: Studio 1557

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1172447/+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 1173279] Re: 1969:2062 Atheros AR8152 v2.0 Fast Ethernet (rev c1) stops working after some minutes

2013-08-20 Thread Timmie

How could something like this happen?
A driver that worked well all the time is made worse in a newer Kernel ;-(

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

Title:
  1969:2062 Atheros AR8152 v2.0 Fast Ethernet (rev c1) stops working
  after some minutes

Status in The Linux Kernel:
  Unknown
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  After some minutes of booting up the ethernet card stops working without any 
evident reason. The same situation was described in the old Bug #680239 over 
kernel 2.6.35.
  It works correctly in Ubuntu 12.04.2 and it worked without any problem in 
12.10. Haven't tried with a clean installation (this was upgraded from 12.10), 
will try from a live media later.

  WORKAROUND: When I disable the Wi-Fi the problem disappears.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-19-generic 3.8.0-19.29
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  xf 2061 F pulseaudio
  Date: Fri Apr 26 18:23:53 2013
  HibernationDevice: RESUME=UUID=6d531763-ff5a-41f4-aa32-86a9981170c2
  InstallationDate: Installed on 2012-10-18 (189 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: Acer AO722
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=80518144-078c-4a1a-a0d8-23942013ee75 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-19-generic N/A
   linux-backports-modules-3.8.0-19-generic  N/A
   linux-firmware1.106
  SourcePackage: linux
  UpgradeStatus: Upgraded to raring on 2013-04-25 (0 days ago)
  dmi.bios.date: 12/06/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.08
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE10-BZ
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.08
  dmi.modalias: 
dmi:bvnAcer:bvrV1.08:bd12/06/2011:svnAcer:pnAO722:pvrV1.08:rvnAcer:rnJE10-BZ:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.08:
  dmi.product.name: AO722
  dmi.product.version: V1.08
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1173279/+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 927794] Re: 14e4:4727 WLAN not working with Lenovo G570

2013-08-20 Thread Timmie

The issue is not remaining anymore in 13.04.

But I suffer terribly from:
1969:2062 Atheros AR8152 v2.0 Fast Ethernet (rev c1) stops working after some 
minutes
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1173279

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

Title:
  14e4:4727 WLAN not working with Lenovo G570

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  with Kernel 3.0.0-15-generic the WLAN does not work on my laptop:

  Lenovo G570
  http://www.lenovo.com/products/us/laptop/essential/g-series/g570/

  With 3.0.0-14-generic all works well.

  WORKAROUND: sudo bzr diff -r149
  === modified file '.etckeeper'
  --- .etckeeper 2012-06-03 11:23:33 +
  +++ .etckeeper 2012-06-03 12:23:50 +
  @@ -1830,8 +1830,6 @@
   maybe chmod 0755 './modprobe.d'
   maybe chmod 0644 './modprobe.d/alsa-base.conf'
   maybe chmod 0644 './modprobe.d/blacklist-ath_pci.conf'
  -maybe chmod 0644 './modprobe.d/blacklist-bcm43.conf'
  -maybe chmod 0644 './modprobe.d/blacklist-bcma.conf'
   maybe chmod 0644 './modprobe.d/blacklist-cups-usblp.conf'
   maybe chmod 0644 './modprobe.d/blacklist-firewire.conf'
   maybe chmod 0644 './modprobe.d/blacklist-framebuffer.conf'
  @@ -1845,6 +1843,7 @@
   maybe chmod 0644 './modprobe.d/thinkfan.conf'
   maybe chmod 0644 './modprobe.d/vmwgfx-fbdev.conf'
   maybe chmod 0644 './modules'
  +maybe chmod 0644 './modules~'
   maybe chmod 0755 './mono'
   maybe chmod 0755 './mono/2.0'
   maybe chmod 0755 './mono/2.0/Browsers'

  === removed file 'modprobe.d/blacklist-bcm43.conf'
  --- modprobe.d/blacklist-bcm43.conf 2012-06-02 22:53:43 +
  +++ modprobe.d/blacklist-bcm43.conf 1970-01-01 00:00:00 +
  @@ -1,9 +0,0 @@
  -# Warning: This file is autogenerated by bcmwl. All changes to this file 
will be lost.
  -blacklist b43
  -blacklist b43legacy
  -blacklist ssb
  -blacklist bcm43xx
  -blacklist brcm80211
  -blacklist brcmfmac
  -blacklist brcmsmac
  -blacklist bcma

  === removed file 'modprobe.d/blacklist-bcma.conf'
  --- modprobe.d/blacklist-bcma.conf 2012-06-02 23:07:52 +
  +++ modprobe.d/blacklist-bcma.conf 1970-01-01 00:00:00 +
  @@ -1,1 +0,0 @@
  -blacklist brcmsmac

  === modified file 'modprobe.d/blacklist.conf'
  --- modprobe.d/blacklist.conf 2012-06-03 12:04:55 +
  +++ modprobe.d/blacklist.conf 2012-06-03 12:16:35 +
  @@ -53,3 +53,12 @@
   # continues to build and is installable for the few cases where its
   # really needed.
   blacklist amd76x_edac
  +
  +### Ubuntu Broadcom madness:
  +# http://ubuntuforums.org/showpost.php?p=11446022&postcount=2
  +blacklist brcm80211
  +blacklist bcma
  +
  +# acc. http://ubuntuforums.org/showpost.php?p=11903104&postcount=18
  +blacklist wl
  +blacklist atl1c

  === modified file 'modules'
  --- modules 2012-03-19 23:16:46 +
  +++ modules 2012-06-03 12:14:58 +
  @@ -5,3 +5,5 @@

   lp
   rtc
  +# acc. to http://ubuntuforums.org/showpost.php?p=11903104&postcount=18
  +brcmsmac

  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hotryce1752 F pulseaudio
  CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xd060 irq 42'
     Mixer name : 'Intel CougarPoint HDMI'
     Components : 'HDA:14f1506e,17aac013,0012 
HDA:80862805,80860101,0010'
     Controls  : 12
     Simple ctrls  : 6
  DistroRelease: Ubuntu 11.10
  HibernationDevice: RESUME=UUID=d69db823-bd68-4998-99a5-419c9e0c7aa8
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  IwConfig:
   lono wireless extensions.

   eth0  no wireless extensions.
  MachineType: LENOVO 4334
  Package: linux (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-15-generic 
root=UUID=25d4600d-a17b-4e61-a1c7-c109921a9535 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-15-generic N/A
   linux-backports-modules-3.0.0-15-generic  N/A
   linux-firmware1.60
  RfKill:
   0: ideapad_wlan: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  StagingDrivers: rts5139 mei
  Tags:  oneiric running-unity staging
  Uname: Linux 3.0.0-15-generic x86_64
  UpgradeStatus: Upgraded to oneiric on 2011-12-20 (47 days ago)
  UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare users
  dmi.bios.date: 10/07/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 40CN28WW(V2.14)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.boa

[Kernel-packages] [Bug 1173279] Re: 1969:2062 Atheros AR8152 v2.0 Fast Ethernet (rev c1) stops working after some minutes

2013-08-20 Thread Luis Henriques

This was a regression (not specific to Ubuntu kernels by the way), which
has finally been fixed upstream with commit
7b70176421993866e616f1cbc4d0dd4054f1bf78.

It is currently under review on the 3.8.y stable kernel (v3.8.13.7) and
should hit the Raring kernel in the next few weeks.

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

Title:
  1969:2062 Atheros AR8152 v2.0 Fast Ethernet (rev c1) stops working
  after some minutes

Status in The Linux Kernel:
  Unknown
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  After some minutes of booting up the ethernet card stops working without any 
evident reason. The same situation was described in the old Bug #680239 over 
kernel 2.6.35.
  It works correctly in Ubuntu 12.04.2 and it worked without any problem in 
12.10. Haven't tried with a clean installation (this was upgraded from 12.10), 
will try from a live media later.

  WORKAROUND: When I disable the Wi-Fi the problem disappears.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-19-generic 3.8.0-19.29
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  xf 2061 F pulseaudio
  Date: Fri Apr 26 18:23:53 2013
  HibernationDevice: RESUME=UUID=6d531763-ff5a-41f4-aa32-86a9981170c2
  InstallationDate: Installed on 2012-10-18 (189 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: Acer AO722
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=80518144-078c-4a1a-a0d8-23942013ee75 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-19-generic N/A
   linux-backports-modules-3.8.0-19-generic  N/A
   linux-firmware1.106
  SourcePackage: linux
  UpgradeStatus: Upgraded to raring on 2013-04-25 (0 days ago)
  dmi.bios.date: 12/06/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.08
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE10-BZ
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.08
  dmi.modalias: 
dmi:bvnAcer:bvrV1.08:bd12/06/2011:svnAcer:pnAO722:pvrV1.08:rvnAcer:rnJE10-BZ:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.08:
  dmi.product.name: AO722
  dmi.product.version: V1.08
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1173279/+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 1167760] Re: [HP 1000] Screen backlight is off after startup.

2013-08-20 Thread Anthony Wong

The patch already landed in Quantal, Raring and mainline kernels.

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

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

Title:
  [HP 1000] Screen backlight is off after startup.

Status in “linux” package in Ubuntu:
  Fix Released

Bug description:
  cid: 201209-11731, 201209-11735 (two machines with the same model)

  The screen backlight is automatically set to off after boot/reboot (after the 
Ubuntu logo screen).
  Using the brightness adjustment key on the keyboard can bring the lights back.
  Kernel upgrade won't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1
  ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
  Uname: Linux 3.5.0-23-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1486 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x5260 irq 44'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:10ec0269,103c1854,00100202 
HDA:80862806,80860101,0010'
 Controls  : 24
 Simple ctrls  : 10
  Date: Wed Apr 10 23:11:39 2013
  HibernationDevice: RESUME=UUID=126e9e5b-4a26-4964-8eae-020440f19e70
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  MachineType: Hewlett-Packard HP 1000 Notebook PC
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic 
root=UUID=cf922830-da62-4875-bbe2-f7d81abe55c4 ro quiet splash initcall_debug 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-23-generic N/A
   linux-backports-modules-3.5.0-23-generic  N/A
   linux-firmware1.79.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1854
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 64.22
  dmi.chassis.asset.tag: 72414P100R
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd10/25/2012:svnHewlett-Packard:pnHP1000NotebookPC:pvr0698100053063:rvnHewlett-Packard:rn1854:rvr64.22:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 1000 Notebook PC
  dmi.product.version: 0698100053063
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1167760/+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 1212679] Re: btrfs segmentation fault when balancing after adding 4th disk to 3 disk raid5

2013-08-20 Thread Robert Heel

Same error witch linux-image-3.11.0-3-generic

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

Title:
  btrfs segmentation fault when balancing after adding 4th disk to 3
  disk raid5

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  [ 1897.180398] [ cut here ]
  [ 1897.181058] Kernel BUG at facfde70 [verbose debug info unavailable]
  [ 1897.181652] invalid opcode:  [#1] SMP 
  [ 1897.182227] Modules linked in: hidp dm_crypt(F) joydev(F) cx22702 
snd_hda_codec_realtek isl6421 snd_soc_wm8776 cx24116 snd_soc_core cx88_dvb 
cx88_vp3054_i2c videobuf_dvb snd_compress(F) wm8775 dvb_core ir_lirc_codec 
lirc_dev ir_mce_kbd_decoder hid_generic ir_sanyo_decoder ir_jvc_decoder 
ir_sony_decoder ir_rc6_decoder ir_rc5_decoder ir_nec_decoder rc_hauppauge 
usbhid hid btusb tuner_simple tuner_types tda9887 snd_hda_intel tda8290 
cx88_alsa tuner snd_hda_codec snd_hwdep(F) cx8800 snd_pcm(F) cx8802 
snd_page_alloc(F) cx88xx snd_seq_midi(F) snd_seq_midi_event(F) btcx_risc 
tveeprom snd_rawmidi(F) videobuf_dma_sg bnep rfcomm parport_pc(F) psmouse(F) 
rc_core ppdev(F) bluetooth serio_raw(F) snd_seq(F) v4l2_common nfsd(F) 
auth_rpcgss(F) nfs_acl(F) nfs(F) lockd(F) sunrpc(F) fscache(F) videobuf_core 
snd_seq_device(F) snd_timer(F) videodev snd(F) mac_hid k8temp ohci_pci 
soundcore(F) i2c_nforce2 lp(F) parport(F) usblp btrfs(F) xor(F) zlib_deflate(F) 
raid6_pq(F) libcrc32c(F) nouveau mxm_wmi wmi video(F) i2c_algo_bit ttm 
pata_acpi drm_kms_helper drm pata_amd sata_nv forcedeth ahci(F) libahci(F)
  [ 1897.184274] CPU: 0 PID: 6899 Comm: btrfs-balance Tainted: GF
3.11.0-2-generic #5-Ubuntu
  [ 1897.184274] Hardware name: Gigabyte Technology Co., Ltd. M61P-S3/M61P-S3, 
BIOS F7f 06/18/2009
  [ 1897.184274] task: f5884d40 ti: ea904000 task.ti: ea904000
  [ 1897.184274] EIP: 0060:[] EFLAGS: 00010246 CPU: 0
  [ 1897.184274] EIP is at build_backref_tree+0x210/0xf40 [btrfs]
  [ 1897.184274] EAX: ef31f0c0 EBX: ef31f0c8 ECX: ea905c78 EDX: 
  [ 1897.184274] ESI: db829b40 EDI:  EBP: ea905cb8 ESP: ea905c28
  [ 1897.184274]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [ 1897.184274] CR0: 8005003b CR2: aefa7000 CR3: 2faae000 CR4: 07f0
  [ 1897.184274] Stack:
  [ 1897.184274]  db829120   02905c54 f00f3894 db829660 
0004 ed28c000
  [ 1897.184274]  db82968c efc610e0 ea326094 eafbcb40 db829b40 db829660 
ea326000 
  [ 1897.184274]  ea326010 efc61150   ea905c78 ea905c78 
ea905c80 ea905c80
  [ 1897.184274] Call Trace:
  [ 1897.184274]  [] relocate_tree_blocks+0x1d9/0x610 [btrfs]
  [ 1897.184274]  [] ? add_data_references+0x239/0x250 [btrfs]
  [ 1897.184274]  [] relocate_block_group+0x25e/0x650 [btrfs]
  [ 1897.184274]  [] btrfs_relocate_block_group+0x1b2/0x310 [btrfs]
  [ 1897.184274]  [] btrfs_relocate_chunk.isra.28+0x59/0x720 [btrfs]
  [ 1897.184274]  [] ? read_extent_buffer+0xaa/0xf0 [btrfs]
  [ 1897.184274]  [] ? _raw_spin_lock+0xd/0x10
  [ 1897.184274]  [] ? release_extent_buffer+0x58/0xb0 [btrfs]
  [ 1897.184274]  [] ? free_extent_buffer+0x4d/0xa0 [btrfs]
  [ 1897.184274]  [] __btrfs_balance+0x481/0x8c0 [btrfs]
  [ 1897.184274]  [] btrfs_balance+0x50a/0x730 [btrfs]
  [ 1897.184274]  [] balance_kthread+0x67/0x70 [btrfs]
  [ 1897.184274]  [] ? btrfs_balance+0x730/0x730 [btrfs]
  [ 1897.184274]  [] kthread+0x94/0xa0
  [ 1897.184274]  [] ? kthread+0x20/0xa0
  [ 1897.184274]  [] ret_from_kernel_thread+0x1b/0x28
  [ 1897.184274]  [] ? kthread_create_on_node+0xc0/0xc0
  [ 1897.184274] Code: e8 01 89 47 20 8b 45 a4 f6 40 45 10 0f 85 be 09 00 00 8b 
7d a4 8b 47 2c 8d 77 2c 89 75 90 39 c6 74 0b 3b 47 30 0f 84 4a 08 00 00 <0f> 0b 
c7 45 ac 00 00 00 00 8d b4 26 00 00 00 00 e8 0b 6d 93 c6
  [ 1897.184274] EIP: [] build_backref_tree+0x210/0xf40 [btrfs] 
SS:ESP 0068:ea905c28
  [ 1897.214978] ---[ end trace c3a3e666541660a2 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.11.0-2-generic 3.11.0-2.5
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic i686
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robert 4167 F pulseaudio
   /dev/snd/controlC1:  robert 4167 F pulseaudio
  Date: Thu Aug 15 15:26:08 2013
  IwConfig:
   tap0  no wireless extensions.
   
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 002 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
   Bus 002 Device 003: ID 0e6a:6001 Megawin Technology Co., Ltd GEMBIRD 
Flexible keyboard KB-109F-B-DE
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Gigabyte Technology Co., Ltd. M61P-S3
  MarkForUpload: True
  ProcEnviron:

[Kernel-packages] [Bug 1173279] Re: 1969:2062 Atheros AR8152 v2.0 Fast Ethernet (rev c1) stops working after some minutes

2013-08-20 Thread Timmie

@Luis Henriques

Thanks for your explanation.

Is there not a code testing mechnism that prevens such things?

Is there any way how we could grab this earlier? 
E.g. by using a development kernel from Ubuntu or alike?

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

Title:
  1969:2062 Atheros AR8152 v2.0 Fast Ethernet (rev c1) stops working
  after some minutes

Status in The Linux Kernel:
  Unknown
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  After some minutes of booting up the ethernet card stops working without any 
evident reason. The same situation was described in the old Bug #680239 over 
kernel 2.6.35.
  It works correctly in Ubuntu 12.04.2 and it worked without any problem in 
12.10. Haven't tried with a clean installation (this was upgraded from 12.10), 
will try from a live media later.

  WORKAROUND: When I disable the Wi-Fi the problem disappears.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-19-generic 3.8.0-19.29
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  xf 2061 F pulseaudio
  Date: Fri Apr 26 18:23:53 2013
  HibernationDevice: RESUME=UUID=6d531763-ff5a-41f4-aa32-86a9981170c2
  InstallationDate: Installed on 2012-10-18 (189 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: Acer AO722
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=80518144-078c-4a1a-a0d8-23942013ee75 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-19-generic N/A
   linux-backports-modules-3.8.0-19-generic  N/A
   linux-firmware1.106
  SourcePackage: linux
  UpgradeStatus: Upgraded to raring on 2013-04-25 (0 days ago)
  dmi.bios.date: 12/06/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.08
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE10-BZ
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.08
  dmi.modalias: 
dmi:bvnAcer:bvrV1.08:bd12/06/2011:svnAcer:pnAO722:pvrV1.08:rvnAcer:rnJE10-BZ:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.08:
  dmi.product.name: AO722
  dmi.product.version: V1.08
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1173279/+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 1214059] Re: Wifi and bluetooth disabled at boot and hard to re-enable

2013-08-20 Thread Nicolas Delvaux

I did the Bios upgrade but it changed nothing. I still get the same
behaviour as the one I described above.

~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
68PDV Ver. F.20
12/08/2011

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

** Tags removed: bios-outdated-f.20

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

Title:
  Wifi and bluetooth disabled at boot and hard to re-enable

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Network Manager says either "Device not ready" or "wireless is disabled by 
hardware switch" (it depends).
  Enabling Bluetooth in the control-center just enable it for like half a 
second and then it's switched off again.

  I have a combined hardware button for both Wifi and Bluetooth, it's red when 
it's disabled and blue when enabled.
  In this case it stays red even when I repeatedly press it (though the 
Bluetooth setting panel reliably indicate when it is hardware disabled, so I 
guess the color is only related to software lock).

  I manage to make it work again after playing with "rfkill
  [block|unblock] all" and messing around with network manager
  (disabling network and then re-enabling it...). I usually need around
  5 minutes to make it work.

  I did not have this problem on Raring. I had it on saucy with the 3.10
  kernel but it seems to be worse with 3.11 (I need to mess around for
  more time in order to make it work again).

  Feel free to ask if you need any additional test.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-2-generic 3.11.0-2.5
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nicolas1670 F pulseaudio
   /dev/snd/controlC0:  nicolas1670 F pulseaudio
  Date: Mon Aug 19 19:20:56 2013
  HibernationDevice: RESUME=UUID=7e493485-d08d-4944-8362-444f69fd1e08
  InstallationDate: Installed on 2013-07-10 (39 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130710)
  MachineType: Hewlett-Packard HP EliteBook 8530p
  MarkForUpload: True
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic 
root=UUID=821ce4aa-35e4-436c-93cc-c8c2d9aba532 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-2-generic N/A
   linux-backports-modules-3.11.0-2-generic  N/A
   linux-firmware1.113
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/08/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PDV Ver. F.11
  dmi.board.name: 30E7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 90.26
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PDVVer.F.11:bd12/08/2009:svnHewlett-Packard:pnHPEliteBook8530p:pvrF.11:rvnHewlett-Packard:rn30E7:rvrKBCVersion90.26:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8530p
  dmi.product.version: F.11
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214059/+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 717931] Re: Unknown Keycode for Touchpad toggle

2013-08-20 Thread Muelli

** Tags removed: needs-upstream-testing
** Tags added: kernel-fixed-upstream kernel-fixed-upstream-v3.9.0

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

Title:
  Unknown Keycode for Touchpad toggle

Status in “linux” package in Ubuntu:
  Incomplete
Status in “linux” package in Fedora:
  Unknown

Bug description:
  I expected to be able to toggle whether the touchpad works via Fn+F6
  on my Lenovo Ideapad S10-3t.

  But instead, I get this:
  [ 2975.474700] atkbd serio0: Unknown key released (translated set 2, code 
0xf2 on isa0060/serio0).
  [ 2975.474716] atkbd serio0: Use 'setkeycodes e072 ' to make it 
known.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: linux-image-2.6.38-3-generic 2.6.38-3.30
  Regression: No
  Reproducible: Yes
  ProcVersionSignature: Ubuntu 2.6.38-3.30-generic 2.6.38-rc4
  Uname: Linux 2.6.38-3-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  muelli 1527 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf040 irq 44'
 Mixer name : 'Conexant CX20582 (Pebble)'
 Components : 'HDA:14f15066,17aa4003,00100302'
 Controls  : 8
 Simple ctrls  : 5
  CurrentDmesg:
   [ 2975.334993] atkbd serio0: Unknown key pressed (translated set 2, code 
0xf2 on isa0060/serio0).
   [ 2975.335008] atkbd serio0: Use 'setkeycodes e072 ' to make it 
known.
   [ 2975.474700] atkbd serio0: Unknown key released (translated set 2, code 
0xf2 on isa0060/serio0).
   [ 2975.474716] atkbd serio0: Use 'setkeycodes e072 ' to make it 
known.
  Date: Sun Feb 13 00:34:44 2011
  HibernationDevice: RESUME=UUID=19373b74-bcce-4bf1-bca7-0c1686eca780
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110201.2)
  MachineType: LENOVO 20040M18
  ProcEnviron:
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
   LC_MESSAGES=en_GB.utf8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-3-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-2.6.38-3-generic N/A
   linux-backports-modules-2.6.38-3-generic N/A
   linux-firmware 1.47
  SourcePackage: linux
  dmi.bios.date: 08/11/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 24CN61WW
  dmi.board.name: Caucasus2
  dmi.board.vendor: LENOVO
  dmi.board.version: Rev 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: Rev 1.0
  dmi.modalias: 
dmi:bvnLENOVO:bvr24CN61WW:bd08/11/2010:svnLENOVO:pn20040M18:pvrLenovoIdeapadS10-3t:rvnLENOVO:rnCaucasus2:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0:
  dmi.product.name: 20040M18
  dmi.product.version: Lenovo Ideapad S10-3t
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/717931/+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 1204666] Re: Raring update to 3.8.13.5 stable release

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Raring update to 3.8.13.5 stable release

Status in “linux” package in Ubuntu:
  Invalid
Status in “linux” source package in Raring:
  Fix Released

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from Linus' tree or in a minimally
     backported form of that patch. The 3.8.13.5 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://kernel.ubuntu.com/ubuntu/linux.git

  TEST CASE: TBD

     The following patches are in the 3.8.13.5 stable release:

  * Linux 3.8.13.5
  * svcrdma: underflow issue in decode_write_list()
  * ext4: don't allow ext4_free_blocks() to fail due to ENOMEM
  * ext4: don't show usrquota/grpquota twice in /proc/mounts
  * lockd: protect nlm_blocked access in nlmsvc_retry_blocked
  * x86/efi: Fix dummy variable buffer allocation
  * Modify UEFI anti-bricking code
  * x86,efi: Implement efi_no_storage_paranoia parameter
  * x86, efi: remove duplicate code in setup_arch() by using, efi_is_native()
  * x86, efivars: firmware bug workarounds should be in platform code
  * perf: Fix perf_lock_task_context() vs RCU
  * perf: Remove WARN_ON_ONCE() check in __perf_event_enable() for valid 
scenario
  * perf: Clone child context from parent context pmu
  * CIFS: Fix a deadlock when a file is reopened
  * dm verity: fix inability to use a few specific devices sizes
  * dm ioctl: set noio flag to avoid __vmalloc deadlock
  * dm mpath: fix ioctl deadlock when no paths
  * ARM: 7778/1: smp_twd: twd_update_frequency need be run on all online CPUs
  * parisc: Fix gcc miscompilation in pa_memcpy()
  * [SCSI] mpt3sas: Infinite loops can occur if 
MPI2_IOCSTATUS_CONFIG_INVALID_PAGE is not returned
  * [SCSI] mpt3sas: fix for kernel panic when driver loads with HBA conected to 
non LUN 0 configured expander
  * iscsi-target: Fix tfc_tpg_nacl_auth_cit configfs length overflow
  * [SCSI] megaraid_sas: fix memory leak if SGL has zero length entries
  * ACPI / power: add missing newline to debug messages
  * drm/nva3/disp: Fix HDMI audio regression
  * drm/nouveau: use vmalloc for pgt allocation
  * [CIFS] use sensible file nlink values if unprovided
  * libceph: Fix NULL pointer dereference in auth client code
  * module: do percpu allocation after uniqueness check.  No, really!
  * uprobes: Fix return value in error handling path
  * Btrfs: only do the tree_mod_log_free_eb if this is our last ref
  * Btrfs: hold the tree mod lock in __tree_mod_log_rewind
  * Btrfs: fix unlock after free on rewinded tree blocks
  * ARM: shmobile: emev2 GIO3 resource fix
  * svcrpc: don't error out on small tcp fragment
  * svcrpc: fix handling of too-short rpc's
  * nfsd4: fix decoding of compounds across page boundaries
  * drm/i915: Only clear write-domains after a successful wait-seqno
  * drm/i915: Fix context sizes on HSW
  * writeback: Fix periodic writeback after fs mount
  * rtlwifi: rtl8723ae: Fix typo in firmware names
  * rt2x00: read 5GHz TX power values from the correct offset
  * iommu/amd: Only unmap large pages from the first pte
  * MIPS: Octeon: Don't clobber bootloader data structures.
  * [media] media: dmxdev: remove dvb_ringbuffer_flush() on writer side
  * rtlwifi: rtl8192cu: Add new USB ID for TP-Link TL-WN8200ND
  * iwlwifi: pcie: wake the queue if stopped when being unmapped
  * iwlwifi: pcie: fix race in queue unmapping
  * ath9k: Do not assign noise for NULL caldata
  * ath9k_hw: Assign default xlna config for AR9485
  * b43: ensue that BCMA is "y" when B43 is "y"
  * drm/radeon: add backlight quirk for hybrid mac
  * charger-manager: Ensure event is not used as format string
  * printk: Fix rq->lock vs logbuf_lock unlock lock inversion
  * drivers/cdrom/cdrom.c: use kzalloc() for failing hardware
  * dma: tegra: avoid channel lock up after free
  * iommu: Fix compile warnings with forward declarations
  * iommu/vt-d: add quirk for broken interrupt remapping on 55XX chipsets
  * ext4: fix data offset overflow on 32-bit archs in ext4_inline_data_fiemap()
  * ext4: fix overflows in SEEK_HOLE, SEEK_DATA implementations
  * ext4: fix data offset overflow in ext4_xattr_fiemap() on 32-bit archs
  * ext4: fix overflow when counting used blocks on 32-bit architectures
  * tracing: Use current_uid() for critical time tracing
  * ipvs: SCTP ports should be writable in ICMP packets
  * netfilter: xt_TCPMSS: Fix IPv6 default MSS too
  * netfilter: xt_TCPMSS: Fix missing fragmentation handling
  * netfilter: xt_TCPOPTSTRIP: don't use tcp

[Kernel-packages] [Bug 1178747] Re: vgaswitcheroo on the Macbook Pro 8, 2 high-res

Sebastian Rühl,

could you please test the latest kernel in raring-updates (3.8.0-29.42)
and see if this bug is fixed? Thanks.

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

Title:
  vgaswitcheroo on the Macbook Pro 8,2 high-res

Status in The Linux Kernel:
  Confirmed
Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  I have the same issue as in Bug #1171940. The difference is that my machine 
is slightly different (High-Res display) and the pci id is somewhat different. 
So I edited the patch supplied there and try to fix the issue. However the 
screen still stays black.
  --- 
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  srhl62 2027 F pulseaudio
   /dev/snd/controlC0:  srhl62 2027 F pulseaudio
  DistroRelease: Ubuntu 13.04
  InstallationDate: Installed on 2013-04-21 (19 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130420)
  MachineType: Apple Inc. MacBookPro8,2
  MarkForUpload: True
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: root=UUID=dc157da7-a9a1-4ce6-963f-c3b28c9cf340 ro 
add_efi_memmap modprobe.blacklist=i915 radeon.modeset=1  quiet splash 
$vt_handoff initrd=\initrd.img-3.8.0-20-mbp82fix
  ProcVersionSignature: Ubuntu 3.8.0-20.31-mbp82fix 3.8.11
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-20-mbp82fix N/A
   linux-backports-modules-3.8.0-20-mbp82fix  N/A
   linux-firmware 1.106
  Tags:  raring
  Uname: Linux 3.8.0-20-mbp82fix x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 01/24/12
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP81.88Z.0047.B27.1201241646
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-94245A3940C91C80
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro8,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-94245A3940C91C80
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80:
  dmi.product.name: MacBookPro8,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1178747/+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 1204600] Re: Quantal update to 3.5.7.17 stable release

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

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

Title:
  Quantal update to 3.5.7.17 stable release

Status in “linux” package in Ubuntu:
  Invalid
Status in “linux” source package in Quantal:
  Fix Released

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from Linus' tree or in a minimally
     backported form of that patch. The 3.5.7.17 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://kernel.ubuntu.com/ubuntu/linux.git

  TEST CASE: TBD

     The following patches are in the 3.5.7.17 stable release:

  * Linux 3.5.7.17
  * iommu/amd: Only unmap large pages from the first pte
  * charger-manager: Ensure event is not used as format string
  * printk: Fix rq->lock vs logbuf_lock unlock lock inversion
  * x86/efi: Fix dummy variable buffer allocation
  * Modify UEFI anti-bricking code
  * x86,efi: Implement efi_no_storage_paranoia parameter
  * x86,efi: Check max_size only if it is non-zero.
  * efi: Export efi_query_variable_store() for efivars.ko
  * x86, efivars: firmware bug workarounds should be in platform code
  * efi: be more paranoid about available space when creating variables
  * efivars: Disable external interrupt while holding efivars->lock
  * efi_pstore: Check remaining space with QueryVariableInfo() before writing 
data
  * drivers/cdrom/cdrom.c: use kzalloc() for failing hardware
  * vgacon: fix missing include.
  * ext4: fix overflow when counting used blocks on 32-bit architectures
  * ext4: fix data offset overflow in ext4_xattr_fiemap() on 32-bit archs
  * rtlwifi: rtl8192cu: Fix duplicate if test
  * libceph: Fix NULL pointer dereference in auth client code
  * drm/mgag200: Added resolution and bandwidth limits for various G200e 
products.
  * drm/mgag200: Reject modes that are too big for VRAM
  * vgacon.c: add cond reschedule points in vgacon_do_font_op
  * rt2x00: read 5GHz TX power values from the correct offset
  * rtlwifi: rtl8192cu: Add new USB ID for TP-Link TL-WN8200ND
  * iwlwifi: pcie: wake the queue if stopped when being unmapped
  * ath9k: Do not assign noise for NULL caldata
  * ath9k: Fix noisefloor calibration
  * ath9k_hw: Remove CHANNEL_CW_INT
  * ath9k_hw: Assign default xlna config for AR9485
  * ath9k: fill channel mode in caldata
  * b43: ensue that BCMA is "y" when B43 is "y"
  * PCI: Fix refcount issue in pci_create_root_bus() error recovery path
  * ext3: fix data=journal fast mount/umount hang
  * tick: Prevent uncontrolled switch to oneshot mode
  * timer: Fix jiffies wrap behavior of round_jiffies_common()
  * hpfs: better test for errors
  * md/raid10: fix two bugs affecting RAID10 reshape.
  * powerpc/smp: Section mismatch from smp_release_cpus to __initdata 
spinning_secondaries
  * aacraid: Fix for arrays are going offline in the system. System hangs
  * [SCSI] sd: Fix parsing of 'temporary ' cache mode prefix
  * [SCSI] mpt2sas: fix firmware failure with wrong task attribute
  * [SCSI] mpt2sas: Fix for device scan following host reset could get stuck in 
a infinite loop
  * [SCSI] mpt2sas: Fix for max_sectors warning message is stating the 
incorrect range
  * [SCSI] mpt2sas: Fix for issue Missing delay not getting set during system 
bootup
  * [SCSI] zfcp: status read buffers on first adapter open with link down
  * [SCSI] zfcp: block queue limits with data router
  * [SCSI] zfcp: fix adapter (re)open recovery while link to SAN is down
  * ipvs: SCTP ports should be writable in ICMP packets
  * netfilter: xt_TCPMSS: Fix IPv6 default MSS too
  * netfilter: xt_TCPMSS: Fix missing fragmentation handling
  * netfilter: xt_TCPOPTSTRIP: don't use tcp_hdr()
  * netfilter: xt_TCPMSS: Fix violation of RFC879 in absence of MSS option
  * netfilter: nfnetlink_acct: fix incomplete dumping of objects
  * netfilter: nfnetlink_cttimeout: fix incomplete dumping of objects
  * ipvs: info leak in __ip_vs_get_dest_entries()
  * netfilter: xt_LOG: fix mark logging for IPv6 packets
  * netfilter: add nf_ipv6_ops hook to fix xt_addrtype with IPv6
  * netfilter: ipt_ULOG: fix non-null terminated string in the nf_log path
  * netfilter: xt_TCPOPTSTRIP: fix possible mangling beyond packet boundary
  * nbd: correct disconnect behavior
  * drivers/rtc/rtc-rv3029c2.c: fix disabling AIE irq
  * mm/memory-hotplug: fix lowmem count overflow when offline pages
  * crypto: sanitize argument for format string
  * block: do not pass disk names as format strings
  * ocfs2: xattr: fix inlined xattr reflink
  * drivers/dma/pl330.c: fix locking in pl330_free_chan_resources()

[Kernel-packages] [Bug 1203320] Re: Multitouch doesn't work on 2013 MacBook Air 6, 2

Linus G Thiel,

could you please test the latest kernel in -updates (3.8.0-29.42) and
see if this bug is fixed? Thanks.

** Changed in: linux (Ubuntu Raring)
   Status: In Progress => 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/1203320

Title:
  Multitouch doesn't work on 2013 MacBook Air 6,2

Status in “linux” package in Ubuntu:
  In Progress
Status in “linux” source package in Raring:
  Incomplete
Status in “linux” source package in Saucy:
  In Progress

Bug description:
  On the 2013 MacBook Air 6,2, the touchpad works very rudimentary. No
  multitouch, not even right click or two finger scroll works. This is
  fixed upstream though, see [1]. Getting that backported would be
  great.

  [1]:
  
https://github.com/torvalds/linux/commit/148c1c8ad3c4170186ebe6ea5900adde27d2a0e7

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-26-generic 3.8.0-26.38
  ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
  Uname: Linux 3.8.0-26-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  linus  1917 F pulseaudio
  CRDA:
   country SE:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  Date: Sat Jul 20 17:29:28 2013
  HibernationDevice:
   RESUME=/dev/mapper/cryptswap1
   #RESUME=UUID=7625120b-1951-4a58-8da6-1c47db358631
  MachineType: Apple Inc. MacBookAir6,2
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-26-generic 
root=UUID=2f08800d-d161-46e7-87b6-0f88e86890af ro i915.i915_enable_rc6=3 
libata.force=1:noncq resume=/dev/sda4 quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-26-generic N/A
   linux-backports-modules-3.8.0-26-generic  N/A
   linux-firmware1.106
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2013
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA61.88Z.0099.B00.1305241529
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-7DF21CB3ED6977E5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir6,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-7DF21CB3ED6977E5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B00.1305241529:bd05/24/2013:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5:
  dmi.product.name: MacBookAir6,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1203320/+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 1196730] Re: Fn key doesn't work in raring on MacBook Air 6, 2

Linus G Thiel,

could you please test the latest kernel in -updates (3.8.0-29.42) and
see if this bug is fixed? Thanks.

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

Title:
  Fn key doesn't work in raring on MacBook Air 6,2

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  After installing Raring on my new MacBook Air 6,2, the Fn key didn't
  work -- I couldn't use the media keys, regardless of "fnmode", neither
  backspace, page up/down, etc.

  I found bug #207127 and I figured it was something like that, and it
  turns out that the keyboard has a new device id. I added it to the
  usbhid driver and after that it works.

  Please see the attached patch.
  --- 
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  linus  1924 F pulseaudio
  CRDA:
   country SE:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  DistroRelease: Ubuntu 13.04
  HibernationDevice:
   RESUME=/dev/mapper/cryptswap1
   #RESUME=UUID=7625120b-1951-4a58-8da6-1c47db358631
  MachineType: Apple Inc. MacBookAir6,2
  MarkForUpload: True
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.13 
root=UUID=2f08800d-d161-46e7-87b6-0f88e86890af ro quiet splash 
i915.i915_enable_rc6=1 libata.force=1:noncq resume=/dev/sda4 vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13
  RelatedPackageVersions:
   linux-restricted-modules-3.8.13 N/A
   linux-backports-modules-3.8.13  N/A
   linux-firmware  1.106
  Tags:  raring
  Uname: Linux 3.8.13 x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 05/24/2013
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA61.88Z.0099.B00.1305241529
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-7DF21CB3ED6977E5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir6,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-7DF21CB3ED6977E5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B00.1305241529:bd05/24/2013:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5:
  dmi.product.name: MacBookAir6,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  --- 
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  linus  1922 F pulseaudio
  CRDA:
   country SE:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  DistroRelease: Ubuntu 13.04
  HibernationDevice:
   RESUME=/dev/mapper/cryptswap1
   #RESUME=UUID=7625120b-1951-4a58-8da6-1c47db358631
  MachineType: Apple Inc. MacBookAir6,2
  MarkForUpload: True
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic 
root=UUID=2f08800d-d161-46e7-87b6-0f88e86890af ro quiet splash 
i915.i915_enable_rc6=1 libata.force=1:noncq resume=/dev/sda4 vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-25-generic N/A
   linux-backports-modules-3.8.0-25-generic  N/A
   linux-firmware1.106
  Tags:  raring
  Uname: Linux 3.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 05/24/2013
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA61.88Z.0099.B00.1305241529
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-7DF21CB3ED6977E5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir6,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-7DF21CB3ED6977E5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B00.1305241529:bd05/24/2013:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5:
  dmi.product.name: MacBookAir6,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196730/+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 1214500] Re: consistent failure with overlayfs and unix sockets

2013-08-20 Thread Scott Moser

I added 'linux' as this is at very least a change in behavior between
12.04 kernel and saucy kernel.


** Also 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/1214500

Title:
  consistent failure with overlayfs and unix sockets

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

Bug description:
  Seems like overlayfs and unix sockets are not playing well. It might
  be racy, as it fails consistently on my laptop with an SSD, whereas
  for smoser it only failed a single time.

  Steps to reproduce:

  REL="precise"
  $ sudo lxc-create -n source-$REL-amd64 -t ubuntu-cloud -- \
 --release=$REL --arch=amd64

  ## clone via overlayfs ##
  $ sudo lxc-clone --snapshot -B overlayfs -o source-$REL-amd64 -n 
$REL-overlayfs-01

  $ sudo lxc-start -n $REL-overlayfs-01

  
  ### inside ###
  $ sudo apt-get update && sudo apt-get install supervisor -y

  $ sudo service supervisor stop
  $ sudo sed -i.dist 's,var/run/*supervisor.sock,srv/supervisor.sock,' 
/etc/supervisor/supervisord.conf
  $ sudo service supervisor start
  $ sudo supervisorctl maintail
  unix:///srv/supervisor.sock refused connection

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214500/+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 930447] Re: Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M x86 Laptop due to bug in PAE kernel, initramfs or syslinux

On 10.04 LTS my little Dell D600I could use PAE-Kernels with no
problems. (36-bits) . As per today it runs with the Mainline Kernel
3.10.7-031007-generic - lawlessly. Thanks to Prof7bits "Fake-PAE"

And this confirms comment #179:
... the Linux documentation states that if you can boot a PAE kernel, then your
CPU has PAE. If you don't have PAE, then the kernel won't even boot.

Simple as that. Don't argue wt dev's why priorize the non-PAE over the
PAE. see also
https://en.wikipedia.org/wiki/Physical_Address_Extension#Linux . It's an
non-arguable decision, even though anyone wt. a RAM > 4GiB should decide
for a 64-Bit system. :-)

If the Kernel naming would clearly state it's a PAE, since the other
Kernel's part was removed, we would probably not need a preinst. script
to drag people away Ubuntu, even from other flavours. Like Elementary-OS

Well, if Intel thought they shouldn't equipe some Pentium M with a PAE
flag (even though it's capable) they deserve a bug-report. And should
publish a new updated BIOS. They always had open ears to Linux users.

It's the old linux-users desease working rather on the effects than on
the impact.

Nowadays I need to edit & manipulate the downloaded CD for an
installation? That's possible & ends up with ISO-start in GRUB2. This is
Not o.k.! Pls support bug#1214462 – " Kernel Description doesn't
explain its a PAE-Kernel _ since 3.4.0.1.1 _ Linus would not smile _. "

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

Title:
Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M
x86 Laptop due to bug in PAE kernel, initramfs or syslinux

Status in “linux” package in Ubuntu:
Won't Fix
Status in “syslinux” package in Ubuntu:
Fix Released
Status in Baltix GNU/Linux:
Triaged

Bug description:
Ubuntu 12.04 doesn't start from Desktop CD or USB with syslinux boot
loader on Pentium M 1.6Ghz or faster Pentium M CPU - displays error
message about missing PAE feature in CPU, but *the same* *Ubuntu
12.04* Desktop CD/LiveUSB starts fine on *the same CPU* (and same PAE
kernel) if GRUB boot loader is used, for example when WUBI or LiveUSB
with GRUB boot loader, like Multisystem
(http://liveusb.info/dotclear/index.php?pages/install ) is used!

The error message is:
"This kernel requires the following features not present on the CPU: pae.
Unable to boot - please use a kernel appropriate for you CPU."

THIS IS AN IMPORTANT REGRESSION! People are able to install and successfully
use Ubuntu 12.04 on such pretty new hardware, like IBM Thinkpad T42 laptop with
Pentium M 1700Mhz processor, but the bug in syslinux (or something related)
forbids Ubuntu 12.04 installation.
This bug is reproducible on lots of computers, there are several log files
and /proc/cpuinfo file attached to this bugreport, AFAIK it's enough to reopen
this bug.

---
ApportVersion: 1.23-0ubuntu4
Architecture: i386
CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission
denied
MachineType: IBM 2373PPU
dmi.bios.date: 06/18/2007
dmi.bios.vendor: IBM
dmi.bios.version: 1RETDRWW (3.23 )
dmi.board.name: 2373PPU
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373PPU:pvrThinkPadT42:rvnIBM:rn2373PPU:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
dmi.product.name: 2373PPU
dmi.product.version: ThinkPad T42
dmi.sys.vendor: IBM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/930447/+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 1214500] Re: consistent failure with overlayfs and unix sockets

2013-08-20 Thread Serge Hallyn

Regarding creating the socket as a non-root user - did you chown the
directory to your user's uid?  I have no problem once I've done that in
running the server.

I have the same issue with the client:

sudo mkdir /mnt2 /upper
sudo mount -t overlayfs -o lowerdir=/mnt2,upperdir=/upper none /mnt
sudo chown -R ubuntu: /mnt
./serv.py /mnt/sock &
./client.py /mnt/sock

Traceback (most recent call last):
  File "./client.py", line 7, in 
s.connect(socketname)
  File "/usr/lib/python2.7/socket.py", line 224, in meth
return getattr(self._sock,name)(*args)
socket.error: [Errno 111] Connection refused

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

Title:
  consistent failure with overlayfs and unix sockets

Status in “linux” package in Ubuntu:
  Incomplete
Status in “lxc” package in Ubuntu:
  New

Bug description:
  Seems like overlayfs and unix sockets are not playing well. It might
  be racy, as it fails consistently on my laptop with an SSD, whereas
  for smoser it only failed a single time.

  Steps to reproduce:

  REL="precise"
  $ sudo lxc-create -n source-$REL-amd64 -t ubuntu-cloud -- \
 --release=$REL --arch=amd64

  ## clone via overlayfs ##
  $ sudo lxc-clone --snapshot -B overlayfs -o source-$REL-amd64 -n 
$REL-overlayfs-01

  $ sudo lxc-start -n $REL-overlayfs-01

  
  ### inside ###
  $ sudo apt-get update && sudo apt-get install supervisor -y

  $ sudo service supervisor stop
  $ sudo sed -i.dist 's,var/run/*supervisor.sock,srv/supervisor.sock,' 
/etc/supervisor/supervisord.conf
  $ sudo service supervisor start
  $ sudo supervisorctl maintail
  unix:///srv/supervisor.sock refused connection

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

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1214500

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

Title:
  consistent failure with overlayfs and unix sockets

Status in “linux” package in Ubuntu:
  Incomplete
Status in “lxc” package in Ubuntu:
  New

Bug description:
  Seems like overlayfs and unix sockets are not playing well. It might
  be racy, as it fails consistently on my laptop with an SSD, whereas
  for smoser it only failed a single time.

  Steps to reproduce:

  REL="precise"
  $ sudo lxc-create -n source-$REL-amd64 -t ubuntu-cloud -- \
 --release=$REL --arch=amd64

  ## clone via overlayfs ##
  $ sudo lxc-clone --snapshot -B overlayfs -o source-$REL-amd64 -n 
$REL-overlayfs-01

  $ sudo lxc-start -n $REL-overlayfs-01

  
  ### inside ###
  $ sudo apt-get update && sudo apt-get install supervisor -y

  $ sudo service supervisor stop
  $ sudo sed -i.dist 's,var/run/*supervisor.sock,srv/supervisor.sock,' 
/etc/supervisor/supervisord.conf
  $ sudo service supervisor start
  $ sudo supervisorctl maintail
  unix:///srv/supervisor.sock refused connection

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214500/+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 1214500] Re: consistent failure with overlayfs and unix sockets

2013-08-20 Thread Serge Hallyn

Oh, never mind, I see - that's on precise.  and yes I get the same
result all around.

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

Title:
  consistent failure with overlayfs and unix sockets

Status in “linux” package in Ubuntu:
  Incomplete
Status in “lxc” package in Ubuntu:
  New

Bug description:
  Seems like overlayfs and unix sockets are not playing well. It might
  be racy, as it fails consistently on my laptop with an SSD, whereas
  for smoser it only failed a single time.

  Steps to reproduce:

  REL="precise"
  $ sudo lxc-create -n source-$REL-amd64 -t ubuntu-cloud -- \
 --release=$REL --arch=amd64

  ## clone via overlayfs ##
  $ sudo lxc-clone --snapshot -B overlayfs -o source-$REL-amd64 -n 
$REL-overlayfs-01

  $ sudo lxc-start -n $REL-overlayfs-01

  
  ### inside ###
  $ sudo apt-get update && sudo apt-get install supervisor -y

  $ sudo service supervisor stop
  $ sudo sed -i.dist 's,var/run/*supervisor.sock,srv/supervisor.sock,' 
/etc/supervisor/supervisord.conf
  $ sudo service supervisor start
  $ sudo supervisorctl maintail
  unix:///srv/supervisor.sock refused connection

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214500/+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 1203320] Re: Multitouch doesn't work on 2013 MacBook Air 6, 2

** Changed in: linux (Ubuntu Saucy)
   Status: In Progress => Fix Released

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

Title:
  Multitouch doesn't work on 2013 MacBook Air 6,2

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

Bug description:
  On the 2013 MacBook Air 6,2, the touchpad works very rudimentary. No
  multitouch, not even right click or two finger scroll works. This is
  fixed upstream though, see [1]. Getting that backported would be
  great.

  [1]:
  
https://github.com/torvalds/linux/commit/148c1c8ad3c4170186ebe6ea5900adde27d2a0e7

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-26-generic 3.8.0-26.38
  ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
  Uname: Linux 3.8.0-26-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  linus  1917 F pulseaudio
  CRDA:
   country SE:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  Date: Sat Jul 20 17:29:28 2013
  HibernationDevice:
   RESUME=/dev/mapper/cryptswap1
   #RESUME=UUID=7625120b-1951-4a58-8da6-1c47db358631
  MachineType: Apple Inc. MacBookAir6,2
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-26-generic 
root=UUID=2f08800d-d161-46e7-87b6-0f88e86890af ro i915.i915_enable_rc6=3 
libata.force=1:noncq resume=/dev/sda4 quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-26-generic N/A
   linux-backports-modules-3.8.0-26-generic  N/A
   linux-firmware1.106
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2013
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA61.88Z.0099.B00.1305241529
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-7DF21CB3ED6977E5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir6,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-7DF21CB3ED6977E5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B00.1305241529:bd05/24/2013:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5:
  dmi.product.name: MacBookAir6,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1203320/+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 1201528] Re: [Realtek ALC889] - Audio Playback Unavailable

Maybe try re-installing the kernels from the partition you use for these
tests?  Or you could also try running update-grub again?

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

Title:
  [Realtek ALC889] - Audio Playback Unavailable

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Incomplete
Status in “alsa-driver” source package in Raring:
  New
Status in “linux” source package in Raring:
  Incomplete
Status in “alsa-driver” source package in Saucy:
  New
Status in “linux” source package in Saucy:
  Incomplete

Bug description:
  This is a fresh upgrade to raring. During the weekend, I updated from
  precise to quantal, and from there to raring. I did not use sound
  while the system was in quantal, so no idea if the bug was present
  there as well.

  The symptom is:

  * after some period of sound usage, playback stops working

  What I mean with sound usage is:

  I tried having a meeting with: mumble, skype, and google hangout, and
  in all three cases, audio input/outout will work just fine for ~5
  minutes, and the playback just dies (people tell me they keep
  listening to me, so mic works fine).

  The only way to solve this is by rebooting. After one of the reboots,
  I was able to play a 20 minute video with mplayer with no further
  issue. Then opened skype and after ~3-5 minute talk, audio playback
  died again.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
  Uname: Linux 3.8.0-26-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nessita2627 F pulseaudio
  Date: Mon Jul 15 14:40:20 2013
  InstallationDate: Installed on 2011-12-20 (572 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(2029.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
  Symptom_AlsaPlaybackTestStderr:
   W r i t e   e r r o r :   - 5 , I n p u t / o u t p u t   e r r o r 
x r u n _ r e c o v e r y   f a i l e d :   - 5 , I n p u t / o u t p u t   
e r r o r 
T r a n s f e r   f a i l e d :   O p e r a t i o n   n o t   p e r m i t t 
e d
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: None of the above
  Title: [, Realtek ALC889, Green Headphone Out, Front] Playback problem
  UpgradeStatus: Upgraded to raring on 2013-07-13 (2 days ago)
  dmi.bios.date: 08/05/2009
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KGIBX10J.86A.3206.2009.0805.1855
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DP55WG
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE57269-404
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKGIBX10J.86A.3206.2009.0805.1855:bd08/05/2009:svn:pn:pvr:rvnIntelCorporation:rnDP55WG:rvrAAE57269-404:cvn:ct2:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1201528/+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 1213795] Re: newer kernels (3.10+) don't boot on MacBook Air 6.1

I started a kernel bisect between v3.9 final and v3.10-rc1. The kernel
bisect will require testing of about 7-10 test kernels.

I built the first test kernel, up to the following commit:
73287a43cc79ca06629a88d1a199cd283f42456a

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1213795

Can you test that kernel and report back if it has the bug or not. I
will build the next test kernel based on your test results.

Thanks in advance


** Also affects: linux via
   http://bugzilla.kernel.org/show_bug.cgi?id=60635
   Importance: Unknown
   Status: Unknown

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

Title:
  newer kernels (3.10+) don't boot on MacBook Air 6.1

Status in The Linux Kernel:
  Unknown
Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” source package in Saucy:
  Confirmed

Bug description:
  The current raring kernel boots (with nosmp and libata.force=noncq),
  newer kernels don't boot at all. They hang with ramdisk loading and
  nothing seems to happen. This is difficult to debug, as it happens so
  early in the boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-27-generic 3.8.0-27.40
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  miek   1872 F pulseaudio
  Date: Sun Aug 18 22:49:05 2013
  HibernationDevice: RESUME=UUID=f4250ce4-23bc-413f-9a97-205cd9ca67e5
  InstallationDate: Installed on 2013-08-19 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac 
(20130424)
  Lsusb:
   Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part 
of BCM2046 Bluetooth)
   Bus 001 Device 003: ID 05ac:0290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05ac:828f Apple, Inc.
  MachineType: Apple Inc. MacBookAir6,1
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic 
root=UUID=003d813a-5ee5-40bc-a81f-dbed66aaf939 ro nosmp libata.force=noncq 
quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-27-generic N/A
   linux-backports-modules-3.8.0-27-generic  N/A
   linux-firmware1.106
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2013
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA61.88Z.0099.B00.1305241529
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-35C1E88140C3E6CF
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir6,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-35C1E88140C3E6CF
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B00.1305241529:bd05/24/2013:svnAppleInc.:pnMacBookAir6,1:pvr1.0:rvnAppleInc.:rnMac-35C1E88140C3E6CF:rvrMacBookAir6,1:cvnAppleInc.:ct10:cvrMac-35C1E88140C3E6CF:
  dmi.product.name: MacBookAir6,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1213795/+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 1213239] Re: Bluetooth subsystem dies after suspend

Thanks for testing, Till.

I'd next try to identify which 3.11 release candidate introduced the
regression.

Can you test the following kernels and report back? We are looking for
the earliest kernel version that exhibits this bug:

v3.11-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc1-saucy
v3.11-rc2: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc2-saucy
v3.11-rc3: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc3-saucy/
v3.11-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc4-saucy/

You don't have to test every kernel, just up until the kernel that first
has this bug.


Thanks in advance!

** Tags added: performing-bisect

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

Title:
  Bluetooth subsystem dies after suspend

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I am using Saucy in XMir mode with the standard Unity desktop on the
  Lenovo Thinkpad Twist.

  When I suspend the system not only the suspend itself is broken (bug
  1213233) but also after waking up I cannot use my Bluetooth devices
  any more (mouse, keyboard). I have to reboot to get Bluetooth back
  working.

  Do not ask me to update the BIOS from 1.52 to 1.57, this leads to bug
  1210748.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-2-generic 3.11.0-2.5
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  till   3099 F pulseaudio
  Date: Fri Aug 16 22:19:52 2013
  HibernationDevice: RESUME=UUID=e0af6e5c-3cf3-47e2-8603-6a9ffb019484
  InstallationDate: Installed on 2013-06-05 (72 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130605)
  MachineType: LENOVO 334729G
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic 
root=UUID=80d8eb01-b0c3-47cc-8dba-1ed122b2be4f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-2-generic N/A
   linux-backports-modules-3.11.0-2-generic  N/A
   linux-firmware1.113
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/05/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GDET92WW (1.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 334729G
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGDET92WW(1.52):bd02/05/2013:svnLENOVO:pn334729G:pvrThinkPadTwist:rvnLENOVO:rn334729G:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 334729G
  dmi.product.version: ThinkPad Twist
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213239/+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 683013] Re: High load averages on Lucid while idling

2013-08-20 Thread Peter Júnoš

Sorry,  I cannot test it as the machine with Lucid is gone (personally,
I use much newer Raring now and problem seems to be fixed there, but I
cannot really compare it).

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

Title:
  High load averages on Lucid while idling

Status in “linux” package in Ubuntu:
  Incomplete
Status in “linux” source package in Lucid:
  New

Bug description:
  There are 2 HDDs in SW raid1, ext3, deadline scheduler and much higher
  loads and CPU usage after upgrade to Lucid. Cpu:
  http://bayimg.com/JAAdOaaDo Fork rate: http://bayimg.com/IaadkaADo
  Interrupts: http://bayimg.com/iaaDLAAdo IRQ stats
  http://bayimg.com/IAAdmaadO Load http://bayimg.com/iaAdnaaDO
  Individual Interrupts http://bayimg.com/iaADOaado VMStat
  http://bayimg.com/KAADbAADo

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: linux-image-2.6.32-25-server 2.6.32-25.45
  Regression: Yes
  Reproducible: Yes
  ProcVersionSignature: Ubuntu 2.6.32-25.45-server 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-server x86_64
  NonfreeKernelModules: ksplice_2j0nhczs ksplice_wsezy5qm ksplice_kbveoa2w 
ksplice_0hanf5d6 ksplice_2c43k68c ksplice_mqoghill ksplice_2m2ow24r 
ksplice_cmm72wdd_vmlinux_new ksplice_cmm72wdd ksplice_f8zlckse_vmlinux_new 
ksplice_f8zlckse ksplice_d0fz3e13_vmlinux_new ksplice_d0fz3e13
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  AplayDevices: Error: [Errno 2] No such file or directory
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/timer'] 
failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  Date: Tue Nov 30 09:37:59 2010
  HibernationDevice: RESUME=UUID=deda08e1-8a7c-4b5c-ae87-238498c29d95
  IwConfig:
   lono wireless extensions.

   eth0  no wireless extensions.
  Lsusb:
   Bus 002 Device 002: ID 8087:0020
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 04d9:1400 Holtek Semiconductor, Inc.
   Bus 001 Device 002: ID 8087:0020
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-25-server 
root=UUID=ec0a3dab-85e2-4898-aa47-e7f9e36a057f ro quiet splash
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: linux-firmware 1.34.1
  RfKill:

  SourcePackage: linux
  WifiSyslog:
   Nov 30 06:52:52 server kernel: [492809.162010] hlds_i686[29851]: segfault at 
a0a140 ip f76a0fd0 sp ffe0d9b0 error 4 in 
libc-2.11.1.so[f7641000+153000]
   Nov 30 07:41:42 server kernel: [495739.830680] hlds_i686[29742]: segfault at 
0 ip f4bec5bb sp ffa41b90 error 4 in 
amxmodx_mm_i386.so[f4bc5000+6f000]
   Nov 30 07:41:53 server kernel: [495750.980815] hlds_i686[2932]: segfault at 
9980f8 ip f766cfd0 sp ffe79230 error 4 in 
libc-2.11.1.so[f760d000+153000]
   Nov 30 07:42:04 server kernel: [495761.087708] hlds_i686[2940]: segfault at 
90f8 ip f766afd0 sp ffd97350 error 4 in 
libc-2.11.1.so[f760b000+153000]
   Nov 30 07:42:14 server kernel: [495771.188378] hlds_i686[2948]: segfault at 
7990f8 ip f75fcfd0 sp ffa67ba0 error 4 in 
libc-2.11.1.so[f759d000+153000]
  dmi.bios.date: 08/02/2009
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: WBIBX10J.86A.0122.2009.0802.2219
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DP55WB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE64798-204
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrWBIBX10J.86A.0122.2009.0802.2219:bd08/02/2009:svn:pn:pvr:rvnIntelCorporation:rnDP55WB:rvrAAE64798-204:cvn:ct2:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/683013/+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 1205494] Re: [Dell XPS 18] Touch screen not functioning under Ubuntu 13.04 13.10

You may need to run the following:

>From a terminal run the commands: 
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the kernel .deb packages.  You don't need to install the
headers, just the linux-image and linux-image-extra .deb packages.

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

Title:
  [Dell XPS 18] Touch screen not functioning under Ubuntu 13.04 13.10

Status in “linux” package in Ubuntu:
  In Progress

Bug description:
  I ran `ubuntu-bug linux` from Ubuntu 13.04 terminal session, and it
  appeared to have uploaded the information successfully.

  Additional items:

  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu 13.04
  Release:  13.04

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-19-generic 3.8.0-19.29
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 3270 F pulseaudio
  CasperVersion: 1.331
  Date: Fri Jul 26 21:11:10 2013
  LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS 18
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper quiet splash --
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-19-generic N/A
   linux-backports-modules-3.8.0-19-generic  N/A
   linux-firmware1.106
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0GWH76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 13
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd06/04/2013:svnDellInc.:pnXPS18:pvrNotSpecified:rvnDellInc.:rn0GWH76:rvrA00:cvnDellInc.:ct13:cvrNotSpecified:
  dmi.product.name: XPS 18
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1205494/+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 1214085] Re: LXC + BTRFS: creating many containers simultaneously can cause system corruption

So it sounds like the bug still exists in the latest Mainline kernel,
and it has been around since at lease the 3.2 kernel.  Do you happen to
know if there was a previous release that did not exhibit this bug?

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

Title:
  LXC + BTRFS: creating many containers simultaneously can cause system
  corruption

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Using lxc with a btrfs filesystem can lead to system corruption and
  containers which are unable to boot when many containers are created
  and started simultaneously.

  Packages involved:

  - btrfs-tools
  - ubuntu-lxc/daily from http://ppa.launchpad.net/ubuntu-lxc/daily/ubuntu

  `lsb_release -rd`:

  ubuntu@ip-10-91-30-131:~$ lsb_release -rd
  Description:  Ubuntu 12.04.2 LTS
  Release:  12.04

  Here is the relevant discussion thread: http://www.mail-archive.com
  /lxc-us...@lists.sourceforge.net/msg05472.html

  And here is a key excerpt regarding reproducing the problem:

  The general system state is something like:
  N containers already running happily
  Launch N+ more containers in rapid succession (in parallell, not serially).

  Here is a test script which closely reflects what my application is
  actually doing.  It slowly launches 10 containers and then uses "&" to
  rapidly fork an additional 10 clone/start operations.  I have it doing
  2 cycles of this, and running the script many times (2-6 times)
  eventually triggers the problem.

  test.sh:
  #!/usr/bin/env bash

  prefix=$1

  test -z "${prefix}" && echo 'error: missing required parameter:
  prefix' 1>&2 && exit 1

  path=/mnt

  sudo lxc-destroy -n c1 2>/dev/null
  sudo lxc-create -t ubuntu -B btrfs -n c1

  for i in `seq 1 10`; do
  sudo lxc-clone -s -B btrfs -P $path -o c1 -n $prefix$i
  sudo lxc-start -d -n $prefix$i
  done
  for i in `seq 11 20`; do
  echo $(sudo lxc-clone -s -B btrfs -P $path -o c1 -n $prefix$i; sudo 
lxc-start -d -n $prefix$i) &
  done

  sleep 10

  # Create even more.
  for i in `seq 21 30`; do
  sudo lxc-clone -s -B btrfs -P $path -o c1 -n $prefix$i
  sudo lxc-start -d -n $prefix$i
  done
  for i in `seq 31 40`; do
  echo $(sudo lxc-clone -s -B btrfs -P $path -o c1 -n $prefix$i; sudo 
lxc-start -d -n $prefix$i) &
  done

  stop.sh:
  #!/usr/bin/env bash

  prefix=$1

  test -z "${prefix}" && echo 'error: missing required parameter:
  prefix' 1>&2 && exit 1

  sudo lxc-destroy -n c1;

  for i in `seq 1 40`; do
  echo $(sudo lxc-stop -k -n $prefix$i; sudo lxc-destroy -n $prefix$i) &
  done

  bash ./test.sh x
  bash ./test.sh y
  bash ./test.sh z

  If it doesn't manifest at first, try starting/stopping/destroying
  varying quantities of containers for several cycles.  Eventually I
  consistently end up not ever getting ip addresses or being able to
  even successfully start a container:

  x1  RUNNING  - - NO
  x10 RUNNING  - - NO
  x11 RUNNING  - - NO
  x12 RUNNING  - - NO
  x13 RUNNING  - - NO
  x14 RUNNING  - - NO
  x15 RUNNING  - - NO
  x16 RUNNING  - - NO
  x17 RUNNING  - - NO
  x18 RUNNING  - - NO
  x19 RUNNING  - - NO
  x2  RUNNING  - - NO
  x20 RUNNING  - - NO
  x21 RUNNING  - - NO
  x22 RUNNING  - - NO
  x23 RUNNING  - - NO
  x24 RUNNING  - - NO
  x25 RUNNING  - - NO
  x26 RUNNING  - - NO
  x27 RUNNING  - - NO
  x28 RUNNING  - - NO
  x29 RUNNING  - - NO
  x3  RUNNING  - - NO
  x30 RUNNING  - - NO
  x31 RUNNING  - - NO
  x32 RUNNING  - - NO
  x33 RUNNING  - - NO
  x34 RUNNING  - - NO
  x35 RUNNING  - - NO
  x36 RUNNING  - - NO
  x37 RUNNING  - - NO
  x38 RUNNING  - - NO
  x39 RUNNING  - - NO
  x4  RUNNING  - - NO
  x40 RUNNING  - - NO
  x5  RUNNING  - - NO
  x6  RUNN

Re: [Kernel-packages] [Bug 1201528] Re: [Realtek ALC889] - Audio Playback Unavailable

2013-08-20 Thread Natalia Bidart

On Tue, Aug 20, 2013 at 5:14 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:

> Maybe try re-installing the kernels from the partition you use for these
> tests?  Or you could also try running update-grub again?
>

I fixed by running update-grub from my saucy, as per my last comment on the
bug.

Tested the 3.9-rc4 and audio broke.

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

Title:
  [Realtek ALC889] - Audio Playback Unavailable

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Incomplete
Status in “alsa-driver” source package in Raring:
  New
Status in “linux” source package in Raring:
  Incomplete
Status in “alsa-driver” source package in Saucy:
  New
Status in “linux” source package in Saucy:
  Incomplete

Bug description:
  This is a fresh upgrade to raring. During the weekend, I updated from
  precise to quantal, and from there to raring. I did not use sound
  while the system was in quantal, so no idea if the bug was present
  there as well.

  The symptom is:

  * after some period of sound usage, playback stops working

  What I mean with sound usage is:

  I tried having a meeting with: mumble, skype, and google hangout, and
  in all three cases, audio input/outout will work just fine for ~5
  minutes, and the playback just dies (people tell me they keep
  listening to me, so mic works fine).

  The only way to solve this is by rebooting. After one of the reboots,
  I was able to play a 20 minute video with mplayer with no further
  issue. Then opened skype and after ~3-5 minute talk, audio playback
  died again.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
  Uname: Linux 3.8.0-26-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nessita2627 F pulseaudio
  Date: Mon Jul 15 14:40:20 2013
  InstallationDate: Installed on 2011-12-20 (572 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(2029.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
  Symptom_AlsaPlaybackTestStderr:
   W r i t e   e r r o r :   - 5 , I n p u t / o u t p u t   e r r o r 
x r u n _ r e c o v e r y   f a i l e d :   - 5 , I n p u t / o u t p u t   
e r r o r 
T r a n s f e r   f a i l e d :   O p e r a t i o n   n o t   p e r m i t t 
e d
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: None of the above
  Title: [, Realtek ALC889, Green Headphone Out, Front] Playback problem
  UpgradeStatus: Upgraded to raring on 2013-07-13 (2 days ago)
  dmi.bios.date: 08/05/2009
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KGIBX10J.86A.3206.2009.0805.1855
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DP55WG
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE57269-404
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKGIBX10J.86A.3206.2009.0805.1855:bd08/05/2009:svn:pn:pvr:rvnIntelCorporation:rnDP55WG:rvrAAE57269-404:cvn:ct2:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1201528/+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 1193174] Re: Enable/disable Hyper-V drivers

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

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

Title:
  Enable/disable Hyper-V drivers

Status in “linux” package in Ubuntu:
  Fix Released

Bug description:
  The Hyper-V team recently discovered an issue in our paravirtualized
  drivers that prevent users from disabling and enabling these drivers.
  To fix that we implemented the following patch in the upstream kernel.
  Please include this in Ubuntu 13.10 release:

  commit c87059793dd02390b504b0292bdb024ffd68b822
  Author: K. Y. Srinivasan 
  Date:   Fri Mar 15 12:25:44 2013 -0700

  Drivers: hv: vmbus: Handle channel rescind message correctly

  Properly cleanup the channel state on receipt of the "offer rescind" 
message.
  Starting with ws2012, the host requires that the channel "relid" be 
properly
  cleaned up when the offer is rescinded.

  Signed-off-by: K. Y. Srinivasan 
  Reviewed-by: Haiyang Zhang 
  Signed-off-by: Greg Kroah-Hartman gre...@linuxfoundation.org

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1193174/+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 1213009] Re: alx driver is not working after system resume

Right, sorry, with 3.2 and 3.5 you would need the backports kernel.  Can
you also test the v3.10 kernel:

https://launchpad.net/ubuntu/+source/linux/3.10.0-6.17/+build/4828465

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

Title:
  alx driver is not working after system resume

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  The following is being reproduced every-time:
  When coming back from suspend, the alx driver wont work: I get 'Cable 
unplugged' in th e kde network manager and when I type dmesg, I see the 
following lines (continuing endlessly, until the computer is restarted): 

  [  866.183169] alx :04:00.0: invalid PHY speed/duplex: 0x
  [  866.184192] alx :04:00.0: invalid PHY speed/duplex: 0x
  [  866.185233] alx :04:00.0: invalid PHY speed/duplex: 0x
  [  866.186255] alx :04:00.0: invalid PHY speed/duplex: 0x
  [  866.187278] alx :04:00.0: invalid PHY speed/duplex: 0x
  [  866.188298] alx :04:00.0: invalid PHY speed/duplex: 0x
  [  866.189314] alx :04:00.0: invalid PHY speed/duplex: 0x
  [  866.190345] alx :04:00.0: invalid PHY speed/duplex: 0x
  ...

  also if I try to do something like
  ifconfig eth0 down
  the system is hanged
  (alternatively it is also hanged when I go to the network manager and uncheck 
the box 'Enable Networking')

  I'm attaching the output of ifconfig and ip before and after suspend,
  in case it might provide help.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-2-generic 3.11.0-2.5
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nope   1852 F pulseaudio
  Date: Fri Aug 16 12:34:30 2013
  HibernationDevice: RESUME=UUID=c2788727-ecc5-4f11-9246-3047690865eb
  MachineType: ASUSTeK COMPUTER INC. N56VB
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic 
root=UUID=58208c52-0ccf-4acc-b88d-b116fe6d369e ro quiet splash pcie_aspm=force 
acpi_backlight=vendor vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-2-generic N/A
   linux-backports-modules-3.11.0-2-generic  N/A
   linux-firmware1.113
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-08-08 (8 days ago)
  dmi.bios.date: 01/21/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N56VB.202
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N56VB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN56VB.202:bd01/21/2013:svnASUSTeKCOMPUTERINC.:pnN56VB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N56VB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213009/+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 1214462] Re: Kernel Description doesn't explain its a PAE-Kernel _ since 3.4.0.1.1 _ Linus would not smile _.

This looks lunatic to me:

http://packages.ubuntu.com/raring/linux-generic-pae (Transitional
package - this is a wrapper?)

http://packages.ubuntu.com/raring/linux-generic (This contains the PAE-
part of the Kernel?)

Distributions find their own namings for Kernels (may be o.k. in little
variants),

but saying the PAE is the Non-PAE is strange thinking (absolutely illogical to 
me)  –  a camouflaged PAE-Kernel
)

If it's hard to understand: try it the other way around - What if: non-
PAE had been kept & PAE would have been kicked - same naming? See?

Anyway, the -i386 was actually removed from the original Linux-Kernel (I
can open new bug on this?):

> http://www.muktware.com/4967/linux-kills-
intels-386-processors#.UMiPlnKMy7J dated 12.12.12

So the newer kernels should probably rather differentiate e.g. into
i486/AMD64 than into i386/AMD64 on top.

On one old little machine Dell D600 I had no Problems installing a PAE-
Kernel, nowadays I need to change the pre-inst. script on every Kernel-
Update or install a fake-PAE upstart skript. My old anger came up upon
usage of a Live-CD of Elemntary-OS. It refused to start: "Use an
appropriate Kernel, bla" The Machine runs with Mainline Kernel 3.10 PAE.
This may thrift away a lot of people from Ubuntu & it's derivates.
Enough reason to finally start thinking "Is it worth a bug report?"
Apport can't help here.

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

Title:
  Kernel Description doesn't explain its a PAE-Kernel _ since 3.4.0.1.1
  _ Linus would not smile _.

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Dear Developers and maintainers,

  trying not to make a big fuzz about it:

  Let me just quote
  https://bugs.launchpad.net/baltix/+bug/930447/comments/97 from
  2012-06-05 (referencing the release-notes on 12.04.2):

  > The non-PAE version of the Linux kernel will be dropped completely
  > following the 12.04 release.

  Pls correct me and mark as invalid, if Ubuntu doesn't have to follow
  naming conventions given on the Linux-Kernel.

  Trying to find appropiate information in the package change-log:

  linux-meta (3.4.0.1.1) quantal; urgency=low

    * Open Quantal Quetzal 12.10
    * Temporarily disable LBM
    * Remove non-PAE i386 references

   -- mail adress hid...@canonical.com>  Wed, 02 May 2012 06:21:45 -0700

  Pls clarify this and correct Ubuntus Kernel-naming on i386 package if
  appropriate.If the leftovers in the package are PAE, the package-names
  are meant to say so Clear & Loud.

  Personally I think Linus wouldn't smile, even though if I thought the
  index-finger to Nvidia was a bit to rough. Personally I think this bug
  has security-potential.

  Thanks for helping to make Ubuntu better every day.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214462/+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 1214598] Status changed to Confirmed

This change was made by a bot.

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

Title:
   kernel 3.8.0-29 does not detect usb memories; but 3.8.0-27 detects
  them

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I updated the kernel from 3.8.0-27 to 3.8.0-29, I rebooted,  the
  3.8.0-29 kernel was used, and...  two usb memories were no longer
  detected.

  I rebooted and chose the 3.8.0-27 kernel, then both usb memories were
  detected.

  I rebooted and chose the 3.8.0-29 kernel again, then both usb memories
  were *not* detected.

  I rebooted and chose the 3.8.0-27 kernel, then both usb memories were
  detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-29-generic 3.8.0-29.42
  ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
  Uname: Linux 3.8.0-29-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  to 2018 F pulseaudio
  Date: Tue Aug 20 22:35:40 2013
  HibernationDevice: RESUME=UUID=4c2c479a-1691-41c5-9c3a-9b6a58b15d0c
  InstallationDate: Installed on 2013-05-05 (107 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Quanta TW8/SW8/DW8
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic 
root=UUID=b1b85f9b-e29c-4726-be45-6f3df935dedf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-29-generic N/A
   linux-backports-modules-3.8.0-29-generic  N/A
   linux-firmware1.106
  RfKill:
   1: phy1: Wireless LAN
Soft blocked: no
Hard blocked: yes
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2008
  dmi.bios.vendor: INSYDE
  dmi.bios.version: I3C42
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: TW8/SW8/DW8
  dmi.board.vendor: Quanta
  dmi.board.version: UnIn
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: UK
  dmi.modalias: 
dmi:bvnINSYDE:bvrI3C42:bd11/10/2008:svnQuanta:pnTW8/SW8/DW8:pvr03:rvnQuanta:rnTW8/SW8/DW8:rvrUnIn:cvnQuanta:ct1:cvrUK:
  dmi.product.name: TW8/SW8/DW8
  dmi.product.version: 03
  dmi.sys.vendor: Quanta

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214598/+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 1214598] [NEW] kernel 3.8.0-29 does not detect usb memories; but 3.8.0-27 detects them

Public bug reported:

I updated the kernel from 3.8.0-27 to 3.8.0-29, I rebooted,  the
3.8.0-29 kernel was used, and...  two usb memories were no longer
detected.

I rebooted and chose the 3.8.0-27 kernel, then both usb memories were
detected.

I rebooted and chose the 3.8.0-29 kernel again, then both usb memories
were *not* detected.

I rebooted and chose the 3.8.0-27 kernel, then both usb memories were
detected.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-29-generic 3.8.0-29.42
ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
Uname: Linux 3.8.0-29-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  to 2018 F pulseaudio
Date: Tue Aug 20 22:35:40 2013
HibernationDevice: RESUME=UUID=4c2c479a-1691-41c5-9c3a-9b6a58b15d0c
InstallationDate: Installed on 2013-05-05 (107 days ago)
InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: Quanta TW8/SW8/DW8
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic 
root=UUID=b1b85f9b-e29c-4726-be45-6f3df935dedf ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-29-generic N/A
 linux-backports-modules-3.8.0-29-generic  N/A
 linux-firmware1.106
RfKill:
 1: phy1: Wireless LAN
Soft blocked: no
Hard blocked: yes
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/10/2008
dmi.bios.vendor: INSYDE
dmi.bios.version: I3C42
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: TW8/SW8/DW8
dmi.board.vendor: Quanta
dmi.board.version: UnIn
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: Quanta
dmi.chassis.version: UK
dmi.modalias: 
dmi:bvnINSYDE:bvrI3C42:bd11/10/2008:svnQuanta:pnTW8/SW8/DW8:pvr03:rvnQuanta:rnTW8/SW8/DW8:rvrUnIn:cvnQuanta:ct1:cvrUK:
dmi.product.name: TW8/SW8/DW8
dmi.product.version: 03
dmi.sys.vendor: Quanta

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


** Tags: amd64 apport-bug raring

** Attachment added: "lspci-vvnn___kernel_3.8.0-29_in_PC_Ganton.text"
   
https://bugs.launchpad.net/bugs/1214598/+attachment/3779900/+files/lspci-vvnn___kernel_3.8.0-29_in_PC_Ganton.text

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

Title:
   kernel 3.8.0-29 does not detect usb memories; but 3.8.0-27 detects
  them

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I updated the kernel from 3.8.0-27 to 3.8.0-29, I rebooted,  the
  3.8.0-29 kernel was used, and...  two usb memories were no longer
  detected.

  I rebooted and chose the 3.8.0-27 kernel, then both usb memories were
  detected.

  I rebooted and chose the 3.8.0-29 kernel again, then both usb memories
  were *not* detected.

  I rebooted and chose the 3.8.0-27 kernel, then both usb memories were
  detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-29-generic 3.8.0-29.42
  ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
  Uname: Linux 3.8.0-29-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  to 2018 F pulseaudio
  Date: Tue Aug 20 22:35:40 2013
  HibernationDevice: RESUME=UUID=4c2c479a-1691-41c5-9c3a-9b6a58b15d0c
  InstallationDate: Installed on 2013-05-05 (107 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Quanta TW8/SW8/DW8
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic 
root=UUID=b1b85f9b-e29c-4726-be45-6f3df935dedf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-29-generic N/A
   linux-backports-modules-3.8.0-29-generic  N/A
   linux-firmware1.106
  RfKill:
   1: phy1: Wireless LAN
Soft blocked: no
Hard blocked: yes
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2008
  dmi.bios.vendor: INSYDE
  dmi.bios.version: I3C42
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: TW8/SW8/DW8
  dmi.board.vendor: Quanta
  dmi.board.version: UnIn
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: UK
  dmi.modalias: 
dmi:bvnINSYDE:bvrI3C42:bd11/10/2008:svnQuanta:pnTW8/SW8/DW8:pvr03:rvnQuanta:rnTW8/SW8/DW8:rvrUnIn:cvnQuanta:ct1:cvrUK:
  dmi.product.name: TW8/SW8/DW8
  dmi.product.version: 03
  dmi.sys.vendor: Quanta

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

-- 
Mailing list: https://launchpad.net/~kernel-pac

[Kernel-packages] [Bug 1062077] Re: [HP TouchSmart tm2-2010eg] Linux hangs with: "[drm:atom_op_jump] ERROR atombios stuck in loop for more than 5secs aborting"

2013-08-20 Thread kapad

> We don't get this issue during normal modeset, so I suspect the regs
are in a wonky state after resume. Perhaps a hard reset before asic_init
would help.

What is a hard reset before asic_init

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

Title:
  [HP TouchSmart tm2-2010eg] Linux hangs with: "[drm:atom_op_jump]
  *ERROR* atombios stuck in loop for more than 5secs aborting"

Status in The Linux Kernel:
  Confirmed
Status in “linux” package in Ubuntu:
  Incomplete
Status in “xserver-xorg-video-ati” package in Ubuntu:
  Confirmed

Bug description:
  Symptom: Linux isn't displaying changes after switching to tty1 and
  back to unity

  Steps to reproduce:
  1. Starting up to Unity
  2. Switch to tty1 (Strg + Alt + F1)
  3. Switching back to Unity

  or:
  Resuming the system from suspend leads to the same isssue.This method isn't 
as reliable as the method stated above

  What happens:
  The screen freezes. Magic Keys [Alt + Print + S/U/B] are working thou (so 
linux-kernel is responding?!) I can't switch to tty1 either. The system becomes 
responding again after ~2min. Switching VTs is possible afterwards but leads to 
the same bug again.

  What is expected:
  Showing up a responding Unity.

  Interesting Sitenote:
  My radeon is switched off using: 
echo"OFF">/sys/kernel/debug/vgaswitcheroo/switch
  By turning "ON" the graphiccard the above stated problem doesn't appear.

  A short extract of kern.log (full one is attached):
  Oct  5 09:06:06 Octavian-Notebook kernel: [  186.691685] [drm:atom_op_jump] 
*ERROR* atombios stuck in loop for more than 5secs aborting
  Oct  5 09:06:06 Octavian-Notebook kernel: [  186.691700] 
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing C98E (len 62, 
WS 0, PS 0) @ 0xC9AA
  Oct  5 09:06:11 Octavian-Notebook kernel: [  191.692930] [drm:atom_op_jump] 
*ERROR* atombios stuck in loop for more than 5secs aborting
  Oct  5 09:06:11 Octavian-Notebook kernel: [  191.692949] 
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing C98E (len 62, 
WS 0, PS 0) @ 0xC9AA
  Oct  5 09:06:11 Octavian-Notebook kernel: [  191.692960] 
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing C040 (len 861, 
WS 0, PS 0) @ 0xC09D
  Oct  5 09:06:16 Octavian-Notebook kernel: [  197.021996] [drm:atom_op_jump] 
*ERROR* atombios stuck in loop for more than 5secs aborting
  Oct  5 09:06:16 Octavian-Notebook kernel: [  197.022011] 
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing CE0C (len 72, 
WS 0, PS 0) @ 0xCE3B
  Oct  5 09:06:22 Octavian-Notebook kernel: [  202.223115] [drm:atom_op_jump] 
*ERROR* atombios stuck in loop for more than 5secs aborting
  Oct  5 09:06:22 Octavian-Notebook kernel: [  202.223134] 
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing C98E (len 62, 
WS 0, PS 0) @ 0xC9AA
  Oct  5 09:06:27 Octavian-Notebook kernel: [  207.424244] [drm:atom_op_jump] 
*ERROR* atombios stuck in loop for more than 5secs aborting
  Oct  5 09:06:27 Octavian-Notebook kernel: [  207.424259] 
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing C98E (len 62, 
WS 0, PS 0) @ 0xC9AA
  Oct  5 09:06:32 Octavian-Notebook kernel: [  212.625368] [drm:atom_op_jump] 
*ERROR* atombios stuck in loop for more than 5secs aborting
  Oct  5 09:06:32 Octavian-Notebook kernel: [  212.625387] 
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing C98E (len 62, 
WS 0, PS 0) @ 0xC9AA
  Oct  5 09:06:37 Octavian-Notebook kernel: [  217.826526] [drm:atom_op_jump] 
*ERROR* atombios stuck in loop for more than 5secs aborting
  Oct  5 09:06:37 Octavian-Notebook kernel: [  217.826545] 
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing C98E (len 62, 
WS 0, PS 0) @ 0xC9AA
  Oct  5 09:06:42 Octavian-Notebook kernel: [  223.027631] [drm:atom_op_jump] 
*ERROR* atombios stuck in loop for more than 5secs aborting
  Oct  5 09:06:42 Octavian-Notebook kernel: [  223.027650] 
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing C98E (len 62, 
WS 0, PS 0) @ 0xC9AA
  Oct  5 09:06:48 Octavian-Notebook kernel: [  228.228756] [drm:atom_op_jump] 
*ERROR* atombios stuck in loop for more than 5secs aborting
  Oct  5 09:06:48 Octavian-Notebook kernel: [  228.228772] 
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing C98E (len 62, 
WS 0, PS 0) @ 0xC9AA
  Oct  5 09:06:51 Octavian-Notebook kernel: [  231.957328] SysRq : This sysrq 
operation is disabled.
  Oct  5 09:06:52 Octavian-Notebook kernel: [  232.739445] SysRq : This sysrq 
operation is disabled.
  Oct  5 09:06:52 Octavian-Notebook kernel: [  233.139471] SysRq : This sysrq 
operation is disabled.
  Oct  5 09:06:53 Octavian-Notebook kernel: [  233.429887] [drm:atom_op_jump] 
*ERROR* atombios stuck in loop for more than 5secs aborting
  Oct  5 09:06:53 Octavian-Notebook kernel: [  233.429900] 
[drm:atom_execute_table_locked] *ERROR* atombios stuck executi

[Kernel-packages] [Bug 946899] Re: [drm:i915_hangcheck_elapsed] ERROR Hangcheck timer elapsed... GPU hung

2013-08-20 Thread Stan Schymanski

Thanks, peterbo, for the link incl. installation instructions! 
Unfortunately after two days, I had another crash with the new kernel on Ubuntu 
12.10. The mouse and keyboard stopped responding and before I could try to do 
CTRL+ALT+F4 or CTRL+ALT+SysRq+REISUB, the laptop just turned itself off. No 
traces left in syslog. Very annoying.

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

Title:
  [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU
  hung

Status in The Linux Kernel:
  Incomplete
Status in The Linux Mint Distribution:
  Confirmed
Status in “linux” package in Ubuntu:
  Triaged
Status in “linux” package in Fedora:
  Unknown

Bug description:
  Since upgrading to 12.04 beta, I've seen this happen twice. The
  symptoms are:

  - The screen freezes
  - The backlight turns off

  At that point I have to reboot to get my display back. In syslog, i
  see:

  
  Mar  4 23:09:18 perseus kernel: [ 3751.612064] [drm:i915_hangcheck_elapsed] 
*ERROR* Hangcheck timer elapsed... GPU hung
  Mar  4 23:09:18 perseus kernel: [ 3751.612076] [drm] capturing error event; 
look for more information in /debug/dri/0/i915_error_state
  Mar  4 23:09:18 perseus kernel: [ 3751.613658] [drm:i915_wait_request] 
*ERROR* i915_wait_request returns -11 (awaiting 114040 at 114004, next 114118)
  Mar  4 23:09:18 perseus kernel: [ 3751.637049] [drm:init_ring_common] *ERROR* 
render ring initialization failed ctl  head  tail  
start 

  followed by a lot of things like:

  
  Mar  4 23:09:18 perseus kernel: [ 3751.700662] WARNING: at 
/build/buildd/linux-3.2.0/drivers/gpu/drm/i915/intel_display.c:793 
intel_enable_pipe+0x14a/0x150 [i915]()
  Mar  4 23:09:18 perseus kernel: [ 3751.700667] Hardware name: 6465CTO
  Mar  4 23:09:18 perseus kernel: [ 3751.700670] PLL state assertion failure 
(expected on, current off)

  Mar  4 23:09:18 perseus kernel: [ 3751.812158] WARNING: at 
/build/buildd/linux-3.2.0/drivers/gpu/drm/i915/intel_display.c:930 
assert_pipe+0x75/0x80 [i915]()
  Mar  4 23:09:18 perseus kernel: [ 3751.812165] Hardware name: 6465CTO
  Mar  4 23:09:18 perseus kernel: [ 3751.812170] pipe B assertion failure 
(expected on, current off)

  then:

  
  Mar  4 23:09:19 perseus kernel: [ 3753.044086] [drm:intel_lvds_enable] 
*ERROR* timed out waiting for panel to power on
  Mar  4 23:09:20 perseus kernel: [ 3753.671451] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.684603] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.704594] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.724594] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.744595] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.764606] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.784607] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.804618] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.824606] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-17-generic 3.2.0-17.27
  ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
  Uname: Linux 3.2.0-17-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.94-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mdz2458 F pulseaudio
   /dev/snd/controlC1:  mdz2458 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfe02 irq 49'
 Mixer name : 'Analog Devices AD1984'
 Components : 'HDA:11d41984,17aa20bb,00100400'
 Controls  : 31
 Simple ctrls  : 19
  Card1.Amixer.info:
   Card hw:1 'Q9000'/'Logitech, Inc. QuickCam Pro 9000 at usb-:00:1a.7-3, 
high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:0990'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 3072
 Mono: Capture 0 [0%] [18.00dB] [off]
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
7KHT24WW-1.0

[Kernel-packages] [Bug 1214598] Re: kernel 3.8.0-29 does not detect usb memories; but 3.8.0-27 detects them

** Attachment added: 
"cat_⁄proc⁄version_signature___kernel_3.8.0-29_in_PC_Ganton.text"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214598/+attachment/3779929/+files/cat_%E2%81%84proc%E2%81%84version_signature___kernel_3.8.0-29_in_PC_Ganton.text

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

Title:
   kernel 3.8.0-29 does not detect usb memories; but 3.8.0-27 detects
  them

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I updated the kernel from 3.8.0-27 to 3.8.0-29, I rebooted,  the
  3.8.0-29 kernel was used, and...  two usb memories were no longer
  detected.

  I rebooted and chose the 3.8.0-27 kernel, then both usb memories were
  detected.

  I rebooted and chose the 3.8.0-29 kernel again, then both usb memories
  were *not* detected.

  I rebooted and chose the 3.8.0-27 kernel, then both usb memories were
  detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-29-generic 3.8.0-29.42
  ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
  Uname: Linux 3.8.0-29-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  to 2018 F pulseaudio
  Date: Tue Aug 20 22:35:40 2013
  HibernationDevice: RESUME=UUID=4c2c479a-1691-41c5-9c3a-9b6a58b15d0c
  InstallationDate: Installed on 2013-05-05 (107 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Quanta TW8/SW8/DW8
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic 
root=UUID=b1b85f9b-e29c-4726-be45-6f3df935dedf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-29-generic N/A
   linux-backports-modules-3.8.0-29-generic  N/A
   linux-firmware1.106
  RfKill:
   1: phy1: Wireless LAN
Soft blocked: no
Hard blocked: yes
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2008
  dmi.bios.vendor: INSYDE
  dmi.bios.version: I3C42
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: TW8/SW8/DW8
  dmi.board.vendor: Quanta
  dmi.board.version: UnIn
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: UK
  dmi.modalias: 
dmi:bvnINSYDE:bvrI3C42:bd11/10/2008:svnQuanta:pnTW8/SW8/DW8:pvr03:rvnQuanta:rnTW8/SW8/DW8:rvrUnIn:cvnQuanta:ct1:cvrUK:
  dmi.product.name: TW8/SW8/DW8
  dmi.product.version: 03
  dmi.sys.vendor: Quanta

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214598/+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 1214598] Re: kernel 3.8.0-29 does not detect usb memories; but 3.8.0-27 detects them

** Attachment added: "lsb_release_-rd___kernel_3.8.0-29_in_PC_Ganton.text"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214598/+attachment/3779932/+files/lsb_release_-rd___kernel_3.8.0-29_in_PC_Ganton.text

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

Title:
   kernel 3.8.0-29 does not detect usb memories; but 3.8.0-27 detects
  them

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I updated the kernel from 3.8.0-27 to 3.8.0-29, I rebooted,  the
  3.8.0-29 kernel was used, and...  two usb memories were no longer
  detected.

  I rebooted and chose the 3.8.0-27 kernel, then both usb memories were
  detected.

  I rebooted and chose the 3.8.0-29 kernel again, then both usb memories
  were *not* detected.

  I rebooted and chose the 3.8.0-27 kernel, then both usb memories were
  detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-29-generic 3.8.0-29.42
  ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
  Uname: Linux 3.8.0-29-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  to 2018 F pulseaudio
  Date: Tue Aug 20 22:35:40 2013
  HibernationDevice: RESUME=UUID=4c2c479a-1691-41c5-9c3a-9b6a58b15d0c
  InstallationDate: Installed on 2013-05-05 (107 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Quanta TW8/SW8/DW8
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic 
root=UUID=b1b85f9b-e29c-4726-be45-6f3df935dedf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-29-generic N/A
   linux-backports-modules-3.8.0-29-generic  N/A
   linux-firmware1.106
  RfKill:
   1: phy1: Wireless LAN
Soft blocked: no
Hard blocked: yes
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2008
  dmi.bios.vendor: INSYDE
  dmi.bios.version: I3C42
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: TW8/SW8/DW8
  dmi.board.vendor: Quanta
  dmi.board.version: UnIn
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: UK
  dmi.modalias: 
dmi:bvnINSYDE:bvrI3C42:bd11/10/2008:svnQuanta:pnTW8/SW8/DW8:pvr03:rvnQuanta:rnTW8/SW8/DW8:rvrUnIn:cvnQuanta:ct1:cvrUK:
  dmi.product.name: TW8/SW8/DW8
  dmi.product.version: 03
  dmi.sys.vendor: Quanta

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214598/+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 1214598] Re: kernel 3.8.0-29 does not detect usb memories; but 3.8.0-27 detects them

** Attachment added: 
"cat_⁄var⁄log⁄syslog___after_inserting_a_usb_memory___kernel_3.8.0-29_in_PC_Ganton.text"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214598/+attachment/3779931/+files/cat_%E2%81%84var%E2%81%84log%E2%81%84syslog___after_inserting_a_usb_memory___kernel_3.8.0-29_in_PC_Ganton.text

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

Title:
   kernel 3.8.0-29 does not detect usb memories; but 3.8.0-27 detects
  them

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I updated the kernel from 3.8.0-27 to 3.8.0-29, I rebooted,  the
  3.8.0-29 kernel was used, and...  two usb memories were no longer
  detected.

  I rebooted and chose the 3.8.0-27 kernel, then both usb memories were
  detected.

  I rebooted and chose the 3.8.0-29 kernel again, then both usb memories
  were *not* detected.

  I rebooted and chose the 3.8.0-27 kernel, then both usb memories were
  detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-29-generic 3.8.0-29.42
  ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
  Uname: Linux 3.8.0-29-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  to 2018 F pulseaudio
  Date: Tue Aug 20 22:35:40 2013
  HibernationDevice: RESUME=UUID=4c2c479a-1691-41c5-9c3a-9b6a58b15d0c
  InstallationDate: Installed on 2013-05-05 (107 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Quanta TW8/SW8/DW8
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic 
root=UUID=b1b85f9b-e29c-4726-be45-6f3df935dedf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-29-generic N/A
   linux-backports-modules-3.8.0-29-generic  N/A
   linux-firmware1.106
  RfKill:
   1: phy1: Wireless LAN
Soft blocked: no
Hard blocked: yes
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2008
  dmi.bios.vendor: INSYDE
  dmi.bios.version: I3C42
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: TW8/SW8/DW8
  dmi.board.vendor: Quanta
  dmi.board.version: UnIn
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: UK
  dmi.modalias: 
dmi:bvnINSYDE:bvrI3C42:bd11/10/2008:svnQuanta:pnTW8/SW8/DW8:pvr03:rvnQuanta:rnTW8/SW8/DW8:rvrUnIn:cvnQuanta:ct1:cvrUK:
  dmi.product.name: TW8/SW8/DW8
  dmi.product.version: 03
  dmi.sys.vendor: Quanta

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214598/+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 1214598] Re: kernel 3.8.0-29 does not detect usb memories; but 3.8.0-27 detects them

** Attachment added: 
"apt-cache_policy_linux___kernel_3.8.0-29_in_PC_Ganton.text"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214598/+attachment/3779925/+files/apt-cache_policy_linux___kernel_3.8.0-29_in_PC_Ganton.text

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

Title:
   kernel 3.8.0-29 does not detect usb memories; but 3.8.0-27 detects
  them

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I updated the kernel from 3.8.0-27 to 3.8.0-29, I rebooted,  the
  3.8.0-29 kernel was used, and...  two usb memories were no longer
  detected.

  I rebooted and chose the 3.8.0-27 kernel, then both usb memories were
  detected.

  I rebooted and chose the 3.8.0-29 kernel again, then both usb memories
  were *not* detected.

  I rebooted and chose the 3.8.0-27 kernel, then both usb memories were
  detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-29-generic 3.8.0-29.42
  ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
  Uname: Linux 3.8.0-29-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  to 2018 F pulseaudio
  Date: Tue Aug 20 22:35:40 2013
  HibernationDevice: RESUME=UUID=4c2c479a-1691-41c5-9c3a-9b6a58b15d0c
  InstallationDate: Installed on 2013-05-05 (107 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Quanta TW8/SW8/DW8
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic 
root=UUID=b1b85f9b-e29c-4726-be45-6f3df935dedf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-29-generic N/A
   linux-backports-modules-3.8.0-29-generic  N/A
   linux-firmware1.106
  RfKill:
   1: phy1: Wireless LAN
Soft blocked: no
Hard blocked: yes
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2008
  dmi.bios.vendor: INSYDE
  dmi.bios.version: I3C42
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: TW8/SW8/DW8
  dmi.board.vendor: Quanta
  dmi.board.version: UnIn
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: UK
  dmi.modalias: 
dmi:bvnINSYDE:bvrI3C42:bd11/10/2008:svnQuanta:pnTW8/SW8/DW8:pvr03:rvnQuanta:rnTW8/SW8/DW8:rvrUnIn:cvnQuanta:ct1:cvrUK:
  dmi.product.name: TW8/SW8/DW8
  dmi.product.version: 03
  dmi.sys.vendor: Quanta

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214598/+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 1214598] Re: kernel 3.8.0-29 does not detect usb memories; but 3.8.0-27 detects them

** Attachment added: "lsmod___kernel_3.8.0-29_in_PC_Ganton.text"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214598/+attachment/3779934/+files/lsmod___kernel_3.8.0-29_in_PC_Ganton.text

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

Title:
   kernel 3.8.0-29 does not detect usb memories; but 3.8.0-27 detects
  them

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I updated the kernel from 3.8.0-27 to 3.8.0-29, I rebooted,  the
  3.8.0-29 kernel was used, and...  two usb memories were no longer
  detected.

  I rebooted and chose the 3.8.0-27 kernel, then both usb memories were
  detected.

  I rebooted and chose the 3.8.0-29 kernel again, then both usb memories
  were *not* detected.

  I rebooted and chose the 3.8.0-27 kernel, then both usb memories were
  detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-29-generic 3.8.0-29.42
  ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
  Uname: Linux 3.8.0-29-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  to 2018 F pulseaudio
  Date: Tue Aug 20 22:35:40 2013
  HibernationDevice: RESUME=UUID=4c2c479a-1691-41c5-9c3a-9b6a58b15d0c
  InstallationDate: Installed on 2013-05-05 (107 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Quanta TW8/SW8/DW8
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic 
root=UUID=b1b85f9b-e29c-4726-be45-6f3df935dedf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-29-generic N/A
   linux-backports-modules-3.8.0-29-generic  N/A
   linux-firmware1.106
  RfKill:
   1: phy1: Wireless LAN
Soft blocked: no
Hard blocked: yes
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2008
  dmi.bios.vendor: INSYDE
  dmi.bios.version: I3C42
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: TW8/SW8/DW8
  dmi.board.vendor: Quanta
  dmi.board.version: UnIn
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: UK
  dmi.modalias: 
dmi:bvnINSYDE:bvrI3C42:bd11/10/2008:svnQuanta:pnTW8/SW8/DW8:pvr03:rvnQuanta:rnTW8/SW8/DW8:rvrUnIn:cvnQuanta:ct1:cvrUK:
  dmi.product.name: TW8/SW8/DW8
  dmi.product.version: 03
  dmi.sys.vendor: Quanta

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214598/+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 1214598] Re: kernel 3.8.0-29 does not detect usb memories; but 3.8.0-27 detects them

** Attachment added: "lspci___kernel_3.8.0-29_in_PC_Ganton.text"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214598/+attachment/3779936/+files/lspci___kernel_3.8.0-29_in_PC_Ganton.text

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

Title:
   kernel 3.8.0-29 does not detect usb memories; but 3.8.0-27 detects
  them

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I updated the kernel from 3.8.0-27 to 3.8.0-29, I rebooted,  the
  3.8.0-29 kernel was used, and...  two usb memories were no longer
  detected.

  I rebooted and chose the 3.8.0-27 kernel, then both usb memories were
  detected.

  I rebooted and chose the 3.8.0-29 kernel again, then both usb memories
  were *not* detected.

  I rebooted and chose the 3.8.0-27 kernel, then both usb memories were
  detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-29-generic 3.8.0-29.42
  ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
  Uname: Linux 3.8.0-29-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  to 2018 F pulseaudio
  Date: Tue Aug 20 22:35:40 2013
  HibernationDevice: RESUME=UUID=4c2c479a-1691-41c5-9c3a-9b6a58b15d0c
  InstallationDate: Installed on 2013-05-05 (107 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Quanta TW8/SW8/DW8
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic 
root=UUID=b1b85f9b-e29c-4726-be45-6f3df935dedf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-29-generic N/A
   linux-backports-modules-3.8.0-29-generic  N/A
   linux-firmware1.106
  RfKill:
   1: phy1: Wireless LAN
Soft blocked: no
Hard blocked: yes
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2008
  dmi.bios.vendor: INSYDE
  dmi.bios.version: I3C42
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: TW8/SW8/DW8
  dmi.board.vendor: Quanta
  dmi.board.version: UnIn
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: UK
  dmi.modalias: 
dmi:bvnINSYDE:bvrI3C42:bd11/10/2008:svnQuanta:pnTW8/SW8/DW8:pvr03:rvnQuanta:rnTW8/SW8/DW8:rvrUnIn:cvnQuanta:ct1:cvrUK:
  dmi.product.name: TW8/SW8/DW8
  dmi.product.version: 03
  dmi.sys.vendor: Quanta

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

Re: [Kernel-packages] [Bug 1213795] Re: newer kernels (3.10+) don't boot on MacBook Air 6.1

2013-08-20 Thread Miek Gieben

[ Quoting  in "[Bug 1213795] Re: newer kernels 
(3" ]
> I started a kernel bisect between v3.9 final and v3.10-rc1. The kernel
> bisect will require testing of about 7-10 test kernels.
> 
> I built the first test kernel, up to the following commit:
> 73287a43cc79ca06629a88d1a199cd283f42456a
> 
> The test kernel can be downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1213795
> 
> Can you test that kernel and report back if it has the bug or not. I
> will build the next test kernel based on your test results.

with nosmp,libata.force=noncq -> crash
with smp -> hang in Booting Node 0, Processor #1

So fail for this bisect.

grtz Miek

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

Title:
  newer kernels (3.10+) don't boot on MacBook Air 6.1

Status in The Linux Kernel:
  Unknown
Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” source package in Saucy:
  Confirmed

Bug description:
  The current raring kernel boots (with nosmp and libata.force=noncq),
  newer kernels don't boot at all. They hang with ramdisk loading and
  nothing seems to happen. This is difficult to debug, as it happens so
  early in the boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-27-generic 3.8.0-27.40
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  miek   1872 F pulseaudio
  Date: Sun Aug 18 22:49:05 2013
  HibernationDevice: RESUME=UUID=f4250ce4-23bc-413f-9a97-205cd9ca67e5
  InstallationDate: Installed on 2013-08-19 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac 
(20130424)
  Lsusb:
   Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part 
of BCM2046 Bluetooth)
   Bus 001 Device 003: ID 05ac:0290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05ac:828f Apple, Inc.
  MachineType: Apple Inc. MacBookAir6,1
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic 
root=UUID=003d813a-5ee5-40bc-a81f-dbed66aaf939 ro nosmp libata.force=noncq 
quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-27-generic N/A
   linux-backports-modules-3.8.0-27-generic  N/A
   linux-firmware1.106
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2013
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA61.88Z.0099.B00.1305241529
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-35C1E88140C3E6CF
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir6,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-35C1E88140C3E6CF
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B00.1305241529:bd05/24/2013:svnAppleInc.:pnMacBookAir6,1:pvr1.0:rvnAppleInc.:rnMac-35C1E88140C3E6CF:rvrMacBookAir6,1:cvnAppleInc.:ct10:cvrMac-35C1E88140C3E6CF:
  dmi.product.name: MacBookAir6,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1213795/+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 1214598] Re: kernel 3.8.0-29 does not detect usb memories; but 3.8.0-27 detects them

** Attachment added: "lshw___kernel_3.8.0-29_in_PC_Ganton.text"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214598/+attachment/3779933/+files/lshw___kernel_3.8.0-29_in_PC_Ganton.text

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

Title:
   kernel 3.8.0-29 does not detect usb memories; but 3.8.0-27 detects
  them

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I updated the kernel from 3.8.0-27 to 3.8.0-29, I rebooted,  the
  3.8.0-29 kernel was used, and...  two usb memories were no longer
  detected.

  I rebooted and chose the 3.8.0-27 kernel, then both usb memories were
  detected.

  I rebooted and chose the 3.8.0-29 kernel again, then both usb memories
  were *not* detected.

  I rebooted and chose the 3.8.0-27 kernel, then both usb memories were
  detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-29-generic 3.8.0-29.42
  ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
  Uname: Linux 3.8.0-29-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  to 2018 F pulseaudio
  Date: Tue Aug 20 22:35:40 2013
  HibernationDevice: RESUME=UUID=4c2c479a-1691-41c5-9c3a-9b6a58b15d0c
  InstallationDate: Installed on 2013-05-05 (107 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Quanta TW8/SW8/DW8
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic 
root=UUID=b1b85f9b-e29c-4726-be45-6f3df935dedf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-29-generic N/A
   linux-backports-modules-3.8.0-29-generic  N/A
   linux-firmware1.106
  RfKill:
   1: phy1: Wireless LAN
Soft blocked: no
Hard blocked: yes
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2008
  dmi.bios.vendor: INSYDE
  dmi.bios.version: I3C42
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: TW8/SW8/DW8
  dmi.board.vendor: Quanta
  dmi.board.version: UnIn
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: UK
  dmi.modalias: 
dmi:bvnINSYDE:bvrI3C42:bd11/10/2008:svnQuanta:pnTW8/SW8/DW8:pvr03:rvnQuanta:rnTW8/SW8/DW8:rvrUnIn:cvnQuanta:ct1:cvrUK:
  dmi.product.name: TW8/SW8/DW8
  dmi.product.version: 03
  dmi.sys.vendor: Quanta

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214598/+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 1214598] Re: kernel 3.8.0-29 does not detect usb memories; but 3.8.0-27 detects them