[Bug 275335] [NEW] Ubuntu fail loading in ATA33 mode with 40-pin cable, dump to busybox/initramfs
Public bug reported: Setup: Asus A8N5X 2GB RAM 320GB SATA HD (1st sata) 80GB SATA (2nd sata) eVGA GeForce 7900 GT LG GSA-H22N DVD writer (using a 40-pin cable) Kubuntu AMD64 LiveCD. Although this apply to all the Ubuntu flavors. In fact, from what I read, this seem to apply to 2.6.26 (and later) kernel in general. Description: I was unable to boot liveCD. Try/Install/Check CD all start to load, and then I get dumped to BusyBox/initramfs text page. Loading with splash screen disabled, I see: Sense key: Hardware Error [Current] Add_Sense: Logical unit communication CRC error (Ultra_DMA/32) I/O error, dev sr0, sector 128 repeating for a couple of times, before getting dumped to command prompt. I looked the Web, and found many people with BusyBox prompt problem. Many of the threads suggested workaround of setting SATA mode to 'RAID' (from 'IDE') in the BIOS, or using 'all_generic_ide' on the command line in the boot. Changing to RAID mode didn't help me. Setting 'all_generic_ide' did let me boot normally. However, I'm concerned that this only patch the real problem, and I worry about the consequences of setting that parameter. Will my IDE run slower for example? Also, from the error above, I deducted that the problem was related to my DVD (dev sr0). I finally found a thread about using a 80-pin cable for the CDROM, which I did (I had 40-pin), and it worked. Now booting without problem. Investigation: I found out, from the BIOS boot screen (the one that show you your devices, when you boot, just after POST, just before booting to HD/CD), that before, with the 40-pin DVD cable, I was in ATA33 mode. Now, I'm in ATA66 mode. This cause no problem with Windows, but seem to have an effect in 2.6.26 kernel. My guess is that the most likely cause is that the kernel try to boot with the device (DVD in my case) in ATA66 mode, even though the 40-pin cable does not allow for more than ATA33 (due to electrical noise consideration). This was causing error after the kernel took over and continue in reading the LiveCD. Is my reasoning right? I could be wrong though :) Conclusion: It appear that using a 40-pin IDE cable for the CDROM (or other devices in the PC), ubuntu fail to access the device because it try to access it in ATA66 mode. The kernel does not properly sense 40-pin cable, in which case it would revert to ATA33 mode. ** Affects: ubuntu Importance: Undecided Status: New -- Ubuntu fail loading in ATA33 mode with 40-pin cable, dump to busybox/initramfs https://bugs.launchpad.net/bugs/275335 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 259901] Re: 8.10 alpha4 / Kernel gives I/O error on CD(?)
I had the same problem. I ended-up 'fixing' it by replacing my DVD cable (40-pin) with an 80-pin cable. It could have problem detecting/using ATA33 mode. In my case, changing the cable let the driver run properly in ATA66 mode (bug#275335). -- 8.10 alpha4 / Kernel gives I/O error on CD(?) https://bugs.launchpad.net/bugs/259901 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 275335] Re: Ubuntu fail loading in ATA33 mode with 40-pin cable, dump to busybox/initramfs
*** This bug is a duplicate of bug 228624 *** https://bugs.launchpad.net/bugs/228624 I just looked at dmesg, and yes, it seem to be that bug. (from dmesg on my system) [ 39.510447] ata2.00: ATAPI: HL-DT-STDVD-RAM GSA-H22N, 1.02, max UDMA/66 [ 39.686305] ata2.00: configured for UDMA/66 Confirmed duplicate. Thanks. -- Ubuntu fail loading in ATA33 mode with 40-pin cable, dump to busybox/initramfs https://bugs.launchpad.net/bugs/275335 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854314] Re: Legacy directory /var/run in /lib/systemd/system/dbus.socket
Same thing here ... Dec 1 06:42:11 lx-dev3 containerd[845]: time="2020-12-01T06:42:11.225821304-05:00" level=info msg="Stop CRI service" Dec 1 06:42:11 lx-dev3 containerd[845]: time="2020-12-01T06:42:11.242385111-05:00" level=info msg="Stop CRI service" Dec 1 06:42:11 lx-dev3 containerd[845]: time="2020-12-01T06:42:11.253040416-05:00" level=info msg="Event monitor stopped" Dec 1 06:42:11 lx-dev3 containerd[845]: time="2020-12-01T06:42:11.253082773-05:00" level=info msg="Stream server stopped" Dec 1 06:42:11 lx-dev3 systemd[1]: containerd.service: Succeeded. Dec 1 06:42:11 lx-dev3 systemd[1]: Stopped containerd container runtime. Dec 1 06:42:14 lx-dev3 systemd[1]: Reloading. Dec 1 06:42:14 lx-dev3 systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. Dec 1 06:42:14 lx-dev3 systemd[1]: /etc/systemd/system/rc-local.service:11: Support for option SysVStartPriority= has been removed and it is ignored Dec 1 06:42:14 lx-dev3 systemd[1]: /lib/systemd/system/docker.socket:6: ListenStream= references a path below legacy directory /var/run/, updating /var/run/docker.sock → /run/docker.sock; please update the unit file accordingly. Dec 1 06:42:15 lx-dev3 systemd[1]: Reloading. Dec 1 06:42:15 lx-dev3 systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. Dec 1 06:42:15 lx-dev3 systemd[1]: /etc/systemd/system/rc-local.service:11: Support for option SysVStartPriority= has been removed and it is ignored Dec 1 06:42:15 lx-dev3 systemd[1]: /lib/systemd/system/docker.socket:6: ListenStream= references a path below legacy directory /var/run/, updating /var/run/docker.sock → /run/docker.sock; please update the unit file accordingly. Dec 1 06:42:15 lx-dev3 systemd[1]: Starting containerd container runtime... Dec 1 06:42:15 lx-dev3 systemd[1]: Started containerd container runtime. ... And, after that, instead of having a file /var/run/docker I had a file /var/run/docker= -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854314 Title: Legacy directory /var/run in /lib/systemd/system/dbus.socket To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1854314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814393] Re: "make: write error: stdout" on parallel builds
I have yet to see any issue (i.e. it's working fine) with 4.15.0.46 (I used xenial-proposed to upgrade). As the rest of you, I had constant issue with this in 4.15.0-45 So yes, maybe it is related to the tty bug. This does seem to be consistent with the behavior I was seeing with current kernel. For example, I had many 'resources busy' and other output-related messages on make output. And, doing: make -j8 2>&1 | tee outfile.txt I often saw the console just stop outpointing any text (although the compilation continued, and completed, in the background). So, Jburgess777 you may be correct about the duplicate... Regards, Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814393 Title: "make: write error: stdout" on parallel builds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1814393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835809] Re: AMD Ryzen 3000 series fails to boot
Good findings! Thank you so much for testing the rdrand theory. I guess a read fix would require a new ISO, which could easily be made as a dot release (19.04.1). Regards, Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835809 Title: AMD Ryzen 3000 series fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1686084] Re: x11vnc on zesty terminates with **stack smashing detected** error
I mean, 0.9.13-6 :) Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1686084 Title: x11vnc on zesty terminates with **stack smashing detected** error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11vnc/+bug/1686084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1686084] Re: x11vnc on zesty terminates with **stack smashing detected** error
This is fixed in 0.19.13-6 The fix is in Cosmic, but this would need to be backported to Bionic See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881632 Regards, Eric ** Bug watch added: Debian Bug tracker #881632 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881632 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1686084 Title: x11vnc on zesty terminates with **stack smashing detected** error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11vnc/+bug/1686084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1686084] Re: x11vnc on zesty terminates with **stack smashing detected** error
I verified by installing x11vnc-data and x11vnc .deb packages from Cosmic (over the already installed Bionic version) and there's no more crash. This is not the recommended solution though, we should have an official backport for Bionic. x11vnc is pretty much unusable with this issue though... This issue appeared mostly when a popup appeared (when clicking on a menu for example, and the menu popup appeared). Regards, Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1686084 Title: x11vnc on zesty terminates with **stack smashing detected** error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11vnc/+bug/1686084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1709649] Re: 229 backport for race between explicit mount and handling automount
Thanks for porting this to Xenial. Should the Xenial Ubuntu Base release be updated? The Ubuntu Base 16.04.3 does come with the problematic systemd, and on some systems, like the armhf, booting to a bare rootfs is impossible (always get the issue, which manifest itself as 'A start job is running for dev-ttys0.device' message and hang pretty much right after the 1:30 minute delay timeout. Or, without releasing an Ubuntu Base update, the documentation (Wiki) probably should include a note on this (i.e. 'To document'). qemu could be used to update the systemd package, or possibly downloading and manually updating the newer systemd related files to the extracted rootfs. Regards, Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1709649 Title: 229 backport for race between explicit mount and handling automount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1709649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1709649] Re: 229 backport for race between explicit mount and handling automount
Ok, I just tried with this version, and the issue I am seeing sadly does persist. So, this does not resolve it. Please ignore the last comment. Sorry, Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1709649 Title: 229 backport for race between explicit mount and handling automount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1709649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
