Re: [arch-general] 2.6.35.4-1 still hangs waiting on udev with usbhid errors
On 09/03/2010 12:16 AM, Myra Nelson wrote: PS Dallas is on I45 and East of I35. I won't even go East of the Brazos anymore. BWood is it. Hmm, check your map and look at the designator for 'Stemmons Freeway' in Dallas, that is I-35E. Recall I-35 EW split to catch both Dallas and Ft. Worth and then come back together ;-) Bwood - dunno, got a case out of the 381st right now in Rio Grande City (Starr Co.) and all I know is it one heck of a loonnng way from home. Cheers... I'll try listing the module. I don't think it is a pure kernel module though. I did a lot of troubleshooting of the driver initially with the NUT developers to get the voltages right on the Cyber Power units (were showing 20+ on the cgi script outputs) I'll follow up with Arjen on the NUT list and see if he knows anything more about the hang on boot. Thanks. -- 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
Re: [arch-general] 2.6.35.4-1 still hangs waiting on udev with usbhid errors
I've tried sever reinstalls of talking archlinux after the August 19, 2010 kernel update and though the Linux installs, it never comes up talking. The sound card device of course is controled by udev so this explains the reason for the failures. I'm doing internet installs since that's how that disk was set up.On Wed, 1 Sep 2010, David C. Rankin wrote: Guys, There are still usbhid-ups problem on boot that hang the boot and don't configure the usbhid-ups driver. This is a flakey issue. I have booted twice, hung the first time (errors below), rebooted and got by the udev/usbhid load in boot and upsmonitoring worked fine. The problem is, there is no way I can remotely administer this box with a 50% chance of it hanging on boot. Any ideas? Here is the error log from everything.log Aug 30 20:30:28 archangel kernel: eth0: no IPv6 routers present Aug 30 20:30:30 archangel kdm_greet[2283]: Cannot load /usr/share/apps/kdm/faces/.default.face: No such file or directory Aug 30 20:31:03 archangel upsd[2295]: listening on 192.168.6.14 port 3493 Aug 30 20:31:03 archangel upsd[2295]: listening on 127.0.0.1 port 3493 Aug 30 20:31:03 archangel upsd[2295]: Can't connect to UPS [archangel_ups] (usbhid-ups-archangel_ups): No such f ile or directory Aug 30 20:31:03 archangel upsd[2296]: Startup successful Aug 30 20:31:03 archangel upsmon[2298]: Startup successful Aug 30 20:31:03 archangel upsmon[2300]: Login on UPS [archangel_...@localhost] failed - got [ERR ACCESS-DENIED] Aug 30 20:31:03 archangel upsmon[2300]: Login on UPS [nirvana_...@nirvana.3111skyline.com] failed - got [ERR ACC ESS-DENIED] Aug 30 20:31:06 archangel kernel: INFO: task modprobe:1579 blocked for more than 120 seconds. Aug 30 20:31:06 archangel kernel: echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Aug 30 20:31:06 archangel kernel: modprobe D 0 1579 1576 0x Aug 30 20:31:06 archangel kernel: 88022616da28 0082 8167eb00 8802 Aug 30 20:31:06 archangel kernel: 00014f40 00014f40 88022616dfd8 88022616dfd8 Aug 30 20:31:06 archangel kernel: 88022616dfd8 8802269c1bc0 88022616dfd8 00014f40 Aug 30 20:31:06 archangel kernel: Call Trace: Aug 30 20:31:06 archangel kernel: [a0202ba5] usb_kill_urb+0x85/0xc0 [usbcore] Aug 30 20:31:06 archangel kernel: [810718d0] ? autoremove_wake_function+0x0/0x40 Aug 30 20:31:06 archangel kernel: [a02e0831] usbhid_init_reports+0xb1/0x120 [usbhid] Aug 30 20:31:06 archangel kernel: [a02e0d53] usbhid_start+0x4b3/0x5a0 [usbhid] Aug 30 20:31:06 archangel kernel: [a02ca6d8] hid_device_probe+0x98/0xe0 [hid] Aug 30 20:31:06 archangel kernel: [812877ea] ? driver_sysfs_add+0x5a/0x90 Aug 30 20:31:06 archangel kernel: [81287ac6] driver_probe_device+0x96/0x1c0 Aug 30 20:31:06 archangel kernel: [81287c90] ? __device_attach+0x0/0x60 Aug 30 20:31:06 archangel kernel: [81287cdb] __device_attach+0x4b/0x60 Aug 30 20:31:06 archangel kernel: [812866a4] bus_for_each_drv+0x64/0x90 Aug 30 20:31:06 archangel kernel: [8128795f] device_attach+0x8f/0xb0 Aug 30 20:31:06 archangel kernel: [81287115] bus_probe_device+0x25/0x40 Aug 30 20:31:06 archangel kernel: [81284e5f] device_add+0x4ff/0x5e0 Aug 30 20:31:06 archangel kernel: [a02ca0a7] hid_add_device+0x87/0x1b0 [hid] Aug 30 20:31:06 archangel kernel: [a02de4b9] usbhid_probe+0x329/0x500 [usbhid] Aug 30 20:31:06 archangel kernel: [a0207a2b] usb_probe_interface+0xfb/0x1f0 [usbcore] Aug 30 20:31:06 archangel kernel: [81287ac6] driver_probe_device+0x96/0x1c0 Aug 30 20:31:06 archangel kernel: [81287c8b] __driver_attach+0x9b/0xa0 Aug 30 20:31:06 archangel kernel: [81287bf0] ? __driver_attach+0x0/0xa0 Aug 30 20:31:06 archangel kernel: [812869fe] bus_for_each_dev+0x5e/0x90 Aug 30 20:31:06 archangel kernel: [81287789] driver_attach+0x19/0x20 Aug 30 20:31:06 archangel kernel: [81287297] bus_add_driver+0xc7/0x2e0 Aug 30 20:31:06 archangel kernel: [81287f01] driver_register+0x71/0x140 Aug 30 20:31:06 archangel kernel: [a02066f8] usb_register_driver+0xb8/0x170 [usbcore] Aug 30 20:31:06 archangel kernel: [a0299000] ? hid_init+0x0/0xd1 [usbhid] Aug 30 20:31:06 archangel kernel: [a0299093] hid_init+0x93/0xd1 [usbhid] Aug 30 20:31:06 archangel kernel: [81002149] do_one_initcall+0x39/0x1a0 Aug 30 20:31:06 archangel kernel: [8108cefb] sys_init_module+0xbb/0x200 Aug 30 20:31:06 archangel kernel: [81009e82] system_call_fastpath+0x16/0x1b Aug 30 20:31:08 archangel upsmon[2300]: Poll UPS [archangel_...@localhost] failed - Driver not connected Aug 30 20:31:08 archangel upsmon[2300]: Communications with UPS archangel_...@localhost lost Aug 30 20:31:08 archangel wall[2302]: wall: user nut broadcasted 1 lines (54
Re: [arch-general] 2.6.35.4-1 still hangs waiting on udev with usbhid errors
On Thu, Sep 2, 2010 at 03:08, Jude DaShiell jdash...@shellworld.net wrote: I've tried sever reinstalls of talking archlinux after the August 19, 2010 kernel update and though the Linux installs, it never comes up talking. The sound card device of course is controled by udev so this explains the reason for the failures. I'm doing internet installs since that's how that disk was set up.On Wed, 1 Sep 2010, David C. Rankin wrote: Guys, There are still usbhid-ups problem on boot that hang the boot and don't configure the usbhid-ups driver. This is a flakey issue. I have booted twice, hung the first time (errors below), rebooted and got by the udev/usbhid load in boot and upsmonitoring worked fine. The problem is, there is no way I can remotely administer this box with a 50% chance of it hanging on boot. Any ideas? Here is the error log from everything.log Aug 30 20:30:28 archangel kernel: eth0: no IPv6 routers present Aug 30 20:30:30 archangel kdm_greet[2283]: Cannot load /usr/share/apps/kdm/faces/.default.face: No such file or directory Aug 30 20:31:03 archangel upsd[2295]: listening on 192.168.6.14 port 3493 Aug 30 20:31:03 archangel upsd[2295]: listening on 127.0.0.1 port 3493 Aug 30 20:31:03 archangel upsd[2295]: Can't connect to UPS [archangel_ups] (usbhid-ups-archangel_ups): No such f ile or directory Aug 30 20:31:03 archangel upsd[2296]: Startup successful Aug 30 20:31:03 archangel upsmon[2298]: Startup successful Aug 30 20:31:03 archangel upsmon[2300]: Login on UPS [archangel_...@localhost] failed - got [ERR ACCESS-DENIED] Aug 30 20:31:03 archangel upsmon[2300]: Login on UPS [nirvana_...@nirvana.3111skyline.com] failed - got [ERR ACC ESS-DENIED] Aug 30 20:31:06 archangel kernel: INFO: task modprobe:1579 blocked for more than 120 seconds. Aug 30 20:31:06 archangel kernel: echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Aug 30 20:31:06 archangel kernel: modprobe D 0 1579 1576 0x Aug 30 20:31:06 archangel kernel: 88022616da28 0082 8167eb00 8802 Aug 30 20:31:06 archangel kernel: 00014f40 00014f40 88022616dfd8 88022616dfd8 Aug 30 20:31:06 archangel kernel: 88022616dfd8 8802269c1bc0 88022616dfd8 00014f40 Aug 30 20:31:06 archangel kernel: Call Trace: Aug 30 20:31:06 archangel kernel: [a0202ba5] usb_kill_urb+0x85/0xc0 [usbcore] Aug 30 20:31:06 archangel kernel: [810718d0] ? autoremove_wake_function+0x0/0x40 Aug 30 20:31:06 archangel kernel: [a02e0831] usbhid_init_reports+0xb1/0x120 [usbhid] Aug 30 20:31:06 archangel kernel: [a02e0d53] usbhid_start+0x4b3/0x5a0 [usbhid] Aug 30 20:31:06 archangel kernel: [a02ca6d8] hid_device_probe+0x98/0xe0 [hid] Aug 30 20:31:06 archangel kernel: [812877ea] ? driver_sysfs_add+0x5a/0x90 Aug 30 20:31:06 archangel kernel: [81287ac6] driver_probe_device+0x96/0x1c0 Aug 30 20:31:06 archangel kernel: [81287c90] ? __device_attach+0x0/0x60 Aug 30 20:31:06 archangel kernel: [81287cdb] __device_attach+0x4b/0x60 Aug 30 20:31:06 archangel kernel: [812866a4] bus_for_each_drv+0x64/0x90 Aug 30 20:31:06 archangel kernel: [8128795f] device_attach+0x8f/0xb0 Aug 30 20:31:06 archangel kernel: [81287115] bus_probe_device+0x25/0x40 Aug 30 20:31:06 archangel kernel: [81284e5f] device_add+0x4ff/0x5e0 Aug 30 20:31:06 archangel kernel: [a02ca0a7] hid_add_device+0x87/0x1b0 [hid] Aug 30 20:31:06 archangel kernel: [a02de4b9] usbhid_probe+0x329/0x500 [usbhid] Aug 30 20:31:06 archangel kernel: [a0207a2b] usb_probe_interface+0xfb/0x1f0 [usbcore] Aug 30 20:31:06 archangel kernel: [81287ac6] driver_probe_device+0x96/0x1c0 Aug 30 20:31:06 archangel kernel: [81287c8b] __driver_attach+0x9b/0xa0 Aug 30 20:31:06 archangel kernel: [81287bf0] ? __driver_attach+0x0/0xa0 Aug 30 20:31:06 archangel kernel: [812869fe] bus_for_each_dev+0x5e/0x90 Aug 30 20:31:06 archangel kernel: [81287789] driver_attach+0x19/0x20 Aug 30 20:31:06 archangel kernel: [81287297] bus_add_driver+0xc7/0x2e0 Aug 30 20:31:06 archangel kernel: [81287f01] driver_register+0x71/0x140 Aug 30 20:31:06 archangel kernel: [a02066f8] usb_register_driver+0xb8/0x170 [usbcore] Aug 30 20:31:06 archangel kernel: [a0299000] ? hid_init+0x0/0xd1 [usbhid] Aug 30 20:31:06 archangel kernel: [a0299093] hid_init+0x93/0xd1 [usbhid] Aug 30 20:31:06 archangel kernel: [81002149] do_one_initcall+0x39/0x1a0 Aug 30 20:31:06 archangel kernel: [8108cefb] sys_init_module+0xbb/0x200 Aug 30 20:31:06 archangel kernel: [81009e82] system_call_fastpath+0x16/0x1b Aug 30 20:31:08 archangel upsmon[2300]: Poll UPS [archangel_...@localhost] failed - Driver not connected Aug 30 20:31:08 archangel upsmon[2300]:
Re: [arch-general] 2.6.35.4-1 still hangs waiting on udev with usbhid errors
On 09/02/2010 04:34 AM, Myra Nelson wrote: David: Stupid question 1, is the usbhid-ups a kernel module (I assume it is, just making sure)? Stupid question 2, do you have the module listed in the modules section of your rc.conf? I've found it much easier to list the modules I need in the rc.conf file and the system seems to boot a little faster. I listed all the modules from lsmod. Myra off topic warning PS. If you would move West of I35 you would have less trouble. The devil made me say that. ROTFLMAO I'm from Dallas originally -- right on top of I35 - so I don't really think that will help :p There are no stupid questions, I have already asked them all! Seriously, yes usbhid-ups is a kernel module used by community/network-ups-tools to enable communications with your UPS. I'm currently running network-ups-tools-2.4.1-1. No - it isn't listed in my rc.conf: MODULES=(dm_mod dm_mirror sata_nv nvidia) So this is one of those that is UDEV activated if the ups is present. I guess if it isn't plugged in on boot, the usbhid-ups driver would never be called. Now this flaky behavior is only on 1 of two boxes I have so I suspect there is some type of bug (a kernel bug maybe) related to the nvidia chipset on this box. I had opened a bug on it, but I guess somebody closed it because I can't find the bug now. I provided all the chipset and hardware info there. Basically, the box is a: MSI K9N2 SLI Platinum Mobo Manufacturer: MSI Product Name: MS-7374 Processor: Phenom Quad Core 9850 Ram: 8G The usb and pci buses looks like this: [23:19 archangel:/home/david/cnf/egw] # lsusb Bus 004 Device 002: ID 045e:0095 Microsoft Corp. IntelliMouse Explorer 4.0 (IntelliPoint) Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [23:16 archangel:/home/david/cnf/egw] # lspci 00:00.0 RAM memory: nVidia Corporation MCP78S [GeForce 8200] Memory Controller (rev a2) 00:01.0 ISA bridge: nVidia Corporation MCP78S [GeForce 8200] LPC Bridge (rev a2) 00:01.1 SMBus: nVidia Corporation MCP78S [GeForce 8200] SMBus (rev a1) 00:01.2 RAM memory: nVidia Corporation MCP78S [GeForce 8200] Memory Controller (rev a1) 00:01.3 Co-processor: nVidia Corporation MCP78S [GeForce 8200] Co-Processor (rev a2) 00:01.4 RAM memory: nVidia Corporation MCP78S [GeForce 8200] Memory Controller (rev a1) 00:02.0 USB Controller: nVidia Corporation MCP78S [GeForce 8200] OHCI USB 1.1 Controller (rev a1) 00:02.1 USB Controller: nVidia Corporation MCP78S [GeForce 8200] EHCI USB 2.0 Controller (rev a1) 00:04.0 USB Controller: nVidia Corporation MCP78S [GeForce 8200] OHCI USB 1.1 Controller (rev a1) 00:04.1 USB Controller: nVidia Corporation MCP78S [GeForce 8200] EHCI USB 2.0 Controller (rev a1) 00:06.0 IDE interface: nVidia Corporation MCP78S [GeForce 8200] IDE (rev a1) 00:07.0 Audio device: nVidia Corporation MCP72XE/MCP72P/MCP78U/MCP78S High Definition Audio (rev a1) 00:08.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Bridge (rev a1) 00:09.0 RAID bus controller: nVidia Corporation MCP78S [GeForce 8200] SATA Controller (RAID mode) (rev a2) 00:0a.0 Ethernet controller: nVidia Corporation MCP77 Ethernet (rev a2) 00:10.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Express Bridge (rev a1) 00:12.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Express Bridge (rev a1) 00:13.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Bridge (rev a1) 00:14.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Bridge (rev a1) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] HyperTransport Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] Miscellaneous Control 00:18.4 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] Link Control 01:06.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01) 01:09.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev c0) 02:00.0 VGA compatible controller: nVidia Corporation G92 [GeForce 8800 GT] (rev a2) 04:00.0 SATA controller: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller (rev 03) 04:00.1 IDE interface: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller (rev 03) Up until this latest string of usbhid problems, I have used this same UPS and setup for a couple of years with both SuSE and Arch and I have never experienced problem like this until the last
Re: [arch-general] 2.6.35.4-1 still hangs waiting on udev with usbhid errors
On 09/02/2010 11:23 PM, David C. Rankin wrote: I had opened a bug on it, but I guess somebody closed it because I can't find the bug now. Correction - I didn't open a bug on this one, I was thinking about the dmraid fail to boot bug where I provided all the hardware info: http://bugs.archlinux.org/task/20499 Let me know if this needs to be opened as a bug. -- 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
Re: [arch-general] 2.6.35.4-1 still hangs waiting on udev with usbhid errors
On Thu, Sep 2, 2010 at 23:33, David C. Rankin drankina...@suddenlinkmail.com wrote: On 09/02/2010 11:23 PM, David C. Rankin wrote: I had opened a bug on it, but I guess somebody closed it because I can't find the bug now. Correction - I didn't open a bug on this one, I was thinking about the dmraid fail to boot bug where I provided all the hardware info: http://bugs.archlinux.org/task/20499 Let me know if this needs to be opened as a bug. -- 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 David: That was my only suggestion. I stopped having usb problems once I listed all my usb modules in rc.conf, so I'm out of ideas. Myra PS Dallas is on I45 and East of I35. I won't even go East of the Brazos anymore. BWood is it. -- Life's fun when your sick and psychotic!
[arch-general] 2.6.35.4-1 still hangs waiting on udev with usbhid errors
Guys, There are still usbhid-ups problem on boot that hang the boot and don't configure the usbhid-ups driver. This is a flakey issue. I have booted twice, hung the first time (errors below), rebooted and got by the udev/usbhid load in boot and upsmonitoring worked fine. The problem is, there is no way I can remotely administer this box with a 50% chance of it hanging on boot. Any ideas? Here is the error log from everything.log Aug 30 20:30:28 archangel kernel: eth0: no IPv6 routers present Aug 30 20:30:30 archangel kdm_greet[2283]: Cannot load /usr/share/apps/kdm/faces/.default.face: No such file or directory Aug 30 20:31:03 archangel upsd[2295]: listening on 192.168.6.14 port 3493 Aug 30 20:31:03 archangel upsd[2295]: listening on 127.0.0.1 port 3493 Aug 30 20:31:03 archangel upsd[2295]: Can't connect to UPS [archangel_ups] (usbhid-ups-archangel_ups): No such f ile or directory Aug 30 20:31:03 archangel upsd[2296]: Startup successful Aug 30 20:31:03 archangel upsmon[2298]: Startup successful Aug 30 20:31:03 archangel upsmon[2300]: Login on UPS [archangel_...@localhost] failed - got [ERR ACCESS-DENIED] Aug 30 20:31:03 archangel upsmon[2300]: Login on UPS [nirvana_...@nirvana.3111skyline.com] failed - got [ERR ACC ESS-DENIED] Aug 30 20:31:06 archangel kernel: INFO: task modprobe:1579 blocked for more than 120 seconds. Aug 30 20:31:06 archangel kernel: echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Aug 30 20:31:06 archangel kernel: modprobe D 0 1579 1576 0x Aug 30 20:31:06 archangel kernel: 88022616da28 0082 8167eb00 8802 Aug 30 20:31:06 archangel kernel: 00014f40 00014f40 88022616dfd8 88022616dfd8 Aug 30 20:31:06 archangel kernel: 88022616dfd8 8802269c1bc0 88022616dfd8 00014f40 Aug 30 20:31:06 archangel kernel: Call Trace: Aug 30 20:31:06 archangel kernel: [a0202ba5] usb_kill_urb+0x85/0xc0 [usbcore] Aug 30 20:31:06 archangel kernel: [810718d0] ? autoremove_wake_function+0x0/0x40 Aug 30 20:31:06 archangel kernel: [a02e0831] usbhid_init_reports+0xb1/0x120 [usbhid] Aug 30 20:31:06 archangel kernel: [a02e0d53] usbhid_start+0x4b3/0x5a0 [usbhid] Aug 30 20:31:06 archangel kernel: [a02ca6d8] hid_device_probe+0x98/0xe0 [hid] Aug 30 20:31:06 archangel kernel: [812877ea] ? driver_sysfs_add+0x5a/0x90 Aug 30 20:31:06 archangel kernel: [81287ac6] driver_probe_device+0x96/0x1c0 Aug 30 20:31:06 archangel kernel: [81287c90] ? __device_attach+0x0/0x60 Aug 30 20:31:06 archangel kernel: [81287cdb] __device_attach+0x4b/0x60 Aug 30 20:31:06 archangel kernel: [812866a4] bus_for_each_drv+0x64/0x90 Aug 30 20:31:06 archangel kernel: [8128795f] device_attach+0x8f/0xb0 Aug 30 20:31:06 archangel kernel: [81287115] bus_probe_device+0x25/0x40 Aug 30 20:31:06 archangel kernel: [81284e5f] device_add+0x4ff/0x5e0 Aug 30 20:31:06 archangel kernel: [a02ca0a7] hid_add_device+0x87/0x1b0 [hid] Aug 30 20:31:06 archangel kernel: [a02de4b9] usbhid_probe+0x329/0x500 [usbhid] Aug 30 20:31:06 archangel kernel: [a0207a2b] usb_probe_interface+0xfb/0x1f0 [usbcore] Aug 30 20:31:06 archangel kernel: [81287ac6] driver_probe_device+0x96/0x1c0 Aug 30 20:31:06 archangel kernel: [81287c8b] __driver_attach+0x9b/0xa0 Aug 30 20:31:06 archangel kernel: [81287bf0] ? __driver_attach+0x0/0xa0 Aug 30 20:31:06 archangel kernel: [812869fe] bus_for_each_dev+0x5e/0x90 Aug 30 20:31:06 archangel kernel: [81287789] driver_attach+0x19/0x20 Aug 30 20:31:06 archangel kernel: [81287297] bus_add_driver+0xc7/0x2e0 Aug 30 20:31:06 archangel kernel: [81287f01] driver_register+0x71/0x140 Aug 30 20:31:06 archangel kernel: [a02066f8] usb_register_driver+0xb8/0x170 [usbcore] Aug 30 20:31:06 archangel kernel: [a0299000] ? hid_init+0x0/0xd1 [usbhid] Aug 30 20:31:06 archangel kernel: [a0299093] hid_init+0x93/0xd1 [usbhid] Aug 30 20:31:06 archangel kernel: [81002149] do_one_initcall+0x39/0x1a0 Aug 30 20:31:06 archangel kernel: [8108cefb] sys_init_module+0xbb/0x200 Aug 30 20:31:06 archangel kernel: [81009e82] system_call_fastpath+0x16/0x1b Aug 30 20:31:08 archangel upsmon[2300]: Poll UPS [archangel_...@localhost] failed - Driver not connected Aug 30 20:31:08 archangel upsmon[2300]: Communications with UPS archangel_...@localhost lost Aug 30 20:31:08 archangel wall[2302]: wall: user nut broadcasted 1 lines (54 chars) Aug 30 20:31:13 archangel upsmon[2300]: Poll UPS [archangel_...@localhost] failed - Driver not connected Aug 30 20:31:13 archangel upsmon[2300]: UPS archangel_...@localhost is unavailable Aug 30 20:31:13 archangel wall[2305]: wall: user nut broadcasted 1 lines (44 chars) Aug 30 20:31:18 archangel upsmon[2300]: Poll UPS [archangel_...@localhost] failed -
