[Bug 1880388] Re: rpi3b+ becomes unresponsive after closing a program
This bug was fixed in the package linux-raspi - 5.4.0-1019.21 --- linux-raspi (5.4.0-1019.21) focal; urgency=medium * focal/linux-raspi: 5.4.0-1019.21 -proposed tracker (LP: #1894636) * rpi3b+ becomes unresponsive after closing a program (LP: #1880388) // Build preemptible raspi kernels (LP: #1890808) - [Config] raspi: Switch from PREEMPT_VOLUNTARY to PREEMPT [ Ubuntu: 5.4.0-48.52 ] * focal/linux: 5.4.0-48.52 -proposed tracker (LP: #1894654) * mm/slub kernel oops on focal kernel 5.4.0-45 (LP: #1895109) - SAUCE: Revert "mm/slub: fix a memory leak in sysfs_slab_add()" * Packaging resync (LP: #1786013) - update dkms package versions - update dkms package versions * Introduce the new NVIDIA 450-server and the 450 UDA series (LP: #1887674) - [packaging] add signed modules for nvidia 450 and 450-server * [UBUNTU 20.04] zPCI attach/detach issues with PF/VF linking support (LP: #1892849) - s390/pci: fix zpci_bus_link_virtfn() - s390/pci: re-introduce zpci_remove_device() - s390/pci: fix PF/VF linking on hot plug * [UBUNTU 20.04] kernel: s390/cpum_cf,perf: changeDFLT_CCERROR counter name (LP: #1891454) - s390/cpum_cf, perf: change DFLT_CCERROR counter name * [UBUNTU 20.04] zPCI: Enabling of a reserved PCI function regression introduced by multi-function support (LP: #1891437) - s390/pci: fix enabling a reserved PCI function * CVE-2020-12888 - vfio/type1: Support faulting PFNMAP vmas - vfio-pci: Fault mmaps to enable vma tracking - vfio-pci: Invalidate mmaps and block MMIO access on disabled memory * [Hyper-V] VSS and File Copy daemons intermittently fails to start (LP: #1891224) - [Packaging] Bind hv_vss_daemon startup to hv_vss device - [Packaging] bind hv_fcopy_daemon startup to hv_fcopy device * alsa/hdmi: support nvidia mst hdmi/dp audio (LP: #1867704) - ALSA: hda - Rename snd_hda_pin_sense to snd_hda_jack_pin_sense - ALSA: hda - Add DP-MST jack support - ALSA: hda - Add DP-MST support for non-acomp codecs - ALSA: hda - Add DP-MST support for NVIDIA codecs - ALSA: hda: hdmi - fix regression in connect list handling - ALSA: hda: hdmi - fix kernel oops caused by invalid PCM idx - ALSA: hda: hdmi - preserve non-MST PCM routing for Intel platforms - ALSA: hda: hdmi - Keep old slot assignment behavior for Intel platforms - ALSA: hda - Fix DP-MST support for NVIDIA codecs * Focal update: v5.4.60 upstream stable release (LP: #1892899) - smb3: warn on confusing error scenario with sec=krb5 - genirq/affinity: Make affinity setting if activated opt-in - genirq/PM: Always unlock IRQ descriptor in rearm_wake_irq() - PCI: hotplug: ACPI: Fix context refcounting in acpiphp_grab_context() - PCI: Add device even if driver attach failed - PCI: qcom: Define some PARF params needed for ipq8064 SoC - PCI: qcom: Add support for tx term offset for rev 2.1.0 - btrfs: allow use of global block reserve for balance item deletion - btrfs: free anon block device right after subvolume deletion - btrfs: don't allocate anonymous block device for user invisible roots - btrfs: ref-verify: fix memory leak in add_block_entry - btrfs: stop incremening log_batch for the log root tree when syncing log - btrfs: remove no longer needed use of log_writers for the log root tree - btrfs: don't traverse into the seed devices in show_devname - btrfs: open device without device_list_mutex - btrfs: move the chunk_mutex in btrfs_read_chunk_tree - btrfs: relocation: review the call sites which can be interrupted by signal - btrfs: add missing check for nocow and compression inode flags - btrfs: avoid possible signal interruption of btrfs_drop_snapshot() on relocation tree - btrfs: sysfs: use NOFS for device creation - btrfs: don't WARN if we abort a transaction with EROFS - btrfs: fix race between page release and a fast fsync - btrfs: fix messages after changing compression level by remount - btrfs: only search for left_info if there is no right_info in try_merge_free_space - btrfs: inode: fix NULL pointer dereference if inode doesn't need compression - btrfs: fix memory leaks after failure to lookup checksums during inode logging - btrfs: make sure SB_I_VERSION doesn't get unset by remount - btrfs: fix return value mixup in btrfs_get_extent - arm64: perf: Correct the event index in sysfs - dt-bindings: iio: io-channel-mux: Fix compatible string in example code - iio: dac: ad5592r: fix unbalanced mutex unlocks in ad5592r_read_raw() - xtensa: add missing exclusive access state management - xtensa: fix xtensa_pmu_setup prototype - cifs: Fix leak when handling lease break for cached root fid - powerpc/ptdump: Fix build failure in hashpagetable.c - powerpc: Allow 4224 bytes of stack expansion for the signal frame - powerpc: Fix circular
[Bug 1880388] Re: rpi3b+ becomes unresponsive after closing a program
This bug was fixed in the package linux-raspi-5.4 - 5.4.0-1019.21~18.04.1 --- linux-raspi-5.4 (5.4.0-1019.21~18.04.1) bionic; urgency=medium * bionic/linux-raspi-5.4: 5.4.0-1019.21~18.04.1 -proposed tracker (LP: #1894635) * rpi3b+ becomes unresponsive after closing a program (LP: #1880388) // Build preemptible raspi kernels (LP: #1890808) - [Config] raspi-bionic: Switch from PREEMPT_VOLUNTARY to PREEMPT [ Ubuntu: 5.4.0-1019.21 ] * focal/linux-raspi: 5.4.0-1019.21 -proposed tracker (LP: #1894636) * rpi3b+ becomes unresponsive after closing a program (LP: #1880388) // Build preemptible raspi kernels (LP: #1890808) - [Config] raspi: Switch from PREEMPT_VOLUNTARY to PREEMPT * focal/linux: 5.4.0-48.52 -proposed tracker (LP: #1894654) * mm/slub kernel oops on focal kernel 5.4.0-45 (LP: #1895109) - SAUCE: Revert "mm/slub: fix a memory leak in sysfs_slab_add()" * Packaging resync (LP: #1786013) - update dkms package versions - update dkms package versions * Introduce the new NVIDIA 450-server and the 450 UDA series (LP: #1887674) - [packaging] add signed modules for nvidia 450 and 450-server * [UBUNTU 20.04] zPCI attach/detach issues with PF/VF linking support (LP: #1892849) - s390/pci: fix zpci_bus_link_virtfn() - s390/pci: re-introduce zpci_remove_device() - s390/pci: fix PF/VF linking on hot plug * [UBUNTU 20.04] kernel: s390/cpum_cf,perf: changeDFLT_CCERROR counter name (LP: #1891454) - s390/cpum_cf, perf: change DFLT_CCERROR counter name * [UBUNTU 20.04] zPCI: Enabling of a reserved PCI function regression introduced by multi-function support (LP: #1891437) - s390/pci: fix enabling a reserved PCI function * CVE-2020-12888 - vfio/type1: Support faulting PFNMAP vmas - vfio-pci: Fault mmaps to enable vma tracking - vfio-pci: Invalidate mmaps and block MMIO access on disabled memory * [Hyper-V] VSS and File Copy daemons intermittently fails to start (LP: #1891224) - [Packaging] Bind hv_vss_daemon startup to hv_vss device - [Packaging] bind hv_fcopy_daemon startup to hv_fcopy device * alsa/hdmi: support nvidia mst hdmi/dp audio (LP: #1867704) - ALSA: hda - Rename snd_hda_pin_sense to snd_hda_jack_pin_sense - ALSA: hda - Add DP-MST jack support - ALSA: hda - Add DP-MST support for non-acomp codecs - ALSA: hda - Add DP-MST support for NVIDIA codecs - ALSA: hda: hdmi - fix regression in connect list handling - ALSA: hda: hdmi - fix kernel oops caused by invalid PCM idx - ALSA: hda: hdmi - preserve non-MST PCM routing for Intel platforms - ALSA: hda: hdmi - Keep old slot assignment behavior for Intel platforms - ALSA: hda - Fix DP-MST support for NVIDIA codecs * Focal update: v5.4.60 upstream stable release (LP: #1892899) - smb3: warn on confusing error scenario with sec=krb5 - genirq/affinity: Make affinity setting if activated opt-in - genirq/PM: Always unlock IRQ descriptor in rearm_wake_irq() - PCI: hotplug: ACPI: Fix context refcounting in acpiphp_grab_context() - PCI: Add device even if driver attach failed - PCI: qcom: Define some PARF params needed for ipq8064 SoC - PCI: qcom: Add support for tx term offset for rev 2.1.0 - btrfs: allow use of global block reserve for balance item deletion - btrfs: free anon block device right after subvolume deletion - btrfs: don't allocate anonymous block device for user invisible roots - btrfs: ref-verify: fix memory leak in add_block_entry - btrfs: stop incremening log_batch for the log root tree when syncing log - btrfs: remove no longer needed use of log_writers for the log root tree - btrfs: don't traverse into the seed devices in show_devname - btrfs: open device without device_list_mutex - btrfs: move the chunk_mutex in btrfs_read_chunk_tree - btrfs: relocation: review the call sites which can be interrupted by signal - btrfs: add missing check for nocow and compression inode flags - btrfs: avoid possible signal interruption of btrfs_drop_snapshot() on relocation tree - btrfs: sysfs: use NOFS for device creation - btrfs: don't WARN if we abort a transaction with EROFS - btrfs: fix race between page release and a fast fsync - btrfs: fix messages after changing compression level by remount - btrfs: only search for left_info if there is no right_info in try_merge_free_space - btrfs: inode: fix NULL pointer dereference if inode doesn't need compression - btrfs: fix memory leaks after failure to lookup checksums during inode logging - btrfs: make sure SB_I_VERSION doesn't get unset by remount - btrfs: fix return value mixup in btrfs_get_extent - arm64: perf: Correct the event index in sysfs - dt-bindings: iio: io-channel-mux: Fix compatible string in example code - iio: dac: ad5592r: fix unbalanced mutex unlocks in ad5592r_read_raw() - xtensa: add
[Bug 1880388] Re: rpi3b+ becomes unresponsive after closing a program
This bug was fixed in the package linux-raspi - 5.8.0-1002.5
---
linux-raspi (5.8.0-1002.5) groovy; urgency=medium
* groovy/linux-raspi: 5.8.0-1002.5 -proposed tracker (LP: #1894068)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
* Miscellaneous Ubuntu changes
- [Config] raspi: updateconfigs after rebase to Ubuntu-5.8.0-18.19
- [Packaging] raspi: Add bootstrap PPA for getabis
[ Ubuntu: 5.8.0-18.19 ]
* groovy/linux: 5.8.0-18.19 -proposed tracker (LP: #1893047)
* Packaging resync (LP: #1786013)
- update dkms package versions
* Groovy update: v5.8.4 upstream stable release (LP: #1893048)
- drm/vgem: Replace opencoded version of drm_gem_dumb_map_offset()
- drm/panel-simple: Fix inverted V/H SYNC for Frida FRD350H54004 panel
- drm/ast: Remove unused code paths for AST 1180
- drm/ast: Initialize DRAM type before posting GPU
- khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()
- ALSA: hda: avoid reset of sdo_limit
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Flex Book
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Book Ion
- can: j1939: transport: j1939_session_tx_dat(): fix use-after-free read in
j1939_tp_txtimer()
- can: j1939: socket: j1939_sk_bind(): make sure ml_priv is allocated
- spi: Prevent adding devices below an unregistering controller
- io_uring: find and cancel head link async work on files exit
- mm/vunmap: add cond_resched() in vunmap_pmd_range
- romfs: fix uninitialized memory leak in romfs_dev_read()
- kernel/relay.c: fix memleak on destroy relay channel
- uprobes: __replace_page() avoid BUG in munlock_vma_page()
- squashfs: avoid bio_alloc() failure with 1Mbyte blocks
- mm: include CMA pages in lowmem_reserve at boot
- mm, page_alloc: fix core hung in free_pcppages_bulk()
- ASoC: amd: renoir: restore two more registers during resume
- RDMA/hfi1: Correct an interlock issue for TID RDMA WRITE request
- opp: Enable resources again if they were disabled earlier
- opp: Put opp table in dev_pm_opp_set_rate() for empty tables
- opp: Put opp table in dev_pm_opp_set_rate() if _set_opp_bw() fails
- ext4: do not block RWF_NOWAIT dio write on unallocated space
- ext4: fix checking of directory entry validity for inline directories
- jbd2: add the missing unlock_buffer() in the error path of
jbd2_write_superblock()
- scsi: zfcp: Fix use-after-free in request timeout handlers
- selftests: kvm: Use a shorter encoding to clear RAX
- s390/pci: fix zpci_bus_link_virtfn()
- s390/pci: re-introduce zpci_remove_device()
- s390/pci: fix PF/VF linking on hot plug
- s390/pci: ignore stale configuration request event
- mm/memory.c: skip spurious TLB flush for retried page fault
- drm: amdgpu: Use the correct size when allocating memory
- drm/amdgpu/display: use GFP_ATOMIC in dcn20_validate_bandwidth_internal
- drm/amd/display: Fix incorrect backlight register offset for DCN
- drm/amd/display: Fix EDID parsing after resume from suspend
- drm/amd/display: Blank stream before destroying HDCP session
- drm/amd/display: Fix DFPstate hang due to view port changed
- drm/amd/display: fix pow() crashing when given base 0
- drm/i915/pmu: Prefer drm_WARN_ON over WARN_ON
- drm/i915: Provide the perf pmu.module
- scsi: ufs: Add DELAY_BEFORE_LPM quirk for Micron devices
- scsi: target: tcmu: Fix crash in tcmu_flush_dcache_range on ARM
- media: budget-core: Improve exception handling in budget_register()
- media: coda: jpeg: add NULL check after kmalloc
- f2fs: fix to check page dirty status before writeback
- rtc: goldfish: Enable interrupt in set_alarm() when necessary
- media: vpss: clean up resources in init
- f2fs: should avoid inode eviction in synchronous path
- Input: psmouse - add a newline when printing 'proto' by sysfs
- MIPS: Fix unable to reserve memory for Crash kernel
- m68knommu: fix overwriting of bits in ColdFire V3 cache control
- svcrdma: Fix another Receive buffer leak
- xfs: fix inode quota reservation checks
- drm/ttm: fix offset in VMAs with a pg_offs in ttm_bo_vm_access
- riscv: Fixup static_obj() fail
- jffs2: fix UAF problem
- ceph: fix use-after-free for fsc->mdsc
- swiotlb-xen: use vmalloc_to_page on vmalloc virt addresses
- cpufreq: intel_pstate: Fix cpuinfo_max_freq when MSR_TURBO_RATIO_LIMIT is 0
- scsi: libfc: Free skb in fc_disc_gpn_id_resp() for valid cases
- virtio_ring: Avoid loop when vq is broken in virtqueue_poll
- media: camss: fix memory leaks on error handling paths in probe
- tools/testing/selftests/cgroup/cgroup_util.c: cg_read_strcmp: fix null
pointer dereference
- xfs: Fix UBSAN null-ptr-deref in xfs_sysfs_init
- alpha: fix annotation of io{read,write}{16,32}be()
- fat: fix fat_ra_init() for data clusters == 0
-
[Bug 1880388] Re: rpi3b+ becomes unresponsive after closing a program
** Also affects: linux-raspi (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux-raspi (Ubuntu) Status: New => Invalid ** No longer affects: linux-raspi (Ubuntu Bionic) ** Also affects: linux-raspi-5.4 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-raspi-5.4 (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: linux-raspi (Ubuntu Bionic) ** No longer affects: linux-raspi-5.4 (Ubuntu Focal) ** Changed in: linux-raspi-5.4 (Ubuntu) Status: New => Invalid ** Changed in: linux-raspi-5.4 (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880388 Title: rpi3b+ becomes unresponsive after closing a program To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880388] Re: rpi3b+ becomes unresponsive after closing a program
Just reiterating what I mentioned in the Github issue, that the test kernel works great. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880388 Title: rpi3b+ becomes unresponsive after closing a program To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880388] Re: rpi3b+ becomes unresponsive after closing a program
** Changed in: linux-raspi (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880388 Title: rpi3b+ becomes unresponsive after closing a program To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880388] Re: rpi3b+ becomes unresponsive after closing a program
@juergh, sorry I didn't get an email notification for what ever reason. I have loaded this onto a board and will try tomorrow and let you know! Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880388 Title: rpi3b+ becomes unresponsive after closing a program To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880388] Re: rpi3b+ becomes unresponsive after closing a program
@RJ, I've built a test kernel, can you give that a try? $ sudo add-apt-repository ppa:juergh/lp1880388 $ sudo apt-get update $ sudo apt install linux-raspi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880388 Title: rpi3b+ becomes unresponsive after closing a program To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880388] Re: rpi3b+ becomes unresponsive after closing a program
** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880388/+attachment/5393323/+files/kern.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880388 Title: rpi3b+ becomes unresponsive after closing a program To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880388] Re: rpi3b+ becomes unresponsive after closing a program
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880388/+attachment/5393324/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880388 Title: rpi3b+ becomes unresponsive after closing a program To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880388] Re: rpi3b+ becomes unresponsive after closing a program
Just want to add that I also had no problems with Raspberry Pi OS 64b beta, and is what I am using at the moment. Thanks Juerg. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880388 Title: rpi3b+ becomes unresponsive after closing a program To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880388] Re: rpi3b+ becomes unresponsive after closing a program
I'm able to reproduce this on a Focal 5.4 kernel by sending data to a Pi via a USB/serial adapter. I'm not able to reproduce this with the Raspberry Pi OS running a 5.4 kernel. I recompiled the Raspi OS kernel using the Ubuntu config and *now* I can reproduce it. It seems it's a config option difference in the Ubuntu kernel that triggers this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880388 Title: rpi3b+ becomes unresponsive after closing a program To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880388] Re: rpi3b+ becomes unresponsive after closing a program
** Changed in: linux-raspi (Ubuntu Focal) 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/1880388 Title: rpi3b+ becomes unresponsive after closing a program To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880388] Re: rpi3b+ becomes unresponsive after closing a program
Sorry for the late reply. That kern.log doesn't help much since it doesn't contain any of the errors mentioned above. >From https://github.com/ROBOTIS-GIT/turtlebot3/issues/593 it seems that 18.04.3 works but 18.04.4 does not? Is that a true statement? ** Bug watch added: github.com/ROBOTIS-GIT/turtlebot3/issues #593 https://github.com/ROBOTIS-GIT/turtlebot3/issues/593 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880388 Title: rpi3b+ becomes unresponsive after closing a program To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880388] Re: rpi3b+ becomes unresponsive after closing a program
Sure. I have attached the most recent one. ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880388/+attachment/5381642/+files/kern.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880388 Title: rpi3b+ becomes unresponsive after closing a program To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880388] Re: rpi3b+ becomes unresponsive after closing a program
Can you attach kern.log? ** Also affects: linux-raspi (Ubuntu Focal) 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/1880388 Title: rpi3b+ becomes unresponsive after closing a program To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880388] Re: rpi3b+ becomes unresponsive after closing a program
Reportedly this was not an issue with 18.04.3, although I cannot say I have personally tried this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880388 Title: rpi3b+ becomes unresponsive after closing a program To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880388] Re: rpi3b+ becomes unresponsive after closing a program
** Summary changed: - rpi3b becomes unresponsive after closing a program + rpi3b+ becomes unresponsive after closing a program ** Description changed: - I am running ROS2 on this raspberry pi 3B that is running as the main + I am running ROS2 on this raspberry pi 3B+ that is running as the main computer on a turtlebot3. There is two USB devices connected to the RPi, one is to communicate with the LIDAR and the other is to communicate with the control board, a OpenCR board. After "bringing the robot up" I open a new shell in tmux, and run `ros2 topic echo battery_state` which starts outputting ROS2 messages to the terminal. Upon ctrl+c'ing out of this, the system become unresponsive. I repeated this while connected to the serial console and captured the error messages that are being output. Issue I rose on github: https://github.com/ROBOTIS-GIT/turtlebot3/issues/593 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-1011-raspi 5.4.0-1011.11 ProcVersionSignature: User Name 5.4.0-1011.11-raspi 5.4.34 Uname: Linux 5.4.0-1011-raspi aarch64 ApportVersion: 2.20.11-0ubuntu27 Architecture: arm64 CasperMD5CheckResult: skip Date: Sun May 24 10:31:26 2020 SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) Serial console output: MMC: mmc@7e202000: 0, mmcnr@7e30: 1 Loading Environment from FAT... *** Warning - bad CRC, using default environment In:serial Out: vidconsole Err: vidconsole Net: No ethernet found. starting USB... Bus usb@7e98: scanning bus usb@7e98 for devices... 6 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found ## Info: input data size = 6 = 0x6 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 2603 bytes read in 6 ms (422.9 KiB/s) ## Executing script at 0240 8378005 bytes read in 364 ms (21.9 MiB/s) Total of 1 halfword(s) were the same Decompressing kernel... Uncompressed size: 25905664 = 0x18B4A00 29426757 bytes read in 1262 ms (22.2 MiB/s) Booting Ubuntu (with booti) from mmc 0:... ## Flattened Device Tree blob at 0260 Booting using the fdt blob at 0x260 Using Device Tree in place at 0260, end 02609f2f Starting kernel ... [1.966598] spi-bcm2835 3f204000.spi: could not get clk: -517 ln: /tmp/mountroot-fail-hooks.d//scripts/init-premount/lvm2: No such file or directory ext4 Thu Jan 1 00:00:07 UTC 1970 date: invalid date ' Wed Apr 1 17:23:46 2020' -.mount dev-mqueue.mount sys-kernel-debug.mount sys-kernel-tracing.mount kmod-static-nodes.service systemd-modules-load.service systemd-remount-fs.service ufw.service sys-fs-fuse-connections.mount sys-kernel-config.mount systemd-sysctl.service systemd-random-seed.service systemd-sysusers.service keyboard-setup.service systemd-tmpfiles-setup-dev.service swapfile.swap lvm2-monitor.service systemd-udevd.service systemd-journald.service systemd-udev-trigger.service systemd-journal-flush.service [ 14.813759] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 15.128676] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 15.174878] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04 systemd-rfkill.service systemd-udev-settle.service netplan-wpa-wlan0.service multipathd.service [ 17.840942] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled systemd-fsckd.service snap-core18-1708.mount snap-core18-1753.mount snap-lxd-14808.mount snap-lxd-15066.mount snap-snapd-7267.mount systemd-fsck@dev-disk-by\x2dlabel-system\x2dboot.service boot-firmware.mount console-setup.service Mounting Arbitrary Executable File Formats File System... finalrd.service [ OK ] Finished Tell Plymouth To Write Out Runtime Data. [ OK ] Mounted Arbitrary Executable File Formats File System. proc-sys-fs-binfmt_misc.mount [ OK ] Finished Create Volatile Files and Directories. systemd-tmpfiles-setup.service Starting Network Time Synchronization... Starting Update UTMP about System Boot/Shutdown... [ OK ] Finished Enable support for…onal executable binary formats. binfmt-support.service [ OK ] Finished Update UTMP about System Boot/Shutdown. systemd-update-utmp.service [ OK ] Finished Load AppArmor profiles. apparmor.service Starting Load AppArmor prof… managed internally by snapd... [ OK ] Finished Load AppArmor prof…es managed internally by snapd. snapd.apparmor.service [ OK ] Started Network Time Synchronization. [ OK ] Reached target System Time Set. [ OK ] Reached target System Time
[Bug 1880388] Re: rpi3b becomes unresponsive after closing a program
** Description changed: - I am running ROS2 on this raspberry pi 3B. After "bringing the robot up" - I open a new shell in tmux, and run `ros2 topic echo battery_state` - which starts outputting ROS2 messages to the terminal. Upon ctrl+c'ing - out of this, the system become unresponsive. I connected to the serial - console and captured the error messages that are being output. + I am running ROS2 on this raspberry pi 3B that is running as the main + computer on a turtlebot3. There is two USB devices connected to the RPi, + one is to communicate with the LIDAR and the other is to communicate + with the control board, a OpenCR board. + + After "bringing the robot up" I open a new shell in tmux, and run `ros2 + topic echo battery_state` which starts outputting ROS2 messages to the + terminal. Upon ctrl+c'ing out of this, the system become unresponsive. I + repeated this while connected to the serial console and captured the + error messages that are being output. Issue I rose on github: https://github.com/ROBOTIS-GIT/turtlebot3/issues/593 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-1011-raspi 5.4.0-1011.11 ProcVersionSignature: User Name 5.4.0-1011.11-raspi 5.4.34 Uname: Linux 5.4.0-1011-raspi aarch64 ApportVersion: 2.20.11-0ubuntu27 Architecture: arm64 CasperMD5CheckResult: skip Date: Sun May 24 10:31:26 2020 SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) - Serial console output: MMC: mmc@7e202000: 0, mmcnr@7e30: 1 Loading Environment from FAT... *** Warning - bad CRC, using default environment In:serial Out: vidconsole Err: vidconsole Net: No ethernet found. starting USB... Bus usb@7e98: scanning bus usb@7e98 for devices... 6 USB Device(s) found -scanning usb for storage devices... 0 Storage Device(s) found + scanning usb for storage devices... 0 Storage Device(s) found ## Info: input data size = 6 = 0x6 - Hit any key to stop autoboot: 0 + Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 2603 bytes read in 6 ms (422.9 KiB/s) ## Executing script at 0240 8378005 bytes read in 364 ms (21.9 MiB/s) Total of 1 halfword(s) were the same Decompressing kernel... Uncompressed size: 25905664 = 0x18B4A00 29426757 bytes read in 1262 ms (22.2 MiB/s) Booting Ubuntu (with booti) from mmc 0:... ## Flattened Device Tree blob at 0260 -Booting using the fdt blob at 0x260 -Using Device Tree in place at 0260, end 02609f2f + Booting using the fdt blob at 0x260 + Using Device Tree in place at 0260, end 02609f2f Starting kernel ... [1.966598] spi-bcm2835 3f204000.spi: could not get clk: -517 ln: /tmp/mountroot-fail-hooks.d//scripts/init-premount/lvm2: No such file or directory ext4 Thu Jan 1 00:00:07 UTC 1970 date: invalid date ' Wed Apr 1 17:23:46 2020' -.mount dev-mqueue.mount sys-kernel-debug.mount sys-kernel-tracing.mount kmod-static-nodes.service systemd-modules-load.service systemd-remount-fs.service ufw.service sys-fs-fuse-connections.mount sys-kernel-config.mount systemd-sysctl.service systemd-random-seed.service systemd-sysusers.service keyboard-setup.service systemd-tmpfiles-setup-dev.service swapfile.swap lvm2-monitor.service systemd-udevd.service systemd-journald.service systemd-udev-trigger.service systemd-journal-flush.service [ 14.813759] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 15.128676] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 15.174878] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04 systemd-rfkill.service systemd-udev-settle.service netplan-wpa-wlan0.service multipathd.service [ 17.840942] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled systemd-fsckd.service snap-core18-1708.mount snap-core18-1753.mount snap-lxd-14808.mount snap-lxd-15066.mount snap-snapd-7267.mount systemd-fsck@dev-disk-by\x2dlabel-system\x2dboot.service boot-firmware.mount console-setup.service - Mounting Arbitrary Executable File Formats File System... + Mounting Arbitrary Executable File Formats File System... finalrd.service [ OK ] Finished Tell Plymouth To Write Out Runtime Data. [ OK ] Mounted Arbitrary Executable File Formats File System. proc-sys-fs-binfmt_misc.mount [ OK ] Finished Create Volatile Files and Directories. systemd-tmpfiles-setup.service - Starting Network Time Synchronization... - Starting Update UTMP about System Boot/Shutdown... + Starting Network Time Synchronization... + Starting Update UTMP about
