[Kernel-packages] [Bug 1358226] Re: kernel and lockd xprt_adjust_timeout rq_timeout
I am also experiencing this bug. This issue did not occur on precise, however it does occur on trusty. I have not tried non-LTS releases. I can confirm that the same issue occurs on the current upstream mainline kernel. I have reproduced the issue with 3.17.1-031701-generic ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1358226 Title: kernel and lockd xprt_adjust_timeout rq_timeout Status in “linux” package in Ubuntu: Incomplete Bug description: I am seeing the following messages in syslog. There are no other messages around that time to suggest why it is happening. Aug 18 11:01:16 hostname kernel: [943559.414398] xprt_adjust_timeout: rq_timeout = 0! Aug 18 11:01:16 hostname kernel: [943559.414401] lockd: server nfs_server not responding, still trying Aug 18 11:01:16 hostname kernel: [943559.415347] lockd: server nfs_server OK System is: Linux hostname 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 14.04.1 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358226/+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 1383097] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1383097 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1383097 Title: Touch pad multi touch features doesn't work Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I am using an Asus X553MA laptop. My touch pad works well. But the features like multitouch, scrolling etc doesn't seem to work. I tried the below command and it didn't return any output. cat /proc/bus/input/devices ~/devices xinput --list ~/xinput And the below code returns all hardware info but not my touchpad ajith@ajith-X553MA:~$ cat /proc/bus/input/devices But i noticed a field as Mouse instead of my touchpad. I: Bus=0011 Vendor=0002 Product=0001 Version=0063 N: Name=PS/2 Logitech Wheel Mouse P: Phys=isa0060/serio4/input0 S: Sysfs=/devices/platform/i8042/serio4/input/input12 U: Uniq= H: Handlers=mouse0 event5 B: PROP=0 B: EV=7 B: KEY=7 0 0 0 0 0 0 0 0 B: REL=3 I have used a mouse earlier with the laptop. But it was not a Logitech one. It was an HP one. Please help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383097/+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 1381968] Re: Fstrim destroys data on loopback device
Do you need any more information? Could you reproduce the bug?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1381968
Title:
Fstrim destroys data on loopback device
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
I've upgraded Ubuntu Server 12.04 LTS to 14.04 LTS.
The setup contains a loopback device (/dev/loop3) mounted into a
software raid 1 (/dev/md2).
After the weekly cronjob (/etc/cron.weekly/fstrim) ran, I've
discovered that it wiped all data on the loopback device from the
raid.
fstrim-all skips check because the loopback device is part of device mapper
raid.
if [ ${REALDEV#/dev/dm-} != $REALDEV ]; then
echo device $DEV is on devmapper, skipping TRIM feature check
Issue can be reproduced on raid setup and plain loopback mount setup!
Here is step-by-step how to reproduce the issue:
1.) create sparse image file
dd of=/sparse-file bs=1k seek=1024000
2.) losetup loopback device
losetup /dev/loop3 /sparse-file
3.) create raid1
mdadm --create /dev/md2 --auto md --level=1 --raid-devices=1 /dev/loop3
4.) create fs
mkfs.ext4 /dev/md2
4.1.) check sparse-file size
ls -lash /sparse-file
5.) mount and copy data
mount /dev/md2 /mnt
copy some random files on /mnt
5.1.) check sparse-file size again
ls -lash /sparse-file - size indicates it contains the copied data
6.) destroy loopback via fstrim
fstrim -v /mnt
7.) data is wiped
umount /mnt
ls -lash /sparse-file - size indicates that all data is wiped out!
fsck -v -f /dev/md2 - will report infinite errors on filesystem
I could not find any similiar bugreport.
Best Regards
Daniel
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381968/+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 1381815] Re: left touchpad button stopped working in 3.16.0-22.19
** Changed in: linux (Ubuntu Trusty) Status: New = Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided = High ** Changed in: linux (Ubuntu Trusty) Importance: Undecided = High ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1381815 Title: left touchpad button stopped working in 3.16.0-22.19 Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: the left touchpad button of my lenovo g50 laptop stopped working in the kernel upgrade 3.16.0-22 #29 The rest of the touchpad and the right button are still working. the previous kernel version #27 worked fine I have tried the mainline kernels and it is also affected from version 3.16.4 up to including the latest available ne 3.17.1. mainline kernel 3.16.3 works. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-22-generic 3.16.0-22.29 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jtaylor3144 F pulseaudio /dev/snd/controlC1: jtaylor3144 F pulseaudio CurrentDesktop: Unity Date: Thu Oct 16 01:39:27 2014 HibernationDevice: RESUME=UUID=86457fb1-d8f8-46e4-9ad2-c85d69ec96f7 InstallationDate: Installed on 2014-08-23 (53 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140822) MachineType: LENOVO 20351 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-22-generic N/A linux-backports-modules-3.16.0-22-generic N/A linux-firmware 1.135 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/02/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN25WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A2 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-70: dmi.product.name: 20351 dmi.product.version: Lenovo G50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381815/+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 1383138] [NEW] New BT firmware for Intel 7265 D0 chipset ROM spin
Public bug reported: Firmware for 7265 Bluetooth ROM-spin SKU is in commit 0e5f6377: commit 0e5f63771d0df6d7859f7c4100a74d737c62ac88 Author: Tedd Ho-Jeong An tedd...@intel.com Date: Thu Oct 9 08:16:05 2014 -0700 linux-firmware: Add firmware patch for Intel Bluetooth 7265 ROM-spin(D0) This patch adds new firmware patch for - Intel Wireless 7265 Bluetooth ROM-spin SKU, also known as StP D0 This patch was submitted but reverted due to patch issue. The original patch's commit id: 935b5557b1485d839748b40f5721539b54d429e1 Signed-off-by: Tedd Ho-Jeong An tedd...@intel.com Signed-off-by: Kyle McMartin k...@kernel.org ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress -- 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/1383138 Title: New BT firmware for Intel 7265 D0 chipset ROM spin Status in HWE Next Project: New Status in “linux-firmware” package in Ubuntu: In Progress Bug description: Firmware for 7265 Bluetooth ROM-spin SKU is in commit 0e5f6377: commit 0e5f63771d0df6d7859f7c4100a74d737c62ac88 Author: Tedd Ho-Jeong An tedd...@intel.com Date: Thu Oct 9 08:16:05 2014 -0700 linux-firmware: Add firmware patch for Intel Bluetooth 7265 ROM-spin(D0) This patch adds new firmware patch for - Intel Wireless 7265 Bluetooth ROM-spin SKU, also known as StP D0 This patch was submitted but reverted due to patch issue. The original patch's commit id: 935b5557b1485d839748b40f5721539b54d429e1 Signed-off-by: Tedd Ho-Jeong An tedd...@intel.com Signed-off-by: Kyle McMartin k...@kernel.org To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1383138/+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 1378663] Re: AMD Radeon R2[1002:9853] Unable to reach full screen on external monitor with fglrx
** Changed in: linux (Ubuntu) Status: Confirmed = Invalid ** Changed in: hwe-next Status: New = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1378663 Title: AMD Radeon R2[1002:9853] Unable to reach full screen on external monitor with fglrx Status in HWE Next Project: Invalid Status in “linux” package in Ubuntu: Invalid Bug description: CID: 201403-14840 Dell Inspiron 3441 The external monitor resolution cannot be set to higher than 1680x1050, or it won't be displayed on full-screen. It will have a gap between the edge of the desktop and the monitor edge. Steps: 1. Install 14.04.1 + fglrx 2. Connect to an external monitor with HDMI cable Expected result: * The desktop displayed on the external monitor should be full-screen displayed Actual result: * With resolution higer than 1680x1050, it will have a gap between the edge of the desktop and the monitor edge. ubuntu@201403-14840:~$ xrandr -q Screen 0: minimum 320 x 200, current 3200 x 1080, maximum 16384 x 16384 LVDS connected primary 1280x768+0+0 (normal left inverted right x axis y axis) 309mm x 173mm 1366x768 60.0 + 48.0 1280x768 60.0*48.0 1280x720 60.0 48.0 1024x768 60.0 48.0 800x60060.0 48.0 640x48060.0 48.0 DFP1 connected 1920x1080+1280+0 (normal left inverted right x axis y axis) 521mm x 293mm 1920x1080 60.0*+ 50.0 59.9 60.1 50.0 60.0 1776x1000 50.0 59.9 50.0 60.0 1680x1050 50.0 60.0 1400x1050 50.0 60.0 1600x900 50.0 60.0 1280x1024 50.0 75.0 60.0 1440x900 50.0 59.9 1280x960 50.0 60.0 1280x768 50.0 60.0 1280x720 60.0 50.0 59.9 1024x768 50.0 75.0 70.1 60.0 1152x648 50.0 59.9 800x60050.0 72.2 75.0 60.3 56.2 720x57659.9 50.0 720x48050.0 60.0 59.9 640x48050.0 75.0 72.8 66.6 60.0 59.9 CRT1 disconnected (normal left inverted right x axis y axis) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-36-generic 3.13.0-36.63 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1911 F pulseaudio /dev/snd/controlC0: ubuntu 1911 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Wed Oct 8 02:54:32 2014 HibernationDevice: RESUME=UUID=101b2112-3f0a-4b08-aea9-668051efacbf InstallationDate: Installed on 2014-10-08 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 3441 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed root=UUID=e1f357a4-fcde-45fc-a0b5-b785f2de7298 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-36-generic N/A linux-backports-modules-3.13.0-36-generic N/A linux-firmware 1.127.7 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/28/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: Inspiron 3441 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA01:bd04/28/2014:svnDellInc.:pnInspiron3441:pvrNotSpecified:rvnDellInc.:rnInspiron3441:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3441 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1378663/+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 1381815] Re: left touchpad button stopped working in 3.16.0-22.19
This fix is marked for stable, so we should expect this to be backported there for v3.13 shortly. I will look at getting this into Utopic before release. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1381815 Title: left touchpad button stopped working in 3.16.0-22.19 Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: the left touchpad button of my lenovo g50 laptop stopped working in the kernel upgrade 3.16.0-22 #29 The rest of the touchpad and the right button are still working. the previous kernel version #27 worked fine I have tried the mainline kernels and it is also affected from version 3.16.4 up to including the latest available ne 3.17.1. mainline kernel 3.16.3 works. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-22-generic 3.16.0-22.29 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jtaylor3144 F pulseaudio /dev/snd/controlC1: jtaylor3144 F pulseaudio CurrentDesktop: Unity Date: Thu Oct 16 01:39:27 2014 HibernationDevice: RESUME=UUID=86457fb1-d8f8-46e4-9ad2-c85d69ec96f7 InstallationDate: Installed on 2014-08-23 (53 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140822) MachineType: LENOVO 20351 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-22-generic N/A linux-backports-modules-3.16.0-22-generic N/A linux-firmware 1.135 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/02/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN25WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A2 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-70: dmi.product.name: 20351 dmi.product.version: Lenovo G50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381815/+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 1383157] [NEW] [Lenovo T440p] New Trackpad: middle button with TrackPoint are not able to perform scroll
Public bug reported: Accroding to bug #1294515 , this feature should be included. Fail to scroll content with trackpoint and middle button. Steps to reproduce: 1. hold the middle button (should be on center-top area, since it's button-less touchpad) 2. move the trackpoint Actual results: nothing move, tried using xev to capture information but nothing return. Expected result: Content/page should scroll as TrackPoint move around. - Additoinal Information: ubuntu@201307-13930:~$ xinput --list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPadid=10 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Integrated Camera id=8[slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=9[slave keyboard (3)] ↳ ThinkPad Extra Buttonsid=12 [slave keyboard (3)] ubuntu@201307-13930:~$ xinput --list-props 11 Device 'TPPS/2 IBM TrackPoint': Device Enabled (136): 1 Coordinate Transformation Matrix (138):1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (260):0 Device Accel Constant Deceleration (261): 1.00 Device Accel Adaptive Deceleration (262): 1.00 Device Accel Velocity Scaling (263): 10.00 Device Product ID (254): 2, 10 Device Node (255): /dev/input/event4 Evdev Axis Inversion (301):0, 0 Evdev Axes Swap (303): 0 Axis Labels (304): Rel X (146), Rel Y (147) Button Labels (305): Button Left (139), Button Middle (140), Button Right (141), Button Wheel Up (142), Button Wheel Down (143), Button Horiz Wheel Left (144), Button Horiz Wheel Right (145) Evdev Scrolling Distance (306):0, 0, 0 Evdev Middle Button Emulation (307): 0 Evdev Middle Button Timeout (308): 50 Evdev Third Button Emulation (309):0 Evdev Third Button Emulation Timeout (310):1000 Evdev Third Button Emulation Button (311): 3 Evdev Third Button Emulation Threshold (312): 20 Evdev Wheel Emulation (313): 1 Evdev Wheel Emulation Axes (314): 6, 7, 4, 5 Evdev Wheel Emulation Inertia (315): 10 Evdev Wheel Emulation Timeout (316): 200 Evdev Wheel Emulation Button (317):2 Evdev Drag Lock Buttons (318): 0 - ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-23-generic 3.16.0-23.30 ProcVersionSignature: Ubuntu 3.16.0-23.30-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2066 F pulseaudio /dev/snd/controlC0: ubuntu 2066 F pulseaudio CurrentDesktop: Unity Date: Mon Oct 20 03:43:58 2014 HibernationDevice: RESUME=UUID=ef079530-e68a-45a8-95b6-84a3dd18dfd6 InstallationDate: Installed on 2014-10-20 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017) MachineType: LENOVO 20ANZ039US ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=fe4fceda-a7bb-4159-a6b0-84357353090c ro rootdelay=60 quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-23-generic N/A linux-backports-modules-3.16.0-23-generic N/A linux-firmware 1.136 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/24/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GLET21WW (0.21) dmi.board.asset.tag: Not Available dmi.board.name: 20ANZ039US dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET21WW(0.21):bd05/24/2013:svnLENOVO:pn20ANZ039US:pvrThinkPadT440p:rvnLENOVO:rn20ANZ039US:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ANZ039US dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO ** Affects: xserver-xorg-input-synaptics (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: 201307-13930 amd64 apport-bug taipei-lab utopic ** Package changed: linux (Ubuntu) = xserver-xorg-input-synaptics (Ubuntu) ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Status: New = Confirmed ** Tags added: 201307-13930 taipei-lab ** Description changed: + Accroding to bug #1294515 , this feature should be included. + + Fail to scroll content with trackpoint and
[Kernel-packages] [Bug 1354975] Re: iwlwifi Intel 7260 Wifi disconnects
still have disconnections, no matter which kind of network ... -- 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/1354975 Title: iwlwifi Intel 7260 Wifi disconnects Status in Unity Linux: New Status in “linux-firmware” package in Ubuntu: Fix Released Bug description: I experience frequent disconnects and auth issues, never more than 30 minutes without a disconnect. Sometimes dozens of disconnects in a few minutes. This happens with the default 7260-8 firmware. Tried replacing the -8 with -9 ucode. Failed to load due to API version. This loaded the -7 driver which seems to be more stable. Tested against 2.4ghz APs (Apple, Netgear, Linksys). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 2577 F pulseaudio /dev/snd/controlC1: steve 2577 F pulseaudio CurrentDesktop: Unity Date: Sun Aug 10 17:49:06 2014 HibernationDevice: RESUME=UUID=374a0c1c-4ac2-456b-a67e-9ea54fe11fe6 InstallationDate: Installed on 2013-12-28 (225 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 12-9Q33 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=58deb355-7a09-440b-ade2-69a84fd74460 ro ipv6.disable=1 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-07-06 (35 days ago) dmi.bios.date: 05/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA00:bd05/06/2013:svnDellInc.:pnXPS12-9Q33:pvrA00:rvnDellInc.:rnXPS12-9Q33:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/unitylinux/+bug/1354975/+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 1041790]
*** Bug 85194 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1041790 Title: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0 Status in X.org xf86-video-intel: In Progress Status in “linux” package in Ubuntu: Incomplete Status in “sandybridge-meta” package in Ubuntu: Confirmed 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 1383184] [NEW] Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported
Public bug reported: Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported Status in “linux” package in Ubuntu: New Bug description: Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/+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 1383184] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1383184 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported Status in “linux” package in Ubuntu: Incomplete Bug description: Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/+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 1381815] Re: left touchpad button stopped working in 3.16.0-22.19
Ok I have produced some 14.10 (utopic) kernels with this proposed fix applied. If someone could urgently test these and report back we should be able to get this into the release. Kernels are at the URL below: http://people.canonical.com/~apw/lp1381815-utopic/ Please report any testing back here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1381815 Title: left touchpad button stopped working in 3.16.0-22.19 Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: the left touchpad button of my lenovo g50 laptop stopped working in the kernel upgrade 3.16.0-22 #29 The rest of the touchpad and the right button are still working. the previous kernel version #27 worked fine I have tried the mainline kernels and it is also affected from version 3.16.4 up to including the latest available ne 3.17.1. mainline kernel 3.16.3 works. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-22-generic 3.16.0-22.29 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jtaylor3144 F pulseaudio /dev/snd/controlC1: jtaylor3144 F pulseaudio CurrentDesktop: Unity Date: Thu Oct 16 01:39:27 2014 HibernationDevice: RESUME=UUID=86457fb1-d8f8-46e4-9ad2-c85d69ec96f7 InstallationDate: Installed on 2014-08-23 (53 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140822) MachineType: LENOVO 20351 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-22-generic N/A linux-backports-modules-3.16.0-22-generic N/A linux-firmware 1.135 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/02/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN25WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A2 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-70: dmi.product.name: 20351 dmi.product.version: Lenovo G50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381815/+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 1065400] Re: Support for loading Broadcom bluetooth firmware
@tephraim: For Utopic, the upstream patch mentioned in #119 is already merged, which means the path and filename of the firmware are changed. The firmware file must be saved as something like /lib/firmware/brcm/BCM43142A0-vid-pid.hcd instead. Please try 'dmesg | grep Bluetooth' and see if there's an error message indicating firmware missing. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1065400 Title: Support for loading Broadcom bluetooth firmware Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Status in “linux” source package in Saucy: Fix Released Bug description: Broadcom bluetooth chips require a tool called patchram uploader [1] to load firmware. This applies to at least BCM20702 and BCM43142. Although some of the devices have an OTPROM that contains required firmware, but it is found that these devices would not have HFP/HSP support unless a upgraded firmware is loaded via patchram uploader. This tool requires hci device to do the firmware loading, but this may cause some race condition between patchram tool and bluetoothd or something that also works on hci interface. Also it needs some hooks to make firmware loads after bootup, s3, s4, rfkill, and device hotplug events. Implement this loader in kernel module would make things more easier. [1] http://marc.info/?l=linux-bluetoothm=132039175324993w=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065400/+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 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported
apport information ** Tags added: apport-collected trusty ** Description changed: Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] - This is on a fully updated Ubuntu Server 14.04 installation, with the - ubuntu-desktop environment installed. This happened in order to get the - md raid drivers for raid0 on my system, as the desktop version doesn't - support them. + This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. + --- + ApportVersion: 2.14.1-0ubuntu3.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: matanis2333 F pulseaudio + /dev/snd/controlC0: matanis2333 F pulseaudio + CRDA: Error: [Errno 2] No such file or directory + CurrentDesktop: Unity + DistroRelease: Ubuntu 14.04 + HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 + InstallationDate: Installed on 2014-10-16 (3 days ago) + InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.3) + IwConfig: + p2p1 no wireless extensions. + + lono wireless extensions. + MachineType: Micro-Star International Co., Ltd. GT72 2QE + NonfreeKernelModules: nvidia + Package: linux (not installed) + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro + ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 + RelatedPackageVersions: + linux-restricted-modules-3.13.0-37-generic N/A + linux-backports-modules-3.13.0-37-generic N/A + linux-firmware 1.127.7 + RfKill: + + Tags: trusty + Uname: Linux 3.13.0-37-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 09/15/2014 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: E1781IMS.10D + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: MS-1781 + dmi.board.vendor: Micro-Star International Co., Ltd. + dmi.board.version: REV:0.C + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: To Be Filled By O.E.M. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: + dmi.product.name: GT72 2QE + dmi.product.version: REV:0.C + dmi.sys.vendor: Micro-Star International Co., Ltd. ** Attachment added: AlsaInfo.txt https://bugs.launchpad.net/bugs/1383184/+attachment/4240501/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported Status in “linux” package in Ubuntu: Confirmed Bug description: Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014
[Kernel-packages] [Bug 1383184] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1383184/+attachment/4240506/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported Status in “linux” package in Ubuntu: Confirmed Bug description: Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/+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 1383184] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1383184/+attachment/4240509/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported Status in “linux” package in Ubuntu: Confirmed Bug description: Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/+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 1383184] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1383184/+attachment/4240502/+files/BootDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported Status in “linux” package in Ubuntu: Confirmed Bug description: Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/+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 1383184] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1383184/+attachment/4240505/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported Status in “linux” package in Ubuntu: Confirmed Bug description: Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/+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 1383184] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1383184/+attachment/4240508/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported Status in “linux” package in Ubuntu: Confirmed Bug description: Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/+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 1383184] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1383184/+attachment/4240503/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported Status in “linux” package in Ubuntu: Confirmed Bug description: Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/+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 1383184] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1383184/+attachment/4240513/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported Status in “linux” package in Ubuntu: Confirmed Bug description: Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/+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 1383184] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1383184/+attachment/4240507/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported Status in “linux” package in Ubuntu: Confirmed Bug description: Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/+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 1383184] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/1383184/+attachment/4240510/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported Status in “linux” package in Ubuntu: Confirmed Bug description: Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/+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 1383184] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1383184/+attachment/4240512/+files/UdevLog.txt ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported Status in “linux” package in Ubuntu: Confirmed Bug description: Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/+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 1383184] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1383184/+attachment/4240511/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported Status in “linux” package in Ubuntu: Confirmed Bug description: Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/+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 1383184] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1383184/+attachment/4240504/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported Status in “linux” package in Ubuntu: Confirmed Bug description: Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/+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 1065400] Re: Support for loading Broadcom bluetooth firmware
Thx for the answer. Sadly, there is no indication of a missing firmware :(. [ 29.980043] Bluetooth: Core ver 2.19 [ 29.980058] Bluetooth: HCI device and connection manager initialized [ 29.980064] Bluetooth: HCI socket layer initialized [ 29.980066] Bluetooth: L2CAP socket layer initialized [ 29.980073] Bluetooth: SCO socket layer initialized [ 32.874973] Bluetooth: RFCOMM TTY layer initialized [ 32.874984] Bluetooth: RFCOMM socket layer initialized [ 32.874997] Bluetooth: RFCOMM ver 1.11 [ 33.702638] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 33.702641] Bluetooth: BNEP filters: protocol multicast [ 33.702649] Bluetooth: BNEP socket layer initialized [ 4216.638384] Bluetooth: hci0 urb 8800c5e09600 failed to resubmit (2) And anyway, in my case it should be a BCM20802A0 can I place the working firmware at /lib/firmware/brcm/ and hope it will be picked? What naming do I need to take care of? Currently the file is called, BCM20702A0_001.001.024.0156.0204.hex, which I do download by bcmfwup.py to make my bluetooth work. Any hints? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1065400 Title: Support for loading Broadcom bluetooth firmware Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Status in “linux” source package in Saucy: Fix Released Bug description: Broadcom bluetooth chips require a tool called patchram uploader [1] to load firmware. This applies to at least BCM20702 and BCM43142. Although some of the devices have an OTPROM that contains required firmware, but it is found that these devices would not have HFP/HSP support unless a upgraded firmware is loaded via patchram uploader. This tool requires hci device to do the firmware loading, but this may cause some race condition between patchram tool and bluetoothd or something that also works on hci interface. Also it needs some hooks to make firmware loads after bootup, s3, s4, rfkill, and device hotplug events. Implement this loader in kernel module would make things more easier. [1] http://marc.info/?l=linux-bluetoothm=132039175324993w=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065400/+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 1379244] Re: linux: 3.13.0-38.65 -proposed tracker
** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) = Yung Shen (kaxing) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1379244 Title: linux: 3.13.0-38.65 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.13.0-38.65 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Thursday, 09. October 2014 09:27 UTC kernel-stable-Prepare-package-end:Thursday, 09. October 2014 18:06 UTC kernel-stable-Promote-to-proposed-start:Thursday, 09. October 2014 18:06 UTC ppa-package-testing-start:Thursday, 09. October 2014 18:06 UTC kernel-stable-Promote-to-proposed-end:Friday, 10. October 2014 18:28 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Friday, 10. October 2014 20:01 UTC kernel-stable-Verification-testing-start:Friday, 10. October 2014 20:01 UTC kernel-stable-Certification-testing-start:Friday, 10. October 2014 20:01 UTC kernel-stable-Security-signoff-start:Friday, 10. October 2014 20:02 UTC kernel-stable-Regression-testing-start:Friday, 10. October 2014 20:02 UTC kernel-stable-Regression-testing-end:Wednesday, 15. October 2014 08:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1379244/+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 1376245] Re: remove_proc_entry+0x139/0x1b0() -- name 'fs/nfsfs'
If it helps: The very first of those kernel stack traces has a slightly different message: [49237.227779] [ cut here ] [49237.227787] WARNING: CPU: 2 PID: 24871 at /build/buildd/linux-3.13.0/fs/proc/generic.c:522 remove_proc_entry+0x19f/0x1b0() [49237.227789] remove_proc_entry: removing non-empty directory 'fs/nfsfs', leaking at least 'volumes' [49237.227790] Modules linked in: [...] The rest is the same as already posted here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1376245 Title: remove_proc_entry+0x139/0x1b0() -- name 'fs/nfsfs' Status in “linux” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04 amd64 ii linux-image-3.13.0-37-generic 3.13.0-37.64amd64Linux kernel image for version 3.13.0 on 64 bit x86 SMP sloeuillet@SLoeuillet-DE107:/sfr$ uname -a Linux SLoeuillet-DE107 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Today, I encountered 2 quite identical stack traces in my dmesg, related to nfs : [368973.412120] WARNING: CPU: 1 PID: 15607 at /build/buildd/linux-3.13.0/fs/proc/generic.c:511 remove_proc_entry+0x139/0x1b0() [368973.412122] name 'fs/nfsfs' [368973.412123] Modules linked in: cdc_acm nfsv3 rpcsec_gss_krb5 8021q garp stp mrp llc cuse bnep rfcomm bluetooth nfsv4 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc binfmt_misc fscache hp_wmi sparse_keymap snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep snd_pcm radeon snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq sp5100_tco snd_seq_device serio_raw snd_timer ttm drm_kms_helper snd kvm edac_core soundcore drm edac_mce_amd k8temp i2c_algo_bit i2c_piix4 tpm_infineon shpchp wmi mac_hid parport_pc ppdev lp parport hid_generic usbhid hid tg3 psmouse ptp pps_core floppy ahci libahci [368973.412164] CPU: 1 PID: 15607 Comm: kworker/u8:1 Tainted: GW 3.13.0-37-generic #64-Ubuntu [368973.412166] Hardware name: Hewlett-Packard HP Compaq dc5850 Small Form Factor/3029h, BIOS 786F6 v03.14 11/15/2011 [368973.412171] Workqueue: netns cleanup_net [368973.412172] 0009 88006a875c80 8171ed09 88006a875cc8 [368973.412176] 88006a875cb8 8106773d 0005 [368973.412179] a05168a8 88011b418b30 0100 88006a875d18 [368973.412182] Call Trace: [368973.412188] [8171ed09] dump_stack+0x45/0x56 [368973.412192] [8106773d] warn_slowpath_common+0x7d/0xa0 [368973.412195] [810677ac] warn_slowpath_fmt+0x4c/0x50 [368973.412198] [81229839] remove_proc_entry+0x139/0x1b0 [368973.412217] [a04f64e2] nfs_fs_proc_net_exit+0x62/0x70 [nfs] [368973.412225] [a04fc5b2] nfs_net_exit+0x12/0x20 [nfs] [368973.412228] [8161b409] ops_exit_list.isra.1+0x39/0x60 [368973.412231] [8161bc90] cleanup_net+0x110/0x250 [368973.412235] [810839c2] process_one_work+0x182/0x450 [368973.412237] [810847b1] worker_thread+0x121/0x410 [368973.412240] [81084690] ? rescuer_thread+0x430/0x430 [368973.412243] [8108b492] kthread+0xd2/0xf0 [368973.412246] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 [368973.412249] [8172f77c] ret_from_fork+0x7c/0xb0 [368973.412251] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 [368973.412253] ---[ end trace bb78fe56a3dcb678 ]--- [368973.448199] WARNING: CPU: 1 PID: 15607 at /build/buildd/linux-3.13.0/fs/proc/generic.c:511 remove_proc_entry+0x139/0x1b0() [368973.448201] name 'fs/nfsfs' [368973.448203] Modules linked in: cdc_acm nfsv3 rpcsec_gss_krb5 8021q garp stp mrp llc cuse bnep rfcomm bluetooth nfsv4 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc binfmt_misc fscache hp_wmi sparse_keymap snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep snd_pcm radeon snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq sp5100_tco snd_seq_device serio_raw snd_timer ttm drm_kms_helper snd kvm edac_core soundcore drm edac_mce_amd k8temp i2c_algo_bit i2c_piix4 tpm_infineon shpchp wmi mac_hid parport_pc ppdev lp parport hid_generic usbhid hid tg3 psmouse ptp pps_core floppy ahci libahci [368973.448250] CPU: 1 PID: 15607 Comm: kworker/u8:1 Tainted: GW 3.13.0-37-generic #64-Ubuntu [368973.448252] Hardware name: Hewlett-Packard HP Compaq dc5850 Small Form Factor/3029h, BIOS 786F6 v03.14 11/15/2011 [368973.448257] Workqueue: netns cleanup_net [368973.448259] 0009 88006a875c80 8171ed09 88006a875cc8 [368973.448263] 88006a875cb8 8106773d 0005 [368973.448265] a05168a8 88011b418b30 0100 88006a875d18 [368973.448268] Call Trace: [368973.448275]
[Kernel-packages] [Bug 1373552] Re: iwlwifi problem causes repeated disconnections to wireless network
** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Seth Forshee (sforshee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1373552 Title: iwlwifi problem causes repeated disconnections to wireless network Status in “linux” package in Ubuntu: Confirmed Bug description: After having iwlwifi problems of constant disconnections every 30 or so minutes, I tried going to http://wireless.kernel.org/en/users/Drivers/iwlwifi to install the latest Intel® Wireless 7260 firmware for my kernel version at /lib/firmware, having only the -8 or -7 version in that directory, restarting my computer, and reinstalling the linux-firmware 1.127.6 package. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-34-generic 3.13.0-34.60 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ely7217 F pulseaudio CurrentDesktop: X-Cinnamon Date: Wed Sep 24 13:53:59 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-26 (60 days ago) InstallationMedia: Linux Mint 17 Qiana - Release amd64 20140624 MachineType: Dell Inc. Inspiron 5520 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=d138850f-7993-493e-9130-0da1070c29b8 ro quiet splash resume=/dev/mapper/Data+Swap-Swap vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-34-generic N/A linux-backports-modules-3.13.0-34-generic N/A linux-firmware 1.127.6 SourcePackage: linux StagingDrivers: rts5139 zram UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: Sep 24 13:42:44 Karasu-Laptop kernel: [ 8117.443248] systemd-hostnamed[21228]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname! dmi.bios.date: 10/03/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 04G65K dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A11 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd10/03/2012:svnDellInc.:pnInspiron5520:pvrA11:rvnDellInc.:rn04G65K:rvrA00:cvnDellInc.:ct8:cvrA11: dmi.product.name: Inspiron 5520 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1373552/+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 1383138] Re: New BT firmware for Intel 7265 D0 chipset ROM spin
** Also affects: linux-firmware (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Utopic) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Changed in: linux-firmware (Ubuntu Utopic) Status: In Progress = Fix Released ** Changed in: linux-firmware (Ubuntu Trusty) Status: New = In Progress ** Changed in: linux-firmware (Ubuntu Trusty) Assignee: (unassigned) = Jesse Sung (wenchien) -- 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/1383138 Title: New BT firmware for Intel 7265 D0 chipset ROM spin Status in HWE Next Project: New Status in “linux-firmware” package in Ubuntu: Fix Released Status in “linux-firmware” source package in Trusty: In Progress Status in “linux-firmware” source package in Utopic: Fix Released Bug description: Firmware for 7265 Bluetooth ROM-spin SKU is in commit 0e5f6377: commit 0e5f63771d0df6d7859f7c4100a74d737c62ac88 Author: Tedd Ho-Jeong An tedd...@intel.com Date: Thu Oct 9 08:16:05 2014 -0700 linux-firmware: Add firmware patch for Intel Bluetooth 7265 ROM-spin(D0) This patch adds new firmware patch for - Intel Wireless 7265 Bluetooth ROM-spin SKU, also known as StP D0 This patch was submitted but reverted due to patch issue. The original patch's commit id: 935b5557b1485d839748b40f5721539b54d429e1 Signed-off-by: Tedd Ho-Jeong An tedd...@intel.com Signed-off-by: Kyle McMartin k...@kernel.org To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1383138/+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 1377878] [NEW] PPC - GUI freezes except for mouse pointer
You have been subscribed to a public bug: During the installation the computer freezes completely except for the mouse pointer. And even that is stuck with whatever shape it happened to have at the time it froze. The steps I have to cause the freeze are run Ubiquity to start the installation open a terminal, run Ubuntu-bug and let it launch Firefox. It will freeze every time then. Even the consoles (ctrl-alt-f1 etc) are unavailable. What kind of information can I collect and how? ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: iso-testing lubuntu ppc -- PPC - GUI freezes except for mouse pointer https://bugs.launchpad.net/bugs/1377878 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1383138] Re: New BT firmware for Intel 7265 D0 chipset ROM spin
** Changed in: linux-firmware (Ubuntu Trusty) Status: In Progress = Fix Committed -- 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/1383138 Title: New BT firmware for Intel 7265 D0 chipset ROM spin Status in HWE Next Project: New Status in “linux-firmware” package in Ubuntu: Fix Released Status in “linux-firmware” source package in Trusty: Fix Committed Status in “linux-firmware” source package in Utopic: Fix Released Bug description: Firmware for 7265 Bluetooth ROM-spin SKU is in commit 0e5f6377: commit 0e5f63771d0df6d7859f7c4100a74d737c62ac88 Author: Tedd Ho-Jeong An tedd...@intel.com Date: Thu Oct 9 08:16:05 2014 -0700 linux-firmware: Add firmware patch for Intel Bluetooth 7265 ROM-spin(D0) This patch adds new firmware patch for - Intel Wireless 7265 Bluetooth ROM-spin SKU, also known as StP D0 This patch was submitted but reverted due to patch issue. The original patch's commit id: 935b5557b1485d839748b40f5721539b54d429e1 Signed-off-by: Tedd Ho-Jeong An tedd...@intel.com Signed-off-by: Kyle McMartin k...@kernel.org To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1383138/+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 1377878] Re: PPC - GUI freezes except for mouse pointer
FWIW, when I've complained in the past about endian issues with the radeon drivers on PPC, the upstream response has often been we know it's broken on big-endian arches, patches welcome, or go buy an nvidia card. So, this may prove to be a lost cause without someone with the time and expertise to dive in. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1377878 Title: PPC - GUI freezes except for mouse pointer Status in “linux” package in Ubuntu: Confirmed Bug description: During the installation the computer freezes completely except for the mouse pointer. And even that is stuck with whatever shape it happened to have at the time it froze. The steps I have to cause the freeze are run Ubiquity to start the installation open a terminal, run Ubuntu-bug and let it launch Firefox. It will freeze every time then. Even the consoles (ctrl-alt-f1 etc) are unavailable. What kind of information can I collect and how? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377878/+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 1377878] Re: PPC - GUI freezes except for mouse pointer
Based on the syslog vomit, this is almost certainly a kernel bug (or possibly an X bug). Reassigning in that direction for now. ** Package changed: ubiquity (Ubuntu) = linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1377878 Title: PPC - GUI freezes except for mouse pointer Status in “linux” package in Ubuntu: Confirmed Bug description: During the installation the computer freezes completely except for the mouse pointer. And even that is stuck with whatever shape it happened to have at the time it froze. The steps I have to cause the freeze are run Ubiquity to start the installation open a terminal, run Ubuntu-bug and let it launch Firefox. It will freeze every time then. Even the consoles (ctrl-alt-f1 etc) are unavailable. What kind of information can I collect and how? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377878/+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 1220146] Re: Ralink Mediatek 14c3:7630 wi-fi card isn't supported out of the box
For kernel Ver 3.16 and later, i found some workin solution only to install the kernel module. All you have to do is just download the GIT repo https://github.com/lwfinger/mt7630 and do $ cd into the extracted dir $ sudo make $ sudo make install Eventhough it installs the kernel module, it still needs some modification as it cannot connect to a AP. -Hope someone will look into this... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1220146 Title: Ralink Mediatek 14c3:7630 wi-fi card isn't supported out of the box Status in HWE Next Project: Confirmed Status in HWE Next trusty series: Confirmed Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Triaged Status in “linux” package in Fedora: New Bug description: This device is appearing in some OEM machines, but driver is not yet available in mainline. The driver seems to be present in machines with pre-installed OS, but isn't available on the download-and-install versions! To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1220146/+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 1371591] Re: file not initialized to 0s under some conditions
** Description changed: + SRU Justification: + + [Impact] + Under some conditions, after fallocate() the file is observed not to be completely initilized to 0s: some 4KB pages have left-over data from previous files that occupied those pages. Note that in addition to causing functional problems for applications expecting files to be initialized to 0s, this is a security issue because it allows data to leak from one file to another, bypassing file access controls. The problem has been seen running under the following VMWare-based virtual environments: Fusion 6.0.2 ESXi 5.1.0 And under the following versions of Ubuntu: Ubuntu 12.04, 3.11.0-26-generic Ubuntu 14.04.1, 3.13.0-32-generic Ubuntu 14.04.1, 3.13.0-35-generic But did not reproduce under the following version: Ubuntu 10.04, 2.6.32-38-server The problem reproduced under LVM, but did not reproduce without LVM. + + [Test Case] I reproduced the problem as follows under VMWare Fusion: set up custom VM with default disk size (20 GB) and memory size (1 GB) attach Ubuntu 14.04.1 ISO to CDROM, set it as boot device, boot up select all defaults during installation _including_ LVM install gcc unpack the attached repro.tgz run repro.sh what it does: * fills the disk with a file containing bytes of 0xcc then deletes it * repeatedly runs the repro program which creates two files and accesses them in a certain pattern * checks the file f0 with hexdump; it should contain all 0s, but if pages 0x1000-0x7000 contain 0xcc you have reproduced the problem If the problem does not appear to reproduce, please try waiting a bit and checking the f0 files with hexdump again. This behavior was observed by a customer reproducing the problem under ESXi. I since added an sync after the running the repro binary which I think will fix that. If you still can't reproduce the problem please let me know if there's anything I can do to help. For example can we trace the disk accesses at the SCSI level to verify whether the appropriate SCSI commands are being sent? This may help determine whether the problem is in Linux or in VMWare. + + [Fix] + + mptfusion: enable no_write_same in scsi_host_template + commit 4089b71cc820a426d601283c92fcd4ffeb5139c2 upstream + + https://lkml.org/lkml/2014/9/25/482 + + (Note this patch may be reverted in the future as there is active + discussion upstream about a more generic 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/1371591 Title: file not initialized to 0s under some conditions Status in “linux” package in Ubuntu: Fix Committed Status in “linux-lts-trusty” package in Ubuntu: Confirmed Status in “linux” source package in Precise: Invalid Status in “linux-lts-trusty” source package in Precise: Triaged Status in “linux” source package in Trusty: Fix Committed Status in “linux-lts-trusty” source package in Trusty: Invalid Bug description: SRU Justification: [Impact] Under some conditions, after fallocate() the file is observed not to be completely initilized to 0s: some 4KB pages have left-over data from previous files that occupied those pages. Note that in addition to causing functional problems for applications expecting files to be initialized to 0s, this is a security issue because it allows data to leak from one file to another, bypassing file access controls. The problem has been seen running under the following VMWare-based virtual environments: Fusion 6.0.2 ESXi 5.1.0 And under the following versions of Ubuntu: Ubuntu 12.04, 3.11.0-26-generic Ubuntu 14.04.1, 3.13.0-32-generic Ubuntu 14.04.1, 3.13.0-35-generic But did not reproduce under the following version: Ubuntu 10.04, 2.6.32-38-server The problem reproduced under LVM, but did not reproduce without LVM. [Test Case] I reproduced the problem as follows under VMWare Fusion: set up custom VM with default disk size (20 GB) and memory size (1 GB) attach Ubuntu 14.04.1 ISO to CDROM, set it as boot device, boot up select all defaults during installation _including_ LVM install gcc unpack the attached repro.tgz run repro.sh what it does: * fills the disk with a file containing bytes of 0xcc then deletes it * repeatedly runs the repro program which creates two files and accesses them in a certain pattern * checks the file f0 with hexdump; it should contain all 0s, but if pages 0x1000-0x7000 contain 0xcc you have reproduced the problem If the problem does not appear to reproduce, please try waiting a bit and checking the f0 files with hexdump again. This behavior was observed by a customer reproducing the problem under ESXi. I since added an sync after the running the repro binary which I think will fix that. If you still can't reproduce the problem please let me know if there's
[Kernel-packages] [Bug 1376245] Re: remove_proc_entry+0x139/0x1b0() -- name 'fs/nfsfs'
Although it should come sooner or later via stable, if people want to test ahead of that I put kernel images with the anticipated fix at http://people.canonical.com/~smb/lp1376245/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1376245 Title: remove_proc_entry+0x139/0x1b0() -- name 'fs/nfsfs' Status in “linux” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04 amd64 ii linux-image-3.13.0-37-generic 3.13.0-37.64amd64Linux kernel image for version 3.13.0 on 64 bit x86 SMP sloeuillet@SLoeuillet-DE107:/sfr$ uname -a Linux SLoeuillet-DE107 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Today, I encountered 2 quite identical stack traces in my dmesg, related to nfs : [368973.412120] WARNING: CPU: 1 PID: 15607 at /build/buildd/linux-3.13.0/fs/proc/generic.c:511 remove_proc_entry+0x139/0x1b0() [368973.412122] name 'fs/nfsfs' [368973.412123] Modules linked in: cdc_acm nfsv3 rpcsec_gss_krb5 8021q garp stp mrp llc cuse bnep rfcomm bluetooth nfsv4 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc binfmt_misc fscache hp_wmi sparse_keymap snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep snd_pcm radeon snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq sp5100_tco snd_seq_device serio_raw snd_timer ttm drm_kms_helper snd kvm edac_core soundcore drm edac_mce_amd k8temp i2c_algo_bit i2c_piix4 tpm_infineon shpchp wmi mac_hid parport_pc ppdev lp parport hid_generic usbhid hid tg3 psmouse ptp pps_core floppy ahci libahci [368973.412164] CPU: 1 PID: 15607 Comm: kworker/u8:1 Tainted: GW 3.13.0-37-generic #64-Ubuntu [368973.412166] Hardware name: Hewlett-Packard HP Compaq dc5850 Small Form Factor/3029h, BIOS 786F6 v03.14 11/15/2011 [368973.412171] Workqueue: netns cleanup_net [368973.412172] 0009 88006a875c80 8171ed09 88006a875cc8 [368973.412176] 88006a875cb8 8106773d 0005 [368973.412179] a05168a8 88011b418b30 0100 88006a875d18 [368973.412182] Call Trace: [368973.412188] [8171ed09] dump_stack+0x45/0x56 [368973.412192] [8106773d] warn_slowpath_common+0x7d/0xa0 [368973.412195] [810677ac] warn_slowpath_fmt+0x4c/0x50 [368973.412198] [81229839] remove_proc_entry+0x139/0x1b0 [368973.412217] [a04f64e2] nfs_fs_proc_net_exit+0x62/0x70 [nfs] [368973.412225] [a04fc5b2] nfs_net_exit+0x12/0x20 [nfs] [368973.412228] [8161b409] ops_exit_list.isra.1+0x39/0x60 [368973.412231] [8161bc90] cleanup_net+0x110/0x250 [368973.412235] [810839c2] process_one_work+0x182/0x450 [368973.412237] [810847b1] worker_thread+0x121/0x410 [368973.412240] [81084690] ? rescuer_thread+0x430/0x430 [368973.412243] [8108b492] kthread+0xd2/0xf0 [368973.412246] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 [368973.412249] [8172f77c] ret_from_fork+0x7c/0xb0 [368973.412251] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 [368973.412253] ---[ end trace bb78fe56a3dcb678 ]--- [368973.448199] WARNING: CPU: 1 PID: 15607 at /build/buildd/linux-3.13.0/fs/proc/generic.c:511 remove_proc_entry+0x139/0x1b0() [368973.448201] name 'fs/nfsfs' [368973.448203] Modules linked in: cdc_acm nfsv3 rpcsec_gss_krb5 8021q garp stp mrp llc cuse bnep rfcomm bluetooth nfsv4 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc binfmt_misc fscache hp_wmi sparse_keymap snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep snd_pcm radeon snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq sp5100_tco snd_seq_device serio_raw snd_timer ttm drm_kms_helper snd kvm edac_core soundcore drm edac_mce_amd k8temp i2c_algo_bit i2c_piix4 tpm_infineon shpchp wmi mac_hid parport_pc ppdev lp parport hid_generic usbhid hid tg3 psmouse ptp pps_core floppy ahci libahci [368973.448250] CPU: 1 PID: 15607 Comm: kworker/u8:1 Tainted: GW 3.13.0-37-generic #64-Ubuntu [368973.448252] Hardware name: Hewlett-Packard HP Compaq dc5850 Small Form Factor/3029h, BIOS 786F6 v03.14 11/15/2011 [368973.448257] Workqueue: netns cleanup_net [368973.448259] 0009 88006a875c80 8171ed09 88006a875cc8 [368973.448263] 88006a875cb8 8106773d 0005 [368973.448265] a05168a8 88011b418b30 0100 88006a875d18 [368973.448268] Call Trace: [368973.448275] [8171ed09] dump_stack+0x45/0x56 [368973.448279] [8106773d] warn_slowpath_common+0x7d/0xa0 [368973.448283] [810677ac] warn_slowpath_fmt+0x4c/0x50 [368973.448286] [81229839] remove_proc_entry+0x139/0x1b0 [368973.448313] [a04f64e2]
[Kernel-packages] [Bug 1371591] Re: file not initialized to 0s under some conditions
Verified in my trusty VM. ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty ** Changed in: linux (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371591 Title: file not initialized to 0s under some conditions Status in “linux” package in Ubuntu: Fix Released Status in “linux-lts-trusty” package in Ubuntu: Confirmed Status in “linux” source package in Precise: Invalid Status in “linux-lts-trusty” source package in Precise: Triaged Status in “linux” source package in Trusty: Fix Committed Status in “linux-lts-trusty” source package in Trusty: Invalid Bug description: SRU Justification: [Impact] Under some conditions, after fallocate() the file is observed not to be completely initilized to 0s: some 4KB pages have left-over data from previous files that occupied those pages. Note that in addition to causing functional problems for applications expecting files to be initialized to 0s, this is a security issue because it allows data to leak from one file to another, bypassing file access controls. The problem has been seen running under the following VMWare-based virtual environments: Fusion 6.0.2 ESXi 5.1.0 And under the following versions of Ubuntu: Ubuntu 12.04, 3.11.0-26-generic Ubuntu 14.04.1, 3.13.0-32-generic Ubuntu 14.04.1, 3.13.0-35-generic But did not reproduce under the following version: Ubuntu 10.04, 2.6.32-38-server The problem reproduced under LVM, but did not reproduce without LVM. [Test Case] I reproduced the problem as follows under VMWare Fusion: set up custom VM with default disk size (20 GB) and memory size (1 GB) attach Ubuntu 14.04.1 ISO to CDROM, set it as boot device, boot up select all defaults during installation _including_ LVM install gcc unpack the attached repro.tgz run repro.sh what it does: * fills the disk with a file containing bytes of 0xcc then deletes it * repeatedly runs the repro program which creates two files and accesses them in a certain pattern * checks the file f0 with hexdump; it should contain all 0s, but if pages 0x1000-0x7000 contain 0xcc you have reproduced the problem If the problem does not appear to reproduce, please try waiting a bit and checking the f0 files with hexdump again. This behavior was observed by a customer reproducing the problem under ESXi. I since added an sync after the running the repro binary which I think will fix that. If you still can't reproduce the problem please let me know if there's anything I can do to help. For example can we trace the disk accesses at the SCSI level to verify whether the appropriate SCSI commands are being sent? This may help determine whether the problem is in Linux or in VMWare. [Fix] mptfusion: enable no_write_same in scsi_host_template commit 4089b71cc820a426d601283c92fcd4ffeb5139c2 upstream https://lkml.org/lkml/2014/9/25/482 (Note this patch may be reverted in the future as there is active discussion upstream about a more generic fix) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371591/+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 1382863] [NEW] Utopic freezes while booting the ISO image
You have been subscribed to a public bug: I'm testing an Ubuntu GNOME Utopic 20141016 amd64 image. When booting the ISO (using grubentry method), the screen freezes and becomes unresponsive after 3 secs of showing up the Gnome desktop screen. Not able to continue beyond that or even to the installation step. Do not face this issue with Beta 1 or Beta 2. The md5sum for iso file is OK. Problem is repeatable everytime. ProblemType: Bug DistroRelease: Ubuntu 14.10 Architecture: amd64 UpgradeStatus: No upgrade log present (probably fresh install) I don't know how to capture information about the crash, although I went through debugging guide, as can't get to part where I can get console / terminal access. I am attaching my laptop profile. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 iso-testing syslinux ubuntu ubuntu-gnome utopic -- Utopic freezes while booting the ISO image https://bugs.launchpad.net/bugs/1382863 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1382863] Re: Utopic freezes while booting the ISO image
There are multiple kernel warnings seen in the log file, and then there is this: BUG: unable to handle kernel NULL pointer dereference at 0048 ** Package changed: syslinux (Ubuntu) = linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1382863 Title: Utopic freezes while booting the ISO image Status in “linux” package in Ubuntu: New Bug description: I'm testing an Ubuntu GNOME Utopic 20141016 amd64 image. When booting the ISO (using grubentry method), the screen freezes and becomes unresponsive after 3 secs of showing up the Gnome desktop screen. Not able to continue beyond that or even to the installation step. Do not face this issue with Beta 1 or Beta 2. The md5sum for iso file is OK. Problem is repeatable everytime. ProblemType: Bug DistroRelease: Ubuntu 14.10 Architecture: amd64 UpgradeStatus: No upgrade log present (probably fresh install) I don't know how to capture information about the crash, although I went through debugging guide, as can't get to part where I can get console / terminal access. I am attaching my laptop profile. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382863/+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 1351519] Re: /sys/class/dmi/id/product_uuid is not world readable
** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1351519 Title: /sys/class/dmi/id/product_uuid is not world readable Status in Ubuntu error tracker client (whoopsie): New Status in “linux” package in Ubuntu: Confirmed Status in “whoopsie” package in Ubuntu: New Bug description: As part of (un)stable whoopsie persistent machine identifier generation /sys/class/dmi/id/product_uuid is used. However: $ ls /sys/class/dmi/id/product_uuid -r 1 root root 4096 Aug 2 01:23 /sys/class/dmi/id/product_uuid It's not world-readable. Hence API calls to whoopsie_identifier_generate return different results for root and non-root users. Either whoopsie should stop using product_uuid, or api calls to whoopsie_identifier_generate should be denied and instead one should use whoopsie-preferences which gets the full uuid (since the service is running as root on system dbus and thus can read product_uuid) To manage notifications about this bug go to: https://bugs.launchpad.net/whoopsie/+bug/1351519/+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 1382863] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1382863 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1382863 Title: Utopic freezes while booting the ISO image Status in “linux” package in Ubuntu: Incomplete Bug description: I'm testing an Ubuntu GNOME Utopic 20141016 amd64 image. When booting the ISO (using grubentry method), the screen freezes and becomes unresponsive after 3 secs of showing up the Gnome desktop screen. Not able to continue beyond that or even to the installation step. Do not face this issue with Beta 1 or Beta 2. The md5sum for iso file is OK. Problem is repeatable everytime. ProblemType: Bug DistroRelease: Ubuntu 14.10 Architecture: amd64 UpgradeStatus: No upgrade log present (probably fresh install) I don't know how to capture information about the crash, although I went through debugging guide, as can't get to part where I can get console / terminal access. I am attaching my laptop profile. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382863/+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 1380432] Re: 24x7 counters: Bug in catalog_read()
I've tried verifying a build with this patch on top of our current 3.16 Utopic tree and the above sysfs directory was still not found. Are there additional steps required to enable the hv_24x7 device? I have been testing on a POWER8 machine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1380432 Title: 24x7 counters: Bug in catalog_read() Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Utopic: In Progress Bug description: ---Problem Description--- 24x7 counters: Bug in catalog_read() ---Additional Hardware Info--- Power8 system with support for 24x7 counters Machine Type = Power8 IBM,9119-MME ---Steps to Reproduce--- cp /sys/bus/event_source/devices/hv_24x7/interface/catalog /tmp ls -l /tmp/catalog Shows a file size 0 for the /tmp/catalog. We recently discovered a bug in the upstream Linux kernel. It was fixed by this patch https://lkml.org/lkml/2014/10/1/35 and that patch is scheduled to be included in powerpc tree. When it is included, we should back port to Ubuntu 14.10 or next release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1380432/+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 1379244] Re: linux: 3.13.0-38.65 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) = John Johansen (jjohansen) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1379244 Title: linux: 3.13.0-38.65 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.13.0-38.65 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Thursday, 09. October 2014 09:27 UTC kernel-stable-Prepare-package-end:Thursday, 09. October 2014 18:06 UTC kernel-stable-Promote-to-proposed-start:Thursday, 09. October 2014 18:06 UTC ppa-package-testing-start:Thursday, 09. October 2014 18:06 UTC kernel-stable-Promote-to-proposed-end:Friday, 10. October 2014 18:28 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Friday, 10. October 2014 20:01 UTC kernel-stable-Verification-testing-start:Friday, 10. October 2014 20:01 UTC kernel-stable-Certification-testing-start:Friday, 10. October 2014 20:01 UTC kernel-stable-Security-signoff-start:Friday, 10. October 2014 20:02 UTC kernel-stable-Regression-testing-start:Friday, 10. October 2014 20:02 UTC kernel-stable-Regression-testing-end:Wednesday, 15. October 2014 08:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1379244/+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 1370025] Re: CVE-2014-3181
** Changed in: linux-armadaxp (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1370025 Title: CVE-2014-3181 Status in “linux” package in Ubuntu: Fix Released Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Released Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Trusty: Fix Released Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: New Status in “linux-lts-backport-natty” source package in Trusty: New Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Fix Released Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: Multiple stack-based buffer overflows in the magicmouse_raw_event function in drivers/hid/hid-magicmouse.c in the Magic Mouse HID driver in the Linux kernel through 3.16.3 allow physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted device that provides a large amount of (1) EHCI or (2) XHCI data associated with an event. Break-Fix: a462230e16acc8664145216da3c928d03556691a c54def7bd64d7c0b6993336abcffb8444795bf38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1370025/+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 1334985] Re: CVE-2014-0206
** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Invalid = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1334985 Title: CVE-2014-0206 Status in “linux” package in Ubuntu: Fix Committed Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Invalid Status in “linux-armadaxp” source package in Precise: Invalid Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: New Status in “linux-lts-backport-natty” source package in Saucy: New Status in “linux” source package in Trusty: Fix Released Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: New Status in “linux-lts-backport-natty” source package in Trusty: New Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Fix Committed Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: Array index error in the aio_read_events_ring function in fs/aio.c in the Linux kernel through 3.15.1 allows local users to obtain sensitive information from kernel memory via a large head value. Break-Fix: a31ad380bed817aa25f8830ad23e1a0480fef797 edfbbf388f293d70bf4b7c0bc38774d05e6f711a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1334985/+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 1370038] Re: CVE-2014-3186
** Changed in: linux-armadaxp (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1370038 Title: CVE-2014-3186 Status in “linux” package in Ubuntu: Fix Released Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Released Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Trusty: Fix Released Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: New Status in “linux-lts-backport-natty” source package in Trusty: New Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Fix Released Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: Buffer overflow in the picolcd_raw_event function in devices/hid/hid- picolcd_core.c in the PicoLCD HID device driver in the Linux kernel through 3.16.3, as used in Android on Nexus 7 devices, allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted device that sends a large report. Break-Fix: 236db47c2b3b69464d50c695ab2ddd516cf64520 844817e47eef14141cf59b8d5ac08dd11c0a9189 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1370038/+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 1370036] Re: CVE-2014-3185
** Changed in: linux-armadaxp (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1370036 Title: CVE-2014-3185 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Released Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Trusty: Fix Released Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: New Status in “linux-lts-backport-natty” source package in Trusty: New Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Invalid Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: Multiple buffer overflows in the command_port_read_callback function in drivers/usb/serial/whiteheat.c in the Whiteheat USB Serial Driver in the Linux kernel before 3.16.2 allow physically proximate attackers to execute arbitrary code or cause a denial of service (memory corruption and system crash) via a crafted device that provides a large amount of (1) EHCI or (2) XHCI data associated with a bulk response. Break-Fix: - 6817ae225cd650fb1c3295d769298c38b1eba818 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1370036/+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 1333612] Re: CVE-2014-4027
** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Invalid = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1333612 Title: CVE-2014-4027 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Released Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux” source package in Trusty: Fix Released Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Invalid Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: Won't Fix Status in “linux-lts-backport-natty” source package in Utopic: Won't Fix Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: The rd_build_device_space function in drivers/target/target_core_rd.c in the Linux kernel before 3.14 does not properly initialize a certain data structure, which allows local users to obtain sensitive information from ramdisk_mcp memory by leveraging access to a SCSI initiator. Break-Fix: c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 4442dc8a92b8f9ad8ee9e7f8438f4c04c03a22dc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1333612/+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 1370035] Re: CVE-2014-3184
** Changed in: linux-armadaxp (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1370035 Title: CVE-2014-3184 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Released Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Trusty: Fix Released Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: New Status in “linux-lts-backport-natty” source package in Trusty: New Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Invalid Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: The report_fixup functions in the HID subsystem in the Linux kernel before 3.16.2 might allow physically proximate attackers to cause a denial of service (out-of-bounds write) via a crafted device that provides a small report descriptor, related to (1) drivers/hid/hid- cherry.c, (2) drivers/hid/hid-kye.c, (3) drivers/hid/hid-lg.c, (4) drivers/hid/hid-monterey.c, (5) drivers/hid/hid-petalynx.c, and (6) drivers/hid/hid-sunplus.c. Break-Fix: - 4ab25786c87eb20857bbb715c3ae34ec8fd6a214 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1370035/+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 1335313] Re: CVE-2014-4608
** No longer affects: linux-armadaxp (Ubuntu Saucy) ** No longer affects: linux-ec2 (Ubuntu Saucy) ** No longer affects: linux-lts-saucy (Ubuntu Saucy) ** No longer affects: linux-lts-quantal (Ubuntu Saucy) ** No longer affects: linux-mvl-dove (Ubuntu Saucy) ** No longer affects: linux (Ubuntu Saucy) ** No longer affects: linux-fsl-imx51 (Ubuntu Saucy) ** No longer affects: linux-ti-omap4 (Ubuntu Saucy) ** No longer affects: linux-lts-raring (Ubuntu Saucy) ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Fix Committed = Fix Released ** Description changed: ** DISPUTED ** Multiple integer overflows in the lzo1x_decompress_safe function in lib/lzo/lzo1x_decompress_safe.c in the LZO decompressor in the Linux kernel before 3.15.2 allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Literal Run. NOTE: the author of the LZO algorithms says the Linux kernel is *not* affected; media hype. - Break-Fix: 64c70b1cf43de158282bc1675918d503e5b15cc1 - 206a81c18401c0cde6e579164f752c4b147324ce + Break-Fix: 64c70b1cf43de158282bc1675918d503e5b15cc1 206a81c18401c0cde6e579164f752c4b147324ce + Break-Fix: 64c70b1cf43de158282bc1675918d503e5b15cc1 af958a38a60c7ca3d8a39c918c1baa2ff7b6b233 + Break-Fix: 64c70b1cf43de158282bc1675918d503e5b15cc1 72cf90124e87d975d0b2114d930808c58b4c05e4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1335313 Title: CVE-2014-4608 Status in “linux” package in Ubuntu: Fix Committed Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Committed Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-lts-raring” source package in Precise: Fix Released Status in “linux-lts-saucy” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux-lts-backport-maverick” source package in Saucy: New Status in “linux-lts-backport-natty” source package in Saucy: New Status in “linux” source package in Trusty: Fix Released Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: New Status in “linux-lts-backport-natty” source package in Trusty: New Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Fix Committed Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid
[Kernel-packages] [Bug 1370042] Re: CVE-2014-6410
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1370042 Title: CVE-2014-6410 Status in “linux” package in Ubuntu: Fix Released Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Released Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Trusty: Fix Released Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: New Status in “linux-lts-backport-natty” source package in Trusty: New Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Fix Released Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. Break-Fix: - c03aa9f6e1f938618e6db2e23afef0574efeeb65 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1370042/+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 1383097] Re: Touch pad multi touch features doesn't work
This is actually an issue with a missing driver. I have run the command to list inputs and returns following. xinput --list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ PS/2 Logitech Wheel Mouse id=14 [slave pointer (2)] ⎜ ↳ USB Optical Mouse id=10 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ Sleep Button id=9[slave keyboard (3)] ↳ Asus WMI hotkeys id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam id=11 [slave keyboard (3)] The touchpad is working fine. But the mutitouch features like scrolling is not working ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1383097 Title: Touch pad multi touch features doesn't work Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I am using an Asus X553MA laptop. My touch pad works well. But the features like multitouch, scrolling etc doesn't seem to work. I tried the below command and it didn't return any output. cat /proc/bus/input/devices ~/devices xinput --list ~/xinput And the below code returns all hardware info but not my touchpad ajith@ajith-X553MA:~$ cat /proc/bus/input/devices But i noticed a field as Mouse instead of my touchpad. I: Bus=0011 Vendor=0002 Product=0001 Version=0063 N: Name=PS/2 Logitech Wheel Mouse P: Phys=isa0060/serio4/input0 S: Sysfs=/devices/platform/i8042/serio4/input/input12 U: Uniq= H: Handlers=mouse0 event5 B: PROP=0 B: EV=7 B: KEY=7 0 0 0 0 0 0 0 0 B: REL=3 I have used a mouse earlier with the laptop. But it was not a Logitech one. It was an HP one. Please help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383097/+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 1370046] Re: CVE-2014-6417
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1370046 Title: CVE-2014-6417 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Released Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Trusty: Fix Released Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: New Status in “linux-lts-backport-natty” source package in Trusty: New Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Invalid Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: net/ceph/auth_x.c in Ceph, as used in the Linux kernel before 3.16.3, does not properly consider the possibility of kmalloc failure, which allows remote attackers to cause a denial of service (system crash) or possibly have unspecified other impact via a long unencrypted auth ticket. Break-Fix: ec0994e48ea2aebf62ff08376227f3a9ccf46262 c27a3e4d667fdcad3db7b104f75659478e0c68d8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1370046/+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 1370044] Re: CVE-2014-6416
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1370044 Title: CVE-2014-6416 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Released Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Trusty: Fix Released Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: New Status in “linux-lts-backport-natty” source package in Trusty: New Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Invalid Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: Buffer overflow in net/ceph/auth_x.c in Ceph, as used in the Linux kernel before 3.16.3, allows remote attackers to cause a denial of service (memory corruption and panic) or possibly have unspecified other impact via a long unencrypted auth ticket. Break-Fix: ec0994e48ea2aebf62ff08376227f3a9ccf46262 c27a3e4d667fdcad3db7b104f75659478e0c68d8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1370044/+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 1373050] Re: CVE-2014-7145
** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux (Ubuntu Trusty) Status: New = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1373050 Title: CVE-2014-7145 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Invalid Status in “linux-armadaxp” source package in Precise: Invalid Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Invalid Status in “linux” source package in Trusty: Fix Committed Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: New Status in “linux-lts-backport-natty” source package in Trusty: New Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Invalid Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. Break-Fix: faaf946a7d5b79194358437150f34ab4c66bfe21 18f39e7be0121317550d03e267e3ebd4dbfbb3ce To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1373050/+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 1370047] Re: CVE-2014-6418
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1370047 Title: CVE-2014-6418 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Released Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Trusty: Fix Released Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: New Status in “linux-lts-backport-natty” source package in Trusty: New Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Invalid Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: net/ceph/auth_x.c in Ceph, as used in the Linux kernel before 3.16.3, does not properly validate auth replies, which allows remote attackers to cause a denial of service (system crash) or possibly have unspecified other impact via crafted data from the IP address of a Ceph Monitor. Break-Fix: ec0994e48ea2aebf62ff08376227f3a9ccf46262 c27a3e4d667fdcad3db7b104f75659478e0c68d8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1370047/+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 1377339] Re: CVE-2014-7284
** Description changed: - [linux kernel net_get_random_once bug] + The net_get_random_once implementation in net/core/utils.c in the Linux + kernel 3.13.x and 3.14.x before 3.14.5 on certain Intel processors does + not perform the intended slow-path operation to initialize random seeds, + which makes it easier for remote attackers to spoof or disrupt IP + communication by leveraging the predictability of TCP sequence numbers, + TCP and UDP port numbers, and IP ID values. Break-Fix: a48e42920ff38bc90bbf75143fff4555723d4540 3d4405226d27b3a215e4d03cfa51f536244e5de7 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1377339 Title: CVE-2014-7284 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Invalid Status in “linux-armadaxp” source package in Precise: Invalid Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Invalid Status in “linux” source package in Trusty: Fix Committed Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: New Status in “linux-lts-backport-natty” source package in Trusty: New Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Invalid Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: The net_get_random_once implementation in net/core/utils.c in the Linux kernel 3.13.x and 3.14.x before 3.14.5 on certain Intel processors does not perform the intended slow-path operation to initialize random seeds, which makes it easier for remote attackers to spoof or disrupt IP communication by leveraging the predictability of TCP sequence numbers, TCP and UDP port numbers, and IP ID values. Break-Fix: a48e42920ff38bc90bbf75143fff4555723d4540 3d4405226d27b3a215e4d03cfa51f536244e5de7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377339/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1377337] Re: CVE-2014-7283
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Invalid ** Changed in: linux (Ubuntu Precise) Status: New = Invalid ** Changed in: linux (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New = Invalid ** Description changed: - [xfs directory hash ordering bug] + The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs + implementation in the Linux kernel before 3.14.2 does not properly + compare btree hash values, which allows local users to cause a denial of + service (filesystem corruption, and OOPS or panic) via operations on + directories that have hash collisions, as demonstrated by rmdir + operations. Break-Fix: f5ea110044fa858925a880b4fa9f551bfa2dfc38 c88547a8119e3b581318ab65e9b72f27f23e641d -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1377337 Title: CVE-2014-7283 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Invalid Status in “linux-armadaxp” source package in Precise: Invalid Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Invalid Status in “linux” source package in Trusty: Fix Committed Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: New Status in “linux-lts-backport-natty” source package in Trusty: New Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Invalid Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as demonstrated by rmdir operations.
[Kernel-packages] [Bug 1383356] [NEW] CVE-2014-7970
*** This bug is a security vulnerability *** Public security bug reported: The pivot_root implementation in fs/namespace.c in the Linux kernel through 3.17 does not properly interact with certain locations of a chroot directory, which allows local users to cause a denial of service (mount-tree loop) via . (dot) values in both arguments to the pivot_root system call. Break-Fix: - 0d0826019e529f21c84687521d03f60cd241ca7d ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Utopic) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided
[Kernel-packages] [Bug 1383356] Re: CVE-2014-7970
CVE-2014-7970 ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-fsl-imx51 (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-fsl-imx51 (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-fsl-imx51 (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New = Invalid ** Description changed: - Placeholder + The pivot_root implementation in fs/namespace.c in the Linux kernel + through 3.17 does not properly interact with certain locations of a + chroot directory, which allows local users to cause a denial of service + (mount-tree loop) via . (dot) values in both arguments to the pivot_root + system call. + + Break-Fix: - 0d0826019e529f21c84687521d03f60cd241ca7d ** Changed in: linux-armadaxp (Ubuntu Precise) Importance: Undecided = Medium ** Changed in:
[Kernel-packages] [Bug 1383358] Re: CVE-2014-7975
CVE-2014-7975 ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-fsl-imx51 (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-fsl-imx51 (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-fsl-imx51 (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New = Invalid ** Description changed: - Placeholder + The do_umount function in fs/namespace.c in the Linux kernel through + 3.17 does not require the CAP_SYS_ADMIN capability for do_remount_sb + calls that change the root filesystem to read-only, which allows local + users to cause a denial of service (loss of writability) by making + certain unshare system calls, clearing the / MNT_LOCKED flag, and making + an MNT_FORCE umount system call. + + Break-Fix: - a1480dcc3c706e309a4723446f2e84fedd5b ** Changed in:
[Kernel-packages] [Bug 1383358] [NEW] CVE-2014-7975
*** This bug is a security vulnerability *** Public security bug reported: The do_umount function in fs/namespace.c in the Linux kernel through 3.17 does not require the CAP_SYS_ADMIN capability for do_remount_sb calls that change the root filesystem to read-only, which allows local users to cause a denial of service (loss of writability) by making certain unshare system calls, clearing the / MNT_LOCKED flag, and making an MNT_FORCE umount system call. Break-Fix: - a1480dcc3c706e309a4723446f2e84fedd5b ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Utopic) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided
[Kernel-packages] [Bug 1383361] Re: CVE-2014-8086
CVE-2014-8086 ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-fsl-imx51 (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-fsl-imx51 (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-fsl-imx51 (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New = Invalid ** Description changed: - Placeholder + Race condition in the ext4_file_write_iter function in fs/ext4/file.c in + the Linux kernel through 3.17 allows local users to cause a denial of + service (file unavailability) via a combination of a write action and an + F_SETFL fcntl operation for the O_DIRECT flag. + + Break-Fix: - - ** Changed in: linux-armadaxp (Ubuntu Precise) Importance: Undecided = Medium ** Changed in: linux-armadaxp (Ubuntu Lucid) Importance: Undecided = Medium ** Changed in:
[Kernel-packages] [Bug 1383361] [NEW] CVE-2014-8086
*** This bug is a security vulnerability *** Public security bug reported: Race condition in the ext4_file_write_iter function in fs/ext4/file.c in the Linux kernel through 3.17 allows local users to cause a denial of service (file unavailability) via a combination of a write action and an F_SETFL fcntl operation for the O_DIRECT flag. Break-Fix: - - ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Utopic) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Utopic)
[Kernel-packages] [Bug 1381815] Re: left touchpad button stopped working in 3.16.0-22.19
ups, didn't install the extras package. With it installed everything seems to work alright. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1381815 Title: left touchpad button stopped working in 3.16.0-22.19 Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: the left touchpad button of my lenovo g50 laptop stopped working in the kernel upgrade 3.16.0-22 #29 The rest of the touchpad and the right button are still working. the previous kernel version #27 worked fine I have tried the mainline kernels and it is also affected from version 3.16.4 up to including the latest available ne 3.17.1. mainline kernel 3.16.3 works. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-22-generic 3.16.0-22.29 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jtaylor3144 F pulseaudio /dev/snd/controlC1: jtaylor3144 F pulseaudio CurrentDesktop: Unity Date: Thu Oct 16 01:39:27 2014 HibernationDevice: RESUME=UUID=86457fb1-d8f8-46e4-9ad2-c85d69ec96f7 InstallationDate: Installed on 2014-08-23 (53 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140822) MachineType: LENOVO 20351 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-22-generic N/A linux-backports-modules-3.16.0-22-generic N/A linux-firmware 1.135 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/02/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN25WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A2 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-70: dmi.product.name: 20351 dmi.product.version: Lenovo G50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381815/+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 1381815] Re: left touchpad button stopped working in 3.16.0-22.19
the kernel fixes the touchpad button issue, but also don't have any network with it. network works fine in the current utopic kernel -22.29 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1381815 Title: left touchpad button stopped working in 3.16.0-22.19 Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: the left touchpad button of my lenovo g50 laptop stopped working in the kernel upgrade 3.16.0-22 #29 The rest of the touchpad and the right button are still working. the previous kernel version #27 worked fine I have tried the mainline kernels and it is also affected from version 3.16.4 up to including the latest available ne 3.17.1. mainline kernel 3.16.3 works. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-22-generic 3.16.0-22.29 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jtaylor3144 F pulseaudio /dev/snd/controlC1: jtaylor3144 F pulseaudio CurrentDesktop: Unity Date: Thu Oct 16 01:39:27 2014 HibernationDevice: RESUME=UUID=86457fb1-d8f8-46e4-9ad2-c85d69ec96f7 InstallationDate: Installed on 2014-08-23 (53 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140822) MachineType: LENOVO 20351 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-22-generic N/A linux-backports-modules-3.16.0-22-generic N/A linux-firmware 1.135 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/02/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN25WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A2 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-70: dmi.product.name: 20351 dmi.product.version: Lenovo G50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381815/+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 1377878] Re: PPC - GUI freezes except for mouse pointer
@adam does this affect all ppc radeon cards? if so, that kills a lot of computers we wanted to support! can you link me to archives of your upstream inquiries? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1377878 Title: PPC - GUI freezes except for mouse pointer Status in “linux” package in Ubuntu: Confirmed Bug description: During the installation the computer freezes completely except for the mouse pointer. And even that is stuck with whatever shape it happened to have at the time it froze. The steps I have to cause the freeze are run Ubiquity to start the installation open a terminal, run Ubuntu-bug and let it launch Firefox. It will freeze every time then. Even the consoles (ctrl-alt-f1 etc) are unavailable. What kind of information can I collect and how? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377878/+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 1327741] Re: Kernel panic on driver rtl8821ae
This bug is present in kubuntu 14.04.1 LTS too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1327741 Title: Kernel panic on driver rtl8821ae Status in “linux” package in Ubuntu: Incomplete Bug description: Since kernel version 3.13.0-27, my Asus VM40B goes into kernel panic during boot, seemingly due to an error with the WiFi driver, rtl8821ae. The attached screenshot of the screen (I have no idea how to otherwise capture the output of a kernel panic) shows the error with kernel version 3.13.0-29, but it happens exactly the same with -27. WORKAROUND: Disabling the WiFi card or using version 3.13.0-24 does not cause any problem. Please bear in mind, while reading the generated report, that I have disabled the WiFi card to be able to boot with kernel -29. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327741/+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 1371379] Re: rtsx_usb module for Realtek Semiconductor Corp. RTS5139 Card Reader Controller doesn't load
Looks fixed with 3.16.0-17.23, change status to Fix Released? It wasn't mentioned in the changelog. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371379 Title: rtsx_usb module for Realtek Semiconductor Corp. RTS5139 Card Reader Controller doesn't load Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Fix Committed Status in “linux” source package in Utopic: Fix Committed Status in “linux” package in Debian: Fix Released Status in “linux” package in openSUSE: Unknown Bug description: The module for Realtek Semiconductor Corp. RTS5139 Card Reader Controller (lsbusb ID 0bda:0139) does not load automatically on boot, so the SD card reader won't work. If I add rtsx_usb to /etc/modules then the correct modules are loaded on boot and the SD card reader will work. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-16-generic 3.16.0-16.22 ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: snafu109 2918 F pulseaudio CurrentDesktop: XFCE Date: Thu Sep 18 21:36:55 2014 HibernationDevice: RESUME=UUID=4e46a15c-d441-4b34-ae15-a93302da75a5 InstallationDate: Installed on 2012-12-26 (631 days ago) InstallationMedia: Xubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120817.3) MachineType: ASUSTeK COMPUTER INC. UX32VD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-16-generic root=UUID=687d7b6d-6fe2-413c-84c1-ed511edff5f9 ro quiet splash intel_pstate=enable vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-16-generic N/A linux-backports-modules-3.16.0-16-generic N/A linux-firmware 1.134 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-08-31 (18 days ago) dmi.bios.date: 01/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX32VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1371379/+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 1377878] Re: PPC - GUI freezes except for mouse pointer
** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1377878 Title: PPC - GUI freezes except for mouse pointer Status in “linux” package in Ubuntu: Confirmed Bug description: During the installation the computer freezes completely except for the mouse pointer. And even that is stuck with whatever shape it happened to have at the time it froze. The steps I have to cause the freeze are run Ubiquity to start the installation open a terminal, run Ubuntu-bug and let it launch Firefox. It will freeze every time then. Even the consoles (ctrl-alt-f1 etc) are unavailable. What kind of information can I collect and how? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377878/+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 1382863] Re: Utopic freezes while booting the ISO image
Can you see if this issue still occurs with the latest daily image? It can be downloaded from: http://cdimage.ubuntu.com/daily-live/current/ ** Changed in: linux (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1382863 Title: Utopic freezes while booting the ISO image Status in “linux” package in Ubuntu: Incomplete Bug description: I'm testing an Ubuntu GNOME Utopic 20141016 amd64 image. When booting the ISO (using grubentry method), the screen freezes and becomes unresponsive after 3 secs of showing up the Gnome desktop screen. Not able to continue beyond that or even to the installation step. Do not face this issue with Beta 1 or Beta 2. The md5sum for iso file is OK. Problem is repeatable everytime. ProblemType: Bug DistroRelease: Ubuntu 14.10 Architecture: amd64 UpgradeStatus: No upgrade log present (probably fresh install) I don't know how to capture information about the crash, although I went through debugging guide, as can't get to part where I can get console / terminal access. I am attaching my laptop profile. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382863/+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 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc1-utopic/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported Status in “linux” package in Ubuntu: Incomplete Bug description: Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/+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 1383097] Re: Touch pad multi touch features doesn't work
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc1-utopic/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1383097 Title: Touch pad multi touch features doesn't work Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I am using an Asus X553MA laptop. My touch pad works well. But the features like multitouch, scrolling etc doesn't seem to work. I tried the below command and it didn't return any output. cat /proc/bus/input/devices ~/devices xinput --list ~/xinput And the below code returns all hardware info but not my touchpad ajith@ajith-X553MA:~$ cat /proc/bus/input/devices But i noticed a field as Mouse instead of my touchpad. I: Bus=0011 Vendor=0002 Product=0001 Version=0063 N: Name=PS/2 Logitech Wheel Mouse P: Phys=isa0060/serio4/input0 S: Sysfs=/devices/platform/i8042/serio4/input/input12 U: Uniq= H: Handlers=mouse0 event5 B: PROP=0 B: EV=7 B: KEY=7 0 0 0 0 0 0 0 0 B: REL=3 I have used a mouse earlier with the laptop. But it was not a Logitech one. It was an HP one. Please help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383097/+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 1372482] Re: mount.cifs does not work with the 3.13.0.36-generic kernel
One more confirm. Cifs mounting with 3.13.0-38-generic/trusty-proposed works for me as well. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1372482 Title: mount.cifs does not work with the 3.13.0.36-generic kernel Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Invalid Bug description: mount.cifs //server_ip/share_name mount_point -o user=user Password... mount error(5): Input/output error Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) From syslog: Sep 22 15:41:04 ds1205 kernel: [ 11.778362] [ cut here ] Sep 22 15:41:04 ds1205 kernel: [ 11.778370] WARNING: CPU: 3 PID: 2253 at /build/buildd/linux-3.13.0/fs/cifs/transport.c:313 smb_send_rqst+0x215/0x270 [cifs]() Sep 22 15:41:04 ds1205 kernel: [ 11.778371] Send length mismatch(send_length=72 smb_buf_length=2164260932) Sep 22 15:41:04 ds1205 kernel: [ 11.778372] Modules linked in: cuse rfcomm bnep bluetooth binfmt_misc snd_hda_codec_realtek nls_utf8 cifs fscache intel_rapl x86_pkg_temp_thermal intel_powerclamp snd_hda_intel coretemp snd_hda_codec kvm_intel kvm snd_hwdep snd_pcm crct10dif_pclmul crc32_pclmul snd_page_alloc ghash_clmulni_intel i915 snd_seq_midi aesni_intel snd_seq_midi_event aes_x86_64 lrw snd_rawmidi gf128mul snd_seq glue_helper ablk_helper snd_seq_device drm_kms_helper cryptd snd_timer drm keucr(C) parport_pc i2c_algo_bit hid_generic snd mei_me ppdev mei usb_storage lp soundcore serio_raw lpc_ich parport wmi mac_hid video usbhid hid psmouse ahci libahci r8169 mii Sep 22 15:41:04 ds1205 kernel: [ 11.778395] CPU: 3 PID: 2253 Comm: mount.cifs Tainted: GWC3.13.0-36-generic #63-Ubuntu Sep 22 15:41:04 ds1205 kernel: [ 11.778396] Hardware name: Hewlett-Packard HP Pro 3500 Series/2ABF, BIOS 8.11 10/24/2012 Sep 22 15:41:04 ds1205 kernel: [ 11.778397] 0009 8800ccaf7bb0 8171e569 8800ccaf7bf8 Sep 22 15:41:04 ds1205 kernel: [ 11.778399] 8800ccaf7be8 8106775d 8800ccaf7d00 88020fecb800 Sep 22 15:41:04 ds1205 kernel: [ 11.778401] 8800ccaf7cc8 0001 8800ccaf7c48 Sep 22 15:41:04 ds1205 kernel: [ 11.778403] Call Trace: Sep 22 15:41:04 ds1205 kernel: [ 11.778406] [8171e569] dump_stack+0x45/0x56 Sep 22 15:41:04 ds1205 kernel: [ 11.778408] [8106775d] warn_slowpath_common+0x7d/0xa0 Sep 22 15:41:04 ds1205 kernel: [ 11.778409] [810677cc] warn_slowpath_fmt+0x4c/0x50 Sep 22 15:41:04 ds1205 kernel: [ 11.778415] [a04904c5] smb_send_rqst+0x215/0x270 [cifs] Sep 22 15:41:04 ds1205 kernel: [ 11.778417] [81690218] ? __inet_stream_connect+0x208/0x320 Sep 22 15:41:04 ds1205 kernel: [ 11.778422] [a049055d] smb_sendv+0x3d/0x40 [cifs] Sep 22 15:41:04 ds1205 kernel: [ 11.778426] [a0490588] smb_send+0x28/0x30 [cifs] Sep 22 15:41:04 ds1205 kernel: [ 11.778430] [a047a15d] generic_ip_connect+0x30d/0x3e0 [cifs] Sep 22 15:41:04 ds1205 kernel: [ 11.778432] [811a1d65] ? __kmalloc+0x55/0x230 Sep 22 15:41:04 ds1205 kernel: [ 11.778437] [a047e69c] cifs_mount+0x85c/0xaf0 [cifs] Sep 22 15:41:04 ds1205 kernel: [ 11.778440] [a046d040] cifs_do_mount+0xa0/0x4d0 [cifs] Sep 22 15:41:04 ds1205 kernel: [ 11.778442] [811c10a9] mount_fs+0x39/0x1b0 Sep 22 15:41:04 ds1205 kernel: [ 11.778444] [811dc447] vfs_kern_mount+0x67/0x110 Sep 22 15:41:04 ds1205 kernel: [ 11.778446] [811deca4] do_mount+0x244/0xb20 Sep 22 15:41:04 ds1205 kernel: [ 11.778448] [811530be] ? __get_free_pages+0xe/0x50 Sep 22 15:41:04 ds1205 kernel: [ 11.778450] [811de8e6] ? copy_mount_options+0x36/0x170 Sep 22 15:41:04 ds1205 kernel: [ 11.778451] [811df873] SyS_mount+0x83/0xc0 Sep 22 15:41:04 ds1205 kernel: [ 11.778453] [8172efad] system_call_fastpath+0x1a/0x1f Sep 22 15:41:04 ds1205 kernel: [ 11.778454] ---[ end trace 826c79e22eb80bab ]--- Sep 22 15:41:04 ds1205 kernel: [ 11.779826] CIFS VFS: Error connecting to socket. Aborting operation. Sep 22 15:41:04 ds1205 kernel: [ 11.779890] CIFS VFS: cifs_mount failed w/return code = -5 I cannot mount share from Samba 3.6.6, but I can mount a share from a Windows 2003 server. But it works with 3.13.0.35-generic. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-36-generic 3.13.0-36.63 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pt 2204 F pulseaudio /dev/snd/pcmC0D0p:
[Kernel-packages] [Bug 1379244] Re: linux: 3.13.0-38.65 -proposed tracker
Looks good ** Changed in: kernel-sru-workflow/security-signoff Status: In Progress = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1379244 Title: linux: 3.13.0-38.65 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.13.0-38.65 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Thursday, 09. October 2014 09:27 UTC kernel-stable-Prepare-package-end:Thursday, 09. October 2014 18:06 UTC kernel-stable-Promote-to-proposed-start:Thursday, 09. October 2014 18:06 UTC ppa-package-testing-start:Thursday, 09. October 2014 18:06 UTC kernel-stable-Promote-to-proposed-end:Friday, 10. October 2014 18:28 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Friday, 10. October 2014 20:01 UTC kernel-stable-Verification-testing-start:Friday, 10. October 2014 20:01 UTC kernel-stable-Certification-testing-start:Friday, 10. October 2014 20:01 UTC kernel-stable-Security-signoff-start:Friday, 10. October 2014 20:02 UTC kernel-stable-Regression-testing-start:Friday, 10. October 2014 20:02 UTC kernel-stable-Regression-testing-end:Wednesday, 15. October 2014 08:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1379244/+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 1380902] Re: impossible to load the greffon
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc1-utopic/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1380902 Title: impossible to load the greffon Status in “linux” package in Ubuntu: Incomplete Bug description: Impossible de trouver le greffon requis Vidéos nécessite d'installer un greffon pour lire les fichiers multimédias du type suivant : audio/x-midi-event decoder it's impossible to read a .mid file because the application (rythmbox for exemple) doesn't find the greffon Ubuntu 3.13.0-37.64-generic 3.13.11.7 I have this problem with Ubuntu 14.04 LTS 32 bits but not with Ubuntu Studio 14.04 --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: jpb1976 F pulseaudio /dev/snd/controlC1: jpb1976 F pulseaudio /dev/snd/controlC0: jpb1976 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=de7c7e33-a5b4-4bd4-be64-e1e59ae987a6 InstallationDate: Installed on 2014-05-25 (141 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=700731a7-ff6c-4343-9863-5c527faf3984 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo WifiSyslog: Oct 14 05:59:28 jpb-desktop kernel: [ 1024.084045] usb 1-4: reset high-speed USB device number 2 using ehci-pci Oct 14 06:04:25 jpb-desktop kernel: [ 1321.413510] perf samples too long (2513 2500), lowering kernel.perf_event_max_sample_rate to 5 Oct 14 06:36:06 jpb-desktop kernel: [ 3221.591244] systemd-hostnamed[4342]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname! Oct 14 07:10:59 jpb-desktop kernel: [ 5314.562469] systemd-hostnamed[5026]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname! _MarkForUpload: True dmi.bios.date: 11/17/2008 dmi.bios.vendor: Intel Corp. dmi.bios.version: TYG4110H.86A.0018.2008.1117.1920 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG41TY dmi.board.vendor: Intel Corporation dmi.board.version: AAE47335-204 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrTYG4110H.86A.0018.2008.1117.1920:bd11/17/2008:svn:pn:pvr:rvnIntelCorporation:rnDG41TY:rvrAAE47335-204:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1380902/+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 1379244] Re: linux: 3.13.0-38.65 -proposed tracker
** Description changed: This bug is for tracking the 3.13.0-38.65 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Thursday, 09. October 2014 09:27 UTC kernel-stable-Prepare-package-end:Thursday, 09. October 2014 18:06 UTC kernel-stable-Promote-to-proposed-start:Thursday, 09. October 2014 18:06 UTC ppa-package-testing-start:Thursday, 09. October 2014 18:06 UTC kernel-stable-Promote-to-proposed-end:Friday, 10. October 2014 18:28 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Friday, 10. October 2014 20:01 UTC kernel-stable-Verification-testing-start:Friday, 10. October 2014 20:01 UTC kernel-stable-Certification-testing-start:Friday, 10. October 2014 20:01 UTC kernel-stable-Security-signoff-start:Friday, 10. October 2014 20:02 UTC kernel-stable-Regression-testing-start:Friday, 10. October 2014 20:02 UTC kernel-stable-Regression-testing-end:Wednesday, 15. October 2014 08:00 UTC + kernel-stable-Security-signoff-end:Monday, 20. October 2014 18:01 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1379244 Title: linux: 3.13.0-38.65 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.13.0-38.65 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Thursday, 09. October 2014 09:27 UTC kernel-stable-Prepare-package-end:Thursday, 09. October 2014 18:06 UTC kernel-stable-Promote-to-proposed-start:Thursday, 09. October 2014 18:06 UTC ppa-package-testing-start:Thursday, 09. October 2014 18:06 UTC kernel-stable-Promote-to-proposed-end:Friday, 10. October 2014 18:28 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Friday, 10. October 2014 20:01 UTC kernel-stable-Verification-testing-start:Friday, 10. October 2014 20:01 UTC kernel-stable-Certification-testing-start:Friday, 10. October 2014 20:01 UTC kernel-stable-Security-signoff-start:Friday, 10. October 2014 20:02 UTC kernel-stable-Regression-testing-start:Friday, 10. October 2014 20:02 UTC kernel-stable-Regression-testing-end:Wednesday, 15. October 2014 08:00 UTC kernel-stable-Security-signoff-end:Monday, 20. October 2014 18:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1379244/+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 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported
Hello. I installed the latest x64 upstream kernel as well as the headers for it from the link you provided. I got to the login screen, and after I entered my password it just hanged there and I never got to the desktop. I tried one more time, and this time I did not enter my password. I used the top bar to connect to the internet in the login screen but wifi was still not recognized. Hence, I just added the tag kernel-bug-exists-upstream. Let me know if I should have used the second one you mentioned. P.S.: I just noticed that during the booting time I get a message saying that Bluetooth is not available either. I guess that doesn't have a proper driver either. Not sure if it's the same device or not. Cheers. ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported Status in “linux” package in Ubuntu: Confirmed Bug description: Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/+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 1382863] Re: Utopic freezes while booting the ISO image
I cannot run apport-collect as that would need to open browser, which means going into Desktop GUI, which automatically leads to freeze. I face the same issue with even the latest daily images, I can see on cdimages.ubuntu.com , namely: - Ubuntu Desktop Utopic 20141017 amd64 image - Ubuntu GNOME Utopic 20141016 amd64 image I have attached kernel logs, before for both the images. If I do Ctrl-ALT-F1 as soon as Desktop screen appears, I acn keep working in Console, abut as soon as I try to go back to desktop Gui, It freezes, both on Ubuntu Unity Desktop and Ubuntu Gnome Desktop. Let me know if I can provide anyother logs, and teh commands I can run to collect those. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1382863 Title: Utopic freezes while booting the ISO image Status in “linux” package in Ubuntu: Confirmed Bug description: I'm testing an Ubuntu GNOME Utopic 20141016 amd64 image. When booting the ISO (using grubentry method), the screen freezes and becomes unresponsive after 3 secs of showing up the Gnome desktop screen. Not able to continue beyond that or even to the installation step. Do not face this issue with Beta 1 or Beta 2. The md5sum for iso file is OK. Problem is repeatable everytime. ProblemType: Bug DistroRelease: Ubuntu 14.10 Architecture: amd64 UpgradeStatus: No upgrade log present (probably fresh install) I don't know how to capture information about the crash, although I went through debugging guide, as can't get to part where I can get console / terminal access. I am attaching my laptop profile. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382863/+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 1275398] Re: i915 driver/i945 hardware: Mir GL clients are rendered as black (or transparent or crash) windows when using i945 graphics
** Summary changed: - i915 driver/i945 hardware: Mir GL clients are rendered as black or transparent windows when using i945 graphics + i915 driver/i945 hardware: Mir GL clients are rendered as black (or transparent or crash) windows when using i945 graphics -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1275398 Title: i915 driver/i945 hardware: Mir GL clients are rendered as black (or transparent or crash) windows when using i945 graphics Status in Mir: Confirmed Status in “linux” package in Ubuntu: Invalid Status in “mesa” package in Ubuntu: In Progress Bug description: Running Mir on a Pentium D system with integrated i945 graphics, appears to work at first. The server starts and software clients are rendered correctly. However hardware (GL) clients are rendered as all black or transparent windows, despite logging to stdout that they think they are rendering: $ sudo bin/mir_demo_client_egltriangle Current active output is 1920x1200 +0+0 Server supports 2 of 6 surface pixel formats. Using format: 4 libEGL warning: unsupported platform (null) 1 FPS 33 FPS 60 FPS 60 FPS 60 FPS 60 FPS To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1275398/+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 1124250] Re: Partially incorrect uid mapping with nfs4/idmapd/ldap-auth
Interesting.. keyutils doesn't seem to help in my case.I'm running ls on the ~27000 user accounts home directory.. I don't understand why this would help... all nfsidmap would do is clear it once, and then it can fill up again/expire again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1124250 Title: Partially incorrect uid mapping with nfs4/idmapd/ldap-auth Status in “linux” package in Ubuntu: Confirmed Status in “nfs-utils” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Won't Fix Status in “nfs-utils” source package in Trusty: New Status in “linux” source package in Utopic: Won't Fix Status in “nfs-utils” source package in Utopic: Confirmed Status in “nfs-utils” package in Debian: Incomplete Status in Fedora: Unknown Bug description: I'm running a nfs4 server exporting a directory /home (ext4,usrquota). This server is running Ubuntu 12.04 amd64(up-to-date). This directory is handling 662 homedirs for ldap authenticated users. /etc/exports is : /exports 192.168.0.0/24(rw,fsid=0,no_subtree_check) Important lines in /etc/idmapd.conf : domain=my-domain.org [Translation] Method=nsswitch. In /etc/default/nfs-common : NEED_IDMAPD=yes In /etc/default/nfs-kernel-server : RPCNFSDCOUNT=75 RPCMOUNTDOPTS=--manage-gids 2 Clients (rhel6 x86 Ubuntu 12.04.2 i686) are mounting this nfs4 exported directory with no problems : When doing ls -l /home on this clients, I have : ... drwx-- 4 user100 oldusers 4096 sept. 21 2011 user100 drwx-- 4 user101 oldusers 4096 sept. 21 2011 user101 drwx-- 37 user102 oldusers 4096 oct. 1 19:06 user102 drwx-- 36 user103 users4096 févr. 5 21:08 user103 drwx-- 36 user104 users4096 févr. 8 14:03 user104 drwx-- 30 user105 users4096 févr. 4 18:01 user105 drwx-- 28 user106 oldusers 4096 oct. 5 2011 user106 drwx-- 37 user107 oldusers 4096 janv. 8 14:52 user107 drwx-- 31 user108 users4096 déc. 4 11:52 user108 drwx-- 4 user109 oldusers 4096 sept. 21 2011 user109 drwx--x--x 45 user110 oldusers 4096 janv. 22 15:53 user109 drwx-- 31 user111 users4096 janv. 29 12:03 user110 ... uid/gid mapping works fine, authldap works fine, ... All Clients running Ubuntu 12.10 i686 or Ubuntu 12.10 amd64 are experiencing the same problem : The config files are the same that used in ubuntu 12.04. Auth ldap is correctly configured, user can log in. This is the /etc/fstab entry for /home : 192.168.0.1:/ /home nfs rw,nfsvers=4 0 0 Important lines in /etc/idmapd.conf : domain=my-domain.org [Translation] Method=nsswitch In /etc/default/nfs-common : NEED_IDMAPD=yes /etc/nsswitch.conf is : passwd: files ldap group: files ldap shadow: files ldap When doing ls -l /home there is a strange problem : drwx-- 4 4294967294 oldusers 4096 sept. 21 2011 user100 drwx-- 4 user101oldusers 4096 sept. 21 2011 user101 drwx-- 37 user102oldusers 4096 oct. 1 19:06 user102 drwx-- 36 4294967294 users4096 févr. 5 21:08 user103 drwx-- 36 4294967294 users4096 févr. 8 14:03 user104 drwx-- 30 4294967294 users4096 févr. 4 18:01 user105 drwx-- 28 4294967294 oldusers 4096 oct. 5 2011 user106 drwx-- 37 4294967294 oldusers 4096 janv. 8 14:52 user107 drwx-- 31 4294967294 users4096 déc. 4 11:52 user108 drwx-- 4 user109oldusers 4096 sept. 21 2011 user109 drwx--x--x 45 4294967294 oldusers 4096 janv. 22 15:53 user110 drwx-- 31 4294967294 users4096 janv. 29 12:03 user111 for 571 homedirs (this number varies at each reboot)/662, the owner is the value 4294967294. For the 91 remaining homedirs, the owner is correct. The gidnumber is correctly mapped for all (only 5 differents values used for gidNumber). In /var/log/syslog, I can see : For example : user110 is mapped as 4294967294. but the command id user110 returns : uid=31124(user110) gid=666(oldusers) groupes=666(oldusers) user110 logs in (auth ldap) from tty1. He runs ls -l /home/user110/ : drwxr-xr-x 8 4294967294 oldusers 4096 janv. 19 2012 Bureau drwxr-xr-x 3 4294967294 oldusers 4096 déc. 2 2011 Documents drwxr-xr-x 2 4294967294 oldusers 4096 déc. 2 2011 Images Then, he runs touch /home/user110/test : drwxr-xr-x 8 4294967294 oldusers 4096 janv. 19 2012 Bureau drwxr-xr-x 3 4294967294 oldusers 4096 déc. 2 2011 Documents drwxr-xr-x 2 4294967294 oldusers 4096 déc. 2 2011 Images drwxr-xr-x 2 4294967294 oldusers0 févr. 13 16:01 test On the nfs server, If i do a ls -l in the same directory : drwxr-xr-x 8 user110 oldusers 4096 janv. 19 2012 Bureau
[Kernel-packages] [Bug 1301245] Re: System unresponsive under (IO/memory?) load
The problem still persists in 14.04 with updates (haven't checked 14.10). I have managed to solve(?) it by adding a noautogroup parameter to the kernel command line. More details: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1219548 ** Changed in: linux (Ubuntu) Status: Expired = 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/1301245 Title: System unresponsive under (IO/memory?) load Status in “linux” package in Ubuntu: Incomplete Bug description: Tasks producing a lot of IO activity and/or use large amount of memory (uncompressing a .tar.gz file, starting a VM in virtualbox) starve the rest of the system. The system is responding to user input very slowly (jerky mouse pointer movement with 1s intervals etc). I have not seen that issue on previous Ubuntu versions, this is the first time I use a 64 bit system with full disk encryption. 64bit Xubuntu 13.10. Full disk encryption. 4GB memory. Sony Vaio laptop. Same behavior observed with Nouveau and NVidia drivers. $ uname -a Linux laptop 3.11.0-18-generic #32-Ubuntu SMP Tue Feb 18 21:11:14 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ free -m total used free sharedbuffers cached Mem: 3870 2580 1289 0 33406 -/+ buffers/cache: 2140 1730 Swap: 4011959 3052 $ lspci 00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02) 00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port (rev 02) 00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) 00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05) 00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 05) 00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 3 (rev 05) 00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 4 (rev 05) 00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 (rev 05) 00:1c.6 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 7 (rev 05) 00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5) 00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05) 00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation GT218M [GeForce 310M] (rev a2) 01:00.1 Audio device: NVIDIA Corporation High Definition Audio Controller (rev a1) 02:00.0 Network controller: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) (rev 01) 03:00.0 SD Host controller: Ricoh Co Ltd MMC/SD Host Controller 03:00.1 System peripheral: Ricoh Co Ltd R5U2xx (R5U230 / R5U231 / R5U241) [Memory Stick Host Controller] 03:00.3 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 PCIe IEEE 1394 Controller 03:00.4 SD Host controller: Ricoh Co Ltd MMC/SD Host Controller 04:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8057 PCI-E Gigabit Ethernet Controller (rev 10) 05:00.0 Multimedia controller: Fujitsu Limited. Device 2036 06:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 03) 3f:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02) 3f:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02) 3f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02) 3f:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02) 3f:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02) 3f:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02) $ lsmod Module Size Used by pci_stub 12622 1 vboxpci23194 0 vboxnetadp 25670 0 vboxnetflt 27613 0 vboxdrv 320455 3 vboxnetadp,vboxnetflt,vboxpci bnep 19704 2 rfcomm 69130 16 parport_pc 32701 0 ppdev 17671 0 snd_hda_codec_hdmi 41154 4 snd_hda_codec_realtek56475 1
[Kernel-packages] [Bug 1383446] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1383446 Title: WARNING: CPU: 0 PID: 6 at /build/buildd/linux-3.13.0/fs/proc/generic.c:522 remove_proc_entry+0x19f/0x1b0() Status in “linux” package in Ubuntu: Confirmed Bug description: kernel oops during boot. no crash. kubuntu still usable. [ cut here ] [ 44.392154] WARNING: CPU: 0 PID: 6 at /build/buildd/linux-3.13.0/fs/proc/generic.c:522 remove_proc_entry+0x19f/0x1b0() [ 44.392157] remove_proc_entry: removing non-empty directory 'fs/nfsfs', leaking at least 'volumes' [ 44.392159] Modules linked in: bridge(+) stp llc ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables nfsv3 nfsv4 rfcomm bnep bluetooth ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi binfmt_misc nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_crypt ir_lirc_codec lirc_dev ir_mce_kbd_decoder ir_sanyo_decoder ir_sony_decoder ir_jvc_decoder ir_rc6_decoder ir_nec_decoder ir_rc5_decoder uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev joydev rc_rc6_mce pl2303 snd_usb_audio mceusb snd_usbmidi_lib rc_core usbserial snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event coretemp snd_rawmidi kvm_intel kvm dm_multipath scsi_dh snd_seq snd_seq_device snd_timer snd serio_raw lpc_ich soundcore mac_hid parport_pc ppdev lp parport hid_generic usbhid hid i915 e1000e video i2c_algo_bit psmouse drm_kms_helper firewire_ohci drm firewire_core ptp crc_itu_t pps_core [ 44.392237] CPU: 0 PID: 6 Comm: kworker/u8:0 Not tainted 3.13.0-37-generic #64-Ubuntu [ 44.392239] Hardware name: AOpen i965GMx-IF/i965GMx-IF, BIOS 6.00 PG 10/03/2008 [ 44.392243] Workqueue: netns cleanup_net [ 44.392245] 0009 880129b25c80 8171ed09 880129b25cc8 [ 44.392249] 880129b25cb8 8106773d 8801240fcd80 0005 [ 44.392252] a053b8a8 8800af22deb0 8801240fcdf5 880129b25d18 [ 44.392255] Call Trace: [ 44.392262] [8171ed09] dump_stack+0x45/0x56 [ 44.392266] [8106773d] warn_slowpath_common+0x7d/0xa0 [ 44.392270] [810677ac] warn_slowpath_fmt+0x4c/0x50 [ 44.392273] [8122989f] remove_proc_entry+0x19f/0x1b0 [ 44.392290] [a051b4e2] nfs_fs_proc_net_exit+0x62/0x70 [nfs] [ 44.392301] [a05215b2] nfs_net_exit+0x12/0x20 [nfs] [ 44.392304] [8161b409] ops_exit_list.isra.1+0x39/0x60 [ 44.392307] [8161bc90] cleanup_net+0x110/0x250 [ 44.392312] [810839c2] process_one_work+0x182/0x450 [ 44.392315] [810847b1] worker_thread+0x121/0x410 [ 44.392318] [81084690] ? rescuer_thread+0x430/0x430 [ 44.392321] [8108b492] kthread+0xd2/0xf0 [ 44.392324] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 [ 44.392328] [8172f77c] ret_from_fork+0x7c/0xb0 [ 44.392331] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 [ 44.392333] ---[ end trace d2c8090166cdd4d7 ]--- ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pascal 3346 F pulseaudio /dev/snd/controlC0: pascal 3346 F pulseaudio CurrentDesktop: KDE Date: Mon Oct 20 21:25:04 2014 HibernationDevice: RESUME=UUID=6e95fe83-ffc6-4f37-b81c-984d3bf3dc85 InstallationDate: Installed on 2011-10-23 (1092 days ago) InstallationMedia: Kubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) IwConfig: eth0 no wireless extensions. lono wireless extensions. virbr0no wireless extensions. MachineType: AOpen i965GMx-IF ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=6326dfb7-36be-4eae-85b8-e49695f3f331 ro security=selinux selinux=1 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-20 (183 days ago) dmi.bios.date: 10/03/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: i965GMx-IF dmi.board.vendor: AOpen dmi.board.version: 558EX10I690 dmi.chassis.type: 3 dmi.chassis.vendor: AOpen dmi.chassis.version: i965GMx-IF dmi.modalias:
[Kernel-packages] [Bug 1383446] [NEW] WARNING: CPU: 0 PID: 6 at /build/buildd/linux-3.13.0/fs/proc/generic.c:522 remove_proc_entry+0x19f/0x1b0()
Public bug reported: kernel oops during boot. no crash. kubuntu still usable. [ cut here ] [ 44.392154] WARNING: CPU: 0 PID: 6 at /build/buildd/linux-3.13.0/fs/proc/generic.c:522 remove_proc_entry+0x19f/0x1b0() [ 44.392157] remove_proc_entry: removing non-empty directory 'fs/nfsfs', leaking at least 'volumes' [ 44.392159] Modules linked in: bridge(+) stp llc ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables nfsv3 nfsv4 rfcomm bnep bluetooth ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi binfmt_misc nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_crypt ir_lirc_codec lirc_dev ir_mce_kbd_decoder ir_sanyo_decoder ir_sony_decoder ir_jvc_decoder ir_rc6_decoder ir_nec_decoder ir_rc5_decoder uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev joydev rc_rc6_mce pl2303 snd_usb_audio mceusb snd_usbmidi_lib rc_core usbserial snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event coretemp snd_rawmidi kvm_intel kvm dm_multipath scsi_dh snd_seq snd_seq_device snd_timer snd serio_raw lpc_ich soundcore mac_hid parport_pc ppdev lp parport hid_generic usbhid hid i915 e1000e video i2c_algo_bit psmouse drm_kms_helper firewire_ohci drm firewire_core ptp crc_itu_t pps_core [ 44.392237] CPU: 0 PID: 6 Comm: kworker/u8:0 Not tainted 3.13.0-37-generic #64-Ubuntu [ 44.392239] Hardware name: AOpen i965GMx-IF/i965GMx-IF, BIOS 6.00 PG 10/03/2008 [ 44.392243] Workqueue: netns cleanup_net [ 44.392245] 0009 880129b25c80 8171ed09 880129b25cc8 [ 44.392249] 880129b25cb8 8106773d 8801240fcd80 0005 [ 44.392252] a053b8a8 8800af22deb0 8801240fcdf5 880129b25d18 [ 44.392255] Call Trace: [ 44.392262] [8171ed09] dump_stack+0x45/0x56 [ 44.392266] [8106773d] warn_slowpath_common+0x7d/0xa0 [ 44.392270] [810677ac] warn_slowpath_fmt+0x4c/0x50 [ 44.392273] [8122989f] remove_proc_entry+0x19f/0x1b0 [ 44.392290] [a051b4e2] nfs_fs_proc_net_exit+0x62/0x70 [nfs] [ 44.392301] [a05215b2] nfs_net_exit+0x12/0x20 [nfs] [ 44.392304] [8161b409] ops_exit_list.isra.1+0x39/0x60 [ 44.392307] [8161bc90] cleanup_net+0x110/0x250 [ 44.392312] [810839c2] process_one_work+0x182/0x450 [ 44.392315] [810847b1] worker_thread+0x121/0x410 [ 44.392318] [81084690] ? rescuer_thread+0x430/0x430 [ 44.392321] [8108b492] kthread+0xd2/0xf0 [ 44.392324] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 [ 44.392328] [8172f77c] ret_from_fork+0x7c/0xb0 [ 44.392331] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 [ 44.392333] ---[ end trace d2c8090166cdd4d7 ]--- ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pascal 3346 F pulseaudio /dev/snd/controlC0: pascal 3346 F pulseaudio CurrentDesktop: KDE Date: Mon Oct 20 21:25:04 2014 HibernationDevice: RESUME=UUID=6e95fe83-ffc6-4f37-b81c-984d3bf3dc85 InstallationDate: Installed on 2011-10-23 (1092 days ago) InstallationMedia: Kubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) IwConfig: eth0 no wireless extensions. lono wireless extensions. virbr0no wireless extensions. MachineType: AOpen i965GMx-IF ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=6326dfb7-36be-4eae-85b8-e49695f3f331 ro security=selinux selinux=1 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-20 (183 days ago) dmi.bios.date: 10/03/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: i965GMx-IF dmi.board.vendor: AOpen dmi.board.version: 558EX10I690 dmi.chassis.type: 3 dmi.chassis.vendor: AOpen dmi.chassis.version: i965GMx-IF dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/03/2008:svnAOpen:pni965GMx-IF:pvrAO1JW:rvnAOpen:rni965GMx-IF:rvr558EX10I690:cvnAOpen:ct3:cvri965GMx-IF: dmi.product.name: i965GMx-IF dmi.product.version: AO1JW dmi.sys.vendor: AOpen ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1383446 Title: WARNING: CPU: 0 PID: 6 at
[Kernel-packages] [Bug 1383138] Please test proposed package
Hello Jesse, or anyone else affected, Accepted linux-firmware into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/linux- firmware/1.127.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- 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/1383138 Title: New BT firmware for Intel 7265 D0 chipset ROM spin Status in HWE Next Project: New Status in “linux-firmware” package in Ubuntu: Fix Released Status in “linux-firmware” source package in Trusty: Fix Committed Status in “linux-firmware” source package in Utopic: Fix Released Bug description: Firmware for 7265 Bluetooth ROM-spin SKU is in commit 0e5f6377: commit 0e5f63771d0df6d7859f7c4100a74d737c62ac88 Author: Tedd Ho-Jeong An tedd...@intel.com Date: Thu Oct 9 08:16:05 2014 -0700 linux-firmware: Add firmware patch for Intel Bluetooth 7265 ROM-spin(D0) This patch adds new firmware patch for - Intel Wireless 7265 Bluetooth ROM-spin SKU, also known as StP D0 This patch was submitted but reverted due to patch issue. The original patch's commit id: 935b5557b1485d839748b40f5721539b54d429e1 Signed-off-by: Tedd Ho-Jeong An tedd...@intel.com Signed-off-by: Kyle McMartin k...@kernel.org To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1383138/+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 1324544] Update Released
The verification of the Stable Release Update for makedumpfile has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1324544 Title: makedumpfile: kdump-config load fails with vmlinux kernel (vs. vmlinuz) Status in “makedumpfile” package in Ubuntu: Fix Released Status in “makedumpfile” source package in Trusty: Fix Released Status in “makedumpfile” source package in Utopic: Fix Released Status in “makedumpfile” package in Debian: New Bug description: SRU Justification: [Impact] Users of ppc64el hardware need the ability to use crashdumps to do kernel debugging. [Test Case] 1) apt-get install kdump-tools 2) kdump-config load 3) this should pass but fails because it expects vmlinuz [Regression Potential] This fix allows the existing case to work, but only checks for vmlinux if vmlinuz is missing. -- On ppc64el, there's no vmlinu/z/, only vmlinu/x/. Thus, kdump-config load fails as follows: # kdump-config load Cannot open `/boot/vmlinuz-3.13.0-27-generic': No such file or directory * failed to load kdump kernel This small patch (attached) fixes the issue. It defaults KDUMP_KERNEL to vmlinux if vmlinuz is not found. # cd /usr/sbin patch -p1 ~/kdump-config-vmlinux.patch patching file kdump-config # kdump-config load [...] * loaded kdump kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1324544/+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 1324544] Re: makedumpfile: kdump-config load fails with vmlinux kernel (vs. vmlinuz)
This bug was fixed in the package makedumpfile - 1.5.5-2ubuntu1.1 --- makedumpfile (1.5.5-2ubuntu1.1) trusty; urgency=medium * kdump-config: load kdump kernel from vmlinux too. (LP: #1324544) -- Mauricio Faria de Oliveira mauri...@linux.vnet.ibm.com Fri, 03 Oct 2014 11:46:27 +0200 ** Changed in: makedumpfile (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1324544 Title: makedumpfile: kdump-config load fails with vmlinux kernel (vs. vmlinuz) Status in “makedumpfile” package in Ubuntu: Fix Released Status in “makedumpfile” source package in Trusty: Fix Released Status in “makedumpfile” source package in Utopic: Fix Released Status in “makedumpfile” package in Debian: New Bug description: SRU Justification: [Impact] Users of ppc64el hardware need the ability to use crashdumps to do kernel debugging. [Test Case] 1) apt-get install kdump-tools 2) kdump-config load 3) this should pass but fails because it expects vmlinuz [Regression Potential] This fix allows the existing case to work, but only checks for vmlinux if vmlinuz is missing. -- On ppc64el, there's no vmlinu/z/, only vmlinu/x/. Thus, kdump-config load fails as follows: # kdump-config load Cannot open `/boot/vmlinuz-3.13.0-27-generic': No such file or directory * failed to load kdump kernel This small patch (attached) fixes the issue. It defaults KDUMP_KERNEL to vmlinux if vmlinuz is not found. # cd /usr/sbin patch -p1 ~/kdump-config-vmlinux.patch patching file kdump-config # kdump-config load [...] * loaded kdump kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1324544/+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 1364427] Update Released
The verification of the Stable Release Update for kexec-tools has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1364427 Title: kexec-tools: kexeced kernel hung Status in “kexec-tools” package in Ubuntu: Fix Released Status in “kexec-tools” source package in Trusty: Fix Released Status in “kexec-tools” source package in Utopic: Fix Released Bug description: SRU Justification: [Impact] Users of ppc64el hardware need the ability to use kexec kernels. [Test Case] 1) apt-get install kexec-tools 2) sudo kexec -l /boot/vmlinux --initrd=/boot/initrd.img 3) sudo kexec -e 4) Kernel should kexec into current kernel and work [Regression Potential] This patch backports the following patches from upstream kexec-tools: 7bb7c2a4bae8 kexec/ppc64: Handle reserved memory ranges d8847573a40f kexec/ppc64: Fix up ELF header and dt for PowerNV 90853885a859 ppc64/purgatory: Device tree values should be 2ca220389d21 kexec/ppc64: move to device tree version 17 335bad77fb07 kexec/ppc64: disabling exception handling when 45b33eb2e70c ppc64/kdump: Fix ELF header endianess These are all specific to POWER architecture. -- ---Problem Description--- kexec is not working with kernel 3.16 or later. The root cause is missing patch in the kexec-tools package provided with Ubuntu 14.04 and 14.10. ---uname output--- Linux qemu 3.16.0-10-generic #15-Ubuntu SMP Thu Aug 21 16:32:31 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux Machine Type = P8 ---Steps to Reproduce--- On a 14.10 guest or host, run : $ sudo kexec -l /boot/vmlinux --initrd=/boot/initrd.img-3.16.0-10-generic $ sudo kexec -e The kexeced kernel will hang here : [ 300.002862] Starting new kernel I'm in purgatory The root cause is the following kexec-tools's patch missing: 2ca220389d21 kexec/ppc64: move to device tree version 17 This patch is required to kexec kernel 3.16 and later. Among this patch, the following upstream pactches should be added to the current package : 335bad77fb07 kexec/ppc64: disabling exception handling when building the purgato 90853885a859 ppc64/purgatory: Device tree values should be read/stored in Big En In addition the following incoming patch should be applied : ppc64/kdump: Fix ELF header endianess (http://lists.infradead.org/pipermail/kexec/2014-July/012247.html) Another option to consider is to move to kexec-tools 2.0.7, and to apply the missing patches Is it possible to get this patches also applied to the kexec-tools shipped with 14.04 ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1364427/+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 1364427] Re: kexec-tools: kexeced kernel hung
This bug was fixed in the package kexec-tools - 1:2.0.6-0ubuntu2.1 --- kexec-tools (1:2.0.6-0ubuntu2.1) trusty; urgency=medium * Add the following patches to enable kexec-tools on ppc64el (LP: #1364427): - kexec-ppc64-Handle-reserved-memory-ranges-exported-b.patch - kexec-ppc64-Fix-up-ELF-header-and-dt-for-PowerNV-pla.patch - ppc64-purgatory-Device-tree-values-should-be-read-st.patch - kexec-ppc64-move-to-device-tree-version-17.patch - kexec-ppc64-disabling-exception-handling-when-buildi.patch - ppc64-kdump-Fix-ELF-header-endianess.patch -- Chris J Arges chris.j.ar...@canonical.com Wed, 01 Oct 2014 11:26:17 -0500 ** Changed in: kexec-tools (Ubuntu Trusty) Status: Fix Committed = 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/1364427 Title: kexec-tools: kexeced kernel hung Status in “kexec-tools” package in Ubuntu: Fix Released Status in “kexec-tools” source package in Trusty: Fix Released Status in “kexec-tools” source package in Utopic: Fix Released Bug description: SRU Justification: [Impact] Users of ppc64el hardware need the ability to use kexec kernels. [Test Case] 1) apt-get install kexec-tools 2) sudo kexec -l /boot/vmlinux --initrd=/boot/initrd.img 3) sudo kexec -e 4) Kernel should kexec into current kernel and work [Regression Potential] This patch backports the following patches from upstream kexec-tools: 7bb7c2a4bae8 kexec/ppc64: Handle reserved memory ranges d8847573a40f kexec/ppc64: Fix up ELF header and dt for PowerNV 90853885a859 ppc64/purgatory: Device tree values should be 2ca220389d21 kexec/ppc64: move to device tree version 17 335bad77fb07 kexec/ppc64: disabling exception handling when 45b33eb2e70c ppc64/kdump: Fix ELF header endianess These are all specific to POWER architecture. -- ---Problem Description--- kexec is not working with kernel 3.16 or later. The root cause is missing patch in the kexec-tools package provided with Ubuntu 14.04 and 14.10. ---uname output--- Linux qemu 3.16.0-10-generic #15-Ubuntu SMP Thu Aug 21 16:32:31 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux Machine Type = P8 ---Steps to Reproduce--- On a 14.10 guest or host, run : $ sudo kexec -l /boot/vmlinux --initrd=/boot/initrd.img-3.16.0-10-generic $ sudo kexec -e The kexeced kernel will hang here : [ 300.002862] Starting new kernel I'm in purgatory The root cause is the following kexec-tools's patch missing: 2ca220389d21 kexec/ppc64: move to device tree version 17 This patch is required to kexec kernel 3.16 and later. Among this patch, the following upstream pactches should be added to the current package : 335bad77fb07 kexec/ppc64: disabling exception handling when building the purgato 90853885a859 ppc64/purgatory: Device tree values should be read/stored in Big En In addition the following incoming patch should be applied : ppc64/kdump: Fix ELF header endianess (http://lists.infradead.org/pipermail/kexec/2014-July/012247.html) Another option to consider is to move to kexec-tools 2.0.7, and to apply the missing patches Is it possible to get this patches also applied to the kexec-tools shipped with 14.04 ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1364427/+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 1379201] Update Released
The verification of the Stable Release Update for openvswitch has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1379201 Title: openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.3: openvswitch kernel module failed to build [error: too many arguments to function ‘ip_select_ident’] Status in “linux” package in Ubuntu: Invalid Status in “openvswitch” package in Ubuntu: Invalid Status in “linux” source package in Precise: Invalid Status in “openvswitch” source package in Precise: Fix Released Bug description: SRU Justification: [Impact] Users can't use openvswitch DKMS package on precise/3.2. [Test Case] 1) install precise VM w/ 3.2 2) sudo apt-get install openvswitch-datapath-dkms 3) the module should build properly without failure [Regression Potential] This patch ifdefs based on kernel versions to select the correct function for that patchlevel. However because we only have 3 numbers in version.sh we may fail for trusty-lts kernels before 015c969f and after 3.13.11. -- Update gives this message. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.3 ProcVersionSignature: Ubuntu 3.2.0-69.103-generic 3.2.62 Uname: Linux 3.2.0-69-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.7 Architecture: amd64 DKMSKernelVersion: 3.2.0-70-generic Date: Thu Oct 9 09:35:00 2014 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True PackageArchitecture: all PackageVersion: 1.4.6-0ubuntu1.12.04.3 SourcePackage: openvswitch Title: openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.3: openvswitch 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/1379201/+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 1383138] Re: New BT firmware for Intel 7265 D0 chipset ROM spin
** Branch linked: lp:ubuntu/trusty-proposed/linux-firmware -- 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/1383138 Title: New BT firmware for Intel 7265 D0 chipset ROM spin Status in HWE Next Project: New Status in “linux-firmware” package in Ubuntu: Fix Released Status in “linux-firmware” source package in Trusty: Fix Committed Status in “linux-firmware” source package in Utopic: Fix Released Bug description: Firmware for 7265 Bluetooth ROM-spin SKU is in commit 0e5f6377: commit 0e5f63771d0df6d7859f7c4100a74d737c62ac88 Author: Tedd Ho-Jeong An tedd...@intel.com Date: Thu Oct 9 08:16:05 2014 -0700 linux-firmware: Add firmware patch for Intel Bluetooth 7265 ROM-spin(D0) This patch adds new firmware patch for - Intel Wireless 7265 Bluetooth ROM-spin SKU, also known as StP D0 This patch was submitted but reverted due to patch issue. The original patch's commit id: 935b5557b1485d839748b40f5721539b54d429e1 Signed-off-by: Tedd Ho-Jeong An tedd...@intel.com Signed-off-by: Kyle McMartin k...@kernel.org To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1383138/+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 1379201] Re: openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.3: openvswitch kernel module failed to build [error: too many arguments to function ‘ip_select_ident’]
This bug was fixed in the package openvswitch - 1.4.6-0ubuntu1.12.04.4 --- openvswitch (1.4.6-0ubuntu1.12.04.4) precise; urgency=medium * Update: d/p/0010-datapath_ip_select_ident_fix.patch: Fix stable kernel changes to ip_select_ident. (LP: #1379201) -- Chris J Arges chris.j.ar...@ubuntu.com Fri, 10 Oct 2014 14:31:19 -0500 ** Changed in: openvswitch (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1379201 Title: openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.3: openvswitch kernel module failed to build [error: too many arguments to function ‘ip_select_ident’] Status in “linux” package in Ubuntu: Invalid Status in “openvswitch” package in Ubuntu: Invalid Status in “linux” source package in Precise: Invalid Status in “openvswitch” source package in Precise: Fix Released Bug description: SRU Justification: [Impact] Users can't use openvswitch DKMS package on precise/3.2. [Test Case] 1) install precise VM w/ 3.2 2) sudo apt-get install openvswitch-datapath-dkms 3) the module should build properly without failure [Regression Potential] This patch ifdefs based on kernel versions to select the correct function for that patchlevel. However because we only have 3 numbers in version.sh we may fail for trusty-lts kernels before 015c969f and after 3.13.11. -- Update gives this message. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.3 ProcVersionSignature: Ubuntu 3.2.0-69.103-generic 3.2.62 Uname: Linux 3.2.0-69-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.7 Architecture: amd64 DKMSKernelVersion: 3.2.0-70-generic Date: Thu Oct 9 09:35:00 2014 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True PackageArchitecture: all PackageVersion: 1.4.6-0ubuntu1.12.04.3 SourcePackage: openvswitch Title: openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.3: openvswitch 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/1379201/+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 1275398] Re: i915 driver/i945 hardware: Mir GL clients are rendered as black (or transparent or crash) windows when using i945 graphics
just tried with mesa 10.4 daily and this crash seems to be fixed, now the unity-dash crashes but thats a different bug (https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1354412) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1275398 Title: i915 driver/i945 hardware: Mir GL clients are rendered as black (or transparent or crash) windows when using i945 graphics Status in Mir: Confirmed Status in “linux” package in Ubuntu: Invalid Status in “mesa” package in Ubuntu: In Progress Bug description: Running Mir on a Pentium D system with integrated i945 graphics, appears to work at first. The server starts and software clients are rendered correctly. However hardware (GL) clients are rendered as all black or transparent windows, despite logging to stdout that they think they are rendering: $ sudo bin/mir_demo_client_egltriangle Current active output is 1920x1200 +0+0 Server supports 2 of 6 surface pixel formats. Using format: 4 libEGL warning: unsupported platform (null) 1 FPS 33 FPS 60 FPS 60 FPS 60 FPS 60 FPS To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1275398/+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 1296660] Re: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA (unable to handle kernel NULL pointer dereference / con_set_unimap+0x32
Also seeing the issue here (on occasion) w/ 3.13.0-37-generic: fb: conflicting fb hw usage nouveaufb vs VESA VGA - removing generic driver Console: switching to colour dummy device 80x25 BUG: unable to handle kernel NULL pointer dereference at 0138 IP: [8145d382] con_set_unimap+0x32/0x290 Call Trace: [8131226d] ? apparmor_capable+0x1d/0x130 [81457223] vt_ioctl+0xe83/0x11c0 [8144ad3d] tty_ioctl+0x26d/0xbb0 [811d03a0] do_vfs_ioctl+0x2e0/0x4c0 [811d0601] SyS_ioctl+0x81/0xa0 [8172f82d] system_call_fastpath+0x1a/0x1f -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1296660 Title: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA (unable to handle kernel NULL pointer dereference / con_set_unimap+0x32 Status in “linux” package in Ubuntu: Confirmed Bug description: Booting hangs on a Ubuntu Trusty Tahr (development branch) [3.13.0-18-generic #38-Ubuntu SMP Mon Mar 17 21:40:06 UTC 2014 x86_64] based system. I can ping the system, but neither local nor remote login is possible. The system log shows this: Mar 23 21:59:08 minerva kernel: [ 36.301855] [drm] AST 2300 detected Mar 23 21:59:08 minerva kernel: [ 36.301899] [drm] dram 163200 1 16 0100 Mar 23 21:59:08 minerva kernel: [ 36.301968] [TTM] Zone kernel: Available graphics memory: 819 kiB Mar 23 21:59:08 minerva kernel: [ 36.301969] [TTM] Zone dma32: Available graphics memory: 2097152 kiB Mar 23 21:59:08 minerva kernel: [ 36.301969] [TTM] Initializing pool allocator Mar 23 21:59:08 minerva kernel: [ 36.301972] [TTM] Initializing DMA pool allocator Mar 23 21:59:09 minerva kernel: [ 36.470046] checking generic (f600 50) vs hw (f600 100) Mar 23 21:59:09 minerva kernel: [ 36.470047] fb: conflicting fb hw usage astdrmfb vs VESA VGA - removing generic driver Mar 23 21:59:09 minerva kernel: [ 36.632111] Console: switching to colour dummy device 80x25 Mar 23 21:59:09 minerva kernel: [ 36.632129] BUG: unable to handle kernel NULL pointer dereference at 0138 Mar 23 21:59:09 minerva kernel: [ 36.632134] IP: [81451e12] con_set_unimap+0x32/0x290 Mar 23 21:59:09 minerva kernel: [ 36.632136] PGD 35c24067 PUD 35c23067 PMD 0 Mar 23 21:59:09 minerva kernel: [ 36.632137] Oops: [#1] SMP Mar 23 21:59:09 minerva kernel: [ 36.632152] Modules linked in: x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm ast(+) ttm drm_kms_helper crct10dif_pclmul crc32_pclmul drm ghash_clmulni_intel aesni_intel aes_x86_64 syscopyarea sysfillrect sysimgblt lrw gf128mul glue_helper ablk_helper cryptd joydev lpc_ich shpchp ipmi_si video mac_hid lp parport raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq igb hid_generic i2c_algo_bit raid1 dca usbhid raid0 ahci ptp multipath hid usb_storage libahci pps_core linear Mar 23 21:59:09 minerva kernel: [ 36.632153] CPU: 4 PID: 665 Comm: setfont Not tainted 3.13.0-18-generic #38-Ubuntu Mar 23 21:59:09 minerva kernel: [ 36.632154] Hardware name: Supermicro X10SLL+-F/X10SLL+-F, BIOS 1.1a 11/01/2013 Mar 23 21:59:09 minerva kernel: [ 36.632155] task: 880408512fe0 ti: 88040852a000 task.ti: 88040852a000 Mar 23 21:59:09 minerva kernel: [ 36.632157] RIP: 0010:[81451e12] [81451e12] con_set_unimap+0x32/0x290 Mar 23 21:59:09 minerva kernel: [ 36.632157] RSP: 0018:88040852bd48 EFLAGS: 00010246 Mar 23 21:59:09 minerva kernel: [ 36.632158] RAX: 880404ee3308 RBX: 01bdcb10 RCX: c710 Mar 23 21:59:09 minerva kernel: [ 36.632159] RDX: 1674 RSI: 16761674 RDI: 0296 Mar 23 21:59:09 minerva kernel: [ 36.632159] RBP: 88040852bdb0 R08: 88040852a000 R09: Mar 23 21:59:09 minerva kernel: [ 36.632160] R10: 024f R11: 01e3 R12: Mar 23 21:59:09 minerva kernel: [ 36.632160] R13: 4b67 R14: 880404ee3000 R15: 880404ee3000 Mar 23 21:59:09 minerva kernel: [ 36.632161] FS: 7fa963158740() GS:88041fd0() knlGS: Mar 23 21:59:09 minerva kernel: [ 36.632162] CS: 0010 DS: ES: CR0: 80050033 Mar 23 21:59:09 minerva kernel: [ 36.632162] CR2: 0138 CR3: 000406428000 CR4: 001407e0 Mar 23 21:59:09 minerva kernel: [ 36.632163] DR0: DR1: DR2: Mar 23 21:59:09 minerva kernel: [ 36.632164] DR3: DR6: fffe0ff0 DR7: 0400 Mar 23 21:59:09 minerva kernel: [ 36.632164] Stack: Mar 23 21:59:09 minerva kernel: [ 36.632166] 8130bd6f 880408512fe0 0001 4b67 Mar 23 21:59:09 minerva kernel: [
[Kernel-packages] [Bug 1382251] Re: Kernel update breaks Picasa
I also have this problem. Picasa starts on 3.2.0-69 but not on 3.2.0-70. I also have not seen any error messages. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1382251 Title: Kernel update breaks Picasa Status in “linux” package in Ubuntu: Confirmed Bug description: After Kernel update (3.2.0-70-pae) Picasa for Linux no longer starts (shows splash screen, then after a while it closes). After restarting the laptop with previous kernel (3.2.0-69-pae), Picasa starts normally. Back and forth several times - confirmed Doesn't change if trying to start Picasa under Nvidia graphics card instead of on-board Intel (Bumblebee) Ubuntu 12.04 LTS ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-70-generic-pae 3.2.0-70.105 ProcVersionSignature: Ubuntu 3.2.0-70.105-generic-pae 3.2.63 Uname: Linux 3.2.0-70-generic-pae i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.7 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fer2137 F pulseaudio /dev/snd/pcmC0D0p: fer2137 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd9c0 irq 49' Mixer name : 'Realtek ALC269VB' Components : 'HDA:10ec0269,10431113,00100100' Controls : 24 Simple ctrls : 13 Date: Thu Oct 16 19:18:28 2014 HibernationDevice: RESUME=UUID=42df4fb0-c9fd-47aa-8274-ce9b3c1255d9 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: ASUSTeK Computer Inc. N53Jf MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-70-generic-pae root=UUID=42e515fa-dd55-4d3f-8668-29854772f749 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-70-generic-pae N/A linux-backports-modules-3.2.0-70-generic-pae N/A linux-firmware1.79.18 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: mei UpgradeStatus: Upgraded to precise on 2013-02-24 (599 days ago) dmi.bios.date: 01/25/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N53Jf.210 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N53Jf dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN53Jf.210:bd01/25/2011:svnASUSTeKComputerInc.:pnN53Jf:pvr1.0:rvnASUSTeKComputerInc.:rnN53Jf:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: N53Jf dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382251/+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 1338706] Re: Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to set xfermode (err_mask=0x40) on upstream kernels = 3.12
I am getting the same error. I have tried as well a Live USB of Ubuntu 14.10 Beta, which fails to detect the drive (I can't risk installing the whole system as this is my production computer). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338706 Title: Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to set xfermode (err_mask=0x40) on upstream kernels = 3.12 Status in “linux” package in Ubuntu: Triaged Bug description: Samsung SSD 840 Series failed to get NCQ Send/Recv Log Emask 0x1. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.55 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2131 F pulseaudio CurrentDesktop: Unity Date: Mon Jul 7 20:01:28 2014 HibernationDevice: RESUME=UUID=685afcb7-7aa6-4048-af15-091d3bcd3b35 InstallationDate: Installed on 2014-06-22 (14 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic root=UUID=d7c2e1cb-d046-460c-83b8-0cfbb330d095 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0901 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M3N78-EM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd09/10/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338706/+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 1382335] [NEW] mdadm+lvm+cryptsetup+big disks: bio too big device
You have been subscribed to a public bug: I installed two new 6TB disks (WD Red) as RAID1 and pmove'd stuff over from old 5x3TB RAID10 array to it (actually the move is still in progress, going to take some 17 hours or so) and I get lots of these (4971 so far) in dmesg: [58693.807553] bio too big device dm-7 (664 8) [58694.037060] bio too big device dm-7 (1024 8) Looks like an old kernel bug that was supposedly fixed in 2012: https://lkml.org/lkml/2012/10/15/398 The LV that apparently triggered that is 3TB in size (90% full) and encrypted with cryptsetup. I don't know if this is reproducible but I can try - it'd just take some two days every time (starting with restoring 3TB from backup). Ubuntu 14.04.1, 3.13.0-37-generic x86_64 kernel, Intel DQ57TM mobo, LSI 9211-8i SAS/SATA controller. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: trusty -- mdadm+lvm+cryptsetup+big disks: bio too big device https://bugs.launchpad.net/bugs/1382335 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
