[Kernel-packages] [Bug 1370018] Re: igb driver does not initialize network cards - no link intel I210 rev03
Thank you for the links, but it seems to me that kernel is quite the same as that one I tested before. The boot issue seems to be fixed but the driver has a lot more issues as described in post #21 (please download the full text because the posted version looks a little bit confusing). Three main issues are remaining: - massive plug/unplug problems - lost packets - wrong packet counter on the interface I am wondering if the problems are caused by the revision of that network card or is it known that the driver/nic is having that sort of problems? This is a build in dual-nic in a FUJITSU PRIMERGY TX2540 M1 server, with an approval for SLES and RHEL ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1370018 Title: igb driver does not initialize network cards - no link intel I210 rev03 Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: In Progress Status in “linux” source package in Utopic: Fix Released Bug description: Hi, our new server installed with ubuntu 14.04.1 lts updated to the latest upstream kernel (Ubuntu 3.13.0-35.62-generic 3.13.11.6), is equipped with two Intel Corporation I210 Gigabit Network Connection (rev 03) nics. The correct network driver is loaded, but the link to the network switch is not always (most of the times) established. Randomly one, two, all or none of the nics will have a network link established (means lights on the nic are dark). This happens with cold or soft boots. Attached you will find an apport-report from our system. We have compiled the latest intel igb-driver downloaded from the intel website (igb-5.2.9.4) and installed it manually in the system. # cp igb.ko /lib/modules/3.13.0-35-generic/kernel/drivers/net/ethernet/intel/igb/igb.ko # update-initramfs -c -k all !! Using the latest intel driver the problem seems to be solved !! If I can supply any further information, please let me know Thanks in advance --- ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: FUJITSU PRIMERGY TX2540 M1 Package: linux (not installed) ProcEnviron: LANGUAGE=de_AT:de TERM=xterm PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=0e2cf726-90e1-4868-8cc3-ae28d4d512d0 ro nomdmonddf nomdmonisw ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 RfKill: Error: [Errno 2] No such file or directory Tags: trusty trusty trusty Uname: Linux 3.13.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/15/2014 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V4.6.5.4 R1.12.0 for D3099-B1x dmi.board.name: D3099-B1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3099-B12 WGS03 GS01 dmi.chassis.asset.tag: cpsvs3 dmi.chassis.type: 17 dmi.chassis.vendor: FUJITSU dmi.chassis.version: TX2540M1F5 dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.5.4R1.12.0forD3099-B1x:bd07/15/2014:svnFUJITSU:pnPRIMERGYTX2540M1:pvrGS01:rvnFUJITSU:rnD3099-B1:rvrS26361-D3099-B12WGS03GS01:cvnFUJITSU:ct17:cvrTX2540M1F5: dmi.product.name: PRIMERGY TX2540 M1 dmi.product.version: GS01 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1370018/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1310800] Re: 056a:0302 Trusty Tahr, kernel 3.13: automatic load of wacom.ko driver cause a hard kernel panic
@riban: As I commented, I can't reproduce it any more. Or maybe it's random (I had a crash with the tablet in once, when reconnected with the wireless option). There is a bug upstream: http://sourceforge.net/p/linuxwacom/bugs/238/ --- maybe you can chime in there and see if the developers can help. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1310800 Title: 056a:0302 Trusty Tahr, kernel 3.13: automatic load of wacom.ko driver cause a hard kernel panic Status in “linux” package in Ubuntu: Confirmed Bug description: I have just upgraded to 14.04 from 13.10. I have a wacom cth-480 touch+pen tablet, which was not recognized on 13.10 (kernel 3.11). With the stock kernel from 14.04, I have an immediate kernel panic as soon as I plug in the tablet to the laptop. The system is a asus 1005PE (32 bit install), Xubuntu, up-to date: Linux asus-romano 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:08:14 UTC 2014 i686 i686 i686 GNU/Linux The really strange thing is that if I manually load the driver with `sudo modprobe wacom` *before* pluggin the tablet in, then the tablet is recognized and works ok: SYS: Apr 21 15:15:47 asus-romano kernel: [ 265.664161] usbcore: registered new interface driver wacom SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.088161] usb 2-1: new full-speed USB device number 2 using uhci_hcd SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253626] usb 2-1: New USB device found, idVendor=056a, idProduct=0302 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253641] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253651] usb 2-1: Product: Intuos PTS SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253659] usb 2-1: Manufacturer: Wacom Co.,Ltd. SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.257027] input: Wacom Intuos PT S Pen as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/input/input14 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.260630] input: Wacom Intuos PT S Finger as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.1/input/input15 SYS: Apr 21 15:15:52 asus-romano mtp-probe: checking bus 2, device 2: /sys/devices/pci:00/:00:1d.0/usb2/2-1 SYS: Apr 21 15:15:52 asus-romano mtp-probe: bus: 2, device: 2 was not an MTP device A screenshot of the kernel panic is added. I can reproduce it at will. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1318477] Re: [Dell XPS 15 9530] Wakes from sleep after exactly 24 hours + 3-5 seconds
Hi, I'm also affected by this issue. The system wakes itself randomly in my XPS 9530 laptop. I've disabled in the BIOS Smart Connect to see if this happens again. I'm running 14.04 with latests updates. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1318477 Title: [Dell XPS 15 9530] Wakes from sleep after exactly 24 hours + 3-5 seconds Status in Dell Sputnik: New Status in “linux” package in Ubuntu: Incomplete Bug description: Symptoms: The system will wake itself from sleep after very nearly exactly 24 hours, + / - 10 seconds or so. /var/log/pm-suspend.log will show this: Sat May 10 22:08:49 MDT 2014: performing suspend Sun May 11 22:08:54 MDT 2014: Awake. In this case the system has resumed after 24 hours and 5 seconds with no user request to do so. Steps to reproduce: Suspend machine by closing lid. The system can be plugged in to charge while it is suspended, and then subsequently unplugged, but the suspend occurs on battery power, and when the resume occurs the system is also not plugged in. I have not tested other permutations. No other action is necessary. The system will randomly resume 24 hours + 3-5 seconds later. WORKAROUND: Disable in BIOS Rapid Start, Smart Connect, and TPM. --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dpoler 2444 F pulseaudio /dev/snd/pcmC1D0p: dpoler 2444 F...m pulseaudio /dev/snd/controlC0: dpoler 2444 F pulseaudio CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied dmesg: write failed: Broken pipe DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes InstallationDate: Installed on 2014-05-06 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. XPS 15 9530 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=02812295-4462-4c5a-9e17-32d49164caf2 ro acpi=force quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Tags: trusty Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: bumblebee libvirtd sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 09/17/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: XPS 15 9530 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:bd09/17/2013:svnDellInc.:pnXPS159530:pvrA00:rvnDellInc.:rnXPS159530:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1318477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1243490] Re: [Lenovo Thinkpad Edge E525] Microphone mute key does not work
Also it's working on 3.8.0-44 with 201108-8258.
** Changed in: linux-lts-raring (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1243490
Title:
[Lenovo Thinkpad Edge E525] Microphone mute key does not work
Status in “linux” package in Ubuntu:
Fix Released
Status in “linux-lts-raring” package in Ubuntu:
Fix Released
Bug description:
CID: 201108-8258 Lenovo Thinkpad Edge E525
The microphone mute key does not work on this system (on F4).
Debugging information:
1. sudo showkey
keycode 190 press
keycode 190 release
2. xev
KeyRelease event, serial 40, synthetic NO, window 0x361,
root 0xa6, subw 0x0, time 50938864, (396,75), root:(462,127),
state 0x10, keycode 198 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 40, synthetic NO, window 0x361,
root 0xa6, subw 0x0, time 50938864, (396,75), root:(462,127),
state 0x10, keycode 198 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
It's weird that the keycode captured between xev and showkey is
different.
Bug 408903 is a similar bug, I open this one since the keycode
captured here is totally different.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 [modified:
boot/vmlinuz-3.8.0-29-generic]
ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5
Uname: Linux 3.8.0-29-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.8.0-29-generic.
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: Generic_1 [HD-Audio Generic], device 0: CONEXANT Analog [CONEXANT
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 1690 F pulseaudio
/dev/snd/controlC0: ubuntu 1690 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Generic'/'HD-Audio Generic at 0xf0b44000 irq 47'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100200'
Controls : 7
Simple ctrls : 1
Card0.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Card1.Amixer.info:
Card hw:1 'Generic_1'/'HD-Audio Generic at 0xf0b4 irq 16'
Mixer name : 'Conexant CX20590'
Components : 'HDA:14f1506e,17aa21ea,0010'
Controls : 22
Simple ctrls : 10
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
unknown'
Mixer name : 'ThinkPad EC (unknown)'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.Amixer.values:
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Tue Oct 22 21:42:42 2013
HibernationDevice: RESUME=UUID=f746ff69-0a94-4753-8729-e754d0d71a4c
InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64
(20130820.1)
MachineType: LENOVO 120024U
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic
root=UUID=5da29fe5-c880-4e79-9e8d-4420e3b1afe4 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.8.0-29-generic N/A
linux-backports-modules-3.8.0-29-generic N/A
linux-firmware1.79.6
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux-lts-raring
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/14/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8IET33WW(1.06)
dmi.board.asset.tag: Not Available
dmi.board.name: 120024U
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvr8IET33WW(1.06):bd07/14/2011:svnLENOVO:pn120024U:pvrThinkPadE525:rvnLENOVO:rn120024U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 120024U
dmi.product.version: ThinkPad E525
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1243490/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe :
[Kernel-packages] [Bug 1310800] Re: 056a:0302 Trusty Tahr, kernel 3.13: automatic load of wacom.ko driver cause a hard kernel panic
I have attached dump files. I note: BUG: unable to handle kernel NULL pointer dereference at 0018 - may be a clue? I have also posted upstream as suggested but that thread seems to have found a work-around so may be less interested. This seems to be an issue with how Ubuntu packages this module and should be fixed out-of-the-box rather than requiring (geeky) workarounds. (I can do that but we Ubuntu is supposed to be for Human Beings - not just geeks!) ** Attachment added: wacom_panic.zip https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310800/+attachment/4208525/+files/wacom_panic.zip -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1310800 Title: 056a:0302 Trusty Tahr, kernel 3.13: automatic load of wacom.ko driver cause a hard kernel panic Status in “linux” package in Ubuntu: Confirmed Bug description: I have just upgraded to 14.04 from 13.10. I have a wacom cth-480 touch+pen tablet, which was not recognized on 13.10 (kernel 3.11). With the stock kernel from 14.04, I have an immediate kernel panic as soon as I plug in the tablet to the laptop. The system is a asus 1005PE (32 bit install), Xubuntu, up-to date: Linux asus-romano 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:08:14 UTC 2014 i686 i686 i686 GNU/Linux The really strange thing is that if I manually load the driver with `sudo modprobe wacom` *before* pluggin the tablet in, then the tablet is recognized and works ok: SYS: Apr 21 15:15:47 asus-romano kernel: [ 265.664161] usbcore: registered new interface driver wacom SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.088161] usb 2-1: new full-speed USB device number 2 using uhci_hcd SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253626] usb 2-1: New USB device found, idVendor=056a, idProduct=0302 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253641] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253651] usb 2-1: Product: Intuos PTS SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253659] usb 2-1: Manufacturer: Wacom Co.,Ltd. SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.257027] input: Wacom Intuos PT S Pen as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/input/input14 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.260630] input: Wacom Intuos PT S Finger as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.1/input/input15 SYS: Apr 21 15:15:52 asus-romano mtp-probe: checking bus 2, device 2: /sys/devices/pci:00/:00:1d.0/usb2/2-1 SYS: Apr 21 15:15:52 asus-romano mtp-probe: bus: 2, device: 2 was not an MTP device A screenshot of the kernel panic is added. I can reproduce it at will. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1140716]
Hi Chris, meanwhile my current kernel is 3.16.1-46.1.g90bc0f1 I'm wondering (after a reinstall) that the semaphore bug hasn't occured yet, which was the case before (after a fresh install). This leads me to 4 definable possible reasons: 1. the named kernel revision somehow contains a fix for it. looking at the changes I could'nt get an affirmation to that assumption. 2. cgroup_memory=disabled has a relation to it. (That's why I removed it for now). 3. the BIOS settings (which could be different now) might have something to do with it. 4. I haven't installed KVM suppport yet. I'll post again if I find a reproducible explanation. Frank -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge Status in Direct Rendering Infrastructure: In Progress Status in The Linux Kernel: Invalid Status in “linux” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “mesa” package in Ubuntu: Triaged Status in “linux” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “mesa” source package in Precise: Triaged Status in “linux” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux” package in Debian: New Status in “linux” package in Fedora: Unknown Bug description: I'm getting errors about GPU hangs every minute or so (usually only when using FF and scrolling a webpage or something). I also get an annoying ubuntu dialog saying there is a system error. This didn't happen with 3.5.0-24-generic. Here is the dmesg: [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.658405] [ cut here ] [26285.658472] WARNING: at /build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 gen6_enable_rps+0x706/0x710 [i915]() [26285.658474] Hardware name: SATELLITE Z830 [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc lp parport e1000e ahci libahci [last unloaded: sdhci] [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic #40-Ubuntu [26285.658539] Call Trace: [26285.658549] [81051bef] warn_slowpath_common+0x7f/0xc0 [26285.658553] [81051c4a] warn_slowpath_null+0x1a/0x20 [26285.658569] [a02d32e6] gen6_enable_rps+0x706/0x710 [i915] [26285.658584] [a02bf3f6] intel_modeset_init_hw+0x66/0xa0 [i915] [26285.658595] [a02954b4] i915_reset+0x1a4/0x6e0 [i915] [26285.658601] [8101257b] ? __switch_to+0x12b/0x420 [26285.658612] [a029a943] i915_error_work_func+0xc3/0x110 [i915] [26285.658618] [8107097a] process_one_work+0x12a/0x420 [26285.658629] [a029a880] ? gen6_pm_rps_work+0xe0/0xe0 [i915] [26285.658632] [8107152e] worker_thread+0x12e/0x2f0 [26285.658636] [81071400] ? manage_workers.isra.26+0x200/0x200 [26285.658640] [81076023] kthread+0x93/0xa0 [26285.658644] [8168a3e4] kernel_thread_helper+0x4/0x10 [26285.658649] [81075f90] ? kthread_freezable_should_stop+0x70/0x70
[Kernel-packages] [Bug 1140716]
2. of course I meant cgroup_disable=memory -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge Status in Direct Rendering Infrastructure: In Progress Status in The Linux Kernel: Invalid Status in “linux” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “mesa” package in Ubuntu: Triaged Status in “linux” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “mesa” source package in Precise: Triaged Status in “linux” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux” package in Debian: New Status in “linux” package in Fedora: Unknown Bug description: I'm getting errors about GPU hangs every minute or so (usually only when using FF and scrolling a webpage or something). I also get an annoying ubuntu dialog saying there is a system error. This didn't happen with 3.5.0-24-generic. Here is the dmesg: [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.658405] [ cut here ] [26285.658472] WARNING: at /build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 gen6_enable_rps+0x706/0x710 [i915]() [26285.658474] Hardware name: SATELLITE Z830 [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc lp parport e1000e ahci libahci [last unloaded: sdhci] [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic #40-Ubuntu [26285.658539] Call Trace: [26285.658549] [81051bef] warn_slowpath_common+0x7f/0xc0 [26285.658553] [81051c4a] warn_slowpath_null+0x1a/0x20 [26285.658569] [a02d32e6] gen6_enable_rps+0x706/0x710 [i915] [26285.658584] [a02bf3f6] intel_modeset_init_hw+0x66/0xa0 [i915] [26285.658595] [a02954b4] i915_reset+0x1a4/0x6e0 [i915] [26285.658601] [8101257b] ? __switch_to+0x12b/0x420 [26285.658612] [a029a943] i915_error_work_func+0xc3/0x110 [i915] [26285.658618] [8107097a] process_one_work+0x12a/0x420 [26285.658629] [a029a880] ? gen6_pm_rps_work+0xe0/0xe0 [i915] [26285.658632] [8107152e] worker_thread+0x12e/0x2f0 [26285.658636] [81071400] ? manage_workers.isra.26+0x200/0x200 [26285.658640] [81076023] kthread+0x93/0xa0 [26285.658644] [8168a3e4] kernel_thread_helper+0x4/0x10 [26285.658649] [81075f90] ? kthread_freezable_should_stop+0x70/0x70 [26285.658652] [8168a3e0] ? gs_change+0x13/0x13 [26285.658654] ---[ end trace 59c6162fdfcbffee ]--- [26756.021167] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26756.021426] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26766.014093] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26766.014397] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26932.376233] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26932.376544] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
[Kernel-packages] [Bug 1140716]
Hi Chris, OK, nothing of the above was the reason. In my case it's simply this: /etc/X11/xorg.conf.d/20-intel.conf Section Device Identifier Intel Graphics Driver intel Option TearFreetrue EndSection I added it when the tearing scrolling through large webpages annoyed me. As soon as I added it, the problems quickly started. Selfmade problem. Frank -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge Status in Direct Rendering Infrastructure: In Progress Status in The Linux Kernel: Invalid Status in “linux” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “mesa” package in Ubuntu: Triaged Status in “linux” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “mesa” source package in Precise: Triaged Status in “linux” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux” package in Debian: New Status in “linux” package in Fedora: Unknown Bug description: I'm getting errors about GPU hangs every minute or so (usually only when using FF and scrolling a webpage or something). I also get an annoying ubuntu dialog saying there is a system error. This didn't happen with 3.5.0-24-generic. Here is the dmesg: [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.658405] [ cut here ] [26285.658472] WARNING: at /build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 gen6_enable_rps+0x706/0x710 [i915]() [26285.658474] Hardware name: SATELLITE Z830 [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc lp parport e1000e ahci libahci [last unloaded: sdhci] [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic #40-Ubuntu [26285.658539] Call Trace: [26285.658549] [81051bef] warn_slowpath_common+0x7f/0xc0 [26285.658553] [81051c4a] warn_slowpath_null+0x1a/0x20 [26285.658569] [a02d32e6] gen6_enable_rps+0x706/0x710 [i915] [26285.658584] [a02bf3f6] intel_modeset_init_hw+0x66/0xa0 [i915] [26285.658595] [a02954b4] i915_reset+0x1a4/0x6e0 [i915] [26285.658601] [8101257b] ? __switch_to+0x12b/0x420 [26285.658612] [a029a943] i915_error_work_func+0xc3/0x110 [i915] [26285.658618] [8107097a] process_one_work+0x12a/0x420 [26285.658629] [a029a880] ? gen6_pm_rps_work+0xe0/0xe0 [i915] [26285.658632] [8107152e] worker_thread+0x12e/0x2f0 [26285.658636] [81071400] ? manage_workers.isra.26+0x200/0x200 [26285.658640] [81076023] kthread+0x93/0xa0 [26285.658644] [8168a3e4] kernel_thread_helper+0x4/0x10 [26285.658649] [81075f90] ? kthread_freezable_should_stop+0x70/0x70 [26285.658652] [8168a3e0] ? gs_change+0x13/0x13 [26285.658654] ---[ end trace 59c6162fdfcbffee ]--- [26756.021167] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26756.021426] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp
[Kernel-packages] [Bug 1140716]
(In reply to comment #191) What information is most useful for these repeating issues, as it just happened again: Sep 16 08:32:59 arrowsmithlap1 kernel: [1182242.139690] [drm] stuck on render ring Sep 16 08:32:59 arrowsmithlap1 kernel: [1182242.139699] [drm] stuck on blitter ring So long as it is the same event, there is no more information we need other than testing feedback for an eventual workaround. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge Status in Direct Rendering Infrastructure: In Progress Status in The Linux Kernel: Invalid Status in “linux” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “mesa” package in Ubuntu: Triaged Status in “linux” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “mesa” source package in Precise: Triaged Status in “linux” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux” package in Debian: New Status in “linux” package in Fedora: Unknown Bug description: I'm getting errors about GPU hangs every minute or so (usually only when using FF and scrolling a webpage or something). I also get an annoying ubuntu dialog saying there is a system error. This didn't happen with 3.5.0-24-generic. Here is the dmesg: [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.658405] [ cut here ] [26285.658472] WARNING: at /build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 gen6_enable_rps+0x706/0x710 [i915]() [26285.658474] Hardware name: SATELLITE Z830 [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc lp parport e1000e ahci libahci [last unloaded: sdhci] [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic #40-Ubuntu [26285.658539] Call Trace: [26285.658549] [81051bef] warn_slowpath_common+0x7f/0xc0 [26285.658553] [81051c4a] warn_slowpath_null+0x1a/0x20 [26285.658569] [a02d32e6] gen6_enable_rps+0x706/0x710 [i915] [26285.658584] [a02bf3f6] intel_modeset_init_hw+0x66/0xa0 [i915] [26285.658595] [a02954b4] i915_reset+0x1a4/0x6e0 [i915] [26285.658601] [8101257b] ? __switch_to+0x12b/0x420 [26285.658612] [a029a943] i915_error_work_func+0xc3/0x110 [i915] [26285.658618] [8107097a] process_one_work+0x12a/0x420 [26285.658629] [a029a880] ? gen6_pm_rps_work+0xe0/0xe0 [i915] [26285.658632] [8107152e] worker_thread+0x12e/0x2f0 [26285.658636] [81071400] ? manage_workers.isra.26+0x200/0x200 [26285.658640] [81076023] kthread+0x93/0xa0 [26285.658644] [8168a3e4] kernel_thread_helper+0x4/0x10 [26285.658649] [81075f90] ? kthread_freezable_should_stop+0x70/0x70 [26285.658652] [8168a3e0] ? gs_change+0x13/0x13 [26285.658654] ---[ end trace 59c6162fdfcbffee ]--- [26756.021167] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26756.021426] [drm] Enabling
[Kernel-packages] [Bug 1140716]
What information is most useful for these repeating issues, as it just happened again: Sep 16 08:32:59 arrowsmithlap1 kernel: [1182242.139690] [drm] stuck on render ring Sep 16 08:32:59 arrowsmithlap1 kernel: [1182242.139699] [drm] stuck on blitter ring Sep 16 08:32:59 arrowsmithlap1 kernel: [1182242.140239] [drm] GPU HANG: ecode 0:0xf4e9fffe, in Xorg [26353], reason: Ring hung, action: reset Sep 16 08:32:59 arrowsmithlap1 kernel: [1182242.140750] [drm:i915_context_is_banned] *ERROR* gpu hanging too fast, banning! Sep 16 08:32:59 arrowsmithlap1 kernel: [drm] stuck on render ring Sep 16 08:32:59 arrowsmithlap1 kernel: [drm] stuck on blitter ring Sep 16 08:32:59 arrowsmithlap1 kernel: [drm] GPU HANG: ecode 0:0xf4e9fffe, in Xorg [26353], reason: Ring hung, action: reset Sep 16 08:32:59 arrowsmithlap1 kernel: [drm:i915_context_is_banned] *ERROR* gpu hanging too fast, banning! Sep 16 08:33:01 arrowsmithlap1 kernel: [1182244.142445] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off Sep 16 08:33:01 arrowsmithlap1 kernel: [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off The only thing under my /etc/X11/xorg.conf.d/ is 00-keyboard.conf (system generated). Do you want a copy of /sys/class/drm/card0/error every time? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge Status in Direct Rendering Infrastructure: In Progress Status in The Linux Kernel: Invalid Status in “linux” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “mesa” package in Ubuntu: Triaged Status in “linux” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “mesa” source package in Precise: Triaged Status in “linux” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux” package in Debian: New Status in “linux” package in Fedora: Unknown Bug description: I'm getting errors about GPU hangs every minute or so (usually only when using FF and scrolling a webpage or something). I also get an annoying ubuntu dialog saying there is a system error. This didn't happen with 3.5.0-24-generic. Here is the dmesg: [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.658405] [ cut here ] [26285.658472] WARNING: at /build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 gen6_enable_rps+0x706/0x710 [i915]() [26285.658474] Hardware name: SATELLITE Z830 [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc lp parport e1000e ahci libahci [last unloaded: sdhci] [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic #40-Ubuntu [26285.658539] Call Trace: [26285.658549] [81051bef] warn_slowpath_common+0x7f/0xc0 [26285.658553] [81051c4a] warn_slowpath_null+0x1a/0x20 [26285.658569] [a02d32e6] gen6_enable_rps+0x706/0x710 [i915] [26285.658584] [a02bf3f6] intel_modeset_init_hw+0x66/0xa0 [i915] [26285.658595] [a02954b4] i915_reset+0x1a4/0x6e0 [i915]
[Kernel-packages] [Bug 1140716]
(In reply to comment #189) Hi Chris, OK, nothing of the above was the reason. In my case it's simply this: /etc/X11/xorg.conf.d/20-intel.conf Section Device Identifier Intel Graphics Driver intel Option TearFreetrue EndSection I added it when the tearing scrolling through large webpages annoyed me. As soon as I added it, the problems quickly started. Selfmade problem. Not really, https://bugs.freedesktop.org/show_bug.cgi?id=70764 tracks that this hang is more likely with TearFree (fundamentally the hang is still the same hardware issue, but it is interesting that TearFree has a higher chance of hitting it). If you want to experiment: http://cgit.freedesktop.org/~ickle/linux-2.6/log/?h=requests should have an interesting fix, at least for trying to prevent the TearFree leading to the semaphore hang. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge Status in Direct Rendering Infrastructure: In Progress Status in The Linux Kernel: Invalid Status in “linux” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “mesa” package in Ubuntu: Triaged Status in “linux” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “mesa” source package in Precise: Triaged Status in “linux” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux” package in Debian: New Status in “linux” package in Fedora: Unknown Bug description: I'm getting errors about GPU hangs every minute or so (usually only when using FF and scrolling a webpage or something). I also get an annoying ubuntu dialog saying there is a system error. This didn't happen with 3.5.0-24-generic. Here is the dmesg: [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.658405] [ cut here ] [26285.658472] WARNING: at /build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 gen6_enable_rps+0x706/0x710 [i915]() [26285.658474] Hardware name: SATELLITE Z830 [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc lp parport e1000e ahci libahci [last unloaded: sdhci] [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic #40-Ubuntu [26285.658539] Call Trace: [26285.658549] [81051bef] warn_slowpath_common+0x7f/0xc0 [26285.658553] [81051c4a] warn_slowpath_null+0x1a/0x20 [26285.658569] [a02d32e6] gen6_enable_rps+0x706/0x710 [i915] [26285.658584] [a02bf3f6] intel_modeset_init_hw+0x66/0xa0 [i915] [26285.658595] [a02954b4] i915_reset+0x1a4/0x6e0 [i915] [26285.658601] [8101257b] ? __switch_to+0x12b/0x420 [26285.658612] [a029a943] i915_error_work_func+0xc3/0x110 [i915] [26285.658618] [8107097a] process_one_work+0x12a/0x420 [26285.658629] [a029a880] ? gen6_pm_rps_work+0xe0/0xe0 [i915] [26285.658632] [8107152e] worker_thread+0x12e/0x2f0 [26285.658636] [81071400] ?
[Kernel-packages] [Bug 1140716] Re: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge
** Bug watch added: freedesktop.org Bugzilla #70764 https://bugs.freedesktop.org/show_bug.cgi?id=70764 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge Status in Direct Rendering Infrastructure: In Progress Status in The Linux Kernel: Invalid Status in “linux” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “mesa” package in Ubuntu: Triaged Status in “linux” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “mesa” source package in Precise: Triaged Status in “linux” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux” package in Debian: New Status in “linux” package in Fedora: Unknown Bug description: I'm getting errors about GPU hangs every minute or so (usually only when using FF and scrolling a webpage or something). I also get an annoying ubuntu dialog saying there is a system error. This didn't happen with 3.5.0-24-generic. Here is the dmesg: [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.658405] [ cut here ] [26285.658472] WARNING: at /build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 gen6_enable_rps+0x706/0x710 [i915]() [26285.658474] Hardware name: SATELLITE Z830 [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc lp parport e1000e ahci libahci [last unloaded: sdhci] [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic #40-Ubuntu [26285.658539] Call Trace: [26285.658549] [81051bef] warn_slowpath_common+0x7f/0xc0 [26285.658553] [81051c4a] warn_slowpath_null+0x1a/0x20 [26285.658569] [a02d32e6] gen6_enable_rps+0x706/0x710 [i915] [26285.658584] [a02bf3f6] intel_modeset_init_hw+0x66/0xa0 [i915] [26285.658595] [a02954b4] i915_reset+0x1a4/0x6e0 [i915] [26285.658601] [8101257b] ? __switch_to+0x12b/0x420 [26285.658612] [a029a943] i915_error_work_func+0xc3/0x110 [i915] [26285.658618] [8107097a] process_one_work+0x12a/0x420 [26285.658629] [a029a880] ? gen6_pm_rps_work+0xe0/0xe0 [i915] [26285.658632] [8107152e] worker_thread+0x12e/0x2f0 [26285.658636] [81071400] ? manage_workers.isra.26+0x200/0x200 [26285.658640] [81076023] kthread+0x93/0xa0 [26285.658644] [8168a3e4] kernel_thread_helper+0x4/0x10 [26285.658649] [81075f90] ? kthread_freezable_should_stop+0x70/0x70 [26285.658652] [8168a3e0] ? gs_change+0x13/0x13 [26285.658654] ---[ end trace 59c6162fdfcbffee ]--- [26756.021167] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26756.021426] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26766.014093] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26766.014397] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26932.376233] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26932.376544] [drm]
[Kernel-packages] [Bug 1354459] Re: kernel crash power 8 bare metal
please retest with neihu 140919-1 or later image which uses kernel 3.13.0-36.63+hwe3 ** Tags added: bdw-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/1354459 Title: kernel crash power 8 bare metal Status in “linux” package in Ubuntu: Incomplete Bug description: I'm seeing crashes on power8 bare metal (powerNV). happens sometimes. [ 66.852889] Workqueue: events .work_for_cpu_fn [ 66.852950] Call Trace: [ 66.852977] [c00fe6edae60] [c0016af0] .show_stack+0x170/0x290 (unreliable) [ 66.853063] [c00fe6edaf50] [c0966fc0] .dump_stack+0x88/0xb4 [ 66.853138] [c00fe6edafd0] [c0111680] .rcu_check_callbacks+0x5b0/0x950 [ 66.853225] [c00fe6edb100] [c00ad2f8] .update_process_times+0x58/0xb0 [ 66.853311] [c00fe6edb190] [c011f890] .tick_sched_handle.isra.17+0x40/0xd0 [ 66.853397] [c00fe6edb220] [c011f984] .tick_sched_timer+0x64/0xa0 [ 66.853472] [c00fe6edb2c0] [c00cda50] .__run_hrtimer+0xa0/0x270 [ 66.853546] [c00fe6edb360] [c00ce948] .hrtimer_interrupt+0x148/0x330 [ 66.853633] [c00fe6edb470] [c0020a00] .timer_interrupt+0x120/0x2c0 [ 66.853718] [c00fe6edb520] [c00023d8] decrementer_common+0x158/0x180 [ 66.853805] --- Exception: 901 at ._raw_spin_lock_irqsave+0xb0/0x110 [ 66.853805] LR = ._raw_spin_lock_irqsave+0xe8/0x110 [ 66.853916] [c00fe6edb810] [c00f0cb4] .finish_wait+0x74/0xb0 (unreliable) [ 66.854008] [c00fe6edb8a0] [deeaa4f4] .ipr_probe_ioa+0xd84/0x1370 [ipr] [ 66.854096] [c00fe6edb9d0] [deeb25c4] .ipr_probe+0x44/0x4c0 [ipr] [ 66.854171] [c00fe6edbac0] [c0516cfc] .local_pci_probe+0x4c/0xe0 [ 66.854245] [c00fe6edbb40] [c00bae68] .work_for_cpu_fn+0x38/0x60 [ 66.854319] [c00fe6edbbc0] [c00bf628] .process_one_work+0x1a8/0x4d0 [ 66.854405] [c00fe6edbc60] [c00c04fc] .worker_thread+0x38c/0x4a0 [ 66.854479] [c00fe6edbd30] [c00c98a0] .kthread+0x110/0x130 [ 66.854553] [c00fe6edbe30] [c000a460] .ret_from_kernel_thread+0x5c/0x7c [ 72.412653] BUG: soft lockup - CPU#40 stuck for 22s! [kworker/40:0:209] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1354459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371477] [NEW] Atheros bluetooth module [0cf3:311e] doesn't work because it is not handled by ath3k
Public bug reported: SRU Justification: Impact: Atheros bluetooth module [0cf3:311e] doesn't work Fix: commit below from upstream, clean cherry-picks. Testcase: we already tested and delivered the fix by dkms in OEM projects, works well. commit af6acae581d502c3e42390497ab27496c3a81a0d Author: Oliver Neukum oli...@neukum.org Date: Thu Jan 16 15:37:11 2014 +0100 Bluetooth: Enable Atheros 0cf3:311e for firmware upload The device will bind to btusb without firmware, but with the original buggy firmware device discovery does not work. No devices are detected. ** Affects: hwe-next Importance: High Status: In Progress ** Affects: linux (Ubuntu) Importance: High Assignee: Adam Lee (adam8157) Status: In Progress ** Changed in: hwe-next Importance: Undecided = High ** Changed in: hwe-next Status: New = In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371477 Title: Atheros bluetooth module [0cf3:311e] doesn't work because it is not handled by ath3k Status in HWE Next Project: In Progress Status in “linux” package in Ubuntu: In Progress Bug description: SRU Justification: Impact: Atheros bluetooth module [0cf3:311e] doesn't work Fix: commit below from upstream, clean cherry-picks. Testcase: we already tested and delivered the fix by dkms in OEM projects, works well. commit af6acae581d502c3e42390497ab27496c3a81a0d Author: Oliver Neukum oli...@neukum.org Date: Thu Jan 16 15:37:11 2014 +0100 Bluetooth: Enable Atheros 0cf3:311e for firmware upload The device will bind to btusb without firmware, but with the original buggy firmware device discovery does not work. No devices are detected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1371477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371477] Re: Atheros bluetooth module [0cf3:311e] doesn't work because it is not handled by ath3k
patch has been submitted to kernel-team@ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371477 Title: Atheros bluetooth module [0cf3:311e] doesn't work because it is not handled by ath3k Status in HWE Next Project: In Progress Status in “linux” package in Ubuntu: In Progress Bug description: SRU Justification: Impact: Atheros bluetooth module [0cf3:311e] doesn't work Fix: commit below from upstream, clean cherry-picks. Testcase: we already tested and delivered the fix by dkms in OEM projects, works well. commit af6acae581d502c3e42390497ab27496c3a81a0d Author: Oliver Neukum oli...@neukum.org Date: Thu Jan 16 15:37:11 2014 +0100 Bluetooth: Enable Atheros 0cf3:311e for firmware upload The device will bind to btusb without firmware, but with the original buggy firmware device discovery does not work. No devices are detected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1371477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1219652] Re: [Dell Latitude 3330] Wireless key does not work.
Verified with 12.04.5 (3.13.0-32) on 201302-12844, It works.
Therefore I will close this bug as Fix-Released, thanks!
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1219652
Title:
[Dell Latitude 3330] Wireless key does not work.
Status in “linux” package in Ubuntu:
Fix Released
Bug description:
CID: 201302-12844 Dell Latitude 3330
The wireless hot key does not work on this system.
Debugging with sudo showkey -k, only key code 240 press was
captured:
ubuntu@201302-12844:~$ sudo showkey -k
kb mode was ?UNKNOWN?
[ if you are trying this under X, it might not work
since the X server is also reading /dev/console ]
press any key (program terminates 10s after last keypress)...
keycode 28 release
keycode 240 press
keycode 240 press
keycode 240 press
keycode 240 press
keycode 240 press
keycode 29 press
^Ccaught signal 2, cleaning up...
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 [modified:
boot/vmlinuz-3.8.0-29-generic]
ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5
Uname: Linux 3.8.0-29-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
Date: Mon Sep 2 14:12:34 2013
InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64
(20130820.1)
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-lts-raring
UpgradeStatus: No upgrade log present (probably fresh install)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.8.0-29-generic.
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1577 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf7c3 irq 47'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:111d76df,102805dc,00100203
HDA:80862806,80860101,0010'
Controls : 26
Simple ctrls : 10
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=1eb734da-756a-421d-9ccd-bbd1044454b6
InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64
(20130820.1)
MachineType: Dell Inc. Latitude 3330
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic
root=UUID=4580c6a4-0261-40f2-8e43-adfe3bc0f848 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5
RelatedPackageVersions:
linux-restricted-modules-3.8.0-29-generic N/A
linux-backports-modules-3.8.0-29-generic N/A
linux-firmware1.79.6
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: precise running-unity
Uname: Linux 3.8.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 03/08/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A00
dmi.board.name: 4LA010
dmi.board.vendor: Dell Inc.
dmi.board.version: S00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA00:bd03/08/2013:svnDellInc.:pnLatitude3330:pvr01:rvnDellInc.:rn4LA010:rvrS00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude 3330
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1219652/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1153618] Re: Support Realtek RTS5227 card reader
1, Neither SD nor MMC do work -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1153618 Title: Support Realtek RTS5227 card reader Status in HWE Next Project: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Bug description: Support of Realtek RTS5227 card reader is currently missing in the kernel, though the support is already in upstream, we need to backport it from upstream to enable this device. 03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device [10ec:5227] (rev 01) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1153618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371526] Re: ceph-disk-prepare command always fails; new partition table not avaliable until reboot
I poked at this with some additional volumes attached to the cloud instance: Offending device: ubuntu@juju-t-machine-22:~$ sudo umount /dev/vdb ubuntu@juju-t-machine-22:~$ sudo lsof | grep vdb jbd2/vdb- 1268 root cwd DIR 253,1 4096 2 / jbd2/vdb- 1268 root rtd DIR 253,1 4096 2 / jbd2/vdb- 1268 root txt unknown /proc/1268/exe Additional device: ubuntu@juju-t-machine-22:~$ sudo mount /dev/vdc /mnt2 ubuntu@juju-t-machine-22:~$ sudo lsof | grep vdc jbd2/vdc- 16058 root cwd DIR 253,1 4096 2 / jbd2/vdc- 16058 root rtd DIR 253,1 4096 2 / jbd2/vdc- 16058 root txt unknown /proc/16058/exe ubuntu@juju-t-machine-22:~$ sudo umount /dev/vdc ubuntu@juju-t-machine-22:~$ sudo lsof | grep vdc As you can see, the jbd2 process for vdb appears to hang around, which I think is what is keeping the partition table locked in kernel and hence stale. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371526 Title: ceph-disk-prepare command always fails; new partition table not avaliable until reboot Status in “ceph” package in Ubuntu: New Status in “linux” package in Ubuntu: New Bug description: $ sudo ceph-disk-prepare --fs-type xfs --zap-disk /dev/vdb Caution: invalid backup GPT header, but valid main header; regenerating backup header from main header. Warning! Main and backup partition tables differ! Use the 'c' and 'e' options on the recovery transformation menu to examine the two tables. Warning! One or more CRCs don't match. You should repair the disk! Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk verification and recovery are STRONGLY recommended. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. GPT data structures destroyed! You may now partition the disk using fdisk or other utilities. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. The operation has completed successfully. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. The operation has completed successfully. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. The operation has completed successfully. mkfs.xfs: cannot open /dev/vdb1: Device or resource busy ceph-disk: Error: Command '['/sbin/mkfs', '-t', 'xfs', '-f', '-i', 'size=2048', '--', '/dev/vdb1']' returned non-zero exit status 1 I can reproduce this consistently across ceph nodes; also impacts on the way we use swift for storage as well. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ceph 0.80.5-1 ProcVersionSignature: User Name 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 Date: Fri Sep 19 09:39:18 2014 Ec2AMI: ami-0084 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 SourcePackage: ceph UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1371526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371526] Re: ceph-disk-prepare command always fails; new partition table not avaliable until reboot
sudo lshw -class disk -class storage *-ide description: IDE interface product: 82371SB PIIX3 IDE [Natoma/Triton II] vendor: Intel Corporation physical id: 1.1 bus info: pci@:00:01.1 version: 00 width: 32 bits clock: 33MHz capabilities: ide bus_master configuration: driver=ata_piix latency=0 resources: irq:0 ioport:1f0(size=8) ioport:3f6 ioport:170(size=8) ioport:376 ioport:c0e0(size=16) *-scsi:0 description: SCSI storage controller product: Virtio block device vendor: Red Hat, Inc physical id: 4 bus info: pci@:00:04.0 version: 00 width: 32 bits clock: 33MHz capabilities: scsi msix bus_master cap_list configuration: driver=virtio-pci latency=0 resources: irq:11 ioport:c000(size=64) memory:febd2000-febd2fff *-scsi:1 description: SCSI storage controller product: Virtio block device vendor: Red Hat, Inc physical id: 5 bus info: pci@:00:05.0 version: 00 width: 32 bits clock: 33MHz capabilities: scsi msix bus_master cap_list configuration: driver=virtio-pci latency=0 resources: irq:10 ioport:c040(size=64) memory:febd3000-febd3fff *-scsi:2 description: SCSI storage controller product: Virtio block device vendor: Red Hat, Inc physical id: 7 bus info: pci@:00:07.0 version: 00 width: 32 bits clock: 33MHz capabilities: scsi msix bus_master cap_list configuration: driver=virtio-pci latency=0 resources: irq:10 ioport:1000(size=64) memory:8000-8fff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371526 Title: ceph-disk-prepare command always fails; new partition table not avaliable until reboot Status in “ceph” package in Ubuntu: New Status in “linux” package in Ubuntu: Incomplete Bug description: $ sudo ceph-disk-prepare --fs-type xfs --zap-disk /dev/vdb Caution: invalid backup GPT header, but valid main header; regenerating backup header from main header. Warning! Main and backup partition tables differ! Use the 'c' and 'e' options on the recovery transformation menu to examine the two tables. Warning! One or more CRCs don't match. You should repair the disk! Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk verification and recovery are STRONGLY recommended. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. GPT data structures destroyed! You may now partition the disk using fdisk or other utilities. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. The operation has completed successfully. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. The operation has completed successfully. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. The operation has completed successfully. mkfs.xfs: cannot open /dev/vdb1: Device or resource busy ceph-disk: Error: Command '['/sbin/mkfs', '-t', 'xfs', '-f', '-i', 'size=2048', '--', '/dev/vdb1']' returned non-zero exit status 1 I can reproduce this consistently across ceph nodes; also impacts on the way we use swift for storage as well. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ceph 0.80.5-1 ProcVersionSignature: User Name 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 Date: Fri Sep 19 09:39:18 2014 Ec2AMI: ami-0084 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 SourcePackage: ceph UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1371526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371526] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1371526 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/1371526 Title: ceph-disk-prepare command always fails; new partition table not avaliable until reboot Status in “ceph” package in Ubuntu: New Status in “linux” package in Ubuntu: Incomplete Bug description: $ sudo ceph-disk-prepare --fs-type xfs --zap-disk /dev/vdb Caution: invalid backup GPT header, but valid main header; regenerating backup header from main header. Warning! Main and backup partition tables differ! Use the 'c' and 'e' options on the recovery transformation menu to examine the two tables. Warning! One or more CRCs don't match. You should repair the disk! Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk verification and recovery are STRONGLY recommended. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. GPT data structures destroyed! You may now partition the disk using fdisk or other utilities. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. The operation has completed successfully. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. The operation has completed successfully. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. The operation has completed successfully. mkfs.xfs: cannot open /dev/vdb1: Device or resource busy ceph-disk: Error: Command '['/sbin/mkfs', '-t', 'xfs', '-f', '-i', 'size=2048', '--', '/dev/vdb1']' returned non-zero exit status 1 I can reproduce this consistently across ceph nodes; also impacts on the way we use swift for storage as well. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ceph 0.80.5-1 ProcVersionSignature: User Name 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 Date: Fri Sep 19 09:39:18 2014 Ec2AMI: ami-0084 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 SourcePackage: ceph UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1371526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371526] Re: ceph-disk-prepare command always fails; new partition table not avaliable until reboot
This only appears to happen with the device on first boot; after a reboot mount/umount drops all jdb2 processes as I think it should. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371526 Title: ceph-disk-prepare command always fails; new partition table not avaliable until reboot Status in “ceph” package in Ubuntu: New Status in “linux” package in Ubuntu: Incomplete Bug description: $ sudo ceph-disk-prepare --fs-type xfs --zap-disk /dev/vdb Caution: invalid backup GPT header, but valid main header; regenerating backup header from main header. Warning! Main and backup partition tables differ! Use the 'c' and 'e' options on the recovery transformation menu to examine the two tables. Warning! One or more CRCs don't match. You should repair the disk! Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk verification and recovery are STRONGLY recommended. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. GPT data structures destroyed! You may now partition the disk using fdisk or other utilities. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. The operation has completed successfully. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. The operation has completed successfully. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. The operation has completed successfully. mkfs.xfs: cannot open /dev/vdb1: Device or resource busy ceph-disk: Error: Command '['/sbin/mkfs', '-t', 'xfs', '-f', '-i', 'size=2048', '--', '/dev/vdb1']' returned non-zero exit status 1 I can reproduce this consistently across ceph nodes; also impacts on the way we use swift for storage as well. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ceph 0.80.5-1 ProcVersionSignature: User Name 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 Date: Fri Sep 19 09:39:18 2014 Ec2AMI: ami-0084 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 SourcePackage: ceph UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1371526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371526] Re: ceph-disk-prepare command always fails; new partition table not avaliable until reboot
apport information ** Tags added: apport-collected ** Description changed: $ sudo ceph-disk-prepare --fs-type xfs --zap-disk /dev/vdb Caution: invalid backup GPT header, but valid main header; regenerating backup header from main header. Warning! Main and backup partition tables differ! Use the 'c' and 'e' options on the recovery transformation menu to examine the two tables. Warning! One or more CRCs don't match. You should repair the disk! Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk verification and recovery are STRONGLY recommended. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. GPT data structures destroyed! You may now partition the disk using fdisk or other utilities. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. The operation has completed successfully. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. The operation has completed successfully. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. The operation has completed successfully. mkfs.xfs: cannot open /dev/vdb1: Device or resource busy ceph-disk: Error: Command '['/sbin/mkfs', '-t', 'xfs', '-f', '-i', 'size=2048', '--', '/dev/vdb1']' returned non-zero exit status 1 I can reproduce this consistently across ceph nodes; also impacts on the way we use swift for storage as well. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ceph 0.80.5-1 ProcVersionSignature: User Name 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 Date: Fri Sep 19 09:39:18 2014 Ec2AMI: ami-0084 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 SourcePackage: ceph UpgradeStatus: No upgrade log present (probably fresh install) + --- + ApportVersion: 2.14.7-0ubuntu2 + Architecture: amd64 + DistroRelease: Ubuntu 14.10 + Ec2AMI: ami-0084 + Ec2AMIManifest: FIXME + Ec2AvailabilityZone: nova + Ec2InstanceType: m1.small + Ec2Kernel: aki-0002 + Ec2Ramdisk: ari-0002 + Package: linux + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 + Tags: utopic ec2-images + Uname: Linux 3.16.0-16-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1371526/+attachment/4208774/+files/Dependencies.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/1371526 Title: ceph-disk-prepare command always fails; new partition table not avaliable until reboot Status in “ceph” package in Ubuntu: New Status in “linux” package in Ubuntu: Incomplete Bug description: $ sudo ceph-disk-prepare --fs-type xfs --zap-disk /dev/vdb Caution: invalid backup GPT header, but valid main header; regenerating backup header from main header. Warning! Main and backup partition tables differ! Use the 'c' and 'e' options on the recovery transformation menu to examine the two tables. Warning! One or more CRCs don't match. You should repair the disk! Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk verification and recovery are STRONGLY recommended. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. GPT data structures destroyed! You may now partition the disk using fdisk or other utilities. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. The operation has completed successfully. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. The operation has completed successfully. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. The operation has completed successfully. mkfs.xfs: cannot open /dev/vdb1: Device or resource busy ceph-disk: Error: Command '['/sbin/mkfs', '-t', 'xfs', '-f', '-i', 'size=2048', '--', '/dev/vdb1']' returned non-zero exit status 1 I can reproduce this consistently across ceph nodes; also impacts on the way we use swift for storage as well. ProblemType: Bug DistroRelease: Ubuntu 14.10
[Kernel-packages] [Bug 1153618] Re: Support Realtek RTS5227 card reader
ref: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1365378 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1153618 Title: Support Realtek RTS5227 card reader Status in HWE Next Project: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Bug description: Support of Realtek RTS5227 card reader is currently missing in the kernel, though the support is already in upstream, we need to backport it from upstream to enable this device. 03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device [10ec:5227] (rev 01) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1153618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371526] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1371526/+attachment/4208775/+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/1371526 Title: ceph-disk-prepare command always fails; new partition table not avaliable until reboot Status in “ceph” package in Ubuntu: New Status in “linux” package in Ubuntu: Incomplete Bug description: $ sudo ceph-disk-prepare --fs-type xfs --zap-disk /dev/vdb Caution: invalid backup GPT header, but valid main header; regenerating backup header from main header. Warning! Main and backup partition tables differ! Use the 'c' and 'e' options on the recovery transformation menu to examine the two tables. Warning! One or more CRCs don't match. You should repair the disk! Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk verification and recovery are STRONGLY recommended. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. GPT data structures destroyed! You may now partition the disk using fdisk or other utilities. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. The operation has completed successfully. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. The operation has completed successfully. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. The operation has completed successfully. mkfs.xfs: cannot open /dev/vdb1: Device or resource busy ceph-disk: Error: Command '['/sbin/mkfs', '-t', 'xfs', '-f', '-i', 'size=2048', '--', '/dev/vdb1']' returned non-zero exit status 1 I can reproduce this consistently across ceph nodes; also impacts on the way we use swift for storage as well. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ceph 0.80.5-1 ProcVersionSignature: User Name 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 Date: Fri Sep 19 09:39:18 2014 Ec2AMI: ami-0084 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 SourcePackage: ceph UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 14.10 Ec2AMI: ami-0084 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Tags: utopic ec2-images Uname: Linux 3.16.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1371526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362199] Re: [FFe] apparmor abstract, anonymous and netlink socket mediation
** Tags removed: rtm14 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362199 Title: [FFe] apparmor abstract, anonymous and netlink socket mediation Status in “apparmor” package in Ubuntu: Fix Released Status in “apparmor-easyprof-ubuntu” package in Ubuntu: Fix Released Status in “isc-dhcp” package in Ubuntu: Fix Released Status in “libvirt” package in Ubuntu: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Status in “linux” package in Ubuntu: In Progress Status in “linux-flo” package in Ubuntu: In Progress Status in “linux-goldfish” package in Ubuntu: In Progress Status in “linux-mako” package in Ubuntu: In Progress Status in “linux-manta” package in Ubuntu: In Progress Status in “rsyslog” package in Ubuntu: Fix Released Status in “tlsdate” package in Ubuntu: Fix Released Bug description: Background: kernel and apparmor userspace updates to support abstract, anonymous and fine-grained netlink socket mediation. These packages are listed in one bug because they are related, but the FFes may be granted and the uploads may happen at different times. = apparmor userspace = Summary: This feature freeze exception is requested for abstract, anonymous and fine-grained netlink socket for apparmor userspace. When used with a compatible kernel, 'unix' and 'network netlink' rules are supported. When used without a compatible apparmor userspace (eg, on a trusty system with an utopic backport kernel), abstract, anonymous and fine-grained netlink socket mediation is not enforced (ie, you can use this userspace with an old kernel without any issues). Testing: * 14.10 system with current kernels lacking abstract, anonymous and fine-grained netlink socket mediation (non-Touch): * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: DONE (exploratory manual testing, lxc, libvirt, etc) * 14.10 system kernel capable of supporting abstract, anonymous and fine-grained netlink socket mediation (non-Touch): * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes test-apparmor.py, exploratory manual testing, lxc, libvirt, etc) * Verify everything in https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles: DONE (except juju since it doesn't have policy itself) Justification: This feature is required to support comprehensive application confinement on Ubuntu Touch. This feature adds a security benefit to libvirt's qemu guest isolation which is fundamental to Ubuntu on Server/Cloud. This feature also adds a welcome improvement to administrators wishing to further protect their systems. Extra information: While the apparmor userspace and kernel changes to support abstract, anonymous and fine-grained netlink socket can happen at different times, the apparmor userspace upload must correspond with uploads for packages that ship AppArmor policy that require updates (eg, libvirt, lightdm, etc). The packages outlined in https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles have been tested to either work without modification to the policy or updated and tested to work with updated policy. Common rules will be added to the apparmor base abstraction such that most packages shipping apparmor policy will not require updating. These updates will be prepared, tested and published en masse via a silo ppa. = linux = Summary: This feature freeze exception is requested for abstract, anonymous and fine-grained netlink socket via apparmor in the kernel. When used with a compatible apparmor userspace, 'unix' and 'network netlink' rules are supported. When used without a compatible apparmor userspace (eg, on a trusty system with an utopic backport kernel), abstract, anonymous and fine-grained netlink socket mediation is not enforced (ie, you can use this kernel with an old userspace without any issues). Testing: * 14.04 system with backported kernel: TODO * test-apparmor.py: TODO (runs extensive tests (upstream and distro)) * exploratory manual testing: TODO (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: TODO * lxc: TODO (containers can be created, started, shutdown) * libvirt: TODO (VMs started via openstack, and test-libvirt.py from QRT passes all tests) * 14.10 system (non-Touch) with updated kernel: * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes click-apparmor, apparmor-easyprof-ubuntu, exploratory manual testing, etc) * 14.10 system (Touch) with updated kernel: * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes click-apparmor, apparmor-easyprof-ubuntu, exploratory manual testing, etc) Justification: This feature is required to support comprehensive application confinement on Ubuntu Touch. This feature adds a
[Kernel-packages] [Bug 1355044] Re: [MSI A88XM-E35] Ubuntu 14.04.1 constant reboot without nomodeset
** Tags removed: needs-reverse-bisect ** Tags added: cherry-pick ** Tags added: reverse-bisect-done ** Changed in: linux (Ubuntu) Status: Confirmed = Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1355044 Title: [MSI A88XM-E35] Ubuntu 14.04.1 constant reboot without nomodeset Status in “linux” package in Ubuntu: Triaged Bug description: I needed to add nomodeset for initial install to prevent constant reboot from live usb. When done and trying to remove the nomodeset option out of /etc/default/grub, the constant reboot comes back, so I had to start in recovery to add nomodeset again. 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.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fab3896 F pulseaudio /dev/snd/controlC0: fab3896 F pulseaudio CurrentDesktop: Unity Date: Mon Aug 11 09:41:49 2014 HibernationDevice: RESUME=UUID=66392631-7c4f-4773-8614-4c5ea0913890 InstallationDate: Installed on 2014-07-26 (16 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) IwConfig: eth1 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7721 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=09ecdff0-44fe-437e-8063-deabc6feb00e ro recovery nomodeset 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 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V30.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-E35 (MS-7721) dmi.board.vendor: MSI dmi.board.version: 6.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 6.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV30.3:bd03/14/2014:svnMSI:pnMS-7721:pvr6.0:rvnMSI:rnA88XM-E35(MS-7721):rvr6.0:cvnMSI:ct3:cvr6.0: dmi.product.name: MS-7721 dmi.product.version: 6.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1355044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371477] Re: Atheros bluetooth module [0cf3:311e] doesn't work because it is not handled by ath3k
** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Status: New = Fix Committed ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) = Adam Lee (adam8157) ** Also affects: linux (Ubuntu Utopic) Importance: High Assignee: Adam Lee (adam8157) Status: In Progress ** Changed in: linux (Ubuntu Utopic) Status: In Progress = Fix Released ** Changed in: linux (Ubuntu Utopic) Assignee: Adam Lee (adam8157) = (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371477 Title: Atheros bluetooth module [0cf3:311e] doesn't work because it is not handled by ath3k Status in HWE Next Project: In Progress Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: SRU Justification: Impact: Atheros bluetooth module [0cf3:311e] doesn't work Fix: commit below from upstream, clean cherry-picks. Testcase: we already tested and delivered the fix by dkms in OEM projects, works well. commit af6acae581d502c3e42390497ab27496c3a81a0d Author: Oliver Neukum oli...@neukum.org Date: Thu Jan 16 15:37:11 2014 +0100 Bluetooth: Enable Atheros 0cf3:311e for firmware upload The device will bind to btusb without firmware, but with the original buggy firmware device discovery does not work. No devices are detected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1371477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1351282] Re: Sometimes USB does not work.
thanks for your suggestions @penalvch and @setaou running 3.17.0-031700rc5-lowlatency for a couple of days and I haven't noticed any usb failure at startup should we mark this bug as closed / fixed ?? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1351282 Title: Sometimes USB does not work. Status in “linux” package in Ubuntu: Incomplete Bug description: Sometimes after booting, USB does not work I can't use the keyboard or mouse to find out. Only solution is to kill the system by long-pressing the powerbutton. The second time I boot, the USB system works. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-lowlatency 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-lowlatency 3.13.11.4 Uname: Linux 3.13.0-32-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: rob1897 F pulseaudio /dev/snd/controlC2: rob1897 F pulseaudio /dev/snd/controlC1: rob1897 F pulseaudio CurrentDesktop: XFCE Date: Fri Aug 1 11:37:29 2014 HibernationDevice: RESUME=UUID=8260a407-c264-46d4-9dfd-e33424768f0a InstallationDate: Installed on 2014-07-04 (27 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) MachineType: Dell Inc. Inspiron 3847 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-lowlatency root=UUID=90a1d355-c5af-46e6-be55-6a153fd2a8fa ro quiet splash nomodeset video=uvesafb:mode_option=1440x900-24,mtrr=3,scroll=ywrap RelatedPackageVersions: linux-restricted-modules-3.13.0-32-lowlatency N/A linux-backports-modules-3.13.0-32-lowlatency N/A linux-firmware1.127.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/03/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 088DT1 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd04/03/2014:svnDellInc.:pnInspiron3847:pvr:rvnDellInc.:rn088DT1:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: Inspiron 3847 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1351282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371477] Re: Atheros bluetooth module [0cf3:311e] doesn't work because it is not handled by ath3k
** Changed in: hwe-next Assignee: (unassigned) = Adam Lee (adam8157) ** Changed in: hwe-next Status: In Progress = Fix Committed ** Changed in: linux (Ubuntu Trusty) 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/1371477 Title: Atheros bluetooth module [0cf3:311e] doesn't work because it is not handled by ath3k Status in HWE Next Project: Fix Committed Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: SRU Justification: Impact: Atheros bluetooth module [0cf3:311e] doesn't work Fix: commit below from upstream, clean cherry-picks. Testcase: we already tested and delivered the fix by dkms in OEM projects, works well. commit af6acae581d502c3e42390497ab27496c3a81a0d Author: Oliver Neukum oli...@neukum.org Date: Thu Jan 16 15:37:11 2014 +0100 Bluetooth: Enable Atheros 0cf3:311e for firmware upload The device will bind to btusb without firmware, but with the original buggy firmware device discovery does not work. No devices are detected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1371477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] [NEW] FS Corruption with Ubuntu and VMWare
Public bug reported: To be filled in... ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Canonical Kernel Team (canonical-kernel-team) 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/1371591 Title: FS Corruption with Ubuntu and VMWare Status in “linux” package in Ubuntu: New Bug description: To be filled in... 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 730820] Re: [Latitude E6510] ricoh e822: SD card is unable to mount
Should I report a new bug, or should this one be reopened? The problem
is definitely back 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/730820
Title:
[Latitude E6510] ricoh e822: SD card is unable to mount
Status in “linux” package in Ubuntu:
Fix Released
Status in “linux” source package in Maverick:
Fix Released
Status in “linux” source package in Natty:
Fix Released
Bug description:
Inserting an sd card does not cause the card to be mounted
automatically. Nothing is displayed to the use in regard to the sd
card. Card works perfectly on multiple other machines.
Card: Kingston 2GB micro SD card (model SDC/2GB)
dmesg snip:
[ 8536.437530] mmc0: ADMA error
[ 8536.439580] mmc0: Got data interrupt 0x0018 even though no data
operation was in progress.
[ 8536.440741] mmc0: error -5 whilst initialising SD card
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-22-generic 2.6.35-22.33
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: u 1498 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0x5696 irq 47'
Mixer name : 'Intel IbexPeak HDMI'
Components : 'HDA:111d76d5,1028040b,00100104
HDA:80862804,80860101,0010'
Controls : 22
Simple ctrls : 11
Date: Mon Mar 7 13:29:24 2011
HibernationDevice: RESUME=UUID=5fb4d9d1-02a8-4ad6-9e81-6971e122d37a
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
Lsusb:
Bus 002 Device 003: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications
Processor
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude E6510
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic
root=UUID=a72f2ab3-fea2-4b13-ba07-1a50f37d9dde ro quiet splash
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
RfKill:
SourcePackage: linux
dmi.bios.date: 11/20/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 02K3Y4
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA06:bd11/20/2010:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn02K3Y4:rvrA02:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6510
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/730820/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-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] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1371591 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/1371591 Title: FS Corruption with Ubuntu and VMWare Status in “linux” package in Ubuntu: Incomplete Bug description: To be filled in... 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 1371601] [NEW] Trusty update to v3.13.11.7 stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from Linus' tree or in a minimally
backported form of that patch. The v3.13.11.7 upstream stable
patch set is now available. It should be included in the Ubuntu
kernel as well.
git://git.kernel.org/
TEST CASE: TBD
The following patches are in the v3.13.11.7 stable release:
UBUNTU: [Config] CONFIG_X86_16BIT=y
bnx2x: fix crash during TSO tunneling
inetpeer: get rid of ip_id_count
ip: make IP identifiers less predictable
tcp: Fix integer-overflows in TCP veno
tcp: Fix integer-overflow in TCP vegas
macvlan: Initialize vlan_features to turn on offload support.
net: Correctly set segment mac_len in skb_segment().
iovec: make sure the caller actually wants anything in memcpy_fromiovecend
batman-adv: Fix out-of-order fragmentation support
sctp: fix possible seqlock seadlock in sctp_packet_transmit()
sparc64: Fix argument sign extension for compat_sys_futex().
sparc64: Make itc_sync_lock raw
sparc64: Fix executable bit testing in set_pmd_at() paths.
sparc64: Fix huge PMD invalidation.
sparc64: Fix bugs in get_user_pages_fast() wrt. THP.
sparc64: Fix hex values in comment above pte_modify().
sparc64: Don't use _PAGE_PRESENT in pte_modify() mask.
sparc64: Handle 32-bit tasks properly in compute_effective_address().
sparc64: Fix top-level fault handling bugs.
sparc64: Fix range check in kern_addr_valid().
sparc64: Use 'ILOG2_4MB' instead of constant '22'.
sparc64: Add basic validations to {pud,pmd}_bad().
sparc64: Give more detailed information in {pgd,pmd}_ERROR() and kill
pte_ERROR().
sparc64: Don't bark so loudly about 32-bit tasks generating 64-bit fault
addresses.
sparc64: Fix huge TSB mapping on pre-UltraSPARC-III cpus.
sparc64: Add membar to Niagara2 memcpy code.
sparc64: Do not insert non-valid PTEs into the TSB hash table.
sparc64: Guard against flushing openfirmware mappings.
bbc-i2c: Fix BBC I2C envctrl on SunBlade 2000
sunsab: Fix detection of BREAK on sunsab serial console
sparc64: ldc_connect() should not return EINVAL when handshake is in progress.
arch/sparc/math-emu/math_32.c: drop stray break operator
Revert x86-64, modify_ldt: Make support for 16-bit segments a runtime option
x86-64, espfix: Don't leak bits 31:16 of %esp returning to 16-bit stack
x86, espfix: Move espfix definitions into a separate header file
x86, espfix: Fix broken header guard
x86, espfix: Make espfix64 a Kconfig option, fix UML
x86, espfix: Make it possible to disable 16-bit support
x86_64/entry/xen: Do not invoke espfix64 on Xen
ALSA: usb-audio: fix BOSS ME-25 MIDI regression
ASoC: wm8994: Prevent double lock of accdet_lock mutex on wm1811
v4l: vsp1: Remove the unneeded vsp1_video_buffer video field
ASoC: max98090: Fix missing free_irq
KVM: x86: Inter-privilege level ret emulation is not implemeneted
au0828: Only alt setting logic when needed
ASoC: pcm: fix dpcm_path_put in dpcm runtime update
crypto: ux500 - make interrupt mode plausible
Bluetooth: btmrvl: wait for HOST_SLEEP_ENABLE event in suspend
ASoC: adau1701: fix adau1701_reg_read()
ASoC: wm_adsp: Add missing MODULE_LICENSE
regulator: arizona-ldo1: remove bypass functionality
ASoC: samsung: Correct I2S DAI suspend/resume ops
drm/tilcdc: panel: fix dangling sysfs connector node
drm/tilcdc: slave: fix dangling sysfs connector node
drm/tilcdc: tfp410: fix dangling sysfs connector node
drm/tilcdc: panel: fix leak when unloading the module
drm/tilcdc: fix release order on exit
drm/tilcdc: fix double kfree
ACPICA: Utilities: Fix memory leak in acpi_ut_copy_iobject_to_iobject
stable_kernel_rules: Add pointer to netdev-FAQ for network patches
USB: ehci-pci: USB host controller support for Intel Quark X1000
debugfs: Fix corrupted loop in debugfs_remove_recursive
serial: core: Preserve termios c_cflag for console resume
mtd/ftl: fix the double free of the buffers allocated in build_maps()
ext4: Fix block zeroing when punching holes in indirect block files
ext4: fix punch hole on files with indirect mapping
x86: don't exclude low BIOS area when allocating address space for non-PCI cards
PCI: Configure ASPM when enabling device
Bluetooth: never linger on process exit
ASoC: blackfin: use samples to set silence
USB: OHCI: fix bugs in debug routines
USB: OHCI: don't lose track of EDs when a controller dies
mei: start disconnect request timer consistently
mei: fix return value on disconnect timeout
USB: Fix persist resume of some SS USB devices
media-device: Remove duplicated memset() in media_enum_entities()
Bluetooth: Avoid use of session socket after the session gets freed
xc5000: Fix get_frequency()
xc4000: Fix get_frequency()
CAPABILITIES: remove undefined caps from all processes
scsi: add a blacklist flag which enables VPD page inquiries
bfa: Fix
[Kernel-packages] [Bug 1371591] Re: FS Corruption with Ubuntu and VMWare
** Changed in: linux (Ubuntu) Importance: Undecided = Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371591 Title: file not initialized to 0s under some conditions on VMWare Status in “linux” package in Ubuntu: Incomplete Bug description: 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. 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 _except_ 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. 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 1371591] Re: FS Corruption with Ubuntu and VMWare
** Description changed: - To be filled in... + 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. + + 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 _except_ 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. -- You 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 on VMWare Status in “linux” package in Ubuntu: Incomplete Bug description: 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. 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 _except_ 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. 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 1371591] Re: FS Corruption with Ubuntu and VMWare
** Changed in: linux (Ubuntu) Assignee: Canonical Kernel Team (canonical-kernel-team) = Chris J Arges (arges) -- You 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 on VMWare Status in “linux” package in Ubuntu: Incomplete Bug description: 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. 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 _except_ 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. 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 1322406] Re: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly
*** This bug is a duplicate of bug 1322407 *** https://bugs.launchpad.net/bugs/1322407 we are having the same issue ubuntu 14.04 Linux version 3.13.0-24-generic here is the debug from the kworker thread kworker/3:2-17063 [003] d... 1961298.739136: workqueue_queue_work: work struct=880231a805e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800ba555e00 req_cpu=256 cpu=3 kworker/3:2-17063 [003] d.s. 1961298.739140: workqueue_queue_work: work struct=880020fdc888 function=rpc_async_schedule [sunrpc] workqueue=8800ba555e00 req_cpu=256 cpu=3 kworker/3:2-17063 [003] d... 1961298.739141: workqueue_queue_work: work struct=880231a805e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800ba555e00 req_cpu=256 cpu=3 kworker/3:2-17063 [003] d.s. 1961298.739146: workqueue_queue_work: work struct=880020fdc888 function=rpc_async_schedule [sunrpc] workqueue=8800ba555e00 req_cpu=256 cpu=3 kworker/3:2-17063 [003] d... 1961298.739146: workqueue_queue_work: work struct=880231a805e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800ba555e00 req_cpu=256 cpu=3 kworker/3:2-17063 [003] d.s. 1961298.739151: workqueue_queue_work: work struct=880020fdc888 function=rpc_async_schedule [sunrpc] workqueue=8800ba555e00 req_cpu=256 cpu=3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1322406 Title: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly Status in “linux” package in Ubuntu: Confirmed Bug description: This concerns the server edition of 14.04. I have set up a NFS server. Once I attach at least one client, one kworker process starts to use 100% CPU. The runaway kworker returns to idle when I reset the NFS server daemon with service nfs-kernel-server stop followed by service nfs-kernel-server start. With the nfs kernel server stopped, the CPU remains idle. With the nfs kernel server running, as soon as one client requests a connection, the kworker process jumps to 100% CPU again. After some random time, the nfs kernel server no longer accepts requests from clients. Restarting the service allows clients to reconnect. The syslog shows no relevant information. Configration: The svcgssd is not running. I played with various configurations (enabling/disabling NFSv3 and NFSv4), but it makes no difference. I tried to nable event debugging: # echo workqueue:workqueue_queue_work /sys/kernel/debug/tracing/set_event # cat /sys/kernel/debug/tracing/trace_pipe /var/tmp/kerntrace.txt and found the following kernel trace in a tight loop: [...] kworker/2:1-86[002] d... 161940.910668: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910674: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910675: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910681: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910682: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910688: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910689: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910695: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910696: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910702: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 [...] At present, I have to consider NFS fubar. Thanks, Mark ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-24-generic. AplayDevices: Error: [Errno 2] No
[Kernel-packages] [Bug 1365052] Re: linux: 3.13.0-36.63 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: In Progress = Fix Released ** Changed in: kernel-sru-workflow/package-testing Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1365052 Title: linux: 3.13.0-36.63 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow package-testing series: Fix Released 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: Fix Released 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-36.63 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:Wednesday, 03. September 2014 16:10 UTC kernel-stable-Prepare-package-end:Thursday, 04. September 2014 05:07 UTC kernel-stable-Promote-to-proposed-start:Thursday, 04. September 2014 05:07 UTC ppa-package-testing-start:Thursday, 04. September 2014 05:07 UTC kernel-stable-Promote-to-proposed-end:Thursday, 04. September 2014 19:44 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Thursday, 04. September 2014 21:06 UTC kernel-stable-Verification-testing-start:Thursday, 04. September 2014 21:06 UTC kernel-stable-Certification-testing-start:Thursday, 04. September 2014 21:06 UTC kernel-stable-Security-signoff-start:Thursday, 04. September 2014 21:06 UTC kernel-stable-Regression-testing-start:Thursday, 04. September 2014 21:06 UTC kernel-stable-Regression-testing-end:Wednesday, 10. September 2014 09:01 UTC kernel-stable-Certification-testing-end:Thursday, 11. September 2014 08:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1365052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 on VMWare
** Summary changed: - FS Corruption with Ubuntu and VMWare + file not initialized to 0s under some conditions on VMWare ** Attachment added: reproducer https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371591/+attachment/4208902/+files/repro.tgz -- You 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 on VMWare Status in “linux” package in Ubuntu: Incomplete Bug description: 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. 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 _except_ 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. 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 1371379] Re: rtsx_usb module for Realtek Semiconductor Corp. RTS5139 Card Reader Controller doesn't load
commit 35dca0e6c20e797175ce8c5f47b03630bb397af3 (drivers/mfd/rtsx_usb.c: export device table) in v3.16.3. Destined for release in 3.16.0-17.23 ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Utopic) Status: New = Fix Committed -- You 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: New Status in “linux” package in Fedora: Unknown 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 1358855] Re: tools/testing/selftests/ptrace fails on ppc64
I guess we can assume this patch didn't break anything in Trusty 'cause nobody is complaining. Marking verification-done-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/1358855 Title: tools/testing/selftests/ptrace fails on ppc64 Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: Compilation of linux/tools/testing/selftests/ptrace/peeksiginfo.c fails becasue the variable PAGE_SIZE is not defined. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358855/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371614] [NEW] linux: 3.16.0-17.23 -proposed tracker
Public bug reported: This bug is for tracking the 3.16.0-17.23 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Friday, 19. September 2014 13:59 UTC kernel-phase-changed:Friday, 19. September 2014 13:59 UTC kernel-phase:Prepare ** Affects: kernel-development-workflow Importance: Medium Status: In Progress ** Affects: kernel-development-workflow/package-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux (Ubuntu Utopic) Importance: Medium Status: New ** Tags: kernel-release-tracking-bug utopic ** Tags added: kernel-release-tracking-bug ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Tags added: utopic ** Also affects: kernel-development-workflow/package-testing Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-development-workflow/promote-to-release Importance: Undecided Status: New ** Changed in: kernel-development-workflow Status: New = In Progress ** Changed in: kernel-development-workflow Importance: Undecided = Medium ** Changed in: kernel-development-workflow/package-testing Importance: Undecided = Medium ** Changed in: kernel-development-workflow/package-testing Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package Importance: Undecided = Medium ** Changed in: kernel-development-workflow/prepare-package Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-meta Importance: Undecided = Medium ** Changed in: kernel-development-workflow/prepare-package-meta Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-signed Importance: Undecided = Medium ** Changed in: kernel-development-workflow/prepare-package-signed Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/promote-to-release Importance: Undecided = Medium ** Changed in: kernel-development-workflow/promote-to-release Assignee: (unassigned) = Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: linux (Ubuntu Utopic) Importance: Undecided = Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371614 Title: linux: 3.16.0-17.23 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow package-testing series: New Status in Kernel Development Workflow prepare-package series: New Status in Kernel Development Workflow prepare-package-meta series: New Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-release series: New Status in “linux” package in Ubuntu: New Status in “linux” source package in Utopic: New Bug description: This bug is for tracking the 3.16.0-17.23 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Friday, 19. September 2014 13:59 UTC kernel-phase-changed:Friday, 19. September 2014 13:59 UTC kernel-phase:Prepare To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1371614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [Bug 1365052] Re: linux: 3.13.0-36.63 -proposed tracker
** Description changed: This bug is for tracking the 3.13.0-36.63 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:Wednesday, 03. September 2014 16:10 UTC kernel-stable-Prepare-package-end:Thursday, 04. September 2014 05:07 UTC kernel-stable-Promote-to-proposed-start:Thursday, 04. September 2014 05:07 UTC ppa-package-testing-start:Thursday, 04. September 2014 05:07 UTC kernel-stable-Promote-to-proposed-end:Thursday, 04. September 2014 19:44 UTC - kernel-stable-phase:Verification Testing - kernel-stable-phase-changed:Thursday, 04. September 2014 21:06 UTC kernel-stable-Verification-testing-start:Thursday, 04. September 2014 21:06 UTC kernel-stable-Certification-testing-start:Thursday, 04. September 2014 21:06 UTC kernel-stable-Security-signoff-start:Thursday, 04. September 2014 21:06 UTC kernel-stable-Regression-testing-start:Thursday, 04. September 2014 21:06 UTC kernel-stable-Regression-testing-end:Wednesday, 10. September 2014 09:01 UTC kernel-stable-Certification-testing-end:Thursday, 11. September 2014 08:02 UTC + kernel-stable-phase:Testing + kernel-stable-phase-changed:Friday, 19. September 2014 14:02 UTC + kernel-stable-Verification-testing-end:Friday, 19. September 2014 14:02 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/1365052 Title: linux: 3.13.0-36.63 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow package-testing series: Fix Released 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: Fix Released 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-36.63 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:Wednesday, 03. September 2014 16:10 UTC kernel-stable-Prepare-package-end:Thursday, 04. September 2014 05:07 UTC kernel-stable-Promote-to-proposed-start:Thursday, 04. September 2014 05:07 UTC ppa-package-testing-start:Thursday, 04. September 2014 05:07 UTC kernel-stable-Promote-to-proposed-end:Thursday, 04. September 2014 19:44 UTC kernel-stable-Verification-testing-start:Thursday, 04. September 2014 21:06 UTC kernel-stable-Certification-testing-start:Thursday, 04. September 2014 21:06 UTC kernel-stable-Security-signoff-start:Thursday, 04. September 2014 21:06 UTC kernel-stable-Regression-testing-start:Thursday, 04. September 2014 21:06 UTC kernel-stable-Regression-testing-end:Wednesday, 10. September 2014 09:01 UTC kernel-stable-Certification-testing-end:Thursday, 11. September 2014 08:02 UTC kernel-stable-phase:Testing kernel-stable-phase-changed:Friday, 19. September 2014 14:02 UTC kernel-stable-Verification-testing-end:Friday, 19. September 2014 14:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1365052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 on VMWare
So are you sure 20GB is enough disk space for the VM? I tried in a KVM VM (just to try the reproducer) and I get 'No space left on device' errors from fallocate. In addition can you post the machine information someone in this bug so I can reproduce the exact setup on my end with vmware. Also to be clear, LVM _is_ required to reproduce the issue. Thanks for the overall great bug description and reproducer script! --chris -- You 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 on VMWare Status in “linux” package in Ubuntu: Incomplete Bug description: 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. 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 _except_ 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. 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 1371623] 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/1371623 Title: Keyboard giv entry like En, but shows Cs and is unable to set Cs funstionality at startup. Status in “linux” package in Ubuntu: Confirmed Bug description: If I launch Ubuntu and make a entry from keyboard it gets chars like on English keymap. I have to turn keyboard by switch in right-top corner to En and again to Cs. After I can write in my national keyboard keyset ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-16-generic 3.16.0-16.22 [modified: boot/vmlinuz-3.16.0-16-generic] 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: jirka 2342 F pulseaudio CurrentDesktop: Unity Date: Fri Sep 19 16:18:39 2014 HibernationDevice: RESUME=UUID=bc5d379d-1433-47e9-9937-08cb7b735e7f InstallationDate: Installed on 2014-09-19 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140919) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 003: ID 8564:1000 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-7100 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-16-generic root=UUID=29b268e8-771e-48d1-81b5-5c38dc1c789d ro persistent quiet splash 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 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2005 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-7100 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/17/2005:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7100:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7100:rvr1.0:cvn:ct3:cvr: dmi.product.name: MS-7100 dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371623] [NEW] Keyboard giv entry like En, but shows Cs and is unable to set Cs funstionality at startup.
Public bug reported: If I launch Ubuntu and make a entry from keyboard it gets chars like on English keymap. I have to turn keyboard by switch in right-top corner to En and again to Cs. After I can write in my national keyboard keyset ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-16-generic 3.16.0-16.22 [modified: boot/vmlinuz-3.16.0-16-generic] 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: jirka 2342 F pulseaudio CurrentDesktop: Unity Date: Fri Sep 19 16:18:39 2014 HibernationDevice: RESUME=UUID=bc5d379d-1433-47e9-9937-08cb7b735e7f InstallationDate: Installed on 2014-09-19 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140919) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 003: ID 8564:1000 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-7100 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-16-generic root=UUID=29b268e8-771e-48d1-81b5-5c38dc1c789d ro persistent quiet splash 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 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2005 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-7100 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/17/2005:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7100:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7100:rvr1.0:cvn:ct3:cvr: dmi.product.name: MS-7100 dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371623 Title: Keyboard giv entry like En, but shows Cs and is unable to set Cs funstionality at startup. Status in “linux” package in Ubuntu: Confirmed Bug description: If I launch Ubuntu and make a entry from keyboard it gets chars like on English keymap. I have to turn keyboard by switch in right-top corner to En and again to Cs. After I can write in my national keyboard keyset ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-16-generic 3.16.0-16.22 [modified: boot/vmlinuz-3.16.0-16-generic] 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: jirka 2342 F pulseaudio CurrentDesktop: Unity Date: Fri Sep 19 16:18:39 2014 HibernationDevice: RESUME=UUID=bc5d379d-1433-47e9-9937-08cb7b735e7f InstallationDate: Installed on 2014-09-19 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140919) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 003: ID 8564:1000 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-7100 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-16-generic root=UUID=29b268e8-771e-48d1-81b5-5c38dc1c789d ro persistent quiet splash 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 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2005 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-7100 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/17/2005:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7100:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7100:rvr1.0:cvn:ct3:cvr: dmi.product.name: MS-7100 dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD To manage notifications about this bug go to: https://bugs.launchpad.net
[Kernel-packages] [Bug 1371634] [NEW] block devices appear twice
Public bug reported: $ sudo blkid /dev/sr0: LABEL=Ubuntu-Server 14.04 LTS ppc64el TYPE=iso9660 /dev/sda2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sda3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdb2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdb3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap /dev/sdg2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sdg3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdh2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdh3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap I'm not sure what exactly those block devices are (as in if they're raided in hardware or they actually represent physical spinning disks). But I do know that writing data to sda causes that data to be readable from sdg. The same is true: sda - sdg sdb - sdh That is what causes those UUIDs to be similar. Everything is functional, you just have to know that if your root device is /dev/sdg that you should probably not write data to /dev/sda thinking you can use it as a disk. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic ppc64le AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [ 88.736220] init: plymouth-upstart-bridge main process ended, respawning Date: Fri Sep 19 14:31:20 2014 HibernationDevice: RESUME=UUID=9c228177-d65c-4d19-a462-db1891e9781e Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 ro console=hvc0 BOOTIF=01-6c-ae-8b-6a-a0-88 quiet RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug ppc64el trusty uec-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice Status in “linux” package in Ubuntu: New Bug description: $ sudo blkid /dev/sr0: LABEL=Ubuntu-Server 14.04 LTS ppc64el TYPE=iso9660 /dev/sda2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sda3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdb2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdb3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap /dev/sdg2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sdg3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdh2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdh3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap I'm not sure what exactly those block devices are (as in if they're raided in hardware or they actually represent physical spinning disks). But I do know that writing data to sda causes that data to be readable from sdg. The same is true: sda - sdg sdb - sdh That is what causes those UUIDs to be similar. Everything is functional, you just have to know that if your root device is /dev/sdg that you should probably not write data to /dev/sda thinking you can use it as a disk. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic ppc64le AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [ 88.736220] init: plymouth-upstart-bridge main process ended, respawning Date: Fri Sep 19 14:31:20 2014 HibernationDevice: RESUME=UUID=9c228177-d65c-4d19-a462-db1891e9781e Lsusb:
[Kernel-packages] [Bug 1369964] Re: Cannot disconnect BQ Vivaldi Bluetooth speaker using Bluetooth settings
** Attachment added: Log file from trying to disconnect the bluetooth speaker https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1369964/+attachment/4208945/+files/application-legacy-ubuntu-system-settings-.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1369964 Title: Cannot disconnect BQ Vivaldi Bluetooth speaker using Bluetooth settings Status in “bluez” package in Ubuntu: Incomplete Bug description: ENVIRONMENT: krillin ubuntu-rtm/14.09-proposed build 44. BQ Avrha Altavoz Vivaldi Bluetooth speaker: http://www.bqreaders.com/gb/accessories-aquaris.html SUMMARY: Cannot disconnect BQ Vivaldi Bluetooth speaker using Bluetooth settings STEPS: 1) Turn on speaker so that it is in pairing mode 2) On Ubuntu device pair with the speaker 3) Play music through the speaker 4) From Bluetooth settings, select the speaker device and press Disconnect button EXPECTED RESULT: The device should disconnect. ACTUAL RESULT: The disconnect button has no effect. Music continues to play through the Bluetooth speaker. For other Bluetooth devices the Disconnect button works. This bug is specific to this particular device. ADDITIONAL INFO: hcitool inq: 12:1F:83:05:03:B4 clock offset: 0x264c class: 0x240414 hcitool info: BD Address: 12:1F:83:05:03:B4 Device Name: Avrha Vivaldi LMP Version: 2.0 (0x3) LMP Subversion: 0x2 Manufacturer: Accel Semiconductor Ltd. (74) Features page 0: 0xff 0x3e 0x0d 0x76 0x80 0x01 0x00 0x80 3-slot packets 5-slot packets encryption slot offset timing accuracy role switch hold mode sniff mode RSSI channel quality SCO link HV2 packets HV3 packets CVSD power control transparent SCO EDR ACL 2 Mbps EDR ACL 3 Mbps interlaced iscan interlaced pscan inquiry with RSSI 3-slot EDR ACL 5-slot EDR ACL extended features Features page 1: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1369964/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1369964] Re: Cannot disconnect BQ Vivaldi Bluetooth speaker using Bluetooth settings
I also noticed that when pairing this device for the first time, the name is not visible in the list and the properties screen is malformed. See attachments of screen shots for details: 1_pairing_no_name.png - No name is displayed (even after waiting) 2_device_details.png - The screen is not formed correctly, but the Connect button still works 3_paired.png - Here the correct name is displayed and the device still works as expected. For all further pairing attempts with this device the correct name is displayed and the connect screen is correctly formed. It is only for the first attempt that this happens. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1369964 Title: Cannot disconnect BQ Vivaldi Bluetooth speaker using Bluetooth settings Status in “bluez” package in Ubuntu: New Bug description: ENVIRONMENT: krillin ubuntu-rtm/14.09-proposed build 44. BQ Avrha Altavoz Vivaldi Bluetooth speaker: http://www.bqreaders.com/gb/accessories-aquaris.html SUMMARY: Cannot disconnect BQ Vivaldi Bluetooth speaker using Bluetooth settings STEPS: 1) Turn on speaker so that it is in pairing mode 2) On Ubuntu device pair with the speaker 3) Play music through the speaker 4) From Bluetooth settings, select the speaker device and press Disconnect button EXPECTED RESULT: The device should disconnect. ACTUAL RESULT: The disconnect button has no effect. Music continues to play through the Bluetooth speaker. For other Bluetooth devices the Disconnect button works. This bug is specific to this particular device. ADDITIONAL INFO: hcitool inq: 12:1F:83:05:03:B4 clock offset: 0x264c class: 0x240414 hcitool info: BD Address: 12:1F:83:05:03:B4 Device Name: Avrha Vivaldi LMP Version: 2.0 (0x3) LMP Subversion: 0x2 Manufacturer: Accel Semiconductor Ltd. (74) Features page 0: 0xff 0x3e 0x0d 0x76 0x80 0x01 0x00 0x80 3-slot packets 5-slot packets encryption slot offset timing accuracy role switch hold mode sniff mode RSSI channel quality SCO link HV2 packets HV3 packets CVSD power control transparent SCO EDR ACL 2 Mbps EDR ACL 3 Mbps interlaced iscan interlaced pscan inquiry with RSSI 3-slot EDR ACL 5-slot EDR ACL extended features Features page 1: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1369964/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1358746] Re: [kernel-fixed-upstream][Gigabyte Technology Co., Ltd. GA-A75-D3H] suspend/resume failure
** Summary changed: - [Gigabyte Technology Co., Ltd. GA-A75-D3H] suspend/resume failure + [kernel-fixed-upstream][Gigabyte Technology Co., Ltd. GA-A75-D3H] suspend/resume failure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1358746 Title: [kernel-fixed-upstream][Gigabyte Technology Co., Ltd. GA-A75-D3H] suspend/resume failure Status in “linux” package in Ubuntu: Incomplete Bug description: i got the erros message after startup ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-7-generic 3.16.0-7.12 ProcVersionSignature: Ubuntu 3.16.0-7.12-generic 3.16.0 Uname: Linux 3.16.0-7-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.5-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: balazs 1777 F pulseaudio Date: Sun Aug 17 13:27:32 2014 DuplicateSignature: suspend/resume:Gigabyte Technology Co., Ltd. GA-A75-D3H:F5b ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InterpreterPath: /usr/bin/python3.4 IwConfig: eth2 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-A75-D3H ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-7-generic root=UUID=742fd1ac-83a8-42ca-a907-11a16d73bc0e ro nosplash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-7-generic N/A linux-backports-modules-3.16.0-7-generic N/A linux-firmware1.132 RfKill: SourcePackage: linux Title: [Gigabyte Technology Co., Ltd. GA-A75-D3H] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/15/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5b dmi.board.name: GA-A75-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5b:bd03/15/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75-D3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75-D3H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-A75-D3H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358746/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1369964] Re: Cannot disconnect BQ Vivaldi Bluetooth speaker using Bluetooth settings
** Attachment added: 2_device_details.png https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1369964/+attachment/4208969/+files/2_device_details.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1369964 Title: Cannot disconnect BQ Vivaldi Bluetooth speaker using Bluetooth settings Status in “bluez” package in Ubuntu: New Bug description: ENVIRONMENT: krillin ubuntu-rtm/14.09-proposed build 44. BQ Avrha Altavoz Vivaldi Bluetooth speaker: http://www.bqreaders.com/gb/accessories-aquaris.html SUMMARY: Cannot disconnect BQ Vivaldi Bluetooth speaker using Bluetooth settings STEPS: 1) Turn on speaker so that it is in pairing mode 2) On Ubuntu device pair with the speaker 3) Play music through the speaker 4) From Bluetooth settings, select the speaker device and press Disconnect button EXPECTED RESULT: The device should disconnect. ACTUAL RESULT: The disconnect button has no effect. Music continues to play through the Bluetooth speaker. For other Bluetooth devices the Disconnect button works. This bug is specific to this particular device. ADDITIONAL INFO: hcitool inq: 12:1F:83:05:03:B4 clock offset: 0x264c class: 0x240414 hcitool info: BD Address: 12:1F:83:05:03:B4 Device Name: Avrha Vivaldi LMP Version: 2.0 (0x3) LMP Subversion: 0x2 Manufacturer: Accel Semiconductor Ltd. (74) Features page 0: 0xff 0x3e 0x0d 0x76 0x80 0x01 0x00 0x80 3-slot packets 5-slot packets encryption slot offset timing accuracy role switch hold mode sniff mode RSSI channel quality SCO link HV2 packets HV3 packets CVSD power control transparent SCO EDR ACL 2 Mbps EDR ACL 3 Mbps interlaced iscan interlaced pscan inquiry with RSSI 3-slot EDR ACL 5-slot EDR ACL extended features Features page 1: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1369964/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1369964] Re: Cannot disconnect BQ Vivaldi Bluetooth speaker using Bluetooth settings
** Attachment added: 1_pairing_no_name.png https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1369964/+attachment/4208968/+files/1_pairing_no_name.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1369964 Title: Cannot disconnect BQ Vivaldi Bluetooth speaker using Bluetooth settings Status in “bluez” package in Ubuntu: New Bug description: ENVIRONMENT: krillin ubuntu-rtm/14.09-proposed build 44. BQ Avrha Altavoz Vivaldi Bluetooth speaker: http://www.bqreaders.com/gb/accessories-aquaris.html SUMMARY: Cannot disconnect BQ Vivaldi Bluetooth speaker using Bluetooth settings STEPS: 1) Turn on speaker so that it is in pairing mode 2) On Ubuntu device pair with the speaker 3) Play music through the speaker 4) From Bluetooth settings, select the speaker device and press Disconnect button EXPECTED RESULT: The device should disconnect. ACTUAL RESULT: The disconnect button has no effect. Music continues to play through the Bluetooth speaker. For other Bluetooth devices the Disconnect button works. This bug is specific to this particular device. ADDITIONAL INFO: hcitool inq: 12:1F:83:05:03:B4 clock offset: 0x264c class: 0x240414 hcitool info: BD Address: 12:1F:83:05:03:B4 Device Name: Avrha Vivaldi LMP Version: 2.0 (0x3) LMP Subversion: 0x2 Manufacturer: Accel Semiconductor Ltd. (74) Features page 0: 0xff 0x3e 0x0d 0x76 0x80 0x01 0x00 0x80 3-slot packets 5-slot packets encryption slot offset timing accuracy role switch hold mode sniff mode RSSI channel quality SCO link HV2 packets HV3 packets CVSD power control transparent SCO EDR ACL 2 Mbps EDR ACL 3 Mbps interlaced iscan interlaced pscan inquiry with RSSI 3-slot EDR ACL 5-slot EDR ACL extended features Features page 1: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1369964/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1369964] Re: Cannot disconnect BQ Vivaldi Bluetooth speaker using Bluetooth settings
** Attachment added: 3_paired.png https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1369964/+attachment/4208970/+files/3_paired.png ** Changed in: bluez (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1369964 Title: Cannot disconnect BQ Vivaldi Bluetooth speaker using Bluetooth settings Status in “bluez” package in Ubuntu: New Bug description: ENVIRONMENT: krillin ubuntu-rtm/14.09-proposed build 44. BQ Avrha Altavoz Vivaldi Bluetooth speaker: http://www.bqreaders.com/gb/accessories-aquaris.html SUMMARY: Cannot disconnect BQ Vivaldi Bluetooth speaker using Bluetooth settings STEPS: 1) Turn on speaker so that it is in pairing mode 2) On Ubuntu device pair with the speaker 3) Play music through the speaker 4) From Bluetooth settings, select the speaker device and press Disconnect button EXPECTED RESULT: The device should disconnect. ACTUAL RESULT: The disconnect button has no effect. Music continues to play through the Bluetooth speaker. For other Bluetooth devices the Disconnect button works. This bug is specific to this particular device. ADDITIONAL INFO: hcitool inq: 12:1F:83:05:03:B4 clock offset: 0x264c class: 0x240414 hcitool info: BD Address: 12:1F:83:05:03:B4 Device Name: Avrha Vivaldi LMP Version: 2.0 (0x3) LMP Subversion: 0x2 Manufacturer: Accel Semiconductor Ltd. (74) Features page 0: 0xff 0x3e 0x0d 0x76 0x80 0x01 0x00 0x80 3-slot packets 5-slot packets encryption slot offset timing accuracy role switch hold mode sniff mode RSSI channel quality SCO link HV2 packets HV3 packets CVSD power control transparent SCO EDR ACL 2 Mbps EDR ACL 3 Mbps interlaced iscan interlaced pscan inquiry with RSSI 3-slot EDR ACL 5-slot EDR ACL extended features Features page 1: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1369964/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 on VMWare
** Attachment added: sample repro script output https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371591/+attachment/4208971/+files/repro.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/1371591 Title: file not initialized to 0s under some conditions on VMWare Status in “linux” package in Ubuntu: Incomplete Bug description: 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. 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. 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 1320022] Re: [Dell Latitude E6540] ALPS touchpad keeps having state reset
Crap thought I replied to this before. It still is happening with 3.15.0-031500rc5-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1320022 Title: [Dell Latitude E6540] ALPS touchpad keeps having state reset Status in “linux” package in Ubuntu: Incomplete Bug description: While using the 'eraser' pointer on my Dell Latitude E6540, the cursor will sometimes instantly jump around randomly and open a few windows. After this happens, it will become completely unresponsive for 10-20 seconds. Sometimes the keyboard will stop responding also. It seems like it is most likely to happen when I bump the trackpad with my palm when using the eraser pointer in the middle of the keyboard. Also - I have always had the trackpad disabled when this happens via the Dell hotkey (Fn-F5). Of course, it has never happened when the laptop is docked and I am using an external keyboard/mouse. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jgibson4335 F pulseaudio /dev/snd/controlC1: jgibson4335 F pulseaudio CurrentDesktop: Unity Date: Thu May 15 17:45:24 2014 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=b89369d3-0c28-4203-b73e-5085341e1fe7 InstallationDate: Installed on 2014-03-12 (64 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140307) MachineType: Dell Inc. Latitude E6540 ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0725FP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE6540:pvr01:rvnDellInc.:rn0725FP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6540 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1320022/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 on VMWare
20 GB should be more than enough. It should run the repro binary several times, using more disk space each time since it leaves the each run in place when it goes on to the next, and then get a failure from fallocate on the last one when the disk is filled up. I've attached a file showing a successful repro run on a 20 GB disk. Could the no space errors you are seeing be a ulimit issue? Yes, LVM is required to reproduce the issue; sorry about the error in the repro steps; fixed now. Can you clarify what machine information you're looking for? ** Description changed: 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. 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 _except_ LVM + 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. -- You 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 on VMWare Status in “linux” package in Ubuntu: Incomplete Bug description: 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. 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
[Kernel-packages] [Bug 1371634] 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/1371634 Title: block devices appear twice Status in “linux” package in Ubuntu: Confirmed Bug description: $ sudo blkid /dev/sr0: LABEL=Ubuntu-Server 14.04 LTS ppc64el TYPE=iso9660 /dev/sda2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sda3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdb2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdb3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap /dev/sdg2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sdg3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdh2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdh3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap I'm not sure what exactly those block devices are (as in if they're raided in hardware or they actually represent physical spinning disks). But I do know that writing data to sda causes that data to be readable from sdg. The same is true: sda - sdg sdb - sdh That is what causes those UUIDs to be similar. Everything is functional, you just have to know that if your root device is /dev/sdg that you should probably not write data to /dev/sda thinking you can use it as a disk. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic ppc64le AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [ 88.736220] init: plymouth-upstart-bridge main process ended, respawning Date: Fri Sep 19 14:31:20 2014 HibernationDevice: RESUME=UUID=9c228177-d65c-4d19-a462-db1891e9781e Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 ro console=hvc0 BOOTIF=01-6c-ae-8b-6a-a0-88 quiet RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371634/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 on VMWare
When creating the VM, did you use the default settings, or was the hardware configuration changed at all? I.e. did you add extra processors, or just use 1? I'll look into my errors a bit more, getting VMWare Workstation setup; has this been only reproduced in VMWare Fusion? Also are there specific versions of VMWare * you have used to repo the issue? Also what kernel version can repo this issue? (uname -a)? -- You 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 on VMWare Status in “linux” package in Ubuntu: In Progress Bug description: 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. 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. 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 1371591] Re: file not initialized to 0s under some conditions on VMWare
** Changed in: linux (Ubuntu) Status: Incomplete = In Progress -- You 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 on VMWare Status in “linux” package in Ubuntu: In Progress Bug description: 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. 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. 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 1371623] Re: Keyboard giv entry like En, but shows Cs and is unable to set Cs funstionality at startup.
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1371623 ** Tags added: iso-testing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371623 Title: Keyboard giv entry like En, but shows Cs and is unable to set Cs funstionality at startup. Status in “linux” package in Ubuntu: Confirmed Bug description: If I launch Ubuntu and make a entry from keyboard it gets chars like on English keymap. I have to turn keyboard by switch in right-top corner to En and again to Cs. After I can write in my national keyboard keyset ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-16-generic 3.16.0-16.22 [modified: boot/vmlinuz-3.16.0-16-generic] 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: jirka 2342 F pulseaudio CurrentDesktop: Unity Date: Fri Sep 19 16:18:39 2014 HibernationDevice: RESUME=UUID=bc5d379d-1433-47e9-9937-08cb7b735e7f InstallationDate: Installed on 2014-09-19 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140919) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 003: ID 8564:1000 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-7100 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-16-generic root=UUID=29b268e8-771e-48d1-81b5-5c38dc1c789d ro persistent quiet splash 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 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2005 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-7100 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/17/2005:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7100:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7100:rvr1.0:cvn:ct3:cvr: dmi.product.name: MS-7100 dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371654] [NEW] Error! Bad return status for module build on kernel bcmwl bdcom in bcmwl-kernel-source package
Public bug reported: Hi, Error within recompiling kernel module: DKMS make.log for bcmwl-6.30.223.248+bdcom for kernel 3.17.0-031700rc5-generic (x86_64) Fri Sep 19 17:07:55 CEST 2014 make: Entering directory '/usr/src/linux-headers-3.17.0-031700rc5-generic' CFG80211 API is prefered for this kernel version Using CFG80211 API LD /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/built-in.o CC [M] /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/shared/linux_osl.o CC [M] /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.o /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_alloc_linux_if’: /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.c:1316:64: error: macro alloc_netdev requires 4 arguments, but only 3 given dev = alloc_netdev(sizeof(priv_link_t), intf_name, ether_setup); ^ /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.c:1316:8: error: ‘alloc_netdev’ undeclared (first use in this function) dev = alloc_netdev(sizeof(priv_link_t), intf_name, ether_setup); ^ /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.c:1316:8: note: each undeclared identifier is reported only once for each function it appears in scripts/Makefile.build:257: recipe for target '/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.o' failed make[1]: *** [/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.o] Error 1 Makefile:1373: recipe for target '_module_/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build' failed make: *** [_module_/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build] Error 2 make: Leaving directory '/usr/src/linux-headers-3.17.0-031700rc5-generic' apt-cache policy bcmwl-kernel-source: bcmwl-kernel-source: Installed: 6.30.223.248+bdcom-0ubuntu1 Candidate: 6.30.223.248+bdcom-0ubuntu1 Version table: *** 6.30.223.248+bdcom-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ utopic/restricted amd64 Packages 100 /var/lib/dpkg/status lsb_release -rd Description:Ubuntu Utopic Unicorn (development branch) Release:14.10 Thank You, Kind Reagrds, Martin ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1371654 Title: Error! Bad return status for module build on kernel bcmwl bdcom in bcmwl-kernel-source package Status in “bcmwl” package in Ubuntu: New Bug description: Hi, Error within recompiling kernel module: DKMS make.log for bcmwl-6.30.223.248+bdcom for kernel 3.17.0-031700rc5-generic (x86_64) Fri Sep 19 17:07:55 CEST 2014 make: Entering directory '/usr/src/linux-headers-3.17.0-031700rc5-generic' CFG80211 API is prefered for this kernel version Using CFG80211 API LD /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/built-in.o CC [M] /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/shared/linux_osl.o CC [M] /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.o /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_alloc_linux_if’: /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.c:1316:64: error: macro alloc_netdev requires 4 arguments, but only 3 given dev = alloc_netdev(sizeof(priv_link_t), intf_name, ether_setup); ^ /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.c:1316:8: error: ‘alloc_netdev’ undeclared (first use in this function) dev = alloc_netdev(sizeof(priv_link_t), intf_name, ether_setup); ^ /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.c:1316:8: note: each undeclared identifier is reported only once for each function it appears in scripts/Makefile.build:257: recipe for target '/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.o' failed make[1]: *** [/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.o] Error 1 Makefile:1373: recipe for target '_module_/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build' failed make: *** [_module_/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build] Error 2 make: Leaving directory '/usr/src/linux-headers-3.17.0-031700rc5-generic' apt-cache policy bcmwl-kernel-source: bcmwl-kernel-source: Installed: 6.30.223.248+bdcom-0ubuntu1 Candidate: 6.30.223.248+bdcom-0ubuntu1 Version table: *** 6.30.223.248+bdcom-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ utopic/restricted amd64 Packages 100 /var/lib/dpkg/status lsb_release -rd Description: Ubuntu Utopic Unicorn (development branch) Release: 14.10 Thank You, Kind Reagrds, Martin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1371654/+subscriptions
[Kernel-packages] [Bug 1371591] Re: file not initialized to 0s under some conditions on VMWare
@bruce-lucas: Ok! I can reproduce this issue in VMWare Workstation. I'll start investigating more deeply. In my KVM instance previously I did not reproduce the issue. -- You 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 on VMWare Status in “linux” package in Ubuntu: In Progress Bug description: 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. 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. 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 1371591] Re: file not initialized to 0s under some conditions on VMWare
I accepted all the default settings when creating the VM (which for Fusion was 20 GB disk, 1 GB memory, single processor). On Fusion at least It is important to do the manual install: select installation method / more options / create a custom VM, mount the CD, set as boot device, bot up, go through the Ubuntu installer, accept the default to use LVM. If you go through select installation method / install from disc it does not take you through the Ubuntu installer UI, and it does not use LVM. At least that's what I see in Fusion; can't say for sure about Workstation. I reproduced it on VMWare Fusion, a customer reproduced it on VMWare ESXi (versions listed in original description). The kernel versions where it has been reproduced are also listed above next to the Ubuntu distro version. Some more information: * was able to reproduce the problem on Fedora 20 Fedora 20 (3.11.10-301, with LVM) * did not reproduce the problem on Centos 7.0 (3.10.0-123, with LVM) So so far all repros have been on 3.11 kernels or later. -- You 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 on VMWare Status in “linux” package in Ubuntu: In Progress Bug description: 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. 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. 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 1371316] Re: Please cherry-pick an aufs patch to unbreak it in conjunction with IMA
Ok precise should not be affected here as we do not have IMA enabled there. ** Changed in: linux (Ubuntu Precise) Status: In Progress = Invalid ** Changed in: linux (Ubuntu Precise) Assignee: Andy Whitcroft (apw) = (unassigned) ** Changed in: linux-lts-trusty (Ubuntu Precise) Assignee: (unassigned) = Andy Whitcroft (apw) ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: In Progress = 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/1371316 Title: Please cherry-pick an aufs patch to unbreak it in conjunction with IMA Status in “linux” package in Ubuntu: Invalid Status in “linux-lts-trusty” package in Ubuntu: Invalid Status in “linux” source package in Precise: Invalid Status in “linux-lts-trusty” source package in Precise: In Progress Status in “linux” source package in Trusty: In Progress Status in “linux-lts-trusty” source package in Trusty: Invalid Bug description: The trusty kernel misses the following patch that already landed in utopic with the recent aufs update: https://github.com/sfjro/aufs3-linux/commit/7aac34b421441b701cd0e6de4685b51e4c462d67 This unbreaks aufs with IMA (Integrity Measurement Architecture) enabled. When IMA is enabled and mmaps are being tracked, the kernel hits a lock ordering bug because a needed semaphore is already held. This patch fixes this issue by not calling out to IMA for the access to the underlying file. However IMA will still see the access to the file in the merged aufs, which should be good enough. Please cherry-pick above patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 on VMWare
** Information type changed from Public to Public Security -- You 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 on VMWare Status in “linux” package in Ubuntu: In Progress Bug description: 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. 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. 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 1371591] Re: file not initialized to 0s under some conditions on VMWare
Awesome, thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371591 Title: file not initialized to 0s under some conditions on VMWare Status in “linux” package in Ubuntu: In Progress Bug description: 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. 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. 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 1371591] Re: file not initialized to 0s under some conditions on VMWare
By the way, a couple more pieces of information that may be relevant: The problem is sensitive to the particular pattern of access to map0. If you remove either of the two writes (at 0x0 and 0x7000) the problem disappears, or if you change 0x7000 to a higher page it also disappears. We also observed a message about a WRITE SAME failure in syslog. I believe this means that the platform does not implement SCSI WRITE SAME, which I imagine would be used to zero pages under some circumstances, but instead uses a fallback of manually zeroing the pages. Perhaps there is a problem in this area? -- You 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 on VMWare Status in “linux” package in Ubuntu: In Progress Bug description: 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. 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. 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 1309578] Re: Ubuntu 14.04 suddenly reboots when booting from Live USB AMD A8 6600k
ps, no issues with my Windows 7, i use my Asus discrete graphics card as Dual graphics enabled with my APU, so the DVI cable is connected to the MOBO and not the GPU, dunno if this has any significance, jsut thought to mention that. good luck, and sorry if this isn't the same problem, i couldn't read all the comments, please feel free to advise... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1309578 Title: Ubuntu 14.04 suddenly reboots when booting from Live USB AMD A8 6600k Status in “linux” package in Ubuntu: Incomplete Bug description: I have a custom built AMD System with the following hardware currently running on Linux Mint 16 : AMD A8 6600k with Integrated graphics | MSI-FM2-A55M-E33 Motherboard | Kingston Hyperx Blu 4GB RAM | Corsair VS450 PSU Today when I tried to install 14.04 amd64 iso using a bootable USB, then the system rebooted. Any further attempts in installing it resulted in the same bug. As soon as I open the Ubuntu installer application and click Continue button then the system restarts after 2-3 seconds. I asked the same on AskUbuntu and some more guys reported the same problem with AMD APU, so I believe it to be a genuine bug and not just with me. The BIOS version is the latest one downloaded from MSI official website which is version 11.5. Also an Interesting thing is that this bug is common with the latest iso of Arch Linux too, but when booting older distros like Linux Mint 16 from USB, then everything works like it should, so it might have something to do with the newer 3.13 Kernel version. I am not an expert, but I can surely tell that only the newer distros are affected by this bug as reported by some other guys at AskUbuntu and the fact that Arch which is running the newer Kernel is having the same bug, so it probably has something to do with the newer Kernel, but I could be wrong. This bug is not letting me install Ubuntu 14.04 on my hardware and it is affecting a few more users too. Here is the AskUbuntu thread : http://askubuntu.com/questions/449391/unable-to-install-ubuntu-14-04 -pc-restarts-after-i-click-continue-button-in I hope this gets fixed soon or with the 14.04.1 upcoming July release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1309578] Re: Ubuntu 14.04 suddenly reboots when booting from Live USB AMD A8 6600k
FIXED restarting problems - I think it was a graphics driver Isssue CPU: AMD APU A86500 3.5ghz MOBO: MSI A78M-E35 2x4gb DDR3 RAM HyperX blu 1866mhz Asus HD6670 1GB DDR5 discrete graphics card OLD HDD: Ubuntu 12.04 64 bit on Mushkin 60gb SSD Windows 7 Home Premium 64 bit on Seagate 320 GB HDD 7200rpm NEW SSHD SSHD Seagate Hybrid drive 1TB O/S : Dual boot Windows 7 home premium 64 bit, Ubuntu 14.04 64bit Hi there, i am a casual user of Ubuntu since 2010 with dual boot of Windows in almost all of my systems. I have used Ubuntu 10.04, 12.04, and now 14.04. I am a newbie in techinical terms, so please excuse the lack of clarity. Initially i had problems installing Ubuntu 14.04 on the above new built in May 2014 alongside windows 7, both live cd and usb would load to install screen and restart constantly. After a few installation trials i gave up. however i successfully installed Ubuntu 12.04 64bit on the SSD and ran it for months no major issues, and my windows 7 boted fine on the normal hdd Today i wanted to upgrade to 14.04 as i migrated both my OS to my new SSHD Seagate 1TB, my SSD started to fail and i sent it back to Muskin, good after sales service, still waiting for replacement. Had to do boot repair for the old dual boot though, worked fine after that. It installed fine after a couple of installation trials when it would just restart automatically. Then during the post installation things to do it kept restarting numerous times. So I restarted on safe mode Linux 3.13.0-xx-generic (Recovery Mode), then booted with normal mode, when to additional drivers, unselected 'Using X.org X AMD/ATI display driver wrapper from xerver-xorg-video-ati (open source, tested)', then selected the last option at the bottom 'Using Video driver for the AMD graphics accelarators from fglrx-updates (proprietary)', rebooted and voila, problem fixed so far. I have been using it now for four hours and no restarting at all, cannot speak for longer term, i will post back daily to confirm or correct. Good luck... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1309578 Title: Ubuntu 14.04 suddenly reboots when booting from Live USB AMD A8 6600k Status in “linux” package in Ubuntu: Incomplete Bug description: I have a custom built AMD System with the following hardware currently running on Linux Mint 16 : AMD A8 6600k with Integrated graphics | MSI-FM2-A55M-E33 Motherboard | Kingston Hyperx Blu 4GB RAM | Corsair VS450 PSU Today when I tried to install 14.04 amd64 iso using a bootable USB, then the system rebooted. Any further attempts in installing it resulted in the same bug. As soon as I open the Ubuntu installer application and click Continue button then the system restarts after 2-3 seconds. I asked the same on AskUbuntu and some more guys reported the same problem with AMD APU, so I believe it to be a genuine bug and not just with me. The BIOS version is the latest one downloaded from MSI official website which is version 11.5. Also an Interesting thing is that this bug is common with the latest iso of Arch Linux too, but when booting older distros like Linux Mint 16 from USB, then everything works like it should, so it might have something to do with the newer 3.13 Kernel version. I am not an expert, but I can surely tell that only the newer distros are affected by this bug as reported by some other guys at AskUbuntu and the fact that Arch which is running the newer Kernel is having the same bug, so it probably has something to do with the newer Kernel, but I could be wrong. This bug is not letting me install Ubuntu 14.04 on my hardware and it is affecting a few more users too. Here is the AskUbuntu thread : http://askubuntu.com/questions/449391/unable-to-install-ubuntu-14-04 -pc-restarts-after-i-click-continue-button-in I hope this gets fixed soon or with the 14.04.1 upcoming July release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 on VMWare
** 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/1371591 Title: file not initialized to 0s under some conditions on VMWare Status in “linux” package in Ubuntu: In Progress Bug description: 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. 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. 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 1371316] Re: Please cherry-pick an aufs patch to unbreak it in conjunction with IMA
** Changed in: linux (Ubuntu Trusty) Importance: Undecided = Medium ** Changed in: linux-lts-trusty (Ubuntu Precise) Importance: Undecided = Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371316 Title: Please cherry-pick an aufs patch to unbreak it in conjunction with IMA Status in “linux” package in Ubuntu: Invalid Status in “linux-lts-trusty” package in Ubuntu: Invalid Status in “linux” source package in Precise: Invalid Status in “linux-lts-trusty” source package in Precise: In Progress Status in “linux” source package in Trusty: In Progress Status in “linux-lts-trusty” source package in Trusty: Invalid Bug description: The trusty kernel misses the following patch that already landed in utopic with the recent aufs update: https://github.com/sfjro/aufs3-linux/commit/7aac34b421441b701cd0e6de4685b51e4c462d67 This unbreaks aufs with IMA (Integrity Measurement Architecture) enabled. When IMA is enabled and mmaps are being tracked, the kernel hits a lock ordering bug because a needed semaphore is already held. This patch fixes this issue by not calling out to IMA for the access to the underlying file. However IMA will still see the access to the file in the merged aufs, which should be good enough. Please cherry-pick above patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371310] Re: docker.io doesn't work with 3.0 RC1 kernel
** 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/1371310 Title: docker.io doesn't work with 3.0 RC1 kernel Status in “apparmor” package in Ubuntu: New Status in “docker.io” package in Ubuntu: New Status in “linux” package in Ubuntu: Confirmed Bug description: Steps to reproduce (from https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor): 1. sudo apt-get install docker.io # 1.2.0~dfsg1-1 2. sudo docker pull ubuntu:trusty 3. sudo docker run ubuntu:trusty uptime 2014/09/18 15:48:48 Error response from daemon: Cannot start container fcdfaaf7945bcd9455fb5e0bde9950451152af14556880033818df7b50ddb1f4: set apparmor profile docker-default: permission denied What is expected? uptime to return something like: $ sudo docker run ubuntu:trusty uptime 20:31:21 up 1 min, 0 users, load average: 0.09, 0.06, 0.03 I set 'sudo sysctl -w kernel.printk_ratelimit=0' but there is nothing apparmor related in the logs. If I boot an earlier kernel without the 3.0 RC1 patches, it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1371310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371316] Re: Please cherry-pick an aufs patch to unbreak it in conjunction with IMA
I have applied this fix for testing. Could you test the kernels at the URL below and let us know if this sorts things for you: http://people.canonical.com/~apw/lp1371316-trusty/ Please report any testing back here. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371316 Title: Please cherry-pick an aufs patch to unbreak it in conjunction with IMA Status in “linux” package in Ubuntu: Invalid Status in “linux-lts-trusty” package in Ubuntu: Invalid Status in “linux” source package in Precise: Invalid Status in “linux-lts-trusty” source package in Precise: In Progress Status in “linux” source package in Trusty: In Progress Status in “linux-lts-trusty” source package in Trusty: Invalid Bug description: The trusty kernel misses the following patch that already landed in utopic with the recent aufs update: https://github.com/sfjro/aufs3-linux/commit/7aac34b421441b701cd0e6de4685b51e4c462d67 This unbreaks aufs with IMA (Integrity Measurement Architecture) enabled. When IMA is enabled and mmaps are being tracked, the kernel hits a lock ordering bug because a needed semaphore is already held. This patch fixes this issue by not calling out to IMA for the access to the underlying file. However IMA will still see the access to the file in the merged aufs, which should be good enough. Please cherry-pick above patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371411] Re: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1365]
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.17 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.17-rc5-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/1371411 Title: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1365] Status in “linux” package in Ubuntu: Incomplete Bug description: ??? ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-14-generic 3.16.0-14.20 [modified: boot/vmlinuz-3.16.0-14-generic] ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-14-generic x86_64 Annotation: Your system might become unstablenow and might need to be restarted. ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: phh4732 F pulseaudio /dev/snd/controlC0: phh4732 F pulseaudio Date: Thu Sep 18 14:55:48 2014 DuplicateSignature: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1365] RIP: 0010:location location ulReadMmRegisterUlongViaAddr+0xc/0x10 [fglrx] Failure: oops HibernationDevice: RESUME=UUID=8e014ded-873e-4733-bd8d-9093e68ef18a InstallationDate: Installed on 2014-09-18 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 (20140916) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7721 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-16-generic root=UUID=b8e29bf4-bea9-46ee-9516-047e2d7a7153 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8 RfKill: SourcePackage: linux Title: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1365] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V32.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A55M-E33 (MS-7721) dmi.board.vendor: MSI dmi.board.version: 7.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV32.5:bd03/20/2014:svnMSI:pnMS-7721:pvr7.0:rvnMSI:rnA55M-E33(MS-7721):rvr7.0:cvnMSI:ct3:cvr7.0: dmi.product.name: MS-7721 dmi.product.version: 7.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371623] Re: Keyboard giv entry like En, but shows Cs and is unable to set Cs funstionality at startup.
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.17 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.17-rc5-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/1371623 Title: Keyboard giv entry like En, but shows Cs and is unable to set Cs funstionality at startup. Status in “linux” package in Ubuntu: Incomplete Bug description: If I launch Ubuntu and make a entry from keyboard it gets chars like on English keymap. I have to turn keyboard by switch in right-top corner to En and again to Cs. After I can write in my national keyboard keyset ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-16-generic 3.16.0-16.22 [modified: boot/vmlinuz-3.16.0-16-generic] 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: jirka 2342 F pulseaudio CurrentDesktop: Unity Date: Fri Sep 19 16:18:39 2014 HibernationDevice: RESUME=UUID=bc5d379d-1433-47e9-9937-08cb7b735e7f InstallationDate: Installed on 2014-09-19 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140919) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 003: ID 8564:1000 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-7100 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-16-generic root=UUID=29b268e8-771e-48d1-81b5-5c38dc1c789d ro persistent quiet splash 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 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2005 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-7100 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/17/2005:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7100:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7100:rvr1.0:cvn:ct3:cvr: dmi.product.name: MS-7100 dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Changed in: linux (Ubuntu Utopic) Importance: Undecided = Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: New Status in “linux” package in Fedora: Unknown 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 1371325] Re: dkms script ... sed: -e expression #1, char 6: unknown command: `m'
Are you unable to install/upgrade to new Utopic kernels? ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Tags added: utopic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371325 Title: dkms script ... sed: -e expression #1, char 6: unknown command: `m' Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, this error appeared in ubuntu utopic 14.10 within installation of each kernel: run-parts: executing /etc/kernel/postinst.d/dkms 3.16.0-16-lowlatency /boot/vmlinuz-3.16.0-16-lowlatency sed: -e expression #1, char 6: unknown command: `m' Error! Problems with depmod detected. Automatically uninstalling this module. DKMS: Install Failed (depmod problems). Module rolled back to built state. sed: -e expression #1, char 6: unknown command: `m' /usr/sbin/dkms script: line 898: sed -e s/INITRD_MODULES=\\(.*\)\/INITRD_MODULES=\\1 $m\/ /etc/sysconfig/kernel $temp_dir_name/kernel.new line 904: sed -e s/\(INITRD_MODULES.*\)$m\b\(.*\)/\1\2/ /etc/sysconfig/kernel $temp_dir_name/kernel.new lsb_release -rd Description: Ubuntu Utopic Unicorn (development branch) Release: 14.10 apt-cache policy linux-image-3.16.0-16-generic linux-image-3.16.0-16-generic: Installed: 3.16.0-16.22 Candidate: 3.16.0-16.22 Version table: *** 3.16.0-16.22 0 500 http://archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status Thank You, Kind Regards, Martin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371325/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1360428] Comment bridged from LTC Bugzilla
--- Comment From ddstr...@us.ibm.com 2014-09-19 15:50 EDT--- Confirmed this is in the latest 14.10 kernel, closing this bug/feature. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1360428 Title: Feature: Add zpool patchset to ubuntu 14.10 Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Utopic: Fix Released Bug description: The zpool patch set allows zswap to use either zbud or zsmalloc for its compressed storage. The patches are upstream now and will be in 3.17. All 4 patches backported to ubuntu 14.10 kernel - only patch 2 required a minor context change. Taken from upstream patches (listed in reverse order of attached patches): 12d79d6 mm/zpool: update zswap to use zpool c795779 mm/zpool: zbud/zsmalloc implement zpool af8d417 mm/zpool: implement common zpool api to zbud/zsmalloc 99eef8e mm/zbud: change zbud_alloc size type to size_t To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1360428/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 on VMWare
@bruce-lucas OK I have reproduced this with the latest 3.17-rc kernel. So most likely this is an upstream issue. However I'll start testing previous versions to see if this is a regression between 3.10,3.11; this will help us zero in on the code changes that may have introduced this behavior. I do get the same error on my runs: [ 176.092640] dm-0: WRITE SAME failed. Manually zeroing. I'll investigate this in parallel. ** Tags added: kernel-bug-exists-upstream ** Also affects: linux (Ubuntu Trusty) 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/1371591 Title: file not initialized to 0s under some conditions on VMWare Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Trusty: New Bug description: 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. 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. 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 1371526] Re: ceph-disk-prepare command always fails; new partition table not avaliable until reboot
So to gather more pointers I tried a Trusty host and Utopic KVM guests. Either manually created (with virt-manager and not involving cloud-init then) and also using uvtool which is at least using a vdb for cloud-init data (in some way, though the image is a ro iso). Both ways the jbd2 process goes away after unmount. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371526 Title: ceph-disk-prepare command always fails; new partition table not avaliable until reboot Status in “ceph” package in Ubuntu: New Status in “linux” package in Ubuntu: Incomplete Bug description: $ sudo ceph-disk-prepare --fs-type xfs --zap-disk /dev/vdb Caution: invalid backup GPT header, but valid main header; regenerating backup header from main header. Warning! Main and backup partition tables differ! Use the 'c' and 'e' options on the recovery transformation menu to examine the two tables. Warning! One or more CRCs don't match. You should repair the disk! Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk verification and recovery are STRONGLY recommended. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. GPT data structures destroyed! You may now partition the disk using fdisk or other utilities. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. The operation has completed successfully. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. The operation has completed successfully. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. The operation has completed successfully. mkfs.xfs: cannot open /dev/vdb1: Device or resource busy ceph-disk: Error: Command '['/sbin/mkfs', '-t', 'xfs', '-f', '-i', 'size=2048', '--', '/dev/vdb1']' returned non-zero exit status 1 I can reproduce this consistently across ceph nodes; also impacts on the way we use swift for storage as well. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ceph 0.80.5-1 ProcVersionSignature: User Name 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 Date: Fri Sep 19 09:39:18 2014 Ec2AMI: ami-0084 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 SourcePackage: ceph UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 14.10 Ec2AMI: ami-0084 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Tags: utopic ec2-images Uname: Linux 3.16.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1371526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371634] Re: block devices appear twice
** Changed in: linux (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice Status in “linux” package in Ubuntu: Confirmed Bug description: $ sudo blkid /dev/sr0: LABEL=Ubuntu-Server 14.04 LTS ppc64el TYPE=iso9660 /dev/sda2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sda3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdb2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdb3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap /dev/sdg2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sdg3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdh2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdh3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap I'm not sure what exactly those block devices are (as in if they're raided in hardware or they actually represent physical spinning disks). But I do know that writing data to sda causes that data to be readable from sdg. The same is true: sda - sdg sdb - sdh That is what causes those UUIDs to be similar. Everything is functional, you just have to know that if your root device is /dev/sdg that you should probably not write data to /dev/sda thinking you can use it as a disk. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic ppc64le AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [ 88.736220] init: plymouth-upstart-bridge main process ended, respawning Date: Fri Sep 19 14:31:20 2014 HibernationDevice: RESUME=UUID=9c228177-d65c-4d19-a462-db1891e9781e Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 ro console=hvc0 BOOTIF=01-6c-ae-8b-6a-a0-88 quiet RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371634/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371634] Re: block devices appear twice
It looks like you have a couple of RAID controllers in the machine. Do you have them configured with and volumes, etc? 0003:04:00.0 RAID bus controller [0104]: IBM PCI-E IPR SAS Adapter (ASIC) [1014:034a] (rev 01) Subsystem: IBM PCIe3 x8 Cache SAS RAID Internal Adapter 6Gb (57D8) [1014:03fe]0003:04:00.0 RAID bus controller [0104]: IBM PCI-E IPR SAS Adapter (ASIC) [1014:034a] (rev 01) Subsystem: IBM PCIe3 x8 Cache SAS RAID Internal Adapter 6Gb (57D8) [1014:03fe] ** 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/1371634 Title: block devices appear twice Status in “linux” package in Ubuntu: Confirmed Bug description: $ sudo blkid /dev/sr0: LABEL=Ubuntu-Server 14.04 LTS ppc64el TYPE=iso9660 /dev/sda2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sda3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdb2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdb3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap /dev/sdg2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sdg3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdh2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdh3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap I'm not sure what exactly those block devices are (as in if they're raided in hardware or they actually represent physical spinning disks). But I do know that writing data to sda causes that data to be readable from sdg. The same is true: sda - sdg sdb - sdh That is what causes those UUIDs to be similar. Everything is functional, you just have to know that if your root device is /dev/sdg that you should probably not write data to /dev/sda thinking you can use it as a disk. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic ppc64le AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [ 88.736220] init: plymouth-upstart-bridge main process ended, respawning Date: Fri Sep 19 14:31:20 2014 HibernationDevice: RESUME=UUID=9c228177-d65c-4d19-a462-db1891e9781e Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 ro console=hvc0 BOOTIF=01-6c-ae-8b-6a-a0-88 quiet RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371634/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** No longer affects: linux (Fedora) -- You 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: New 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 1371233] Re: USB 3.0 connection is unreliable + xHCI xhci_drop_endpoint called with disabled ep
This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug. Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org. Once this bug is reported upstream, please add the tag: 'kernel-bug- reported-upstream'. [0] https://wiki.ubuntu.com/Bugs/Upstream/kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371233 Title: USB 3.0 connection is unreliable + xHCI xhci_drop_endpoint called with disabled ep Status in “linux” package in Ubuntu: Confirmed Bug description: based on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358871/comments/7 I tested with the HDD enclosure IcyBox IB-351 series with USB 3.0 connection with the same result (connection drops after 300 MB reading, error message xHCI xhci_drop_endpoint called with disabled ep occurs sometimes, other devices (e.g. Samsung HD103SI 1 TB HDD connected with 3.0 USB adapter to eSATA of enclosure) read hundreds of GB before failing, but definitely do before reading 1TB). Reading tested with `dd`, `gpart` and `btrfsck`. Also confirmed on Lenovo IdeaPad-Z500 after BIOS update to 71CN51WW(V1.21) (changelog didn't indicate any USB issues anyway). Also confirmed with 3.16.3 and 3.16.0-14 on Ubuntu 14.10-beta1 after updates. The issue seems to cause failure of ASIX AX179 gigabit ethernet chip as well, but is independent from the usage of the ethernet adapter. I'm without any clue and stuck with an unreliable USB and ethernet connection which basically means no I/O out of the machine!! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Thu Sep 18 19:58:24 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-10 (8 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 20221 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-35-generic.efi.signed root=UUID=5e999111-7efe-4818-b9e8-a950ad6d3296 ro rootflags=subvol=@ quiet splash nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371233] Re: USB 3.0 connection is unreliable + xHCI xhci_drop_endpoint called with disabled ep
Also, was there a prior kernel version that did not exhibit this bug? If there is, we can perform a bisect to identify the commit that introduced 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/1371233 Title: USB 3.0 connection is unreliable + xHCI xhci_drop_endpoint called with disabled ep Status in “linux” package in Ubuntu: Confirmed Bug description: based on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358871/comments/7 I tested with the HDD enclosure IcyBox IB-351 series with USB 3.0 connection with the same result (connection drops after 300 MB reading, error message xHCI xhci_drop_endpoint called with disabled ep occurs sometimes, other devices (e.g. Samsung HD103SI 1 TB HDD connected with 3.0 USB adapter to eSATA of enclosure) read hundreds of GB before failing, but definitely do before reading 1TB). Reading tested with `dd`, `gpart` and `btrfsck`. Also confirmed on Lenovo IdeaPad-Z500 after BIOS update to 71CN51WW(V1.21) (changelog didn't indicate any USB issues anyway). Also confirmed with 3.16.3 and 3.16.0-14 on Ubuntu 14.10-beta1 after updates. The issue seems to cause failure of ASIX AX179 gigabit ethernet chip as well, but is independent from the usage of the ethernet adapter. I'm without any clue and stuck with an unreliable USB and ethernet connection which basically means no I/O out of the machine!! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Thu Sep 18 19:58:24 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-10 (8 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 20221 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-35-generic.efi.signed root=UUID=5e999111-7efe-4818-b9e8-a950ad6d3296 ro rootflags=subvol=@ quiet splash nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1358746] Re: [kernel-fixed-upstream][Gigabyte Technology Co., Ltd. GA-A75-D3H] suspend/resume failure
** Changed in: linux (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1358746 Title: [kernel-fixed-upstream][Gigabyte Technology Co., Ltd. GA-A75-D3H] suspend/resume failure Status in “linux” package in Ubuntu: Fix Released Bug description: i got the erros message after startup ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-7-generic 3.16.0-7.12 ProcVersionSignature: Ubuntu 3.16.0-7.12-generic 3.16.0 Uname: Linux 3.16.0-7-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.5-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: balazs 1777 F pulseaudio Date: Sun Aug 17 13:27:32 2014 DuplicateSignature: suspend/resume:Gigabyte Technology Co., Ltd. GA-A75-D3H:F5b ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InterpreterPath: /usr/bin/python3.4 IwConfig: eth2 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-A75-D3H ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-7-generic root=UUID=742fd1ac-83a8-42ca-a907-11a16d73bc0e ro nosplash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-7-generic N/A linux-backports-modules-3.16.0-7-generic N/A linux-firmware1.132 RfKill: SourcePackage: linux Title: [Gigabyte Technology Co., Ltd. GA-A75-D3H] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/15/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5b dmi.board.name: GA-A75-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5b:bd03/15/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75-D3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75-D3H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-A75-D3H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358746/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 on VMWare
The 'regression' is between 3.9 and 3.10-rc1. I'll bisect between these tags to see where the issue is. -- You 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 on VMWare Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Trusty: New Bug description: 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. 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. 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 1370365] Re: After the last `apt-get update` the screen backlight is turned off.
Great, so we can bisect between 3.13.11.5 and 3.13.11.6. Before starting the bisect, can you also test the latest 3.13 upstream stable kernel to see if the bug has been fixed: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.11.7-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/1370365 Title: After the last `apt-get update` the screen backlight is turned off. Status in “linux” package in Ubuntu: Incomplete Bug description: Cause: After the last `apt-get update` and system `reboot` the screen backlight is turned off. Expected: The screen is expected to have the backlight turned on or at least to be able to set it on. Comment: The last update has updated the linux kernel and kernel headers package. After booting up with the new kerlnel the screen backlight has turned off after a second (right after the system boot). I have not found any way to torn it on, no mether if I increase or decrease the backlight setting and no mether if the system is working on batery or with the power cord attached. I am running Ubuntu Desktop 14.04 LTS at Dell Vostro-5470. $ uname -a Linux Vostro-5470 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 [modified: boot/vmlinuz-3.13.0-32-generic] 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.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebo 2267 F pulseaudio /dev/snd/pcmC1D0p: sebo 2267 F...m pulseaudio /dev/snd/controlC0: sebo 2267 F pulseaudio CurrentDesktop: Unity Date: Wed Sep 17 09:02:17 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-08 (39 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Vostro 5470 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro 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: No upgrade log present (probably fresh install) dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 0RYY7X 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.:bvrA00:bd08/09/2013:svnDellInc.:pnVostro5470:pvr:rvnDellInc.:rn0RYY7X:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Vostro 5470 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1370365/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371310] Re: docker.io doesn't work with 3.0 RC1 kernel
This is being caused by a bug fix in apparmor that places tighter requirements on the use of change_onexec from a multi-threaded application. How to best resolve this issue on the apparmor side is being investigated. It is very likely that docker is not using the change_profile api correctly, and should be audited as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371310 Title: docker.io doesn't work with 3.0 RC1 kernel Status in “apparmor” package in Ubuntu: New Status in “docker.io” package in Ubuntu: New Status in “linux” package in Ubuntu: Confirmed Bug description: Steps to reproduce (from https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor): 1. sudo apt-get install docker.io # 1.2.0~dfsg1-1 2. sudo docker pull ubuntu:trusty 3. sudo docker run ubuntu:trusty uptime 2014/09/18 15:48:48 Error response from daemon: Cannot start container fcdfaaf7945bcd9455fb5e0bde9950451152af14556880033818df7b50ddb1f4: set apparmor profile docker-default: permission denied What is expected? uptime to return something like: $ sudo docker run ubuntu:trusty uptime 20:31:21 up 1 min, 0 users, load average: 0.09, 0.06, 0.03 I set 'sudo sysctl -w kernel.printk_ratelimit=0' but there is nothing apparmor related in the logs. If I boot an earlier kernel without the 3.0 RC1 patches, it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1371310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371325] Re: dkms script ... sed: -e expression #1, char 6: unknown command: `m'
I am able to install/upgrade new Utopic Kernels. It is just small ammendments of that script :-) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371325 Title: dkms script ... sed: -e expression #1, char 6: unknown command: `m' Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, this error appeared in ubuntu utopic 14.10 within installation of each kernel: run-parts: executing /etc/kernel/postinst.d/dkms 3.16.0-16-lowlatency /boot/vmlinuz-3.16.0-16-lowlatency sed: -e expression #1, char 6: unknown command: `m' Error! Problems with depmod detected. Automatically uninstalling this module. DKMS: Install Failed (depmod problems). Module rolled back to built state. sed: -e expression #1, char 6: unknown command: `m' /usr/sbin/dkms script: line 898: sed -e s/INITRD_MODULES=\\(.*\)\/INITRD_MODULES=\\1 $m\/ /etc/sysconfig/kernel $temp_dir_name/kernel.new line 904: sed -e s/\(INITRD_MODULES.*\)$m\b\(.*\)/\1\2/ /etc/sysconfig/kernel $temp_dir_name/kernel.new lsb_release -rd Description: Ubuntu Utopic Unicorn (development branch) Release: 14.10 apt-cache policy linux-image-3.16.0-16-generic linux-image-3.16.0-16-generic: Installed: 3.16.0-16.22 Candidate: 3.16.0-16.22 Version table: *** 3.16.0-16.22 0 500 http://archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status Thank You, Kind Regards, Martin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371325/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371262] Re: kernel try to mount partition with unknown filesystem
I have installed that kernel and did try twice to run it but it freeze. So, after log in - within couple of seconds the computer hang up. So , I cannot test it. ** Tags added: kernel-unable-to-test-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/1371262 Title: kernel try to mount partition with unknown filesystem Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have got syslog error that kernel is trying to mount partition with unknown file system: Sep 18 01:03:39 ARIVUBU os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sde1 Sep 18 01:03:39 ARIVUBU kernel: [ 1149.585226] EXT4-fs (sde1): VFS: Can't find ext4 filesystem Sep 18 01:03:39 ARIVUBU kernel: [ 1149.586163] EXT4-fs (sde1): VFS: Can't find ext4 filesystem Sep 18 01:03:39 ARIVUBU kernel: [ 1149.587100] EXT4-fs (sde1): VFS: Can't find ext4 filesystem Sep 18 01:03:39 ARIVUBU kernel: [ 1149.588039] FAT-fs (sde1): invalid media value (0xb5) Sep 18 01:03:39 ARIVUBU kernel: [ 1149.588041] FAT-fs (sde1): Can't find a valid FAT filesystem Sep 18 01:03:39 ARIVUBU kernel: [ 1149.621168] XFS (sde1): Invalid superblock magic number Sep 18 01:03:39 ARIVUBU kernel: [ 1149.628618] FAT-fs (sde1): invalid media value (0xb5) Sep 18 01:03:39 ARIVUBU kernel: [ 1149.628620] FAT-fs (sde1): Can't find a valid FAT filesystem Sep 18 01:03:39 ARIVUBU kernel: [ 1149.631463] VFS: Can't find a Minix filesystem V1 | V2 | V3 on device sde1. Sep 18 01:03:39 ARIVUBU kernel: [ 1149.634430] hfsplus: unable to find HFS+ superblock Sep 18 01:03:39 ARIVUBU kernel: [ 1149.635388] qnx4: no qnx4 filesystem (no root dir). Sep 18 01:03:39 ARIVUBU kernel: [ 1149.636181] You didn't specify the type of your ufs filesystem Sep 18 01:03:39 ARIVUBU kernel: [ 1149.636181] Sep 18 01:03:39 ARIVUBU kernel: [ 1149.636181] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ... Sep 18 01:03:39 ARIVUBU kernel: [ 1149.636181] Sep 18 01:03:39 ARIVUBU kernel: [ 1149.636181] WARNING Wrong ufstype may corrupt your filesystem, default is ufstype=old Sep 18 01:03:39 ARIVUBU kernel: [ 1149.636349] ufs_read_super: bad magic number Sep 18 01:03:39 ARIVUBU kernel: [ 1149.637321] hfs: can't find a HFS filesystem on dev sde1 Sep 18 01:03:39 ARIVUBU os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sdf1 Sep 18 01:03:39 ARIVUBU kernel: [ 1149.784640] EXT4-fs (sdf1): VFS: Can't find ext4 filesystem Sep 18 01:03:39 ARIVUBU kernel: [ 1149.785889] EXT4-fs (sdf1): VFS: Can't find ext4 filesystem Sep 18 01:03:39 ARIVUBU kernel: [ 1149.787125] EXT4-fs (sdf1): VFS: Can't find ext4 filesystem Sep 18 01:03:39 ARIVUBU kernel: [ 1149.788280] FAT-fs (sdf1): invalid media value (0x7d) Sep 18 01:03:39 ARIVUBU kernel: [ 1149.788283] FAT-fs (sdf1): Can't find a valid FAT filesystem Sep 18 01:03:39 ARIVUBU kernel: [ 1149.793998] XFS (sdf1): Invalid superblock magic number Sep 18 01:03:39 ARIVUBU kernel: [ 1149.797373] FAT-fs (sdf1): invalid media value (0x7d) Sep 18 01:03:39 ARIVUBU kernel: [ 1149.797375] FAT-fs (sdf1): Can't find a valid FAT filesystem Sep 18 01:03:39 ARIVUBU kernel: [ 1149.801157] VFS: Can't find a Minix filesystem V1 | V2 | V3 on device sdf1. Sep 18 01:03:39 ARIVUBU kernel: [ 1149.802872] hfsplus: unable to find HFS+ superblock Sep 18 01:03:39 ARIVUBU kernel: [ 1149.804030] qnx4: no qnx4 filesystem (no root dir). Sep 18 01:03:39 ARIVUBU kernel: [ 1149.804847] You didn't specify the type of your ufs filesystem Sep 18 01:03:39 ARIVUBU kernel: [ 1149.804847] Sep 18 01:03:39 ARIVUBU kernel: [ 1149.804847] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ... Sep 18 01:03:39 ARIVUBU kernel: [ 1149.804847] Sep 18 01:03:39 ARIVUBU kernel: [ 1149.804847] WARNING Wrong ufstype may corrupt your filesystem, default is ufstype=old Sep 18 01:03:39 ARIVUBU kernel: [ 1149.805620] ufs_read_super: bad magic number Sep 18 01:03:39 ARIVUBU kernel: [ 1149.807247] hfs: can't find a HFS filesystem on dev sdf1 The first case: /dev/sde1 Partition is marked as bios-grub and should not be trying to be mounted by kernel. The second case /dev/sdf1 is used by truecrypt application . Kernel should not be trying to mount it. uname -a Linux ARIVUBU 3.16.0-14-lowlatency #20-Ubuntu SMP PREEMPT Sun Sep 7 00:05:40 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux apt-cache policy linux-image-3.16.0-14-lowlatency linux-image-3.16.0-14-lowlatency: Installed: 3.16.0-14.20 Candidate: 3.16.0-14.20 Version table: *** 3.16.0-14.20 0 500 http://archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status Thank You, Kind Regards, Martin P.S. Is it possible to tell to kernel not to trying mount some
[Kernel-packages] [Bug 1363462] Re: Crucial M550 1TB SSD missing from NCQ TRIM blacklist
** Changed in: linux (Ubuntu) Status: In Progress = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1363462 Title: Crucial M550 1TB SSD missing from NCQ TRIM blacklist Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Incomplete Bug description: I own a Crucial/Micron M550 1TB SSD which does has data loss when using NCQ TRIM. The current Ubuntu Trusty kernel has a blacklist which matches all M550 SSDs except the 1024 GB (1 TB) version because the matching pattern is limited to 3 digits for size. Upstream Linux has fixed this bug already: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2a13772a144d2956a7fedd18685921d0a9b8b783 Please try to get this merged and tell me where I can start an installation with a fixed kernel so I won't have a corrupt disk already on the end of the installation. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1363462/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1354710] Re: Backlight control does not work, but there are entries in /sys/class/backlight. Lenovo B570
I built the next test kernel, up to the following commit: e4f5a3adc454745fea35f1c312e14cbeba6e0ea4 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1354710 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1354710 Title: Backlight control does not work, but there are entries in /sys/class/backlight. Lenovo B570 Status in “linux” package in Ubuntu: Confirmed Bug description: Laptop model: Lenovo B570 package version: Ubuntu 3.13.0-32.57-generic 3.13.11.4 I expected the keys for changeing the backlight brightness to work they had no effect on the backlight further details in attatched Tar 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 i686 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: x321x321 1977 F pulseaudio Date: Sat Aug 9 16:11:34 2014 HibernationDevice: RESUME=UUID=61c2c6a6-4b45-4af0-941a-dadf05ad0aba InstallationDate: Installed on 2014-07-31 (8 days ago) InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140723) MachineType: LENOVO 1068FJG ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 44CN36WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr44CN36WW:bd07/11/2011:svnLENOVO:pn1068FJG:pvrLenovoB570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.name: 1068FJG dmi.product.version: Lenovo B570 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1354710/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1356558] Re: BUG: soft lockup - CPU stuck for 22s! [md3_raid1]
So the test kernel posted in comment #20 does fix this bug? It has commit c6c1f325 reverted. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1356558 Title: BUG: soft lockup - CPU stuck for 22s! [md3_raid1] Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, this bug appeared in Ubuntu 14.04, Ubuntu 12.04 didn't show this behavior. I've found a possible predecessor in bug #212684. Switching to a recent mainline kernel didn't fix this issue. Starting $ /usr/share/mdadm/checkarray /dev/md3 will repeat this behavior. /dev/md3 is a LVM PV: --- Physical volume --- PV Name /dev/md3 VG Name local_vg1 PV Size 1.36 TiB / not usable 2.25 MiB Allocatable yes PE Size 4.00 MiB Total PE 355619 Free PE 31011 Allocated PE 324608 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-33-generic 3.13.0-33.58 ProcVersionSignature: Ubuntu 3.13.0-33.58-generic 3.13.11.4 Uname: Linux 3.13.0-33-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-33-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Wed Aug 13 21:42:12 2014 HibernationDevice: RESUME=UUID=c4a03c5e-f650-4ca8-9dab-f0c4ad12c901 InstallationDate: Installed on 2014-07-06 (37 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release i386 (20140416.2) IwConfig: lono wireless extensions. em1 no wireless extensions. ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-33-generic root=UUID=9c2715cb-dd8a-4687-9537-009e1e4e83d8 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.13.0-33-generic N/A linux-backports-modules-3.13.0-33-generic N/A linux-firmware 1.127.5 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: JT94510H.86A.0045.2010.0519.1750 dmi.board.name: D945GSEJT dmi.board.vendor: Intel Corporation dmi.board.version: AAE57850-300 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrJT94510H.86A.0045.2010.0519.1750:bd05/19/2010:svn:pn:pvr:rvnIntelCorporation:rnD945GSEJT:rvrAAE57850-300:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1356558/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371733] [NEW] package linux-firmware 1.127.5 failed to install/upgrade: cannot copy extracted data for './lib/firmware/libertas/sd8686_v9.bin' to '/lib/firmware/libertas/sd8686
Public bug reported: dpkg-deb (subprocess): decompressing archive member: lzma error: compressed data is corrupt dpkg-deb: error: subprocess decompress returned error exit status 2 dpkg: error processing archive /var/cache/apt/archives/linux-firmware_1.127.6_all.deb (--unpack): cannot copy extracted data for './lib/firmware/libertas/sd8686_v9.bin' to '/lib/firmware/libertas/sd8686_v9.bin.dpkg-new': unexpected end of file or stream Errors were encountered while processing: /var/cache/apt/archives/linux-firmware_1.127.6_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) 32-bit Ubuntu 14.04 on Pentium 4 SM-IG31-MKII Simmtronics (G33/31 Express) Intel® G33 x86/MMX/SSE2 2GB DDR2 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-firmware 1.127.5 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic i686 ApportVersion: 2.14.1-0ubuntu3.4 AptOrdering: linux-firmware: Install linux-firmware: Configure Architecture: i386 Date: Fri Sep 19 23:18:45 2014 Dependencies: DuplicateSignature: package:linux-firmware:1.127.5:cannot copy extracted data for './lib/firmware/libertas/sd8686_v9.bin' to '/lib/firmware/libertas/sd8686_v9.bin.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './lib/firmware/libertas/sd8686_v9.bin' to '/lib/firmware/libertas/sd8686_v9.bin.dpkg-new': unexpected end of file or stream InstallationDate: Installed on 2014-01-06 (256 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) PackageArchitecture: all SourcePackage: linux-firmware Title: package linux-firmware 1.127.5 failed to install/upgrade: cannot copy extracted data for './lib/firmware/libertas/sd8686_v9.bin' to '/lib/firmware/libertas/sd8686_v9.bin.dpkg-new': unexpected end of file or stream UpgradeStatus: Upgraded to trusty on 2014-04-21 (151 days ago) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- 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/1371733 Title: package linux-firmware 1.127.5 failed to install/upgrade: cannot copy extracted data for './lib/firmware/libertas/sd8686_v9.bin' to '/lib/firmware/libertas/sd8686_v9.bin.dpkg-new': unexpected end of file or stream Status in “linux-firmware” package in Ubuntu: New Bug description: dpkg-deb (subprocess): decompressing archive member: lzma error: compressed data is corrupt dpkg-deb: error: subprocess decompress returned error exit status 2 dpkg: error processing archive /var/cache/apt/archives/linux-firmware_1.127.6_all.deb (--unpack): cannot copy extracted data for './lib/firmware/libertas/sd8686_v9.bin' to '/lib/firmware/libertas/sd8686_v9.bin.dpkg-new': unexpected end of file or stream Errors were encountered while processing: /var/cache/apt/archives/linux-firmware_1.127.6_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) 32-bit Ubuntu 14.04 on Pentium 4 SM-IG31-MKII Simmtronics (G33/31 Express) Intel® G33 x86/MMX/SSE2 2GB DDR2 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-firmware 1.127.5 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic i686 ApportVersion: 2.14.1-0ubuntu3.4 AptOrdering: linux-firmware: Install linux-firmware: Configure Architecture: i386 Date: Fri Sep 19 23:18:45 2014 Dependencies: DuplicateSignature: package:linux-firmware:1.127.5:cannot copy extracted data for './lib/firmware/libertas/sd8686_v9.bin' to '/lib/firmware/libertas/sd8686_v9.bin.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './lib/firmware/libertas/sd8686_v9.bin' to '/lib/firmware/libertas/sd8686_v9.bin.dpkg-new': unexpected end of file or stream InstallationDate: Installed on 2014-01-06 (256 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) PackageArchitecture: all SourcePackage: linux-firmware Title: package linux-firmware 1.127.5 failed to install/upgrade: cannot copy extracted data for './lib/firmware/libertas/sd8686_v9.bin' to '/lib/firmware/libertas/sd8686_v9.bin.dpkg-new': unexpected end of file or stream UpgradeStatus: Upgraded to trusty on 2014-04-21 (151 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1371733/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 898003] Re: usbip source is maintained in kernel tree now
This really needs some attention. USBIP will be moved out of the staging area in kernel 3.17. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/898003 Title: usbip source is maintained in kernel tree now Status in “linux” package in Ubuntu: Won't Fix Status in “usbip” package in Ubuntu: Confirmed Bug description: Both the userspace and kernel module parts of usbip are in the linux kernel tree now. The source used in this package is quite old. I'm not sure how to best handle the packaging aspects here -- I imagine that it would be undesirable for usbip to be built as a side effect of the main kernel package build, because then the kernel package build would be even slower and usbip is probably not updated enough to justify that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/898003/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371614] Re: linux: 3.16.0-17.23 -proposed tracker
** Changed in: kernel-development-workflow/prepare-package-meta Status: New = Fix Released ** Changed in: kernel-development-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) = Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371614 Title: linux: 3.16.0-17.23 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow package-testing series: New Status in Kernel Development Workflow prepare-package series: New Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-release series: New Status in “linux” package in Ubuntu: New Status in “linux” source package in Utopic: New Bug description: This bug is for tracking the 3.16.0-17.23 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Friday, 19. September 2014 13:59 UTC kernel-phase-changed:Friday, 19. September 2014 13:59 UTC kernel-phase:Prepare To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1371614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371733] Re: package linux-firmware 1.127.5 failed to install/upgrade: cannot copy extracted data for './lib/firmware/libertas/sd8686_v9.bin' to '/lib/firmware/libertas/sd8686_v
** Tags removed: need-duplicate-check -- 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/1371733 Title: package linux-firmware 1.127.5 failed to install/upgrade: cannot copy extracted data for './lib/firmware/libertas/sd8686_v9.bin' to '/lib/firmware/libertas/sd8686_v9.bin.dpkg-new': unexpected end of file or stream Status in “linux-firmware” package in Ubuntu: New Bug description: dpkg-deb (subprocess): decompressing archive member: lzma error: compressed data is corrupt dpkg-deb: error: subprocess decompress returned error exit status 2 dpkg: error processing archive /var/cache/apt/archives/linux-firmware_1.127.6_all.deb (--unpack): cannot copy extracted data for './lib/firmware/libertas/sd8686_v9.bin' to '/lib/firmware/libertas/sd8686_v9.bin.dpkg-new': unexpected end of file or stream Errors were encountered while processing: /var/cache/apt/archives/linux-firmware_1.127.6_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) 32-bit Ubuntu 14.04 on Pentium 4 SM-IG31-MKII Simmtronics (G33/31 Express) Intel® G33 x86/MMX/SSE2 2GB DDR2 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-firmware 1.127.5 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic i686 ApportVersion: 2.14.1-0ubuntu3.4 AptOrdering: linux-firmware: Install linux-firmware: Configure Architecture: i386 Date: Fri Sep 19 23:18:45 2014 Dependencies: DuplicateSignature: package:linux-firmware:1.127.5:cannot copy extracted data for './lib/firmware/libertas/sd8686_v9.bin' to '/lib/firmware/libertas/sd8686_v9.bin.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './lib/firmware/libertas/sd8686_v9.bin' to '/lib/firmware/libertas/sd8686_v9.bin.dpkg-new': unexpected end of file or stream InstallationDate: Installed on 2014-01-06 (256 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) PackageArchitecture: all SourcePackage: linux-firmware Title: package linux-firmware 1.127.5 failed to install/upgrade: cannot copy extracted data for './lib/firmware/libertas/sd8686_v9.bin' to '/lib/firmware/libertas/sd8686_v9.bin.dpkg-new': unexpected end of file or stream UpgradeStatus: Upgraded to trusty on 2014-04-21 (151 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1371733/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1356558] Re: BUG: soft lockup - CPU stuck for 22s! [md3_raid1]
Hello Joseph, the last kernel, you have prepared for testing contains this bug. I've just noticed that 3.13.0-031300rc3-generic kernel contains the bug the bug as well, so the bisect went in the wrong direction. Sorry for this. I'll have a deeper look inside, hoping to understand why the bug didn't appear during the first testing. [44094.835704] md: data-check of RAID array md1 [44094.835716] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. [44094.835723] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for data-check. [44094.835732] md: using 128k window, over a total of 4192192k. [44095.909810] type=1400 audit(1411015241.514:35): apparmor=STATUS operation=profile_replace name=/usr/lib/cups/backend/cups-pdf pid=8865 comm=apparmor_parser [44095.909839] type=1400 audit(1411015241.514:36): apparmor=STATUS operation=profile_replace name=/usr/sbin/cupsd pid=8865 comm=apparmor_parser [44095.912967] type=1400 audit(1411015241.518:37): apparmor=STATUS operation=profile_replace name=/usr/sbin/cupsd pid=8865 comm=apparmor_parser [44403.916160] INFO: task md1_resync:8767 blocked for more than 120 seconds. [44403.916448] Not tainted 3.13.0-031300rc3-generic #201312061335 [44403.916692] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [44403.916988] md1_resync D c10a8e24 0 8767 2 0x [44403.917009] ebc1bd5c 0046 ebc1bce8 c10a8e24 0092 20e0b127 2833 c1af0400 [44403.917039] c105bbd2 c1af0400 f7bde400 e794b400 f7210d00 f6a8be48 ebc1bd1c [44403.917066] ebc1bd30 f6a8be00 f6a8be48 ebc1bd70 ebc1bd90 c16998b3 0082 e794b400 [44403.917093] Call Trace: [44403.917122] [c10a8e24] ? irq_to_desc+0x14/0x20 [44403.917141] [c105bbd2] ? irq_exit+0x62/0xa0 [44403.917162] [c16998b3] ? common_interrupt+0x33/0x38 [44403.917178] [c1093f31] ? prepare_to_wait_event+0x71/0xd0 [44403.917195] [c168e733] schedule+0x23/0x60 [44403.917247] [f8444e45] raise_barrier+0x125/0x1c0 [raid1] [44403.917263] [c1094010] ? __wake_up_sync+0x20/0x20 [44403.917291] [f8444fab] sync_request+0xcb/0xad0 [raid1] [44403.917312] [c1534b9f] md_do_sync+0x9bf/0x1000 [44403.917341] [f8444ee0] ? raise_barrier+0x1c0/0x1c0 [raid1] [44403.917361] [c10653d7] ? recalc_sigpending+0x17/0x50 [44403.917379] [c1531da0] ? md_rdev_init+0x100/0x100 [44403.917395] [c1531e84] md_thread+0xe4/0x110 [44403.917409] [c1093adf] ? __wake_up_locked+0x1f/0x30 [44403.917426] [c1531da0] ? md_rdev_init+0x100/0x100 [44403.917441] [c107625b] kthread+0x9b/0xb0 [44403.917459] [c1699337] ret_from_kernel_thread+0x1b/0x28 [44403.917474] [c10761c0] ? flush_kthread_worker+0x90/0x90 [44523.916155] INFO: task md1_resync:8767 blocked for more than 120 seconds. [44523.916433] Not tainted 3.13.0-031300rc3-generic #201312061335 [44523.916676] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [44523.916972] md1_resync D c10a8e24 0 8767 2 0x [44523.916993] ebc1bd5c 0046 ebc1bce8 c10a8e24 0092 20e0b127 2833 c1af0400 [44523.917022] c105bbd2 c1af0400 f7bde400 e794b400 f7210d00 f6a8be48 ebc1bd1c [44523.917049] ebc1bd30 f6a8be00 f6a8be48 ebc1bd70 ebc1bd90 c16998b3 0082 e794b400 [44523.917077] Call Trace: [44523.917106] [c10a8e24] ? irq_to_desc+0x14/0x20 [44523.917125] [c105bbd2] ? irq_exit+0x62/0xa0 [44523.917145] [c16998b3] ? common_interrupt+0x33/0x38 [44523.917162] [c1093f31] ? prepare_to_wait_event+0x71/0xd0 [44523.917179] [c168e733] schedule+0x23/0x60 [44523.917232] [f8444e45] raise_barrier+0x125/0x1c0 [raid1] [44523.917248] [c1094010] ? __wake_up_sync+0x20/0x20 [44523.917276] [f8444fab] sync_request+0xcb/0xad0 [raid1] [44523.917296] [c1534b9f] md_do_sync+0x9bf/0x1000 [44523.917325] [f8444ee0] ? raise_barrier+0x1c0/0x1c0 [raid1] [44523.917345] [c10653d7] ? recalc_sigpending+0x17/0x50 [44523.917363] [c1531da0] ? md_rdev_init+0x100/0x100 [44523.917379] [c1531e84] md_thread+0xe4/0x110 [44523.917393] [c1093adf] ? __wake_up_locked+0x1f/0x30 [44523.917410] [c1531da0] ? md_rdev_init+0x100/0x100 [44523.917425] [c107625b] kthread+0x9b/0xb0 [44523.917443] [c1699337] ret_from_kernel_thread+0x1b/0x28 [44523.917458] [c10761c0] ? flush_kthread_worker+0x90/0x90 [44643.916158] INFO: task md1_resync:8767 blocked for more than 120 seconds. [44643.916436] Not tainted 3.13.0-031300rc3-generic #201312061335 [44643.916679] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [44643.916975] md1_resync D c10a8e24 0 8767 2 0x [44643.916996] ebc1bd5c 0046 ebc1bce8 c10a8e24 0092 20e0b127 2833 c1af0400 [44643.917026] c105bbd2 c1af0400 f7bde400 e794b400 f7210d00 f6a8be48 ebc1bd1c [44643.917052] ebc1bd30 f6a8be00 f6a8be48 ebc1bd70 ebc1bd90 c16998b3 0082 e794b400 [44643.917080] Call Trace: [44643.917109] [c10a8e24] ? irq_to_desc+0x14/0x20 [44643.917128] [c105bbd2] ? irq_exit+0x62/0xa0 [44643.917149] [c16998b3] ?
[Kernel-packages] [Bug 1341027] Re: init: Failed to obtain startpar-bridge instance: Unknown parameter: INSTANCE
In Utopic kernel 3.16 it is still appearing. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1341027 Title: init: Failed to obtain startpar-bridge instance: Unknown parameter: INSTANCE Status in “linux” package in Ubuntu: Incomplete Bug description: [6.768712] init: Failed to obtain startpar-bridge instance: Unknown parameter: INSTANCE ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-3-lowlatency 3.16.0-3.8 ProcVersionSignature: Ubuntu 3.16.0-3.8-lowlatency 3.16.0-rc4 Uname: Linux 3.16.0-3-lowlatency x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: caravena 2878 F...m pulseaudio /dev/snd/controlC1: caravena 2878 F pulseaudio /dev/snd/controlC0: caravena 2878 F pulseaudio CurrentDesktop: GNOME Date: Fri Jul 11 20:10:48 2014 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2014-04-27 (75 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-3-lowlatency root=UUID=13144268-2374-4154-83f1-c35d81306190 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-3-lowlatency N/A linux-backports-modules-3.16.0-3-lowlatency N/A linux-firmware 1.132 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1341027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
