[Kernel-packages] [Bug 1525152] Status changed to Confirmed

[Brad Figg]

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

Title:
  package linux-image-3.13.0-70-generic 3.13.0-70.113 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 17

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  o sistema está travando, ficando inacesível. Precisa reiniciar o
  computador.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-70-generic 3.13.0-70.113
  ProcVersionSignature: Ubuntu 3.13.0-70.113-generic 3.13.11-ckt29
  Uname: Linux 3.13.0-70-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lightdm2554 F pulseaudio
jadelino   3060 F pulseaudio
   /dev/snd/controlC0:  lightdm2554 F pulseaudio
jadelino   3060 F pulseaudio
  Date: Fri Dec 11 08:10:32 2015
  DuplicateSignature: 
package:linux-image-3.13.0-70-generic:3.13.0-70.113:subprocess installed 
post-installation script returned error exit status 17
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 17
  InstallationDate: Installed on 2014-08-20 (477 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-70-generic root=/dev/sda5 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.02~beta2-9ubuntu1.4
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-3.13.0-70-generic 3.13.0-70.113 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 17
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 07/18/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-M LX
  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.:bvr0402:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H61-MLX:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525152/+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 1523624] Re: wireless scanner function depends on kernel-version

[rincewind]

** Description changed:

  I am using Ubuntu Ubuntu 14.04.3 LTS
  
  I run into problems, when I try to operate (the printer or) the scanner
  of my Canon Pixma MG3250 via wireless connection using the driver
  scangearmp.
  
  This malfunction correlates with the kernel-version I'm using.
  
  Until kernel 3.13.0-65 everything was OK.
  
  3.13.0-66 didn't work, the scanner was not found.
  
- 3.13.0-67 did work again 
+ 3.13.0-67 did work again
  3.13.0-68 did still work
  
  3.13.0-70 didn't work anymore, the scanner could not be found
  3.13.0-71 same as above
-  
+ 
+ (Ubuntu 15.10 with kernel 4.2.0-19 works fine !!!) < update
+ 11.12.2015
+ 
  Reinstallation of driver package didn't change anything.
- --- 
+ ---
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  jens   2491 F pulseaudio
-  /dev/snd/pcmC0D0p:   jens   2491 F...m pulseaudio
-  /dev/snd/seq:timidity   1591 F timidity
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  jens   2491 F pulseaudio
+  /dev/snd/pcmC0D0p:   jens   2491 F...m pulseaudio
+  /dev/snd/seq:timidity   1591 F timidity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=d4da7400-8b56-48da-956a-f5ed44201045
  InstallationDate: Installed on 2014-04-18 (598 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 434299G
  Package: linux (not installed)
  ProcEnviron:
-  LANGUAGE=de_DE
-  TERM=xterm
-  PATH=(custom, no user)
-  LANG=de_DE.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=de_DE
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=de_DE.UTF-8
+  SHELL=/bin/bash
  ProcFB:
-  0 inteldrmfb
-  1 nouveaufb
+  0 inteldrmfb
+  1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=38a9f02e-508a-40b0-893c-ba067344cd2e ro noplymouth resume=/dev/sda2
  ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
  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.
+  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.13.0-71-generic N/A
-  linux-backports-modules-3.13.0-71-generic  N/A
-  linux-firmware 1.127.19
+  linux-restricted-modules-3.13.0-71-generic N/A
+  linux-backports-modules-3.13.0-71-generic  N/A
+  linux-firmware 1.127.19
  Tags:  trusty
  Uname: Linux 3.13.0-71-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: fuse
  _MarkForUpload: True
  dmi.bios.date: 07/19/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 39CN15WW
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: MoutCook
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr39CN15WW:bd07/19/2010:svnLENOVO:pn434299G:pvrLenovoV560:rvnLENOVO:rnMoutCook:rvrNotApplicable:cvnLENOVO:ct10:cvrN/A:
  dmi.product.name: 434299G
  dmi.product.version: Lenovo V560
  dmi.sys.vendor: LENOVO

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

Title:
  wireless scanner function depends on kernel-version

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using Ubuntu Ubuntu 14.04.3 LTS

  I run into problems, when I try to operate (the printer or) the
  scanner of my Canon Pixma MG3250 via wireless connection using the
  driver scangearmp.

  This malfunction correlates with the kernel-version I'm using.

  Until kernel 3.13.0-65 everything was OK.

  3.13.0-66 didn't work, the scanner was not found.

  3.13.0-67 did work again
  3.13.0-68 did still work

  3.13.0-70 didn't work anymore, the scanner could not be found
  3.13.0-71 same as above

  (Ubuntu 15.10 with kernel 4.2.0-19 works fine !!!) < update
  11.12.2015

  Reinstallation of driver package didn't change anything.
  ---
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jens   2491 F pulseaudio
   /dev/snd/pcmC0D0p:   jens   2491 F...m pulseaudio
   /dev/snd/seq:timidity   1591 F timidity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=d4da7400-8b56-48da-956a-f5ed44201045
  InstallationDate: Installed on 2014-04-18 (598 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 434299G
  Package: linux (not installed)
  ProcEnviron:
   

[Kernel-packages] [Bug 1494242] Re: Try to auto connect devices when user enables bluetooth

[Victor gonzalez]

Hi all,

I reproduced this bug, find below all the info:

Product: bq Aquaris E4.5 
FW version: RC 201 ( Bluez5)
HW version:  MP

Bug's timeline:

9.37 Android device "c" paired and checkbox for Auto connect
when detected marked.

9.38 With the Android device(c) we select Aquaris E4.5 and both
appears as connected and synced.

9.40  Aquaris E4.5 bluetooth is turned off and then turned on to see if it 
connects automatically with the Android device paired before.
 
9.40 --> 10.20 Android device (c) still appears as disconnected. 
Automatic connection seems to be not working.

Additional Info: Logs attached were gathered following the steps in
https://wiki.ubuntu.com/DebuggingBluetooth

** Attachment added: "log_BT_autoconnect.zip"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1494242/+attachment/4533056/+files/log_BT_autoconnect.zip

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

Title:
  Try to auto connect devices when user enables bluetooth

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  New

Bug description:
  When bluetooth gets enabled by the user we should try to connect all
  devices we're currently paired with and which are marked as trusted.
  This will help to improve the user experience that the user will get
  his configured devices connected right away.

  Android does this similar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1494242/+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 1515152] Re: virtualbox-dkms 5.0.4-dfsg-2: virtualbox kernel module failed to build

[Alberto Salvia Novella]

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

Title:
  virtualbox-dkms 5.0.4-dfsg-2: virtualbox kernel module failed to build

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Soon after the installation is completed the problem occurred.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: virtualbox-dkms 5.0.4-dfsg-2
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  DKMSKernelVersion: 4.2.0-18-generic
  Date: Wed Nov 11 05:51:41 2015
  InstallationDate: Installed on 2015-11-11 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  PackageVersion: 5.0.4-dfsg-2
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5
   apt  1.0.10.2ubuntu1
  SourcePackage: virtualbox
  Title: virtualbox-dkms 5.0.4-dfsg-2: virtualbox 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/linux/+bug/1515152/+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 1512468] Re: Bluetooth pin rejected for Microsoft Bluetooth Mobile Keyboard 5000

[Alberto Salvia Novella]

The keyboard doesn't want you to use Linux, hahaha!

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

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

Title:
  Bluetooth pin rejected for Microsoft Bluetooth Mobile Keyboard 5000

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  When attempting to connect with the Microsoft Bluetooth Mobile
  Keyboard 5000 keyboard a pin should be generated but it isn't, and the
  bluetooth pairing fails.

  /var/log/syslog shows:
    Agent replied with an error: org.bluez.Error.Rejected, Rejected bluetoothd 
generated PIN code

  This is on Xenial Xerus.  The last know Ubuntu release this worked on
  was Vivid.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.35-0ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov  2 14:48:35 2015
  InstallationDate: Installed on 2015-09-27 (36 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20AQCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=f0277d29-ea7b-4e0c-8327-9f48359b16ce ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to xenial on 2015-11-02 (0 days ago)
  dmi.bios.date: 05/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET77WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98420 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET77WW(2.27):bd05/20/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98420STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AQCTO1WW
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: 5C:51:4F:E7:6F:3E  ACL MTU: 1021:5  SCO MTU: 96:5
    UP RUNNING PSCAN
    RX bytes:2539 acl:0 sco:0 events:223 errors:0
    TX bytes:27011 acl:0 sco:0 commands:187 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1512468/+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 1523133] Re: strongswan vpn does not work

[volker kempter]

ad #2:
the problem appears still not to be fixed with kernel 4.3.0-3.12 (dec 10): 
strongswan vpn does not work (same behavior as described in #1).

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

Title:
  strongswan vpn does not work

Status in linux package in Ubuntu:
  Fix Committed
Status in strongswan package in Ubuntu:
  Invalid

Bug description:
  strongswan vpn does not work with any of the published kernels 4.3
  (including 4.3.0-2):

  I have already reported this problem some days ago to strongswan.org under 
ticket #1189:
  "I'm using strongswan 5.1.2-0ubuntu8 in lubuntu-16.04 (development) with 
kernel 4.3.

  Setting up VPN with the NetworkManager, I get no error, BUT VPN does
  not work; establishing VPN manually with: sudo ipsec restart, sudo
  ipsec up ..., I get the following in the console:

  received netlink error: invalid argument (22).
  Unable to install source route for 139.174.7..

  But finally it says: "connection "" established correctly" (as
  when using the NetworkManager VPN connection does not work
  however!!)."

  No such problem occur when using the kernel 4.2.0-19 (also 4.2.0-21)
  instead: VPN works okay.

  The same behaviour is found for lubuntu-15.10 with all kernels 4.3
  where a older version of strongswan is still installed.

  I was told by strongswan.org that this is a kernel bug (a patch
  appears to exist; see the discussion at #1189).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: strongswan 5.1.2-0ubuntu6.2
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic i686
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sat Dec  5 17:22:51 2015
  InstallationDate: Installed on 2014-02-12 (660 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release i386 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: strongswan
  UpgradeStatus: Upgraded to wily on 2015-10-09 (57 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523133/+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 1522080] Re: *ERROR* mismatch in ips_enabled

[Alberto Salvia Novella]

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

Title:
  *ERROR* mismatch in ips_enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  no problems except I'm seeing a lot of traces in dmesg, about 40 times
  on boot, on Hewlett-Packard HP Pro x2 612 G1 Tablet, with or without
  docking station

  
  [   22.076275] [ cut here ]
  [   22.076300] WARNING: CPU: 2 PID: 203 at 
/build/linux-26_gwp/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12328 
check_crtc_state+0x2c5/0x440 [i915]()
  [   22.076300] pipe state doesn't match!
  [   22.076323] Modules linked in: wacom_w8001 serport binfmt_misc bnep 
hid_sensor_gyro_3d hid_sensor_magn_3d hid_sensor_accel_3d hid_sensor_rotation 
hid_sensor_incl_3d hid_sensor_trigger industrialio_triggered_buffer 
hid_sensor_iio_common hid_sensor_custom arc4 hid_sensor_hub nls_iso8859_1 
intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp hp_wmi 
kvm_intel sparse_keymap kvm crct10dif_pclmul crc32_pclmul snd_hda_codec_realtek 
aesni_intel snd_hda_codec_generic snd_hda_codec_hdmi aes_x86_64 iwlmvm lrw 
gf128mul snd_hda_intel mac80211 glue_helper ablk_helper snd_hda_codec cryptd 
snd_hda_core joydev snd_hwdep serio_raw iwlwifi snd_pcm cfg80211 rtsx_pci_ms 
snd_seq_midi memstick snd_seq_midi_event uvcvideo snd_rawmidi lpc_ich 
videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev
  [   22.076343]  btusb btrtl media btbcm snd_seq btintel input_leds bluetooth 
snd_seq_device snd_timer hid_multitouch snd mei_me mei soundcore shpchp 
acpi_als 8250_dw dw_dmac kfifo_buf hp_accel 8250_fintek dw_dmac_core 
industrialio lis3lv02d soc_button_array i2c_designware_platform input_polldev 
mac_hid i2c_designware_core spi_pxa2xx_platform tpm_infineon intel_smartconnect 
hp_wireless parport_pc ppdev lp parport autofs4 hid_generic usbhid 
rtsx_pci_sdmmc i915 psmouse i2c_algo_bit drm_kms_helper ahci e1000e drm libahci 
rtsx_pci ptp pps_core wmi i2c_hid sdhci_acpi hid video sdhci
  [   22.076346] CPU: 2 PID: 203 Comm: plymouthd Tainted: GW   
4.2.0-19-generic #23-Ubuntu
  [   22.076346] Hardware name: Hewlett-Packard HP Pro x2 612 G1 Tablet/221B, 
BIOS M83 Ver. 01.03 11/06/2014
  [   22.076349]   7294313e 880035af34a8 
817e93f9
  [   22.076350]   880035af3500 880035af34e8 
8107b3d6
  [   22.076351]  880035af3528 880035af3590 880240d54800 
0001
  [   22.076351] Call Trace:
  [   22.076356]  [] dump_stack+0x45/0x57
  [   22.076359]  [] warn_slowpath_common+0x86/0xc0
  [   22.076361]  [] warn_slowpath_fmt+0x55/0x70
  [   22.076373]  [] ? intel_pipe_config_compare+0xb31/0xc60 
[i915]
  [   22.076383]  [] check_crtc_state+0x2c5/0x440 [i915]
  [   22.076397]  [] intel_modeset_check_state+0x21d/0x6d0 
[i915]
  [   22.076408]  [] intel_crtc_set_config+0x4c7/0x580 [i915]
  [   22.076420]  [] drm_mode_set_config_internal+0x66/0x100 
[drm]
  [   22.076425]  [] restore_fbdev_mode+0xc2/0xf0 
[drm_kms_helper]
  [   22.076429]  [] 
drm_fb_helper_restore_fbdev_mode_unlocked+0x29/0x70 [drm_kms_helper]
  [   22.076432]  [] drm_fb_helper_set_par+0x22/0x40 
[drm_kms_helper]
  [   22.076444]  [] intel_fbdev_set_par+0x1a/0x60 [i915]
  [   22.076446]  [] fb_set_var+0x236/0x460
  [   22.076448]  [] ? __enqueue_entity+0x6c/0x70
  [   22.076450]  [] ? enqueue_entity+0x421/0xc30
  [   22.076451]  [] ? enqueue_task_fair+0x332/0x770
  [   22.076454]  [] ? native_smp_send_reschedule+0x4d/0x70
  [   22.076456]  [] fbcon_blank+0x312/0x360
  [   22.076458]  [] ? pollwake+0x73/0x90
  [   22.076461]  [] do_unblank_screen+0xd3/0x1a0
  [   22.076463]  [] vt_ioctl+0x50a/0x12f0
  [   22.076469]  [] ? drm_dropmaster_ioctl+0x77/0x90 [drm]
  [   22.076472]  [] tty_ioctl+0x3cc/0xbc0
  [   22.076475]  [] ? 
schedule_hrtimeout_range_clock.part.24+0xac/0x160
  [   22.076477]  [] ? 
schedule_hrtimeout_range_clock+0x19/0x40
  [   22.076478]  [] do_vfs_ioctl+0x295/0x480
  [   22.076481]  [] ? wake_up_q+0x70/0x70
  [   22.076482]  [] SyS_ioctl+0x79/0x90
  [   22.076485]  [] entry_SYSCALL_64_fastpath+0x16/0x75
  [   22.076486] ---[ end trace a105930a63a59b48 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  apt12  2016 F pulseaudio
   /dev/snd/controlC0:  apt12  2016 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Dec  2 15:59:04 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-25 (280 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  

[Kernel-packages] [Bug 1525152] [NEW] package linux-image-3.13.0-70-generic 3.13.0-70.113 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17

[José Silva Adelino]

Public bug reported:

o sistema está travando, ficando inacesível. Precisa reiniciar o
computador.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-70-generic 3.13.0-70.113
ProcVersionSignature: Ubuntu 3.13.0-70.113-generic 3.13.11-ckt29
Uname: Linux 3.13.0-70-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  lightdm2554 F pulseaudio
  jadelino   3060 F pulseaudio
 /dev/snd/controlC0:  lightdm2554 F pulseaudio
  jadelino   3060 F pulseaudio
Date: Fri Dec 11 08:10:32 2015
DuplicateSignature: 
package:linux-image-3.13.0-70-generic:3.13.0-70.113:subprocess installed 
post-installation script returned error exit status 17
ErrorMessage: subprocess installed post-installation script returned error exit 
status 17
InstallationDate: Installed on 2014-08-20 (477 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
IwConfig:
 eth0  no wireless extensions.
 
 eth1  no wireless extensions.
 
 lono wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-70-generic root=/dev/sda5 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.02~beta2-9ubuntu1.4
RfKill:
 
SourcePackage: linux
Title: package linux-image-3.13.0-70-generic 3.13.0-70.113 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 17
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:
 
dmi.bios.date: 07/18/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0402
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H61-M LX
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.:bvr0402:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H61-MLX:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-package need-duplicate-check trusty

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

Title:
  package linux-image-3.13.0-70-generic 3.13.0-70.113 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 17

Status in linux package in Ubuntu:
  New

Bug description:
  o sistema está travando, ficando inacesível. Precisa reiniciar o
  computador.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-70-generic 3.13.0-70.113
  ProcVersionSignature: Ubuntu 3.13.0-70.113-generic 3.13.11-ckt29
  Uname: Linux 3.13.0-70-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lightdm2554 F pulseaudio
jadelino   3060 F pulseaudio
   /dev/snd/controlC0:  lightdm2554 F pulseaudio
jadelino   3060 F pulseaudio
  Date: Fri Dec 11 08:10:32 2015
  DuplicateSignature: 
package:linux-image-3.13.0-70-generic:3.13.0-70.113:subprocess installed 
post-installation script returned error exit status 17
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 17
  InstallationDate: Installed on 2014-08-20 (477 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-70-generic root=/dev/sda5 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.02~beta2-9ubuntu1.4
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-3.13.0-70-generic 3.13.0-70.113 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 17
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 07/18/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0402
  dmi.board.asset.tag: To be filled by 

[Kernel-packages] [Bug 1510962] Re: Module ioremap seems to crash at booting time.

[Alberto Salvia Novella]

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

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

Title:
  Module ioremap seems to crash at booting time.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is  buntu 15.10, on a Lenovo x250.

  journalctl -b output:

  Oct 27 23:04:07 sai kernel: [ cut here ]
  Oct 27 23:04:07 sai kernel: WARNING: CPU: 1 PID: 1 at 
/build/linux-AxjFAn/linux-4.2.0/arch/x86/mm/ioremap.c:198 
__ioremap_caller+0x2c5/0x380()
  Oct 27 23:04:07 sai kernel: Info: mapping multiple BARs. Your kernel is fine.
  Oct 27 23:04:07 sai kernel: Modules linked in:
  Oct 27 23:04:07 sai kernel: 
  Oct 27 23:04:07 sai kernel: CPU: 1 PID: 1 Comm: swapper/0 Not tainted 
4.2.0-16-generic #19-Ubuntu
  Oct 27 23:04:07 sai kernel: Hardware name: LENOVO 20CMCTO1WW/20CMCTO1WW, BIOS 
N10ET36W (1.15 ) 06/19/2015
  Oct 27 23:04:07 sai kernel:   720220ad 
880224587ab8 817e8c09
  Oct 27 23:04:07 sai kernel:   880224587b10 
880224587af8 8107b3c6
  Oct 27 23:04:07 sai kernel:  880224587b28 fed1 
c9e88000 6000
  Oct 27 23:04:07 sai kernel: Call Trace:
  Oct 27 23:04:07 sai kernel:  [] dump_stack+0x45/0x57
  Oct 27 23:04:07 sai kernel:  [] 
warn_slowpath_common+0x86/0xc0
  Oct 27 23:04:07 sai kernel:  [] warn_slowpath_fmt+0x55/0x70
  Oct 27 23:04:07 sai kernel:  [] __ioremap_caller+0x2c5/0x380
  Oct 27 23:04:07 sai kernel:  [] ioremap_nocache+0x17/0x20
  Oct 27 23:04:07 sai kernel:  [] 
snb_uncore_imc_init_box+0x79/0xb0
  Oct 27 23:04:07 sai kernel:  [] uncore_pci_probe+0xd6/0x1c0
  Oct 27 23:04:07 sai kernel:  [] local_pci_probe+0x45/0xa0
  Oct 27 23:04:07 sai kernel:  [] ? 
pci_match_device+0xf4/0x120
  Oct 27 23:04:07 sai kernel:  [] pci_device_probe+0xf3/0x140
  Oct 27 23:04:07 sai kernel:  [] 
driver_probe_device+0x21a/0x490
  Oct 27 23:04:07 sai kernel:  [] __driver_attach+0x90/0xa0
  Oct 27 23:04:07 sai kernel:  [] ? 
driver_probe_device+0x490/0x490
  Oct 27 23:04:07 sai kernel:  [] bus_for_each_dev+0x6c/0xc0
  Oct 27 23:04:07 sai kernel:  [] driver_attach+0x1e/0x20
  Oct 27 23:04:07 sai kernel:  [] bus_add_driver+0x1eb/0x280
  Oct 27 23:04:07 sai kernel:  [] ? uncore_cpu_setup+0x12/0x12
  Oct 27 23:04:07 sai kernel:  [] driver_register+0x60/0xe0
  Oct 27 23:04:07 sai kernel:  [] 
__pci_register_driver+0x4c/0x50
  Oct 27 23:04:07 sai kernel:  [] intel_uncore_init+0xe3/0x2d8
  Oct 27 23:04:07 sai kernel:  [] ? uncore_cpu_setup+0x12/0x12
  Oct 27 23:04:07 sai kernel:  [] do_one_initcall+0xb3/0x200
  Oct 27 23:04:07 sai kernel:  [] ? parse_args+0x154/0x4a0
  Oct 27 23:04:07 sai kernel:  [] 
kernel_init_freeable+0x17b/0x21a
  Oct 27 23:04:07 sai kernel:  [] ? rest_init+0x80/0x80
  Oct 27 23:04:07 sai kernel:  [] kernel_init+0xe/0xe0
  Oct 27 23:04:07 sai kernel:  [] ret_from_fork+0x3f/0x70
  Oct 27 23:04:07 sai kernel:  [] ? rest_init+0x80/0x80
  Oct 27 23:04:07 sai kernel: ---[ end trace 1d7db9c9abf685a2 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gpoo   2278 F pulseaudio
   /dev/snd/controlC0:  gpoo   2278 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Oct 28 07:28:32 2015
  InstallationDate: Installed on 2015-04-07 (203 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  MachineType: LENOVO 20CMCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=6d7b32fc-b6c2-4bd8-8a58-fe1941d338b1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-22 (5 days ago)
  dmi.bios.date: 06/19/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET36W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CMCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET36W(1.15):bd06/19/2015:svnLENOVO:pn20CMCTO1WW:pvrThinkPadX250:rvnLENOVO:rn20CMCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CMCTO1WW
  dmi.product.version: ThinkPad X250
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1516215] Re: kernel 4.x has issues with lite-on sata controller in dell xps 13 (2015)

[Christopher M. Penalver]

Carolin Latze, that's going to be a different problem, not scoped under this 
report. Hence, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to 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/1516215

Title:
   kernel 4.x has issues with lite-on sata controller in dell xps 13
  (2015)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I have a Dell XPS 13 (2015) which has a Lite-On Sata controller:
  03:00.0 SATA controller: Lite-On Technology Corporation Device 0224 (rev 10)

  Right from the beginning, I have issues with that one under Linux (not
  Windows). It might happen that the notebook just dies (loosing its
  SSD), or it might not even boot. Whenever it does not boot, it usually
  stops with a message around "job 1 of 12 ..." (I don't find them in
  any logs ). Sometimes when I boot into Windows and then immediately
  reboot into Linux it works. It usually helps to boot a 3.19.x kernel,
  although even that one can have the same issues (although way less
  than 4.x).

  The system almost always crashes completely when I run the dump tool.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  latze  1599 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Nov 14 09:29:04 2015
  HibernationDevice: RESUME=UUID=b8662265-a1f0-487e-9d85-2731c765b3eb
  InstallationDate: Installed on 2015-08-23 (82 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:5682 Realtek Semiconductor Corp.
   Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp.
   Bus 001 Device 002: ID 8087:0a2a Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed 
root=UUID=9e67912b-c59e-47ac-b2f1-3ef39e3d38fb ro debug
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.1
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-31 (13 days ago)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516215/+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 1522793] Re: [Dell Inspiron 5547] Touchpad not working

[Christopher M. Penalver]

Marcin, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522793/comments/6
regarding this being fixed with an update. 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: 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/1522793

Title:
  [Dell Inspiron 5547] Touchpad not working

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Touchpad not working on Dell Inspiron 5547.

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=10   [slave  pointer 
 (2)]
  ⎜   ↳ DLL063E:00 06CB:2934id=12   [slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=14   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_HDid=11   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=15   [slave  
keyboard (3)]

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  marcin 3077 F pulseaudio
   /dev/snd/controlC0:  marcin 3077 F pulseaudio
  CasperVersion: 1.365
  CurrentDesktop: Unity
  Date: Fri Dec  4 10:59:53 2015
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. Inspiron 5547
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/NFS/15.10/desktop-amd64/casper/vmlinuz.efi 
append noprompt boot=casper modprobe.blacklist=wl rfkill.master_switch_mode=0 
rfkill.default_state=1 nohibernate userfullname=User Name username=username 
proceed=AIO nfsroot=usb showmounts persistent-path=/NFS/15.10/desktop-amd64 
persistent iso-scan/filename=/NFS/15.10/hostname-15.10-desktop-amd64.iso toram
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0CXY41
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A04
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd05/09/2014:svnDellInc.:pnInspiron5547:pvrA04:rvnDellInc.:rn0CXY41:rvrA00:cvnDellInc.:ct8:cvrA04:
  dmi.product.name: Inspiron 5547
  dmi.product.version: A04
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522793/+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 1524215] Re: Lenovo B50-70 inverted internal microphone

[Alberto Salvia Novella]

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

Title:
  Lenovo B50-70 inverted internal microphone

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978 
  Attached the alsa-info txt to this bug
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marian 1981 F pulseaudio
   /dev/snd/pcmC1D0c:   marian 1981 F...m pulseaudio
   /dev/snd/pcmC1D0p:   marian 1981 F...m pulseaudio
   /dev/snd/controlC1:  marian 1981 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=10570c82-8e52-4379-9a8e-2e30baae9f63
  InstallationDate: Installed on 2015-09-10 (90 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20384
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic 
root=UUID=1791e4c1-12de-4fef-88b1-31716c981648 ro quiet splash
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: Upgraded to wily on 2015-10-24 (45 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/21/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9DCN34WW(V3.04)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo B50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo B50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9DCN34WW(V3.04):bd07/21/2015:svnLENOVO:pn20384:pvrLenovoB50-70:rvnLENOVO:rnLenovoB50-70:rvrNODPK:cvnLENOVO:ct10:cvrLenovoB50-70:
  dmi.product.name: 20384
  dmi.product.version: Lenovo B50-70
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1524215/+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 1264311] Re: BCM43142 bluetooth adapter not finding any bluetooth devices

[Michael]

I should add, that I needed

fw-105b_e065.hcd in /lib/firmware/
and BCM.hcd in /lib/firmware/brcm/

in order for it to work. In case either of those copies was not present,
bluetooth would not work.

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

Title:
  BCM43142 bluetooth adapter not finding any bluetooth devices

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On my officially Ubuntu-certified Lenovo B590 laptop the BCM43142
  bluetooth adapter is not working. I have two further bluetooth devices
  placed closely to the laptop, non-paired and each being able to
  discover the other respectively. None of them is able to discover the
  laptop, nor does 'hcitool scan' on the laptop find any devices. It
  does not give any errors though.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluez 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Thu Dec 26 15:34:08 2013
  InstallationDate: Installed on 2013-12-25 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: LENOVO 37613EG
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic 
root=UUID=c379c17a-9869-47a8-b9b3-83be4e302040 ro acpi_backlight=vendor quiet 
splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H9ET74WW(1.11)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 37613EG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH9ET74WW(1.11):bd06/26/2013:svnLENOVO:pn37613EG:pvrLenovoB590:rvnLENOVO:rn37613EG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 37613EG
  dmi.product.version: Lenovo B590
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 1C:3E:84:E8:81:98  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1244 acl:0 sco:0 events:81 errors:0
TX bytes:2820 acl:0 sco:0 commands:77 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1264311/+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 1505241] Re: Phone does not suspend

[Pat McGowan]

I think I long ago added a bug on that, when plugged in to a charger we
should certainly suspend, its not an active USB data connection so we
should not hold the wakelock in that case.

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

Title:
  Phone does not suspend

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  I am seeing both the MX4 on proposed and the E4.5 on stable exhibit similar 
behavior
  According to the logs they are not able to suspend due to active wakeup 
sources.
  (I am running a BT test kernel on the MX4 3.10.35+)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505241/+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 1525228] Re: Qualcomm Atheros QCA61x4 cannot connect to encrypted 5Ghz networks

[Roman]

** Description changed:

  The device works fine with Ubuntu 15.10 mainline kernel 4.2.0 and the
  firmware provided in linux-firmware on 2,4 Ghz wifi networks or
  unencrypted 5GHz networks.
  
  But when i connect to a encrypted 5Ghz network.  The firmware provide in 
linux-firmware (WLAN.RM.1.1-00141) crashed like i think is described here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516384
  
  So i installed the latest firmware release SW_RM.1.1.1-00157-QCARMSWPZ-1
  from ath10k-firmware (https://github.com/kvalo/ath10k-firmware/)
  
  In this version the firmware doesn't crash but goes into a loop. Like
  you see in dmesg, the device associates with the AP, but from an unknown
  reason it cannot connect.
  
  At the moment i cannot provide you any details about the AP im testing
  with, because im using my universities network, but if you really need
  them i can test the device with an known AP in a week or so.
  
+ I reported the bug to the ath10k mailing list, but i think the topic got lost:
+ http://lists.infradead.org/pipermail/ath10k/2015-November/006478.html
  
- PS: I tested the problem with all mainline and upstream kernels(4.2.6, 
4.3.0,4.4rc4) without any difference.
+ PS: I tested the problem with all mainline and upstream kernels(4.2.6,
+ 4.3.0,4.4rc4) without any difference.
  
  -
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-21-generic 4.2.0-21.25
  ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6
  Uname: Linux 4.2.0-21-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  roman  2043 F pulseaudio
   /dev/snd/controlC1:  roman  2043 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Dec 11 14:01:58 2015
  HibernationDevice: RESUME=UUID=38f2bb72-0ff3-498e-ab17-249df8b33aef
  InstallationDate: Installed on 2015-10-23 (49 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Aspire VN7-571G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic.efi.signed 
root=UUID=da03328e-3129-4dfc-98d7-b8b06fa3d5f1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-21-generic N/A
   linux-backports-modules-4.2.0-21-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-571G
  dmi.board.vendor: Acer
  dmi.board.version: V1.14
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.14
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.14:bd01/08/2015:svnAcer:pnAspireVN7-571G:pvrV1.14:rvnAcer:rnAspireVN7-571G:rvrV1.14:cvnAcer:ct10:cvrV1.14:
  dmi.product.name: Aspire VN7-571G
  dmi.product.version: V1.14
  dmi.sys.vendor: Acer

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

Title:
  Qualcomm Atheros QCA61x4 cannot connect to encrypted 5Ghz networks

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The device works fine with Ubuntu 15.10 mainline kernel 4.2.0 and the
  firmware provided in linux-firmware on 2,4 Ghz wifi networks or
  unencrypted 5GHz networks.

  But when i connect to a encrypted 5Ghz network.  The firmware provide in 
linux-firmware (WLAN.RM.1.1-00141) crashed like i think is described here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516384

  So i installed the latest firmware release
  SW_RM.1.1.1-00157-QCARMSWPZ-1 from ath10k-firmware
  (https://github.com/kvalo/ath10k-firmware/)

  In this version the firmware doesn't crash but goes into a loop. Like
  you see in dmesg, the device associates with the AP, but from an
  unknown reason it cannot connect.

  At the moment i cannot provide you any details about the AP im testing
  with, because im using my universities network, but if you really need
  them i can test the device with an known AP in a week or so.

  I reported the bug to the ath10k mailing list, but i think the topic got lost:
  http://lists.infradead.org/pipermail/ath10k/2015-November/006478.html

  PS: I tested the problem with all mainline and upstream kernels(4.2.6,
  4.3.0,4.4rc4) without any difference.

  -

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-21-generic 4.2.0-21.25
  ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6
  Uname: Linux 4.2.0-21-generic x86_64
  

[Kernel-packages] [Bug 1513648] Re: [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0)

[Christopher M. Penalver]

** This bug is no longer a duplicate of bug 1511101
   [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled 
(expected 1, found 0) appears repeatedly during boot; Ubuntu boots normally to 
GNOME3 afterwards

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

Title:
  [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled
  (expected 1, found 0)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  A few seconds after boot I get this message in the log (and wifi does
  not activate).

  Many things still work, but the system acts a bit confused. Sometimes
  it gets almost unsusable until reboot (and then there are more of
  those "cut here" sections in the log).

  Kind regards,
Patrik


  [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled 
(expected 1, found 0)
   [ cut here ]
  [6.549187] WARNING: CPU: 2 PID: 1048 at 
/build/linux-AxjFAn/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12326 
check_crtc_state+0x2c5/0x440 [i915]()
  [6.549188] pipe state doesn't match!
  [6.549189] Modules linked in: iptable_filter ip_tables x_tables pci_stub 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc bnep 
pn544_mei mei_phy pn544 hci nfc arc4 dell_wmi joydev btusb btrtl btbcm 
sparse_keymap btintel bluetooth dell_laptop dcdbas dell_smm_hwmon uvcvideo 
videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media 
intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm snd_soc_rt5640 iwlmvm snd_soc_rl6231 mac80211 snd_soc_core snd_compress 
snd_hda_codec_hdmi crct10dif_pclmul ac97_bus crc32_pclmul snd_pcm_dmaengine 
ghash_clmulni_intel snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep aesni_intel aes_x86_64 lrw gf128mul 
glue_helper ablk_helper cryptd iwlwifi snd_pcm input_leds serio_raw
  [6.549234]  cfg80211 lpc_ich snd_seq_midi snd_seq_midi_event shpchp 
mei_me mei snd_rawmidi snd_seq snd_seq_device snd_timer snd 8250_fintek 
soundcore dw_dmac dw_dmac_core dell_smo8800 snd_soc_sst_acpi 8250_dw dell_rbtn 
i2c_designware_platform i2c_designware_core spi_pxa2xx_platform mac_hid 
cdc_mbim qcserial cdc_wdm cdc_ncm usb_wwan usbnet mii usbserial parport_pc 
ppdev lp parport autofs4 uas usb_storage i915 i2c_algo_bit psmouse 
drm_kms_helper e1000e drm ahci libahci ptp sdhci_pci pps_core wmi sdhci_acpi 
video sdhci i2c_hid hid
  [6.549269] CPU: 2 PID: 1048 Comm: Xorg Tainted: GW  OE   
4.2.0-16-generic #19-Ubuntu
  [6.549270] Hardware name: Dell Inc. Latitude E7440/07F3F4, BIOS A09 
05/01/2014
  [6.549272]   2ecf7f35 880409e337c8 
817e8c09
  [6.549275]   880409e33820 880409e33808 
8107b3c6
  [6.549278]  880409e33848 880409e338b0 8804072d6800 
0001
  [6.549280] Call Trace:
  [6.549286]  [] dump_stack+0x45/0x57
  [6.549291]  [] warn_slowpath_common+0x86/0xc0
  [6.549293]  [] warn_slowpath_fmt+0x55/0x70
  [6.549308]  [] ? intel_pipe_config_compare+0xb31/0xc60 
[i915]
  [6.549320]  [] check_crtc_state+0x2c5/0x440 [i915]
  [6.549336]  [] intel_modeset_check_state+0x21d/0x6d0 
[i915]
  [6.549350]  [] intel_crtc_set_config+0x4c7/0x580 [i915]
  [6.549364]  [] ? drm_mode_create+0x25/0x60 [drm]
  [6.549374]  [] drm_mode_set_config_internal+0x66/0x100 
[drm]
  [6.549384]  [] drm_mode_setcrtc+0x3e9/0x500 [drm]
  [6.549392]  [] drm_ioctl+0x125/0x610 [drm]
  [6.549400]  [] ? drm_mode_setplane+0x1b0/0x1b0 [drm]
  [6.549404]  [] do_vfs_ioctl+0x295/0x480
  [6.549407]  [] ? __set_task_blocked+0x41/0xa0
  [6.549410]  [] SyS_ioctl+0x79/0x90
  [6.549413]  [] ? SyS_rt_sigprocmask+0x8e/0xc0
  [6.549416]  [] entry_SYSCALL_64_fastpath+0x16/0x75
  [6.549418] ---[ end trace 5a9f3f63db8e3888 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  patrikj1724 F pulseaudio
   /dev/snd/controlC1:  patrikj1724 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Nov  5 23:43:28 2015
  HibernationDevice: RESUME=UUID=2c948eae-cab3-47b5-a293-ceefec2af360
  InstallationDate: Installed on 2014-10-14 (387 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Latitude E7440
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=a8c1bdf4-4a10-4923-be0e-03d7148a6b88 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   

[Kernel-packages] [Bug 760142] Re: ImPS/2 ALPS GlidePoint configure as PS/2 mouse instead of proper touchpad

[Christopher M. Penalver]

Anonymous (reason), to advise, this isn't a hardware bug, but a software
driver one.

Despite this, it will help immensely if you file a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

** Summary changed:

- ImPS/2 ALPS GlidePoint configure as PS/2 mouse instead of proper touchpad
+ [Dell Inspiron N5110] ImPS/2 ALPS GlidePoint configure as PS/2 mouse

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

Title:
  [Dell Inspiron N5110] ImPS/2 ALPS GlidePoint configure as PS/2 mouse

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On the Dell 15R. the touchpad is not recognised as a touchpad, it is
  recognised as a mouse.

  $ cat /proc/bus/input/devices
  [snip]
  I: Bus=0011 Vendor=0002 Product=0005 Version=7326
  N: Name="ImPS/2 ALPS GlidePoint"
  P: Phys=isa0060/serio1/input0
  S: Sysfs=/devices/platform/i8042/serio1/input/input7
  U: Uniq=
  H: Handlers=mouse0 event7
  B: PROP=0
  B: EV=7
  B: KEY=7 0 0 0 0
  B: REL=103
  [snip]

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: linux-image-2.6.38-8-generic 2.6.38-8.42
  Regression: No
  Reproducible: Yes
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jude   1571 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf7f0 irq 54'
     Mixer name : 'Intel CougarPoint HDMI'
     Components : 'HDA:111d76d1,102804b0,00100205 
HDA:80862805,80860101,0010'
     Controls  : 18
     Simple ctrls  : 10
  CurrentDmesg:
   [   35.342430] eth0: no IPv6 routers present
   [   48.913433] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro,commit=0
  Date: Wed Apr 13 20:11:55 2011
  HibernationDevice: RESUME=UUID=9203eac6-4c4c-41c8-bf51-e18329de0e3f
  InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: Dell Inc. Inspiron N5110
  ProcEnviron:
   LANGUAGE=
   LANG=en_IE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic 
root=UUID=64711ccc-07ea-40e8-ac9d-c9e7c40ca1f7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-2.6.38-8-generic N/A
   linux-backports-modules-2.6.38-8-generic  N/A
   linux-firmware1.50
  SourcePackage: linux
  UpgradeStatus: Upgraded to natty on 2011-04-11 (1 days ago)
  dmi.bios.date: 03/02/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 034W60
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd03/02/2011:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn034W60:rvrA02:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N5110
  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/760142/+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 1514315] Re: [SKL-U] System hangs when switching video out to the next mode

[Christopher M. Penalver]

** Changed in: linux (Ubuntu Xenial)
   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/1514315

Title:
  [SKL-U] System hangs when switching video out to the next mode

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Vivid:
  Confirmed
Status in linux source package in Wily:
  Confirmed
Status in linux source package in Xenial:
  Incomplete

Bug description:
  After update to test kernel 3.19.0-32.37+bpo1, system will hang with 
blackscreen while switching to the next mode with HDMI video out.
  * The function works fine with -28 kernel.
  * SKL-H doesn't find this issue

  Test configs:
  Intel SKL-U graphics: Dell Inspiron 13-7359

  Kernel version: 3.19.0-32.37+bpo1
  --- 
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  2108 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  CurrentDesktop: Unity
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-kittyhawk2-trusty-amd64-20150907-1
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=61acef2b-8b38-40a2-a2a1-1f8346dbfa80
  InstallationDate: Installed on 2015-11-06 (2 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Failed to find casper uuid.conf in 
'binary/casper/initrd.img-3.19.0-28-generic.old-dkms' LIVE Binary 20150907-22:18
  MachineType: Dell Inc. Inspiron 13-7359
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=fc10fc31-8426-4eb5-8157-35d5d5c70335 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37+bpo1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.15
  Tags:  trusty
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd09/08/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514315/+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 1503731] Re: 8086:0f31 Ubuntu 15.04-15.10 freezes totally

[Christopher M. Penalver]

** Description changed:

- Behavior:
- 
  Ever since I first installed 15.04 back in April/May on my new DELL
- Inspiron 3646:
- 
- Handle 0x0001, DMI type 1, 27 bytes
- System Information
- Manufacturer: Dell Inc.
- Product Name: Inspiron 3646
- 
- I have experienced frequent(daily/every-other-day)complete
+ Inspiron 3646 I have experienced frequent(daily/every-other-day)complete
  lockups(cannot even switch to console(Alt-F1,F2,etc.).
  
  I have determined that the issue is related to the 'i915' driver in
- relation to my GPU:
+ relation to my GPU.
  
- 00:02.0 VGA compatible controller: Intel Corporation Atom Processor
- Z36xxx/Z37xxx Series Graphics & Display (rev 0e)
+ I'm currently using intel-linux-graphics-
+ installer_1.2.0-0intel1_amd64.deb from https://01.org/linuxgraphics with
+ similar results (maybe a little better than the stock i915 stack in
+ 15.04).
  
- on SoC:
- 
- Handle 0x0004, DMI type 4, 42 bytes
- Processor Information
- Socket Designation: CPU 1
- Type: Central Processor
- Family: Atom
- Manufacturer: Intel(R) Corporation
- Version: Intel(R) Pentium(R) CPU  J2900  @ 2.41GHz
- 
+ WORKAROUND: Use kernel boot parameter:
+ intel_idle.max_cstate=1
  
  I have gained _significant_ improvements in reliability / stability by
- using various flags / parameters in the i915 module:
+ using parameters in the i915 module:
  
  /etc/modprobe.d/i915.conf:
- 
  options i915 semaphores=1
  
  and / or
  
  /etc/default/grub:
- 
  GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_pstate=disable"
  
  and / or
- 
  /usr/share/X11/xorg.conf.d/20-intel.conf:
  
  Section "Device"
     Identifier "Intel Graphics"
     Driver "intel"
     Option "TearFree" "1"
  EndSection
  
  and / or
- 
  Disable "Intel Virtualization Technologies" in the BIOS.
- 
- chris@CKR-DKM:~$ lsb_release -rd
- Description:Ubuntu 15.04
- Release:15.04
- 
- chris@CKR-DKM:~$ apt-cache policy xorg
- xorg:
-   Installed: (none)
-   Candidate: 1:7.7+7ubuntu4
-   Version table:
-  1:7.7+7ubuntu4 0
- 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
- 
- 
- *
- 
- I'm currently using:  intel-linux-graphics-
- installer_1.2.0-0intel1_amd64.deb
- 
- from:  https://01.org/linuxgraphics
- 
- with similar results(maybe a little better than the stock i915 stack in
- 15.04).
- 
- 
- *
- 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CompositorRunning: None
  Date: Wed Oct  7 09:32:47 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:068d]
  InstallationDate: Installed on 2015-09-17 (19 days ago)
  InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:1005): WARNING **: [PIDs] Failed to execute command: 
upstart
  
   ** (lightdm-gtk-greeter:1005): WARNING **: Failed to load user image: Failed 
to open file '/home/chris/.face': No such file or directory
  MachineType: Dell Inc. Inspiron 3646
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic.efi.signed 
root=UUID=ef22be35-6f79-4356-be42-2689d1de0378 ro quiet
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0V6D8J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/17/2015:svnDellInc.:pnInspiron3646:pvr:rvnDellInc.:rn0V6D8J:rvrA00:cvnDellInc.:ct3:cvrA09:
  dmi.product.name: Inspiron 3646
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  

[Kernel-packages] [Bug 1525228] Status changed to Confirmed

[Brad Figg]

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

Title:
  Qualcomm Atheros QCA61x4 cannot connect to encrypted 5Ghz networks

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The device works fine with Ubuntu 15.10 mainline kernel 4.2.0 and the
  firmware provided in linux-firmware on 2,4 Ghz wifi networks or
  unencrypted 5GHz networks.

  But when i connect to a encrypted 5Ghz network.  The firmware provide in 
linux-firmware (WLAN.RM.1.1-00141) crashed like i think is described here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516384

  So i installed the latest firmware release
  SW_RM.1.1.1-00157-QCARMSWPZ-1 from ath10k-firmware
  (https://github.com/kvalo/ath10k-firmware/)

  In this version the firmware doesn't crash but goes into a loop. Like
  you see in dmesg, the device associates with the AP, but from an
  unknown reason it cannot connect.

  At the moment i cannot provide you any details about the AP im testing
  with, because im using my universities network, but if you really need
  them i can test the device with an known AP in a week or so.

  
  PS: I tested the problem with all mainline and upstream kernels(4.2.6, 
4.3.0,4.4rc4) without any difference.

  -

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-21-generic 4.2.0-21.25
  ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6
  Uname: Linux 4.2.0-21-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  roman  2043 F pulseaudio
   /dev/snd/controlC1:  roman  2043 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Dec 11 14:01:58 2015
  HibernationDevice: RESUME=UUID=38f2bb72-0ff3-498e-ab17-249df8b33aef
  InstallationDate: Installed on 2015-10-23 (49 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Aspire VN7-571G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic.efi.signed 
root=UUID=da03328e-3129-4dfc-98d7-b8b06fa3d5f1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-21-generic N/A
   linux-backports-modules-4.2.0-21-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-571G
  dmi.board.vendor: Acer
  dmi.board.version: V1.14
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.14
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.14:bd01/08/2015:svnAcer:pnAspireVN7-571G:pvrV1.14:rvnAcer:rnAspireVN7-571G:rvrV1.14:cvnAcer:ct10:cvrV1.14:
  dmi.product.name: Aspire VN7-571G
  dmi.product.version: V1.14
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525228/+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 1510612] Re: package linux-image-4.2.0-17-generic 4.2.0-17.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17

[Alberto Salvia Novella]

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

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

Title:
  package linux-image-4.2.0-17-generic 4.2.0-17.21 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 17

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  package linux-image-4.2.0-17-generic 4.2.0-17.21 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 17

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-17-generic 4.2.0-17.21
  ProcVersionSignature: Ubuntu 4.2.0-17.20-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   richter3412 F...m pulseaudio
   /dev/snd/controlC0:  root   2162 F fsodeviced
richter3412 F pulseaudio
  Date: Tue Oct 27 16:42:31 2015
  DuplicateSignature: 
package:linux-image-4.2.0-17-generic:4.2.0-17.21:subprocess installed 
post-installation script returned error exit status 17
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 17
  HibernationDevice: RESUME=UUID=bd202ae7-9602-46bb-88fb-ae03a8769732
  InstallationDate: Installed on 2015-09-14 (42 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20221
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-17-generic 
root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro 
rootflags=subvol=ubuntu-main-root
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  Title: package linux-image-4.2.0-17-generic 4.2.0-17.21 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 17
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-23 (4 days ago)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1510612/+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 1510038] Re: atheros ar8161 wired ethernet doesn't work

[Alberto Salvia Novella]

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

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

Title:
  atheros ar8161 wired ethernet doesn't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  having a new hard disk, I'have installed the last relaese of ubuntu 15.10.
  Previousmy, I was running a 15.04 version upgrade from 13.04 ubuntu through 
13.10 14.04  and 14.10.
  My nic was working, not now.
  Is there a solution to make it worked 
  I 've found this solution 
http://askubuntu.com/questions/165192/how-do-i-install-drivers-for-the-atheros-ar8161-ethernet-controller

  but I have this error :

  make
  make -C /lib/modules/4.2.0-16-generic/build 
M=/home/isanaud/compat-wireless-2012-07-03-pc modules
  make[1]: Entering directory '/usr/src/linux-headers-4.2.0-16-generic'
  /home/isanaud/compat-wireless-2012-07-03-pc/config.mk:21: *** "ERROR: 
compat-wireless by default supports kernels >= 2.6.24, try enabling only one 
driver though". Arrêt.
  Makefile:1398: recipe for target 
'_module_/home/isanaud/compat-wireless-2012-07-03-pc' failed
  make[1]: *** [_module_/home/isanaud/compat-wireless-2012-07-03-pc] Error 2
  make[1]: Leaving directory '/usr/src/linux-headers-4.2.0-16-generic'
  Makefile:86: recipe for target 'modules' failed
  make: *** [modules] Error 2
  --- 
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   arnaud 1689 F...m pulseaudio
   /dev/snd/controlC0:  arnaud 1689 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=82584e6a-7be7-4020-97cb-69af146c560f
  InstallationDate: Installed on 2015-10-22 (3 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: ASUSTeK COMPUTER INC. N56VZ
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed 
root=UUID=c0cf975f-8195-45cf-bc8f-21a708d8ea52 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  Tags:  wily
  UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
  Uname: Linux 4.2.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/15/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N56VZ.202
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N56VZ
  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.:bvrN56VZ.202:bd03/15/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N56VZ
  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/1510038/+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 1522949] Re: Bluetooth doesn't work on 0930:0225 Toshiba Corporation

[Alberto Salvia Novella]

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

Title:
  Bluetooth doesn't work on 0930:0225 Toshiba Corporation

Status in linux package in Ubuntu:
  In Progress

Bug description:
  I have not been able to get bluetooth running in Ubuntu 14.04, 14.10,
  or 15.10 on my Toshiba laptop. Bluetooth does work under Windows.
  There is no bluetooth icon. The bluetooth manager says "Bluetooth is
  disabled" whether I set it to On or Off.

  
  rfkill list:

  0: Toshiba Bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
  [...]

  The modified kernel is because I installed btusb-lp1506615-dkms from
  https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth . No
  change in behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19 [modified: 
boot/vmlinuz-4.2.0-16-generic]
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  josiah 1874 F pulseaudio
   /dev/snd/controlC1:  josiah 1874 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Dec  4 14:45:28 2015
  HibernationDevice: RESUME=UUID=0bcbd4ab-9f94-44d7-857f-717f4e7c9481
  InstallationDate: Installed on 2015-12-03 (1 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: TOSHIBA Satellite L75-B
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \boot\vmlinuz-4.2.0-16-generic.efi.signed 
root=UUID=edea9167-ead7-4da4-81ac-fa65520b3e91 ro quiet splash vt.handoff=7 
initrd=boot\initrd.img-4.2.0-16-generic
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/03/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.60
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  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:bvnInsydeCorp.:bvr1.60:bd11/03/2014:svnTOSHIBA:pnSatelliteL75-B:pvrPSKRLU-01400M:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L75-B
  dmi.product.version: PSKRLU-01400M
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522949/+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 1525270] [NEW] Wi-Di Realtek 8192E disconnects after a while and fails to reconnect

[Gilbert Dion]

Public bug reported:

A few minutes after booting my Samsung R580 laptop, the Wi-Fi
disconnects and it fails to reconnect until I restart the machine. This
happens with all the 64 bit versions of Ubuntu I tried, from 14.04 to
15.10. With the 32 bit versions, everything runs perfectly. No loss of
connection at all, even after 48 hours in a row.

Here is the output of iwconfig after loss of connexion:

eth7  no wireless extensions.

lono wireless extensions.

wlan6 802.11bgn  ESSID:"JeLisVosCourriels"  Nickname:"rtl8192E"
  Mode:Managed  Frequency=2.417 GHz  Access Point: Not-Associated   
  Bit Rate:19.5 Mb/s   
  Retry min limit:7   RTS thr:off   Fragment thr:off
  Power Management:off
  Link Quality=10/100  Signal level=0 dBm  Noise level=-100 dBm
  Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
  Tx excessive retries:0  Invalid misc:0   Missed beacon:0

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-19-generic 4.2.0-19.23
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  gilbert3115 F pulseaudio
 /dev/snd/controlC0:  gilbert3115 F pulseaudio
CurrentDesktop: Unity
Date: Fri Dec 11 09:27:18 2015
HibernationDevice: RESUME=UUID=e19f92d5-541f-412f-b5b0-7d97bfa1b7ec
InstallationDate: Installed on 2015-12-03 (7 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: SAMSUNG ELECTRONICS CO., LTD. R580
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic 
root=UUID=f6b1d099-6ed1-4e82-823a-352535c7596c ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-19-generic N/A
 linux-backports-modules-4.2.0-19-generic  N/A
 linux-firmware1.149.3
SourcePackage: linux
UpgradeStatus: Upgraded to wily on 2015-12-03 (7 days ago)
dmi.bios.date: 12/21/2009
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 04JB.M014.20091221.hkk
dmi.board.asset.tag: Tag 12345
dmi.board.name: R580
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
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:bvnPhoenixTechnologiesLtd.:bvr04JB.M014.20091221.hkk:bd12/21/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnR580:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR580:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: R580
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: amd64 apport-bug wily

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

Title:
  Wi-Di Realtek 8192E disconnects after a while and fails to reconnect

Status in linux package in Ubuntu:
  New

Bug description:
  A few minutes after booting my Samsung R580 laptop, the Wi-Fi
  disconnects and it fails to reconnect until I restart the machine.
  This happens with all the 64 bit versions of Ubuntu I tried, from
  14.04 to 15.10. With the 32 bit versions, everything runs perfectly.
  No loss of connection at all, even after 48 hours in a row.

  Here is the output of iwconfig after loss of connexion:

  eth7  no wireless extensions.

  lono wireless extensions.

  wlan6 802.11bgn  ESSID:"JeLisVosCourriels"  Nickname:"rtl8192E"
Mode:Managed  Frequency=2.417 GHz  Access Point: Not-Associated   
Bit Rate:19.5 Mb/s   
Retry min limit:7   RTS thr:off   Fragment thr:off
Power Management:off
Link Quality=10/100  Signal level=0 dBm  Noise level=-100 dBm
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:0  Invalid misc:0   Missed beacon:0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gilbert3115 F pulseaudio
   /dev/snd/controlC0:  gilbert3115 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Dec 11 09:27:18 2015
  HibernationDevice: RESUME=UUID=e19f92d5-541f-412f-b5b0-7d97bfa1b7ec
  InstallationDate: Installed on 2015-12-03 (7 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R580
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic 

[Kernel-packages] [Bug 1525228] Re: Qualcomm Atheros QCA61x4 cannot connect to encrypted 5Ghz networks

[Alberto Salvia Novella]

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

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

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

Title:
  Qualcomm Atheros QCA61x4 cannot connect to encrypted 5Ghz networks

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The device works fine with Ubuntu 15.10 mainline kernel 4.2.0 and the
  firmware provided in linux-firmware on 2,4 Ghz wifi networks or
  unencrypted 5GHz networks.

  But when i connect to a encrypted 5Ghz network.  The firmware provide in 
linux-firmware (WLAN.RM.1.1-00141) crashed like i think is described here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516384

  So i installed the latest firmware release
  SW_RM.1.1.1-00157-QCARMSWPZ-1 from ath10k-firmware
  (https://github.com/kvalo/ath10k-firmware/)

  In this version the firmware doesn't crash but goes into a loop. Like
  you see in dmesg, the device associates with the AP, but from an
  unknown reason it cannot connect.

  At the moment i cannot provide you any details about the AP im testing
  with, because im using my universities network, but if you really need
  them i can test the device with an known AP in a week or so.

  I reported the bug to the ath10k mailing list, but i think the topic got lost:
  http://lists.infradead.org/pipermail/ath10k/2015-November/006478.html

  PS: I tested the problem with all mainline and upstream kernels(4.2.6,
  4.3.0,4.4rc4) without any difference.

  -

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-21-generic 4.2.0-21.25
  ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6
  Uname: Linux 4.2.0-21-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  roman  2043 F pulseaudio
   /dev/snd/controlC1:  roman  2043 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Dec 11 14:01:58 2015
  HibernationDevice: RESUME=UUID=38f2bb72-0ff3-498e-ab17-249df8b33aef
  InstallationDate: Installed on 2015-10-23 (49 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Aspire VN7-571G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic.efi.signed 
root=UUID=da03328e-3129-4dfc-98d7-b8b06fa3d5f1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-21-generic N/A
   linux-backports-modules-4.2.0-21-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-571G
  dmi.board.vendor: Acer
  dmi.board.version: V1.14
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.14
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.14:bd01/08/2015:svnAcer:pnAspireVN7-571G:pvrV1.14:rvnAcer:rnAspireVN7-571G:rvrV1.14:cvnAcer:ct10:cvrV1.14:
  dmi.product.name: Aspire VN7-571G
  dmi.product.version: V1.14
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525228/+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 1512149] Re: package linux-image-4.2.0-16-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

[Alberto Salvia Novella]

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

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

Title:
  package linux-image-4.2.0-16-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No idea. When I run ubuntu-bug linux, I get the error:
  The problem cannot be reported:
  This is not an official Ubuntu package. Please remove any third party package 
and try again.

  Since that gives no clue as to what package it's talking about, it could be a 
Microsoft error message. All I did was let Update Manger upgrade Ubuntu to 
15.10 at its own suggestion, unsuccessfully, apparently. During the process, I 
got dependency problem errors on kernel packages. It took a while, but the 
machine did reboot. Now I have:
  $ uname -a
  Linux Inspiron600m 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:01 UTC 
2015 i686 i686 i686 GNU/Linux
  (which I believe is what I had before the upgrade started). So I did this:
  $ sudo apt-get check
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  You might want to run 'apt-get -f install' to correct these.
  The following packages have unmet dependencies:
   linux-image-extra-4.2.0-16-generic : Depends: linux-image-4.2.0-16-generic 
but it is not installed
   linux-image-generic : Depends: linux-image-4.2.0-16-generic but it is not 
installed
  E: Unmet dependencies. Try using -f.

  $ sudo apt-get -f install
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Correcting dependencies... Done
  The following packages were automatically installed and are no longer 
required:
g++-4.9 gir1.2-vte-2.90 gstreamer0.10-gconf libapt-inst1.5 libavcodec56
libavformat56 libavresample2 libavutil54 libboost-filesystem1.55.0
libboost-iostreams1.55.0 libboost-system1.54.0 libboost-system1.55.0
libboost-thread1.54.0 libcamel-1.2-49 libclass-load-perl libdvbpsi9
libebackend-1.2-7 libebook-1.2-14 libebook-contacts-1.2-0 libecal-1.2-16
libedata-book-1.2-20 libedata-cal-1.2-23 libedataserver-1.2-18 libept1.4.12
libexiv2-13 libfarstream-0.1-0 libgdata19 libgegl-0.2-0 libgnome-bluetooth11
libgphoto2-port10 libgsoap5 libhogweed2 libinput7 libjson0
libkf5kcmutils-data libkf5kcmutils5 libkomparediff2-4 libkonq-common
libkonq5-templates libkonq5abi1 liblist-allutils-perl libmirclient8
libmircommon3 libmirprotobuf0 libnettle4 libplist2 libpoppler49
libpostproc52 libprotobuf9 libreadline5 libregexp-common-perl
libstdc++-4.9-dev libswscale3 libvncclient0 libvncserver0 libvpx1
libx264-142 libxcb-util0 mir-client-platform-mesa2 python-commandnotfound
python3-crypto upstart-bin
  Use 'apt-get autoremove' to remove them.
  The following extra packages will be installed:
linux-image-4.2.0-16-generic
  Suggested packages:
fdutils linux-doc-4.2.0 linux-source-4.2.0 linux-tools
  The following NEW packages will be installed:
linux-image-4.2.0-16-generic
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  3 not fully installed or removed.
  Need to get 0 B/16.9 MB of archives.
  After this operation, 38.8 MB of additional disk space will be used.
  Do you want to continue? [Y/n] Y
  (Reading database ... 292072 files and directories currently installed.)
  Preparing to unpack .../linux-image-4.2.0-16-generic_4.2.0-16.19_i386.deb ...
  This kernel does not support a non-PAE CPU.
  dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.2.0-16-generic_4.2.0-16.19_i386.deb 
(--unpack):
   subprocess new pre-installation script returned error exit status 1
  Examining /etc/kernel/postrm.d .
  run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.2.0-16-generic 
/boot/vmlinuz-4.2.0-16-generic
  run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.2.0-16-generic 
/boot/vmlinuz-4.2.0-16-generic
  Errors were encountered while processing:
   /var/cache/apt/archives/linux-image-4.2.0-16-generic_4.2.0-16.19_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  That (finally) tells me the real problem is that Update Manager tried
  to install an upgrade that doesn't "support a non-PAE CPU". Strictly
  speaking, as I understand it, the Centrino on this machine has the PAE
  capability but not the ability to tell the OS the ability is there, as
  I had to start with a "non-PAE" Ubuntu installer and everything
  through 15.04 seems to have worked just fine.

  I guess since the machine still works, I can purge the kernel packages that 
won't work and see what problems I have to deal with in the future. It is 
unfortunate that we allow industry to force us to buy new computers when 99.99% 
of all computers currently used privately and 

[Kernel-packages] [Bug 1510405] Re: Direct firmware load for radeon/kaveri_sdma1.bin failed with error -2

[Luis Henriques]

Thank you Timothy.  As per comment #8, I am tagging this bug as verified
for wily.

** Tags removed: verification-needed-wily
** Tags added: verification-done-wily

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

Title:
  Direct firmware load for radeon/kaveri_sdma1.bin failed with error -2

Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux source package in Wily:
  In Progress
Status in linux-firmware source package in Wily:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-firmware source package in Xenial:
  Invalid

Bug description:
  == SRU Justification ==

  Impact: CONFIG_DRM_AMDGPU_CIK enables experimental support for some
  AMD hardware in the amdgpu driver. It's not considered stable yet and
  is not working properly with some hardware.

  Fix: Disable this option. The hardware which is no longer supported by
  amdgpu is all supported by the radeon driver.

  Regression Potential: It's possible that some regressions might be
  seen by users with affected hardware, but generally using radeon for
  this hardware should be more stable.

  ---

  Version 1.149 of the package does not have
  /lib/firmware/radeon/kaveri_sdma1.bin needed for the latest AMD DRM
  module.

  After booting my monitor is blank.

  For other AMD chipsets *_sdma1.bin is needed as well:
  drivers/gpu/drm/amd/amdgpu/cik_sdma.c(126): snprintf(fw_name, 
sizeof(fw_name), "radeon/%s_sdma1.bin", chip_name);

  Similar to https://bugs.launchpad.net/ubuntu/+source/linux-
  firmware/+bug/1183777, https://bugs.launchpad.net/ubuntu/+source
  /linux-firmware/+bug/1218691

  Best regards,
  Timothy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1510405/+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 1511041] Re: initramfs-tools btrfs hook warning: /sbin/fsck.btrfs doesn't exist

[Alberto Salvia Novella]

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

Title:
  initramfs-tools btrfs hook warning: /sbin/fsck.btrfs doesn't exist

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  New warning after upgrade from 15.04 to 15.10
  It appears that no script is using the binary, just there to repair a damaged 
btrfs drive if something fails while booting 

  $ sudo update-initramfs -u -k all
  update-initramfs: Generating /boot/initrd.img-4.2.0-16-generic
  Warning: /sbin/fsck.btrfs doesn't exist, can't install to initramfs, ignoring.
  update-initramfs: Generating /boot/initrd.img-3.19.0-31-generic
  Warning: /sbin/fsck.btrfs doesn't exist, can't install to initramfs, ignoring.
  $ sudo rgrep fsck.btrfs /etc/initramfs-tools/
  $ sudo rgrep fsck.btrfs /usr/lib/initramfs-tools/
  $ sudo rgrep fsck.btrfs /usr/share/initramfs-tools/
  /usr/share/initramfs-tools/hooks/btrfs:   copy_exec /bin/fsck.btrfs 
/bin

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.2.0-16-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Wed Oct 28 16:40:31 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-08 (111 days ago)
  InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  IwConfig:
   p1p1  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:0103 Elan Microelectronics Corp. ActiveJet 
K-2024 Multimedia Keyboard
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/vmlinuz-4.2.0-16-generic.efi.signed 
root=UUID=fb39de06-cf03-43a0-a736-ac681cf65dcb ro rootflags=subvol=@
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-27 (1 days ago)
  dmi.bios.date: 11/04/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: Q1900B-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd11/04/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnQ1900B-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511041/+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 1511002] Re: Computer freezes/crashes while using GNOME

[Alberto Salvia Novella]

Please:

1. If this bug is a duplicate of bug #1507255, please mark it as such.
2. Anyway, set this bug status back to "confirmed".

Thank you.

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

** Package changed: linux (Ubuntu) => xserver-xorg-video-intel (Ubuntu)

** Changed in: xserver-xorg-video-intel (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/1511002

Title:
  Computer freezes/crashes while using GNOME

Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  I think I have two issues (may related) with the Intel driver for my
  graphic card. Sometimes the text is shown as garbage, and every other
  day (after suspending) it crashes.  As I have not figure out what is
  the SysRq magic key is in this new laptop (Lenovo x250), I can only
  recover control on my computer after pressing the power off button.

  I cannot go to a vt. No nothing.  I hope the follow call trace is
  related to that, although it should not be there in any case :-)

  
  Oct 27 14:49:33 sai kernel: [38682.963345] [ cut here 
]
  Oct 27 14:49:33 sai kernel: [38682.963368] WARNING: CPU: 0 PID: 0 at 
/build/linux-AxjFAn/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:11100 
intel_check_page_flip+0xfc/0x110 [i915]()
  Oct 27 14:49:33 sai kernel: [38682.963369] Kicking stuck page flip: queued at 
2122948, now 2122952
  Oct 27 14:49:33 sai kernel: [38682.963370] Modules linked in: ses enclosure 
uas usb_storage hid_generic usbhid hid msr rfcomm pci_stub vboxpci(OE) 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) drbg ansi_cprng ctr ccm binfmt_misc 
bnep arc4 int
  el_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm 
uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core crct10dif_pclmul 
v4l2_common videodev crc32_pclmul iwlmvm snd_hda_codec_hdmi 
snd_hda_codec_realtek bt
  usb media snd_hda_codec_generic ghash_clmulni_intel btrtl mac80211 btbcm 
btintel bluetooth aesni_intel snd_hda_intel aes_x86_64 snd_hda_codec lrw 
gf128mul snd_hda_core glue_helper snd_hwdep ablk_helper thinkpad_acpi cryptd 
iwlwifi snd_pcm
   nvram snd_seq_midi snd_seq_midi_event snd_rawmidi input_leds cfg80211 joydev 
snd_seq serio_raw rtsx_pci_ms snd_seq_device memstick snd_timer snd mei_me 
soundcore shpchp mei lpc_ich mac_hid parport_pc ppdev sunrpc lp parport autofs4 
rtsx_
  pci_sdmmc i915 psmouse i2c_algo_bit e1000e drm_kms_helper ahci libahci drm 
ptp rtsx_pci pps_core wmi video
  Oct 27 14:49:33 sai kernel: [38682.963414] CPU: 0 PID: 0 Comm: swapper/0 
Tainted: GW  OE   4.2.0-16-generic #19-Ubuntu
  Oct 27 14:49:33 sai kernel: [38682.963415] Hardware name: LENOVO 
20CMCTO1WW/20CMCTO1WW, BIOS N10ET36W (1.15 ) 06/19/2015
  Oct 27 14:49:33 sai kernel: [38682.963416]   4c472c3169d69ebc 
88022dc03d48 817e8c09
  Oct 27 14:49:33 sai kernel: [38682.963418]   88022dc03da0 
88022dc03d88 8107b3c6
  Oct 27 14:49:33 sai kernel: [38682.963420]  88022dc03db8 8800b872d000 
8802201e2000 8800b872d1a8
  Oct 27 14:49:33 sai kernel: [38682.963421] Call Trace:
  Oct 27 14:49:33 sai kernel: [38682.963422][] 
dump_stack+0x45/0x57
  Oct 27 14:49:33 sai kernel: [38682.963429]  [] 
warn_slowpath_common+0x86/0xc0
  Oct 27 14:49:33 sai kernel: [38682.963431]  [] 
warn_slowpath_fmt+0x55/0x70
  Oct 27 14:49:33 sai kernel: [38682.963443]  [] 
intel_check_page_flip+0xfc/0x110 [i915]
  Oct 27 14:49:33 sai kernel: [38682.963453]  [] 
gen8_irq_handler+0x325/0x590 [i915]
  Oct 27 14:49:33 sai kernel: [38682.963456]  [] 
handle_irq_event_percpu+0x74/0x180
  Oct 27 14:49:33 sai kernel: [38682.963457]  [] 
handle_irq_event+0x49/0x70
  Oct 27 14:49:33 sai kernel: [38682.963459]  [] 
handle_edge_irq+0x81/0x150
  Oct 27 14:49:33 sai kernel: [38682.963461]  [] 
handle_irq+0x25/0x40
  Oct 27 14:49:33 sai kernel: [38682.963463]  [] 
do_IRQ+0x4f/0xe0
  Oct 27 14:49:33 sai kernel: [38682.963465]  [] 
common_interrupt+0x6b/0x6b
  Oct 27 14:49:33 sai kernel: [38682.963465][] ? 
enqueue_hrtimer+0x44/0x80
  Oct 27 14:49:33 sai kernel: [38682.963469]  [] ? 
cpuidle_enter_state+0x130/0x270
  Oct 27 14:49:33 sai kernel: [38682.963471]  [] ? 
cpuidle_enter_state+0x10b/0x270
  Oct 27 14:49:33 sai kernel: [38682.963472]  [] 
cpuidle_enter+0x17/0x20
  Oct 27 14:49:33 sai kernel: [38682.963474]  [] 
call_cpuidle+0x32/0x60
  Oct 27 14:49:33 sai kernel: [38682.963475]  [] ? 
cpuidle_select+0x13/0x20
  Oct 27 14:49:33 sai kernel: [38682.963476]  [] 
cpu_startup_entry+0x268/0x320
  Oct 27 14:49:33 sai kernel: [38682.963479]  [] 
rest_init+0x7c/0x80
  Oct 27 14:49:33 sai kernel: [38682.963481]  [] 
start_kernel+0x48b/0x4ac
  Oct 27 14:49:33 sai kernel: [38682.963483]  [] ? 
early_idt_handler_array+0x120/0x120
  Oct 27 14:49:33 sai kernel: [38682.963484]  [] 

[Kernel-packages] [Bug 1503731] Re: 8086:0f31 Ubuntu 15.04-15.10 freezes totally

[Christopher M. Penalver]

Chris Rainey, to advise, given this is Lauchpad (downstream reporting
system) it's impossible to mark it a duplicate of an freedesktop.org
(upstream reporting system) report, or any other reporting system. Also,
this is not considered being tracked at bugzilla, as this hasn't been
confirmed to be related.

Despite that, this report (downstream) is still pending
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503731/comments/12
. Given your belief there is a commonality to an upstream report, it
would help to provide evidence of it by confirming the regression commit
noted in the upstream report is indeed the same for your hardware.

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

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

Title:
  8086:0f31 Ubuntu 15.04-15.10 freezes totally

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ever since I first installed 15.04 back in April/May on my new DELL
  Inspiron 3646 I have experienced frequent(daily/every-other-
  day)complete lockups(cannot even switch to console(Alt-F1,F2,etc.).

  I have determined that the issue is related to the 'i915' driver in
  relation to my GPU.

  I'm currently using intel-linux-graphics-
  installer_1.2.0-0intel1_amd64.deb from https://01.org/linuxgraphics
  with similar results (maybe a little better than the stock i915 stack
  in 15.04).

  WORKAROUND: Use kernel boot parameter:
  intel_idle.max_cstate=1

  I have gained _significant_ improvements in reliability / stability by
  using parameters in the i915 module:

  /etc/modprobe.d/i915.conf:
  options i915 semaphores=1

  and / or

  /etc/default/grub:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_pstate=disable"

  and / or
  /usr/share/X11/xorg.conf.d/20-intel.conf:

  Section "Device"
     Identifier "Intel Graphics"
     Driver "intel"
     Option "TearFree" "1"
  EndSection

  and / or
  Disable "Intel Virtualization Technologies" in the BIOS.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CompositorRunning: None
  Date: Wed Oct  7 09:32:47 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:068d]
  InstallationDate: Installed on 2015-09-17 (19 days ago)
  InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:1005): WARNING **: [PIDs] Failed to execute command: 
upstart

   ** (lightdm-gtk-greeter:1005): WARNING **: Failed to load user image: Failed 
to open file '/home/chris/.face': No such file or directory
  MachineType: Dell Inc. Inspiron 3646
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic.efi.signed 
root=UUID=ef22be35-6f79-4356-be42-2689d1de0378 ro quiet
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0V6D8J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/17/2015:svnDellInc.:pnInspiron3646:pvr:rvnDellInc.:rn0V6D8J:rvrA00:cvnDellInc.:ct3:cvrA09:
  dmi.product.name: Inspiron 3646
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Tue Oct  6 20:05:51 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 990
   vendor ACR
  xserver.version: 2:1.17.1-0ubuntu3.1

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to  

[Kernel-packages] [Bug 1523178] Re: 1217:8520 [Dell Latitude E7450] O2 Micro, SD/MMC Card Reader doesn't work

[Christopher M. Penalver]

Blackgr, the issue you are reporting is an upstream one. Could you
please report this problem following the instructions verbatim at
https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate venue
(TO Adam Lee, Peter Guo, and Ulf Hansson CC linux-mmc)?

Please provide a direct URL to your newly made report when it becomes
available so that it may be tracked.

Thank you for your understanding.

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

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

Title:
  1217:8520 [Dell Latitude E7450] O2 Micro, SD/MMC Card Reader doesn't
  work

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Under ubuntu 15.10 I can't use my Sandisk ultra 64GB microSD (with a
  SD card adapter) with the built in SD card reader. I seem to be
  getting the following errors.

  [ 1268.126602] sdhci: Timeout waiting for Buffer Read Ready interrupt during 
tuning procedure, falling back to fixed sampling clock
  [ 1268.128381] mmc0: tuning execution failed
  [ 1268.128386] mmc0: error -5 whilst initialising SD card
  [ 1268.554319] sdhci: Timeout waiting for Buffer Read Ready interrupt during 
tuning procedure, falling back to fixed sampling clock
  [ 1268.556098] mmc0: tuning execution failed
  [ 1268.556103] mmc0: error -5 whilst initialising SD card
  [ 1268.993995] sdhci: Timeout waiting for Buffer Read Ready interrupt during 
tuning procedure, falling back to fixed sampling clock
  [ 1268.995778] mmc0: tuning execution failed
  [ 1268.995786] mmc0: error -5 whilst initialising SD card
  [ 1269.453666] sdhci: Timeout waiting for Buffer Read Ready interrupt during 
tuning procedure, falling back to fixed sampling clock
  [ 1269.455449] mmc0: tuning execution failed
  [ 1269.455458] mmc0: error -5 whilst initialising SD card

  It was working fine under vivid with kernel 3.19.

  Went through all the kernels from 3.19 to 4.2
  (http://kernel.ubuntu.com/~kernel-ppa/) and found out that until
  4.1.8-040108-generic the SD card reader would play fine and only after
  I put 4.1.9 and on I started getting the errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  alex   1606 F pulseaudio
   /dev/snd/controlC0:  alex   1606 F pulseaudio
   /dev/snd/controlC1:  alex   1606 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Dec  6 01:40:18 2015
  HibernationDevice: RESUME=UUID=acf75838-59f9-4461-9fe4-e9bdf33b28be
  InstallationDate: Installed on 2015-10-27 (38 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic 
root=UUID=c654e4bc-b0e1-4a85-844f-99f068b2efff ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2015-11-04 (31 days ago)
  dmi.bios.date: 10/28/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0R1VJD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/28/2015:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0R1VJD:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523178/+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 1518570] Re: Touchpad not working on Asus Zenbook UX305CA-FC022T

[Christopher M. Penalver]

Pelle van der Scheer, while it could be the same root cause, it has so
little information as to be considered useless in determining that. If
you would like to maximize the chances of the issue being addressed, you
would want to file a new report. If not, that decision falls on you.

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

Title:
  Touchpad not working on Asus Zenbook UX305CA-FC022T

Status in linux package in Ubuntu:
  Triaged

Bug description:
  New install of Ubuntu 15.10

  Touchpad is not working, using usb mouse.

  Tested mainstream kernel upto 4.4-rc1, still not working.

  Asus Zenbook UX305CA-FC022T

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pelle  1532 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Nov 21 16:02:10 2015
  InstallationDate: Installed on 2015-11-20 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed 
root=UUID=199cbad3-e17e-4549-b0ba-8eedbbbc3795 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.2
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305CA.201
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX305CA.201:bd09/11/2015:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX305CA
  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/1518570/+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 1521749] Re: NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19)

[Alberto Salvia Novella]

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

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

Title:
  NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Intel NUC NUC5CPYH. This is the unit:
  http://www.intel.com/content/www/us/en/nuc/nuc-kit-nuc5cpyh.html

  It boots beautifully on Ubuntu 15.04 and Ubuntu 15.10 with linux-
  image-3.19.0-34-generic -- but when I try to boot with  linux-
  image-4.2.0-19-generic  I simply see the following:

  https://www.dropbox.com/s/y2c9i87kafvwsq1/IMG_1476.jpg?dl=0

  The keyboard stops responding after this line: systemd[1]: Started
  udev Kernel Device Manager.

  Here is output from lspci -vnvn < http://pastie.org/10596250 - I am
  running headless, so there is no Xorg (or any other X server)
  installed.

  - I tried adding GRUB_CMDLINE_LINUX="nomodeset" (also: noacpi noapic)
  - I tried disabling devices in the bios like audio
  - Tried selecting "Ubuntu, with Linux 4.2.0-19-generic (recovery mode)" from 
the list, it does not boot into the recovery console either :(
  - I tried installing a clean 15.10 version on a blank hard drive (with 
debootstrap so latest packages)

  I am able to boot if I add systemd.unit=emergency.target to the kernel
  line. I can run "systemctl start networking" for example and it works,
  but if I run "systemctl start apport" (or ssh even) - I see this and
  the system freezes:

  https://www.dropbox.com/s/gmpse7bx0c70e4v/IMG_1479.jpg?dl=0

  I am not sure how to troubleshoot further. When I reboot and select
  Kernel 3.19, there is nothing in /var/log/syslog or journalctl from
  the failed boot :(

  Any suggestions?

  - EDIT: It seems downgrading from the latest PY0044 BIOS version to
  PY0043 allows me to boot the system, but it freezes if running
  "reboot" - more details in this bug report:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+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 1525228] [NEW] Qualcomm Atheros QCA61x4 cannot connect to encrypted 5Ghz networks

[Roman]

Public bug reported:

The device works fine with Ubuntu 15.10 mainline kernel 4.2.0 and the
firmware provided in linux-firmware on 2,4 Ghz wifi networks or
unencrypted 5GHz networks.

But when i connect to a encrypted 5Ghz network.  The firmware provide in 
linux-firmware (WLAN.RM.1.1-00141) crashed like i think is described here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516384

So i installed the latest firmware release SW_RM.1.1.1-00157-QCARMSWPZ-1
from ath10k-firmware (https://github.com/kvalo/ath10k-firmware/)

In this version the firmware doesn't crash but goes into a loop. Like
you see in dmesg, the device associates with the AP, but from an unknown
reason it cannot connect.

At the moment i cannot provide you any details about the AP im testing
with, because im using my universities network, but if you really need
them i can test the device with an known AP in a week or so.


PS: I tested the problem with all mainline and upstream kernels(4.2.6, 
4.3.0,4.4rc4) without any difference.

-

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-21-generic 4.2.0-21.25
ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6
Uname: Linux 4.2.0-21-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  roman  2043 F pulseaudio
 /dev/snd/controlC1:  roman  2043 F pulseaudio
CurrentDesktop: Unity
Date: Fri Dec 11 14:01:58 2015
HibernationDevice: RESUME=UUID=38f2bb72-0ff3-498e-ab17-249df8b33aef
InstallationDate: Installed on 2015-10-23 (49 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Acer Aspire VN7-571G
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic.efi.signed 
root=UUID=da03328e-3129-4dfc-98d7-b8b06fa3d5f1 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-21-generic N/A
 linux-backports-modules-4.2.0-21-generic  N/A
 linux-firmware1.149.3
SourcePackage: linux
UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/08/2015
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.14
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Aspire VN7-571G
dmi.board.vendor: Acer
dmi.board.version: V1.14
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.14
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.14:bd01/08/2015:svnAcer:pnAspireVN7-571G:pvrV1.14:rvnAcer:rnAspireVN7-571G:rvrV1.14:cvnAcer:ct10:cvrV1.14:
dmi.product.name: Aspire VN7-571G
dmi.product.version: V1.14
dmi.sys.vendor: Acer

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


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

** Description changed:

  The device works fine with Ubuntu 15.10 mainline kernel 4.2.0 and the
  firmware provided in linux-firmware on 2,4 Ghz wifi networks or
  unencrypted 5GHz networks.
  
  But when i connect to a encrypted 5Ghz network.  The firmware provide in 
linux-firmware (WLAN.RM.1.1-00141) crashed like i think is described here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516384
  
  So i installed the latest firmware release SW_RM.1.1.1-00157-QCARMSWPZ-1
  from ath10k-firmware (https://github.com/kvalo/ath10k-firmware/)
  
  In this version the firmware doesn't crash but goes into a loop. Like
  you see in dmesg, the device associates with the AP, but from an unknown
  reason it cannot connect.
  
  At the moment i cannot provide you any details about the AP im testing
  with, because im using my universities network, but if you really need
  them i can test the device with an known AP in a week or so.
  
+ -
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-21-generic 4.2.0-21.25
  ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6
  Uname: Linux 4.2.0-21-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  roman  2043 F pulseaudio
-  /dev/snd/controlC1:  roman  2043 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  roman  2043 F pulseaudio
+  /dev/snd/controlC1:  roman  2043 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Dec 11 14:01:58 2015
  HibernationDevice: RESUME=UUID=38f2bb72-0ff3-498e-ab17-249df8b33aef
  InstallationDate: Installed on 2015-10-23 (49 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Aspire VN7-571G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic.efi.signed 
root=UUID=da03328e-3129-4dfc-98d7-b8b06fa3d5f1 ro 

[Kernel-packages] [Bug 1525254] Status changed to Confirmed

[Brad Figg]

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

Title:
  The r8188eu driver shipped with wily is broken, new working driver
  exists

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After update to wily, I have continuous disconnections with a tplink
  725N wifi usb dongle that uses the r8188eu driver to the point that
  the dongle is completely useless.

  In vivid, the  driver driver shipped with the kernel was problematic
  but working a bit better (some disconnections, and incorrect link
  quality reporting, but OK for the rest) so we definitely have a
  REGRESSION.

  Furthermore, on the tplink driver the *source* or a driver that works
  fine is available:

  http://www.tp-link.us/res/down/soft/TL-WN725N_V2_150911.zip

  Porting to a format consistent with the pristine kernel has been done,
  see

  https://github.com/lwfinger/rtl8188eu/issues/152

  and

  https://www.dropbox.com/s/znp5munr03oow0b/rtl8188eu-linux-
  driver.zip?dl=0

  The thing still does not compile cleanly against the 4.2 kernel
  shipped in wily, because the interface of cfg80211_disconnected has
  changed, but the fix is trivial

  diff -r rtl8188eu-linux-driver/os_dep/linux/ioctl_cfg80211.c 
rtl8188eu-linux-driver2/os_dep/linux/ioctl_cfg80211.c
  907c907
  <   cfg80211_disconnected(padapter->pnetdev, 0, NULL, 0, 
GFP_ATOMIC);
  ---
  >   cfg80211_disconnected(padapter->pnetdev, 0, NULL, 0, 
false, GFP_ATOMIC);

  Furthermore there is a re-definition that needs removing

  diff -r rtl8188eu-linux-driver/hal/hal_com_phycfg.c 
rtl8188eu-linux-driver2/hal/hal_com_phycfg.c
  2578c2578
  < char  file_path[PATH_LENGTH_MAX];
  ---
  > //charfile_path[PATH_LENGTH_MAX];

  Once that is done, the tplink driver works perfectly.

  Please update wily to use the new driver.

  It may be worth informing the upstream kernel maintainer and Greg K.H.
  about the new opensource driver for possible inclusion  in the
  upstream kernel staging tree in place of the troublesome driver that
  is currently there.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-generic 4.2.0.19.21
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  callegar   2596 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Dec 11 14:50:16 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=c50b4249-43ed-49ef-a3d8-ec7aa9718265
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-19-generic 
root=/dev/mapper/DISK00-root ro quiet splash nomdmonddf nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  StagingDrivers: r8188eu
  UpgradeStatus: Upgraded to wily on 2015-11-28 (12 days ago)
  WpaSupplicantLog:
   
  dmi.bios.date: 04/21/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: N68-S
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/21/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525254/+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 1498862] Re: autopkgtest: rebuild test should not run when testing ourselves

[Luis Henriques]

The rebuild-stdout for trusty adt tests contains:

  rebuild: short circuiting build for 'linux-meta/3.13.0.73.79'

The rebuild-stdout for vivid adt tests contains:

  rebuild: short circuiting build for 'linux-meta/3.19.0.41.40'

Tagging as verified both for trusty and vivid.

** Tags removed: verification-needed-trusty verification-needed-vivid
** Tags added: verification-done-trusty verification-done-vivid

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

Title:
  autopkgtest: rebuild test should not run when testing ourselves

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Released

Bug description:
  We have a rebuild test which is intended to confirm the kernel still
  builds when core-utils, gcc, ld etc change.  It makes no sense for
  this test to run for the kernel itself as it takes a very long time to
  run and we have literally just built the kernel with those tools.

  Check for the trigger being something other than the kernel packages
  themselves before doing the rebuild.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1498862/+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 1504441] Re: [4.2.0-16.19] kernel: nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.

[Alberto Salvia Novella]

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

** Changed in: linux (Ubuntu)
   Importance: Low => 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/1504441

Title:
  [4.2.0-16.19] kernel: nf_conntrack: automatic helper assignment is
  deprecated and it will be removed soon. Use the iptables CT target to
  attach helpers instead.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  canonical-kernel-team ppa

  still need to fix that error logged into journalctl
  ( the system seems to work as expected)
  --- 
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem1587 F pulseaudio
   /dev/snd/pcmC0D0p:   oem1587 F...m pulseaudio
   /dev/snd/controlC0:  oem1587 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   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
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro intel_iommu=on
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  RfKill:
   
  Tags:  wily
  Uname: Linux 4.2.0-16-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504441/+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 1264311] Re: BCM43142 bluetooth adapter not finding any bluetooth devices

[Pilot6]

The first is not needed.

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

Title:
  BCM43142 bluetooth adapter not finding any bluetooth devices

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On my officially Ubuntu-certified Lenovo B590 laptop the BCM43142
  bluetooth adapter is not working. I have two further bluetooth devices
  placed closely to the laptop, non-paired and each being able to
  discover the other respectively. None of them is able to discover the
  laptop, nor does 'hcitool scan' on the laptop find any devices. It
  does not give any errors though.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluez 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Thu Dec 26 15:34:08 2013
  InstallationDate: Installed on 2013-12-25 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: LENOVO 37613EG
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic 
root=UUID=c379c17a-9869-47a8-b9b3-83be4e302040 ro acpi_backlight=vendor quiet 
splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H9ET74WW(1.11)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 37613EG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH9ET74WW(1.11):bd06/26/2013:svnLENOVO:pn37613EG:pvrLenovoB590:rvnLENOVO:rn37613EG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 37613EG
  dmi.product.version: Lenovo B590
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 1C:3E:84:E8:81:98  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1244 acl:0 sco:0 events:81 errors:0
TX bytes:2820 acl:0 sco:0 commands:77 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1264311/+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 1525251] [NEW] linux: 4.3.0-4.13 -proposed tracker

[Tim Gardner]

Public bug reported:

This bug is for tracking the 4.3.0-4.13 upload package. This bug will
contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel-Prepare-package-start:Friday, 11. December 2015 13:51 UTC
kernel-phase-changed:Friday, 11. December 2015 13:51 UTC
kernel-phase:Prepare
kernel-stable-Promote-to-proposed-end:Friday, 11. December 2015 14:00 UTC

** Affects: kernel-development-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-development-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

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

** Affects: linux (Ubuntu Xenial)
 Importance: Medium
 Status: New


** Tags: block-proposed kernel-release-tracking-bug xenial

** Tags added: kernel-release-tracking-bug

** Tags added: block-proposed

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

** Tags added: xenial

** Also affects: kernel-development-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Changed in: kernel-development-workflow
   Status: New => In Progress

** Changed in: kernel-development-workflow
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

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

Title:
  linux: 4.3.0-4.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  New
Status in Kernel Development Workflow prepare-package-meta series:
  New
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  

[Kernel-packages] [Bug 1447053] Re: IO_PAGE_FAULT

[Serban Maerean]

Actually, you helped more than you think. :-)

So I did a little reading about the IOMMU issue and the problem is that
IOMMU itself is not the problem.  It just shows the real problem (I
think this is not new news, really.)  Anyway, the problem appears to be
the xhci_hcd device driver that I cannot disable.  I still don't
understand how that impacts the ethernet device driver, though.

I added the iommu=soft option to the boot menu and it seems that the
kernel is more lenient in treating the xhci_hcd mis-behavior and things
seem to work fine now.  So I guess I'll have to make option permanent
for the boot image.  That means I need to do that for every kernel
update.  Yuck.

Thanks so much.

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

Title:
  IO_PAGE_FAULT

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since a couple of weeks I'm experiencing a problem with my
  motherboard. For some reason the network goes randomly offline and I
  get a error messages about AMD-Vi.

  [ 6462.248434] AMD-Vi: Event logged [IO_PAGE_FAULT device=04:00.0
  domain=0x0019 address=0x3000 flags=0x0050]

  I didn't changed anything except for the internet modem is changed and
  I installed updates as I always do. When using google I see there are
  more people with this problem exactly the same motherboard, I find
  this strange because my pc is almost a year old and I never had this
  problem. Could it be a problem in the kernel of *ubuntu 14.04?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-49-generic 3.13.0-49.83
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  allard 2282 F pulseaudio
allard 2467 F pulseaudio
   /dev/snd/controlC0:  allard 2282 F pulseaudio
allard 2467 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Apr 22 11:34:46 2015
  HibernationDevice: RESUME=UUID=96633d31-18c6-4b01-b756-f5f919c43fb4
  InstallationDate: Installed on 2015-03-27 (25 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic 
root=UUID=2c77ade3-e2ea-4d88-94d6-e131053f8ac8 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-49-generic N/A
   linux-backports-modules-3.13.0-49-generic  N/A
   linux-firmware 1.127.11
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/02/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2204
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  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.:bvr2204:bd04/02/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1447053/+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 1508593] Re: [Hyper-V] x86/ioapic: Disable interrupts when re-routing legacy IRQs

[Joshua R. Poulson]

In progress. Sorry, there were a lot of -proposed requests this week.

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

Title:
  [Hyper-V] x86/ioapic: Disable interrupts when re-routing legacy IRQs

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Committed

Bug description:
  A sporadic hang with consequent crash is observed when booting Hyper-V
  Gen1 guests...

  Sauce request for upstream submission:

  https://lkml.org/lkml/2015/10/15/673

  From Vitaly Kuznetsov <> 
  Subject [PATCH] x86/ioapic: Disable interrupts when re-routing legacy IRQs 
  Date Thu, 15 Oct 2015 19:42:23 +0200 

  A sporadic hang with consequent crash is observed when booting Hyper-V Gen1
  guests:

   Call Trace:

[] ? trace_hardirqs_off+0xd/0x10
[] queue_work_on+0x46/0x90
[] ? add_interrupt_randomness+0x176/0x1d0
...

[] ? _raw_spin_unlock_irqrestore+0x3b/0x60
[] __irq_put_desc_unlock+0x1e/0x40
[] irq_modify_status+0xb5/0xd0
[] mp_register_handler+0x4b/0x70
[] mp_irqdomain_alloc+0x1ea/0x2a0
[] irq_domain_alloc_irqs_recursive+0x40/0xa0
[] __irq_domain_alloc_irqs+0x13c/0x2b0
[] alloc_isa_irq_from_domain.isra.1+0xc0/0xe0
[] mp_map_pin_to_irq+0x165/0x2d0
[] pin_2_irq+0x47/0x80
[] setup_IO_APIC+0xfe/0x802
...
[] ? rest_init+0x140/0x140
  The issue is easily reproducible with a simple instrumentation: if
  mdelay(10) is put between mp_setup_entry() and mp_register_handler() calls
  in mp_irqdomain_alloc() Hyper-V guest always fails to boot when re-routing
  IRQ0. The issue seems to be caused by the fact that we don't disable
  interrupts while doing IOPIC programming for legacy IRQs and IRQ0 actually
  happens. Decorate manipulations with legacy IRQs with local_irq_save()/
  local_irq_restore().

  Cc: Thomas Gleixner 
  Cc: Ingo Molnar 
  Cc: "H. Peter Anvin" 
  Cc: Jiang Liu 
  Cc: Yinghai Lu 
  Cc: K. Y. Srinivasan 
  Signed-off-by: Vitaly Kuznetsov 
  ---
  It may make sense to have interrupts disabled for non-legacy IRQs as well
  but I'm unaware of any bugs with them at this moment.
  ---
   arch/x86/kernel/apic/io_apic.c | 8 +++-
   1 file changed, 7 insertions(+), 1 deletion(-)
  diff --git a/arch/x86/kernel/apic/io_apic.c b/arch/x86/kernel/apic/io_apic.c
  index 5c60bb1..9aac777 100644
  --- a/arch/x86/kernel/apic/io_apic.c
  +++ b/arch/x86/kernel/apic/io_apic.c
  @@ -2907,6 +2907,7 @@ int mp_irqdomain_alloc(struct irq_domain *domain, 
unsigned int virq,
struct irq_data *irq_data;
struct mp_chip_data *data;
struct irq_alloc_info *info = arg;
  + unsigned long flags = 0;
   
if (!info || nr_irqs > 1)
return -EINVAL;
  @@ -2939,11 +2940,16 @@ int mp_irqdomain_alloc(struct irq_domain *domain, 
unsigned int virq,
   
cfg = irqd_cfg(irq_data);
add_pin_to_irq_node(data, ioapic_alloc_attr_node(info), ioapic, pin);
  +
  + if (virq < nr_legacy_irqs())
  + local_irq_save(flags);
if (info->ioapic_entry)
mp_setup_entry(cfg, data, info->ioapic_entry);
mp_register_handler(virq, data->trigger);
  - if (virq < nr_legacy_irqs())
  + if (virq < nr_legacy_irqs()) {
legacy_pic->mask(virq);
  + local_irq_restore(flags);
  + }
   
apic_printk(APIC_VERBOSE, KERN_DEBUG
"IOAPIC[%d]: Set routing entry (%d-%d -> 0x%x -> IRQ %d 
Mode:%i Active:%i Dest:%d)\n",
  -- 
  2.4.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508593/+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 1509029] Re: [Hyper-V] Crash in hot-add/remove scsi devices (smp)

[Joshua R. Poulson]

In progress. Sorry, there were a lot of -proposed requests this week.

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

Title:
  [Hyper-V] Crash in hot-add/remove scsi devices (smp)

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released

Bug description:
  On some host errors storvsc module tries to remove sdev by scheduling a job
  which does the following:

 sdev = scsi_device_lookup(wrk->host, 0, 0, wrk->lun);
 if (sdev) {
 scsi_remove_device(sdev);
 scsi_device_put(sdev);
 }

  While this code seems correct the following crash is observed:

   general protection fault:  [#1] SMP DEBUG_PAGEALLOC
   RIP: 0010:[]  [] bdi_destroy+0x39/0x220
   ...
   [] ? _raw_spin_unlock_irq+0x2c/0x40
   [] blk_cleanup_queue+0x17b/0x270
   [] __scsi_remove_device+0x54/0xd0 [scsi_mod]
   [] scsi_remove_device+0x2b/0x40 [scsi_mod]
   [] storvsc_remove_lun+0x3d/0x60 [hv_storvsc]
   [] process_one_work+0x1b1/0x530
   ...

  The problem comes with the fact that many such jobs (for the same device)
  are being scheduled simultaneously. While scsi_remove_device() uses
  shost->scan_mutex and scsi_device_lookup() will fail for a device in
  SDEV_DEL state there is no protection against someone who did
  scsi_device_lookup() before we actually entered __scsi_remove_device(). So
  the whole scenario looks like that: two callers do simultaneous (or
  preemption happens) calls to scsi_device_lookup() ant these calls succeed
  for all of them, after that both callers try doing scsi_remove_device().
  shost->scan_mutex only serializes their calls to __scsi_remove_device()
  and we end up doing the cleanup path twice.

  Signed-off-by: Vitaly Kuznetsov 
  ---
   drivers/scsi/scsi_sysfs.c | 8 
   1 file changed, 8 insertions(+)

  diff --git a/drivers/scsi/scsi_sysfs.c b/drivers/scsi/scsi_sysfs.c
  index b89..e0d2707 100644
  --- a/drivers/scsi/scsi_sysfs.c
  +++ b/drivers/scsi/scsi_sysfs.c
  @@ -1076,6 +1076,14 @@ void __scsi_remove_device(struct scsi_device *sdev)
   {
  struct device *dev = >sdev_gendev;

  +   /*
  +* This cleanup path is not reentrant and while it is impossible
  +* to get a new reference with scsi_device_get() someone can still
  +* hold a previously acquired one.
  +*/
  +   if (sdev->sdev_state == SDEV_DEL)
  +   return;
  +
  if (sdev->is_visible) {
  if (scsi_device_set_state(sdev, SDEV_CANCEL) != 0)
  return;

  
  --
  2.4.3

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

[Brad Figg]

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

Title:
  Wi-Di Realtek 8192E disconnects after a while and fails to reconnect

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A few minutes after booting my Samsung R580 laptop, the Wi-Fi
  disconnects and it fails to reconnect until I restart the machine.
  This happens with all the 64 bit versions of Ubuntu I tried, from
  14.04 to 15.10. With the 32 bit versions, everything runs perfectly.
  No loss of connection at all, even after 48 hours in a row.

  Here is the output of iwconfig after loss of connexion:

  eth7  no wireless extensions.

  lono wireless extensions.

  wlan6 802.11bgn  ESSID:"JeLisVosCourriels"  Nickname:"rtl8192E"
Mode:Managed  Frequency=2.417 GHz  Access Point: Not-Associated   
Bit Rate:19.5 Mb/s   
Retry min limit:7   RTS thr:off   Fragment thr:off
Power Management:off
Link Quality=10/100  Signal level=0 dBm  Noise level=-100 dBm
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:0  Invalid misc:0   Missed beacon:0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gilbert3115 F pulseaudio
   /dev/snd/controlC0:  gilbert3115 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Dec 11 09:27:18 2015
  HibernationDevice: RESUME=UUID=e19f92d5-541f-412f-b5b0-7d97bfa1b7ec
  InstallationDate: Installed on 2015-12-03 (7 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R580
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic 
root=UUID=f6b1d099-6ed1-4e82-823a-352535c7596c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2015-12-03 (7 days ago)
  dmi.bios.date: 12/21/2009
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 04JB.M014.20091221.hkk
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: R580
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  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:bvnPhoenixTechnologiesLtd.:bvr04JB.M014.20091221.hkk:bd12/21/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnR580:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR580:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: R580
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525270/+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 1514971] Re: [SRU trusty] arm64 USB support not enabled for APM Mustang

[Craig Magina]

The patches submitted for this bug turned out to not be the complete
picture. I have not hit any issues with these patches, but there are
additional patches that have been discovered recently as well as some
bug fixes that will need to be upstreamed around the dwc3 driver to
completely enable USB on the mustang platform. The current patch set
will not be changed, just additional patches will be added to the set.

** Tags removed: verification-needed-trusty
** Tags added: verification-failed-trusty

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

Title:
  [SRU trusty] arm64 USB support not enabled for APM Mustang

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

Bug description:
  [Impact]
  Currently USB is not enabled for arm64 platforms. The patches will enable USB 
for arm64 and for APM's Mustang platform. 

  [Test Case]
  Insert a USB device into an APM Mustang based platform.

  [Regression Risk]
  This patch set enables USB for all arm64 platforms, but they have all been 
accepted by upstream and have been tested on a couple Mustang platforms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514971/+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 1525324] [NEW] kernel/bonding: wrong netlink messages when deleting a bonding interface

[Nicolas Dichtel]

Public bug reported:

Here is the bug:

root@ubuntu1404:~# modprobe bonding
root@ubuntu1404:~# modprobe dummy
root@ubuntu1404:~# ip link set dummy0 master bond0
root@ubuntu1404:~# ip monitor link&
[1] 1065
root@ubuntu1404:~# ip link del bond0
Deleted 6: bond0:  mtu 1500 qdisc noop state DOWN 
group default 
link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
7: dummy0:  mtu 1500 qdisc noqueue state 
UNKNOWN group default 
link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
7: dummy0:  mtu 1500 qdisc noqueue state UNKNOWN 
group default 
link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
6: bond0:  mtu 1500 qdisc noop state DOWN group 
default 
link/ether e6:49:16:3b:17:fe brd ff:ff:ff:ff:ff:ff
6: bond0:  mtu 1500 qdisc noop state DOWN group 
default 
root@ubuntu1404:~# link/ether e6:49:16:3b:17:fe brd ff:ff:ff:ff:ff:ff
7: dummy0:  mtu 1500 qdisc noqueue state DOWN group default 
link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
7: dummy0:  mtu 1500 qdisc noqueue state DOWN group default 
link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
^C
root@ubuntu1404:~# uname -a
Linux ubuntu1404 3.13.0-71-generic #114-Ubuntu SMP Tue Dec 1 02:34:22 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux
root@ubuntu1404:~#

A netlink message advertise that bond0 is deleted and after that two
netlink messages are sent telling that bond0 exists again.

This bug has been fixed by these upstream commits:
56bfa7ee7c88 unregister_netdevice : move RTM_DELLINK to until after ndo_uninit
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=56bfa7ee7c88
395eea6ccf2b rtnetlink: delay RTM_DELLINK notification until after ndo_uninit()
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=395eea6ccf2b

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


** Tags: 6wind

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

Title:
  kernel/bonding: wrong netlink messages when deleting a bonding
  interface

Status in linux-lts-trusty package in Ubuntu:
  New

Bug description:
  Here is the bug:

  root@ubuntu1404:~# modprobe bonding
  root@ubuntu1404:~# modprobe dummy
  root@ubuntu1404:~# ip link set dummy0 master bond0
  root@ubuntu1404:~# ip monitor link&
  [1] 1065
  root@ubuntu1404:~# ip link del bond0
  Deleted 6: bond0:  mtu 1500 qdisc noop state DOWN 
group default 
  link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
  7: dummy0:  mtu 1500 qdisc noqueue state 
UNKNOWN group default 
  link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
  7: dummy0:  mtu 1500 qdisc noqueue state UNKNOWN 
group default 
  link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
  6: bond0:  mtu 1500 qdisc noop state DOWN group 
default 
  link/ether e6:49:16:3b:17:fe brd ff:ff:ff:ff:ff:ff
  6: bond0:  mtu 1500 qdisc noop state DOWN group 
default 
  root@ubuntu1404:~# link/ether e6:49:16:3b:17:fe brd ff:ff:ff:ff:ff:ff
  7: dummy0:  mtu 1500 qdisc noqueue state DOWN group default 
  link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
  7: dummy0:  mtu 1500 qdisc noqueue state DOWN group default 
  link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
  ^C
  root@ubuntu1404:~# uname -a
  Linux ubuntu1404 3.13.0-71-generic #114-Ubuntu SMP Tue Dec 1 02:34:22 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux
  root@ubuntu1404:~#

  A netlink message advertise that bond0 is deleted and after that two
  netlink messages are sent telling that bond0 exists again.

  This bug has been fixed by these upstream commits:
  56bfa7ee7c88 unregister_netdevice : move RTM_DELLINK to until after ndo_uninit
  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=56bfa7ee7c88
  395eea6ccf2b rtnetlink: delay RTM_DELLINK notification until after 
ndo_uninit()
  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=395eea6ccf2b

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1525324/+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 1505564] Re: Soft lockup with "block nbdX: Attempted send on closed socket" spam

[Dan Streetman]

I've dl'ed the dump and I'm reviewing 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/1505564

Title:
  Soft lockup with "block nbdX: Attempted send on closed socket" spam

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Some of our nova compute hosts regularly freeze, sometimes for a few
  hours, with kern.log getting spammed with:

  block nbdX: Attempted send on closed socket

  and a few "CPU soft lockup" messages (see attached log). This clears
  up when the queue gets cleared, eg :

  block nbdX: queue cleared

  trusty hosts with kernel version 3.19.0-30-generic.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 24 12:23 seq
   crw-rw 1 root audio 116, 33 Nov 24 12:23 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 14.04
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL385 G7
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-36-generic 
root=UUID=13289ac9-8dc9-4feb-b6bd-ca7db66b21d6 ro console=tty0 
console=ttyS1,38400 nosplash crashkernel=384M-:512M nox2apic intremap=off
  ProcVersionSignature: Ubuntu 
3.19.0-36.41~14.04.1hf00090138v20151122b1-generic 3.19.8-ckt9
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-36-generic N/A
   linux-backports-modules-3.19.0-36-generic  N/A
   linux-firmware 1.127.18
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.19.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/02/2014
  dmi.bios.vendor: HP
  dmi.bios.version: A18
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrA18:bd02/02/2014:svnHP:pnProLiantDL385G7:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL385 G7
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505564/+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 1525297] Re: nic-modules udeb missing s390 modules

[Dimitri John Ledkov]

** Description changed:

  should have things similar to debian:
  
- drwxr-xr-x root/root 0 2015-12-06 07:11 
./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/cio/
- -rw-r--r-- root/root 21656 2015-12-06 06:17 
./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/cio/ccwgroup.ko
- drwxr-xr-x root/root 0 2015-12-06 07:11 
./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/
- -rw-r--r-- root/root173104 2015-12-06 06:17 
./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/ctcm.ko
- -rw-r--r-- root/root 11760 2015-12-06 06:17 
./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/fsm.ko
- -rw-r--r-- root/root 84168 2015-12-06 06:17 
./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/lcs.ko
- -rw-r--r-- root/root 81568 2015-12-06 06:17 
./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/netiucv.ko
- -rw-r--r-- root/root223640 2015-12-06 06:17 
./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/qeth.ko
- -rw-r--r-- root/root 80216 2015-12-06 06:17 
./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/qeth_l2.ko
- -rw-r--r-- root/root136240 2015-12-06 06:17 
./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/qeth_l3.ko
+ ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/cio/
+ ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/cio/ccwgroup.ko
+ ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/
+ ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/ctcm.ko
+ ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/fsm.ko
+ ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/lcs.ko
+ ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/netiucv.ko
+ ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/qeth.ko
+ ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/qeth_l2.ko
+ ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/qeth_l3.ko

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

Title:
  nic-modules udeb missing s390 modules

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  should have things similar to debian:

  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/cio/
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/cio/ccwgroup.ko
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/ctcm.ko
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/fsm.ko
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/lcs.ko
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/netiucv.ko
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/qeth.ko
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/qeth_l2.ko
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/qeth_l3.ko

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525297/+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 1509029] Re: [Hyper-V] Crash in hot-add/remove scsi devices (smp)

[Joseph Salisbury]

Have you had a chance to test -proposed as of yet so we can mark the bug
as 'verification-done-wily'?

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

Title:
  [Hyper-V] Crash in hot-add/remove scsi devices (smp)

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released

Bug description:
  On some host errors storvsc module tries to remove sdev by scheduling a job
  which does the following:

 sdev = scsi_device_lookup(wrk->host, 0, 0, wrk->lun);
 if (sdev) {
 scsi_remove_device(sdev);
 scsi_device_put(sdev);
 }

  While this code seems correct the following crash is observed:

   general protection fault:  [#1] SMP DEBUG_PAGEALLOC
   RIP: 0010:[]  [] bdi_destroy+0x39/0x220
   ...
   [] ? _raw_spin_unlock_irq+0x2c/0x40
   [] blk_cleanup_queue+0x17b/0x270
   [] __scsi_remove_device+0x54/0xd0 [scsi_mod]
   [] scsi_remove_device+0x2b/0x40 [scsi_mod]
   [] storvsc_remove_lun+0x3d/0x60 [hv_storvsc]
   [] process_one_work+0x1b1/0x530
   ...

  The problem comes with the fact that many such jobs (for the same device)
  are being scheduled simultaneously. While scsi_remove_device() uses
  shost->scan_mutex and scsi_device_lookup() will fail for a device in
  SDEV_DEL state there is no protection against someone who did
  scsi_device_lookup() before we actually entered __scsi_remove_device(). So
  the whole scenario looks like that: two callers do simultaneous (or
  preemption happens) calls to scsi_device_lookup() ant these calls succeed
  for all of them, after that both callers try doing scsi_remove_device().
  shost->scan_mutex only serializes their calls to __scsi_remove_device()
  and we end up doing the cleanup path twice.

  Signed-off-by: Vitaly Kuznetsov 
  ---
   drivers/scsi/scsi_sysfs.c | 8 
   1 file changed, 8 insertions(+)

  diff --git a/drivers/scsi/scsi_sysfs.c b/drivers/scsi/scsi_sysfs.c
  index b89..e0d2707 100644
  --- a/drivers/scsi/scsi_sysfs.c
  +++ b/drivers/scsi/scsi_sysfs.c
  @@ -1076,6 +1076,14 @@ void __scsi_remove_device(struct scsi_device *sdev)
   {
  struct device *dev = >sdev_gendev;

  +   /*
  +* This cleanup path is not reentrant and while it is impossible
  +* to get a new reference with scsi_device_get() someone can still
  +* hold a previously acquired one.
  +*/
  +   if (sdev->sdev_state == SDEV_DEL)
  +   return;
  +
  if (sdev->is_visible) {
  if (scsi_device_set_state(sdev, SDEV_CANCEL) != 0)
  return;

  
  --
  2.4.3

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

[Brad Figg]

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

apport-collect 1525297

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

Title:
  nic-modules udeb missing s390 modules

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  should have things similar to debian:

  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/cio/
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/cio/ccwgroup.ko
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/ctcm.ko
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/fsm.ko
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/lcs.ko
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/netiucv.ko
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/qeth.ko
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/qeth_l2.ko
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/qeth_l3.ko

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525297/+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 1525297] Re: nic-modules udeb missing s390 modules

[Joseph Salisbury]

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

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

** Tags added: bot-stop-nagging 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/1525297

Title:
  nic-modules udeb missing s390 modules

Status in linux package in Ubuntu:
  Triaged

Bug description:
  should have things similar to debian:

  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/cio/
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/cio/ccwgroup.ko
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/ctcm.ko
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/fsm.ko
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/lcs.ko
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/netiucv.ko
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/qeth.ko
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/qeth_l2.ko
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/qeth_l3.ko

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525297/+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 1483343] Re: NMI watchdog: BUG: soft lockup errors when we execute lock_torture_wr tests

[Joseph Salisbury]

Thanks for running those two tests.  The results would indicate this bug
still exists in the mainline kernel and commit f548d99ef4 is not the fix
for this bug.

Was there a prior kernel that did not exhibit the bug?  If that is the
case, and this is a regression, we can perform a kernel bisect to
identify the commit that introduced the bug.

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

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

Title:
  NMI watchdog: BUG: soft lockup errors when we execute lock_torture_wr
  tests

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Vivid:
  In Progress

Bug description:
  ---Problem Description---
  NMI watchdog: BUG: soft lockup errors when we execute lock_torture_wr tests

  ---uname output---
  Linux alp15 3.19.0-18-generic #18~14.04.1-Ubuntu SMP Wed May 20 09:40:36 UTC 
2015 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = P8 

  ---Steps to Reproduce---
  Install a P8 Power VM LPAR with Ubuntu 14.04.2 ISO.
  Then install the Ubuntu 14.04.3 kernel on the same and reboot.
  Then compile and build the LTP latest test suites on the same.

  root@alp15:~# tar -xvf ltp-full-20150420.tar.bz2
  root@alp15:~# cd ltp-full-20150420/
  root@alp15:~/ltp-full-20150420# ls
  aclocal.m4  configure execltp.in  install-sh  Makefile  
READMErunltplite.shtestcasesutils
  autom4te.cache  configure.ac  IDcheck.sh  lib Makefile.release  
README.kernel_config  runtest  testscripts  ver_linux
  config.guessCOPYING   include ltpmenu missing   
runalltests.shscenario_groups  TODO VERSION
  config.sub  doc   INSTALL m4  pan   
runltpscripts  tools
  root@alp15:~/ltp-full-20150420# ./configure
  root@alp15:~/ltp-full-20150420# make
  root@alp15:~/ltp-full-20150420# make install

  root@alp15:/opt/ltp/testcases/bin# ./lock_torture.sh
  lock_torture 1 TINFO : estimate time 6.00 min
  lock_torture 1 TINFO : spin_lock: running 60 sec...

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034386] NMI watchdog: BUG: soft lockup - CPU#10 stuck 
for 21s! [lock_torture_wr:2337]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034389] NMI watchdog: BUG: soft lockup - CPU#6 stuck for 
22s! [lock_torture_wr:2331]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034394] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 
22s! [lock_torture_wr:2339]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034396] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 
22s! [lock_torture_wr:2346]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034398] NMI watchdog: BUG: soft lockup - CPU#7 stuck for 
21s! [lock_torture_wr:2334]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034410] NMI watchdog: BUG: soft lockup - CPU#11 stuck 
for 22s! [lock_torture_wr:2321]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034412] NMI watchdog: BUG: soft lockup - CPU#9 stuck for 
22s! [lock_torture_wr:2333]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.038386] NMI watchdog: BUG: soft lockup - CPU#14 stuck 
for 22s! [lock_torture_wr:2327]

   
  Stack trace output:
   root@alp15:~# dmesg | more
  [ 1717.146881] lock_torture_wr R  running task
  [ 1717.146881]
  [ 1717.146885] 0  2555  2 0x0804
  [ 1717.146887] Call Trace:
  [ 1717.146894] [c00c7551b820] [c00c7551b860] 0xc00c7551b860 
(unreliable)
  [ 1717.146899] [c00c7551b860] [c00b4fb0] __do_softirq+0x220/0x3b0
  [ 1717.146904] [c00c7551b960] [c00b5478] irq_exit+0x98/0x100
  [ 1717.146909] [c00c7551b980] [c001fa54] timer_interrupt+0xa4/0xe0
  [ 1717.146913] [c00c7551b9b0] [c0002758] 
decrementer_common+0x158/0x180
  [ 1717.146922] --- interrupt: 901 at _raw_write_lock+0x68/0xc0
  [ 1717.146922] LR = torture_rwlock_write_lock+0x28/0x40 [locktorture]
  [ 1717.146927] [c00c7551bca0] [c00c7551bcd0] 0xc00c7551bcd0 
(unreliable)
  [ 1717.146934] [c00c7551bcd0] [dd4810b8] 
torture_rwlock_write_lock+0x28/0x40 [locktorture]
  [ 1717.146939] [c00c7551bcf0] [dd480578] 
lock_torture_writer+0x98/0x210 [locktorture]
  [ 1717.146944] [c00c7551bd80] [c00da4d4] kthread+0x114/0x140
  [ 1717.146948] [c00c7551be30] [c000956c] 
ret_from_kernel_thread+0x5c/0x70
  [ 1717.146951] Task dump for CPU 10:
  [ 1717.146953] lock_torture_wr R  running task0  2537  2 
0x0804
  [ 1717.146957] Call Trace:
  [ 1717.146961] [c00c7557b820] [c00c7557b860] 0xc00c7557b860 

[Kernel-packages] [Bug 1505241] Re: Phone does not suspend

[Pat McGowan]

Latest log

Suspend blocking wakelocks:
  None

Resume wakeup causes:
  EINT, 170  98.84%
  CLDMA_MD1   0.58%
  CLDMA_MD,   1   0.58%

Suspend failure causes:
  tasks freezer abort   783  99.87%
  devices failed to suspend   1   0.13%

Time between successful suspends:
   Interval (seconds)  FrequencyCumulative Time (Seconds)
 0.250 -0.499  1   0.59%   0.42   0.02%
 0.500 -0.999 66  38.82%  61.81   2.23%
 1.000 -1.999 63  37.06%  94.71   3.42%
 2.000 -3.999 18  10.59%  41.06   1.48%
 4.000 -7.999 15   8.82%  87.16   3.15%
 8.000 -   15.999  0   0.00%   0.00   0.00%
16.000 -   31.999  1   0.59%  16.47   0.60%
32.000 -   63.999  0   0.00%   0.00   0.00%
64.000 -  127.999  0   0.00%   0.00   0.00%
   128.000 -  255.999  4   2.35% 634.54  22.92%
   256.000 -  511.999  1   0.59% 261.71   9.45%
   512.000 - 1023.999  0   0.00%   0.00   0.00%
  1024.000 - 2047.999  1   0.59%1570.61  56.73%

Duration of successful suspends:
   Interval (seconds)  FrequencyCumulative Time (Seconds)
 0.250 -0.499  3   1.75%   1.13   0.04%
 0.500 -0.999  0   0.00%   0.00   0.00%
 1.000 -1.999 10   5.85%  12.97   0.48%
 2.000 -3.999 17   9.94%  48.77   1.81%
 4.000 -7.999 91  53.22% 514.08  19.12%
 8.000 -   15.999 11   6.43% 122.08   4.54%
16.000 -   31.999  9   5.26% 212.36   7.90%
32.000 -   63.999 22  12.87%1165.36  43.35%
64.000 -  127.999  8   4.68% 611.53  22.75%

Suspends:
  789 suspends aborted (82.19%).
  171 suspends succeeded (17.81%).
  total time: 2688.280289 seconds (49.27%).
  minimum: 0.365635 seconds.
  maximum: 124.066354 seconds.
  mean: 15.720937 seconds.
  mode: 6.00 seconds.
  median: 6.060716 seconds.

Time between successful suspends:
  total time: 2768.483611 seconds (50.73%).
  minimum: 0.424609 seconds.
  maximum: 1570.606069 seconds.
  mean: 16.285198 seconds.
  mode: 1.00 seconds.
  median: 1.247488 seconds.


** Attachment added: "syslog"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505241/+attachment/4533267/+files/syslog

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

Title:
  Phone does not suspend

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  I am seeing both the MX4 on proposed and the E4.5 on stable exhibit similar 
behavior
  According to the logs they are not able to suspend due to active wakeup 
sources.
  (I am running a BT test kernel on the MX4 3.10.35+)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505241/+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 1508593] Re: [Hyper-V] x86/ioapic: Disable interrupts when re-routing legacy IRQs

[Joseph Salisbury]

Have you had a chance to test -proposed as of yet so we can mark the bug
as 'verification-done-wily'?

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

Title:
  [Hyper-V] x86/ioapic: Disable interrupts when re-routing legacy IRQs

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Committed

Bug description:
  A sporadic hang with consequent crash is observed when booting Hyper-V
  Gen1 guests...

  Sauce request for upstream submission:

  https://lkml.org/lkml/2015/10/15/673

  From Vitaly Kuznetsov <> 
  Subject [PATCH] x86/ioapic: Disable interrupts when re-routing legacy IRQs 
  Date Thu, 15 Oct 2015 19:42:23 +0200 

  A sporadic hang with consequent crash is observed when booting Hyper-V Gen1
  guests:

   Call Trace:

[] ? trace_hardirqs_off+0xd/0x10
[] queue_work_on+0x46/0x90
[] ? add_interrupt_randomness+0x176/0x1d0
...

[] ? _raw_spin_unlock_irqrestore+0x3b/0x60
[] __irq_put_desc_unlock+0x1e/0x40
[] irq_modify_status+0xb5/0xd0
[] mp_register_handler+0x4b/0x70
[] mp_irqdomain_alloc+0x1ea/0x2a0
[] irq_domain_alloc_irqs_recursive+0x40/0xa0
[] __irq_domain_alloc_irqs+0x13c/0x2b0
[] alloc_isa_irq_from_domain.isra.1+0xc0/0xe0
[] mp_map_pin_to_irq+0x165/0x2d0
[] pin_2_irq+0x47/0x80
[] setup_IO_APIC+0xfe/0x802
...
[] ? rest_init+0x140/0x140
  The issue is easily reproducible with a simple instrumentation: if
  mdelay(10) is put between mp_setup_entry() and mp_register_handler() calls
  in mp_irqdomain_alloc() Hyper-V guest always fails to boot when re-routing
  IRQ0. The issue seems to be caused by the fact that we don't disable
  interrupts while doing IOPIC programming for legacy IRQs and IRQ0 actually
  happens. Decorate manipulations with legacy IRQs with local_irq_save()/
  local_irq_restore().

  Cc: Thomas Gleixner 
  Cc: Ingo Molnar 
  Cc: "H. Peter Anvin" 
  Cc: Jiang Liu 
  Cc: Yinghai Lu 
  Cc: K. Y. Srinivasan 
  Signed-off-by: Vitaly Kuznetsov 
  ---
  It may make sense to have interrupts disabled for non-legacy IRQs as well
  but I'm unaware of any bugs with them at this moment.
  ---
   arch/x86/kernel/apic/io_apic.c | 8 +++-
   1 file changed, 7 insertions(+), 1 deletion(-)
  diff --git a/arch/x86/kernel/apic/io_apic.c b/arch/x86/kernel/apic/io_apic.c
  index 5c60bb1..9aac777 100644
  --- a/arch/x86/kernel/apic/io_apic.c
  +++ b/arch/x86/kernel/apic/io_apic.c
  @@ -2907,6 +2907,7 @@ int mp_irqdomain_alloc(struct irq_domain *domain, 
unsigned int virq,
struct irq_data *irq_data;
struct mp_chip_data *data;
struct irq_alloc_info *info = arg;
  + unsigned long flags = 0;
   
if (!info || nr_irqs > 1)
return -EINVAL;
  @@ -2939,11 +2940,16 @@ int mp_irqdomain_alloc(struct irq_domain *domain, 
unsigned int virq,
   
cfg = irqd_cfg(irq_data);
add_pin_to_irq_node(data, ioapic_alloc_attr_node(info), ioapic, pin);
  +
  + if (virq < nr_legacy_irqs())
  + local_irq_save(flags);
if (info->ioapic_entry)
mp_setup_entry(cfg, data, info->ioapic_entry);
mp_register_handler(virq, data->trigger);
  - if (virq < nr_legacy_irqs())
  + if (virq < nr_legacy_irqs()) {
legacy_pic->mask(virq);
  + local_irq_restore(flags);
  + }
   
apic_printk(APIC_VERBOSE, KERN_DEBUG
"IOAPIC[%d]: Set routing entry (%d-%d -> 0x%x -> IRQ %d 
Mode:%i Active:%i Dest:%d)\n",
  -- 
  2.4.3

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

[Tim Gardner]

You can make that option permanent by editing GRUB_CMDLINE_LINUX_DEFAULT
in /etc/default/grub, then running update-grub.

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

Title:
  IO_PAGE_FAULT

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since a couple of weeks I'm experiencing a problem with my
  motherboard. For some reason the network goes randomly offline and I
  get a error messages about AMD-Vi.

  [ 6462.248434] AMD-Vi: Event logged [IO_PAGE_FAULT device=04:00.0
  domain=0x0019 address=0x3000 flags=0x0050]

  I didn't changed anything except for the internet modem is changed and
  I installed updates as I always do. When using google I see there are
  more people with this problem exactly the same motherboard, I find
  this strange because my pc is almost a year old and I never had this
  problem. Could it be a problem in the kernel of *ubuntu 14.04?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-49-generic 3.13.0-49.83
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  allard 2282 F pulseaudio
allard 2467 F pulseaudio
   /dev/snd/controlC0:  allard 2282 F pulseaudio
allard 2467 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Apr 22 11:34:46 2015
  HibernationDevice: RESUME=UUID=96633d31-18c6-4b01-b756-f5f919c43fb4
  InstallationDate: Installed on 2015-03-27 (25 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic 
root=UUID=2c77ade3-e2ea-4d88-94d6-e131053f8ac8 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-49-generic N/A
   linux-backports-modules-3.13.0-49-generic  N/A
   linux-firmware 1.127.11
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/02/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2204
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  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.:bvr2204:bd04/02/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1447053/+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 1523765] Re: USB performance extremely unstable

[Alberto Salvia Novella]

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

Title:
  USB performance extremely unstable

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since I upgraded from Trusty to Wily, the USB performance has become
  extremely unstable. Sometimes file transfers were fast, like 1GB in 30
  sec, then most days it is so slow like 1 GB in 20 minutes for no
  reason.

  Here some relevant log lines from the `dmesg` command when I USB is
  plugged in:

  ```
  [  496.912939] usb 4-5: new high-speed USB device number 2 using ehci-pci
  [  497.111419] usb 4-5: New USB device found, idVendor=1b1c, idProduct=1ab1
  [  497.111425] usb 4-5: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [  497.111428] usb 4-5: Product: Voyager
  [  497.111430] usb 4-5: Manufacturer: Corsair
  [  497.111433] usb 4-5: SerialNumber: AA400825
  [  497.134497] usb-storage 4-5:1.0: USB Mass Storage device detected
  [  497.134600] scsi host12: usb-storage 4-5:1.0
  [  497.134713] usbcore: registered new interface driver usb-storage
  [  497.137090] usbcore: registered new interface driver uas
  [  498.420795] scsi 12:0:0:0: Direct-Access Corsair  Voyager  
1100 PQ: 0 ANSI: 0 CCS
  [  498.421211] sd 12:0:0:0: Attached scsi generic sg5 type 0
  [  498.913643] sd 12:0:0:0: [sdd] 15663104 512-byte logical blocks: (8.01 
GB/7.46 GiB)
  [  498.914804] sd 12:0:0:0: [sdd] Write Protect is off
  [  498.914809] sd 12:0:0:0: [sdd] Mode Sense: 43 00 00 00
  [  498.915930] sd 12:0:0:0: [sdd] No Caching mode page found
  [  498.915934] sd 12:0:0:0: [sdd] Assuming drive cache: write through
  [  498.920710]  sdd: sdd1
  [  498.924684] sd 12:0:0:0: [sdd] Attached SCSI removable disk
  [ 1184.038007] usb 4-5: USB disconnect, device number 2
  ```

  these two lines appear in *red*

  ```
  [  498.915930] sd 12:0:0:0: [sdd] No Caching mode page found
  [  498.915934] sd 12:0:0:0: [sdd] Assuming drive cache: write through
  ```

  What can we do here? How can this be investigated and fixed properly?
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  michael-heuberger   4363 F pulseaudio
   /dev/snd/controlC2:  michael-heuberger   4363 F pulseaudio
   /dev/snd/controlC0:  michael-heuberger   4363 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=b0b47183-895a-4f27-bb25-40bd23028028
  InstallationDate: Installed on 2014-10-31 (403 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic 
root=UUID=b5b38333-3694-4441-8a13-50bf4dbf2f41 ro quiet
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.149.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  wily
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark www-data
  _MarkForUpload: True
  dmi.bios.date: 08/06/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0803
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6X58D-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0803:bd08/06/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6X58D-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523765/+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 1523738] Re: touchpad not working alienware 13 on ubuntu 15.10

[Alberto Salvia Novella]

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

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

Title:
  touchpad not working alienware 13 on ubuntu 15.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed ubuntu 15.10 on alienware 13, touchpad is showing up in xinput list 
as expected, but is totally unresponsive. Was working fine on 14.05
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sean   1610 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=ed54b297-8650-46ee-b615-6d543bb47b7a
  InstallationDate: Installed on 2015-12-07 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Alienware Alienware 13 R2
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=4c119f73-b6e4-4100-9d32-f6052a303bcf ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/15/2015
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.2.0
  dmi.board.name: Alienware 13 R2
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.2.0:bd10/15/2015:svnAlienware:pnAlienware13R2:pvr1.2.0:rvnAlienware:rnAlienware13R2:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
  dmi.product.name: Alienware 13 R2
  dmi.product.version: 1.2.0
  dmi.sys.vendor: Alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523738/+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 1522201] Re: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19)

[Alberto Salvia Novella]

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

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

Title:
  NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Intel NUC NUC5CPYH. This is the unit:
  http://www.intel.com/content/www/us/en/nuc/nuc-kit-nuc5cpyh.html

  It boots and reboots beautifully on Ubuntu 15.04 and Ubuntu 15.10 with
  linux-image-3.19.0-34-generic -- but when I try to boot with linux-
  image-4.2.0-19-generic on the latest PY0044 BIOS version, it freezes
  on boot almost every time, reported bug here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749

  If I downgrade the BIOS to PY0043, it boots most of the time, but when
  I run "reboot" it freezes almost every single time. This is what I see
  on the screen when it freezes:

  https://www.dropbox.com/s/fxy4opcqwnmjmwo/IMG_1489.jpg?dl=0

  I am also attaching the full syslog, dmesg and the relevant part of
  the syslog when the system froze.

  I tried to boot with acpi_osi="Windows 2013" as well as Windows 2015
  and Windows 2009, that did not seem to make any difference.

  Any ideas?

  ---
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  DistroRelease: Ubuntu 15.10

  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic 
root=UUID=4fa37335-eed0-4580-ae4b-62c996dfc275 ro vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.149.3
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/04/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-404
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201/+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 1519897] Re: [Hyper-V] hv: vmbus: Fix a host signaling bug

[Joseph Salisbury]

Dear Joshua,

I built a Xenial test kernel with the V2 patch.

Please test the kernel and let us know your results.  If we can receive
positive test feedback by December 18, we can proceed to submit the
patches for kernel SRU review in an attempt to make the upcoming kernel
SRU cycle starting on December 20th.  Assuming the patches are accepted
for SRU and land in the upcoming SRU cycle, the fix should be available
from the -updates pocket by January 9th.

The Xenial test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1519897/xenial

This kernel will cover both Xenial and Wily testing.  Vivid and Trusty
will need some backporting of the patch, so separate test kernels will
be posted for them.

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

Title:
  [Hyper-V] hv: vmbus: Fix a host signaling bug

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Vivid:
  Triaged
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  The following fix has been submitted upstream, but has high enough
  severity that we would like early inclusion into the Ubuntu kernel.
  Please consider for wily, vivid, and trusty (and the HWE kernels for
  the same).

  Patch follows:

  Currently we have two policies for deciding when to signal the host:
  One based on the ring buffer state and the other based on what the VMBUS 
client driver wants to do. Consider the case when the client wants to 
explicitly control when to signal the host. In this case, if the client were to 
defer signaling, we will not be able to signal the host subsequently when the 
client does want to signal since the ring buffer state will prevent the 
signaling. Implement logic to have only one signaling policy in force for a 
given channel.

  Signed-off-by: K. Y. Srinivasan 
  Reviewed-by: Haiyang Zhang 
  Tested-by: Haiyang Zhang 
  Cc:  # v4.2+
  ---
   drivers/hv/channel.c   |   18 ++
   include/linux/hyperv.h |   12 
   2 files changed, 30 insertions(+), 0 deletions(-)

  diff --git a/drivers/hv/channel.c b/drivers/hv/channel.c index 
77d2579..c6278c7 100644
  --- a/drivers/hv/channel.c
  +++ b/drivers/hv/channel.c
  @@ -653,10 +653,19 @@ int vmbus_sendpacket_ctl(struct vmbus_channel *channel, 
void *buffer,
     *on the ring. We will not signal if more data is
     *to be placed.
     *
  +  * Based on the channel signal state, we will decide
  +  * which signaling policy will be applied.
  +  *
     * If we cannot write to the ring-buffer; signal the host
     * even if we may not have written anything. This is a rare
     * enough condition that it should not matter.
     */
  +
  + if (channel->signal_state)
  + signal = true;
  + else
  + kick_q = true;
  +
    if (((ret == 0) && kick_q && signal) || (ret))
     vmbus_setevent(channel);

  @@ -756,10 +765,19 @@ int vmbus_sendpacket_pagebuffer_ctl(struct 
vmbus_channel *channel,
     *on the ring. We will not signal if more data is
     *to be placed.
     *
  +  * Based on the channel signal state, we will decide
  +  * which signaling policy will be applied.
  +  *
     * If we cannot write to the ring-buffer; signal the host
     * even if we may not have written anything. This is a rare
     * enough condition that it should not matter.
     */
  +
  + if (channel->signal_state)
  + signal = true;
  + else
  + kick_q = true;
  +
    if (((ret == 0) && kick_q && signal) || (ret))
     vmbus_setevent(channel);

  diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h index 
437c9c8..7b1af52 100644
  --- a/include/linux/hyperv.h
  +++ b/include/linux/hyperv.h
  @@ -756,8 +756,20 @@ struct vmbus_channel {
     * link up channels based on their CPU affinity.
     */
    struct list_head percpu_list;
  + /*
  +  * Host signaling policy: The default policy will be
  +  * based on the ring buffer state. We will also support
  +  * a policy where the client driver can have explicit
  +  * signaling control.
  +  */
  + bool signal_state;
   };

  +static inline void set_channel_signal_state(struct vmbus_channel *c,
  +bool state) {
  + c->signal_state = state;
  +}
  +
   static inline void set_channel_read_state(struct vmbus_channel *c, bool 
state)  {
    c->batched_reading = state;
  --
  1.7.4.1

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : 

[Kernel-packages] [Bug 1523565] Re: Qualcomm atheros network controller [168c:0042] (rev 30) does not work

[Alberto Salvia Novella]

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

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

Title:
  Qualcomm atheros network controller [168c:0042] (rev 30) does not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed the latest ath10k kernels, which changed the status of the
  hardware from unclaimed to claimed, but it still does not seem to be
  recognized as a wireless device

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1: (removed for privacy)  1358 F pulseaudio
   /dev/snd/controlC0: (removed for privacy)  1358 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Dec  7 21:22:43 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=ec603e54-8e2b-40c2-9bd4-559d5e329d2c
  InstallationDate: Installed on 2015-12-07 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   enp2s0no wireless extensions.

   lono wireless extensions.
  MachineType: Acer Aspire E5-573
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-19-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.149
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.15
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZORO_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.15:bd05/27/2015:svnAcer:pnAspireE5-573:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-573
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523565/+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 1519897] Re: [Hyper-V] hv: vmbus: Fix a host signaling bug

[Joshua R. Poulson]

Ah, we hadn't started Xenial testing yet. Give me a little more time to
spin that up.

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

Title:
  [Hyper-V] hv: vmbus: Fix a host signaling bug

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Vivid:
  Triaged
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  The following fix has been submitted upstream, but has high enough
  severity that we would like early inclusion into the Ubuntu kernel.
  Please consider for wily, vivid, and trusty (and the HWE kernels for
  the same).

  Patch follows:

  Currently we have two policies for deciding when to signal the host:
  One based on the ring buffer state and the other based on what the VMBUS 
client driver wants to do. Consider the case when the client wants to 
explicitly control when to signal the host. In this case, if the client were to 
defer signaling, we will not be able to signal the host subsequently when the 
client does want to signal since the ring buffer state will prevent the 
signaling. Implement logic to have only one signaling policy in force for a 
given channel.

  Signed-off-by: K. Y. Srinivasan 
  Reviewed-by: Haiyang Zhang 
  Tested-by: Haiyang Zhang 
  Cc:  # v4.2+
  ---
   drivers/hv/channel.c   |   18 ++
   include/linux/hyperv.h |   12 
   2 files changed, 30 insertions(+), 0 deletions(-)

  diff --git a/drivers/hv/channel.c b/drivers/hv/channel.c index 
77d2579..c6278c7 100644
  --- a/drivers/hv/channel.c
  +++ b/drivers/hv/channel.c
  @@ -653,10 +653,19 @@ int vmbus_sendpacket_ctl(struct vmbus_channel *channel, 
void *buffer,
     *on the ring. We will not signal if more data is
     *to be placed.
     *
  +  * Based on the channel signal state, we will decide
  +  * which signaling policy will be applied.
  +  *
     * If we cannot write to the ring-buffer; signal the host
     * even if we may not have written anything. This is a rare
     * enough condition that it should not matter.
     */
  +
  + if (channel->signal_state)
  + signal = true;
  + else
  + kick_q = true;
  +
    if (((ret == 0) && kick_q && signal) || (ret))
     vmbus_setevent(channel);

  @@ -756,10 +765,19 @@ int vmbus_sendpacket_pagebuffer_ctl(struct 
vmbus_channel *channel,
     *on the ring. We will not signal if more data is
     *to be placed.
     *
  +  * Based on the channel signal state, we will decide
  +  * which signaling policy will be applied.
  +  *
     * If we cannot write to the ring-buffer; signal the host
     * even if we may not have written anything. This is a rare
     * enough condition that it should not matter.
     */
  +
  + if (channel->signal_state)
  + signal = true;
  + else
  + kick_q = true;
  +
    if (((ret == 0) && kick_q && signal) || (ret))
     vmbus_setevent(channel);

  diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h index 
437c9c8..7b1af52 100644
  --- a/include/linux/hyperv.h
  +++ b/include/linux/hyperv.h
  @@ -756,8 +756,20 @@ struct vmbus_channel {
     * link up channels based on their CPU affinity.
     */
    struct list_head percpu_list;
  + /*
  +  * Host signaling policy: The default policy will be
  +  * based on the ring buffer state. We will also support
  +  * a policy where the client driver can have explicit
  +  * signaling control.
  +  */
  + bool signal_state;
   };

  +static inline void set_channel_signal_state(struct vmbus_channel *c,
  +bool state) {
  + c->signal_state = state;
  +}
  +
   static inline void set_channel_read_state(struct vmbus_channel *c, bool 
state)  {
    c->batched_reading = state;
  --
  1.7.4.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1519897/+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 1519897] Re: [Hyper-V] hv: vmbus: Fix a host signaling bug

[Joshua R. Poulson]

Indeed. Sorry, I should have recognized it. Too many parallel threads of
effort.

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

Title:
  [Hyper-V] hv: vmbus: Fix a host signaling bug

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  The following fix has been submitted upstream, but has high enough
  severity that we would like early inclusion into the Ubuntu kernel.
  Please consider for wily, vivid, and trusty (and the HWE kernels for
  the same).

  Patch follows:

  Currently we have two policies for deciding when to signal the host:
  One based on the ring buffer state and the other based on what the VMBUS 
client driver wants to do. Consider the case when the client wants to 
explicitly control when to signal the host. In this case, if the client were to 
defer signaling, we will not be able to signal the host subsequently when the 
client does want to signal since the ring buffer state will prevent the 
signaling. Implement logic to have only one signaling policy in force for a 
given channel.

  Signed-off-by: K. Y. Srinivasan 
  Reviewed-by: Haiyang Zhang 
  Tested-by: Haiyang Zhang 
  Cc:  # v4.2+
  ---
   drivers/hv/channel.c   |   18 ++
   include/linux/hyperv.h |   12 
   2 files changed, 30 insertions(+), 0 deletions(-)

  diff --git a/drivers/hv/channel.c b/drivers/hv/channel.c index 
77d2579..c6278c7 100644
  --- a/drivers/hv/channel.c
  +++ b/drivers/hv/channel.c
  @@ -653,10 +653,19 @@ int vmbus_sendpacket_ctl(struct vmbus_channel *channel, 
void *buffer,
     *on the ring. We will not signal if more data is
     *to be placed.
     *
  +  * Based on the channel signal state, we will decide
  +  * which signaling policy will be applied.
  +  *
     * If we cannot write to the ring-buffer; signal the host
     * even if we may not have written anything. This is a rare
     * enough condition that it should not matter.
     */
  +
  + if (channel->signal_state)
  + signal = true;
  + else
  + kick_q = true;
  +
    if (((ret == 0) && kick_q && signal) || (ret))
     vmbus_setevent(channel);

  @@ -756,10 +765,19 @@ int vmbus_sendpacket_pagebuffer_ctl(struct 
vmbus_channel *channel,
     *on the ring. We will not signal if more data is
     *to be placed.
     *
  +  * Based on the channel signal state, we will decide
  +  * which signaling policy will be applied.
  +  *
     * If we cannot write to the ring-buffer; signal the host
     * even if we may not have written anything. This is a rare
     * enough condition that it should not matter.
     */
  +
  + if (channel->signal_state)
  + signal = true;
  + else
  + kick_q = true;
  +
    if (((ret == 0) && kick_q && signal) || (ret))
     vmbus_setevent(channel);

  diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h index 
437c9c8..7b1af52 100644
  --- a/include/linux/hyperv.h
  +++ b/include/linux/hyperv.h
  @@ -756,8 +756,20 @@ struct vmbus_channel {
     * link up channels based on their CPU affinity.
     */
    struct list_head percpu_list;
  + /*
  +  * Host signaling policy: The default policy will be
  +  * based on the ring buffer state. We will also support
  +  * a policy where the client driver can have explicit
  +  * signaling control.
  +  */
  + bool signal_state;
   };

  +static inline void set_channel_signal_state(struct vmbus_channel *c,
  +bool state) {
  + c->signal_state = state;
  +}
  +
   static inline void set_channel_read_state(struct vmbus_channel *c, bool 
state)  {
    c->batched_reading = state;
  --
  1.7.4.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1519897/+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 1519897] Re: [Hyper-V] hv: vmbus: Fix a host signaling bug

[Joseph Salisbury]

Also, it looks like it's the V1 version of the patch in Vivid.  However,
it will be replace by V2 when it comes down from stable as an update.

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

Title:
  [Hyper-V] hv: vmbus: Fix a host signaling bug

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  The following fix has been submitted upstream, but has high enough
  severity that we would like early inclusion into the Ubuntu kernel.
  Please consider for wily, vivid, and trusty (and the HWE kernels for
  the same).

  Patch follows:

  Currently we have two policies for deciding when to signal the host:
  One based on the ring buffer state and the other based on what the VMBUS 
client driver wants to do. Consider the case when the client wants to 
explicitly control when to signal the host. In this case, if the client were to 
defer signaling, we will not be able to signal the host subsequently when the 
client does want to signal since the ring buffer state will prevent the 
signaling. Implement logic to have only one signaling policy in force for a 
given channel.

  Signed-off-by: K. Y. Srinivasan 
  Reviewed-by: Haiyang Zhang 
  Tested-by: Haiyang Zhang 
  Cc:  # v4.2+
  ---
   drivers/hv/channel.c   |   18 ++
   include/linux/hyperv.h |   12 
   2 files changed, 30 insertions(+), 0 deletions(-)

  diff --git a/drivers/hv/channel.c b/drivers/hv/channel.c index 
77d2579..c6278c7 100644
  --- a/drivers/hv/channel.c
  +++ b/drivers/hv/channel.c
  @@ -653,10 +653,19 @@ int vmbus_sendpacket_ctl(struct vmbus_channel *channel, 
void *buffer,
     *on the ring. We will not signal if more data is
     *to be placed.
     *
  +  * Based on the channel signal state, we will decide
  +  * which signaling policy will be applied.
  +  *
     * If we cannot write to the ring-buffer; signal the host
     * even if we may not have written anything. This is a rare
     * enough condition that it should not matter.
     */
  +
  + if (channel->signal_state)
  + signal = true;
  + else
  + kick_q = true;
  +
    if (((ret == 0) && kick_q && signal) || (ret))
     vmbus_setevent(channel);

  @@ -756,10 +765,19 @@ int vmbus_sendpacket_pagebuffer_ctl(struct 
vmbus_channel *channel,
     *on the ring. We will not signal if more data is
     *to be placed.
     *
  +  * Based on the channel signal state, we will decide
  +  * which signaling policy will be applied.
  +  *
     * If we cannot write to the ring-buffer; signal the host
     * even if we may not have written anything. This is a rare
     * enough condition that it should not matter.
     */
  +
  + if (channel->signal_state)
  + signal = true;
  + else
  + kick_q = true;
  +
    if (((ret == 0) && kick_q && signal) || (ret))
     vmbus_setevent(channel);

  diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h index 
437c9c8..7b1af52 100644
  --- a/include/linux/hyperv.h
  +++ b/include/linux/hyperv.h
  @@ -756,8 +756,20 @@ struct vmbus_channel {
     * link up channels based on their CPU affinity.
     */
    struct list_head percpu_list;
  + /*
  +  * Host signaling policy: The default policy will be
  +  * based on the ring buffer state. We will also support
  +  * a policy where the client driver can have explicit
  +  * signaling control.
  +  */
  + bool signal_state;
   };

  +static inline void set_channel_signal_state(struct vmbus_channel *c,
  +bool state) {
  + c->signal_state = state;
  +}
  +
   static inline void set_channel_read_state(struct vmbus_channel *c, bool 
state)  {
    c->batched_reading = state;
  --
  1.7.4.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1519897/+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 1525297] Re: nic-modules udeb missing s390 modules

[Tim Gardner]

** Also affects: linux (Ubuntu Xenial)
   Importance: Medium
   Status: Triaged

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

** Changed in: linux (Ubuntu Xenial)
 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/1525297

Title:
  nic-modules udeb missing s390 modules

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

Bug description:
  should have things similar to debian:

  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/cio/
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/cio/ccwgroup.ko
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/ctcm.ko
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/fsm.ko
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/lcs.ko
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/netiucv.ko
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/qeth.ko
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/qeth_l2.ko
  ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/qeth_l3.ko

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525297/+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 1525254] Re: The r8188eu driver shipped with wily is broken, new working driver exists

[Alberto Salvia Novella]

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

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

Title:
  The r8188eu driver shipped with wily is broken, new working driver
  exists

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After update to wily, I have continuous disconnections with a tplink
  725N wifi usb dongle that uses the r8188eu driver to the point that
  the dongle is completely useless.

  In vivid, the  driver driver shipped with the kernel was problematic
  but working a bit better (some disconnections, and incorrect link
  quality reporting, but OK for the rest) so we definitely have a
  REGRESSION.

  Furthermore, on the tplink driver the *source* or a driver that works
  fine is available:

  http://www.tp-link.us/res/down/soft/TL-WN725N_V2_150911.zip

  Porting to a format consistent with the pristine kernel has been done,
  see

  https://github.com/lwfinger/rtl8188eu/issues/152

  and

  https://www.dropbox.com/s/znp5munr03oow0b/rtl8188eu-linux-
  driver.zip?dl=0

  The thing still does not compile cleanly against the 4.2 kernel
  shipped in wily, because the interface of cfg80211_disconnected has
  changed, but the fix is trivial

  diff -r rtl8188eu-linux-driver/os_dep/linux/ioctl_cfg80211.c 
rtl8188eu-linux-driver2/os_dep/linux/ioctl_cfg80211.c
  907c907
  <   cfg80211_disconnected(padapter->pnetdev, 0, NULL, 0, 
GFP_ATOMIC);
  ---
  >   cfg80211_disconnected(padapter->pnetdev, 0, NULL, 0, 
false, GFP_ATOMIC);

  Furthermore there is a re-definition that needs removing

  diff -r rtl8188eu-linux-driver/hal/hal_com_phycfg.c 
rtl8188eu-linux-driver2/hal/hal_com_phycfg.c
  2578c2578
  < char  file_path[PATH_LENGTH_MAX];
  ---
  > //charfile_path[PATH_LENGTH_MAX];

  Once that is done, the tplink driver works perfectly.

  Please update wily to use the new driver.

  It may be worth informing the upstream kernel maintainer and Greg K.H.
  about the new opensource driver for possible inclusion  in the
  upstream kernel staging tree in place of the troublesome driver that
  is currently there.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-generic 4.2.0.19.21
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  callegar   2596 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Dec 11 14:50:16 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=c50b4249-43ed-49ef-a3d8-ec7aa9718265
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-19-generic 
root=/dev/mapper/DISK00-root ro quiet splash nomdmonddf nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  StagingDrivers: r8188eu
  UpgradeStatus: Upgraded to wily on 2015-11-28 (12 days ago)
  WpaSupplicantLog:
   
  dmi.bios.date: 04/21/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: N68-S
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/21/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525254/+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 1525270] Re: Wi-Di Realtek 8192E disconnects after a while and fails to reconnect

[Alberto Salvia Novella]

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

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

Title:
  Wi-Di Realtek 8192E disconnects after a while and fails to reconnect

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A few minutes after booting my Samsung R580 laptop, the Wi-Fi
  disconnects and it fails to reconnect until I restart the machine.
  This happens with all the 64 bit versions of Ubuntu I tried, from
  14.04 to 15.10. With the 32 bit versions, everything runs perfectly.
  No loss of connection at all, even after 48 hours in a row.

  Here is the output of iwconfig after loss of connexion:

  eth7  no wireless extensions.

  lono wireless extensions.

  wlan6 802.11bgn  ESSID:"JeLisVosCourriels"  Nickname:"rtl8192E"
Mode:Managed  Frequency=2.417 GHz  Access Point: Not-Associated   
Bit Rate:19.5 Mb/s   
Retry min limit:7   RTS thr:off   Fragment thr:off
Power Management:off
Link Quality=10/100  Signal level=0 dBm  Noise level=-100 dBm
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:0  Invalid misc:0   Missed beacon:0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gilbert3115 F pulseaudio
   /dev/snd/controlC0:  gilbert3115 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Dec 11 09:27:18 2015
  HibernationDevice: RESUME=UUID=e19f92d5-541f-412f-b5b0-7d97bfa1b7ec
  InstallationDate: Installed on 2015-12-03 (7 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R580
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic 
root=UUID=f6b1d099-6ed1-4e82-823a-352535c7596c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2015-12-03 (7 days ago)
  dmi.bios.date: 12/21/2009
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 04JB.M014.20091221.hkk
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: R580
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  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:bvnPhoenixTechnologiesLtd.:bvr04JB.M014.20091221.hkk:bd12/21/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnR580:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR580:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: R580
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

[garyr]

apport information

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

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

Title:
  transparent hugepages and thrashing on amd64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I seem to have found a solution to a severe
  thrashing/swapping/freezing problem that I've been having for months
  now.  I guess the real question is - should I turn it into a bug
  report and what would be useful data to include if so.

  This is a quad core AMD Phaeom system with 4G of ram, dual monitors
  and a single 1TB WD caviar black HD.  It had been behaving normally
  until something broke sometime late in the 11.x release cycle and
  continues in the current 12.04 LTS.  The symptoms are running a
  moderate load of apps (firefox with ~8 tabs, a terminal or 2, and
  aisleriot solitaire for example) and experiencing system freezes where
  the entire UI becomes totally unresponsive for 20 seconds - 5 minutes
  with solid disk activity.  Trying to figure out what was going on via
  iotop and top show jbd2 and kswapd accounting for the largest load,
  but since it freezes iotop like everything else I can't tell what's
  going during the worst storms.  Googling around shows a fair number of
  other people with similar problems, most of them with multi core amd64
  systems.

  The other day I spotted this report on opensuse that looked similar
  but not identical:

  http://lists.opensuse.org/opensuse/2012-03/msg00657.html

  I booted with the grub parameter transparent_hugepage=never yesterday
  and the problem went and away and hasn't come back. I've streesed the
  system by running  a bunch of flash/java tabs in firefox, running a
  large java based stock app (ThinkorSwim) in another workspace and
  playing a 1080p 60fps movie in a third workspace.  This certainly
  causes swapping, but not freezing or stumbling.  It actually did a bit
  of swapping a minute ago while I was typing and it managed to make
  Pandora radio stumble for a moment - but that's orders of magnitude
  better than it has been.

  I think there may be a fundamental problem with how transparent
  hugepages are handled with some AMD CPUs.  I think this problem
  started when this feature was implemented and enabled by default. The
  manpage for madvise() says this was added in 2.6.38, but I don't know
  if it was enabled by default at that point.

  Hre's a partial list of things that haven't worked well in the past:

  Playing with the swappiness value: setting swappiness to very low
  values makes the problem take longer to surface, but (unsurprisinglly)
  makes it even worse once it does.

  swapoff-a ; swapon-a: this makes it go away for a while.  A
  potentially interesting thing is that as soon as I can get the system
  to act on the swapoff -a the system becomes responsive again. It pegs
  once CPU core at 100% and the HD grinds like crazy but it stops
  freezing right away.

  Moving swap from the HD to a USB thumb drive: Obviously I didn't
  expect that to be faster but wanted to see if segregating swap to a
  different device on a different bus would make it swap more smoothly -
  it didn't.

  Playing with nice and ionice priorities for jdb2, kswapd.  The fact
  that running these processes at a lower priority than anything else on
  the system makes no difference leads me to think they were just
  symptoms and not at the root of the problem.

  I think this may be a tip of the iceberg and there may be a lot of
  other having this problem.  Looking around I see a fair number of
  reports, most of them unsolved.  Some may have been fixed by just
  adding enough RAM that dirty hugepages just don't collect.  Some may
  have been fixed by chaanging filesystems - ext4 seems like something a
  lot of people with this problem have in common.

  Workaround:
  hold down the spacebar during boot in order to bring up the grub menu, edit 
the command line and add
  transparent_hugepage=never

  If this fixes the problem you can make it permanent by editing
  /etc/default/grub and adding the ransparent_hugepage=never to the
  GRUB_CMDLINE_LINUX_DEFAULT  line and then running update-grub

  Problems with this workaround:
  1) transparent hugepages should work.  This may cause a small performance hit 
in some situations and a larger hit in others.
  2) If you do this you will probably never know when or if it actually gets 
fixed.

  PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ]
  Samba Team
  SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

  is looking for bugzilla reports on this too.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  garyrich   2339 F pulseaudio
   /dev/snd/controlC1:  garyrich   2339 F pulseaudio
  

[Kernel-packages] [Bug 1013807] JournalErrors.txt

[garyr]

apport information

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

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

Title:
  transparent hugepages and thrashing on amd64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I seem to have found a solution to a severe
  thrashing/swapping/freezing problem that I've been having for months
  now.  I guess the real question is - should I turn it into a bug
  report and what would be useful data to include if so.

  This is a quad core AMD Phaeom system with 4G of ram, dual monitors
  and a single 1TB WD caviar black HD.  It had been behaving normally
  until something broke sometime late in the 11.x release cycle and
  continues in the current 12.04 LTS.  The symptoms are running a
  moderate load of apps (firefox with ~8 tabs, a terminal or 2, and
  aisleriot solitaire for example) and experiencing system freezes where
  the entire UI becomes totally unresponsive for 20 seconds - 5 minutes
  with solid disk activity.  Trying to figure out what was going on via
  iotop and top show jbd2 and kswapd accounting for the largest load,
  but since it freezes iotop like everything else I can't tell what's
  going during the worst storms.  Googling around shows a fair number of
  other people with similar problems, most of them with multi core amd64
  systems.

  The other day I spotted this report on opensuse that looked similar
  but not identical:

  http://lists.opensuse.org/opensuse/2012-03/msg00657.html

  I booted with the grub parameter transparent_hugepage=never yesterday
  and the problem went and away and hasn't come back. I've streesed the
  system by running  a bunch of flash/java tabs in firefox, running a
  large java based stock app (ThinkorSwim) in another workspace and
  playing a 1080p 60fps movie in a third workspace.  This certainly
  causes swapping, but not freezing or stumbling.  It actually did a bit
  of swapping a minute ago while I was typing and it managed to make
  Pandora radio stumble for a moment - but that's orders of magnitude
  better than it has been.

  I think there may be a fundamental problem with how transparent
  hugepages are handled with some AMD CPUs.  I think this problem
  started when this feature was implemented and enabled by default. The
  manpage for madvise() says this was added in 2.6.38, but I don't know
  if it was enabled by default at that point.

  Hre's a partial list of things that haven't worked well in the past:

  Playing with the swappiness value: setting swappiness to very low
  values makes the problem take longer to surface, but (unsurprisinglly)
  makes it even worse once it does.

  swapoff-a ; swapon-a: this makes it go away for a while.  A
  potentially interesting thing is that as soon as I can get the system
  to act on the swapoff -a the system becomes responsive again. It pegs
  once CPU core at 100% and the HD grinds like crazy but it stops
  freezing right away.

  Moving swap from the HD to a USB thumb drive: Obviously I didn't
  expect that to be faster but wanted to see if segregating swap to a
  different device on a different bus would make it swap more smoothly -
  it didn't.

  Playing with nice and ionice priorities for jdb2, kswapd.  The fact
  that running these processes at a lower priority than anything else on
  the system makes no difference leads me to think they were just
  symptoms and not at the root of the problem.

  I think this may be a tip of the iceberg and there may be a lot of
  other having this problem.  Looking around I see a fair number of
  reports, most of them unsolved.  Some may have been fixed by just
  adding enough RAM that dirty hugepages just don't collect.  Some may
  have been fixed by chaanging filesystems - ext4 seems like something a
  lot of people with this problem have in common.

  Workaround:
  hold down the spacebar during boot in order to bring up the grub menu, edit 
the command line and add
  transparent_hugepage=never

  If this fixes the problem you can make it permanent by editing
  /etc/default/grub and adding the ransparent_hugepage=never to the
  GRUB_CMDLINE_LINUX_DEFAULT  line and then running update-grub

  Problems with this workaround:
  1) transparent hugepages should work.  This may cause a small performance hit 
in some situations and a larger hit in others.
  2) If you do this you will probably never know when or if it actually gets 
fixed.

  PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ]
  Samba Team
  SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

  is looking for bugzilla reports on this too.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  garyrich   2339 F pulseaudio
   /dev/snd/controlC1:  garyrich   2339 F 

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

[garyr]

apport information

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

Title:
  transparent hugepages and thrashing on amd64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I seem to have found a solution to a severe
  thrashing/swapping/freezing problem that I've been having for months
  now.  I guess the real question is - should I turn it into a bug
  report and what would be useful data to include if so.

  This is a quad core AMD Phaeom system with 4G of ram, dual monitors
  and a single 1TB WD caviar black HD.  It had been behaving normally
  until something broke sometime late in the 11.x release cycle and
  continues in the current 12.04 LTS.  The symptoms are running a
  moderate load of apps (firefox with ~8 tabs, a terminal or 2, and
  aisleriot solitaire for example) and experiencing system freezes where
  the entire UI becomes totally unresponsive for 20 seconds - 5 minutes
  with solid disk activity.  Trying to figure out what was going on via
  iotop and top show jbd2 and kswapd accounting for the largest load,
  but since it freezes iotop like everything else I can't tell what's
  going during the worst storms.  Googling around shows a fair number of
  other people with similar problems, most of them with multi core amd64
  systems.

  The other day I spotted this report on opensuse that looked similar
  but not identical:

  http://lists.opensuse.org/opensuse/2012-03/msg00657.html

  I booted with the grub parameter transparent_hugepage=never yesterday
  and the problem went and away and hasn't come back. I've streesed the
  system by running  a bunch of flash/java tabs in firefox, running a
  large java based stock app (ThinkorSwim) in another workspace and
  playing a 1080p 60fps movie in a third workspace.  This certainly
  causes swapping, but not freezing or stumbling.  It actually did a bit
  of swapping a minute ago while I was typing and it managed to make
  Pandora radio stumble for a moment - but that's orders of magnitude
  better than it has been.

  I think there may be a fundamental problem with how transparent
  hugepages are handled with some AMD CPUs.  I think this problem
  started when this feature was implemented and enabled by default. The
  manpage for madvise() says this was added in 2.6.38, but I don't know
  if it was enabled by default at that point.

  Hre's a partial list of things that haven't worked well in the past:

  Playing with the swappiness value: setting swappiness to very low
  values makes the problem take longer to surface, but (unsurprisinglly)
  makes it even worse once it does.

  swapoff-a ; swapon-a: this makes it go away for a while.  A
  potentially interesting thing is that as soon as I can get the system
  to act on the swapoff -a the system becomes responsive again. It pegs
  once CPU core at 100% and the HD grinds like crazy but it stops
  freezing right away.

  Moving swap from the HD to a USB thumb drive: Obviously I didn't
  expect that to be faster but wanted to see if segregating swap to a
  different device on a different bus would make it swap more smoothly -
  it didn't.

  Playing with nice and ionice priorities for jdb2, kswapd.  The fact
  that running these processes at a lower priority than anything else on
  the system makes no difference leads me to think they were just
  symptoms and not at the root of the problem.

  I think this may be a tip of the iceberg and there may be a lot of
  other having this problem.  Looking around I see a fair number of
  reports, most of them unsolved.  Some may have been fixed by just
  adding enough RAM that dirty hugepages just don't collect.  Some may
  have been fixed by chaanging filesystems - ext4 seems like something a
  lot of people with this problem have in common.

  Workaround:
  hold down the spacebar during boot in order to bring up the grub menu, edit 
the command line and add
  transparent_hugepage=never

  If this fixes the problem you can make it permanent by editing
  /etc/default/grub and adding the ransparent_hugepage=never to the
  GRUB_CMDLINE_LINUX_DEFAULT  line and then running update-grub

  Problems with this workaround:
  1) transparent hugepages should work.  This may cause a small performance hit 
in some situations and a larger hit in others.
  2) If you do this you will probably never know when or if it actually gets 
fixed.

  PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ]
  Samba Team
  SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

  is looking for bugzilla reports on this too.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  garyrich   2339 F pulseaudio
   /dev/snd/controlC1:  garyrich   2339 F pulseaudio
  

[Kernel-packages] [Bug 1013807] ProcCpuinfo.txt

[garyr]

apport information

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

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

Title:
  transparent hugepages and thrashing on amd64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I seem to have found a solution to a severe
  thrashing/swapping/freezing problem that I've been having for months
  now.  I guess the real question is - should I turn it into a bug
  report and what would be useful data to include if so.

  This is a quad core AMD Phaeom system with 4G of ram, dual monitors
  and a single 1TB WD caviar black HD.  It had been behaving normally
  until something broke sometime late in the 11.x release cycle and
  continues in the current 12.04 LTS.  The symptoms are running a
  moderate load of apps (firefox with ~8 tabs, a terminal or 2, and
  aisleriot solitaire for example) and experiencing system freezes where
  the entire UI becomes totally unresponsive for 20 seconds - 5 minutes
  with solid disk activity.  Trying to figure out what was going on via
  iotop and top show jbd2 and kswapd accounting for the largest load,
  but since it freezes iotop like everything else I can't tell what's
  going during the worst storms.  Googling around shows a fair number of
  other people with similar problems, most of them with multi core amd64
  systems.

  The other day I spotted this report on opensuse that looked similar
  but not identical:

  http://lists.opensuse.org/opensuse/2012-03/msg00657.html

  I booted with the grub parameter transparent_hugepage=never yesterday
  and the problem went and away and hasn't come back. I've streesed the
  system by running  a bunch of flash/java tabs in firefox, running a
  large java based stock app (ThinkorSwim) in another workspace and
  playing a 1080p 60fps movie in a third workspace.  This certainly
  causes swapping, but not freezing or stumbling.  It actually did a bit
  of swapping a minute ago while I was typing and it managed to make
  Pandora radio stumble for a moment - but that's orders of magnitude
  better than it has been.

  I think there may be a fundamental problem with how transparent
  hugepages are handled with some AMD CPUs.  I think this problem
  started when this feature was implemented and enabled by default. The
  manpage for madvise() says this was added in 2.6.38, but I don't know
  if it was enabled by default at that point.

  Hre's a partial list of things that haven't worked well in the past:

  Playing with the swappiness value: setting swappiness to very low
  values makes the problem take longer to surface, but (unsurprisinglly)
  makes it even worse once it does.

  swapoff-a ; swapon-a: this makes it go away for a while.  A
  potentially interesting thing is that as soon as I can get the system
  to act on the swapoff -a the system becomes responsive again. It pegs
  once CPU core at 100% and the HD grinds like crazy but it stops
  freezing right away.

  Moving swap from the HD to a USB thumb drive: Obviously I didn't
  expect that to be faster but wanted to see if segregating swap to a
  different device on a different bus would make it swap more smoothly -
  it didn't.

  Playing with nice and ionice priorities for jdb2, kswapd.  The fact
  that running these processes at a lower priority than anything else on
  the system makes no difference leads me to think they were just
  symptoms and not at the root of the problem.

  I think this may be a tip of the iceberg and there may be a lot of
  other having this problem.  Looking around I see a fair number of
  reports, most of them unsolved.  Some may have been fixed by just
  adding enough RAM that dirty hugepages just don't collect.  Some may
  have been fixed by chaanging filesystems - ext4 seems like something a
  lot of people with this problem have in common.

  Workaround:
  hold down the spacebar during boot in order to bring up the grub menu, edit 
the command line and add
  transparent_hugepage=never

  If this fixes the problem you can make it permanent by editing
  /etc/default/grub and adding the ransparent_hugepage=never to the
  GRUB_CMDLINE_LINUX_DEFAULT  line and then running update-grub

  Problems with this workaround:
  1) transparent hugepages should work.  This may cause a small performance hit 
in some situations and a larger hit in others.
  2) If you do this you will probably never know when or if it actually gets 
fixed.

  PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ]
  Samba Team
  SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

  is looking for bugzilla reports on this too.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  garyrich   2339 F pulseaudio
   /dev/snd/controlC1:  garyrich   2339 F pulseaudio

[Kernel-packages] [Bug 1013807] ProcEnviron.txt

[garyr]

apport information

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

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

Title:
  transparent hugepages and thrashing on amd64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I seem to have found a solution to a severe
  thrashing/swapping/freezing problem that I've been having for months
  now.  I guess the real question is - should I turn it into a bug
  report and what would be useful data to include if so.

  This is a quad core AMD Phaeom system with 4G of ram, dual monitors
  and a single 1TB WD caviar black HD.  It had been behaving normally
  until something broke sometime late in the 11.x release cycle and
  continues in the current 12.04 LTS.  The symptoms are running a
  moderate load of apps (firefox with ~8 tabs, a terminal or 2, and
  aisleriot solitaire for example) and experiencing system freezes where
  the entire UI becomes totally unresponsive for 20 seconds - 5 minutes
  with solid disk activity.  Trying to figure out what was going on via
  iotop and top show jbd2 and kswapd accounting for the largest load,
  but since it freezes iotop like everything else I can't tell what's
  going during the worst storms.  Googling around shows a fair number of
  other people with similar problems, most of them with multi core amd64
  systems.

  The other day I spotted this report on opensuse that looked similar
  but not identical:

  http://lists.opensuse.org/opensuse/2012-03/msg00657.html

  I booted with the grub parameter transparent_hugepage=never yesterday
  and the problem went and away and hasn't come back. I've streesed the
  system by running  a bunch of flash/java tabs in firefox, running a
  large java based stock app (ThinkorSwim) in another workspace and
  playing a 1080p 60fps movie in a third workspace.  This certainly
  causes swapping, but not freezing or stumbling.  It actually did a bit
  of swapping a minute ago while I was typing and it managed to make
  Pandora radio stumble for a moment - but that's orders of magnitude
  better than it has been.

  I think there may be a fundamental problem with how transparent
  hugepages are handled with some AMD CPUs.  I think this problem
  started when this feature was implemented and enabled by default. The
  manpage for madvise() says this was added in 2.6.38, but I don't know
  if it was enabled by default at that point.

  Hre's a partial list of things that haven't worked well in the past:

  Playing with the swappiness value: setting swappiness to very low
  values makes the problem take longer to surface, but (unsurprisinglly)
  makes it even worse once it does.

  swapoff-a ; swapon-a: this makes it go away for a while.  A
  potentially interesting thing is that as soon as I can get the system
  to act on the swapoff -a the system becomes responsive again. It pegs
  once CPU core at 100% and the HD grinds like crazy but it stops
  freezing right away.

  Moving swap from the HD to a USB thumb drive: Obviously I didn't
  expect that to be faster but wanted to see if segregating swap to a
  different device on a different bus would make it swap more smoothly -
  it didn't.

  Playing with nice and ionice priorities for jdb2, kswapd.  The fact
  that running these processes at a lower priority than anything else on
  the system makes no difference leads me to think they were just
  symptoms and not at the root of the problem.

  I think this may be a tip of the iceberg and there may be a lot of
  other having this problem.  Looking around I see a fair number of
  reports, most of them unsolved.  Some may have been fixed by just
  adding enough RAM that dirty hugepages just don't collect.  Some may
  have been fixed by chaanging filesystems - ext4 seems like something a
  lot of people with this problem have in common.

  Workaround:
  hold down the spacebar during boot in order to bring up the grub menu, edit 
the command line and add
  transparent_hugepage=never

  If this fixes the problem you can make it permanent by editing
  /etc/default/grub and adding the ransparent_hugepage=never to the
  GRUB_CMDLINE_LINUX_DEFAULT  line and then running update-grub

  Problems with this workaround:
  1) transparent hugepages should work.  This may cause a small performance hit 
in some situations and a larger hit in others.
  2) If you do this you will probably never know when or if it actually gets 
fixed.

  PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ]
  Samba Team
  SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

  is looking for bugzilla reports on this too.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  garyrich   2339 F pulseaudio
   /dev/snd/controlC1:  garyrich   2339 F pulseaudio

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

[garyr]

apport information

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

Title:
  transparent hugepages and thrashing on amd64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I seem to have found a solution to a severe
  thrashing/swapping/freezing problem that I've been having for months
  now.  I guess the real question is - should I turn it into a bug
  report and what would be useful data to include if so.

  This is a quad core AMD Phaeom system with 4G of ram, dual monitors
  and a single 1TB WD caviar black HD.  It had been behaving normally
  until something broke sometime late in the 11.x release cycle and
  continues in the current 12.04 LTS.  The symptoms are running a
  moderate load of apps (firefox with ~8 tabs, a terminal or 2, and
  aisleriot solitaire for example) and experiencing system freezes where
  the entire UI becomes totally unresponsive for 20 seconds - 5 minutes
  with solid disk activity.  Trying to figure out what was going on via
  iotop and top show jbd2 and kswapd accounting for the largest load,
  but since it freezes iotop like everything else I can't tell what's
  going during the worst storms.  Googling around shows a fair number of
  other people with similar problems, most of them with multi core amd64
  systems.

  The other day I spotted this report on opensuse that looked similar
  but not identical:

  http://lists.opensuse.org/opensuse/2012-03/msg00657.html

  I booted with the grub parameter transparent_hugepage=never yesterday
  and the problem went and away and hasn't come back. I've streesed the
  system by running  a bunch of flash/java tabs in firefox, running a
  large java based stock app (ThinkorSwim) in another workspace and
  playing a 1080p 60fps movie in a third workspace.  This certainly
  causes swapping, but not freezing or stumbling.  It actually did a bit
  of swapping a minute ago while I was typing and it managed to make
  Pandora radio stumble for a moment - but that's orders of magnitude
  better than it has been.

  I think there may be a fundamental problem with how transparent
  hugepages are handled with some AMD CPUs.  I think this problem
  started when this feature was implemented and enabled by default. The
  manpage for madvise() says this was added in 2.6.38, but I don't know
  if it was enabled by default at that point.

  Hre's a partial list of things that haven't worked well in the past:

  Playing with the swappiness value: setting swappiness to very low
  values makes the problem take longer to surface, but (unsurprisinglly)
  makes it even worse once it does.

  swapoff-a ; swapon-a: this makes it go away for a while.  A
  potentially interesting thing is that as soon as I can get the system
  to act on the swapoff -a the system becomes responsive again. It pegs
  once CPU core at 100% and the HD grinds like crazy but it stops
  freezing right away.

  Moving swap from the HD to a USB thumb drive: Obviously I didn't
  expect that to be faster but wanted to see if segregating swap to a
  different device on a different bus would make it swap more smoothly -
  it didn't.

  Playing with nice and ionice priorities for jdb2, kswapd.  The fact
  that running these processes at a lower priority than anything else on
  the system makes no difference leads me to think they were just
  symptoms and not at the root of the problem.

  I think this may be a tip of the iceberg and there may be a lot of
  other having this problem.  Looking around I see a fair number of
  reports, most of them unsolved.  Some may have been fixed by just
  adding enough RAM that dirty hugepages just don't collect.  Some may
  have been fixed by chaanging filesystems - ext4 seems like something a
  lot of people with this problem have in common.

  Workaround:
  hold down the spacebar during boot in order to bring up the grub menu, edit 
the command line and add
  transparent_hugepage=never

  If this fixes the problem you can make it permanent by editing
  /etc/default/grub and adding the ransparent_hugepage=never to the
  GRUB_CMDLINE_LINUX_DEFAULT  line and then running update-grub

  Problems with this workaround:
  1) transparent hugepages should work.  This may cause a small performance hit 
in some situations and a larger hit in others.
  2) If you do this you will probably never know when or if it actually gets 
fixed.

  PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ]
  Samba Team
  SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

  is looking for bugzilla reports on this too.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  garyrich   2339 F pulseaudio
   /dev/snd/controlC1:  garyrich   2339 F pulseaudio
  

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

[garyr]

apport information

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

Title:
  transparent hugepages and thrashing on amd64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I seem to have found a solution to a severe
  thrashing/swapping/freezing problem that I've been having for months
  now.  I guess the real question is - should I turn it into a bug
  report and what would be useful data to include if so.

  This is a quad core AMD Phaeom system with 4G of ram, dual monitors
  and a single 1TB WD caviar black HD.  It had been behaving normally
  until something broke sometime late in the 11.x release cycle and
  continues in the current 12.04 LTS.  The symptoms are running a
  moderate load of apps (firefox with ~8 tabs, a terminal or 2, and
  aisleriot solitaire for example) and experiencing system freezes where
  the entire UI becomes totally unresponsive for 20 seconds - 5 minutes
  with solid disk activity.  Trying to figure out what was going on via
  iotop and top show jbd2 and kswapd accounting for the largest load,
  but since it freezes iotop like everything else I can't tell what's
  going during the worst storms.  Googling around shows a fair number of
  other people with similar problems, most of them with multi core amd64
  systems.

  The other day I spotted this report on opensuse that looked similar
  but not identical:

  http://lists.opensuse.org/opensuse/2012-03/msg00657.html

  I booted with the grub parameter transparent_hugepage=never yesterday
  and the problem went and away and hasn't come back. I've streesed the
  system by running  a bunch of flash/java tabs in firefox, running a
  large java based stock app (ThinkorSwim) in another workspace and
  playing a 1080p 60fps movie in a third workspace.  This certainly
  causes swapping, but not freezing or stumbling.  It actually did a bit
  of swapping a minute ago while I was typing and it managed to make
  Pandora radio stumble for a moment - but that's orders of magnitude
  better than it has been.

  I think there may be a fundamental problem with how transparent
  hugepages are handled with some AMD CPUs.  I think this problem
  started when this feature was implemented and enabled by default. The
  manpage for madvise() says this was added in 2.6.38, but I don't know
  if it was enabled by default at that point.

  Hre's a partial list of things that haven't worked well in the past:

  Playing with the swappiness value: setting swappiness to very low
  values makes the problem take longer to surface, but (unsurprisinglly)
  makes it even worse once it does.

  swapoff-a ; swapon-a: this makes it go away for a while.  A
  potentially interesting thing is that as soon as I can get the system
  to act on the swapoff -a the system becomes responsive again. It pegs
  once CPU core at 100% and the HD grinds like crazy but it stops
  freezing right away.

  Moving swap from the HD to a USB thumb drive: Obviously I didn't
  expect that to be faster but wanted to see if segregating swap to a
  different device on a different bus would make it swap more smoothly -
  it didn't.

  Playing with nice and ionice priorities for jdb2, kswapd.  The fact
  that running these processes at a lower priority than anything else on
  the system makes no difference leads me to think they were just
  symptoms and not at the root of the problem.

  I think this may be a tip of the iceberg and there may be a lot of
  other having this problem.  Looking around I see a fair number of
  reports, most of them unsolved.  Some may have been fixed by just
  adding enough RAM that dirty hugepages just don't collect.  Some may
  have been fixed by chaanging filesystems - ext4 seems like something a
  lot of people with this problem have in common.

  Workaround:
  hold down the spacebar during boot in order to bring up the grub menu, edit 
the command line and add
  transparent_hugepage=never

  If this fixes the problem you can make it permanent by editing
  /etc/default/grub and adding the ransparent_hugepage=never to the
  GRUB_CMDLINE_LINUX_DEFAULT  line and then running update-grub

  Problems with this workaround:
  1) transparent hugepages should work.  This may cause a small performance hit 
in some situations and a larger hit in others.
  2) If you do this you will probably never know when or if it actually gets 
fixed.

  PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ]
  Samba Team
  SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

  is looking for bugzilla reports on this too.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  garyrich   2339 F pulseaudio
   /dev/snd/controlC1:  garyrich   2339 F pulseaudio
  

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

[garyr]

apport information

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

Title:
  transparent hugepages and thrashing on amd64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I seem to have found a solution to a severe
  thrashing/swapping/freezing problem that I've been having for months
  now.  I guess the real question is - should I turn it into a bug
  report and what would be useful data to include if so.

  This is a quad core AMD Phaeom system with 4G of ram, dual monitors
  and a single 1TB WD caviar black HD.  It had been behaving normally
  until something broke sometime late in the 11.x release cycle and
  continues in the current 12.04 LTS.  The symptoms are running a
  moderate load of apps (firefox with ~8 tabs, a terminal or 2, and
  aisleriot solitaire for example) and experiencing system freezes where
  the entire UI becomes totally unresponsive for 20 seconds - 5 minutes
  with solid disk activity.  Trying to figure out what was going on via
  iotop and top show jbd2 and kswapd accounting for the largest load,
  but since it freezes iotop like everything else I can't tell what's
  going during the worst storms.  Googling around shows a fair number of
  other people with similar problems, most of them with multi core amd64
  systems.

  The other day I spotted this report on opensuse that looked similar
  but not identical:

  http://lists.opensuse.org/opensuse/2012-03/msg00657.html

  I booted with the grub parameter transparent_hugepage=never yesterday
  and the problem went and away and hasn't come back. I've streesed the
  system by running  a bunch of flash/java tabs in firefox, running a
  large java based stock app (ThinkorSwim) in another workspace and
  playing a 1080p 60fps movie in a third workspace.  This certainly
  causes swapping, but not freezing or stumbling.  It actually did a bit
  of swapping a minute ago while I was typing and it managed to make
  Pandora radio stumble for a moment - but that's orders of magnitude
  better than it has been.

  I think there may be a fundamental problem with how transparent
  hugepages are handled with some AMD CPUs.  I think this problem
  started when this feature was implemented and enabled by default. The
  manpage for madvise() says this was added in 2.6.38, but I don't know
  if it was enabled by default at that point.

  Hre's a partial list of things that haven't worked well in the past:

  Playing with the swappiness value: setting swappiness to very low
  values makes the problem take longer to surface, but (unsurprisinglly)
  makes it even worse once it does.

  swapoff-a ; swapon-a: this makes it go away for a while.  A
  potentially interesting thing is that as soon as I can get the system
  to act on the swapoff -a the system becomes responsive again. It pegs
  once CPU core at 100% and the HD grinds like crazy but it stops
  freezing right away.

  Moving swap from the HD to a USB thumb drive: Obviously I didn't
  expect that to be faster but wanted to see if segregating swap to a
  different device on a different bus would make it swap more smoothly -
  it didn't.

  Playing with nice and ionice priorities for jdb2, kswapd.  The fact
  that running these processes at a lower priority than anything else on
  the system makes no difference leads me to think they were just
  symptoms and not at the root of the problem.

  I think this may be a tip of the iceberg and there may be a lot of
  other having this problem.  Looking around I see a fair number of
  reports, most of them unsolved.  Some may have been fixed by just
  adding enough RAM that dirty hugepages just don't collect.  Some may
  have been fixed by chaanging filesystems - ext4 seems like something a
  lot of people with this problem have in common.

  Workaround:
  hold down the spacebar during boot in order to bring up the grub menu, edit 
the command line and add
  transparent_hugepage=never

  If this fixes the problem you can make it permanent by editing
  /etc/default/grub and adding the ransparent_hugepage=never to the
  GRUB_CMDLINE_LINUX_DEFAULT  line and then running update-grub

  Problems with this workaround:
  1) transparent hugepages should work.  This may cause a small performance hit 
in some situations and a larger hit in others.
  2) If you do this you will probably never know when or if it actually gets 
fixed.

  PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ]
  Samba Team
  SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

  is looking for bugzilla reports on this too.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  garyrich   2339 F pulseaudio
   /dev/snd/controlC1:  garyrich   2339 F pulseaudio

[Kernel-packages] [Bug 1013807] ProcInterrupts.txt

[garyr]

apport information

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

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

Title:
  transparent hugepages and thrashing on amd64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I seem to have found a solution to a severe
  thrashing/swapping/freezing problem that I've been having for months
  now.  I guess the real question is - should I turn it into a bug
  report and what would be useful data to include if so.

  This is a quad core AMD Phaeom system with 4G of ram, dual monitors
  and a single 1TB WD caviar black HD.  It had been behaving normally
  until something broke sometime late in the 11.x release cycle and
  continues in the current 12.04 LTS.  The symptoms are running a
  moderate load of apps (firefox with ~8 tabs, a terminal or 2, and
  aisleriot solitaire for example) and experiencing system freezes where
  the entire UI becomes totally unresponsive for 20 seconds - 5 minutes
  with solid disk activity.  Trying to figure out what was going on via
  iotop and top show jbd2 and kswapd accounting for the largest load,
  but since it freezes iotop like everything else I can't tell what's
  going during the worst storms.  Googling around shows a fair number of
  other people with similar problems, most of them with multi core amd64
  systems.

  The other day I spotted this report on opensuse that looked similar
  but not identical:

  http://lists.opensuse.org/opensuse/2012-03/msg00657.html

  I booted with the grub parameter transparent_hugepage=never yesterday
  and the problem went and away and hasn't come back. I've streesed the
  system by running  a bunch of flash/java tabs in firefox, running a
  large java based stock app (ThinkorSwim) in another workspace and
  playing a 1080p 60fps movie in a third workspace.  This certainly
  causes swapping, but not freezing or stumbling.  It actually did a bit
  of swapping a minute ago while I was typing and it managed to make
  Pandora radio stumble for a moment - but that's orders of magnitude
  better than it has been.

  I think there may be a fundamental problem with how transparent
  hugepages are handled with some AMD CPUs.  I think this problem
  started when this feature was implemented and enabled by default. The
  manpage for madvise() says this was added in 2.6.38, but I don't know
  if it was enabled by default at that point.

  Hre's a partial list of things that haven't worked well in the past:

  Playing with the swappiness value: setting swappiness to very low
  values makes the problem take longer to surface, but (unsurprisinglly)
  makes it even worse once it does.

  swapoff-a ; swapon-a: this makes it go away for a while.  A
  potentially interesting thing is that as soon as I can get the system
  to act on the swapoff -a the system becomes responsive again. It pegs
  once CPU core at 100% and the HD grinds like crazy but it stops
  freezing right away.

  Moving swap from the HD to a USB thumb drive: Obviously I didn't
  expect that to be faster but wanted to see if segregating swap to a
  different device on a different bus would make it swap more smoothly -
  it didn't.

  Playing with nice and ionice priorities for jdb2, kswapd.  The fact
  that running these processes at a lower priority than anything else on
  the system makes no difference leads me to think they were just
  symptoms and not at the root of the problem.

  I think this may be a tip of the iceberg and there may be a lot of
  other having this problem.  Looking around I see a fair number of
  reports, most of them unsolved.  Some may have been fixed by just
  adding enough RAM that dirty hugepages just don't collect.  Some may
  have been fixed by chaanging filesystems - ext4 seems like something a
  lot of people with this problem have in common.

  Workaround:
  hold down the spacebar during boot in order to bring up the grub menu, edit 
the command line and add
  transparent_hugepage=never

  If this fixes the problem you can make it permanent by editing
  /etc/default/grub and adding the ransparent_hugepage=never to the
  GRUB_CMDLINE_LINUX_DEFAULT  line and then running update-grub

  Problems with this workaround:
  1) transparent hugepages should work.  This may cause a small performance hit 
in some situations and a larger hit in others.
  2) If you do this you will probably never know when or if it actually gets 
fixed.

  PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ]
  Samba Team
  SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

  is looking for bugzilla reports on this too.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  garyrich   2339 F pulseaudio
   /dev/snd/controlC1:  garyrich   2339 F 

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

[garyr]

apport information

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

Title:
  transparent hugepages and thrashing on amd64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I seem to have found a solution to a severe
  thrashing/swapping/freezing problem that I've been having for months
  now.  I guess the real question is - should I turn it into a bug
  report and what would be useful data to include if so.

  This is a quad core AMD Phaeom system with 4G of ram, dual monitors
  and a single 1TB WD caviar black HD.  It had been behaving normally
  until something broke sometime late in the 11.x release cycle and
  continues in the current 12.04 LTS.  The symptoms are running a
  moderate load of apps (firefox with ~8 tabs, a terminal or 2, and
  aisleriot solitaire for example) and experiencing system freezes where
  the entire UI becomes totally unresponsive for 20 seconds - 5 minutes
  with solid disk activity.  Trying to figure out what was going on via
  iotop and top show jbd2 and kswapd accounting for the largest load,
  but since it freezes iotop like everything else I can't tell what's
  going during the worst storms.  Googling around shows a fair number of
  other people with similar problems, most of them with multi core amd64
  systems.

  The other day I spotted this report on opensuse that looked similar
  but not identical:

  http://lists.opensuse.org/opensuse/2012-03/msg00657.html

  I booted with the grub parameter transparent_hugepage=never yesterday
  and the problem went and away and hasn't come back. I've streesed the
  system by running  a bunch of flash/java tabs in firefox, running a
  large java based stock app (ThinkorSwim) in another workspace and
  playing a 1080p 60fps movie in a third workspace.  This certainly
  causes swapping, but not freezing or stumbling.  It actually did a bit
  of swapping a minute ago while I was typing and it managed to make
  Pandora radio stumble for a moment - but that's orders of magnitude
  better than it has been.

  I think there may be a fundamental problem with how transparent
  hugepages are handled with some AMD CPUs.  I think this problem
  started when this feature was implemented and enabled by default. The
  manpage for madvise() says this was added in 2.6.38, but I don't know
  if it was enabled by default at that point.

  Hre's a partial list of things that haven't worked well in the past:

  Playing with the swappiness value: setting swappiness to very low
  values makes the problem take longer to surface, but (unsurprisinglly)
  makes it even worse once it does.

  swapoff-a ; swapon-a: this makes it go away for a while.  A
  potentially interesting thing is that as soon as I can get the system
  to act on the swapoff -a the system becomes responsive again. It pegs
  once CPU core at 100% and the HD grinds like crazy but it stops
  freezing right away.

  Moving swap from the HD to a USB thumb drive: Obviously I didn't
  expect that to be faster but wanted to see if segregating swap to a
  different device on a different bus would make it swap more smoothly -
  it didn't.

  Playing with nice and ionice priorities for jdb2, kswapd.  The fact
  that running these processes at a lower priority than anything else on
  the system makes no difference leads me to think they were just
  symptoms and not at the root of the problem.

  I think this may be a tip of the iceberg and there may be a lot of
  other having this problem.  Looking around I see a fair number of
  reports, most of them unsolved.  Some may have been fixed by just
  adding enough RAM that dirty hugepages just don't collect.  Some may
  have been fixed by chaanging filesystems - ext4 seems like something a
  lot of people with this problem have in common.

  Workaround:
  hold down the spacebar during boot in order to bring up the grub menu, edit 
the command line and add
  transparent_hugepage=never

  If this fixes the problem you can make it permanent by editing
  /etc/default/grub and adding the ransparent_hugepage=never to the
  GRUB_CMDLINE_LINUX_DEFAULT  line and then running update-grub

  Problems with this workaround:
  1) transparent hugepages should work.  This may cause a small performance hit 
in some situations and a larger hit in others.
  2) If you do this you will probably never know when or if it actually gets 
fixed.

  PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ]
  Samba Team
  SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

  is looking for bugzilla reports on this too.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  garyrich   2339 F pulseaudio
   /dev/snd/controlC1:  garyrich   2339 F 

[Kernel-packages] [Bug 1524122] Re: XPS 15 (9550) Won't boot with 4.4

[Alberto Salvia Novella]

** Bug watch added: Linux Kernel Bug Tracker #108981
   http://bugzilla.kernel.org/show_bug.cgi?id=108981

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

** Description changed:

  Neither 4.4rc3 nor 4.3rc4 will boot on my Dell XPS 15 (9550).  4.3 boots
  fine.
  
  The boot process halts with "ALERT! /dev/disk/by-uuid/ does not
  exist", although the UUID does exist, and other kernels boot fine.
  
  I'm attaching a screenshot of the console boot log.  I apologize that it
  is hard to read, because my screen is 3840x2160 and each line is less
  that 2mm high.
  
  Here's my grub stanza:
  
- load_video
- gfxmode $linux_gfx_mode
- insmod gzio
- if [ x$grub_platform = xxen ]; then insmod xzio; insmod 
lzopio; fi
- insmod part_gpt
- insmod ext2
- if [ x$feature_platform_search_hint = xy ]; then
-   search --no-floppy --fs-uuid --set=root  
7e2ed448-28a7-465e-a5b0-58db19b2711a
- else
-   search --no-floppy --fs-uuid --set=root 
7e2ed448-28a7-465e-a5b0-58db19b2711a
- fi
- echo'Loading Linux 4.4.0-040400rc4-generic ...'
- linux   /boot/vmlinuz-4.4.0-040400rc4-generic 
root=UUID=7e2ed448-28a7-465e-a5b0-58db19b2711a ro  quiet splash 
i915.preliminary_hw_support=1 i915.enable_ips=0 $vt_handoff
- echo'Loading initial ramdisk ...'
- initrd  /boot/initrd.img-4.4.0-040400rc4-generic
+ load_video
+ gfxmode $linux_gfx_mode
+ insmod gzio
+ if [ x$grub_platform = xxen ]; then insmod xzio; insmod 
lzopio; fi
+ insmod part_gpt
+ insmod ext2
+ if [ x$feature_platform_search_hint = xy ]; then
+   search --no-floppy --fs-uuid --set=root  
7e2ed448-28a7-465e-a5b0-58db19b2711a
+ else
+   search --no-floppy --fs-uuid --set=root 
7e2ed448-28a7-465e-a5b0-58db19b2711a
+ fi
+ echo'Loading Linux 4.4.0-040400rc4-generic ...'
+ linux   /boot/vmlinuz-4.4.0-040400rc4-generic 
root=UUID=7e2ed448-28a7-465e-a5b0-58db19b2711a ro  quiet splash 
i915.preliminary_hw_support=1 i915.enable_ips=0 $vt_handoff
+ echo'Loading initial ramdisk ...'
+ initrd  /boot/initrd.img-4.4.0-040400rc4-generic
  
  Possibly related is the following warning when i update-initramfs:
  
  $ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-4.4.0-040400rc4-generic
  W: Possible missing firmware /lib/firmware/i915/skl_guc_ver4.bin for module 
i915
  
- I have also reported this bug upstream:
- https://bugzilla.kernel.org/show_bug.cgi?id=108981
- 
  Please let me know what other info would be helpful.  Thanks!
- --- 
+ ---
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2015-11-18 (20 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Package: linux (not installed)
  Tags:  wily
  Uname: Linux 4.3.0-040300-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users video 
wireshark
  _MarkForUpload: True

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

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

Title:
   XPS 15 (9550) Won't boot with 4.4

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

Bug description:
  Neither 4.4rc3 nor 4.3rc4 will boot on my Dell XPS 15 (9550).  4.3
  boots fine.

  The boot process halts with "ALERT! /dev/disk/by-uuid/ does not
  exist", although the UUID does exist, and other kernels boot fine.

  I'm attaching a screenshot of the console boot log.  I apologize that
  it is hard to read, because my screen is 3840x2160 and each line is
  less that 2mm high.

  Here's my grub stanza:

  load_video
  gfxmode $linux_gfx_mode
  insmod gzio
  if [ x$grub_platform = xxen ]; then insmod xzio; insmod 
lzopio; fi
  insmod part_gpt
  insmod ext2
  if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root  
7e2ed448-28a7-465e-a5b0-58db19b2711a
  else
    search --no-floppy --fs-uuid --set=root 
7e2ed448-28a7-465e-a5b0-58db19b2711a
  fi
  echo'Loading Linux 4.4.0-040400rc4-generic ...'
  

[Kernel-packages] [Bug 1525008] Re: Ubuntu doesn't boot after laptop runs out of battery

[Alberto Salvia Novella]

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

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

Title:
  Ubuntu doesn't boot after laptop runs out of battery

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  If my laptop runs out of battery, the next time I start it up and put
  in my disk password, I get a black screen that goes nowhere. I always
  have to hard-reset the laptop in order for the OS to load after I put
  in the disk password.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vadi   2571 F pulseaudio
   /dev/snd/controlC0:  vadi   2571 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Dec 11 08:42:12 2015
  HibernationDevice: RESUME=UUID=745d185e-0cf7-47d5-8900-9f89f21b1af8
  InstallationDate: Installed on 2014-06-26 (531 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP ZBook 14
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2015-10-26 (44 days ago)
  dmi.bios.date: 04/29/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.11
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.54
  dmi.chassis.asset.tag: CNU424B3ZZ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.11:bd04/29/2014:svnHewlett-Packard:pnHPZBook14:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.54:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ZBook 14
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525008/+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 1519897] Re: [Hyper-V] hv: vmbus: Fix a host signaling bug

[Joseph Salisbury]

The patch is actually already in Vivid due to bug 1508706 .

** Changed in: linux (Ubuntu Vivid)
   Status: Triaged => 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/1519897

Title:
  [Hyper-V] hv: vmbus: Fix a host signaling bug

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  The following fix has been submitted upstream, but has high enough
  severity that we would like early inclusion into the Ubuntu kernel.
  Please consider for wily, vivid, and trusty (and the HWE kernels for
  the same).

  Patch follows:

  Currently we have two policies for deciding when to signal the host:
  One based on the ring buffer state and the other based on what the VMBUS 
client driver wants to do. Consider the case when the client wants to 
explicitly control when to signal the host. In this case, if the client were to 
defer signaling, we will not be able to signal the host subsequently when the 
client does want to signal since the ring buffer state will prevent the 
signaling. Implement logic to have only one signaling policy in force for a 
given channel.

  Signed-off-by: K. Y. Srinivasan 
  Reviewed-by: Haiyang Zhang 
  Tested-by: Haiyang Zhang 
  Cc:  # v4.2+
  ---
   drivers/hv/channel.c   |   18 ++
   include/linux/hyperv.h |   12 
   2 files changed, 30 insertions(+), 0 deletions(-)

  diff --git a/drivers/hv/channel.c b/drivers/hv/channel.c index 
77d2579..c6278c7 100644
  --- a/drivers/hv/channel.c
  +++ b/drivers/hv/channel.c
  @@ -653,10 +653,19 @@ int vmbus_sendpacket_ctl(struct vmbus_channel *channel, 
void *buffer,
     *on the ring. We will not signal if more data is
     *to be placed.
     *
  +  * Based on the channel signal state, we will decide
  +  * which signaling policy will be applied.
  +  *
     * If we cannot write to the ring-buffer; signal the host
     * even if we may not have written anything. This is a rare
     * enough condition that it should not matter.
     */
  +
  + if (channel->signal_state)
  + signal = true;
  + else
  + kick_q = true;
  +
    if (((ret == 0) && kick_q && signal) || (ret))
     vmbus_setevent(channel);

  @@ -756,10 +765,19 @@ int vmbus_sendpacket_pagebuffer_ctl(struct 
vmbus_channel *channel,
     *on the ring. We will not signal if more data is
     *to be placed.
     *
  +  * Based on the channel signal state, we will decide
  +  * which signaling policy will be applied.
  +  *
     * If we cannot write to the ring-buffer; signal the host
     * even if we may not have written anything. This is a rare
     * enough condition that it should not matter.
     */
  +
  + if (channel->signal_state)
  + signal = true;
  + else
  + kick_q = true;
  +
    if (((ret == 0) && kick_q && signal) || (ret))
     vmbus_setevent(channel);

  diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h index 
437c9c8..7b1af52 100644
  --- a/include/linux/hyperv.h
  +++ b/include/linux/hyperv.h
  @@ -756,8 +756,20 @@ struct vmbus_channel {
     * link up channels based on their CPU affinity.
     */
    struct list_head percpu_list;
  + /*
  +  * Host signaling policy: The default policy will be
  +  * based on the ring buffer state. We will also support
  +  * a policy where the client driver can have explicit
  +  * signaling control.
  +  */
  + bool signal_state;
   };

  +static inline void set_channel_signal_state(struct vmbus_channel *c,
  +bool state) {
  + c->signal_state = state;
  +}
  +
   static inline void set_channel_read_state(struct vmbus_channel *c, bool 
state)  {
    c->batched_reading = state;
  --
  1.7.4.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1519897/+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 1524167] Re: Computer freezes since 15.10 upgrade

[Alberto Salvia Novella]

It happened to me three times, and in my case looked like an xorg
freeze.

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

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  Computer freezes since 15.10 upgrade

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Machine freezes randomly. No crash logs or anything in syslog. Not
  enough know-how to figure it out.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-21-generic 4.2.0-21.25
  ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6
  Uname: Linux 4.2.0-21-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jd 2303 F pulseaudio
  Date: Tue Dec  8 22:23:17 2015
  HibernationDevice: RESUME=UUID=97af6a20-8cf6-48bb-a4a4-20d55865a2e3
  MachineType: Acer Aspire ES1-512
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic.efi.signed 
root=UUID=af5dae25-82ce-4518-83af-ee2f6e077b25 ro recovery nomodeset
  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-4.2.0-21-generic N/A
   linux-backports-modules-4.2.0-21-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2015-11-01 (37 days ago)
  dmi.bios.date: 09/11/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Aspire ES1-512
  dmi.board.vendor: Acer
  dmi.board.version: V1.07
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.07
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.07:bd09/11/2014:svnAcer:pnAspireES1-512:pvrV1.07:rvnAcer:rnAspireES1-512:rvrV1.07:cvnAcer:ct10:cvrV1.07:
  dmi.product.name: Aspire ES1-512
  dmi.product.version: V1.07
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1524167/+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 1013807] [NEW] transparent hugepages and thrashing on amd64

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I seem to have found a solution to a severe thrashing/swapping/freezing
problem that I've been having for months now.  I guess the real question
is - should I turn it into a bug report and what would be useful data to
include if so.

This is a quad core AMD Phaeom system with 4G of ram, dual monitors and
a single 1TB WD caviar black HD.  It had been behaving normally until
something broke sometime late in the 11.x release cycle and continues in
the current 12.04 LTS.  The symptoms are running a moderate load of apps
(firefox with ~8 tabs, a terminal or 2, and aisleriot solitaire for
example) and experiencing system freezes where the entire UI becomes
totally unresponsive for 20 seconds - 5 minutes with solid disk
activity.  Trying to figure out what was going on via iotop and top show
jbd2 and kswapd accounting for the largest load, but since it freezes
iotop like everything else I can't tell what's going during the worst
storms.  Googling around shows a fair number of other people with
similar problems, most of them with multi core amd64 systems.

The other day I spotted this report on opensuse that looked similar but
not identical:

http://lists.opensuse.org/opensuse/2012-03/msg00657.html

I booted with the grub parameter transparent_hugepage=never yesterday
and the problem went and away and hasn't come back. I've streesed the
system by running  a bunch of flash/java tabs in firefox, running a
large java based stock app (ThinkorSwim) in another workspace and
playing a 1080p 60fps movie in a third workspace.  This certainly causes
swapping, but not freezing or stumbling.  It actually did a bit of
swapping a minute ago while I was typing and it managed to make Pandora
radio stumble for a moment - but that's orders of magnitude better than
it has been.

I think there may be a fundamental problem with how transparent
hugepages are handled with some AMD CPUs.  I think this problem started
when this feature was implemented and enabled by default. The manpage
for madvise() says this was added in 2.6.38, but I don't know if it was
enabled by default at that point.

Hre's a partial list of things that haven't worked well in the past:

Playing with the swappiness value: setting swappiness to very low values
makes the problem take longer to surface, but (unsurprisinglly) makes it
even worse once it does.

swapoff-a ; swapon-a: this makes it go away for a while.  A potentially
interesting thing is that as soon as I can get the system to act on the
swapoff -a the system becomes responsive again. It pegs once CPU core at
100% and the HD grinds like crazy but it stops freezing right away.

Moving swap from the HD to a USB thumb drive: Obviously I didn't expect
that to be faster but wanted to see if segregating swap to a different
device on a different bus would make it swap more smoothly - it didn't.

Playing with nice and ionice priorities for jdb2, kswapd.  The fact that
running these processes at a lower priority than anything else on the
system makes no difference leads me to think they were just symptoms and
not at the root of the problem.

I think this may be a tip of the iceberg and there may be a lot of other
having this problem.  Looking around I see a fair number of reports,
most of them unsolved.  Some may have been fixed by just adding enough
RAM that dirty hugepages just don't collect.  Some may have been fixed
by chaanging filesystems - ext4 seems like something a lot of people
with this problem have in common.

Workaround:
hold down the spacebar during boot in order to bring up the grub menu, edit the 
command line and add
transparent_hugepage=never

If this fixes the problem you can make it permanent by editing
/etc/default/grub and adding the ransparent_hugepage=never to the
GRUB_CMDLINE_LINUX_DEFAULT  line and then running update-grub

Problems with this workaround:
1) transparent hugepages should work.  This may cause a small performance hit 
in some situations and a larger hit in others.
2) If you do this you will probably never know when or if it actually gets 
fixed.

PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ]
Samba Team
SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

is looking for bugzilla reports on this too.

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


** Tags: bot-comment
-- 
transparent hugepages and thrashing on amd64
https://bugs.launchpad.net/bugs/1013807
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 1013807] Re: transparent hugepages and thrashing on amd64

[Geoffrey Thomas]

Since you seem to be using transparent hugepages and not libhugetlbfs
(LD_PRELOAD=libhugetlbfs.so), I'm going to reassign this bug to the
Linux kernel package.

(It's also entirely possible this bug got solved in the last 3 years, to
be fair)

** Package changed: libhugetlbfs (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/1013807

Title:
  transparent hugepages and thrashing on amd64

Status in linux package in Ubuntu:
  New

Bug description:
  I seem to have found a solution to a severe
  thrashing/swapping/freezing problem that I've been having for months
  now.  I guess the real question is - should I turn it into a bug
  report and what would be useful data to include if so.

  This is a quad core AMD Phaeom system with 4G of ram, dual monitors
  and a single 1TB WD caviar black HD.  It had been behaving normally
  until something broke sometime late in the 11.x release cycle and
  continues in the current 12.04 LTS.  The symptoms are running a
  moderate load of apps (firefox with ~8 tabs, a terminal or 2, and
  aisleriot solitaire for example) and experiencing system freezes where
  the entire UI becomes totally unresponsive for 20 seconds - 5 minutes
  with solid disk activity.  Trying to figure out what was going on via
  iotop and top show jbd2 and kswapd accounting for the largest load,
  but since it freezes iotop like everything else I can't tell what's
  going during the worst storms.  Googling around shows a fair number of
  other people with similar problems, most of them with multi core amd64
  systems.

  The other day I spotted this report on opensuse that looked similar
  but not identical:

  http://lists.opensuse.org/opensuse/2012-03/msg00657.html

  I booted with the grub parameter transparent_hugepage=never yesterday
  and the problem went and away and hasn't come back. I've streesed the
  system by running  a bunch of flash/java tabs in firefox, running a
  large java based stock app (ThinkorSwim) in another workspace and
  playing a 1080p 60fps movie in a third workspace.  This certainly
  causes swapping, but not freezing or stumbling.  It actually did a bit
  of swapping a minute ago while I was typing and it managed to make
  Pandora radio stumble for a moment - but that's orders of magnitude
  better than it has been.

  I think there may be a fundamental problem with how transparent
  hugepages are handled with some AMD CPUs.  I think this problem
  started when this feature was implemented and enabled by default. The
  manpage for madvise() says this was added in 2.6.38, but I don't know
  if it was enabled by default at that point.

  Hre's a partial list of things that haven't worked well in the past:

  Playing with the swappiness value: setting swappiness to very low
  values makes the problem take longer to surface, but (unsurprisinglly)
  makes it even worse once it does.

  swapoff-a ; swapon-a: this makes it go away for a while.  A
  potentially interesting thing is that as soon as I can get the system
  to act on the swapoff -a the system becomes responsive again. It pegs
  once CPU core at 100% and the HD grinds like crazy but it stops
  freezing right away.

  Moving swap from the HD to a USB thumb drive: Obviously I didn't
  expect that to be faster but wanted to see if segregating swap to a
  different device on a different bus would make it swap more smoothly -
  it didn't.

  Playing with nice and ionice priorities for jdb2, kswapd.  The fact
  that running these processes at a lower priority than anything else on
  the system makes no difference leads me to think they were just
  symptoms and not at the root of the problem.

  I think this may be a tip of the iceberg and there may be a lot of
  other having this problem.  Looking around I see a fair number of
  reports, most of them unsolved.  Some may have been fixed by just
  adding enough RAM that dirty hugepages just don't collect.  Some may
  have been fixed by chaanging filesystems - ext4 seems like something a
  lot of people with this problem have in common.

  Workaround:
  hold down the spacebar during boot in order to bring up the grub menu, edit 
the command line and add
  transparent_hugepage=never

  If this fixes the problem you can make it permanent by editing
  /etc/default/grub and adding the ransparent_hugepage=never to the
  GRUB_CMDLINE_LINUX_DEFAULT  line and then running update-grub

  Problems with this workaround:
  1) transparent hugepages should work.  This may cause a small performance hit 
in some situations and a larger hit in others.
  2) If you do this you will probably never know when or if it actually gets 
fixed.

  PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ]
  Samba Team
  SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

  is looking for bugzilla reports on this too.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1013807] Missing required logs.

[Brad Figg]

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

apport-collect 1013807

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

Title:
  transparent hugepages and thrashing on amd64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I seem to have found a solution to a severe
  thrashing/swapping/freezing problem that I've been having for months
  now.  I guess the real question is - should I turn it into a bug
  report and what would be useful data to include if so.

  This is a quad core AMD Phaeom system with 4G of ram, dual monitors
  and a single 1TB WD caviar black HD.  It had been behaving normally
  until something broke sometime late in the 11.x release cycle and
  continues in the current 12.04 LTS.  The symptoms are running a
  moderate load of apps (firefox with ~8 tabs, a terminal or 2, and
  aisleriot solitaire for example) and experiencing system freezes where
  the entire UI becomes totally unresponsive for 20 seconds - 5 minutes
  with solid disk activity.  Trying to figure out what was going on via
  iotop and top show jbd2 and kswapd accounting for the largest load,
  but since it freezes iotop like everything else I can't tell what's
  going during the worst storms.  Googling around shows a fair number of
  other people with similar problems, most of them with multi core amd64
  systems.

  The other day I spotted this report on opensuse that looked similar
  but not identical:

  http://lists.opensuse.org/opensuse/2012-03/msg00657.html

  I booted with the grub parameter transparent_hugepage=never yesterday
  and the problem went and away and hasn't come back. I've streesed the
  system by running  a bunch of flash/java tabs in firefox, running a
  large java based stock app (ThinkorSwim) in another workspace and
  playing a 1080p 60fps movie in a third workspace.  This certainly
  causes swapping, but not freezing or stumbling.  It actually did a bit
  of swapping a minute ago while I was typing and it managed to make
  Pandora radio stumble for a moment - but that's orders of magnitude
  better than it has been.

  I think there may be a fundamental problem with how transparent
  hugepages are handled with some AMD CPUs.  I think this problem
  started when this feature was implemented and enabled by default. The
  manpage for madvise() says this was added in 2.6.38, but I don't know
  if it was enabled by default at that point.

  Hre's a partial list of things that haven't worked well in the past:

  Playing with the swappiness value: setting swappiness to very low
  values makes the problem take longer to surface, but (unsurprisinglly)
  makes it even worse once it does.

  swapoff-a ; swapon-a: this makes it go away for a while.  A
  potentially interesting thing is that as soon as I can get the system
  to act on the swapoff -a the system becomes responsive again. It pegs
  once CPU core at 100% and the HD grinds like crazy but it stops
  freezing right away.

  Moving swap from the HD to a USB thumb drive: Obviously I didn't
  expect that to be faster but wanted to see if segregating swap to a
  different device on a different bus would make it swap more smoothly -
  it didn't.

  Playing with nice and ionice priorities for jdb2, kswapd.  The fact
  that running these processes at a lower priority than anything else on
  the system makes no difference leads me to think they were just
  symptoms and not at the root of the problem.

  I think this may be a tip of the iceberg and there may be a lot of
  other having this problem.  Looking around I see a fair number of
  reports, most of them unsolved.  Some may have been fixed by just
  adding enough RAM that dirty hugepages just don't collect.  Some may
  have been fixed by chaanging filesystems - ext4 seems like something a
  lot of people with this problem have in common.

  Workaround:
  hold down the spacebar during boot in order to bring up the grub menu, edit 
the command line and add
  transparent_hugepage=never

  If this fixes the problem you can make it permanent by editing
  /etc/default/grub and adding the ransparent_hugepage=never to the
  GRUB_CMDLINE_LINUX_DEFAULT  line and then running update-grub

  Problems with this workaround:
  1) transparent hugepages should work.  This may cause a small performance hit 
in some situations and a larger hit in others.
  2) If you do this you will probably never know when or if it actually gets 
fixed.

  PS: Lars 

[Kernel-packages] [Bug 1525061] Re: linux-headers-4.3.0-2 have unstable to connect in Acer Aspire 4740 after close the lid.

[Alberto Salvia Novella]

Please:

1. Edit the bug so it is clear what becomes unstable.
2. Set this bug status back to "confirmed".

Thank you.

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

Title:
  linux-headers-4.3.0-2 have unstable to connect in Acer Aspire 4740
  after close the lid.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  linux-headers-4.3.0-2 have unstable to connect in Acer Aspire 4740
  after close the lid.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-headers-4.3.0-2 4.3.0-2.11
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic i686
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sumate 2095 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Dec 11 11:20:28 2015
  HibernationDevice: RESUME=UUID=fddd00e8-74d2-41b5-9315-8ef84a5fc982
  InstallationDate: Installed on 2011-01-30 (1775 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  MachineType: Acer Aspire 4740
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-2-generic 
root=UUID=974de5d6-f5a0-47e0-badd-13eb79a5ba69 ro quiet splash acpi_osi=Linux 
acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.3.0-2-generic N/A
   linux-backports-modules-4.3.0-2-generic  N/A
   linux-firmware   1.154
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2015-10-29 (42 days ago)
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire 4740
  dmi.board.vendor: Acer
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.modalias: 
dmi:bvnAcer:bvrV1.10:bd10/20/2010:svnAcer:pnAspire4740:pvrV1.10:rvnAcer:rnAspire4740:rvrV1.10:cvnAcer:ct10:cvrV1.10:
  dmi.product.name: Aspire 4740
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525061/+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 1013807] Re: transparent hugepages and thrashing on amd64

[garyr]

apport information

** Tags added: apport-collected wily

** Description changed:

  I seem to have found a solution to a severe thrashing/swapping/freezing
  problem that I've been having for months now.  I guess the real question
  is - should I turn it into a bug report and what would be useful data to
  include if so.
  
  This is a quad core AMD Phaeom system with 4G of ram, dual monitors and
  a single 1TB WD caviar black HD.  It had been behaving normally until
  something broke sometime late in the 11.x release cycle and continues in
  the current 12.04 LTS.  The symptoms are running a moderate load of apps
  (firefox with ~8 tabs, a terminal or 2, and aisleriot solitaire for
  example) and experiencing system freezes where the entire UI becomes
  totally unresponsive for 20 seconds - 5 minutes with solid disk
  activity.  Trying to figure out what was going on via iotop and top show
  jbd2 and kswapd accounting for the largest load, but since it freezes
  iotop like everything else I can't tell what's going during the worst
  storms.  Googling around shows a fair number of other people with
  similar problems, most of them with multi core amd64 systems.
  
  The other day I spotted this report on opensuse that looked similar but
  not identical:
  
  http://lists.opensuse.org/opensuse/2012-03/msg00657.html
  
  I booted with the grub parameter transparent_hugepage=never yesterday
  and the problem went and away and hasn't come back. I've streesed the
  system by running  a bunch of flash/java tabs in firefox, running a
  large java based stock app (ThinkorSwim) in another workspace and
  playing a 1080p 60fps movie in a third workspace.  This certainly causes
  swapping, but not freezing or stumbling.  It actually did a bit of
  swapping a minute ago while I was typing and it managed to make Pandora
  radio stumble for a moment - but that's orders of magnitude better than
  it has been.
  
  I think there may be a fundamental problem with how transparent
  hugepages are handled with some AMD CPUs.  I think this problem started
  when this feature was implemented and enabled by default. The manpage
  for madvise() says this was added in 2.6.38, but I don't know if it was
  enabled by default at that point.
  
  Hre's a partial list of things that haven't worked well in the past:
  
  Playing with the swappiness value: setting swappiness to very low values
  makes the problem take longer to surface, but (unsurprisinglly) makes it
  even worse once it does.
  
  swapoff-a ; swapon-a: this makes it go away for a while.  A potentially
  interesting thing is that as soon as I can get the system to act on the
  swapoff -a the system becomes responsive again. It pegs once CPU core at
  100% and the HD grinds like crazy but it stops freezing right away.
  
  Moving swap from the HD to a USB thumb drive: Obviously I didn't expect
  that to be faster but wanted to see if segregating swap to a different
  device on a different bus would make it swap more smoothly - it didn't.
  
  Playing with nice and ionice priorities for jdb2, kswapd.  The fact that
  running these processes at a lower priority than anything else on the
  system makes no difference leads me to think they were just symptoms and
  not at the root of the problem.
  
  I think this may be a tip of the iceberg and there may be a lot of other
  having this problem.  Looking around I see a fair number of reports,
  most of them unsolved.  Some may have been fixed by just adding enough
  RAM that dirty hugepages just don't collect.  Some may have been fixed
  by chaanging filesystems - ext4 seems like something a lot of people
  with this problem have in common.
  
  Workaround:
  hold down the spacebar during boot in order to bring up the grub menu, edit 
the command line and add
  transparent_hugepage=never
  
  If this fixes the problem you can make it permanent by editing
  /etc/default/grub and adding the ransparent_hugepage=never to the
  GRUB_CMDLINE_LINUX_DEFAULT  line and then running update-grub
  
  Problems with this workaround:
  1) transparent hugepages should work.  This may cause a small performance hit 
in some situations and a larger hit in others.
  2) If you do this you will probably never know when or if it actually gets 
fixed.
  
  PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ]
  Samba Team
  SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
  
  is looking for bugzilla reports on this too.
+ --- 
+ ApportVersion: 2.19.1-0ubuntu5
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  garyrich   2339 F pulseaudio
+  /dev/snd/controlC1:  garyrich   2339 F pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 15.10
+ EcryptfsInUse: Yes
+ HibernationDevice: RESUME=UUID=5b22d42d-33c8-435c-bea0-c1fbba7f88bf
+ InstallationDate: Installed on 2010-01-22 (2149 days ago)
+ InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
+ IwConfig:
+  eth0  no wireless 

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

[garyr]

apport information

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

Title:
  transparent hugepages and thrashing on amd64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I seem to have found a solution to a severe
  thrashing/swapping/freezing problem that I've been having for months
  now.  I guess the real question is - should I turn it into a bug
  report and what would be useful data to include if so.

  This is a quad core AMD Phaeom system with 4G of ram, dual monitors
  and a single 1TB WD caviar black HD.  It had been behaving normally
  until something broke sometime late in the 11.x release cycle and
  continues in the current 12.04 LTS.  The symptoms are running a
  moderate load of apps (firefox with ~8 tabs, a terminal or 2, and
  aisleriot solitaire for example) and experiencing system freezes where
  the entire UI becomes totally unresponsive for 20 seconds - 5 minutes
  with solid disk activity.  Trying to figure out what was going on via
  iotop and top show jbd2 and kswapd accounting for the largest load,
  but since it freezes iotop like everything else I can't tell what's
  going during the worst storms.  Googling around shows a fair number of
  other people with similar problems, most of them with multi core amd64
  systems.

  The other day I spotted this report on opensuse that looked similar
  but not identical:

  http://lists.opensuse.org/opensuse/2012-03/msg00657.html

  I booted with the grub parameter transparent_hugepage=never yesterday
  and the problem went and away and hasn't come back. I've streesed the
  system by running  a bunch of flash/java tabs in firefox, running a
  large java based stock app (ThinkorSwim) in another workspace and
  playing a 1080p 60fps movie in a third workspace.  This certainly
  causes swapping, but not freezing or stumbling.  It actually did a bit
  of swapping a minute ago while I was typing and it managed to make
  Pandora radio stumble for a moment - but that's orders of magnitude
  better than it has been.

  I think there may be a fundamental problem with how transparent
  hugepages are handled with some AMD CPUs.  I think this problem
  started when this feature was implemented and enabled by default. The
  manpage for madvise() says this was added in 2.6.38, but I don't know
  if it was enabled by default at that point.

  Hre's a partial list of things that haven't worked well in the past:

  Playing with the swappiness value: setting swappiness to very low
  values makes the problem take longer to surface, but (unsurprisinglly)
  makes it even worse once it does.

  swapoff-a ; swapon-a: this makes it go away for a while.  A
  potentially interesting thing is that as soon as I can get the system
  to act on the swapoff -a the system becomes responsive again. It pegs
  once CPU core at 100% and the HD grinds like crazy but it stops
  freezing right away.

  Moving swap from the HD to a USB thumb drive: Obviously I didn't
  expect that to be faster but wanted to see if segregating swap to a
  different device on a different bus would make it swap more smoothly -
  it didn't.

  Playing with nice and ionice priorities for jdb2, kswapd.  The fact
  that running these processes at a lower priority than anything else on
  the system makes no difference leads me to think they were just
  symptoms and not at the root of the problem.

  I think this may be a tip of the iceberg and there may be a lot of
  other having this problem.  Looking around I see a fair number of
  reports, most of them unsolved.  Some may have been fixed by just
  adding enough RAM that dirty hugepages just don't collect.  Some may
  have been fixed by chaanging filesystems - ext4 seems like something a
  lot of people with this problem have in common.

  Workaround:
  hold down the spacebar during boot in order to bring up the grub menu, edit 
the command line and add
  transparent_hugepage=never

  If this fixes the problem you can make it permanent by editing
  /etc/default/grub and adding the ransparent_hugepage=never to the
  GRUB_CMDLINE_LINUX_DEFAULT  line and then running update-grub

  Problems with this workaround:
  1) transparent hugepages should work.  This may cause a small performance hit 
in some situations and a larger hit in others.
  2) If you do this you will probably never know when or if it actually gets 
fixed.

  PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ]
  Samba Team
  SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

  is looking for bugzilla reports on this too.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  garyrich   2339 F pulseaudio
   /dev/snd/controlC1:  garyrich   2339 F pulseaudio
  

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

[garyr]

apport information

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

Title:
  transparent hugepages and thrashing on amd64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I seem to have found a solution to a severe
  thrashing/swapping/freezing problem that I've been having for months
  now.  I guess the real question is - should I turn it into a bug
  report and what would be useful data to include if so.

  This is a quad core AMD Phaeom system with 4G of ram, dual monitors
  and a single 1TB WD caviar black HD.  It had been behaving normally
  until something broke sometime late in the 11.x release cycle and
  continues in the current 12.04 LTS.  The symptoms are running a
  moderate load of apps (firefox with ~8 tabs, a terminal or 2, and
  aisleriot solitaire for example) and experiencing system freezes where
  the entire UI becomes totally unresponsive for 20 seconds - 5 minutes
  with solid disk activity.  Trying to figure out what was going on via
  iotop and top show jbd2 and kswapd accounting for the largest load,
  but since it freezes iotop like everything else I can't tell what's
  going during the worst storms.  Googling around shows a fair number of
  other people with similar problems, most of them with multi core amd64
  systems.

  The other day I spotted this report on opensuse that looked similar
  but not identical:

  http://lists.opensuse.org/opensuse/2012-03/msg00657.html

  I booted with the grub parameter transparent_hugepage=never yesterday
  and the problem went and away and hasn't come back. I've streesed the
  system by running  a bunch of flash/java tabs in firefox, running a
  large java based stock app (ThinkorSwim) in another workspace and
  playing a 1080p 60fps movie in a third workspace.  This certainly
  causes swapping, but not freezing or stumbling.  It actually did a bit
  of swapping a minute ago while I was typing and it managed to make
  Pandora radio stumble for a moment - but that's orders of magnitude
  better than it has been.

  I think there may be a fundamental problem with how transparent
  hugepages are handled with some AMD CPUs.  I think this problem
  started when this feature was implemented and enabled by default. The
  manpage for madvise() says this was added in 2.6.38, but I don't know
  if it was enabled by default at that point.

  Hre's a partial list of things that haven't worked well in the past:

  Playing with the swappiness value: setting swappiness to very low
  values makes the problem take longer to surface, but (unsurprisinglly)
  makes it even worse once it does.

  swapoff-a ; swapon-a: this makes it go away for a while.  A
  potentially interesting thing is that as soon as I can get the system
  to act on the swapoff -a the system becomes responsive again. It pegs
  once CPU core at 100% and the HD grinds like crazy but it stops
  freezing right away.

  Moving swap from the HD to a USB thumb drive: Obviously I didn't
  expect that to be faster but wanted to see if segregating swap to a
  different device on a different bus would make it swap more smoothly -
  it didn't.

  Playing with nice and ionice priorities for jdb2, kswapd.  The fact
  that running these processes at a lower priority than anything else on
  the system makes no difference leads me to think they were just
  symptoms and not at the root of the problem.

  I think this may be a tip of the iceberg and there may be a lot of
  other having this problem.  Looking around I see a fair number of
  reports, most of them unsolved.  Some may have been fixed by just
  adding enough RAM that dirty hugepages just don't collect.  Some may
  have been fixed by chaanging filesystems - ext4 seems like something a
  lot of people with this problem have in common.

  Workaround:
  hold down the spacebar during boot in order to bring up the grub menu, edit 
the command line and add
  transparent_hugepage=never

  If this fixes the problem you can make it permanent by editing
  /etc/default/grub and adding the ransparent_hugepage=never to the
  GRUB_CMDLINE_LINUX_DEFAULT  line and then running update-grub

  Problems with this workaround:
  1) transparent hugepages should work.  This may cause a small performance hit 
in some situations and a larger hit in others.
  2) If you do this you will probably never know when or if it actually gets 
fixed.

  PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ]
  Samba Team
  SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

  is looking for bugzilla reports on this too.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  garyrich   2339 F pulseaudio
   /dev/snd/controlC1:  garyrich   2339 F pulseaudio
  

[Kernel-packages] [Bug 1013807] UdevDb.txt

[garyr]

apport information

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

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

Title:
  transparent hugepages and thrashing on amd64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I seem to have found a solution to a severe
  thrashing/swapping/freezing problem that I've been having for months
  now.  I guess the real question is - should I turn it into a bug
  report and what would be useful data to include if so.

  This is a quad core AMD Phaeom system with 4G of ram, dual monitors
  and a single 1TB WD caviar black HD.  It had been behaving normally
  until something broke sometime late in the 11.x release cycle and
  continues in the current 12.04 LTS.  The symptoms are running a
  moderate load of apps (firefox with ~8 tabs, a terminal or 2, and
  aisleriot solitaire for example) and experiencing system freezes where
  the entire UI becomes totally unresponsive for 20 seconds - 5 minutes
  with solid disk activity.  Trying to figure out what was going on via
  iotop and top show jbd2 and kswapd accounting for the largest load,
  but since it freezes iotop like everything else I can't tell what's
  going during the worst storms.  Googling around shows a fair number of
  other people with similar problems, most of them with multi core amd64
  systems.

  The other day I spotted this report on opensuse that looked similar
  but not identical:

  http://lists.opensuse.org/opensuse/2012-03/msg00657.html

  I booted with the grub parameter transparent_hugepage=never yesterday
  and the problem went and away and hasn't come back. I've streesed the
  system by running  a bunch of flash/java tabs in firefox, running a
  large java based stock app (ThinkorSwim) in another workspace and
  playing a 1080p 60fps movie in a third workspace.  This certainly
  causes swapping, but not freezing or stumbling.  It actually did a bit
  of swapping a minute ago while I was typing and it managed to make
  Pandora radio stumble for a moment - but that's orders of magnitude
  better than it has been.

  I think there may be a fundamental problem with how transparent
  hugepages are handled with some AMD CPUs.  I think this problem
  started when this feature was implemented and enabled by default. The
  manpage for madvise() says this was added in 2.6.38, but I don't know
  if it was enabled by default at that point.

  Hre's a partial list of things that haven't worked well in the past:

  Playing with the swappiness value: setting swappiness to very low
  values makes the problem take longer to surface, but (unsurprisinglly)
  makes it even worse once it does.

  swapoff-a ; swapon-a: this makes it go away for a while.  A
  potentially interesting thing is that as soon as I can get the system
  to act on the swapoff -a the system becomes responsive again. It pegs
  once CPU core at 100% and the HD grinds like crazy but it stops
  freezing right away.

  Moving swap from the HD to a USB thumb drive: Obviously I didn't
  expect that to be faster but wanted to see if segregating swap to a
  different device on a different bus would make it swap more smoothly -
  it didn't.

  Playing with nice and ionice priorities for jdb2, kswapd.  The fact
  that running these processes at a lower priority than anything else on
  the system makes no difference leads me to think they were just
  symptoms and not at the root of the problem.

  I think this may be a tip of the iceberg and there may be a lot of
  other having this problem.  Looking around I see a fair number of
  reports, most of them unsolved.  Some may have been fixed by just
  adding enough RAM that dirty hugepages just don't collect.  Some may
  have been fixed by chaanging filesystems - ext4 seems like something a
  lot of people with this problem have in common.

  Workaround:
  hold down the spacebar during boot in order to bring up the grub menu, edit 
the command line and add
  transparent_hugepage=never

  If this fixes the problem you can make it permanent by editing
  /etc/default/grub and adding the ransparent_hugepage=never to the
  GRUB_CMDLINE_LINUX_DEFAULT  line and then running update-grub

  Problems with this workaround:
  1) transparent hugepages should work.  This may cause a small performance hit 
in some situations and a larger hit in others.
  2) If you do this you will probably never know when or if it actually gets 
fixed.

  PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ]
  Samba Team
  SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

  is looking for bugzilla reports on this too.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  garyrich   2339 F pulseaudio
   /dev/snd/controlC1:  garyrich   2339 F pulseaudio
  

[Kernel-packages] [Bug 1433906] Re: Acer, Inc ID 5986:055a is useless after 14.04.2 installed.

[Gary G.]

While it's wonderful that a patch has been created, could someone out
there PLEASE wrap it up in a nice and simple .DEB package so the rest of
us idiots can install it without having to manually recompile the
kernel?

After all, most of us *buntu users are simpletons who can't work a BASH
shell if our lives depended on it, at least if you go by the continual
dumbing down of the interface with each successive  version :P

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

Title:
  Acer, Inc ID 5986:055a is useless after 14.04.2 installed.

Status in HWE Next:
  Won't Fix
Status in linux-lts-utopic package in Ubuntu:
  Confirmed
Status in linux-lts-vivid package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  New
Status in Fedora:
  Unknown

Bug description:
  CID : 201411-16166 Lenovo E450 (I+A) with 14.04.2 (utopic)
  CID : 201408-15472 Lenovo E555 (A+A) with 14.04.2 (utopic)

  Steps:
  1. Install 14.04.2 on E450 or E555.
  2. Log in system and open a terminal.
  3. $ gst-launch-0.10 v4l2src ! xvimagesink

  Expected result:
  Camara is activated

  Actual result:
  $  gst-launch-0.10 v4l2src ! xvimagesink
  Setting pipeline to PAUSED ...
  ERROR: Pipeline doesn't want to pause.
  ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Cannot 
identify device '/dev/video0'.
  Additional debug info:
  v4l2_calls.c(497): gst_v4l2_open (): 
/GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
  system error: No such file or directory
  Setting pipeline to NULL ...
  Freeing pipeline ...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 [modified: 
boot/vmlinuz-3.16.0-30-generic]
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 19 02:21:31 2015
  InstallationDate: Installed on 2015-03-16 (2 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: linux-lts-utopic
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1433906/+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 1013807] Re: transparent hugepages and thrashing on amd64

[garyr]

What may be useful to a 3 year old bug report other than the log files?
The problem still exists on that computer. I added zram swap shortly
after this bug report and it helped some. Some. Using hugepages
currently and there times when it's easier to walk away and do something
else for 10 minutes while some i/o intensive cron job like mlocate
(since uninstalled) thrashes. Obscuring the problem is that some apt
update set the scheduler to "deadline" rather than "cfq" so ionice
values don't work. Forcing it back to "cfq" helps some - at least the
entire user interface isn't locked up for half an hour.

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

Title:
  transparent hugepages and thrashing on amd64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I seem to have found a solution to a severe
  thrashing/swapping/freezing problem that I've been having for months
  now.  I guess the real question is - should I turn it into a bug
  report and what would be useful data to include if so.

  This is a quad core AMD Phaeom system with 4G of ram, dual monitors
  and a single 1TB WD caviar black HD.  It had been behaving normally
  until something broke sometime late in the 11.x release cycle and
  continues in the current 12.04 LTS.  The symptoms are running a
  moderate load of apps (firefox with ~8 tabs, a terminal or 2, and
  aisleriot solitaire for example) and experiencing system freezes where
  the entire UI becomes totally unresponsive for 20 seconds - 5 minutes
  with solid disk activity.  Trying to figure out what was going on via
  iotop and top show jbd2 and kswapd accounting for the largest load,
  but since it freezes iotop like everything else I can't tell what's
  going during the worst storms.  Googling around shows a fair number of
  other people with similar problems, most of them with multi core amd64
  systems.

  The other day I spotted this report on opensuse that looked similar
  but not identical:

  http://lists.opensuse.org/opensuse/2012-03/msg00657.html

  I booted with the grub parameter transparent_hugepage=never yesterday
  and the problem went and away and hasn't come back. I've streesed the
  system by running  a bunch of flash/java tabs in firefox, running a
  large java based stock app (ThinkorSwim) in another workspace and
  playing a 1080p 60fps movie in a third workspace.  This certainly
  causes swapping, but not freezing or stumbling.  It actually did a bit
  of swapping a minute ago while I was typing and it managed to make
  Pandora radio stumble for a moment - but that's orders of magnitude
  better than it has been.

  I think there may be a fundamental problem with how transparent
  hugepages are handled with some AMD CPUs.  I think this problem
  started when this feature was implemented and enabled by default. The
  manpage for madvise() says this was added in 2.6.38, but I don't know
  if it was enabled by default at that point.

  Hre's a partial list of things that haven't worked well in the past:

  Playing with the swappiness value: setting swappiness to very low
  values makes the problem take longer to surface, but (unsurprisinglly)
  makes it even worse once it does.

  swapoff-a ; swapon-a: this makes it go away for a while.  A
  potentially interesting thing is that as soon as I can get the system
  to act on the swapoff -a the system becomes responsive again. It pegs
  once CPU core at 100% and the HD grinds like crazy but it stops
  freezing right away.

  Moving swap from the HD to a USB thumb drive: Obviously I didn't
  expect that to be faster but wanted to see if segregating swap to a
  different device on a different bus would make it swap more smoothly -
  it didn't.

  Playing with nice and ionice priorities for jdb2, kswapd.  The fact
  that running these processes at a lower priority than anything else on
  the system makes no difference leads me to think they were just
  symptoms and not at the root of the problem.

  I think this may be a tip of the iceberg and there may be a lot of
  other having this problem.  Looking around I see a fair number of
  reports, most of them unsolved.  Some may have been fixed by just
  adding enough RAM that dirty hugepages just don't collect.  Some may
  have been fixed by chaanging filesystems - ext4 seems like something a
  lot of people with this problem have in common.

  Workaround:
  hold down the spacebar during boot in order to bring up the grub menu, edit 
the command line and add
  transparent_hugepage=never

  If this fixes the problem you can make it permanent by editing
  /etc/default/grub and adding the ransparent_hugepage=never to the
  GRUB_CMDLINE_LINUX_DEFAULT  line and then running update-grub

  Problems with this workaround:
  1) transparent hugepages should work.  This may cause a small performance hit 
in some situations and a larger hit in others.
  2) 

[Kernel-packages] [Bug 889071] Re: SATA III recognized as SATA II (chipset intel z68)

[Grizzly]

On Kernel 4.2 now. Less shaky, but sometimes one of the crucial's is SATA II 
only.
Also, the ATA-Numbers are changing from time to time. So indeed, I am filing a 
new 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/889071

Title:
  SATA III recognized as SATA II (chipset intel z68)

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My SSD OCZ vertex 3 60Go SATAIII and my WesternDigital 500Go/s SATAIII
  are recognized as SATA II discs, according to palimpsest. When I run
  hdparm -tT /dev/sd?, it returns me that my SSD works à 300Mo/s which
  means that the disc is effectively limited by the SATA II norm. I have
  tested the same configuration under windows, and the SSD runs at
  480Mo/s in average.

  My chipset is the intel Z68, and I have updated both the motherboard's
  and SSD's BIOS. The AHCI mode is activated.

  Since Ubuntu 12.04, the hdd speed go from 330Mo/s to 360Mo/so.

  I have tested the kenerl 3.4 rc6 without any improvement.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image-3.0.0-12-generic 3.0.0-12.20
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  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: ALC892 Analog [ALC892 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jason  1777 F pulseaudio
  CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xfa30 irq 59'
     Mixer name : 'Realtek ALC892'
     Components : 'HDA:10ec0892,1043841b,00100302'
     Controls  : 35
     Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xfa08 irq 17'
     Mixer name : 'Nvidia GPU 12 HDMI/DP'
     Components : 'HDA:10de0012,10de0101,00100100'
     Controls  : 16
     Simple ctrls  : 4
  Date: Fri Nov 11 12:40:07 2011
  HibernationDevice: RESUME=UUID=aec865ce-43e4-4b3e-9bf1-16375f15d4ad
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111010.1)
  IwConfig:
   lono wireless extensions.

   eth0  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic 
root=UUID=15b45aa7-65f1-4983-bb8a-7d6e8575f68f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-12-generic N/A
   linux-backports-modules-3.0.0-12-generic  N/A
   linux-firmware1.60
  RfKill:

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

  dmi.bios.date: 09/14/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V LE
  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.:bvr0702:bd09/14/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/889071/+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 1521982] Re: package linux-image-extra-4.2.0-19-generic 4.2.0-19.23 failed to install/upgrade: Extrahierte Daten für »./lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/le

[Stan]

Translation (best effort):


package linux-image-extra-4.2.0-19-generic 4.2.0-19.23 failed to 
install/upgrade: Extract Data for 
»./lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko« 
can not be copied to 
»/lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko.dpkg-new«
 : unexpected end of file or stream.

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

Title:
  package linux-image-extra-4.2.0-19-generic 4.2.0-19.23 failed to
  install/upgrade: Extrahierte Daten für
  »./lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko«
  können nicht nach
  »/lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko
  .dpkg-new« kopiert werden: Unerwartetes Ende der Datei oder des
  Datenstroms

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  none

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: linux-image-extra-4.2.0-19-generic 4.2.0-19.23
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  carsten1741 F pulseaudio
   /dev/snd/controlC1:  carsten1741 F pulseaudio
  Date: Tue Dec  1 21:46:29 2015
  DpkgHistoryLog:
   
  DpkgTerminalLog:
   
  ErrorMessage: Extrahierte Daten für 
»./lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko« 
können nicht nach 
»/lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko.dpkg-new«
 kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms
  HibernationDevice: RESUME=UUID=55b16c37-9a10-448a-8d4e-f59a0ed550ea
  InstallationDate: Installed on 2015-11-19 (12 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. P67A-UD3-B3
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic 
root=UUID=9c54422a-2851-4e1a-b9f6-28e6374aa754 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.02~beta2-29
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-extra-4.2.0-19-generic 4.2.0-19.23 failed to 
install/upgrade: Extrahierte Daten für 
»./lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko« 
können nicht nach 
»/lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko.dpkg-new«
 kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9
  dmi.board.name: P67A-UD3-B3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd03/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnP67A-UD3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67A-UD3-B3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P67A-UD3-B3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521982/+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 1518566] Re: Ubuntu 15.10 freezing randomly

[Spyros Theodoritsis]

Ubuntu froze again after BIOS upgrade, so this is reproducible.

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

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

Title:
  Ubuntu 15.10 freezing randomly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.10 freezing randomly

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  spyros 3013 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Nov 21 16:15:04 2015
  HibernationDevice: RESUME=UUID=3fbc151c-b9b3-492c-a1f4-c598a0b080bb
  InstallationDate: Installed on 2015-09-23 (58 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 04b4:0060 Cypress Semiconductor Corp. Wireless 
optical mouse
   Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 002: ID 0bda:57bc Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X751MA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=59242a09-40d6-4231-b79b-543e0a88dbde ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.2
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-11-05 (15 days ago)
  dmi.bios.date: 01/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X751MA.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X751MA
  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.:bvrX751MA.208:bd01/26/2015:svnASUSTeKCOMPUTERINC.:pnX751MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX751MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X751MA
  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/1518566/+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 1525270] Re: Wi-Di Realtek 8192E disconnects after a while and fails to reconnect

[Gilbert Dion]

Title should read "Wi-Fi Realtek 8192E" etc.

g

2015-12-11 18:45 GMT-05:00 Alberto Salvia Novella
:

> ** Changed in: linux (Ubuntu)
>Importance: Undecided => High
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1525270
>
> Title:
>   Wi-Di Realtek 8192E disconnects after a while and fails to reconnect
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   A few minutes after booting my Samsung R580 laptop, the Wi-Fi
>   disconnects and it fails to reconnect until I restart the machine.
>   This happens with all the 64 bit versions of Ubuntu I tried, from
>   14.04 to 15.10. With the 32 bit versions, everything runs perfectly.
>   No loss of connection at all, even after 48 hours in a row.
>
>   Here is the output of iwconfig after loss of connexion:
>
>   eth7  no wireless extensions.
>
>   lono wireless extensions.
>
>   wlan6 802.11bgn  ESSID:"JeLisVosCourriels"  Nickname:"rtl8192E"
> Mode:Managed  Frequency=2.417 GHz  Access Point: Not-Associated
> Bit Rate:19.5 Mb/s
> Retry min limit:7   RTS thr:off   Fragment thr:off
> Power Management:off
> Link Quality=10/100  Signal level=0 dBm  Noise level=-100 dBm
> Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
> Tx excessive retries:0  Invalid misc:0   Missed beacon:0
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 15.10
>   Package: linux-image-4.2.0-19-generic 4.2.0-19.23
>   ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
>   Uname: Linux 4.2.0-19-generic x86_64
>   ApportVersion: 2.19.1-0ubuntu5
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1:  gilbert3115 F pulseaudio
>/dev/snd/controlC0:  gilbert3115 F pulseaudio
>   CurrentDesktop: Unity
>   Date: Fri Dec 11 09:27:18 2015
>   HibernationDevice: RESUME=UUID=e19f92d5-541f-412f-b5b0-7d97bfa1b7ec
>   InstallationDate: Installed on 2015-12-03 (7 days ago)
>   InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64
> (20141022.1)
>   MachineType: SAMSUNG ELECTRONICS CO., LTD. R580
>   ProcFB: 0 nouveaufb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic
> root=UUID=f6b1d099-6ed1-4e82-823a-352535c7596c ro quiet splash vt.handoff=7
>   RelatedPackageVersions:
>linux-restricted-modules-4.2.0-19-generic N/A
>linux-backports-modules-4.2.0-19-generic  N/A
>linux-firmware1.149.3
>   SourcePackage: linux
>   UpgradeStatus: Upgraded to wily on 2015-12-03 (7 days ago)
>   dmi.bios.date: 12/21/2009
>   dmi.bios.vendor: Phoenix Technologies Ltd.
>   dmi.bios.version: 04JB.M014.20091221.hkk
>   dmi.board.asset.tag: Tag 12345
>   dmi.board.name: R580
>   dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
>   dmi.board.version: Not Applicable
>   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:bvnPhoenixTechnologiesLtd.:bvr04JB.M014.20091221.hkk:bd12/21/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnR580:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR580:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
>   dmi.product.name: R580
>   dmi.product.version: Not Applicable
>   dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525270/+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/1525270

Title:
  Wi-Di Realtek 8192E disconnects after a while and fails to reconnect

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A few minutes after booting my Samsung R580 laptop, the Wi-Fi
  disconnects and it fails to reconnect until I restart the machine.
  This happens with all the 64 bit versions of Ubuntu I tried, from
  14.04 to 15.10. With the 32 bit versions, everything runs perfectly.
  No loss of connection at all, even after 48 hours in a row.

  Here is the output of iwconfig after loss of connexion:

  eth7  no wireless extensions.

  lono wireless extensions.

  wlan6 802.11bgn  ESSID:"JeLisVosCourriels"  Nickname:"rtl8192E"
Mode:Managed  Frequency=2.417 GHz  Access Point: Not-Associated   
Bit Rate:19.5 Mb/s   
Retry min limit:7   RTS thr:off   Fragment thr:off
Power Management:off
Link Quality=10/100  Signal level=0 dBm  Noise level=-100 dBm
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:0  Invalid misc:0   Missed beacon:0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23
  ProcVersionSignature: Ubuntu 

[Kernel-packages] [Bug 1504219] Re: [To Be Filled By O.E.M. To Be Filled By O.E.M.] suspend/resume failure

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  [To Be Filled By O.E.M. To Be Filled By O.E.M.] suspend/resume failure

Status in linux package in Ubuntu:
  Expired

Bug description:
  Rebooted after trying to suspend

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-15-generic 4.2.0-15.18
  ProcVersionSignature: Ubuntu 4.2.0-15.18-generic 4.2.3
  Uname: Linux 4.2.0-15-generic x86_64
  Annotation: This occurred during a previous suspend, and prevented the system 
from resuming properly.
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timmillwood   1627 F pulseaudio
   /dev/snd/controlC1:  timmillwood   1627 F pulseaudio
  Date: Thu Oct  8 17:37:07 2015
  DuplicateSignature: suspend/resume:To Be Filled By O.E.M. To Be Filled By 
O.E.M.:P1.30
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=3415ec44-04bc-4d6d-8fc8-bd4f7b6c3451
  InstallationDate: Installed on 2015-10-04 (4 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  InterpreterPath: /usr/bin/python3.4
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-15-generic 
root=UUID=c621629a-b55c-47f1-8534-ccdd44a1c5dd ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-15-generic N/A
   linux-backports-modules-4.2.0-15-generic  N/A
   linux-firmware1.149
  RfKill:
   
  SourcePackage: linux
  Title: [To Be Filled By O.E.M. To Be Filled By O.E.M.] suspend/resume failure
  UpgradeStatus: Upgraded to wily on 2015-10-07 (0 days ago)
  UserGroups:
   
  dmi.bios.date: 05/04/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.30
  dmi.board.name: Z68 Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd05/04/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ68Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504219/+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 1389675] Re: Function keys will not adjust brightness

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Function keys will not adjust brightness

Status in linux package in Ubuntu:
  Expired

Bug description:
  I have just installed Ubuntu 14.04, and I cannot make the function
  keys adjust the brightness.  I have been trying to get a solution to
  the problem in this forum
  
http://ubuntuforums.org/showthread.php?t=2250862=2=13159626#post13159626
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-39-generic 3.13.0-39.66
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  paul   1336 F pulseaudio
   /dev/snd/pcmC0D0p:   paul   1336 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Wed Nov  5 13:31:30 2014
  HibernationDevice: RESUME=UUID=6357ccbf-2f39-4ca6-9cc1-65eb05bf30f6
  InstallationDate: Installed on 2014-10-29 (6 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b404 Chicony Electronics Co., Ltd 
   Bus 001 Device 006: ID 1c4f:0003 SiGma Micro HID controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X551MA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic.efi.signed 
root=UUID=730dc0d2-8142-4bc0-a5ee-a2928da9bd65 ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-39-generic N/A
   linux-backports-modules-3.13.0-39-generic  N/A
   linux-firmware 1.127.7
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X551MA.510
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X551MA
  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.:bvrX551MA.510:bd06/27/2014:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X551MA
  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/1389675/+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 1504417] Re: BUG: unable to handle kernel NULL pointer dereference at 00000011

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

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

Status in linux package in Ubuntu:
  Expired

Bug description:
  The boot was failed. This session was start with "GRUB menù"

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-15-generic 4.2.0-15.17
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-15-generic i686
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.19-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  emsidj 2468 F pulseaudio
  Date: Thu Oct  8 13:12:38 2015
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location EIP: location show_map_vma+0x45/0x2d0 SS:ESP 0068:d58b3e88
  Failure: oops
  HibernationDevice: RESUME=UUID=ad686395-81e9-40d1-86a3-708eead8c6b4
  InstallationDate: Installed on 2012-01-14 (1364 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic 
root=UUID=69b276ef-4078-4eff-a226-1f20f85929ba ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at 0011
  UpgradeStatus: Upgraded to wily on 2015-09-20 (18 days ago)
  dmi.bios.date: 12/11/2008
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 04CA.MP00.20081211.KTW
  dmi.board.name: NC10
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr04CA.MP00.20081211.KTW:bd12/11/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC10:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC10:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.name: NC10
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

[Brad Figg]

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

apport-collect 1525450

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

Title:
   SATA III recognized as SATA II

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Following #889071, I want to say that even on Kernel 
linux-image-4.2.0-19-generic 4.2.0-19.23~14.04.1
   (14.04 LTS with wily-kernel ) the SATA III recognition is  a bit shaky, but 
less than it used to be in the 3.x series.

  Also, the SATA-Numbers keep changing, so it is hard to tell which disk
  has the issue...:

  [2.481536] ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
  [2.481568] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
  [2.481600] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
  [2.485425] ata11: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
  [2.649406] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
  [2.481503] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) 
<= Thats unexpected
  [2.501404] ata14: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
  [2.557461] ata13: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
  [3.468992] ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

  (about 10-20% of boots)

  ---

  That's OK, but why different numbers?

  [2.476286] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
  [2.476324] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
  [2.476356] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
  [2.476386] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
  [2.476409] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
  [2.480199] ata11: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
  [2.500201] ata13: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
  [2.500229] ata14: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
  [3.303818] ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

  That is on Asus Sabertooth AMD-FX8350-Board.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525450/+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 1523765] Re: USB performance extremely unstable

[Michael Heuberger]

Why incomplete @Alberto?

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

Title:
  USB performance extremely unstable

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since I upgraded from Trusty to Wily, the USB performance has become
  extremely unstable. Sometimes file transfers were fast, like 1GB in 30
  sec, then most days it is so slow like 1 GB in 20 minutes for no
  reason.

  Here some relevant log lines from the `dmesg` command when I USB is
  plugged in:

  ```
  [  496.912939] usb 4-5: new high-speed USB device number 2 using ehci-pci
  [  497.111419] usb 4-5: New USB device found, idVendor=1b1c, idProduct=1ab1
  [  497.111425] usb 4-5: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [  497.111428] usb 4-5: Product: Voyager
  [  497.111430] usb 4-5: Manufacturer: Corsair
  [  497.111433] usb 4-5: SerialNumber: AA400825
  [  497.134497] usb-storage 4-5:1.0: USB Mass Storage device detected
  [  497.134600] scsi host12: usb-storage 4-5:1.0
  [  497.134713] usbcore: registered new interface driver usb-storage
  [  497.137090] usbcore: registered new interface driver uas
  [  498.420795] scsi 12:0:0:0: Direct-Access Corsair  Voyager  
1100 PQ: 0 ANSI: 0 CCS
  [  498.421211] sd 12:0:0:0: Attached scsi generic sg5 type 0
  [  498.913643] sd 12:0:0:0: [sdd] 15663104 512-byte logical blocks: (8.01 
GB/7.46 GiB)
  [  498.914804] sd 12:0:0:0: [sdd] Write Protect is off
  [  498.914809] sd 12:0:0:0: [sdd] Mode Sense: 43 00 00 00
  [  498.915930] sd 12:0:0:0: [sdd] No Caching mode page found
  [  498.915934] sd 12:0:0:0: [sdd] Assuming drive cache: write through
  [  498.920710]  sdd: sdd1
  [  498.924684] sd 12:0:0:0: [sdd] Attached SCSI removable disk
  [ 1184.038007] usb 4-5: USB disconnect, device number 2
  ```

  these two lines appear in *red*

  ```
  [  498.915930] sd 12:0:0:0: [sdd] No Caching mode page found
  [  498.915934] sd 12:0:0:0: [sdd] Assuming drive cache: write through
  ```

  What can we do here? How can this be investigated and fixed properly?
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  michael-heuberger   4363 F pulseaudio
   /dev/snd/controlC2:  michael-heuberger   4363 F pulseaudio
   /dev/snd/controlC0:  michael-heuberger   4363 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=b0b47183-895a-4f27-bb25-40bd23028028
  InstallationDate: Installed on 2014-10-31 (403 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic 
root=UUID=b5b38333-3694-4441-8a13-50bf4dbf2f41 ro quiet
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.149.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  wily
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark www-data
  _MarkForUpload: True
  dmi.bios.date: 08/06/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0803
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6X58D-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0803:bd08/06/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6X58D-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523765/+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 1525459] Re: Touchpad not detected

[Evert]

** Attachment added: "~devices"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525459/+attachment/4533532/+files/%7Edevices

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

Title:
  Touchpad not detected

Status in linux package in Ubuntu:
  New

Bug description:
   USB Optical mouse is detected and functioning, xinput does not detect
  the touchpad.

  cat /proc/bus/input/devices does not detect the touchpad either.

  
  xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ PixArt Lenovo USB Optical Mouse id=9[slave  pointer 
 (2)]


  evert@evert-laptop:~$ cat /proc/bus/input/devices 
  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0003 Vendor=17ef Product=6019 Version=0111
  N: Name="PixArt Lenovo USB Optical Mouse"
  P: Phys=usb-:00:14.0-6/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003:17EF:6019.0001/input/input4
  U: Uniq=
  H: Handlers=mouse0 event4 
  B: PROP=0
  B: EV=17
  B: KEY=ff 0 0 0 0
  B: REL=103
  B: MSC=10

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Asus WMI hotkeys"
  P: Phys=asus-nb-wmi/input0
  S: Sysfs=/devices/platform/asus-nb-wmi/input/input5
  U: Uniq=
  H: Handlers=rfkill kbd event5 
  B: PROP=0
  B: EV=100013
  B: KEY=8 0 8000 0 0 a1606f0090 8200027800501000 e 0
  B: MSC=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Mic"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input6
  U: Uniq=
  H: Handlers=event6 
  B: PROP=0
  B: EV=21
  B: SW=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input7
  U: Uniq=
  H: Handlers=event7 
  B: PROP=0
  B: EV=21
  B: SW=4

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8
  U: Uniq=
  H: Handlers=event8 
  B: PROP=0 Include an attachment (Optional)
  Attachment: (Optio
  B: EV=21
  B: SW=140

  I: Bus=0003 Vendor=04f2 Product=b424 Version=6969
  N: Name="USB2.0 HD UVC WebCam"
  P: Phys=usb-:00:14.0-4/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/input/input9
  U: Uniq=
  H: Handlers=kbd event9 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-15-generic 3.19.0-15.15 [modified: 
boot/vmlinuz-3.19.0-15-generic]
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  evert  1749 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Dec 11 21:01:01 2015
  HibernationDevice: RESUME=UUID=33cc4efa-1999-47ad-b0f6-2c6fa5cc2d24
  InstallationDate: Installed on 2015-12-11 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 17ef:6019 Lenovo 
   Bus 001 Device 002: ID 04f2:b424 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. GL552VW
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic 
root=UUID=ebbce668-5e09-4c15-b5c8-83a1b796ad4a ro recovery nomodeset reboot=efi
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware

[Kernel-packages] [Bug 1525459] [NEW] Touchpad not detected

[Evert]

Public bug reported:

 USB Optical mouse is detected and functioning, xinput does not detect
the touchpad.

cat /proc/bus/input/devices does not detect the touchpad either.


xinput list
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ PixArt Lenovo USB Optical Mouse   id=9[slave  pointer  (2)]


evert@evert-laptop:~$ cat /proc/bus/input/devices 
I: Bus=0019 Vendor= Product=0005 Version=
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
U: Uniq=
H: Handlers=event0 
B: PROP=0
B: EV=21
B: SW=1

I: Bus=0019 Vendor= Product=0003 Version=
N: Name="Sleep Button"
P: Phys=PNP0C0E/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
U: Uniq=
H: Handlers=kbd event1 
B: PROP=0
B: EV=3
B: KEY=4000 0 0

I: Bus=0019 Vendor= Product=0001 Version=
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
U: Uniq=
H: Handlers=kbd event2 
B: PROP=0
B: EV=3
B: KEY=10 0

I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input3
U: Uniq=
H: Handlers=sysrq kbd event3 
B: PROP=0
B: EV=120013
B: KEY=40200 3803078f800d001 fedfffef fffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=17ef Product=6019 Version=0111
N: Name="PixArt Lenovo USB Optical Mouse"
P: Phys=usb-:00:14.0-6/input0
S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003:17EF:6019.0001/input/input4
U: Uniq=
H: Handlers=mouse0 event4 
B: PROP=0
B: EV=17
B: KEY=ff 0 0 0 0
B: REL=103
B: MSC=10

I: Bus=0019 Vendor= Product= Version=
N: Name="Asus WMI hotkeys"
P: Phys=asus-nb-wmi/input0
S: Sysfs=/devices/platform/asus-nb-wmi/input/input5
U: Uniq=
H: Handlers=rfkill kbd event5 
B: PROP=0
B: EV=100013
B: KEY=8 0 8000 0 0 a1606f0090 8200027800501000 e 0
B: MSC=10

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input6
U: Uniq=
H: Handlers=event6 
B: PROP=0
B: EV=21
B: SW=10

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input7
U: Uniq=
H: Handlers=event7 
B: PROP=0
B: EV=21
B: SW=4

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH HDMI/DP,pcm=3"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8
U: Uniq=
H: Handlers=event8 
B: PROP=0 Include an attachment (Optional)
Attachment: (Optio
B: EV=21
B: SW=140

I: Bus=0003 Vendor=04f2 Product=b424 Version=6969
N: Name="USB2.0 HD UVC WebCam"
P: Phys=usb-:00:14.0-4/button
S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/input/input9
U: Uniq=
H: Handlers=kbd event9 
B: PROP=0
B: EV=3
B: KEY=10 0 0 0

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-15-generic 3.19.0-15.15 [modified: 
boot/vmlinuz-3.19.0-15-generic]
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  evert  1749 F pulseaudio
CurrentDesktop: GNOME
Date: Fri Dec 11 21:01:01 2015
HibernationDevice: RESUME=UUID=33cc4efa-1999-47ad-b0f6-2c6fa5cc2d24
InstallationDate: Installed on 2015-12-11 (0 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 003: ID 17ef:6019 Lenovo 
 Bus 001 Device 002: ID 04f2:b424 Chicony Electronics Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. GL552VW
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic 
root=UUID=ebbce668-5e09-4c15-b5c8-83a1b796ad4a ro recovery nomodeset reboot=efi
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-15-generic N/A
 linux-backports-modules-3.19.0-15-generic  N/A
 linux-firmware 1.143
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/01/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GL552VW.210
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GL552VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: