Hi,
Today when I have tried to update the kernel pacman got stack:
Updating module dependencies. Please wait ... Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image from preset: 'default' -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img ==> Starting build: 3.0-ARCH -> Parsing hook: [base] -> Parsing hook: [udev] -> Parsing hook: [autodetect]
After this point nothing happen. In everything.log I get infinite amount of the following message:
"
Aug 19 15:18:03 localhost kernel: [608984.681025] xhci_hcd 0000:02:00.0: WARN: Stalled endpoint
"
Does anybody know what is going on? Hector
Aug 19 15:18:03 localhost kernel: [608984.681025] xhci_hcd 0000:02:00.0: WARN: Stalled endpoint
Hi, Do you have a USB 3.0 controller/disk?
Am 19.08.2011 14:19, schrieb Hector Martinez-Seara:
Hi,
Today when I have tried to update the kernel pacman got stack:
Updating module dependencies. Please wait ... Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image from preset: 'default' -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img ==> Starting build: 3.0-ARCH -> Parsing hook: [base] -> Parsing hook: [udev] -> Parsing hook: [autodetect]
After this point nothing happen. In everything.log I get infinite amount of the following message:
"
Aug 19 15:18:03 localhost kernel: [608984.681025] xhci_hcd 0000:02:00.0: WARN: Stalled endpoint
"
Does anybody know what is going on? Hector
Can you run 'ps fx' as root while pacman hangs here and post the output?
Hi, I'm sorry for the late reply. After rebooting my computer was not functioning any longer :). Yes, I have a USB 3.0 controller and an external disk attached to it in a x86_64 system. Once I unplugged the disk everything worked as should be and I manage to install the new kernel. I have notice that trying to downgrade to previous linux version lead (3.0.2) lead me to the same problem despite I could install it without any problem when it was pushed. I haven't tried to plug it back and I won't be able to until monday. Any body knows what happened? Hector PD: Thomas Bächler: I will try to reproduce the problem on Monday and I will post you the output of 'ps fx'.
On 19 August 2011 15:38, Thomas Bächler thomas@archlinux.org wrote:
Am 19.08.2011 14:19, schrieb Hector Martinez-Seara:
Hi,
Today when I have tried to update the kernel pacman got stack:
Updating module dependencies. Please wait ... Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image from preset: 'default' -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img ==> Starting build: 3.0-ARCH -> Parsing hook: [base] -> Parsing hook: [udev] -> Parsing hook: [autodetect]
After this point nothing happen. In everything.log I get infinite amount of the following message:
"
Aug 19 15:18:03 localhost kernel: [608984.681025] xhci_hcd 0000:02:00.0: WARN: Stalled endpoint
"
Does anybody know what is going on? Hector
Can you run 'ps fx' as root while pacman hangs here and post the output?
On Sat, Aug 20, 2011 at 10:23 AM, Hector Martinez-Seara hseara@gmail.com wrote:
Any body knows what happened?
Uhm. Tried searching for "0000:02:00.0: WARN: Stalled endpoint" on Google, and I found a considerable amount of complains about Linux (2.6.38-39, 3) and USB 3.0 controllers. I think that's an upstream bug and we should report this issue.
Am 20.08.2011 10:23, schrieb Hector Martinez-Seara:
Hi, I'm sorry for the late reply. After rebooting my computer was not functioning any longer :).
Of course it wasn't.
Yes, I have a USB 3.0 controller and an external disk attached to it in a x86_64 system. Once I unplugged the disk everything worked as should be and I manage to install the new kernel. I have notice that trying to downgrade to previous linux version lead (3.0.2) lead me to the same problem despite I could install it without any problem when it was pushed.
It's not about the version you install, the problem is the version you are running while you install.
I haven't tried to plug it back and I won't be able to until monday. Any body knows what happened?
Lots of guessing here: In the autodetect stage, mkinitcpio autodetects hard disk controllers, file systems and raid superblocks. The only place where it actually accesses any hard drive is the RAID autodetection. It probably hung while accessing the USB3 drive in that stage.
I guess this is a kernel bug that could be triggered by accessing the USB3 drive any time (some RAID versions store their superblock at the end of the partition, so maybe accessing the end of your drive is a problem). You can probably work around the update problem by uninstalling mdadm, in case you do not use RAID.
arch-general@lists.archlinux.org