You are not logged in.
With the last linux kernel in arch repositories (4.10.1-1) my system hang at boot at the message "Loading initial ramdisk"; if I use the lts kernel, the system boots normally. I suspect I've some issue with the keyboard: when I shutdown the system, I've to press CTRL button to "unlock" the shutdown, that hangs at the message "Reached target shutdown". Any ideas?
Offline
remove "quiet" from the kernel parameters and see whether you get more information on where it hangs.
Offline
If I remove the quiet option, the linux kernel still don't boot and I don't receive any message: the system is stuck on "Loading initial ramdisk".
The lts kernel without the quiet option hangs at the first udev message after "loading initial ramdisk", if I unplug the keyboard, the system boots normally.
Offline
Well, bootin wasn't in the cards anyway ;-)
Do you have a replacement keyboard t o try?
What if you plug it into another USB slot (try usb 2 ./. 3 slots)
Offline
Well, bootin wasn't in the cards anyway ;-)
Do you have a replacement keyboard t o try?
What if you plug it into another USB slot (try usb 2 ./. 3 slots)
This problem occurs with two different keyboards, a logitech wireless one and a corsair wired one. If I try another usb port the problem is still there.
Offline
grep HOOKS /etc/mkinitcpio.conf
Can you boot the fallback image?
Offline
giacomo@ironman(20:05 Wed Mar 15)
~ 63 files, 278Mb
→ grep HOOKS /etc/mkinitcpio.conf
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# HOOKS="base"
# HOOKS="base udev autodetect block filesystems"
# HOOKS="base udev block filesystems"
# HOOKS="base udev block mdadm encrypt filesystems"
# HOOKS="base udev block lvm2 filesystems"
HOOKS="base udev autodetect modconf block filesystems keyboard fsck"
None, the fallback image doesn't boot.
Offline
Unspectacular.
Pass "loglevel=7" (more debug out) and "usbcore.old_scheme_first=1" (voodoo) - and then there's possibly iommu, try "iommu=soft" or "iommu=off"
Afterwards i'm running out of ideas...
Your "/proc/cmdline" is otherwise free of "exotic" parameters?
Offline
cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-linux-lts root=UUID=e65c17b1-409d-423e-b3b2-fde9dd6b85aa rw
All the parameters you suggest (loglevel=7, usbcore.old_scheme_first=1 and iommu=soft have to be passed via the grub options after pressing the "e" button on the grub entry?
Offline
With the last linux kernel in arch repositories (4.10.1-1) my system hang at boot at the message "Loading initial ramdisk"; Any ideas?
had same thing happen a couple kernel updates back (from 4.8 to 4.9 i think it was). booted up with an archiso media, chrooted in and pacman reinstalled filesystem and that solved it. I'm sure i found that solution in another thread, others had mixed results.
∞ hard times make the strong, the strong make good times, good times make the weak, the weak make hard times ∞
Offline
The cmdline is unsuspicious.
All the parameters you suggest (loglevel=7, usbcore.old_scheme_first=1 and iommu=soft have to be passed via the grub options after pressing the "e" button on the grub entry?
Yes.
@WFV, was it also related to a keyboard being connected?
Offline
@WFV, was it also related to a keyboard being connected?
No i didn't notice any problem with keyboard at shutdown, only the hang at start, most likely unrelated, apologies.
∞ hard times make the strong, the strong make good times, good times make the weak, the weak make hard times ∞
Offline
With the file /etc/default/grub set as
GRUB_CMDLINE_LINUX_DEFAULT="loglevel=7 usbcore.old_scheme_first=1 iommu=off"
the system doesn't boot.
I've noticed that also when I was booting the archlinux live from an usb disk to revert the /etc/default/grub changes, the boot process hangs and I've to "unlock" it via pressing the Ctrl key...
I'm out of any ideas... Maybe there's something wrong with the BIOS?
Offline
Don't edit /etc/default/grub to test kernel parameters, just [e]dit the boot commands.
The total failure likely stems from the iommu parameter, so you could try w/o - notably to hopefully get more debug out through the increased loglevel.
Offline
With loglevel=7 and usbcore...=1 the system, after a first hang, boot after a mine press of the CTRL button of the kayboard. Where can I find the detailed log produced from this boot?
Offline
This should print much more stuff into the console and can afterwards be inspected by "dmesg | less" ("less" because you care mostly about the beginning of the kernel messages)
Also try iommu=soft (if you haven't already)
Offline
I suspect some strange behaviour of an internal usb hub (an hub of my computer case); this is a portion of the log, as you can see the computer hangs for some seconds: the boot process restart when I press CRTL button of my keyboard (or when I unplug and then replug the keyboard).
1.663011] hub 5-0:1.0: USB hub found
[ 1.666533] hub 5-0:1.0: 3 ports detected
[ 1.670160] ohci-pci 0000:00:13.1: OHCI PCI host controller
[ 1.673594] ohci-pci 0000:00:13.1: new USB bus registered, assigned bus number 6
[ 1.677091] ohci-pci 0000:00:13.1: irq 18, io mem 0xfe02a000
[ 1.739667] hub 6-0:1.0: USB hub found
[ 1.743115] hub 6-0:1.0: 3 ports detected
[ 1.746679] ohci-pci 0000:00:14.5: OHCI PCI host controller
[ 1.750074] ohci-pci 0000:00:14.5: new USB bus registered, assigned bus number 7
[ 1.753533] ohci-pci 0000:00:14.5: irq 18, io mem 0xfe028000
[ 1.816316] hub 7-0:1.0: USB hub found
[ 1.819739] hub 7-0:1.0: 2 ports detected
[ 31.231104] ata11: SATA link down (SStatus 0 SControl 300)
Offline
[ 31.231104] ata11: SATA link down (SStatus 0 SControl 300)
I'd rather worry about this line ...
dmesg | grep -E '[P|S]ATA'
cat /proc/scsi/scsi
Offline
The system is still booting only if I unplug and then replug the usb keyboard... Here the report of the two commands you told to me:
giacomo@ironman(18:46 Mon Mar 27)
~ 65 files, 278Mb
→ dmesg | grep -E '[P|S]ATA'
[ 1.319929] ata1: PATA max UDMA/100 cmd 0xdf00 ctl 0xde00 bmdma 0xdb00 irq 19
[ 1.319930] ata2: PATA max UDMA/100 cmd 0xdd00 ctl 0xdc00 bmdma 0xdb08 irq 19
[ 1.349298] ahci 0000:00:11.0: AHCI 0001.0100 32 slots 6 ports 3 Gbps 0x3f impl SATA mode
[ 1.350815] ata3: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f100 irq 22
[ 1.350817] ata4: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f180 irq 22
[ 1.350819] ata5: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f200 irq 22
[ 1.350821] ata6: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f280 irq 22
[ 1.350823] ata7: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f300 irq 22
[ 1.350824] ata8: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f380 irq 22
[ 1.351907] ata9: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xfa00 irq 14
[ 1.351908] ata10: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xfa08 irq 15
[ 1.361578] ahci 0000:04:00.0: AHCI 0001.0000 32 slots 2 ports 3 Gbps 0x3 impl SATA mode
[ 1.362040] ata11: SATA max UDMA/133 abar m8192@0xfdcfe000 port 0xfdcfe100 irq 18
[ 1.362041] ata12: SATA max UDMA/133 abar m8192@0xfdcfe000 port 0xfdcfe180 irq 18
[ 6.108903] ata11: SATA link down (SStatus 0 SControl 300)
[ 6.108976] ata12: SATA link down (SStatus 0 SControl 300)
[ 6.110345] ata8: SATA link down (SStatus 0 SControl 300)
[ 6.265564] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 6.265590] ata7: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 6.265617] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 6.268553] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 6.268581] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
giacomo@ironman(18:46 Mon Mar 27)
~ 65 files, 278Mb
→ cat /proc/scsi/scsi
Attached devices:
Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: ATA Model: Samsung SSD 840 Rev: DB6Q
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi3 Channel: 00 Id: 00 Lun: 00
Vendor: ATA Model: WDC WD3200AAKS-0 Rev: 1D05
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi4 Channel: 00 Id: 00 Lun: 00
Vendor: ATA Model: WDC WD20EARX-008 Rev: AB51
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi5 Channel: 00 Id: 00 Lun: 00
Vendor: ATA Model: ST3500418AS Rev: CC38
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi6 Channel: 00 Id: 00 Lun: 00
Vendor: HL-DT-ST Model: DVDRAM GH22NS50 Rev: TN02
Type: CD-ROM ANSI SCSI revision: 05
Last edited by giacombum (2017-03-27 16:49:28)
Offline
The next thing is always the "ata11: SATA link down (SStatus 0 SControl 300)" message?
What if you pass "libata.ata_probe_timeout=2" as kernel parameter?
Can you disable the esata ports in BIOS/UEFI?
Offline
I've noticed this very strange thing: the system boots only if I pass the loglevel=7 option!
The operating system starts to load all but at a certain point, the light of the keyboard (I've a retroilluminated one) turns off and the system hangs: at this point I unplug, then replug the keyboard, the light turns on, I press the CTRL button and the boot resumes.
Now the log shows that the system hangs at this point:
[ 2.270119] input: Cooler Master Technology Inc. MasterKeys Lite L Combo Mouse as /devices/pci0000:00/0000:00:12.0/usb3/3-1/3-1:1.0/0003:2516:0044.0001/input/input2
[ 2.292622] ata5.00: ATA-8: WDC WD20EARX-008FB0, 51.0AB51, max UDMA/133
[ 2.296845] ata5.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[ 2.304065] ata5.00: configured for UDMA/133
[ 2.308504] scsi 4:0:0:0: Direct-Access ATA WDC WD20EARX-008 AB51 PQ: 0 ANSI: 5
[ 2.332050] hid-generic 0003:2516:0044.0001: input,hidraw0: USB HID v1.10 Keyboard [Cooler Master Technology Inc. MasterKeys Lite L Combo Mouse] on usb-0000:00:12.0-1/input0
[ 2.341512] input: Cooler Master Technology Inc. MasterKeys Lite L Combo Mouse as /devices/pci0000:00/0000:00:12.0/usb3/3-1/3-1:1.1/0003:2516:0044.0002/input/input3
[ 2.352306] scsi 5:0:0:0: Direct-Access ATA ST3500418AS CC38 PQ: 0 ANSI: 5
[ 12.087944] floppy0: no floppy controllers found
[ 12.088078] hid-generic 0003:2516:0044.0002: input,hiddev0,hidraw1: USB HID v1.10 Mouse [Cooler Master Technology
So is there aproblem with SCSI?
Offline
Looks like your Coolermaster device is detected as both mouse and keyboard .
Try booting without the mouse plugged in.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
No, it doesn't work. And after upgrading to the latest kernel available in the official arch repo, the system doesn't boot anymore also with the keyboard plug-unplug trick: I'm writing from Windows...
I suspect the strange behaviour of SCSI also because when I switch off the pc, the shutdown process hangs at some messages regarding SCSI...
Maybe I've some wrong setting with SCSI, SATA and USB in the BIOS: there are some options for SATA controllers...
Offline
You can install (and boot) the linux-lts kernel in addition; does "latest kernel available in the official arch repo" mean you installed the kernel from testing (w/o really adding the testing repo...)?
How and where does the boot fail?
Offline
You're right, I'm sorry, I haven't explained very well: I've installed the latest kernel available in the core repository, not testing. And unfortunately I've already installed the Linux-Lts kernel, but the system won't boot also with this kernel. The system hangs at the same point: loading initial ramdisk, after I'll try with the loglevel=7 option.
Offline