On Saturday 28 March 2009 10:45:24 pm David Johnson wrote:
My last email was premature. I hung again while trying to open an image. I
am attaching the output of dmesg, ps and the Xorg log. The latter is full
of the following messages:
Forgot the Xorg log. Here it is:
--
David Johnson
On Saturday 28 March 2009 11:08:49 pm David Johnson wrote:
On Saturday 28 March 2009 10:45:24 pm David Johnson wrote:
My last email was premature. I hung again while trying to open an image.
I am attaching the output of dmesg, ps and the Xorg log. The latter is
full of the following
Danny Braniss wrote:
it seems March 12 was a bit off :-)
it took some time, but I managed to close the gap:
189100 ok
189150 fails
I will continue tomorrow, but this should be helpful.
189150 is in the middle of a big string of related commits. Try
updating to the
Danny Braniss wrote:
Danny Braniss wrote:
it seems March 12 was a bit off :-)
it took some time, but I managed to close the gap:
189100 ok
189150 fails
I will continue tomorrow, but this should be helpful.
189150 is in the middle of a big string of related commits. Try
Dominic Fandrey wrote:
Since I updated to the 7.2 prerelease, powerd is broken.
uname -a
FreeBSD mobileKamikaze.norad 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE #0: Tue Mar
24 07:57:30 CET 2009
r...@mobilekamikaze.norad:/usr/obj/HP6510b/amd64/usr/src/sys/HP6510b amd64
It increases the CPU
Danny Braniss wrote:
Danny Braniss wrote:
it seems March 12 was a bit off :-)
it took some time, but I managed to close the gap:
189100 ok
189150 fails
I will continue tomorrow, but this should be helpful.
189150 is in the middle of a big string of related commits. Try
Alexander Motin wrote:
Dominic Fandrey wrote:
Since I updated to the 7.2 prerelease, powerd is broken.
uname -a
FreeBSD mobileKamikaze.norad 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE #0:
Tue Mar 24 07:57:30 CET 2009
r...@mobilekamikaze.norad:/usr/obj/HP6510b/amd64/usr/src/sys/HP6510b
On Tue, 20 Jan 2009 08:08:29 +0100
Marc UBM Bocklet u...@u-boot-man.de wrote:
On Tue, 20 Jan 2009 09:39:51 +1100
Andrew Snow and...@modulus.org wrote:
I think that if you use eSATA you probably need dedicated eSATA
controller ports. eSATA standard specifies a higher voltage for
the
Danny Braniss danny at cs.huji.ac.il writes:
at least for me :-)
[and sorry for the cross posting]
[...]
amr0: LSILogic MegaRAID 1.53 mem
0xfbef-0xfbef,0xfe58-0xfe5f
irq 27 at device 0.0 on pci4
amr0: [ITHREAD]
amr0: delete logical drives supported by
Dominic Fandrey wrote:
Alexander Motin wrote:
Dominic Fandrey wrote:
Since I updated to the 7.2 prerelease, powerd is broken.
uname -a
FreeBSD mobileKamikaze.norad 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE #0:
Tue Mar 24 07:57:30 CET 2009
Alexander Motin wrote:
Dominic Fandrey wrote:
Alexander Motin wrote:
Dominic Fandrey wrote:
Since I updated to the 7.2 prerelease, powerd is broken.
uname -a
FreeBSD mobileKamikaze.norad 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE #0:
Tue Mar 24 07:57:30 CET 2009
Dominic Fandrey wrote:
Alexander Motin wrote:
Dominic Fandrey wrote:
Alexander Motin wrote:
Dominic Fandrey wrote:
Since I updated to the 7.2 prerelease, powerd is broken.
uname -a
FreeBSD mobileKamikaze.norad 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE #0:
Tue Mar 24 07:57:30 CET 2009
Alexander Motin wrote:
Dominic Fandrey wrote:
Alexander Motin wrote:
Dominic Fandrey wrote:
Alexander Motin wrote:
Dominic Fandrey wrote:
Since I updated to the 7.2 prerelease, powerd is broken.
uname -a
FreeBSD mobileKamikaze.norad 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE
#0:
Tue Mar 24
Dominic Fandrey wrote:
Alexander Motin wrote:
It means that one of your CPUs spent most of it's time in interrupt
processing and so far from idle. What does `top -P` shows you? Where
have you seen that ~6% CPU load?
That is the load shown by the e17 CPU module. It's display has always
been in
Nathanael Jean-Francois wrote:
Hello all,
I've been getting some panics with a 7.1 stable machine from March 14th.
I've not been able to determine the cause nor reproduce them at will.
Here's a backtrace from the latest panic on March 23rd. Let me know if any
more information is needed. Thanks.
Alexander Motin wrote:
Dominic Fandrey wrote:
Alexander Motin wrote:
It means that one of your CPUs spent most of it's time in interrupt
processing and so far from idle. What does `top -P` shows you? Where
have you seen that ~6% CPU load?
That is the load shown by the e17 CPU module. It's
Dominic Fandrey wrote:
Alexander Motin wrote:
Dominic Fandrey wrote:
Alexander Motin wrote:
It means that one of your CPUs spent most of it's time in interrupt
processing and so far from idle. What does `top -P` shows you? Where
have you seen that ~6% CPU load?
That is the load shown by the
Danny Braniss wrote:
Danny Braniss wrote:
Danny Braniss wrote:
it seems March 12 was a bit off :-)
it took some time, but I managed to close the gap:
189100 ok
189150 fails
I will continue tomorrow, but this should be helpful.
189150 is in the middle of a big string of
Dominic Fandrey wrote:
Dominic Fandrey wrote:
Alexander Motin wrote:
Dominic Fandrey wrote:
Alexander Motin wrote:
It means that one of your CPUs spent most of it's time in interrupt
processing and so far from idle. What does `top -P` shows you? Where
have you seen that ~6% CPU load?
That
On Sat, 2009-03-28 at 21:04 -0700, Chris H wrote:
Greetings,
A fresh install of 7 followed by a cvsup to 7.2-PRE on the 26th
results in an inability to build Xorg on the system. A cvsup only
an hour ago provides no solution.
An attempt at the following:
cd /usr/ports/x11/xorg-minimal
Dominic Fandrey wrote:
I can rule out drm0 as the cause, because uhci0 is the only common
presence in all occurrences of this problem.
You have other examples? If you mean irq16: hdac0 uhci+ string, then
+ there means and some other devices, which in this case is probably
drm0.
There were
Dear colleagues,
is it normal that between reboots NFS exported ZFS file systems change NFS
handles? After server reboot, I have
stale NFS handle
on any request to previously mounted FS. On UFS, mounted NFS file systems
survive server reboots...
Thanks in advance.
--
Sincerely,
D.Marck
Alexander Motin wrote:
Dominic Fandrey wrote:
I can rule out drm0 as the cause, because uhci0 is the only common
presence in all occurrences of this problem.
You have other examples? If you mean irq16: hdac0 uhci+ string, then
+ there means and some other devices, which in this case is
23 matches
Mail list logo