[Bug 1880607] Re: Raspberry Pi 4 extremely slow file i/o after upgrade to 20.04
Kernel 5.4.0-1012.12 fixes the issue. ** Changed in: linux-raspi (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880607 Title: Raspberry Pi 4 extremely slow file i/o after upgrade to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880607] Re: Raspberry Pi 4 extremely slow file i/o after upgrade to 20.04
A buddy is running a Pi 4 with the official 20.04 Pi image (freshly set up) and with the 1011 kernel WITHOUT ISSUES. His config looks like this: cmdline.txt: root=LABEL=writable rootfstype=ext4 rootwait console=serial0,115200 console=tty1 net.ifnames=0 dwc_otg.lpm_enable=0 elevator=deadline fixrtc config.txt: [pi4] kernel=uboot_rpi_4.bin max_framebuffers=2 [all] arm_64bit=1 device_tree_address=0x0300 enable_uart=1 dtparam=audio=on dtparam=i2c_arm=on dtparam=spi=on cmdline=cmdline.txt over_voltage=3 arm_freq=1900 gpu_freq=600 I don't have time to experiment at the moment, though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880607 Title: Raspberry Pi 4 extremely slow file i/o after upgrade to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880607] Re: Raspberry Pi 4 extremely slow file i/o after upgrade to 20.04
My cmdline.txt: root=LABEL=rpi4-root rootfstype=ext4 rootwait verbose nosplash console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 net.ifnames=0 dwc_otg.lpm_enable=0 dwc_otg.fiq_fix_enable=1 fsck.repair=yes My config.txt: [pi4] # Route interrupts to ARM cores using legacy interrupt controller (default: 0 = route via GIC-400) enable_gic=1 armstub=armstub8-gic.bin # Fix graphical glitches dtoverlay=vc4-fkms-v3d [all] # evade u-boot, just boot directly (vmlinuz has to be uncompressed!) kernel=vmlinuz initramfs initrd.img followkernel # boot in AArch64 (64-bit) mode arm_64bit=1 # GPU shared memory, default: 64 (too low might disable features) gpu_mem=32 # Energy Efficient Ethernet off dtparam=eee=off # Use red PWR LED for activity indicator dtparam=pwr_led_trigger=cpu # Use green ACT LED for MicroSD indicator dtparam=act_led_trigger=mmc0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880607 Title: Raspberry Pi 4 extremely slow file i/o after upgrade to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880607] Re: Raspberry Pi 4 extremely slow file i/o after upgrade to 20.04
Downgrading to 5.4.0-1008-raspi fixes the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880607 Title: Raspberry Pi 4 extremely slow file i/o after upgrade to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880607] Re: Raspberry Pi 4 extremely slow file i/o after upgrade to 20.04
** Attachment added: "ubuntu-bug linux-raspi (gzipped)" https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880607/+attachment/5376655/+files/apport.linux-raspi.2ccw0izb.apport.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880607 Title: Raspberry Pi 4 extremely slow file i/o after upgrade to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880607] [NEW] Raspberry Pi 4 extremely slow file i/o after upgrade to 20.04
Public bug reported: After upgrading my Raspberry Pi 4 from Eoan to Focal (arm64), it now runs awfully slow with dmesg showing loots of these warnings: [ 3821.602211] [ cut here ] [ 3821.603018] WARNING: CPU: 2 PID: 25391 at drivers/mmc/host/sdhci.c:1101 sdhci_prepare_data+0x3dc/0x7b0 [ 3821.603805] Modules linked in: md4 nls_utf8 cifs libdes libarc4 fscache btsdio bluetooth ecdh_generic ecc bcm2835_v4l2(CE) brcmfmac vc4 bcm2835_mmal_vchiq(CE) videobuf2_vmalloc drm_kms_helper brcmutil videobuf2_memops cfg80211 videobuf2_v4l2 snd_soc_core videobuf2_common videodev snd_compress ac97_bus mc snd_pcm_dmaengine snd_pcm snd_timer snd fb_sys_fops vc_sm_cma(CE) syscopyarea sysfillrect raspberrypi_hwmon sysimgblt rpivid_mem uio_pdrv_genirq uio crct10dif_ce sch_fq_codel drm ip_tables x_tables autofs4 phy_generic [ 3821.607749] CPU: 2 PID: 25391 Comm: kworker/2:1H Tainted: GWC E 5.4.0-1011-raspi #11-Ubuntu [ 3821.608526] Hardware name: Raspberry Pi 4 Model B Rev 1.1 (DT) [ 3821.609298] Workqueue: kblockd blk_mq_run_work_fn [ 3821.610059] pstate: a0400085 (NzCv daIf +PAN -UAO) [ 3821.610820] pc : sdhci_prepare_data+0x3dc/0x7b0 [ 3821.611579] lr : sdhci_prepare_data+0x2cc/0x7b0 [ 3821.612338] sp : 80001063b9b0 [ 3821.613105] x29: 80001063b9b0 x28: ecb7b800 [ 3821.613890] x27: 0002 x26: [ 3821.614670] x25: f63a7000 x24: f63a7580 [ 3821.615448] x23: 00418958 x22: ecbf01d8 [ 3821.616268] x21: f3599dc0 x20: ecbf0258 [ 3821.617128] x19: f63a7580 x18: [ 3821.617934] x17: x16: [ 3821.618777] x15: x14: df7a1aa12be812e6 [ 3821.619567] x13: 0038fe30 x12: 4b956d3506ed8169 [ 3821.620348] x11: 0038fd88 x10: d75619a60c149ecb [ 3821.621125] x9 : 0038fce8 x8 : 8ca0b852b1c7c8e1 [ 3821.621897] x7 : 0038fbb0 x6 : a00671009a44 [ 3821.622671] x5 : x4 : 0020 [ 3821.623445] x3 : 0001 x2 : [ 3821.624219] x1 : ecbea000 x0 : ffe4 [ 3821.624993] Call trace: [ 3821.625756] sdhci_prepare_data+0x3dc/0x7b0 [ 3821.626523] sdhci_send_command+0xe0/0x5f0 [ 3821.627289] sdhci_request+0x110/0x150 [ 3821.628054] __mmc_start_request+0x88/0x1a8 [ 3821.628819] mmc_start_request+0x98/0xc0 [ 3821.629585] mmc_blk_mq_issue_rq+0x30c/0x778 [ 3821.630351] mmc_mq_queue_rq+0x14c/0x320 [ 3821.631118] blk_mq_dispatch_rq_list+0xa4/0x5f8 [ 3821.631888] blk_mq_do_dispatch_sched+0x68/0x108 [ 3821.632659] blk_mq_sched_dispatch_requests+0x164/0x1c0 [ 3821.633431] __blk_mq_run_hw_queue+0xfc/0x158 [ 3821.634200] blk_mq_run_work_fn+0x28/0x38 [ 3821.634970] process_one_work+0x1d0/0x430 [ 3821.635737] worker_thread+0x54/0x4a0 [ 3821.636505] kthread+0xfc/0x128 [ 3821.637272] ret_from_fork+0x10/0x1c [ 3821.638039] ---[ end trace bbce8914f99b8e25 ]--- syslog and kern.log fill up with these messages to hundreds of megabytes in an hour. This is with kernel 5.4.0.1011.11 . The green "SD activity" LED is constantly lit. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880607 Title: Raspberry Pi 4 extremely slow file i/o after upgrade to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865642] [NEW] package dma 0.11-2 failed to install/upgrade: installed dma package post-installation script subprocess returned error exit status 128
Public bug reported: During upgrade on a Raspberry Pi 3 (armhf) from disco to eoan, the upgrade of dma failed. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: dma 0.11-2 ProcVersionSignature: Ubuntu 5.0.0-1025.26-raspi2 5.0.21 Uname: Linux 5.0.0-1025-raspi2 armv7l ApportVersion: 2.20.11-0ubuntu8.5 Architecture: armhf Date: Tue Mar 3 01:44:46 2020 DuplicateSignature: package:dma:0.11-2 Setting up dma (0.11-2) ... dpkg: error processing package dma (--configure): installed dma package post-installation script subprocess returned error exit status 128 ErrorMessage: installed dma package post-installation script subprocess returned error exit status 128 Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: dma Title: package dma 0.11-2 failed to install/upgrade: installed dma package post-installation script subprocess returned error exit status 128 UpgradeStatus: Upgraded to eoan on 2020-03-03 (0 days ago) modified.conffile..etc.dma.auth.conf: [modified] mtime.conffile..etc.dma.auth.conf: 2019-10-29T11:14:01.611576 ** Affects: dma (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package armhf eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865642 Title: package dma 0.11-2 failed to install/upgrade: installed dma package post-installation script subprocess returned error exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dma/+bug/1865642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855627] [NEW] projectM 2.1.0+dfsg-4build2 crashes with SIGABRT on first preset change
Public bug reported: Starting projectM is fine and it comes up with the default visualisation, menu works, etc.. But as soon as you try to change to ANY other preset, it crashes with either free(): double free detected in tcache 2 or double free or corruption (fasttop) It seems to be related to these ones: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924925 https://bugzilla.redhat.com/show_bug.cgi?id=1663047 https://bugzilla.redhat.com/show_bug.cgi?id=1631104 Also, 2.1.0 is a bit old now. ** Affects: projectm (Ubuntu) Importance: Undecided Status: New ** Affects: projectm (Debian) Importance: Unknown Status: Unknown ** Affects: fedora Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #924925 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924925 ** Also affects: projectm (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924925 Importance: Unknown Status: Unknown ** Bug watch added: Red Hat Bugzilla #1631104 https://bugzilla.redhat.com/show_bug.cgi?id=1631104 ** Also affects: fedora via https://bugzilla.redhat.com/show_bug.cgi?id=1631104 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855627 Title: projectM 2.1.0+dfsg-4build2 crashes with SIGABRT on first preset change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/projectm/+bug/1855627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843207] Re: Doesn't boot on Raspberry Pi 4
This was fixed in #1847163. ** Changed in: linux-raspi2 (Ubuntu Eoan) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843207 Title: Doesn't boot on Raspberry Pi 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1843207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847163] Re: [FFe] Firmware bump for Pi 4 boot support
THANK YOU!! I just made it boot (without u-boot ATM) with all 4GB RAM enabled. And my problem was my own stupidity. Several weeks ago, when researching why it wouldn't boot, I somewhere found the boot param "modprobe.blacklist=sdhci_iproc" which I added to my command.txt. Without that module, the microSD can't be read, of course. (IIRC, the website was about booting from SSD via USB since the USB port is faster than the MicroSD port on pre-4 models.) So after removing that part, the system started to come alive. Now when doing apt update from the Pi4 itself, this came up: Processing triggers for flash-kernel (3.98ubuntu3) ... Unsupported platform. dpkg: error processing package flash-kernel (--configure): installed flash-kernel package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: flash-kernel I had to add the proper entries for the RPi4 to /etc/flash-kernel/db and then that worked, too. It seems I can finally start to migrate my Pi 3 services to the newer (and faster) Pi 4. Awesome! Many thanks again for your help! Now looking forward to the u-boot with 4GB RAM support, then it's perfect. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847163 Title: [FFe] Firmware bump for Pi 4 boot support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1847163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847163] Re: [FFe] Firmware bump for Pi 4 boot support
> I'd *guess* that's a limitation due to u-boot, but I'll try and find > time to test the kernel alone to confirm that. Obviously it's > something we'll want to sort out fairly quickly but I suspect it'll > have to be post-release at this point. For me, the Raspberry never leaves the rainbow screen if I omit the total_mem=1024. So it doesn't seem to be a thing with u-boot (which I don't use). I've read reports of people that can boot their (custom) kernels with 3GB RAM but get lockups with 4GB ... so I'll experiment with that, too. But they might have been using a 32bit kernel. This guy built a custom system image (with custom kernel) based on bionic that seems to be able to access all 4GB: https://jamesachambers.com/raspberry-pi-4-ubuntu-server-desktop-18-04-3 -image-unofficial/ But since I want to use the official kernel, I never tested it. However, he has the kernel config and boot config on his GitHub (link is on that page). So maybe this helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847163 Title: [FFe] Firmware bump for Pi 4 boot support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1847163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847163] Re: [FFe] Firmware bump for Pi 4 boot support
> Which release of Ubuntu are we talking about here? This is a clone of my RPi3 system (disco, IIRC it started out as bionic) that was upgraded to eoan (on the Pi3). btw: I've upgraded(?) the EEPROM to the July version (https://static.raspberrypi.org/files/rpi-boot-eeprom- recovery-2019-07-15.zip). I don't think this changes anything, but wanted to mention it. Thanks for the suggestions. I'll experiment with my setup when I get home today and report back. I'm not sure at this moment if it didn't detect the SD card or if the device names somehow changed. Or if it's really just the armstub thingy. > Anyway, I don't *think* the Pi's bootloader is capable of dealing with > compressed kernel images in which case, when we do start compressing our > kernels, I'm afraid your boot sequence will suddenly break. Thanks for the headsup. I was planning to use u-boot again in the near future, anyways. The reason I stopped using it was that there were several changes of the DTB address about a year ago and there was a mismatch between the inofficial raspi2-pi3 PPA (0x200) and the default packages (0x020-something) and my config.txt (always had the wrong one). That broke things on my Raspberrys a few times so I switched to the u-boot-less config to not have to bother about DTB memory addresses anymore. Do you know if booting via u-boot makes the whole 4GB RAM accessible to the system or is there still a limit of 1GB? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847163 Title: [FFe] Firmware bump for Pi 4 boot support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1847163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847163] Re: [FFe] Firmware bump for Pi 4 boot support
I'm booting my Pis without u-boot with this in my config.txt: [pi4] enable_gic=1 armstub=armstub8-gic.bin total_mem=1024 [all] kernel=vmlinuz initramfs initrd.img followkernel arm_64bit=1 gpu_mem=32 dtparam=eee=off This exact setup works fine on my Pi 3B+ (and also my Pi 2B has this non-u-boot-setup - they both boot fine this way.) The Pi 4 only even tries to boot with that total_mem=1024 line in the config.txt. Without that line (i.e. with the full 4GB RAM) it stays at the rainbow screen. But this isn't the big issue. When booting, it's failing to detect the SD card and thus the root filesystem. This is with today's updates and your PPA included. cmdline.txt is: root=/dev/mmcblk0p2 rootfstype=ext4 rootflags=noload rootwait verbose nosplash net.ifnames=0 dwc_otg.lpm_enable=0 dwc_otg.fiq_fix_enable=1 fsck.repair=yes modprobe.blacklist=sdhci_iproc So what does u-boot do differently than the internal bootloader? Or what could be the issue in my setup? I'd like to keep going without u-boot if possible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847163 Title: [FFe] Firmware bump for Pi 4 boot support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1847163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843207] Re: Doesn't boot on Raspberry Pi 4
The DTB is also missing from the package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843207 Title: Doesn't boot on Raspberry Pi 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1843207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843207] [NEW] Doesn't boot on Raspberry Pi 4
Public bug reported: linux-raspi2 from Eoan (19.10) doesn't boot on Raspberry Pi 4 due to missing kernel modules for the new hardware components. It would be nice if these got included. Also it only boots the kernel when the Pi is configured for 1GB RAM or less. (Then gets stuck on missing root FS because the microSD isn't detected.) ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843207 Title: Doesn't boot on Raspberry Pi 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1843207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832834] Re: Irregular system freezes after updating to 1.1.1b-1ubuntu2.2
With 1.1.1b-1ubuntu2.3 it's a bit different. The system doesn't seem to freeze anymore, but network traffic stops working. Happend about 1-2 hours after a fresh reboot (after applying updates). It still answered to PINGs, but no other network traffic. Neither SSH, nor HTTP/HTTPS or XMPP. After downgrading to 1.1.1b-1ubuntu2.1 it's now running for 3 hours without problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832834 Title: Irregular system freezes after updating to 1.1.1b-1ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832834] [NEW] Irregular system freezes after updating to 1.1.1b-1ubuntu2.2
Public bug reported: Yesterday, I've updated openssl on my Raspberry Pi 3B+ running disco arm64 from 1.1.1b-1ubuntu2.1 to 1.1.1b-1ubuntu2.2 . That was at 10:41 CEST. About 12:36 the system froze. I was able to reset the system at around 17:17. It froze again at around 17:55. Reset it again 19:09, froze again 00:15. Freeze = solid green "busy" light and doesn't answer to anything. Since it's a headless system, I only have the logfiles but they don't show anything obvious. At 01:06, I've downgraded back to 1.1.1b-1ubuntu2.1 and didn't have ANY freeze at all since then (13:13 now here). The system is running ejabberd, SyncThing and a few more programs, that make heavy use of OpenSSL. ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Description changed: Yesterday, I've updated openssl on my Raspberry Pi 3B+ running disco arm64 from 1.1.1b-1ubuntu2.1 to 1.1.1b-1ubuntu2.2 . That was at 10:41 CEST. About 12:36 the system froze. I was able to reset the system at around 17:17. It froze again at around 17:55. Reset it again 19:09, froze again 00:15. Freeze = solid green "busy" light and doesn't answer to anything. Since it's a headless system, I only have the logfiles but they don't show anything obvious. At 01:06, I've downgraded back to 1.1.1b-1ubuntu2.1 and didn't have ANY - freeze at all since then. + freeze at all since then (13:13 now here). The system is running ejabberd, SyncThing and a few more programs, that make heavy use of OpenSSL. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832834 Title: Irregular system freezes after updating to 1.1.1b-1ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826403] Re: Ethernet won't connect when cable is plugged in at boot
I have this, too, on a Raspberry Pi 3 with arm64 Ubuntu. However, I've also upgraded my Raspberry Pi 2 with armhf and there, NetworkManager still autoconnects just fine after boot. The configuration looks identical on both machines. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826403 Title: Ethernet won't connect when cable is plugged in at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1826403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811984] Re: flash-kernel 3.90ubuntu3.18.10.1 fails with mkimage: not found if no uboot is used
The thing is: In the previous version, flash-kernel ignored if mkimage was missing and just continued normally without throwing any error or even showing any warning. Which is the behaviour I'd prefer. The new version aborts and throws an error although there's no need to run mkimage on my system (a Raspberry Pi with somewhat recent firmware can boot the Linux kernel directly without the need for uboot). In my eyes this is a newly introduced bug. Especially if flash-kernel doesn't run properly with a "recommended" package missing. The image I'm using is the Ubuntu arm64 one - but I got rid of u-boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811984 Title: flash-kernel 3.90ubuntu3.18.10.1 fails with mkimage: not found if no uboot is used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1811984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811984] [NEW] flash-kernel 3.90ubuntu3.18.10.1 fails with mkimage: not found if no uboot is used
Public bug reported: After updating flash-kernel from 3.90ubuntu3 to 3.90ubuntu3.18.10.1, dpkg aborted with this error: Processing triggers for flash-kernel (3.90ubuntu3.18.10.1) ... Using DTB: bcm2710-rpi-3-b-plus.dtb Installing /lib/firmware/4.18.0-1009-raspi2/device-tree/broadcom/bcm2710-rpi-3-b-plus.dtb into /boot/dtbs/4.18.0-1009-raspi2/bcm2710-rpi-3-b-plus.dtb Taking backup of bcm2710-rpi-3-b-plus.dtb. Installing new bcm2710-rpi-3-b-plus.dtb. flash-kernel: installing version 4.18.0-1009-raspi2 Taking backup of vmlinuz. Installing new vmlinuz. Taking backup of bcm2710-rpi-3-b-plus.dtb. Installing new bcm2710-rpi-3-b-plus.dtb. Taking backup of initrd.img. Installing new initrd.img. Generating boot script u-boot image... /usr/sbin/flash-kernel: 497: /usr/sbin/flash-kernel: mkimage: not found dpkg: error processing package flash-kernel (--configure): installed flash-kernel package post-installation script subprocess returned error exit status 127 Errors were encountered while processing: flash-kernel The missing mkimage tool is in the package u-boot-tools which is recommended, but no dependency. Since I don't use uboot, I don't have that installed. The previous version of flash-kernel didn't care about that and worked just fine (updated DTB, initrd and vmlinuz). ** Affects: flash-kernel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811984 Title: flash-kernel 3.90ubuntu3.18.10.1 fails with mkimage: not found if no uboot is used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1811984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804457] [NEW] ANSI codes for Save/Restore Cursor Position not working in 0.54.1
Public bug reported: The current version of vte2.91 is 0.54.1 which breaks SCOSC/SCORC ANSI codes for saving the cursor position and returning to it. (Aka. SCP and RCP) This is fixed in 0.54.2 as per https://gitlab.gnome.org/GNOME/vte/issues/48 . Please update package for cosmic. ** Affects: vte2.91 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804457 Title: ANSI codes for Save/Restore Cursor Position not working in 0.54.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1804457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794841] [NEW] flash-kernel still using u-boot for Raspberry Pi
Public bug reported: The Raspberry Pi firmware can boot a Linux kernel perfectly fine with these settings in config.txt: kernel=vmlinuz initramfs initrd.img followkernel (Note that the space between "initramfs" and "initrd.img" is intentional!) So there's no actual need to use u-boot anymore. Also, at the moment, there's bug #1791466 with u-boot on the Raspberry Pi 3. Removing the u-boot bootloader and boot scripts would clean things up a lot. Also removing that shouldn't have any effect on existing installations because the boot script doesn't change anyways. ** Affects: flash-kernel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794841 Title: flash-kernel still using u-boot for Raspberry Pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1794841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764491] Re: Missing RaspberryPi 3B+
Can we omit this u-boot dependency, please? The Raspberry firmware can boot Linux kernels perfectly fine all on its own without the need of u-boot. There's absolutely no need to add this additional layer of potential problems, e.g. bug #1791466 . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764491 Title: Missing RaspberryPi 3B+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1764491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652270] Re: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
This might be related to bug #1791466 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652270 Title: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791471] [NEW] Upgrading from 0.11-1 (artful) to 0.11-1build1 (bionic) fails with exit status 128
Public bug reported: When dist-upgrading from artful to bionic, the upgrade of dma failed with: Setting up dma (0.11-1build1) ... dpkg: error processing package dma (--configure): installed dma package post-installation script subprocess returned error exit status 128 Only after temporarily renaming my /etc/dma/dma.conf did the upgrade succeed. Renaming back my configuration made dma work fine again. ** Affects: dma (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #847659 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847659 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791471 Title: Upgrading from 0.11-1 (artful) to 0.11-1build1 (bionic) fails with exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dma/+bug/1791471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791471] Re: Upgrading from 0.11-1 (artful) to 0.11-1build1 (bionic) fails with exit status 128
This might be related to this one: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=847659 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791471 Title: Upgrading from 0.11-1 (artful) to 0.11-1build1 (bionic) fails with exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dma/+bug/1791471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791466] Re: RPi3: fdt_addr_r conflicts with scriptaddr from u-boot-rpi
** Also affects: u-boot (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791466 Title: RPi3: fdt_addr_r conflicts with scriptaddr from u-boot-rpi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1791466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791466] [NEW] RPi3: fdt_addr_r conflicts with scriptaddr from u-boot-rpi
Public bug reported: u-boot-rpi_2016.03+dfsg1-6ubuntu2 (armhf) loads the boot.scr to 0x0200 but the bootscr.rpi3 also expects the FDT to be at this address. Changing the bootscr.rpi3 (and /boot/firmware/config.txt) to have the FDT at 0x02008000 and running flash-kernel afterwards makes the Raspberry boot again. ** Affects: flash-kernel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791466 Title: RPi3: fdt_addr_r conflicts with scriptaddr from u-boot-rpi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1791466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754371] Re: package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Same here while upgrading my Raspberry Pi 2 (armhf) from 17.10 to 18.04. Upgrader finished with "Upgrade complete" but left hundreds of packages in their old versions. I had to fix that with aptitude and now it's actually finishing the upgrade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754371 Title: package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1754371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311316] Re: After locking screen there is no input field to type password for unlock
@Andrea: @include common-auth auth optional pam_gnome_keyring.so -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311316] Re: After locking screen there is no input field to type password for unlock
@Andrea: Yes, no "switch to greeter" for me anymore. But still I get the LightDM lock screen (with working password field) instead of GDM3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311316] Re: After locking screen there is no input field to type password for unlock
A few reboots later, I'm now able to unlock the notebook from the LightDM lockscreen. There's no "switch to greeter" anymore, but a real password entry field which works. However, I still don't know why I had the GDM3 lockscreen before. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697230] Re: atkbd serio0: Unknown key pressed (translated set 2, code 0x87 on isa0060/serio0).
I see this during bootup with a fresh install of artful on a HP Spectre x360 13-4104ng notebook. For me it's setkeycodes e057 and code 0xd7, though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697230 Title: atkbd serio0: Unknown key pressed (translated set 2, code 0x87 on isa0060/serio0). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727842] Re: Volume and Mute buttons on keyboard not doing anything in Unity after upgrade to 17.10
After a reboot, with nothing else changed, media keys are no worky again. So it's NOT the Commands plugin. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727842 Title: Volume and Mute buttons on keyboard not doing anything in Unity after upgrade to 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1727842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727842] Re: Volume and Mute buttons on keyboard not doing anything in Unity after upgrade to 17.10
After enabling it and disabling it again, the media keys work now for some reason. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727842 Title: Volume and Mute buttons on keyboard not doing anything in Unity after upgrade to 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1727842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727842] Re: Volume and Mute buttons on keyboard not doing anything in Unity after upgrade to 17.10
My Commands plugin was already disabled and the media keys still don't work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727842 Title: Volume and Mute buttons on keyboard not doing anything in Unity after upgrade to 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1727842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311316] Re: After locking screen there is no input field to type password for unlock
Just for the record: I had Ubuntu 17.10 (upgraded from 17.04 which was upgraded from 16.10) running on my HP Spectre x360 just fine with GDM3 and Unity and when the screensaver kicked in or I locked the screen, it turned to the GDM3 greeter. A few days ago, I cleared my SSD and installed 17.10 from scratch. But now, when I lock the screen, I see what looks like the LightDM greeter with a red "Authentication failed" message and "Switch to greeter..." where the password input should be. I then have to Ctrl+Alt+F1 to the GDM3 greeter and unlock from there. Why is that? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727842] Re: Volume and Mute buttons on keyboard not doing anything in Unity after upgrade to 17.10
Today I was able to get media keys working about every 3rd restart of unity-settings-daemon. I've saved 2 logs of each state. I suspect it has to do with the order the plugins are loaded. ** Attachment added: "mylogs.zip" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1727842/+attachment/5025782/+files/mylogs.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727842 Title: Volume and Mute buttons on keyboard not doing anything in Unity after upgrade to 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1727842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727842] Re: Volume and Mute buttons on keyboard not doing anything in Unity after upgrade to 17.10
Ah, I gave up after about 8 attempts without any luck - wanted to try some more today. Glad you did it first. :) After cleaning up different port numbers and IDs, the only obvious difference between your logs seems to be something about the color- plugin. I've attached the cleaned logs. ** Attachment added: "logfiles-cleaned.zip" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1727842/+attachment/5025695/+files/logfiles-cleaned.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727842 Title: Volume and Mute buttons on keyboard not doing anything in Unity after upgrade to 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1727842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727842] Re: Volume and Mute buttons on keyboard not doing anything in Unity after upgrade to 17.10
This is after waiting a few minutes at the GDM logon screen. I also tested the media keys in GDM and they worked. But they DON'T work in Unity. https://pastebin.ubuntu.com/26222796/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727842 Title: Volume and Mute buttons on keyboard not doing anything in Unity after upgrade to 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1727842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727842] Re: Volume and Mute buttons on keyboard not doing anything in Unity after upgrade to 17.10
I think I found a pattern: When I login immediately after GDM comes up, the hotkeys seem to work. When I wait a bit at the user selection and THEN login, the hotkeys DON'T work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727842 Title: Volume and Mute buttons on keyboard not doing anything in Unity after upgrade to 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1727842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727842] Re: Volume and Mute buttons on keyboard not doing anything in Unity after upgrade to 17.10
I don't know what happened, but yesterday, all hotkeys worked for some reason. After shutting down the PC over night and booting it up today with no changes made - they DON'T work again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727842 Title: Volume and Mute buttons on keyboard not doing anything in Unity after upgrade to 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1727842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725458] Re: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful
*** This bug is a duplicate of bug 1726930 *** https://bugs.launchpad.net/bugs/1726930 ** This bug has been marked a duplicate of bug 1726930 System fails to start (boot) on battery due to read-only root file-system -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725458 Title: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727842] [NEW] Volume and Mute buttons on keyboard not doing anything in Unity after upgrade to 17.10
Public bug reported:
After upgrade to 17.10, my volume up/down and mute buttons/keys don't
change anything.
They keys get recognised in keyboard configuration as "Audio lower
volume" and "Audio raise volume" and "Audio mute". But pressing them
doesn't do anything.
Inside applications, the other media keys ("Play/Pause", "rewind",
"forward") work fine.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: unity 7.5.0+17.10.20171010-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CompizPlugins:
[core,composite,opengl,compiztoolbox,decor,place,regex,move,session,gnomecompat,imgpng,resize,mousepoll,animation,unitymtgrabhandles,vpswitch,wall,grid,snap,expo,ezoom,fade,workarounds,scale,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7:ubuntu
Date: Thu Oct 26 21:40:09 2017
DistUpgraded: 2017-10-12 22:36:20,416 DEBUG Running PostInstallScript:
'./xorg_fix_proprietary.py'
DistroCodename: artful
DistroVariant: ubuntu
EcryptfsInUse: Yes
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] RV730 XT [Radeon HD 4670] [1002:9490]
(prog-if 00 [VGA controller])
Subsystem: Hightech Information System Ltd. RV730 XT [Radeon HD 4670]
[1787:2003]
MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7512
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic
root=UUID=2f7f02c3-629a-404f-bc90-4771dd3019cf ro verbose nosplash
SourcePackage: unity
UpgradeStatus: Upgraded to artful on 2017-10-12 (13 days ago)
dmi.bios.date: 09/24/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.7B14
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P45 Platinum (MS-7512)
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: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrV1.7B14:bd09/24/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7512:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnP45Platinum(MS-7512):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: MS-7512
dmi.product.version: 1.0
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Thu Oct 12 20:13:53 2017
xserver.configfile: default
xserver.errors:
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.1
xserver.video_driver: radeon
** Affects: unity (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug artful compiz-0.9 third-party-packages ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727842
Title:
Volume and Mute buttons on keyboard not doing anything in Unity after
upgrade to 17.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1727842/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577575] Re: NFS share does not mount on boot using fstab
This bug reappeared (with cifs/smb mounts in fstab) after upgrade to 17.10 "artful" for me. The fix in #5 worked just fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577575 Title: NFS share does not mount on boot using fstab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1577575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
Confirmed on a hp Spectre x360 13-4104ng. On battery power, the system DOESN'T boot up. With the charger connected, the system boots up just fine. See https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725458 for my apport logs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725458] Re: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful
Yes, this seems to be a duplicate of your bug. On battery power, the system DOESN'T boot up. With the charger connected, the system boots up just fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725458 Title: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725458] Re: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful
The change in the fstab seems to have worked only once. Today, it doesn't boot again (with the changed fstab). I've tried switching from UEFI to Legacy mode without luck, too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725458 Title: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725458] Re: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful
I changed my fstab from UUID=a936dbe9-5ab5-4272-aaae-d22030824373 / ext4 errors=remount-ro 0 1 to UUID=a936dbe9-5ab5-4272-aaae-d22030824373 / ext4 rw,errors=remount-ro 0 1 and it now boots fine again. I don't know why that is necessary now and why the update didn't notify me or made the change automatically. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725458 Title: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725458] [NEW] System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful
Public bug reported: After not touching my notebook since 30th September (where I did the dist-upgrade to artful and installed all available updates), I did all available updates today (20th October) and the system didn't boot after that. The last message I see is "Reached target Bluetooth". Before that, there are several failed services. GDM doesn't come up. After logging in on tty2, I saw that the root partition was mounted read-only. Inspecting the messages of e.g. systemd-resolved shows that it didn't start because of the read-only filesystem. After remounting it fw, I was able to restart the daemons and could also start GDM and login fine. My fstab shows: UUID=a936dbe9-5ab5-4272-aaae-d22030824373 / ext4errors =remount-ro 0 1 The UUID is correct as "mount / -o remount,rw" works fine. Booting with the previous kernel doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Fri Oct 20 21:46:36 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-26 (451 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:2073 Elan Microelectronics Corp. Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2c7d Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=a936dbe9-5ab5-4272-aaae-d22030824373 ro text SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-09-30 (20 days ago) dmi.bios.date: 09/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 81A1 dmi.board.vendor: HP dmi.board.version: 33.76 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd09/28/2016:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn81A1:rvr33.76:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible dmi.sys.vendor: HP ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725458 Title: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667160] Re: Kernel panic when using rtlwifi since 4.8.0-1025 on RasPi 2
For the record: I upgraded to zesty and with kernel 4.10.0-1004 everything works fine, too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667160 Title: Kernel panic when using rtlwifi since 4.8.0-1025 on RasPi 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667160] Re: Kernel panic when using rtlwifi since 4.8.0-1025 on RasPi 2
4.8.0-1035 seems to fix the problem. (Didn't check -1034.) Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667160 Title: Kernel panic when using rtlwifi since 4.8.0-1025 on RasPi 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed
The error message is: Preparing to unpack .../bash_4.4-2ubuntu1_amd64.deb ... Unpacking bash (4.4-2ubuntu1) over (4.3-15ubuntu1) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu15) ... update-initramfs: deferring update (trigger activated) dpkg: dependency problems prevent processing triggers for cracklib-runtime: cracklib-runtime depends on file; however: Package file is not configured yet. dpkg: error processing package cracklib-runtime (--configure): dependency problems - leaving triggers unprocessed And then that error about the dependency problem with cracklib-runtime repeats over and over until it aborts because of "too many errors". ** Attachment added: "apt-term.log" https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1681231/+attachment/4862209/+files/apt-term.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1681231 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1681231/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667160] Re: Kernel panic when using rtlwifi since 4.8.0-1025 on RasPi 2
Did anybody check the current kernel from zesty? I'm thinking about upgrading, but don't want to render the thing unbootable because there's no working kernel left. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667160 Title: Kernel panic when using rtlwifi since 4.8.0-1025 on RasPi 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1681231] [NEW] package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: This seems to be the same problem as described in bug #1636262, only this time it happened during upgrade from 16.10 to 17.04. The setup process (do-release-upgrade -d) aborted and I had to finish it manually. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: cracklib-runtime 2.9.2-3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 Date: Sun Apr 9 17:09:37 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-07-26 (257 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.4 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago) ** Affects: cracklib2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1681231 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1681231/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667160] Re: Kernel panic when using rtlwifi since 4.8.0-1025 on RasPi 2
Problem still exists with 4.8.0-1033.37. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667160 Title: Kernel panic when using rtlwifi since 4.8.0-1025 on RasPi 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop
Possible duplicate: bug #1667160 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1666421 Title: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667160] Re: Kernel panic since 4.8.0-1025 on RasPi 2
A workaround seems to be using https://github.com/dz0ny/rt8192cu instead of the rtlwifi driver. Bug also reported for the Orange Pi here: https://github.com/orangepi- xunlong/orangepi_h3_linux/pull/1 Also related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666421 ** Summary changed: - Kernel panic since 4.8.0-1025 on RasPi 2 + Kernel panic when using rtlwifi since 4.8.0-1025 on RasPi 2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667160 Title: Kernel panic when using rtlwifi since 4.8.0-1025 on RasPi 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667160] Re: Kernel panic with 4.8.0-1025 through -1031 on RasPi 2
Same problem with 4.8.0-1032. ** Summary changed: - Kernel panic with 4.8.0-1025 through -1031 on RasPi 2 + Kernel panic since 4.8.0-1025 on RasPi 2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667160 Title: Kernel panic since 4.8.0-1025 on RasPi 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667160] Re: Kernel panic with 4.8.0-1025, -1026 and -1028 on RasPi 2
Still no worky with kernel 4.8.0-1031. ** Attachment added: "Kernel panic with kernel 4.8.0-1031" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+attachment/4849159/+files/vlcsnap-2017-03-28-21h33m24s240.png ** Summary changed: - Kernel panic with 4.8.0-1025, -1026 and -1028 on RasPi 2 + Kernel panic with 4.8.0-1025 through -1031 on RasPi 2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667160 Title: Kernel panic with 4.8.0-1025 through -1031 on RasPi 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667160] Re: Kernel panic with 4.8.0-1025, -1026 and -1028 on RasPi 2
I just got the update to kernel 4.8.0-1031.35 ... will test later today. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667160 Title: Kernel panic with 4.8.0-1025, -1026 and -1028 on RasPi 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667160] Re: Kernel panic with 4.8.0-1025, -1026 and -1028 on RasPi 2
** Also affects: linux-meta-raspi2 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-meta-raspi2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667160 Title: Kernel panic with 4.8.0-1025, -1026 and -1028 on RasPi 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667160] Re: Kernel panic with 4.8.0-1025, -1026 and -1028 on RasPi 2
** Summary changed: - Kernel panic with 4.8.0-1025 and -1026 on RasPi 2 + Kernel panic with 4.8.0-1025, -1026 and -1028 on RasPi 2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667160 Title: Kernel panic with 4.8.0-1025, -1026 and -1028 on RasPi 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667160] Re: Kernel panic with 4.8.0-1025 and -1026 on RasPi 2
** Attachment added: "vlcsnap-2017-03-09-23h36m39s986.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+attachment/4834940/+files/vlcsnap-2017-03-09-23h36m39s986.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667160 Title: Kernel panic with 4.8.0-1025 and -1026 on RasPi 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667160] Re: Kernel panic with 4.8.0-1025 and -1026 on RasPi 2
Tested today with the -1028 kernel. The problem IS STILL THERE. This time, I made a video of the problem: https://www.youtube.com/watch?v=H_PxSXsgVQU The error part starts with: Unable to handle kernel NULL pointer dereference at virtual address 0034 pgd = afcfc000 [0034] *pgd= Internal error: Oops: 5 [#1] SMP ARM Modules linked in: ccm appletalk ipx p8023 p8022 psnap llc CPU: 1 PID: 1719 Comm: dhclient Not tainted 4.8.0-1028-raspi2 #31-Ubuntu Hardware name: BCM2709 task: b9796740 task.stack: afc6e000 PC is at rtl_lps_leave+0x38/0x6c [rtlwifi] LR is at setup_arp_tx+0x60/0x74 [rtlwifi] ... Looks like it's a problem with the Realtek WiFi module? Or dhclient? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667160 Title: Kernel panic with 4.8.0-1025 and -1026 on RasPi 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667160] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1667160/+attachment/4825134/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667160 Title: Kernel panic with 4.8.0-1025 and -1026 on RasPi 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667160] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1667160/+attachment/4825135/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667160 Title: Kernel panic with 4.8.0-1025 and -1026 on RasPi 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667160] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1667160/+attachment/4825139/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667160 Title: Kernel panic with 4.8.0-1025 and -1026 on RasPi 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667160] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1667160/+attachment/4825140/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667160 Title: Kernel panic with 4.8.0-1025 and -1026 on RasPi 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667160] Re: Kernel panic with 4.8.0-1025 and -1026 on RasPi 2
NOTE: The apport I sent was created with the WORKING 1024 kernel. IT IS NOT from the here mentioned -1025 or -1026 kernel as there I can barely login until the kernel panics. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667160 Title: Kernel panic with 4.8.0-1025 and -1026 on RasPi 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667160] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1667160/+attachment/4825137/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667160 Title: Kernel panic with 4.8.0-1025 and -1026 on RasPi 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667160] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1667160/+attachment/4825136/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667160 Title: Kernel panic with 4.8.0-1025 and -1026 on RasPi 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667160] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1667160/+attachment/4825138/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667160 Title: Kernel panic with 4.8.0-1025 and -1026 on RasPi 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667160] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1667160/+attachment/4825141/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667160 Title: Kernel panic with 4.8.0-1025 and -1026 on RasPi 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667160] Re: Kernel panic with 4.8.0-1025 and -1026 on RasPi 2
apport information ** Tags added: apport-collected yakkety ** Description changed: I have a Raspberry Pi 2 running Ubuntu 16.10 without problems. I use wicd to let it connect to my WiFi with a RTL8188CUS USB dongle. And there's a RTL2838 DVB-T USB stick attached to monitor airplane positions for Flightradar24. After updateing the kernel from 4.8.0-1024, which runs flawlessly, to -1025, there's a kernel panic happening 10-20 seconds after booting up to the login prompt. I thought the -1026 fixed that, but it's still no worky. The trace is scrolling so fast I can't read anything but the last page: [<808c76c8>] (sock_sendmsg) from... [<808c7778>] (sock_write_iter) from... [<802c39c8>] (new_sync_write) from... [<802c3a4c>] (__vfs_write) from... [<802c48d8>] (vfs_write) from... [<802c5ab4>] (SyS_write) from... Code: e5922004 e0033002 e353 0a0a (e5902034) ---[ end trace 0f53d17efe0c6ba ]--- Kernel panic - not syncing: Fatal exception in interrupt CPU2: stopping CPU: 2 PID: 21 Comm: migration/2 Tainted: G D 4.8.0-1026-raspi2 #29-Ubuntu Hardware name: BCM2709 [<801120ac>] (unwind_backtrace) from ... [<8010d2dc>] (show_stack) from ... [<8059c38c>] (handle_IPI) from ... [<80101564>] (bcm2836_arm_irqchip_handle_irq) from [<80a49f3c>] (__irq_svc+0x5c/0x7c) Exception stack(0xbb99de68 to 0xbb99deb0) de60: 0004 0001 bac05de0 0001 de80: bac05dcc a00e0013 bac05d6c bb99dedc bb99dee0 bb99deb8 dea0: 801d367c 801d35f4 600e0013 [<80a49f3c>] (__irq_svc) from ... [<801d35f4>] (multi_cpu_stop) from ... [<801d38ec>] (cpu_stopper_thread) from ... [<8014b71c>] (smpboot_thread_fn) from ... [<80147770>] (kthread) from [<80108e28>] (ret_from_fork+0x14/0x2c) And then this block repeats with CPU3 and CPU0. Going back to 4.8.0-1024 makes everything work again. Affected packages: linux-image-4.8.0-1025-raspi2:armhf (4.8.0-1025.28) linux-image-4.8.0-1026-raspi2:armhf (4.8.0-1026.29) + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Jul 25 2016 seq + crw-rw 1 root audio 116, 33 Jul 25 2016 timer + AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.8.0-1024-raspi2. + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.20.3-0ubuntu8.2 + Architecture: armhf + 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: N/A + DistroRelease: Ubuntu 16.10 + Lsusb: + Bus 001 Device 005: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T + Bus 001 Device 004: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS] + Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter + Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Package: linux (not installed) + PciMultimedia: + + ProcFB: 0 BCM2708 FB + ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2709.boardrev=0xa01041 bcm2709.serial=0xecd3f749 smsc95xx.macaddr=B8:27:EB:D3:F7:49 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3ea0 vc_mem.mem_size=0x3f00 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait + ProcVersionSignature: Ubuntu 4.8.0-1024.27-raspi2 4.8.16 + RelatedPackageVersions: + linux-restricted-modules-4.8.0-1024-raspi2 N/A + linux-backports-modules-4.8.0-1024-raspi2 N/A + linux-firmware 1.161.1 + RfKill: + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no + Tags: yakkety + Uname: Linux 4.8.0-1024-raspi2 armv7l + UnreportableReason: The report belongs to a package that is not installed. + UpgradeStatus: Upgraded to yakkety on 2016-10-24 (122 days ago) + UserGroups: adm audio cdrom dialout floppy fuse netdev plugdev sudo users video www-data + _MarkForUpload: False ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1667160/+attachment/4825133/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667160 Title: Kernel panic with 4.8.0-1025 and -1026 on RasPi 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667160] [NEW] Kernel panic with 4.8.0-1025 and -1026 on RasPi 2
Public bug reported: I have a Raspberry Pi 2 running Ubuntu 16.10 without problems. I use wicd to let it connect to my WiFi with a RTL8188CUS USB dongle. And there's a RTL2838 DVB-T USB stick attached to monitor airplane positions for Flightradar24. After updateing the kernel from 4.8.0-1024, which runs flawlessly, to -1025, there's a kernel panic happening 10-20 seconds after booting up to the login prompt. I thought the -1026 fixed that, but it's still no worky. The trace is scrolling so fast I can't read anything but the last page: [<808c76c8>] (sock_sendmsg) from... [<808c7778>] (sock_write_iter) from... [<802c39c8>] (new_sync_write) from... [<802c3a4c>] (__vfs_write) from... [<802c48d8>] (vfs_write) from... [<802c5ab4>] (SyS_write) from... Code: e5922004 e0033002 e353 0a0a (e5902034) ---[ end trace 0f53d17efe0c6ba ]--- Kernel panic - not syncing: Fatal exception in interrupt CPU2: stopping CPU: 2 PID: 21 Comm: migration/2 Tainted: G D 4.8.0-1026-raspi2 #29-Ubuntu Hardware name: BCM2709 [<801120ac>] (unwind_backtrace) from ... [<8010d2dc>] (show_stack) from ... [<8059c38c>] (handle_IPI) from ... [<80101564>] (bcm2836_arm_irqchip_handle_irq) from [<80a49f3c>] (__irq_svc+0x5c/0x7c) Exception stack(0xbb99de68 to 0xbb99deb0) de60: 0004 0001 bac05de0 0001 de80: bac05dcc a00e0013 bac05d6c bb99dedc bb99dee0 bb99deb8 dea0: 801d367c 801d35f4 600e0013 [<80a49f3c>] (__irq_svc) from ... [<801d35f4>] (multi_cpu_stop) from ... [<801d38ec>] (cpu_stopper_thread) from ... [<8014b71c>] (smpboot_thread_fn) from ... [<80147770>] (kthread) from [<80108e28>] (ret_from_fork+0x14/0x2c) And then this block repeats with CPU3 and CPU0. Going back to 4.8.0-1024 makes everything work again. Affected packages: linux-image-4.8.0-1025-raspi2:armhf (4.8.0-1025.28) linux-image-4.8.0-1026-raspi2:armhf (4.8.0-1026.29) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667160 Title: Kernel panic with 4.8.0-1025 and -1026 on RasPi 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667160] Re: Kernel panic with 4.8.0-1025 and -1026 on RasPi 2
** Attachment added: "Screenshot of kernel panic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+attachment/4824869/+files/IMG_20170223_0030047.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667160 Title: Kernel panic with 4.8.0-1025 and -1026 on RasPi 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652504] Re: Recent updates broke Ubuntu on Raspberry Pi 3
I just got access to that Raspberry Pi 3 again. I saw that the expected fdt address now changed to 0x02008000 in the boot script. In the config.txt, it was set as: # set extended DT area device_tree_address=0x100 device_tree_end=0x8000 So I changed it to: # set extended DT area device_tree_address=0x2008000 device_tree_end=0x200ff00 And voilà - it works. Even the MAC address is correct now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652504 Title: Recent updates broke Ubuntu on Raspberry Pi 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1652504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652504] Re: Recent updates broke Ubuntu on Raspberry Pi 3
I don't have access to the RasPi3 at the moment (due to the changing MAC screwing with DHCP and port forwardings). I'll see what I can do. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652504 Title: Recent updates broke Ubuntu on Raspberry Pi 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1652504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652504] Re: Recent updates broke Ubuntu on Raspberry Pi 3
Could the missing fdt at 0x0200 be the reason, the RasPi now has a different MAC address on each and every boot? Because I noticed this after I got the boot process working again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652504 Title: Recent updates broke Ubuntu on Raspberry Pi 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1652504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652504] Re: Recent updates broke Ubuntu on Raspberry Pi 3
Also the official flash-kernel_3.0~rc.4ubuntu64_armhf.deb sets the fdt address to 0x100 whereas 3.0~rc.4ubuntu64.1.1 from yakkety-updates sets it to 0x0200. So it seems to be a regression in that package. Downgrading to 3.0~rc.4ubuntu64 and running "sudo flash-kernel" works. (Don't know why it didn't work when I tried that a few hours ago, probably forgot to run the command to update the boot.scr.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652504 Title: Recent updates broke Ubuntu on Raspberry Pi 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1652504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652504] Re: Recent updates broke Ubuntu on Raspberry Pi 3
Upon further inspection: The flash-kernel from the rpi3 PPA https://launchpad.net/~ubuntu-raspi2/+archive/ubuntu/ppa-rpi3 is only published for Xenial and there, the boot script sets the fdt address to 0x100 instead of 0x200. And that works without explicitly loading the fdt. So it seems I had the "old" flash-kernel from before upgrading to Yakkety and that worked. The new version tries to load the fdt from 0x200 where it isn't located. ** Also affects: flash-kernel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652504 Title: Recent updates broke Ubuntu on Raspberry Pi 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1652504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652504] Re: Recent updates broke Ubuntu on Raspberry Pi 3
Downgrading the kernel or recently upgraded packages flash-kernel or
linux-firmware-raspi2 didn't work for me. But you can fix this
temporarily by editing /usr/share/flash-kernel/bootscript/bootscr.rpi3
and adding the line
fatload mmc 0:1 ${fdt_addr_r} bcm2710-rpi-3-b.dtb
after the line
setenv fdt_addr_r 0x0200
Then run:
update-initramfs -u -k all
To update the boot.scr in /boot/firmware/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652504
Title:
Recent updates broke Ubuntu on Raspberry Pi 3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652504/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652504] Re: Recent updates broke Ubuntu on Raspberry Pi 3
It seems the FDT isn't loaded properly. I can boot the system if I load
the FDT manually and do the remaining steps from the boot.scr manually:
fatload mmc 0:1 0x0200 bcm2710-rpi-3-b.dtb
fdt addr 0x0200
fatload mmc 0:1 0x0100 vmlinuz
fatload mmc 0:1 0x0210 initrd.img
setenv initrdsize $filesize
bootz 0x0100 0x0210:${initrdsize} 0x0200
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652504
Title:
Recent updates broke Ubuntu on Raspberry Pi 3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652504/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652504] Re: Recent updates broke Ubuntu on Raspberry Pi 3
The actual problem happens earlier in the process than depicted in the screenshot above: Found U-Boot script /boot.scr reading /boot.scr 412 bytes read in 13 ms (30.3 KiB/s) ## Executing script at 0200 libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr " command. Aborting! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652504 Title: Recent updates broke Ubuntu on Raspberry Pi 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652504] Re: Recent updates broke Ubuntu on Raspberry Pi 3
Same here. The update to 1021 breaks the boot and the only way to recover is to rename all *.bak files back so it boots the older kernel. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652504 Title: Recent updates broke Ubuntu on Raspberry Pi 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616108] [NEW] DragonFly Mail Agent (dma) puts tab in From-line, breaks mailutils' mail
Public bug reported: The version of dma coming with Xenial is 0.9-1 and puts a Tab character between sender name and stamp in the From line. This causes a "You have new mail." message on login, but running "mail" (from mailutils) gives "No mail for $USER.". Changing all those tabs to spaces makes "mail" work. This was fixed in dma 0.11, see https://github.com/corecode/dma/issues/38 . ** Affects: dma (Ubuntu) Importance: Undecided Status: New ** Affects: mailutils (Ubuntu) Importance: Undecided Status: New ** Also affects: mailutils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616108 Title: DragonFly Mail Agent (dma) puts tab in From-line, breaks mailutils' mail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dma/+bug/1616108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506166] Re: Bracketed paste should be per-terminal [PATCH]
I have this problem in Ubuntu 15.10 and Guake Terminal 0.8.4 (from the WebUpd8 PPA, as recommended on their homepage). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506166 Title: Bracketed paste should be per-terminal [PATCH] To manage notifications about this bug go to: https://bugs.launchpad.net/vte/+bug/1506166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 918657] Re: unity-greeter_0.2.0-0ubuntu2 breaks desktop-selector
I'm on Vivid Beta 1 now and still no gear icon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/918657 Title: unity-greeter_0.2.0-0ubuntu2 breaks desktop-selector To manage notifications about this bug go to: https://bugs.launchpad.net/unity-greeter/+bug/918657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1214779] [NEW] Broken dependencies: could not find a Qt installation of ''
Public bug reported: After installing the moc package (2.5.0~alpha4+svn20120224-1ubuntu1) incl. all dependencies, I get this when trying to run it: $ moc moc: could not find a Qt installation of '' ** Affects: moc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1214779 Title: Broken dependencies: could not find a Qt installation of '' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/moc/+bug/1214779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211631] Re: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)
Steve, turns out, there already was such a bug report: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1066484/comments/11 Regarding the CIFS mounts: Today, I changed the auto cifs mounts during startup to noauto,user mounts, which get mounted by my user using a script after login. At the end of the day, the delay upon shutdown was gone. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/211631 Title: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/211631/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1066484] Re: long delay at shutdown/reboot - network-manager doesn't close correctly
While trying to catch a samba related bug, Steve Langasek pointed me to this NM bug. The screenshot shows the nm-dispatcher.action: Caught signal 15, shutting down... message. Steve's comment (https://bugs.launchpad.net/ubuntu/+source/samba/+bug/211631/comments/191): Markus, your screenshot shows a network-manager error: nm-dispatcher.action: Caught signal 15, shutting down... This indicates that some part of NM is not being correctly guarded from /etc/init.d/sendsigs, resulting in abnormal termination that breaks the network connection before network filesystems are being unmounted. Network Manager has previously been fixed for such bugs, but it seems to have recurred. ** Attachment added: Shutdown messages https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1066484/+attachment/3689222/+files/IMG_20130527_192438.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066484 Title: long delay at shutdown/reboot - network-manager doesn't close correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1066484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211631] Re: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)
Steve, turns out, there already was such a bug report: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1066484/comments/11 Regarding the CIFS mounts: Today, I changed the auto cifs mounts during startup to noauto,user mounts, which get mounted by my user using a script after login. At the end of the day, the delay upon shutdown was gone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/211631 Title: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/211631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211631] Re: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)
Here's a screenshot of the last few lines visible before my notebook shuts down. It's 13.04 as of May 27th. ** Attachment added: Shutdown messages https://bugs.launchpad.net/ubuntu/+source/samba/+bug/211631/+attachment/3688214/+files/IMG_20130527_192438.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/211631 Title: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/211631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1183690] [NEW] dkms only using one core for compiling
Public bug reported: I've set my CONCURRENCY_LEVEL variable to 8 to use all CPU cores of the i7. This works fine when compiling programs from the command line. But whenever dkms needs to compile something, like e.g. the vboxdrv, it only uses one single core (can be seen with htop) and thus takes a lot longer. This is on Ubuntu 13.04 with dkms 2.2.0.3-1.1ubuntu2. I also noticed this on Quantal with older dkms versions. ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: compiling concurrency cores threads -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1183690 Title: dkms only using one core for compiling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1183690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211631] Re: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)
The problem is still there on a fresh Raring installation. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/211631 Title: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/211631/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 211631] Re: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)
The problem is still there on a fresh Raring installation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/211631 Title: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/211631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 966294] Re: gstreamer hangs when accessing webcam (on specific hardware)
Just for the record: Had this problem today with the current 12.10 64-bit installer on a Lenovo E530. The installer was booted via EFI from USB stick. Removing the ubi-webcam.py didn't work. But I noticed a dd process taking ~10% CPU although the installer showed that all files were already copied. A few minutes later this was still the case so I killed that process and voilà - the installer went on and finished successfully. My installation layout: /dev/sda (1TB HDD) /dev/sda1 - /home (999GB) /dev/sda2 - swap (1GB) /dev/sdb (16GB mSATA SSD) /dev/sdb1 - efi (256MB) /dev/sdb2 - / (15.7GB) Maybe it has something to do with it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/966294 Title: gstreamer hangs when accessing webcam (on specific hardware) To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/966294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 162452] Re: vbetool vbemode get does not work, unary operator expected
After booting my Acer Revo R3610 with linux-image:amd64 3.5.0.24.30, vbetool dpms off (and other commands) also produces the Real mode call failed error. It worked fine with kernel 3.5.0.21.32. Don't know about the versions in-between. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/162452 Title: vbetool vbemode get does not work, unary operator expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/162452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 750139] Re: Guake size is messed up
Bug still appears in 12.10 (guake 0.4.3-3). A workaround is to edit /usr/bin/guake and change line 821 to width = 97 (May vary depending on your screen width.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/750139 Title: Guake size is messed up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/guake/+bug/750139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
