On 10/25/2010 5:53 PM, Garrett Cooper wrote:
On Mon, Oct 25, 2010 at 2:15 PM, Doug Bartondo...@freebsd.org wrote:
On 10/25/2010 13:33, Ivan Voras wrote:
(except if the message is changed to say please look at the kernel
syslog messages to find out the real reason for this failure)
Thinking
On 10/26/10 02:53, Garrett Cooper wrote:
Wouldn't noting this in the manpage be sufficient?
I ran into this `item' (:)..) today after a power outage because
nvidia-driver was built against different kernel headers, and it
prints out the error clear as day on /dev/console,
Luckily in
On Mon, Oct 25, 2010 at 1:07 AM, Matthias Apitz g...@unixarea.de wrote:
I have a new laptop Acer Aspire One D250 and pulled out HEAD from SVN
today morning. As far as I can see in sys/dev/bwi and sys/dev/bwn the
above chip is still not supported. I am wrong?
i have the same problem with a
On Monday, October 25, 2010 3:19:26 pm Xin LI wrote:
Hi,
Here is a simple patch that adds more meaning messages when kldload hits
ENOEXEC.
Before patch:
kldload: can't load geom_eli.ko: Exec format error
After patch:
kldload: can't load geom_eli.ko: Exec format error
kldload:
On 10/26/10, Alberto Villa avi...@freebsd.org wrote:
On Mon, Oct 25, 2010 at 1:07 AM, Matthias Apitz g...@unixarea.de wrote:
I have a new laptop Acer Aspire One D250 and pulled out HEAD from SVN
today morning. As far as I can see in sys/dev/bwi and sys/dev/bwn the
above chip is still not
It looks like a bug in intr_event_destroy(9): I'm trying to unload a
new driver being developed internally for NVRAM, and I get this
WITNESS warning and hang:
# kldunload rnv
Sleeping on ithdty with the following non-sleepable locks held:
exclusive sleep mutex intr event list (intr event list) r
On Tuesday, October 26, 2010 11:55:10 am Matthew Fleming wrote:
It looks like a bug in intr_event_destroy(9): I'm trying to unload a
new driver being developed internally for NVRAM, and I get this
WITNESS warning and hang:
# kldunload rnv
Sleeping on ithdty with the following
On Tue, Oct 26, 2010 at 9:46 AM, John Baldwin j...@freebsd.org wrote:
On Tuesday, October 26, 2010 11:55:10 am Matthew Fleming wrote:
It looks like a bug in intr_event_destroy(9): I'm trying to unload a
new driver being developed internally for NVRAM, and I get this
WITNESS warning and hang:
I updated my FreeBSD tree on laptop, to the current
as of 18 Oct.2010, it works fine with CPU C3 state enabled,
I think this is your achievement of event time scheduler,
thanks!
But when USB driver is enabled, the load average is considerablly
high (0.6 to 1.0) if sysctl oid
Takanori Watanabe wrote:
I updated my FreeBSD tree on laptop, to the current
as of 18 Oct.2010, it works fine with CPU C3 state enabled,
I think this is your achievement of event time scheduler,
thanks!
But when USB driver is enabled, the load average is considerablly
high (0.6 to 1.0)
On 10/26/2010 12:57 PM, Alexander Motin wrote:
Takanori Watanabe wrote:
I updated my FreeBSD tree on laptop, to the current
as of 18 Oct.2010, it works fine with CPU C3 state enabled,
I think this is your achievement of event time scheduler,
thanks!
Ah, so mav@ implemented a
11 matches
Mail list logo