Re: cpufreq and changing driver
Hi Bruno, > > 2) sorry what about the point that we were discussing above? The high > > number of transition you were explaining me, are present in the actual > > implementation of powerd, and if not, why? > > It's not present under powerd for the simple fact that to be efficient > in term of not being too intrusive (kernel to user data transfers, etc), > powerd can only provide a limited number of check per second (at this > time, 2 per second). But the current algorithm present in powerd is > not well suited in that case. You have to wait one demi-second > for the processor being put to full speed if the system was idle > before. > Are there on the horizon any sort of plans to implement a newer and more efficient algorithm to increase the number of transition per second? Sorry but i've not understood why linux-cpufreqd is able to cope with those without being so intrusive. Best regards, MC ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Fatal trap 12: page fault while in kernel mode
I have the following panic occurring several times a week. The machine is an
NFS server, and it usually panics early in the morning, when first people try
to access it. After reboot it may work OK for 1-2 days, and then panics
again. I have tried changing memory and replacing disk which was exported via
NFS, but nothing helped :(
Any suggestion on how to fix this panic will be very much appreciated !
/Yuri
[EMAIL PROTECTED]/var/crash]# uname -a
FreeBSD XXX.irfu.se 6.0-STABLE FreeBSD 6.0-STABLE #0: Tue Nov 29 13:31:15 CET
2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/HEM i386
[EMAIL PROTECTED]/var/crash]# kgdb /usr/obj/usr/src/sys/HEM/kernel.debug
vmcore.7
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:
Undefined symbol "ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd".
Unread portion of the kernel message buffer:
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x74
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc053a426
stack pointer = 0x28:0xd56c0b88
frame pointer = 0x28:0xd56c0b8c
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= resume, IOPL = 0
current process = 77 (vnlru)
trap number = 12
panic: page fault
Uptime: 2d12h22m11s
Dumping 511 MB (2 chunks)
chunk 0: 1MB (160 pages) ... ok
chunk 1: 511MB (130800 pages) 495 479 463 447 431 415 399 383 367 351 335
319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15
#0 doadump () at pcpu.h:165
165 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) where
#0 doadump () at pcpu.h:165
#1 0xc051577a in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399
#2 0xc0515a84 in panic (fmt=0xc06ce475 "%s")
at /usr/src/sys/kern/kern_shutdown.c:555
#3 0xc06b4815 in trap_fatal (frame=0xd56c0b48, eva=0)
at /usr/src/sys/i386/i386/trap.c:836
#4 0xc06b3f2d in trap (frame=
{tf_fs = 1133445128, tf_es = 40, tf_ds = 40, tf_edi = -1017997312,
tf_esi = -1020120704, tf_ebp = -714339444, tf_isp = -714339468, tf_ebx =
-1012942272, tf_edx = -1020120704, tf_ecx = 0, tf_eax = 0, tf_trapno = 12,
tf_err = 0, tf_eip = -1068260314, tf_cs = 32, tf_eflags = 589831, tf_esp =
-1020120704, tf_ss = -714339408})
at /usr/src/sys/i386/i386/trap.c:269
#5 0xc06a24fa in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#6 0xc053a426 in turnstile_setowner (ts=0xc39fba40, owner=0x0)
at /usr/src/sys/kern/subr_turnstile.c:417
#7 0xc053a752 in turnstile_wait (lock=0xc461fe00, owner=0x0)
at /usr/src/sys/kern/subr_turnstile.c:576
#8 0xc050b511 in _mtx_lock_sleep (m=0xc461fe00, tid=3274846592, opts=0,
file=0x0, line=0)
at /usr/src/sys/kern/kern_mutex.c:555
#9 0xc064becd in ufsdirhash_free (ip=0xc4a33840)
at /usr/src/sys/ufs/ufs/ufs_dirhash.c:289
#10 0xc064de66 in ufs_reclaim (ap=0x0) at /usr/src/sys/ufs/ufs/ufs_inode.c:175
#11 0xc06bef38 in VOP_RECLAIM_APV (vop=0x0, a=0xc3323180) at vnode_if.c:1589
#12 0xc057adfe in vgonel (vp=0xc3cf3aa0) at vnode_if.h:818
#13 0xc0577530 in vtryrecycle (vp=0xc3cf3aa0)
at /usr/src/sys/kern/vfs_subr.c:840
#14 0xc0576ec6 in vnlru_free (count=1376) at /usr/src/sys/kern/vfs_subr.c:668
#15 0xc0577019 in vnlru_proc () at /usr/src/sys/kern/vfs_subr.c:703
#16 0xc04fc310 in fork_exit (callout=0xc0576f24 , arg=0x0,
frame=0x0)
at /usr/src/sys/kern/kern_fork.c:789
#17 0xc06a255c in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:208
(kgdb) quit
--
Dr. Yuri Khotyaintsev
Institutet för rymdfysik (IRF), Uppsala
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cpufreq and changing driver
Marco Calviani wrote: Hi Bruno, > > 2) sorry what about the point that we were discussing above? The high number of transition you were explaining me, are present in the actual implementation of powerd, and if not, why? It's not present under powerd for the simple fact that to be efficient in term of not being too intrusive (kernel to user data transfers, etc), powerd can only provide a limited number of check per second (at this time, 2 per second). But the current algorithm present in powerd is not well suited in that case. You have to wait one demi-second for the processor being put to full speed if the system was idle before. Are there on the horizon any sort of plans to implement a newer and more efficient algorithm to increase the number of transition per second? Sorry but i've not understood why linux-cpufreqd is able to cope with those without being so intrusive. This work is easy, it's just grunt work implementing and testing to see which is best. See this page for details on how to proceed: http://wikitest.freebsd.org/moin.cgi/powerd Wikitest seems to be down so here's the text only: http://66.102.7.104/search?q=cache:IEXV5nW17ZMJ:wikitest.freebsd.org/moin.cgi/powerd+site:wikitest.freebsd.org+powerd+&hl=en&lr=&strip=1 -- Nate ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cpufreq and changing driver
On Fri, 2 Dec 2005 19:35, Marco Calviani wrote: > > It's not present under powerd for the simple fact that to be efficient > > in term of not being too intrusive (kernel to user data transfers, etc), > > powerd can only provide a limited number of check per second (at this > > time, 2 per second). But the current algorithm present in powerd is > > not well suited in that case. You have to wait one demi-second > > for the processor being put to full speed if the system was idle > > before. > > Are there on the horizon any sort of plans to implement a newer and > more efficient algorithm to increase the number of transition per > second? Sorry but i've not understood why linux-cpufreqd is able to > cope with those without being so intrusive. I don't see why you can't run powerd more frequently, I do.. Unless your ACPI has a problem that means the transition is slow. I can't imagine that doing 5 (or even 50) syscalls a second is a big CPU load unless there is a specific problem with sysctls or the cpufreq infrastructure. I run powerd like this -> /usr/sbin/powerd -i 90 -r 30 -a adaptive -b adaptive -n adaptive -p 200 -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgp7RxMCHbtHH.pgp Description: PGP signature
Re: cpufreq and changing driver
On Friday 02 December 2005 08:05, Daniel O'Connor wrote: > > I run powerd like this -> > /usr/sbin/powerd -i 90 -r 30 -a adaptive -b adaptive -n adaptive -p 200 Hi n my NB an Acer 3002 I got best battery life with -a max -r 30 -i 80 -b adaptive any other settings resulted in continuous cpufreq and fan up-down loops even only looking at the screen ;) but I got nothing on changing the default -p value João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
/dev/agpgart missing
Since sometime in the not-so-distant past, I've lost my xv support in Xorg. This seems to be related to /dev/agpgart beeing gone, but agp is certainly in my kernel. The chipset is Intel 855GM and running on a Dell Latitude x300. I've got a custom kernel, but I haven't changed my kernconf in months, and XV used to be supported by my setup just recently. Please provide me with any pointers. If you don't know my problem, hints on keyword to search for is most welcome. Svein Halvor ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
cpu-timer rate
Hi,
I am just wondering why the cpu-timer is doubled from what I set in
kern.hz?
# vmstat -i
interrupt total rate
irq1: atkbd0 4 0
irq6: fdc087 0
irq13: npx01 0
irq14: ata0 46 0
irq29: bge0 154553 21
irq30: ciss0 282200 39
cpu0: timer 14314031 1999
Total 14750922 2060
# sysctl -a | grep hz
kern.clockrate: { hz = 1000, tick = 1000, profhz = 666, stathz = 133 }
/Bjorn
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fatal trap 12: page fault while in kernel mode
On Friday 02 December 2005 05:00 am, Yuri Khotyaintsev wrote: > I have the following panic occurring several times a week. The machine is > an NFS server, and it usually panics early in the morning, when first > people try to access it. After reboot it may work OK for 1-2 days, and then > panics again. I have tried changing memory and replacing disk which was > exported via NFS, but nothing helped :( > > Any suggestion on how to fix this panic will be very much appreciated ! This panic (in propagate_priority) is usually caused when a thread goes to sleep while holding a mutex (which is forbidden). If you enable INVARIANTS and/or WITNESS you should get a better panic, and with WITNESS you will even be warned when a thread goes to sleep while holding a mutex. However, these options do introduce considerable execution overhead, and sometimes that overhead changes the timing enough to hide the race. :( -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cpufreq and changing driver
On Fri, Dec 02, 2005 at 08:35:54PM +1030, Daniel O'Connor wrote: > On Fri, 2 Dec 2005 19:35, Marco Calviani wrote: > > > It's not present under powerd for the simple fact that to be efficient > > > in term of not being too intrusive (kernel to user data transfers, etc), > > > powerd can only provide a limited number of check per second (at this > > > time, 2 per second). But the current algorithm present in powerd is > > > not well suited in that case. You have to wait one demi-second > > > for the processor being put to full speed if the system was idle > > > before. > > > > Are there on the horizon any sort of plans to implement a newer and > > more efficient algorithm to increase the number of transition per > > second? Sorry but i've not understood why linux-cpufreqd is able to > > cope with those without being so intrusive. > > I don't see why you can't run powerd more frequently, I do.. Unless your ACPI > has a problem that means the transition is slow. I'm sure this could not be done under Linux without a lot of problems (it is required to use the /proc things and it's too slow in that case). > I can't imagine that doing 5 (or even 50) syscalls a second is a big CPU load > unless there is a specific problem with sysctls or the cpufreq > infrastructure. If that's possible being not so intrusive with, say 50 syscalls under FreeBSD, then all I said above is indeed stupid crap. > I run powerd like this -> > /usr/sbin/powerd -i 90 -r 30 -a adaptive -b adaptive -n adaptive -p 200 > -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cpufreq and changing driver
Hi list, 2005/12/2, Bruno Ducrot <[EMAIL PROTECTED]>: > > I don't see why you can't run powerd more frequently, I do.. Unless your > > ACPI > > has a problem that means the transition is slow. > > I'm sure this could not be done under Linux without a lot of > problems (it is required to use the /proc things and it's too slow in > that case). > > > I can't imagine that doing 5 (or even 50) syscalls a second is a big CPU > > load > > unless there is a specific problem with sysctls or the cpufreq > > infrastructure. > > If that's possible being not so intrusive with, say 50 syscalls under FreeBSD, > then all I said above is indeed stupid crap. > > > I run powerd like this -> > > /usr/sbin/powerd -i 90 -r 30 -a adaptive -b adaptive -n adaptive -p 200 > > Well, i've tried decreasing the polling interval, but there is an increased powerd cpu load: at 100ms polling interval the cpu load is to an astonishing 20% circa, which i think it's too much for a normal use. The sampling rate with ondemand governor in linux kernel is 10ms but cpufreqd is at 0.6% on average cpu load. Regards, MC ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cpufreq and changing driver
Hi Nate, 2005/12/2, Nate Lawson <[EMAIL PROTECTED]>: > This work is easy, it's just grunt work implementing and testing to see > which is best. See this page for details on how to proceed: > > http://wikitest.freebsd.org/moin.cgi/powerd > > Wikitest seems to be down so here's the text only: > http://66.102.7.104/search?q=cache:IEXV5nW17ZMJ:wikitest.freebsd.org/moin.cgi/powerd+site:wikitest.freebsd.org+powerd+&hl=en&lr=&strip=1 > I'll have a look at it whenever it will become online again. Regards, MC ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fatal trap 12: page fault while in kernel mode
On Friday 02 December 2005 14.54, John Baldwin wrote: > On Friday 02 December 2005 05:00 am, Yuri Khotyaintsev wrote: > > I have the following panic occurring several times a week. The machine is > > an NFS server, and it usually panics early in the morning, when first > > people try to access it. After reboot it may work OK for 1-2 days, and > > then panics again. I have tried changing memory and replacing disk which > > was exported via NFS, but nothing helped :( > > > > Any suggestion on how to fix this panic will be very much appreciated ! > > This panic (in propagate_priority) is usually caused when a thread goes to > sleep while holding a mutex (which is forbidden). If you enable INVARIANTS > and/or WITNESS you should get a better panic, and with WITNESS you will > even be warned when a thread goes to sleep while holding a mutex. However, > these options do introduce considerable execution overhead, and sometimes > that overhead changes the timing enough to hide the race. :( I am compiling a new kernel with INVARIANTS and WITNESS now. Will wait for a "better" panic ;-) -- Dr. Yuri Khotyaintsev Institutet för rymdfysik (IRF), Uppsala ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cpufreq and changing driver
Marco Calviani wrote: Hi list, 2005/12/2, Bruno Ducrot <[EMAIL PROTECTED]>: I don't see why you can't run powerd more frequently, I do.. Unless your ACPI has a problem that means the transition is slow. I'm sure this could not be done under Linux without a lot of problems (it is required to use the /proc things and it's too slow in that case). I can't imagine that doing 5 (or even 50) syscalls a second is a big CPU load unless there is a specific problem with sysctls or the cpufreq infrastructure. If that's possible being not so intrusive with, say 50 syscalls under FreeBSD, then all I said above is indeed stupid crap. I run powerd like this -> /usr/sbin/powerd -i 90 -r 30 -a adaptive -b adaptive -n adaptive -p 200 Well, i've tried decreasing the polling interval, but there is an increased powerd cpu load: at 100ms polling interval the cpu load is to an astonishing 20% circa, which i think it's too much for a normal use. The sampling rate with ondemand governor in linux kernel is 10ms but cpufreqd is at 0.6% on average cpu load. powerd is not intended to do high speed polling. If you do that, your system will almost never be idle and so we can't save power via Cx. We don't need high speed sampling right now, we need a predictive algorithm. So until someone implements this, it's moot. -- Nate ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cpufreq and changing driver
On Friday 02 December 2005 12:04, Marco Calviani wrote: > > Well, i've tried decreasing the polling interval, but there is an > increased powerd cpu load: at 100ms polling interval the cpu load is > to an astonishing 20% circa, which i think it's too much for a normal > use. The sampling rate with ondemand governor in linux kernel is 10ms > but cpufreqd is at 0.6% on average cpu load. > could you please tell what you are aspecting from higher rates? I am not sure if the cicles spend for polling are not using more power than an probably already idle processor and fan. João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
6-STABLE and mount_ufs.c
Hello, I'm tracking 6-STABLE, and cvsup'ed sources as of 6:00am GMT today (in fact, I did this yesterday, too, with a fresh copy of the repository). Upon building world, I got the following error: [...] rm -f .depend mkdep -f .depend -a /usr/src/sbin/mksnap_ffs/mksnap_ffs.c echo mksnap_ffs: /usr/obj/usr/src/tmp/usr/lib/libc.a >> .depend ===> sbin/mount (depend) make: don't know how to make mount_ufs.c. Stop *** Error code 2 Stop in /usr/src/sbin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. I took a closer look at the deltas in the CVSWeb, and, if I understood correctly, mount_ufs.c should no longer exist, but is still being referenced in the Makefile. I removed the reference from the Makefile, and the compilation goes a little bit further, but fails with: [...] ld -dc -r -o chroot.lo chroot_stub.o /usr/obj/usr/src/rescue/rescue//usr/src/usr .sbin/chroot/chroot.o crunchide -k _crunched_chroot_stub chroot.lo cc -static -o rescue rescue.o cat.lo chflags.lo chio.lo chmod.lo cp.lo date.lo d d.lo df.lo echo.lo ed.lo expr.lo getfacl.lo hostname.lo kenv.lo kill.lo ln.lo ls .lo mkdir.lo mv.lo pax.lo ps.lo pwd.lo realpath.lo rm.lo rmdir.lo setfacl.lo sh. lo stty.lo sync.lo test.lo rcp.lo csh.lo atacontrol.lo badsect.lo bsdlabel.lo ca mcontrol.lo ccdconfig.lo clri.lo devfs.lo dmesg.lo dump.lo dumpfs.lo dumpon.lo f sck.lo fsck_ffs.lo fsck_msdosfs.lo fsdb.lo fsirand.lo gbde.lo ifconfig.lo init.l o kldconfig.lo kldload.lo kldstat.lo kldunload.lo ldconfig.lo md5.lo mdconfig.lo mdmfs.lo mknod.lo mount.lo mount_cd9660.lo mount_ext2fs.lo mount_msdosfs.lo mou nt_nfs.lo mount_ntfs.lo mount_nullfs.lo mount_std.lo mount_udf.lo mount_umapfs.l o mount_unionfs.lo newfs.lo newfs_msdos.lo nos-tun.lo ping.lo reboot.lo restore. lo rcorder.lo route.lo routed.lo rtquery.lo rtsol.lo savecore.lo slattach.lo spp pcontrol.lo startslip.lo swapon.lo sysctl.lo tunefs.lo umount.lo ping6.lo ipf.lo sconfig.lo fdisk.lo dhclient.lo bzip2.lo tar.lo vi.lo id.lo gzip.lo chroot.lo / usr/obj/usr/src/rescue/rescue/../librescue/exec.o /usr/obj/usr/src/rescue/rescue /../librescue/getusershell.o /usr/obj/usr/src/rescue/rescue/../librescue/login_c lass.o /usr/obj/usr/src/rescue/rescue/../librescue/popen.o /usr/obj/usr/src/resc ue/rescue/../librescue/rcmdsh.o /usr/obj/usr/src/rescue/rescue/../librescue/sysc tl.o /usr/obj/usr/src/rescue/rescue/../librescue/system.o -lcrypt -ledit -lkvm - ll -lm -ltermcap -lutil -lcrypto -lalias -lbsdxml -lcam -lcurses -ldevstat -lips ec -lipx -lgeom -lkiconv -lmd -lreadline -lsbuf -lufs -lz -lbz2 -larchive mount.lo(.text+0xc33): In function `mountfs': : undefined reference to `mount_ufs' *** Error code 1 Stop in /usr/obj/usr/src/rescue/rescue. *** Error code 1 Stop in /usr/src/rescue/rescue. *** Error code 1 Stop in /usr/src/rescue. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Looking in the sbin/mount.c file, I found a call to mount_ufs, a function which was previously in mount_ufs.c. What is the correct way I should deal with this? Copy the old mount_ufs.c? Or change the call to something else? I suppose this would be nmount()? Or am I missing something else? The revision of mount.c is 1.69, and for the Makefile, is 1.15. Are they correct for 6-STABLE? Can I safely use the HEAD tag for those two files in a stable tree? Thanks in advance, Torgan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cpu-timer rate
On Fri, 2005-Dec-02 14:32:58 +0100, kama wrote:
>I am just wondering why the cpu-timer is doubled from what I set in
>kern.hz?
>
># vmstat -i
>interrupt total rate
...
>cpu0: timer 14314031 1999
>Total 14750922 2060
>
># sysctl -a | grep hz
>kern.clockrate: { hz = 1000, tick = 1000, profhz = 666, stathz = 133 }
There's only a single timer but FreeBSD needs two independent clocks.
The 'tick' clock is used to update the TOD counters and decide when to
reschedule processes. The 'stathz' is used to collect statistics on
CPU utilisation ('profhz' is used instead if any process is using
profiling). Since processes tend to synchronize to 'tick' the
statistics clock needs to be independent to ensure that a CPU utilisation
is correctly allocated.
In order to simulate two clocks, FreeBSD runs the hardware clock at a
high rate and uses two different divisors for the soft clocks (/2 for
tick, /3 for profhz and /15 for stathz). Larger divisors are better
for utilisation statistics but increase clock interrupt overheads.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IBM T42 freezes when going to sleep under X11
Jacques Garrigue writes: > From: Jacques Garrigue <[EMAIL PROTECTED]> > > I've got a strange problem with my IBM T42 / Radeon M10 setup. > > > > When using the 6.0-RELEASE kernel (including GENERIC), I cannot go to > > sleep when X11 is running: the machine freezes, display still on. I > > tried disabling DRI, but this does not seem to be the problem: I have > > no DRM anyway. > > > > On the other hand, everything works fines with a 6.0-RC1 kernel. > > Was there a big change in between, such that I need to change my > > configuration? > > I finally found the cause of my problems: there has been changes in > the em driver (Gb ethernet), such that the machine freezes when trying > to switch automatically from the X11 VT to the system console, before > going to sleep. The interaction is surprising, but clearly the problem > disappears when I remove "device em" from the kernel configuration, > and it reappears when I do "kldload if_em". Since I'm using only ath > (wireless) anyway, this is fine with me... > > A previous partial solution suggested to me was to add > hw.syscons.sc_no_suspend_vtswitch=1 > to sysctl.conf, but this means the screen gets garbled and I have to > do the switch by hand anyway, which is a real pain. > Worse still: the machine would still freeze when going to sleep while > the disk is active. > > The last step is to track down the bug in em, as it still seems to > be there in yesterday's STABLE. I don't seem to have any problem with my T42p using a kernel compiled on 11/29 11:21 My copy of if_em.c is: /*$FreeBSD: src/sys/dev/em/if_em.c,v 1.65.2.8 2005/11/25 14:11:59 glebius Exp $*/ g. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD-6 amr and ahd trouble
I know I'm a couple weeks late, but I've been having the same problem with my 300-8x. It seems that after a seemingly random period of time on my dual opteron box, the system just hangs. It did kernel panic once when I was taking down the geom array. Originally I thought it might have something to do with GEOM, but since it's also happened outside of a GEOM array, I'm kind of at a loss. Have you managed to find anything out about what exactly is causing the problem? I don't get any kind of error messages, so I haven't had much luck in tracking it down. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IBM T42 freezes when going to sleep under X11
From: George Hartzell <[EMAIL PROTECTED]> > Jacques Garrigue writes: > > From: Jacques Garrigue <[EMAIL PROTECTED]> > > > I've got a strange problem with my IBM T42 / Radeon M10 setup. > > > > > > When using the 6.0-RELEASE kernel (including GENERIC), I cannot go to > > > sleep when X11 is running: the machine freezes, display still on. I > > > tried disabling DRI, but this does not seem to be the problem: I have > > > no DRM anyway. > > > > > > On the other hand, everything works fines with a 6.0-RC1 kernel. > > > Was there a big change in between, such that I need to change my > > > configuration? > > > > I finally found the cause of my problems: there has been changes in > > the em driver (Gb ethernet), such that the machine freezes when trying > > to switch automatically from the X11 VT to the system console, before > > going to sleep. The interaction is surprising, but clearly the problem > > disappears when I remove "device em" from the kernel configuration, > > and it reappears when I do "kldload if_em". Since I'm using only ath > > (wireless) anyway, this is fine with me... > > I don't seem to have any problem with my T42p using a kernel compiled > on 11/29 11:21 > > My copy of if_em.c is: > > /*$FreeBSD: src/sys/dev/em/if_em.c,v 1.65.2.8 2005/11/25 14:11:59 glebius Exp > $*/ The very same version I could reproduce the bug with... I suppose the cause is a complex interaction. For instance it only appears under X11. So part of the reason might be the difference between the radeon M10 and the FIRE GL T2. Or the fact I'm simultaneously using ath. Or anything else... My point was just that the direct trigger was a change in em between 6.0-RC1 and 6.0-RELEASE. But if it cannot be reproduced on any other machine, this is going to be difficult to track down. By the way, I have another problem: if I set my display background to an image (under KDE or xfce4), then the bottom half of the image gets garbled after resume. Do you observer anything like that? Might this be a sign of something wrong in the X11 driver? (I just use the default Xorg) Jacques Garrigue ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
