| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <dd18b0c30803221623p16d6e47fjedd15a0ce34a576a@mail.gmail.com> Date: Sat, 22 Mar 2008 23:23:34 +0000 From: "Justin Mattock" <justinmattock@...il.com> To: linux-kernel@...r.kernel.org Subject: rh_timer_func Hello; I'm not going to talk about fglrx. My goal right now is to make sure everything is up and running i.g. keyboard,isight,ati,infrared receiver etc... So I can focus on tyring to get the macbook to four hours of battery life. here is a list of problems I see, Hopefully I can get some answers so linux can reach the spec on a mac, or even better: drivers/hid/usbhid/hid-core.c: couldn't find an input interrupt endpoint. this error occurs randomly every so often: drivers/input/mouse/appletouch.c: could not do mode read request from device (Geyser Raw mode) appletouch: probe of 1-2:1.1 suspend was working at around 2.6.21, then never worked. When using powertop I was able to reach around 3:10hrs at 16W, running OSX I see around 4:17 on a fresh battery. I've noticed the processor goes to the C3 state, but stays at 100% due to too many interrupts: a main interrupt I see is this one = <kernel modules> : usb_hcd_poll_rh_status (rh_timer_func); when the system is powered on this timer is around 1.1% then when powering down the system; i.g. turning of daemons, and rrmod, this timer goes to around 80-90%. I've read the usb documentation; but seem to be missing something to have this timer fall asleep. any help would be appreciated. -- Justin P. Mattock -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists