On 08/14/2010 04:46 PM, Tobias Powalowski wrote:
Latest kernel is in testing,
please signoff for both arches.
greetings
tpowa
Tobias,
I updated the box that 2.6.34.3 fails to boot do to dmraid problems
(http://bugs.archlinux.org/task/20499) to 2.6.35.2-1 and the box boots with
dmraid just fine. However, there is a problem with udev.
During boot, the box hangs at udev start for a good 2 minutes. The display
on the screen is:
"Waiting for Udev events to be processed:"
The corresponding dmesg failure is:
Adding 1951860k swap on /dev/mapper/nvidia_baaccajap8. Priority:-1 extents:1
across:1951860k
forcedeth 0000:00:0a.0: irq 45 for MSI/MSI-X
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
f71882fg: Found f71882fg chip at 0xa00, revision 32
f71882fg f71882fg.2560: Fan: 1 is in duty-cycle mode
f71882fg f71882fg.2560: Fan: 2 is in duty-cycle mode
f71882fg f71882fg.2560: Fan: 3 is in duty-cycle mode
f71882fg f71882fg.2560: Fan: 4 is in duty-cycle mode
eth0: no IPv6 routers present
INFO: task modprobe:1642 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
modprobe D 0000000000000000 0 1642 1640 0x00000000
ffff880226d2ba28 0000000000000082 ffff88022fca0000 ffff880200000000
0000000000014f40 0000000000014f40 ffff880226d2bfd8 ffff880226d2bfd8
ffff880226d2bfd8 ffff8802276dbe70 ffff880226d2bfd8 0000000000014f40
Call Trace:
[<ffffffffa01c3ba5>] usb_kill_urb+0x85/0xc0 [usbcore]
[<ffffffff810717c0>] ? autoremove_wake_function+0x0/0x40
[<ffffffffa01f6831>] usbhid_init_reports+0xb1/0x120 [usbhid]
[<ffffffffa01f6d53>] usbhid_start+0x4b3/0x5a0 [usbhid]
[<ffffffffa02bf6d8>] hid_device_probe+0x98/0xe0 [hid]
[<ffffffff812875ba>] ? driver_sysfs_add+0x5a/0x90
[<ffffffff81287896>] driver_probe_device+0x96/0x1c0
[<ffffffff81287a60>] ? __device_attach+0x0/0x60
[<ffffffff81287aab>] __device_attach+0x4b/0x60
[<ffffffff81286474>] bus_for_each_drv+0x64/0x90
[<ffffffff8128772f>] device_attach+0x8f/0xb0
[<ffffffff81286ee5>] bus_probe_device+0x25/0x40
[<ffffffff81284c2f>] device_add+0x4ff/0x5e0
[<ffffffffa02bf0a7>] hid_add_device+0x87/0x1b0 [hid]
[<ffffffffa01f44b9>] usbhid_probe+0x329/0x500 [usbhid]
[<ffffffffa01c8a2b>] usb_probe_interface+0xfb/0x1f0 [usbcore]
[<ffffffff81287896>] driver_probe_device+0x96/0x1c0
[<ffffffff81287a5b>] __driver_attach+0x9b/0xa0
[<ffffffff812879c0>] ? __driver_attach+0x0/0xa0
[<ffffffff812867ce>] bus_for_each_dev+0x5e/0x90
[<ffffffff81287559>] driver_attach+0x19/0x20
[<ffffffff81287067>] bus_add_driver+0xc7/0x2e0
[<ffffffff81287cd1>] driver_register+0x71/0x140
[<ffffffffa01c76f8>] usb_register_driver+0xb8/0x170 [usbcore]
[<ffffffffa0116000>] ? hid_init+0x0/0xd1 [usbhid]
[<ffffffffa0116093>] hid_init+0x93/0xd1 [usbhid]
[<ffffffff81002149>] do_one_initcall+0x39/0x1a0
[<ffffffff8108cdeb>] sys_init_module+0xbb/0x200
[<ffffffff81009e82>] system_call_fastpath+0x16/0x1b
I know it fails because after the boot process completes, I get errors like:
12:59 nirvana:~/arch/pkg/parnell>
Broadcast message from nut (Wed Aug 18 12:59:54 2010):
UPS archangel_ups@xxxxxxxxxxxxxxxxxxxxxxxxx is unavailable
So something is wrong. What do you want me to do?
--
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com
