[Kernel-packages] [Bug 1327220] Re: No sound after kernel upgrade
For me, the problem has been fixed in kernel version 2.6.32-62. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1327220 Title: No sound after kernel upgrade Status in “linux” package in Ubuntu: Won't Fix Bug description: After a kernel upgrade to linux-image-2.6.32-61-generic sound has stopped working. Sound applications hang and no sound is produced. "ubuntu-bug -s audio" does produce the first test tone but not the second one. Any subsequent attempt to close apport then causes it to stop responding. After rebooting with the previous kernel (linux- image-2.6.32-60-generic) sound works as before. Machine is a Dell E5500 laptop with HDA-Intel sound hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327220/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1315736] Re: [Dell PowerEdge R720] Machine Check Exception
This is duplicate of #1323165 . There is also a possible 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/1315736 Title: [Dell PowerEdge R720] Machine Check Exception Status in “linux” package in Ubuntu: Incomplete Bug description: Dell PowerEdge 720 on ubuntu 14.04 shows MCE errors on dmesg. Dell support instructed to run DSET and BIOS hardware diagnostics. Neither of the tools showed any errors. Dell support said that if there was a hardware error it would have been shown on Dell logs and the probable reason for the dmesg log is a bug in ubuntu kernel MCE reporting. So, is it that following dmesg is because of a kernel bug in ubuntu 14.04 server? [11562.171040] Please check user daemon is running. [94953.306404] sbridge: HANDLING MCE MEMORY ERROR [94953.306415] CPU 1: Machine Check Exception: 0 Bank 9: 8c4b000800c0 [94953.306416] TSC 0 ADDR 2dfa0e1000 MISC 9800080168c PROCESSOR 0:306e4 TIME 1399142359 SOCKET 1 APIC 20 [94953.306422] sbridge: HANDLING MCE MEMORY ERROR [94953.306423] CPU 1: Machine Check Exception: 0 Bank 10: 8c5800c1 [94953.306424] TSC 0 ADDR 2dfa0e1000 MISC 900208c PROCESSOR 0:306e4 TIME 1399142359 SOCKET 1 APIC 20 [94953.532217] EDAC MC1: 1 CE memory scrubbing error on CPU_SrcID#1_Channel#0_DIMM#0 (channel:0 slot:0 page:0x2dfa0e1 offset:0x0 grain:32 syndrome:0x0 - area:DRAM err_code:0008:00c0 socket:1 channel_mask:3 rank:0) [94953.532226] EDAC MC1: 1 CE memory scrubbing error on CPU_SrcID#1_Channel#1_DIMM#0 (channel:1 slot:0 page:0x2dfa0e1 offset:0x0 grain:32 syndrome:0x0 - area:DRAM err_code:0008:00c1 socket:1 channel_mask:3 rank:0) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 touko 2 19:15 seq crw-rw 1 root audio 116, 33 touko 2 19:15 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory 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 InstallationDate: Installed on 2014-02-26 (66 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140219) MachineType: Dell Inc. PowerEdge R720 Package: linux (not installed) PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=c03eb237-955a-4dee-bba1-deded53df372 ro ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/16/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.2.2 dmi.board.name: 0DCWD1 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.2.2:bd01/16/2014:svnDellInc.:pnPowerEdgeR720:pvr:rvnDellInc.:rn0DCWD1:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R720 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1315736/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1305522] Re: Backport Synaptics HID touchpad driver for 14.04
When this fixed in 14.04 Trusty Tahr for 14.04.1 (24 July)? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1305522 Title: Backport Synaptics HID touchpad driver for 14.04 Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Trusty: In Progress Bug description: Synaptics just upstreamed a new set of HID touchpad driver: http://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/commit/?h=for-3.16/rmi4&id=9fb6bf02e3ad04c20edb8e46536ce3eeda32c736 It's better we can have it in 14.04 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1305522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1308761] Re: apparmor spams log with warning message
When this fixed in 14.04 Trusty Tahr for 14.04.1 (24 July)? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308761 Title: apparmor spams log with warning message Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Confirmed Status in “linux” source package in Utopic: Fix Released Bug description: The apparmor kernel module will spam the dmesg log with a stack trace and warning when the label on a unix socket does not match the label on the task sending the message. This happens when a socket is delegated to another task Example Message in the log Apr 5 05:16:45 cormac kernel: [66784.479777] [ cut here ] Apr 5 05:16:45 cormac kernel: [66784.479791] WARNING: CPU: 0 PID: 21866 at /build/buildd/linux-3.13.0/security/apparmor/lsm.c:839 apparmor_unix_may_send+0x16c/0x180() Apr 5 05:16:45 cormac kernel: [66784.479793] AppArmor WARN apparmor_unix_may_send: ((!aa_label_is_subset(cxt->label, label))): Apr 5 05:16:45 cormac kernel: [66784.479794] Modules linked in: xt_hl ipt_REJECT xt_comment xt_limit xt_tcpudp xt_addrtype ppdev nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp iptable_filter ip_tables kvm_intel kvm cirrus psmouse serio_raw ip6t_REJECT xt_LOG ttm ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack parport_pc ip6table_filter ip6_tables x_tables drm_kms_helper drm lp parport mac_hid syscopyarea sysfillrect sysimgblt i2c_piix4 floppy Apr 5 05:16:45 cormac kernel: [66784.479828] CPU: 0 PID: 21866 Comm: sshd Tainted: GW3.13.0-22-generic #44-Ubuntu Apr 5 05:16:45 cormac kernel: [66784.479829] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 Apr 5 05:16:45 cormac kernel: [66784.479832] 0009 8800d5d25bd0 81714914 8800d5d25c18 Apr 5 05:16:45 cormac kernel: [66784.479834] 8800d5d25c08 810676bd 8800d67a3c30 880138147b80 Apr 5 05:16:45 cormac kernel: [66784.479836] 88003681cb40 880138147680 8801384217f0 8800d5d25c68 Apr 5 05:16:45 cormac kernel: [66784.479839] Call Trace: Apr 5 05:16:45 cormac kernel: [66784.479846] [] dump_stack+0x45/0x56 Apr 5 05:16:45 cormac kernel: [66784.479851] [] warn_slowpath_common+0x7d/0xa0 Apr 5 05:16:45 cormac kernel: [66784.479853] [] warn_slowpath_fmt+0x4c/0x50 Apr 5 05:16:45 cormac kernel: [66784.479855] [] apparmor_unix_may_send+0x16c/0x180 Apr 5 05:16:45 cormac kernel: [66784.479859] [] security_unix_may_send+0x16/0x20 Apr 5 05:16:45 cormac kernel: [66784.479863] [] unix_dgram_sendmsg+0x2a5/0x620 Apr 5 05:16:45 cormac kernel: [66784.479868] [] sock_sendmsg+0x8b/0xc0 Apr 5 05:16:45 cormac kernel: [66784.479872] [] ? kvm_clock_read+0x1f/0x30 Apr 5 05:16:45 cormac kernel: [66784.479875] [] SYSC_sendto+0x121/0x1c0 Apr 5 05:16:45 cormac kernel: [66784.479901] [] ? vtime_account_user+0x54/0x60 Apr 5 05:16:45 cormac kernel: [66784.479907] [] ? syscall_trace_enter+0x145/0x250 Apr 5 05:16:45 cormac kernel: [66784.479909] [] SyS_sendto+0xe/0x10 Apr 5 05:16:45 cormac kernel: [66784.479913] [] tracesys+0xe1/0xe6 Apr 5 05:16:45 cormac kernel: [66784.479915] ---[ end trace c4dfb167bafcc341 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1054732] Re: [LENOVO 4298R86] suspend/resume failure
When this fixed in 14.04 Trusty Tahr for 14.04.1 (24 July)? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1054732 Title: [LENOVO 4298R86] suspend/resume failure Status in “linux” package in Ubuntu: Incomplete Status in “linux” source package in Raring: Expired Status in “linux” source package in Saucy: Incomplete Bug description: Getting that message every time I open lid, or, sometime, even during normal workflow. ProblemType: KernelOops DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-15-generic 3.5.0-15.22 ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4 Uname: Linux 3.5.0-15-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.5.2-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amarao 2066 F pulseaudio Date: Sat Sep 22 01:33:21 2012 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=d3e012f1-f3c1-4ffe-9908-1d77a770d06b InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) InterpreterPath: /usr/bin/python3.2mu MachineType: LENOVO 4298R86 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-15-generic root=UUID=da13c7f0-b499-4c33-a0ea-6e1b7170d913 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.5.0-15-generic N/A linux-backports-modules-3.5.0-15-generic N/A linux-firmware1.93 SourcePackage: linux Title: [LENOVO 4298R86] suspend/resume failure UpgradeStatus: Upgraded to quantal on 2012-09-16 (5 days ago) UserGroups: dmi.bios.date: 12/01/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET56WW (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 4298R86 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:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4298R86:pvrThinkPadX220Tablet:rvnLENOVO:rn4298R86:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4298R86 dmi.product.version: ThinkPad X220 Tablet dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1054732/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328088] Re: Kernel network namespace performance regression during rcu development on kernels above 3.8
** Description changed:
Please, follow this in: http://people.canonical.com/~inaddy/lp1328088/.
Same description on daily-basis updated text.
--
-
- It was brought to my attention that "fake router creation" scalability
- was affected during kernel development.
+ It was brought to my attention that network namespace creation scalability
was affected during kernel development.
The following script was used for all the tests and charts generation:
http://people.canonical.com/~inaddy/lp1328088/make_fake_routers.sh
http://people.canonical.com/~inaddy/lp1328088/parse.py
I measured how many "fake routers" (above script) could be added per
second from 0 to 4000 created routers mark. Using this script and a git
bisect on kernel tree I was led to one specific commit causing
- regression: #911af505 "rcu: Provide compile-time control for no-CBs
- CPUs".
+ regression: #911af50 "rcu: Provide compile-time control for no-CBs
+ CPUs". Even Though this change was experimental at that point, it
+ introduced a performance scalability regression (explained below) that
+ still last and seems to be the default option for distributions
+ nowadays.
- It appeared that rcu, rcu callbacks and no-cb cpus were causing the
- issue so every commit that changed any of this files: "kernel/rcutree.c
- kernel/rcutree.h kernel/rcutree_plugin.h include/trace/events/rcu.h
- include/linux/rcupdate.h" was tested. The idea was to check performance
- regression during rcu development. In the worst case I would have data
- for performance regression during kernel development (since we have rcu
- commits from 3.8 to 3.14).
+ RCU related code looked like to be responsible for the problem. With
+ that, every commit from tag v3.8..master that changed any of this files:
+ "kernel/rcutree.c kernel/rcutree.h kernel/rcutree_plugin.h
+ include/trace/events/rcu.h include/linux/rcupdate.h" was tested. The
+ idea was to check performance regression during rcu development. In the
+ worst case, the regression not being related to rcu, I would still have
+ data to interpret the performance/scalability regression.
All text below this refer to 2 groups of charts, generated during the
study:
1) Kernel git tags from 3.8 to 3.14.
http://people.canonical.com/~inaddy/lp1328088/charts/250-tag.html
2) Kernel git commits for rcu development (111 commits).
http://people.canonical.com/~inaddy/lp1328088/charts/250.html
Since there was difference in results depending on how many cpus or how
the no-cb cpus were configured, 3 kernel config options were used on
every measure:
- - CONFIG_RCU_NOCB_CPU (disabled: nocbno)
- - CONFIG_RCU_NOCB_CPU_ALL (enabled: nocball)
- - CONFIG_RCU_NOCB_CPU_NONE (enabled: nocbnone)
+ - CONFIG_RCU_NOCB_CPU (disabled): nocbno
+ - CONFIG_RCU_NOCB_CPU_ALL (enabled): nocball
+ - CONFIG_RCU_NOCB_CPU_NONE (enabled): nocbnone
- After charts generation and study it was clear that NOCB_CPU_ALL (4
- cpus) affected the "fake routers" creation process performance and this
+ Obs: For 1 cpu cases: nocbno, nocbnone, nocball behaves the same since
+ w/ only 1 cpu there is no no-cb cpu
+
+ After charts being generated it was clear that NOCB_CPU_ALL (4 cpus)
+ affected the "fake routers" creation process performance and this
regression continues up to upstream version. It was also clear that,
- after this commit, there is no scalability executing this test with more
- than 1 cpu.
+ after commit #911af50, having more than 1 cpu does not improve
+ performance/scalability for netns, makes it worse.
+
+ #911af50
+ ...
+ +#ifdef CONFIG_RCU_NOCB_CPU_ALL
+ + pr_info("\tExperimental no-CBs for all CPUs\n");
+ + cpumask_setall(rcu_nocb_mask);
+ +#endif /* #ifdef CONFIG_RCU_NOCB_CPU_ALL */
+ ...
Comparing standing out points (see charts):
#81e5949 - good
#911af50 - bad
- #6faf728 - not good enough
- I was able to see that from the script above the following lines were
- affected:
+ I was able to see that, from the script above, the following lines
+ causes major impact on netns scalability/performance:
- 1) ip netns add -> huge performance regression
+ 1) ip netns add -> huge performance regression:
+ 1 cpu: no regression
+ 4 cpu: regression for NOCB_CPU_ALL
+ obs: regression from 250 netns/sec to 50 netns/sec
+ on 500 netns already created mark
+
2) ip netns exec -> some performance regression
+ 1 cpu: no regression
+ 4 cpu: regression for NOCB_CPU_ALL
+ obs: regression from 40 netns (+1 exec per netns
+ creation) to 20 netns/sec on 500 netns created
+ mark
- #
- # Assumption
- #
+ # Assumption (to be confirmed)
rcu callbacks being offloaded to other cpus caused regression in
- unshare(CLONE_NEWNET) code.
-
- # Specific kernel entry being investigated:
-
- unshare(CLONE_NEWNET)
+ copy_net_ns<-created_new_namespaces or unshare(clone_newnet).
--
You received this bug notification because you are a member of Kernel
[Kernel-packages] [Bug 1306573] Re: The kernel seems to fail to cache disk blocks in some cases.
OK... Just for reference, the problem was fixed by installing a 64-bit kernel. Apparently something about caching doesn't work properly on a 32-bit machine with 16G RAM. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1306573 Title: The kernel seems to fail to cache disk blocks in some cases. Status in “linux” package in Ubuntu: Expired Bug description: I have a server with 16G RAM. When running Ubuntu 10.04, it would cache my mail directory (with way too many messages: about 2), and starting mutt was quick unless the daily backup had been running. After upgrading to 14.04, I now notice that I have to wait much more often for the maildir to get cached. I have a script called "cmd" for "cache-mail-dir". I had run it just before this, so everything was still cached when I started this: abra2:~> time cmd ; time cmd; sleep 120 ; time cmd; time cmd 0.080u 0.084s 0:00.24 66.6% 0+0k 0+0io 0pf+0w 0.072u 0.088s 0:00.23 65.2% 0+0k 0+0io 0pf+0w 0.096u 0.128s 0:30.52 0.6% 0+0k 229768+0io 0pf+0w 0.088u 0.076s 0:00.27 55.5% 0+0k 0+0io 0pf+0w abra2:~> The first two commands run in 0.25 seconds. Good. Then, wait for two minutes, and everything needs to come from teh disk again, taking half a minute. Run the command again, and you're back to 0.25 seconds The server claims to have 13G of memory "free", and this is still the case after weeks of uptime. The "reporting guidelines" tell me to run "ubuntu-bug linux" for kernel bugs, which then tells me that "linux is not an ubuntu package". ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic i686 ApportVersion: 2.14.1-0ubuntu2 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Apr 11 13:46:03 2014 HibernationDevice: RESUME=UUID=4aa126df-bbdf-4fd1-a333-9249ebffd271 InstallationDate: Installed on 2012-01-19 (812 days ago) InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=065abdd3-9e4d-4c45-a924-28b42317d6aa ro recovery nomodeset 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.13.0-19-generic N/A linux-backports-modules-3.13.0-19-generic N/A linux-firmware 1.127 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-03-27 (15 days ago) dmi.bios.date: 01/24/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0304 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-A/USB3 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd01/24/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH61M-A/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1306573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328767] 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/1328767 Title: Random PC freezes Status in “linux” package in Ubuntu: Confirmed Bug description: My computer randomly freezes once in a few days. I had the following observations 1. Mouse does not move. Keyboard does not respond. Ctrl+Alt+F1 does not switch to text-mode console. 2. Probability of freeze increases while playing video in a web browser. 3. Probability of freeze increases while running a VMWare virtual machine running Windows 8.1. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alex 3583 F pulseaudio /dev/snd/controlC0: alex 3583 F pulseaudio CurrentDesktop: GNOME Date: Wed Jun 11 07:06:12 2014 HibernationDevice: RESUME=UUID=7affd901-52f2-40a9-a3b2-3b97f7616c9f InstallationDate: Installed on 2014-03-27 (75 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326.1) MachineType: LENOVO 24382HU ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-29-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/25/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G5ET29WW (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 24382HU 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:bvrG5ET29WW(1.07):bd05/25/2012:svnLENOVO:pn24382HU:pvrThinkPadW530:rvnLENOVO:rn24382HU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 24382HU dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328767/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1306466] Re: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:31]
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1306466 Title: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:31] Status in “linux” package in Ubuntu: Expired Bug description: The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic i686 ApportVersion: 2.14.1-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 1509 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 11 10:29:14 2014 HibernationDevice: RESUME=UUID=9e3eed2b-ae9b-422e-b1ac-ca37a1397ba6 InstallationDate: Installed on 2014-04-09 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily i386 (20140407) MachineType: ASUSTeK Computer INC. 1001PX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=c5daf734-9931-4d53-a57e-448540669133 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1001PX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd02/18/2011:svnASUSTeKComputerINC.:pn1001PX:pvrx.x:rvnASUSTeKComputerINC.:rn1001PX:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1001PX dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1306466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1280848] Re: Everything gets swapped out after suspend-resume cycle
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1280848
Title:
Everything gets swapped out after suspend-resume cycle
Status in “linux” package in Ubuntu:
Expired
Bug description:
After resume from suspend to RAM, system is non-responsive with high
disk activity. Checking with 'top', system load is above 20, i/o wait
is 50-90%, and used swap space is constantly increasing. My conclusion
is that the kernel swaps out just about anything.
Disabling swap before suspend does not cause the same problem,
although system may be stale because of high disk activity anyway.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-58-generic 3.2.0-58.88
ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53
Uname: Linux 3.2.0-58-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stefan 2093 F pulseaudio
/dev/snd/controlC0: stefan 2093 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xe4524000 irq 47'
Mixer name : 'Analog Devices AD1981'
Components : 'HDA:11d41981,103c30c5,00100200
HDA:14f12c06,103c1379,0010'
Controls : 17
Simple ctrls : 12
Card1.Amixer.info:
Card hw:1 'HDMI'/'HDA ATI HDMI at 0xe441 irq 48'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,0010'
Controls : 6
Simple ctrls : 1
Card1.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Sun Feb 16 19:31:01 2014
HibernationDevice: RESUME=UUID=48ceb714-be12-4d28-b656-c5961917795d
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64
(20120823.1)
MachineType: Hewlett-Packard HP Compaq 8510p
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=sv_SE.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-58-generic
root=UUID=5794fa75-c358-467b-a2c0-c8d23890bba4 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-58-generic N/A
linux-backports-modules-3.2.0-58-generic N/A
linux-firmware1.79.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68MVD Ver. F.20
dmi.board.name: 30C5
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 71.36
dmi.chassis.asset.tag: CZC82909DP
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pnHPCompaq8510p:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq 8510p
dmi.product.version: F.20
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1280848/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1306524] Re: [Dell Inc. Latitude E6500] suspend/resume failure
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1306524 Title: [Dell Inc. Latitude E6500] suspend/resume failure Status in “linux” package in Ubuntu: Expired Bug description: i dont know it just happen when i boot the computer in the morning ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sabri 5389 F pulseaudio Date: Fri Apr 11 12:25:48 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2014-03-27 (15 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) InterpreterPath: /usr/bin/python3.4 MachineType: Dell Inc. Latitude E6500 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=82bd68ff-9399-4104-9e28-12be64267d36 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 SourcePackage: linux Title: [Dell Inc. Latitude E6500] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2014-04-01 (9 days ago) UserGroups: libvirtd dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A29 dmi.board.name: 0W610R dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA29:bd06/04/2013:svnDellInc.:pnLatitudeE6500:pvr:rvnDellInc.:rn0W610R:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E6500 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1306524/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1258996] Re: [MSI GE60] Black screen in live cd
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1258996 Title: [MSI GE60] Black screen in live cd Status in “linux” package in Ubuntu: Expired Bug description: On my MSI GE60 when I want to install in UEFI/Legacy linux I get a blackscreen. It is bug which works also on other distro like Debian etc. The only distro which works is arch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258996/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1306594] Re: BUG: soft lockup - CPU#3 stuck for 22s! [Xorg:1000]
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1306594 Title: BUG: soft lockup - CPU#3 stuck for 22s! [Xorg:1000] Status in “linux” package in Ubuntu: Expired Bug description: Dual head with NVIDIA GEFORCE 210 SERIES, POWEREDGE 840 ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 [modified: boot/vmlinuz-3.13.0-23-generic] ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 NonfreeKernelModules: nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: naldo 1319 F pulseaudio /dev/snd/controlC0: naldo 1319 F pulseaudio Date: Thu Apr 10 16:58:11 2014 DuplicateSignature: BUG: soft lockup - CPU#3 stuck for 22s! [Xorg:1000] RIP: 0010:location location ioread32+0x42/0x50 Failure: oops InstallationDate: Installed on 2014-04-10 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140410) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Dell Computer Corporation PowerEdge 840 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=84fc4f48-9d6a-41da-9b3d-f2d3050d1e57 ro quiet splash 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: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Title: BUG: soft lockup - CPU#3 stuck for 22s! [Xorg:1000] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2007 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A05 dmi.board.name: 0XM091 dmi.board.vendor: Dell Computer Corporation dmi.board.version: A01 dmi.chassis.type: 17 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA05:bd10/04/2007:svnDellComputerCorporation:pnPowerEdge840:pvr:rvnDellComputerCorporation:rn0XM091:rvrA01:cvnDellComputerCorporation:ct17:cvr: dmi.product.name: PowerEdge 840 dmi.sys.vendor: Dell Computer Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1306594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1306684] Re: [Micro-Star International Co., Ltd. GP60 2OD] suspend/resume failure
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1306684 Title: [Micro-Star International Co., Ltd. GP60 2OD] suspend/resume failure Status in “linux” package in Ubuntu: Expired Bug description: This error shows me every time I suspend / reboot ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lightdm1415 F pulseaudio donc3 2036 F pulseaudio /dev/snd/controlC0: lightdm1415 F pulseaudio donc3 2036 F pulseaudio Date: Fri Apr 11 17:25:02 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2014-03-29 (13 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) InterpreterPath: /usr/bin/python3.4 MachineType: Micro-Star International Co., Ltd. GP60 2OD ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=5cfd626f-8975-4fc0-979d-de474221df46 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 SourcePackage: linux Title: [Micro-Star International Co., Ltd. GP60 2OD] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16GDIMS.30G dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16GD dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: GP60 2OD dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16GDIMS.30G:bd01/18/2014:svnMicro-StarInternationalCo.,Ltd.:pnGP602OD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GD:rvrREV1.0:cvnGP602OD:ct10:cvrN/A: dmi.product.name: GP60 2OD dmi.product.version: REV: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/1306684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1306573] Re: The kernel seems to fail to cache disk blocks in some cases.
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1306573 Title: The kernel seems to fail to cache disk blocks in some cases. Status in “linux” package in Ubuntu: Expired Bug description: I have a server with 16G RAM. When running Ubuntu 10.04, it would cache my mail directory (with way too many messages: about 2), and starting mutt was quick unless the daily backup had been running. After upgrading to 14.04, I now notice that I have to wait much more often for the maildir to get cached. I have a script called "cmd" for "cache-mail-dir". I had run it just before this, so everything was still cached when I started this: abra2:~> time cmd ; time cmd; sleep 120 ; time cmd; time cmd 0.080u 0.084s 0:00.24 66.6% 0+0k 0+0io 0pf+0w 0.072u 0.088s 0:00.23 65.2% 0+0k 0+0io 0pf+0w 0.096u 0.128s 0:30.52 0.6% 0+0k 229768+0io 0pf+0w 0.088u 0.076s 0:00.27 55.5% 0+0k 0+0io 0pf+0w abra2:~> The first two commands run in 0.25 seconds. Good. Then, wait for two minutes, and everything needs to come from teh disk again, taking half a minute. Run the command again, and you're back to 0.25 seconds The server claims to have 13G of memory "free", and this is still the case after weeks of uptime. The "reporting guidelines" tell me to run "ubuntu-bug linux" for kernel bugs, which then tells me that "linux is not an ubuntu package". ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic i686 ApportVersion: 2.14.1-0ubuntu2 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Apr 11 13:46:03 2014 HibernationDevice: RESUME=UUID=4aa126df-bbdf-4fd1-a333-9249ebffd271 InstallationDate: Installed on 2012-01-19 (812 days ago) InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=065abdd3-9e4d-4c45-a924-28b42317d6aa ro recovery nomodeset 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.13.0-19-generic N/A linux-backports-modules-3.13.0-19-generic N/A linux-firmware 1.127 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-03-27 (15 days ago) dmi.bios.date: 01/24/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0304 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-A/USB3 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd01/24/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH61M-A/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1306573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328767] [NEW] Random PC freezes
Public bug reported: My computer randomly freezes once in a few days. I had the following observations 1. Mouse does not move. Keyboard does not respond. Ctrl+Alt+F1 does not switch to text-mode console. 2. Probability of freeze increases while playing video in a web browser. 3. Probability of freeze increases while running a VMWare virtual machine running Windows 8.1. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alex 3583 F pulseaudio /dev/snd/controlC0: alex 3583 F pulseaudio CurrentDesktop: GNOME Date: Wed Jun 11 07:06:12 2014 HibernationDevice: RESUME=UUID=7affd901-52f2-40a9-a3b2-3b97f7616c9f InstallationDate: Installed on 2014-03-27 (75 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326.1) MachineType: LENOVO 24382HU ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-29-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/25/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G5ET29WW (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 24382HU 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:bvrG5ET29WW(1.07):bd05/25/2012:svnLENOVO:pn24382HU:pvrThinkPadW530:rvnLENOVO:rn24382HU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 24382HU dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1328767 Title: Random PC freezes Status in “linux” package in Ubuntu: New Bug description: My computer randomly freezes once in a few days. I had the following observations 1. Mouse does not move. Keyboard does not respond. Ctrl+Alt+F1 does not switch to text-mode console. 2. Probability of freeze increases while playing video in a web browser. 3. Probability of freeze increases while running a VMWare virtual machine running Windows 8.1. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alex 3583 F pulseaudio /dev/snd/controlC0: alex 3583 F pulseaudio CurrentDesktop: GNOME Date: Wed Jun 11 07:06:12 2014 HibernationDevice: RESUME=UUID=7affd901-52f2-40a9-a3b2-3b97f7616c9f InstallationDate: Installed on 2014-03-27 (75 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326.1) MachineType: LENOVO 24382HU ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-29-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/25/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G5ET29WW (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 24382HU 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:bvrG5ET29WW(1.07):bd05/25/2012:svnLENOVO:pn24382HU:pvrThinkPadW530:rvnLENOVO:rn24382HU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 24382HU dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328767/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328746] Re: Soundblaster Audigy front panel MIDI fails to initialize
Please note that the entire apport information is irrelevant in this
context.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1328746
Title:
Soundblaster Audigy front panel MIDI fails to initialize
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
This bug has been around for a while. I have seen it in the forums
circa 2007, and I have provided a solution in 2009. Since the modified
code never found its way into the mainstream kernels, I am issuing the
fix as a bug report.
The bug concerns the Soundblaster Audigy cards with the emu10k1 chip
in both i386 and amd64 architectures, in any kernel (standard, RT
etc). They have on-board joystick MIDI. There is an optional front-
panel module, which provides its own MIDI UART. Under Linux, the front
MIDI does not work. People with dual-boot systems have reported that
booting Windows first, then rebooting into Linux makes the UART
function properly.
The cause for the bug lies in the fact that the front panel MIDI is
routed through a microcontroller (resides in the front panel module),
and this microcontroller needs a defined reset signal once after
power-up. Up to this point, the GPIO _levels_ are initialized
correctly, but the reset _pulse_ is never issued. Essentially, the
emu10k1 chip's GPIO2 needs to be pulled high for a brief interval.
The bug can be fixed in the file linux-
source-3.13.0/sound/pci/emu10k1/emumpu401.c in the function
snd_emu10k1_audigy_midi(). The proposed patch follows right after the
present initialization of the second UART (note the added variable
"val" to store the GPIO bits):
int snd_emu10k1_audigy_midi(struct snd_emu10k1 *emu)
{
struct snd_emu10k1_midi *midi;
int err;
unsigned int val;/* Needed in GPOUT2 pulse initialization */
midi = &emu->midi;
if ((err = emu10k1_midi_init(emu, midi, 0, "Audigy MPU-401 (UART)")) < 0)
return err;
midi->tx_enable = INTE_MIDITXENABLE;
midi->rx_enable = INTE_MIDIRXENABLE;
midi->port = A_MUDATA1;
midi->ipr_tx = IPR_MIDITRANSBUFEMPTY;
midi->ipr_rx = IPR_MIDIRECVBUFEMPTY;
midi->interrupt = snd_emu10k1_midi_interrupt;
midi = &emu->midi2;
if ((err = emu10k1_midi_init(emu, midi, 1, "Audigy MPU-401 #2")) < 0)
return err;
midi->tx_enable = INTE_A_MIDITXENABLE2;
midi->rx_enable = INTE_A_MIDIRXENABLE2;
midi->port = A_MUDATA2;
midi->ipr_tx = IPR_A_MIDITRANSBUFEMPTY2;
midi->ipr_rx = IPR_A_MIDIRECVBUFEMPTY2;
midi->interrupt = snd_emu10k1_midi_interrupt2;
/*** NEW CODE *** Pulse reset line for the second UART */
val = inl(emu->port + A_IOCFG);
outl (val | A_IOCFG_GPOUT2, emu->port + A_IOCFG);
udelay(10); /* udelay is a bad kludge, but remember that this is
called only once on startup */
outl (val, emu->port + A_IOCFG);
return 0;
}
I suspect that my use of udelay would make a real kernel hacker
cringe, but the level of GPOUT2 needs to remain high for a few
microseconds to provide a stable RESET signal.
Anyway, this fixes the problem. I have applied the patch for pretty much
every major upgrade of the kernel. It is sufficient to compile the module
snd-emu10k1.ko and replace it in the module tree.
---
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: mhaidekk 2321 F pulseaudio
/dev/snd/controlC1: mhaidekk 2321 F pulseaudio
/dev/snd/controlC0: mhaidekk 2321 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
CurrentDesktop: KDE
DistroRelease: Ubuntu 14.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=b15a827a-7aa7-4add-a9b4-cb68262cfddd
InstallationDate: Installed on 2013-12-31 (161 days ago)
InstallationMedia: Kubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130822)
IwConfig:
eth1 no wireless extensions.
lono wireless extensions.
MachineType: BIOSTAR Group TA970
NonfreeKernelModules: fglrx
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic
root=UUID=11a18cc0-0c2e-4ce8-9acd-44c5bb8820e2 ro
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
RelatedPackageVersions:
linux-restricted-modules-3.13.0-29-generic N/A
linux-backports-modules-3.13.0-29-generic N/A
linux-firmware 1.127.2
RfKill:
Tags: trusty
Uname: Linux 3.13.0-29-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-06-07 (3 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/14/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: None
dmi.board.name: TA970
dmi.board.vendor:
[Kernel-packages] [Bug 1328746] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1328746/+attachment/4129350/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1328746
Title:
Soundblaster Audigy front panel MIDI fails to initialize
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
This bug has been around for a while. I have seen it in the forums
circa 2007, and I have provided a solution in 2009. Since the modified
code never found its way into the mainstream kernels, I am issuing the
fix as a bug report.
The bug concerns the Soundblaster Audigy cards with the emu10k1 chip
in both i386 and amd64 architectures, in any kernel (standard, RT
etc). They have on-board joystick MIDI. There is an optional front-
panel module, which provides its own MIDI UART. Under Linux, the front
MIDI does not work. People with dual-boot systems have reported that
booting Windows first, then rebooting into Linux makes the UART
function properly.
The cause for the bug lies in the fact that the front panel MIDI is
routed through a microcontroller (resides in the front panel module),
and this microcontroller needs a defined reset signal once after
power-up. Up to this point, the GPIO _levels_ are initialized
correctly, but the reset _pulse_ is never issued. Essentially, the
emu10k1 chip's GPIO2 needs to be pulled high for a brief interval.
The bug can be fixed in the file linux-
source-3.13.0/sound/pci/emu10k1/emumpu401.c in the function
snd_emu10k1_audigy_midi(). The proposed patch follows right after the
present initialization of the second UART (note the added variable
"val" to store the GPIO bits):
int snd_emu10k1_audigy_midi(struct snd_emu10k1 *emu)
{
struct snd_emu10k1_midi *midi;
int err;
unsigned int val;/* Needed in GPOUT2 pulse initialization */
midi = &emu->midi;
if ((err = emu10k1_midi_init(emu, midi, 0, "Audigy MPU-401 (UART)")) < 0)
return err;
midi->tx_enable = INTE_MIDITXENABLE;
midi->rx_enable = INTE_MIDIRXENABLE;
midi->port = A_MUDATA1;
midi->ipr_tx = IPR_MIDITRANSBUFEMPTY;
midi->ipr_rx = IPR_MIDIRECVBUFEMPTY;
midi->interrupt = snd_emu10k1_midi_interrupt;
midi = &emu->midi2;
if ((err = emu10k1_midi_init(emu, midi, 1, "Audigy MPU-401 #2")) < 0)
return err;
midi->tx_enable = INTE_A_MIDITXENABLE2;
midi->rx_enable = INTE_A_MIDIRXENABLE2;
midi->port = A_MUDATA2;
midi->ipr_tx = IPR_A_MIDITRANSBUFEMPTY2;
midi->ipr_rx = IPR_A_MIDIRECVBUFEMPTY2;
midi->interrupt = snd_emu10k1_midi_interrupt2;
/*** NEW CODE *** Pulse reset line for the second UART */
val = inl(emu->port + A_IOCFG);
outl (val | A_IOCFG_GPOUT2, emu->port + A_IOCFG);
udelay(10); /* udelay is a bad kludge, but remember that this is
called only once on startup */
outl (val, emu->port + A_IOCFG);
return 0;
}
I suspect that my use of udelay would make a real kernel hacker
cringe, but the level of GPOUT2 needs to remain high for a few
microseconds to provide a stable RESET signal.
Anyway, this fixes the problem. I have applied the patch for pretty much
every major upgrade of the kernel. It is sufficient to compile the module
snd-emu10k1.ko and replace it in the module tree.
---
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: mhaidekk 2321 F pulseaudio
/dev/snd/controlC1: mhaidekk 2321 F pulseaudio
/dev/snd/controlC0: mhaidekk 2321 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
CurrentDesktop: KDE
DistroRelease: Ubuntu 14.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=b15a827a-7aa7-4add-a9b4-cb68262cfddd
InstallationDate: Installed on 2013-12-31 (161 days ago)
InstallationMedia: Kubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130822)
IwConfig:
eth1 no wireless extensions.
lono wireless extensions.
MachineType: BIOSTAR Group TA970
NonfreeKernelModules: fglrx
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic
root=UUID=11a18cc0-0c2e-4ce8-9acd-44c5bb8820e2 ro
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
RelatedPackageVersions:
linux-restricted-modules-3.13.0-29-generic N/A
linux-backports-modules-3.13.0-29-generic N/A
linux-firmware 1.127.2
RfKill:
Tags: trusty
Uname: Linux 3.13.0-29-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-06-07 (3 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/14/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: None
dmi.board.name: TA970
dmi.board.vend
[Kernel-packages] [Bug 1328746] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1328746/+attachment/4129355/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1328746
Title:
Soundblaster Audigy front panel MIDI fails to initialize
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
This bug has been around for a while. I have seen it in the forums
circa 2007, and I have provided a solution in 2009. Since the modified
code never found its way into the mainstream kernels, I am issuing the
fix as a bug report.
The bug concerns the Soundblaster Audigy cards with the emu10k1 chip
in both i386 and amd64 architectures, in any kernel (standard, RT
etc). They have on-board joystick MIDI. There is an optional front-
panel module, which provides its own MIDI UART. Under Linux, the front
MIDI does not work. People with dual-boot systems have reported that
booting Windows first, then rebooting into Linux makes the UART
function properly.
The cause for the bug lies in the fact that the front panel MIDI is
routed through a microcontroller (resides in the front panel module),
and this microcontroller needs a defined reset signal once after
power-up. Up to this point, the GPIO _levels_ are initialized
correctly, but the reset _pulse_ is never issued. Essentially, the
emu10k1 chip's GPIO2 needs to be pulled high for a brief interval.
The bug can be fixed in the file linux-
source-3.13.0/sound/pci/emu10k1/emumpu401.c in the function
snd_emu10k1_audigy_midi(). The proposed patch follows right after the
present initialization of the second UART (note the added variable
"val" to store the GPIO bits):
int snd_emu10k1_audigy_midi(struct snd_emu10k1 *emu)
{
struct snd_emu10k1_midi *midi;
int err;
unsigned int val;/* Needed in GPOUT2 pulse initialization */
midi = &emu->midi;
if ((err = emu10k1_midi_init(emu, midi, 0, "Audigy MPU-401 (UART)")) < 0)
return err;
midi->tx_enable = INTE_MIDITXENABLE;
midi->rx_enable = INTE_MIDIRXENABLE;
midi->port = A_MUDATA1;
midi->ipr_tx = IPR_MIDITRANSBUFEMPTY;
midi->ipr_rx = IPR_MIDIRECVBUFEMPTY;
midi->interrupt = snd_emu10k1_midi_interrupt;
midi = &emu->midi2;
if ((err = emu10k1_midi_init(emu, midi, 1, "Audigy MPU-401 #2")) < 0)
return err;
midi->tx_enable = INTE_A_MIDITXENABLE2;
midi->rx_enable = INTE_A_MIDIRXENABLE2;
midi->port = A_MUDATA2;
midi->ipr_tx = IPR_A_MIDITRANSBUFEMPTY2;
midi->ipr_rx = IPR_A_MIDIRECVBUFEMPTY2;
midi->interrupt = snd_emu10k1_midi_interrupt2;
/*** NEW CODE *** Pulse reset line for the second UART */
val = inl(emu->port + A_IOCFG);
outl (val | A_IOCFG_GPOUT2, emu->port + A_IOCFG);
udelay(10); /* udelay is a bad kludge, but remember that this is
called only once on startup */
outl (val, emu->port + A_IOCFG);
return 0;
}
I suspect that my use of udelay would make a real kernel hacker
cringe, but the level of GPOUT2 needs to remain high for a few
microseconds to provide a stable RESET signal.
Anyway, this fixes the problem. I have applied the patch for pretty much
every major upgrade of the kernel. It is sufficient to compile the module
snd-emu10k1.ko and replace it in the module tree.
---
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: mhaidekk 2321 F pulseaudio
/dev/snd/controlC1: mhaidekk 2321 F pulseaudio
/dev/snd/controlC0: mhaidekk 2321 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
CurrentDesktop: KDE
DistroRelease: Ubuntu 14.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=b15a827a-7aa7-4add-a9b4-cb68262cfddd
InstallationDate: Installed on 2013-12-31 (161 days ago)
InstallationMedia: Kubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130822)
IwConfig:
eth1 no wireless extensions.
lono wireless extensions.
MachineType: BIOSTAR Group TA970
NonfreeKernelModules: fglrx
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic
root=UUID=11a18cc0-0c2e-4ce8-9acd-44c5bb8820e2 ro
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
RelatedPackageVersions:
linux-restricted-modules-3.13.0-29-generic N/A
linux-backports-modules-3.13.0-29-generic N/A
linux-firmware 1.127.2
RfKill:
Tags: trusty
Uname: Linux 3.13.0-29-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-06-07 (3 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/14/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: None
dmi.board.name: TA970
dmi.board.vendor: BIOS
[Kernel-packages] [Bug 1328746] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1328746/+attachment/4129353/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1328746
Title:
Soundblaster Audigy front panel MIDI fails to initialize
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
This bug has been around for a while. I have seen it in the forums
circa 2007, and I have provided a solution in 2009. Since the modified
code never found its way into the mainstream kernels, I am issuing the
fix as a bug report.
The bug concerns the Soundblaster Audigy cards with the emu10k1 chip
in both i386 and amd64 architectures, in any kernel (standard, RT
etc). They have on-board joystick MIDI. There is an optional front-
panel module, which provides its own MIDI UART. Under Linux, the front
MIDI does not work. People with dual-boot systems have reported that
booting Windows first, then rebooting into Linux makes the UART
function properly.
The cause for the bug lies in the fact that the front panel MIDI is
routed through a microcontroller (resides in the front panel module),
and this microcontroller needs a defined reset signal once after
power-up. Up to this point, the GPIO _levels_ are initialized
correctly, but the reset _pulse_ is never issued. Essentially, the
emu10k1 chip's GPIO2 needs to be pulled high for a brief interval.
The bug can be fixed in the file linux-
source-3.13.0/sound/pci/emu10k1/emumpu401.c in the function
snd_emu10k1_audigy_midi(). The proposed patch follows right after the
present initialization of the second UART (note the added variable
"val" to store the GPIO bits):
int snd_emu10k1_audigy_midi(struct snd_emu10k1 *emu)
{
struct snd_emu10k1_midi *midi;
int err;
unsigned int val;/* Needed in GPOUT2 pulse initialization */
midi = &emu->midi;
if ((err = emu10k1_midi_init(emu, midi, 0, "Audigy MPU-401 (UART)")) < 0)
return err;
midi->tx_enable = INTE_MIDITXENABLE;
midi->rx_enable = INTE_MIDIRXENABLE;
midi->port = A_MUDATA1;
midi->ipr_tx = IPR_MIDITRANSBUFEMPTY;
midi->ipr_rx = IPR_MIDIRECVBUFEMPTY;
midi->interrupt = snd_emu10k1_midi_interrupt;
midi = &emu->midi2;
if ((err = emu10k1_midi_init(emu, midi, 1, "Audigy MPU-401 #2")) < 0)
return err;
midi->tx_enable = INTE_A_MIDITXENABLE2;
midi->rx_enable = INTE_A_MIDIRXENABLE2;
midi->port = A_MUDATA2;
midi->ipr_tx = IPR_A_MIDITRANSBUFEMPTY2;
midi->ipr_rx = IPR_A_MIDIRECVBUFEMPTY2;
midi->interrupt = snd_emu10k1_midi_interrupt2;
/*** NEW CODE *** Pulse reset line for the second UART */
val = inl(emu->port + A_IOCFG);
outl (val | A_IOCFG_GPOUT2, emu->port + A_IOCFG);
udelay(10); /* udelay is a bad kludge, but remember that this is
called only once on startup */
outl (val, emu->port + A_IOCFG);
return 0;
}
I suspect that my use of udelay would make a real kernel hacker
cringe, but the level of GPOUT2 needs to remain high for a few
microseconds to provide a stable RESET signal.
Anyway, this fixes the problem. I have applied the patch for pretty much
every major upgrade of the kernel. It is sufficient to compile the module
snd-emu10k1.ko and replace it in the module tree.
---
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: mhaidekk 2321 F pulseaudio
/dev/snd/controlC1: mhaidekk 2321 F pulseaudio
/dev/snd/controlC0: mhaidekk 2321 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
CurrentDesktop: KDE
DistroRelease: Ubuntu 14.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=b15a827a-7aa7-4add-a9b4-cb68262cfddd
InstallationDate: Installed on 2013-12-31 (161 days ago)
InstallationMedia: Kubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130822)
IwConfig:
eth1 no wireless extensions.
lono wireless extensions.
MachineType: BIOSTAR Group TA970
NonfreeKernelModules: fglrx
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic
root=UUID=11a18cc0-0c2e-4ce8-9acd-44c5bb8820e2 ro
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
RelatedPackageVersions:
linux-restricted-modules-3.13.0-29-generic N/A
linux-backports-modules-3.13.0-29-generic N/A
linux-firmware 1.127.2
RfKill:
Tags: trusty
Uname: Linux 3.13.0-29-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-06-07 (3 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/14/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: None
dmi.board.name: TA970
dmi.board.vendor: BIOSTAR Group
[Kernel-packages] [Bug 1328746] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1328746/+attachment/4129349/+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/1328746
Title:
Soundblaster Audigy front panel MIDI fails to initialize
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
This bug has been around for a while. I have seen it in the forums
circa 2007, and I have provided a solution in 2009. Since the modified
code never found its way into the mainstream kernels, I am issuing the
fix as a bug report.
The bug concerns the Soundblaster Audigy cards with the emu10k1 chip
in both i386 and amd64 architectures, in any kernel (standard, RT
etc). They have on-board joystick MIDI. There is an optional front-
panel module, which provides its own MIDI UART. Under Linux, the front
MIDI does not work. People with dual-boot systems have reported that
booting Windows first, then rebooting into Linux makes the UART
function properly.
The cause for the bug lies in the fact that the front panel MIDI is
routed through a microcontroller (resides in the front panel module),
and this microcontroller needs a defined reset signal once after
power-up. Up to this point, the GPIO _levels_ are initialized
correctly, but the reset _pulse_ is never issued. Essentially, the
emu10k1 chip's GPIO2 needs to be pulled high for a brief interval.
The bug can be fixed in the file linux-
source-3.13.0/sound/pci/emu10k1/emumpu401.c in the function
snd_emu10k1_audigy_midi(). The proposed patch follows right after the
present initialization of the second UART (note the added variable
"val" to store the GPIO bits):
int snd_emu10k1_audigy_midi(struct snd_emu10k1 *emu)
{
struct snd_emu10k1_midi *midi;
int err;
unsigned int val;/* Needed in GPOUT2 pulse initialization */
midi = &emu->midi;
if ((err = emu10k1_midi_init(emu, midi, 0, "Audigy MPU-401 (UART)")) < 0)
return err;
midi->tx_enable = INTE_MIDITXENABLE;
midi->rx_enable = INTE_MIDIRXENABLE;
midi->port = A_MUDATA1;
midi->ipr_tx = IPR_MIDITRANSBUFEMPTY;
midi->ipr_rx = IPR_MIDIRECVBUFEMPTY;
midi->interrupt = snd_emu10k1_midi_interrupt;
midi = &emu->midi2;
if ((err = emu10k1_midi_init(emu, midi, 1, "Audigy MPU-401 #2")) < 0)
return err;
midi->tx_enable = INTE_A_MIDITXENABLE2;
midi->rx_enable = INTE_A_MIDIRXENABLE2;
midi->port = A_MUDATA2;
midi->ipr_tx = IPR_A_MIDITRANSBUFEMPTY2;
midi->ipr_rx = IPR_A_MIDIRECVBUFEMPTY2;
midi->interrupt = snd_emu10k1_midi_interrupt2;
/*** NEW CODE *** Pulse reset line for the second UART */
val = inl(emu->port + A_IOCFG);
outl (val | A_IOCFG_GPOUT2, emu->port + A_IOCFG);
udelay(10); /* udelay is a bad kludge, but remember that this is
called only once on startup */
outl (val, emu->port + A_IOCFG);
return 0;
}
I suspect that my use of udelay would make a real kernel hacker
cringe, but the level of GPOUT2 needs to remain high for a few
microseconds to provide a stable RESET signal.
Anyway, this fixes the problem. I have applied the patch for pretty much
every major upgrade of the kernel. It is sufficient to compile the module
snd-emu10k1.ko and replace it in the module tree.
---
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: mhaidekk 2321 F pulseaudio
/dev/snd/controlC1: mhaidekk 2321 F pulseaudio
/dev/snd/controlC0: mhaidekk 2321 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
CurrentDesktop: KDE
DistroRelease: Ubuntu 14.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=b15a827a-7aa7-4add-a9b4-cb68262cfddd
InstallationDate: Installed on 2013-12-31 (161 days ago)
InstallationMedia: Kubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130822)
IwConfig:
eth1 no wireless extensions.
lono wireless extensions.
MachineType: BIOSTAR Group TA970
NonfreeKernelModules: fglrx
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic
root=UUID=11a18cc0-0c2e-4ce8-9acd-44c5bb8820e2 ro
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
RelatedPackageVersions:
linux-restricted-modules-3.13.0-29-generic N/A
linux-backports-modules-3.13.0-29-generic N/A
linux-firmware 1.127.2
RfKill:
Tags: trusty
Uname: Linux 3.13.0-29-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-06-07 (3 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/14/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: None
dmi.board.name: TA970
dmi.board.vendor: BI
[Kernel-packages] [Bug 1328746] UdevLog.txt
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1328746/+attachment/4129354/+files/UdevLog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1328746
Title:
Soundblaster Audigy front panel MIDI fails to initialize
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
This bug has been around for a while. I have seen it in the forums
circa 2007, and I have provided a solution in 2009. Since the modified
code never found its way into the mainstream kernels, I am issuing the
fix as a bug report.
The bug concerns the Soundblaster Audigy cards with the emu10k1 chip
in both i386 and amd64 architectures, in any kernel (standard, RT
etc). They have on-board joystick MIDI. There is an optional front-
panel module, which provides its own MIDI UART. Under Linux, the front
MIDI does not work. People with dual-boot systems have reported that
booting Windows first, then rebooting into Linux makes the UART
function properly.
The cause for the bug lies in the fact that the front panel MIDI is
routed through a microcontroller (resides in the front panel module),
and this microcontroller needs a defined reset signal once after
power-up. Up to this point, the GPIO _levels_ are initialized
correctly, but the reset _pulse_ is never issued. Essentially, the
emu10k1 chip's GPIO2 needs to be pulled high for a brief interval.
The bug can be fixed in the file linux-
source-3.13.0/sound/pci/emu10k1/emumpu401.c in the function
snd_emu10k1_audigy_midi(). The proposed patch follows right after the
present initialization of the second UART (note the added variable
"val" to store the GPIO bits):
int snd_emu10k1_audigy_midi(struct snd_emu10k1 *emu)
{
struct snd_emu10k1_midi *midi;
int err;
unsigned int val;/* Needed in GPOUT2 pulse initialization */
midi = &emu->midi;
if ((err = emu10k1_midi_init(emu, midi, 0, "Audigy MPU-401 (UART)")) < 0)
return err;
midi->tx_enable = INTE_MIDITXENABLE;
midi->rx_enable = INTE_MIDIRXENABLE;
midi->port = A_MUDATA1;
midi->ipr_tx = IPR_MIDITRANSBUFEMPTY;
midi->ipr_rx = IPR_MIDIRECVBUFEMPTY;
midi->interrupt = snd_emu10k1_midi_interrupt;
midi = &emu->midi2;
if ((err = emu10k1_midi_init(emu, midi, 1, "Audigy MPU-401 #2")) < 0)
return err;
midi->tx_enable = INTE_A_MIDITXENABLE2;
midi->rx_enable = INTE_A_MIDIRXENABLE2;
midi->port = A_MUDATA2;
midi->ipr_tx = IPR_A_MIDITRANSBUFEMPTY2;
midi->ipr_rx = IPR_A_MIDIRECVBUFEMPTY2;
midi->interrupt = snd_emu10k1_midi_interrupt2;
/*** NEW CODE *** Pulse reset line for the second UART */
val = inl(emu->port + A_IOCFG);
outl (val | A_IOCFG_GPOUT2, emu->port + A_IOCFG);
udelay(10); /* udelay is a bad kludge, but remember that this is
called only once on startup */
outl (val, emu->port + A_IOCFG);
return 0;
}
I suspect that my use of udelay would make a real kernel hacker
cringe, but the level of GPOUT2 needs to remain high for a few
microseconds to provide a stable RESET signal.
Anyway, this fixes the problem. I have applied the patch for pretty much
every major upgrade of the kernel. It is sufficient to compile the module
snd-emu10k1.ko and replace it in the module tree.
---
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: mhaidekk 2321 F pulseaudio
/dev/snd/controlC1: mhaidekk 2321 F pulseaudio
/dev/snd/controlC0: mhaidekk 2321 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
CurrentDesktop: KDE
DistroRelease: Ubuntu 14.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=b15a827a-7aa7-4add-a9b4-cb68262cfddd
InstallationDate: Installed on 2013-12-31 (161 days ago)
InstallationMedia: Kubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130822)
IwConfig:
eth1 no wireless extensions.
lono wireless extensions.
MachineType: BIOSTAR Group TA970
NonfreeKernelModules: fglrx
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic
root=UUID=11a18cc0-0c2e-4ce8-9acd-44c5bb8820e2 ro
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
RelatedPackageVersions:
linux-restricted-modules-3.13.0-29-generic N/A
linux-backports-modules-3.13.0-29-generic N/A
linux-firmware 1.127.2
RfKill:
Tags: trusty
Uname: Linux 3.13.0-29-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-06-07 (3 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/14/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: None
dmi.board.name: TA970
dmi.board.vendor: BIOSTAR Gr
[Kernel-packages] [Bug 1328746] PulseList.txt
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1328746/+attachment/4129352/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1328746
Title:
Soundblaster Audigy front panel MIDI fails to initialize
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
This bug has been around for a while. I have seen it in the forums
circa 2007, and I have provided a solution in 2009. Since the modified
code never found its way into the mainstream kernels, I am issuing the
fix as a bug report.
The bug concerns the Soundblaster Audigy cards with the emu10k1 chip
in both i386 and amd64 architectures, in any kernel (standard, RT
etc). They have on-board joystick MIDI. There is an optional front-
panel module, which provides its own MIDI UART. Under Linux, the front
MIDI does not work. People with dual-boot systems have reported that
booting Windows first, then rebooting into Linux makes the UART
function properly.
The cause for the bug lies in the fact that the front panel MIDI is
routed through a microcontroller (resides in the front panel module),
and this microcontroller needs a defined reset signal once after
power-up. Up to this point, the GPIO _levels_ are initialized
correctly, but the reset _pulse_ is never issued. Essentially, the
emu10k1 chip's GPIO2 needs to be pulled high for a brief interval.
The bug can be fixed in the file linux-
source-3.13.0/sound/pci/emu10k1/emumpu401.c in the function
snd_emu10k1_audigy_midi(). The proposed patch follows right after the
present initialization of the second UART (note the added variable
"val" to store the GPIO bits):
int snd_emu10k1_audigy_midi(struct snd_emu10k1 *emu)
{
struct snd_emu10k1_midi *midi;
int err;
unsigned int val;/* Needed in GPOUT2 pulse initialization */
midi = &emu->midi;
if ((err = emu10k1_midi_init(emu, midi, 0, "Audigy MPU-401 (UART)")) < 0)
return err;
midi->tx_enable = INTE_MIDITXENABLE;
midi->rx_enable = INTE_MIDIRXENABLE;
midi->port = A_MUDATA1;
midi->ipr_tx = IPR_MIDITRANSBUFEMPTY;
midi->ipr_rx = IPR_MIDIRECVBUFEMPTY;
midi->interrupt = snd_emu10k1_midi_interrupt;
midi = &emu->midi2;
if ((err = emu10k1_midi_init(emu, midi, 1, "Audigy MPU-401 #2")) < 0)
return err;
midi->tx_enable = INTE_A_MIDITXENABLE2;
midi->rx_enable = INTE_A_MIDIRXENABLE2;
midi->port = A_MUDATA2;
midi->ipr_tx = IPR_A_MIDITRANSBUFEMPTY2;
midi->ipr_rx = IPR_A_MIDIRECVBUFEMPTY2;
midi->interrupt = snd_emu10k1_midi_interrupt2;
/*** NEW CODE *** Pulse reset line for the second UART */
val = inl(emu->port + A_IOCFG);
outl (val | A_IOCFG_GPOUT2, emu->port + A_IOCFG);
udelay(10); /* udelay is a bad kludge, but remember that this is
called only once on startup */
outl (val, emu->port + A_IOCFG);
return 0;
}
I suspect that my use of udelay would make a real kernel hacker
cringe, but the level of GPOUT2 needs to remain high for a few
microseconds to provide a stable RESET signal.
Anyway, this fixes the problem. I have applied the patch for pretty much
every major upgrade of the kernel. It is sufficient to compile the module
snd-emu10k1.ko and replace it in the module tree.
---
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: mhaidekk 2321 F pulseaudio
/dev/snd/controlC1: mhaidekk 2321 F pulseaudio
/dev/snd/controlC0: mhaidekk 2321 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
CurrentDesktop: KDE
DistroRelease: Ubuntu 14.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=b15a827a-7aa7-4add-a9b4-cb68262cfddd
InstallationDate: Installed on 2013-12-31 (161 days ago)
InstallationMedia: Kubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130822)
IwConfig:
eth1 no wireless extensions.
lono wireless extensions.
MachineType: BIOSTAR Group TA970
NonfreeKernelModules: fglrx
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic
root=UUID=11a18cc0-0c2e-4ce8-9acd-44c5bb8820e2 ro
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
RelatedPackageVersions:
linux-restricted-modules-3.13.0-29-generic N/A
linux-backports-modules-3.13.0-29-generic N/A
linux-firmware 1.127.2
RfKill:
Tags: trusty
Uname: Linux 3.13.0-29-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-06-07 (3 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/14/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: None
dmi.board.name: TA970
dmi.board.vendor: BIOSTA
[Kernel-packages] [Bug 1328746] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1328746/+attachment/4129351/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1328746
Title:
Soundblaster Audigy front panel MIDI fails to initialize
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
This bug has been around for a while. I have seen it in the forums
circa 2007, and I have provided a solution in 2009. Since the modified
code never found its way into the mainstream kernels, I am issuing the
fix as a bug report.
The bug concerns the Soundblaster Audigy cards with the emu10k1 chip
in both i386 and amd64 architectures, in any kernel (standard, RT
etc). They have on-board joystick MIDI. There is an optional front-
panel module, which provides its own MIDI UART. Under Linux, the front
MIDI does not work. People with dual-boot systems have reported that
booting Windows first, then rebooting into Linux makes the UART
function properly.
The cause for the bug lies in the fact that the front panel MIDI is
routed through a microcontroller (resides in the front panel module),
and this microcontroller needs a defined reset signal once after
power-up. Up to this point, the GPIO _levels_ are initialized
correctly, but the reset _pulse_ is never issued. Essentially, the
emu10k1 chip's GPIO2 needs to be pulled high for a brief interval.
The bug can be fixed in the file linux-
source-3.13.0/sound/pci/emu10k1/emumpu401.c in the function
snd_emu10k1_audigy_midi(). The proposed patch follows right after the
present initialization of the second UART (note the added variable
"val" to store the GPIO bits):
int snd_emu10k1_audigy_midi(struct snd_emu10k1 *emu)
{
struct snd_emu10k1_midi *midi;
int err;
unsigned int val;/* Needed in GPOUT2 pulse initialization */
midi = &emu->midi;
if ((err = emu10k1_midi_init(emu, midi, 0, "Audigy MPU-401 (UART)")) < 0)
return err;
midi->tx_enable = INTE_MIDITXENABLE;
midi->rx_enable = INTE_MIDIRXENABLE;
midi->port = A_MUDATA1;
midi->ipr_tx = IPR_MIDITRANSBUFEMPTY;
midi->ipr_rx = IPR_MIDIRECVBUFEMPTY;
midi->interrupt = snd_emu10k1_midi_interrupt;
midi = &emu->midi2;
if ((err = emu10k1_midi_init(emu, midi, 1, "Audigy MPU-401 #2")) < 0)
return err;
midi->tx_enable = INTE_A_MIDITXENABLE2;
midi->rx_enable = INTE_A_MIDIRXENABLE2;
midi->port = A_MUDATA2;
midi->ipr_tx = IPR_A_MIDITRANSBUFEMPTY2;
midi->ipr_rx = IPR_A_MIDIRECVBUFEMPTY2;
midi->interrupt = snd_emu10k1_midi_interrupt2;
/*** NEW CODE *** Pulse reset line for the second UART */
val = inl(emu->port + A_IOCFG);
outl (val | A_IOCFG_GPOUT2, emu->port + A_IOCFG);
udelay(10); /* udelay is a bad kludge, but remember that this is
called only once on startup */
outl (val, emu->port + A_IOCFG);
return 0;
}
I suspect that my use of udelay would make a real kernel hacker
cringe, but the level of GPOUT2 needs to remain high for a few
microseconds to provide a stable RESET signal.
Anyway, this fixes the problem. I have applied the patch for pretty much
every major upgrade of the kernel. It is sufficient to compile the module
snd-emu10k1.ko and replace it in the module tree.
---
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: mhaidekk 2321 F pulseaudio
/dev/snd/controlC1: mhaidekk 2321 F pulseaudio
/dev/snd/controlC0: mhaidekk 2321 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
CurrentDesktop: KDE
DistroRelease: Ubuntu 14.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=b15a827a-7aa7-4add-a9b4-cb68262cfddd
InstallationDate: Installed on 2013-12-31 (161 days ago)
InstallationMedia: Kubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130822)
IwConfig:
eth1 no wireless extensions.
lono wireless extensions.
MachineType: BIOSTAR Group TA970
NonfreeKernelModules: fglrx
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic
root=UUID=11a18cc0-0c2e-4ce8-9acd-44c5bb8820e2 ro
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
RelatedPackageVersions:
linux-restricted-modules-3.13.0-29-generic N/A
linux-backports-modules-3.13.0-29-generic N/A
linux-firmware 1.127.2
RfKill:
Tags: trusty
Uname: Linux 3.13.0-29-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-06-07 (3 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/14/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: None
dmi.board.name: TA970
dmi.board.vendor: BI
[Kernel-packages] [Bug 1328746] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1328746/+attachment/4129346/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1328746
Title:
Soundblaster Audigy front panel MIDI fails to initialize
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
This bug has been around for a while. I have seen it in the forums
circa 2007, and I have provided a solution in 2009. Since the modified
code never found its way into the mainstream kernels, I am issuing the
fix as a bug report.
The bug concerns the Soundblaster Audigy cards with the emu10k1 chip
in both i386 and amd64 architectures, in any kernel (standard, RT
etc). They have on-board joystick MIDI. There is an optional front-
panel module, which provides its own MIDI UART. Under Linux, the front
MIDI does not work. People with dual-boot systems have reported that
booting Windows first, then rebooting into Linux makes the UART
function properly.
The cause for the bug lies in the fact that the front panel MIDI is
routed through a microcontroller (resides in the front panel module),
and this microcontroller needs a defined reset signal once after
power-up. Up to this point, the GPIO _levels_ are initialized
correctly, but the reset _pulse_ is never issued. Essentially, the
emu10k1 chip's GPIO2 needs to be pulled high for a brief interval.
The bug can be fixed in the file linux-
source-3.13.0/sound/pci/emu10k1/emumpu401.c in the function
snd_emu10k1_audigy_midi(). The proposed patch follows right after the
present initialization of the second UART (note the added variable
"val" to store the GPIO bits):
int snd_emu10k1_audigy_midi(struct snd_emu10k1 *emu)
{
struct snd_emu10k1_midi *midi;
int err;
unsigned int val;/* Needed in GPOUT2 pulse initialization */
midi = &emu->midi;
if ((err = emu10k1_midi_init(emu, midi, 0, "Audigy MPU-401 (UART)")) < 0)
return err;
midi->tx_enable = INTE_MIDITXENABLE;
midi->rx_enable = INTE_MIDIRXENABLE;
midi->port = A_MUDATA1;
midi->ipr_tx = IPR_MIDITRANSBUFEMPTY;
midi->ipr_rx = IPR_MIDIRECVBUFEMPTY;
midi->interrupt = snd_emu10k1_midi_interrupt;
midi = &emu->midi2;
if ((err = emu10k1_midi_init(emu, midi, 1, "Audigy MPU-401 #2")) < 0)
return err;
midi->tx_enable = INTE_A_MIDITXENABLE2;
midi->rx_enable = INTE_A_MIDIRXENABLE2;
midi->port = A_MUDATA2;
midi->ipr_tx = IPR_A_MIDITRANSBUFEMPTY2;
midi->ipr_rx = IPR_A_MIDIRECVBUFEMPTY2;
midi->interrupt = snd_emu10k1_midi_interrupt2;
/*** NEW CODE *** Pulse reset line for the second UART */
val = inl(emu->port + A_IOCFG);
outl (val | A_IOCFG_GPOUT2, emu->port + A_IOCFG);
udelay(10); /* udelay is a bad kludge, but remember that this is
called only once on startup */
outl (val, emu->port + A_IOCFG);
return 0;
}
I suspect that my use of udelay would make a real kernel hacker
cringe, but the level of GPOUT2 needs to remain high for a few
microseconds to provide a stable RESET signal.
Anyway, this fixes the problem. I have applied the patch for pretty much
every major upgrade of the kernel. It is sufficient to compile the module
snd-emu10k1.ko and replace it in the module tree.
---
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: mhaidekk 2321 F pulseaudio
/dev/snd/controlC1: mhaidekk 2321 F pulseaudio
/dev/snd/controlC0: mhaidekk 2321 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
CurrentDesktop: KDE
DistroRelease: Ubuntu 14.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=b15a827a-7aa7-4add-a9b4-cb68262cfddd
InstallationDate: Installed on 2013-12-31 (161 days ago)
InstallationMedia: Kubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130822)
IwConfig:
eth1 no wireless extensions.
lono wireless extensions.
MachineType: BIOSTAR Group TA970
NonfreeKernelModules: fglrx
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic
root=UUID=11a18cc0-0c2e-4ce8-9acd-44c5bb8820e2 ro
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
RelatedPackageVersions:
linux-restricted-modules-3.13.0-29-generic N/A
linux-backports-modules-3.13.0-29-generic N/A
linux-firmware 1.127.2
RfKill:
Tags: trusty
Uname: Linux 3.13.0-29-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-06-07 (3 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/14/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: None
dmi.board.name: TA970
dmi.board.vendor: BIOSTAR Group
[Kernel-packages] [Bug 1328746] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1328746/+attachment/4129348/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1328746
Title:
Soundblaster Audigy front panel MIDI fails to initialize
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
This bug has been around for a while. I have seen it in the forums
circa 2007, and I have provided a solution in 2009. Since the modified
code never found its way into the mainstream kernels, I am issuing the
fix as a bug report.
The bug concerns the Soundblaster Audigy cards with the emu10k1 chip
in both i386 and amd64 architectures, in any kernel (standard, RT
etc). They have on-board joystick MIDI. There is an optional front-
panel module, which provides its own MIDI UART. Under Linux, the front
MIDI does not work. People with dual-boot systems have reported that
booting Windows first, then rebooting into Linux makes the UART
function properly.
The cause for the bug lies in the fact that the front panel MIDI is
routed through a microcontroller (resides in the front panel module),
and this microcontroller needs a defined reset signal once after
power-up. Up to this point, the GPIO _levels_ are initialized
correctly, but the reset _pulse_ is never issued. Essentially, the
emu10k1 chip's GPIO2 needs to be pulled high for a brief interval.
The bug can be fixed in the file linux-
source-3.13.0/sound/pci/emu10k1/emumpu401.c in the function
snd_emu10k1_audigy_midi(). The proposed patch follows right after the
present initialization of the second UART (note the added variable
"val" to store the GPIO bits):
int snd_emu10k1_audigy_midi(struct snd_emu10k1 *emu)
{
struct snd_emu10k1_midi *midi;
int err;
unsigned int val;/* Needed in GPOUT2 pulse initialization */
midi = &emu->midi;
if ((err = emu10k1_midi_init(emu, midi, 0, "Audigy MPU-401 (UART)")) < 0)
return err;
midi->tx_enable = INTE_MIDITXENABLE;
midi->rx_enable = INTE_MIDIRXENABLE;
midi->port = A_MUDATA1;
midi->ipr_tx = IPR_MIDITRANSBUFEMPTY;
midi->ipr_rx = IPR_MIDIRECVBUFEMPTY;
midi->interrupt = snd_emu10k1_midi_interrupt;
midi = &emu->midi2;
if ((err = emu10k1_midi_init(emu, midi, 1, "Audigy MPU-401 #2")) < 0)
return err;
midi->tx_enable = INTE_A_MIDITXENABLE2;
midi->rx_enable = INTE_A_MIDIRXENABLE2;
midi->port = A_MUDATA2;
midi->ipr_tx = IPR_A_MIDITRANSBUFEMPTY2;
midi->ipr_rx = IPR_A_MIDIRECVBUFEMPTY2;
midi->interrupt = snd_emu10k1_midi_interrupt2;
/*** NEW CODE *** Pulse reset line for the second UART */
val = inl(emu->port + A_IOCFG);
outl (val | A_IOCFG_GPOUT2, emu->port + A_IOCFG);
udelay(10); /* udelay is a bad kludge, but remember that this is
called only once on startup */
outl (val, emu->port + A_IOCFG);
return 0;
}
I suspect that my use of udelay would make a real kernel hacker
cringe, but the level of GPOUT2 needs to remain high for a few
microseconds to provide a stable RESET signal.
Anyway, this fixes the problem. I have applied the patch for pretty much
every major upgrade of the kernel. It is sufficient to compile the module
snd-emu10k1.ko and replace it in the module tree.
---
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: mhaidekk 2321 F pulseaudio
/dev/snd/controlC1: mhaidekk 2321 F pulseaudio
/dev/snd/controlC0: mhaidekk 2321 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
CurrentDesktop: KDE
DistroRelease: Ubuntu 14.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=b15a827a-7aa7-4add-a9b4-cb68262cfddd
InstallationDate: Installed on 2013-12-31 (161 days ago)
InstallationMedia: Kubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130822)
IwConfig:
eth1 no wireless extensions.
lono wireless extensions.
MachineType: BIOSTAR Group TA970
NonfreeKernelModules: fglrx
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic
root=UUID=11a18cc0-0c2e-4ce8-9acd-44c5bb8820e2 ro
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
RelatedPackageVersions:
linux-restricted-modules-3.13.0-29-generic N/A
linux-backports-modules-3.13.0-29-generic N/A
linux-firmware 1.127.2
RfKill:
Tags: trusty
Uname: Linux 3.13.0-29-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-06-07 (3 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/14/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: None
dmi.board.name: TA970
dmi.board.vendor: BI
[Kernel-packages] [Bug 1328746] BootDmesg.txt
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1328746/+attachment/4129344/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1328746
Title:
Soundblaster Audigy front panel MIDI fails to initialize
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
This bug has been around for a while. I have seen it in the forums
circa 2007, and I have provided a solution in 2009. Since the modified
code never found its way into the mainstream kernels, I am issuing the
fix as a bug report.
The bug concerns the Soundblaster Audigy cards with the emu10k1 chip
in both i386 and amd64 architectures, in any kernel (standard, RT
etc). They have on-board joystick MIDI. There is an optional front-
panel module, which provides its own MIDI UART. Under Linux, the front
MIDI does not work. People with dual-boot systems have reported that
booting Windows first, then rebooting into Linux makes the UART
function properly.
The cause for the bug lies in the fact that the front panel MIDI is
routed through a microcontroller (resides in the front panel module),
and this microcontroller needs a defined reset signal once after
power-up. Up to this point, the GPIO _levels_ are initialized
correctly, but the reset _pulse_ is never issued. Essentially, the
emu10k1 chip's GPIO2 needs to be pulled high for a brief interval.
The bug can be fixed in the file linux-
source-3.13.0/sound/pci/emu10k1/emumpu401.c in the function
snd_emu10k1_audigy_midi(). The proposed patch follows right after the
present initialization of the second UART (note the added variable
"val" to store the GPIO bits):
int snd_emu10k1_audigy_midi(struct snd_emu10k1 *emu)
{
struct snd_emu10k1_midi *midi;
int err;
unsigned int val;/* Needed in GPOUT2 pulse initialization */
midi = &emu->midi;
if ((err = emu10k1_midi_init(emu, midi, 0, "Audigy MPU-401 (UART)")) < 0)
return err;
midi->tx_enable = INTE_MIDITXENABLE;
midi->rx_enable = INTE_MIDIRXENABLE;
midi->port = A_MUDATA1;
midi->ipr_tx = IPR_MIDITRANSBUFEMPTY;
midi->ipr_rx = IPR_MIDIRECVBUFEMPTY;
midi->interrupt = snd_emu10k1_midi_interrupt;
midi = &emu->midi2;
if ((err = emu10k1_midi_init(emu, midi, 1, "Audigy MPU-401 #2")) < 0)
return err;
midi->tx_enable = INTE_A_MIDITXENABLE2;
midi->rx_enable = INTE_A_MIDIRXENABLE2;
midi->port = A_MUDATA2;
midi->ipr_tx = IPR_A_MIDITRANSBUFEMPTY2;
midi->ipr_rx = IPR_A_MIDIRECVBUFEMPTY2;
midi->interrupt = snd_emu10k1_midi_interrupt2;
/*** NEW CODE *** Pulse reset line for the second UART */
val = inl(emu->port + A_IOCFG);
outl (val | A_IOCFG_GPOUT2, emu->port + A_IOCFG);
udelay(10); /* udelay is a bad kludge, but remember that this is
called only once on startup */
outl (val, emu->port + A_IOCFG);
return 0;
}
I suspect that my use of udelay would make a real kernel hacker
cringe, but the level of GPOUT2 needs to remain high for a few
microseconds to provide a stable RESET signal.
Anyway, this fixes the problem. I have applied the patch for pretty much
every major upgrade of the kernel. It is sufficient to compile the module
snd-emu10k1.ko and replace it in the module tree.
---
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: mhaidekk 2321 F pulseaudio
/dev/snd/controlC1: mhaidekk 2321 F pulseaudio
/dev/snd/controlC0: mhaidekk 2321 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
CurrentDesktop: KDE
DistroRelease: Ubuntu 14.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=b15a827a-7aa7-4add-a9b4-cb68262cfddd
InstallationDate: Installed on 2013-12-31 (161 days ago)
InstallationMedia: Kubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130822)
IwConfig:
eth1 no wireless extensions.
lono wireless extensions.
MachineType: BIOSTAR Group TA970
NonfreeKernelModules: fglrx
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic
root=UUID=11a18cc0-0c2e-4ce8-9acd-44c5bb8820e2 ro
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
RelatedPackageVersions:
linux-restricted-modules-3.13.0-29-generic N/A
linux-backports-modules-3.13.0-29-generic N/A
linux-firmware 1.127.2
RfKill:
Tags: trusty
Uname: Linux 3.13.0-29-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-06-07 (3 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/14/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: None
dmi.board.name: TA970
dmi.board.vendor: BIOSTA
[Kernel-packages] [Bug 1328746] Re: Soundblaster Audigy front panel MIDI fails to initialize
apport information
** Tags added: apport-collected trusty
** Description changed:
This bug has been around for a while. I have seen it in the forums circa
2007, and I have provided a solution in 2009. Since the modified code
never found its way into the mainstream kernels, I am issuing the fix as
a bug report.
The bug concerns the Soundblaster Audigy cards with the emu10k1 chip in
both i386 and amd64 architectures, in any kernel (standard, RT etc).
They have on-board joystick MIDI. There is an optional front-panel
module, which provides its own MIDI UART. Under Linux, the front MIDI
does not work. People with dual-boot systems have reported that booting
Windows first, then rebooting into Linux makes the UART function
properly.
The cause for the bug lies in the fact that the front panel MIDI is
routed through a microcontroller (resides in the front panel module),
and this microcontroller needs a defined reset signal once after power-
up. Up to this point, the GPIO _levels_ are initialized correctly, but
the reset _pulse_ is never issued. Essentially, the emu10k1 chip's GPIO2
needs to be pulled high for a brief interval.
The bug can be fixed in the file linux-
source-3.13.0/sound/pci/emu10k1/emumpu401.c in the function
snd_emu10k1_audigy_midi(). The proposed patch follows right after the
present initialization of the second UART (note the added variable "val"
to store the GPIO bits):
int snd_emu10k1_audigy_midi(struct snd_emu10k1 *emu)
{
struct snd_emu10k1_midi *midi;
int err;
unsigned int val;/* Needed in GPOUT2 pulse initialization */
midi = &emu->midi;
if ((err = emu10k1_midi_init(emu, midi, 0, "Audigy MPU-401 (UART)")) < 0)
return err;
midi->tx_enable = INTE_MIDITXENABLE;
midi->rx_enable = INTE_MIDIRXENABLE;
midi->port = A_MUDATA1;
midi->ipr_tx = IPR_MIDITRANSBUFEMPTY;
midi->ipr_rx = IPR_MIDIRECVBUFEMPTY;
midi->interrupt = snd_emu10k1_midi_interrupt;
midi = &emu->midi2;
if ((err = emu10k1_midi_init(emu, midi, 1, "Audigy MPU-401 #2")) < 0)
return err;
midi->tx_enable = INTE_A_MIDITXENABLE2;
midi->rx_enable = INTE_A_MIDIRXENABLE2;
midi->port = A_MUDATA2;
midi->ipr_tx = IPR_A_MIDITRANSBUFEMPTY2;
midi->ipr_rx = IPR_A_MIDIRECVBUFEMPTY2;
midi->interrupt = snd_emu10k1_midi_interrupt2;
/*** NEW CODE *** Pulse reset line for the second UART */
val = inl(emu->port + A_IOCFG);
outl (val | A_IOCFG_GPOUT2, emu->port + A_IOCFG);
udelay(10); /* udelay is a bad kludge, but remember that this is
called only once on startup */
outl (val, emu->port + A_IOCFG);
return 0;
}
I suspect that my use of udelay would make a real kernel hacker cringe,
but the level of GPOUT2 needs to remain high for a few microseconds to
provide a stable RESET signal.
- Anyway, this fixes the problem. I have applied the patch for pretty much
- every major upgrade of the kernel. It is sufficient to compile the
- module snd-emu10k1.ko and replace it in the module tree.
+ Anyway, this fixes the problem. I have applied the patch for pretty much
every major upgrade of the kernel. It is sufficient to compile the module
snd-emu10k1.ko and replace it in the module tree.
+ ---
+ ApportVersion: 2.14.1-0ubuntu3.2
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC2: mhaidekk 2321 F pulseaudio
+ /dev/snd/controlC1: mhaidekk 2321 F pulseaudio
+ /dev/snd/controlC0: mhaidekk 2321 F pulseaudio
+ CRDA: Error: [Errno 2] No such file or directory
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 14.04
+ EcryptfsInUse: Yes
+ HibernationDevice: RESUME=UUID=b15a827a-7aa7-4add-a9b4-cb68262cfddd
+ InstallationDate: Installed on 2013-12-31 (161 days ago)
+ InstallationMedia: Kubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130822)
+ IwConfig:
+ eth1 no wireless extensions.
+
+ lono wireless extensions.
+ MachineType: BIOSTAR Group TA970
+ NonfreeKernelModules: fglrx
+ Package: linux (not installed)
+ ProcFB: 0 VESA VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic
root=UUID=11a18cc0-0c2e-4ce8-9acd-44c5bb8820e2 ro
+ ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
+ RelatedPackageVersions:
+ linux-restricted-modules-3.13.0-29-generic N/A
+ linux-backports-modules-3.13.0-29-generic N/A
+ linux-firmware 1.127.2
+ RfKill:
+
+ Tags: trusty
+ Uname: Linux 3.13.0-29-generic x86_64
+ UpgradeStatus: Upgraded to trusty on 2014-06-07 (3 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 01/14/2013
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 4.6.4
+ dmi.board.asset.tag: None
+ dmi.board.name: TA970
+ dmi.board.vendor: BIOSTAR Group
+ dmi.chassis.asset.tag: None
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: BIOSTAR Group
+ dmi.modalias:
dmi:bvnAmerican
[Kernel-packages] [Bug 1328746] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1328746/+attachment/4129345/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1328746
Title:
Soundblaster Audigy front panel MIDI fails to initialize
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
This bug has been around for a while. I have seen it in the forums
circa 2007, and I have provided a solution in 2009. Since the modified
code never found its way into the mainstream kernels, I am issuing the
fix as a bug report.
The bug concerns the Soundblaster Audigy cards with the emu10k1 chip
in both i386 and amd64 architectures, in any kernel (standard, RT
etc). They have on-board joystick MIDI. There is an optional front-
panel module, which provides its own MIDI UART. Under Linux, the front
MIDI does not work. People with dual-boot systems have reported that
booting Windows first, then rebooting into Linux makes the UART
function properly.
The cause for the bug lies in the fact that the front panel MIDI is
routed through a microcontroller (resides in the front panel module),
and this microcontroller needs a defined reset signal once after
power-up. Up to this point, the GPIO _levels_ are initialized
correctly, but the reset _pulse_ is never issued. Essentially, the
emu10k1 chip's GPIO2 needs to be pulled high for a brief interval.
The bug can be fixed in the file linux-
source-3.13.0/sound/pci/emu10k1/emumpu401.c in the function
snd_emu10k1_audigy_midi(). The proposed patch follows right after the
present initialization of the second UART (note the added variable
"val" to store the GPIO bits):
int snd_emu10k1_audigy_midi(struct snd_emu10k1 *emu)
{
struct snd_emu10k1_midi *midi;
int err;
unsigned int val;/* Needed in GPOUT2 pulse initialization */
midi = &emu->midi;
if ((err = emu10k1_midi_init(emu, midi, 0, "Audigy MPU-401 (UART)")) < 0)
return err;
midi->tx_enable = INTE_MIDITXENABLE;
midi->rx_enable = INTE_MIDIRXENABLE;
midi->port = A_MUDATA1;
midi->ipr_tx = IPR_MIDITRANSBUFEMPTY;
midi->ipr_rx = IPR_MIDIRECVBUFEMPTY;
midi->interrupt = snd_emu10k1_midi_interrupt;
midi = &emu->midi2;
if ((err = emu10k1_midi_init(emu, midi, 1, "Audigy MPU-401 #2")) < 0)
return err;
midi->tx_enable = INTE_A_MIDITXENABLE2;
midi->rx_enable = INTE_A_MIDIRXENABLE2;
midi->port = A_MUDATA2;
midi->ipr_tx = IPR_A_MIDITRANSBUFEMPTY2;
midi->ipr_rx = IPR_A_MIDIRECVBUFEMPTY2;
midi->interrupt = snd_emu10k1_midi_interrupt2;
/*** NEW CODE *** Pulse reset line for the second UART */
val = inl(emu->port + A_IOCFG);
outl (val | A_IOCFG_GPOUT2, emu->port + A_IOCFG);
udelay(10); /* udelay is a bad kludge, but remember that this is
called only once on startup */
outl (val, emu->port + A_IOCFG);
return 0;
}
I suspect that my use of udelay would make a real kernel hacker
cringe, but the level of GPOUT2 needs to remain high for a few
microseconds to provide a stable RESET signal.
Anyway, this fixes the problem. I have applied the patch for pretty much
every major upgrade of the kernel. It is sufficient to compile the module
snd-emu10k1.ko and replace it in the module tree.
---
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: mhaidekk 2321 F pulseaudio
/dev/snd/controlC1: mhaidekk 2321 F pulseaudio
/dev/snd/controlC0: mhaidekk 2321 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
CurrentDesktop: KDE
DistroRelease: Ubuntu 14.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=b15a827a-7aa7-4add-a9b4-cb68262cfddd
InstallationDate: Installed on 2013-12-31 (161 days ago)
InstallationMedia: Kubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130822)
IwConfig:
eth1 no wireless extensions.
lono wireless extensions.
MachineType: BIOSTAR Group TA970
NonfreeKernelModules: fglrx
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic
root=UUID=11a18cc0-0c2e-4ce8-9acd-44c5bb8820e2 ro
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
RelatedPackageVersions:
linux-restricted-modules-3.13.0-29-generic N/A
linux-backports-modules-3.13.0-29-generic N/A
linux-firmware 1.127.2
RfKill:
Tags: trusty
Uname: Linux 3.13.0-29-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-06-07 (3 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/14/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: None
dmi.board.name: TA970
dmi.board.vendor:
[Kernel-packages] [Bug 1328746] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1328746/+attachment/4129347/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1328746
Title:
Soundblaster Audigy front panel MIDI fails to initialize
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
This bug has been around for a while. I have seen it in the forums
circa 2007, and I have provided a solution in 2009. Since the modified
code never found its way into the mainstream kernels, I am issuing the
fix as a bug report.
The bug concerns the Soundblaster Audigy cards with the emu10k1 chip
in both i386 and amd64 architectures, in any kernel (standard, RT
etc). They have on-board joystick MIDI. There is an optional front-
panel module, which provides its own MIDI UART. Under Linux, the front
MIDI does not work. People with dual-boot systems have reported that
booting Windows first, then rebooting into Linux makes the UART
function properly.
The cause for the bug lies in the fact that the front panel MIDI is
routed through a microcontroller (resides in the front panel module),
and this microcontroller needs a defined reset signal once after
power-up. Up to this point, the GPIO _levels_ are initialized
correctly, but the reset _pulse_ is never issued. Essentially, the
emu10k1 chip's GPIO2 needs to be pulled high for a brief interval.
The bug can be fixed in the file linux-
source-3.13.0/sound/pci/emu10k1/emumpu401.c in the function
snd_emu10k1_audigy_midi(). The proposed patch follows right after the
present initialization of the second UART (note the added variable
"val" to store the GPIO bits):
int snd_emu10k1_audigy_midi(struct snd_emu10k1 *emu)
{
struct snd_emu10k1_midi *midi;
int err;
unsigned int val;/* Needed in GPOUT2 pulse initialization */
midi = &emu->midi;
if ((err = emu10k1_midi_init(emu, midi, 0, "Audigy MPU-401 (UART)")) < 0)
return err;
midi->tx_enable = INTE_MIDITXENABLE;
midi->rx_enable = INTE_MIDIRXENABLE;
midi->port = A_MUDATA1;
midi->ipr_tx = IPR_MIDITRANSBUFEMPTY;
midi->ipr_rx = IPR_MIDIRECVBUFEMPTY;
midi->interrupt = snd_emu10k1_midi_interrupt;
midi = &emu->midi2;
if ((err = emu10k1_midi_init(emu, midi, 1, "Audigy MPU-401 #2")) < 0)
return err;
midi->tx_enable = INTE_A_MIDITXENABLE2;
midi->rx_enable = INTE_A_MIDIRXENABLE2;
midi->port = A_MUDATA2;
midi->ipr_tx = IPR_A_MIDITRANSBUFEMPTY2;
midi->ipr_rx = IPR_A_MIDIRECVBUFEMPTY2;
midi->interrupt = snd_emu10k1_midi_interrupt2;
/*** NEW CODE *** Pulse reset line for the second UART */
val = inl(emu->port + A_IOCFG);
outl (val | A_IOCFG_GPOUT2, emu->port + A_IOCFG);
udelay(10); /* udelay is a bad kludge, but remember that this is
called only once on startup */
outl (val, emu->port + A_IOCFG);
return 0;
}
I suspect that my use of udelay would make a real kernel hacker
cringe, but the level of GPOUT2 needs to remain high for a few
microseconds to provide a stable RESET signal.
Anyway, this fixes the problem. I have applied the patch for pretty much
every major upgrade of the kernel. It is sufficient to compile the module
snd-emu10k1.ko and replace it in the module tree.
---
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: mhaidekk 2321 F pulseaudio
/dev/snd/controlC1: mhaidekk 2321 F pulseaudio
/dev/snd/controlC0: mhaidekk 2321 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
CurrentDesktop: KDE
DistroRelease: Ubuntu 14.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=b15a827a-7aa7-4add-a9b4-cb68262cfddd
InstallationDate: Installed on 2013-12-31 (161 days ago)
InstallationMedia: Kubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130822)
IwConfig:
eth1 no wireless extensions.
lono wireless extensions.
MachineType: BIOSTAR Group TA970
NonfreeKernelModules: fglrx
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic
root=UUID=11a18cc0-0c2e-4ce8-9acd-44c5bb8820e2 ro
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
RelatedPackageVersions:
linux-restricted-modules-3.13.0-29-generic N/A
linux-backports-modules-3.13.0-29-generic N/A
linux-firmware 1.127.2
RfKill:
Tags: trusty
Uname: Linux 3.13.0-29-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-06-07 (3 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/14/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: None
dmi.board.name: TA970
dmi.board.vendor: BIOSTAR Group
Re: [Kernel-packages] [Bug 1327014] Re: Linux kernel 2.6.32-61 hangs gnome desktop on ubuntu 10.04 lucid lynx
Am Dienstag, den 10.06.2014, 03:24 + schrieb Steve Langasek: > On Tue, Jun 10, 2014 at 02:50:04AM -, hamish wrote: > > er, seriously? the kernel and firefox don't fall under things people > > might possibly need LTS for? > > You seem to have misunderstood what "LTS" means. "LTS" does not mean "feel > free to run this OS indefinitely, without upgrading, and expect to continue > to receive support from the Ubuntu community". The 10.04 LTS desktop > packages - which *definitely* include firefox - were only supported until > April 2013. Anyone running a desktop environment on top of 10.04 is using > software that has not been receiving critical security updates for over a > year. > > So no, you should not expect Ubuntu developers to go out of their way to > enable you to continue running in a configuration which we do not endorse. > Any desktop-affecting regressions in the kernel security update are > certainly unintentional, but if they only affect no-longer-supported desktop > packages, it is not a critical regression. Hmm. But you withdrew that kernel update for 10.04, i.e. the 10.04 update-manager does not show that new kernel version as an update anymore. And you continue to deliver critical security fixes to this unsupported 10.04 release for a while, right? Well, then you should also try to fix these issues in due time or at least give clear advice what sysadmins or experienced users can do get things working again. Or stop updating the kernel for 10.04 all together! > Sure; the solution is to upgrade to a supported version of the Ubuntu > desktop packages, 12.04 LTS (or 14.04 LTS). > ...which will potentially break existing software which had been running stably for a long time and had many happy users. ... and has a little blackmailing momentum in it, doesn't it? -- thomas -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1327014 Title: Linux kernel 2.6.32-61 hangs gnome desktop on ubuntu 10.04 lucid lynx Status in “linux” package in Ubuntu: Won't Fix Bug description: Just did a regular update and the latest kernel would boot, but when logging into my gnome desktop the mouse cursor shows a sandbox and is inaccessible. Had to go back to 2.6.32-60. Ubuntu 2.6.32-60.122-generic 2.6.32.61+drm33.26 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327014/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328746] Re: Soundblaster Audigy front panel MIDI fails to initialize
** Description changed:
This bug has been around for a while. I have seen it in the forums circa
2007, and I have provided a solution in 2009. Since the modified code
never found its way into the mainstream kernels, I am issuing the fix as
a bug report.
The bug concerns the Soundblaster Audigy cards with the emu10k1 chip in
both i386 and amd64 architectures, in any kernel (standard, RT etc).
They have on-board joystick MIDI. There is an optional front-panel
- module, which provides its own MIDI UART. Under Liunux, the front MIDI
- does not work. People wuth dual-boot systems have reported that booting
+ module, which provides its own MIDI UART. Under Linux, the front MIDI
+ does not work. People with dual-boot systems have reported that booting
Windows first, then rebooting into Linux makes the UART function
properly.
The cause for the bug lies in the fact that the front panel MIDI is
routed through a microcontroller (resides in the front panel module),
- and this microcontroller needs a defined reset signal. Up to this point,
- the GPIO _levels_ are initialized correctly, but the reset pulse is
- never issued.
+ and this microcontroller needs a defined reset signal once after power-
+ up. Up to this point, the GPIO _levels_ are initialized correctly, but
+ the reset _pulse_ is never issued. Essentially, the emu10k1 chip's GPIO2
+ needs to be pulled high for a brief interval.
The bug can be fixed in the file linux-
source-3.13.0/sound/pci/emu10k1/emumpu401.c in the function
snd_emu10k1_audigy_midi(). The proposed patch follows right after the
- present initialization of the second UART:
-
+ present initialization of the second UART (note the added variable "val"
+ to store the GPIO bits):
int snd_emu10k1_audigy_midi(struct snd_emu10k1 *emu)
{
- struct snd_emu10k1_midi *midi;
- int err;
- unsigned int val; /* Needed in GPOUT2 pulse
initialization */
+ struct snd_emu10k1_midi *midi;
+ int err;
+ unsigned int val;/* Needed in GPOUT2 pulse initialization */
- midi = &emu->midi;
- if ((err = emu10k1_midi_init(emu, midi, 0, "Audigy MPU-401 (UART)")) <
0)
- return err;
+ midi = &emu->midi;
+ if ((err = emu10k1_midi_init(emu, midi, 0, "Audigy MPU-401 (UART)")) < 0)
+ return err;
- midi->tx_enable = INTE_MIDITXENABLE;
- midi->rx_enable = INTE_MIDIRXENABLE;
- midi->port = A_MUDATA1;
- midi->ipr_tx = IPR_MIDITRANSBUFEMPTY;
- midi->ipr_rx = IPR_MIDIRECVBUFEMPTY;
- midi->interrupt = snd_emu10k1_midi_interrupt;
+ midi->tx_enable = INTE_MIDITXENABLE;
+ midi->rx_enable = INTE_MIDIRXENABLE;
+ midi->port = A_MUDATA1;
+ midi->ipr_tx = IPR_MIDITRANSBUFEMPTY;
+ midi->ipr_rx = IPR_MIDIRECVBUFEMPTY;
+ midi->interrupt = snd_emu10k1_midi_interrupt;
- midi = &emu->midi2;
- if ((err = emu10k1_midi_init(emu, midi, 1, "Audigy MPU-401 #2")) < 0)
- return err;
+ midi = &emu->midi2;
+ if ((err = emu10k1_midi_init(emu, midi, 1, "Audigy MPU-401 #2")) < 0)
+ return err;
- midi->tx_enable = INTE_A_MIDITXENABLE2;
- midi->rx_enable = INTE_A_MIDIRXENABLE2;
- midi->port = A_MUDATA2;
- midi->ipr_tx = IPR_A_MIDITRANSBUFEMPTY2;
- midi->ipr_rx = IPR_A_MIDIRECVBUFEMPTY2;
- midi->interrupt = snd_emu10k1_midi_interrupt2;
+ midi->tx_enable = INTE_A_MIDITXENABLE2;
+ midi->rx_enable = INTE_A_MIDIRXENABLE2;
+ midi->port = A_MUDATA2;
+ midi->ipr_tx = IPR_A_MIDITRANSBUFEMPTY2;
+ midi->ipr_rx = IPR_A_MIDIRECVBUFEMPTY2;
+ midi->interrupt = snd_emu10k1_midi_interrupt2;
- /*** NEW CODE *** Pulse reset line for the second UART */
+ /*** NEW CODE *** Pulse reset line for the second UART */
- val = inl(emu->port + A_IOCFG);
- outl (val | A_IOCFG_GPOUT2, emu->port + A_IOCFG);
- udelay(10); /* udelay is a bad kludge, but remember that
this is called only once on startup */
- outl (val, emu->port + A_IOCFG);
+ val = inl(emu->port + A_IOCFG);
+ outl (val | A_IOCFG_GPOUT2, emu->port + A_IOCFG);
+ udelay(10); /* udelay is a bad kludge, but remember that this is
called only once on startup */
+ outl (val, emu->port + A_IOCFG);
- return 0;
+ return 0;
}
-
- I suspect that my use of udelay would make a real kernel hacker cringe, but
the level of GPOUT2 needs to remain high for a few microseconds to provide a
stable RESET signal.
+ I suspect that my use of udelay would make a real kernel hacker cringe,
+ but the level of GPOUT2 needs to remain high for a few microseconds to
+ provide a stable RESET signal.
Anyway, this fixes the problem. I have applied the patch for pretty much
every major upgrade of the kernel. It is sufficient to compile the
module snd-emu10k1.ko and replace it in the module tree.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
[Kernel-packages] [Bug 1328746] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1328746
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/1328746
Title:
Soundblaster Audigy front panel MIDI fails to initialize
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
This bug has been around for a while. I have seen it in the forums
circa 2007, and I have provided a solution in 2009. Since the modified
code never found its way into the mainstream kernels, I am issuing the
fix as a bug report.
The bug concerns the Soundblaster Audigy cards with the emu10k1 chip
in both i386 and amd64 architectures, in any kernel (standard, RT
etc). They have on-board joystick MIDI. There is an optional front-
panel module, which provides its own MIDI UART. Under Linux, the front
MIDI does not work. People with dual-boot systems have reported that
booting Windows first, then rebooting into Linux makes the UART
function properly.
The cause for the bug lies in the fact that the front panel MIDI is
routed through a microcontroller (resides in the front panel module),
and this microcontroller needs a defined reset signal once after
power-up. Up to this point, the GPIO _levels_ are initialized
correctly, but the reset _pulse_ is never issued. Essentially, the
emu10k1 chip's GPIO2 needs to be pulled high for a brief interval.
The bug can be fixed in the file linux-
source-3.13.0/sound/pci/emu10k1/emumpu401.c in the function
snd_emu10k1_audigy_midi(). The proposed patch follows right after the
present initialization of the second UART (note the added variable
"val" to store the GPIO bits):
int snd_emu10k1_audigy_midi(struct snd_emu10k1 *emu)
{
struct snd_emu10k1_midi *midi;
int err;
unsigned int val;/* Needed in GPOUT2 pulse initialization */
midi = &emu->midi;
if ((err = emu10k1_midi_init(emu, midi, 0, "Audigy MPU-401 (UART)")) < 0)
return err;
midi->tx_enable = INTE_MIDITXENABLE;
midi->rx_enable = INTE_MIDIRXENABLE;
midi->port = A_MUDATA1;
midi->ipr_tx = IPR_MIDITRANSBUFEMPTY;
midi->ipr_rx = IPR_MIDIRECVBUFEMPTY;
midi->interrupt = snd_emu10k1_midi_interrupt;
midi = &emu->midi2;
if ((err = emu10k1_midi_init(emu, midi, 1, "Audigy MPU-401 #2")) < 0)
return err;
midi->tx_enable = INTE_A_MIDITXENABLE2;
midi->rx_enable = INTE_A_MIDIRXENABLE2;
midi->port = A_MUDATA2;
midi->ipr_tx = IPR_A_MIDITRANSBUFEMPTY2;
midi->ipr_rx = IPR_A_MIDIRECVBUFEMPTY2;
midi->interrupt = snd_emu10k1_midi_interrupt2;
/*** NEW CODE *** Pulse reset line for the second UART */
val = inl(emu->port + A_IOCFG);
outl (val | A_IOCFG_GPOUT2, emu->port + A_IOCFG);
udelay(10); /* udelay is a bad kludge, but remember that this is
called only once on startup */
outl (val, emu->port + A_IOCFG);
return 0;
}
I suspect that my use of udelay would make a real kernel hacker
cringe, but the level of GPOUT2 needs to remain high for a few
microseconds to provide a stable RESET signal.
Anyway, this fixes the problem. I have applied the patch for pretty
much every major upgrade of the kernel. It is sufficient to compile
the module snd-emu10k1.ko and replace it in the module tree.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328746/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328746] [NEW] Soundblaster Audigy front panel MIDI fails to initialize
Public bug reported:
This bug has been around for a while. I have seen it in the forums circa
2007, and I have provided a solution in 2009. Since the modified code
never found its way into the mainstream kernels, I am issuing the fix as
a bug report.
The bug concerns the Soundblaster Audigy cards with the emu10k1 chip in
both i386 and amd64 architectures, in any kernel (standard, RT etc).
They have on-board joystick MIDI. There is an optional front-panel
module, which provides its own MIDI UART. Under Linux, the front MIDI
does not work. People with dual-boot systems have reported that booting
Windows first, then rebooting into Linux makes the UART function
properly.
The cause for the bug lies in the fact that the front panel MIDI is
routed through a microcontroller (resides in the front panel module),
and this microcontroller needs a defined reset signal once after power-
up. Up to this point, the GPIO _levels_ are initialized correctly, but
the reset _pulse_ is never issued. Essentially, the emu10k1 chip's GPIO2
needs to be pulled high for a brief interval.
The bug can be fixed in the file linux-
source-3.13.0/sound/pci/emu10k1/emumpu401.c in the function
snd_emu10k1_audigy_midi(). The proposed patch follows right after the
present initialization of the second UART (note the added variable "val"
to store the GPIO bits):
int snd_emu10k1_audigy_midi(struct snd_emu10k1 *emu)
{
struct snd_emu10k1_midi *midi;
int err;
unsigned int val; /* Needed in GPOUT2 pulse initialization */
midi = &emu->midi;
if ((err = emu10k1_midi_init(emu, midi, 0, "Audigy MPU-401 (UART)")) < 0)
return err;
midi->tx_enable = INTE_MIDITXENABLE;
midi->rx_enable = INTE_MIDIRXENABLE;
midi->port = A_MUDATA1;
midi->ipr_tx = IPR_MIDITRANSBUFEMPTY;
midi->ipr_rx = IPR_MIDIRECVBUFEMPTY;
midi->interrupt = snd_emu10k1_midi_interrupt;
midi = &emu->midi2;
if ((err = emu10k1_midi_init(emu, midi, 1, "Audigy MPU-401 #2")) < 0)
return err;
midi->tx_enable = INTE_A_MIDITXENABLE2;
midi->rx_enable = INTE_A_MIDIRXENABLE2;
midi->port = A_MUDATA2;
midi->ipr_tx = IPR_A_MIDITRANSBUFEMPTY2;
midi->ipr_rx = IPR_A_MIDIRECVBUFEMPTY2;
midi->interrupt = snd_emu10k1_midi_interrupt2;
/*** NEW CODE *** Pulse reset line for the second UART */
val = inl(emu->port + A_IOCFG);
outl (val | A_IOCFG_GPOUT2, emu->port + A_IOCFG);
udelay(10);/* udelay is a bad kludge, but remember that this is
called only once on startup */
outl (val, emu->port + A_IOCFG);
return 0;
}
I suspect that my use of udelay would make a real kernel hacker cringe,
but the level of GPOUT2 needs to remain high for a few microseconds to
provide a stable RESET signal.
Anyway, this fixes the problem. I have applied the patch for pretty much
every major upgrade of the kernel. It is sufficient to compile the
module snd-emu10k1.ko and replace it in the module tree.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: 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/1328746
Title:
Soundblaster Audigy front panel MIDI fails to initialize
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
This bug has been around for a while. I have seen it in the forums
circa 2007, and I have provided a solution in 2009. Since the modified
code never found its way into the mainstream kernels, I am issuing the
fix as a bug report.
The bug concerns the Soundblaster Audigy cards with the emu10k1 chip
in both i386 and amd64 architectures, in any kernel (standard, RT
etc). They have on-board joystick MIDI. There is an optional front-
panel module, which provides its own MIDI UART. Under Linux, the front
MIDI does not work. People with dual-boot systems have reported that
booting Windows first, then rebooting into Linux makes the UART
function properly.
The cause for the bug lies in the fact that the front panel MIDI is
routed through a microcontroller (resides in the front panel module),
and this microcontroller needs a defined reset signal once after
power-up. Up to this point, the GPIO _levels_ are initialized
correctly, but the reset _pulse_ is never issued. Essentially, the
emu10k1 chip's GPIO2 needs to be pulled high for a brief interval.
The bug can be fixed in the file linux-
source-3.13.0/sound/pci/emu10k1/emumpu401.c in the function
snd_emu10k1_audigy_midi(). The proposed patch follows right after the
present initialization of the second UART (note the added variable
"val" to store the GPIO bits):
int snd_emu10k1_audigy_midi(struct snd_emu10k1 *emu)
{
struct snd_emu10k1_midi *midi;
int err;
unsigned int val;/* Needed in GPOUT2 pulse initialization */
midi = &emu->midi;
if ((err = emu10k1_midi_init(emu, midi, 0, "Audigy MPU-401 (UART)")) < 0)
return err;
midi->tx_enable = INTE_MIDITXENABLE;
midi->rx_enable = INTE_
[Kernel-packages] [Bug 1328313] Re: [Dell Latitude E7240] Alps Touchpad acts erratically when multi-touch is vertical, not horizontal
Mark Smith, just to focus the scope, I have a similar laptop touchpad design, and using my right hand, I move the cursor with my index, scroll on the right-hand side with the middle, and primary click with my thumb. When I am moving the cursor with my index, my middle is either hovering on slightly raised portion beyond the touchpad at the top. My thumb would rest on the primary click. With this method of use, I don't have any stray clicks, or mis-movements. Given this, I would expect non-desirable behavior if I have three fingers not quite altogether on the touchpad, in Windows, Ubuntu, or Mac. Could you please re-word the one specific problem here, and is their a configuration one would do in Windows that either minimizes or eliminates what you are referring to here? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1328313 Title: [Dell Latitude E7240] Alps Touchpad acts erratically when multi-touch is vertical, not horizontal Status in “linux” package in Ubuntu: Incomplete Bug description: I'm on a Dell Latitude E7240 running 12.04 LTS and my touch pad acts erratically. It happens because my middle and ring fingers accidentally touch the top edge of the pad while my pointer finger is moving the cursor. I can reproduce this on purpose by running "xinput --test [device number]" and watching the events while I do the following: - Touch the pad near the middle or bottom. The cursor moves slightly as my finger wiggles around. - Without removing the first finger, touch the pad again with a second finger above the first finger. The cursor shoots up to a[1]=0 (which is the y position). - Without removing the first finger, remove the second (top) finger. The cursor shoots back down to a[1]= Sometimes it takes it all the way to the bottom of the screen, sometimes it goes back to where it was, or somewhere else. I haven't been able to figure out how it decides what to go back to. With this, while I touching with my pointer finger and my middle or ring finger accidentally touch the pad at the top, the cursor shoots where I don't want it. Then when my middle/ring finger leaves the pad (usually because I started cursing (get it?) at my cursor), it shoots back down again somewhere completely arbitrary. Similarly: - Touch the bad near the top. - Without removing the top finger, touch somewhere near the bottom. The cursor doesn't (yet) move. - Lift the top finger. The cursor shoots to the bottom. - Put down the top finger again, without lifting the bottom. The cursor shoots back up again. You can make the cursor shoot up and down just by keeping your bottom finger down and tapping the top finger. The cursor follows the top finger no matter what you do. Interestingly, this does NOT happen from side-to-side. Two touches side-by-side trigger the multi-touch gestures and don't move the cursor. This problem does not happen in Windows 7. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-29-generic. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 1: PCH [HDA Intel PCH], device 0: ALC292 Analog [ALC292 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mrksmith 2576 F pulseaudio /dev/snd/controlC0: mrksmith 2576 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'HDMI'/'HDA Intel HDMI at 0xf7e34000 irq 64' Mixer name : 'Intel Haswell HDMI' Components : 'HDA:80862807,80860101,0010' Controls : 21 Simple ctrls : 3 Card1.Amixer.info: Card hw:1 'PCH'/'HDA Intel PCH at 0xf7e3 irq 65' Mixer name : 'Realtek ALC292' Components : 'HDA:10ec0292,102805ca,0011' Controls : 28 Simple ctrls : 13 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=303359b5-1c66-468d-935e-a6d9bc56e4e9 MachineType: Dell Inc. Latitude E7240 MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-29-generic root=/dev/mapper/vg0-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-29.53~precise1-generic 3.13.11.2 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.79.14 Tags: precise running-unity Uname: Linux 3.13.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout lpadmin plugdev sambashare sudo dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.asset.tag: 120
[Kernel-packages] [Bug 1327625] Re: system spontaneously awakes from sleep; other sleep problems
slowtrain, as per http://h10025.www1.hp.com/ewfrf/wc/softwareCategory?os=4063&lc=en&cc=us&dlc=en&sw_lang=&product=5171116#N1791 an update to your BIOS is available (F.1C). If you update to this following https://help.ubuntu.com/community/BiosUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Thank you for your understanding. ** Tags removed: needs-full-computer-model ** Tags added: bios-outdated-f.1c ** Summary changed: - system spontaneously awakes from sleep; other sleep problems + [HP Pavilion dv6t-6b00 CTO Quad Edition Entertainment Notebook PC] System spontaneously awakes from sleep; other sleep problems -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1327625 Title: [HP Pavilion dv6t-6b00 CTO Quad Edition Entertainment Notebook PC] System spontaneously awakes from sleep; other sleep problems Status in “linux” package in Ubuntu: Incomplete Bug description: I added KDE to an Ubuntu installation. When I'm in KDE, I've had numerous problems with suspend to RAM, even though I don't believe I had these problems in Unity. The particular problem I just had, so perhaps the data apport collected spotted something, was this: I deliberately suspended to RAM. A few seconds later, the computer woke up without my doing anything (did not touch the keyboard, etc.). This has happened numerous times. For a while, I had to suspend twice whenever I wanted the suspend to take hold. [Other suspend problems, but which have not occurred just now: a) system freezes when I initiate a suspend--have to hard shutdown otherwise computer keeps running with nothing showing on either display; b) system goes into suspend, and wakes right back up again a few seconds later, for no apparent reason--can happen when I'm watching a video or editing some text; c) system suspends and wakes up when I move between activities] I erased the contents of various system logs to see what records were being generated when the problem occurs. Only two logs showed any addition of material (from empty)--pm-suspend and pm-powersave. I'm attaching them here. Because other logs will have no content, I'll attach some older logs in case there's something that might be useful. Best wishes figuring this out! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peterm 3016 F pulseaudio BootDmesg: CurrentDesktop: KDE Date: Sat Jun 7 17:47:52 2014 HibernationDevice: RESUME=UUID=5d23be8c-e134-466b-8698-0344f70809a4 InstallationDate: Installed on 2014-04-20 (48 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-29-generic root=UUID=905a5deb-feac-448c-9f59-7040a9ea9942 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 10/23/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1B dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 17FB dmi.board.vendor: Hewlett-Packard dmi.board.version: 10.5A dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1B:bd10/23/2012:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058D11000220472622100:rvnHewlett-Packard:rn17FB:rvr10.5A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 058D11000220472622100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327625/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/Lis
[Kernel-packages] [Bug 1283938] Re: [Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after wakeup from sleep
Ken Nakasya, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via: ubuntu-bug linux For more on this, please read the official Ubuntu documentation: Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette When opening up the new report, please feel free to subscribe me to it. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1283938 Title: [Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after wakeup from sleep Status in “linux” package in Ubuntu: Incomplete Bug description: In 14.04 after wakeup from suspend, the notebook screen goes blank while the OS and the hardware is awake (I can also press Ctrl+F1 and Ctrl+Alt+Del to reboot the system). Changeing "quiet splash" to "nomodeset" in /etc/default/grub allows the wakeup, but the pc is really slow (can't be used). WORKAROUND: This problem is not happening with the AMD property drivers. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Feb 24 12:58:07 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7500G] [1002:990a] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c660] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] [1002:6841] (rev ff) (prog-if ff) InstallationDate: Installed on 2014-02-22 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140218) MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U4C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic root=UUID=9f8c7e92-a6ea-41fd-9489-a256c8b9f5d5 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P06RAF.N93.130403.LEO dmi.board.asset.tag: No Asset Tag dmi.board.name: NP535U4X-S01TH dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP06RAF.N93.130403.LEO:bd04/03/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U4C:pvrP06RAF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP535U4X-S01TH:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 535U4C dmi.product.version: P06RAF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Feb 24 12:54:54 2014 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu6 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packag
[Kernel-packages] [Bug 1328313] Re: [Dell Latitude E7240] Alps Touchpad acts erratically when multi-touch is vertical, not horizontal
** Description changed: I'm on a Dell Latitude E7240 running 12.04 LTS and my touch pad acts erratically. It happens because my middle and ring fingers accidentally touch the top edge of the pad while my pointer finger is moving the cursor. I can reproduce this on purpose by running "xinput --test [device number]" and watching the events while I do the following: - Touch the pad near the middle or bottom. The cursor moves slightly as my finger wiggles around. - Without removing the first finger, touch the pad again with a second finger above the first finger. The cursor shoots up to a[1]=0 (which is the y position). - Without removing the first finger, remove the second (top) finger. The cursor shoots back down to a[1]= Sometimes it takes it all the way to the bottom of the screen, sometimes it goes back to where it was, or somewhere else. I haven't been able to figure out how it decides what to go back to. With this, while I touching with my pointer finger and my middle or ring finger accidentally touch the pad at the top, the cursor shoots where I don't want it. Then when my middle/ring finger leaves the pad (usually because I started cursing (get it?) at my cursor), it shoots back down again somewhere completely arbitrary. Similarly: - Touch the bad near the top. - Without removing the top finger, touch somewhere near the bottom. The cursor doesn't (yet) move. - Lift the top finger. The cursor shoots to the bottom. - Put down the top finger again, without lifting the bottom. The cursor shoots back up again. You can make the cursor shoot up and down just by keeping your bottom finger down and tapping the top finger. The cursor follows the top finger no matter what you do. Interestingly, this does NOT happen from side-to-side. Two touches side- by-side trigger the multi-touch gestures and don't move the cursor. - ProblemType: Bug - DistroRelease: Ubuntu 12.04 - Package: linux-image-3.13.0-29-generic 3.13.0-29.53~precise1 - ProcVersionSignature: Ubuntu 3.13.0-29.53~precise1-generic 3.13.11.2 - Uname: Linux 3.13.0-29-generic x86_64 - ApportVersion: 2.0.1-0ubuntu17.6 - Architecture: amd64 - Date: Mon Jun 9 16:59:49 2014 - MarkForUpload: True - ProcEnviron: - TERM=xterm - PATH=(custom, no user) - SHELL=/bin/bash - SourcePackage: linux-lts-trusty - UpgradeStatus: No upgrade log present (probably fresh install) - --- + This problem does not happen in Windows 7. + + --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-29-generic. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 ArecordDevices: - List of CAPTURE Hardware Devices - card 1: PCH [HDA Intel PCH], device 0: ALC292 Analog [ALC292 Analog] -Subdevices: 1/1 -Subdevice #0: subdevice #0 + List of CAPTURE Hardware Devices + card 1: PCH [HDA Intel PCH], device 0: ALC292 Analog [ALC292 Analog] + Subdevices: 1/1 + Subdevice #0: subdevice #0 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: mrksmith 2576 F pulseaudio - /dev/snd/controlC0: mrksmith 2576 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: mrksmith 2576 F pulseaudio + /dev/snd/controlC0: mrksmith 2576 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: - Card hw:0 'HDMI'/'HDA Intel HDMI at 0xf7e34000 irq 64' -Mixer name : 'Intel Haswell HDMI' -Components : 'HDA:80862807,80860101,0010' -Controls : 21 -Simple ctrls : 3 + Card hw:0 'HDMI'/'HDA Intel HDMI at 0xf7e34000 irq 64' + Mixer name : 'Intel Haswell HDMI' + Components : 'HDA:80862807,80860101,0010' + Controls : 21 + Simple ctrls : 3 Card1.Amixer.info: - Card hw:1 'PCH'/'HDA Intel PCH at 0xf7e3 irq 65' -Mixer name : 'Realtek ALC292' -Components : 'HDA:10ec0292,102805ca,0011' -Controls : 28 -Simple ctrls : 13 + Card hw:1 'PCH'/'HDA Intel PCH at 0xf7e3 irq 65' + Mixer name : 'Realtek ALC292' + Components : 'HDA:10ec0292,102805ca,0011' + Controls : 28 + Simple ctrls : 13 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=303359b5-1c66-468d-935e-a6d9bc56e4e9 MachineType: Dell Inc. Latitude E7240 MarkForUpload: True Package: linux (not installed) ProcEnviron: - TERM=xterm - PATH=(custom, no user) - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-29-generic root=/dev/mapper/vg0-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-29.53~precise1-generic 3.13.11.2 RelatedPackageVersions: - linux-restricted-modules-3.13.0-29-generic N/A - linux-backports-modules-3.13.0-29-generic N/A - linux-firmware 1.79.14 + linux-restricted-modules-3.13.0-29-generic N/A + linux-backports-modules-3.13.0-29-generic N/A + linux-firmware
[Kernel-packages] [Bug 1280668] Re: [Medion MS-7857] Computer freezes or hangs during install, boot or usage
Kelvin Gonzalez, the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel ? Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked. Thank you for your understanding. ** Tags added: oneiric ** 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/1280668 Title: [Medion MS-7857] Computer freezes or hangs during install, boot or usage Status in “linux” package in Ubuntu: Triaged Bug description: Every time I tried to install this new it was hanging during the install or even before during boot. This system is a pre-installed windows 8 (64bits). In the file /var/log/dmesg I can see the following: [ 28.119124] BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:1] [ 28.119127] Modules linked in: [ 28.119130] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.11.0-15-generic #25~precise1-Ubuntu [ 28.119132] Hardware name: MEDION MS-7857/MS-7857, BIOS M7857W08.203 01/06/2014 [ 28.119133] task: 88042962 ti: 880429628000 task.ti: 880429628000 [ 28.119134] RIP: 0010:[] [] delay_tsc+0x42/0x80 [ 28.119140] RSP: :880429629c68 EFLAGS: 0246 [ 28.119141] RAX: 001c549ce3bd RBX: 032f RCX: 549ce3bd [ 28.119142] RDX: 0cf2 RSI: 0282 RDI: 0e50 [ 28.119143] RBP: 880429629c88 R08: 2000 R09: [ 28.119144] R10: 0330 R11: 0720072007200720 R12: 0026 [ 28.119145] R13: 81ef8bc2 R14: 0246 R15: 880429629c38 [ 28.119147] FS: () GS:88043ec0() knlGS: [ 28.119148] CS: 0010 DS: ES: CR0: 8005003b [ 28.119149] CR2: 88043efff000 CR3: 01c0d000 CR4: 000407f0 [ 28.119150] Stack: [ 28.119153] 1a0e 880429629cf0 1ff0 880429579814 [ 28.119162] 880429629c98 813802bc 880429629cb8 81607e55 [ 28.119164] 880429579800 2000 880429629d28 81607f57 [ 28.119167] Call Trace: [ 28.119170] [] __const_udelay+0x2c/0x30 [ 28.119174] [] wait_on_sem+0x35/0x70 [ 28.119176] [] iommu_queue_command_sync+0xc7/0x140 [ 28.119178] [] iommu_queue_command+0x13/0x20 [ 28.119183] [] iommu_flush_all_caches+0x9d/0xf0 [ 28.119185] [] early_enable_iommus+0x61/0x160 [ 28.119189] [] ? memblock_find_dma_reserve+0x13d/0x13d [ 28.119192] [] state_next+0xbf/0x201 [ 28.119194] [] ? memblock_find_dma_reserve+0x13d/0x13d [ 28.119196] [] iommu_go_to_state+0x14/0x2f [ 28.119197] [] amd_iommu_init+0x13/0xff [ 28.119200] [] ? load_default_modules+0x9/0xb [ 28.119203] [] pci_iommu_init+0x13/0x3e [ 28.119206] [] do_one_initcall+0xfa/0x1b0 [ 28.119208] [] ? parse_args+0xd0/0x1d0 [ 28.119211] [] ? do_early_param+0x87/0x87 [ 28.119213] [] do_basic_setup+0x96/0xb9 [ 28.119215] [] ? do_early_param+0x87/0x87 [ 28.119218] [] ? sched_init_smp+0x119/0x11b [ 28.119220] [] kernel_init_freeable+0xb8/0x131 [ 28.119224] [] ? rest_init+0x80/0x80 [ 28.119226] [] kernel_init+0xe/0xf0 [ 28.119229] [] ret_from_fork+0x7c/0xb0 [ 28.119231] [] ? rest_init+0x80/0x80 [ 28.119232] Code: 25 64 b0 00 00 0f ae f0 66 66 90 e8 c9 b0 c9 ff 66 90 41 89 c4 eb 11 66 90 f3 90 65 8b 1c 25 64 b0 00 00 41 39 dd 75 20 0f ae f0 <66> 66 90 e8 a6 b0 c9 ff 66 90 89 c2 44 29 e2 44 39 f2 72 da 5b [ 28.219649] AMD-Vi: Completion-Wait loop timed out WORKAROUND: I was able to complete the install passing the following kernel parameter, then the computer boots fine but hangs for between 25 to 2 minutes and then continues working. I would expect the computer not to hang: noapic --- ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.11.0-15-generic 3.11.0-15.25~precise1 [modified: boot/vmlinuz-3.11.0-15-generic] ProcVersionSignature: Ubuntu 3.11.0-15.25~precise1-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.11.0-15-generic. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kelvin 1952 F pulseaudio /dev/snd/controlC0: kelvin 1952 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb0 irq 10' Mixer name : 'Realtek ALC887-VD' Components : 'HDA:10ec0887,14627857,00100302' Cont
[Kernel-packages] [Bug 1328392] Re: [Asus X550LD] Touchpad not working - Ubuntu 14.04
gsoundsgood, could you please test the latest upstream kernel available from the first line at the top page (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: kernel-fixed-upstream kernel-fixed-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. For example: kernel-fixed-upstream-3.15 This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag: needs-upstream-testing If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER As well, please remove the tag: needs-upstream-testing Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Tags removed: bios-outdated-306 ** Tags added: latest-bios-306 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1328392 Title: [Asus X550LD] Touchpad not working - Ubuntu 14.04 Status in “linux” package in Ubuntu: Triaged Bug description: Touchpad on the Asus X550LD is not working on Ubuntu 14.04 with either default or mainline kernel 3.15.0-031500-generic. Cursor does make some movements if you insist toying and clicking on the touchpad, but only seldomly (just using it normally often would produce no move), and in a direction that apparently has no relation with touch. Generally moves towards bottom, bottom/left, but insisting one can have patchy movements in other directions. However, clicking has no effect. Mouse connected with USB works normally, until you try to use the touchpad. If you touch the touchpad, the cursor mostly keeps on moving as per the mouse, but click mostly does not work. Logging out and logging in or restarting fixes the problem. WORKAROUND: Use external USB mouse but don't touch the touchpad. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: g 1530 F pulseaudio /dev/snd/controlC0: g 1530 F pulseaudio CurrentDesktop: GNOME Date: Tue Jun 10 08:18:41 2014 HibernationDevice: RESUME=UUID=205b0b44-7997-42f7-806d-3b367ebfdceb InstallationDate: Installed on 2014-06-09 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: ASUSTeK COMPUTER INC. X550LD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic.efi.signed root=UUID=ee58b2b6-1d8c-4137-beca-6a52a4634265 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LD.300:bd01/17/2014:svnASUSTeKCOMPUTERINC.:pnX550LD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550LD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328727] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1328727/+attachment/4129324/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1328727 Title: s2disk/hibernate hangs during saving of image data Status in “linux” package in Ubuntu: Confirmed Bug description: Hibernation with the pm-hibernate command works fine on a freshly booted system, but when a significant portion of the RAM is in use, for instance by starting gimp, google-chrome and firefox at the same time, it stalls at the start of the saving of the image data: s2disk: Snapshotting system s2disk: System snapshot ready. Preparing to write s2disk: Image size: 441652 kilobytes s2disk: Free swap: 1798624 kilobytes s2disk: Saving 110413 image data pages (press backspace to abort) ... 0% The system is not usable at this point, although alt-sysrq still works. It looks like some sort of deadlock. The system is an Asus eeePC 1000HE with 2GB RAM and a 2GB swap partition and a Samsung SSD 840 EVO. The Ubuntu release is 14.04 LTS. The kernel package is linux-image-3.13.0-27-generic version 3.13.0-27.50 (32 bit). I found a kernel bug report that looks exactly the same: https://bugzilla.kernel.org/show_bug.cgi?id=75101 In that bug report, the problem was bisected to commit a1c3bfb2. This commit is part of the 3.14 kernel, but was apparently backported to the 3.13 Ubuntu kernel. I've rebuild the kernel package with this commit reverted, and it seems to fix this issue for me. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dick 1719 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c6b78f80-b4a1-4b1a-91b4-8ae5c41b36f4 InstallationDate: Installed on 2013-04-28 (408 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: ASUSTeK Computer INC. 1000HE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=54684f57-2a33-403f-ae4d-ad6b3d0168ea ro acpi_osi=Linux acpi_backlight=vendor quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-27.50hib-generic 3.13.11 RelatedPackageVersions: linux-restricted-modules-3.13.0-27-generic N/A linux-backports-modules-3.13.0-27-generic N/A linux-firmware 1.127.2 Tags: trusty Uname: Linux 3.13.0-27-generic i686 UpgradeStatus: Upgraded to trusty on 2014-04-26 (45 days ago) UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/24/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1000HE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd06/24/2009:svnASUSTeKComputerINC.:pn1000HE:pvrx.x:rvnASUSTeKComputerINC.:rn1000HE:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 1000HE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328313] Re: [Dell Latitude E7240] Alps Touchpad acts erratically when multi-touch is vertical, not horizontal
I just confirmed on a coworker's laptop, same hardware but with Windows
7, does not have this problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1328313
Title:
[Dell Latitude E7240] Alps Touchpad acts erratically when multi-touch
is vertical, not horizontal
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
I'm on a Dell Latitude E7240 running 12.04 LTS and my touch pad acts
erratically. It happens because my middle and ring fingers accidentally touch
the top edge of the pad while my pointer finger is moving the cursor. I can
reproduce this on purpose by running "xinput --test [device number]" and
watching the events while I do the following:
- Touch the pad near the middle or bottom. The cursor moves slightly as my
finger wiggles around.
- Without removing the first finger, touch the pad again with a second finger
above the first finger. The cursor shoots up to a[1]=0 (which is the y
position).
- Without removing the first finger, remove the second (top) finger. The
cursor shoots back down to a[1]= Sometimes it takes it all
the way to the bottom of the screen, sometimes it goes back to where it was, or
somewhere else. I haven't been able to figure out how it decides what to go
back to.
With this, while I touching with my pointer finger and my middle or
ring finger accidentally touch the pad at the top, the cursor shoots
where I don't want it. Then when my middle/ring finger leaves the pad
(usually because I started cursing (get it?) at my cursor), it shoots
back down again somewhere completely arbitrary.
Similarly:
- Touch the bad near the top.
- Without removing the top finger, touch somewhere near the bottom. The
cursor doesn't (yet) move.
- Lift the top finger. The cursor shoots to the bottom.
- Put down the top finger again, without lifting the bottom. The cursor
shoots back up again.
You can make the cursor shoot up and down just by keeping your bottom
finger down and tapping the top finger. The cursor follows the top
finger no matter what you do.
Interestingly, this does NOT happen from side-to-side. Two touches
side-by-side trigger the multi-touch gestures and don't move the
cursor.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.13.0-29-generic 3.13.0-29.53~precise1
ProcVersionSignature: Ubuntu 3.13.0-29.53~precise1-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
Date: Mon Jun 9 16:59:49 2014
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
SHELL=/bin/bash
SourcePackage: linux-lts-trusty
UpgradeStatus: No upgrade log present (probably fresh install)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.13.0-29-generic.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: PCH [HDA Intel PCH], device 0: ALC292 Analog [ALC292 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: mrksmith 2576 F pulseaudio
/dev/snd/controlC0: mrksmith 2576 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'HDMI'/'HDA Intel HDMI at 0xf7e34000 irq 64'
Mixer name : 'Intel Haswell HDMI'
Components : 'HDA:80862807,80860101,0010'
Controls : 21
Simple ctrls : 3
Card1.Amixer.info:
Card hw:1 'PCH'/'HDA Intel PCH at 0xf7e3 irq 65'
Mixer name : 'Realtek ALC292'
Components : 'HDA:10ec0292,102805ca,0011'
Controls : 28
Simple ctrls : 13
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=303359b5-1c66-468d-935e-a6d9bc56e4e9
MachineType: Dell Inc. Latitude E7240
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-29-generic
root=/dev/mapper/vg0-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-29.53~precise1-generic 3.13.11.2
RelatedPackageVersions:
linux-restricted-modules-3.13.0-29-generic N/A
linux-backports-modules-3.13.0-29-generic N/A
linux-firmware 1.79.14
Tags: precise running-unity
Uname: Linux 3.13.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout lpadmin plugdev sambashare sudo
dmi.bios.date: 02/18/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.asset.tag: 1201037379
dmi.board.name: 0531FD
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.asset.tag: 1201037379
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA08
[Kernel-packages] [Bug 1328392] Re: [Asus X550LD] Touchpad not working - Ubuntu 14.04
gsoundsgood, the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel ? Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked. Thank you for your understanding. ** Changed in: linux (Ubuntu) Importance: Low => High ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1328392 Title: [Asus X550LD] Touchpad not working - Ubuntu 14.04 Status in “linux” package in Ubuntu: Triaged Bug description: Touchpad on the Asus X550LD is not working on Ubuntu 14.04 with either default or mainline kernel 3.15.0-031500-generic. Cursor does make some movements if you insist toying and clicking on the touchpad, but only seldomly (just using it normally often would produce no move), and in a direction that apparently has no relation with touch. Generally moves towards bottom, bottom/left, but insisting one can have patchy movements in other directions. However, clicking has no effect. Mouse connected with USB works normally, until you try to use the touchpad. If you touch the touchpad, the cursor mostly keeps on moving as per the mouse, but click mostly does not work. Logging out and logging in or restarting fixes the problem. WORKAROUND: Use external USB mouse but don't touch the touchpad. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: g 1530 F pulseaudio /dev/snd/controlC0: g 1530 F pulseaudio CurrentDesktop: GNOME Date: Tue Jun 10 08:18:41 2014 HibernationDevice: RESUME=UUID=205b0b44-7997-42f7-806d-3b367ebfdceb InstallationDate: Installed on 2014-06-09 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: ASUSTeK COMPUTER INC. X550LD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic.efi.signed root=UUID=ee58b2b6-1d8c-4137-beca-6a52a4634265 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LD.300:bd01/17/2014:svnASUSTeKCOMPUTERINC.:pnX550LD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550LD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1327908] Re: HP NC375T / phanfw.bin: firmware is older than flash / Direct firmware load failed with error -2 / HP firmware is newer in cards
JSE, could you please do an apport-collect 1327908 when booted into the default (not mainline) kernel? ** 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/1327908 Title: HP NC375T / phanfw.bin: firmware is older than flash / Direct firmware load failed with error -2 / HP firmware is newer in cards Status in “linux” package in Ubuntu: Incomplete Bug description: HP has a newer firmware on their NC375T server nics: 4.0.593 This generates an error at the startup of Ubuntu Server 14.04 LTS The version of phanfw.bin seems to be older. [ 16.573260] QLogic/NetXen Network Driver v4.0.82 [ 16.87] netxen_nic :07:00.0: 2MB memory map [ 16.812455] netxen_nic :07:00.0: phanfw.bin: firmware is older than flash [ 16.818949] netxen_nic :07:00.0: Direct firmware load failed with error -2 [ 16.818950] netxen_nic :07:00.0: Falling back to user helper [ 23.138390] netxen_nic :07:00.0: loading firmware from flash [ 27.586070] netxen_nic :07:00.0: Gen2 strapping detected [ 30.185964] netxen_nic :07:00.0: using 64-bit dma mask [ 30.373956] netxen_nic: Quad Gig LP Board S/N TI13BK1960 Chip rev 0x42 [ 30.450969] netxen_nic :07:00.0: Driver v4.0.82, firmware v4.0.593 [legacy] [ 39.718557] netxen_nic :07:00.0: irq 67 for MSI/MSI-X [ 39.718561] netxen_nic :07:00.0: irq 68 for MSI/MSI-X [ 39.718564] netxen_nic :07:00.0: irq 69 for MSI/MSI-X [ 39.718567] netxen_nic :07:00.0: irq 70 for MSI/MSI-X [ 39.718605] netxen_nic :07:00.0: using msi-x interrupts [ 39.780399] netxen_nic :07:00.0: non ULA adapter [ 39.841095] netxen_nic :07:00.0: eth0: GbE port initialized [ 39.901172] netxen_nic :07:00.1: 2MB memory map [ 39.959403] netxen_nic :07:00.1: using 64-bit dma mask [ 40.117279] netxen_nic :07:00.1: Driver v4.0.82, firmware v4.0.593 [legacy] [ 40.174172] netxen_nic :07:00.1: irq 71 for MSI/MSI-X [ 40.174175] netxen_nic :07:00.1: irq 72 for MSI/MSI-X [ 40.174178] netxen_nic :07:00.1: irq 73 for MSI/MSI-X [ 40.174181] netxen_nic :07:00.1: irq 74 for MSI/MSI-X [ 40.174209] netxen_nic :07:00.1: using msi-x interrupts [ 40.229992] netxen_nic :07:00.1: eth1: GbE port initialized [ 40.284766] netxen_nic :07:00.2: 2MB memory map [ 40.339836] netxen_nic :07:00.2: using 64-bit dma mask [ 40.465258] netxen_nic :07:00.2: Driver v4.0.82, firmware v4.0.593 [legacy] [ 40.522359] netxen_nic :07:00.2: irq 75 for MSI/MSI-X [ 40.522363] netxen_nic :07:00.2: irq 76 for MSI/MSI-X [ 40.522365] netxen_nic :07:00.2: irq 77 for MSI/MSI-X [ 40.522368] netxen_nic :07:00.2: irq 78 for MSI/MSI-X [ 40.522392] netxen_nic :07:00.2: using msi-x interrupts [ 40.578742] netxen_nic :07:00.2: eth2: GbE port initialized [ 40.634802] netxen_nic :07:00.3: 2MB memory map [ 40.690423] netxen_nic :07:00.3: using 64-bit dma mask [ 40.825233] netxen_nic :07:00.3: Driver v4.0.82, firmware v4.0.593 [legacy] [ 40.882915] netxen_nic :07:00.3: irq 79 for MSI/MSI-X [ 40.882919] netxen_nic :07:00.3: irq 80 for MSI/MSI-X [ 40.882922] netxen_nic :07:00.3: irq 81 for MSI/MSI-X [ 40.882925] netxen_nic :07:00.3: irq 82 for MSI/MSI-X [ 40.882951] netxen_nic :07:00.3: using msi-x interrupts [ 40.939825] netxen_nic :07:00.3: eth3: GbE port initialized # ethtool -i p4p1 driver: netxen_nic version: 4.0.82 firmware-version: 4.0.593 bus-info: :07:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no # ./nxflash.bin -i p4p1 --info Board Type: 0x24 (NC375T PCI Express Quad Port Gigabit Server Adapter) Board Chip Rev: B2 Serial Id: TI13BK1960 Efuse ID: 0x Firmware version(on Flash): 4.0.593 Active Firmware version: 4.0.593 Driver version: 0.0.0 BIOS version: 2.1.0 MAC Addr 0: 78:AC:C0:10:F9:DC Subsystem ID: 0x1740103c PXE Status 0: Disabled WOL Status 0: Disabled # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3 Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x8 Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) 00:1c.2 PCI bridge: Intel C
[Kernel-packages] [Bug 1328727] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1328727/+attachment/4129315/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1328727 Title: s2disk/hibernate hangs during saving of image data Status in “linux” package in Ubuntu: Confirmed Bug description: Hibernation with the pm-hibernate command works fine on a freshly booted system, but when a significant portion of the RAM is in use, for instance by starting gimp, google-chrome and firefox at the same time, it stalls at the start of the saving of the image data: s2disk: Snapshotting system s2disk: System snapshot ready. Preparing to write s2disk: Image size: 441652 kilobytes s2disk: Free swap: 1798624 kilobytes s2disk: Saving 110413 image data pages (press backspace to abort) ... 0% The system is not usable at this point, although alt-sysrq still works. It looks like some sort of deadlock. The system is an Asus eeePC 1000HE with 2GB RAM and a 2GB swap partition and a Samsung SSD 840 EVO. The Ubuntu release is 14.04 LTS. The kernel package is linux-image-3.13.0-27-generic version 3.13.0-27.50 (32 bit). I found a kernel bug report that looks exactly the same: https://bugzilla.kernel.org/show_bug.cgi?id=75101 In that bug report, the problem was bisected to commit a1c3bfb2. This commit is part of the 3.14 kernel, but was apparently backported to the 3.13 Ubuntu kernel. I've rebuild the kernel package with this commit reverted, and it seems to fix this issue for me. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dick 1719 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c6b78f80-b4a1-4b1a-91b4-8ae5c41b36f4 InstallationDate: Installed on 2013-04-28 (408 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: ASUSTeK Computer INC. 1000HE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=54684f57-2a33-403f-ae4d-ad6b3d0168ea ro acpi_osi=Linux acpi_backlight=vendor quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-27.50hib-generic 3.13.11 RelatedPackageVersions: linux-restricted-modules-3.13.0-27-generic N/A linux-backports-modules-3.13.0-27-generic N/A linux-firmware 1.127.2 Tags: trusty Uname: Linux 3.13.0-27-generic i686 UpgradeStatus: Upgraded to trusty on 2014-04-26 (45 days ago) UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/24/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1000HE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd06/24/2009:svnASUSTeKComputerINC.:pn1000HE:pvrx.x:rvnASUSTeKComputerINC.:rn1000HE:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 1000HE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328727] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1328727/+attachment/4129312/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1328727 Title: s2disk/hibernate hangs during saving of image data Status in “linux” package in Ubuntu: Confirmed Bug description: Hibernation with the pm-hibernate command works fine on a freshly booted system, but when a significant portion of the RAM is in use, for instance by starting gimp, google-chrome and firefox at the same time, it stalls at the start of the saving of the image data: s2disk: Snapshotting system s2disk: System snapshot ready. Preparing to write s2disk: Image size: 441652 kilobytes s2disk: Free swap: 1798624 kilobytes s2disk: Saving 110413 image data pages (press backspace to abort) ... 0% The system is not usable at this point, although alt-sysrq still works. It looks like some sort of deadlock. The system is an Asus eeePC 1000HE with 2GB RAM and a 2GB swap partition and a Samsung SSD 840 EVO. The Ubuntu release is 14.04 LTS. The kernel package is linux-image-3.13.0-27-generic version 3.13.0-27.50 (32 bit). I found a kernel bug report that looks exactly the same: https://bugzilla.kernel.org/show_bug.cgi?id=75101 In that bug report, the problem was bisected to commit a1c3bfb2. This commit is part of the 3.14 kernel, but was apparently backported to the 3.13 Ubuntu kernel. I've rebuild the kernel package with this commit reverted, and it seems to fix this issue for me. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dick 1719 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c6b78f80-b4a1-4b1a-91b4-8ae5c41b36f4 InstallationDate: Installed on 2013-04-28 (408 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: ASUSTeK Computer INC. 1000HE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=54684f57-2a33-403f-ae4d-ad6b3d0168ea ro acpi_osi=Linux acpi_backlight=vendor quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-27.50hib-generic 3.13.11 RelatedPackageVersions: linux-restricted-modules-3.13.0-27-generic N/A linux-backports-modules-3.13.0-27-generic N/A linux-firmware 1.127.2 Tags: trusty Uname: Linux 3.13.0-27-generic i686 UpgradeStatus: Upgraded to trusty on 2014-04-26 (45 days ago) UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/24/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1000HE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd06/24/2009:svnASUSTeKComputerINC.:pn1000HE:pvrx.x:rvnASUSTeKComputerINC.:rn1000HE:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 1000HE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328727] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1328727/+attachment/4129323/+files/UdevLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1328727 Title: s2disk/hibernate hangs during saving of image data Status in “linux” package in Ubuntu: Confirmed Bug description: Hibernation with the pm-hibernate command works fine on a freshly booted system, but when a significant portion of the RAM is in use, for instance by starting gimp, google-chrome and firefox at the same time, it stalls at the start of the saving of the image data: s2disk: Snapshotting system s2disk: System snapshot ready. Preparing to write s2disk: Image size: 441652 kilobytes s2disk: Free swap: 1798624 kilobytes s2disk: Saving 110413 image data pages (press backspace to abort) ... 0% The system is not usable at this point, although alt-sysrq still works. It looks like some sort of deadlock. The system is an Asus eeePC 1000HE with 2GB RAM and a 2GB swap partition and a Samsung SSD 840 EVO. The Ubuntu release is 14.04 LTS. The kernel package is linux-image-3.13.0-27-generic version 3.13.0-27.50 (32 bit). I found a kernel bug report that looks exactly the same: https://bugzilla.kernel.org/show_bug.cgi?id=75101 In that bug report, the problem was bisected to commit a1c3bfb2. This commit is part of the 3.14 kernel, but was apparently backported to the 3.13 Ubuntu kernel. I've rebuild the kernel package with this commit reverted, and it seems to fix this issue for me. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dick 1719 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c6b78f80-b4a1-4b1a-91b4-8ae5c41b36f4 InstallationDate: Installed on 2013-04-28 (408 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: ASUSTeK Computer INC. 1000HE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=54684f57-2a33-403f-ae4d-ad6b3d0168ea ro acpi_osi=Linux acpi_backlight=vendor quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-27.50hib-generic 3.13.11 RelatedPackageVersions: linux-restricted-modules-3.13.0-27-generic N/A linux-backports-modules-3.13.0-27-generic N/A linux-firmware 1.127.2 Tags: trusty Uname: Linux 3.13.0-27-generic i686 UpgradeStatus: Upgraded to trusty on 2014-04-26 (45 days ago) UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/24/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1000HE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd06/24/2009:svnASUSTeKComputerINC.:pn1000HE:pvrx.x:rvnASUSTeKComputerINC.:rn1000HE:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 1000HE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328727] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1328727/+attachment/4129322/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1328727 Title: s2disk/hibernate hangs during saving of image data Status in “linux” package in Ubuntu: Confirmed Bug description: Hibernation with the pm-hibernate command works fine on a freshly booted system, but when a significant portion of the RAM is in use, for instance by starting gimp, google-chrome and firefox at the same time, it stalls at the start of the saving of the image data: s2disk: Snapshotting system s2disk: System snapshot ready. Preparing to write s2disk: Image size: 441652 kilobytes s2disk: Free swap: 1798624 kilobytes s2disk: Saving 110413 image data pages (press backspace to abort) ... 0% The system is not usable at this point, although alt-sysrq still works. It looks like some sort of deadlock. The system is an Asus eeePC 1000HE with 2GB RAM and a 2GB swap partition and a Samsung SSD 840 EVO. The Ubuntu release is 14.04 LTS. The kernel package is linux-image-3.13.0-27-generic version 3.13.0-27.50 (32 bit). I found a kernel bug report that looks exactly the same: https://bugzilla.kernel.org/show_bug.cgi?id=75101 In that bug report, the problem was bisected to commit a1c3bfb2. This commit is part of the 3.14 kernel, but was apparently backported to the 3.13 Ubuntu kernel. I've rebuild the kernel package with this commit reverted, and it seems to fix this issue for me. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dick 1719 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c6b78f80-b4a1-4b1a-91b4-8ae5c41b36f4 InstallationDate: Installed on 2013-04-28 (408 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: ASUSTeK Computer INC. 1000HE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=54684f57-2a33-403f-ae4d-ad6b3d0168ea ro acpi_osi=Linux acpi_backlight=vendor quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-27.50hib-generic 3.13.11 RelatedPackageVersions: linux-restricted-modules-3.13.0-27-generic N/A linux-backports-modules-3.13.0-27-generic N/A linux-firmware 1.127.2 Tags: trusty Uname: Linux 3.13.0-27-generic i686 UpgradeStatus: Upgraded to trusty on 2014-04-26 (45 days ago) UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/24/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1000HE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd06/24/2009:svnASUSTeKComputerINC.:pn1000HE:pvrx.x:rvnASUSTeKComputerINC.:rn1000HE:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 1000HE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328727] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1328727/+attachment/4129319/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1328727 Title: s2disk/hibernate hangs during saving of image data Status in “linux” package in Ubuntu: Confirmed Bug description: Hibernation with the pm-hibernate command works fine on a freshly booted system, but when a significant portion of the RAM is in use, for instance by starting gimp, google-chrome and firefox at the same time, it stalls at the start of the saving of the image data: s2disk: Snapshotting system s2disk: System snapshot ready. Preparing to write s2disk: Image size: 441652 kilobytes s2disk: Free swap: 1798624 kilobytes s2disk: Saving 110413 image data pages (press backspace to abort) ... 0% The system is not usable at this point, although alt-sysrq still works. It looks like some sort of deadlock. The system is an Asus eeePC 1000HE with 2GB RAM and a 2GB swap partition and a Samsung SSD 840 EVO. The Ubuntu release is 14.04 LTS. The kernel package is linux-image-3.13.0-27-generic version 3.13.0-27.50 (32 bit). I found a kernel bug report that looks exactly the same: https://bugzilla.kernel.org/show_bug.cgi?id=75101 In that bug report, the problem was bisected to commit a1c3bfb2. This commit is part of the 3.14 kernel, but was apparently backported to the 3.13 Ubuntu kernel. I've rebuild the kernel package with this commit reverted, and it seems to fix this issue for me. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dick 1719 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c6b78f80-b4a1-4b1a-91b4-8ae5c41b36f4 InstallationDate: Installed on 2013-04-28 (408 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: ASUSTeK Computer INC. 1000HE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=54684f57-2a33-403f-ae4d-ad6b3d0168ea ro acpi_osi=Linux acpi_backlight=vendor quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-27.50hib-generic 3.13.11 RelatedPackageVersions: linux-restricted-modules-3.13.0-27-generic N/A linux-backports-modules-3.13.0-27-generic N/A linux-firmware 1.127.2 Tags: trusty Uname: Linux 3.13.0-27-generic i686 UpgradeStatus: Upgraded to trusty on 2014-04-26 (45 days ago) UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/24/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1000HE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd06/24/2009:svnASUSTeKComputerINC.:pn1000HE:pvrx.x:rvnASUSTeKComputerINC.:rn1000HE:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 1000HE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328727] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1328727/+attachment/4129314/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1328727 Title: s2disk/hibernate hangs during saving of image data Status in “linux” package in Ubuntu: Confirmed Bug description: Hibernation with the pm-hibernate command works fine on a freshly booted system, but when a significant portion of the RAM is in use, for instance by starting gimp, google-chrome and firefox at the same time, it stalls at the start of the saving of the image data: s2disk: Snapshotting system s2disk: System snapshot ready. Preparing to write s2disk: Image size: 441652 kilobytes s2disk: Free swap: 1798624 kilobytes s2disk: Saving 110413 image data pages (press backspace to abort) ... 0% The system is not usable at this point, although alt-sysrq still works. It looks like some sort of deadlock. The system is an Asus eeePC 1000HE with 2GB RAM and a 2GB swap partition and a Samsung SSD 840 EVO. The Ubuntu release is 14.04 LTS. The kernel package is linux-image-3.13.0-27-generic version 3.13.0-27.50 (32 bit). I found a kernel bug report that looks exactly the same: https://bugzilla.kernel.org/show_bug.cgi?id=75101 In that bug report, the problem was bisected to commit a1c3bfb2. This commit is part of the 3.14 kernel, but was apparently backported to the 3.13 Ubuntu kernel. I've rebuild the kernel package with this commit reverted, and it seems to fix this issue for me. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dick 1719 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c6b78f80-b4a1-4b1a-91b4-8ae5c41b36f4 InstallationDate: Installed on 2013-04-28 (408 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: ASUSTeK Computer INC. 1000HE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=54684f57-2a33-403f-ae4d-ad6b3d0168ea ro acpi_osi=Linux acpi_backlight=vendor quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-27.50hib-generic 3.13.11 RelatedPackageVersions: linux-restricted-modules-3.13.0-27-generic N/A linux-backports-modules-3.13.0-27-generic N/A linux-firmware 1.127.2 Tags: trusty Uname: Linux 3.13.0-27-generic i686 UpgradeStatus: Upgraded to trusty on 2014-04-26 (45 days ago) UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/24/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1000HE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd06/24/2009:svnASUSTeKComputerINC.:pn1000HE:pvrx.x:rvnASUSTeKComputerINC.:rn1000HE:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 1000HE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328727] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1328727/+attachment/4129316/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1328727 Title: s2disk/hibernate hangs during saving of image data Status in “linux” package in Ubuntu: Confirmed Bug description: Hibernation with the pm-hibernate command works fine on a freshly booted system, but when a significant portion of the RAM is in use, for instance by starting gimp, google-chrome and firefox at the same time, it stalls at the start of the saving of the image data: s2disk: Snapshotting system s2disk: System snapshot ready. Preparing to write s2disk: Image size: 441652 kilobytes s2disk: Free swap: 1798624 kilobytes s2disk: Saving 110413 image data pages (press backspace to abort) ... 0% The system is not usable at this point, although alt-sysrq still works. It looks like some sort of deadlock. The system is an Asus eeePC 1000HE with 2GB RAM and a 2GB swap partition and a Samsung SSD 840 EVO. The Ubuntu release is 14.04 LTS. The kernel package is linux-image-3.13.0-27-generic version 3.13.0-27.50 (32 bit). I found a kernel bug report that looks exactly the same: https://bugzilla.kernel.org/show_bug.cgi?id=75101 In that bug report, the problem was bisected to commit a1c3bfb2. This commit is part of the 3.14 kernel, but was apparently backported to the 3.13 Ubuntu kernel. I've rebuild the kernel package with this commit reverted, and it seems to fix this issue for me. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dick 1719 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c6b78f80-b4a1-4b1a-91b4-8ae5c41b36f4 InstallationDate: Installed on 2013-04-28 (408 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: ASUSTeK Computer INC. 1000HE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=54684f57-2a33-403f-ae4d-ad6b3d0168ea ro acpi_osi=Linux acpi_backlight=vendor quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-27.50hib-generic 3.13.11 RelatedPackageVersions: linux-restricted-modules-3.13.0-27-generic N/A linux-backports-modules-3.13.0-27-generic N/A linux-firmware 1.127.2 Tags: trusty Uname: Linux 3.13.0-27-generic i686 UpgradeStatus: Upgraded to trusty on 2014-04-26 (45 days ago) UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/24/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1000HE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd06/24/2009:svnASUSTeKComputerINC.:pn1000HE:pvrx.x:rvnASUSTeKComputerINC.:rn1000HE:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 1000HE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328727] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1328727/+attachment/4129313/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1328727 Title: s2disk/hibernate hangs during saving of image data Status in “linux” package in Ubuntu: Confirmed Bug description: Hibernation with the pm-hibernate command works fine on a freshly booted system, but when a significant portion of the RAM is in use, for instance by starting gimp, google-chrome and firefox at the same time, it stalls at the start of the saving of the image data: s2disk: Snapshotting system s2disk: System snapshot ready. Preparing to write s2disk: Image size: 441652 kilobytes s2disk: Free swap: 1798624 kilobytes s2disk: Saving 110413 image data pages (press backspace to abort) ... 0% The system is not usable at this point, although alt-sysrq still works. It looks like some sort of deadlock. The system is an Asus eeePC 1000HE with 2GB RAM and a 2GB swap partition and a Samsung SSD 840 EVO. The Ubuntu release is 14.04 LTS. The kernel package is linux-image-3.13.0-27-generic version 3.13.0-27.50 (32 bit). I found a kernel bug report that looks exactly the same: https://bugzilla.kernel.org/show_bug.cgi?id=75101 In that bug report, the problem was bisected to commit a1c3bfb2. This commit is part of the 3.14 kernel, but was apparently backported to the 3.13 Ubuntu kernel. I've rebuild the kernel package with this commit reverted, and it seems to fix this issue for me. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dick 1719 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c6b78f80-b4a1-4b1a-91b4-8ae5c41b36f4 InstallationDate: Installed on 2013-04-28 (408 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: ASUSTeK Computer INC. 1000HE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=54684f57-2a33-403f-ae4d-ad6b3d0168ea ro acpi_osi=Linux acpi_backlight=vendor quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-27.50hib-generic 3.13.11 RelatedPackageVersions: linux-restricted-modules-3.13.0-27-generic N/A linux-backports-modules-3.13.0-27-generic N/A linux-firmware 1.127.2 Tags: trusty Uname: Linux 3.13.0-27-generic i686 UpgradeStatus: Upgraded to trusty on 2014-04-26 (45 days ago) UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/24/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1000HE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd06/24/2009:svnASUSTeKComputerINC.:pn1000HE:pvrx.x:rvnASUSTeKComputerINC.:rn1000HE:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 1000HE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328727] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1328727/+attachment/4129311/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1328727 Title: s2disk/hibernate hangs during saving of image data Status in “linux” package in Ubuntu: Confirmed Bug description: Hibernation with the pm-hibernate command works fine on a freshly booted system, but when a significant portion of the RAM is in use, for instance by starting gimp, google-chrome and firefox at the same time, it stalls at the start of the saving of the image data: s2disk: Snapshotting system s2disk: System snapshot ready. Preparing to write s2disk: Image size: 441652 kilobytes s2disk: Free swap: 1798624 kilobytes s2disk: Saving 110413 image data pages (press backspace to abort) ... 0% The system is not usable at this point, although alt-sysrq still works. It looks like some sort of deadlock. The system is an Asus eeePC 1000HE with 2GB RAM and a 2GB swap partition and a Samsung SSD 840 EVO. The Ubuntu release is 14.04 LTS. The kernel package is linux-image-3.13.0-27-generic version 3.13.0-27.50 (32 bit). I found a kernel bug report that looks exactly the same: https://bugzilla.kernel.org/show_bug.cgi?id=75101 In that bug report, the problem was bisected to commit a1c3bfb2. This commit is part of the 3.14 kernel, but was apparently backported to the 3.13 Ubuntu kernel. I've rebuild the kernel package with this commit reverted, and it seems to fix this issue for me. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dick 1719 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c6b78f80-b4a1-4b1a-91b4-8ae5c41b36f4 InstallationDate: Installed on 2013-04-28 (408 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: ASUSTeK Computer INC. 1000HE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=54684f57-2a33-403f-ae4d-ad6b3d0168ea ro acpi_osi=Linux acpi_backlight=vendor quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-27.50hib-generic 3.13.11 RelatedPackageVersions: linux-restricted-modules-3.13.0-27-generic N/A linux-backports-modules-3.13.0-27-generic N/A linux-firmware 1.127.2 Tags: trusty Uname: Linux 3.13.0-27-generic i686 UpgradeStatus: Upgraded to trusty on 2014-04-26 (45 days ago) UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/24/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1000HE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd06/24/2009:svnASUSTeKComputerINC.:pn1000HE:pvrx.x:rvnASUSTeKComputerINC.:rn1000HE:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 1000HE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328727] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1328727/+attachment/4129317/+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/1328727 Title: s2disk/hibernate hangs during saving of image data Status in “linux” package in Ubuntu: Confirmed Bug description: Hibernation with the pm-hibernate command works fine on a freshly booted system, but when a significant portion of the RAM is in use, for instance by starting gimp, google-chrome and firefox at the same time, it stalls at the start of the saving of the image data: s2disk: Snapshotting system s2disk: System snapshot ready. Preparing to write s2disk: Image size: 441652 kilobytes s2disk: Free swap: 1798624 kilobytes s2disk: Saving 110413 image data pages (press backspace to abort) ... 0% The system is not usable at this point, although alt-sysrq still works. It looks like some sort of deadlock. The system is an Asus eeePC 1000HE with 2GB RAM and a 2GB swap partition and a Samsung SSD 840 EVO. The Ubuntu release is 14.04 LTS. The kernel package is linux-image-3.13.0-27-generic version 3.13.0-27.50 (32 bit). I found a kernel bug report that looks exactly the same: https://bugzilla.kernel.org/show_bug.cgi?id=75101 In that bug report, the problem was bisected to commit a1c3bfb2. This commit is part of the 3.14 kernel, but was apparently backported to the 3.13 Ubuntu kernel. I've rebuild the kernel package with this commit reverted, and it seems to fix this issue for me. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dick 1719 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c6b78f80-b4a1-4b1a-91b4-8ae5c41b36f4 InstallationDate: Installed on 2013-04-28 (408 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: ASUSTeK Computer INC. 1000HE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=54684f57-2a33-403f-ae4d-ad6b3d0168ea ro acpi_osi=Linux acpi_backlight=vendor quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-27.50hib-generic 3.13.11 RelatedPackageVersions: linux-restricted-modules-3.13.0-27-generic N/A linux-backports-modules-3.13.0-27-generic N/A linux-firmware 1.127.2 Tags: trusty Uname: Linux 3.13.0-27-generic i686 UpgradeStatus: Upgraded to trusty on 2014-04-26 (45 days ago) UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/24/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1000HE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd06/24/2009:svnASUSTeKComputerINC.:pn1000HE:pvrx.x:rvnASUSTeKComputerINC.:rn1000HE:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 1000HE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328727] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1328727/+attachment/4129310/+files/BootDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1328727 Title: s2disk/hibernate hangs during saving of image data Status in “linux” package in Ubuntu: Confirmed Bug description: Hibernation with the pm-hibernate command works fine on a freshly booted system, but when a significant portion of the RAM is in use, for instance by starting gimp, google-chrome and firefox at the same time, it stalls at the start of the saving of the image data: s2disk: Snapshotting system s2disk: System snapshot ready. Preparing to write s2disk: Image size: 441652 kilobytes s2disk: Free swap: 1798624 kilobytes s2disk: Saving 110413 image data pages (press backspace to abort) ... 0% The system is not usable at this point, although alt-sysrq still works. It looks like some sort of deadlock. The system is an Asus eeePC 1000HE with 2GB RAM and a 2GB swap partition and a Samsung SSD 840 EVO. The Ubuntu release is 14.04 LTS. The kernel package is linux-image-3.13.0-27-generic version 3.13.0-27.50 (32 bit). I found a kernel bug report that looks exactly the same: https://bugzilla.kernel.org/show_bug.cgi?id=75101 In that bug report, the problem was bisected to commit a1c3bfb2. This commit is part of the 3.14 kernel, but was apparently backported to the 3.13 Ubuntu kernel. I've rebuild the kernel package with this commit reverted, and it seems to fix this issue for me. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dick 1719 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c6b78f80-b4a1-4b1a-91b4-8ae5c41b36f4 InstallationDate: Installed on 2013-04-28 (408 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: ASUSTeK Computer INC. 1000HE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=54684f57-2a33-403f-ae4d-ad6b3d0168ea ro acpi_osi=Linux acpi_backlight=vendor quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-27.50hib-generic 3.13.11 RelatedPackageVersions: linux-restricted-modules-3.13.0-27-generic N/A linux-backports-modules-3.13.0-27-generic N/A linux-firmware 1.127.2 Tags: trusty Uname: Linux 3.13.0-27-generic i686 UpgradeStatus: Upgraded to trusty on 2014-04-26 (45 days ago) UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/24/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1000HE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd06/24/2009:svnASUSTeKComputerINC.:pn1000HE:pvrx.x:rvnASUSTeKComputerINC.:rn1000HE:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 1000HE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328727] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1328727/+attachment/4129318/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1328727 Title: s2disk/hibernate hangs during saving of image data Status in “linux” package in Ubuntu: Confirmed Bug description: Hibernation with the pm-hibernate command works fine on a freshly booted system, but when a significant portion of the RAM is in use, for instance by starting gimp, google-chrome and firefox at the same time, it stalls at the start of the saving of the image data: s2disk: Snapshotting system s2disk: System snapshot ready. Preparing to write s2disk: Image size: 441652 kilobytes s2disk: Free swap: 1798624 kilobytes s2disk: Saving 110413 image data pages (press backspace to abort) ... 0% The system is not usable at this point, although alt-sysrq still works. It looks like some sort of deadlock. The system is an Asus eeePC 1000HE with 2GB RAM and a 2GB swap partition and a Samsung SSD 840 EVO. The Ubuntu release is 14.04 LTS. The kernel package is linux-image-3.13.0-27-generic version 3.13.0-27.50 (32 bit). I found a kernel bug report that looks exactly the same: https://bugzilla.kernel.org/show_bug.cgi?id=75101 In that bug report, the problem was bisected to commit a1c3bfb2. This commit is part of the 3.14 kernel, but was apparently backported to the 3.13 Ubuntu kernel. I've rebuild the kernel package with this commit reverted, and it seems to fix this issue for me. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dick 1719 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c6b78f80-b4a1-4b1a-91b4-8ae5c41b36f4 InstallationDate: Installed on 2013-04-28 (408 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: ASUSTeK Computer INC. 1000HE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=54684f57-2a33-403f-ae4d-ad6b3d0168ea ro acpi_osi=Linux acpi_backlight=vendor quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-27.50hib-generic 3.13.11 RelatedPackageVersions: linux-restricted-modules-3.13.0-27-generic N/A linux-backports-modules-3.13.0-27-generic N/A linux-firmware 1.127.2 Tags: trusty Uname: Linux 3.13.0-27-generic i686 UpgradeStatus: Upgraded to trusty on 2014-04-26 (45 days ago) UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/24/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1000HE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd06/24/2009:svnASUSTeKComputerINC.:pn1000HE:pvrx.x:rvnASUSTeKComputerINC.:rn1000HE:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 1000HE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328727] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1328727/+attachment/4129321/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1328727 Title: s2disk/hibernate hangs during saving of image data Status in “linux” package in Ubuntu: Confirmed Bug description: Hibernation with the pm-hibernate command works fine on a freshly booted system, but when a significant portion of the RAM is in use, for instance by starting gimp, google-chrome and firefox at the same time, it stalls at the start of the saving of the image data: s2disk: Snapshotting system s2disk: System snapshot ready. Preparing to write s2disk: Image size: 441652 kilobytes s2disk: Free swap: 1798624 kilobytes s2disk: Saving 110413 image data pages (press backspace to abort) ... 0% The system is not usable at this point, although alt-sysrq still works. It looks like some sort of deadlock. The system is an Asus eeePC 1000HE with 2GB RAM and a 2GB swap partition and a Samsung SSD 840 EVO. The Ubuntu release is 14.04 LTS. The kernel package is linux-image-3.13.0-27-generic version 3.13.0-27.50 (32 bit). I found a kernel bug report that looks exactly the same: https://bugzilla.kernel.org/show_bug.cgi?id=75101 In that bug report, the problem was bisected to commit a1c3bfb2. This commit is part of the 3.14 kernel, but was apparently backported to the 3.13 Ubuntu kernel. I've rebuild the kernel package with this commit reverted, and it seems to fix this issue for me. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dick 1719 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c6b78f80-b4a1-4b1a-91b4-8ae5c41b36f4 InstallationDate: Installed on 2013-04-28 (408 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: ASUSTeK Computer INC. 1000HE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=54684f57-2a33-403f-ae4d-ad6b3d0168ea ro acpi_osi=Linux acpi_backlight=vendor quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-27.50hib-generic 3.13.11 RelatedPackageVersions: linux-restricted-modules-3.13.0-27-generic N/A linux-backports-modules-3.13.0-27-generic N/A linux-firmware 1.127.2 Tags: trusty Uname: Linux 3.13.0-27-generic i686 UpgradeStatus: Upgraded to trusty on 2014-04-26 (45 days ago) UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/24/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1000HE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd06/24/2009:svnASUSTeKComputerINC.:pn1000HE:pvrx.x:rvnASUSTeKComputerINC.:rn1000HE:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 1000HE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328727] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1328727/+attachment/4129320/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1328727 Title: s2disk/hibernate hangs during saving of image data Status in “linux” package in Ubuntu: Confirmed Bug description: Hibernation with the pm-hibernate command works fine on a freshly booted system, but when a significant portion of the RAM is in use, for instance by starting gimp, google-chrome and firefox at the same time, it stalls at the start of the saving of the image data: s2disk: Snapshotting system s2disk: System snapshot ready. Preparing to write s2disk: Image size: 441652 kilobytes s2disk: Free swap: 1798624 kilobytes s2disk: Saving 110413 image data pages (press backspace to abort) ... 0% The system is not usable at this point, although alt-sysrq still works. It looks like some sort of deadlock. The system is an Asus eeePC 1000HE with 2GB RAM and a 2GB swap partition and a Samsung SSD 840 EVO. The Ubuntu release is 14.04 LTS. The kernel package is linux-image-3.13.0-27-generic version 3.13.0-27.50 (32 bit). I found a kernel bug report that looks exactly the same: https://bugzilla.kernel.org/show_bug.cgi?id=75101 In that bug report, the problem was bisected to commit a1c3bfb2. This commit is part of the 3.14 kernel, but was apparently backported to the 3.13 Ubuntu kernel. I've rebuild the kernel package with this commit reverted, and it seems to fix this issue for me. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dick 1719 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c6b78f80-b4a1-4b1a-91b4-8ae5c41b36f4 InstallationDate: Installed on 2013-04-28 (408 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: ASUSTeK Computer INC. 1000HE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=54684f57-2a33-403f-ae4d-ad6b3d0168ea ro acpi_osi=Linux acpi_backlight=vendor quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-27.50hib-generic 3.13.11 RelatedPackageVersions: linux-restricted-modules-3.13.0-27-generic N/A linux-backports-modules-3.13.0-27-generic N/A linux-firmware 1.127.2 Tags: trusty Uname: Linux 3.13.0-27-generic i686 UpgradeStatus: Upgraded to trusty on 2014-04-26 (45 days ago) UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/24/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1000HE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd06/24/2009:svnASUSTeKComputerINC.:pn1000HE:pvrx.x:rvnASUSTeKComputerINC.:rn1000HE:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 1000HE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328727] Re: s2disk/hibernate hangs during saving of image data
apport information ** Tags added: apport-collected ** Description changed: Hibernation with the pm-hibernate command works fine on a freshly booted system, but when a significant portion of the RAM is in use, for instance by starting gimp, google-chrome and firefox at the same time, it stalls at the start of the saving of the image data: s2disk: Snapshotting system s2disk: System snapshot ready. Preparing to write s2disk: Image size: 441652 kilobytes s2disk: Free swap: 1798624 kilobytes s2disk: Saving 110413 image data pages (press backspace to abort) ... 0% The system is not usable at this point, although alt-sysrq still works. It looks like some sort of deadlock. The system is an Asus eeePC 1000HE with 2GB RAM and a 2GB swap partition and a Samsung SSD 840 EVO. The Ubuntu release is 14.04 LTS. The kernel package is linux-image-3.13.0-27-generic version 3.13.0-27.50 (32 bit). I found a kernel bug report that looks exactly the same: https://bugzilla.kernel.org/show_bug.cgi?id=75101 In that bug report, the problem was bisected to commit a1c3bfb2. This commit is part of the 3.14 kernel, but was apparently backported to the 3.13 Ubuntu kernel. I've rebuild the kernel package with this commit reverted, and it seems to fix this issue for me. + --- + ApportVersion: 2.14.1-0ubuntu3.2 + Architecture: i386 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: dick 1719 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 14.04 + HibernationDevice: RESUME=UUID=c6b78f80-b4a1-4b1a-91b4-8ae5c41b36f4 + InstallationDate: Installed on 2013-04-28 (408 days ago) + InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) + MachineType: ASUSTeK Computer INC. 1000HE + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=54684f57-2a33-403f-ae4d-ad6b3d0168ea ro acpi_osi=Linux acpi_backlight=vendor quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.13.0-27.50hib-generic 3.13.11 + RelatedPackageVersions: + linux-restricted-modules-3.13.0-27-generic N/A + linux-backports-modules-3.13.0-27-generic N/A + linux-firmware 1.127.2 + Tags: trusty + Uname: Linux 3.13.0-27-generic i686 + UpgradeStatus: Upgraded to trusty on 2014-04-26 (45 days ago) + UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 06/24/2009 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 0902 + dmi.board.asset.tag: To Be Filled By O.E.M. + dmi.board.name: 1000HE + dmi.board.vendor: ASUSTeK Computer INC. + dmi.board.version: x.xx + dmi.chassis.asset.tag: 0x + dmi.chassis.type: 10 + dmi.chassis.vendor: ASUSTek Computer INC. + dmi.chassis.version: x.x + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd06/24/2009:svnASUSTeKComputerINC.:pn1000HE:pvrx.x:rvnASUSTeKComputerINC.:rn1000HE:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: + dmi.product.name: 1000HE + dmi.product.version: x.x + dmi.sys.vendor: ASUSTeK Computer INC. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1328727/+attachment/4129309/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1328727 Title: s2disk/hibernate hangs during saving of image data Status in “linux” package in Ubuntu: Confirmed Bug description: Hibernation with the pm-hibernate command works fine on a freshly booted system, but when a significant portion of the RAM is in use, for instance by starting gimp, google-chrome and firefox at the same time, it stalls at the start of the saving of the image data: s2disk: Snapshotting system s2disk: System snapshot ready. Preparing to write s2disk: Image size: 441652 kilobytes s2disk: Free swap: 1798624 kilobytes s2disk: Saving 110413 image data pages (press backspace to abort) ... 0% The system is not usable at this point, although alt-sysrq still works. It looks like some sort of deadlock. The system is an Asus eeePC 1000HE with 2GB RAM and a 2GB swap partition and a Samsung SSD 840 EVO. The Ubuntu release is 14.04 LTS. The kernel package is linux-image-3.13.0-27-generic version 3.13.0-27.50 (32 bit). I found a kernel bug report that looks exactly the same: https://bugzilla.kernel.org/show_bug.cgi?id=75101 In that bug report, the problem was bisected to commit a1c3bfb2. This commit is part of the 3.14 kernel, but was apparently backported to the 3.13 Ubuntu kernel. I've rebuild the kernel package with this commit reverted, and it seems to fix this issue for me. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dick 1719 F pulseaudio CurrentDesktop: Unity DistroRelease:
[Kernel-packages] [Bug 1318322] Re: 1002:9616 [Gigabyte GA-78LMT-USB3 (rev. 4.1)] Kernel panic crash to black screen
Ben, the next step is to fully reverse commit bisect the kernel in order to identify the fix commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ? ** Tags removed: bios-outdated-f4 ** Tags added: latest-bios-f4 ** 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/1318322 Title: 1002:9616 [Gigabyte GA-78LMT-USB3 (rev. 4.1)] Kernel panic crash to black screen Status in “linux” package in Ubuntu: Incomplete Bug description: Ubuntu 14.04 crashes two to five times a day with kernel panic to black screen. This only occurs on my two AMD systems. My ohter three intel systems are not affected. 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 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: benjamin 2417 F pulseaudio /dev/snd/controlC0: benjamin 2417 F pulseaudio CurrentDesktop: Unity Date: Sun May 11 13:14:04 2014 HibernationDevice: RESUME=UUID=2ac10fcb-4806-4de5-bdde-5279fcd614c5 InstallationDate: Installed on 2013-07-18 (296 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=ae852eed-50f8-4c51-87de-12cd738cf1a4 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 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-18 (22 days ago) dmi.bios.date: 08/10/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd08/10/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318322/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1327598] Re: running bumblebee in Ubuntu 14.04 results in call trace in logs
Sayantan Das, as a potential WORKAROUND, would using either nouveau, or a different version of the nvidia drivers as noted in https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia change anything? As well, did this problem not occur in a release prior to Trusty? ** Tags removed: kernel-bug-exists-upstream-3.14.1 ** Tags added: kernel-bug-exists-upstream-3.15 ** 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/1327598 Title: running bumblebee in Ubuntu 14.04 results in call trace in logs Status in “linux” package in Ubuntu: Incomplete Bug description: I tried installing bumblebee with nvidia-337 graphics driver. Bumblebee does not work. WORKAROUND: Don't install bumblebee. # Configuration file for Bumblebee. Values should **not** be put between quotes ## Server options. Any change made in this section will need a server restart # to take effect. [bumblebeed] # The secondary Xorg server DISPLAY number VirtualDisplay=:8 # Should the unused Xorg server be kept running? Set this to true if waiting # for X to be ready is too long and don't need power management at all. KeepUnusedXServer=false # The name of the Bumbleblee server group name (GID name) ServerGroup=bumblebee # Card power state at exit. Set to false if the card shoud be ON when Bumblebee # server exits. TurnCardOffAtExit=false # The default behavior of '-f' option on optirun. If set to "true", '-f' will # be ignored. NoEcoModeOverride=false # The Driver used by Bumblebee server. If this value is not set (or empty), # auto-detection is performed. The available drivers are nvidia and nouveau # (See also the driver-specific sections below) Driver=nvidia-337 # Directory with a dummy config file to pass as a -configdir to secondary X XorgConfDir=/etc/bumblebee/xorg.conf.d ## Client options. Will take effect on the next optirun executed. [optirun] # Acceleration/ rendering bridge, possible values are auto, virtualgl and # primus. Bridge=auto # The method used for VirtualGL to transport frames between X servers. # Possible values are proxy, jpeg, rgb, xv and yuv. VGLTransport=proxy # List of paths which are searched for the primus libGL.so.1 when using # the primus bridge PrimusLibraryPath=/usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus # Should the program run under optirun even if Bumblebee server or nvidia card # is not available? AllowFallbackToIGC=false # Driver-specific settings are grouped under [driver-NAME]. The sections are # parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto- # detection resolves to NAME). # PMMethod: method to use for saving power by disabling the nvidia card, valid # values are: auto - automatically detect which PM method to use # bbswitch - new in BB 3, recommended if available # switcheroo - vga_switcheroo method, use at your own risk # none - disable PM completely # https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods ## Section with nvidia driver specific options, only parsed if Driver=nvidia [driver-nvidia] # Module name to load, defaults to Driver if empty or unset KernelDriver=nvidia-337 PMMethod=auto # colon-separated path to the nvidia libraries LibraryPath=/usr/lib/nvidia-337:/usr/lib32/nvidia-337 # comma-separated path of the directory containing nvidia_drv.so and the # default Xorg modules path XorgModulePath=/usr/lib/nvidia-337/xorg,/usr/lib/xorg/modules XorgConfFile=/etc/bumblebee/xorg.conf.nvidia ## Section with nouveau driver specific options, only parsed if Driver=nouveau [driver-nouveau] KernelDriver=nouveau PMMethod=auto XorgConfFile=/etc/bumblebee/xorg.conf.nouveau attached is the dmesg log --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sayantan 2374 F pulseaudio /dev/snd/controlC0: sayantan 2374 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=bf97d424-fc0a-40d8-a799-ee28fc70d432 InstallationDate: Installed on 2014-06-01 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Vostro 3300 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=0cdd0302-af0e-41f3-9d3c-5992d54b61c8 ro persistent quiet splash ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 RelatedPackageVersions: linux-restricted-modules-3.13.0-27-generic N/A linux-backports-modules-3.13.0-27-generic N/A linux-firmware 1.127.2 Tags: trusty Uname: Linux 3.13.0-27-generic x86_64 UpgradeStatus: No upgrade
[Kernel-packages] [Bug 1328313] Re: [Dell Latitude E7240] Alps Touchpad acts erratically when multi-touch is vertical, not horizontal
Mark Smith, could you please advise on what happened/s when using
Windows with the same scenario?
** Summary changed:
- Alps Touchpad acts erratically when multi-touch is vertical, not horizontal
+ [Dell Latitude E7240] Alps Touchpad acts erratically when multi-touch is
vertical, not horizontal
** Tags added: latest-bios-a08
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1328313
Title:
[Dell Latitude E7240] Alps Touchpad acts erratically when multi-touch
is vertical, not horizontal
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
I'm on a Dell Latitude E7240 running 12.04 LTS and my touch pad acts
erratically. It happens because my middle and ring fingers accidentally touch
the top edge of the pad while my pointer finger is moving the cursor. I can
reproduce this on purpose by running "xinput --test [device number]" and
watching the events while I do the following:
- Touch the pad near the middle or bottom. The cursor moves slightly as my
finger wiggles around.
- Without removing the first finger, touch the pad again with a second finger
above the first finger. The cursor shoots up to a[1]=0 (which is the y
position).
- Without removing the first finger, remove the second (top) finger. The
cursor shoots back down to a[1]= Sometimes it takes it all
the way to the bottom of the screen, sometimes it goes back to where it was, or
somewhere else. I haven't been able to figure out how it decides what to go
back to.
With this, while I touching with my pointer finger and my middle or
ring finger accidentally touch the pad at the top, the cursor shoots
where I don't want it. Then when my middle/ring finger leaves the pad
(usually because I started cursing (get it?) at my cursor), it shoots
back down again somewhere completely arbitrary.
Similarly:
- Touch the bad near the top.
- Without removing the top finger, touch somewhere near the bottom. The
cursor doesn't (yet) move.
- Lift the top finger. The cursor shoots to the bottom.
- Put down the top finger again, without lifting the bottom. The cursor
shoots back up again.
You can make the cursor shoot up and down just by keeping your bottom
finger down and tapping the top finger. The cursor follows the top
finger no matter what you do.
Interestingly, this does NOT happen from side-to-side. Two touches
side-by-side trigger the multi-touch gestures and don't move the
cursor.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.13.0-29-generic 3.13.0-29.53~precise1
ProcVersionSignature: Ubuntu 3.13.0-29.53~precise1-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
Date: Mon Jun 9 16:59:49 2014
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
SHELL=/bin/bash
SourcePackage: linux-lts-trusty
UpgradeStatus: No upgrade log present (probably fresh install)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.13.0-29-generic.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: PCH [HDA Intel PCH], device 0: ALC292 Analog [ALC292 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: mrksmith 2576 F pulseaudio
/dev/snd/controlC0: mrksmith 2576 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'HDMI'/'HDA Intel HDMI at 0xf7e34000 irq 64'
Mixer name : 'Intel Haswell HDMI'
Components : 'HDA:80862807,80860101,0010'
Controls : 21
Simple ctrls : 3
Card1.Amixer.info:
Card hw:1 'PCH'/'HDA Intel PCH at 0xf7e3 irq 65'
Mixer name : 'Realtek ALC292'
Components : 'HDA:10ec0292,102805ca,0011'
Controls : 28
Simple ctrls : 13
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=303359b5-1c66-468d-935e-a6d9bc56e4e9
MachineType: Dell Inc. Latitude E7240
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-29-generic
root=/dev/mapper/vg0-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-29.53~precise1-generic 3.13.11.2
RelatedPackageVersions:
linux-restricted-modules-3.13.0-29-generic N/A
linux-backports-modules-3.13.0-29-generic N/A
linux-firmware 1.79.14
Tags: precise running-unity
Uname: Linux 3.13.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout lpadmin plugdev sambashare sudo
dmi.bios.date: 02/18/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.ass
[Kernel-packages] [Bug 1328673] Re: Playstation 3 gamepad does not get a device created
Based on the test results of that kernel, we can decide if a kernel bisect is needed. ** Tags added: performing-bisect -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1328673 Title: Playstation 3 gamepad does not get a device created Status in “linux” package in Ubuntu: Confirmed Bug description: The newer Ubuntu kernel 3.13.0.27-generic breaks my Sony Playstation 3 gamepad. A device entry does not get created for it. I had to migrate back to the older 3.13.0.24-generic kernel. Note that the extra packages are installed for both of these kernels so it has nothing to do with the omission of the extras kernel package. This problem happens at boot time with the newer kernel installed. The kernel log claims that the operational mode cannot be set for the controller. I believe the following is the most informative. Also the entry for the gamepad is omitted when running lsusb probably because no device exists for it either. This also happens on the 3.13.0.29-generic kernel. Ouput from lsb_release -rd: Ubuntu 14.04 LTS This is dmesg on a good kernel: Using Ubuntu kernel 3.13.0.24-generic Jun 2 09:36:58 localhost kernel: [4.123307] usb 1-3.1.3: new full-speed USB device number 7 using ehci-pci Jun 2 09:36:58 localhost kernel: [4.234026] usb 1-3.1.3: New USB device found, idVendor=054c, idProduct=0268 Jun 2 09:36:58 localhost kernel: [4.234094] usb 1-3.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 2 09:36:58 localhost kernel: [4.234171] usb 1-3.1.3: Product: PLAYSTATION(R)3 Controller Jun 2 09:36:58 localhost kernel: [4.234237] usb 1-3.1.3: Manufacturer: Sony Jun 2 09:36:58 localhost kernel: [4.242847] sony 0003:054C:0268.0003: Fixing up Sony Sixaxis report descriptor Jun 2 09:36:58 localhost kernel: [4.268720] input: Sony PLAYSTATION(R)3 Controller as /devices/pci:00/:00:13.5/usb1/1-3/1-3.1/1-3.1.3/1-3.1.3:1.0/input/input6 Jun 2 09:36:58 localhost kernel: [4.268971] sony 0003:054C:0268.0003: input,hiddev0,hidraw1: USB HID v1.11 Joystick [Sony PLAYSTATION(R)3 Controller] on usb-:00:13.5-3.1.3/input0 This is dmesg on the newer kernel: Using Ubuntu kernel 3.13.0.27-generic May 29 09:20:58 localhost kernel: [4.123491] usb 1-3.1.3: new full-speed USB device number 7 using ehci-pci May 29 09:20:58 localhost kernel: [4.234206] usb 1-3.1.3: New USB device found, idVendor=054c, idProduct=0268 May 29 09:20:58 localhost kernel: [4.234275] usb 1-3.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 May 29 09:20:58 localhost kernel: [4.234352] usb 1-3.1.3: Product: PLAYSTATION(R)3 Controller May 29 09:20:58 localhost kernel: [4.234418] usb 1-3.1.3: Manufacturer: Sony May 29 09:20:58 localhost kernel: [4.243617] sony 0003:054C:0268.0003: Fixing up Sony Sixaxis report descriptor May 29 09:20:58 localhost kernel: [4.269540] input: Sony PLAYSTATION(R)3 Controller as /devices/pci:00/:00:13.5/usb1/1-3/1-3.1/1-3.1.3/1-3.1.3:1.0/input/input6 May 29 09:20:58 localhost kernel: [4.269779] sony 0003:054C:0268.0003: input,hiddev0,hidraw1: USB HID v1.11 Joystick [Sony PLAYSTATION(R)3 Controller] on usb-:00:13.5-3.1.3/input0 May 29 09:20:58 localhost kernel: [4.269863] sony 0003:054C:0268.0003: can't set operational mode May 29 09:20:58 localhost kernel: [4.275222] sony: probe of 0003:054C:0268.0003 failed with error -38 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-27-generic 3.13.0-27.50 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: smitty 3101 F pulseaudio CurrentDesktop: KDE Date: Tue Jun 10 15:54:02 2014 HibernationDevice: RESUME=UUID=4001960a-c07d-4731-af22-47abce9408b6 InstallationDate: Installed on 2014-04-17 (53 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7388 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=b1e4a07d-688e-472b-a067-aa7e1045e057 ro RelatedPackageVersions: linux-restricted-modules-3.13.0-27-generic N/A linux-backports-modules-3.13.0-27-generic N/A linux-firmware 1.127.2 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/12
[Kernel-packages] [Bug 1325412] Re: 046d:0896 [Acer Aspire 5630] Orbicam not working on Ubuntu 14.04
thicot: >"Christopher, the original report is about a normal installation of Lubuntu 14.04 and as requested, I installed an upstream kernel on testing purpose." This is already obvious to anyone reading this report. >"I am a normal user who just would like to help going forward with an annoying issue with Ubuntu." If you want to help, you would want to follow the directions previously advised to you in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1325412/comments/13 . >"The original issue is still on Ubuntu 3.13.0-27.50-generic 3.13.11 and upstream kernel (2 versions ahead) proved that, somewhere in the code there is something blocking normal use of the Orbicam." See above. >"Does it really make sense to open so many reports in different places?" As the vast majority of upstream developers aren't looking at this report, but the appropriate upstream mailinglist, e-mailing them would only increase the likelihood of your bug being addressed as soon as possible. Would that make sense? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1325412 Title: 046d:0896 [Acer Aspire 5630] Orbicam not working on Ubuntu 14.04 Status in “linux” package in Ubuntu: Triaged Bug description: Webcam Logitech Orbicam (046d:0826) does not work on a newly installed lubuntu 14.04. Machine is an Acer Aspire 5630 with integrated webcam. I have tried with no success guvcview and skype. Each time, video display remains black and no led on webcam. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-27-generic 3.13.0-27.50 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: LXDE Date: Sun Jun 1 21:20:59 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-05-29 (3 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=d8a36955-2ebd-48b4-9724-e4e5e1effdf9 ro quiet splash vt.handoff=7 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2006 dmi.bios.vendor: Acer dmi.bios.version: V3.01 dmi.board.name: Grapevine dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrV3.01:bd10/25/2006:svnAcer:pnAspire5630:pvrV3.01:rvnAcer:rnGrapevine:rvrN/A:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 5630 dmi.product.version: V3.01 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1325412/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328673] Re: Playstation 3 gamepad does not get a device created
Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.13 stable kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.11.2-trusty/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1328673 Title: Playstation 3 gamepad does not get a device created Status in “linux” package in Ubuntu: Confirmed Bug description: The newer Ubuntu kernel 3.13.0.27-generic breaks my Sony Playstation 3 gamepad. A device entry does not get created for it. I had to migrate back to the older 3.13.0.24-generic kernel. Note that the extra packages are installed for both of these kernels so it has nothing to do with the omission of the extras kernel package. This problem happens at boot time with the newer kernel installed. The kernel log claims that the operational mode cannot be set for the controller. I believe the following is the most informative. Also the entry for the gamepad is omitted when running lsusb probably because no device exists for it either. This also happens on the 3.13.0.29-generic kernel. Ouput from lsb_release -rd: Ubuntu 14.04 LTS This is dmesg on a good kernel: Using Ubuntu kernel 3.13.0.24-generic Jun 2 09:36:58 localhost kernel: [4.123307] usb 1-3.1.3: new full-speed USB device number 7 using ehci-pci Jun 2 09:36:58 localhost kernel: [4.234026] usb 1-3.1.3: New USB device found, idVendor=054c, idProduct=0268 Jun 2 09:36:58 localhost kernel: [4.234094] usb 1-3.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 2 09:36:58 localhost kernel: [4.234171] usb 1-3.1.3: Product: PLAYSTATION(R)3 Controller Jun 2 09:36:58 localhost kernel: [4.234237] usb 1-3.1.3: Manufacturer: Sony Jun 2 09:36:58 localhost kernel: [4.242847] sony 0003:054C:0268.0003: Fixing up Sony Sixaxis report descriptor Jun 2 09:36:58 localhost kernel: [4.268720] input: Sony PLAYSTATION(R)3 Controller as /devices/pci:00/:00:13.5/usb1/1-3/1-3.1/1-3.1.3/1-3.1.3:1.0/input/input6 Jun 2 09:36:58 localhost kernel: [4.268971] sony 0003:054C:0268.0003: input,hiddev0,hidraw1: USB HID v1.11 Joystick [Sony PLAYSTATION(R)3 Controller] on usb-:00:13.5-3.1.3/input0 This is dmesg on the newer kernel: Using Ubuntu kernel 3.13.0.27-generic May 29 09:20:58 localhost kernel: [4.123491] usb 1-3.1.3: new full-speed USB device number 7 using ehci-pci May 29 09:20:58 localhost kernel: [4.234206] usb 1-3.1.3: New USB device found, idVendor=054c, idProduct=0268 May 29 09:20:58 localhost kernel: [4.234275] usb 1-3.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 May 29 09:20:58 localhost kernel: [4.234352] usb 1-3.1.3: Product: PLAYSTATION(R)3 Controller May 29 09:20:58 localhost kernel: [4.234418] usb 1-3.1.3: Manufacturer: Sony May 29 09:20:58 localhost kernel: [4.243617] sony 0003:054C:0268.0003: Fixing up Sony Sixaxis report descriptor May 29 09:20:58 localhost kernel: [4.269540] input: Sony PLAYSTATION(R)3 Controller as /devices/pci:00/:00:13.5/usb1/1-3/1-3.1/1-3.1.3/1-3.1.3:1.0/input/input6 May 29 09:20:58 localhost kernel: [4.269779] sony 0003:054C:0268.0003: input,hiddev0,hidraw1: USB HID v1.11 Joystick [Sony PLAYSTATION(R)3 Controller] on usb-:00:13.5-3.1.3/input0 May 29 09:20:58 localhost kernel: [4.269863] sony 0003:054C:0268.0003: can't set operational mode May 29 09:20:58 localhost kernel: [4.275222] sony: probe of 0003:054C:0268.0003 failed with error -38 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-27-generic 3.13.0-27.50 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: smitty 3101 F pulseaudio CurrentDesktop: KDE Date: Tue Jun 10 15:54:02 2014 HibernationDevice: RESUME=UUID=4001960a-c07d-4731-af22-47abce9408b6 InstallationDate: Installed on 2014-04-17 (53 days ago) Installa
[Kernel-packages] [Bug 1173681] Re: 168c:002b [asus_nb_wmi] [Asus U32U] AR9285 ath9k not working after updating to ubuntu 13.04 Raring (linux 3.8.0-19-generic)
ne, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via: ubuntu-bug linux For more on this, please read the official Ubuntu documentation: Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette When opening up the new report, please feel free to subscribe me to it. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1173681 Title: 168c:002b [asus_nb_wmi] [Asus U32U] AR9285 ath9k not working after updating to ubuntu 13.04 Raring (linux 3.8.0-19-generic) Status in The Linux Kernel: New Status in “linux” package in Ubuntu: Incomplete Bug description: update: updated the BIOS to the latest version but the problem persists. Booting with the older kernel (latest linux kernel from 12.10) every thing works fine. After upgrading to Raring Ringtail Ubuntu 13.04, with the new kernel, hardware get blocked/disabled and wireless doesn't work: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes 1: asus-wlan: Wireless LAN Soft blocked: no Hard blocked: no WORKAROUND - is only applicable to Asus Notebooks/netbooks that use the "asus_nb_wmi" driver: Create and edit asus_nb_wmi.conf file with this command: sudo echo "options asus_nb_wmi wapf=1" | sudo tee /etc/modprobe.d/asus_nb_wmi.conf For more detailed info of the workaround please see: http://ubuntuforums.org/showthread.php?t=2181558 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic 3.8.0-19.29 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: x 1822 F pulseaudio CurrentDmesg: [ 370.100280] r8169 :04:00.2 eth1: link up [ 370.100322] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [ 891.718748] systemd-hostnamed[2649]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname! [14119.241628] rtsx_pci :04:00.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update. Date: Sat Apr 27 17:31:51 2013 HibernationDevice: RESUME=UUID=e417e9f2-b63e-4b79-9be4-c21f55547205 InstallationDate: Installed on 2012-07-13 (287 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: ASUSTeK Computer Inc. U32U MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=3ad9d88b-a7a5-460f-ba15-a78dd7f2fc94 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: Upgraded to raring on 2013-04-27 (0 days ago) dmi.bios.date: 12/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U32U.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U32U dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU32U.204:bd12/16/2011:svnASUSTeKComputerInc.:pnU32U:pvr1.0:rvnASUSTeKComputerInc.:rnU32U:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: U32U 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/1173681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1322068] Re: Turn on bluetooth with Fn+F12 not working
Antoine Sibold, at this point no, as a bisect would need to occur. Feel free to read the article, and post back where exactly you may have gotten stuck. ** 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/1322068 Title: Turn on bluetooth with Fn+F12 not working Status in “linux” package in Ubuntu: Incomplete Bug description: After installing Ubuntu 14.04 LTS, i cannot turn on Bluetooth with Fn+F12 as usual. I have tested other versions of Ubuntu the results are: Ubuntu 12.04.LTS it works Ubuntu 12.04.1 LTS it works Ubuntu 12.04.2 LTS it works Ubuntu 12.04.3 LTS it does not working Ubuntu 12.04.4 LTS it does not working 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 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sibold 1910 F pulseaudio CurrentDesktop: Unity Date: Thu May 22 09:31:55 2014 HibernationDevice: RESUME=UUID=135e9bbf-c0ff-411b-a1d8-e28de2b970ab InstallationDate: Installed on 2014-05-17 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=88147625-e531-4dd3-a5a1-fe593a977841 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 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W240EU/W250EUQ/W270EUQ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd05/09/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: W240EU/W250EUQ/W270EUQ dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322068/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1327086] Re: [Dell Precision M3800] DisplayLink USB Graphics adapter not working
bcygan, the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel ? Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked. Thank you for your understanding. ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1327086 Title: [Dell Precision M3800] DisplayLink USB Graphics adapter not working Status in “linux” package in Ubuntu: Triaged Bug description: Dell USB Docking Station D3000. dmesg says that DisplayLink was found and DisplayLink is visible via lsusb, but nothing happens on the monitor. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bcygan 3606 F pulseaudio /dev/snd/controlC2: bcygan 3606 F pulseaudio Date: Fri Jun 6 09:42:40 2014 InstallationDate: Installed on 2014-04-25 (41 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. Dell Precision M3800 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic.efi.signed root=UUID=31d8de7d-5798-4462-9c7f-c372c063b991 ro quiet splash ipv6.disable=1 i915.i915_enable_fbc=0 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-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.130~gd~t SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-25 (41 days ago) dmi.bios.date: 04/16/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd04/16/2014:svnDellInc.:pnDellPrecisionM3800:pvrA05:rvnDellInc.:rnDellPrecisionM3800:rvrA05:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.version: A05 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328727] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1328727 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 ** Tags added: 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/1328727 Title: s2disk/hibernate hangs during saving of image data Status in “linux” package in Ubuntu: Incomplete Bug description: Hibernation with the pm-hibernate command works fine on a freshly booted system, but when a significant portion of the RAM is in use, for instance by starting gimp, google-chrome and firefox at the same time, it stalls at the start of the saving of the image data: s2disk: Snapshotting system s2disk: System snapshot ready. Preparing to write s2disk: Image size: 441652 kilobytes s2disk: Free swap: 1798624 kilobytes s2disk: Saving 110413 image data pages (press backspace to abort) ... 0% The system is not usable at this point, although alt-sysrq still works. It looks like some sort of deadlock. The system is an Asus eeePC 1000HE with 2GB RAM and a 2GB swap partition and a Samsung SSD 840 EVO. The Ubuntu release is 14.04 LTS. The kernel package is linux-image-3.13.0-27-generic version 3.13.0-27.50 (32 bit). I found a kernel bug report that looks exactly the same: https://bugzilla.kernel.org/show_bug.cgi?id=75101 In that bug report, the problem was bisected to commit a1c3bfb2. This commit is part of the 3.14 kernel, but was apparently backported to the 3.13 Ubuntu kernel. I've rebuild the kernel package with this commit reverted, and it seems to fix this issue for me. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328727] [NEW] s2disk/hibernate hangs during saving of image data
Public bug reported: Hibernation with the pm-hibernate command works fine on a freshly booted system, but when a significant portion of the RAM is in use, for instance by starting gimp, google-chrome and firefox at the same time, it stalls at the start of the saving of the image data: s2disk: Snapshotting system s2disk: System snapshot ready. Preparing to write s2disk: Image size: 441652 kilobytes s2disk: Free swap: 1798624 kilobytes s2disk: Saving 110413 image data pages (press backspace to abort) ... 0% The system is not usable at this point, although alt-sysrq still works. It looks like some sort of deadlock. The system is an Asus eeePC 1000HE with 2GB RAM and a 2GB swap partition and a Samsung SSD 840 EVO. The Ubuntu release is 14.04 LTS. The kernel package is linux-image-3.13.0-27-generic version 3.13.0-27.50 (32 bit). I found a kernel bug report that looks exactly the same: https://bugzilla.kernel.org/show_bug.cgi?id=75101 In that bug report, the problem was bisected to commit a1c3bfb2. This commit is part of the 3.14 kernel, but was apparently backported to the 3.13 Ubuntu kernel. I've rebuild the kernel package with this commit reverted, and it seems to fix this issue for me. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: 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/1328727 Title: s2disk/hibernate hangs during saving of image data Status in “linux” package in Ubuntu: Incomplete Bug description: Hibernation with the pm-hibernate command works fine on a freshly booted system, but when a significant portion of the RAM is in use, for instance by starting gimp, google-chrome and firefox at the same time, it stalls at the start of the saving of the image data: s2disk: Snapshotting system s2disk: System snapshot ready. Preparing to write s2disk: Image size: 441652 kilobytes s2disk: Free swap: 1798624 kilobytes s2disk: Saving 110413 image data pages (press backspace to abort) ... 0% The system is not usable at this point, although alt-sysrq still works. It looks like some sort of deadlock. The system is an Asus eeePC 1000HE with 2GB RAM and a 2GB swap partition and a Samsung SSD 840 EVO. The Ubuntu release is 14.04 LTS. The kernel package is linux-image-3.13.0-27-generic version 3.13.0-27.50 (32 bit). I found a kernel bug report that looks exactly the same: https://bugzilla.kernel.org/show_bug.cgi?id=75101 In that bug report, the problem was bisected to commit a1c3bfb2. This commit is part of the 3.14 kernel, but was apparently backported to the 3.13 Ubuntu kernel. I've rebuild the kernel package with this commit reverted, and it seems to fix this issue for me. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1315369] Re: Log in not available after lock screen with multi-monitor
Gregory and David, in order to make sure weather your problem is related to unity or not, please follow the steps I wrote above to double check. 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/1315369 Title: Log in not available after lock screen with multi-monitor Status in Unity: Invalid Status in “linux” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Invalid Status in “linux” source package in Trusty: Confirmed Status in “unity” source package in Trusty: Confirmed Bug description: After the screen locks I am unable to log back in because the screen with the login prompt is black, and the screen on my laptop just shows the Ubuntu logo. Furthermore, if I then unplug the external monitor (in an attempt to force the log in option to be displayed on the laptop) the laptop screen then goes black and I can't do anything at all. I can't reproduce this if I select "lock screen" from the UI, but it happens reliably if it locks due to inactivity. Other info: - I am running a fresh install of 14.04 - I have it set to lock after 5 min of inactivity, and require login after lock - I have an external monitor, configured to be on the left side of the laptop screen --- ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jane 2184 F pulseaudio /dev/snd/controlC0: jane 2184 F pulseaudio CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=61f52096-031e-4e3d-b1ae-e504b3b3edec InstallationDate: Installed on 2014-05-01 (20 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) MachineType: Dell Inc. Dell System XPS L321X Package: unity 7.2.0+14.04.20140416-0ubuntu1 PackageArchitecture: i386 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 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 Tags: trusty trusty Uname: Linux 3.13.0-24-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/09/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 085X6F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd04/09/2012:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn085X6F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L321X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1315369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1327625] Re: system spontaneously awakes from sleep; other sleep problems
There's no sticker giving specifics on the computer, at least that I could find. The order form for the computer says it's a HP Pavilion dv6t Quad Edition Laptop, product # A2Z57AV. That product number suggests, according to a google search, that the specific version of the dv6t it is is dv6t-6b00. I've also filed a bug report when the system froze on trying to suspend. It is bug #1328708. The system has frozen on suspend three times in the last three days. The install of Ubuntu 14.04 was a fresh install about 2 months ago w/ KDE on top of it. Started having these problems with suspend from almost the day I started using KDE. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1327625 Title: system spontaneously awakes from sleep; other sleep problems Status in “linux” package in Ubuntu: Incomplete Bug description: I added KDE to an Ubuntu installation. When I'm in KDE, I've had numerous problems with suspend to RAM, even though I don't believe I had these problems in Unity. The particular problem I just had, so perhaps the data apport collected spotted something, was this: I deliberately suspended to RAM. A few seconds later, the computer woke up without my doing anything (did not touch the keyboard, etc.). This has happened numerous times. For a while, I had to suspend twice whenever I wanted the suspend to take hold. [Other suspend problems, but which have not occurred just now: a) system freezes when I initiate a suspend--have to hard shutdown otherwise computer keeps running with nothing showing on either display; b) system goes into suspend, and wakes right back up again a few seconds later, for no apparent reason--can happen when I'm watching a video or editing some text; c) system suspends and wakes up when I move between activities] I erased the contents of various system logs to see what records were being generated when the problem occurs. Only two logs showed any addition of material (from empty)--pm-suspend and pm-powersave. I'm attaching them here. Because other logs will have no content, I'll attach some older logs in case there's something that might be useful. Best wishes figuring this out! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peterm 3016 F pulseaudio BootDmesg: CurrentDesktop: KDE Date: Sat Jun 7 17:47:52 2014 HibernationDevice: RESUME=UUID=5d23be8c-e134-466b-8698-0344f70809a4 InstallationDate: Installed on 2014-04-20 (48 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-29-generic root=UUID=905a5deb-feac-448c-9f59-7040a9ea9942 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 10/23/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1B dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 17FB dmi.board.vendor: Hewlett-Packard dmi.board.version: 10.5A dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1B:bd10/23/2012:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058D11000220472622100:rvnHewlett-Packard:rn17FB:rvr10.5A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 058D11000220472622100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327625/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1283938] Re: [Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after wakeup from sleep
I've tested Ubuntu14.04LTS with v3.15-utopic/linux-kernel-3.15.0-031500-generic_3.15.0-031500.201406081435_amd64. But, situation does not change anything. I resume the laptop from sleep, screen shows login screen(very very slow) or sometime black screen freeze. Even I 'm able to login, then, Ubuntu will always freeze. MacBookPro17inch (6,1) 8GRAM SSD-400G(Intel) with ahci Nouveau display driver -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1283938 Title: [Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after wakeup from sleep Status in “linux” package in Ubuntu: Incomplete Bug description: In 14.04 after wakeup from suspend, the notebook screen goes blank while the OS and the hardware is awake (I can also press Ctrl+F1 and Ctrl+Alt+Del to reboot the system). Changeing "quiet splash" to "nomodeset" in /etc/default/grub allows the wakeup, but the pc is really slow (can't be used). WORKAROUND: This problem is not happening with the AMD property drivers. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Feb 24 12:58:07 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7500G] [1002:990a] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c660] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] [1002:6841] (rev ff) (prog-if ff) InstallationDate: Installed on 2014-02-22 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140218) MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U4C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic root=UUID=9f8c7e92-a6ea-41fd-9489-a256c8b9f5d5 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P06RAF.N93.130403.LEO dmi.board.asset.tag: No Asset Tag dmi.board.name: NP535U4X-S01TH dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP06RAF.N93.130403.LEO:bd04/03/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U4C:pvrP06RAF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP535U4X-S01TH:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 535U4C dmi.product.version: P06RAF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Feb 24 12:54:54 2014 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu6 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328348] Re: linux-ppc: -proposed tracker
** Changed in: linux-ppc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ppc in Ubuntu. https://bugs.launchpad.net/bugs/1328348 Title: linux-ppc: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New 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: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in “linux-ppc” package in Ubuntu: Invalid Status in “linux-ppc” source package in Saucy: New Bug description: This bug is for tracking the 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:Tuesday, 10. June 2014 03:02 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Tuesday, 10. June 2014 03:02 UTC kernel-stable-master-bug:1328153 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1328348/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328620] Re: linux: 3.2.0-65.98 -proposed tracker
** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1328620 Title: linux: 3.2.0-65.98 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-lbm series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Precise: New Bug description: This bug is for tracking the 3.2.0-65.98 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:Tuesday, 10. June 2014 17:29 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Tuesday, 10. June 2014 17:29 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1328620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1271444] Re: CVE-2014-1445
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Fix Committed => Fix Released ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Precise) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Saucy) Status: Fix Committed => Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: Fix Committed => Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Saucy) Status: Fix Committed => Fix Released ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Won't Fix => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1271444 Title: CVE-2014-1445 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Released Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-lts-raring” source package in Precise: Fix Released Status in “linux-lts-saucy” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Fix Released Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Released Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Invalid Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: Won't Fix Status in “linux-l
[Kernel-packages] [Bug 1327908] Re: HP NC375T / phanfw.bin: firmware is older than flash / Direct firmware load failed with error -2 / HP firmware is newer in cards
Is this helpful? http://ldriver.qlogic.com/driver-srpms/nx_nic/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1327908 Title: HP NC375T / phanfw.bin: firmware is older than flash / Direct firmware load failed with error -2 / HP firmware is newer in cards Status in “linux” package in Ubuntu: Confirmed Bug description: HP has a newer firmware on their NC375T server nics: 4.0.593 This generates an error at the startup of Ubuntu Server 14.04 LTS The version of phanfw.bin seems to be older. [ 16.573260] QLogic/NetXen Network Driver v4.0.82 [ 16.87] netxen_nic :07:00.0: 2MB memory map [ 16.812455] netxen_nic :07:00.0: phanfw.bin: firmware is older than flash [ 16.818949] netxen_nic :07:00.0: Direct firmware load failed with error -2 [ 16.818950] netxen_nic :07:00.0: Falling back to user helper [ 23.138390] netxen_nic :07:00.0: loading firmware from flash [ 27.586070] netxen_nic :07:00.0: Gen2 strapping detected [ 30.185964] netxen_nic :07:00.0: using 64-bit dma mask [ 30.373956] netxen_nic: Quad Gig LP Board S/N TI13BK1960 Chip rev 0x42 [ 30.450969] netxen_nic :07:00.0: Driver v4.0.82, firmware v4.0.593 [legacy] [ 39.718557] netxen_nic :07:00.0: irq 67 for MSI/MSI-X [ 39.718561] netxen_nic :07:00.0: irq 68 for MSI/MSI-X [ 39.718564] netxen_nic :07:00.0: irq 69 for MSI/MSI-X [ 39.718567] netxen_nic :07:00.0: irq 70 for MSI/MSI-X [ 39.718605] netxen_nic :07:00.0: using msi-x interrupts [ 39.780399] netxen_nic :07:00.0: non ULA adapter [ 39.841095] netxen_nic :07:00.0: eth0: GbE port initialized [ 39.901172] netxen_nic :07:00.1: 2MB memory map [ 39.959403] netxen_nic :07:00.1: using 64-bit dma mask [ 40.117279] netxen_nic :07:00.1: Driver v4.0.82, firmware v4.0.593 [legacy] [ 40.174172] netxen_nic :07:00.1: irq 71 for MSI/MSI-X [ 40.174175] netxen_nic :07:00.1: irq 72 for MSI/MSI-X [ 40.174178] netxen_nic :07:00.1: irq 73 for MSI/MSI-X [ 40.174181] netxen_nic :07:00.1: irq 74 for MSI/MSI-X [ 40.174209] netxen_nic :07:00.1: using msi-x interrupts [ 40.229992] netxen_nic :07:00.1: eth1: GbE port initialized [ 40.284766] netxen_nic :07:00.2: 2MB memory map [ 40.339836] netxen_nic :07:00.2: using 64-bit dma mask [ 40.465258] netxen_nic :07:00.2: Driver v4.0.82, firmware v4.0.593 [legacy] [ 40.522359] netxen_nic :07:00.2: irq 75 for MSI/MSI-X [ 40.522363] netxen_nic :07:00.2: irq 76 for MSI/MSI-X [ 40.522365] netxen_nic :07:00.2: irq 77 for MSI/MSI-X [ 40.522368] netxen_nic :07:00.2: irq 78 for MSI/MSI-X [ 40.522392] netxen_nic :07:00.2: using msi-x interrupts [ 40.578742] netxen_nic :07:00.2: eth2: GbE port initialized [ 40.634802] netxen_nic :07:00.3: 2MB memory map [ 40.690423] netxen_nic :07:00.3: using 64-bit dma mask [ 40.825233] netxen_nic :07:00.3: Driver v4.0.82, firmware v4.0.593 [legacy] [ 40.882915] netxen_nic :07:00.3: irq 79 for MSI/MSI-X [ 40.882919] netxen_nic :07:00.3: irq 80 for MSI/MSI-X [ 40.882922] netxen_nic :07:00.3: irq 81 for MSI/MSI-X [ 40.882925] netxen_nic :07:00.3: irq 82 for MSI/MSI-X [ 40.882951] netxen_nic :07:00.3: using msi-x interrupts [ 40.939825] netxen_nic :07:00.3: eth3: GbE port initialized # ethtool -i p4p1 driver: netxen_nic version: 4.0.82 firmware-version: 4.0.593 bus-info: :07:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no # ./nxflash.bin -i p4p1 --info Board Type: 0x24 (NC375T PCI Express Quad Port Gigabit Server Adapter) Board Chip Rev: B2 Serial Id: TI13BK1960 Efuse ID: 0x Firmware version(on Flash): 4.0.593 Active Firmware version: 4.0.593 Driver version: 0.0.0 BIOS version: 2.1.0 MAC Addr 0: 78:AC:C0:10:F9:DC Subsystem ID: 0x1740103c PXE Status 0: Disabled WOL Status 0: Disabled # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3 Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x8 Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) 00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5) 00:1c.3 PCI bridge: Intel
[Kernel-packages] [Bug 1327908] Re: HP NC375T / phanfw.bin: firmware is older than flash / Direct firmware load failed with error -2 / HP firmware is newer in cards
Or am I wrong here and does this "phanfw.bin' belong to the linux-kernel team and do they need to update that file, so it has a newer version compatible with the HP cards? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1327908 Title: HP NC375T / phanfw.bin: firmware is older than flash / Direct firmware load failed with error -2 / HP firmware is newer in cards Status in “linux” package in Ubuntu: Confirmed Bug description: HP has a newer firmware on their NC375T server nics: 4.0.593 This generates an error at the startup of Ubuntu Server 14.04 LTS The version of phanfw.bin seems to be older. [ 16.573260] QLogic/NetXen Network Driver v4.0.82 [ 16.87] netxen_nic :07:00.0: 2MB memory map [ 16.812455] netxen_nic :07:00.0: phanfw.bin: firmware is older than flash [ 16.818949] netxen_nic :07:00.0: Direct firmware load failed with error -2 [ 16.818950] netxen_nic :07:00.0: Falling back to user helper [ 23.138390] netxen_nic :07:00.0: loading firmware from flash [ 27.586070] netxen_nic :07:00.0: Gen2 strapping detected [ 30.185964] netxen_nic :07:00.0: using 64-bit dma mask [ 30.373956] netxen_nic: Quad Gig LP Board S/N TI13BK1960 Chip rev 0x42 [ 30.450969] netxen_nic :07:00.0: Driver v4.0.82, firmware v4.0.593 [legacy] [ 39.718557] netxen_nic :07:00.0: irq 67 for MSI/MSI-X [ 39.718561] netxen_nic :07:00.0: irq 68 for MSI/MSI-X [ 39.718564] netxen_nic :07:00.0: irq 69 for MSI/MSI-X [ 39.718567] netxen_nic :07:00.0: irq 70 for MSI/MSI-X [ 39.718605] netxen_nic :07:00.0: using msi-x interrupts [ 39.780399] netxen_nic :07:00.0: non ULA adapter [ 39.841095] netxen_nic :07:00.0: eth0: GbE port initialized [ 39.901172] netxen_nic :07:00.1: 2MB memory map [ 39.959403] netxen_nic :07:00.1: using 64-bit dma mask [ 40.117279] netxen_nic :07:00.1: Driver v4.0.82, firmware v4.0.593 [legacy] [ 40.174172] netxen_nic :07:00.1: irq 71 for MSI/MSI-X [ 40.174175] netxen_nic :07:00.1: irq 72 for MSI/MSI-X [ 40.174178] netxen_nic :07:00.1: irq 73 for MSI/MSI-X [ 40.174181] netxen_nic :07:00.1: irq 74 for MSI/MSI-X [ 40.174209] netxen_nic :07:00.1: using msi-x interrupts [ 40.229992] netxen_nic :07:00.1: eth1: GbE port initialized [ 40.284766] netxen_nic :07:00.2: 2MB memory map [ 40.339836] netxen_nic :07:00.2: using 64-bit dma mask [ 40.465258] netxen_nic :07:00.2: Driver v4.0.82, firmware v4.0.593 [legacy] [ 40.522359] netxen_nic :07:00.2: irq 75 for MSI/MSI-X [ 40.522363] netxen_nic :07:00.2: irq 76 for MSI/MSI-X [ 40.522365] netxen_nic :07:00.2: irq 77 for MSI/MSI-X [ 40.522368] netxen_nic :07:00.2: irq 78 for MSI/MSI-X [ 40.522392] netxen_nic :07:00.2: using msi-x interrupts [ 40.578742] netxen_nic :07:00.2: eth2: GbE port initialized [ 40.634802] netxen_nic :07:00.3: 2MB memory map [ 40.690423] netxen_nic :07:00.3: using 64-bit dma mask [ 40.825233] netxen_nic :07:00.3: Driver v4.0.82, firmware v4.0.593 [legacy] [ 40.882915] netxen_nic :07:00.3: irq 79 for MSI/MSI-X [ 40.882919] netxen_nic :07:00.3: irq 80 for MSI/MSI-X [ 40.882922] netxen_nic :07:00.3: irq 81 for MSI/MSI-X [ 40.882925] netxen_nic :07:00.3: irq 82 for MSI/MSI-X [ 40.882951] netxen_nic :07:00.3: using msi-x interrupts [ 40.939825] netxen_nic :07:00.3: eth3: GbE port initialized # ethtool -i p4p1 driver: netxen_nic version: 4.0.82 firmware-version: 4.0.593 bus-info: :07:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no # ./nxflash.bin -i p4p1 --info Board Type: 0x24 (NC375T PCI Express Quad Port Gigabit Server Adapter) Board Chip Rev: B2 Serial Id: TI13BK1960 Efuse ID: 0x Firmware version(on Flash): 4.0.593 Active Firmware version: 4.0.593 Driver version: 0.0.0 BIOS version: 2.1.0 MAC Addr 0: 78:AC:C0:10:F9:DC Subsystem ID: 0x1740103c PXE Status 0: Disabled WOL Status 0: Disabled # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3 Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x8 Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) 00:1c.2 PCI bridge: Intel Cor
[Kernel-packages] [Bug 1327908] Re: HP NC375T / phanfw.bin: firmware is older than flash / Direct firmware load failed with error -2 / HP firmware is newer in cards
** Attachment added: "HP 4.0.593 Firmware (as is on the cards now)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327908/+attachment/4129306/+files/phantom_romimage ** Attachment removed: "Flash Utility for the NC375T and other cards" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327908/+attachment/4129305/+files/nxflash -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1327908 Title: HP NC375T / phanfw.bin: firmware is older than flash / Direct firmware load failed with error -2 / HP firmware is newer in cards Status in “linux” package in Ubuntu: Confirmed Bug description: HP has a newer firmware on their NC375T server nics: 4.0.593 This generates an error at the startup of Ubuntu Server 14.04 LTS The version of phanfw.bin seems to be older. [ 16.573260] QLogic/NetXen Network Driver v4.0.82 [ 16.87] netxen_nic :07:00.0: 2MB memory map [ 16.812455] netxen_nic :07:00.0: phanfw.bin: firmware is older than flash [ 16.818949] netxen_nic :07:00.0: Direct firmware load failed with error -2 [ 16.818950] netxen_nic :07:00.0: Falling back to user helper [ 23.138390] netxen_nic :07:00.0: loading firmware from flash [ 27.586070] netxen_nic :07:00.0: Gen2 strapping detected [ 30.185964] netxen_nic :07:00.0: using 64-bit dma mask [ 30.373956] netxen_nic: Quad Gig LP Board S/N TI13BK1960 Chip rev 0x42 [ 30.450969] netxen_nic :07:00.0: Driver v4.0.82, firmware v4.0.593 [legacy] [ 39.718557] netxen_nic :07:00.0: irq 67 for MSI/MSI-X [ 39.718561] netxen_nic :07:00.0: irq 68 for MSI/MSI-X [ 39.718564] netxen_nic :07:00.0: irq 69 for MSI/MSI-X [ 39.718567] netxen_nic :07:00.0: irq 70 for MSI/MSI-X [ 39.718605] netxen_nic :07:00.0: using msi-x interrupts [ 39.780399] netxen_nic :07:00.0: non ULA adapter [ 39.841095] netxen_nic :07:00.0: eth0: GbE port initialized [ 39.901172] netxen_nic :07:00.1: 2MB memory map [ 39.959403] netxen_nic :07:00.1: using 64-bit dma mask [ 40.117279] netxen_nic :07:00.1: Driver v4.0.82, firmware v4.0.593 [legacy] [ 40.174172] netxen_nic :07:00.1: irq 71 for MSI/MSI-X [ 40.174175] netxen_nic :07:00.1: irq 72 for MSI/MSI-X [ 40.174178] netxen_nic :07:00.1: irq 73 for MSI/MSI-X [ 40.174181] netxen_nic :07:00.1: irq 74 for MSI/MSI-X [ 40.174209] netxen_nic :07:00.1: using msi-x interrupts [ 40.229992] netxen_nic :07:00.1: eth1: GbE port initialized [ 40.284766] netxen_nic :07:00.2: 2MB memory map [ 40.339836] netxen_nic :07:00.2: using 64-bit dma mask [ 40.465258] netxen_nic :07:00.2: Driver v4.0.82, firmware v4.0.593 [legacy] [ 40.522359] netxen_nic :07:00.2: irq 75 for MSI/MSI-X [ 40.522363] netxen_nic :07:00.2: irq 76 for MSI/MSI-X [ 40.522365] netxen_nic :07:00.2: irq 77 for MSI/MSI-X [ 40.522368] netxen_nic :07:00.2: irq 78 for MSI/MSI-X [ 40.522392] netxen_nic :07:00.2: using msi-x interrupts [ 40.578742] netxen_nic :07:00.2: eth2: GbE port initialized [ 40.634802] netxen_nic :07:00.3: 2MB memory map [ 40.690423] netxen_nic :07:00.3: using 64-bit dma mask [ 40.825233] netxen_nic :07:00.3: Driver v4.0.82, firmware v4.0.593 [legacy] [ 40.882915] netxen_nic :07:00.3: irq 79 for MSI/MSI-X [ 40.882919] netxen_nic :07:00.3: irq 80 for MSI/MSI-X [ 40.882922] netxen_nic :07:00.3: irq 81 for MSI/MSI-X [ 40.882925] netxen_nic :07:00.3: irq 82 for MSI/MSI-X [ 40.882951] netxen_nic :07:00.3: using msi-x interrupts [ 40.939825] netxen_nic :07:00.3: eth3: GbE port initialized # ethtool -i p4p1 driver: netxen_nic version: 4.0.82 firmware-version: 4.0.593 bus-info: :07:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no # ./nxflash.bin -i p4p1 --info Board Type: 0x24 (NC375T PCI Express Quad Port Gigabit Server Adapter) Board Chip Rev: B2 Serial Id: TI13BK1960 Efuse ID: 0x Firmware version(on Flash): 4.0.593 Active Firmware version: 4.0.593 Driver version: 0.0.0 BIOS version: 2.1.0 MAC Addr 0: 78:AC:C0:10:F9:DC Subsystem ID: 0x1740103c PXE Status 0: Disabled WOL Status 0: Disabled # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3 Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x8 Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chi
[Kernel-packages] [Bug 1327908] Re: HP NC375T / phanfw.bin: firmware is older than flash / Direct firmware load failed with error -2 / HP firmware is newer in cards
** Attachment added: "Flash Utility for the NC375T and other cards" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327908/+attachment/4129307/+files/nxflash.bin -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1327908 Title: HP NC375T / phanfw.bin: firmware is older than flash / Direct firmware load failed with error -2 / HP firmware is newer in cards Status in “linux” package in Ubuntu: Confirmed Bug description: HP has a newer firmware on their NC375T server nics: 4.0.593 This generates an error at the startup of Ubuntu Server 14.04 LTS The version of phanfw.bin seems to be older. [ 16.573260] QLogic/NetXen Network Driver v4.0.82 [ 16.87] netxen_nic :07:00.0: 2MB memory map [ 16.812455] netxen_nic :07:00.0: phanfw.bin: firmware is older than flash [ 16.818949] netxen_nic :07:00.0: Direct firmware load failed with error -2 [ 16.818950] netxen_nic :07:00.0: Falling back to user helper [ 23.138390] netxen_nic :07:00.0: loading firmware from flash [ 27.586070] netxen_nic :07:00.0: Gen2 strapping detected [ 30.185964] netxen_nic :07:00.0: using 64-bit dma mask [ 30.373956] netxen_nic: Quad Gig LP Board S/N TI13BK1960 Chip rev 0x42 [ 30.450969] netxen_nic :07:00.0: Driver v4.0.82, firmware v4.0.593 [legacy] [ 39.718557] netxen_nic :07:00.0: irq 67 for MSI/MSI-X [ 39.718561] netxen_nic :07:00.0: irq 68 for MSI/MSI-X [ 39.718564] netxen_nic :07:00.0: irq 69 for MSI/MSI-X [ 39.718567] netxen_nic :07:00.0: irq 70 for MSI/MSI-X [ 39.718605] netxen_nic :07:00.0: using msi-x interrupts [ 39.780399] netxen_nic :07:00.0: non ULA adapter [ 39.841095] netxen_nic :07:00.0: eth0: GbE port initialized [ 39.901172] netxen_nic :07:00.1: 2MB memory map [ 39.959403] netxen_nic :07:00.1: using 64-bit dma mask [ 40.117279] netxen_nic :07:00.1: Driver v4.0.82, firmware v4.0.593 [legacy] [ 40.174172] netxen_nic :07:00.1: irq 71 for MSI/MSI-X [ 40.174175] netxen_nic :07:00.1: irq 72 for MSI/MSI-X [ 40.174178] netxen_nic :07:00.1: irq 73 for MSI/MSI-X [ 40.174181] netxen_nic :07:00.1: irq 74 for MSI/MSI-X [ 40.174209] netxen_nic :07:00.1: using msi-x interrupts [ 40.229992] netxen_nic :07:00.1: eth1: GbE port initialized [ 40.284766] netxen_nic :07:00.2: 2MB memory map [ 40.339836] netxen_nic :07:00.2: using 64-bit dma mask [ 40.465258] netxen_nic :07:00.2: Driver v4.0.82, firmware v4.0.593 [legacy] [ 40.522359] netxen_nic :07:00.2: irq 75 for MSI/MSI-X [ 40.522363] netxen_nic :07:00.2: irq 76 for MSI/MSI-X [ 40.522365] netxen_nic :07:00.2: irq 77 for MSI/MSI-X [ 40.522368] netxen_nic :07:00.2: irq 78 for MSI/MSI-X [ 40.522392] netxen_nic :07:00.2: using msi-x interrupts [ 40.578742] netxen_nic :07:00.2: eth2: GbE port initialized [ 40.634802] netxen_nic :07:00.3: 2MB memory map [ 40.690423] netxen_nic :07:00.3: using 64-bit dma mask [ 40.825233] netxen_nic :07:00.3: Driver v4.0.82, firmware v4.0.593 [legacy] [ 40.882915] netxen_nic :07:00.3: irq 79 for MSI/MSI-X [ 40.882919] netxen_nic :07:00.3: irq 80 for MSI/MSI-X [ 40.882922] netxen_nic :07:00.3: irq 81 for MSI/MSI-X [ 40.882925] netxen_nic :07:00.3: irq 82 for MSI/MSI-X [ 40.882951] netxen_nic :07:00.3: using msi-x interrupts [ 40.939825] netxen_nic :07:00.3: eth3: GbE port initialized # ethtool -i p4p1 driver: netxen_nic version: 4.0.82 firmware-version: 4.0.593 bus-info: :07:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no # ./nxflash.bin -i p4p1 --info Board Type: 0x24 (NC375T PCI Express Quad Port Gigabit Server Adapter) Board Chip Rev: B2 Serial Id: TI13BK1960 Efuse ID: 0x Firmware version(on Flash): 4.0.593 Active Firmware version: 4.0.593 Driver version: 0.0.0 BIOS version: 2.1.0 MAC Addr 0: 78:AC:C0:10:F9:DC Subsystem ID: 0x1740103c PXE Status 0: Disabled WOL Status 0: Disabled # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3 Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x8 Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) 00:1c.2 PCI bridge: Intel Cor
[Kernel-packages] [Bug 1327908] Re: HP NC375T / phanfw.bin: firmware is older than flash / Direct firmware load failed with error -2 / HP firmware is newer in cards
** Attachment added: "Flash Utility for the NC375T and other cards" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327908/+attachment/4129305/+files/nxflash -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1327908 Title: HP NC375T / phanfw.bin: firmware is older than flash / Direct firmware load failed with error -2 / HP firmware is newer in cards Status in “linux” package in Ubuntu: Confirmed Bug description: HP has a newer firmware on their NC375T server nics: 4.0.593 This generates an error at the startup of Ubuntu Server 14.04 LTS The version of phanfw.bin seems to be older. [ 16.573260] QLogic/NetXen Network Driver v4.0.82 [ 16.87] netxen_nic :07:00.0: 2MB memory map [ 16.812455] netxen_nic :07:00.0: phanfw.bin: firmware is older than flash [ 16.818949] netxen_nic :07:00.0: Direct firmware load failed with error -2 [ 16.818950] netxen_nic :07:00.0: Falling back to user helper [ 23.138390] netxen_nic :07:00.0: loading firmware from flash [ 27.586070] netxen_nic :07:00.0: Gen2 strapping detected [ 30.185964] netxen_nic :07:00.0: using 64-bit dma mask [ 30.373956] netxen_nic: Quad Gig LP Board S/N TI13BK1960 Chip rev 0x42 [ 30.450969] netxen_nic :07:00.0: Driver v4.0.82, firmware v4.0.593 [legacy] [ 39.718557] netxen_nic :07:00.0: irq 67 for MSI/MSI-X [ 39.718561] netxen_nic :07:00.0: irq 68 for MSI/MSI-X [ 39.718564] netxen_nic :07:00.0: irq 69 for MSI/MSI-X [ 39.718567] netxen_nic :07:00.0: irq 70 for MSI/MSI-X [ 39.718605] netxen_nic :07:00.0: using msi-x interrupts [ 39.780399] netxen_nic :07:00.0: non ULA adapter [ 39.841095] netxen_nic :07:00.0: eth0: GbE port initialized [ 39.901172] netxen_nic :07:00.1: 2MB memory map [ 39.959403] netxen_nic :07:00.1: using 64-bit dma mask [ 40.117279] netxen_nic :07:00.1: Driver v4.0.82, firmware v4.0.593 [legacy] [ 40.174172] netxen_nic :07:00.1: irq 71 for MSI/MSI-X [ 40.174175] netxen_nic :07:00.1: irq 72 for MSI/MSI-X [ 40.174178] netxen_nic :07:00.1: irq 73 for MSI/MSI-X [ 40.174181] netxen_nic :07:00.1: irq 74 for MSI/MSI-X [ 40.174209] netxen_nic :07:00.1: using msi-x interrupts [ 40.229992] netxen_nic :07:00.1: eth1: GbE port initialized [ 40.284766] netxen_nic :07:00.2: 2MB memory map [ 40.339836] netxen_nic :07:00.2: using 64-bit dma mask [ 40.465258] netxen_nic :07:00.2: Driver v4.0.82, firmware v4.0.593 [legacy] [ 40.522359] netxen_nic :07:00.2: irq 75 for MSI/MSI-X [ 40.522363] netxen_nic :07:00.2: irq 76 for MSI/MSI-X [ 40.522365] netxen_nic :07:00.2: irq 77 for MSI/MSI-X [ 40.522368] netxen_nic :07:00.2: irq 78 for MSI/MSI-X [ 40.522392] netxen_nic :07:00.2: using msi-x interrupts [ 40.578742] netxen_nic :07:00.2: eth2: GbE port initialized [ 40.634802] netxen_nic :07:00.3: 2MB memory map [ 40.690423] netxen_nic :07:00.3: using 64-bit dma mask [ 40.825233] netxen_nic :07:00.3: Driver v4.0.82, firmware v4.0.593 [legacy] [ 40.882915] netxen_nic :07:00.3: irq 79 for MSI/MSI-X [ 40.882919] netxen_nic :07:00.3: irq 80 for MSI/MSI-X [ 40.882922] netxen_nic :07:00.3: irq 81 for MSI/MSI-X [ 40.882925] netxen_nic :07:00.3: irq 82 for MSI/MSI-X [ 40.882951] netxen_nic :07:00.3: using msi-x interrupts [ 40.939825] netxen_nic :07:00.3: eth3: GbE port initialized # ethtool -i p4p1 driver: netxen_nic version: 4.0.82 firmware-version: 4.0.593 bus-info: :07:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no # ./nxflash.bin -i p4p1 --info Board Type: 0x24 (NC375T PCI Express Quad Port Gigabit Server Adapter) Board Chip Rev: B2 Serial Id: TI13BK1960 Efuse ID: 0x Firmware version(on Flash): 4.0.593 Active Firmware version: 4.0.593 Driver version: 0.0.0 BIOS version: 2.1.0 MAC Addr 0: 78:AC:C0:10:F9:DC Subsystem ID: 0x1740103c PXE Status 0: Disabled WOL Status 0: Disabled # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3 Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x8 Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) 00:1c.2 PCI bridge: Intel Corpora
[Kernel-packages] [Bug 1327908] Re: HP NC375T / phanfw.bin: firmware is older than flash / Direct firmware load failed with error -2 / HP firmware is newer in cards
Christopher, the test are done with the latest mainline kernel 3.15.0-031500-generic as mentioned earlier. With that kernel I get the messages as above. I think the netxen driver should be updated, so it can handle the latest firmware of HP too. The issue is there is no source code of the HP drivers available and the HP drivers are compiled for RedHat 4/5/6, Suse 10/11 and Solaris 10. Anybody on the Ubuntu Kernel team doing the netxen driver (I guess: https://github.com/Canonical-kernel/Ubuntu-kernel/tree/master/drivers/net/ethernet/qlogic/netxen) who can find out what the 2 fixes by HP contain? I guess they should know at QLogic too right? Or it this only known at HP? * Fix Receive Side Scaling distribution on W2K12 systems. * Fix incorrect reporting of checksum status for packets with TCP checksum error in promiscuous mode. (btw. the updated description was only the lspci info added now) ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1327908 Title: HP NC375T / phanfw.bin: firmware is older than flash / Direct firmware load failed with error -2 / HP firmware is newer in cards Status in “linux” package in Ubuntu: Confirmed Bug description: HP has a newer firmware on their NC375T server nics: 4.0.593 This generates an error at the startup of Ubuntu Server 14.04 LTS The version of phanfw.bin seems to be older. [ 16.573260] QLogic/NetXen Network Driver v4.0.82 [ 16.87] netxen_nic :07:00.0: 2MB memory map [ 16.812455] netxen_nic :07:00.0: phanfw.bin: firmware is older than flash [ 16.818949] netxen_nic :07:00.0: Direct firmware load failed with error -2 [ 16.818950] netxen_nic :07:00.0: Falling back to user helper [ 23.138390] netxen_nic :07:00.0: loading firmware from flash [ 27.586070] netxen_nic :07:00.0: Gen2 strapping detected [ 30.185964] netxen_nic :07:00.0: using 64-bit dma mask [ 30.373956] netxen_nic: Quad Gig LP Board S/N TI13BK1960 Chip rev 0x42 [ 30.450969] netxen_nic :07:00.0: Driver v4.0.82, firmware v4.0.593 [legacy] [ 39.718557] netxen_nic :07:00.0: irq 67 for MSI/MSI-X [ 39.718561] netxen_nic :07:00.0: irq 68 for MSI/MSI-X [ 39.718564] netxen_nic :07:00.0: irq 69 for MSI/MSI-X [ 39.718567] netxen_nic :07:00.0: irq 70 for MSI/MSI-X [ 39.718605] netxen_nic :07:00.0: using msi-x interrupts [ 39.780399] netxen_nic :07:00.0: non ULA adapter [ 39.841095] netxen_nic :07:00.0: eth0: GbE port initialized [ 39.901172] netxen_nic :07:00.1: 2MB memory map [ 39.959403] netxen_nic :07:00.1: using 64-bit dma mask [ 40.117279] netxen_nic :07:00.1: Driver v4.0.82, firmware v4.0.593 [legacy] [ 40.174172] netxen_nic :07:00.1: irq 71 for MSI/MSI-X [ 40.174175] netxen_nic :07:00.1: irq 72 for MSI/MSI-X [ 40.174178] netxen_nic :07:00.1: irq 73 for MSI/MSI-X [ 40.174181] netxen_nic :07:00.1: irq 74 for MSI/MSI-X [ 40.174209] netxen_nic :07:00.1: using msi-x interrupts [ 40.229992] netxen_nic :07:00.1: eth1: GbE port initialized [ 40.284766] netxen_nic :07:00.2: 2MB memory map [ 40.339836] netxen_nic :07:00.2: using 64-bit dma mask [ 40.465258] netxen_nic :07:00.2: Driver v4.0.82, firmware v4.0.593 [legacy] [ 40.522359] netxen_nic :07:00.2: irq 75 for MSI/MSI-X [ 40.522363] netxen_nic :07:00.2: irq 76 for MSI/MSI-X [ 40.522365] netxen_nic :07:00.2: irq 77 for MSI/MSI-X [ 40.522368] netxen_nic :07:00.2: irq 78 for MSI/MSI-X [ 40.522392] netxen_nic :07:00.2: using msi-x interrupts [ 40.578742] netxen_nic :07:00.2: eth2: GbE port initialized [ 40.634802] netxen_nic :07:00.3: 2MB memory map [ 40.690423] netxen_nic :07:00.3: using 64-bit dma mask [ 40.825233] netxen_nic :07:00.3: Driver v4.0.82, firmware v4.0.593 [legacy] [ 40.882915] netxen_nic :07:00.3: irq 79 for MSI/MSI-X [ 40.882919] netxen_nic :07:00.3: irq 80 for MSI/MSI-X [ 40.882922] netxen_nic :07:00.3: irq 81 for MSI/MSI-X [ 40.882925] netxen_nic :07:00.3: irq 82 for MSI/MSI-X [ 40.882951] netxen_nic :07:00.3: using msi-x interrupts [ 40.939825] netxen_nic :07:00.3: eth3: GbE port initialized # ethtool -i p4p1 driver: netxen_nic version: 4.0.82 firmware-version: 4.0.593 bus-info: :07:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no # ./nxflash.bin -i p4p1 --info Board Type: 0x24 (NC375T PCI Express Quad Port Gigabit Server Adapter) Board Chip Rev: B2 Serial Id: TI13BK1960 Efuse ID: 0x Firmware version(on Flash): 4.0.593 Active Firmware version: 4.0.593 Driver version: 0.0.0
[Kernel-packages] [Bug 1328708] 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/1328708 Title: system freezes periodically when I try to suspend to RAM Status in “linux” package in Ubuntu: Confirmed Bug description: About a couple times a week, my system freezes when I suspend to RAM (only way out is hard power off--alternative terminals are inaccessible). These seems to be happening more in KDE than when I was using Unity. KDE has a number of suspend issues for my system, which are mentioned in bug #1327625. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peterm 3598 F pulseaudio CurrentDesktop: KDE Date: Tue Jun 10 18:25:42 2014 HibernationDevice: RESUME=UUID=5d23be8c-e134-466b-8698-0344f70809a4 InstallationDate: Installed on 2014-04-20 (51 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-29-generic root=UUID=905a5deb-feac-448c-9f59-7040a9ea9942 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1B dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 17FB dmi.board.vendor: Hewlett-Packard dmi.board.version: 10.5A dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1B:bd10/23/2012:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058D11000220472622100:rvnHewlett-Packard:rn17FB:rvr10.5A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 058D11000220472622100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328708/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1280668] Re: [Medion MS-7857] Computer freezes or hangs during install, boot or usage
Ubuntu 10.04.4 LTS (Lucid Lynx) unable to boot the PC due to a Kernel panic. [0.812538] Kernel panic – not syncing : AMD-Vi : ILLEGAL_COMMAND_ERROR while resetting command buffer Ubuntu 10.10 (Maverick Meerkat) unable to boot the PC due to a Kernel panic. But I wasn’t able to capture the complete error. Ubuntu 11.04 (Natty Narwhal) unable to boot the PC due to a Kernel panic. But I wasn’t able to capture the complete error. Ubuntu 11.10 (Oneiric Ocelot) the computer boot up and hang up for more than 20 minutes. I wasn’t able to work with the computer or get any logs. However, the last message in console was: [147.992078] AMD-Vi : Completion-Wait loop timed out After these tests the problem appeared for first time in the release Ubuntu 11.10 (Oneiric Ocelot). And with previous Ubuntu versions this PC is unable to boot. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1280668 Title: [Medion MS-7857] Computer freezes or hangs during install, boot or usage Status in “linux” package in Ubuntu: Confirmed Bug description: Every time I tried to install this new it was hanging during the install or even before during boot. This system is a pre-installed windows 8 (64bits). In the file /var/log/dmesg I can see the following: [ 28.119124] BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:1] [ 28.119127] Modules linked in: [ 28.119130] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.11.0-15-generic #25~precise1-Ubuntu [ 28.119132] Hardware name: MEDION MS-7857/MS-7857, BIOS M7857W08.203 01/06/2014 [ 28.119133] task: 88042962 ti: 880429628000 task.ti: 880429628000 [ 28.119134] RIP: 0010:[] [] delay_tsc+0x42/0x80 [ 28.119140] RSP: :880429629c68 EFLAGS: 0246 [ 28.119141] RAX: 001c549ce3bd RBX: 032f RCX: 549ce3bd [ 28.119142] RDX: 0cf2 RSI: 0282 RDI: 0e50 [ 28.119143] RBP: 880429629c88 R08: 2000 R09: [ 28.119144] R10: 0330 R11: 0720072007200720 R12: 0026 [ 28.119145] R13: 81ef8bc2 R14: 0246 R15: 880429629c38 [ 28.119147] FS: () GS:88043ec0() knlGS: [ 28.119148] CS: 0010 DS: ES: CR0: 8005003b [ 28.119149] CR2: 88043efff000 CR3: 01c0d000 CR4: 000407f0 [ 28.119150] Stack: [ 28.119153] 1a0e 880429629cf0 1ff0 880429579814 [ 28.119162] 880429629c98 813802bc 880429629cb8 81607e55 [ 28.119164] 880429579800 2000 880429629d28 81607f57 [ 28.119167] Call Trace: [ 28.119170] [] __const_udelay+0x2c/0x30 [ 28.119174] [] wait_on_sem+0x35/0x70 [ 28.119176] [] iommu_queue_command_sync+0xc7/0x140 [ 28.119178] [] iommu_queue_command+0x13/0x20 [ 28.119183] [] iommu_flush_all_caches+0x9d/0xf0 [ 28.119185] [] early_enable_iommus+0x61/0x160 [ 28.119189] [] ? memblock_find_dma_reserve+0x13d/0x13d [ 28.119192] [] state_next+0xbf/0x201 [ 28.119194] [] ? memblock_find_dma_reserve+0x13d/0x13d [ 28.119196] [] iommu_go_to_state+0x14/0x2f [ 28.119197] [] amd_iommu_init+0x13/0xff [ 28.119200] [] ? load_default_modules+0x9/0xb [ 28.119203] [] pci_iommu_init+0x13/0x3e [ 28.119206] [] do_one_initcall+0xfa/0x1b0 [ 28.119208] [] ? parse_args+0xd0/0x1d0 [ 28.119211] [] ? do_early_param+0x87/0x87 [ 28.119213] [] do_basic_setup+0x96/0xb9 [ 28.119215] [] ? do_early_param+0x87/0x87 [ 28.119218] [] ? sched_init_smp+0x119/0x11b [ 28.119220] [] kernel_init_freeable+0xb8/0x131 [ 28.119224] [] ? rest_init+0x80/0x80 [ 28.119226] [] kernel_init+0xe/0xf0 [ 28.119229] [] ret_from_fork+0x7c/0xb0 [ 28.119231] [] ? rest_init+0x80/0x80 [ 28.119232] Code: 25 64 b0 00 00 0f ae f0 66 66 90 e8 c9 b0 c9 ff 66 90 41 89 c4 eb 11 66 90 f3 90 65 8b 1c 25 64 b0 00 00 41 39 dd 75 20 0f ae f0 <66> 66 90 e8 a6 b0 c9 ff 66 90 89 c2 44 29 e2 44 39 f2 72 da 5b [ 28.219649] AMD-Vi: Completion-Wait loop timed out WORKAROUND: I was able to complete the install passing the following kernel parameter, then the computer boots fine but hangs for between 25 to 2 minutes and then continues working. I would expect the computer not to hang: noapic --- ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.11.0-15-generic 3.11.0-15.25~precise1 [modified: boot/vmlinuz-3.11.0-15-generic] ProcVersionSignature: Ubuntu 3.11.0-15.25~precise1-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.11.0-15-generic. ApportVe
[Kernel-packages] [Bug 1327908] Re: HP NC375T / phanfw.bin: firmware is older than flash / Direct firmware load failed with error -2 / HP firmware is newer in cards
apport information ** Description changed: HP has a newer firmware on their NC375T server nics: 4.0.593 This generates an error at the startup of Ubuntu Server 14.04 LTS The version of phanfw.bin seems to be older. [ 16.573260] QLogic/NetXen Network Driver v4.0.82 [ 16.87] netxen_nic :07:00.0: 2MB memory map [ 16.812455] netxen_nic :07:00.0: phanfw.bin: firmware is older than flash [ 16.818949] netxen_nic :07:00.0: Direct firmware load failed with error -2 [ 16.818950] netxen_nic :07:00.0: Falling back to user helper [ 23.138390] netxen_nic :07:00.0: loading firmware from flash [ 27.586070] netxen_nic :07:00.0: Gen2 strapping detected [ 30.185964] netxen_nic :07:00.0: using 64-bit dma mask [ 30.373956] netxen_nic: Quad Gig LP Board S/N TI13BK1960 Chip rev 0x42 [ 30.450969] netxen_nic :07:00.0: Driver v4.0.82, firmware v4.0.593 [legacy] [ 39.718557] netxen_nic :07:00.0: irq 67 for MSI/MSI-X [ 39.718561] netxen_nic :07:00.0: irq 68 for MSI/MSI-X [ 39.718564] netxen_nic :07:00.0: irq 69 for MSI/MSI-X [ 39.718567] netxen_nic :07:00.0: irq 70 for MSI/MSI-X [ 39.718605] netxen_nic :07:00.0: using msi-x interrupts [ 39.780399] netxen_nic :07:00.0: non ULA adapter [ 39.841095] netxen_nic :07:00.0: eth0: GbE port initialized [ 39.901172] netxen_nic :07:00.1: 2MB memory map [ 39.959403] netxen_nic :07:00.1: using 64-bit dma mask [ 40.117279] netxen_nic :07:00.1: Driver v4.0.82, firmware v4.0.593 [legacy] [ 40.174172] netxen_nic :07:00.1: irq 71 for MSI/MSI-X [ 40.174175] netxen_nic :07:00.1: irq 72 for MSI/MSI-X [ 40.174178] netxen_nic :07:00.1: irq 73 for MSI/MSI-X [ 40.174181] netxen_nic :07:00.1: irq 74 for MSI/MSI-X [ 40.174209] netxen_nic :07:00.1: using msi-x interrupts [ 40.229992] netxen_nic :07:00.1: eth1: GbE port initialized [ 40.284766] netxen_nic :07:00.2: 2MB memory map [ 40.339836] netxen_nic :07:00.2: using 64-bit dma mask [ 40.465258] netxen_nic :07:00.2: Driver v4.0.82, firmware v4.0.593 [legacy] [ 40.522359] netxen_nic :07:00.2: irq 75 for MSI/MSI-X [ 40.522363] netxen_nic :07:00.2: irq 76 for MSI/MSI-X [ 40.522365] netxen_nic :07:00.2: irq 77 for MSI/MSI-X [ 40.522368] netxen_nic :07:00.2: irq 78 for MSI/MSI-X [ 40.522392] netxen_nic :07:00.2: using msi-x interrupts [ 40.578742] netxen_nic :07:00.2: eth2: GbE port initialized [ 40.634802] netxen_nic :07:00.3: 2MB memory map [ 40.690423] netxen_nic :07:00.3: using 64-bit dma mask [ 40.825233] netxen_nic :07:00.3: Driver v4.0.82, firmware v4.0.593 [legacy] [ 40.882915] netxen_nic :07:00.3: irq 79 for MSI/MSI-X [ 40.882919] netxen_nic :07:00.3: irq 80 for MSI/MSI-X [ 40.882922] netxen_nic :07:00.3: irq 81 for MSI/MSI-X [ 40.882925] netxen_nic :07:00.3: irq 82 for MSI/MSI-X [ 40.882951] netxen_nic :07:00.3: using msi-x interrupts [ 40.939825] netxen_nic :07:00.3: eth3: GbE port initialized # ethtool -i p4p1 driver: netxen_nic version: 4.0.82 firmware-version: 4.0.593 bus-info: :07:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no # ./nxflash.bin -i p4p1 --info Board Type: 0x24 (NC375T PCI Express Quad Port Gigabit Server Adapter) Board Chip Rev: B2 Serial Id: TI13BK1960 Efuse ID: 0x Firmware version(on Flash): 4.0.593 Active Firmware version: 4.0.593 Driver version: 0.0.0 BIOS version: 2.1.0 - MAC Addr 0: 78:AC:C0:10:F9:DC + MAC Addr 0: 78:AC:C0:10:F9:DC Subsystem ID: 0x1740103c PXE Status 0: Disabled WOL Status 0: Disabled - --- + + # lspci + 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3 Processor DRAM Controller (rev 06) + 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) + 00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x8 Controller (rev 06) + 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) + 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) + 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) + 00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5) + 00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5) + 00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 (rev d5) + 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) + 00:1f.0 ISA bridge: Intel Corporation C222
[Kernel-packages] [Bug 1327828] Re: [Asus G53JW] Cannot change keyboard backlight brightness
Could not complete kernel testing since the video card driver didn't like the new kernel. The resolution was incorrect. I am a nub and didn't know how to correct. Going back to old kernel fixed the problem. linux-image-3.15.0-031500-generic_3.15.0-031500.201406081435_amd64 linux-headers-3.15.0-031500-generic_3.15.0-031500.201406081435_amd64 I should add I had to do the following to fix the screen back light on 13.10 and 14.04: 1) Go to Nvidia settings and save config into xorg.conf (the file will be at /etc/X11) 2) In xorg.conf in the "Device" section for your GPU add (use sudo to edit with your favorite editor) Option "RegistryDwords" "EnableBrightnessControl=1" 3) restart X and brightness works or reboot ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1327828 Title: [Asus G53JW] Cannot change keyboard backlight brightness Status in “linux” package in Ubuntu: Confirmed Bug description: When pressing function key plus F3 or F4 the backlight on the keyboard does not change. This was working on a Ubuntu 13.10. No longer works in ubuntu 14.04. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: sonwon 2028 F pulseaudio /dev/snd/controlC1: sonwon 2028 F pulseaudio /dev/snd/controlC0: sonwon 2028 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=4d6d29f4-40a8-44cf-80ea-f0fd044e7f80 InstallationDate: Installed on 2014-06-08 (1 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: ASUSTeK Computer Inc. G53JW NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=7eb10043-4463-42ac-bef7-723d8c108f94 ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 Tags: trusty Uname: Linux 3.13.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/28/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G53JW.211 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G53JW 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.:bvrG53JW.211:bd01/28/2011:svnASUSTeKComputerInc.:pnG53JW:pvr1.0:rvnASUSTeKComputerInc.:rnG53JW:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: G53JW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327828/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328708] [NEW] system freezes periodically when I try to suspend to RAM
Public bug reported: About a couple times a week, my system freezes when I suspend to RAM (only way out is hard power off--alternative terminals are inaccessible). These seems to be happening more in KDE than when I was using Unity. KDE has a number of suspend issues for my system, which are mentioned in bug #1327625. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peterm 3598 F pulseaudio CurrentDesktop: KDE Date: Tue Jun 10 18:25:42 2014 HibernationDevice: RESUME=UUID=5d23be8c-e134-466b-8698-0344f70809a4 InstallationDate: Installed on 2014-04-20 (51 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-29-generic root=UUID=905a5deb-feac-448c-9f59-7040a9ea9942 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1B dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 17FB dmi.board.vendor: Hewlett-Packard dmi.board.version: 10.5A dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1B:bd10/23/2012:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058D11000220472622100:rvnHewlett-Packard:rn17FB:rvr10.5A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 058D11000220472622100 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1328708 Title: system freezes periodically when I try to suspend to RAM Status in “linux” package in Ubuntu: New Bug description: About a couple times a week, my system freezes when I suspend to RAM (only way out is hard power off--alternative terminals are inaccessible). These seems to be happening more in KDE than when I was using Unity. KDE has a number of suspend issues for my system, which are mentioned in bug #1327625. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peterm 3598 F pulseaudio CurrentDesktop: KDE Date: Tue Jun 10 18:25:42 2014 HibernationDevice: RESUME=UUID=5d23be8c-e134-466b-8698-0344f70809a4 InstallationDate: Installed on 2014-04-20 (51 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-29-generic root=UUID=905a5deb-feac-448c-9f59-7040a9ea9942 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1B dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 17FB dmi.board.vendor: Hewlett-Packard dmi.board.version: 10.5A dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1B:bd10/23/2012:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058D11000220472622100:rvnHewlett-Packard:rn17FB:rvr10.5A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 058D11000220472622100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328708/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1313450] Re: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2 or Xen) with default configuration
A simple test case was created by Steven Noonan to trigger the issue: Copy the attached code into a file named bugtest.c Compile with "gcc -o bugtest bugtest.c" Run ./bugtest (does not have to be run as root) If you see no output, bug does not exist; if it does you will immediately see something similar to: triden@tweety:~$ ./bugtest [ 837.276658] BUG: Bad page map in process bugtest pte:8965 pmd:3c076067 [ 837.27] page:ea00 count:-31 mapcount:-31 mapping: (null) index:0x0 [ 837.276669] page flags: 0x10(dirty) [ 837.276672] page dumped because: bad pte [ 837.276674] addr:7f0639a5e000 vm_flags:08100071 anon_vma:88003b1fdbc0 mapping: (null) index:7f0639a5e [ 837.276821] BUG: Bad rss-counter state mm:88003d2e8700 idx:0 val:-1 [ 837.276825] BUG: Bad rss-counter state mm:88003d2e8700 idx:1 val:1 Reference: https://lkml.org/lkml/2014/1/21/544 ** Attachment added: "testcase program" https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1313450/+attachment/4129266/+files/xen-bug.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/1313450 Title: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2 or Xen) with default configuration Status in “linux” package in Ubuntu: Confirmed Status in “vsftpd” package in Ubuntu: Invalid Status in “linux” source package in Trusty: Confirmed Status in “vsftpd” source package in Trusty: Invalid Bug description: The configuration submitted was modified during testing, but this also failed with the default configuration. The only solution I have found so far was to delete the configuration, this would allow the service to start, but obviously not work as intended. If I try to start the service manually using vsftpd or sudo vsftpd I receive the following error message: 500 OOPS: munmap I also tried the default commands /etc/init.d/vsftpd or service vsftpd start ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: vsftpd 3.0.2-1ubuntu2 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Sun Apr 27 21:23:18 2014 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1b Ec2InstanceType: t1.micro Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vsftpd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.vsftpd.conf: [modified] mtime.conffile..etc.vsftpd.conf: 2014-04-27T21:16:28.222467 --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1b Ec2InstanceType: t1.micro Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable Package: vsftpd 3.0.2-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 Tags: trusty ec2-images Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True modified.conffile..etc.vsftpd.conf: [modified] mtime.conffile..etc.vsftpd.conf: 2014-04-29T19:03:28.834467 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313450/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328088] Re: Kernel network namespace performance regression during rcu development on kernels above 3.8
** 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/1328088 Title: Kernel network namespace performance regression during rcu development on kernels above 3.8 Status in The Linux Kernel: In Progress Status in “linux” package in Ubuntu: New Bug description: Please, follow this in: http://people.canonical.com/~inaddy/lp1328088/. Same description on daily-basis updated text. -- It was brought to my attention that "fake router creation" scalability was affected during kernel development. The following script was used for all the tests and charts generation: http://people.canonical.com/~inaddy/lp1328088/make_fake_routers.sh http://people.canonical.com/~inaddy/lp1328088/parse.py I measured how many "fake routers" (above script) could be added per second from 0 to 4000 created routers mark. Using this script and a git bisect on kernel tree I was led to one specific commit causing regression: #911af505 "rcu: Provide compile-time control for no-CBs CPUs". It appeared that rcu, rcu callbacks and no-cb cpus were causing the issue so every commit that changed any of this files: "kernel/rcutree.c kernel/rcutree.h kernel/rcutree_plugin.h include/trace/events/rcu.h include/linux/rcupdate.h" was tested. The idea was to check performance regression during rcu development. In the worst case I would have data for performance regression during kernel development (since we have rcu commits from 3.8 to 3.14). All text below this refer to 2 groups of charts, generated during the study: 1) Kernel git tags from 3.8 to 3.14. http://people.canonical.com/~inaddy/lp1328088/charts/250-tag.html 2) Kernel git commits for rcu development (111 commits). http://people.canonical.com/~inaddy/lp1328088/charts/250.html Since there was difference in results depending on how many cpus or how the no-cb cpus were configured, 3 kernel config options were used on every measure: - CONFIG_RCU_NOCB_CPU (disabled: nocbno) - CONFIG_RCU_NOCB_CPU_ALL (enabled: nocball) - CONFIG_RCU_NOCB_CPU_NONE (enabled: nocbnone) After charts generation and study it was clear that NOCB_CPU_ALL (4 cpus) affected the "fake routers" creation process performance and this regression continues up to upstream version. It was also clear that, after this commit, there is no scalability executing this test with more than 1 cpu. Comparing standing out points (see charts): #81e5949 - good #911af50 - bad #6faf728 - not good enough I was able to see that from the script above the following lines were affected: 1) ip netns add -> huge performance regression 2) ip netns exec -> some performance regression # # Assumption # rcu callbacks being offloaded to other cpus caused regression in unshare(CLONE_NEWNET) code. # Specific kernel entry being investigated: unshare(CLONE_NEWNET) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1328088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1327979] Re: window content not repaint
Thanks reply Christopher, re using Gnome2-like interfaces, may get round to investigating sometime. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1327979 Title: window content not repaint Status in “linux” package in Ubuntu: Invalid Bug description: The bug appeared after installing the linux-image-2.6.32-61-generic package. The bug doesn't happen when I manually booted with the image from linux-image-2.6.32-60 (ESC key when Grub countdown and select the "60" kernel). I first though it was a firefox bug. I uninstalled "flash-plugin- installer" but the problem still occur : I couldn't use the window content nor the menu bar. I next installed Midori and lauchned it. It worked well for a few minutes. Then I had the same issue (window content frozen, can't access to the menu bar). I notice that a virtual console (GNOME Terminal) had the same issue. I installed the proprietary graphic driver from NVIDIA but it didn't fix the bug. I finally went back to the previous kernel and the bug disappeared. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-61-generic 2.6.32-61.124 Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.32-60.122-generic 2.6.32.61+drm33.26 Uname: Linux 2.6.32-60-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: j 1302 F pulseaudio /dev/snd/pcmC0D0p: j 1302 F...m pulseaudio CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type Card0.Amixer.info: Card hw:0 'NVidia'/'HDA NVidia at 0xdddf8000 irq 22' Mixer name : 'Analog Devices AD1988' Components : 'HDA:11d41988,10438241,00100400' Controls : 40 Simple ctrls : 23 Date: Mon Jun 9 09:51:56 2014 HibernationDevice: RESUME=UUID=c7f7fe9c-e1cd-4b24-8c8e-84a7d1337874 Lsusb: Bus 002 Device 002: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-60-generic root=UUID=61eae3b7-cc04-4622-bc67-2e883b1a5b2e ro quiet splash ProcEnviron: LANGUAGE=fr_FR:fr:en_GB:en PATH=(custom, no user) LANG=fr_FR.utf8 SHELL=/bin/bash RelatedPackageVersions: linux-firmware 1.34.14 RfKill: SourcePackage: linux dmi.bios.date: 05/28/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd05/28/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328674] 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/1328674 Title: Asus UX31E turns off doesn't hibernate on empty battery Status in “linux” package in Ubuntu: Confirmed Bug description: On low battery, my ASus UX31E Zenbook simply turns off power even though power settings say to hibernate when battery is critically low. Hibernating works otherwise. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.54 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zach 1862 F pulseaudio CurrentDesktop: Unity Date: Tue Jun 10 22:10:27 2014 HibernationDevice: RESUME=UUID=6ff901b8-a6b6-4771-a1a4-e25f5370816b InstallationDate: Installed on 2012-05-01 (770 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) MachineType: ASUSTeK Computer Inc. UX31E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=db8fc294-e837-4964-a660-b0ee544109c5 ro quiet splash pcie_aspm=force drm.vblankoffdelay=1 i915.i915_enable_rc6=1 i915.semaphores=1 i915.powersave=1 "acpi_os_name=Microsoft Windows XP" vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.2 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: Upgraded to trusty on 2014-04-28 (43 days ago) dmi.bios.date: 08/14/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX31E.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX31E 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.:bvrUX31E.214:bd08/14/2012:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: UX31E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328673] 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/1328673 Title: Playstation 3 gamepad does not get a device created Status in “linux” package in Ubuntu: Confirmed Bug description: The newer Ubuntu kernel 3.13.0.27-generic breaks my Sony Playstation 3 gamepad. A device entry does not get created for it. I had to migrate back to the older 3.13.0.24-generic kernel. Note that the extra packages are installed for both of these kernels so it has nothing to do with the omission of the extras kernel package. This problem happens at boot time with the newer kernel installed. The kernel log claims that the operational mode cannot be set for the controller. I believe the following is the most informative. Also the entry for the gamepad is omitted when running lsusb probably because no device exists for it either. This also happens on the 3.13.0.29-generic kernel. Ouput from lsb_release -rd: Ubuntu 14.04 LTS This is dmesg on a good kernel: Using Ubuntu kernel 3.13.0.24-generic Jun 2 09:36:58 localhost kernel: [4.123307] usb 1-3.1.3: new full-speed USB device number 7 using ehci-pci Jun 2 09:36:58 localhost kernel: [4.234026] usb 1-3.1.3: New USB device found, idVendor=054c, idProduct=0268 Jun 2 09:36:58 localhost kernel: [4.234094] usb 1-3.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 2 09:36:58 localhost kernel: [4.234171] usb 1-3.1.3: Product: PLAYSTATION(R)3 Controller Jun 2 09:36:58 localhost kernel: [4.234237] usb 1-3.1.3: Manufacturer: Sony Jun 2 09:36:58 localhost kernel: [4.242847] sony 0003:054C:0268.0003: Fixing up Sony Sixaxis report descriptor Jun 2 09:36:58 localhost kernel: [4.268720] input: Sony PLAYSTATION(R)3 Controller as /devices/pci:00/:00:13.5/usb1/1-3/1-3.1/1-3.1.3/1-3.1.3:1.0/input/input6 Jun 2 09:36:58 localhost kernel: [4.268971] sony 0003:054C:0268.0003: input,hiddev0,hidraw1: USB HID v1.11 Joystick [Sony PLAYSTATION(R)3 Controller] on usb-:00:13.5-3.1.3/input0 This is dmesg on the newer kernel: Using Ubuntu kernel 3.13.0.27-generic May 29 09:20:58 localhost kernel: [4.123491] usb 1-3.1.3: new full-speed USB device number 7 using ehci-pci May 29 09:20:58 localhost kernel: [4.234206] usb 1-3.1.3: New USB device found, idVendor=054c, idProduct=0268 May 29 09:20:58 localhost kernel: [4.234275] usb 1-3.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 May 29 09:20:58 localhost kernel: [4.234352] usb 1-3.1.3: Product: PLAYSTATION(R)3 Controller May 29 09:20:58 localhost kernel: [4.234418] usb 1-3.1.3: Manufacturer: Sony May 29 09:20:58 localhost kernel: [4.243617] sony 0003:054C:0268.0003: Fixing up Sony Sixaxis report descriptor May 29 09:20:58 localhost kernel: [4.269540] input: Sony PLAYSTATION(R)3 Controller as /devices/pci:00/:00:13.5/usb1/1-3/1-3.1/1-3.1.3/1-3.1.3:1.0/input/input6 May 29 09:20:58 localhost kernel: [4.269779] sony 0003:054C:0268.0003: input,hiddev0,hidraw1: USB HID v1.11 Joystick [Sony PLAYSTATION(R)3 Controller] on usb-:00:13.5-3.1.3/input0 May 29 09:20:58 localhost kernel: [4.269863] sony 0003:054C:0268.0003: can't set operational mode May 29 09:20:58 localhost kernel: [4.275222] sony: probe of 0003:054C:0268.0003 failed with error -38 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-27-generic 3.13.0-27.50 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: smitty 3101 F pulseaudio CurrentDesktop: KDE Date: Tue Jun 10 15:54:02 2014 HibernationDevice: RESUME=UUID=4001960a-c07d-4731-af22-47abce9408b6 InstallationDate: Installed on 2014-04-17 (53 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7388 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=b1e4a07d-688e-472b-a067-aa7e1045e057 ro RelatedPackageVersions: linux-restricted-modules-3.13.0-27-generic N/A linux-backports-modules-3.13.0-27-generic N/A linux-firmware 1.127.2 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/12/2008 dmi.bios.vendor: A
[Kernel-packages] [Bug 1324571] Re: powerpc: enable powernv-cpufreq as built-in (vs. module)
The claim that "That cpufreq driver fails gracefully on other (non IBM, OPAL) powerpc platforms that don't have the expected files in the device-tree" seems to imply it should be perfectly harmless on pre- power8 platforms. Of course, I'll put it through its paces on a couple such machines to make sure anyway. :P -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1324571 Title: powerpc: enable powernv-cpufreq as built-in (vs. module) Status in “linux” package in Ubuntu: Fix Committed Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Committed Bug description: The cpufreq driver for powernv is currently built as a module (powernv-cpufreq.ko; see bug 1309576). It is not automatically loaded in the boot process (even when included in the initrd). It is desirable to have it built-in so it automatically loads on systems booting in PowerNV mode. One of the reaons is to save power by default (the default cpufreq governor is ondemand). That cpufreq driver fails gracefully on other (non IBM, OPAL) powerpc platforms that don't have the expected files in the device-tree (see [2]). A patch will be sent to the kernel-team mailing list. Thanks. [1] https://lists.ubuntu.com/archives/kernel- team/2014-April/042431.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1324571/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1324571] Re: powerpc: enable powernv-cpufreq as built-in (vs. module)
(And, for the record, it only needs to be on in the powerpc64-smp flavour, as none of the other flavours could conceivably boot on a POWER8/OPAL system anyway) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1324571 Title: powerpc: enable powernv-cpufreq as built-in (vs. module) Status in “linux” package in Ubuntu: Fix Committed Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Committed Bug description: The cpufreq driver for powernv is currently built as a module (powernv-cpufreq.ko; see bug 1309576). It is not automatically loaded in the boot process (even when included in the initrd). It is desirable to have it built-in so it automatically loads on systems booting in PowerNV mode. One of the reaons is to save power by default (the default cpufreq governor is ondemand). That cpufreq driver fails gracefully on other (non IBM, OPAL) powerpc platforms that don't have the expected files in the device-tree (see [2]). A patch will be sent to the kernel-team mailing list. Thanks. [1] https://lists.ubuntu.com/archives/kernel- team/2014-April/042431.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1324571/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1313591] Re: Panic on 3.13.0-24 with bnx2, iptables and MASQUERADE
Afaik I've tested with the kernel as requested and it seems to happen there as well. Also I tested using VXLAN and the same or alike panics seems to happen there too . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1313591 Title: Panic on 3.13.0-24 with bnx2, iptables and MASQUERADE Status in “linux” package in Ubuntu: Incomplete Bug description: I get a panic when I use MASQUERADE on a subnet towards a nic that's bnx2. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 28 11:15 seq crw-rw 1 root audio 116, 33 Apr 28 11:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' 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: 'iw' Date: Mon Apr 28 11:27:29 2014 HibernationDevice: RESUME=/dev/mapper/vg_root-lv_swap InstallationDate: Installed on 2014-03-28 (30 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Alpha amd64+mac (20140222) MachineType: HP ProLiant DL380 G7 PciMultimedia: ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/vg_root-lv_root ro biosdevname=0 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 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2011 dmi.bios.vendor: HP dmi.bios.version: P67 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP67:bd05/05/2011:svnHP:pnProLiantDL380G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328392] Re: [Asus X550LD] Touchpad not working - Ubuntu 14.04
Hi Cristopher. As requested, I updated the BIOS. this is the output of the command you suggested: X550LD.306 05/14/2014 I haven't noticed any substantial change, same behaviour as described in the bug description. I'm not sure what you mean by "Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful." Any suggestion or advise on how to proceed is welcome. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1328392 Title: [Asus X550LD] Touchpad not working - Ubuntu 14.04 Status in “linux” package in Ubuntu: Incomplete Bug description: Touchpad on the Asus X550LD is not working on Ubuntu 14.04 with either default or mainline kernel 3.15.0-031500-generic. Cursor does make some movements if you insist toying and clicking on the touchpad, but only seldomly (just using it normally often would produce no move), and in a direction that apparently has no relation with touch. Generally moves towards bottom, bottom/left, but insisting one can have patchy movements in other directions. However, clicking has no effect. Mouse connected with USB works normally, until you try to use the touchpad. If you touch the touchpad, the cursor mostly keeps on moving as per the mouse, but click mostly does not work. Logging out and logging in or restarting fixes the problem. WORKAROUND: Use external USB mouse but don't touch the touchpad. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: g 1530 F pulseaudio /dev/snd/controlC0: g 1530 F pulseaudio CurrentDesktop: GNOME Date: Tue Jun 10 08:18:41 2014 HibernationDevice: RESUME=UUID=205b0b44-7997-42f7-806d-3b367ebfdceb InstallationDate: Installed on 2014-06-09 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: ASUSTeK COMPUTER INC. X550LD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic.efi.signed root=UUID=ee58b2b6-1d8c-4137-beca-6a52a4634265 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LD.300:bd01/17/2014:svnASUSTeKCOMPUTERINC.:pnX550LD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550LD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328673] [NEW] Playstation 3 gamepad does not get a device created
Public bug reported: The newer Ubuntu kernel 3.13.0.27-generic breaks my Sony Playstation 3 gamepad. A device entry does not get created for it. I had to migrate back to the older 3.13.0.24-generic kernel. Note that the extra packages are installed for both of these kernels so it has nothing to do with the omission of the extras kernel package. This problem happens at boot time with the newer kernel installed. The kernel log claims that the operational mode cannot be set for the controller. I believe the following is the most informative. Also the entry for the gamepad is omitted when running lsusb probably because no device exists for it either. This also happens on the 3.13.0.29-generic kernel. Ouput from lsb_release -rd: Ubuntu 14.04 LTS This is dmesg on a good kernel: Using Ubuntu kernel 3.13.0.24-generic Jun 2 09:36:58 localhost kernel: [4.123307] usb 1-3.1.3: new full-speed USB device number 7 using ehci-pci Jun 2 09:36:58 localhost kernel: [4.234026] usb 1-3.1.3: New USB device found, idVendor=054c, idProduct=0268 Jun 2 09:36:58 localhost kernel: [4.234094] usb 1-3.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 2 09:36:58 localhost kernel: [4.234171] usb 1-3.1.3: Product: PLAYSTATION(R)3 Controller Jun 2 09:36:58 localhost kernel: [4.234237] usb 1-3.1.3: Manufacturer: Sony Jun 2 09:36:58 localhost kernel: [4.242847] sony 0003:054C:0268.0003: Fixing up Sony Sixaxis report descriptor Jun 2 09:36:58 localhost kernel: [4.268720] input: Sony PLAYSTATION(R)3 Controller as /devices/pci:00/:00:13.5/usb1/1-3/1-3.1/1-3.1.3/1-3.1.3:1.0/input/input6 Jun 2 09:36:58 localhost kernel: [4.268971] sony 0003:054C:0268.0003: input,hiddev0,hidraw1: USB HID v1.11 Joystick [Sony PLAYSTATION(R)3 Controller] on usb-:00:13.5-3.1.3/input0 This is dmesg on the newer kernel: Using Ubuntu kernel 3.13.0.27-generic May 29 09:20:58 localhost kernel: [4.123491] usb 1-3.1.3: new full-speed USB device number 7 using ehci-pci May 29 09:20:58 localhost kernel: [4.234206] usb 1-3.1.3: New USB device found, idVendor=054c, idProduct=0268 May 29 09:20:58 localhost kernel: [4.234275] usb 1-3.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 May 29 09:20:58 localhost kernel: [4.234352] usb 1-3.1.3: Product: PLAYSTATION(R)3 Controller May 29 09:20:58 localhost kernel: [4.234418] usb 1-3.1.3: Manufacturer: Sony May 29 09:20:58 localhost kernel: [4.243617] sony 0003:054C:0268.0003: Fixing up Sony Sixaxis report descriptor May 29 09:20:58 localhost kernel: [4.269540] input: Sony PLAYSTATION(R)3 Controller as /devices/pci:00/:00:13.5/usb1/1-3/1-3.1/1-3.1.3/1-3.1.3:1.0/input/input6 May 29 09:20:58 localhost kernel: [4.269779] sony 0003:054C:0268.0003: input,hiddev0,hidraw1: USB HID v1.11 Joystick [Sony PLAYSTATION(R)3 Controller] on usb-:00:13.5-3.1.3/input0 May 29 09:20:58 localhost kernel: [4.269863] sony 0003:054C:0268.0003: can't set operational mode May 29 09:20:58 localhost kernel: [4.275222] sony: probe of 0003:054C:0268.0003 failed with error -38 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-27-generic 3.13.0-27.50 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: smitty 3101 F pulseaudio CurrentDesktop: KDE Date: Tue Jun 10 15:54:02 2014 HibernationDevice: RESUME=UUID=4001960a-c07d-4731-af22-47abce9408b6 InstallationDate: Installed on 2014-04-17 (53 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7388 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=b1e4a07d-688e-472b-a067-aa7e1045e057 ro RelatedPackageVersions: linux-restricted-modules-3.13.0-27-generic N/A linux-backports-modules-3.13.0-27-generic N/A linux-firmware 1.127.2 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/12/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.7 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7388 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd06/12/2008:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7388:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7388:rvr1.
[Kernel-packages] [Bug 1328674] [NEW] Asus UX31E turns off doesn't hibernate on empty battery
Public bug reported: On low battery, my ASus UX31E Zenbook simply turns off power even though power settings say to hibernate when battery is critically low. Hibernating works otherwise. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.54 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zach 1862 F pulseaudio CurrentDesktop: Unity Date: Tue Jun 10 22:10:27 2014 HibernationDevice: RESUME=UUID=6ff901b8-a6b6-4771-a1a4-e25f5370816b InstallationDate: Installed on 2012-05-01 (770 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) MachineType: ASUSTeK Computer Inc. UX31E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=db8fc294-e837-4964-a660-b0ee544109c5 ro quiet splash pcie_aspm=force drm.vblankoffdelay=1 i915.i915_enable_rc6=1 i915.semaphores=1 i915.powersave=1 "acpi_os_name=Microsoft Windows XP" vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.2 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: Upgraded to trusty on 2014-04-28 (43 days ago) dmi.bios.date: 08/14/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX31E.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX31E 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.:bvrUX31E.214:bd08/14/2012:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: UX31E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug package-from-proposed staging 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/1328674 Title: Asus UX31E turns off doesn't hibernate on empty battery Status in “linux” package in Ubuntu: New Bug description: On low battery, my ASus UX31E Zenbook simply turns off power even though power settings say to hibernate when battery is critically low. Hibernating works otherwise. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.54 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zach 1862 F pulseaudio CurrentDesktop: Unity Date: Tue Jun 10 22:10:27 2014 HibernationDevice: RESUME=UUID=6ff901b8-a6b6-4771-a1a4-e25f5370816b InstallationDate: Installed on 2012-05-01 (770 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) MachineType: ASUSTeK Computer Inc. UX31E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=db8fc294-e837-4964-a660-b0ee544109c5 ro quiet splash pcie_aspm=force drm.vblankoffdelay=1 i915.i915_enable_rc6=1 i915.semaphores=1 i915.powersave=1 "acpi_os_name=Microsoft Windows XP" vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.2 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: Upgraded to trusty on 2014-04-28 (43 days ago) dmi.bios.date: 08/14/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX31E.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX31E 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.:bvrUX31E.214:bd08/14/2012:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: UX31E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328154] Re: Precise update to v3.2.60 stable release
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Precise) 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/1328154 Title: Precise update to v3.2.60 stable release Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Precise: Confirmed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from Linus' tree or in a minimally backported form of that patch. The v3.2.60 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.2.60 stable release: Linux 3.2.60 futex: Prevent attaching to kernel threads futex: Add another early deadlock detection check mm/memory-failure.c: fix memory leak by race between poison and unpoison hwpoison, hugetlb: lock_page/unlock_page does not match for handling a free hugepage dma: mv_xor: Flush descriptors before activating a channel nfsd4: warn on finding lockowner without stateid's nfsd4: remove lockowner when removing lock stateid can: peak_pci: prevent use after free at netdev removal can: peak_pci: Fix the way channels are linked together drm/radeon: handle non-VGA class pci devices with ATRM drm/radeon: also try GART for CPU accessed buffers perf: Prevent false warning in perf_swevent_add perf: Limit perf_event_attr::sample_period to 63 bits libceph: fix corruption when using page_count 0 page in rbd libceph: only call kernel_sendpage() via helper PCI: shpchp: Check bridge's secondary (not primary) bus speed x86-64, modify_ldt: Make support for 16-bit segments a runtime option i2c: s3c2410: resume race fix i2c: designware: Mask all interrupts during i2c controller enable x86, mm, hugetlb: Add missing TLB page invalidation for hugetlb_cow() V4L2: fix VIDIOC_CREATE_BUFS in 64- / 32-bit compatibility mode V4L2: ov7670: fix a wrong index, potentially Oopsing the kernel from user-space hwmon: (emc1403) Support full range of known chip revision numbers hwmon: (emc1403) fix inverted store_hyst() hrtimer: Set expiry time before switch_hrtimer_base() NFSD: Call ->set_acl with a NULL ACL structure if no entries trace: module: Maintain a valid user count sched: Use CPUPRI_NR_PRIORITIES instead of MAX_RT_PRIO in cpupri check mm/page-writeback.c: fix divide by zero in pos_ratio_polynom Negative (setpoint-dirty) in bdi_position_ratio() posix_acl: handle NULL ACL in posix_acl_equiv_mode NFSd: call rpc_destroy_wait_queue() from free_client() NFSd: Move default initialisers from create_client() to alloc_client() md: avoid possible spinning md thread at shutdown. Input: elantech - fix touchpad initialization on Gigabyte U2442 HID: add NO_INIT_REPORTS quirk for Synaptics Touch Pad V 103S HID: usbhid: quirk for Synaptics Quad HD touchscreen HID: usbhid: quirk for Synaptics HD touchscreen HID: usbhid: quirk for Synaptics Large Touchccreen USB: Nokia 5300 should be treated as unusual dev USB: Nokia 305 should be treated as unusual dev drivers/tty/hvc: don't free hvc_console_setup after init usb: storage: shuttle_usbat: fix discs being detected twice drm/nouveau/acpi: allow non-optimus setups to load vbios from acpi media-device: fix infoleak in ioctl media_enum_entities() rtl8192cu: Fix unbalanced irq enable in error path of rtl92cu_hw_init() rtlwifi: rtl8192cu: Fix too long disable of IRQs timer: Prevent overflow in apply_slack hrtimer: Prevent remote enqueue of leftmost timers hrtimer: Prevent all reprogramming if hang detected mpt2sas: Don't disable device twice at suspend. ftrace/module: Hardcode ftrace_module_init() call into load_module() KVM: async_pf: mm->mm_users can not pin apf->mm kvm: remove .done from struct kvm_async_pf kvm: free resources after canceling async_pf crypto: caam - add allocation failure handling in SPRINTFCAT macro Bluetooth: Add support for Lite-on [04ca:3007] Bluetooth: Fix redundant encryption request for reauthentication drm/vmwgfx: Make sure user-space can't DMA across buffer object boundaries v2 Input: synaptics - add min/max quirk for ThinkPad Edge E431 rt2x00: fix beaconing on USB net-gro: reset skb->truesize in napi_reuse_skb() skb: Add inline helper for getting the skb end offset from head ipv4: initialise the itag variable in __mkroute_input act_mirred: do not drop packets when fails to mirror it macvlan: Don't propagate IFF_ALLMULTI changes on down interfaces. ipv4: fib_semantics: increment
[Kernel-packages] [Bug 1328154] Re: Precise update to v3.2.60 stable release
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1328154 Title: Precise update to v3.2.60 stable release Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Precise: Confirmed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from Linus' tree or in a minimally backported form of that patch. The v3.2.60 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.2.60 stable release: Linux 3.2.60 futex: Prevent attaching to kernel threads futex: Add another early deadlock detection check mm/memory-failure.c: fix memory leak by race between poison and unpoison hwpoison, hugetlb: lock_page/unlock_page does not match for handling a free hugepage dma: mv_xor: Flush descriptors before activating a channel nfsd4: warn on finding lockowner without stateid's nfsd4: remove lockowner when removing lock stateid can: peak_pci: prevent use after free at netdev removal can: peak_pci: Fix the way channels are linked together drm/radeon: handle non-VGA class pci devices with ATRM drm/radeon: also try GART for CPU accessed buffers perf: Prevent false warning in perf_swevent_add perf: Limit perf_event_attr::sample_period to 63 bits libceph: fix corruption when using page_count 0 page in rbd libceph: only call kernel_sendpage() via helper PCI: shpchp: Check bridge's secondary (not primary) bus speed x86-64, modify_ldt: Make support for 16-bit segments a runtime option i2c: s3c2410: resume race fix i2c: designware: Mask all interrupts during i2c controller enable x86, mm, hugetlb: Add missing TLB page invalidation for hugetlb_cow() V4L2: fix VIDIOC_CREATE_BUFS in 64- / 32-bit compatibility mode V4L2: ov7670: fix a wrong index, potentially Oopsing the kernel from user-space hwmon: (emc1403) Support full range of known chip revision numbers hwmon: (emc1403) fix inverted store_hyst() hrtimer: Set expiry time before switch_hrtimer_base() NFSD: Call ->set_acl with a NULL ACL structure if no entries trace: module: Maintain a valid user count sched: Use CPUPRI_NR_PRIORITIES instead of MAX_RT_PRIO in cpupri check mm/page-writeback.c: fix divide by zero in pos_ratio_polynom Negative (setpoint-dirty) in bdi_position_ratio() posix_acl: handle NULL ACL in posix_acl_equiv_mode NFSd: call rpc_destroy_wait_queue() from free_client() NFSd: Move default initialisers from create_client() to alloc_client() md: avoid possible spinning md thread at shutdown. Input: elantech - fix touchpad initialization on Gigabyte U2442 HID: add NO_INIT_REPORTS quirk for Synaptics Touch Pad V 103S HID: usbhid: quirk for Synaptics Quad HD touchscreen HID: usbhid: quirk for Synaptics HD touchscreen HID: usbhid: quirk for Synaptics Large Touchccreen USB: Nokia 5300 should be treated as unusual dev USB: Nokia 305 should be treated as unusual dev drivers/tty/hvc: don't free hvc_console_setup after init usb: storage: shuttle_usbat: fix discs being detected twice drm/nouveau/acpi: allow non-optimus setups to load vbios from acpi media-device: fix infoleak in ioctl media_enum_entities() rtl8192cu: Fix unbalanced irq enable in error path of rtl92cu_hw_init() rtlwifi: rtl8192cu: Fix too long disable of IRQs timer: Prevent overflow in apply_slack hrtimer: Prevent remote enqueue of leftmost timers hrtimer: Prevent all reprogramming if hang detected mpt2sas: Don't disable device twice at suspend. ftrace/module: Hardcode ftrace_module_init() call into load_module() KVM: async_pf: mm->mm_users can not pin apf->mm kvm: remove .done from struct kvm_async_pf kvm: free resources after canceling async_pf crypto: caam - add allocation failure handling in SPRINTFCAT macro Bluetooth: Add support for Lite-on [04ca:3007] Bluetooth: Fix redundant encryption request for reauthentication drm/vmwgfx: Make sure user-space can't DMA across buffer object boundaries v2 Input: synaptics - add min/max quirk for ThinkPad Edge E431 rt2x00: fix beaconing on USB net-gro: reset skb->truesize in napi_reuse_skb() skb: Add inline helper for getting the skb end offset from head ipv4: initialise the itag variable in __mkroute_input act_mirred: do not drop packets when fails to mirror it macvlan: Don't propagate IFF_ALLMULTI changes on down interfaces. ipv4: fib_semantics: increment fib_info
