I haven't noticed that issue and it is surely not expected for me. I will try to reproduce it. Most likely you should be able to avoid interrupt sharing using some I can't say about USB, but you may try this patch to optimize some other Surely it is. I was even thinking about possibility to port one from OpenSolaris, but other work distracted me. You may take it, it you wish. -- Alexander Motin _______________________________________________ freebsd-current@freebsd.org mailing ...

The USB controller often keeps the bus mastering bit set. This keeps the system out of C3. The way to fix this is to implement global suspend. Put a device in suspend mode and then turn off power to the USB port it This seems silly. The whole point of APIC is to avoid clustering on a It seems worth doing the internals new, but maybe outputting information in a compatible format for reporting tools. -- Nate _______________________________________________ freebsd-current@freebsd.org ...

No, it's actually on purpose I think as the other bits under notyet destroy the thread when the last handler for it goes away. However, ithread_destroy() does not block in any of 7.x or later: static void ithread_destroy(struct intr_thread *ithread) { struct thread *td; CTR2(KTR_INTR, "%s: killing %s", __func__, ithread->it_event->ie_name); td = ithread->it_thread; thread_lock(td); ithread->it_flags |= IT_DEAD; if (TD_AWAITING_INTR(td)) { TD_CLR_IWAIT(td); sched_add(td, ...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, Here is a patch that makes top(1) to inverse its table header (PID USERNAME THR, etc). Cheers, - -- Xin LI <delphij@delphij.net> http://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 ...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I'm thinking about the attached patch which turns printf(9) to uprintf(9) call. Cheers, - -- Xin LI <delphij@delphij.net> http://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 ...

Err... that would cause problems if someone was reading the syslog output as it would no longer be logged (from uprintf(9)): The uprintf() function outputs to the current process' controlling tty, while printf() writes to the console as well as to the logging facility. I personally like reading syslog output more than I do like reading the console because messages can get lost on the console quicker :/... Is there a hybrid ...

The reason I vote know is that ENOEXEC can mean several things. I thought you had a patch to catch the actual kernel error message and pass it back to userland. That would be a useful feature, but this message doesn't really help and can point people in the wrong direction if their error is due to a different problem. If you want to help the user, then I think a more useful approach would be to tell the user to check dmesg for error messages when kldload(2) fails with ENOEXEC. -- ...

Sharing you experience would help (if you are not on amd64). _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"