[Bug 596329] New: boot delayed on PREEMPT RT Kernel (udevadm keeps working and working)
http://bugzilla.novell.com/show_bug.cgi?id=596329 http://bugzilla.novell.com/show_bug.cgi?id=596329#c0 Summary: boot delayed on PREEMPT RT Kernel (udevadm keeps working and working) Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: PC OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: fi@igh-essen.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.1.6) Gecko/20091201 SUSE/3.5.6-1.1.1 Firefox/3.5.6 we installed OpenSuSE 11.2 on different, but recent PC hardware. Booting the default kernel ( 2.6.31.12-0.2-desktop ) works fine. But booting the PREEMPT RT Kernel (2.6.31-rc8-rt9-3-rt) reproducibly gives remarkable delays (about two minutes) compared to the default kernel mentionaed above. During delay udevadm sends the following info to console: ... Creating device nodes with udevd udevadm settle - timeout of 30 seconds reached, the event queue contains: /sys/devices/pci0000... ... (up to 10 lines like the one before) ... udevadm[551]: error sending message: Connection refused udevadm settle - timeout of 30 seconds reached, the event queue contains: /sys/devices/pci0000... ... (up to 10 lines like the one before) ... udevadm[552]: error sending message: Connection refused udevadm settle - timeout of 30 seconds reached, the event queue contains: /sys/devices/pci0000... ... (up to 10 lines like the one before) ... resume device not found (ignoring) udevadm[551]: error sending message: Connection refused udevadm settle - timeout of 30 seconds reached, the event queue contains: /sys/devices/pci0000... ... (up to 10 lines like the one before) ... Waiting for devive /dev/sda1 to appear: ok. (please note the double space after "resume device". Is there something missing?) Then the systems do boot and work as usual. Reproducible: Always Steps to Reproduce: 1. install default OpenSuSE 11.2 2. install default PREMPT RT Kernel 3. boot Actual Results: delay and error messages during this delay. Expected Results: boot duration should not heavily depend on the kernel (PREMPT RT Kernel or Desktop Kernel) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=596329 http://bugzilla.novell.com/show_bug.cgi?id=596329#c1 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |jeffm@novell.com, | |kasievers@novell.com InfoProvider| |fi@igh-essen.com --- Comment #1 from Jeff Mahoney <jeffm@novell.com> 2010-04-20 18:36:32 UTC --- This looks like udev isn't running from the initrd on your -rt kernel. Can you double check that it's started? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=596329 http://bugzilla.novell.com/show_bug.cgi?id=596329#c2 Torsten Finke <fi@igh-essen.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |fi@igh-essen.com InfoProvider|fi@igh-essen.com | --- Comment #2 from Torsten Finke <fi@igh-essen.com> 2010-04-22 15:50:32 UTC --- I've just checked this (twice). The first message from my report above ("Creating device nodes with udev") appearing immediately after "doing fast boot" comes from ./boot/04-udev.sh contained in the initrd. Also the 30-seconds timeout is defined only in the initrd. So I'm pretty sure, that udev is run from initrd. Also there was nothing special in installing the PREMPT RT Kernel. I did that by YaST (or Zypper, don't remember exactly). The initrd has been built during the Kernel installation. I did no customization nor manual configuratiuon. Here are some details that may be interesting: $ cat mkinitrd.config -k /boot/vmlinuz-2.6.31-rc8-rt9-3-rt -i /boot/initrd-2.6.31-rc8-rt9-3-rt $ grep -v '^#' /etc/sysconfig/kernel INITRD_MODULES="thermal ahci ata_piix ata_generic piix ide_pci_generic processor fan" DOMU_INITRD_MODULES="xennet xenblk" MODULES_LOADED_ON_BOOT="" ACPI_DSDT="" SKIP_RUNNING_KERNEL="" Regards Torsten -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=596329 http://bugzilla.novell.com/show_bug.cgi?id=596329#c3 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |fi@igh-essen.com --- Comment #3 from Jeff Mahoney <jeffm@novell.com> 2010-04-22 20:10:47 UTC --- Well the thing is that "error sending message: Connection refused" gets issued when there is nothing listening on the other end of the socket. udevd is what is supposed to be listening there. udevd --daeon is run right before the udevadm trigger and then the wait for events. The problem is that unless it's in debug mode, then it doesn't dump anything on stderr. Can you boot with "linuxrc=trace" and report what you see? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=596329 http://bugzilla.novell.com/show_bug.cgi?id=596329#c4 --- Comment #4 from Torsten Finke <fi@igh-essen.com> 2010-04-23 13:19:10 UTC --- I tried that: - fetched console messages as described in http://en.opensuse.org/Bugs:mkinitrd [ 0.838983] ***************************************************************************** [ 0.936915] * * [ 1.034892] * REMINDER, the following debugging option is turned on in your config: * [ 1.132868] * * [ 1.230844] * CONFIG_FTRACE * [ 1.328822] * * [ 1.426798] * it may increase runtime overhead and latencies. * [ 1.524775] * * [ 1.622753] ***************************************************************************** [ 142.269801] powernow: This module only works with AMD K7 CPUs [ 174.466694] BIOS EDD facility v0.16 2004-Jun-25, 1 devices found - fetched dmesg [ 2.091279] ata5: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xf800 irq 14 [ 2.091284] ata6: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xf808 irq 15 [ 2.091447] ata6: port disabled. ignoring. [ 2.242268] ata5.01: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80) [ 7.393250] ata5.01: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80) [ 12.544225] ata5.01: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80) [ 17.698330] ata5.00: CFA: SanDisk SDCFH-008G, HDX 5.00, max UDMA/66 [ 17.698335] ata5.00: 15649200 sectors, multi 0: LBA [ 17.704224] ata5.00: configured for UDMA/66 [ 17.715182] scsi 4:0:0:0: Direct-Access ATA SanDisk SDCFH-00 HDX PQ: 0 ANSI: 5 [ 17.741859] Uniform Multi-Platform E-IDE driver [ 17.754781] processor LNXCPU:00: registered as cooling_device0 [ 17.754854] processor LNXCPU:01: registered as cooling_device1 [ 17.758174] fan PNP0C0B:00: registered as cooling_device2 [ 17.758184] ACPI: Fan [FAN] (on) [ 17.771748] udev: starting version 146 [ 17.922543] usbcore: registered new interface driver usbfs [ 17.922580] usbcore: registered new interface driver hub [ 17.922635] usbcore: registered new device driver usb [ 17.926019] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 17.927644] ACPI: PCI Interrupt Link [LNK1] enabled at IRQ 9 [ 17.927649] PCI: setting IRQ 9 as level-triggered [ 17.927656] ehci_hcd 0000:00:1d.7: PCI INT A -> Link[LNK1] -> GSI 9 (level, low) -> IRQ 9 [ 17.927687] ehci_hcd 0000:00:1d.7: setting latency timer to 64 [ 17.927694] ehci_hcd 0000:00:1d.7: EHCI Host Controller [ 17.927742] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1 [ 17.934095] ehci_hcd 0000:00:1d.7: debug port 1 [ 17.934105] ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported [ 17.934165] ehci_hcd 0000:00:1d.7: irq 9, io mem 0xfdfff000 [ 17.940633] sd 4:0:0:0: [sda] 15649200 512-byte logical blocks: (8.01 GB/7.46 GiB) [ 17.940723] sd 4:0:0:0: [sda] Write Protect is off [ 17.940727] sd 4:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 17.940770] sd 4:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 17.941194] sda: sda1 [ 17.942382] sd 4:0:0:0: [sda] Attached SCSI removable disk [ 17.944017] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00 [ 17.944114] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 17.944118] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 17.944121] usb usb1: Product: EHCI Host Controller [ 17.944124] usb usb1: Manufacturer: Linux 2.6.31-rc8-rt9-3-rt ehci_hcd [ 17.944127] usb usb1: SerialNumber: 0000:00:1d.7 [ 17.944273] usb usb1: configuration #1 chosen from 1 choice [ 17.944323] hub 1-0:1.0: USB hub found [ 17.944336] hub 1-0:1.0: 8 ports detected ... lots of messages concerning USB [ 18.447041] usb 3-2: new low speed USB device using uhci_hcd and address 2 [ 18.620065] usb 3-2: New USB device found, idVendor=046d, idProduct=c313 [ 18.620070] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 18.620074] usb 3-2: Product: USB Multimedia Keyboard [ 18.620077] usb 3-2: Manufacturer: LITEON Technology [ 18.620219] usb 3-2: configuration #1 chosen from 1 choice [ 18.688203] usbcore: registered new interface driver hiddev [ 18.703376] input: LITEON Technology USB Multimedia Keyboard as /devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/input/input0 [ 18.703500] generic-usb 0003:046D:C313.0001: input,hidraw0: USB HID v1.10 Keyboard [LITEON Technology USB Multimedia Keyboard] on usb-0000:00:1d.1-2/input0 [ 18.722130] input: LITEON Technology USB Multimedia Keyboard as /devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.1/input/input1 [ 18.722237] generic-usb 0003:046D:C313.0002: input,hidraw1: USB HID v1.10 Device [LITEON Technology USB Multimedia Keyboard] on usb-0000:00:1d.1-2/input1 [ 18.722263] usbcore: registered new interface driver usbhid [ 18.722268] usbhid: v2.6:USB HID core driver [ 138.369071] kjournald starting. Commit interval 15 seconds [ 138.371924] EXT3 FS on sda1, internal journal [ 138.371931] EXT3-fs: mounted filesystem with ordered data mode. [ 138.998812] udev: starting version 146 [ 139.109447] Linux agpgart interface v0.103 [ 139.152806] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 [ 139.152875] ACPI: Power Button [PWRF] [ 139.152967] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input3 [ 139.153008] ACPI: Power Button [PWRB] [ 139.161997] sd 4:0:0:0: Attached scsi generic sg0 type 0 [ 139.172967] intel_rng: FWH not detected - fetched /var/log/boot.msg (looking similar to the output from dmesg) but unfortunately the obviously most interesting messages I could not manage to grab. There are lots of messages from "udevd-work" flying over the screen. Would there be any trick to grab them? Regards Torsten -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=596329 http://bugzilla.novell.com/show_bug.cgi?id=596329#c5 --- Comment #5 from Jeff Mahoney <jeffm@novell.com> 2010-04-23 13:30:01 UTC --- The easiest way, if you have another system, is to use a serial console to capture the output. You boot with "console=ttyS0,115200 console=tty0" on the command line and use the serial terminal program of your choice to capture it. Personally, I just use screen(1) with logging enabled: screen -L /dev/ttyS0 It will log everything into screenlog.<some number> -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=596329 http://bugzilla.novell.com/show_bug.cgi?id=596329#c6 --- Comment #6 from Torsten Finke <fi@igh-essen.com> 2010-04-23 14:12:17 UTC --- That was exactly what I did, but but nothing was grabbed between doing fast boot (and) [ 142.269801] powernow: This module only works with AMD K7 CPUs (I've tried that with different baud rates and with different other systems) Regards Torsten -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=596329 https://bugzilla.novell.com/show_bug.cgi?id=596329#c7 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|fi@igh-essen.com | Resolution| |WONTFIX --- Comment #7 from Jeff Mahoney <jeffm@novell.com> 2010-09-03 17:40:31 UTC --- openSUSE 11.2 is in security-maintenance mode. Please reopen if this issue still occurs with 11.3 or Factory. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com