[Kernel-packages] [Bug 1763532] Re: set reasonable default cmdlines for arm64

[Bug Watch Updater]

** Changed in: makedumpfile (Debian)
   Status: Unknown => Fix Released

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

Title:
  set reasonable default cmdlines for arm64

Status in kexec-tools package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  New
Status in kexec-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  New
Status in kexec-tools source package in Artful:
  New
Status in makedumpfile source package in Artful:
  New
Status in makedumpfile package in Debian:
  Fix Released

Bug description:
  [Impact]
  Crash dump support doesn't work by default on any known arm64 platform. Users 
have to figure out working incantations for the crashkernel= parameter and the 
parameters passed to the crash-dump kernel themselves and manual edit 2 
different config files.

  [Test Case]
  Using either a Centriq 2400 or a Cavium ThunderX CRB (these platforms are 
known to support crashdump), and with a kernel >= 4.13 (xenial-ga did not 
support crashdump):

  sudo apt install kdump-tools
  (reboot, so crashkernel= is added to the kernel commandline)
  echo c | sudo tee /proc/sysrq-trigger

  Crash dump should occur, with artifacts collected in /var/crash.

  If you want to verify that the dump is usable, install the
  corresponding linux-image--dbgsym package and run:

  sudo crash /usr/lib/debug/boot/vmlinux-
  /var/crash//dump.

  crash should successfully load, placing you at a "crash>" prompt. At that 
prompt, you can issue the 'bt' command to see a backtrace.
  Note: you need crash from zesty (7.1.8-1ubuntu1) or later.

  [Regression Risk]
  TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1763532/+subscriptions

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

[Kernel-packages] [Bug 1723948] Re: error -lock in zfs send

[Bug Watch Updater]

** Changed in: zfs
   Status: Unknown => New

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

Title:
  error -lock in zfs send

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  zfs send stop working. the process did not produce output. checked by
  mbuffer log

  in kernel.log: 
  Oct 15 07:25:53 zfs-cis kernel: [479439.151281] INFO: task zfs:8708 blocked 
for more than 120 seconds.
  Oct 15 07:25:53 zfs-cis kernel: [479439.156980]   Tainted: P   OE 
  4.4.0-96-generic #119-Ubuntu
  Oct 15 07:25:53 zfs-cis kernel: [479439.162688] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Oct 15 07:25:53 zfs-cis kernel: [479439.173974] zfs D 
88197bd77318 0  8708   8141 0x
  Oct 15 07:25:53 zfs-cis kernel: [479439.173981]  88197bd77318 
810c3dc2 8820374cf000 881b645ff000
  Oct 15 07:25:53 zfs-cis kernel: [479439.173985]  88197bd78000 
00792c6d 882030aa4ac8 
  Oct 15 07:25:53 zfs-cis kernel: [479439.173989]  88101dac1840 
88197bd77330 8183f165 882030aa4a00
  Oct 15 07:25:53 zfs-cis kernel: [479439.173993] Call Trace:
  Oct 15 07:25:53 zfs-cis kernel: [479439.174006]  [] ? 
__wake_up_common+0x52/0x90
  Oct 15 07:25:53 zfs-cis kernel: [479439.174023]  [] 
schedule+0x35/0x80
  Oct 15 07:25:53 zfs-cis kernel: [479439.174045]  [] 
taskq_wait_id+0x60/0xb0 [spl]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174051]  [] ? 
wake_atomic_t_function+0x60/0x60
  Oct 15 07:25:53 zfs-cis kernel: [479439.174115]  [] ? 
dump_write+0x230/0x230 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174178]  [] 
spa_taskq_dispatch_sync+0x92/0xd0 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174223]  [] 
dump_bytes+0x51/0x70 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174267]  [] 
dump_write+0x11e/0x230 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174311]  [] 
backup_cb+0x633/0x850 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174356]  [] 
traverse_visitbp+0x47a/0x960 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174365]  [] ? 
spl_kmem_alloc+0xaf/0x190 [spl]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174409]  [] 
traverse_visitbp+0x5c0/0x960 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174462]  [] 
traverse_visitbp+0x5c0/0x960 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174503]  [] 
traverse_dnode+0x7f/0xe0 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174542]  [] 
traverse_visitbp+0x6cc/0x960 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174579]  [] 
traverse_visitbp+0x5c0/0x960 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174616]  [] 
traverse_visitbp+0x5c0/0x960 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174653]  [] 
traverse_visitbp+0x5c0/0x960 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174690]  [] 
traverse_visitbp+0x5c0/0x960 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174726]  [] 
traverse_visitbp+0x5c0/0x960 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174762]  [] 
traverse_visitbp+0x5c0/0x960 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174799]  [] 
traverse_dnode+0x7f/0xe0 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174835]  [] 
traverse_visitbp+0x865/0x960 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174871]  [] 
traverse_impl+0x1ae/0x410 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174908]  [] ? 
dmu_recv_end_check+0x210/0x210 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174944]  [] 
traverse_dataset+0x52/0x60 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174981]  [] ? 
dmu_recv_end_check+0x210/0x210 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.175017]  [] 
dmu_send_impl+0x409/0x560 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.175060]  [] 
dmu_send_obj+0x172/0x1e0 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.175129]  [] 
zfs_ioc_send+0xe9/0x2c0 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.175143]  [] ? 
strdup+0x3b/0x60 [spl]
  Oct 15 07:25:53 zfs-cis kernel: [479439.175207]  [] 
zfsdev_ioctl+0x44b/0x4e0 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.175218]  [] 
do_vfs_ioctl+0x29f/0x490
  Oct 15 07:25:53 zfs-cis kernel: [479439.175225]  [] ? 
_do_fork+0xec/0x360
  Oct 15 07:25:53 zfs-cis kernel: [479439.175232]  [] 
SyS_ioctl+0x79/0x90
  Oct 15 07:25:53 zfs-cis kernel: [479439.175242]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/1723948/+subscriptions

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

[Kernel-packages] [Bug 1746740] Re: XPS13 L322X Bionic (daily dev) touchpad laggy

[Bug Watch Updater]

** Changed in: libinput
   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/1746740

Title:
  XPS13 L322X Bionic (daily dev) touchpad laggy

Status in libinput:
  Confirmed
Status in libinput package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Also, all function keys work as expected, even F6 (keyboard 3-states
  backlight), but OSD picture for this last feature randomly auto-
  triggers.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1876 F pulseaudio
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  1 14:05:22 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- debian-installer/language=fr 
keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libinput/+bug/1746740/+subscriptions

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

[Kernel-packages] [Bug 1760973] Re: virtualbox-dkms 5.2.8-dfsg-5: virtualbox kernel module failed to build

[Bug Watch Updater]

** Changed in: linux (Debian)
   Status: Unknown => 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/1760973

Title:
  virtualbox-dkms 5.2.8-dfsg-5: virtualbox kernel module failed to build

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

Bug description:
  crash while upgrading today

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: virtualbox-dkms 5.2.8-dfsg-5
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-14-generic
  Date: Tue Apr  3 16:27:06 2018
  InstallationDate: Installed on 2018-01-12 (81 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111)
  PackageArchitecture: all
  PackageVersion: 5.2.8-dfsg-5
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: virtualbox
  Title: virtualbox-dkms 5.2.8-dfsg-5: 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/1760973/+subscriptions

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

[Kernel-packages] [Bug 159356] Re: System freeze on high memory usage

[Bug Watch Updater]

Launchpad has imported 4 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1472336.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2017-07-18T13:24:02+00:00 Steven wrote:

After a fix to glibc that fixed Unity 3D based games (Fedora ref: https://
bugzilla.redhat.com/show_bug.cgi?id=1440287), I have noticed that when I play 
Cities: Skylines that the system becomes unresponsive when digging into swap.

I have 10Gb of RAM in this system and run Fedora 26. If I launch Cities: 
Skylines with no swap space, things run well performance wise until I get an 
OOM - and it all dies - which is expected.

When I turn on swap to /dev/sda2 which resides on an SSD, I get complete 
system freezes while swap is being accessed.

The first swap was after loading a saved game, then launching kmail in the 
background. This caused ~500Mb to be swapped to /dev/sda2 on an SSD. The 
system froze for about 8 minutes - barely being able to move the mouse. The 
HDD LED was on constantly during the entire time.

To hopefully rule out the above glibc issue, I started the game via jemalloc - 
but experienced even more severe freezes while swapping. I gave up waiting 
after 13 minutes of non-responsiveness - not even being able to move the mouse 
properly.

During these hangs, I could typed into a Konsole window, and some of the 
typing took 3+ minutes to display on the screen (yay for buffers?).

I have tested this with both the default vm.swappiness values, as well as the 
following:
vm.swappiness = 1
vm.min_free_kbytes = 32768
vm.vfs_cache_pressure = 60

I noticed that when I do eventually get screen updates, all 8 cpus (4 cores / 
2 threads) show 100% CPU usage - and kswapd is right up there in the process 
list for CPU usage. Sadly I haven't been able to capture this information 
fully yet due to said unresponsiveness.

This seems to be a relatively new problem that I did not encounter during the 
Fedora 26 beta - but do now.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/comments/61


On 2017-07-18T13:25:32+00:00 Steven wrote:

Forgot to add kernel version!

Currently testing with:
kernel-4.11.10-300.fc26.x86_64

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/comments/62


On 2017-10-20T17:07:52+00:00 Jan wrote:

Related bug reports:

https://bugzilla.redhat.com/show_bug.cgi?id=1357032
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/comments/65


On 2018-02-28T03:52:10+00:00 Laura wrote:

We apologize for the inconvenience.  There is a large number of bugs to go 
through and several of them have gone stale. The kernel moves very fast so bugs 
may get fixed as part of a kernel update. Due to this, we are doing a mass bug 
update across all of the Fedora 26 kernel bugs.
 
Fedora 26 has now been rebased to 4.15.4-200.fc26.  Please test this kernel 
update (or newer) and let us know if you issue has been resolved or if it is 
still present with the newer kernel.
 
If you have moved on to Fedora 27, and are still experiencing this issue, 
please change the version to Fedora 27.
 
If you experience different issues, please open a new bug report for those.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/comments/71


** Changed in: fedora
   Status: Unknown => Confirmed

** Changed in: fedora
   Importance: Unknown => Medium

** Bug watch added: Red Hat Bugzilla #1357032
   https://bugzilla.redhat.com/show_bug.cgi?id=1357032

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

Title:
  System freeze on high memory usage

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  New
Status in Fedora:
  Confirmed

Bug description:
  I run a batch matlab job server here at my lab, running Dapper 6.06 (for the 
LTS). One of the users has submitted a very memory-consuming job, which 
successfully crashes the server. Upon closer inspection, the crash happens like 
this:
  1. I run matlab with the given file (as an ordinary, unpriveleged user)
  2. RAM usage quickly fills up
  3. Once the RAM meter hits 100%, the system freezes: All SSH connections 
freeze up, and while switching VTs directly on the machine works, no new 
processes run - so one can't log in, or do anything if he is logged in. 
(Sometimes typing doesn't work at all)

  Note that the swap - while 7 gig

[Kernel-packages] [Bug 1724639] Re: Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

[Bug Watch Updater]

** Changed in: linux
   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/1724639

Title:
  Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

Status in Linux:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in openSUSE:
  Confirmed

Bug description:
  Installed O.S. on Samsung NC10. Display worked O.K. in text mode so
  the install went smoothly. When the system is rebooted, however,
  switching to graphics mode results in the below described screen
  corruption:-

  Left  Hand Side 80% of screen black with a blue of white pixels and some blue 
lines at the top
  Right Hand Side 20% of screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-16-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian 918 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf034 irq 25'
 Mixer name : 'Realtek ALC272'
 Components : 'HDA:10ec0272,144dca00,0011'
 Controls  : 25
 Simple ctrls  : 12
  CurrentDesktop: LXDE
  Date: Wed Oct 18 18:30:15 2017
  HibernationDevice: RESUME=UUID=c54e130e-6625-4d96-ba75-4efaa6a9da75
  InstallationDate: Installed on 2017-10-18 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=d74a58ab-e96e-4531-a2eb-13f0d1610658 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2009
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 07CA.M002.20090414.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.:bvr07CA.M002.20090414.KTW:bd04/14/2009: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/linux/+bug/1724639/+subscriptions

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

[Kernel-packages] [Bug 1751268] Re: bionic desktop does not boot with external monitor attached - [drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A stuck / vblank wait timed out on crt

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => 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/1751268

Title:
  bionic desktop does not boot with external monitor attached -
  [drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A
  stuck / vblank wait timed out on crtc 1

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  Ubuntu Desktop Bionic up to date

  System doesn't boot with an external monitor attached.

  There is this message in the journal (full journal attached for this
  boot)

  fbcon: inteldrmfb (fb0) is primary device
  [drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A stuck
  vblank wait timed out on crtc 1
  [ cut here ]
  WARNING: CPU: 3 PID: 201 at 
/build/linux-UKCsxy/linux-4.13.0/drivers/gpu/drm/drm_vblank.c:1090 
drm_wait_one_vblank+0x19b/0x1b0 [drm]
  Modules linked in: hid_lenovo uas usb_storage rtsx_usb_sdmmc rtsx_usb 
hid_generic usbhid hid i915 mxm_wmi i2c_algo_bit drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops psmouse ahci libahci drm wmi video
  CPU: 3 PID: 201 Comm: kworker/u8:6 Tainted: G U  
4.13.0-32-generic #35-Ubuntu
  Hardware name: ASUSTeK COMPUTER INC. UX32VD/UX32VD, BIOS UX32VD.214 01/29/2013
  Workqueue: events_unbound async_run_entry_fn
  task: 9760d81cae80 task.stack: b01dc1fb8000
  RIP: 0010:drm_wait_one_vblank+0x19b/0x1b0 [drm]
  RSP: 0018:b01dc1fbb7c8 EFLAGS: 00010282
  RAX: 001f RBX: 9760d708 RCX: 
  RDX:  RSI: 0002 RDI: 0246
  RBP: b01dc1fbb828 R08: 001f R09: 0002af84
  R10: b01dc1fbb7c8 R11: 041b R12: 0001
  R13: 0170 R14: 0001 R15: 
  FS:  () GS:9760eef8() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 7f156d6d68f0 CR3: 00024660a002 CR4: 001606e0
  Call Trace:
   ? wait_woken+0x80/0x80
   ironlake_crtc_enable+0x477/0xc00 [i915]
   ? gen6_write8+0x190/0x190 [i915]
   intel_update_crtc+0x4b/0xe0 [i915]
   intel_update_crtcs+0x5b/0x80 [i915]
   intel_atomic_commit_tail+0x254/0xf90 [i915]
   ? __schedule+0x293/0x880
   intel_atomic_commit+0x3d5/0x490 [i915]
   ? drm_atomic_check_only+0x37b/0x540 [drm]
   drm_atomic_commit+0x4b/0x50 [drm]
   restore_fbdev_mode+0x15e/0x270 [drm_kms_helper]
   drm_fb_helper_restore_fbdev_mode_unlocked+0x2e/0x80 [drm_kms_helper]
   drm_fb_helper_set_par+0x2d/0x60 [drm_kms_helper]
   intel_fbdev_set_par+0x1a/0x70 [i915]
   fbcon_init+0x484/0x650
   visual_init+0xd6/0x130
   do_bind_con_driver+0x1fc/0x410
   do_take_over_console+0x82/0x1a0
   do_fbcon_takeover+0x5c/0xb0
   fbcon_event_notify+0x587/0x780
   notifier_call_chain+0x4a/0x70
   blocking_notifier_call_chain+0x43/0x60
   fb_notifier_call_chain+0x1b/0x20
   register_framebuffer+0x24d/0x360
   drm_fb_helper_initial_config+0x249/0x400 [drm_kms_helper]
   intel_fbdev_initial_config+0x18/0x30 [i915]
   async_run_entry_fn+0x36/0x150
   process_one_work+0x1e7/0x410
   worker_thread+0x4b/0x420
   kthread+0x125/0x140
   ? process_one_work+0x410/0x410
   ? kthread_create_on_node+0x70/0x70
   ret_from_fork+0x1f/0x30
  Code: ff e8 da 3b 4c d6 48 8b 7d a0 48 8d 75 a8 e8 dd 93 50 d6 45 85 ff 0f 85 
0c ff ff ff 44 89 e6 48 c7 c7 d8 eb 3d c0 e8 b6 46 52 d6 <0f> ff e9 f6 fe ff ff 
0f 1f 40 00 66 2e 0f 1f 84 00 00 00 00 00 
  ---[ end trace a1db7ccd0b5e4dfc ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  j-lallement   3671 F pulseaudio
   /dev/snd/controlC0:  j-lallement   3671 F pulseaudio
   /dev/snd/controlC1:  j-lallement   3671 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 23 13:58:39 2018
  InstallationDate: Installed on 2013-09-03 (1633 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force 
drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware   

[Kernel-packages] [Bug 1749715] Re: general protection fault in zfs module

[Bug Watch Updater]

** Changed in: zfs
   Status: Unknown => New

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

Title:
   general protection fault in zfs module

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  Got this call trace during a rsync backup of a machine using ZFS:

  general protection fault:  [#1] SMP 
  Modules linked in: ip6table_filter ip6_tables xt_tcpudp xt_conntrack 
iptable_filter ip_tables x_tables zfs(PO) zunicode(PO) zcommon(PO) znvpair(PO) 
spl(O) zavl(PO) input_leds sch_fq_codel nf_conntrack_ipv6 nf_defrag_ipv6 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack virtio_scsi
  CPU: 0 PID: 4238 Comm: rsync Tainted: P   O4.4.0-112-generic 
#135-Ubuntu
  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  task: 880078a4f2c0 ti: 880047c28000 task.ti: 880047c28000
  RIP: 0010:[]  [] avl_insert+0x33/0xe0 
[zavl]
  RSP: 0018:880047c2bc20  EFLAGS: 00010246
  RAX: 0001 RBX: 880043b46200 RCX: 0001
  RDX:  RSI: 001f880043b46208 RDI: 88005aa0c9a8
  RBP: 880047c2bc20 R08:  R09: 88007d001700
  R10: 880043b46200 R11: 0246 R12: 88005aa0c9a8
  R13: 880043b46200 R14:  R15: 88005aa0c9a8
  FS:  7f04124ec700() GS:88007fc0() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 7ffd25c1cb8c CR3: 47cb CR4: 0670
  Stack:
   880047c2bc68 c0313721  0028
   880043b46200 88005aa0c8c8 6b34 
   88005aa0c9a8 880047c2bcc8 c04609ee 
  Call Trace:
   [] avl_add+0x71/0xa0 [zavl]
   [] zfs_range_lock+0x3ee/0x5e0 [zfs]
   [] ? rrw_enter_read_impl+0xbc/0x160 [zfs]
   [] zfs_read+0xd0/0x3c0 [zfs]
   [] ? profile_path_perm.part.7+0x7d/0xa0
   [] zpl_read_common_iovec+0x80/0xd0 [zfs]
   [] zpl_iter_read+0xa0/0xd0 [zfs]
   [] new_sync_read+0x94/0xd0
   [] __vfs_read+0x26/0x40
   [] vfs_read+0x86/0x130
   [] SyS_read+0x55/0xc0
   [] ? entry_SYSCALL_64_after_swapgs+0xd1/0x18c
   [] entry_SYSCALL_64_fastpath+0x2b/0xe7
  Code: 83 e2 01 48 03 77 10 49 83 e0 fe 8d 04 95 00 00 00 00 55 4c 89 c1 48 83 
47 18 01 83 e0 04 48 83 c9 01 48 89 e5 48 09 c8 4d 85 c0 <48> c7 06 00 00 00 00 
48 c7 46 08 00 00 00 00 48 89 46 10 0f 84 
  RIP  [] avl_insert+0x33/0xe0 [zavl]
   RSP 
  ---[ end trace c4ba4478b6002697 ]---

  
  This is the first time it happens but I'll report any future occurrence in 
here.

  Additional info:

  $ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  $ apt-cache policy linux-image-4.4.0-112-generic zfsutils-linux
  linux-image-4.4.0-112-generic:
Installed: 4.4.0-112.135
Candidate: 4.4.0-112.135
Version table:
   *** 4.4.0-112.135 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
  zfsutils-linux:
Installed: 0.6.5.6-0ubuntu18
Candidate: 0.6.5.6-0ubuntu18
Version table:
   *** 0.6.5.6-0ubuntu18 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.6.5.6-0ubuntu8 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 14 16:19 seq
   crw-rw 1 root audio 116, 33 Feb 14 16:19 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Thu Feb 15 08:45:07 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=db4864d4-cc2e-40c7-bc2b-a14bc0f09c9f ro console=ttyS0 net.ifnames=0 
kaslr nmi_watchd

[Kernel-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

[Bug Watch Updater]

Launchpad has imported 14 comments from the remote bug at
https://bugzilla.suse.com/show_bug.cgi?id=1076898.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-01-20T14:48:14+00:00 Vincent Petry wrote:

Before upgrading, connecting to bluetooth headset from TaoTronics worked
correctly. I also have a cheap bluetooth watch and connecting to it with
bluetoothctl worked fine.

Today I updated Tumbleweed to snapshot 20180117 and I observe the
following behavior:

1) Connecting to bluetooth headset does not work any more even after a fresh 
boot. It connects shortly then disconnects. Both with the Plasma widget and 
with bluetoothctl.
2) Sometimes even after a fresh boot, the plasma widget doesn't show any of the 
known bluetooth devices
3) Strangely connecting to my bluetooth watch still works with bluetoothctl.

>From what I remember, before the update I had bluez-5.47 and now it has
been updated to 5.48.

Furthermore there is a similar report here for Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=1534857

The workaround, as indicated in that link, is to restart the bluetooth
service with "systemctl restart bluetooth". After that the headset can
connect again.

This is on a Dell XPS 13 9333 (different model than the above).

There are already logs in the Fedora ticket, I'll reboot now to try and
gather some from here.

Please let me know if you need further information.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759628/comments/0


On 2018-01-20T14:53:29+00:00 Vincent Petry wrote:

Created attachment 756957
Log with errors

I've attached the log from journalctl from the connection failure.

Please note that during the short time where the connection to the
headset is done, I can hear a beep in the headset which is an indication
from its hardware that the connection was done. However the laptop /
bluez somehow decides to disconnect again.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759628/comments/1


On 2018-01-20T15:06:15+00:00 Vincent Petry wrote:

Okay, so I forgot to mention something: I had the module "btusb"
blacklisted by default. The reason was mostly to save some power when I
don't use bluetooth. I wonder if those Fedora users did the same.

Anyway, now I removed "btusb" from blacklist and rebooted. And now it
all works !

This seems to make sense because I suspect that whenever the bluetooth
service is started at boot time, it needs btusb to be loaded already. So
if you load the module afterwards, you need to restart the service.

At this point, if this is by design, feel free to close as the problem
is solved for me.

---

My bluetooth adapter is built-in, so far so good.

But what happens for people who have bluetooth USB dongles ? Would btusb
only load later once the dongle is plugged in ? If that's the case, then
the problem I describe *might* happen for said users who might need to
restart the bluetooth service.

Now this is marked as regression, it used to work with previous bluez
versions. So not sure if this is something to be fixed upstream or
whether this slight change of behavior / expectation is by design.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759628/comments/2


On 2018-01-24T13:56:16+00:00 Seife-c wrote:

well, blacklisting the driver for the hardware is of course not helping
:-)

I think bluetoothd should still pick up devices that are added after
starting (hot-plugged USB dongles come to my mind).

Anyway, this is not an openSUSE problem, so I'd kindly ask you to report
the issue upstream to the bluez-devel mailinglist at linux-
blueto...@vger.kernel.org

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759628/comments/3


On 2018-01-25T06:46:40+00:00 Vincent Petry wrote:

Thanks, makes sense.

I just observed that resuming from suspend also causes the issue and
requires to restart the bluetooth service.

Thanks for mentioning the mailing list.

It was already reported by someone here on the mailing list:
https://www.spinics.net/lists/linux-bluetooth/msg73824.html.

I've sent my own message there which should appear shortly in the
archives.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759628/comments/4


On 2018-02-06T15:33:32+00:00 Vincent Petry wrote:

Email discussion and investigation in progress: https://marc.info/?l
=linux-bluetooth&m=1517927341128

[Kernel-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

[Bug Watch Updater]

** Changed in: bluez (Fedora)
   Status: Unknown => Fix Released

** Changed in: bluez (Fedora)
   Importance: Unknown => Undecided

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  New
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Unknown

Bug description:
  STEPS TO REPRODUCE:
  1. Connect to Bluetooth audio device
  2. Suspend & Resume
  3. Reconnect to Bluetooth device.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:5025 acl:32 sco:0 events:202 errors:0
TX bytes:5785 acl:32 sco:0 commands:103 errors:0

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

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

[Kernel-packages] [Bug 1746740] Re: XPS13 L322X Bionic (daily dev) touchpad laggy

[Bug Watch Updater]

** Changed in: libinput
   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/1746740

Title:
  XPS13 L322X Bionic (daily dev) touchpad laggy

Status in libinput:
  Incomplete
Status in libinput package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Also, all function keys work as expected, even F6 (keyboard 3-states
  backlight), but OSD picture for this last feature randomly auto-
  triggers.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1876 F pulseaudio
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  1 14:05:22 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- debian-installer/language=fr 
keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libinput/+bug/1746740/+subscriptions

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

[Kernel-packages] [Bug 1153618] Re: Support Realtek RTS5227 card reader

[Bug Watch Updater]

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

Title:
  Support Realtek RTS5227 card reader

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Quantal:
  Fix Released
Status in linux source package in Raring:
  Fix Released
Status in linux package in Fedora:
  Expired

Bug description:
  Support of Realtek RTS5227 card reader is currently missing in the
  kernel, though the support is already in upstream, we need to backport
  it from upstream to enable this device.

  03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd.
  Device [10ec:5227] (rev 01)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1153618/+subscriptions

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

[Kernel-packages] [Bug 1752829] Re: AMD HAINAN (Radeon R5 M330) Clock frequency is 750MHz while it is supposed to be 1030MHz

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => 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/1752829

Title:
  AMD HAINAN (Radeon R5 M330) Clock frequency is 750MHz while it is
  supposed to be 1030MHz

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel source: /drivers/gpu/drm/radeon/si_dpm.c line 2985:

  max_sclk = 75000;

  instead of

  max_sclk = 103000;

  Why is that? I changed it and rebuilt the kernel, and I can say that
  there are absolutely no issues when using the 1030MHz clock, which is
  what it is supposed to be.

  Linux Version: 4.13.0-36-generic

  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yassine3068 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=e9860ff6-0207-40ae-b2dd-115d7c7956b8
  InstallationDate: Installed on 2016-12-19 (439 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 25a7:0701  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \\boot\vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=070ac60f-63d1-48e3-9322-44812d365c40 ro quiet splash radeon.runpm=1 
vt.handoff=7 initrd=boot\initrd.img-4.13.0-36-generic
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-20 (135 days ago)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 11/24/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8136
  dmi.board.vendor: HP
  dmi.board.version: 31.34
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1D:bd11/24/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8136:rvr31.34:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1757012] Re: Upgrade ZFS to v0.7.7

[Bug Watch Updater]

** Changed in: zfs-linux (Debian)
   Status: Unknown => New

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

Title:
  Upgrade ZFS to v0.7.7

Status in zfs-linux package in Ubuntu:
  New
Status in zfs-linux package in Debian:
  New

Bug description:
  v0.7.7 is out:

  https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.7.7

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

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

[Kernel-packages] [Bug 1694859] Re: arm64 kernel crashdump support

[Bug Watch Updater]

** Changed in: makedumpfile (Debian)
   Status: Unknown => Fix Released

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

Title:
  arm64 kernel crashdump support

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in makedumpfile source package in Xenial:
  Fix Released
Status in kexec-tools source package in Yakkety:
  Won't Fix
Status in linux source package in Yakkety:
  Won't Fix
Status in makedumpfile source package in Yakkety:
  Won't Fix
Status in kexec-tools source package in Zesty:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in makedumpfile source package in Zesty:
  Fix Released
Status in kexec-tools source package in Artful:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in makedumpfile source package in Artful:
  In Progress
Status in makedumpfile package in Debian:
  Fix Released

Bug description:
  Note: Updates are being staged at ppa:dannf/arm64-kdump.

  [Impact]
  It is not possible to collect a kernel crash dump from a crashed arm64 server 
for later debugging.

  [Test Case]
  sudo apt install kdump-tools
  (reboot, so crashkernel= is added to the kernel commandline)
  echo c | sudo tee /proc/sysrq-trigger

  Crash dump should occur, with artifacts collected in /var/crash.

  If you want to verify that the dump is usable, install the
  corresponding linux-image--dbgsym package and run:

  sudo crash /usr/lib/debug/boot/vmlinux-
  /var/crash//dump.

  crash should successfully load, placing you at a "crash>" prompt. At that 
prompt, you can issue the 'bt' command to see a backtrace.
  Note: you need crash from zesty (7.1.8-1ubuntu1) or later.

  [Regression Risk]
  = Kernel =
  3 patches here touch code outside of arch/arm64/:

  memblock: add memblock_clear_nomap()
  This adds a new function with no callers, so regression risk is negligible.
  (A later patch adds a call to it under arch/arm64/).

  memblock: add memblock_cap_memory_range()
  This refactors some of the code in memblock_mem_limit_remove_map() into a new 
function. The only existing caller of memblock_mem_limit_remove_map() is under 
arch/arm64/, so the regression risk outside of arm64 is negligible.

  efi/libstub/arm*: Set default address and size cells values for an empty dtb
  Because this code is for EFI platforms that support device-tree, it is 
de-facto ARM-specific (as noted in the patch title).

  For arm64, we have mitigated the risk by explicit regression testing on 
several platforms:
   - Qualcomm QDF2400
   - Cavium ThunderX CRB1S
   - HP m400 (X-Gene)
   - HiSilicon D05 (Hi07)

  = kexec-tools =
  == zesty ==
  For zesty, 10 patches are required to add kdump support.

  0001-kexec-extend-the-semantics-of-kexec_iomem_for_each_l.patch:
  This modifies a function used on armhf & x86. The description explains the 
change, and why it does not impact those archs:

  -
  The current users of kexec_iomem_for_each_line(), arm, sh and x86, will not
  be affected by this change because
  * arm
    The callback function only returns -1 or 0, and the return value of
    kexec_iomem_for_each_line() will never be used.
  * sh, x86
    The callback function may return (-1 for sh,) 0 or 1, but always returns
    1 once we have reached the maximum number of entries allowed.
    Even so the current kexec_iomem_for_each_line() counts them up.
    This change actually fixes this bug.
  -

  0002-kexec-generalize-and-rename-get_kernel_stext_sym.patch:
  This generalizes a function that was duplicated by arm & x86 and makes it 
common so arm64 can use it.

  The remaining 8 of these only touch code in kexec/arch/arm64, so
  regression risk for other architectures is negligible.

  Finally, I have tested this update on both i386 and amd64 VMs. i386
  crashes do not currently work in zesty (filed LP: #1699874), and my
  test results show no change there. amd64 worked before, and continues
  to work with these changes.

  == yakkety ==
  Since yakkety is based on an older upstream, 6 additional patches are 
required:

  arm-fix-get_kernel_stext_sym-to-close-its-file.patch:
  This is a cleanup patch, cherry-picked because it allows later patches to 
apply w/o backporting. ARM-specific.

  kexec-add-max_size-to-memory_ranges.patch:
  Adds a new element to struct, to be used by later commits.

  kexec-add-generic-helper-to-add-to-memoryq_regions.patch,
  kexec-add-mem_regions-sorting-implementation.patch,
  kexec-add-helper-to-exlude-a-region-from-a-set-of-me.patch,
  kexec-fix-mem_regions_sort.patch:
  These patches only add new functions, which will be used by later patches.

  kexec-arch-i386-Add-support-f

[Kernel-packages] [Bug 1153618] Re: Support Realtek RTS5227 card reader

[Bug Watch Updater]

** Changed in: linux (Fedora)
   Status: Won't Fix => 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/1153618

Title:
  Support Realtek RTS5227 card reader

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Quantal:
  Fix Released
Status in linux source package in Raring:
  Fix Released
Status in linux package in Fedora:
  Confirmed

Bug description:
  Support of Realtek RTS5227 card reader is currently missing in the
  kernel, though the support is already in upstream, we need to backport
  it from upstream to enable this device.

  03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd.
  Device [10ec:5227] (rev 01)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1153618/+subscriptions

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

[Kernel-packages] [Bug 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"

[Bug Watch Updater]

** Changed in: gnome-bluetooth
   Status: Unknown => Fix Released

** Changed in: gnome-bluetooth
   Importance: Unknown => Medium

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

Title:
  Bluetooth icon shows "Off" and the only option given below it is "Turn
  Off"

Status in GNOME Bluetooth:
  Fix Released
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  See video. I have installed bluetooth, blueman, bluez but it makes no
  difference to a broken interface to control bluetooth under Gnome
  17.10, as shown in the attached video.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluetooth 5.46-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 17 22:32:30 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 20BXCTO1WW
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed 
root=UUID=02bd5120-a925-442c-a0dd-1cce59920632 ro quiet splash 
psmouse.synaptics_intertouch=0 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET54WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  hciconfig:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1738838/+subscriptions

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

[Kernel-packages] [Bug 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"

[Bug Watch Updater]

** Changed in: gnome-bluetooth
   Status: Confirmed => Invalid

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

Title:
  Bluetooth icon shows "Off" and the only option given below it is "Turn
  Off"

Status in GNOME Bluetooth:
  Invalid
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  See video. I have installed bluetooth, blueman, bluez but it makes no
  difference to a broken interface to control bluetooth under Gnome
  17.10, as shown in the attached video.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluetooth 5.46-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 17 22:32:30 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 20BXCTO1WW
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed 
root=UUID=02bd5120-a925-442c-a0dd-1cce59920632 ro quiet splash 
psmouse.synaptics_intertouch=0 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET54WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  hciconfig:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1738838/+subscriptions

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

[Kernel-packages] [Bug 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"

[Bug Watch Updater]

** Changed in: gnome-bluetooth
   Status: Unknown => Confirmed

** Changed in: gnome-bluetooth
   Importance: Unknown => Low

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

Title:
  Bluetooth icon shows "Off" and the only option given below it is "Turn
  Off"

Status in GNOME Bluetooth:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  See video. I have installed bluetooth, blueman, bluez but it makes no
  difference to a broken interface to control bluetooth under Gnome
  17.10, as shown in the attached video.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluetooth 5.46-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 17 22:32:30 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 20BXCTO1WW
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed 
root=UUID=02bd5120-a925-442c-a0dd-1cce59920632 ro quiet splash 
psmouse.synaptics_intertouch=0 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET54WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  hciconfig:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1738838/+subscriptions

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

[Kernel-packages] [Bug 1746740] Re: XPS13 L322X Bionic (daily dev) touchpad laggy

[Bug Watch Updater]

** Changed in: libinput
   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/1746740

Title:
  XPS13 L322X Bionic (daily dev) touchpad laggy

Status in libinput:
  Confirmed
Status in libinput package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Also, all function keys work as expected, even F6 (keyboard 3-states
  backlight), but OSD picture for this last feature randomly auto-
  triggers.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1876 F pulseaudio
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  1 14:05:22 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- debian-installer/language=fr 
keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libinput/+bug/1746740/+subscriptions

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

[Kernel-packages] [Bug 1436945] Re: devel: consider fq_codel as the default qdisc for networking

[Bug Watch Updater]

** Changed in: systemd (Debian)
   Status: Unknown => New

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

Title:
  devel: consider fq_codel as the default qdisc for networking

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  New

Bug description:
  This was raised on the kernel-team@ mailing list, we should look at
  this if other distros are starting to move.

  ===

  Date: Tue, 24 Mar 2015 10:54:37 -0700 
 
  From: Dave Taht  
 
  To: Joseph Salisbury  
 
  Cc: Kernel Team , ubuntu-de...@lists.ubuntu.com 
 
  Subject: Re: Minutes from the Ubuntu Kernel Team meeting, 2015-03-24  
 

 
  I must confess I had hoped ubuntu would adopt fq_codel as the default 
 
  qdisc in this go-around. It is still not quite part of fedora´s   
 
  default either, but is now in arch, (and nearly everyone else 
 
  downstream from systemd), and has long been the default in openwrt,   
 
  and at this point, just requires a single sysctl to enable.   
 

 
  It certainly could use more widespread testing, perhaps in the next release?  
 

 
  d@nuc-client:~$ cat /etc/sysctl.d/10-bufferbloat.conf 
 
  net.core.default_qdisc=fq_codel

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

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

[Kernel-packages] [Bug 1746740] Re: XPS13 L322X Bionic (daily dev) touchpad laggy

[Bug Watch Updater]

** Changed in: libinput
   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/1746740

Title:
  XPS13 L322X Bionic (daily dev) touchpad laggy

Status in libinput:
  Incomplete
Status in libinput package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Also, all function keys work as expected, even F6 (keyboard 3-states
  backlight), but OSD picture for this last feature randomly auto-
  triggers.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1876 F pulseaudio
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  1 14:05:22 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- debian-installer/language=fr 
keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libinput/+bug/1746740/+subscriptions

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

[Kernel-packages] [Bug 1746740] Re: XPS13 L322X Bionic (daily dev) touchpad laggy

[Bug Watch Updater]

** Changed in: libinput
   Status: Unknown => Confirmed

** Changed in: libinput
   Importance: Unknown => 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/1746740

Title:
  XPS13 L322X Bionic (daily dev) touchpad laggy

Status in libinput:
  Confirmed
Status in libinput package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Also, all function keys work as expected, even F6 (keyboard 3-states
  backlight), but OSD picture for this last feature randomly auto-
  triggers.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1876 F pulseaudio
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  1 14:05:22 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- debian-installer/language=fr 
keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libinput/+bug/1746740/+subscriptions

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

[Kernel-packages] [Bug 1745492] Re: Backport of Debian bug #785714 for Xenial to avoid unclean reboots

[Bug Watch Updater]

** Changed in: kexec-tools (Debian)
   Status: Unknown => Fix Released

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

Title:
  Backport of Debian bug #785714 for Xenial to avoid unclean reboots

Status in kexec-tools package in Ubuntu:
  New
Status in kexec-tools package in Debian:
  Fix Released

Bug description:
  Debian bug #785714 is a fairly substantial one, as it causes unclean
  shutdowns.  In our case, KVM hosts with many guests will begin to
  partially shutdown a couple before kexec jumps the gun and reboots the
  machine.  Without this fix, kexec is of only minimal use on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1745492/+subscriptions

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

[Kernel-packages] [Bug 1742630] Re: PTI Kernels: Booting from 4.13 leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci]

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => 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/1742630

Title:
  PTI Kernels: Booting from 4.13 leads to Oops: NULL pointer dereference
  - RIP: isci_task_abort_task+0x30/0x3e0 [isci]

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  I cannot boot from 4.13.0-21-generic

  Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0
  [isci]

  This Kernel bug was already fixed in Debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882414

  Relevant discussion:
  https://marc.info/?l=linux-scsi&m=151523964725984&w=2

  Ubuntu needs to fix this, because otherwise _many_ people will
  complain about crashes when they upgrade from 4.9 (or 4.4) to 4.13,
  which Ubuntu defined as their new “HWE” kernel.

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

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

[Kernel-packages] [Bug 1724639] Re: Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

[Bug Watch Updater]

Launchpad has imported 15 comments from the remote bug at
https://bugzilla.opensuse.org/show_bug.cgi?id=1058870.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2017-09-15T13:31:31+00:00 Axel Braun wrote:

Created attachment 740759
Screenshot

Did an update on an old ASUS eeePC to the above TW. With Kernel 4.13.1 2/3 of 
the screen is black. Switching back to Kernel 4.12.11 fixes the problem. See 
attached screenshot
Graphics chip is a Intel mobile GM945 GM
Let me know if I can provide further information

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/comments/0


On 2017-09-18T14:28:03+00:00 Ada-lovelace wrote:

I have the same problem with a Lenovo ThinkPad 13 (Ultrabook) with Intel
Come i5. I receive a error message with "Failed to start Setup Virtual
System Console". After that I have a black window.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/comments/1


On 2017-09-18T14:32:45+00:00 Ada-lovelace wrote:

I have the same problem with a Lenovo ThinkPad S2 (Ultrabook) with Intel
Core i5. I receive a error message with "Failed to start Setup Virtual
System Console". After that I have a black window.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/comments/2


On 2017-09-18T16:03:50+00:00 Ada-lovelace wrote:

My graphic card is a Intel(R) Graphics 520.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/comments/3


On 2017-09-19T14:15:32+00:00 Jslaby-h wrote:

Could you attach output of dmesg?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/comments/4


On 2017-09-20T06:09:49+00:00 Axel Braun wrote:

Created attachment 741173
dmesg

It should be noted that the screen distortion appears in runlevel 3 as
well. so it is not an issue of the video driver!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/comments/5


On 2017-09-21T07:27:27+00:00 Jslaby-h wrote:

Hmm...

Can you create a bug at https://bugs.freedesktop.org -- product DRI,
component DRM/Intel?

plane B assertion failure, should be off on pipe B but is still active
[ cut here ]
WARNING: CPU: 1 PID: 259 at ../drivers/gpu/drm/i915/intel_display.c:1252 
assert_planes_disabled+0x128/0x140 [i915]
Modules linked in: ata_piix i915(+) serio_raw i2c_algo_bit uhci_hcd ehci_pci 
drm_kms_helper ehci_hcd syscopyarea sysfillrect sysimgblt usbcore fb_sys_fops 
drm video button sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua
CPU: 1 PID: 259 Comm: systemd-udevd Not tainted 4.13.1-1-pae #1
Hardware name: ASUSTeK Computer INC. 901/901, BIOS 190303/17/2009
task: f4ae4700 task.stack: f4b3c000
EIP: assert_planes_disabled+0x128/0x140 [i915]
EFLAGS: 00010286 CPU: 1
EAX: 0046 EBX: f4bbc000 ECX: f71eb340 EDX: f71e486c
ESI: 0001 EDI: 0001 EBP: f4b3dbe4 ESP: f4b3dbc8
 DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
CR0: 80050033 CR2: b7152000 CR3: 34aeca60 CR4: 06f0
Call Trace:
 ? intel_disable_pipe+0x45/0x220 [i915]
 ? i9xx_crtc_disable+0x5c/0x3a0 [i915]
 ? drm_connector_list_iter_next+0x71/0xa0 [drm]
 ? drm_atomic_add_affected_connectors+0xd0/0xf0 [drm]
 ? intel_crtc_disable_noatomic+0xb5/0x290 [i915]
 ? intel_modeset_setup_hw_state+0xa58/0xc40 [i915]
 ? intel_modeset_setup_hw_state+0xa85/0xc40 [i915]
 ? intel_modeset_init+0x4d1/0xea0 [i915]
 ? intel_setup_gmbus+0x1e1/0x270 [i915]
 ? i915_driver_load+0xa4c/0x1330 [i915]
 ? local_pci_probe+0x35/0x80
 ? pci_device_probe+0x158/0x170
 ? driver_probe_device+0x2b9/0x410
 ? __driver_attach+0x99/0xe0
 ? driver_probe_device+0x410/0x410
 ? bus_for_each_dev+0x4f/0x80
 ? driver_attach+0x19/0x20
 ? driver_probe_device+0x410/0x410
 ? bus_add_driver+0x187/0x230
 ? 0xf8306000
 ? driver_register+0x56/0xd0
 ? 0xf8306000
 ? do_one_initcall+0x46/0x170
 ? do_init_module+0x21/0x1d9
 ? do_init_module+0x50/0x1d9
 ? load_module+0x1435/0x1980
 ? SyS_finit_module+0x79/0xc0
 ? do_fast_syscall_32+0x71/0x150
 ? entry_SYSENTER_32+0x4e/0x7c
Code: ff 83 c4 10 e9 44 ff ff ff 57 68 a0 91 29 f8 e8 cc 8c 2d e0 0f ff 58 5a 
e9 30 ff ff ff ff 75 f0 50 68 d8 91 29 f8 e8 b5 8c 2d e0 <0f> ff 83 c4 0c e9 3e 
ff ff ff 8d b4 26 00 00 00 00 8d bc 27 00
---[ end trace 0e7d08f54709149f ]---

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/comments/6

[Kernel-packages] [Bug 1735032] Re: rebase iproute2 to newer version

[Bug Watch Updater]

** Changed in: iproute2 (Debian)
   Status: New => Fix Released

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

Title:
  rebase iproute2 to newer version

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 package in Debian:
  Fix Released

Bug description:
  Ubuntu's iproute2 version [1] is still many kernel versions behind.
  It's still on 4.9, whereas shipped kernel is on 4.13 in the meantime!

  iproute2 is developed alongside the kernel, so new kernel features
  will also get updates to iproute2 whenever they change related code.
  Meaning, these features cannot be used out of the box if the actual
  shipped iproute2 version here is not on par with the kernel version
  (the release tags have 1:1 mapping with kernel releases) [2].

  Please consider updating iproute2 package, and please also consider
  updating it regularly along with officially shipped kernels in Ubuntu,
  so that all the added networking features can be used there without
  forcing users to do a manual compilation of iproute2.

  Thanks,
  Daniel

[1] 
http://changelogs.ubuntu.com/changelogs/pool/main/i/iproute2/iproute2_4.9.0-1ubuntu2/changelog
[2] 
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/refs/tags

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

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

[Kernel-packages] [Bug 1724639] Re: Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

[Bug Watch Updater]

** Changed in: linux
   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/1724639

Title:
  Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in openSUSE:
  Unknown

Bug description:
  Installed O.S. on Samsung NC10. Display worked O.K. in text mode so
  the install went smoothly. When the system is rebooted, however,
  switching to graphics mode results in the below described screen
  corruption:-

  Left  Hand Side 80% of screen black with a blue of white pixels and some blue 
lines at the top
  Right Hand Side 20% of screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-16-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian 918 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf034 irq 25'
 Mixer name : 'Realtek ALC272'
 Components : 'HDA:10ec0272,144dca00,0011'
 Controls  : 25
 Simple ctrls  : 12
  CurrentDesktop: LXDE
  Date: Wed Oct 18 18:30:15 2017
  HibernationDevice: RESUME=UUID=c54e130e-6625-4d96-ba75-4efaa6a9da75
  InstallationDate: Installed on 2017-10-18 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=d74a58ab-e96e-4531-a2eb-13f0d1610658 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2009
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 07CA.M002.20090414.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.:bvr07CA.M002.20090414.KTW:bd04/14/2009: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/linux/+bug/1724639/+subscriptions

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

[Kernel-packages] [Bug 1153618] Re: Support Realtek RTS5227 card reader

[Bug Watch Updater]

** Changed in: linux (Fedora)
   Status: Confirmed => Won't Fix

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

Title:
  Support Realtek RTS5227 card reader

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Quantal:
  Fix Released
Status in linux source package in Raring:
  Fix Released
Status in linux package in Fedora:
  Won't Fix

Bug description:
  Support of Realtek RTS5227 card reader is currently missing in the
  kernel, though the support is already in upstream, we need to backport
  it from upstream to enable this device.

  03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd.
  Device [10ec:5227] (rev 01)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1153618/+subscriptions

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

[Kernel-packages] [Bug 1724639] Re: Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

[Bug Watch Updater]

** Changed in: linux
   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/1724639

Title:
  Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in openSUSE:
  Unknown

Bug description:
  Installed O.S. on Samsung NC10. Display worked O.K. in text mode so
  the install went smoothly. When the system is rebooted, however,
  switching to graphics mode results in the below described screen
  corruption:-

  Left  Hand Side 80% of screen black with a blue of white pixels and some blue 
lines at the top
  Right Hand Side 20% of screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-16-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian 918 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf034 irq 25'
 Mixer name : 'Realtek ALC272'
 Components : 'HDA:10ec0272,144dca00,0011'
 Controls  : 25
 Simple ctrls  : 12
  CurrentDesktop: LXDE
  Date: Wed Oct 18 18:30:15 2017
  HibernationDevice: RESUME=UUID=c54e130e-6625-4d96-ba75-4efaa6a9da75
  InstallationDate: Installed on 2017-10-18 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=d74a58ab-e96e-4531-a2eb-13f0d1610658 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2009
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 07CA.M002.20090414.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.:bvr07CA.M002.20090414.KTW:bd04/14/2009: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/linux/+bug/1724639/+subscriptions

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

[Kernel-packages] [Bug 1699772] Re: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic | Regressio

[Bug Watch Updater]

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

Title:
  linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-
  image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-
  image-3.13.0-121-generic | Regression: many user-space apps crashing

Status in LibreOffice:
  Won't Fix
Status in commons-daemon package in Ubuntu:
  Confirmed
Status in eclipse package in Ubuntu:
  Confirmed
Status in imagej package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in octave package in Ubuntu:
  Confirmed
Status in python-jpype package in Ubuntu:
  Confirmed
Status in rustc package in Ubuntu:
  Confirmed
Status in scilab package in Ubuntu:
  Confirmed
Status in linux package in Debian:
  Fix Released

Bug description:
  Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10)

  linux-image-4.4.0-81-generic appears to contain a regression, probably
  related to the CVE-2017-1000364 fix backport / patch.

  Using this kernel, the Oracle Java browser plugin always crashes
  during stack-related actions on initialization. This means, the plugin
  completely stopped working.

  
  It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to 
CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also 
contains a fix for CVE-2017-1000364.


  uname -a:

  > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06
  UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


  I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as
  well as Iceweasel / Firefox/3.5.16 in a chroot.

  Using linux-image-4.4.0-81-generic it crashes in all combinations
  while with both other kernels it works.

  
  I was not able to obtain any detailed crash information from Firefox 51.0.1, 
but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace 
which shows the relation to stack operations performed by the plugin, even 
without proper debug symbols:

  
  > (gdb) bt full
  > #0  0x7fa06d805307 in _expand_stack_to(unsigned char*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #1  0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, 
unsigned char*) ()
  >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #2  0x7fa06d80cf0b in JVM_handle_linux_signal () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #3  0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #4  

  
  I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6.

  
  The crash will be triggered by any applet, for example the test applet at:

  * https://java.com/en/download/installed8.jsp

  
  I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow 
apparently does not allow me to use apport to report this bug:

  > $ LANG= apport-cli linux-image-4.4.0-81-generic
  > 
  > *** Collecting problem information
  > 
  > The collected information can be sent to the developers to improve the
  > application. This might take a few minutes.
  > .
  > 
  > *** Problem in linux-image-4.4.0-81-generic
  > 
  > The problem cannot be reported:
  > 
  > This is not an official KDE package. Please remove any third party package 
and try again.

  If someone can tell me how to get apport working for this package, I
  can use it to collect additional information, but (unfortunately?) the
  problem should be fairly easy to reproduce...

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+subscriptions

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

[Kernel-packages] [Bug 1724639] Re: Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

[Bug Watch Updater]

** Changed in: linux
   Status: Incomplete => Confirmed

** Changed in: linux
   Importance: Medium => 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/1724639

Title:
  Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in openSUSE:
  Unknown

Bug description:
  Installed O.S. on Samsung NC10. Display worked O.K. in text mode so
  the install went smoothly. When the system is rebooted, however,
  switching to graphics mode results in the below described screen
  corruption:-

  Left  Hand Side 80% of screen black with a blue of white pixels and some blue 
lines at the top
  Right Hand Side 20% of screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-16-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian 918 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf034 irq 25'
 Mixer name : 'Realtek ALC272'
 Components : 'HDA:10ec0272,144dca00,0011'
 Controls  : 25
 Simple ctrls  : 12
  CurrentDesktop: LXDE
  Date: Wed Oct 18 18:30:15 2017
  HibernationDevice: RESUME=UUID=c54e130e-6625-4d96-ba75-4efaa6a9da75
  InstallationDate: Installed on 2017-10-18 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=d74a58ab-e96e-4531-a2eb-13f0d1610658 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2009
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 07CA.M002.20090414.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.:bvr07CA.M002.20090414.KTW:bd04/14/2009: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/linux/+bug/1724639/+subscriptions

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

[Kernel-packages] [Bug 1729736] Re: 10de:1c8c [MSI] Module nouveau fails to manage GeForce GTX 1050 Ti Mobile

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => 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/1729736

Title:
  10de:1c8c [MSI] Module nouveau fails to manage GeForce GTX 1050 Ti
  Mobile

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Trying to use 'Nvidia GeForce GTX 1050 Ti Mobile' with 'Ubuntu 17.10
  (Artful)' :

  - Linux kernel 4.13.0-16 from 'Ubuntu 17.10 (Artful)' systematically
  fails (1 CPU stuck).

  - Linux kernel 4.14.0-041400rc7 from http://kernel.ubuntu.com/~kernel-
  ppa/mainline seems to succeed.

  See attached kern.log

  
  After reboot on Linux kernel 4.13.0-16 with nouveau blacklisted :

  $ lspci -nn -v -s 1:0.0

  01:00.0 3D controller [0302]: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti 
Mobile] [10de:1c8c] (rev a1)
Subsystem: Micro-Star International Co., Ltd. [MSI] GP107M [GeForce GTX 
1050 Ti Mobile] [1462:11c8]
Flags: bus master, fast devsel, latency 0, IRQ 255
Memory at de00 (32-bit, non-prefetchable) [size=16M]
Memory at c000 (64-bit, prefetchable) [size=256M]
Memory at d000 (64-bit, prefetchable) [size=32M]
I/O ports at e000 [disabled] [size=128]
Expansion ROM at df00 [disabled] [size=512K]
Capabilities: 
Kernel modules: nvidiafb, nouveau

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

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

[Kernel-packages] [Bug 1724639] Re: Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => Incomplete

** Changed in: linux
   Importance: Unknown => 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/1724639

Title:
  Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in openSUSE:
  Unknown

Bug description:
  Installed O.S. on Samsung NC10. Display worked O.K. in text mode so
  the install went smoothly. When the system is rebooted, however,
  switching to graphics mode results in the below described screen
  corruption:-

  Left  Hand Side 80% of screen black with a blue of white pixels and some blue 
lines at the top
  Right Hand Side 20% of screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-16-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian 918 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf034 irq 25'
 Mixer name : 'Realtek ALC272'
 Components : 'HDA:10ec0272,144dca00,0011'
 Controls  : 25
 Simple ctrls  : 12
  CurrentDesktop: LXDE
  Date: Wed Oct 18 18:30:15 2017
  HibernationDevice: RESUME=UUID=c54e130e-6625-4d96-ba75-4efaa6a9da75
  InstallationDate: Installed on 2017-10-18 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=d74a58ab-e96e-4531-a2eb-13f0d1610658 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2009
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 07CA.M002.20090414.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.:bvr07CA.M002.20090414.KTW:bd04/14/2009: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/linux/+bug/1724639/+subscriptions

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

[Kernel-packages] [Bug 1411487] Re: [GNOME gnome-control-center] Not work AD2P in device HV-800 (problem random)

[Bug Watch Updater]

** Changed in: gnome-bluetooth
   Status: Incomplete => Expired

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

Title:
  [GNOME gnome-control-center] Not work AD2P in device HV-800 (problem
  random)

Status in GNOME Bluetooth:
  Expired
Status in bluez package in Ubuntu:
  Incomplete
Status in gnome-bluetooth package in Ubuntu:
  Incomplete

Bug description:
  Attach video.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: bluez 4.101-0ubuntu22
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jan 15 23:27:34 2015
  InstallationDate: Installed on 2014-09-25 (113 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.18.0-9-generic 
root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf 
nomdmonisw vt.handoff=7 init=/lib/systemd/systemd
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: C4:85:08:6C:01:0A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:3923189 acl:28369 sco:67913 events:523 errors:0
TX bytes:3351604 acl:260 sco:65569 commands:111 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1411487/+subscriptions

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

[Kernel-packages] [Bug 1140716] Re: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge

[Bug Watch Updater]

** Changed in: dri
   Status: Confirmed => Won't Fix

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

Title:
  [regression] 3.5.0-26-generic and  3.2.0-39-generic GPU hangs on
  Sandybridge

Status in DRI:
  Won't Fix
Status in Mesa:
  Unknown
Status in linux package in Ubuntu:
  Invalid
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in linux source package in Precise:
  Fix Committed
Status in linux-lts-quantal source package in Precise:
  Fix Committed
Status in linux-lts-raring source package in Precise:
  Invalid
Status in mesa source package in Precise:
  Triaged
Status in linux source package in Quantal:
  Invalid
Status in linux-lts-quantal source package in Quantal:
  Invalid
Status in linux source package in Raring:
  Invalid
Status in linux-lts-quantal source package in Raring:
  Invalid
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Won't Fix

Bug description:
  I'm getting errors about GPU hangs every minute or so (usually only
  when using FF and scrolling a webpage or something). I also get an
  annoying ubuntu dialog saying there is a "system error".

  This didn't happen with 3.5.0-24-generic.

  Here is the dmesg:
  [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26285.658405] [ cut here ]
  [26285.658472] WARNING: at 
/build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 
gen6_enable_rps+0x706/0x710 [i915]()
  [26285.658474] Hardware name: SATELLITE Z830
  [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate 
libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 
snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm 
arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel 
snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep 
iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi 
rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer 
snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap 
soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei 
video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc 
lp parport e1000e ahci libahci [last unloaded: sdhci]
  [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic 
#40-Ubuntu
  [26285.658539] Call Trace:
  [26285.658549]  [] warn_slowpath_common+0x7f/0xc0
  [26285.658553]  [] warn_slowpath_null+0x1a/0x20
  [26285.658569]  [] gen6_enable_rps+0x706/0x710 [i915]
  [26285.658584]  [] intel_modeset_init_hw+0x66/0xa0 [i915]
  [26285.658595]  [] i915_reset+0x1a4/0x6e0 [i915]
  [26285.658601]  [] ? __switch_to+0x12b/0x420
  [26285.658612]  [] i915_error_work_func+0xc3/0x110 [i915]
  [26285.658618]  [] process_one_work+0x12a/0x420
  [26285.658629]  [] ? gen6_pm_rps_work+0xe0/0xe0 [i915]
  [26285.658632]  [] worker_thread+0x12e/0x2f0
  [26285.658636]  [] ? manage_workers.isra.26+0x200/0x200
  [26285.658640]  [] kthread+0x93/0xa0
  [26285.658644]  [] kernel_thread_helper+0x4/0x10
  [26285.658649]  [] ? kthread_freezable_should_stop+0x70/0x70
  [26285.658652]  [] ? gs_change+0x13/0x13
  [26285.658654] ---[ end trace 59c6162fdfcbffee ]---
  [26756.021167] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26756.021426] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26766.014093] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26766.014397] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26932.376233] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26932.376544] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26932.384285] [ cut here ]
  [26932.384354] WARNING: at 
/build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 
gen6_enable_rps+0x706/0x710 [i915]()
  [26932.384356] Hardware name: SATELLITE Z830
  [26932.384358] Modules linked in: sdhci_pci sdhci 

[Kernel-packages] [Bug 1041790] Re: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0

[Bug Watch Updater]

** Changed in: xserver-xorg-video-intel
   Status: Confirmed => Won't Fix

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

Title:
  [snb] GPU lockup  IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround
  i915.semaphores=0

Status in xf86-video-intel:
  Won't Fix
Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  Triaged

Bug description:
  X locks up periodically for a 2 to ten seconds at a time and this
  crash log gets generated. It's significantly more than several times a
  day but not quite continuous. If you indeed have this bug, that should
  stop the lockups from happening. Irrespective, please file a new bug
  report so your hardware may be tracked.

  WORKAROUND: Edit your /etc/default/grub from:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

  to:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.semaphores=0"

  run the following and reboot:
  sudo update-grub

  The side effects of this is rendering throughput is dropped by 10%
  with SNA, or as much as 3x with UXA. OpenGL performance is likely to
  be reduced by about 30%. More CPU time is spent waiting for the GPU
  with rc6 disabled, so increased power consumption.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: xserver-xorg-video-intel 2:2.20.3-0ubuntu1
  Uname: Linux 3.6.0-rc3-git-20120826.1015 x86_64
  ApportVersion: 2.5.1-0ubuntu2
  Architecture: amd64
  Chipset: sandybridge-m-gt2
  Date: Sun Aug 26 16:06:32 2012
  DistroCodename: quantal
  DistroVariant: ubuntu
  DuplicateSignature: [sandybridge-m-gt2] GPU lockup  IPEHR: 0x0b160001 IPEHR: 
0x0b140001 Ubuntu 12.10
  EcryptfsInUse: Yes
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  GpuHangFrequency: Continuously
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
  InterpreterPath: /usr/bin/python3.2mu
  MachineType: Dell Inc. Dell System XPS L502X
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.0-rc3-git-20120826.1015 
root=UUID=135c8090-427c-460a-909d-eff262cd44b6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu3
   libdrm2  2.4.38-0ubuntu2
   xserver-xorg-video-intel 2:2.20.3-0ubuntu1
  SourcePackage: xserver-xorg-video-intel
  Title: [sandybridge-m-gt2] GPU lockup  IPEHR: 0x0b160001 IPEHR: 0x0b140001
  UdevDb: Error: [Errno 2] No such file or directory: 'udevadm'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 05/29/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1041790/+subscriptions

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

[Kernel-packages] [Bug 1603715] Re: bluetooth unavailable after rfkill hard (or soft) unblocking and after suspend/resume

[Bug Watch Updater]

** Changed in: bluez
   Status: New => Incomplete

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

Title:
  bluetooth unavailable after rfkill hard (or soft) unblocking and after
  suspend/resume

Status in Bluez Utilities:
  Incomplete
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  DELL Latitude E5510 has a hardware switch to disable and enable
  bluetooth and wifi devices ("hard blocking" in terms of rfkill). In
  terms of wifi, this works great: After hard unblocking, the device
  resumes back to normal operation without any manual intervention. That
  was also working with bluetooth as of ubuntu 14.04, kernel 4.2.

  In ubuntu 16.04, kernel 4.4.0-31-generic, together with systemd, this
  is not working any more:

  After hard blocking and unblocking

  - bluetooth is not working at all
  - the applet-indicator remains gray
  - bluetooth cannot be enabled with the applet-indicator (see 
https://storage6.static.itmages.com/i/16/0717/h_1468721829_7715160_83cd33bfba.png).
 Applet-indicator remains gray
  - rfkill list tells me that the kernel knows about the hard unblocking (turns 
from "yes" to "no"):
  rfkill list bluetooth
  2: dell-bluetooth: Bluetooth
   Soft blocked: no
   Hard blocked: no
  8: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no

  The device is a
  sudo lsusb
  Bus 002 Device 010: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module

  Workaround: After a

  sudo service bluetooth restart

  the bluetooth device turns back to normal operation and the applet-
  indicator turns from gray to black (available).

  Suggested fix: Make the workaround obsolete.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jul 17 04:00:58 2016
  InstallationDate: Installed on 2014-11-29 (595 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Latitude E5510
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-31-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (31 days ago)
  dmi.bios.date: 12/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 023HKR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5510
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1603715/+subscriptions

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

[Kernel-packages] [Bug 1730864] Re: Shutdown crashing when connected to AC adapter

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => 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/1730864

Title:
  Shutdown crashing when connected to AC adapter

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello there,

  I'm using Ubuntu 17.10 (fully updated) and my system is crashing at
  shutdown when connected to an AC adapter.

  The error is:

  Nov  6 22:16:49 rene-Inspiron-5447 kernel: [  248.294280] [drm:atom_op_jump 
[amdgpu]] *ERROR* atombios stuck in loop for more than 5secs aborting
  Nov  6 22:16:49 rene-Inspiron-5447 kernel: [  248.294336] 
[drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck 
executing 75A8 (len 272, WS 0, PS 4) @ 0x75F1
  Nov  6 22:16:49 rene-Inspiron-5447 kernel: [  248.294384] 
[drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck 
executing 640C (len 68, WS 0, PS 8) @ 0x6430]

  This behavior is only happening when my laptop is charging. When
  running on battery I got a clean shutdown/reboot.

  Already tried to run the latest kernel package (from Mainline) and the
  problem is exactly the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rene   1249 F pulseaudio
   /dev/snd/controlC0:  rene   1249 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Nov  8 01:00:51 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=0f3b9237-1086-430d-be15-043b9ca00fd2
  InstallationDate: Installed on 2017-11-06 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Dell Inc. Inspiron 5447
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=1237aa76-9a2f-4a06-8552-526f124914ff ro quiet splash 
acpi_backlight=intel_backlight
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0MHP6R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A10
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/25/2016:svnDellInc.:pnInspiron5447:pvrA10:rvnDellInc.:rn0MHP6R:rvrA00:cvnDellInc.:ct8:cvrA10:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5447
  dmi.product.version: A10
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

[Bug Watch Updater]

Launchpad has imported 27 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1460789.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2017-06-12T18:51:16+00:00 Christian wrote:

This is a Dell XPS 13 connected to the network via the TB16 dock.
Kernel is: Linux ag13.local 4.12.0-0.rc3.git0.2.fc27.x86_64 #1 SMP Tue May 30 
19:36:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Host controller of the dock:
09:00.0 USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller

USB network interface in the dock:
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/7p, 5000M
|__ Port 2: Dev 3, If 0, Class=Vendor Specific Class, Driver=r8152, 
5000M

[32930.573816] usb 4-1.2: new SuperSpeed USB device number 3 using xhci_hcd
[32930.591744] usb 4-1.2: New USB device found, idVendor=0bda, idProduct=8153
[32930.591752] usb 4-1.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=6
[32930.591757] usb 4-1.2: Product: USB 10/100/1000 LAN
[32930.591761] usb 4-1.2: Manufacturer: Realtek
[32930.591766] usb 4-1.2: SerialNumber: 0100
[32930.739428] usb 4-1.2: reset SuperSpeed USB device number 3 using xhci_hcd

I *sometimes* get the following in the log and with that the ethernet port 
stops working. 
Jun 12 19:00:04 ag13.local kernel: xhci_hcd :09:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
Jun 12 19:00:04 ag13.local kernel: xhci_hcd :09:00.0: Looking for event-dma 
0001c3eec010 trb-start 0001c3eebfe0 trb-end 0001c3eebfe0 seg-start 
0001c3eeb000 seg-end 0001c3eebff0
Jun 12 19:00:04 ag13.local kernel: xhci_hcd :09:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
Jun 12 19:00:04 ag13.local kernel: xhci_hcd :09:00.0: Looking for event-dma 
0001c3eec020 trb-start 0001c3eebfe0 trb-end 0001c3eebfe0 seg-start 
0001c3eeb000 seg-end 0001c3eebff0
Jun 12 19:00:04 ag13.local kernel: xhci_hcd :09:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
Jun 12 19:00:04 ag13.local kernel: xhci_hcd :09:00.0: Looking for event-dma 
0001c3eec030 trb-start 0001c3eebfe0 trb-end 0001c3eebfe0 seg-start 
0001c3eeb000 seg-end 0001c3eebff0
Jun 12 19:00:04 ag13.local kernel: xhci_hcd :09:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
Jun 12 19:00:04 ag13.local kernel: xhci_hcd :09:00.0: Looking for event-dma 
0001c3eec040 trb-start 0001c3eebfe0 trb-end 0001c3eebfe0 seg-start 
0001c3eeb000 seg-end 0001c3eebff0
Jun 12 19:00:04 ag13.local kernel: xhci_hcd :09:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
Jun 12 19:00:04 ag13.local kernel: xhci_hcd :09:00.0: Looking for event-dma 
0001c3eec050 trb-start 0001c3eebfe0 trb-end 0001c3eebfe0 seg-start 
0001c3eeb000 seg-end 0001c3eebff0
Jun 12 19:00:04 ag13.local kernel: xhci_hcd :09:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
Jun 12 19:00:04 ag13.local kernel: xhci_hcd :09:00.0: Looking for event-dma 
0001c3eec060 trb-start 0001c3eebfe0 trb-end 0001c3eebfe0 seg-start 
0001c3eeb000 seg-end 0001c3eebff0
Jun 12 19:00:04 ag13.local kernel: xhci_hcd :09:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
Jun 12 19:00:04 ag13.local kernel: xhci_hcd :09:00.0: Looking for event-dma 
0001c3eec070 trb-start 0001c3eebfe0 trb-end 0001c3eebfe0 seg-start 
0001c3eeb000 seg-end 0001c3eebff0
Jun 12 19:00:04 ag13.local kernel: xhci_hcd :09:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
Jun 12 19:00:04 ag13.local kernel: xhci_hcd :09:00.0: Looking for event-dma 
0001c3eec080 trb-start 0001c3eebfe0 trb-end 0001c3eebfe0 seg-start 
0001c3eeb000 seg-end 0001c3eebff0

earlier in the log (and maybe related):
Jun 12 18:39:08 ag13.local kernel: WARNING: CPU: 0 PID: 0 at 
net/core/dev.c:5411 net_rx_action+0x2d0/0x3c0
Jun 12 18:39:08 ag13.local kernel: Modules linked in: cdc_ether usbnet r8152 
mii snd_usb_audio snd_usbmidi_lib snd_rawmidi rfcomm fuse ccm xt_CHECKSUM 
ipt_MASQUERADE nf_nat_masquerade_ipv4 tun nf_conntrack_netbios_ns 
nf_conntrack_broadcast xt_CT ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 
xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc 
ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle 
ip6table_raw ip6table_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_co

[Kernel-packages] [Bug 1727662] Re: [Lenovo ThinkPad T450s] Issues after docking and locking: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => Incomplete

** Changed in: linux
   Importance: Unknown => 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/1727662

Title:
  [Lenovo ThinkPad T450s] Issues after docking and locking:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

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

Bug description:
  What happens is after I dock my laptop into a Lenovo ThinkPad Ultra Dock Type 
40A2 20V, lock it via clicking the lock icon, and wait ~30 minutes, one of the 
following three things happen ~50% of the time when I come back to unlock it:
  * Most of the time the computer is found shut down.
  * Sometimes the notebook screen flickers weirdly and one of the two external 
monitors show pixelation.
  * The notebook screen shows the lock screen but is completely frozen. 
Occasionally unlocking works.

  I have two external monitors attached to the docking station.

  When I dock my laptop, the battery indicator does recognize its
  charging.

  I've not seen this issue when:
  1) With the laptop in the dock, while actively using the laptop.
  2) With the laptop out of the dock and no external monitors present.

  This bug started after upgrading from Ubtuntu 17.04 to Ubuntu 17.10.

  Using or not using the following kernel parameter didn't change anything:
  i915.enable_rc6=0

  PC temperatures are normal as per lm-sensors.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-lowlatency 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  akops  3337 F pulseaudio
   /dev/snd/controlC0:  akops  3337 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:44:11 2017
  HibernationDevice: RESUME=/dev/mapper/system-swap_1
  MachineType: LENOVO 20BWS2YL00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency 
root=/dev/mapper/system-root ro quiet splash i915.enable_rc6=0 
crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-lowlatency N/A
   linux-backports-modules-4.13.0-16-lowlatency  N/A
   linux-firmware1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago)
  dmi.bios.date: 07/08/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET51WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS2YL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BWS2YL00:pvrThinkPadT450s:rvnLENOVO:rn20BWS2YL00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS2YL00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1730680] Re: Shutdown failure in 17.10 with Nvidia Nouveau Driver

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => 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/1730680

Title:
  Shutdown failure in 17.10 with Nvidia Nouveau Driver

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The following errors display at shutdown. The system never shuts down
  and I must hold down the power key to turn the system off. The
  hardware is a Dell 7559 laptop with Intel / Nvidia Prime Graphics GTX
  960M. The display driver in use is the Nouveau driver.

  wlp5s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardare (-22)
  watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561]
  watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561]
  INFO: rcu_sched self-detected stall on CPU
  $3...: (14999 ticks this GP) idle=e6e/14001/0 softirq:55865/55865 
fqs:7490
  $ (t=15000 jiffies g=41392 c=41391 q=3432)
  watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561]
  watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561]
  INFO: task systemd-timesyn:305 blocked for more than 120 seconds.
  Tained: G DEL 4.13-0-16-generic $19-ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message
  INFO: task systemd-timesyn:305 blocked for more than 120 seconds.
  Tained: G DEL 4.13-0-16-generic $19-ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message
  watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561]
  watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561]
  watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561]
  watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561]

  At this point I had to hold down the power key to turn off the system.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  donp   1203 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-11-07 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171009)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 7559
  Package: linux (not installed)
  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=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=aa8f7506-7293-4695-a16a-9ecaf014f632 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  wayland-session artful
  Uname: Linux 4.13.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: 06/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.4
  dmi.board.name: 0H87XC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.4:bd06/08/2017:svnDellInc.:pnInspiron7559:pvr1.2.4:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.2.4
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1709708] Re: [Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but produces no sound on an HDMI TV until power cycled.

[Bug Watch Updater]

** Changed in: dri
   Status: Unknown => Fix Released

** Changed in: dri
   Importance: Unknown => 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/1709708

Title:
  [Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but
  produces no sound on an HDMI TV until power cycled.

Status in DRI:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Upon bootup, the HDMI output connected to a Samsung TV shows up as an
  output. If this output is selected and a sound test run (either using
  the GUI or using aplay /user/share/sounds/alsa/Front_Center.wav) no
  sound is heard. Pavumeter does however show sound coming through.

  I found that sound can be fixed by allowing the display to sleep,
  waking it up, and then restarting pulseaudio (pulseaudio -k). After
  that sound output through HDMI to the TV will work until rebooted.

  The fix can be succesfully scripted as follows:

  xset dpms force off
  sleep 1
  pulseaudio -k

  The machine is an Intel NUC6CAYH, connected to a not particularly new
  Samsung 42" TV using an HDMI cable, running a fresh install of Ubuntu
  16.04.

  In earlier attempts at fixing the issue I set pulseaudio to never let
  the sound device sleep (commented out load-module module-suspend-on-
  idle in /etc/pulse/default.pa), and also set the default sampling rate
  to 48000 (default-sample-rate = 48000 in /etc/pulse/daemon.conf). Not
  sure if these settings contributed to the fix, but they are not
  sufficient on their own.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Aug  9 21:48:39 2017
  InstallationDate: Installed on 2017-08-06 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Title: [, Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio fails to detect 
card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
  dmi.board.name: NUC6CAYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J23203-402
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0029.2016.1124.1625:bd11/24/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-402:cvn:ct3:cvr:
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-08-06T22:55:35.510382
  mtime.conffile..etc.pulse.default.pa: 2017-08-06T22:51:49.639085

To manage notifications about this bug go to:
https://bugs.launchpad.net/dri/+bug/1709708/+subscriptions

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

[Kernel-packages] [Bug 1729051] Re: dkms mkdeb fails: Can't find package

[Bug Watch Updater]

** Changed in: dkms (Debian)
   Status: Unknown => New

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

Title:
  dkms mkdeb fails: Can't find package

Status in dkms package in Ubuntu:
  Confirmed
Status in dkms package in Debian:
  New

Bug description:
  For some reason, the Debian version of dkms mkdeb tries to generate a
  .deb package with the current arch as a suffix in its name, instead of
  'all'. However, since the control file wasn't properly set up, the
  .deb file will have the 'all' suffix and dkms mkdeb will fail.

  This bug is also present in Ubuntu. I added a patch to the original
  Debian bug report, here:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832558

  but since the original bug report was made about a year ago and nobody
  cared, I'm hoping that someone will at least fix this for Ubuntu.

  The patch looks like this:

  --- a/etc/dkms/template-dkms-mkdeb/debian/control 2017-10-31 
14:40:41.690069116 -0300
  +++ b/etc/dkms/template-dkms-mkdeb/debian/control 2017-10-31 
14:41:12.137973994 -0300
  @@ -6,6 +6,6 @@
   Standards-Version: 3.8.1

   Package: DEBIAN_PACKAGE-dkms
  -Architecture: all
  +Architecture: DEBIAN_BUILD_ARCH
   Depends: dkms (>= 1.95), ${misc:Depends}
   Description: DEBIAN_PACKAGE driver in DKMS format.

  I'm using Ubuntu 17.10. dkms version is 2.3-3ubuntu3.

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

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

[Kernel-packages] [Bug 1140716] Re: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge

[Bug Watch Updater]

** Changed in: dri
   Status: Fix Released => Confirmed

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

Title:
  [regression] 3.5.0-26-generic and  3.2.0-39-generic GPU hangs on
  Sandybridge

Status in DRI:
  Confirmed
Status in Mesa:
  Unknown
Status in linux package in Ubuntu:
  Invalid
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in linux source package in Precise:
  Fix Committed
Status in linux-lts-quantal source package in Precise:
  Fix Committed
Status in linux-lts-raring source package in Precise:
  Invalid
Status in mesa source package in Precise:
  Triaged
Status in linux source package in Quantal:
  Invalid
Status in linux-lts-quantal source package in Quantal:
  Invalid
Status in linux source package in Raring:
  Invalid
Status in linux-lts-quantal source package in Raring:
  Invalid
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Won't Fix

Bug description:
  I'm getting errors about GPU hangs every minute or so (usually only
  when using FF and scrolling a webpage or something). I also get an
  annoying ubuntu dialog saying there is a "system error".

  This didn't happen with 3.5.0-24-generic.

  Here is the dmesg:
  [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26285.658405] [ cut here ]
  [26285.658472] WARNING: at 
/build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 
gen6_enable_rps+0x706/0x710 [i915]()
  [26285.658474] Hardware name: SATELLITE Z830
  [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate 
libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 
snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm 
arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel 
snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep 
iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi 
rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer 
snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap 
soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei 
video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc 
lp parport e1000e ahci libahci [last unloaded: sdhci]
  [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic 
#40-Ubuntu
  [26285.658539] Call Trace:
  [26285.658549]  [] warn_slowpath_common+0x7f/0xc0
  [26285.658553]  [] warn_slowpath_null+0x1a/0x20
  [26285.658569]  [] gen6_enable_rps+0x706/0x710 [i915]
  [26285.658584]  [] intel_modeset_init_hw+0x66/0xa0 [i915]
  [26285.658595]  [] i915_reset+0x1a4/0x6e0 [i915]
  [26285.658601]  [] ? __switch_to+0x12b/0x420
  [26285.658612]  [] i915_error_work_func+0xc3/0x110 [i915]
  [26285.658618]  [] process_one_work+0x12a/0x420
  [26285.658629]  [] ? gen6_pm_rps_work+0xe0/0xe0 [i915]
  [26285.658632]  [] worker_thread+0x12e/0x2f0
  [26285.658636]  [] ? manage_workers.isra.26+0x200/0x200
  [26285.658640]  [] kthread+0x93/0xa0
  [26285.658644]  [] kernel_thread_helper+0x4/0x10
  [26285.658649]  [] ? kthread_freezable_should_stop+0x70/0x70
  [26285.658652]  [] ? gs_change+0x13/0x13
  [26285.658654] ---[ end trace 59c6162fdfcbffee ]---
  [26756.021167] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26756.021426] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26766.014093] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26766.014397] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26932.376233] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26932.376544] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26932.384285] [ cut here ]
  [26932.384354] WARNING: at 
/build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 
gen6_enable_rps+0x706/0x710 [i915]()
  [26932.384356] Hardware name: SATELLITE Z830
  [26932.384358] Modules linked in: sdhci_pci sdh

[Kernel-packages] [Bug 1041790] Re: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0

[Bug Watch Updater]

** Changed in: xserver-xorg-video-intel
   Status: Fix Released => 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/1041790

Title:
  [snb] GPU lockup  IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround
  i915.semaphores=0

Status in xf86-video-intel:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  Triaged

Bug description:
  X locks up periodically for a 2 to ten seconds at a time and this
  crash log gets generated. It's significantly more than several times a
  day but not quite continuous. If you indeed have this bug, that should
  stop the lockups from happening. Irrespective, please file a new bug
  report so your hardware may be tracked.

  WORKAROUND: Edit your /etc/default/grub from:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

  to:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.semaphores=0"

  run the following and reboot:
  sudo update-grub

  The side effects of this is rendering throughput is dropped by 10%
  with SNA, or as much as 3x with UXA. OpenGL performance is likely to
  be reduced by about 30%. More CPU time is spent waiting for the GPU
  with rc6 disabled, so increased power consumption.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: xserver-xorg-video-intel 2:2.20.3-0ubuntu1
  Uname: Linux 3.6.0-rc3-git-20120826.1015 x86_64
  ApportVersion: 2.5.1-0ubuntu2
  Architecture: amd64
  Chipset: sandybridge-m-gt2
  Date: Sun Aug 26 16:06:32 2012
  DistroCodename: quantal
  DistroVariant: ubuntu
  DuplicateSignature: [sandybridge-m-gt2] GPU lockup  IPEHR: 0x0b160001 IPEHR: 
0x0b140001 Ubuntu 12.10
  EcryptfsInUse: Yes
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  GpuHangFrequency: Continuously
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
  InterpreterPath: /usr/bin/python3.2mu
  MachineType: Dell Inc. Dell System XPS L502X
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.0-rc3-git-20120826.1015 
root=UUID=135c8090-427c-460a-909d-eff262cd44b6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu3
   libdrm2  2.4.38-0ubuntu2
   xserver-xorg-video-intel 2:2.20.3-0ubuntu1
  SourcePackage: xserver-xorg-video-intel
  Title: [sandybridge-m-gt2] GPU lockup  IPEHR: 0x0b160001 IPEHR: 0x0b140001
  UdevDb: Error: [Errno 2] No such file or directory: 'udevadm'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 05/29/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1041790/+subscriptions

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

[Kernel-packages] [Bug 1034281] Re: CVE-2012-3412

[Bug Watch Updater]

Launchpad has imported 10 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-3412.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2012-07-31T13:27:49+00:00 Petr wrote:

A peer (or local user) may cause TCP to use a nominal MSS of as little
as 88 (actual MSS of 76 with timestamps).  Given that we have a
sufficiently prodigious local sender and the peer ACKs quickly enough,
it is nevertheless possible to grow the window for such a connection
to the point that we will try to send just under 64K at once.  This
results in a single skb that expands to 861 segments.

In some drivers with TSO support, such an skb will require hundreds of
DMA descriptors; a substantial fraction of a TX ring or even more than
a full ring.  The TX queue selected for the skb may stall and trigger
the TX watchdog repeatedly (since the problem skb will be retried
after the TX reset).

Upstream patch:
http://www.spinics.net/lists/netdev/msg206332.html

References:
http://seclists.org/oss-sec/2012/q3/171

Acknowledgements:

Red Hat would like to thank Ben Hutchings of Solarflare (tm) for
reporting this issue.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1034281/comments/0


On 2012-08-03T12:35:31+00:00 Petr wrote:

Created kernel tracking bugs for this issue

Affects: fedora-all [bug 845558]

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1034281/comments/1


On 2012-08-03T16:46:54+00:00 Petr wrote:

Mitigation as recommended by Ben Hutchings
--

If all processes that may send on the sfc interface use Onload, or do
not use TCP, the vulnerability does not exist.

The vulnerability can otherwise be avoided by making a temporary
configuration change.  For an sfc interface named eth0, either:

a. Increase the TX queue size:
   ethtool -G eth0 tx 4096
   This can increase TX latency and memory usage.

or:

b. Disable TSO:
   ethtool -K eth0 tso off
   This can reduce TX throughput and/or increase CPU usage.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1034281/comments/2


On 2012-10-02T17:11:36+00:00 errata-xmlrpc wrote:

This issue has been addressed in following products:

  RHEV-H, V2V and Agents for RHEL-5

Via RHSA-2012:1324 https://rhn.redhat.com/errata/RHSA-2012-1324.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1034281/comments/4


On 2012-10-02T17:45:30+00:00 errata-xmlrpc wrote:

This issue has been addressed in following products:

  Red Hat Enterprise Linux 5

Via RHSA-2012:1323 https://rhn.redhat.com/errata/RHSA-2012-1323.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1034281/comments/5


On 2012-10-09T10:28:53+00:00 errata-xmlrpc wrote:

This issue has been addressed in following products:

  Red Hat Enterprise Linux 5.6 EUS - Server Only

Via RHSA-2012:1347 https://rhn.redhat.com/errata/RHSA-2012-1347.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1034281/comments/6


On 2012-10-16T14:46:08+00:00 errata-xmlrpc wrote:

This issue has been addressed in following products:

  Red Hat Enterprise Linux 6

Via RHSA-2012:1366 https://rhn.redhat.com/errata/RHSA-2012-1366.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1034281/comments/7


On 2012-10-18T16:46:58+00:00 errata-xmlrpc wrote:

This issue has been addressed in following products:

  RHEV-H and Agents for RHEL-6

Via RHSA-2012:1375 https://rhn.redhat.com/errata/RHSA-2012-1375.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1034281/comments/8


On 2012-10-23T18:11:32+00:00 errata-xmlrpc wrote:

This issue has been addressed in following products:

  Red Hat Enterprise Linux 6.2 EUS - Server Only

Via RHSA-2012:1401 https://rhn.redhat.com/errata/RHSA-2012-1401.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1034281/comments/9


On 2012-11-06T18:06:34+00:00 errata-xmlrpc wrote:

This issue has been addressed in following products:

  Red Hat Enterprise Linux 6.1 EUS - Server Only

Via RHSA-2012:1430 https://rhn.redhat.com/errata/RHSA-2

[Kernel-packages] [Bug 1219256] Re: usbnet changes in 3.10 stop use of sierra_net devices

[Bug Watch Updater]

Launchpad has imported 26 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=998342.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-08-19T05:19:25+00:00 John wrote:

Description of problem:

My Sierra Wireless modems (312U & 320U) not working.

Version-Release number of selected component (if applicable):

v3.10 kernel versions


How reproducible:

Always

Steps to Reproduce:
1.
2.
3.

Actual results:

ifconfig shows wwan0 not running;

"wwan0: flags=4227  mtu 1500"


Expected results:

"wwan0: flags=4291  mtu 1500"


Additional info:

I've found the fix is to "make" and "make install" the v3.9 kernel
driver files "sierra.c" and "sierra_net.c" from http://lxr.free-
electrons.com/source/

In fact, it's only "sierra_net.c" that seems to be implicated.  For more
detailed info, please see: http://forums.whirlpool.net.au/forum-
replies.cfm?t=2135188&p=14#r275

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1219256/comments/0


On 2013-09-16T03:44:02+00:00 Rob wrote:

Hi,

Just updated this to reflect that F19 is also affected.

Is this an upstream issue? I see there's also a user on Arch with
similar difficulties. https://bbs.archlinux.org/viewtopic.php?id=168656

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1219256/comments/17


On 2013-09-16T08:15:31+00:00 Bjørn wrote:

Yes, this is definitely an upstream issue. It is a regression related to the
commit 7b0c5f21f ("sierra_net: keep status interrupt URB active") from Dan, so 
I was hoping he would look into it...

John has tested a number of different suggestions in addition to
reverting that commit (which will cause another regression for devices
needing it), but the exact trigger is still not known.  It seems like
the firmware of these devices somehow either need the repeated SYNC
messages, or need some delayed SYNC message. But I have not been able to
find out how to satisfy the firmware without completely disabling the
changes from commit 7b0c5f21f.

The only DirectIP device I've got does "unfortunately" work without
problems both with and without this fix, so I am unable to test either
of the firmware bugs.

The full results of all John's testing is posted in the whirlpool thread.  I 
believe this post in particualar shows where the problem is:
http://forums.whirlpool.net.au/forum-replies.cfm?t=2135188&p=15#r300

But it would be good if Dan or anyone else with a device/firmware
needing commit 7b0c5f21f could get involved in the testing. As it is
now, it looks like it is best to revert this commit.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1219256/comments/18


On 2013-10-12T21:23:01+00:00 Rob wrote:

Confirming this is still the case in Fedora 20.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1219256/comments/19


On 2013-10-19T09:12:37+00:00 John wrote:

I've just received kernel 3.11.4 (3.11.4-101.fc18.i686) as an upgrade,
and the problem persists.

I find that the kernel 3.9 drivers I've been using as a work-around will
no longer compile with kernel 3.11.

So the problem is now getting serious.  I can no longer use my Sierra
312U or 320U modems.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1219256/comments/20


On 2013-10-20T01:14:18+00:00 John wrote:

I've discovered the kernel 3.9 drivers will compile and work in kernel
3.11 if the following line in sierra.c

  ifnum = port->number - serial->minor;

is replaced with:

  ifnum = port->port_number;

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1219256/comments/21


On 2013-11-01T00:41:45+00:00 Rob wrote:

Thanks John.

That's bought us some time..

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1219256/comments/23


On 2013-11-01T08:38:45+00:00 Bjørn wrote:

I thought it was concluded that the serial driver had nothing to do with
this problem?  Quoting from the initial comment above:


   `In fact, it's only "sierra_net.c" that seems to be implicated. For more
detailed info, please see: 
http://forums.whirlpool.net.au/forum-replies.cfm?t=2135188&p=14#r275`

So you shouldn't have to do anything in particular to build on v3.11.
Just leave the v3.11 version of sierra.c as it is.  It's fine.


As I couldn't

[Kernel-packages] [Bug 1242310] Re: Bluetooth disabled after resume

[Bug Watch Updater]

Launchpad has imported 47 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=988481.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-07-25T16:41:10+00:00 Jacek wrote:

Description of problem:
suspend to ram and resume cycle breaks bluetooth 

Version-Release number of selected component (if applicable):
kernel 3.10.2-301.fc19.x86_64

How reproducible:
always

Steps to Reproduce:
1. start laptop, use bluetooth mouse
2. suspend laptop to ram (using lid or suspend key combination)
3. wait >20 s
4. resume laptop

Actual results:
bluetooth is not present 

Expected results:
bluetooth works mouse connects and works

Additional info:
to force bluetooth to work one has to run
sudo modprobe -r btusb
sudo modprobe btusb

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242310/comments/0


On 2013-07-26T05:44:10+00:00 Jacek wrote:

*** Bug 980938 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242310/comments/1


On 2013-09-01T20:58:31+00:00 Jacek wrote:

kernel 3.11.0-0.rc7.git4.1.fc19.x86_64 the same problem

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242310/comments/2


On 2013-09-05T06:30:46+00:00 Jacek wrote:

kernel 3.11.0-3.fc20.x86_64

the same problem

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242310/comments/3


On 2013-09-07T20:30:07+00:00 Michele wrote:

Hi Jacek,

if you reproduce it on 3.11.X then the following is already included:
commit 502f769662978a2fe99d0caed5e53e3006107381
Author: Shuah Khan 
Date:   Tue May 21 09:32:06 2013 -0600

Bluetooth: Add missing reset_resume dev_pm_ops

so it must be something else. Do you get any messages related to btusb
in /var/log/messages?

cheers,
Michele

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242310/comments/4


On 2013-09-08T10:58:04+00:00 Jacek wrote:

Michele,

No nothing specific, here is what I get when I resume machine:

Sep  8 12:45:39 jacek kernel: [30486.586778] ACPI: Low-level resume complete
Sep  8 12:45:39 jacek kernel: [30486.586778] PM: Restoring platform NVS memory
Sep  8 12:45:39 jacek kernel: [30486.587038] Enabling non-boot CPUs ...
Sep  8 12:45:39 jacek kernel: [30486.587081] smpboot: Booting Node 0 Processor 
1 APIC 0x1
Sep  8 12:45:39 jacek kernel: [30486.598618] CPU1 is up
Sep  8 12:45:39 jacek kernel: [30486.601790] ACPI: Waking up from system sleep 
state S3
Sep  8 12:45:39 jacek kernel: [30486.673111] ehci-pci :00:1a.7: System 
wakeup disabled by ACPI
Sep  8 12:45:39 jacek kernel: [30486.673159] snd_hda_intel :00:1b.0: power 
state changed by ACPI to D0
Sep  8 12:45:39 jacek kernel: [30486.684790] uhci_hcd :00:1d.0: System 
wakeup disabled by ACPI
Sep  8 12:45:39 jacek kernel: [30486.684927] uhci_hcd :00:1d.2: System 
wakeup disabled by ACPI
Sep  8 12:45:39 jacek kernel: [30486.695096] ehci-pci :00:1d.7: System 
wakeup disabled by ACPI
Sep  8 12:45:39 jacek kernel: [30486.728552] PM: noirq resume of devices 
complete after 77.413 msecs
Sep  8 12:45:39 jacek kernel: [30486.728855] PM: early resume of devices 
complete after 0.250 msecs
Sep  8 12:45:39 jacek kernel: [30486.729272] usb usb3: root hub lost power or 
was reset
Sep  8 12:45:39 jacek kernel: [30486.729480] usb usb4: root hub lost power or 
was reset
Sep  8 12:45:39 jacek kernel: [30486.729684] usb usb5: root hub lost power or 
was reset
Sep  8 12:45:39 jacek kernel: [30486.730563] usb usb6: root hub lost power or 
was reset
Sep  8 12:45:39 jacek kernel: [30486.730768] usb usb7: root hub lost power or 
was reset
Sep  8 12:45:39 jacek kernel: [30486.730973] usb usb8: root hub lost power or 
was reset
Sep  8 12:45:39 jacek kernel: [30487.109303] ata2: SATA link up 1.5 Gbps 
(SStatus 113 SControl 300)
Sep  8 12:45:39 jacek kernel: [30487.111057] ata5: SATA link down (SStatus 0 
SControl 300)
Sep  8 12:45:39 jacek kernel: [30487.116335] ata2.00: configured for UDMA/33
Sep  8 12:45:39 jacek kernel: [30487.118079] usb 2-3: reset high-speed USB 
device number 2 using ehci-pci
Sep  8 12:45:39 jacek kernel: [30487.353353] usb 7-2: reset full-speed USB 
device number 2 using uhci_hcd
Sep  8 12:45:39 jacek kernel: [30488.638337] ata1: SATA link up 3.0 Gbps 
(SStatus 123 SControl 300)
Sep  8 12:45:39 jacek kernel: [30488.937953] ata1.00: configured for UDMA/133
Sep  8 12:45:39 jacek kernel: [30

[Kernel-packages] [Bug 1201092] Re: Cannot load kvm_amd module - (says disabled by bios)

[Bug Watch Updater]

Launchpad has imported 7 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=978608.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-06-26T22:57:22+00:00 George wrote:

Description of problem:
Despite exposed flags and SVM enabled in the BIOS - module won't load. Works 
flawlessly in Virtualbox.

vendor_id   : AuthenticAMD
cpu family  : 20
model   : 2
model name  : AMD E-350D APU with Radeon(tm) HD Graphics
stepping: 0
microcode   : 0x500010d

Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
pse36 clflush mmx fxsr sse sse2 ht syscall mmxext fxsr_opt pdpe1gb
rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf
pni monitor ssse3 cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy
abm sse4a misalignsse 3dnowprefetch ibs skinit wdt arat hw_pstate npt
lbrv svm_lock nrip_save pausefilter

Hardware: AMD APU E350, M/B Gigabyte E350N Win8, F3 BIOS

Version-Release number of selected component (if applicable):
Kernels 3.6.10-4.fc18.x86_64 (release), 3.9.6-200.fc18.x86_64 (latest)

How reproducible:
For my HW - always

Steps to Reproduce:
1. Enable SVM in BIOS
2. Install Fedora 18
3. modprobe kvm_amd

Actual results:
[root@localhost ~]# modprobe kvm_amd
modprobe: ERROR: could not insert 'kvm_amd': Operation not supported
[root@localhost ~]# dmesg|tail -n1
[ 1611.001914] kvm: disabled by bios

Additional info:
AMD-V available in Virtualbox

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1201092/comments/0


On 2013-07-14T11:10:25+00:00 Massimiliano wrote:

I confirm that this issue arises even with kernels 3.8.0-27 and 3.10 (tryied on 
Ubuntu): dmesg shows the message "kvm: disabled by bios"
I don't know if Red Hat has the 'kvm-ok' executable, BTW in Ubuntu it says that 
the machine is capable of running KVM, but KVM is disable. This is the output:

# kvm-ok 
INFO: /dev/kvm does not exist
HINT:   sudo modprobe kvm_amd
INFO: Your CPU supports KVM extensions
INFO: KVM (svm) is disabled by your BIOS
HINT: Enter your BIOS setup and enable Virtualization Technology (VT),
  and then hard poweroff/poweron your system
KVM acceleration can NOT be used

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1201092/comments/1


On 2013-07-15T10:19:47+00:00 Kashyap wrote:

On Fedora based systems, you can run

$ virt-host-validate 
  QEMU: Checking for hardware virtualization : 
PASS
  QEMU: Checking for device /dev/kvm : 
PASS
  QEMU: Checking for device /dev/vhost-net   : 
PASS
  QEMU: Checking for device /dev/net/tun : 
PASS
   LXC: Checking for Linux >= 2.6.26 : 
PASS


(NOTE: 'libvirt-client' package provide the above tool.)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1201092/comments/19


On 2013-07-24T13:54:48+00:00 George wrote:

FYI: we've got pretty heavy email traffic regarding this issue, will
update as soon as will confirm the problem.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1201092/comments/27


On 2013-10-18T21:13:46+00:00 Justin wrote:

*** MASS BUG UPDATE **

We apologize for the inconvenience.  There is a large number of bugs to
go through and several of them have gone stale.  Due to this, we are
doing a mass bug update across all of the Fedora 18 kernel bugs.

Fedora 18 has now been rebased to 3.11.4-101.fc18.  Please test this
kernel update (or newer) and let us know if you issue has been resolved
or if it is still present with the newer kernel.

If you have moved on to Fedora 19, and are still experiencing this
issue, please change the version to Fedora 19.

If you experience different issues, please open a new bug report for
those.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1201092/comments/38


On 2013-11-27T16:03:27+00:00 Justin wrote:

*** MASS BUG UPDATE **

We apologize for the inconvenience.  There is a large number of bugs to
go through and several of them have gone stale.

It has been over a month since we asked you to test the 3.11 kernel
updates and let us know if your issue has been resolved or is still a
problem. When this happened, the bug was set to needinfo.  Because the
needinfo i

[Kernel-packages] [Bug 1176577] Re: [HP Compaq dc7700 Small Form Factor PC] mei unexpected reset in kernel 3.8

[Bug Watch Updater]

** Changed in: linux (Fedora)
   Status: Unknown => Fix Released

** Changed in: linux (Fedora)
   Importance: Unknown => 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/1176577

Title:
  [HP Compaq dc7700 Small Form Factor PC] mei unexpected reset in kernel
  3.8

Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Arch Linux:
  New
Status in linux package in Fedora:
  Fix Released

Bug description:
  Right after upgrading kernel from 3.5 to 3.8 (Ubuntu 13.04), the
  syslog got flooded by a large number of such messages:

  (cut)
  May  5 15:33:15 compaq-aldo kernel: [  205.064042] mei :00:03.0: 
unexpected reset: dev_state = RESETING
  May  5 15:33:21 compaq-aldo kernel: [  211.076029] mei :00:03.0: 
unexpected reset: dev_state = RESETING
  May  5 15:33:27 compaq-aldo kernel: [  217.088035] mei :00:03.0: 
unexpected reset: dev_state = RESETING
  May  5 15:33:33 compaq-aldo kernel: [  223.100039] mei :00:03.0: 
unexpected reset: dev_state = RESETING
  May  5 15:33:39 compaq-aldo kernel: [  229.112045] mei :00:03.0: 
unexpected reset: dev_state = RESETING
  (cut)

  This was associated by non reliable ethernet functionality, i.e.
  transfer of large files from my Ubuntu box to a local NAS connected
  via ethernet got hanging with no other apparent errors or diagnostics:
  nautilus copy just stopped transferring data, leaving the copy window
  there with the progress bar stopped.

  I tried to reboot, but this behaviour is perfectly reproducible.

  This is one of the first syslog lines got from that kernel:

  May  5 15:30:15 compaq-aldo kernel: [0.00] Linux version
  3.8.0-19-generic (buildd@roseapple) (gcc version 4.7.3 (Ubuntu/Linaro
  4.7.3-1ubuntu1) ) #30-Ubuntu SMP Wed May 1 16:36:13 UTC 2013 (Ubuntu
  3.8.0-19.30-generic 3.8.8)

  I attach the whole syslog from boot of that kernel.

  On the same box, launching a previsous kernel (3.5) works flawlessly.
  For the time being, I removed 3.8 kernel from my box, now running 3.5.

  Kind regards
  Aldo
  --- 
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ldx2074 F pulseaudio
   /dev/snd/controlC0:  ldx2074 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  DistroRelease: Ubuntu 13.04
  HibernationDevice: RESUME=UUID=32cc5d6d-43c1-4e97-a8b7-10b71aac3e29
  InstallationDate: Installed on 2013-01-04 (121 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=38ce1d51-c3cf-438d-b395-f7c4744e2e37 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-19-generic N/A
   linux-backports-modules-3.8.0-19-generic  N/A
   linux-firmware1.106
  RfKill:
   
  Tags:  raring
  Uname: Linux 3.8.0-19-generic i686
  UpgradeStatus: Upgraded to raring on 2013-04-26 (9 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
  dmi.bios.date: 04/13/2007
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786E1 v01.10
  dmi.board.name: 0A54h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC7451V4Q
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786E1v01.10:bd04/13/2007:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.name: HP Compaq dc7700 Small Form Factor
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1094744] Re: MS Sculpt Touch Mouse needs to be re-paired periodically

[Bug Watch Updater]

Launchpad has imported 6 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=923349.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-03-19T16:05:11+00:00 nicu wrote:

When you don't use the mouse for a long enough time, the mouse
disconnects and won't reconnect. I have to go into bluetooth settings,
remove it, and re-pair it.

This is the same bug as here:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1094744

I have bluez-4.101-6.fc18.x86_64


How reproducible:
every time

Steps to Reproduce:
1. wait to enter standby
2. exit standby by pressing any key
3. try to move mouse, mouse is disconnected
  
Expected results:
mouse pointer should move


Additional info:

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1094744/comments/7


On 2013-03-19T16:32:19+00:00 nicu wrote:

dmesg output when first connecting:

[25476.140823] hid-generic 0005:045E:077C.000A: unknown main item tag 0x0
[25476.141156] input: Microsoft Sculpt Touch Mouse as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input26
[25476.141905] hid-generic 0005:045E:077C.000A: input,hidraw0: BLUETOOTH HID 
v1.1e Mouse [Microsoft Sculpt Touch Mouse] on 9c:b7:0d:ab:1c:ee

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1094744/comments/8


On 2013-03-20T19:34:57+00:00 nicu wrote:

I have observed that the pairing is also lost when a new device is
inserted, like a usb stick. Otherwise, the pairing lasts 20 minutes
max...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1094744/comments/9


On 2013-06-28T02:06:38+00:00 Dimitris wrote:

I see what I think is the same problem with:

bluez-4.101-8.fc19.x86_64.rpm
kernel 3.9.5-301.fc19.x86_64
Thinkpad Laser Mouse

- [Re-]discover mouse and pair:

Jun 27 18:48:45 gaspode bluetoothd[10091]: bluetoothd[10091]: Discovery session 
0x7f898f20a5c0 with :1.453 activated
Jun 27 18:48:45 gaspode bluetoothd[10091]: Discovery session 0x7f898f20a5c0 
with :1.453 activated
Jun 27 18:48:47 gaspode bluetoothd[10091]: bluetoothd[10091]: Unknown command 
complete for opcode 37
Jun 27 18:48:47 gaspode bluetoothd[10091]: Unknown command complete for opcode 
37
Jun 27 18:48:50 gaspode bluetoothd[10091]: bluetoothd[10091]: Unknown command 
complete for opcode 37
Jun 27 18:48:50 gaspode bluetoothd[10091]: Unknown command complete for opcode 
37
Jun 27 18:48:54 gaspode bluetoothd[10091]: bluetoothd[10091]: Stopping discovery
Jun 27 18:48:54 gaspode bluetoothd[10091]: Stopping discovery
Jun 27 18:48:56 gaspode kernel: hid-generic 0005:17EF:6038.0006: unknown main 
item tag 0x0
Jun 27 18:48:56 gaspode kernel: input: ThinkPad Bluetooth Laser Mouse as 
/devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0/bluetooth/hci0/hci0:11/input22
Jun 27 18:48:56 gaspode kernel: hid-generic 0005:17EF:6038.0006: input,hidraw3: 
BLUETOOTH HID v2.00 Mouse [ThinkPad Bluetooth Laser Mouse] on 00:27:13:96:48:a
Jun 27 18:48:56 gaspode /etc/gdm/Xsession[1422]: ** Message: has_config_widget 
F0:65:DD:67:A2:B9 HumanInterfaceDeviceService

- After using the mouse for a little, bit, turn it off (hardware
switch); then, a little while later:

Jun 27 18:49:35 gaspode kernel: power_supply hid-f0:65:dd:67:a2:b9-battery: 
driver failed to report `capacity' property: -5
Jun 27 18:49:40 gaspode kernel: power_supply hid-f0:65:dd:67:a2:b9-battery: 
driver failed to report `capacity' property: -5
Jun 27 18:51:22 gaspode bluetoothd[10091]: bluetoothd[10091]: Adapter 
/org/bluez/10091/hci0 has been disabled
Jun 27 18:51:22 gaspode bluetoothd[10091]: Adapter /org/bluez/10091/hci0 has 
been disabled
Jun 27 18:51:22 gaspode bluetoothd[10091]: bluetoothd[10091]: Unregister path: 
/org/bluez/10091/hci0
Jun 27 18:51:22 gaspode bluetoothd[10091]: Unregister path: 
/org/bluez/10091/hci0

- Turn mouse back on; Nothing happens (was expecting it to reconnect).  The 
machine is a Thinkpad X200s using a:
Bus 004 Device 009: ID 0a5c:217f Broadcom Corp. BCM2045B (BDC-2.1)
built-in adapter.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1094744/comments/24


On 2013-12-21T12:17:56+00:00 Fedora wrote:

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open wit

[Kernel-packages] [Bug 1171285] Re: intel centrino Wireless-N 1000 firmware is wrong under LTS 12.04

[Bug Watch Updater]

** Changed in: linux-firmware (Fedora)
   Status: Unknown => Expired

** Changed in: linux-firmware (Fedora)
   Importance: Unknown => Critical

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

Title:
  intel centrino Wireless-N 1000 firmware is wrong under LTS 12.04

Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux-firmware package in Fedora:
  Expired

Bug description:
  After a fresh installation, I can't drive my wireless card, Intel Centrino 
Wireless-N 1000.
  The problem is about the firmware used in LTS 12.04.

  First I'm very sure that both my hardware switch and soft switch are on.
  [code]
  nico@jacob-pc:~$ rfkill list all
  0: ideapad_wlan: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  1: ideapad_bluetooth: Bluetooth
  Soft blocked: no
  Hard blocked: no
  2: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
  5: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  nico@jacob-pc:~$
  [/code]

  Then when running 'iwconfig' command, I got this
  [code]
  nico@jacob-pc:~$ iwconfig
  eth0  no wireless extensions.
  lono wireless extensions.
  wlan0 IEEE 802.11bgn  ESSID:off/any  
Mode:Managed  Access Point: Not-Associated   Tx-Power=0 dBm   
Retry  long limit:7   RTS thr:off   Fragment thr:off
Power Management:off
  [/code]
  This means the system can probe my card, but can't drive it.

  Third, I used 'iwlist scan' command, 'ifup wlan0' command and 'dhclient 
wlan0' command, there are the outputs:
  [code]
  nico@jacob-pc:~$ iwlist scan
  eth0  Interface doesn't support scanning.
  loInterface doesn't support scanning.
  wlan0 Failed to read scan data : Network is down

  nico@jacob-pc:~$ sudo ifup wlan0
  [sudo] password for nico: 
  Ignoring unknown interface wlan0=wlan0.

  nico@jacob-pc:~$ sudo dhclient wlan0
  RTNETLINK answers: Input/output error
  ^C
  [/code]
  This means the system can't drive my card, there may be something wrong with 
the firmware.

  
  After a long time trying, I found a way to solve this problem at last.
  Download a older firmware from 
  
http://wireless.kernel.org/en/users/Drivers/iwlwifi?action=AttachFile&do=get&target=iwlwifi-1000-ucode-128.50.3.1.tgz
  This firmware is only for kernel 2.6.30+, the original one is for 3.2+. LTS 
12.04 use a latest one from that website, 
  that's the reason. So just delete or rename the original one which is named  
iwlwifi-1000-5.ucode,
  and put iwlwifi-1000-3.ucode from that tarball to /lib/firmware, and run 
'modprobe -r iwlwifi',
   'modprobe iwlwifi', everything will be wonderful.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-firmware 1.79.1
  ProcVersionSignature: Ubuntu 3.2.0-39.62-generic 3.2.39
  Uname: Linux 3.2.0-39-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.2
  Architecture: amd64
  Date: Mon Apr 22 10:24:08 2013
  Dependencies:
   
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1173997] Re: [HP 6730b] Fan at full speed after suspend

[Bug Watch Updater]

** Changed in: linux (Fedora)
   Status: Unknown => Fix Released

** Changed in: linux (Fedora)
   Importance: Unknown => Undecided

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

Title:
  [HP 6730b] Fan at full speed after suspend

Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Fedora:
  Fix Released

Bug description:
  After upgrading to 13.04 the fan of my HP 6730b runs at full speed
  when resuming after suspend. Before the suspend everything is ok.

  Workaround is to boot with the old kernel from 12.10 (3.5.0-27).

  I also tried mainline build 3.8.9-030809. Problem occurs there as well.
  --- 
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mnl2949 F pulseaudio
  CRDA:
   country DE:
(2400 - 2483 @ 40), (N/A, 20)
(5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR
(5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS
(5470 - 5725 @ 40), (N/A, 26), DFS
  DistroRelease: Ubuntu 13.04
  HibernationDevice: RESUME=UUID=86292e17-edd2-4a1b-8e1b-5208a1731140
  InstallationDate: Installed on 2010-11-10 (900 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  MachineType: Hewlett-Packard HP Compaq 6730b (GB990EA#ABD)
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=cff10fb4-08a2-459b-be12-80698b20d2d3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-19-generic N/A
   linux-backports-modules-3.8.0-19-generic  N/A
   linux-firmware1.106
  Tags:  raring
  Uname: Linux 3.8.0-19-generic i686
  UpgradeStatus: Upgraded to raring on 2013-04-28 (0 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare voice 
wireshark
  dmi.bios.date: 12/07/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PDD Ver. F.20
  dmi.board.name: 30DD
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 96.23
  dmi.chassis.asset.tag: CNU9326SJY
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PDDVer.F.20:bd12/07/2011:svnHewlett-Packard:pnHPCompaq6730b(GB990EA#ABD):pvrF.20:rvnHewlett-Packard:rn30DD:rvrKBCVersion96.23:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq 6730b (GB990EA#ABD)
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1098216] Re: Regression in brightness control on Lenovo Thinkpad X230 (+tablet) and X1 Carbon

[Bug Watch Updater]

** Changed in: linux (Fedora)
   Status: Unknown => Fix Released

** Changed in: linux (Fedora)
   Importance: Unknown => 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/1098216

Title:
  Regression in brightness control on Lenovo Thinkpad X230 (+tablet) and
  X1 Carbon

Status in Linux:
  In Progress
Status in linux package in Ubuntu:
  Triaged
Status in linux package in Fedora:
  Fix Released

Bug description:
  == Raring SRU Justification ==

  Impact: A number of ThinkPad models have a workaround in the ACPI
  backlight implementation for Windows 8 that more or less completely
  breaks backlight control.

  Fix: Add an OSI quirk to no longer claim to be Windows 8 on these
  machines, causing the firmware to revert to the older, working behavior.

  Test Case: Verified on LP #1098216 and bugzill.kernel.org #51231.

  ---

  Something changed between the 3.5 and the 3.7 kernel, leading to
  broken brightness control on my Thinkpad x230.

  Here are some test results:
  == 3.5.0-21-generic ==
  === Post-boot values ===
  /sys/class/backlight:
    - intel-backlight
  + actual_brightness => 4438
  + bl_power => 0
  + brightness => 4438
  + max_brightness => 4438
    - acpi_video0
  + actual_brightness => 15
  + bl_power => 0
  + brightness => 15
  + max_brightness => 15

  === Tests ===
  echo 0 > acpi_video0/brightness => works
  echo 0 > intel_backlight/brightness => works

  == 3.8.0-0-generic ==
  === Post-boot values ===
  /sys/class/backlight:
    - intel-backlight
  + actual_brightness => 4438
  + bl_power => 0
  + brightness => 4438
  + max_brightness => 4438
    - acpi_video0
  + actual_brightness => 100
  + bl_power => 0
  + brightness => 100
  + max_brightness => 100

  === Tests ===
  echo 0 > acpi_video0/brightness => doesn't do anything
  echo 0 > intel_backlight/brightness => works
  ---
  ApportVersion: 2.8-0ubuntu1
  Architecture: amd64
  CheckboxSubmission: 12108b8b8b67d760cdd84f1b9574e7f3
  CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
  DistroRelease: Ubuntu 13.04
  InstallationDate: Installed on 2012-09-02 (129 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120902)
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.8.0-0.1-generic 3.8.0-rc3
  Tags:  raring
  Uname: Linux 3.8.0-0-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  WORKAROUND:

  Add to /etc/default/grub
  in the variable "GRUB_CMDLINE_LINUX_DEFAULT":

  acpi_osi=\"!Windows 2012\"

  e.g:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi=\"!Windows 2012\""

  Then run "sudo update-grub".

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

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

[Kernel-packages] [Bug 1109298] Re: [Regression] error when trying to compile a program which uses alsa/asoundlib.h with EGLIBC 2.17

[Bug Watch Updater]

Launchpad has imported 12 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=885306.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2012-12-08T14:29:54+00:00 Richard wrote:

Description of problem:
While trying to build the latest mythtv on RPM Fusion for rawhide I ran into 
the following issue:

g++ -c -pipe -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -DPIC -O2 -g
-pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic -fomit-frame-pointer
-fomit-frame-pointer -fPIC -pthread -g -Wall -Wpointer-arith
-Wno-non-virtual-dtor -D__STDC_CONSTANT_MACROS -D__STDC_LIMIT_MACROS
-fvisibility-inlines-hidden -Wmissing-declarations -Wno-switch
-Wredundant-decls -funit-at-a-time -D_REENTRANT -fPIC -DMMX
-D_GNU_SOURCE -DQT_NO_DEBUG -DQT_CORE_LIB -DQT_SHARED
-I/usr/lib64/qt4/mkspecs/linux-g++ -I. -I/usr/include/QtCore
-I/usr/include -I/usr/include -I/usr -I/usr/include/libxml2
-I../../zeromq/include -I../../nzmqt/include/nzmqt -I../include -I.
-I. -o parser.o parser.cpp
In file included from /usr/include/alsa/asoundlib.h:49:0,
 from libavdevice/alsa-audio-common.c:31:
/usr/include/alsa/pcm.h:944:1: error: unknown type name 'u_int8_t'
/usr/include/alsa/pcm.h:945:1: error: unknown type name 'u_int16_t'
/usr/include/alsa/pcm.h:946:1: error: unknown type name 'u_int32_t'
/usr/include/alsa/pcm.h:947:1: error: unknown type name 'u_int64_t'
In file included from /usr/include/alsa/asoundlib.h:49:0,
 from libavdevice/alsa-audio-common.c:31:
/usr/include/alsa/pcm.h:1052:1: error: unknown type name 'int16_t'
make[2]: *** [libavdevice/alsa-audio-common.o] Error 1
make[2]: Leaving directory
`/builddir/build/BUILD/MythTV-mythtv-d2f9798/mythtv/external/FFmpeg'
make[1]: *** [FFmpeg-all] Error 2


Version-Release number of selected component (if applicable):
alsa-lib-devel-1.0.26-1.fc19.x86_64


A mythtv dev suggested the following *might* be the fix. Since I build mythtv 
in mock/rpmbuild I don't think it's possible/practical to test this patch:

--- /usr/include/alsa/asoundlib.h   2012-09-06 06:18:02.0 -0700
+++ asoundlib.h 2012-12-07 19:30:53.131751067 -0800
@@ -31,6 +31,7 @@
 #include 
 #include 
 #include 
+#include 
 #include 
 #include 
 #include 

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
lib/+bug/1109298/comments/0


On 2012-12-10T17:02:58+00:00 Richard wrote:

Created attachment 660967
Git diff from master

I have verified that the patch essentially works (I had to actually
patch asoundlib-head.h)

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
lib/+bug/1109298/comments/1


On 2012-12-10T17:04:16+00:00 Richard wrote:

Created attachment 660968
Patch to asoundlib.h

Attaching since I couldn't get it to show up in the git diff...

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
lib/+bug/1109298/comments/2


On 2012-12-10T18:44:22+00:00 Gary wrote:

(In reply to comment #0)
.
> A mythtv dev suggested the following *might* be the fix. 

I believe the (root) cause is that stdlib.h no longer
includes sys/types.h, and the alsa includes depend on
the u_int... types being defined (which were being
defined in sys/types.h, no longer included).

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
lib/+bug/1109298/comments/3


On 2012-12-20T21:55:10+00:00 Richard wrote:

As it's been 10 days since the last comment on this bug I just wanted to
ping you guys to see if anyone is working on a fix.

I would think that breaking a program from building would be considered
a serious, though not urgent, bug.

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
lib/+bug/1109298/comments/4


On 2013-03-23T04:29:02+00:00 Gary wrote:

It appears that this has been addressed upstream http://git.alsa-
project.org/?p=alsa-
lib.git;a=commit;h=3e7dc283ed2d3ed2341f0657811c588f4dbcba6d

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
lib/+bug/1109298/comments/15


On 2013-04-03T15:18:49+00:00 Fedora wrote:

This bug appears to have been reported against 'rawhide' during the Fedora 19 
development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 
19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 
End Of

[Kernel-packages] [Bug 1088271] Re: X startup fails with "failed to get resources" error after update to 3.5.0-18

[Bug Watch Updater]

Launchpad has imported 5 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=889687.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2012-12-22T15:26:59+00:00 Milan wrote:

Created attachment 667712
/var/log obtained in failsafe graphics mode with F18 beta LiveCD

LiveCD for both F18 beta and nightly build from 2012-12-17 fail to build
on my machine with an Ironlake Mobile GPU (see below). If I choose the
normal boot mode, Plymouth is not visible: the screen goes grey, then
blanks and never returns. If I choose failsafe graphics mode
(xdriver=vesa nomodeset), I am able to see the boot process, but X fails
to start: on F18 beta, I am able to go to a console; with the nightly
build, the machine hangs when X starts, and the fan does not stop
(probably CPU use).

I am attaching the logs I could get with F18 beta in failsafe graphics
mode.

Please ask for any information/debugging you may need.

The card model is:
00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor 
Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA 
controller])

The most interesting part of Xorg.0.log is:
[13.212] (II) VESA: driver for VESA chipsets: vesa
[13.212] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[13.212] (II) FBDEV: driver for framebuffer: fbdev
[13.212] (++) using VT number 1

[13.214] (II) intel(0): using device path '/dev/dri/card0'
[13.218] (WW) Falling back to old probe method for vesa
[13.218] (WW) Falling back to old probe method for modesetting
[13.218] (WW) Falling back to old probe method for fbdev
[13.218] (II) Loading sub module "fbdevhw"
[13.218] (II) LoadModule: "fbdevhw"
[13.218] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
[13.229] (II) Module fbdevhw: vendor="X.Org Foundation"
[13.229]compiled for 1.13.0, module version = 0.0.2
[13.229]ABI class: X.Org Video Driver, version 13.0
[13.229] (EE) open /dev/fb0: No such file or directory
[13.235] (II) intel(0): Creating default Display subsection in Screen 
section
"Default Screen Section" for depth/fbbpp 24/32
[13.235] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[13.235] (==) intel(0): RGB weight 888
[13.235] (==) intel(0): Default visual is TrueColor
[13.236] (--) intel(0): Integrated Graphics Chipset: Intel(R) Arrandale
[13.236] (**) intel(0): Relaxed fencing enabled
[13.236] (**) intel(0): Wait on SwapBuffers? enabled
[13.236] (**) intel(0): Triple buffering? enabled
[13.236] (**) intel(0): Framebuffer tiled
[13.236] (**) intel(0): Pixmaps tiled
[13.236] (**) intel(0): 3D buffers tiled
[13.236] (**) intel(0): SwapBuffers wait enabled
[13.236] (==) intel(0): video overlay key set to 0x101fe
[13.236] (EE) intel(0): failed to get resources: Invalid argument
[13.236] (II) UnloadModule: "intel"
[13.236] (EE) Screen(s) found, but none have a usable configuration.
[13.236] 
Fatal server error:
[13.236] no screens found

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1088271/comments/3


On 2012-12-22T15:31:23+00:00 Milan wrote:

FWIW, a report against Ubuntu 12.04 has the very same X log, and says it
was working with Linux kernel 3.5.0-17, but fails with 3.5.0-18. Of
course F18 has much more recent kernels.

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1088271

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1088271/comments/4


On 2012-12-22T16:08:28+00:00 Milan wrote:

OK, acpi_backlight=vendor fixes the problem in normal boot mode. This is
bug 771110 striking again.

Still, I think there's a separate problem with failsafe graphics mode.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1088271/comments/5


On 2013-12-21T10:02:59+00:00 Fedora wrote:

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is e

[Kernel-packages] [Bug 946899] Re: 8086:2a02 [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung

[Bug Watch Updater]

** Changed in: linux (Fedora)
   Status: Unknown => Won't Fix

** Changed in: linux (Fedora)
   Importance: Unknown => Undecided

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

Title:
  8086:2a02 [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer
  elapsed... GPU hung

Status in Linux:
  Incomplete
Status in Linux Mint:
  Confirmed
Status in xf86-video-intel:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in linux package in Fedora:
  Won't Fix

Bug description:
  Since upgrading to 12.04 beta, I've seen this happen twice. The
  symptoms are:

  - The screen freezes
  - The backlight turns off

  At that point I have to reboot to get my display back. In syslog, i
  see:

  
  Mar  4 23:09:18 perseus kernel: [ 3751.612064] [drm:i915_hangcheck_elapsed] 
*ERROR* Hangcheck timer elapsed... GPU hung
  Mar  4 23:09:18 perseus kernel: [ 3751.612076] [drm] capturing error event; 
look for more information in /debug/dri/0/i915_error_state
  Mar  4 23:09:18 perseus kernel: [ 3751.613658] [drm:i915_wait_request] 
*ERROR* i915_wait_request returns -11 (awaiting 114040 at 114004, next 114118)
  Mar  4 23:09:18 perseus kernel: [ 3751.637049] [drm:init_ring_common] *ERROR* 
render ring initialization failed ctl  head  tail  
start 

  followed by a lot of things like:

  
  Mar  4 23:09:18 perseus kernel: [ 3751.700662] WARNING: at 
/build/buildd/linux-3.2.0/drivers/gpu/drm/i915/intel_display.c:793 
intel_enable_pipe+0x14a/0x150 [i915]()
  Mar  4 23:09:18 perseus kernel: [ 3751.700667] Hardware name: 6465CTO
  Mar  4 23:09:18 perseus kernel: [ 3751.700670] PLL state assertion failure 
(expected on, current off)

  Mar  4 23:09:18 perseus kernel: [ 3751.812158] WARNING: at 
/build/buildd/linux-3.2.0/drivers/gpu/drm/i915/intel_display.c:930 
assert_pipe+0x75/0x80 [i915]()
  Mar  4 23:09:18 perseus kernel: [ 3751.812165] Hardware name: 6465CTO
  Mar  4 23:09:18 perseus kernel: [ 3751.812170] pipe B assertion failure 
(expected on, current off)

  then:

  
  Mar  4 23:09:19 perseus kernel: [ 3753.044086] [drm:intel_lvds_enable] 
*ERROR* timed out waiting for panel to power on
  Mar  4 23:09:20 perseus kernel: [ 3753.671451] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.684603] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.704594] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.724594] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.744595] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.764606] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.784607] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.804618] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.824606] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-17-generic 3.2.0-17.27
  ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
  Uname: Linux 3.2.0-17-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.94-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mdz2458 F pulseaudio
   /dev/snd/controlC1:  mdz2458 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfe02 irq 49'
 Mixer name : 'Analog Devices AD1984'
 Components : 'HDA:11d41984,17aa20bb,00100400'
 Controls  : 31
 Simple ctrls  : 19
  Card1.Amixer.info:
   Card hw:1 'Q9000'/'Logitech, Inc. QuickCam Pro 9000 at usb-:00:1a.7-3, 
high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:0990'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 3072
 Mono: Capture 0 [0%] [18.00dB] [off]
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
7KHT24WW-1.08'
 Mixer name : 'ThinkPad EC 7KHT24WW-1.08'
 Components : ''
 Controls  : 1
 Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
 Capab

[Kernel-packages] [Bug 1140716] Re: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge

[Bug Watch Updater]

** Changed in: linux (Fedora)
   Status: Unknown => Won't Fix

** Changed in: linux (Fedora)
   Importance: Unknown => Undecided

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

Title:
  [regression] 3.5.0-26-generic and  3.2.0-39-generic GPU hangs on
  Sandybridge

Status in DRI:
  Fix Released
Status in Mesa:
  Unknown
Status in linux package in Ubuntu:
  Invalid
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in linux source package in Precise:
  Fix Committed
Status in linux-lts-quantal source package in Precise:
  Fix Committed
Status in linux-lts-raring source package in Precise:
  Invalid
Status in mesa source package in Precise:
  Triaged
Status in linux source package in Quantal:
  Invalid
Status in linux-lts-quantal source package in Quantal:
  Invalid
Status in linux source package in Raring:
  Invalid
Status in linux-lts-quantal source package in Raring:
  Invalid
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Won't Fix

Bug description:
  I'm getting errors about GPU hangs every minute or so (usually only
  when using FF and scrolling a webpage or something). I also get an
  annoying ubuntu dialog saying there is a "system error".

  This didn't happen with 3.5.0-24-generic.

  Here is the dmesg:
  [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26285.658405] [ cut here ]
  [26285.658472] WARNING: at 
/build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 
gen6_enable_rps+0x706/0x710 [i915]()
  [26285.658474] Hardware name: SATELLITE Z830
  [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate 
libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 
snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm 
arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel 
snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep 
iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi 
rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer 
snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap 
soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei 
video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc 
lp parport e1000e ahci libahci [last unloaded: sdhci]
  [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic 
#40-Ubuntu
  [26285.658539] Call Trace:
  [26285.658549]  [] warn_slowpath_common+0x7f/0xc0
  [26285.658553]  [] warn_slowpath_null+0x1a/0x20
  [26285.658569]  [] gen6_enable_rps+0x706/0x710 [i915]
  [26285.658584]  [] intel_modeset_init_hw+0x66/0xa0 [i915]
  [26285.658595]  [] i915_reset+0x1a4/0x6e0 [i915]
  [26285.658601]  [] ? __switch_to+0x12b/0x420
  [26285.658612]  [] i915_error_work_func+0xc3/0x110 [i915]
  [26285.658618]  [] process_one_work+0x12a/0x420
  [26285.658629]  [] ? gen6_pm_rps_work+0xe0/0xe0 [i915]
  [26285.658632]  [] worker_thread+0x12e/0x2f0
  [26285.658636]  [] ? manage_workers.isra.26+0x200/0x200
  [26285.658640]  [] kthread+0x93/0xa0
  [26285.658644]  [] kernel_thread_helper+0x4/0x10
  [26285.658649]  [] ? kthread_freezable_should_stop+0x70/0x70
  [26285.658652]  [] ? gs_change+0x13/0x13
  [26285.658654] ---[ end trace 59c6162fdfcbffee ]---
  [26756.021167] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26756.021426] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26766.014093] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26766.014397] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26932.376233] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26932.376544] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26932.384285] [ cut here ]
  [26932.384354] WARNING: at 
/build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 
gen6_enable_rps+0x706/0x710 [i915]()
  [26932.384356] Har

[Kernel-packages] [Bug 1124250] Re: Partially incorrect uid mapping with nfs4/idmapd/ldap-auth

[Bug Watch Updater]

Launchpad has imported 42 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=876705.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2012-11-14T18:52:45+00:00 Maurizio wrote:

Description of problem:
When listing an nfs4 mounted directory an incorrect ownership of -2 is shown
for some users. 

Version-Release number of selected component (if applicable):
nfs client (Fedora 17):
nfs-utils-1.2.6-5.fc17.i686
kernel-PAE-3.6.5-1.fc17.i686

nfs server (Fedora 16):
nfs-utils-1.2.5-5.fc16.i686
kernel-PAE-3.3.5-2.fc16.i686

How reproducible:
by listing an NFS4 mounted directory with files owned by many users.

Steps to Reproduce:
1. Mount via NFS4 an export containing files owned by more than 200 different 
users (e.g. /var/spool/mail/)
2. Do "ls -l "
  
Actual results:
for some users the ownership is incorrectly given as 4294967294

Expected results:
the owner of all files should be mapped correctly

Additional info:
in /proc/keys there is a listing of all cached uid mappings, the user that
are not listed correctly are not present in the list.
Strangely, all keys are shown as "permanent" instead of having an expiration
time of 600 seconds.
Also they are contributing (flag Q) to the quota.

in /proc/key-users you can find the current maximum allowed number of keys
for the root user (200).

Bug https://bugzilla.redhat.com/show_bug.cgi?id=847084 probably has the
same origin; however that bug has been closed as NOTABUG.

Reply at: https://bugs.launchpad.net/fedora/+bug/1124250/comments/0


On 2012-11-15T08:56:06+00:00 Steve wrote:

*** Bug 847084 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/fedora/+bug/1124250/comments/1


On 2012-11-15T09:01:16+00:00 Steve wrote:

David,

Would it make sense to patch the kernel so the maxkeys/root_maxkeys are
set to a more reasonable value?

Reply at: https://bugs.launchpad.net/fedora/+bug/1124250/comments/2


On 2012-11-15T09:15:05+00:00 Luca wrote:

I have given a look at the relevant sources for the fedora kernel
(upstream it is just the same). It appears that nfsid keys should be
created within the keyring


keyring = key_alloc(&key_type_keyring, ".id_resolver", 0, 0, cred,
 (KEY_POS_ALL & ~KEY_POS_SETATTR) |
 KEY_USR_VIEW | KEY_USR_READ,
 KEY_ALLOC_NOT_IN_QUOTA);

in idmap.c

However they do still count toward the quota of root (whence the problem).
This is quite surprising and, unless I am misrepresenting the situation, it 
could be a bug somewhere else.

Reply at: https://bugs.launchpad.net/fedora/+bug/1124250/comments/3


On 2013-02-03T22:09:14+00:00 Maurizio wrote:

The issue is still there on a fresh installation of a Fedora 18.  Now this is
quite unfortunate: like this NFS4 is unreliable and quite unusable especially 
on systems like mail servers that typically handle files with many differing 
ownerships in a common directory.
Is this going to be fixed?

Reply at: https://bugs.launchpad.net/fedora/+bug/1124250/comments/4


On 2013-03-13T05:35:34+00:00 Maurizio wrote:

The problem is still present after a fresh update of the client:

nfs client (Fedora 18):
nfs-utils-1.2.7-3.fc18.i686
kernel-PAE-3.8.2-206.fc18.i686

nfs server (Fedora 16):
nfs-utils-1.2.5-5.fc16.i686
kernel-PAE-3.3.5-2.fc16.i686

The description of the problem above still applies.  Moreover nothing
is written in /var/log/messages

Reply at: https://bugs.launchpad.net/fedora/+bug/1124250/comments/7


On 2013-04-10T08:27:53+00:00 David wrote:

I don't see the issue between 2 Fedora 18 machines. Unfortunately, our Fedora 
and Ubuntu clients do run into this problem all the time with the home and mail 
directories, which are on RHEL 6 servers.
Could it be that the bug was fixed in recent Fedora kernels, but that RHEL 6 is 
still waiting for a fix?

Reply at: https://bugs.launchpad.net/fedora/+bug/1124250/comments/8


On 2013-04-10T09:21:00+00:00 Anders wrote:

This is what I use on our Fedora machines (1000 is enough for us ATM):

/etc/sysctl.d/nfsv4_idmap_maxkeys:

  # NFSv4 idmap entries are counted against a very low quota
  # https://bugzilla.redhat.com/show_bug.cgi?id=876705
  kernel.keys.root_maxkeys = 1000

[Kernel-packages] [Bug 1043518] Re: live cd is unusable due to video degradation with the splash boot option enabled

[Bug Watch Updater]

Launchpad has imported 13 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=857300.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2012-09-14T04:35:34+00:00 Adam wrote:

This bug splits off the problem described in comments #12 through #20 of
https://bugzilla.redhat.com/show_bug.cgi?id=848305 . After plymouth was
updated to 0.8.7 - partly to fix that bug - a serious issue showed up
with several NVIDIA adapters: when booting normally to a desktop,
runlevel '5', plymouth enabled, all as normal, either the DM doesn't
really appear at all (though it claims to be running), or it appears but
somewhat corrupted; if you can get through the DM to the desktop, it
will also be corrupted.

Booting to runlevel 3 and starting the DM service manually, or dropping
'rhgb' from the kernel parameters, acts as a workaround.

airlied says he has found the fix for this:
https://patchwork.kernel.org/patch/1455231/ . He plans to run it by Ben
and then submit it upstream.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518/comments/14


On 2012-09-14T04:38:18+00:00 Adam wrote:

Proposing as Beta blocker (conditional infringement of the 'live must
boot' and 'installed system must boot' criteria in the case of certain
NVIDIA adapters. We should commonbugs this for Alpha, as Alpha has the
bug.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518/comments/15


On 2012-09-14T06:02:37+00:00 Xavier wrote:

Created attachment 612728
F18 Alpha Live KDE, loading sessiion

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518/comments/16


On 2012-09-14T06:04:34+00:00 Xavier wrote:

Created attachment 612729
F18 Alpha Live KDE, session ready (Device notifier offering usb stick)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518/comments/17


On 2012-09-14T06:45:58+00:00 Xavier wrote:

Captures made on Asus V1S laptop with GeForce 8600M GT (512MB VRAM).

Alpha (RC3) is the first of GNOME/KDE Live TCs/RCs to run plymouth
charge correctly on this hardware (bug 87), despite leading to the
present defect. Dropping 'rhgb' from the kernel parameters, acts as a
workaround as you mentioned (raw tty messaging instead of any animation,
then no graphic corruption, KDE loads fine and Desktop Effects are
enabled by default).

Safe graphics (vesa) acts as yet another workaround, loading plymouth
text animation. All other routes -- except vesa -- lead to extreme
slowness (bug 855560) on this hardware, for both GNOME and KDE Live
spins. LXDE Live Alpha (RC3) just works as default, without any
workaround, running plymouth charge. Is the present defect, only
affecting desktop acceleration ?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518/comments/18


On 2012-09-14T17:54:50+00:00 Patrick wrote:

I had this issue when installing TC5 and could not make heads of tails
of it. I stumbled on a fix when I installed F17 and then "upgraded" to
F18. When I boot with the old F17 kernel (3.5.3-1.fc17.x86_64)
everything works perfectly, but with the F18 3.6 kernels I am lucky to
get to a GDM and if I do it is a horrid mess. Booting to runlevel 3 and
then launching the GDM did not help.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518/comments/19


On 2012-09-14T18:48:54+00:00 Adam wrote:

I've tested airlied's fix and it works for me. The scratch build I used
to test is here:

http://koji.fedoraproject.org/koji/taskinfo?taskID=4482706

feel free to grab it before it expires and check that it works for you
too. thanks!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518/comments/20


On 2012-09-16T13:13:12+00:00 Josh wrote:

Patch is picked up in kernel-3.6.0-0.rc5.git3.1.fc18

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518/comments/23


On 2012-09-17T08:59:35+00:00 Kamil wrote:

On an installed system I never reproduced the graphics corruption, the
system froze instead after login. kernel-3.6.0-0.rc5.git3.1.fc18 fixed
the issue for me.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518/comments/24

---

[Kernel-packages] [Bug 1070837] Re: general protection fault: 0000 [#1] SMP; RIP: 0010:[] [] HostIF_SafeRDMSR+0xf/0x30 [vmmon]

[Bug Watch Updater]

Launchpad has imported 2 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=861837.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2012-10-01T02:35:35+00:00 Dan wrote:

Description of problem:
installing VMware Workstation 9

Additional info:
libreport version: 2.0.14
abrt_version:   2.0.13
cmdline:BOOT_IMAGE=/vmlinuz-3.5.4-2.fc17.x86_64 
root=/dev/mapper/vg_dm--t510-lv_root ro rd.lvm.lv=vg_dm-t510/lv_swap rd.dm=0 
KEYTABLE=us SYSFONT=True rd.md=0 rd.luks=0 rd.lvm.lv=vg_dm-t510/lv_root 
LANG=en_US.UTF-8 rhgb quiet nouveau.modeset=0 rd.driver.blacklist=nouveau
kernel: 3.5.4-2.fc17.x86_64

kernel_tainted_long:
:Proprietary module has been loaded.
:Modules from drivers/staging are loaded.

backtrace:
:general protection fault:  [#1] SMP 
:CPU 6 
:Modules linked in: vmnet(O) parport_pc vsock(O) vmci(O) vmmon(O) ppdev parport 
nls_utf8 vfat fat fuse ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat 
xt_CHECKSUM iptable_mangle be2iscsi iscsi_boot_sysfs bnx2i vboxpci(O) 
vboxnetadp(O) vboxnetflt(O) bridge stp llc cnic uio cxgb4i cxgb4 cxgb3i cxgb3 
mdio libcxgbi ib_iser lockd sunrpc vboxdrv(O) rdma_cm ib_addr iw_cm ib_cm ib_sa 
ib_mad ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi rfcomm bnep 
nf_conntrack_ipv4 nf_defrag_ipv4 ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 
xt_state nf_conntrack ip6table_filter ip6_tables snd_hda_codec_hdmi 
snd_hda_codec_conexant arc4 nvidia(PO) btusb bluetooth coretemp microcode 
i7core_edac snd_hda_intel edac_core snd_hda_codec i2c_i801 snd_hwdep lpc_ich 
mfd_core snd_seq snd_seq_device snd_pcm iwlwifi mac80211 e1000e cfg80211 
snd_page_alloc mei snd_timer i2c_core vhost_net tun macvtap macvlan kvm_intel 
kvm thinkpad_acpi snd soundcore rfkill uinput mmc_block crc32c_intel
:usb_storage firewire_ohci firewire_core crc_itu_t sdhci_pci sdhci mmc_core 
mxm_wmi video wmi [last unloaded: vmnet]
:Pid: 5159, comm: vmware-hostd Tainted: P C O 3.5.4-2.fc17.x86_64 #1 
LENOVO 4391BS6/4391BS6
:RIP: 0010:[]  [] HostIF_SafeRDMSR+0xf/0x30 
[vmmon]
:RSP: 0018:880207f31b88  EFLAGS: 00010246
:RAX:  RBX: 0001 RCX: 0491
:RDX:  RSI: 880207cc4210 RDI: 0491
:RBP: 880207f31b88 R08: 880237d96670 R09: a119c872
:R10: 06953e14 R11:  R12: 
:R13: 880207cc4200 R14: 880207cc4200 R15: 7fff25832480
:FS:  7fd57d873740() GS:880237d8() knlGS:
:CS:  0010 DS:  ES:  CR0: 80050033
:CR2: 00db93e0 CR3: 000227c23000 CR4: 07e0
:DR0:  DR1:  DR2: 
:DR3:  DR6: 0ff0 DR7: 0400
:Process vmware-hostd (pid: 5159, threadinfo 880207f3, task 
880207df9710)
:Stack:
: 880207f31bb8 a119ee23 a119eda0 880207f31be8
: 880207cc4200  880207f31bd8 a119d980
: 880207cc4200 fff4 880207f31c08 a11a0c1c
:Call Trace:
: [] Vmx86GetMSR+0x83/0xd0 [vmmon]
: [] ? Vmx86GetUnavailPerfCtrsOnCPU+0x150/0x150 [vmmon]
: [] HostIF_CallOnEachCPU+0x20/0x40 [vmmon]
: [] Vmx86_GetAllMSRs+0x2c/0x50 [vmmon]
: [] LinuxDriver_Ioctl+0x70f/0xd40 [vmmon]
: [] ? unlock_page+0x31/0x50
: [] ? __do_fault+0x3f9/0x560
: [] ? handle_pte_fault+0x95/0xb10
: [] ? handle_mm_fault+0x259/0x320
: [] ? do_page_fault+0x1bc/0x4b0
: [] LinuxDriver_UnlockedIoctl+0x18/0x20 [vmmon]
: [] do_vfs_ioctl+0x99/0x580
: [] ? inode_has_perm.isra.31.constprop.61+0x2a/0x30
: [] ? file_has_perm+0x97/0xb0
: [] sys_ioctl+0x99/0xa0
: [] system_call_fastpath+0x16/0x1b
:Code: 83 c4 01 e8 74 46 f9 df 44 89 e0 48 3b 43 08 72 e9 48 89 df e8 23 54 fd 
df eb 9e 90 55 48 89 e5 66 66 66 66 90 31 c0 89 c2 89 f9 <0f> 32 31 ff 41 89 c0 
48 c1 e2 20 89 f8 4c 09 c2 48 89 16 5d c3 
:RIP  [] HostIF_SafeRDMSR+0xf/0x30 [vmmon]
: RSP 

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1070837/comments/0


On 2012-10-01T11:50:05+00:00 Josh wrote:

Bug in vmware modules.  We can't fix that.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1070837/comments/1


** Changed in: linux (Fedora)
   Status: Unknown => Invalid

** Changed in: linux (Fedora)
   Importance: Unknown => Undecided

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

Title:
  general protection fault:  [#1] SMP; RIP:
  0010:[] []
  HostIF_SafeRDMSR+0xf/0x30 [vmmon]

Status in linux package in Ubuntu:
  Invalid
Status in vmware-play

[Kernel-packages] [Bug 913272] Re: drm:intel_dsm_platform_mux_info] *ERROR* MUX INFO call failed‏

[Bug Watch Updater]

Launchpad has imported 5 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=846382.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2012-08-07T15:37:50+00:00 Renato wrote:

Just cloning the bug that was never fixed since F15.
+++ This bug was initially created as a clone of Bug #709115 +++

Description of problem:
every time i boot my laptop the graphical boot thing comes up for a little bit 
and then the screen goes black and shows this error. another user on the 
#fedora irc said he had the same problem and linked it to nvidia chipsets with 
intel processors. my laptop has an nvidia mobility 550 graphics card and a 2nd 
generation i7 processor.

Version-Release number of selected component (if applicable):
fedora 15

How reproducible:
every time i turn on my laptop.

Steps to Reproduce:
1.restart computer
2.
3.
  
Actual results:


Expected results:


Additional info:
http://fpaste.org/DL6r/ - messages log lines 1437 shows error.

--- Additional comment from mc...@redhat.com on 2011-06-03 05:57:25 EDT
---

Thanks for the bug report. This is interesting

May 29 10:55:46 localhost kernel: [ 2.868467] [drm] Initialized drm 1.1.0 
20060810
May 29 10:55:46 localhost kernel: [ 2.891688] i915 :00:02.0: PCI INT A -> 
GSI 16 (level, low) -> IRQ 16
May 29 10:55:46 localhost kernel: [ 2.905710] VGA switcheroo: detected DSM 
switching method \_SB_.PCI0.PEG0.PEGP handle
May 29 10:55:46 localhost kernel: [ 2.905733] nouveau :01:00.0: power state 
changed by ACPI to D0
May 29 10:55:46 localhost kernel: [ 2.905737] nouveau :01:00.0: power state 
changed by ACPI to D0
May 29 10:55:46 localhost kernel: [ 2.905742] nouveau :01:00.0: enabling 
device (0006 -> 0007)
May 29 10:55:46 localhost kernel: [ 2.905749] nouveau :01:00.0: PCI INT A 
-> GSI 16 (level, low) -> IRQ 16
May 29 10:55:46 localhost kernel: [ 2.927493] [drm] Supports vblank timestamp 
caching Rev 1 (10.10.2010).
May 29 10:55:46 localhost kernel: [ 2.927495] [drm] Driver supports precise 
vblank timestamp query.
May 29 10:55:46 localhost kernel: [ 2.962260] [drm:intel_dsm_platform_mux_info] 
*ERROR* MUX INFO call failed
May 29 10:55:46 localhost kernel: [ 2.962377] [drm:intel_dsm_platform_mux_info] 
*ERROR* MUX INFO call failed
May 29 10:55:46 localhost kernel: [ 3.026017] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=none:owns=io+mem
May 29 10:55:46 localhost kernel: [ 3.026020] vgaarb: transferring owner from 
PCI::00:02.0 to PCI::01:00.0
May 29 10:55:46 localhost kernel: [ 3.078529] fbcon: inteldrmfb (fb0) is 
primary device
May 29 10:55:46 localhost kernel: [ 3.140048] Console: switching to colour 
frame buffer device 200x56
May 29 10:55:46 localhost kernel: [ 3.144878] fb0: inteldrmfb frame buffer 
device
May 29 10:55:46 localhost kernel: [ 3.144880] drm: registered panic notifier
May 29 10:55:46 localhost kernel: [ 3.145108] [Firmware Bug]: ACPI(PEGP) 
defines _DOD but not _DOS

but there is some additional information we require that will be helpful
in our diagnosis of this issue.

Please add drm.debug=0x04 to the kernel command line, restart computer,
and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of the dmesg command, and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the
bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this
information.

Thanks in advance.

--- Additional comment from mc...@redhat.com on 2011-06-03 05:58:27 EDT
---

Created attachment 502770
dmesg output

--- Additional comment from jero...@gmail.com on 2011-06-03 18:08:19 EDT
---

Created attachment 502919
my xorg log

--- Additional comment from jero...@gmail.com on 2011-06-03 18:15:36 EDT
---

Created attachment 502920
my messages log

--- Additional comment from jero...@gmail.com on 2011-06-03 18:17:36 EDT
---

Created attachment 502921
dmesg output.

--- Additional comment from jero...@gmail.com on 2011-06-03 21:17:32 EDT
---

I should probably say that this error happens also happens when i close
my laptop (normally puts OS to sleep) and then i open it, its displaying
that error and sometimes freezes

--- Additional comment from mc...@redhat.com on 2011-06-06 17:42:56 EDT
---

(In reply to comment #6)
> I should probably say that this error happens also happens when i close my
> laptop (normally puts OS to sleep) and then i open it, its displaying that
> error and sometimes freezes

Can I ask for clarification please? When this error happens (on boot or
suspend) that's the end of the story? Computer is not usable anytime
later on its own?

Thank you

Matěj

--- A

[Kernel-packages] [Bug 1070773] Re: 1002:7188 system hangs on boot (at loading radeon related modules)

[Bug Watch Updater]

** Changed in: linux (Fedora)
   Status: Unknown => Invalid

** Changed in: linux (Fedora)
   Importance: Unknown => Undecided

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

Title:
  1002:7188 system hangs on boot (at loading radeon related modules)

Status in linux package in Ubuntu:
  Fix Released
Status in linux package in Fedora:
  Invalid

Bug description:
  After an upgrade to Ubuntu 12.10 (kernel 3.5), the system fails to
  boot. When starting without "quiet splash" options, the last kernel
  messages relate to loading and initializing radeon and drm modules.

  Same problems are here when trying to boot 12.10 live usb images, both
  32- and 64-bit.

  I'm currently using 3.2 kernel from Precise, which boots fine.

  According to RH bug report comment, the problem was introduced with an 
upstream merge commit:
  f9369910a6225b8d4892c3f20ae740a711cd5ace
  Ubuntu kernel 3.4.0-5.11 boots fine, 3.5.0-1.1 freezes.

  WORKAROUND: When using the following kernel boot parameter the system boots 
but doesn't switch to the native resolution of 1280x800, and leaves it as 
1024x768:
  nomodeset

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-17-generic 3.5.0-17.28
  ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
  Uname: Linux 3.2.0-32-generic i686
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  keplicz4275 F pulseaudio
  Date: Wed Oct 24 12:34:20 2012
  HibernationDevice: RESUME=UUID=3a2133a7-9acb-4a14-a4f8-2dd1a8b1e412
  MachineType: Hewlett-Packard HP Compaq 6910p
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-32-generic 
root=UUID=b1aade02-95c2-4d36-8878-027b70c9ec46 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-32-generic N/A
   linux-backports-modules-3.2.0-32-generic  N/A
   linux-firmware1.95
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to quantal on 2012-10-21 (2 days ago)
  dmi.bios.date: 09/13/2007
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MCD Ver. F.0A
  dmi.board.name: 30C1
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 68.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MCDVer.F.0A:bd09/13/2007:svnHewlett-Packard:pnHPCompaq6910p:pvrF.0A:rvnHewlett-Packard:rn30C1:rvrKBCVersion68.32:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq 6910p
  dmi.product.version: F.0A
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1009675] Re: suspend causes system lockup

[Bug Watch Updater]

** Changed in: linux (Fedora)
   Status: Unknown => Expired

** Changed in: linux (Fedora)
   Importance: Unknown => Undecided

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

Title:
  suspend causes system lockup

Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Fedora:
  Expired

Bug description:
  when I press the top right button on th screen and select suspend the
  system locks up with the screen black but lit

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-24-generic-pae 3.2.0-24.39
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic-pae 3.2.16
  Uname: Linux 3.2.0-24-generic-pae i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ms 1425 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf7e0 irq 49'
 Mixer name : 'Intel CougarPoint HDMI'
 Components : 'HDA:14f1506e,17aa5003,0012 
HDA:80862805,17aa5003,0010'
 Controls  : 14
 Simple ctrls  : 6
  Date: Wed Jun  6 23:29:36 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  MachineType: LENOVO 20111
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic-pae 
root=UUID=96d4f02b-91cb-4d84-b6cc-790e49b48a73 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-24-generic-pae N/A
   linux-backports-modules-3.2.0-24-generic-pae  N/A
   linux-firmware1.79
  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/03/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 56CN43WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: U300s
  dmi.board.vendor: LENOVO
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad U300s
  dmi.modalias: 
dmi:bvnLENOVO:bvr56CN43WW:bd04/03/2012:svnLENOVO:pn20111:pvrLenovoIdeaPadU300s:rvnLENOVO:rnU300s:rvr1.0:cvnLENOVO:ct10:cvrLenovoIdeaPadU300s:
  dmi.product.name: 20111
  dmi.product.version: Lenovo IdeaPad U300s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1029790] Re: 1002:714a Can't boot without nomodeset option-kernel 3.5.X.X/3.6.X.X ATI M52 [Mobility Radeon X1300]

[Bug Watch Updater]

** Changed in: linux (Fedora)
   Status: Unknown => Invalid

** Changed in: linux (Fedora)
   Importance: Unknown => Undecided

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

Title:
  1002:714a Can't boot without nomodeset option-kernel 3.5.X.X/3.6.X.X
  ATI M52 [Mobility Radeon X1300]

Status in linux package in Ubuntu:
  Fix Released
Status in linux package in Fedora:
  Invalid

Bug description:
  I'm using Ubuntu quantal (development branch), since the new 3.5 kernel 
coming, I can't boot I don't know where is the problem, kernel or ati module, 
but with 3.4 kernel there is no problem booting the Ubuntu.
  When choose the 3.5 kernel from grub menu and start loading, after 10-15 
seconds, just freeze, and can't do anything. I tried and mainline kernel from 
kernel-ppa/mainline but no change, still can't boot.

  A Ubuntu kernel version bisect revealed that 3.4.0-5.11 works and the
  first problematic kernel is 3.5.0-1.1 .

  WORKAROUND: 1. edit grub command line to add 'nomodeset' and boot.

  2. Then add 'nomodeset' in GRUB2's kernel command line (using
  GRUB_CMDLINE_LINUX in /etc/default/grub) and run 'sudo update-grub'

  3. Add the following to /etc/rc.d/rc.local:
  modprobe -r radeon
  modprobe -r drm
  modprobe radeon modeset=1

  4. Remove ~/.Xauthority

  5. Reboot

  WORKAROUND: Use kernel parameter:
  nomodeset

  However, with nomodeset, 3D don't work correctly, cant use normal
  unity session, unity 2D session works but with artifacts.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-generic 3.5.0.6.6
  ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0
  Uname: Linux 3.4.0-5-generic x86_64
  ApportVersion: 2.4-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tolostoi   1789 F pulseaudio
  Date: Fri Jul 27 09:38:39 2012
  HibernationDevice: RESUME=UUID=8f2b4b51-ca26-4a68-8969-ea8e5c00f4b6
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120408)
  MachineType: Hewlett-Packard HP Compaq nc6400 (RH484EA#ABB)
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.4.0-5-generic 
root=UUID=c2283854-278c-4d59-93dd-d05801489a93 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.4.0-5-generic N/A
   linux-backports-modules-3.4.0-5-generic  N/A
   linux-firmware   1.86
  SourcePackage: linux
  UpgradeStatus: Upgraded to quantal on 2012-06-11 (45 days ago)
  dmi.bios.date: 09/05/2007
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68YCD Ver. F.0B
  dmi.board.name: 30AC
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 56.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68YCDVer.F.0B:bd09/05/2007:svnHewlett-Packard:pnHPCompaqnc6400(RH484EA#ABB):pvrF.0B:rvnHewlett-Packard:rn30AC:rvrKBCVersion56.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq nc6400 (RH484EA#ABB)
  dmi.product.version: F.0B
  dmi.sys.vendor: Hewlett-Packard
  ---
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 3199 F pulseaudio
  CasperVersion: 1.331
  DistroRelease: Ubuntu 13.04
  LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MachineType: Hewlett-Packard HP Compaq nc6400 (RH484EA#ABB)
  MarkForUpload: True
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/username.seed 
boot=casper nomodeset quiet splash -- BOOT_IMAGE=/casper/vmlinuz
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-19-generic N/A
   linux-backports-modules-3.8.0-19-generic  N/A
   linux-firmware1.106
  Tags:  raring
  Uname: Linux 3.8.0-19-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 09/05/2007
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68YCD Ver. F.0B
  dmi.board.name: 30AC
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 56.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68YCDVer.F.0B:bd09/05/2007:svnHewlett-Packard:pnHPCompaqnc6400(RH484EA#ABB):pvrF.0B:rvnHewlett-Packard:rn30AC:rvrKBCVersion56.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq nc6400 (RH484EA#ABB)
  dmi.prod

[Kernel-packages] [Bug 1124328] Re: *ERROR* failed to set mode on [CRTC:7]

[Bug Watch Updater]

** Changed in: fedora
   Status: Unknown => Won't Fix

** Changed in: fedora
   Importance: Unknown => 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/1124328

Title:
  *ERROR* failed to set mode on [CRTC:7]

Status in Linux:
  Invalid
Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  Opinion
Status in Fedora:
  Won't Fix

Bug description:
  When I boot I receive this error. This is the same bug being tracked
  (and possibly ignored) by redhat. Please see the link for logs that
  others have submitted etc...

  https://bugzilla.redhat.com/show_bug.cgi?id=753050

  I am using a Thinkpad T430s docked with DVI monitor and VGA monitor (a
  common configuration I would imagine). I read that there is a hardware
  limitation for supporting LVDS+DVI+VGA concurrently, but since the
  laptop is docked (and screen closed) I don't believe this explains the
  bug.

  For the record, I am using 
  Ubuntu Release:   12.10
  kernel 3.5.0-23-generic
  Graphics: 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen 
Core processor Graphics Controller [8086:0166] (rev 09)
Subsystem: Lenovo Device [17aa:21fb]
Kernel driver in use: i915

  
  Please let me know how I can be of any further help.

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

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

[Kernel-packages] [Bug 886820] Re: [Kubuntu 11.10] Screen brightness control does not work on Samsung RV511 laptop

[Bug Watch Updater]

Launchpad has imported 25 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=796626.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2012-02-23T11:00:12+00:00 carasin wrote:

Description of problem:

There is a laptop Samsung RV520 with installed Fedora 16. Some hotkeys (Fn + 
) don't work, e.g. [Fn + Up/Down] (backlight brightness control), [Fn + 
F5] (display backlight off/on), [Fn + F9] (wireless devices on/off). At the 
same time, hotkeys [Fn + Esc] (suspend), [Fn + Right/Left] (volume level 
up/down) and [Fn + F6] (volume off/on) work fine.
 shows that  module isn't loaded. Attempt to load this 
module fails with error "No such device".
When I press [Fn + Up/Down], the contents of the files (, 
) at the path 
 
change. But actually brightness level doesn't change.
___

Version-Release number of selected component (if applicable):

kernel-3.1.0-7.fc16.i686 / kernel-3.2.6-3.fc16.i686, udev-173-3.fc16.i686
___

How reproducible:
always
___

Steps to Reproduce:
1. Press [Fn + Up/Down/F9] (Samsung RV520, Fedora 16)
2. Backlight level doesn't change, wireless devices don't switch
___

Actual results:
Some [Fn + ] hotkeys don't work.
___

Expected results:
All [Fn + ] hotkeys (e.g. brightness control and wireless devices on/off) 
work fine.

Additional info:
 command returns 
.
The passing the  argument to the kernel doesn't help.
This trouble appears also in the Live-CD mode.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/886820/comments/29


On 2012-02-24T15:54:03+00:00 carasin wrote:

I've tried to change the display brightness level with the 
command, but this attempt has failed:

$ lspci | grep VGA
01:00.0 VGA compatible controller: nVidia Corporation Device 1050 (rev a1)
$ sudo setpci -s 01:00.0 F4.B
00
$ sudo setpci -s 01:00.0 F4.B=50
$ sudo setpci -s 01:00.0 F4.B
00

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/886820/comments/30


On 2012-02-24T20:45:24+00:00 Josh wrote:

Theoretically, the patches for this are here:

http://thread.gmane.org/gmane.linux.drivers.platform.x86.devel/2700/focus=2701

and queued up in the platform maintainer's git tree somewhere.  The
don't seem to have made the 3.3 kernel though.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/886820/comments/31


On 2012-02-24T21:13:21+00:00 carasin wrote:

As far as I'm concerned, the necessary changes at the 
driver will be in the kernel 3.4 or, if lucky, in 3.3. Right?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/886820/comments/32


On 2012-02-25T12:46:09+00:00 carasin wrote:

I've took a workaround, which made brightness control to work:
I've put this code to the 
___
{
.ident = "RV420/RV520/RV720/E3530/S3530/E3420/E3520",
.matches = {
DMI_MATCH(DMI_SYS_VENDOR,
"SAMSUNG ELECTRONICS CO., LTD."),
DMI_MATCH(DMI_PRODUCT_NAME, 
"RV420/RV520/RV720/E3530/S3530/E3420/E3520"),
DMI_MATCH(DMI_BOARD_NAME, 
"RV420/RV520/RV720/E3530/S3530/E3420/E3520"),
},
.callback = dmi_check_cb,
},
___
and compiled the module with this Makefile:
___
obj-m   := samsung-laptop.o

KERNELDIR ?= /lib/modules/$(shell uname -r)/build
PWD   := $(shell pwd)

all:
$(MAKE) -C $(KERNELDIR) M=$(PWD)

clean:
rm -f *.o *~ core .depend .*.cmd *.ko *.mod.c
rm -f Module.markers Module.symvers modules.order
rm -rf .tmp_versions Modules.symvers
___
Then I've put  to the  directory and run <# depmod -a>.

Now the brightness level is adjustable.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/886820/comments/33


On 2012-03-22T17:12:31+00:00 Dave wrote:

[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/886820/comments/35


On 2012-03-22T17:14:48+00:00 Dave wrote:

[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repos

[Kernel-packages] [Bug 974838] Re: Wireless Dropout - Tx aggregation enabled on ra (workaround: iwlwifi requires 11n_disable=1)

[Bug Watch Updater]

Launchpad has imported 10 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=787446.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2012-02-05T06:18:30+00:00 Simon wrote:

After a period of time, the wireless simply stops functioning... NetworkManager 
thinks its still connected.. but no network traffic works.
After a period of time (if left) sometimes it reconnects at G-54Mbit speed.. vs 
'N' at around 270Mbit

The following are observed in dmesg:

[  505.669220] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[  555.202192] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[  588.834218] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[  617.740773] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[  690.116581] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[  742.430541] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[  788.704026] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[  801.676020] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[  962.686813] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1015.634260] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1099.420837] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1107.568703] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1119.465765] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1147.984058] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1213.937449] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1239.211977] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1352.128153] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1428.874172] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1467.239910] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1501.816674] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1585.802417] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1638.777505] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1669.836635] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1706.886181] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1733.298790] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0



Kernel; Linux greenback.local 3.2.2-1.fc16.x86_64 #1 SMP Thu Jan 26
03:21:58 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux




Some details as to the wireless adapter;

[5.214347] Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
[5.214441] iwlwifi :03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[5.214496] iwlwifi :03:00.0: setting latency timer to 64
[5.214542] iwlwifi :03:00.0: pci_resource_len = 0x2000
[5.214544] iwlwifi :03:00.0: pci_resource_base = c900058a
[5.214545] iwlwifi :03:00.0: HW Revision ID = 0x34
[5.214830] iwlwifi :03:00.0: irq 50 for MSI/MSI-X
[5.214919] iwlwifi :03:00.0: CONFIG_IWLWIFI_DEBUG disabled
[5.214921] iwlwifi :03:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
[5.214922] iwlwifi :03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled
[5.214924] iwlwifi :03:00.0: CONFIG_IWLWIFI_DEVICE_TESTMODE disabled
[5.214925] iwlwifi :03:00.0: CONFIG_IWLWIFI_P2P disabled
[5.214956] iwlwifi :03:00.0: Detected Intel(R) Centrino(R) Advanced-N 
6205 AGN, REV=0xB0
[5.215034] iwlwifi :03:00.0: L1 Enabled; Disabling L0S
[5.225137] iwlwifi :03:00.0: device EEPROM VER=0x715, CALIB=0x6
[5.225140] iwlwifi :03:00.0: Device SKU: 0x1F0
[5.225142] iwlwifi :03:00.0: Valid Tx ant: 0x3, Valid Rx ant: 0x3
[5.225166] iwlwifi :03:00.0: Tunable channels: 13 802.11bg, 24 802.11a 
channels
[5.241189] iwlwifi :03:00.0: loaded firmware version 17.168.5.3 build 
42301
[9.282736] iwlwifi :03:00.0: L1 Enabled; Disabling L0S
[9.282928] iwlwifi :03:00.0: Radio type=0x1-0x2-0x0
[9.565154] iwlwifi :03:00.0: L1 Enabled; Disabling L0S
[9.565344] iwlwifi :03:00.0: Radio type=0x1-0x2-0x0
[   45.937516] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 6

Reply at:
https:/

[Kernel-packages] [Bug 957131] Re: btrfs kernel bug

[Bug Watch Updater]

Launchpad has imported 4 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=788064.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2012-02-07T11:20:27+00:00 Tomasz wrote:

Description of problem:
I have 4 1TB disk in raid10. Everytime I run following fio load, after few 
hours I got BUG() like below. Btrfs mounted with compress=lzo,space_cache

#v+
[write-test]


rw=randwrite
ioengine=libaio 


blocksize=4k


iodepth=32  


size=1512G   
#v-

[64354.305737] [ cut here ]
[64354.306009] kernel BUG at fs/btrfs/inode.c:1668!
[64354.306009] invalid opcode:  [#1] SMP 
[64354.306009] CPU 1 
[64354.306009] Modules linked in: lockd bnep bluetooth rfkill snd_intel8x0 
snd_ac97_codec ac97_bus snd_seq snd_seq_device ppdev snd_pcm snd_timer snd 
soundcore iTCO_wdt tg3 parport_pc iTCO_vendor_support parport snd_page_alloc 
dcdbas serio_raw i2c_i801 microcode sunrpc uinput aoe btrfs zlib_deflate 
libcrc32c sata_promise i915 drm_kms_helper drm i2c_algo_bit i2c_core video 
[last unloaded: scsi_wait_scan]
[64354.330470] 
[64354.330470] Pid: 5149, comm: btrfs-endio-wri Tainted: GW
3.3.0-0.rc2.git3.2.fc17.x86_64 #1 Dell Inc. OptiPlex GX620  
 /0FH884
[64354.330470] RIP: 0010:[]  [] 
insert_reserved_file_extent.constprop.50+0x251/0x260 [btrfs]
[64354.330470] RSP: 0018:8800757ffbd0  EFLAGS: 00010286
[64354.330470] RDX:  RSI: ea00033c3700 RDI: 0246
[64354.330470] RBP: 8800757ffc60 R08: 8800cf0dc760 R09: 000100110002
[64354.330470] R10: 8800cf0dc7f0 R11:  R12: 8800a453a290
[64354.330470] R13: 8800cf0dc1d8 R14: 8800a3a69868 R15: 002e8f0b2000
[64354.330470] FS:  () GS:8800db00() 
knlGS:
[64354.330470] CS:  0010 DS:  ES:  CR0: 8005003b
[64354.330470] CR2: 003238285240 CR3: 23ba8000 CR4: 06e0
[64354.330470] DR0:  DR1:  DR2: 
[64354.330470] DR3:  DR6: 0ff0 DR7: 0400
[64354.330470] Process btrfs-endio-wri (pid: 5149, threadinfo 8800757fe000, 
task 880097978000)
[64354.330470] Stack:
[64354.330470]  00ff8800757ffc00 1000 001d7ab1f000 
8800a453a290
[64354.330470]  1000 8800cf207a90 8800757ffc50 
a0123455
[64354.330470]  8800757ffc30  00cc 
8800a3a69868
[64354.330470] Call Trace:
[64354.330470]  [] ? start_transaction+0x85/0x3b0 [btrfs]
[64354.330470]  [] btrfs_finish_ordered_io+0x232/0x350 [btrfs]
[64354.330470]  [] btrfs_writepage_end_io_hook+0x4c/0x150 
[btrfs]
[64354.330470]  [] end_bio_extent_writepage+0x122/0x170 
[btrfs]
[64354.330470]  [] bio_endio+0x1d/0x40
[64354.330470]  [] end_workqueue_fn+0x64/0x150 [btrfs]
[64354.330470]  [] worker_loop+0x149/0x5d0 [btrfs]
[64354.330470]  [] ? btrfs_queue_worker+0x310/0x310 [btrfs]
[64354.330470]  [] kthread+0xb7/0xc0
[64354.330470]  [] ? trace_hardirqs_on+0xd/0x10
[64354.330470]  [] kernel_thread_helper+0x4/0x10
[64354.330470]  [] ? _raw_spin_unlock_irq+0x30/0x50
[64354.330470]  [] ? retint_restore_args+0x13/0x13
[64354.330470]  [] ? kthread_worker_fn+0x1a0/0x1a0
[64354.330470]  [] ? gs_change+0x13/0x13
[64354.330470] Code: ff 84 0f 85 67 fe ff ff e9 5e fe ff ff 0f 1f 44 00 00 41 
80 be 78 fb ff ff 84 75 9a eb 94 0f 1f 40 00 b8 f4 ff ff ff eb b9 0f 0b <0f> 0b 
0f 0b 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 48 83 
[64354.330470] RIP  [] 
insert_reserved_file_extent.constprop.50+0x251/0x260 [btrfs]
[64354.330470]  RSP 
[64354.557410] ---[ end trace 6288379729f3c564 ]---
[64354.650352] [ cut here ]
[64354.651007] kernel BUG at fs/btrfs/inode.c:1668!
[64354.651007] invalid opcode:  [#2] SMP 
[64354.651007] CPU 0 
[64354.651007] Modules linked in: lockd bnep bluetooth rfkill snd_intel8x0 
snd_ac97_codec ac97_bus snd_seq snd_seq_device ppdev snd_pcm snd_timer snd 
soundc

[Kernel-packages] [Bug 974664] Re: Kernel Oops - BUG: unable to handle kernel paging request at ffffffffffffffb8; RIP: 0010:[] [] nfs_have_delegation+0x9/0x40 [nfs]

[Bug Watch Updater]

Launchpad has imported 33 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=811138.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2012-04-10T08:59:31+00:00 Bert wrote:

Description of problem:

Kernel traceback on NFS4 locking attempt

Version-Release number of selected component (if applicable):

kernel 3.3.1-2 (and 3.3.1-3)

How reproducible:

Always

Steps to Reproduce:
1. Install kernel 3.3.1-{2,3}; mount a users home over NFS4
2. Start e.g. pidgin, which tries to lock some file
3.
  
Actual results:

*) Pidgin crashes with 'Killed'.  Strace shows that the last activity
   is:

[...]
open("/users/visics/deknuydt/.config/enchant/en_US.dic", O_RDONLY) = 11
flock(11, LOCK_EX 
+++ killed by SIGKILL +++
Killed

*) In dmesg, you see:

 [  322.987247] BUG: unable to handle kernel paging request at ffb8
[  322.987330] IP: [] nfs_have_delegation+0x9/0x40 [nfs]
[  322.987418] PGD 1c07067 PUD 1c08067 PMD 0 
[  322.987495] Oops:  [#1] SMP 
[  322.987565] CPU 1 
[  322.987574] Modules linked in: nfs fscache nf_conntrack_ipv4 nf_defrag_ipv4 
xt_state nf_conntrack sha256_generic dm_crypt nvidia(PO) nfsd uinput lockd 
nfs_acl auth_rpcgss sunrpc snd_hda_codec_realtek snd_hda_intel snd_hda_codec 
snd_hwdep snd_seq snd_seq_device snd_pcm iTCO_wdt i2c_i801 iTCO_vendor_support 
intel_rng microcode r8169 i2c_core mii snd_timer snd soundcore snd_page_alloc 
serio_raw firewire_ohci firewire_core crc_itu_t sata_sil24 video [last 
unloaded: scsi_wait_scan]
[  322.988230] 
[  322.988230] Pid: 1697, comm: pidgin Tainted: P   O 
3.3.1-3.fc16.x86_64 #1 transtec AG /DG31PR
[  322.988230] RIP: 0010:[]  [] 
nfs_have_delegation+0x9/0x40 [nfs]
[  322.988230] RSP: 0018:880112e55dd8  EFLAGS: 00010246
[  322.988230] RAX: 880122411800 RBX: 880112e55e68 RCX: d8ca
[  322.988230] RDX:  RSI: 0001 RDI: 
[  322.988230] RBP: 880112e55dd8 R08: 00016560 R09: ea00044b8400
[  322.988230] R10: a0e0457a R11:  R12: d8ca
[  322.988230] R13: 8801218be000 R14: 88011573cc00 R15: 8801224b0480
[  322.988230] FS:  7fdda2060980() GS:88012fc8() 
knlGS:
[  322.988230] CS:  0010 DS:  ES:  CR0: 80050033
[  322.988230] CR2: ffb8 CR3: 000112c07000 CR4: 06e0
[  322.988230] DR0:  DR1:  DR2: 
[  322.988230] DR3:  DR6: 0ff0 DR7: 0400
[  322.988230] Process pidgin (pid: 1697, threadinfo 880112e54000, task 
880112dd2e60)
[  322.988230] Stack:
[  322.988230]  880112e55e28 a0e01fa1 880112e11e60 

[  322.988230]  8801224b0480 8801224b0780 8801224b0480 
0082
[  322.988230]  880112e55e68 fff5 880112e55eb8 
a0e04b9c
[  322.988230] Call Trace:
[  322.988230]  [] nfs4_handle_exception+0x241/0x3a0 [nfs]
[  322.988230]  [] nfs4_proc_lock+0xec/0x440 [nfs]
[  322.988230]  [] do_setlk+0xed/0x110 [nfs]
[  322.988230]  [] nfs_flock+0x89/0xe0 [nfs]
[  322.988230]  [] sys_flock+0x113/0x1c0
[  322.988230]  [] system_call_fastpath+0x16/0x1b
[  322.988230] Code: fd ff e9 40 fe ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 55 
48 89 e5 66 66 66 66 90 f0 80 4f 48 04 5d c3 55 48 89 e5 66 66 66 66 90 <48> 8b 
57 b8 31 c0 48 85 d2 74 0c 8b 4a 30 83 e6 03 21 f1 39 f1 
[  322.988230] RIP  [] nfs_have_delegation+0x9/0x40 [nfs]
[  322.988230]  RSP 
[  322.988230] CR2: ffb8
[  322.988230] ---[ end trace 158525064a4030cd ]---


Expected results:

*) No NFS4 delegation problems.

Additional info:

1) Koji kernel 3.3.1-3 has exactly the same problem.

2) Kernel 3.3.0-8 does not have the problem.

3) Sorry for the tainted kernel (nvidia).  I'll confirm with an untainted
   asap.

4) It seems that Ubuntu has this problem too.
   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/974664

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/974664/comments/3


On 2012-04-10T12:37:33+00:00 Tim wrote:

We are suffering the same problem, it occurs right after login when
gnome-keyring tries to access the home directory mounted via NFSv4 with
kernel 3.3.1-3 on the client. Server is CentOS 6.2. Client-side kernel
3.2.10-3.fc16.x86_64 works for us. Kernel is not tainted.

Apr 10 14:26:32 morgan kernel: [   54.179536] BUG: unable to handle kernel 
paging request at ffb8
Apr 10 14:26:32 morgan kernel: [   54.179575] IP: [] 
nfs_have_delegation+0x9/0x40 [nfs]
Apr 10 14:26:32 morgan kernel: [   54.179621] PGD 1c07067 PUD 1c08067 PM

[Kernel-packages] [Bug 1075478] Re: [HP EliteBook 8530w] Bluetooth keyboards and mice not working after suspend/resume

[Bug Watch Updater]

Launchpad has imported 15 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=811534.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2012-04-11T11:00:10+00:00 James wrote:

Created attachment 576744
Xorg.0.log from problem session

Description of problem:
After a suspend/resume cycle, X no longer recognises my Bluetooth mouse.

 - There's a confounding issue in that sometimes the Bt subsystem doesn't
   come back properly, see Bug 727106. Devices reappear after restarting
   the bluetooth service.

 - Following this, the mouse appears in the devices list in Gnome Shell,
   and other devices (e.g. file transfer from phone) works properly.

 - Upon reconnecting the mouse, messages like

 (WW) evdev: Bluetooth Mouse: device file is duplicate. Ignoring.

   appear in the Xorg logs (attached).

Sometimes waiting for a few hours and then trying again works.

I don't know if this is strictly an evdev bug. Might be udev or bluez or
kernel or ... please reassign as appropriate.

Version-Release number of selected component (if applicable):
xorg-x11-drv-evdev-2.6.99.901-7.20120118git9d9c9870c.fc16.x86_64
udev-173-3.fc16.x86_64
bluez-4.96-3.fc16.x86_64
kernel-3.3.0-8.fc16.x86_64
kernel-3.3.1-2.fc16.x86_64
kernel-3.3.1-3.fc16.x86_64
xorg-x11-server-Xorg-1.11.4-3.fc16.x86_64

How reproducible:
Intermittent, but frequent.

Steps to Reproduce:
1. Suspend then resume.
2. Restart bluetooth.service if necessary, according to Bug 727106.
3. Reconnect Bluetooth mouse.
  
Actual results:
Mouse doesn't work.

Expected results:
Mouse works.

Additional info:

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1075478/comments/0


On 2012-04-20T01:38:27+00:00 Peter wrote:

*** Bug 811681 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1075478/comments/1


On 2012-04-20T02:31:11+00:00 Peter wrote:

Either server or udev bug. The last parts of the log show that we get
the "device added" event, but we never saw the "device removed" for it.

The config_info string changes, so we don't automatically remove the
previous instance when the new one is added.

Lennart, any comments? Is there some race condition that we may suffer
from in the server that we don't see the device removed event?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1075478/comments/2


On 2012-08-27T21:29:57+00:00 Dan wrote:

Are there any workarounds known, besides restarting X?  I don't
particularly like having to shut down all programs to restart X.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1075478/comments/3


On 2012-08-27T21:49:57+00:00 Scott wrote:

(In reply to comment #2)
> Either server or udev bug. The last parts of the log show that we get the
> "device added" event, but we never saw the "device removed" for it. 
> 
> The config_info string changes, so we don't automatically remove the
> previous instance when the new one is added.
> 
> Lennart, any comments? Is there some race condition that we may suffer from
> in the server that we don't see the device removed event?

Actually it's increasingly looking like a kernel bug - we're seeing the
kernel netlink events with missing or corrupted components and also
seeing other signs that pointers aren't going where they're supposed
to...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1075478/comments/4


On 2012-08-27T22:00:09+00:00 Pierre-Yves wrote:

Dan, you might probably just unplug and re-plug the mouse

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1075478/comments/5


On 2012-08-27T22:26:09+00:00 Dan wrote:

Pierre-Yves: I have internal bluetooth so there is no possibility to
unplug anything.  However, I have tried cycling power on the mouse and
have tried running "systemctl restart bluetooth.service" without
success.  Restarting X (by logging out and back in) works though.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1075478/comments/6


On 2012-08-28T20:51:52+00:00 Andrew wrote:

Scott is referring to the debugging we've been doing on Chromium OS. We
have some more details in the bug: http://code.google.com/p/chromium-
os/issues/detail?id=33813

It's looking like a r

[Kernel-packages] [Bug 652775] Re: WARNING: at /build/buildd/linux-2.6.35/include/net/mac80211.h:2601 rate_control_send_low+0xc2/0x140 [mac80211]()

[Bug Watch Updater]

Launchpad has imported 39 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=786609.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2012-02-01T22:03:04+00:00 Mat wrote:

libreport version: 2.0.8
abrt_version:   2.0.7
cmdline:BOOT_IMAGE=/vmlinuz-3.2.2-1.fc16.x86_64 
root=/dev/mapper/vg_sd-lv_root ro rd.md=0 rd.dm=0 quiet 
SYSFONT=latarcyrheb-sun16 rhgb KEYTABLE=uk rd.luks=0 rd.lvm.lv=vg_sd/lv_swap 
rd.lvm.lv=vg_sd/lv_root LANG=en_US.UTF-8
kernel: 3.2.2-1.fc16.x86_64
reason: WARNING: at 
/builddir/build/BUILD/kernel-3.2.fc16/compat-wireless-3.3-rc1-2/include/net/mac80211.h:3618
 rate_control_send_low+0x23e/0x250 [mac80211]()
time:   Tue 31 Jan 2012 22:53:53 GMT

backtrace:
:WARNING: at 
/builddir/build/BUILD/kernel-3.2.fc16/compat-wireless-3.3-rc1-2/include/net/mac80211.h:3618
 rate_control_send_low+0x23e/0x250 [mac80211]()
:Hardware name: F3Sr
:Modules linked in: ppdev parport_pc lp parport fuse lockd ip6t_REJECT 
nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables nf_conntrack_ipv4 
nf_defrag_ipv4 xt_state nf_conntrack uvcvideo videodev media 
v4l2_compat_ioctl32 snd_hda_codec_si3054 microcode snd_hda_codec_realtek 
snd_hda_intel arc4 snd_hda_codec snd_hwdep snd_seq snd_seq_device joydev r852 
snd_pcm sm_common nand nand_ids r592 mtd memstick nand_ecc iwl3945(O) iTCO_wdt 
iwlegacy(O) iTCO_vendor_support serio_raw mac80211(O) cfg80211(O) snd_timer 
asus_laptop snd soundcore sparse_keymap rfkill snd_page_alloc atl1 
input_polldev mii uinput sunrpc firewire_ohci sdhci_pci sdhci firewire_core 
crc_itu_t mmc_core video radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core 
[last unloaded: scsi_wait_scan]
:Pid: 3167, comm: kworker/u:50 Tainted: G   O 3.2.2-1.fc16.x86_64 #1
:Call Trace:
: [] warn_slowpath_common+0x7f/0xc0
: [] warn_slowpath_null+0x1a/0x20
: [] rate_control_send_low+0x23e/0x250 [mac80211]
: [] il3945_rs_get_rate+0x42/0x4a0 [iwl3945]
: [] ? il3945_mac_tx+0x5c6/0x8e0 [iwl3945]
: [] rate_control_get_rate+0x96/0x170 [mac80211]
: [] invoke_tx_handlers+0x6ff/0x13e0 [mac80211]
: [] ? ksize+0x1c/0xc0
: [] ? sta_info_get+0x6c/0x80 [mac80211]
: [] ieee80211_tx+0x60/0xc0 [mac80211]
: [] ieee80211_xmit+0x81/0xd0 [mac80211]
: [] ieee80211_tx_skb_tid+0x5f/0x70 [mac80211]
: [] ieee80211_send_probe_req+0x4f/0x70 [mac80211]
: [] ieee80211_mgd_probe_ap_send+0xdf/0x100 [mac80211]
: [] ? mutex_lock+0x1d/0x50
: [] ieee80211_sta_work+0x90/0x150 [mac80211]
: [] ieee80211_iface_work+0x2b8/0x350 [mac80211]
: [] ? ieee80211_teardown_sdata+0xe0/0xe0 [mac80211]
: [] process_one_work+0x11d/0x470
: [] worker_thread+0x15f/0x350
: [] ? manage_workers+0x230/0x230
: [] kthread+0x8c/0xa0
: [] kernel_thread_helper+0x4/0x10
: [] ? kthread_worker_fn+0x190/0x190
: [] ? gs_change+0x13/0x13

smolt_data:
:
:
:General
:=
:UUID: 302c32f3-8bc4-4089-85f1-57b729c25b1f
:OS: Fedora release 16 (Verne)
:Default run level: Unknown
:Language: en_GB.utf8
:Platform: x86_64
:BogoMIPS: 3990.50
:CPU Vendor: GenuineIntel
:CPU Model: Intel(R) Core(TM)2 Duo CPU T7250  @ 2.00GHz
:CPU Stepping: 13
:CPU Family: 6
:CPU Model Num: 15
:Number of CPUs: 2
:CPU Speed: 2001
:System Memory: 2004
:System Swap: 4031
:Vendor: ASUSTeK Computer Inc.
:System: F3Sr 1.0
:Form factor: Notebook
:Kernel: 3.2.2-1.fc16.x86_64
:SELinux Enabled: 1
:SELinux Policy: targeted
:SELinux Enforce: Permissive
:MythTV Remote: Unknown
:MythTV Role: Unknown
:MythTV Theme: Unknown
:MythTV Plugin: 
:MythTV Tuner: -1
:
:
:Devices
:=
:(32902:17486:32902:17486) pci, None, MEMORY, Turbo Memory Controller
:(32902:10752:4163:5942) pci, None, HOST/PCI, Mobile PM965/GM965/GL960 Memory 
Controller Hub
:(32902:10753:32902:10753) pci, pcieport, PCI/PCI, Mobile PM965/GM965/GL960 PCI 
Express Root Port
:(6523:9056:4163:5942) pci, ahci, STORAGE, JMB360 AHCI Controller
:(32902:10281:4163:5942) pci, ahci, STORAGE, 82801HBM/HEM (ICH8M/ICH8M-E) SATA 
AHCI Controller
:(32902:10320:4163:5942) pci, ata_piix, STORAGE, 82801HBM/HEM (ICH8M/ICH8M-E) 
IDE Controller
:(32902:10261:4163:5942) pci, None, PCI/ISA, 82801HEM (ICH8M) LPC Interface 
Controller
:(6505:4168:4163:5349) pci, atl1, ETHERNET, L1 Gigabit Ethernet
:(32902:10289:4163:5942) pci, uhci_hcd, USB, 82801H (ICH8 Family) USB UHCI 
Controller #2
:(32902:9288:4163:5942) pci, None, PCI/PCI, 82801 Mobile PCI Bridge
:(32902:10290:4163:5942) pci, uhci_hcd, USB, 82801H (ICH8 Family) USB UHCI 
Controller #3
:(32902:10294:4163:5942) pci, ehci_hcd, USB, 82801H (ICH8 Family) USB2 EHCI 
Controller #1
:(32902:10298:4163:5942) pci, ehci_hcd, USB, 82801H (ICH8 Family) USB2 EHCI 
Controller #2
:(4480:2130:4163:5942) pci, r852, BASE, xD-Picture Card Controller
:(32902:16930:3290

[Kernel-packages] [Bug 872044] Re: Bluetooth 'Send files' returns permission denied error

[Bug Watch Updater]

Launchpad has imported 41 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=753617.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2011-11-13T19:14:17+00:00 Saurav wrote:

Description of problem:
The Bluetooth userspace utilities do not work properly on kernels newer than
2.6.38. In particular, sending files by Bluetooth from the computer to a remote
device (obex push) fails. The problem occurs on both Fedora 15 with the latest 
updates and Fedora 16. On Fedora 16, the Bluetooth adaptor is functional
only if the bluez-hid2hci package is installed.

Version-Release number of selected component (if applicable):
4.96-3

How reproducible:
On a Fedora 16 system with the bluez-hid-2hci package installed, turn on
Bluetooth and try to send a file via Bluetooth to a remote device such as a
mobile phone.

Steps to Reproduce:
1. On Fedora 16, if package bluez-hid2hci is not installed, install it.
2. Turn on Bluetooth (system adaptor).
3. Try to send a file to a remote device such as a mobile phone.
  
Actual results:
gnome-blueooth either crashes or fails to send file to remote device.

Expected results:
File gets transferred successfully.

Additional info:
There are various manifestations of this bug on different Linux distributions, 
including crashing, failing with the error message, "Connection refused" and 
failing with the error code 111.

Reply at: https://bugs.launchpad.net/gnome-
bluetooth/+bug/872044/comments/21


On 2011-11-13T19:19:11+00:00 Saurav wrote:

*** Bug 747264 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/gnome-
bluetooth/+bug/872044/comments/22


On 2011-11-18T02:21:57+00:00 Adam wrote:


-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Reply at: https://bugs.launchpad.net/gnome-
bluetooth/+bug/872044/comments/27


On 2011-11-18T05:03:17+00:00 Michael wrote:

I'm not so sure it's the kernel. I could receive files on Fedora 15 (3.0
kernel) just fine. On F16 it fails to send, receive, or browse. Pairing
works fine, but repairing doesn't fix anything. It fails with SELinux
enabled or in permissive mode.

I see this in my /var/log/messages after trying to send a file.

Nov 17 22:45:04 mcronenworth obex-client[441]: obex-client daemon 0.42
Nov 17 22:45:04 mcronenworth bluetoothd[976]: Mode session 0x7f8c953c4840 with 
:1.470 activated
Nov 17 22:45:04 mcronenworth bluetoothd[976]: bluetoothd[976]: Mode session 
0x7f8c953c4840 with :1.470 activated
Nov 17 22:45:17 mcronenworth obex-client[441]: Transfer(0xf9e630) Error: 
Unknown response
Nov 17 22:45:17 mcronenworth dbus[1100]: [system] Rejected send message, 2 
matched rules; type="method_return", sender=":1.1" (uid=0 pid=976 
comm="/usr/sbin/bluetoothd -n ") interface="(unset)" member="(unset)" error 
name="(unset)" requested_reply="0" destination=":1.470" (uid=502 pid=441 
comm="/usr/libexec/obex-client ")
Nov 17 22:45:17 mcronenworth dbus-daemon[1100]: dbus[1100]: [system] Rejected 
send message, 2 matched rules; type="method_return", sender=":1.1" (uid=0 
pid=976 comm="/usr/sbin/bluetoothd -n ") interface="(unset)" member="(unset)" 
error name="(unset)" requested_reply="0" destination=":1.470" (uid=502 pid=441 
comm="/usr/libexec/obex-client ")

Reply at: https://bugs.launchpad.net/gnome-
bluetooth/+bug/872044/comments/28


On 2011-11-18T05:49:21+00:00 Michael wrote:

Installing bluez-hid2hci does allow browsing to work, but file transfers
(to or from) do not work.

Reply at: https://bugs.launchpad.net/gnome-
bluetooth/+bug/872044/comments/29


On 2011-11-18T10:38:33+00:00 Saurav wrote:

(In reply to comment #3)
> I'm not so sure it's the kernel. I could receive files on Fedora 15 (3.0
> kernel) just fine. On F16 it fails to send, receive, or browse. Pairing works
> fine, but repairing doesn't fix anything. It fails with SELinux enabled or in
> permissive mode.
> 
> I see this in my /var/log/messages after trying to send a file.
> 
> Nov 17 22:45:04 mcronenworth obex-client[441]: obex-client daemon 0.42
> Nov 17 22:45:04 mcronenworth bluetoothd[976]: Mode session 0x7f8c953c4840 with
> :1.470 activated
> Nov 17 22:45:04 mcronenworth bluetoothd[976]: bluetoothd[976]: Mode session
> 0x7f8c953c4840 with :1.470 activated
> Nov 17 22:45:17 mcronenworth obex-client[441]: Transfer(0xf9e630) Error:
> Unknown response
> Nov 17 22:45:17 mcronenworth dbus

[Kernel-packages] [Bug 736171] Re: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame

[Bug Watch Updater]

** Changed in: fedora
   Status: Unknown => Expired

** Changed in: fedora
   Importance: Unknown => 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/736171

Title:
  168c:002a ath: Failed to stop TX DMA in 100 msec after killing last
  frame

Status in Linux:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in Fedora:
  Expired

Bug description:
  Message in dmesg:

  [   22.308381] ath: Failed to stop TX DMA in 100 msec after killing last frame
  [   22.308447] ath: Failed to stop TX DMA!
  --- 
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1670 F pulseaudio
   /dev/snd/controlC1:  caravena   1670 F pulseaudio
   /dev/snd/pcmC1D0p:   caravena   1670 F...m pulseaudio
  CRDA:
   country CL:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5735 - 5835 @ 40), (N/A, 20)
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2013-07-31 (17 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 
(20130724)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.11.0-2-generic 
root=UUID=0c67119c-ddae-476a-b510-142ec598f691 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-2-generic N/A
   linux-backports-modules-3.11.0-2-generic  N/A
   linux-firmware1.113
  Tags:  saucy
  Uname: Linux 3.11.0-2-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 940267] Re: USB keyboard and mouse can't be used after shutdown and power on

[Bug Watch Updater]

Launchpad has imported 4 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=784999.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2012-01-26T21:16:34+00:00 Andreas wrote:

Description of problem:
If I shutdown the computer finally turns off. If I turn on the computer again, 
the BIOS does not recognize my USB keyboard and mouse. As a result, no OS 
(Fedora nor Windows) is able to initialize and use the keyboard and mouse. I 
have to unplug the power chord and wait until the power supply is discharged. 
After the next power on, the mouse and keyboard functions completely ok.
I had exactly the same bug with kernel 2.6.38 on ubuntu.

Version-Release number of selected component (if applicable):
kernel
3.2.1-3.fc16.x86_64 - BUG PRESENT
3.1.9-1.fc16.x86_64 - BUG PRESENT
3.1.7-1.fc16.x86_64 - bug free!

How reproducible:
all times

Steps to Reproduce:
1. boot with kernel 3.2.1-3 or 3.1.9-1
2. login
3. shutdown the computer
4. after power down, turn on the computer

  
Actual results:
the bios does not recognize the USB keyboard and mouse. The mouse and keyboard 
can't be used.

Expected results:
mouse and keyboard must function

Additional info:
See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/786272 for more 
details. The hardware details are the same exept the graphics card.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/940267/comments/0


On 2012-02-11T20:36:24+00:00 Andreas wrote:

Linux 3.2.5-3.fc16.x86_64 has the bug, too.

If I boot 3.2.5-3 the logon screen finally appears. But the keyboard and
mouse do not function. If I press a key in this state, the three leds
num lock, caps lock and scroll lock will be turned on for approx. 0.5sec
once or two times.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/940267/comments/1


On 2012-10-23T15:37:36+00:00 Dave wrote:

# Mass update to all open bugs.

Kernel 3.6.2-1.fc16 has just been pushed to updates.
This update is a significant rebase from the previous version.

Please retest with this kernel, and let us know if your problem has been
fixed.

In the event that you have upgraded to a newer release and the bug you reported
is still present, please change the version field to the newest release you have
encountered the issue with.  Before doing so, please ensure you are testing the
latest kernel update in that release and attach any new and relevant information
you may have gathered.

If you are not the original bug reporter and you still experience this bug,
please file a new report, as it is possible that you may be seeing a
different problem. 
(Please don't clone this bug, a fresh bug referencing this bug in the comment 
is sufficient).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/940267/comments/5


On 2012-11-14T16:22:47+00:00 Justin wrote:

With no response, we are closing this bug under the assumption that it
is no longer an issue. If you still experience this bug, please feel
free to reopen the bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/940267/comments/6


** Changed in: linux (Fedora)
   Status: Unknown => Expired

** Changed in: linux (Fedora)
   Importance: Unknown => 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/940267

Title:
  USB keyboard and mouse can't be used after shutdown and power on

Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Fedora:
  Expired

Bug description:
  I initially reported this bug in Ubuntu 11.04
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/786272). Maybe
  somebody can reactivate bug #786272...

  ---

  If I shutdown 11.10 the computer finally turns off. But the mouse
  light sometimes remains lit. If I turn on the computer again, the BIOS
  does not recognize my USB keyboard and mouse. I saw that the three
  LEDs on the keyboard were blinking.

  As a result, no OS is able to initialize and use the keyboard and
  mouse. I have to unplug the power chord and wait until the power
  supply is discharged or unplug the keyboard and mouse. Then the mouse
  and keyboard functions completely ok.

  This bug also exists in Fedora 16 >3.1.7 kernels. 3.1.7 worked well
  for me.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image-3.0.0-16-generic 3.0.0-16.28
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic x86_64
  NonfreeKernelModules: fglr

[Kernel-packages] [Bug 935778] Re: Toshiba Tecra R840 - brightness controls work on first boot, but do nothing after suspend/resume

[Bug Watch Updater]

Launchpad has imported 5 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=755768.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2011-11-22T01:19:02+00:00 Jim wrote:

Description of problem:
Screen cannot be brightened or dimmed after suspend.

Version-Release number of selected component (if applicable):
?

How reproducible:
Suspend, then resume. After resume, neither function buttons nor screen setting 
in gnome will allow screen brightness to be changed.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Computer: Toshiba Portege Z830

Specifics:
[jim@toshiba ~]$ uname -r
3.1.1-2.fc16.i686
[jim@toshiba ~]$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller (rev 09)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/comments/4


On 2012-09-13T06:18:52+00:00 Tom wrote:

Hi

I can second that!

Got the same model and same issue.

In case Fedora-crew need some system output, let me know.

Thanks!

Tom

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/comments/61


On 2012-09-13T06:21:51+00:00 Tom wrote:

Hmm

I can see I were a bit too fast - I use an up-to-date Fedora 17.
Got the latest Intel graphics drivers 2.20.7-1.fc17 32bit.

Cheers!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/comments/62


On 2013-01-16T13:43:51+00:00 Fedora wrote:

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/comments/69


On 2013-02-13T14:37:26+00:00 Fedora wrote:

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/comments/70


** Changed in: fedora
   Status: Unknown => Won't Fix

** Changed in: fedora
   Importance: Unknown => Undecided

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

Title:
  Toshiba Tecra R840 - brightness controls work on first boot, but do
  nothing after suspend/resume

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in Debian:
  Confirmed
Status in Fedora:
  Won't Fix
Status in openSUSE:
  Won't Fix

Bug description:
  Overview -

  This bug affects many Toshiba laptops including R700, R705, R800,
  R830, R835, R840, R850, Z930 models - please update this description
  if your model is also affected, but make sure the symptoms match
  exactly.

  The symptoms are that brightness control operates normally when the
  system is first booted, but after a suspend-to-RAM and resume cycle
  the brightness controls have no effect.

  After a normal reboot, or hibernate & resume cycle, the brightness
  controls ope

[Kernel-packages] [Bug 925760] Re: Constant warnings from the kernel: Test WP failed, assume Write Enabled

[Bug Watch Updater]

Launchpad has imported 46 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=769747.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2011-12-22T03:41:38+00:00 Ralf wrote:

Description of problem:

Since having upgraded to F16 from F14, I am drowning in messages similar
to the one below on the console (corrupting any console output)

[ 1400.353433] sd 4:0:0:0: [sdb] Asking for cache data failed
[ 1400.356601] sd 4:0:0:0: [sdb] Assuming drive cache: write through

accompanied by a message similar to the one in /var/log/messages
(gradually filling it up)

[ 1400.351374] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 1400.353433] sd 4:0:0:0: [sdb] Asking for cache data failed
[ 1400.356601] sd 4:0:0:0: [sdb] Assuming drive cache: write through 


This machine (a netbook) only has one hard disk. sdb seems to refer to the 
builtin usb card reader.

Version-Release number of selected component (if applicable):
kernel-PAE-3.1.5-6.fc16.i686

How reproducible:
100%


Expected results:
The kernel not to raise these warnings/errors, but to work flawlessly (Older 
kernels did).

I am inclined to believe the kernel is not handling this sdb device
properly.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925760/comments/0


On 2011-12-22T04:02:41+00:00 Dave wrote:

please attach the dmesg output from a fresh boot.
need to see exactly which device we're working with here.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925760/comments/1


On 2011-12-22T04:21:51+00:00 Ralf wrote:

Created attachment 549125
dmesg of the system exposing this issue

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925760/comments/2


On 2011-12-22T16:07:24+00:00 Dave wrote:

reported to upstream maintainer. thanks.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925760/comments/3


On 2011-12-22T17:27:01+00:00 Ralf wrote:

(In reply to comment #3)
> reported to upstream maintainer. thanks.
Welcome.

Any upstream BZ/PR? Any patch proposals, workarounds to try?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925760/comments/4


On 2011-12-27T21:04:55+00:00 Joe wrote:

I've been getting the same messages during boot on my laptop ever since
"upgrading" from F14 to F16 and the boot process hangs right there.  The
only way I can use my laptop is to boot with the last 2.X kernel from
F14, which works fine.  No matter what 3.X kernel I try, this happens.
My laptop only has one internal HDD, and I never have a CD or flash
drive mounted during boot if that helps.  If there's a way for me to get
some data about a failed boot, please let me know and I'll do what's
needed.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925760/comments/5


On 2012-01-30T22:52:38+00:00 Joe wrote:

More info.  Ever since the "upgrade," the CD/DVD on my laptop has been
unusable.  If I into a 3.x kernel with it empty, I get the endless [sdb]
errors and putting a known-good CD in the drive first doesn't change
anything.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925760/comments/6


On 2012-02-28T14:57:21+00:00 Mark wrote:

I'm seeing this also on a laptop with builtin card reader. Every 50
seconds or so:

kernel: [  312.932881] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
kernel: [  312.935878] sd 6:0:0:0: [sdb] Asking for cache data failed
kernel: [  312.935888] sd 6:0:0:0: [sdb] Assuming drive cache: write through

But if I remove the plastic fake SD card which fits in the slot to
prevent dust, etc:

kernel: [  317.199029] usb 2-1.6: USB disconnect, device number 4

Then the kernel messages stop. On reinsertion of the fake card:

kernel: [  556.312591] usb 2-1.6: New USB device found, idVendor=0bda, 
idProduct=0138
kernel: [  556.312601] usb 2-1.6: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
kernel: [  556.312608] usb 2-1.6: Product: USB2.0-CRW
kernel: [  556.312612] usb 2-1.6: Manufacturer: Generic
kernel: [  556.312616] usb 2-1.6: SerialNumber: 2009051638820
kernel: [  556.494090] scsi7 : usb-storage 2-1.6:1.0
mtp-probe: checking bus 2, device 5: 
"/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.6"
mtp-probe: bus: 2, device: 5 was not an MTP device
kernel

[Kernel-packages] [Bug 1007901] Re: driver crash radeon_gart.c:187 radeon_gart_bind+0x1b4/0x1c0

[Bug Watch Updater]

** Changed in: fedora
   Status: Unknown => Fix Released

** Changed in: fedora
   Importance: Unknown => Undecided

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

Title:
  driver crash radeon_gart.c:187 radeon_gart_bind+0x1b4/0x1c0

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in Fedora:
  Fix Released

Bug description:
  Linux  3.2.0-24-generic #39-Ubuntu SMP Mon May 21 16:52:17 UTC 2012 x86_64 
x86_64 x86_64 GNU/Linux
  Linux Mint 13 maya
  MATE x64

  
  I have upgraded my Linux Mint system from previous kernel version 3.2.0-23 
and after reboot I get error on screen may be thousands of times:

  Failed to allocate:
  size: 4096000 bytes
  aligment: 0 bytes
  domains:  2

  and in dmesg is this:

  WARNING: at 
/build/buildd/linux-3.2.0/drivers/gpu/drm/radeon/radeon_gart.c:187 
radeon_gart_bind+0x1b4/0x1c0 [radeon]()
  [   23.157299] Hardware name: AMILO Pa 2510
  [   23.157301] trying to bind memory to uninitialized GART !
  [   23.157303] Modules linked in: rfcomm bnep bluetooth parport_pc ppdev 
binfmt_misc nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc ext2 ip6t_LOG 
xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT ipt_LOG xt_limit 
xt_tcpudp xt_addrtype snd_hda_codec_realtek snd_hda_codec_si3054 xt_state arc4 
snd_hda_intel snd_hda_codec ip6table_filter snd_hwdep ip6_tables snd_pcm 
snd_seq_midi nf_conntrack_netbios_ns nf_conntrack_broadcast snd_rawmidi 
nf_nat_ftp nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 ath5k snd_seq_midi_event 
nf_conntrack_ftp nf_conntrack iptable_filter ip_tables snd_seq x_tables ath 
radeon snd_timer mac80211 snd_seq_device joydev snd psmouse soundcore 
sp5100_tco serio_raw ttm snd_page_alloc cfg80211 video i2c_piix4 k8temp 
drm_kms_helper edac_core edac_mce_amd mac_hid drm i2c_algo_bit shpchp lp 
parport usbhid hid pata_atiixp r8169 usb_storage
  [   23.157372] Pid: 284, comm: plymouthd Tainted: GW
3.2.0-24-generic #39-Ubuntu
  [   23.157375] Call Trace:
  [   23.157388]  [] warn_slowpath_common+0x7f/0xc0
  [   23.157392]  [] warn_slowpath_fmt+0x46/0x50
  [   23.157412]  [] ? ttm_mem_global_alloc_page+0x42/0x50 
[ttm]
  [   23.157433]  [] radeon_gart_bind+0x1b4/0x1c0 [radeon]
  [   23.157453]  [] radeon_ttm_backend_bind+0x35/0xb0 
[radeon]
  [   23.157464]  [] ttm_tt_bind+0x50/0x80 [ttm]
  [   23.157473]  [] ttm_bo_handle_move_mem+0x347/0x3c0 [ttm]
  [   23.157482]  [] ttm_bo_move_buffer+0x13a/0x150 [ttm]
  [   23.157524]  [] ? drm_mm_kmalloc+0x3c/0xe0 [drm]
  [   23.157529]  [] ? alloc_file+0x9c/0xd0
  [   23.157539]  [] ttm_bo_validate+0xe7/0xf0 [ttm]
  [   23.157547]  [] ttm_bo_init+0x1b8/0x260 [ttm]
  [   23.157569]  [] radeon_bo_create+0x176/0x2a0 [radeon]
  [   23.157590]  [] ? 
radeon_create_ttm_backend_entry+0x40/0x40 [radeon]
  [   23.157614]  [] radeon_gem_object_create+0x5a/0x100 
[radeon]
  [   23.157637]  [] radeon_gem_create_ioctl+0x58/0xd0 
[radeon]
  [   23.157643]  [] ? security_capable+0x21/0x30
  [   23.157657]  [] drm_ioctl+0x444/0x510 [drm]
  [   23.157682]  [] ? radeon_gem_pwrite_ioctl+0x30/0x30 
[radeon]
  [   23.157688]  [] ? default_spin_lock_flags+0x9/0x10
  [   23.157693]  [] ? ep_poll+0x1cc/0x380
  [   23.157698]  [] do_vfs_ioctl+0x8a/0x340
  [   23.157702]  [] ? vfs_write+0x110/0x180
  [   23.157706]  [] sys_ioctl+0x91/0xa0
  [   23.157710]  [] ? sys_epoll_wait+0x8e/0xe0
  [   23.157716]  [] system_call_fastpath+0x16/0x1b
  [   23.157719] ---[ end trace 406cb566ecd48e27 ]---
  [   23.157724] [drm:radeon_ttm_backend_bind] *ERROR* failed to bind 1000 
pages at 0x
  [   23.163030] radeon :01:05.0: object_init failed for (4096000, 
0x0002)
  [   23.168037] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM 
object (4096000, 2, 4096, -22)

  So it seems to be a problem with driver for ATI in new kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linuxmint/+bug/1007901/+subscriptions

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

[Kernel-packages] [Bug 1034740] Re: 8086:4238 [Lenovo ThinkPad X201] iwlwifi drops connection when using 802.11n

[Bug Watch Updater]

** Changed in: fedora
   Status: Unknown => Fix Released

** Changed in: fedora
   Importance: Unknown => 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/1034740

Title:
  8086:4238 [Lenovo ThinkPad X201] iwlwifi drops connection when using
  802.11n

Status in Linux:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Debian:
  New
Status in Fedora:
  Fix Released

Bug description:
  Symptoms: After a few minutes, the WiFi connection to my home router
  first becomes slow (packet loss), then entirely unusable. NetWork
  manager still shows the connection as up and working.

  dmesg shows messages like these:
  Aug  9 06:17:16 thinkpad kernel: [ 5026.531127] iwlwifi :02:00.0: Tx 
aggrega
  tion enabled on ra = b0:48:7a:d6:91:50 tid = 6

  WORKAROUND: rfkill to disable and enable WiFi, or add:
  options iwlwifi 11n_disable=1

  to /etc/modprobe.d/iwlwifi.conf

  However, this means that all my network connections will only run in 
802.11a/g mode, which is undesirably slow. Other people using MacOS in my place 
don't observe any issues, so I can rule out the router(s) as the culprits.
  Hardware: 02:00.0 Network controller: Intel Corporation Centrino Ultimate-N 
6300 (rev 35)
  Routers: TP-Link WR1043ND, WR2543ND using OpenWRT trunk.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-27-generic 3.2.0-27.43
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
  Uname: Linux 3.2.0-27-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC29: alex   2261 F xfce4-volumed
   /dev/snd/controlC0:  alex   2250 F pulseaudio
    alex   2261 F xfce4-volumed
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf252 irq 44'
     Mixer name : 'Intel IbexPeak HDMI'
     Components : 'HDA:14f15069,17aa2155,00100302 
HDA:80862804,17aa21b5,0010'
     Controls  : 14
     Simple ctrls  : 6
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
6QHT33WW-1.14'
     Mixer name : 'ThinkPad EC 6QHT33WW-1.14'
     Components : ''
     Controls  : 1
     Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
     Capabilities: pswitch pswitch-joined penum
     Playback channels: Mono
     Mono: Playback [on]
  Date: Thu Aug  9 12:24:19 2012
  HibernationDevice: RESUME=UUID=9fee4cfb-53b9-43d7-8425-1666aff145c4
  InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: LENOVO 3626A14
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-27-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-27-generic N/A
   linux-backports-modules-3.2.0-27-generic  N/A
   linux-firmware1.79
  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET69WW (1.39 )
  dmi.board.name: 3626A14
  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:bvr6QET69WW(1.39):bd04/26/2012:svnLENOVO:pn3626A14:pvrThinkPadX201:rvnLENOVO:rn3626A14:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3626A14
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1240143] Re: NFS client reports a 'readdir loop' with a corrupt name

[Bug Watch Updater]

** Changed in: linux (Fedora)
   Status: Unknown => Invalid

** Changed in: linux (Fedora)
   Importance: Unknown => 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/1240143

Title:
  NFS client reports a 'readdir loop' with a corrupt name

Status in linux package in Ubuntu:
  Fix Released
Status in linux package in Debian:
  Fix Released
Status in linux package in Fedora:
  Invalid

Bug description:
  We have an NFS server running on a RedHat system. One particular
  directory contains many, many RPMs (96850). It reports that there is a
  'readdir loop',  and the loop in question contains corrupted names. I
  assume the name corruption is happening on the Linux kernel end, not
  the server end:

  "NFS: directory Development/rpms contains a readdir loop.Please contact your 
server vendor.  The file: foo-bar-11.0flange-12345.AB5.x86_64.rpmmpmpmmT53 has 
duplicate cookie 1110018804"
  "NFS: directory Development/rpms contains a readdir loop.Please contact your 
server vendor.  The file: 
widget-wiggle-11.0-12356.AB5.x86_64.rpmpm.AB5.x86_64.rpm\xm has 
duplicate cookie 353422206"

  Since the corrupted names are never displayed in an 'ls' of the
  directory (even whilst the problem is occurring), I assume that this
  is a presentation problem in the warning message.

  Unfortunately the problem had gone away by the time I tried using
  tcpdump to capture the on-the-wire data.

  jfletcher@gromit:~$ cat /proc/version
  Linux version 3.2.0-29-generic (buildd@allspice) (gcc version 4.6.3 
(Ubuntu/Linaro 4.6.3-1ubuntu5) ) #46-Ubuntu SMP Fri Jul 27 17:03:23 UTC 2012
  jfletcher@gromit:~$ lsb_release -rd
  Description:  Ubuntu 12.04.3 LTS
  Release:  12.04

  
  The lspci information would not be useful - the system was running under KVM, 
with a single interface.

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

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

[Kernel-packages] [Bug 435190] Re: Disk wakes up every 30 minutes and produces errors on dmesg

[Bug Watch Updater]

Launchpad has imported 38 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=491552.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-03-22T22:53:45+00:00 Mace wrote:

Created attachment 336227
"sysctl -w vm.block_dump=1" activity for sdb

Description of problem:

I have an internal SATA drive (sdb) that I only use for backups; it is
otherwise unmounted.  I have it set to spin down when idle.

Recently, I noticed taht the drive is not spinning down.  I checked to
see what was accessing it using "sysctl -w vm.block_dump=1" (see the
attached who-io.log).  It appeared to be devkit-disks-part-id.

I ran "devkit-disks --monitor-detail" (see attached devkit.log), and it
appears that deviceKit is polling smart data, which keeps the drive from
spinning down.

The device is not removable, and it's not in the list of polled drives:

# ps -Afl | grep devkit-disks-daemon | grep -v grep
4 S root  4326 1  0  80   0 - 0 poll_s 17:23 ?00:00:02 
/usr/libexec/devkit-disks-daemon
1 S root  4382  4326  0  80   0 - 0 poll_s 17:23 ?00:00:03 
devkit-disks-daemon: polling /dev/sdg /dev/sdf /dev/sr0 /dev/sde /dev/sr1 
/dev/sdd

Version-Release number of selected component (if applicable):

DeviceKit-disks-003-7.fc11.x86_64
DeviceKit-003-1.x86_64
DeviceKit-power-006-3.fc11.x86_64

How reproducible:

Always

Steps to Reproduce:
1.Unmount a drive
2.Set the spin down time
3.Watch nothing happen
  
Actual results:

Drives stay spun up, even when unmounted

Expected results:

Drives should spin down

Additional info:

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/435190/comments/0


On 2009-03-22T22:55:00+00:00 Mace wrote:

Created attachment 336228
devkit-disks --monitor-detail

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/435190/comments/1


On 2009-03-24T21:22:12+00:00 Eric wrote:

Mace, feel free to add it to the tracker bug if you like; it's a
slightly different issue, but the same net result, sounds like.

-Eric

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/435190/comments/2


On 2009-03-24T21:30:16+00:00 David wrote:

FWIW, this is fixed with the smartmontools->libatasmart port that I
committed upstream yesterday. I'll keep this bug open until it's in
Rawhide.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/435190/comments/3


On 2009-03-25T00:31:19+00:00 Mace wrote:

(In reply to comment #3)
> FWIW, this is fixed with the smartmontools->libatasmart port that I committed
> upstream yesterday. I'll keep this bug open until it's in Rawhide.  

I don't have libatasmart installed; how does it relate to the issue?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/435190/comments/4


On 2009-03-25T16:52:28+00:00 David wrote:

(In reply to comment #4)
> (In reply to comment #3)
> > FWIW, this is fixed with the smartmontools->libatasmart port that I 
> > committed
> > upstream yesterday. I'll keep this bug open until it's in Rawhide.  
> 
> I don't have libatasmart installed; how does it relate to the issue?  

As I said this is fixed upstream but the fix is not in Rawhide yet. Once
the next version hits Rawhide libatasmart will be pulled in and then a
drive will not be spun up for checking ATA SMART if the drive are
sleeping.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/435190/comments/5


On 2009-04-07T04:43:04+00:00 Matthias wrote:

Should be fixed in DeviceKit-disks-004

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/435190/comments/6


On 2009-04-07T05:17:41+00:00 Mace wrote:

Created attachment 338456
devkit-disks monitor output

I updated to DeviceKit-disks-004 from Koji, rebooted, and still see the
same issue.  Sdb is unmounted, has 'hdparm -S2' set, but will not spin
down.  The 'devkit-disks --monitor-detail' still shows /dev/sdb being
polled.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/435190/comments/7


On 2009-04-07T16:19:32+00:00 David wrote:

Interesting. Please try to boot into runlevel 3 (to avoid the desktop
starting devkit-disks-daemon), ensure that devkit-disk

[Kernel-packages] [Bug 177076] Re: acpi-cpufreq doesn't allow >800Mhz on Fujistu T4220

[Bug Watch Updater]

Launchpad has imported 23 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=403651.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2007-11-28T23:47:15+00:00 Ryan wrote:

>From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.9) Gecko/20071105 
Fedora/2.0.0.9-1.fc9 Firefox/2.0.0.9

Description of problem:
On my Santa Rosa based Fujitsu T4220 notebook the CPU frequency is permanently 
stuck at 800MHz (actual max is 2GHz) no matter what the load. This occurs no 
matter which governor is selected (userspace, ondemand, performance etc..).

On resume from suspend to ram, the frequency fluctuates between 800MHz
and 1.6GHz for approx. a minute, and then goes back to being stuck at
800MHz.

Version-Release number of selected component (if applicable):
kernel-2.6.24-0.42.rc3.git1.fc9

How reproducible:
Always


Steps to Reproduce:
1. boot into fedora
2. check /cat/proc/cpuinfo ( will be 800MHz )
3. run something cpu intensive
3. check cpuinfo (still stuck at 800MHz)

Actual Results:
The CPU frequency doesn't change

Expected Results:
The frequency should increase to max if needed and go back to min when not.

Additional info:

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/177076/comments/0


On 2007-11-28T23:48:38+00:00 Ryan wrote:

Created attachment 271951
lspci -vv output

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/177076/comments/1


On 2007-11-28T23:49:31+00:00 Ryan wrote:

Created attachment 271961
lspci -vvn output

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/177076/comments/2


On 2007-11-28T23:50:05+00:00 Ryan wrote:

Created attachment 271971
dmidecode output

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/177076/comments/3


On 2007-11-28T23:57:42+00:00 Ryan wrote:

[ryan@tablet ~]$ ls /sys/devices/system/cpu/cpu0/cpufreq/
affected_cpus scaling_available_frequencies  scaling_governor
cpuinfo_cur_freq  scaling_available_governorsscaling_max_freq
cpuinfo_max_freq  scaling_cur_freq   scaling_min_freq
cpuinfo_min_freq  scaling_driver scaling_setspeed

[root@tablet ryan]# cat /sys/devices/system/cpu/cpu0/cpufreq/*
0 1
80
2001000
80
2001000 200 160 120 80 
userspace performance 
80
acpi-cpufreq
performance
80
80

Also, I am not sure how relevant this is, but
/proc/acpi/processor/CPU0/throttling outputs "".

I have the same problems on every linux distro I have tried on this
laptop

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/177076/comments/4


On 2007-12-01T00:48:49+00:00 Ryan wrote:

Created attachment 274581
dmesg output

Here's my dmesg

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/177076/comments/5


On 2007-12-10T20:54:09+00:00 Jaakko wrote:

On updated Fedora 8, on Dell Inspiron 9300 laptop, I have the same problem. 
Frequency policy is stuck at 800 MHz.  Scaling worked in the past on some
earlier FC, not sure if I paid attention so much on FC7.

# cpufreq-info 
cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to li...@brodo.de, please.
analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which need to switch frequency at the same time: 0
  hardware limits: 800 MHz - 1.73 GHz
  available frequency steps: 1.73 GHz, 1.33 GHz, 1.07 GHz, 800 MHz
  available cpufreq governors: ondemand, userspace, performance
  current policy: frequency should be within 800 MHz and 800 MHz.
  The governor "ondemand" may decide which speed to use
  within this range.
  current CPU frequency is 800 MHz.

# cat /proc/cpuinfo
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 13
model name  : Intel(R) Pentium(R) M processor 1.73GHz
stepping: 8
cpu MHz : 800.000
cache size  : 2048 KB
fdiv_bug: no
hlt_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 2
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat
clflush dts acpi mmx fxsr sse sse2 ss tm pbe nx up bts est tm2
bogomips: 1597.42
clflush size: 64

# cat /proc/acpi/processor/CPU0/throttling 
state count:

[Kernel-packages] [Bug 602049] Re: Suspend to RAM fails due to tpm_tis kernel module (regression)

[Bug Watch Updater]

** Changed in: linux (Fedora)
   Status: Unknown => Fix Released

** Changed in: linux (Fedora)
   Importance: Unknown => 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/602049

Title:
  Suspend to RAM fails due to tpm_tis kernel module (regression)

Status in Linux:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Fedora:
  Fix Released

Bug description:
  Suspend reliably fails with this kernel version, which I think came
  through on proposed a few days ago.  The computer appears to go
  through the normal steps but doesn't power down.  Hard power-off is
  required - there is no automatic recovery of the failed suspend.

  According to the developers, tpm_tis is supposed to work with all 1.2
  TPMs, complying with the TIS specification (that determines how the
  1.2 TPMs should interface with PC platforms), so it looks like a bug
  in this kernel module.

  The tpm developers are aware of this bug, so further investigation
  should be discussed here, on the tpmdd-devel mailing list and the
  kernel mailing list.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: linux-image-2.6.32-23-generic 2.6.32-23.37
  Regression: Yes
  Reproducible: Yes
  ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-23-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mdoube 2533 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfc50 irq 21'
     Mixer name : 'SigmaTel STAC9872AK'
     Components : 'HDA:83847662,104d1e00,00100201 
HDA:14f12c06,104d1700,0010'
     Controls  : 11
     Simple ctrls  : 7
  Date: Mon Jul  5 22:38:17 2010
  HibernationDevice: RESUME=UUID=a017c7e4-4a29-4ba1-bfea-52cd609781d8
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100412)
  MachineType: Sony Corporation VGN-SZ650N
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-23-generic 
root=UUID=31cf7381-5708-4104-8d9e-a2eaaec7cbe7 ro quiet splash
  ProcEnviron:
   LANG=en_GB.utf8
   SHELL=/bin/bash
  RelatedPackageVersions: linux-firmware 1.34.1
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  dmi.bios.date: 04/04/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R0122S5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR0122S5:bd04/04/2008:svnSonyCorporation:pnVGN-SZ650N:pvrJ002UR2M:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VGN-SZ650N
  dmi.product.version: J002UR2M
  dmi.sys.vendor: Sony Corporation
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mdoube 2541 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfc50 irq 21'
     Mixer name : 'SigmaTel STAC9872AK'
     Components : 'HDA:83847662,104d1e00,00100201 
HDA:14f12c06,104d1700,0010'
     Controls  : 11
     Simple ctrls  : 7
  DistroRelease: Ubuntu 10.04
  HibernationDevice: RESUME=UUID=a017c7e4-4a29-4ba1-bfea-52cd609781d8
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100412)
  MachineType: Sony Corporation VGN-SZ650N
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-24-generic 
root=UUID=31cf7381-5708-4104-8d9e-a2eaaec7cbe7 ro quiet splash
  ProcEnviron:
   LANG=en_GB.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu

[Kernel-packages] [Bug 515246] Re: Intel 915GM/GMS/910GML: blank screen after booting 2.6.32

[Bug Watch Updater]

Launchpad has imported 5 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=545323.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-12-08T07:18:49+00:00 Michael wrote:

User-Agent:   Mozilla/5.0 (Windows; U; Windows NT 5.1; de;
rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 (.NET CLR 3.5.30729)

Booting up kernel 2.6.31.6-162.fc12.i686.PAE on my ASRock A330GC
mainboard with Intel Dual-Core Atom processor A330 and Intel 945GC +
ICH7 chipset with no monitor plugged in (a server does not need a
monitor) I get this waring in dmesg output:

i915 :00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
i915 :00:02.0: setting latency timer to 64
[ cut here ]
WARNING: at drivers/gpu/drm/drm_crtc_helper.c:1032 
drm_helper_initial_config+0x3b/0x57 [drm_kms_helper]() (Not tainted)
Hardware name: To Be Filled By O.E.M.
No connectors reported connected with modes
Modules linked in: i915(+) drm_kms_helper usb_storage drm i2c_algo_bit i2c_core 
video output
Pid: 110, comm: modprobe Not tainted 2.6.31.6-162.fc12.i686.PAE #1
Call Trace:
 [] warn_slowpath_common+0x70/0x87
 [] ? drm_helper_initial_config+0x3b/0x57 [drm_kms_helper]
 [] warn_slowpath_fmt+0x29/0x2c
 [] drm_helper_initial_config+0x3b/0x57 [drm_kms_helper]
 [] i915_driver_load+0xb1b/0xba1 [i915]
 [] drm_get_dev+0x2da/0x3b1 [drm]
 [] i915_pci_probe+0x12/0x98 [i915]
 [] local_pci_probe+0x13/0x15
 [] pci_device_probe+0x48/0x6b
 [] driver_probe_device+0xbc/0x1b8
 [] __driver_attach+0x48/0x64
 [] bus_for_each_dev+0x42/0x6c
 [] driver_attach+0x19/0x1b
 [] ? __driver_attach+0x0/0x64
 [] bus_add_driver+0xd0/0x211
 [] ? kset_find_obj+0x23/0x4f
 [] driver_register+0x7e/0xe5
 [] __pci_register_driver+0x3d/0x9a
 [] drm_init+0x62/0xba [drm]
 [] ? i915_init+0x0/0x48 [i915]
 [] i915_init+0x46/0x48 [i915]
 [] do_one_initcall+0x51/0x13f
 [] sys_init_module+0xac/0x1bd
 [] sysenter_do_call+0x12/0x28
---[ end trace 9cf3ad6febedbb1c ]---
[drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0


Reproducible: Always

Steps to Reproduce:
1. Reboot system
2. look at dmesg output

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/515246/comments/0


On 2009-12-12T15:58:38+00:00 George wrote:

Confirmed on like system:

MSI Wind Nettop 100 (Intel Atom 330)

2.6.31.6-166.fc12.x86_64

[ cut here ]
WARNING: at drivers/gpu/drm/drm_crtc_helper.c:1032 
drm_helper_initial_config+0x46/0x61 [drm_kms_helper]() (Not tainted)
Hardware name: MS-7418
No connectors reported connected with modes
Modules linked in: i915(+) drm_kms_helper drm i2c_algo_bit i2c_core video output
Pid: 140, comm: work_for_cpu Not tainted 2.6.31.6-166.fc12.x86_64 #1
Call Trace:
 [] warn_slowpath_common+0x84/0x9c
 [] warn_slowpath_fmt+0x41/0x43
 [] drm_helper_initial_config+0x46/0x61 [drm_kms_helper]
 [] i915_driver_load+0xb1b/0xba8 [i915]
 [] drm_get_dev+0x36e/0x46f [drm]
 [] ? do_work_for_cpu+0x0/0x2a
 [] i915_pci_probe+0x15/0xd5 [i915]
 [] local_pci_probe+0x17/0x1b
 [] do_work_for_cpu+0x18/0x2a
 [] kthread+0x91/0x99
 [] child_rip+0xa/0x20
 [] ? kthread+0x0/0x99
 [] ? child_rip+0x0/0x20
---[ end trace afac59a7c55e7a6d ]---

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/515246/comments/1


On 2010-02-11T11:33:31+00:00 Nerijus wrote:

2.6.31.12-174.2.3.fc12.i686:

[drm] Initialized drm 1.1.0 20060810
i915 :00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
mtrr: type mismatch for e000,1000 old: write-back new: write-combining
[drm] MTRR allocation failed.  Graphics performance may suffer.
[ cut here ]
WARNING: at drivers/gpu/drm/drm_crtc_helper.c:1032 
drm_helper_initial_config+0x3b/0x57 [drm_kms_helper]() (Not tainted)
Hardware name: X7SLA
No connectors reported connected with modes
Modules linked in: i915(+) drm_kms_helper drm i2c_algo_bit i2c_core video output
Pid: 111, comm: modprobe Not tainted 2.6.31.12-174.2.3.fc12.i686 #1
Call Trace:
[] warn_slowpath_common+0x70/0x87
[] ? drm_helper_initial_config+0x3b/0x57 [drm_kms_helper]
[] warn_slowpath_fmt+0x29/0x2c
[] drm_helper_initial_config+0x3b/0x57 [drm_kms_helper]
[] i915_driver_load+0xacb/0xb51 [i915]
[] drm_get_dev+0x2da/0x3b1 [drm]
[] i915_pci_probe+0x12/0x9e [i915]
[] local_pci_probe+0x13/0x15
[] pci_device_probe+0x48/0x6b
[] driver_probe_device+0xbc/0x1b8
[] __driver_attach+0x48/0x64
[] bus_for_each_dev+0x42/0x6c
[] driver_attach+0x19/0x1b
[] ? __driver_attach+0x0/0x64
[] bus_add_driver+0xd0/0x211
[] ? kset_find_obj+0x23/0x4f
[] driver_register+0x7e/0xe5
[] __pci_register_driver+0x3d/0x9a
[] drm_init+0x62/0xba [drm]
[] ? i915_in

[Kernel-packages] [Bug 608907] Re: [i915] Lenovo U160 Intel i7 620UM blank screen

[Bug Watch Updater]

Launchpad has imported 22 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=596557.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2010-05-26T23:48:07+00:00 Adam wrote:

I have here a Sony Vaio Z laptop. It's a fairly new model with
switchable graphics: it has both a GeForce and an Intel integrated
graphics chipset.

I can configure the BIOS so I can enable only one card during any given
boot, using the selector switch on the laptop. At this point it ought to
be just like dealing with a single adapter for the OS, so we should be
able to cope with driving either adapter using nouveau or intel
(respectively). In fact, neither work. Here's the report for the intel
adapter.

As soon as i915 gets loaded with KMS enabled, the screen goes blank
(with the backlight on). If I load i915 without KMS, it succeeds, but
obviously this is no use for actually running X now the UMS support is
gone from the X driver.

I will attach relevant sections from /var/log/messages , and the lspci
-nn output. Xorg.0.log doesn't seem useful in this case as the failure
is earlier.

Chip is: 00:02.0 VGA compatible controller [0300]: Intel Corporation
Core Processor Integrated Graphics Controller [8086:0046] (rev 02)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/608907/comments/0


On 2010-05-26T23:49:00+00:00 Adam wrote:

Created attachment 417065
lspci output on the affected system

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/608907/comments/1


On 2010-05-26T23:54:02+00:00 Adam wrote:

By the looks of the logs, the following appears in /var/log/messages
when loading i915 *without* KMS:

May 26 16:39:05 vaioz kernel: [drm] Initialized drm 1.1.0 20060810
May 26 16:39:05 vaioz kernel: pci :00:02.0: power state changed by ACPI to 
D0
May 26 16:39:05 vaioz kernel: pci :00:02.0: power state changed by ACPI to 
D0
May 26 16:39:05 vaioz kernel: pci :00:02.0: PCI INT A -> GSI 16 (level, 
low) -> IRQ 16
May 26 16:39:05 vaioz kernel: mtrr: no more MTRRs available
May 26 16:39:05 vaioz kernel: [drm] MTRR allocation failed.  Graphics 
performance may suffer.
May 26 16:39:05 vaioz kernel: acpi device:00: registered as cooling_device4
May 26 16:39:05 vaioz kernel: input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input7
May 26 16:39:05 vaioz kernel: ACPI: Video Device [GFX0] (multi-head: yes  rom: 
no  post: no)
May 26 16:39:05 vaioz kernel: [drm] Initialized i915 1.6.0 20080730 for 
:00:02.0 on minor 0
May 26 16:39:05 vaioz kernel: modprobe used greatest stack depth: 3176 bytes 
left

when loading i915 *with* KMS, nothing at all appears in the logs.
There's nothing in /var/log/messages between where boot is complete, and
when the next boot starts up. I will attach the entire /var/log/messages
. Here's my timing notes. All refer to today, May 26th:

16:36:28 - boot complete
~16:37 - modprobe i915 , screen blank with backlight on

16:38:35 - second boot complete
~16:39 - modprobe i915 modeset=0, screen fine


-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/608907/comments/2


On 2010-05-26T23:55:15+00:00 Adam wrote:

Created attachment 417066
/var/log/messages from the affected system

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/608907/comments/3


On 2010-05-26T23:55:48+00:00 Adam wrote:

if you're wondering why the adapter apparently disappears entirely
outside of these couple of test boots, to actually *use* the system I
boot with the NVIDIA adapter selected, and use the NVIDIA proprietary
driver (which works).


-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/608907/comments/4


On 2010-05-27T00:00:28+00:00 Adam wrote:

Final note - this happens with both 2.6.34-2.fc14.x86_64 and
2.6.33.4-95.fc13.x86_64 .


-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/608907/comments/5


On 2010-05-28T20:42:34+00:00 Adam wrote:

with thanks to the inhabitants of #fedora-devel, I'll attach the drm
debug messages (with drm.debug=0x06 as directed by ajax).


-- 

[Kernel-packages] [Bug 880648] Re: 8086:0084 wifi iwlagn fails to authenticate after wake from suspend

[Bug Watch Updater]

** Changed in: linux (Fedora)
   Status: Unknown => Fix Released

** Changed in: linux (Fedora)
   Importance: Unknown => 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/880648

Title:
  8086:0084 wifi iwlagn fails to authenticate after wake from suspend

Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Fedora:
  Fix Released

Bug description:
  Upgraded to 11.10 from 11.04 today. Now when resume from suspend, wifi
  fails to reconnect saying waiting for authentication. If I use the
  last kernel from 11.04, 2.4.39 instead of the new 3.0.0, it still
  works OK. After wake from suspend, if using ethernet it works OK.

  lspci -v

  0d:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000
  Subsystem: Intel Corporation Centrino Wireless-N 1000 BGN
  Flags: bus master, fast devsel, latency 0, IRQ 53
  Memory at c450 (64-bit, non-prefetchable) [size=8K]
  Capabilities: [c8] Power Management version 3
  Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
  Capabilities: [e0] Express Endpoint, MSI 00
  Capabilities: [100] Advanced Error Reporting
  Capabilities: [140] Device Serial Number 8c-a9-82-ff-ff-a0-f4-7a
  Kernel driver in use: iwlagn
  Kernel modules: iwlagn

  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  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:  gene   1793 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xc750 irq 53'
 Mixer name : 'Intel CougarPoint HDMI'
 Components : 'HDA:111d7605,103c165a,00100105 
HDA:80862805,80860101,0010'
 Controls  : 18
 Simple ctrls  : 10
  DistroRelease: Ubuntu 11.10
  HibernationDevice: RESUME=UUID=522d916f-a489-4247-acf5-ddf837f836b9
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=UUID=ca71fcf1-cfed-4e2c-9593-29b47c9cc6a0 ro   quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.0.0-12.20-usernameric 3.0.4
  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: Error: [Errno 2] No such file or directory
  StagingDrivers: rts_pstor mei
  Tags:  oneiric staging
  UdevDb: Error: [Errno 2] No such file or directory
  Uname: Linux 3.0.0-12-generic x86_64
  UpgradeStatus: Upgraded to oneiric on 2011-10-23 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1A
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 165A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 10.31
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1A:bd07/20/2011:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr058D11244620001620100:rvnHewlett-Packard:rn165A:rvr10.31:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 058D11244620001620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 847187] Re: [HP Pavilion dv7-6104eg Entertainment Notebook PC] Backlight control doesn't work

[Bug Watch Updater]

** Changed in: fedora
   Status: Unknown => Won't Fix

** Changed in: fedora
   Importance: Unknown => 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/847187

Title:
  [HP Pavilion dv7-6104eg Entertainment Notebook PC] Backlight control
  doesn't work

Status in linux package in Ubuntu:
  Incomplete
Status in Fedora:
  Won't Fix

Bug description:
  Backlight control on HP Pavilion dv7 6104eg notebook doesn't work
  using function keys or Gnome power management applet. I found a patch,
  that should solve the problem:
  http://www.edgrochowski.com/articles/backlight.htm (haven't tried it
  yet)

  lsmod:
  Module  Size  Used by
  parport_pc 36959  0
  ppdev  17113  0
  rfcomm 47694  8
  binfmt_misc17565  1
  sco18187  2
  bnep   18308  2
  l2cap  53570  16 rfcomm,bnep
  vboxnetadp 13340  0
  vboxnetflt 28297  0
  vboxdrv   252684  2 vboxnetadp,vboxnetflt
  snd_hda_codec_hdmi 28167  1
  snd_hda_codec_idt  71137  1
  arc4   12529  2
  joydev 17606  0
  uvcvideo   72195  0
  usbhid 46956  0
  iwlagn333716  0
  snd_hda_intel  33176  4
  snd_hda_codec 103804  3 
snd_hda_codec_hdmi,snd_hda_codec_idt,snd_hda_intel
  snd_hwdep  13604  1 snd_hda_codec
  iwlcore   167502  1 iwlagn
  snd_pcm96391  4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
  videodev   82052  1 uvcvideo
  i915  515121  3
  snd_seq_midi   13324  0
  snd_rawmidi30486  1 snd_seq_midi
  btusb  18600  2
  snd_seq_midi_event 14899  1 snd_seq_midi
  bluetooth  72320  9 rfcomm,sco,bnep,l2cap,btusb
  snd_seq61621  2 snd_seq_midi,snd_seq_midi_event
  snd_timer  29602  2 snd_pcm,snd_seq
  v4l2_compat_ioctl3217078  1 videodev
  snd_seq_device 14462  3 snd_seq_midi,snd_rawmidi,snd_seq
  hid91020  1 usbhid
  hp_wmi 13706  0
  sparse_keymap  13898  1 hp_wmi
  mac80211  294370  2 iwlagn,iwlcore
  psmouse73535  0
  snd67382  17 
snd_hda_codec_hdmi,snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
  drm_kms_helper 42136  1 i915
  serio_raw  13166  0
  cfg80211  178528  3 iwlagn,iwlcore,mac80211
  rts_pstor 440614  0
  drm   227534  4 i915,drm_kms_helper
  soundcore  12680  1 snd
  snd_page_alloc 18529  2 snd_hda_intel,snd_pcm
  i2c_algo_bit   13400  1 i915
  video  19438  1 i915
  hp_accel   21880  0
  lis3lv02d  19893  1 hp_accel
  max665014324  0
  input_polldev  14007  1 lis3lv02d
  coretemp   13490  0
  lp 17825  0
  parport46458  3 parport_pc,ppdev,lp
  ahci   25951  2
  xhci_hcd   77643  0
  libahci26642  1 ahci
  r8169  48022  0

  ---
  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:  matthias   1587 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xc750 irq 53'
     Mixer name : 'Intel CougarPoint HDMI'
     Components : 'HDA:111d7605,103c3389,00100105 
HDA:80862805,80860101,0010'
     Controls  : 18
     Simple ctrls  : 10
  DistroRelease: Ubuntu 11.04
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-11-generic 
root=UUID=6562386e-524b-41be-8383-6e1944f15f1c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  RelatedPackageVersions:
   linux-restricted-modules-2.6.38-11-generic N/A
   linux-backports-modules-2.6.38-11-generic  N/A
   linux-firmware 1.52
  StagingDrivers: rts_pstor
  Tags:  natty staging
  Uname: Linux 2.6.38-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Hew

[Kernel-packages] [Bug 583760] Re: [PATCH] Mouse cursor dissappears with nouveau

[Bug Watch Updater]

Launchpad has imported 77 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=537065.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-11-12T11:19:40+00:00 Gianluca wrote:

Nouveau works nicely on my laptop, including suspend and resume, until
the power source changes (from AC to battery or from battery to AC).

After that event, mouse pointer gets flaky and I see in
/var/log/messages lots of lines like:

Nov 12 01:01:12 localhost kernel: [drm] nouveau :01:00.0: no space while 
unhiding cursor
Nov 12 01:01:12 localhost kernel: [drm] nouveau :01:00.0: no space while 
setting cursor image
Nov 12 01:01:12 localhost kernel: [drm] nouveau :01:00.0: no space while 
unhiding cursor
Nov 12 01:01:14 localhost kernel: [drm] nouveau :01:00.0: no space while 
setting cursor image
Nov 12 01:01:14 localhost kernel: [drm] nouveau :01:00.0: no space while 
unhiding cursor


Card is:
nVidia Corporation Quadro NVS 130M [10de:042a]

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/583760/comments/0


On 2009-11-12T22:18:28+00:00 Ben wrote:

Is this 100% reproducible on your system, or a random occurance?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/583760/comments/1


On 2009-11-13T07:42:59+00:00 Gianluca wrote:

100% reproducible. The timing between power source change and the
symptoms varies, but always within minutes I get to the issue.

Right now the only way out seems a reboot, suspending or hibernating
leads to a black screen on resume.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/583760/comments/2


On 2009-11-16T23:57:39+00:00 Richard wrote:

I have experienced this same problem on my desktop system a few days
ago.  I have not used suspend/resume.

xorg-x11-server-Xorg-1.7.1-7.fc12.i686
xorg-x11-drv-nouveau-0.0.15-17.20091105gite1c2efd.fc12.i686
xorg-x11-drv-nouveau-debuginfo-0.0.15-17.20091105gite1c2efd.fc12.i686

It's only happened once, but when it happened, my machine got horribly
slow.  Restarting X "resolved" the issue.

Xorg.0.log and /var/log/messages will be attached...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/583760/comments/3


On 2009-11-16T23:58:52+00:00 Richard wrote:

Created attachment 369809
Xorg.0.log from the session where the cursor problem occured

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/583760/comments/4


On 2009-11-16T23:59:41+00:00 Richard wrote:

Created attachment 369810
Relevant /var/log/messages from the session where the cursor problem occured

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/583760/comments/5


On 2009-11-22T10:11:29+00:00 Andrew wrote:

Affects me too. 100% reproducible by doing the following:

1. Set close lid to blank screen
2. Close lid
3. Open lid

It also seems to happen after 30-60 minutes of general usage.

>From that point on any cursor change (mouse over anything) creates the
following messages and bursts of high CPU usage:

Nov 22 09:58:44 localhost kernel: [drm] nouveau :01:00.0: no space while 
unhiding cursor
Nov 22 09:58:44 localhost kernel: [drm] nouveau :01:00.0: no space while 
setting cursor image
Nov 22 09:58:44 localhost kernel: [drm] nouveau :01:00.0: no space while 
unhiding cursor
Nov 22 09:58:45 localhost kernel: [drm] nouveau :01:00.0: no space while 
setting cursor image
Nov 22 09:58:45 localhost kernel: [drm] nouveau :01:00.0: no space while 
unhiding cursor

Card is:
01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 130M (rev a1) 
(prog-if 00 [VGA controller])
Subsystem: Toshiba America Info Systems Device 0001
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [128] Power Budgeting 
Capabilities: [600] Vendor Specific Information 
Kernel driver in use: nouveau
Kernel modules: nouveau, nvidiafb


Rebooting clears this, and doesn't happen with proprietary driver.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/583760/comments/6


On 2009-11-22T10:20:22+00:00 Andrew wrote:

In my case suspend/resume works t

[Kernel-packages] [Bug 655413] Re: NetworkManager: page allocation failure. order:3, mode:0x4020

[Bug Watch Updater]

Launchpad has imported 62 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=629158.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2010-09-01T05:49:55+00:00 A. wrote:

Description of problem:
Network adapter "disappears" after resuming from acpi suspend. Network Managaer 
doesn't see the device, the device doesn't show up in kinfocenter, either.

Version-Release number of selected component (if applicable):
kernel-2.6.33.6-147.2.4.fc13.x86_64

How reproducible:
Every time.

Steps to Reproduce:
1. Switch on computer
2. Ascertain that networking works
3. Suspend
4. Resume (switch it on again)
5. See how there is no networking
  
Actual results:
No networking

Expected results:
Everything works normally

Additional info:

>From /var/log/messages:

Sep  1 06:54:09 localhost NetworkManager[1234]:  wake requested 
(sleeping: yes  enabled: yes)
Sep  1 06:54:09 localhost NetworkManager[1234]:  waking up and 
re-enabling...
Sep  1 06:54:09 localhost NetworkManager[1234]:  (eth2): now managed
Sep  1 06:54:09 localhost NetworkManager[1234]:  (eth2): device state 
change: 1 -> 2 (reason 2)
Sep  1 06:54:09 localhost NetworkManager[1234]:  (eth2): bringing up 
device.
Sep  1 06:54:09 localhost kernel: NetworkManager: page allocation failure. 
order:3, mode:0x4020
Sep  1 06:54:09 localhost kernel: Pid: 1234, comm: NetworkManager Not tainted 
2.6.33.6-147.2.4.fc13.x86_64 #1


>From dmesg:

NetworkManager: page allocation failure. order:3, mode:0x4020
Pid: 1234, comm: NetworkManager Not tainted 2.6.33.6-147.2.4.fc13.x86_64 #1
Call Trace:
 [] __alloc_pages_nodemask+0x5ad/0x630
 [] kmalloc_large_node+0x5a/0x97
 [] __kmalloc_node_track_caller+0x2c/0x119
 [] ? __netdev_alloc_skb+0x2f/0x4c
 [] __alloc_skb+0x7b/0x16b
 [] __netdev_alloc_skb+0x2f/0x4c
 [] rtl8169_rx_fill+0xa3/0x14f [r8169]
 [] rtl8169_init_ring+0x6c/0x99 [r8169]
 [] rtl8169_open+0x7a/0x194 [r8169]
 [] dev_open+0x98/0xd3
 [] dev_change_flags+0xb9/0x179
 [] do_setlink+0x26c/0x33d
 [] ? avc_has_perm+0x57/0x69
 [] rtnl_setlink+0xfd/0x110
 [] rtnetlink_rcv_msg+0x1c1/0x1de
 [] ? rtnetlink_rcv_msg+0x0/0x1de
 [] netlink_rcv_skb+0x3e/0x8f
 [] rtnetlink_rcv+0x21/0x28
 [] netlink_unicast+0xe6/0x14f
 [] netlink_sendmsg+0x254/0x263
 [] __sock_sendmsg+0x59/0x64
 [] sock_sendmsg+0xa3/0xbc
 [] ? sock_sendmsg+0xa3/0xbc
 [] ? might_fault+0x1c/0x1e
 [] ? copy_from_user+0x2a/0x2c
 [] ? verify_iovec+0x4f/0x8d
 [] sys_sendmsg+0x217/0x29b
 [] ? sockfd_lookup_light+0x1b/0x53
 [] ? fput_light+0xd/0xf
 [] ? sys_sendto+0x120/0x14d
 [] ? path_put+0x1d/0x22
 [] ? audit_syscall_entry+0x119/0x145
 [] system_call_fastpath+0x16/0x1b

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/655413/comments/0


On 2010-09-01T05:51:53+00:00 A. wrote:

I forgot. Here is some data about my hardware:
# dmidecode

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: ASUSTeK Computer INC.
Product Name: M4A88T-M

Handle 0x0004, DMI type 4, 40 bytes
Processor Information
Socket Designation: AM3

Handle 0x002D, DMI type 10, 6 bytes
On Board Device Information
Type: Ethernet
Status: Enabled
Description: To Be Filled By O.E.M.

#

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/655413/comments/1


On 2010-09-09T14:24:20+00:00 Stanislaw wrote:

After resume network driver rtl8169 is not able to allocate memory and
fail to initialize, hence "disappears"  effect. I will prepare patch
with change allocation strategy, what should fix the problem.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/655413/comments/2


On 2010-09-09T16:15:13+00:00 Stanislaw wrote:

Created attachment 446284
f13-r8169-alloc-fix.patch

Could you please test this patch. Please build debug kernel since it
catch bugs when improper allocation method is used. I you can not build
kernel by yourself, I will prepare packages tomorrow. Thanks.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/655413/comments/3


On 2010-09-10T14:49:00+00:00 Stanislaw wrote:

http://koji.fedoraproject.org/koji/taskinfo?taskID=2459629
Please test kernel-debug when it finish to build.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/655413/comments/4


On 2010-09-13T11:55:07+00:00 Stanislaw wrote:

These koji builds are automatically removed after about a week, so
please test soon.

Reply at:
https://bugs.lau

[Kernel-packages] [Bug 625364] Re: lenovo/thinkpad R400/R500/T6x/T400[s]/T420/T500/W500/W700/X60/X200 suspend fails

[Bug Watch Updater]

Launchpad has imported 14 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=647604.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2010-10-28T21:35:05+00:00 Felix wrote:

Created attachment 456339
/var/log/pm-suspend.log

I had suspend working on my notebook for several Fedora versions. It
broke recently.

Debugging it I found out that it fails with 
# echo mem > /sys/power/state 
bash: echo: Write-Error: Input/Output-Error


pm-utils-1.3.1-3.fc14.i686
# uname -a
Linux thinkpad 2.6.35.6-46.fc14.i686.PAE #1 SMP Tue Oct 19 03:06:38 UTC 2010 
i686 i686 i386 GNU/Linux

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/625364/comments/17


On 2010-10-28T22:12:08+00:00 Robert wrote:

Created attachment 456346
Similar experience on a Lenovo Thinkpad X200s

Suspend fails at the same point as the aforementioned poster, except in
my /usr/lib64/pm-utils/pm-functions at line 295 I have an echo -n.

I have pm-utils-1.3.1-2.fc14.x86_64 installed.

If I cat /sys/power/state I observe:

$ cat /sys/power/state 
mem disk

If there is anything you would like me to try or any further information
you wish to obtain from me, please ask.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/625364/comments/18


On 2010-10-29T22:26:48+00:00 Robert wrote:

This issue is fixed for me with the kernel update to:

kernel.x86_64   2.6.35.6-48.fc14

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/625364/comments/19


On 2010-10-31T08:50:53+00:00 Felix wrote:

In fact I can "echo mem > /sys/power/state" now without error.
But the system hangs on suspend every time. I just see the blue plymouth 
screen...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/625364/comments/21


On 2010-10-31T10:06:19+00:00 Jaroslav wrote:

Seems like kernel problem. Could you provide output of pm-utils-
bugreport-info.sh?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/625364/comments/22


On 2010-11-01T08:06:32+00:00 Felix wrote:

Created attachment 456809
pm-utils-bugreport-info.sh

Here is the output of pm-utils-bugreport-info.sh.

My systems suspends fine with "echo mem > /sys/power/state". However it
does not work from the menu (gnome) and from the terminal with "pm-
suspend"...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/625364/comments/24


On 2010-11-01T09:27:18+00:00 Jaroslav wrote:

Log looks good. I do not have here T400 for testing now but I will try
to get one. Can you try without video quirks? Create file in
/etc/pm/config.d with content:

HOOK_BLACKLIST=98video-quirk-db-handler

If it doesn't help try to blacklist other hooks from the log above.
Maybe one of the hook is causing problem. Please report result.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/625364/comments/26


On 2010-11-01T10:35:48+00:00 Felix wrote:

Hi Jaroslav thanks alot for your suggestion:

HOOK_BLACKLIST=98video-quirk-db-handler

fixes the problem for me.

What do you need to really fix this?
At what time is 
http://cgit.freedesktop.org/pm-utils/tree/video-quirks/20-video-quirk-pm-lenovo.quirkdb?h=video-quirks
 used?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/625364/comments/27


On 2010-11-05T16:48:37+00:00 Jaroslav wrote:

Thanks for info. It seems the quirks DB is not shipped with pm-utils.
Please try to download latest quirk DB from http://pm-
utils.freedesktop.org/releases/ and unpack it to /usr/lib/pm-utils (or
/usr/lib64/pm-utils/ for 64 bit) and retest.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/625364/comments/31


On 2010-11-09T11:45:48+00:00 Jaroslav wrote:

Please try following scratch build:
http://koji.fedoraproject.org/koji/taskinfo?taskID=2589652

It incorporates all quirks. Also pm-utils-bugreport-info.sh was updated.
If you still encounter the problem, please post output of pm-utils-
bugreport-info.sh from the above scratch build. It should reveal more
information now.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/625364/comments/37

-

[Kernel-packages] [Bug 765082] Re: [ips-monitor] is in state 'D'

[Bug Watch Updater]

Launchpad has imported 14 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=703511.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2011-05-10T14:49:25+00:00 Richard wrote:

Description of problem:

This seems to be the same as this Ubuntu bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/765082

With all up to date Fedora 15, ips-monitor kernel thread is
constantly in D state, resulting in the load avg always being
over 1.0, resulting in the laptop fan running continuously.

Version-Release number of selected component (if applicable):

Linux spin.home.annexia.org 2.6.38.5-22.fc15.x86_64 #1 SMP Mon May 2
19:28:55 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

How reproducible:

Always.

Steps to Reproduce:
1. Nothing, just boot the machine.
2.
3.

Additional info:

$ ps ax | grep ' D '
  723 ?D  0:04 [ips-monitor]
 3477 pts/0S+ 0:00 grep --color=auto  D 

According to the Ubuntu bug, it is fixed by this patch:
https://lkml.org/lkml/2011/3/19/37

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/765082/comments/6


On 2011-05-10T14:51:27+00:00 Richard wrote:

I mean, this patch:
https://lkml.org/lkml/2011/3/22/345

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/765082/comments/7


On 2011-05-10T23:38:06+00:00 Chuck wrote:

Upstream commit:

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=a3424216e4935221fdaa5ca3c26e024f11297164

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/765082/comments/8


On 2011-05-11T13:28:33+00:00 Chuck wrote:

Patch will be in kernel-2.6.38.6-27.fc15

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/765082/comments/9


On 2011-05-16T04:46:17+00:00 Fedora wrote:

kernel-2.6.38.6-27.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/kernel-2.6.38.6-27.fc15

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/765082/comments/10


On 2011-05-17T05:37:00+00:00 Fedora wrote:

Package kernel-2.6.38.6-27.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kernel-2.6.38.6-27.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/kernel-2.6.38.6-27.fc15
then log in and leave karma (feedback).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/765082/comments/11


On 2011-05-17T18:48:04+00:00 Adam wrote:

probably worth a commonbugs note; do we know what systems this will
affect?


-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/765082/comments/12


On 2011-05-17T18:56:50+00:00 Richard wrote:

I've installed the update but not booted to test it yet.

Mine is a Thinkpad T510W.

I'm not sure this is common .. I seem to be the only one
that has noticed :-)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/765082/comments/13


On 2011-05-18T18:09:41+00:00 Chuck wrote:

*** Bug 702775 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/765082/comments/14


On 2011-05-18T18:19:41+00:00 Chuck wrote:

(In reply to comment #6)
> probably worth a commonbugs note; do we know what systems this will affect?
> 

Intel systems with integrated i915 graphics.
IPS controls power sharing between the CPU and the GPU.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/765082/comments/15


On 2011-05-19T05:10:51+00:00 Fedora wrote:

kernel-2.6.38.6-27.fc15 has been pushed to the Fedora 15 stable
repository.  If problems still persist, please make note of it in this
bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/765082/comments/16


On 2011-05-19T13:54:58+00:00 Jeff wr

[Kernel-packages] [Bug 751689] Re: [Lenovo Thinkpad x201s] Overheat due to slow fans when on 'auto'

[Bug Watch Updater]

** Changed in: linux (Fedora)
   Status: Unknown => Won't Fix

** Changed in: linux (Fedora)
   Importance: Unknown => 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/751689

Title:
  [Lenovo Thinkpad x201s] Overheat due to slow fans when on 'auto'

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Maverick:
  Won't Fix
Status in linux source package in Natty:
  Won't Fix
Status in linux source package in Precise:
  Confirmed
Status in thinkfan package in Debian:
  Fix Released
Status in linux package in Fedora:
  Won't Fix

Bug description:
  On my Thinkpad x201s with an i7, if I utilize all of the CPUs/hyperthreads, 
the machine can be made to overheat very quickly. This is because of the 
default level setting of 'auto' in /proc/acpi/ibm/fan. On 'auto', the fan only 
ever goes up to around 4500rpm, while in 'disengaged' mode it can go as high as 
6400rpm. At 4500rpm, the CPU continues to climb until the system is forcibly 
shutdown at 100C. If I reload thinkpad_acpi like so:
  $ sudo rmmod thinkpad_acpi
  $ sudo modprobe thinkpad_acpi fan_control=1

  Then I can set the fan to disengaged mode manually:
  echo "level disengaged" > /proc/acpi/ibm/fan

  With this setting, I can utilize all of the CPUs for an extended time
  and not surpass 85C, still pretty hot but well under the 100C range.
  Furthermore, setting to level '7' (the supposed max fan speed) runs
  the fan at ~5300, well below the maximum fan speed.

  In maverick this did not seem to be as much of a problem (perhaps
  because of the lack of the big kernel lock in natty?).

  Related bugs:
  https://bugzilla.redhat.com/show_bug.cgi?id=675433
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610722 (against thinkfan 
package, but demonstrates that other x201 users are having the same problem)

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: linux-image-2.6.38-7-generic 2.6.38-7.39
  Regression: Yes
  Reproducible: Yes
  ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
  Uname: Linux 2.6.38-7-generic x86_64
  AcpiTables:
   Error: command ['gksu', '-D', 'Apport', '--', 
'/usr/share/apport/dump_acpi_tables.py'] failed with exit code 1: 
GNOME_SUDO_PASS
   Sorry, try again.
   sudo: 3 incorrect password attempts
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jamie  2641 F pulseaudio
   /dev/snd/pcmC0D0p:   jamie  2641 F...m pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf252 irq 43'
     Mixer name : 'Intel IbexPeak HDMI'
     Components : 'HDA:14f15069,17aa2156,00100302 
HDA:80862804,17aa21b5,0010'
     Controls  : 12
     Simple ctrls  : 6
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
6QHT28WW-1.09'
     Mixer name : 'ThinkPad EC 6QHT28WW-1.09'
     Components : ''
     Controls  : 1
     Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
     Capabilities: pswitch pswitch-joined penum
     Playback channels: Mono
     Mono: Playback [on]
  Date: Tue Apr  5 11:56:28 2011
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=58280e6e-d161-43ea-8593-a89fb7b6851a
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
  MachineType: LENOVO 5129CTO
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-7-generic 
root=UUID=82571cfb-fdda-4d2f-b708-f8924aa0fe21 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-2.6.38-7-generic N/A
   linux-backports-modules-2.6.38-7-generic  N/A
   linux-firmware1.49
  SourcePackage: linux
  UpgradeStatus: Upgraded to natty on 2011-02-24 (39 days ago)
  dmi.bios.date: 04/20/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET44WW (1.14 )
  dmi.board.name: 5129CTO
  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:bvr6QET44WW(1.14):bd04/20/2010:svnLENOVO:pn5129CTO:pvrThinkPadX201s:rvnLENOVO:rn5129CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 5129CTO
  dmi.product.version: ThinkPad X201s
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel

[Kernel-packages] [Bug 764003] Re: vodafone k3805-z requires "ifconfig usb0 -arp" prior to connecting to achieve connectivity

[Bug Watch Updater]

Launchpad has imported 6 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=729952.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2011-08-11T11:38:45+00:00 Pedro wrote:

Description of problem:
Vodafone k3805-z requires "ifconfig usb0 -arp" prior to connecting to achieve 
connectivity

Version-Release number of selected component (if applicable):
0.4.998 - 1.git20110706.fc15

How reproducible:
Always.

Steps to Reproduce:
1. plug usb modem and workaround whatever needed to connect (#697122)
2. try to ping/access some site
  
Actual results:
Nothing happens (Wireshark shows ARP requests being sent to every IP one tries 
to connect with)

Expected results:
Ping should be successful.

Additional info:
$ route -n [with or without NOARP]
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 0.0.0.0 0.0.0.0 U 0  00 usb0

Also, the driver on Windows 7 has an option which says "Enable
promiscuous mode" (?on a 3G pen?) which, after enabled, results on the
same behavior as if one does "ifconfig usb0 arp" on Linux.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/764003/comments/26


On 2011-08-22T07:18:41+00:00 Karl wrote:

I can confirm this bug, with this hardware.

The "ifconfig usb0 -arp" workaround works.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/764003/comments/27


On 2012-07-20T22:44:18+00:00 Dan wrote:

Huh, quite odd.  Probably something we should do for all 3G devices that
provide eth ports, since they are all acutally point-to-point
underneath.  I have just bought a K3805z off ebay that I can use to test
this out when it arrives.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/764003/comments/37


On 2012-07-21T08:14:35+00:00 Pedro wrote:

@Dan Williams : Hello! Just to point out you will also find bug #745454
if using Gnome-Shell ;)

Also, I don't know if all devices are affected. Looking at
https://github.com/andrewbird/wader/blob/master/resources/udev/99-wader-
quirks.rules you can see a relatively small list of quirks.

(that URL is the temporary Git repo of Vodafone's
https://forge.betavine.net/projects/bcm (which curiously is hidden from
public project list), as the result of the migration off SVN
https://forge.betavine.net/forum/forum.php?forum_id=245 )

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/764003/comments/38


On 2013-01-16T13:06:33+00:00 Fedora wrote:

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/764003/comments/44


On 2013-01-31T12:46:11+00:00 Pedro wrote:

At least on Fedora 18, the device is now recognized as "wwan0" and no
longer requires ifconfig INTERFACE_NAME -arp .

Closing bug.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/764003/comments/45


** Changed in: linux (Fedora)
   Status: Unknown => Fix Released

** Changed in: linux (Fedora)
   Importance: Unknown => Undecided

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

[Kernel-packages] [Bug 313486] Re: internal microphone doesn't work on Medion MD 96630

[Bug Watch Updater]

** Changed in: fedora
   Importance: Unknown => High

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

Title:
  internal microphone doesn't work on Medion MD 96630

Status in alsa-lib package in Ubuntu:
  Invalid
Status in Fedora:
  Won't Fix

Bug description:
  If I try to use my mic with Skype/Audacity it doesn't work with my
  Medion Akoya MD 96630 with Ubuntu 8.10.

  cat /proc/version_signature: Ubuntu 2.6.27-9.19-generic
  uname -a: Linux pc07 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 
i686 GNU/Linux
  cat /proc/asound/cards:
   0 [Intel  ]: HDA-Intel - HDA Intel
HDA Intel at 0xfa20 irq 22

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/313486/+subscriptions

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

[Kernel-packages] [Bug 324211] Re: AMD X2 CPU stuck at 1Ghz lowest speed

[Bug Watch Updater]

Launchpad has imported 23 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=403651.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2007-11-28T23:47:15+00:00 Ryan wrote:

>From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.9) Gecko/20071105 
Fedora/2.0.0.9-1.fc9 Firefox/2.0.0.9

Description of problem:
On my Santa Rosa based Fujitsu T4220 notebook the CPU frequency is permanently 
stuck at 800MHz (actual max is 2GHz) no matter what the load. This occurs no 
matter which governor is selected (userspace, ondemand, performance etc..).

On resume from suspend to ram, the frequency fluctuates between 800MHz
and 1.6GHz for approx. a minute, and then goes back to being stuck at
800MHz.

Version-Release number of selected component (if applicable):
kernel-2.6.24-0.42.rc3.git1.fc9

How reproducible:
Always


Steps to Reproduce:
1. boot into fedora
2. check /cat/proc/cpuinfo ( will be 800MHz )
3. run something cpu intensive
3. check cpuinfo (still stuck at 800MHz)

Actual Results:
The CPU frequency doesn't change

Expected Results:
The frequency should increase to max if needed and go back to min when not.

Additional info:

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/324211/comments/0


On 2007-11-28T23:48:38+00:00 Ryan wrote:

Created attachment 271951
lspci -vv output

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/324211/comments/1


On 2007-11-28T23:49:31+00:00 Ryan wrote:

Created attachment 271961
lspci -vvn output

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/324211/comments/2


On 2007-11-28T23:50:05+00:00 Ryan wrote:

Created attachment 271971
dmidecode output

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/324211/comments/3


On 2007-11-28T23:57:42+00:00 Ryan wrote:

[ryan@tablet ~]$ ls /sys/devices/system/cpu/cpu0/cpufreq/
affected_cpus scaling_available_frequencies  scaling_governor
cpuinfo_cur_freq  scaling_available_governorsscaling_max_freq
cpuinfo_max_freq  scaling_cur_freq   scaling_min_freq
cpuinfo_min_freq  scaling_driver scaling_setspeed

[root@tablet ryan]# cat /sys/devices/system/cpu/cpu0/cpufreq/*
0 1
80
2001000
80
2001000 200 160 120 80 
userspace performance 
80
acpi-cpufreq
performance
80
80

Also, I am not sure how relevant this is, but
/proc/acpi/processor/CPU0/throttling outputs "".

I have the same problems on every linux distro I have tried on this
laptop

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/324211/comments/4


On 2007-12-01T00:48:49+00:00 Ryan wrote:

Created attachment 274581
dmesg output

Here's my dmesg

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/324211/comments/5


On 2007-12-10T20:54:09+00:00 Jaakko wrote:

On updated Fedora 8, on Dell Inspiron 9300 laptop, I have the same problem. 
Frequency policy is stuck at 800 MHz.  Scaling worked in the past on some
earlier FC, not sure if I paid attention so much on FC7.

# cpufreq-info 
cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to li...@brodo.de, please.
analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which need to switch frequency at the same time: 0
  hardware limits: 800 MHz - 1.73 GHz
  available frequency steps: 1.73 GHz, 1.33 GHz, 1.07 GHz, 800 MHz
  available cpufreq governors: ondemand, userspace, performance
  current policy: frequency should be within 800 MHz and 800 MHz.
  The governor "ondemand" may decide which speed to use
  within this range.
  current CPU frequency is 800 MHz.

# cat /proc/cpuinfo
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 13
model name  : Intel(R) Pentium(R) M processor 1.73GHz
stepping: 8
cpu MHz : 800.000
cache size  : 2048 KB
fdiv_bug: no
hlt_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 2
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat
clflush dts acpi mmx fxsr sse sse2 ss tm pbe nx up bts est tm2
bogomips: 1597.42
clflush size: 64

# cat /proc/acpi/processor/CPU0/throttling 
state count:

[Kernel-packages] [Bug 438136] Re: palimpsest bad sectors false positive

[Bug Watch Updater]

** Changed in: libatasmart (Fedora)
   Status: Confirmed => Won't Fix

** Changed in: libatasmart (Fedora)
   Importance: Unknown => High

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

Title:
  palimpsest bad sectors false positive

Status in libatasmart:
  Confirmed
Status in OEM Priority Project:
  Fix Released
Status in libatasmart package in Ubuntu:
  Fix Released
Status in libatasmart source package in Lucid:
  Fix Released
Status in libatasmart source package in Karmic:
  Fix Released
Status in libatasmart package in Fedora:
  Won't Fix
Status in libatasmart package in Mandriva:
  New
Status in libatasmart package in zUbuntu:
  New

Bug description:
  Binary package hint: gnome-disk-utility

  palimpsest complains, that the disk has many bad sectors. palimpsest
  thinks, that SMART value 5 "Reallocated Sector Count" fails
  (screenshot attached). smartctl reports "  5 Reallocated_Sector_Ct
  0x0033   097   097   010Pre-fail  Always   -   117" (full
  log attached) which seems to be ok. This error appears on a different
  system, too.

  SRU information:
   - Impact: Way too trigger happy about "broken disk" notifications, which 
both scares people and also makes them ignore situations where the disk is 
actually about to die
   - Fixed in lucid by reverting from our own bad sectors heuristics (using the 
raw numbers) to the manufactuer normalized numbers and manufacturer thresholds: 
http://bugs.freedesktop.org/attachment.cgi?id=34242
  - No regression reports since then in lucid.

  SRU TEST CASE:
  - Download seb128's demo SMART data which have a few bad blocks, but not 
enough to be over the manufacturer threshold:

     wget -O /tmp/smart.blob
  http://bugs.freedesktop.org/attachment.cgi?id=34234

  - Install libatasmart-bin

  - Run

    skdump --load=/tmp/smart.blob --overall

  With the karmic final version this says "BAD_SECTOR_MANY" which the GUI will 
react on with a scary notification.
  The updated version should just say BAD_SECTOR.

  If you leave out the --overall argument, you get a detailled list of
  the attributes. The broken ones will be printed in bold.

  On a healthy system, "sudo ./skdump   /dev/sda --overall" should still
  say "GOOD", and on a genuinely broken hard disk it should give the
  appropriate BAD_SECTOR/BAD_SECTOR_MANY answer.

  ProblemType: Bug
  Architecture: amd64
  Date: Mon Sep 28 15:20:15 2009
  DistroRelease: Ubuntu 9.10
  Package: gnome-disk-utility 2.28.0-0ubuntu2
  ProcEnviron:
   PATH=(custom, user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
  SourcePackage: gnome-disk-utility
  Uname: Linux 2.6.31-11-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+bug/438136/+subscriptions

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

[Kernel-packages] [Bug 1153618] Re: Support Realtek RTS5227 card reader

[Bug Watch Updater]

Launchpad has imported 23 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1242712.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2015-07-14T03:03:36+00:00 Steven wrote:

Description of problem:
Unable to access SDCX cards via the SD Card reader in my T440s.

No issues with any SDHC or micro SDHC cards via an adapter.


Version-Release number of selected component (if applicable):
Realtek PCI-E Card Reader Driver
Current Kernel 4.0.7-200.fc21.x86_64

How reproducible:
Fully

Steps to Reproduce:
1. Insert an EXFAT / FAT / NTFS formatted SDXC Card
2. Card appears in Nautilus and under /run/media/user/X
3. Attempts to read/write to card result in errors or card corrpution

Actual results:
Numerous errors logged relating to the RTSX and MMC drivers.

Jul 14 10:32:05 t440s kernel: rtsx_pci_sdmmc rtsx_pci_sdmmc.0: no support for 
card's volts
Jul 14 10:32:05 t440s kernel: mmc0: error -22 whilst initialising SDIO card
Jul 14 10:32:05 t440s kernel: mmc0: error -95 whilst initialising SD card
Jul 14 10:32:05 t440s kernel: rtsx_pci_sdmmc rtsx_pci_sdmmc.0: no support for 
card's volts
Jul 14 10:32:05 t440s kernel: mmc0: error -22 whilst initialising MMC card

Jul 14 12:03:31 t440s kernel: mmc0: cannot verify signal voltage switch 
Jul 14 12:03:31 t440s kernel: mmc0: new ultra high speed SDR104 SDXC card at 
address 0007
Jul 14 12:03:31 t440s kernel: mmcblk0: mmc0:0007 SD64G 58.2 GiB 
Jul 14 12:03:31 t440s kernel:  mmcblk0: p1
Jul 14 12:03:31 t440s kernel: mmcblk0: unknown error -22 sending read/write 
command, card status 0x900
Jul 14 12:03:31 t440s kernel: mmc0: cannot verify signal voltage switch 

Jul 14 12:03:31 t440s kernel: mmc0: tried to reset card
Jul 14 12:03:31 t440s kernel: mmcblk0: unknown error -22 sending read/write 
command, card status 0x900
Jul 14 12:03:31 t440s kernel: mmc0: cannot verify signal voltage switch 
Jul 14 12:03:31 t440s kernel: mmc0: tried to reset card
Jul 14 12:03:31 t440s kernel: mmcblk0: unknown error -22 sending read/write 
command, card status 0x900
Jul 14 12:03:31 t440s kernel: blk_update_request: 2337 callbacks suppressed
Jul 14 12:03:31 t440s kernel: blk_update_request: I/O error, dev mmcblk0, 
sector 2176
Jul 14 12:03:31 t440s kernel: blk_update_request: I/O error, dev mmcblk0, 
sector 2184


Expected results:
R/W access should work cleanly with FAT/NTFS formatted cards
R/W access should work for exFAT with the rpmfusion RPMS
 - fuse-exfat-1.1.0-1.fc21.x86_64
 - exfat-utils-1.1.1-1.fc21.x86_64

Additional info:

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1153618/comments/21


On 2015-07-14T03:04:47+00:00 Steven wrote:

Current Kernel Modules Version
 - kernel-modules-4.0.5-200.fc21.x86_64

Note that HW Certification for RHEL 7 is underway under
https://bugzilla.redhat.com/show_bug.cgi?id=1220211

They should confirm that the device is fully operational with both SDHC
and SDXC cards.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1153618/comments/22


On 2015-07-23T03:18:06+00:00 Steven wrote:

Updated RHEL7 BZ 1220211 as the same issues occur

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1153618/comments/23


On 2015-07-23T03:19:56+00:00 Steven wrote:

Tested the card under a friends T440s running Ubuntu 15.04

Insert vfat formatted card and create a new file. Then eject card.


[ 1214.355115] mmc0: cannot verify signal voltage switch
[ 1214.467278] mmc0: new ultra high speed SDR104 SDXC card at address 0007
[ 1214.474164] Driver 'mmcblk' needs updating - please use bus_type methods
[ 1214.474277] mmcblk0: mmc0:0007 SD64G 58.2 GiB
[ 1214.476144]  mmcblk0: p1
[ 1224.953923] mmcblk0: timed out sending r/w cmd command, card status 0x400900
[ 1225.053874] mmcblk0: timed out sending r/w cmd command, card status 0x400900
[ 1231.207667] mmcblk0: timed out sending r/w cmd command, card status 0x400900
[ 1235.642101] mmcblk0: timed out sending r/w cmd command, card status 0x400900
[ 1240.232505] mmc0: card 0007 removed 

Getting the same r/w kernel errors when writing to the card. Ejected
card is corrupted and needs re-formatting

Confirms issue isn't specific to my T440s

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1153618/comments/24


On 2015-07-23T19:27:50+00:00 Laura wrote:

I have the same hardware in my T540p

lspci | grep -i RTS
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI 
Express Card Reader (rev 01

The card 

[Kernel-packages] [Bug 382140] Re: regression since karmic, still in precise: high-pitched noise from snd-hda-intel

[Bug Watch Updater]

Launchpad has imported 13 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=523340.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-09-14T23:12:14+00:00 Andreas wrote:

Description of problem:
As description says, a high-frequency sound coming from the speakers when there 
has been no connection to pulseaudio for ~10 seconds. Very annoying, and a 
regression, seeing as I use pulse now on ubuntu, and it works nice.

How reproducible:
every time

Steps to Reproduce:
1. Boot fedora, turn on speakers
2. done
  
Actual results:
High-freq sound coming from speakers

Expected results:
silence

Additional info:
The sound disappear when anything is connected to pulseaudio (it seems). Even 
the pa-volume-control

hw-info:
http://www.smolts.org/client/show/?uuid=pub_044784f1-3d15-4c08-a282-6c1300053734

Seems like its the "ATI Technologies Inc SB600 Azalia" that is the
sinner, seeing as I don't use anything but the dvi-output from the card.

What logs are needed for this?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/382140/comments/5


On 2009-09-15T01:22:00+00:00 Lennart wrote:

Sounds more like a driver/hw problem.

Could you please run "pacmd ls" when you hear this and attach this here.
If everything is correct in PA this should tell us that no app is
playing audio an the device closed becuase idle. If that is the case
then we should reassign this to the kernel, as it is a kernel driver/hw
prob.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/382140/comments/6


On 2009-09-16T15:46:00+00:00 Andreas wrote:

Created attachment 361305
output from pacmd ls

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/382140/comments/8


On 2009-09-16T16:25:19+00:00 Andreas wrote:

Created attachment 361316
alsa-info.sh output

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/382140/comments/9


On 2009-09-17T02:42:47+00:00 Lennart wrote:

The "pacmd ls" shows that all of PA's sinks are in state "SUSPENDED"
meaning that the devices are closed. If you hear noise this means the
sound must come from somewhere else.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/382140/comments/10


On 2009-09-17T08:21:04+00:00 Andreas wrote:

Why changing from "10 seconds" to "for a while?", I counted, and it
starts after pretty much 10 seconds every time.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/382140/comments/11


On 2009-09-22T19:54:14+00:00 Adam wrote:

do you see any interesting messages in /var/log/messages ? especially
around the time the problem kicks in / goes away (when you start playing
sound).

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/382140/comments/12


On 2009-09-22T20:33:15+00:00 Andreas wrote:

I'll get a copy of /var/log/messages uploaded as soon as I get the time
(hopefully tomorrow). Any other files that would be interesting?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/382140/comments/13


On 2009-11-03T00:30:34+00:00 Andreas wrote:

The problem seems to be the same as described on launchpad, and can
(probably,haven't tested it yet) temporarily be solved by changing
"options snd-hda-intel power_save=10 power_save_controller=N" to
"options snd-hda-intel power_save=0 power_save_controller=N" in alsa-
base.conf

Will test when I get the time.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/382140/comments/20


On 2009-11-16T12:23:10+00:00 Bug wrote:


This bug appears to have been reported against 'rawhide' during the Fedora 12 
development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/382140/comments/22


On 2009-12-01T18:09:05+00:00 Diego wrote:

I can confirm that adding line "options snd-hda-intel power_save=0" to a
file in /etc/modprobe.d (for e

[Kernel-packages] [Bug 398292] Re: constant kernel message: [drm:drm_wait_vblank] *ERROR* failed to acquire vblank counter, -22

[Bug Watch Updater]

** Changed in: fedora
   Status: In Progress => Won't Fix

** Changed in: fedora
   Importance: Unknown => 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/398292

Title:
  constant kernel message: [drm:drm_wait_vblank] *ERROR* failed to
  acquire vblank counter, -22

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Won't Fix
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid
Status in Fedora:
  Won't Fix

Bug description:
  I these messages constantly in dmesg, and in kern.log:
  Jul 11 19:04:39 dellmini9 kernel: [ 1145.712280] [drm:drm_wait_vblank] 
*ERROR* failed to acquire vblank counter, -22
  Jul 11 19:04:39 dellmini9 kernel: [ 1145.712305] [drm:drm_wait_vblank] 
*ERROR* failed to acquire vblank counter, -22
  Jul 11 19:04:39 dellmini9 kernel: [ 1145.750009] [drm:drm_wait_vblank] 
*ERROR* failed to acquire vblank counter, -22
  Jul 11 19:04:39 dellmini9 kernel: [ 1145.750040] [drm:drm_wait_vblank] 
*ERROR* failed to acquire vblank counter, -22
  Jul 11 19:04:39 dellmini9 kernel: [ 1145.786861] [drm:drm_wait_vblank] 
*ERROR* failed to acquire vblank counter, -22
  Jul 11 19:04:39 dellmini9 kernel: [ 1145.786890] [drm:drm_wait_vblank] 
*ERROR* failed to acquire vblank counter, -22
  Jul 11 19:04:39 dellmini9 kernel: [ 1145.806755] [drm:drm_wait_vblank] 
*ERROR* failed to acquire vblank counter, -22
  Jul 11 19:04:39 dellmini9 kernel: [ 1145.806787] [drm:drm_wait_vblank] 
*ERROR* failed to acquire vblank counter, -22
  Jul 11 19:04:39 dellmini9 kernel: [ 1145.826735] [drm:drm_wait_vblank] 
*ERROR* failed to acquire vblank counter, -22
  Jul 11 19:04:39 dellmini9 kernel: [ 1145.826762] [drm:drm_wait_vblank] 
*ERROR* failed to acquire vblank counter, -22

  I'm assuming that this is related to the video drivers, but I'm not
  sure what I should do to make this stop.

  ProblemType: Bug
  Architecture: i386
  Date: Sat Jul 11 19:03:31 2009
  DistroRelease: Ubuntu 9.10
  MachineType: Dell Inc. Inspiron 910
  NonfreeKernelModules: wl
  Package: linux-image-generic 2.6.31.2.13
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-2-generic 
root=UUID=566c781e-99df-41fa-a6d6-6dd6e2b72247 ro quiet splash
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-2.17-generic
  RelatedPackageVersions: linux-backports-modules-2.6.31-2-generic N/A
  SourcePackage: linux-meta
  Tags:  ubuntu-unr
  Uname: Linux 2.6.31-2-generic i686
  dmi.bios.date: 03/05/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: CN0J14
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A05
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd03/05/2009:svnDellInc.:pnInspiron910:pvrA05:rvnDellInc.:rnCN0J14:rvrA05:cvnDellInc.:ct8:cvrA05:
  dmi.product.name: Inspiron 910
  dmi.product.version: A05
  dmi.sys.vendor: Dell Inc.

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

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