You are not logged in.
when I first experienced this problem, I thought there were some bad configuration because I wasn't upgrading the machine for weeks.
I've been temporarily used kernel from installation CD I made earlier(3.10.10-1).
having some time today, I experimented a little.
3.10.3-1 - working(the last working cached version of pacman)
3.10.10-1 - working(the last 3.10.* version from mainline arch kernel)
3.10.29-1 - working(the last LTS version)
3.11-1 - not working(the first 3.11* version from mainline arch kernel)
3.12.9-1 - not working(the last mainline arch kernel by the time)
the symptom is that the kernel hangs on "[ OK ] Started Load/Save Random Seed" message while booting.
(where in normal booting resolution of the display gets changed)
Ctrl + Alt + F2 doesn't work, Ctrl + Alt + Del doesn't work.
when I use --quiet kernel parameter, the last line shown is "uhci_hcd 0000:00:1d.2:init 0000:00:1d.2 fail, -16"
(lspci says 00:1d.2 is a usb port for me.)
how could I fix this problem?
EDIT : Oops, no hardware info at all
Sony VAIO VGN-FJ65L(2006)
$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 03)
00:1d.0 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03)
00:1d.1 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03)
00:1d.2 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03)
00:1d.3 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03)
00:1d.7 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3)
00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 03)
00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 03)
06:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
06:09.0 CardBus bridge: Texas Instruments PCI7420 CardBus Controller
06:09.2 FireWire (IEEE 1394): Texas Instruments PCI7x20 1394a-2000 OHCI Two-Port PHY/Link-Layer Controller
06:09.3 Mass storage controller: Texas Instruments PCI7420/7620 SD/MS-Pro Controller
06:0a.0 Ethernet controller: Qualcomm Atheros AR5212/AR5213 Wireless Network Adapter (rev 01)Last edited by freaxtux (2014-02-12 06:28:56)
Offline
I don't know if it will help you, but here are the differences concerning USB in the config files to build the kernel, between linux-lts 3.10.29 (to the left) and linux-3.11.1 (to the right):
> CONFIG_RTLWIFI_USB=m
> CONFIG_VIDEO_USBTV=m
> CONFIG_SND_USB_HIFACE=m
CONFIG_USB_ARCH_HAS_OHCI=y <
CONFIG_USB_ARCH_HAS_EHCI=y <
CONFIG_USB_ARCH_HAS_XHCI=y <
> CONFIG_USB_FUSBH200_HCD=m
> CONFIG_USB_OHCI_HCD_PCI=m
> # CONFIG_USB_MUSB_HOST is not set
> # CONFIG_USB_MUSB_GADGET is not set
> CONFIG_USB_MUSB_DUAL_ROLE=y
> CONFIG_USB_CHIPIDEA_UDC=y
> # CONFIG_USB_CHIPIDEA_DEBUG is not set
> CONFIG_USB_SERIAL_FLASHLOADER=m
> CONFIG_USB_SERIAL_SUUNTO=m
> CONFIG_USB_FUSB300=m
> CONFIG_USB_FOTG210_UDC=m
CONFIG_USB_GADGET_MUSB_HDRC=m <
> CONFIG_USB_U_ETHER=m
> CONFIG_USB_U_RNDIS=m
> CONFIG_USB_F_NCM=m
> CONFIG_USB_F_ECM=m
> CONFIG_USB_F_SUBSET=m
> CONFIG_USB_F_RNDIS=m
> # CONFIG_USB_CONFIGFS is not set
> CONFIG_USB_BTMTK=mMaybe a change there is the cause of the problem; I don't know..
Offline
I just tried mint. Mint 16(kernel version 3.11) fails booting, but mint 13(LTS, kernel version 3.2) works. Maybe it's not fault of arch?
Offline
Compare the entire dmesg output from linux-lts 3.10.29 and linux 3.11.1
And waiting for a better solution, you can stick to the linux-lts 3.10 branch which should be maintained until Sep. 2015.
Last edited by berbae (2014-02-13 11:20:53)
Offline
Compare the entire dmesg output from linux-lts 3.10.29 and linux 3.11.1
And waiting for a better solution, you can stick to the linux-lts 3.10 branch which should be maintained until Sep. 2015.
+1 if you cannot figure this out.
Since your problem is true across distros and does seem to be kernel related, I recommend that you seek help on lkml but you will want to shrink down your problem to a few sentences and provide both dmegs outputs to the post to keep things short. With any luck, someone will reply and help.
Offline
Thanks for your advices.
I can't use dmesg since the hanging occurs before login prompt. Is it enough if i post the boot messageswith --quiet flag?
Offline
Use the systemd journal instead of dmesg to see kernel messages from previous and current boots:
journalctl -b -1 (previous boot messages)
journalctl -b (current boot messages)
Offline
systemd leaves nothing on the failed boot attemts.
it seems that the error occur too early.
Last edited by freaxtux (2014-02-14 03:59:08)
Offline
On my system I have:
févr. 14 10:20:54 arch64 systemd-journal[111]: Journal started
...
févr. 14 10:20:54 arch64 systemd[1]: Started Load/Save Random Seed.
...
févr. 14 10:20:59 arch64 systemd-journal[111]: Permanent journal is using 15.5M (max 16.0M, leaving 2.9G of free 14.0G, current limit 1
févr. 14 10:20:58 arch64 systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.The journal seems started before your last message on the screen (without the --quiet option).
But it takes ~4-5s to flush the volatile journal to the persistent one on the disk.
What do you mean 'systemd leaves nothing'? What is the exact output of:
# journalctl -b -1
after a failed boot followed with a normal boot with another kernel?
You can also redirect the journal messages to the console by adding:
systemd.journald.forward_to_console=yes
to the kernel command line from grub or syslinux boot loader.
And the not yet flushed messages should stay on the screen.
These are just suggestions if you want to contribute to the search for a fix, but you can also just use the linux-lts kernel and ask for help as Graysky posted earlier.
Offline
oh, it was journalctl, not systemd. that was mistake. Journalctl is completely unaware of the failed boot, and shows the log of second last boot.
Anyway, thanks for the cmdline parameter. I'll try that soon.
Offline