| Author |
Message |
alexk
|
|
Post subject: Black screen on boot
 Posted: 20.08.2013, 13:00
|
|
Joined: 2010-10-01
Posts: 284
Status: Offline
|
|
After dist-upgrade today, I'm getting a black screen on boot, around populating devices. It times out after a minute or two and the boot process continues, apparently normally, to the kdm login screen.
Code:
$ tail history.log
Commandline: apt-get -y dist-upgrade
Install: libavformat54:amd64 (9.8-2, automatic), liblwres90:amd64 (9.9.3.dfsg.P2-2, automatic), libavresample1:amd64 (9.8-2, automatic), libavfilter3:amd64 (9.8-2, automatic), libcogl-pango12:amd64 (1.14.0-2, automatic), libcogl12:amd64 (1.14.0-2, automatic), libisccfg90:amd64 (9.9.3.dfsg.P2-2, automatic), libbind9-90:amd64 (9.9.3.dfsg.P2-2, automatic), libavcodec-extra-54:amd64 (9.8-2, automatic), libboost-system1.54.0:amd64 (1.54.0-2+b1, automatic), python3-pkg-resources:amd64 (0.6.49-2, automatic), python3-defer:amd64 (1.0.6-2, automatic), libboost-filesystem1.54.0:amd64 (1.54.0-2+b1, automatic), libdns99:amd64 (9.9.3.dfsg.P2-2, automatic), libopenimageio1.2:amd64 (1.2.1~dfsg0-3, automatic), blender-data:amd64 (2.68a-3, automatic), python3-gi:amd64 (3.8.3-1+b1, automatic), python3-aptdaemon:amd64 (1.1.1-1, automatic), libboost-locale1.49.0:amd64 (1.49.0-4, automatic), python3-dbus:amd64 (1.2.0-2+b1, automatic), libavutil52:amd64 (9.8-2, automatic), libisccc90:amd64 (9.9.3.dfsg.P2-2, automatic), libisc95:amd64 (9.9.3.dfsg.P2-2, automatic)
Upgrade: bind9-host:amd64 (9.8.4.dfsg.P1-6+nmu3, 9.9.3.dfsg.P2-2), libktoblzcheck1c2a:amd64 (1.42-1, 1.43-1), gir1.2-clutter-1.0:amd64 (1.10.8-2, 1.14.4-2), python3:amd64 (3.3.2-13, 3.3.2-15), aptdaemon-data:amd64 (0.45-3, 1.1.1-1), python-httplib2:amd64 (0.7.4-2, 0.8-2), libdb5.1:amd64 (5.1.29-6, 5.1.29-7), libdb5.1:i386 (5.1.29-6, 5.1.29-7), gettext-base:amd64 (0.18.3-1, 0.18.3.1-1), libclutter-gtk-1.0-0:amd64 (1.2.0-2, 1.2.0-2+b1), libstdc++-4.8-dev:amd64 (4.8.1-8, 4.8.1-9), hplip:amd64 (3.13.4-1+b1, 3.13.8-1), libmediainfo0:amd64 (0.7.64-1, 0.7.64-2), empathy-common:amd64 (3.4.2.3-3, 3.4.2.3-4), enfuse:amd64 (4.0+dfsg-5, 4.0+dfsg-6), libasan0:amd64 (4.8.1-8, 4.8.1-9), libqt4-xml:amd64 (4.8.5+dfsg-2, 4.8.5+dfsg-3), libqt4-xml:i386 (4.8.5+dfsg-2, 4.8.5+dfsg-3), libatomicparsley0:amd64 (2.1.3-5, 2.1.3-5+b1), libquadmath0:amd64 (4.8.1-8, 4.8.1-9), libnetfilter-conntrack3:amd64 (1.0.3-1, 1.0.4-1), gcc-4.8-base:amd64 (4.8.1-8, 4.8.1-9), gcc-4.8-base:i386 (4.8.1-8, 4.8.1-9), libqt4-network:amd64 (4.8.5+dfsg-2, 4.8.5+dfsg-3), libqt4-network:i386 (4.8.5+dfsg-2, 4.8.5+dfsg-3), libqt4-sql-mysql:amd64 (4.8.5+dfsg-2, 4.8.5+dfsg-3), mesa-utils:amd64 (8.0.1-2+b3, 8.1.0-1), libgettextpo-dev:amd64 (0.18.3-1, 0.18.3.1-1), unrar:amd64 (4.2.4-0.3, 5.0.10-1), libqt4-sql:amd64 (4.8.5+dfsg-2, 4.8.5+dfsg-3), claws-mail:amd64 (3.9.2-1, 3.9.2-2), rss-glx:amd64 (0.9.1-5+b4, 0.9.1-6), x11-utils:amd64 (7.7~1, 7.7+1), libsane-hpaio:amd64 (3.13.4-1+b1, 3.13.8-1), gir1.2-gst-plugins-base-1.0:amd64 (1.0.8-1, 1.0.9-1), cpp-4.8:amd64 (4.8.1-8, 4.8.1-9), qdbus:amd64 (4.8.5+dfsg-2, 4.8.5+dfsg-3), gtkpod:amd64 (2.1.3-5, 2.1.3-5+b1), libgettextpo0:amd64 (0.18.3-1, 0.18.3.1-1), libgstreamer-plugins-base1.0-0:amd64 (1.0.8-1, 1.0.9-1), libgomp1:amd64 (4.8.1-8, 4.8.1-9), libqtcore4:amd64 (4.8.5+dfsg-2, 4.8.5+dfsg-3), libqtcore4:i386 (4.8.5+dfsg-2, 4.8.5+dfsg-3), at-spi2-core:amd64 (2.9.4-1, 2.9.5-1), libqt4-qt3support:amd64 (4.8.5+dfsg-2, 4.8.5+dfsg-3), gstreamer1.0-plugins-base:amd64 (1.0.8-1, 1.0.9-1), libmx-1.0-2:amd64 (1.4.6-2, 1.4.6-2+b1), amarok-utils:amd64 (2.7.1-1, 2.8.0-1), libqt4-svg:amd64 (4.8.5+dfsg-2, 4.8.5+dfsg-3), libasprintf-dev:amd64 (0.18.3-1, 0.18.3.1-1), libqt4-dbus:amd64 (4.8.5+dfsg-2, 4.8.5+dfsg-3), libqt4-dbus:i386 (4.8.5+dfsg-2, 4.8.5+dfsg-3), libqt4-xmlpatterns:amd64 (4.8.5+dfsg-2, 4.8.5+dfsg-3), libqt4-sql-sqlite:amd64 (4.8.5+dfsg-2, 4.8.5+dfsg-3), gir1.2-coglpango-1.0:amd64 (1.10.2-7, 1.14.0-2), libjavascriptcoregtk-3.0-0:amd64 (1.8.1-4, 2.0.4-2+b1), libqt4-opengl:amd64 (4.8.5+dfsg-2, 4.8.5+dfsg-3), libtsan0:amd64 (4.8.1-8, 4.8.1-9), console-setup:amd64 (1.94, 1.95), libwebkitgtk-1.0-0:amd64 (1.8.1-4, 2.0.4-2+b1), qt4-qtconfig:amd64 (4.8.5+dfsg-2, 4.8.5+dfsg-3), uswsusp:amd64 (1.0+20120915-3, 1.0+20120915-4), console-setup-linux:amd64 (1.94, 1.95), gstreamer1.0-x:amd64 (1.0.8-1, 1.0.9-1), gir1.2-javascriptcoregtk-3.0:amd64 (1.8.1-4, 2.0.4-2+b1), sudo:amd64 (1.8.5p2-1+nmu1, 1.8.7-3), libhpmud0:amd64 (3.13.4-1+b1, 3.13.8-1), libgcc1-dbg:amd64 (4.8.1-8, 4.8.1-9), libqt4-script:amd64 (4.8.5+dfsg-2, 4.8.5+dfsg-3), parted:amd64 (2.3-14, 2.3-15), python-aptdaemon.gtkwidgets:amd64 (0.45-3, 1.1.1-1), libzbar0:amd64 (0.10+doc-8, 0.10+doc-9), libgcc1:amd64 (4.8.1-8, 4.8.1-9), libgcc1:i386 (4.8.1-8, 4.8.1-9), grub-common:amd64 (2.00-15, 2.00-17), dh-python:amd64 (1.20130807-1, 1.20130819-1), rhino:amd64 (1.7R3-5, 1.7R4-2), amarok:amd64 (2.7.1-1, 2.8.0-1), enblend:amd64 (4.0+dfsg-5, 4.0+dfsg-6), gir1.2-cogl-1.0:amd64 (1.10.2-7, 1.14.0-2), gpicview:amd64 (0.2.3-2, 0.2.3+git20130714-2), nmap:amd64 (6.25-0.2, 6.40-0.1), dnsutils:amd64 (9.8.4.dfsg.P1-6+nmu3, 9.9.3.dfsg.P2-2), hplip-doc:amd64 (3.13.4-1, 3.13.8-1), python-aptdaemon.gtk3widgets:amd64 (0.45-3, 1.1.1-1), klibc-utils:amd64 (2.0.1-3.1, 2.0.2-1), libclutter-imcontext-0.1-0:amd64 (0.1.4-3, 0.1.4-3+b1), libqt4-dev-bin:amd64 (4.8.5+dfsg-2, 4.8.5+dfsg-3), qt4-linguist-tools:amd64 (4.8.5+dfsg-2, 4.8.5+dfsg-3), libclutter-1.0-0:amd64 (1.10.8-2, 1.14.4-2), grub2-common:amd64 (2.00-15, 2.00-17), libatomic1:amd64 (4.8.1-8, 4.8.1-9), printer-driver-hpijs:amd64 (3.13.4-1+b1, 3.13.8-1), libxtables10:amd64 (1.4.20-1, 1.4.20-2), openjdk-7-jre-headless:amd64 (7u25-2.3.12-2, 7u25-2.3.12-4), libswscale2:amd64 (0.8.8-1, 9.8-2), libpython3-stdlib:amd64 (3.3.2-13, 3.3.2-15), libatk-bridge2.0-0:amd64 (2.9.4-1, 2.9.5-1), gstreamer1.0-alsa:amd64 (1.0.8-1, 1.0.9-1), ca-certificates-java:amd64 (20121112+nmu2, 20130815), blender:amd64 (2.63a-4, 2.68a-3), g++-4.8:amd64 (4.8.1-8, 4.8.1-9), libparted0debian1:amd64 (2.3-14, 2.3-15), libatk-wrapper-java:amd64 (0.30.4-3, 0.30.4-4), librhino-java:amd64 (1.7R3-5, 1.7R4-2), liblzo2-2:amd64 (2.06-1, 2.06-1.1), liblzo2-2:i386 (2.06-1, 2.06-1.1), iptables:amd64 (1.4.20-1, 1.4.20-2), libqt4-designer:amd64 (4.8.5+dfsg-2, 4.8.5+dfsg-3), qtcore4-l10n:amd64 (4.8.5+dfsg-2, 4.8.5+dfsg-3), python3-minimal:amd64 (3.3.2-13, 3.3.2-15), libqtdbus4:amd64 (4.8.5+dfsg-2, 4.8.5+dfsg-3), libqtdbus4:i386 (4.8.5+dfsg-2, 4.8.5+dfsg-3), libclutter-gst-1.0-0:amd64 (1.6.0-2, 1.6.0-2+b1), libwebkitgtk-3.0-0:amd64 (1.8.1-4, 2.0.4-2+b1), libav-tools:amd64 (0.8.8-1, 9.8-2), libarmadillo3:amd64 (3.900.7+dfsg-1, 3.910.0+dfsg-1), devede:amd64 (3.23.0~ds1-2, 3.23.0~ds1-3), openjdk-7-jre-lib:amd64 (7u25-2.3.12-2, 7u25-2.3.12-4), libgcc-4.8-dev:amd64 (4.8.1-8, 4.8.1-9), python-sip:amd64 (4.14.7-3+b1, 4.14.7-4), xserver-xorg-video-ati:amd64 (6.14.4-8, 7.2.0-1), libpostproc52:amd64 (0.8.8-1, 0.git20120821-3), python-aptdaemon-gtk:amd64 (0.45-3, 1.1.1-1), dnsmasq-base:amd64 (2.66-3, 2.66-4), libnetcf1:amd64 (0.2.3-3, 0.2.3-4), gcc-4.8:amd64 (4.8.1-8, 4.8.1-9), libatspi2.0-0:amd64 (2.9.4-1, 2.9.5-1), grub2:amd64 (2.00-15, 2.00-17), xserver-xorg-video-fbdev:amd64 (0.4.2-4+b3, 0.4.3-1), git-man:amd64 (1.8.4~rc2-1, 1.8.4~rc3-1), grub-pc-bin:amd64 (2.00-15, 2.00-17), python-aptdaemon:amd64 (0.45-3, 1.1.1-1), openjdk-7-jre:amd64 (7u25-2.3.12-2, 7u25-2.3.12-4), aptdaemon:amd64 (0.45-3, 1.1.1-1), gstreamer1.0-pulseaudio:amd64 (1.0.8-1, 1.0.9-1), libqt4-test:amd64 (4.8.5+dfsg-2, 4.8.5+dfsg-3), amarok-common:amd64 (2.7.1-1, 2.8.0-1), git:amd64 (1.8.4~rc2-1, 1.8.4~rc3-1), grub-pc:amd64 (2.00-15, 2.00-17), gettext:amd64 (0.18.3-1, 0.18.3.1-1), youtube-dl:amd64 (2013.08.08-1, 2013.08.17-1), printer-driver-hpcups:amd64 (3.13.4-1+b1, 3.13.8-1), libcluttergesture-0.0.2-0:amd64 (0.0.2.1-7, 0.0.2.1-7+b1), libklibc:amd64 (2.0.1-3.1, 2.0.2-1), libgfortran3:amd64 (4.8.1-8, 4.8.1-9), libatk-wrapper-java-jni:amd64 (0.30.4-3, 0.30.4-4), libgstreamer1.0-0:amd64 (1.0.8-1, 1.0.9-1), gstreamer1.0-plugins-good:amd64 (1.0.8-1, 1.0.9-1), keyboard-configuration:amd64 (1.94, 1.95), libwebkitgtk-3.0-common:amd64 (1.8.1-4, 2.0.4-2), libasprintf0c2:amd64 (0.18.3-1, 0.18.3.1-1), libqt4-scripttools:amd64 (4.8.5+dfsg-2, 4.8.5+dfsg-3), git-core:amd64 (1.8.4~rc2-1, 1.8.4~rc3-1), xserver-xorg-video-radeon:amd64 (6.14.4-8, 7.2.0-1), libqt4-dbg:amd64 (4.8.5+dfsg-2, 4.8.5+dfsg-3), gzip:amd64 (1.6-1, 1.6-2), libwebkitgtk-1.0-common:amd64 (1.8.1-4, 2.0.4-2), libavdevice53:amd64 (0.8.8-1, 9.8-2), hplip-data:amd64 (3.13.4-1, 3.13.8-1), gir1.2-gstreamer-1.0:amd64 (1.0.8-1, 1.0.9-1), libqt4-dev:amd64 (4.8.5+dfsg-2, 4.8.5+dfsg-3), libvdpau1:amd64 (0.6-2, 0.7-1), linux-libc-dev:amd64 (3.10.5-1, 3.10.7-1), libjavascriptcoregtk-1.0-0:amd64 (1.8.1-4, 2.0.4-2+b1), qt4-qmake:amd64 (4.8.5+dfsg-2, 4.8.5+dfsg-3), libstdc++6:amd64 (4.8.1-8, 4.8.1-9), libstdc++6:i386 (4.8.1-8, 4.8.1-9), libqtgui4:amd64 (4.8.5+dfsg-2, 4.8.5+dfsg-3), libqtgui4:i386 (4.8.5+dfsg-2, 4.8.5+dfsg-3), libgtkpod1:amd64 (2.1.3-5, 2.1.3-5+b1), ruby-locale:amd64 (2.0.5-6, 2.0.8-1), libitm1:amd64 (4.8.1-8, 4.8.1-9), gir1.2-webkit-3.0:amd64 (1.8.1-4, 2.0.4-2+b1), hplip-gui:amd64 (3.13.4-1, 3.13.8-1), amarok-doc:amd64 (2.7.1-1, 2.8.0-1), dmidecode:amd64 (2.12-1, 2.12-2), libqt4-declarative:amd64 (4.8.5+dfsg-2, 4.8.5+dfsg-3), libset-intspan-perl:amd64 (1.16-1, 1.19-1), libgpgme11:amd64 (1.4.2-0.1, 1.4.3-0.1), tar:amd64 (1.26+dfsg-6, 1.26+dfsg-8), libqt4-help:amd64 (4.8.5+dfsg-2, 4.8.5+dfsg-3)
Remove: libcogl9:amd64 (1.10.2-7), libcogl-pango0:amd64 (1.10.2-7)
End-Date: 2013-08-20 08:11:13
$ apt-show-versions -u
iceweasel:amd64/experimental *manually* upgradeable from 22.0-1 to 23.0-2
$ infobash -v3
Host/Kernel/OS "MSAK1" running Linux 3.10-7.slh.2-aptosid-amd64 x86_64 [ sidux 2009-02 Αιθήρ - kde-full - (200907141427) ]
CPU Info 4x Intel Core i5-2500K @ 6144 KB cache flags( sse3 ht nx lm vmx ) clocked at [ 2541.000 MHz ]
Videocard Intel 2nd Generation Core Processor Family Integrated Graphics Controller X.Org 1.12.4 [ 1280x1024@60.0hz ]
Network cards Intel 82579V Gigabit
ATHEROS USB2.0 WLAN
Processes 197 | Uptime 26min | Memory 1305.2/7899.4MB | HDD WDC WD3200AAKS-0 Size 320GB (41%used) | Client Shell | Infobash v3.46
|
|
|
| |
|
|
|
 |
|
slh
|
|
|
Post subject: RE: Black screen on boot
Posted: 20.08.2013, 22:17
|
|
Joined: 2010-08-25
Posts: 944
Status: Offline
|
|
| There will be a new kernel coming up in a few hours, which might fix the issue - please test (there is one potential issue, which might explain this behaviour, but I can not reproduce the bug locally). |
|
|
| |
|
|
|
|
|
vinur
|
|
|
Post subject: RE: Black screen on boot
Posted: 21.08.2013, 18:53
|
|
Joined: 2010-09-11
Posts: 83
Location: Lake Oswego
Status: Offline
|
|
Just a quick note that I am experiencing the same wait. its about 2 minutes and then the system seems to load normally at first glance... I have not as yet investigated it much... so actual data is not available but it has been going on for a couple of days.
I will pay attention to the effect next boot time.
here is what I am running this minute:
michael@Eyland0:~$ infobash -v3
Host/Kernel/OS "Eyland0" running Linux 3.10-7.slh.2-aptosid-amd64 x86_64 [ aptosid 2013-01 Ἑσπερίδες - kde-lite - (201305050307) ]
CPU Info 8x AMD FX-8120 Eight-Core 2048 KB cache flags( sse3 ht nx lm svm ) clocked at [ 1400.000 MHz ]
Videocard NVIDIA G86 [GeForce 8500 GT] X.Org 1.12.4 [ 1920x1080@60.0hz ]
Network cards D-Link System Inc DGE-560T PCI Express Gigabit
Processes 180 | Uptime 7:56 | Memory 761.5/7973.8MB | HDD WDC WD6000HLHX-0,ST3500418AS,AS2105 Size 1484GB (2%used) | GLX Renderer Gallium 0.4 on NV86 | GLX Version Yes | Client Shell | Infobash v3.46
michael@Eyland0:~$
nothing seems to be running poorly... just a long hang at populating devices |
|
|
| |
|
|
|
|
|
slh
|
|
|
Post subject: RE: Black screen on boot
Posted: 21.08.2013, 20:30
|
|
Joined: 2010-08-25
Posts: 944
Status: Offline
|
|
| Please, as mentioned yesterday, test "3.10-9.slh.1-aptosid-amd64" (or its 686 variant), I'm very interested if the issue persists. There is a very high probability that it's fixed with the current kernel, so I'm considering 3.10-7.slh.2-aptosid-amd64 (3.10-7.slh.2-aptosid-686 respectively) as "known-broken" and am only interested in issues with other (newer) kernels. |
|
|
| |
|
|
|
|
|
alexk
|
|
|
Post subject:
Posted: 21.08.2013, 21:05
|
|
Joined: 2010-10-01
Posts: 284
Status: Offline
|
|
I still have the same issue with kernel 3.10-9.slh.1-aptosid-amd64 and after another dist-upgrade. When I hit Scroll Lock after the 1-2 minutes of black screen, I see messages like this on the screen (this is as recorded for yesterday in /var/log/daemon.log, I saw the same kind of messages today):
Code:
Aug 20 08:15:36 MSAK1 udevd[501]: timeout: killing '/bin/sh -c 'if [ -f /usr/bin/systemctl ]; then /usr/bin/systemctl --no-block start hplip-printer@001:003.service; else /usr/bin/nohup /usr/bin/hp-config_usb_printer 001:003 ; fi'' [556]
Aug 20 08:15:36 MSAK1 udevd[505]: timeout: killing '/bin/sh -c 'if [ -f /usr/bin/systemctl ]; then /usr/bin/systemctl --no-block start hplip-printer@001:004.service; else /usr/bin/nohup /usr/bin/hp-config_usb_printer 001:004 ; fi'' [557]
Aug 20 08:15:36 MSAK1 udevd[501]: '/bin/sh -c 'if [ -f /usr/bin/systemctl ]; then /usr/bin/systemctl --no-block start hplip-printer@001:003.service; else /usr/bin/nohup /usr/bin/hp-config_usb_printer 001:003 ; fi'' [556] terminated by signal 9 (Killed)
Aug 20 08:15:36 MSAK1 udevd[505]: '/bin/sh -c 'if [ -f /usr/bin/systemctl ]; then /usr/bin/systemctl --no-block start hplip-printer@001:004.service; else /usr/bin/nohup /usr/bin/hp-config_usb_printer 001:004 ; fi'' [557] terminated by signal 9 (Killed)
I don't have /usr/bin/systemctl, but I do have hp-config_usb_printer in the hplip package:
Code:
$ dpkg -S hp-config_usb_printer
hplip: /usr/bin/hp-config_usb_printer
alex@MSAK1:/var/log$ apt-cache policy hplip
hplip:
Installed: 3.13.8-1
Candidate: 3.13.8-1
Version table:
*** 3.13.8-1 0
990 http://ftp.debian.org/debian/ unstable/main amd64 Packages
100 /var/lib/dpkg/status
3.13.4-1+b1 0
500 http://ftp.us.debian.org/debian/ testing/main amd64 Packages
alex@MSAK1:/var/log$ dpkg -S systemctl
dpkg-query: no path found matching pattern *systemctl*
|
|
|
| |
|
|
|
|
|
vinur
|
|
|
Post subject:
Posted: 21.08.2013, 23:11
|
|
Joined: 2010-09-11
Posts: 83
Location: Lake Oswego
Status: Offline
|
|
hello slh,
Did a DU to the new kernel...
michael@Eyland0:~$ infobash -v3
Host/Kernel/OS "Eyland0" running Linux 3.10-9.slh.1-aptosid-amd64 x86_64 [ aptosid 2013-01 Ἑσπερίδες - kde-lite - (201305050307) ]
CPU Info 8x AMD FX-8120 Eight-Core 2048 KB cache flags( sse3 ht nx lm svm ) clocked at [ 1400.000 MHz ]
Videocard NVIDIA G86 [GeForce 8500 GT] X.Org 1.12.4 [ 1920x1080@60.0hz ]
Network cards D-Link System Inc DGE-560T PCI Express Gigabit
Processes 177 | Uptime 1:02 | Memory 730.7/7973.8MB | HDD ST3500418AS,WDC WD6000HLHX-0,AS2105 Size 1420GB (22%used) | GLX Renderer Gallium 0.4 on NV86 | GLX Version Yes | Client Shell | Infobash v3.46
Still hangs for 1 min at /dev to be populated
Then comes up with some code I did not have enough time to see well, at which point it runs the rest of the start up as more or less normally.
Otherwise all is the same as far as I can see running the machine.
Is there some command I can use to get information you can use that may help? |
|
|
| |
|
|
|
|
|
slh
|
|
|
Post subject:
Posted: 21.08.2013, 23:55
|
|
Joined: 2010-08-25
Posts: 944
Status: Offline
|
|
O.k., now it would be interesting to confirm if this is actually a kernel regression or a new bug in hplip (which was updated on saturday).
So if you still have an older kernel installed, please check if that one is affected as well. In order to rule out stale initramfs (without the new hplip udev rules), you'll have to refresh the initramfs for your old kernel as well, so boot into an older (perviously unaffected) kernel and run "update-initramfs -u -k $(uname -r)" as root, which will recreate the initramfs for the running kernel and update the embedded udev rules. I'd also need to know which was the last unaffected kernel version - and if it remains unaffected after refreshing the initramfs.
In case you don't own a HP printer, it might be easier to purge hplip alltogether (apt-get purge hplip hplip-data libhpmud0 printer-driver-hpcups) - and reboot. |
|
|
| |
|
|
|
|
|
vinur
|
|
|
Post subject:
Posted: 22.08.2013, 00:50
|
|
Joined: 2010-09-11
Posts: 83
Location: Lake Oswego
Status: Offline
|
|
Hello slh,
Did some reboots with different older kernels going back to 3.9 and the issue seemed to follow with a change of the microcode failed. (does not seem to track the kernel id so I think the numbers are unrelated 3.904644, 3.831470, ... etc)
however the one consistency is fam15h.bin which is always present in the failed to load information... its been there for a long time so I don't think it is related to the hanging issue, but I don't know enough to judge.
What I am going to do now is start to boot with the oldest extant kernel I have on this drive and see what happens. |
|
|
| |
|
|
|
|
|
vinur
|
|
|
Post subject:
Posted: 22.08.2013, 01:15
|
|
Joined: 2010-09-11
Posts: 83
Location: Lake Oswego
Status: Offline
|
|
Hello slh,
booted to 3.9-0.slh.4 microcode failed 3.456039 and the hang continues for about 1 minute
the fam15h.bin I think is related to an AMD issue and never seemed to amount to much of an problem as it has always been there in passing fast and the machine just boots fast.
I see that the hang is related to something about hp printers as *it is* correcting for some issue relative to that.
By the way the printer is a low end hp laser I got as a trade in and is very junky... but it does continue to work through these issues... just printed your last instructions so I will have them available in what ever mode and drive I am in.
I don't mind purging the printer drivers on this system for a while
I have an older Linux aptosid drive on this computer that runs OK and it contains printer drivers that will run the hp p1006 printer ok. it is a crash backup system and is old but I do use it from time to time.
let you know what I find out soon.
If I need to print I can use that old drive |
|
|
| |
|
|
|
|
|
vinur
|
|
|
Post subject:
Posted: 22.08.2013, 02:23
|
|
Joined: 2010-09-11
Posts: 83
Location: Lake Oswego
Status: Offline
|
|
Hello slh,
As the hang seemed to be independent of which kernel I was using... always a time hang independent of kernel version I did the purge option you gave (apt-get purge hplip hplip-data libhpmud0 printer-driver-hpcups)
when I rebooted the time hang was gone.
Hope this bit of info is useful to you.
For the time being I will use the older (older = un-upgraded system 1.5 years) as connected dual boot aptosid to print from. |
|
|
| |
|
|
|
|
|
alexk
|
|
|
Post subject:
Posted: 23.08.2013, 12:32
|
|
Joined: 2010-10-01
Posts: 284
Status: Offline
|
|
The last kernel that I didn't have the issue with was 3.10-2.slh.2-aptosid-amd64 and I still have the issue with that kernel now, even after running an "update-initramfs -u -k 3.10-2.slh.2-aptosid-amd64" from the 3.10-9.slh.1-aptosid-amd64 kernel and then booting into 3.10-2.slh.2-aptosid-amd64.
The udev rule that's generating the timeout on boot is in /lib/udev/rules.d/56-hpmud.rules from hplip:
Code:
cat /lib/udev/rules.d/56-hpmud.rules
# HPLIP udev rules file. Notify console user if plugin support is required for this device.
ACTION!="add", GOTO="hpmud_rules_end"
SUBSYSTEM=="ppdev", OWNER="root", GROUP="lp", MODE="0660"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", GOTO="hpmud_usb_rules"
LABEL="hpmud_usb_rules"
# ENV{ID_HPLIP}="1" is for Ubuntu udev-acl
ATTR{idVendor}=="03f0", ATTR{idProduct}=="????", OWNER="root", GROUP="lp", MODE="0660", ENV{sane_hpaio}="yes", ENV{libsane_matched}="yes", ENV{hp_test}="yes", ENV{ID_HPLIP}="1"
# This rule will add the printer and install plugin
ENV{hp_test}=="yes", PROGRAM="/bin/sh -c 'logger -p user.info loading HP Device $env{BUSNUM} $env{DEVNUM}'", RUN+="/bin/sh -c 'if [ -f /usr/bin/systemctl ]; then /usr/bin/systemctl --no-block start hplip-printer@$env{BUSNUM}:$env{DEVNUM}.service; else /usr/bin/nohup /usr/bin/hp-config_usb_printer $env{BUSNUM}:$env{DEVNUM} ; fi'"
# If sane-bankends is installed add hpaio backend support to dll.conf if needed.
ENV{sane_hpaio}=="yes", RUN+="/bin/sh -c 'grep -q ^#hpaio /etc/sane.d/dll.conf;if [ $$? -eq 0 ];then sed -i -e s/^#hpaio/hpaio/ /etc/sane.d/dll.conf;else grep -q ^hpaio /etc/sane.d/dll.conf;if [ $$? -ne 0 ];then echo hpaio >>/etc/sane.d/dll.conf;fi;fi'"
# The following rule will disable USB autosuspend for the device
ENV{libsane_matched}=="yes", RUN+="/bin/sh -c 'test -e /sys/$env{DEVPATH}/power/level && echo on > /sys/$env{DEVPATH}/power/level'"
LABEL="hpmud_rules_end"
|
|
|
| |
|
|
|
|
|
alexk
|
|
|
Post subject:
Posted: 25.08.2013, 20:47
|
|
Joined: 2010-10-01
Posts: 284
Status: Offline
|
|
This issue disappears after downgrading hplip to the testing version 3.13.4-1+b1.
Code:
tail /var/log/apt/history.log
Start-Date: 2013-08-23 19:34:27
Commandline: apt-get install hplip/testing libhpmud0/testing libsane-hpaio/testing hplip-data/testing printer-driver-hpcups/testing hpijs/testing hplip-gui/testing printer-driver-hpijs/testing
Downgrade: hplip:amd64 (3.13.8-1, 3.13.4-1+b1), libsane-hpaio:amd64 (3.13.8-1, 3.13.4-1+b1), libhpmud0:amd64 (3.13.8-1, 3.13.4-1+b1), printer-driver-hpijs:amd64 (3.13.8-1, 3.13.4-1+b1), printer-driver-hpcups:amd64 (3.13.8-1, 3.13.4-1+b1), hplip-data:amd64 (3.13.8-1, 3.13.4-1), hplip-gui:amd64 (3.13.8-1, 3.13.4-1)
End-Date: 2013-08-23 19:35:30
|
|
|
| |
|
|
|
|
|
slh
|
|
|
Post subject:
Posted: 25.08.2013, 21:02
|
|
Joined: 2010-08-25
Posts: 944
Status: Offline
|
|
| Then I'd suggest to report a bug against the hplip package, unfortunately I don't have access to any printers using it. |
|
|
| |
|
|
|
|
|
alexk
|
|
|
Post subject:
Posted: 25.10.2013, 03:13
|
|
Joined: 2010-10-01
Posts: 284
Status: Offline
|
|
| I still have this issue with hplip version 3.13.9-2, except that I get the black screen for only 30 seconds after "Populating devices ...", then the boot continues. |
|
|
| |
|
|
|
|
|
slh
|
|
|
Post subject:
Posted: 25.10.2013, 03:48
|
|
Joined: 2010-08-25
Posts: 944
Status: Offline
|
|
| Please check dmesg for gaps between the timestamps. A short black screen is normal for that stage, caused by the graphics mode switch - this typically takes 2-3 seconds (and is only cosmetic, the system actually continues booting in parallel). If your screen is slow with adjusting to resolution changes, that modeswitch might easily take up to around 10-12s, so dmesg is best at telling the truth. |
|
|
| |
|
|
|
|
|
|
|
