[Kernel-packages] [Bug 1440536] Re: Oops __d_lookup+0x88/0x194
I flashed 1.15.22 firmware and indeed it helped. I don't observe the oops anymore. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1440536 Title: Oops __d_lookup+0x88/0x194 Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Vivid: Triaged Bug description: This started happening on a Mustang board after upgrading to 3.19.0-9.9 and persists in 3.19.0-11. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-11-generic 3.19.0-11.11 ProcVersionSignature: Ubuntu 3.19.0-11.11-generic 3.19.3 Uname: Linux 3.19.0-11-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 31 1969 seq crw-rw 1 root audio 116, 33 Dec 31 1969 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.17-0ubuntu1 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Sun Apr 5 08:32:28 2015 HibernationDevice: RESUME=UUID=014663f6-5135-4075-bf04-d2f42c4fc90b IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,115200n8 ro earlyprintk=uart8250-32bit,0x1c02 RelatedPackageVersions: linux-restricted-modules-3.19.0-11-generic N/A linux-backports-modules-3.19.0-11-generic N/A linux-firmware 1.143 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux SystemImageInfo: current build number: 0 device name: ? channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1440536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1440536] Re: Oops __d_lookup+0x88/0x194
Ming Lei, yes, on Mustang. We're using U-Boot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1440536 Title: Oops __d_lookup+0x88/0x194 Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Vivid: Triaged Bug description: This started happening on a Mustang board after upgrading to 3.19.0-9.9 and persists in 3.19.0-11. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-11-generic 3.19.0-11.11 ProcVersionSignature: Ubuntu 3.19.0-11.11-generic 3.19.3 Uname: Linux 3.19.0-11-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 31 1969 seq crw-rw 1 root audio 116, 33 Dec 31 1969 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.17-0ubuntu1 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Sun Apr 5 08:32:28 2015 HibernationDevice: RESUME=UUID=014663f6-5135-4075-bf04-d2f42c4fc90b IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,115200n8 ro earlyprintk=uart8250-32bit,0x1c02 RelatedPackageVersions: linux-restricted-modules-3.19.0-11-generic N/A linux-backports-modules-3.19.0-11-generic N/A linux-firmware 1.143 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux SystemImageInfo: current build number: 0 device name: ? channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1440536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 784176] Re: CPU_FREQ support is broken for OMAP 3 and OMAP 4
** Changed in: linux-linaro-omap (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linaro-ubuntu Status: Confirmed => Fix Released ** Changed in: linux-linaro Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/784176 Title: CPU_FREQ support is broken for OMAP 3 and OMAP 4 Status in Linaro Ubuntu Engineering Builds: Fix Released Status in Linaro Linux: Fix Released Status in “linux-linaro-omap” package in Ubuntu: Fix Released Status in “linux-ti-omap4” package in Ubuntu: Fix Released Bug description: Current both Nicolas and Andy's kernel tree (2.6.38) is lacking proper support for CPU_FREQ. On OMAP 4 it tries to change the frequencies for the first CPU, and on OMAP 3 is basically freezes when calling cpufreq-info, besides not having a proper frequency scaling. The workaround now for the linux-linaro-omap kernel is to disable CPU_FREQ, so this bug is basically to track why it's currently disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/linaro-ubuntu/+bug/784176/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 971091] Re: Pandaboard ES freezes with the default CPU scaling governor ondemand
** Changed in: linaro-ubuntu Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/971091 Title: Pandaboard ES freezes with the default CPU scaling governor ondemand Status in Linaro Texas Instruments Landing Team: Fix Released Status in Linaro Ubuntu Engineering Builds: Fix Released Status in “linux-ti-omap4” package in Ubuntu: Fix Released Bug description: Pandaboard ES freezes sporadically with the CPU scaling governor default setting, which is "ondemand". It is a complete freeze, no syslog entry, no serial access, no network, no keyboard/mouse anymore. When pressing the reset button, it will not even reboot. The SD card interface seems to be hanging. Pulling and re-inserting the SD card before pressing the reset button, or a global power-cycle will re-boot the board properly. The error occurs during normal operation on desktop, but can also be procuded in an unattended way: 1. Create a RAM disk by adding this to fstab none /tmp tmpfs defaults,noatime,mode=1777,size=600M 0 0 2. Mount it and create a big file on the RAM disk: dd bs=1M count=210 if=/dev/urandom of=/tmp/a 3. Change to /tmp and start an endless loop: while true; do cp a b; date; sleep 3; done Note that the "sleep" is important to cause the governor to switch CPU speed up and down. Wait for 1 to 8 hrs and find the Pandaboard ES in frozen state. You can do the same with a bigger file and /tmp on the SD card. This will often produce the error faster (possibly due to CPU idling at flash write delays) but will stress your flash card. Setting the CPU scaling governor to "performance" completely solves the problem. I guess there might be a HW issue on the Pandaboard ES that kicks in with frequent CPU speed changes. Solution proposal: set the CPU scaling governor to "performance" as default until the issue is further analysed. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-1411-omap4 3.2.0-1411.14 ProcVersionSignature: Ubuntu 3.2.0-1411.14-omap4 3.2.9 Uname: Linux 3.2.0-1411-omap4 armv7l ApportVersion: 1.95-0ubuntu1 Architecture: armhf Date: Sun Apr 1 23:01:52 2012 ProcEnviron: TERM=xterm LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-ti-omap4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linaro-landing-team-ti/+bug/971091/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
