[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
I only have the 3B+ board - the issue was encountered, and is still reproducible on that board. OS has always been Ubuntu. I'll try to reduce the repro steps/conditions when I have time; my setup is the v6 tunnel +v6 router + ip6tables + bridge reproduces the issue immediately, so hopefully determining what contributes to the issue and what doesn't should be too hard. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
@Chrostopher: if it's a driver problem, wouldn't your issue with WLAN be distinct from mine, where I'm seeing the wired Ethernet break? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
FWIW, I tried the dwc2 overlay again with kernel 5.4.0-1021-raspi - as before in #21 this changes nothing - network still dies during first major (>100MB) download, while other USB ports continue working. On the plus side, the Pi can now actually boot with an external NIC plugged in. I'm not sure if the issue I had (boot getting stuck with external USB Ethernet adapter) got fixed or a hardware change I made (Apple USB Ethernet adapter -> generic RTL8153-based adapter) is responsible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
@Matt I didn't find any special way to easily select between kernels on
raspberry - installing the linux-{headers,image}--raspi2 would
overwrite whatever was on the FAT partition, making it the kernel loaded
on next boot. To revert to previous kernel, its package would need to be
reinstalled (apt install --reinstall ).
I did run into a problem where a tested kernel wouldn't boot, so I'd
recommend making a backup of the FAT partition in advance so you can
recover it outside of the Raspberry's OS session.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861936
Title:
Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel
network load ((lan78xx): transmit queue 0 timed out)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890883] Re: [ICH9M] (e)SATA hotplug doesn't work
@Kai - if I change the policy after startup (the default value is med_power_with_dipm), I still have to issue a manual scan once (doesn't matter if a device is attached or not), but subsequent attach/detach changes are noticed as expected. I found that kernel-cmdline equivalent of this setting should be ahci.mobile_lpm_policy=0, but haven't found if/how to apply this change to a specific ahci host port. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890883 Title: [ICH9M] (e)SATA hotplug doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890883] Re: [ICH9M] (e)SATA hotplug doesn't work
Indeed - as reported in that bug, eSATA hotplug does work on Ubuntu 16.04 (just tried the live image of 16.04.6, kernel 4.15.0-45-generic), so this is actually a regression. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890883 Title: [ICH9M] (e)SATA hotplug doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890883] Re: [ICH9M] (e)SATA hotplug doesn't work
Possibly related bug #1879276 ** Tags added: esata hotplug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890883 Title: [ICH9M] (e)SATA hotplug doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890883] [NEW] [ICH9M] (e)SATA hotplug doesn't work
Public bug reported: Hardware is a laptop - DELL Latitude E6400, SATA controller Intel ICH9M with 4 ports, at least 2 of which should be hotplug-enabled - the optical drive bay which has an push-to-eject mechanism, and a combo eSATA+USB port on the side. Trying various eSATA and plain SATA devices on the port, and inserting the optical drive after booting up, neither is detected automatically and need a manual bus scan to be detected: # scan - - - > /sys/class/scsi_host/host?/scan Hotplug works without such manual intervention on this laptop in Windows. I've also seen Linux handle hotplug without this intervention with an eSATA ExpressCard (SiI3132 chipset) on another machine (can't use that in this one, it's only got a CardBus slot). I've also read recommendations related to BIOS settings marking the slot as "external/removable", but I haven't seen anything of the sort in this machine's BIOS setup. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zdenek 767 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 8 12:41:53 2020 InstallationDate: Installed on 2020-08-06 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Latitude E6400 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5962cfa3-cf85-4f62-9655-8bf792852323 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A34 dmi.board.name: 0W620R dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA34:bd06/04/2013:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0W620R:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E6400 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal ** Description changed: Hardware is a laptop - DELL Latitude E6400, SATA controller Intel ICH9M with 4 ports, at least 2 of which should be hotplug-enabled - the optical drive bay which has an push-to-eject mechanism, and a combo eSATA+USB port on the side. Trying various eSATA and plain SATA devices on the port, and inserting the optical drive after booting up, neither is detected automatically and need a manual bus scan to be detected: # scan - - - > /sys/class/scsi_host/host?/scan Hotplug works without such manual intervention on this laptop in Windows. I've also seen Linux handle hotplug without this intervention with an eSATA ExpressCard (SiI3132 chipset) on another machine (can't use that in this one, it's only got a CardBus slot). + I've also read recommendations related to BIOS settings marking the slot + as "external/removable", but I haven't seen anything of the sort in this + machine's BIOS setup. + ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: zdenek 767 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: zdenek 767 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 8 12:41:53 2020 InstallationDate: Installed on 2020-08-06 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Latitude E6400 PccardctlIdent: - Socket 0: -no product info available + Socket 0: + no product info available PccardctlStatus: - Socket 0: -no card + Socket 0: + no card ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5962cfa3-cf85-4f62-9655-8bf792852323 ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.4.0-42-generic N/A - linux-backports-modules-5.4.0-42-generic N/A - linux-firmware1.187.2 + linux-restricted-modules-5.4.0-42-generic N/A + linux-backports-modules-5.4.0-42-generic N/A + linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2013 dmi.bios.ve
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Thanks. I hope the installation worked - I only have Focal now, and the headers package in that folder was asking for a dependency from Eoan which I don't have. Still, I managed to boot the system, and unfortunately the behaviour is the same. Aug 1 12:04:56 rpi3 kernel: [ 117.985005] [ cut here ] Aug 1 12:04:56 rpi3 kernel: [ 117.985053] NETDEV WATCHDOG: eth0 (lan78xx): transmit queue 0 timed out Aug 1 12:04:56 rpi3 kernel: [ 117.985163] WARNING: CPU: 1 PID: 0 at /home/hwang4/work/mainline/build/eoan-rpi/ubuntu-eoan/net/sched/sch_generic.c:448 dev_watchdog+0x370/0x378 Aug 1 12:04:56 rpi3 kernel: [ 117.985168] Modules linked in: sit tunnel4 ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil cfg80211 input_leds bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) raspberrypi_hwmon vc_sm_cma(CE) raspberrypi_cpufreq v4l2_common videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel drm ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid sdhci_iproc spidev phy_generic crct10dif_ce fixed aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 Aug 1 12:04:56 rpi3 kernel: [ 117.985309] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G C E 5.3.0-1030-raspi2 #32+testpreempt Aug 1 12:04:56 rpi3 kernel: [ 117.985311] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT) Aug 1 12:04:56 rpi3 kernel: [ 117.985316] pstate: 8045 (Nzcv daif +PAN -UAO) Aug 1 12:04:56 rpi3 kernel: [ 117.985320] pc : dev_watchdog+0x370/0x378 Aug 1 12:04:56 rpi3 kernel: [ 117.985324] lr : dev_watchdog+0x370/0x378 Aug 1 12:04:56 rpi3 kernel: [ 117.985326] sp : 1000bd90 Aug 1 12:04:56 rpi3 kernel: [ 117.985329] x29: 1000bd90 x28: 567789c1abf0 Aug 1 12:04:56 rpi3 kernel: [ 117.985334] x27: eeb8788d4480 x26: Aug 1 12:04:56 rpi3 kernel: [ 117.985338] x25: 0140 x24: eeb86f5c8480 Aug 1 12:04:56 rpi3 kernel: [ 117.985342] x23: 56778a807000 x22: eeb8788d445c Aug 1 12:04:56 rpi3 kernel: [ 117.985346] x21: eeb8788d4000 x20: eeb8788d4480 Aug 1 12:04:56 rpi3 kernel: [ 117.985351] x19: x18: Aug 1 12:04:56 rpi3 kernel: [ 117.985355] x17: x16: Aug 1 12:04:56 rpi3 kernel: [ 117.985359] x15: 56778a809708 x14: 56778a9418e0 Aug 1 12:04:56 rpi3 kernel: [ 117.985363] x13: 56778a941533 x12: 56778a82e000 Aug 1 12:04:56 rpi3 kernel: [ 117.985367] x11: x10: 56778a94 Aug 1 12:04:56 rpi3 kernel: [ 117.985372] x9 : x8 : 56778a94b8ab Aug 1 12:04:56 rpi3 kernel: [ 117.985376] x7 : x6 : 0002 Aug 1 12:04:56 rpi3 kernel: [ 117.985379] x5 : x4 : 0002 Aug 1 12:04:56 rpi3 kernel: [ 117.985385] x3 : x2 : 0004 Aug 1 12:04:56 rpi3 kernel: [ 117.985389] x1 : 2668adad17146c00 x0 : Aug 1 12:04:56 rpi3 kernel: [ 117.985394] Call trace: Aug 1 12:04:56 rpi3 kernel: [ 117.985400] dev_watchdog+0x370/0x378 Aug 1 12:04:56 rpi3 kernel: [ 117.985407] call_timer_fn+0x38/0x1e8 Aug 1 12:04:56 rpi3 kernel: [ 117.985412] run_timer_softirq+0x518/0x550 Aug 1 12:04:56 rpi3 kernel: [ 117.985417] __do_softirq+0x178/0x428 Aug 1 12:04:56 rpi3 kernel: [ 117.985422] irq_exit+0xf4/0x100 Aug 1 12:04:56 rpi3 kernel: [ 117.985429] __handle_domain_irq+0x90/0xf8 Aug 1 12:04:56 rpi3 kernel: [ 117.985433] bcm2836_arm_irqchip_handle_irq+0x68/0xd0 Aug 1 12:04:56 rpi3 kernel: [ 117.985436] el1_irq+0x108/0x200 Aug 1 12:04:56 rpi3 kernel: [ 117.985443] arch_cpu_idle+0x30/0x228 Aug 1 12:04:56 rpi3 kernel: [ 117.985453] default_idle_call+0x28/0x4c Aug 1 12:04:56 rpi3 kernel: [ 117.985458] do_idle+0x1e0/0x2c8 Aug 1 12:04:56 rpi3 kernel: [ 117.985464] cpu_startup_entry+0x28/0x30 Aug 1 12:04:56 rpi3 kernel: [ 117.985473] secondary_start_kernel+0x184/0x250 Aug 1 12:04:56 rpi3 kernel: [ 117.985476] ---[ end trace 6bb7d08c2e67083a ]--- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
@Hui, is there a guide/checklist how to test the Pi OS kernel on Ubuntu? I trie replacing the contents of the FAT partition, and the kernel did boot, but that's still missing the modules, possibly something else..? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
** Attachment added: "kernel_5.4.0-1015.log" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+attachment/5397093/+files/kernel_5.4.0-1015.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
I got myself the Ruideng TC66 USB tester and played a bit with it - it appears that after the network dies on Raspberry, the system's stable power consumption ends up higher than when it's functional and idling. Some stray endless loop, perhaps? ** Attachment added: "RPi3B+ power consumption during bug" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+attachment/5397091/+files/Screenshot%202020-07-30%20at%2001.16.47.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
@hui.wang - yes, I have seen this a few times in Focal since upgrading about a month ago. I didn't look at the logs closely, but the message that appears repeatedly after the interface fails is "eth0: kevent 0 may have been dropped" I think, and bug #1647397 may be related/identical. User from that bug ascribes the cause to the use of bridge, and this is my case. @Matt, are you also running the interface in a bridge? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Still observed with 5.3.0-1023 on eoan. Will be switching to focal, seeing as it should now boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Minor update - tried to check what's going on with 5.4 kernel by listening on the UART - there's no output. Setting standard priority on the focal-proposed repo, and reinstalling the linux-raspi2 package (along with its dependencies) from focal-proposed makes no difference. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
For reference, recovered the installation with:
cd <1st partition, FAT>
for FILE in *.bak ;do mv -i ${FILE%%.bak} ${FILE%%.bak}.broken; mv -i ${FILE}
${FILE%%.bak}; done
So yeah, kernel 5.4.0.1004.4 is unbootable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861936
Title:
Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel
network load ((lan78xx): transmit queue 0 timed out)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
@juergh - I'm using origin/priority/pinning, so I installed that kernel with apt install linux-raspi2=5.4.0.1004.4 linux-image-raspi2=5.4.0.1004.4 linux-headers=5.4.0.1004.4 # (or something like that) Now my RPi is stuck at the color palette screen. As there is no grub2 AFAICT, what do I need to do to switch back to the older kernel? (I'm pretty sure the kernel was not uninstalled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
** Description changed: - Raspberry Pi 3 network dies shortly after a burst of SD card IO (writes) and network load. Happened a few times (every time) when I tried to download a gparted zip release (~350 MiB) directly to the SD card, and then finally when I tried to scp the finished download from a desktop onto RPi's card. - Didn't collect information when it happened, but kept a copy of kern.log. Here's the relevant part: + Desciption changed: + Raspberry Pi 3 network partially dies (transmission doesn't work, reception still does) shortly after a burst of network load over IPv6, when IPv6 connectivity is provided by a tunnel from tunnelbroker.net. The triggering load is typically an HTTP(S) download, and replication can be done without actually saving the file (wget -O /dev/null ...). Problem happens within downloading ~10 GB, usually withinthe first 1 GB of traffic) + Replication is 100% as long as _all_ of the following conditions are met + - 6in4 tunnel to HE.net set up with netplan + - ipv6 rules applied (netfilter-persistent) + - ipv6 forwarding enabled (edit /etc/sysctl.conf) + + + kern.log message that appears after a while: Feb 4 23:42:59 rpi3 kernel: [ 571.878359] [ cut here ] Feb 4 23:42:59 rpi3 kernel: [ 571.878420] NETDEV WATCHDOG: eth0 (lan78xx): transmit queue 0 timed out Feb 4 23:42:59 rpi3 kernel: [ 571.878550] WARNING: CPU: 3 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878557] Modules linked in: sit tunnel4 ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 Feb 4 23:42:59 rpi3 kernel: [ 571.878774] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu Feb 4 23:42:59 rpi3 kernel: [ 571.878781] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT) Feb 4 23:42:59 rpi3 kernel: [ 571.878789] pstate: 6045 (nZCv daif +PAN -UAO) Feb 4 23:42:59 rpi3 kernel: [ 571.878800] pc : dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878807] lr : dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878812] sp : 1001bd60 Feb 4 23:42:59 rpi3 kernel: [ 571.878817] x29: 1001bd60 x28: 0140 Feb 4 23:42:59 rpi3 kernel: [ 571.878827] x27: x26: Feb 4 23:42:59 rpi3 kernel: [ 571.878836] x25: 8ecbefa4e000 x24: 305e0f529018 Feb 4 23:42:59 rpi3 kernel: [ 571.878845] x23: x22: 0001 Feb 4 23:42:59 rpi3 kernel: [ 571.878853] x21: 8ecbefa4e480 x20: 305e0f807000 Feb 4 23:42:59 rpi3 kernel: [ 571.878862] x19: x18: Feb 4 23:42:59 rpi3 kernel: [ 571.878871] x17: 10fd8218 x16: 305e0e30efb8 Feb 4 23:42:59 rpi3 kernel: [ 571.878879] x15: 8ecbf922a290 x14: Feb 4 23:42:59 rpi3 kernel: [ 571.87] x13: x12: 305e0f944000 Feb 4 23:42:59 rpi3 kernel: [ 571.878897] x11: 305e0f82d000 x10: Feb 4 23:42:59 rpi3 kernel: [ 571.878905] x9 : 0004 x8 : 017f Feb 4 23:42:59 rpi3 kernel: [ 571.878913] x7 : x6 : 0001 Feb 4 23:42:59 rpi3 kernel: [ 571.878921] x5 : x4 : 0008 Feb 4 23:42:59 rpi3 kernel: [ 571.878929] x3 : 305e0ee15750 x2 : 0004 Feb 4 23:42:59 rpi3 kernel: [ 571.878937] x1 : 6abb42c67c954600 x0 : Feb 4 23:42:59 rpi3 kernel: [ 571.878946] Call trace: Feb 4 23:42:59 rpi3 kernel: [ 571.878955] dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878967] call_timer_fn+0x3c/0x178 Feb 4 23:42:59 rpi3 kernel: [ 571.878977] __run_timers.part.0+0x200/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878985] run_timer_softirq+0x40/0x78 Feb 4 23:42:59 rpi3 kernel: [ 571.878995] __do_softirq+0x168/0x384 Feb 4 23:42:59 rpi3 kernel: [ 571.879007] irq_exit+0xb0/0xe8 Feb 4 23:42:59 rpi3 kernel: [ 571.879020] __handle_domain_irq+0x70/0xc0 Feb 4 23:42:59 rpi3 kernel: [ 571.879028] bcm2836_arm_irqchip_handle_irq+0x74/0xe0 Feb 4 23:42:59 rpi3 kernel: [ 571.879037] el1_irq+0x
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
Well, I only managed to replicate it on Ubuntu, and it requires many conditions to be met: - 6in4 tunnel to HE.net - ipv6 rules applied - ipv6 forwarding enabled Removing/replacing any one of these made downloading (wget -O /dev/null) reliable for at least 3 repeats of a large (~1GB+) downloads. I recreated the setup on Raspbian, and so far haven't had the issue. ** Summary changed: - Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) + Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
Never mind the LAN7515 heatsink. The issue was avoided by some combination of other missing configuration (I have since managed to trigger the issue): - iptables-rules not loaded - dnsmasq not running Sometimes (in the full HE.net tunnel + v6 gateway configuration), the problem is triggered by an IPv4 download, even. I'll keep tracking this down. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
Huh... even downloading over HE.net's tunnel doesn't kill it (within the 3 attempts I've tried) now. I have previously added a passive cooler to the USB/NIC chip as the RPi3 was down for this test. I'll keep the RPi3 up as a caching DNS + IPv6 gateway (ie. as before, minus DHCPv4), point DNS queries to it, and see how it behaves for the next week. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
I made a pair of scripts - one sets up the tunnel, addresses on dummy interfaces, and routing. The other one cleans up. Testing with iperf does NOT replicate the issue, however. Maybe someone else can find a test case that reliably triggers the bug. I have some ideas which I'll try soon. https://gist.github.com/myxal/7a191e8a62a45f9187ae56cbe3c862b2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
Sorry for the delayed response. I moved my network back to RPi1 so I can do experiments on the affected RPi3. I'm thinking, if this is indeed caused by the usage of a 6in4 tunnel, and you're unable to set up one with HE.net because of unavailability/ISP restrictions, it should be possible to set up a 6in4 tunnel within your own network (obviously, another host would be needed for this). I'll try to provide a config/script/whatever that would do this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
Oh, I had the URL wrong (archive.ubuntu instead of ports...). Installed .1019 kernel, headers, etc... issue persists with the new kernel - dmesg attached. ** Attachment added: "dmesg-1019.txt" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+attachment/5330924/+files/dmesg-1019.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
re: dnsmasq - whoops, private repo. Here's another link: https://paste.ubuntu.com/p/TCwQBkg9vS/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
@hui.wang: Only the RPi is acting as the IPv6 gateway for the network (it sends router advertisements to internal LAN on br0, issued by dnsmasq - the relevant dnsmasq config is here: https://github.com/myxal/DigitalHome/blob/master/configurations/dnsmasq/dnsmasq.d/Echolife6.conf The mac is unaware of the tunnel, it autoconfigures itself according to the router advertisements, and RPi forwards the packets according to normal forwaring rules. But we're getting off-topic here. Regarding your config - the internal (br0) and external (he-ipv6) should have addresses from different prefixes. I'm not sure which of the settings is wrong, but seeing as you are setting the gateway to what looks like a correct address, I'm guessing your internal address is wrong. On tunnelbroker, this is listed as: "Client IPv6 address" - this is the external address, and must be set exactly as indicated by tunnelbroker "Server IPv6 address" - this is the gateway - seems correctly entered in the config "Routed /64" - this is the prefix from which you'll pick an address for the internal (br0) interface. I picked ...::1 because it's easy to enter and remember. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
Not quite. - for downloads, as the issue happens when using IPv6 tunnel, so I'd use wget -6 ... - for youtube - this is playing on another machine (Mac running Chromium browser). I mentioned it because it's significant amount of traffic which, in presence of IPv6 connectivity, will (mostly) go through the tunnel. Your IPv6 addresses look misconfigured, as both he-ipv6 and br0 have addresses from the same /64 prefix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
How to set up bridge - is github gist link OK? https://gist.github.com/myxal/6554bd370658a11621a30cd2e6e7d7a8 Testing without IPv6 tunnel - I'm not sure what you mean. If eth0 is the WAN side, and only wlan0 is for the LAN side, then there's no bridge needed... This would introduce another NAT (currently IPv4 NAT is already performed at the ISP router, and I can't change that), compared to the current setup - see the gist linked above. I have tried (previously, with kernel 1017 I think) just disabling the IPv6 part altogether (the tunnel interface was not created, static addresses not assigned, etc. wlan and eth0 still in bridge), and the issue was not reproduced. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
Sorry, got kinda stuck trying to test with a USB NIC: https://askubuntu.com/q/1212529/325336 After disabling systemd-resolved (+ putting a public DNS IPv4 address in resolv.conf), v6 download over the external USB NIC (Apple USB Ethernet, 05ac:1402) works fine. After switching the cable back to the built-in NIC, the error appeared almost immediately, didn't even get to try the v6 download. [ 2452.471188] br0: port 3(eth1) entered disabled state [ 3030.723594] br0: received packet on wlan0 with own address as source address (addr:b8:27:eb:3a:ba:a2, vlan:0) [ 3030.860954] br0: received packet on wlan0 with own address as source address (addr:b8:27:eb:3a:ba:a2, vlan:0) [ 3037.463785] br0: received packet on wlan0 with own address as source address (addr:b8:27:eb:3a:ba:a2, vlan:0) [ 3228.800706] asix 1-1.3:1.0 eth1: link up, 100Mbps, full-duplex, lpa 0xCDE1 [ 3228.804385] br0: port 3(eth1) entered blocking state [ 3228.804417] br0: port 3(eth1) entered forwarding state [ 3293.930873] [ cut here ] [ 3293.930958] NETDEV WATCHDOG: eth0 (lan78xx): transmit queue 0 timed out [ 3293.931102] WARNING: CPU: 3 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330 [ 3293.931109] Modules linked in: asix sit tunnel4 ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic bcm2835_v4l2(CE) ecc bcm2835_mmal_vchiq(CE) vc_sm_cma(CE) brcmfmac v4l2_common videobuf2_vmalloc brcmutil videobuf2_memops videobuf2_v4l2 cfg80211 videobuf2_common input_leds videodev mc spidev raspberrypi_hwmon uio_pdrv_genirq uio sch_fq_codel ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 [ 3293.931334] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G C E 5.3.0-1018-raspi2 #20-Ubuntu [ 3293.931339] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT) [ 3293.931348] pstate: 6045 (nZCv daif +PAN -UAO) [ 3293.931356] pc : dev_watchdog+0x324/0x330 [ 3293.931363] lr : dev_watchdog+0x324/0x330 [ 3293.931366] sp : 1001bd60 [ 3293.931371] x29: 1001bd60 x28: 0140 [ 3293.931380] x27: x26: [ 3293.931388] x25: f2fb79363000 x24: 4f7cab129018 [ 3293.931396] x23: x22: 0001 [ 3293.931404] x21: f2fb79363480 x20: 4f7cab407000 [ 3293.931412] x19: x18: [ 3293.931420] x17: 10fd8218 x16: 4f7ca9f0f060 [ 3293.931428] x15: f2fb79228510 x14: [ 3293.931437] x13: x12: 4f7cab54 [ 3293.931445] x11: 4f7cab42d000 x10: [ 3293.931453] x9 : 0004 x8 : 0192 [ 3293.931461] x7 : x6 : 0001 [ 3293.931468] x5 : x4 : 0008 [ 3293.931476] x3 : 4f7caaa15750 x2 : 0004 [ 3293.931484] x1 : 59c84c96ab783c00 x0 : [ 3293.931492] Call trace: [ 3293.931500] dev_watchdog+0x324/0x330 [ 3293.931515] call_timer_fn+0x3c/0x178 [ 3293.931525] __run_timers.part.0+0x200/0x330 [ 3293.931533] run_timer_softirq+0x40/0x78 [ 3293.931544] __do_softirq+0x168/0x384 [ 3293.931554] irq_exit+0xb0/0xe8 [ 3293.931564] __handle_domain_irq+0x70/0xc0 [ 3293.931572] bcm2836_arm_irqchip_handle_irq+0x74/0xe0 [ 3293.931579] el1_irq+0x108/0x200 [ 3293.931590] arch_cpu_idle+0x3c/0x1c8 [ 3293.931603] default_idle_call+0x24/0x48 [ 3293.931615] do_idle+0x210/0x2a0 [ 3293.931623] cpu_startup_entry+0x2c/0x30 [ 3293.931636] secondary_start_kernel+0x154/0x1c8 [ 3293.931641] ---[ end trace 356cf2f8b780723e ]--- [ 3734.263219] br0: port 3(eth1) entered disabled state [ 3737.505916] lan78xx 1-1.1.1:1.0 eth0: kevent 0 may have been dropped [ 3737.523763] lan78xx 1-1.1.1:1.0 eth0: kevent 0 may have been dropped [ 3737.541622] lan78xx 1-1.1.1:1.0 eth0: kevent 0 may have been dropped [ 3737.559099] lan78xx 1-1.1.1:1.0 eth0: kevent 0 may have been dropped [ 3737.576635] lan78xx 1-1.1.1:1.0 eth0: kevent 0 may have been dropped [ 3737.593932] lan78xx 1-1.1.1:1.0 eth0: kevent 0 may have been dropped [ 3737.611136] lan78xx 1-1.1.1:1.0 eth0: kevent 0 may have been dropped [ 3737.628048] lan78xx 1-1.1.1:1.0 eth0: kevent 0 may have been dropped ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
> Looks like to setup a 6in4 tunnel, I need a static public IP first I don't think that static IP is needed to make it work at least temporarily, I don't have a static one either, just public. You only need to have public IP on the device you can manage - e.g. router at home, and make sure that raspberry has a static internal address. Then, in the router's firewall/forwarding settings, either set raspberry as the DMZ host, or set forward anything from the remote tunnel IP to raspberry. That being said, if are behind a carrier NAT which you can't manage, you won't be able to set up the tunnel. I've just tried the switch to dwc2 driver, it didn't help. (still on ~1018 kernel). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
Where can I find the ~1019 kernel? The repositories are still at ~1018. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
Hi. The USB ports still work fine - I use a USB keyboard to correctly reboot the machine when it gets stuck. My most recent replication was with ~1017 kernel, will try the newer ones. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
@hui.wang Is there anything else needed from me? The issue still happens (intermittently under my normal use as an IPv6 gateway). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
** Attachment added: "10rpi3-bridge-static.yaml" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+attachment/5326547/+files/10rpi3-bridge-static.yaml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
** Attachment added: "99-ipv6-home.conf" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+attachment/5326537/+files/99-ipv6-home.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
** Attachment added: "rules.v4" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+attachment/5326548/+files/rules.v4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
** Attachment added: "rules.v6" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+attachment/5326549/+files/rules.v6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
(This is still with full setup, ie, jool and iptunnel, traffic using the tunnel): The first time I tried I also managed to download gparted without issues, but next time the issue appeared again. No jool and no tunnel: wget 2x 900MB (ubuntu iso), no issue. scp the same iso from local machine to RPi, also no issue. No jool, 6in4 tunnel + ip6tables: Replicated on 3rd attempt with wget. I think what may be contributing is that the machine is acting as an IPv6 gateway for my network, and there are some background bursts of load on the tunnel (Youtube playing on the desktop). The wget download itself is also going through the tunnel: $ wget http://ftp.antik.sk/ubuntu-releases/eoan/ubuntu-19.10-live-server-amd64.iso --2020-02-08 21:51:00-- http://ftp.antik.sk/ubuntu-releases/eoan/ubuntu-19.10-live-server-amd64.iso Resolving ftp.antik.sk (ftp.antik.sk)... 2a02:130:9900:30::12, 88.212.10.12 Connecting to ftp.antik.sk (ftp.antik.sk)|2a02:130:9900:30::12|:80... connected. Can you retry with a 6in4 tunnel? Im using the free offering from tunnelbroker.net Or perhaps suggest a way to collect more logs. I'll upload a set of relevant config files for: - netplan - netfilter-persistent - sysctl -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
** Attachment added: "15rpi3-HEnet-Prague.yaml" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+attachment/5326546/+files/15rpi3-HEnet-Prague.yaml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
Hmm, will look into this again. I'm using a feature-rich networking setup (6in4 tunnel, jool NAT64, LAN + WLAN bridge, ip(6)tables), maybe some of it is also required). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
** Description changed: - Raspberry Pi 3 network dies shortly after a burst of SD card IO (writes) and network load. Happened a few times when I tried to download a gparted zip release (~350 MiB) directly to the SD card, and then finally when I tried to scp the finished download from a desktop onto RPi's card. - Didn't collect information when it happened, but kept a copy of kernel.log. Here's the relevant part: + Raspberry Pi 3 network dies shortly after a burst of SD card IO (writes) and network load. Happened a few times (every time) when I tried to download a gparted zip release (~350 MiB) directly to the SD card, and then finally when I tried to scp the finished download from a desktop onto RPi's card. + Didn't collect information when it happened, but kept a copy of kern.log. Here's the relevant part: Feb 4 23:42:59 rpi3 kernel: [ 571.878359] [ cut here ] Feb 4 23:42:59 rpi3 kernel: [ 571.878420] NETDEV WATCHDOG: eth0 (lan78xx): transmit queue 0 timed out Feb 4 23:42:59 rpi3 kernel: [ 571.878550] WARNING: CPU: 3 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878557] Modules linked in: sit tunnel4 ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 Feb 4 23:42:59 rpi3 kernel: [ 571.878774] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu Feb 4 23:42:59 rpi3 kernel: [ 571.878781] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT) Feb 4 23:42:59 rpi3 kernel: [ 571.878789] pstate: 6045 (nZCv daif +PAN -UAO) Feb 4 23:42:59 rpi3 kernel: [ 571.878800] pc : dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878807] lr : dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878812] sp : 1001bd60 - Feb 4 23:42:59 rpi3 kernel: [ 571.878817] x29: 1001bd60 x28: 0140 - Feb 4 23:42:59 rpi3 kernel: [ 571.878827] x27: x26: - Feb 4 23:42:59 rpi3 kernel: [ 571.878836] x25: 8ecbefa4e000 x24: 305e0f529018 - Feb 4 23:42:59 rpi3 kernel: [ 571.878845] x23: x22: 0001 - Feb 4 23:42:59 rpi3 kernel: [ 571.878853] x21: 8ecbefa4e480 x20: 305e0f807000 - Feb 4 23:42:59 rpi3 kernel: [ 571.878862] x19: x18: - Feb 4 23:42:59 rpi3 kernel: [ 571.878871] x17: 10fd8218 x16: 305e0e30efb8 - Feb 4 23:42:59 rpi3 kernel: [ 571.878879] x15: 8ecbf922a290 x14: - Feb 4 23:42:59 rpi3 kernel: [ 571.87] x13: x12: 305e0f944000 - Feb 4 23:42:59 rpi3 kernel: [ 571.878897] x11: 305e0f82d000 x10: - Feb 4 23:42:59 rpi3 kernel: [ 571.878905] x9 : 0004 x8 : 017f - Feb 4 23:42:59 rpi3 kernel: [ 571.878913] x7 : x6 : 0001 - Feb 4 23:42:59 rpi3 kernel: [ 571.878921] x5 : x4 : 0008 - Feb 4 23:42:59 rpi3 kernel: [ 571.878929] x3 : 305e0ee15750 x2 : 0004 - Feb 4 23:42:59 rpi3 kernel: [ 571.878937] x1 : 6abb42c67c954600 x0 : + Feb 4 23:42:59 rpi3 kernel: [ 571.878817] x29: 1001bd60 x28: 0140 + Feb 4 23:42:59 rpi3 kernel: [ 571.878827] x27: x26: + Feb 4 23:42:59 rpi3 kernel: [ 571.878836] x25: 8ecbefa4e000 x24: 305e0f529018 + Feb 4 23:42:59 rpi3 kernel: [ 571.878845] x23: x22: 0001 + Feb 4 23:42:59 rpi3 kernel: [ 571.878853] x21: 8ecbefa4e480 x20: 305e0f807000 + Feb 4 23:42:59 rpi3 kernel: [ 571.878862] x19: x18: + Feb 4 23:42:59 rpi3 kernel: [ 571.878871] x17: 10fd8218 x16: 305e0e30efb8 + Feb 4 23:42:59 rpi3 kernel: [ 571.878879] x15: 8ecbf922a290 x14: + Feb 4 23:42:59 rpi3 kernel: [ 571.87] x13: x12: 305e0f944000 + Feb 4 23:42:59 rpi3 kernel: [ 571.878897] x11: 305e0f82d000 x10: + Feb 4 23:42:59 rpi3 kernel: [ 571.878905] x9 : 0004 x8 : 017f + Feb 4 23:42:59 rpi3 kernel: [ 571.
[Bug 1861936] [NEW] Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
Public bug reported: Raspberry Pi 3 network dies shortly after a burst of SD card IO (writes) and network load. Happened a few times (every time) when I tried to download a gparted zip release (~350 MiB) directly to the SD card, and then finally when I tried to scp the finished download from a desktop onto RPi's card. Didn't collect information when it happened, but kept a copy of kern.log. Here's the relevant part: Feb 4 23:42:59 rpi3 kernel: [ 571.878359] [ cut here ] Feb 4 23:42:59 rpi3 kernel: [ 571.878420] NETDEV WATCHDOG: eth0 (lan78xx): transmit queue 0 timed out Feb 4 23:42:59 rpi3 kernel: [ 571.878550] WARNING: CPU: 3 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878557] Modules linked in: sit tunnel4 ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 Feb 4 23:42:59 rpi3 kernel: [ 571.878774] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu Feb 4 23:42:59 rpi3 kernel: [ 571.878781] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT) Feb 4 23:42:59 rpi3 kernel: [ 571.878789] pstate: 6045 (nZCv daif +PAN -UAO) Feb 4 23:42:59 rpi3 kernel: [ 571.878800] pc : dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878807] lr : dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878812] sp : 1001bd60 Feb 4 23:42:59 rpi3 kernel: [ 571.878817] x29: 1001bd60 x28: 0140 Feb 4 23:42:59 rpi3 kernel: [ 571.878827] x27: x26: Feb 4 23:42:59 rpi3 kernel: [ 571.878836] x25: 8ecbefa4e000 x24: 305e0f529018 Feb 4 23:42:59 rpi3 kernel: [ 571.878845] x23: x22: 0001 Feb 4 23:42:59 rpi3 kernel: [ 571.878853] x21: 8ecbefa4e480 x20: 305e0f807000 Feb 4 23:42:59 rpi3 kernel: [ 571.878862] x19: x18: Feb 4 23:42:59 rpi3 kernel: [ 571.878871] x17: 10fd8218 x16: 305e0e30efb8 Feb 4 23:42:59 rpi3 kernel: [ 571.878879] x15: 8ecbf922a290 x14: Feb 4 23:42:59 rpi3 kernel: [ 571.87] x13: x12: 305e0f944000 Feb 4 23:42:59 rpi3 kernel: [ 571.878897] x11: 305e0f82d000 x10: Feb 4 23:42:59 rpi3 kernel: [ 571.878905] x9 : 0004 x8 : 017f Feb 4 23:42:59 rpi3 kernel: [ 571.878913] x7 : x6 : 0001 Feb 4 23:42:59 rpi3 kernel: [ 571.878921] x5 : x4 : 0008 Feb 4 23:42:59 rpi3 kernel: [ 571.878929] x3 : 305e0ee15750 x2 : 0004 Feb 4 23:42:59 rpi3 kernel: [ 571.878937] x1 : 6abb42c67c954600 x0 : Feb 4 23:42:59 rpi3 kernel: [ 571.878946] Call trace: Feb 4 23:42:59 rpi3 kernel: [ 571.878955] dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878967] call_timer_fn+0x3c/0x178 Feb 4 23:42:59 rpi3 kernel: [ 571.878977] __run_timers.part.0+0x200/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878985] run_timer_softirq+0x40/0x78 Feb 4 23:42:59 rpi3 kernel: [ 571.878995] __do_softirq+0x168/0x384 Feb 4 23:42:59 rpi3 kernel: [ 571.879007] irq_exit+0xb0/0xe8 Feb 4 23:42:59 rpi3 kernel: [ 571.879020] __handle_domain_irq+0x70/0xc0 Feb 4 23:42:59 rpi3 kernel: [ 571.879028] bcm2836_arm_irqchip_handle_irq+0x74/0xe0 Feb 4 23:42:59 rpi3 kernel: [ 571.879037] el1_irq+0x108/0x200 Feb 4 23:42:59 rpi3 kernel: [ 571.879050] arch_cpu_idle+0x3c/0x1c8 Feb 4 23:42:59 rpi3 kernel: [ 571.879069] default_idle_call+0x24/0x48 Feb 4 23:42:59 rpi3 kernel: [ 571.879081] do_idle+0x210/0x2a0 Feb 4 23:42:59 rpi3 kernel: [ 571.879091] cpu_startup_entry+0x28/0x30 Feb 4 23:42:59 rpi3 kernel: [ 571.879102] secondary_start_kernel+0x154/0x1c8 Feb 4 23:42:59 rpi3 kernel: [ 571.879108] ---[ end trace 349744d60a20e77a ]--- ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-1017-raspi2 5.3.0-1017.19 ProcVersionSignature: Ubuntu 5.3.0-1017.19-raspi2 5.3.13 Uname: Linux 5.3.0-1017-raspi2 aarch64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: arm64 Date: Tue Feb 4 23:49:19 2020 ProcEnviron: TERM=linux PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash S
[Bug 1858210] [NEW] timedatectl doesn't list all timezones
Public bug reported: Is there some filter determining which timezones are displayed by `timedatectl list-timezones`? My zone, Europe/Bratislava, is missing. Even stranger, it can successfully be set by timedatectl. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.2 ProcVersionSignature: Ubuntu 5.3.0-1014.16-raspi2 5.3.10 Uname: Linux 5.3.0-1014-raspi2 aarch64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: arm64 Date: Fri Jan 3 15:36:03 2020 Lspci: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.systemd.resolved.conf: 2020-01-03T01:02:47.779343 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858210 Title: timedatectl doesn't list all timezones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1858210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750392] Re: nplan cannot enable IPv6 privacy extensions
Ran into this issue today and found out why the privacy settings in /etc/sysctl.d/10-ipv6-privacy.conf are getting ignored - they're being overwritten by /etc/sysctl.d/99-cloudimg-ipv6.conf. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750392 Title: nplan cannot enable IPv6 privacy extensions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1750392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758507] Re: sky2 gigabit ethernet driver sometimes stops working after lid-open resume from sleep (88E8055)
@kleber-souza, I should get to it early next week. Which ubuntu releases do you need? artful and xenial? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758507 Title: sky2 gigabit ethernet driver sometimes stops working after lid-open resume from sleep (88E8055) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758507] Re: sky2 gigabit ethernet driver sometimes stops working after lid-open resume from sleep (88E8055)
Yes, the 200 variant also works (3 boots with 3 resumes). The first boot produced this new warning, but subsequent were OK: [ 64.072147] [ cut here ] [ 64.072149] Delta way too big! 18446743987613365433 ts=18446744047041339774 write stamp = 59427974341 If you just came from a suspend/resume, please switch to the trace global clock: echo global > /sys/kernel/debug/tracing/trace_clock ... [ 64.072244] Call Trace: [ 64.072248] ring_buffer_lock_reserve+0x137/0x350 [ 64.072253] trace_event_buffer_lock_reserve+0x6c/0x110 [ 64.072256] trace_event_buffer_reserve+0x62/0x80 [ 64.072260] trace_event_raw_event_do_sys_open+0x81/0x130 [ 64.072262] do_sys_open+0x260/0x290 [ 64.072264] SyS_openat+0x14/0x20 [ 64.072268] do_syscall_64+0x73/0x130 [ 64.072271] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 ... [ 64.072316] ---[ end trace 41d884fa46b78bbb ]--- ** Attachment added: "dmesg-d3-200-boot1.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758507/+attachment/5096427/+files/dmesg-d3-200-boot1.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758507 Title: sky2 gigabit ethernet driver sometimes stops working after lid-open resume from sleep (88E8055) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758507] Re: sky2 gigabit ethernet driver sometimes stops working after lid-open resume from sleep (88E8055)
Thanks, that appears to have fixed the issue. The lid device non- compliance message persists, but subsequent resumes by lid (tried 4) don't kill the NIC anymore. ** Attachment added: "dmesg-4.15.0-14-15-khfeng.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758507/+attachment/5095709/+files/dmesg-4.15.0-14-15-khfeng.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758507 Title: sky2 gigabit ethernet driver sometimes stops working after lid-open resume from sleep (88E8055) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758507] Re: sky2 gigabit ethernet driver sometimes stops working after lid-open resume from sleep (88E8055)
Well this is odd... I tried following the instructions on PM tracing from https://wiki.ubuntu.com/DebuggingKernelSuspend (using systemctl suspend instead of pm-suspend), but the system hangs on resume when tracing is enabled - and this happens also when pm_test is set to "devices" (doesn't happen with "freezer"). There is no hang when tracing full suspend on 4.8.0. ** Attachment added: "pm_trace of boot after hang with pm_test=devices" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758507/+attachment/5095301/+files/dmesg-4.16-rc7-test-devices-fail.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758507 Title: sky2 gigabit ethernet driver sometimes stops working after lid-open resume from sleep (88E8055) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758507] Re: sky2 gigabit ethernet driver sometimes stops working after lid-open resume from sleep (88E8055)
** Description changed: - After resuming from sleep, OCCASIONALLY the NIC is not functional, and - reloading the sky2 module does not work. Relevant parts from dmesg: + After resuming from sleep using the lid-open event, OFTEN (60% + replicable, usually after 2nd or later resume) the NIC is not + functional, and reloading the sky2 module does not help. Relevant parts + from dmesg: [ 582.852065] sky2 :04:00.0: Refused to change power state, currently in D3 ... [ 827.613729] sky2 :04:00.0: ignoring stuck error report bit [ 827.613748] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613750] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613752] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613754] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613756] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613759] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613761] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613763] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613765] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613767] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613769] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613772] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613774] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613776] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613778] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613780] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613782] sky2 :04:00.0: enp4s0: phy I/O error And after reloading the module: [ 1421.781480] sky2: driver version 1.30 [ 1421.781533] sky2 :04:00.0: enabling device ( -> 0003) [ 1421.781667] sky2 :04:00.0: unsupported chip type 0xff [ 1421.782292] sky2: probe of :04:00.0 failed with error -95 Possibly relevant: [ 1235.944086] ACPI: button: The lid device is not compliant to SW_LID. - Replicability: When it happens once, further suspend-resume cycles (tried ~5) don't fix it. Reboot may fix it, (again, for at least the 5 suspend cycles I've tried). + Replicability: When it happens once, further suspend-resume cycles (tried ~5) don't fix it. Reboot fixes the NIC, and it often survives first resume after that, but 1-2 suspend-resume cycles later the issue WILL occur again. Per-boot chance of encountering the issue - so far 2/5. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-12-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Sat Mar 24 09:54:10 2018 HibernationDevice: RESUME=UUID=02d18685-fc92-4ebe-a43e-34d1e52a26b1 InstallationDate: Installed on 2018-03-21 (3 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: FUJITSU SIEMENS ESPRIMO Mobile U9200 ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=bc171dce-b703-44f6-8244-22b6b3b1dc33 ro video=SVIDEO-1:d consoleblank=300 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2008 dmi.bios.vendor: Phoenix dmi.bios.version: 1.11 - 067 - 1566 dmi.board.name: S11D dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: 1.0 dmi.chassis.asset.tag: FSC dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnPhoenix:bvr1.11-067-1566:bd04/22/2008:svnFUJITSUSIEMENS:pnESPRIMOMobileU9200:pvr1.0:rvnFUJITSUSIEMENS:rnS11D:rvr1.0:cvnFUJITSUSIEMENS:ct10:cvr1.0: dmi.product.name: ESPRIMO Mobile U9200 dmi.product.version: 1.0 dmi.sys.vendor: FUJITSU SIEMENS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758507 Title: sky
[Bug 1758507] Re: sky2 gigabit ethernet driver sometimes stops working after lid-open resume from sleep (88E8055)
** Description changed: - After resuming from sleep using the lid-open event, OFTEN (60% - replicable, usually after 2nd or later resume) the NIC is not - functional, and reloading the sky2 module does not help. Relevant parts - from dmesg: + After resuming from sleep, OCCASIONALLY the NIC is not functional, and + reloading the sky2 module does not work. Relevant parts from dmesg: [ 582.852065] sky2 :04:00.0: Refused to change power state, currently in D3 ... [ 827.613729] sky2 :04:00.0: ignoring stuck error report bit [ 827.613748] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613750] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613752] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613754] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613756] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613759] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613761] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613763] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613765] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613767] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613769] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613772] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613774] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613776] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613778] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613780] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613782] sky2 :04:00.0: enp4s0: phy I/O error And after reloading the module: [ 1421.781480] sky2: driver version 1.30 [ 1421.781533] sky2 :04:00.0: enabling device ( -> 0003) [ 1421.781667] sky2 :04:00.0: unsupported chip type 0xff [ 1421.782292] sky2: probe of :04:00.0 failed with error -95 - Replicability: When it happens once, further suspend-resume cycles - (tried ~5) don't fix it. Reboot fixes the NIC, and it often survives - first resume after that, but 1-2 suspend-resume cycles later the issue - WILL occur again. + Possibly relevant: + [ 1235.944086] ACPI: button: The lid device is not compliant to SW_LID. + Replicability: When it happens once, further suspend-resume cycles (tried ~5) don't fix it. Reboot may fix it, (again, for at least the 5 suspend cycles I've tried). + Per-boot chance of encountering the issue - so far 2/5. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-12-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Sat Mar 24 09:54:10 2018 HibernationDevice: RESUME=UUID=02d18685-fc92-4ebe-a43e-34d1e52a26b1 InstallationDate: Installed on 2018-03-21 (3 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: FUJITSU SIEMENS ESPRIMO Mobile U9200 ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=bc171dce-b703-44f6-8244-22b6b3b1dc33 ro video=SVIDEO-1:d consoleblank=300 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2008 dmi.bios.vendor: Phoenix dmi.bios.version: 1.11 - 067 - 1566 dmi.board.name: S11D dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: 1.0 dmi.chassis.asset.tag: FSC dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnPhoenix:bvr1.11-067-1566:bd04/22/2008:svnFUJITSUSIEMENS:pnESPRIMOMobileU9200:pvr1.0:rvnFUJITSUSIEMENS:rnS11D:rvr1.0:cvnFUJITSUSIEMENS:ct10:cvr1.0: dmi.product.name: ESPRIMO Mobile U9200 dmi.product.version: 1.0 dmi.sys.vendor: FUJITSU SIEMENS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758507 Title:
[Bug 1758507] Re: sky2 gigabit ethernet driver sometimes stops working after resume from sleep (88E8055)
Hi, I have not been keeping up with ubuntu - before 18.04, I've been using only
16.10 to the extent where this issue would show up, and it didn't appear in
that release (I would suspend and resume the machine at least twice a week).
I would also point out, that I've seen identical symptoms ("Refused to change
power state") way back in Linux 3.2 in Ubuntu 12.04, see Ubuntu bug 1007841
In the meantime, I've also noticed a situation (with stock 18.04 kernel)
where the NIC would fail after 2nd resume or later - but, see below...
As for 4.16-rc7: I've tried 5 boots with 3 suspends each, and while none
of them failed after 1st resume, 4 failed after 2nd or 3rd resume.
I'm watching for something else now with 4.16-rc7 - it seems the bug is
triggered only when the machine is waken up by the lid-open event (about
60% failure rate - and I think all of the successful resumes were 1st
resumes after reboot). 0% replication when waking up by power button.
I will update repro steps with this info.
** Summary changed:
- sky2 gigabit ethernet driver sometimes stops working after resume from sleep
(88E8055)
+ sky2 gigabit ethernet driver sometimes stops working after lid-open resume
from sleep (88E8055)
** Description changed:
- After resuming from sleep, OCCASIONALLY the NIC is not functional, and
- reloading the sky2 module does not work. Relevant parts from dmesg:
+ After resuming from sleep using the lid-open event, OFTEN (60%
+ replicable, usually after 2nd or later resume) the NIC is not
+ functional, and reloading the sky2 module does not help. Relevant parts
+ from dmesg:
[ 582.852065] sky2 :04:00.0: Refused to change power state, currently in
D3
...
[ 827.613729] sky2 :04:00.0: ignoring stuck error report bit
[ 827.613748] sky2 :04:00.0: enp4s0: phy I/O error
[ 827.613750] sky2 :04:00.0: enp4s0: phy I/O error
[ 827.613752] sky2 :04:00.0: enp4s0: phy I/O error
[ 827.613754] sky2 :04:00.0: enp4s0: phy I/O error
[ 827.613756] sky2 :04:00.0: enp4s0: phy I/O error
[ 827.613759] sky2 :04:00.0: enp4s0: phy I/O error
[ 827.613761] sky2 :04:00.0: enp4s0: phy I/O error
[ 827.613763] sky2 :04:00.0: enp4s0: phy I/O error
[ 827.613765] sky2 :04:00.0: enp4s0: phy I/O error
[ 827.613767] sky2 :04:00.0: enp4s0: phy I/O error
[ 827.613769] sky2 :04:00.0: enp4s0: phy I/O error
[ 827.613772] sky2 :04:00.0: enp4s0: phy I/O error
[ 827.613774] sky2 :04:00.0: enp4s0: phy I/O error
[ 827.613776] sky2 :04:00.0: enp4s0: phy I/O error
[ 827.613778] sky2 :04:00.0: enp4s0: phy I/O error
[ 827.613780] sky2 :04:00.0: enp4s0: phy I/O error
[ 827.613782] sky2 :04:00.0: enp4s0: phy I/O error
And after reloading the module:
[ 1421.781480] sky2: driver version 1.30
[ 1421.781533] sky2 :04:00.0: enabling device ( -> 0003)
[ 1421.781667] sky2 :04:00.0: unsupported chip type 0xff
[ 1421.782292] sky2: probe of :04:00.0 failed with error -95
Replicability: When it happens once, further suspend-resume cycles (tried ~5)
don't fix it. Reboot may fix it, (again, for at least the 5 suspend cycles I've
tried).
Per-boot chance of encountering the issue - so far 2/5.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-12-generic 4.15.0-12.13
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-12-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p',
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer':
'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer':
'amixer'
Date: Sat Mar 24 09:54:10 2018
HibernationDevice: RESUME=UUID=02d18685-fc92-4ebe-a43e-34d1e52a26b1
InstallationDate: Installed on 2018-03-21 (3 days ago)
InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64
(20180319)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: FUJITSU SIEMENS ESPRIMO Mobile U9200
ProcEnviron:
LANGUAGE=en_US:en
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic
root=UUID=bc171dce-b703-44f6-8244-22b6b3b1dc33 ro video=SVIDEO-1:d
consoleblank=300
RelatedPackageVersions:
linux-restricted-modules-4.15.0-12-generic N/A
linux-backports-modules-4.15.0-12-generic N/A
linux-firmware 1.173
R
[Bug 1758507] Re: sky2 gigabit ethernet driver sometimes stops working after resume from sleep (88E8055)
** Summary changed: - sky2 gigabit ethernet driver stops working after resume from sleep (88E8055) + sky2 gigabit ethernet driver sometimes stops working after resume from sleep (88E8055) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758507 Title: sky2 gigabit ethernet driver sometimes stops working after resume from sleep (88E8055) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758507] Re: sky2 gigabit ethernet driver stops working after resume from sleep (88E8055)
** Description changed: - After resuming from sleep, the NIC is not functional, and reloading the - sky2 module does not work. Relevant parts from dmesg: + After resuming from sleep, OCCASIONALLY the NIC is not functional, and + reloading the sky2 module does not work. Relevant parts from dmesg: [ 582.852065] sky2 :04:00.0: Refused to change power state, currently in D3 - ... + ... [ 827.613729] sky2 :04:00.0: ignoring stuck error report bit [ 827.613748] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613750] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613752] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613754] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613756] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613759] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613761] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613763] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613765] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613767] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613769] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613772] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613774] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613776] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613778] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613780] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613782] sky2 :04:00.0: enp4s0: phy I/O error And after reloading the module: [ 1421.781480] sky2: driver version 1.30 [ 1421.781533] sky2 :04:00.0: enabling device ( -> 0003) [ 1421.781667] sky2 :04:00.0: unsupported chip type 0xff [ 1421.782292] sky2: probe of :04:00.0 failed with error -95 + + Replicability: When it happens once, further suspend-resume cycles (tried ~5) don't fix it. Reboot may fix it, (again, for at least the 5 suspend cycles I've tried). + Per-boot chance of encountering the issue - so far 2/5. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-12-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Sat Mar 24 09:54:10 2018 HibernationDevice: RESUME=UUID=02d18685-fc92-4ebe-a43e-34d1e52a26b1 InstallationDate: Installed on 2018-03-21 (3 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: FUJITSU SIEMENS ESPRIMO Mobile U9200 ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=bc171dce-b703-44f6-8244-22b6b3b1dc33 ro video=SVIDEO-1:d consoleblank=300 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2008 dmi.bios.vendor: Phoenix dmi.bios.version: 1.11 - 067 - 1566 dmi.board.name: S11D dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: 1.0 dmi.chassis.asset.tag: FSC dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnPhoenix:bvr1.11-067-1566:bd04/22/2008:svnFUJITSUSIEMENS:pnESPRIMOMobileU9200:pvr1.0:rvnFUJITSUSIEMENS:rnS11D:rvr1.0:cvnFUJITSUSIEMENS:ct10:cvr1.0: dmi.product.name: ESPRIMO Mobile U9200 dmi.product.version: 1.0 dmi.sys.vendor: FUJITSU SIEMENS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758507 Title: sky2 gigabit ethernet driver sometimes stops working after resume from sleep (88E8055) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758507] [NEW] sky2 gigabit ethernet driver stops working after resume from sleep (88E8055)
Public bug reported: After resuming from sleep, the NIC is not functional, and reloading the sky2 module does not work. Relevant parts from dmesg: [ 582.852065] sky2 :04:00.0: Refused to change power state, currently in D3 ... [ 827.613729] sky2 :04:00.0: ignoring stuck error report bit [ 827.613748] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613750] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613752] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613754] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613756] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613759] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613761] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613763] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613765] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613767] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613769] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613772] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613774] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613776] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613778] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613780] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613782] sky2 :04:00.0: enp4s0: phy I/O error And after reloading the module: [ 1421.781480] sky2: driver version 1.30 [ 1421.781533] sky2 :04:00.0: enabling device ( -> 0003) [ 1421.781667] sky2 :04:00.0: unsupported chip type 0xff [ 1421.782292] sky2: probe of :04:00.0 failed with error -95 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-12-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Sat Mar 24 09:54:10 2018 HibernationDevice: RESUME=UUID=02d18685-fc92-4ebe-a43e-34d1e52a26b1 InstallationDate: Installed on 2018-03-21 (3 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: FUJITSU SIEMENS ESPRIMO Mobile U9200 ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=bc171dce-b703-44f6-8244-22b6b3b1dc33 ro video=SVIDEO-1:d consoleblank=300 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2008 dmi.bios.vendor: Phoenix dmi.bios.version: 1.11 - 067 - 1566 dmi.board.name: S11D dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: 1.0 dmi.chassis.asset.tag: FSC dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnPhoenix:bvr1.11-067-1566:bd04/22/2008:svnFUJITSUSIEMENS:pnESPRIMOMobileU9200:pvr1.0:rvnFUJITSUSIEMENS:rnS11D:rvr1.0:cvnFUJITSUSIEMENS:ct10:cvr1.0: dmi.product.name: ESPRIMO Mobile U9200 dmi.product.version: 1.0 dmi.sys.vendor: FUJITSU SIEMENS ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: - *TODO* + After resuming from sleep, the NIC is not functional, and reloading the + sky2 module does not work. Relevant parts from dmesg: + + [ 582.852065] sky2 :04:00.0: Refused to change power state, currently in D3 + ... + [ 827.613729] sky2 :04:00.0: ignoring stuck error report bit + [ 827.613748] sky2 :04:00.0: enp4s0: phy I/O error + [ 827.613750] sky2 :04:00.0: enp4s0: phy I/O error + [ 827.613752] sky2 :04:00.0: enp4s0: phy I/O error + [ 827.613754] sky2 :04:00.0: enp4s0: phy I/O error + [ 827.613756] sky2 :04:00.0: enp4s0: phy I/O error + [ 827.613759] sky2 :04:00.0: enp4s0: phy I/O error + [ 827.613761] sky2 :04:00.0: enp4s0: phy I/O error + [ 827.613763] sky2 :04:00.0: enp4s0: phy I/O error + [ 827.613765] sky2 :04:00.0: enp4s0: phy I/O error + [ 827.613767] sky2 :04:00.0: enp4s0: phy I/O error + [ 827.613769] sky2 :04:00.0: enp4s0: phy I/O error + [ 827.613772] sky2 :04:00.0: enp
[Bug 1685442] Re: Errors: flip_done timed out during boot-up; slow boot
Related: https://bugs.freedesktop.org/show_bug.cgi?id=93782 Some patches are available there. ** Bug watch added: freedesktop.org Bugzilla #93782 https://bugs.freedesktop.org/show_bug.cgi?id=93782 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685442 Title: Errors: flip_done timed out during boot-up; slow boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685442] Re: Errors: flip_done timed out during boot-up; slow boot
** Attachment added: "4.8.0-040800rc1-generic-dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685442/+attachment/5086299/+files/4.8.0-040800rc1-generic-dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685442 Title: Errors: flip_done timed out during boot-up; slow boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685442] Re: Errors: flip_done timed out during boot-up; slow boot
** Attachment added: "4.7.0-040700rc1-generic-dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685442/+attachment/5086298/+files/4.7.0-040700rc1-generic-dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685442 Title: Errors: flip_done timed out during boot-up; slow boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685442] Re: Errors: flip_done timed out during boot-up; slow boot
** Attachment added: "4.6.0-040600rc1-generic-dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685442/+attachment/5086297/+files/4.6.0-040600rc1-generic-dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685442 Title: Errors: flip_done timed out during boot-up; slow boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685442] Re: Errors: flip_done timed out during boot-up; slow boot
** Attachment added: "4.5.0-040500rc7-generic-dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685442/+attachment/5086296/+files/4.5.0-040500rc7-generic-dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685442 Title: Errors: flip_done timed out during boot-up; slow boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685442] Re: Errors: flip_done timed out during boot-up; slow boot
Strange observation - to save my eyes from the strain of looking at the old laptop's screen, I hooked up a monitor over VGA - and the stalls stopped (on both the tested 16.04 and on 18.04!! The message is still there in dmesg, so this had the positive effect of cutting down the time to find "first bad kernel" drastically. I tested on latest 16.04, and the first kernel with the "vblank wait timed out on crtc 0" message is 4.6-rc1; 4.5-rc7 is OK. I will upload dmesg logs shortly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685442 Title: Errors: flip_done timed out during boot-up; slow boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685442] Re: Errors: flip_done timed out during boot-up; slow boot
Tested yesterday's bionic daily server build, issue is still present on my FSC Esprimo Mobile U9200 (Intel GM965). Hopefully, I'll find time to track down which -rc release introduced the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685442 Title: Errors: flip_done timed out during boot-up; slow boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1363654] Re: Upgrade netatalk to version 3.x
>From what I've read in the debian bug, the issue there is that some parts of the code have unspecified license and authors could not be reached to clarify the situation. Unless Canonical decide to update the package themselves, the answer for Debian is probably never - the relevant file (debian/copyright) hasn't seen a commit in 2 years. The PPA also seems to have been inactive for over a year. As a user, I can only recommend building it yourself, the project has a decent how-to targeted at Ubuntu: http://netatalk.sourceforge.net/wiki/index.php/Install_Netatalk_3.1.7_on_Ubuntu_14.10_Utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1363654 Title: Upgrade netatalk to version 3.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netatalk/+bug/1363654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1363654] [NEW] Upgrade netatalk to version 3.x
Public bug reported: All ubuntu versions up to and including utopic, use the legacy 2.x release. Netatalk 3.0.0 was released as stable in 2012, the latest version as of time of reporting is 3.1.6. http://netatalk.sourceforge.net/ ** Affects: netatalk (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version ** Summary changed: - Upgrade package to version 3.x + Upgrade netatalk to version 3.x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1363654 Title: Upgrade netatalk to version 3.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netatalk/+bug/1363654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1270453] Re: Clonezilla is incompatible with partclone
I'm also affected by this :( Out of curiosity, I checked out Clonezilla live system and debian testing, both are updated to partclone v 0.2.70. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1270453 Title: Clonezilla is incompatible with partclone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partclone/+bug/1270453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 656675] Re: Two saned processes and "bind failed: Address already in use"
Has this changed in the 4 years since? I just tried saned on 12.04, then 14.04, and the same problem occurs on both of them. Indeed, ps listing reveals 2 saned processes running, with only 1 of them being bound to only tcp6. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/656675 Title: Two saned processes and "bind failed: Address already in use" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/656675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1011669] Re: PCIe ExpressCards are not automatically detected upon insertion on FSC Esprimo Mobile U9200
Backport - no, I don't think it's worth the trouble. Linux is my secondary system, as there are many issues in KDE keeping me from making it my primary OS. I'll try it again when trusty's released. Feel free to close the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1011669 Title: PCIe ExpressCards are not automatically detected upon insertion on FSC Esprimo Mobile U9200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1011669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007841] Re: 11ab:4363 sky2 driver (Marvell Ethernet devices) problem after resume
Tested with today's daily (kernel 3.12.0-7), no issues on 2 susped/resume cycles. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007841 Title: 11ab:4363 sky2 driver (Marvell Ethernet devices) problem after resume To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1007841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1011669] Re: PCIe ExpressCards are not automatically detected upon insertion on FSC Esprimo Mobile U9200
Verfied - no problems when booting with the card inserted, the relevant device are correctly removed from the system. Consider this bug fixed as of 3.12.0-7 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1011669 Title: PCIe ExpressCards are not automatically detected upon insertion on FSC Esprimo Mobile U9200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1011669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1011669] Re: PCIe ExpressCards are not automatically detected upon insertion on FSC Esprimo Mobile U9200
Well this is nice surprise - today's daily (liveCD session) detects the card (inserted after booting with an empty slot) without issues and without any extra kernel parameters. There seem to be no logs on card insert/eject (only the first time, when the card's driver is loaded), but the relevant interfaces appear and work - I connected an HDD and browsed the contents in the file manager, benchmarked with hdparm and looked at SMART status and values with smartctl - no problems encountered. $ uname -r 3.12.0-7-generic $ cat /proc/cmdline file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ~# ls -l /sys/class/scsi_host/ total 0 ... lrwxrwxrwx 1 root root 0 Jan 2 18:41 host17 -> ../../devices/pci:00/:00:1c.0/:02:00.0/ata16/host17/scsi_host/host17 lrwxrwxrwx 1 root root 0 Jan 2 18:41 host18 -> ../../devices/pci:00/:00:1c.0/:02:00.0/ata17/host18/scsi_host/host18 ... Attaching dmesg from this working system for reference. I'll now try booting with the card in the slot, then eject it to see if the scsi_host device is properly removed from the system. ** Attachment added: "working kernel's dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1011669/+attachment/3939301/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1011669 Title: PCIe ExpressCards are not automatically detected upon insertion on FSC Esprimo Mobile U9200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1011669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1250618] Re: ogg123 can't play flac files with ID3 tags
Filed ticket upstream: https://trac.xiph.org/ticket/1988 ** Bug watch added: Xiph.org Trac #1988 http://trac.xiph.org/ticket/1988 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1250618 Title: ogg123 can't play flac files with ID3 tags To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vorbis-tools/+bug/1250618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1250618] Re: ogg123 can't play flac files with ID3 tags
** Description changed: 1) Kubuntu saucy (13.10) amd64 2) 1.4.0-1ubuntu3 - ogg123 command from vorbis-tools refuses to play some flac files. mplayer2 has no issue with the same file: - $ ogg123 /tmp/02.The\ Lioness.flac + ogg123 command from vorbis-tools refuses flac files with id3 tags. + $ file ./02\ -\ The\ Lioness.flac + ./02 - The Lioness.flac: Audio file with ID3 version 2.3.0, contains: FLAC audio bitstream data, 16 bit, stereo, 44.1 kHz, 12755484 samples + $ ogg123 /tmp/02.The\ Lioness.flac Audio Device: Advanced Linux Sound Architecture (ALSA) output - Error opening /tmp/02.The Lioness.flac using the oggvorbis module. The file may be corrupted. - $ mplayer /tmp/02.The\ Lioness.flac - MPlayer2 UNKNOWN (C) 2000-2012 MPlayer Team - mplayer: could not connect to socket - mplayer: No such file or directory - Failed to open LIRC support. You will not be able to use your remote control. + Error opening /tmp/02.The Lioness.flac using the oggvorbis module. The + file may be corrupted. - Playing /tmp/02.The Lioness.flac. - Detected file format: raw FLAC (libavformat) - [flac @ 0x7f090bbf7220]max_analyze_duration reached - [lavf] stream 0: audio (flac), -aid 0 - Clip info: - ARTIST: Xandria - ALBUM: Ravenheart - TITLE: The Lioness - encoder: FLAC.EXE -6 -V -T "ARTIST=Xandria" -T "TITLE=The Lioness" -T "ALBUM=Ravenheart" -T "DATE=2004" -T "TRACKNUMBER=02" -T "GENRE=Gothic Rock" -T "COMMENT=CRC : 26A47C55" -o - TLEN: 289240 - track: 02 - encoded_by: Exact Audio Copy (Sicherer Modus) - DATE: 2004 - GENRE: Gothic Rock - COMMENT: CRC : 26A47C55 - Load subtitles in /tmp/ - == - Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders - AUDIO: 44100 Hz, 2 ch, s16le, 0.0 kbit/0.00% (ratio: 0->176400) - Selected audio codec: [ffflac] afm: ffmpeg (FFmpeg FLAC audio) - == - AO: [pulse] 44100Hz 2ch s16le (2 bytes per sample) - Video: no video - Starting playback... + WORKAROUND: You can strip the tags from the file using id3v2 utility (thanks, dardar at ubuntuforums): + id3v2 -D *.flac + Stripping id3 tag in "…"...id3v1 and v2 stripped. + ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: vorbis-tools 1.4.0-1ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 12 21:23:24 2013 InstallationDate: Installed on 2013-09-05 (67 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902.2) MarkForUpload: True SourcePackage: vorbis-tools UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1250618 Title: ogg123 can't play flac files with ID3 tags To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vorbis-tools/+bug/1250618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1250618] Re: ogg123 can't play flac files with ID3 tags
** Summary changed: - ogg123 can't play some flac files + ogg123 can't play flac files with ID3 tags -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1250618 Title: ogg123 can't play flac files with ID3 tags To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vorbis-tools/+bug/1250618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1250618] Re: ogg123 can't play some flac files
You can get the flac file in question here: https://mega.co.nz/#!5U5VmSiY!BV6QekSpym-_USdutnWtHHCT45VGEd- _i0KxPO7Axxs (~35MiB) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1250618 Title: ogg123 can't play some flac files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vorbis-tools/+bug/1250618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1250618] [NEW] ogg123 can't play some flac files
Public bug reported: 1) Kubuntu saucy (13.10) amd64 2) 1.4.0-1ubuntu3 ogg123 command from vorbis-tools refuses to play some flac files. mplayer2 has no issue with the same file: $ ogg123 /tmp/02.The\ Lioness.flac Audio Device: Advanced Linux Sound Architecture (ALSA) output Error opening /tmp/02.The Lioness.flac using the oggvorbis module. The file may be corrupted. $ mplayer /tmp/02.The\ Lioness.flac MPlayer2 UNKNOWN (C) 2000-2012 MPlayer Team mplayer: could not connect to socket mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. Playing /tmp/02.The Lioness.flac. Detected file format: raw FLAC (libavformat) [flac @ 0x7f090bbf7220]max_analyze_duration reached [lavf] stream 0: audio (flac), -aid 0 Clip info: ARTIST: Xandria ALBUM: Ravenheart TITLE: The Lioness encoder: FLAC.EXE -6 -V -T "ARTIST=Xandria" -T "TITLE=The Lioness" -T "ALBUM=Ravenheart" -T "DATE=2004" -T "TRACKNUMBER=02" -T "GENRE=Gothic Rock" -T "COMMENT=CRC : 26A47C55" -o TLEN: 289240 track: 02 encoded_by: Exact Audio Copy (Sicherer Modus) DATE: 2004 GENRE: Gothic Rock COMMENT: CRC : 26A47C55 Load subtitles in /tmp/ == Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders AUDIO: 44100 Hz, 2 ch, s16le, 0.0 kbit/0.00% (ratio: 0->176400) Selected audio codec: [ffflac] afm: ffmpeg (FFmpeg FLAC audio) == AO: [pulse] 44100Hz 2ch s16le (2 bytes per sample) Video: no video Starting playback... ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: vorbis-tools 1.4.0-1ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 12 21:23:24 2013 InstallationDate: Installed on 2013-09-05 (67 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902.2) MarkForUpload: True SourcePackage: vorbis-tools UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: vorbis-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1250618 Title: ogg123 can't play some flac files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vorbis-tools/+bug/1250618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1233898] Re: kio-mtp misbehaves after opening a photo with Gwenview, the device disconnects
Well, bummer. Literally minutes after I posted this, update do KDE 4.11.2 appears and seems to fix the problem. The syslog messages about not claiming the interface still appear though, but now it produces a device reset without losing the connection: Oct 2 01:48:35 esprimo kernel: [ 896.948291] usb 2-3: reset high-speed USB device number 9 using ehci-pci Oct 2 01:48:36 esprimo kernel: [ 897.085024] usb 2-3: usbfs: process 5358 (kio_mtp) did not claim interface 0 before use Oct 2 01:48:45 esprimo kernel: [ 906.437486] usb 2-3: usbfs: process 5312 (kio_mtp) did not claim interface 0 before use Oct 2 01:49:11 esprimo kernel: [ 932.859337] usb 2-3: usbfs: process 5398 (kio_mtp) did not claim interface 0 before use Oct 2 01:49:12 esprimo kernel: [ 932.968099] usb 2-3: reset high-speed USB device number 9 using ehci-pci Oct 2 01:49:12 esprimo kernel: [ 933.100984] usb 2-3: usbfs: process 5398 (kio_mtp) did not claim interface 0 before use Oct 2 01:49:22 esprimo kernel: [ 943.925586] usb 2-3: usbfs: process 5312 (kio_mtp) did not claim interface 0 before use I'm also posting the list of updated packages, which does not include kio-mtp, strangely. ** Attachment added: "aptitude update log" https://bugs.launchpad.net/ubuntu/+source/kio-mtp/+bug/1233898/+attachment/3854350/+files/aptitude-log.txt ** Summary changed: - kio-mtp misbehaves after opening a photo with Gwenview, the device disconnects + kio-mtp misbehaves after opening a photo with Gwenview, the device resets -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1233898 Title: kio-mtp misbehaves after opening a photo with Gwenview, the device resets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kio-mtp/+bug/1233898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1233898] [NEW] kio-mtp misbehaves after opening a photo with Gwenview, the device disconnects
Public bug reported: Trying this on the latest 13.10 Kubuntu: 1. Connect MTP device (Nexus 4 with CyanogenMod 10.1.3) with some jpg photos on it 2. Navigate to the photos in Dolphin, and open one - Gwenview will open Problem: Gwenview will never finish opening the photo - the device is re-connected (new device notification appears in notifications), and the old connection is lost. This appears in syslog during the event: Oct 2 00:51:27 esprimo kernel: [32149.302961] usb 2-2: usbfs: process 11390 (kio_mtp) did not claim interface 0 before use Oct 2 00:51:27 esprimo kernel: [32149.412083] usb 2-2: reset high-speed USB device number 31 using ehci-pci Oct 2 00:51:27 esprimo kernel: [32149.544547] usb 2-2: device firmware changed Oct 2 00:51:27 esprimo kernel: [32149.544621] usb 2-2: USB disconnect, device number 31 Oct 2 00:51:27 esprimo colord: device removed: sysfs-LGE-Nexus_4 Oct 2 00:51:27 esprimo kernel: [32149.660038] usb 2-2: new high-speed USB device number 32 using ehci-pci Oct 2 00:51:27 esprimo kernel: [32149.793879] usb 2-2: New USB device found, idVendor=18d1, idProduct=4ee2 Oct 2 00:51:27 esprimo kernel: [32149.793883] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 2 00:51:27 esprimo kernel: [32149.793886] usb 2-2: Product: Nexus 4 Oct 2 00:51:27 esprimo kernel: [32149.793888] usb 2-2: Manufacturer: LGE Oct 2 00:51:27 esprimo kernel: [32149.793890] usb 2-2: SerialNumber: 0244a95994d88bed Oct 2 00:51:27 esprimo colord: Device added: sysfs-LGE-Nexus_4 Versions: gwenview: 4.11.1-0ubuntu1 kio-mtp: 0.75+git20130930-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: kio-mtp 0.75+git20130930-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Wed Oct 2 00:52:21 2013 InstallationDate: Installed on 2013-09-05 (26 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902.2) MarkForUpload: True SourcePackage: kio-mtp UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kio-mtp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1233898 Title: kio-mtp misbehaves after opening a photo with Gwenview, the device disconnects To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kio-mtp/+bug/1233898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007841] Re: 11ab:4363 sky2 driver (Marvell Ethernet devices) problem after resume
Actually, that's the same link that's already posted in the summary since a year ago. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007841 Title: 11ab:4363 sky2 driver (Marvell Ethernet devices) problem after resume To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1007841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007841] Re: 11ab:4363 sky2 driver (Marvell Ethernet devices) problem after resume
Aye, right - turns out I did: http://marc.info/?l=linux-pm&m=134229404527442&w=2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007841 Title: 11ab:4363 sky2 driver (Marvell Ethernet devices) problem after resume To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1007841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007841] Re: 11ab:4363 sky2 driver (Marvell Ethernet devices) problem after resume
** Description changed: After resuming from suspend, a Marvel 88E8055 (wired NIC) will fail to detect carrier (link is permanently down). Reloading the sky2 module does not help - the module will fail to initialize the hardware and the eth0 interfaces is gone until reboot. The suspend/resume for this NIC has worked without issues in 10.10 and some older releases I've had permanently installed. I haven't really tested this with other releases that have come and gone since - which is the best course of action here: - testing older releases, or - obtaining older kernel versions (from mainline ppa?) and testing those? Upstream contacted: http://www.spinics.net/lists/netdev/msg203017.html + + WORKAROUND: + Delete the NIC from the system and have kernel perform a rescan on the PCI bus: + echo 1 > /sys/class/net/eth0/device/remove ; sleep 1;\ + echo 1 > /sys/class/pci_bus/\:00/rescan + + Adjust PCI bus number as appropriate. http://marc.info/?l=linux-pm&m=134229404527442&w=2 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-24-generic 3.2.0-24.39 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michalp1932 F pulseaudio /dev/snd/pcmC0D0p: michalp1932 F...m pulseaudio CRDA: country SK: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfc40 irq 47' Mixer name : 'Realtek ALC262' Components : 'HDA:10ec0262,1734,00100202' Controls : 33 Simple ctrls : 19 Date: Sat Jun 2 17:08:19 2012 InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423) MachineType: FUJITSU SIEMENS ESPRIMO Mobile U9200 ProcEnviron: LANGUAGE= TERM=xterm LANG=sk_SK.UTF-8 LC_MESSAGES=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=e8d55f9c-868e-4354-afc7-f15447baa72b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-24-generic N/A linux-backports-modules-3.2.0-24-generic N/A linux-firmware1.79 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2008 dmi.bios.vendor: Phoenix dmi.bios.version: 1.11 - 067 - 1566 dmi.board.name: S11D dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: 1.0 dmi.chassis.asset.tag: FSC dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnPhoenix:bvr1.11-067-1566:bd04/22/2008:svnFUJITSUSIEMENS:pnESPRIMOMobileU9200:pvr1.0:rvnFUJITSUSIEMENS:rnS11D:rvr1.0:cvnFUJITSUSIEMENS:ct10:cvr1.0: dmi.product.name: ESPRIMO Mobile U9200 dmi.product.version: 1.0 dmi.sys.vendor: FUJITSU SIEMENS ** Description changed: After resuming from suspend, a Marvel 88E8055 (wired NIC) will fail to detect carrier (link is permanently down). Reloading the sky2 module does not help - the module will fail to initialize the hardware and the eth0 interfaces is gone until reboot. The suspend/resume for this NIC has worked without issues in 10.10 and some older releases I've had permanently installed. I haven't really tested this with other releases that have come and gone since - which is the best course of action here: - testing older releases, or - obtaining older kernel versions (from mainline ppa?) and testing those? Upstream contacted: http://www.spinics.net/lists/netdev/msg203017.html + http://marc.info/?l=linux-pm&m=134229404527442&w=2 WORKAROUND: Delete the NIC from the system and have kernel perform a rescan on the PCI bus: echo 1 > /sys/class/net/eth0/device/remove ; sleep 1;\ - echo 1 > /sys/class/pci_bus/\:00/rescan + echo 1 > /sys/class/pci_bus/\:00/rescan Adjust PCI bus number as appropriate. - http://marc.info/?l=linux-pm&m=134229404527442&w=2 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-24-generic 3.2.0-24.39 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 AudioDe
[Bug 1007841] Re: 11ab:4363 sky2 driver (Marvell Ethernet devices) problem after resume
Hello Chris. Regarding bug progress - sorry, no. I'm not that experienced with kernel code and building modules. With that said, I have installed Arch some 2 months ago (kernel 3.10, now it's at 3.11), and a month ago a daily build of Kubuntu 13.10 (kernel 3.11-rc-something, now updated to stable 3.11). While I've used each only for about 2 weeks, I don't recall this bug occurring even once - I certainly cannot induce it by suspending and resuming immediately, something that DOES happen with Kubuntu 12.10, which I also keep around. I suggest you try a new kernel and see what it does. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007841 Title: 11ab:4363 sky2 driver (Marvell Ethernet devices) problem after resume To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1007841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 761730] Re: zabbix-server-pgsql should depend on php5-pgsql
Sorry if I'm musguided it this, but zabbix-server does not, and should not depend on php-pgsql, it's the zabbix-frontend-php, that should, and does depend on php5-pgsql OR php5-mysql. The whole problem here is that apt installs the mysql variant, when it should use the pgsql version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/761730 Title: zabbix-server-pgsql should depend on php5-pgsql To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zabbix/+bug/761730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1074033] Re: Menu from menu button in titlebar opens in wrong position/direction on multiscreen setup
Yes, occurs with Oxygen theme as well ** Attachment added: "screenshot - oxygen" https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1074033/+attachment/3423455/+files/menu-fail-Oxygen.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1074033 Title: Menu from menu button in titlebar opens in wrong position/direction on multiscreen setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1074033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 629358] Re: [Fujitsu ESPRIMO Mobile U9200] Incorrect response to Brightness Up/Down keys
The key codes with atkbd.softraw=0 are the same as posted in the summary: # single brightness-down 0xe0 0x4c 0xe0 0xcc #single brighness-up 0xe0 0x54 0xe0 0xd4 0xe0 0x4c 0xe0 0xcc When the brightness level is at either extreme, the key, which can no longer change the brightness does not produce any output in showkey. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/629358 Title: [Fujitsu ESPRIMO Mobile U9200] Incorrect response to Brightness Up/Down keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/629358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 629358] Re: [Fujitsu ESPRIMO Mobile U9200] Incorrect response to Brightness Up/Down keys
With the video.use_bios... parameter set to 0, the backlight keys are as broken as with stock configuration. Chris, should I boot the kernel with only "atkbd.softraw=0" option, or with both atkbd.. and video.use_bios..? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/629358 Title: [Fujitsu ESPRIMO Mobile U9200] Incorrect response to Brightness Up/Down keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/629358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 629358] Re: [Fujitsu ESPRIMO Mobile U9200] Incorrect response to Brightness Up/Down keys
Writing "8" to the brightness file errors out with "Invalid argument". According to max_brightness, highest value is 1. Writing either 0 or 1 into the brightness file does not change the physical backlight brightness level. ** Attachment added: "lslabacklight" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/629358/+attachment/3421587/+files/lslabacklight -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/629358 Title: [Fujitsu ESPRIMO Mobile U9200] Incorrect response to Brightness Up/Down keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/629358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 629358] Re: [Fujitsu ESPRIMO Mobile U9200] Incorrect response to Brightness Up/Down keys
Oh, btw - with the vendor boot option, I can no longer change the brightness using KDE's power management widget. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/629358 Title: [Fujitsu ESPRIMO Mobile U9200] Incorrect response to Brightness Up/Down keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/629358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 629358] Re: [Fujitsu ESPRIMO Mobile U9200] Incorrect response to Brightness Up/Down keys
Using the acpi_backlight=vendor boot option fixes the button behaviour ** Attachment added: "vendorbacklight" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/629358/+attachment/3421586/+files/vendorbacklight -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/629358 Title: [Fujitsu ESPRIMO Mobile U9200] Incorrect response to Brightness Up/Down keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/629358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 629358] Re: [Fujitsu ESPRIMO Mobile U9200] Incorrect response to Brightness Up/Down keys
I'll reboot to try the acpi=vendor trick and report on that in a while. ** Attachment added: "version" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/629358/+attachment/3421500/+files/version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/629358 Title: [Fujitsu ESPRIMO Mobile U9200] Incorrect response to Brightness Up/Down keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/629358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 629358] Re: [Fujitsu ESPRIMO Mobile U9200] Incorrect response to Brightness Up/Down keys
** Attachment added: "backlight" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/629358/+attachment/3421464/+files/backlight -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/629358 Title: [Fujitsu ESPRIMO Mobile U9200] Incorrect response to Brightness Up/Down keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/629358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 629358] Re: [Fujitsu ESPRIMO Mobile U9200] Incorrect response to Brightness Up/Down keys
** Attachment added: "fwts results" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/629358/+attachment/3421467/+files/results.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/629358 Title: [Fujitsu ESPRIMO Mobile U9200] Incorrect response to Brightness Up/Down keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/629358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 629358] Re: [Fujitsu ESPRIMO Mobile U9200] Incorrect response to Brightness Up/Down keys
** Attachment added: "acpi" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/629358/+attachment/3421465/+files/acpi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/629358 Title: [Fujitsu ESPRIMO Mobile U9200] Incorrect response to Brightness Up/Down keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/629358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 629358] Re: [Fujitsu ESPRIMO Mobile U9200] Incorrect response to Brightness Up/Down keys
** Attachment added: "video" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/629358/+attachment/3421468/+files/video -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/629358 Title: [Fujitsu ESPRIMO Mobile U9200] Incorrect response to Brightness Up/Down keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/629358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 629358] Re: [Fujitsu ESPRIMO Mobile U9200] Incorrect response to Brightness Up/Down keys
** Attachment added: "DSDT.dsl" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/629358/+attachment/3421466/+files/DSDT.dsl -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/629358 Title: [Fujitsu ESPRIMO Mobile U9200] Incorrect response to Brightness Up/Down keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/629358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 629358] Re: [Fujitsu ESPRIMO Mobile U9200] Incorrect response to Brightness Up/Down keys
** Attachment added: "dmidecode.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/629358/+attachment/3421469/+files/dmidecode.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/629358 Title: [Fujitsu ESPRIMO Mobile U9200] Incorrect response to Brightness Up/Down keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/629358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 629358] Re: [Fujitsu ESPRIMO Mobile U9200] Incorrect response to Brightness Up/Down keys
Yes, just booted a live session of 10.04.4 and it behaves the same way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/629358 Title: [Fujitsu ESPRIMO Mobile U9200] Incorrect response to Brightness Up/Down keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/629358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 629358] Re: Incorrect response to Brightness Up/Down keys
Same behaviour on 3.7.0-030700rc3-generic ** Tags removed: kernel-bug-exists-upstream-3.7.0-030700rc2-generic needs-upstream-testing ** Tags added: kernel-bug-exists-upstream-3.7.0-030700rc3-generic ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/629358 Title: Incorrect response to Brightness Up/Down keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/629358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1074033] Re: Menu from menu button in titlebar opens in wrong position/direction on multiscreen setup
** Attachment added: "screenshot with insufficient space above the button" https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1074033/+attachment/3420799/+files/snapshot1.png -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1074033 Title: Menu from menu button in titlebar opens in wrong position/direction on multiscreen setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1074033/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1074033] [NEW] Menu from menu button in titlebar opens in wrong position/direction on multiscreen setup
Public bug reported: Kubuntu Quantal (12.10) amd64, stock KDE packages. Description: The menu that is opened by the "menu" button in the window titlebar (this button has the icon of a particular application, to which the window belongs, and is the left-most button in default Kubuntu setup) is positioned wrong on bottom monitor in a multi-monitor setup. Preconditions: The monitor setup is: laptop screen under an external monitor connected over VGA: xrandr --output VGA1 --auto xrandr --output LVDS1 --auto --below VGA1 Replication/problem: Move a window (any window) to the laptop screen, then click on the menu button. If there's enough space above the button to display the entire menu, it's displayed upwards of the button. If there isn't enough space, it's displayed on the VGA monitor. Expected behaviour: The menu should be displayed downwards, unless there's not enough space on the screen where the button is actually located. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: kde-window-manager 4:4.9.2-0ubuntu2.1 Uname: Linux 3.7.0-030700rc2-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Thu Nov 1 16:37:21 2012 InstallationDate: Installed on 2012-10-28 (3 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: kde-workspace UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kde-workspace (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal ** Attachment added: "screenshot with enough space above the button" https://bugs.launchpad.net/bugs/1074033/+attachment/3420796/+files/snapshot2.png -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1074033 Title: Menu from menu button in titlebar opens in wrong position/direction on multiscreen setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1074033/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 629358] Re: Incorrect response to Brightness Up/Down keys
Bug still exists, tested with quantal: stock kernel (3.5.0-17) mainlinee build (3.7.0-030700rc2-generic) Both kernels show the same behaviour. As in previous releases, can be worked around by disabling the brightness_switch_enabled parameter: # echo N > /sys/module/video/parameters/brightness_switch_enabled ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/629358 Title: Incorrect response to Brightness Up/Down keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/629358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 629358] Re: Incorrect response to Brightness Up/Down keys
** Tags added: kernel-bug-exists-upstream-3.7.0-030700rc2-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/629358 Title: Incorrect response to Brightness Up/Down keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/629358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
