Re: Swapfile problem in 6?
Lars Kristiansen wrote: Hello again, I am the me too-guy with console-access. Hi Lars, I'm the one who started this thread, when I could not compile a new kernel after I upgraded to 6 (Pentium-1, 150 MHz, 32 MB Ram). How do you trigger the deadlock? The only way I know of how to trigger the deadlock, is to compile a new kernel and the 'linking kernel' stage will lock-up the PC. With a regular kernel, this takes 2.5 hours until deadlock, but with a fully equipped debug kernel it takes about 8 hours If you have a different (and possibly quicker) way to trigger the deadlock, I would like to try that also on my system. Please let me know. Regards, Rob. - Yahoo! FareChase - Search multiple travel sites in one click. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Swapfile problem in 6?
On Thu, 2005-Nov-17 00:00:03 -0800, Rob wrote:
The only way I know of how to trigger the deadlock, is to compile
a new kernel and the 'linking kernel' stage will lock-up the PC.
With a regular kernel, this takes 2.5 hours until deadlock, but with
a fully equipped debug kernel it takes about 8 hours
When the first deadlock occurs, you have a fully populated set of kernel
objects (though possibly some of them are in the buffer case rather than
on disk). You should be able to quickly reproduce the panic by running:
# cd /usr/obj/usr/src/sys/KERNEL
# make
(Adjust the directory to suit your config name and MAKEOBJDIRPREFIX).
Alternatively, check out the following lines in /usr/src/Makefile.inc1
# -DNO_KERNELCONFIG do not run config in ${MAKE} buildkernel
# -DNO_KERNELCLEAN do not run ${MAKE} clean in ${MAKE} buildkernel
# -DNO_KERNELDEPEND do not run ${MAKE} depend in ${MAKE} buildkernel
--
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: Swapfile problem in 6?
Peter Jeremy wrote: On Thu, 2005-Nov-17 00:00:03 -0800, Rob wrote: The only way I know of how to trigger the deadlock, is to compile a new kernel and the 'linking kernel' stage will lock-up the PC. With a regular kernel, this takes 2.5 hours until deadlock, but with a fully equipped debug kernel it takes about 8 hours When the first deadlock occurs, you have a fully populated set of kernel objects (though possibly some of them are in the buffer case rather than on disk). You should be able to quickly reproduce the panic by running: # cd /usr/obj/usr/src/sys/KERNEL # make I'm doing this right now... Although I have not got into the deadlock yet, I do get these lines in the serial console: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 12333, size: 4096 swap_pager: indefinite wait buffer: bufobj: 0, blkno: 22990, size: 4096 swap_pager: indefinite wait buffer: bufobj: 0, blkno: 22928, size: 4096 swap_pager: indefinite wait buffer: bufobj: 0, blkno: 22625, size: 8192 swap_pager: indefinite wait buffer: bufobj: 0, blkno: 22990, size: 4096 swap_pager: indefinite wait buffer: bufobj: 0, blkno: 22784, size: 8192 swap_pager: indefinite wait buffer: bufobj: 0, blkno: 23233, size: 4096 swap_pager: indefinite wait buffer: bufobj: 0, blkno: 23404, size: 4096 swap_pager: indefinite wait buffer: bufobj: 0, blkno: 23154, size: 4096 A typical snapshot of 'swapinfo' at this time is: Device 1K-blocks UsedAvail Capacity /dev/ad0s1b 398483984039848 100% /dev/md0 13107254136 13107241% Total 170920939767694455% (By the way, notice that the 'Avail' column of /dev/ad0s1b and /dev/md0 is wrong; for Total it's correct. Is this a general bug in 6 or only on my PC? ) Googling on the above swap_pager lines, I found this conversation: http://lists.freebsd.org/pipermail/freebsd-current/2005-September/00.html which claims that DragonFly has fixed this problem. Regards, Rob. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Swapfile problem in 6?
Lars Kristiansen wrote: Hello again, I am the me too-guy with console-access. Hi Lars, I'm the one who started this thread, when I could not compile a new kernel after I upgraded to 6 (Pentium-1, 150 MHz, 32 MB Ram). How do you trigger the deadlock? The only way I know of how to trigger the deadlock, is to compile a new kernel and the 'linking kernel' stage will lock-up the PC. With a regular kernel, this takes 2.5 hours until deadlock, but with a fully equipped debug kernel it takes about 8 hours If you have a different (and possibly quicker) way to trigger the deadlock, I would like to try that also on my system. Please let me know. Hi Rob! swapoff all other swap than md0, which is on the same disk as busy filesystems. Then I run for example: nice +19 portupgrade -frbWp libtool Did you see the debug-output I posted? Did those tell you anything? I do not understand those things. But I do have the debugscreen open after a crash if you want me too run anything. Just glad if I can be of help. -- Lars Regards, Rob. - Yahoo! FareChase - Search multiple travel sites in one click. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel clock for 6-STABLE runs at 1/2 speed in VMware 5.0 - WORKAROUND FOUND
After noticing the problem went away in Safe Mode, and then figuring out what Safe Mode actually does*, I've worked around the problem by disabling the APIC device, which, I gather, forces FreeBSD to use the old-fashioned IRQ timers. This fix will not work if you want to run an SMP kernel in VMWare, I suppose, but I imagine there aren't too many people doing such a thing. Anyhoo: In /boot/loader.conf , add: hint.apic.0.disabled=1 * All currently available documentation for FreeBSD Safe Mode, for those who are interested, is apparently located here: grep -A11 'bootsafekey @' /boot/beastie.4th ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [PATCH] nve(4) locking cleanup
John Baldwin wrote: I have a patch for nve(4) which fixes at least one known LOR in the driver and generally fixes up the locking. If you have an nve(4) card that currently works, please test this patch to make sure it doesn't break anything. If you have an nve(4) card that doesn't work, this patch probably won't help. http://www.FreeBSD.org/~jhb/patches/nve_locking.patch After this patch is applied, I got: nve0: NVIDIA nForce MCP7 Networking Adapter port 0xb400-0xb407 mem 0xec00-0xec000fff irq 20 at device 5.0 on pci0 nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: Ethernet address 00:04:61:fe:fb:7f nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held miibus0: MII bus on nve0 ciphy0: Cicada CS8201 10/100/1000TX PHY on miibus0 nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0: nve_oslockacquire: normal mutex not held nve0: nve_oslockrelease: normal mutex not held nve0:
6-Stable: swapinfo has wrong output?
Hi, I have upgraded to 6-Stable. The swapinfo command gives wrong output: Device1K-blocks UsedAvail Capacity /dev/md0 13107211848 131072 9% I guess, the math should be: 1K-blocks = Used + Avail However, 1K-blocks = Avail, irrespective of what is used. In case of more than one swap device, then the Total line shows the right numbers. Is this a bug? Rob. __ Start your day with Yahoo! - Make it your home page! http://www.yahoo.com/r/hs ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6-Stable: swapinfo has wrong output?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rob wrote: | Hi, | | I have upgraded to 6-Stable. | The swapinfo command gives wrong output: | | Device1K-blocks UsedAvail Capacity | /dev/md0 13107211848 131072 9% | | I guess, the math should be: | 1K-blocks = Used + Avail | | However, 1K-blocks = Avail, irrespective | of what is used. | | In case of more than one swap device, then | the Total line shows the right numbers. | | Is this a bug? Yes - I noticed it because the nagios plug-in ceased to give me sensible numbers - I *always* have 100% swap available ;-) Michael -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) iD8DBQFDfK55iJykeV6HPMURAouiAJwNHf+11/3f4elXIfxi1+ipza9S/QCg/gK8 zMALDxTY9R9MQBDAqI3n9W8= =ZFnw -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Performance problem since updating from 6.0-RELEASE to 6.0-STABLE last friday
Pierre-Luc Drouin wrote: Nate Lawson wrote: Pierre-Luc Drouin wrote: Hajimu UMEMOTO wrote: On Mon, 14 Nov 2005 12:40:36 -0500 Pierre-Luc Drouin [EMAIL PROTECTED] said: pldrouin Yep, smart battery is definately the problem. The performance of my pldrouin laptop is back to normal when I remove the xfce4-battery-plugin. pldrouin acpiconf -i loop reproduces the problem for me too. So it looks like pldrouin there is something wrong in smart battery. The cmbat has similar issue on some laptops. So, acpi_cmbat.c uses cache for retrieval to reduce its influence, and its expiration time is set by hw.acpi.battery.info_expire. However, acpi_smbat.c doesn't use cache. So, I made a patch. Since I don't have a laptop which has smbat, I cannot test it by myself. Please test it and let me know the result. The patch seams to do its job correctly, but it is still very annoying to have the whole computer to freeze for 1 second when the cache expires. What does make the whole system to freeze? Before the code was changed in 6.0-stable, FreeBSD was able to read the battery status without freezing my laptop... I have been running 3 OSes (FreeBSD, Ubuntu and Win XP) on my laptop for a while and never experienced that kind of problem with either Linux or Win XP. I guess there is something wrong in the new code added after 6.0-release. If you have both smbat and cmbat, just disable smbat if you don't like it. Add this to /boot/loader.conf: debug.acpi.disabled=smbat The pause is related to a buggy or slow EC. Caching the values happens to hide it. Do you get pauses with smbat disabled (see above for how to do this)? Can you still get battery status from cmbat? Ok, there is new development. I realized by playing with debug.acpi.disabled=smbat, debug.acpi.disabled=smbat cmbat and debug.acpi.disabled=cmbat, that my laptop battery is not a smbat, but a cmbat. When I played with hw.acpi.battery.info_expire after to have applied the patch for acpi_smbat.c, it was freezing less often because that sysctl variable was shared by both cmbat and smbat. So I can only get battery status from cmbat (disabling cmbat disables the use of acpiconf -i loop). To get the status of my battery via cmbat was working fine up to 6.0-RELEASE (included), but makes my laptop to freeze since I upgraded to 6.0-stable with Nov 10th sources. What change related to cmbat between 6.0-release and 6.0-stable could be causing this? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] Has someone found how to fix this problem in -stable? Thank you ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Page fault, GEOM problem??
Ok, just got this not so very nice error on a RELENG_6_0 box (built from sources this morning, GENERIC kernel minus drivers I dont use): Nov 17 15:35:43 elfi kernel: subdisk10: detached Nov 17 15:35:43 elfi kernel: ad10: detached Nov 17 15:35:43 elfi kernel: unknown: TIMEOUT - READ_DMA retrying (1 retry left) LBA=85720528 Nov 17 15:35:43 elfi kernel: GEOM_MIRROR: Device gm0s1: provider ad10s1 disconnected. Nov 17 15:35:43 elfi kernel: GEOM_MIRROR: Request failed (error=6). ad10s1[WRITE(offset=134356992, length=16384)] Nov 17 15:35:43 elfi kernel: GEOM_MIRROR: Request failed (error=6). ad10s1[WRITE(offset=134373376, length=16384)] Nov 17 15:35:43 elfi kernel: GEOM_MIRROR: Request failed (error=6). ad10s1[WRITE(offset=134438912, length=16384)] Nov 17 15:35:43 elfi kernel: GEOM_MIRROR: Request failed (error=6). ad10s1[WRITE(offset=268591104, length=16384)] Nov 17 15:35:43 elfi kernel: GEOM_MIRROR: Request failed (error=6). ad10s1[WRITE(offset=268607488, length=16384)] Nov 17 15:35:43 elfi kernel: GEOM_MIRROR: Request failed (error=6). ad10s1[WRITE(offset=268623872, length=16384)] Nov 17 15:35:43 elfi kernel: GEOM_MIRROR: Request failed (error=6). ad10s1[WRITE(offset=268640256, length=16384)] Nov 17 15:35:43 elfi kernel: GEOM_MIRROR: Request failed (error=6). ad10s1[WRITE(offset=20151026176, length=2048)] Nov 17 15:35:43 elfi kernel: GEOM_MIRROR: Request failed (error=6). ad10s1[WRITE(offset=32299655680, length=8192)] Nov 17 15:35:43 elfi kernel: GEOM_MIRROR: Request failed (error=6). ad10s1[READ(offset=37363671552, length=16384)] Nov 17 15:35:43 elfi kernel: GEOM_MIRROR: Request failed (error=6). ad10s1[READ(offset=38349087232, length=16384)] Nov 17 15:35:43 elfi kernel: GEOM_MIRROR: Request failed (error=6). ad10s1[READ(offset=45453566464, length=16384)] Nov 17 15:35:43 elfi kernel: GEOM_MIRROR: Request failed (error=6). ad10s1[READ(offset=54459458048, length=131072)] Nov 17 17:59:18 elfi syslogd: kernel boot file is /boot/kernel/kernel Nov 17 17:59:18 elfi kernel: Nov 17 17:59:18 elfi kernel: Nov 17 17:59:18 elfi kernel: Fatal trap 12: page fault while in kernel mode Nov 17 17:59:18 elfi kernel: fault virtual address = 0x48 Nov 17 17:59:18 elfi kernel: fault code = supervisor read, page not present Nov 17 17:59:18 elfi kernel: instruction pointer= 0x20:0xc0506b92 Nov 17 17:59:18 elfi kernel: stack pointer = 0x28:0xd56d7c9c Nov 17 17:59:18 elfi kernel: frame pointer = 0x28:0xd56d7c9c Nov 17 17:59:18 elfi kernel: code segment = base 0x0, limit 0xf, type 0x1b Nov 17 17:59:18 elfi kernel: = DPL 0, pres 1, def32 1, gran 1 Nov 17 17:59:18 elfi kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Nov 17 17:59:18 elfi kernel: current process= 36 (swi4: clock sio) Nov 17 17:59:18 elfi kernel: trap number= 12 Nov 17 17:59:18 elfi kernel: panic: page fault Nov 17 17:59:18 elfi kernel: Uptime: 8h55m1s ad10 and ad6, 2 brand new Maxtor Maxline 300GB SATA, attached to a Promise PDC40518 SATA150 controller, makes a GEOM mirror gm0s1. I've been running this stuff in another test machine (MSI K8N neo Platinum, KT333 chip I believe), and I havent had a single problem. I moved the disks/controllercard to my real server 24 hours ago, with the only apparent problem I seemd to have was this: Nov 17 07:06:12 elfi kernel: xl0: transmission error: 90 Nov 17 07:06:12 elfi kernel: xl0: tx underrun, increasing tx start threshold to 120 bytes Nov 17 07:06:18 elfi kernel: xl0: watchdog timeout Nov 17 07:06:18 elfi kernel: xl0: link state changed to DOWN Nov 17 07:06:18 elfi kernel: vlan5: link state changed to DOWN Nov 17 07:06:20 elfi kernel: xl0: link state changed to UP Nov 17 07:06:20 elfi kernel: vlan5: link state changed to UP Comming and going... these problems just apperade during first 20-30 minutes after boot, then they dissapeared totally (and yes there was plenty of IO on the net going on both during and after these messages). Sometimes i just got the first two messages and nothing happened, but sometimes the watchdog message came and the network died for a minute or so. Here is dmesg from last boot (directly after crash): Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-RELEASE #0: Thu Nov 17 00:49:29 CET 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ELFI ACPI APIC Table: ASUS A7V333 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Athlon(TM) XP 1900+ (1599.56-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x662 Stepping = 2 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE, MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE AMD Features=0xc0480800SYSCALL,MP,MMX+,3DNow+,3DNow real memory = 536854528 (511 MB) avail memory = 516014080 (492 MB) ioapic0:
Smart Array P600 Controller Supported ... ?
Either at the 4.x or 6.x versions ... ? I'm looking at an HP 1U server that has this included ... will this be a problem? Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6-Stable: swapinfo has wrong output?
On Thu, 17 Nov 2005, Rob wrote: I have upgraded to 6-Stable. The swapinfo command gives wrong output: Device1K-blocks UsedAvail Capacity /dev/md0 13107211848 131072 9% I guess, the math should be: 1K-blocks = Used + Avail However, 1K-blocks = Avail, irrespective of what is used. In case of more than one swap device, then the Total line shows the right numbers. Is this a bug? Very much so. I've committed a fix to HEAD as pstat.c:1.96, which I'll MFC to 6-STABLE in a few days. Thanks! Robert N M Watson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg-clients conflicts with xterm (patch)
Joel Hatton wrote: What was the rationale behind changing this behaviour for 206_1? That xterm should install as xterm and not xterm-static. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
PERFMON with Athlon breaks ata.
A custom kernel compiled with options PERFMON and cputype=athlon when ran on an athlon causes ATA to not probe devices on FreeBSD 6.0-RELEASE. dmesg seems normal except the ata probe is never done, so the only boot devices available is the floppy. Just something I noticed in passing, not opening a PR since I'll never follow this up. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Swapfile problem in 6?
--- Peter Jeremy [EMAIL PROTECTED] wrote: Basically, wait until your system deadlocks. BREAK into DDB. As a start, run 'show lockedvnods', 'ps'. My guess is that you'll see a lock that has a number of waiters which is probably the culprit. Use 'panic' to get a crashdump and then you can use kgdb to rummage around once you reboot If in doubt, post the output from the above commands here and someone will hopefully provide further input. The output is here: http://surfion.snu.ac.kr/~lahaye/swapfile.txt A swapfile is only swap device: /swapfile of 128 MB on /dev/ad0s1a as /dev/md0 At time of deadlock: swapdevice used 13% Serial console gets exactly this line every few seconds: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 4317, size: 4096 Do you understand this? Rob. __ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Swapfile problem in 6?
On Thu, Nov 17, 2005 at 02:52:12PM -0800, Rob wrote: --- Peter Jeremy [EMAIL PROTECTED] wrote: Basically, wait until your system deadlocks. BREAK into DDB. As a start, run 'show lockedvnods', 'ps'. My guess is that you'll see a lock that has a number of waiters which is probably the culprit. Use 'panic' to get a crashdump and then you can use kgdb to rummage around once you reboot If in doubt, post the output from the above commands here and someone will hopefully provide further input. The output is here: http://surfion.snu.ac.kr/~lahaye/swapfile.txt A swapfile is only swap device: /swapfile of 128 MB on /dev/ad0s1a as /dev/md0 At time of deadlock: swapdevice used 13% Serial console gets exactly this line every few seconds: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 4317, size: 4096 Do you understand this? I commented on it elsewhere in this thread. Kris pgpeguxnEhKqJ.pgp Description: PGP signature
Re: Swapfile problem in 6?
--- Kris Kennaway [EMAIL PROTECTED] wrote: I commented on it elsewhere in this thread. Do you mean your comment on the swap_pager error: Quote: AFAICT that is just a trigger-happy timer..it's supposed to detect when a swap operation took too long to complete, but it also triggers on swapfiles since they're so much less efficient (i.e. slower) than swapping onto a bare device. EndQuote. Remains the question: using this swapfile always worked very well with 5-Stable, but suddenly with 6 I run into these troubles. I hoped that the debugger output made some sense to an expert as to why this happens with 6, but never with 5 Rob. __ Start your day with Yahoo! - Make it your home page! http://www.yahoo.com/r/hs ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Swapfile problem in 6?
On Thu, Nov 17, 2005 at 04:33:50PM -0800, Rob wrote: --- Kris Kennaway [EMAIL PROTECTED] wrote: I commented on it elsewhere in this thread. Do you mean your comment on the swap_pager error: Quote: AFAICT that is just a trigger-happy timer..it's supposed to detect when a swap operation took too long to complete, but it also triggers on swapfiles since they're so much less efficient (i.e. slower) than swapping onto a bare device. EndQuote. Right: harmless warning not error. Remains the question: using this swapfile always worked very well with 5-Stable, but suddenly with 6 I run into these troubles. I hoped that the debugger output made some sense to an expert as to why this happens with 6, but never with 5 Give it a little time for someone to take a look. Kris pgpRhAJFn7wpW.pgp Description: PGP signature
4.8 alternate system clock has died error
Hello all, I've been digging through Google for more information on this. I have a 4.8 box that's been up for about 430 days. In the last week or so, top and ps have started reporting all CPU usage numbers as zero, and running systat -vmstat results in the message The alternate system clock has died! Reverting to ``pigs'' display. I've found instances of this message in the archives for some 3.x users, some pre 4.8 users and some 5.3 users. There were a number of suggestions including a patch if pre-4.8, sending init a HUP, and setting the following sysctl mib: kern.timecounter.method: 1. I'm already at 4.8-p24, so I did not look into patching anything, and HUP'ing init and setting the sysctl mib does not seem to have any effect. I'm not quite ready to believe that some hardware has actually failed. Perhaps due to the long uptime something has rolled over? Let me know what info you would like, I can supply anything. I'm following this with some mainboard info from dmidecode and a full dmesg. Thanks, Charles dmidecode: Handle 0x0002 DMI type 2, 8 bytes. Base Board Information Manufacturer: Tyan Product Name: S2462 THUNDER K7 Version: EVT1 Serial Number: dmesg: Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.8-RELEASE-p24 #0: Sun Sep 19 08:44:43 GMT 2004 root@:/usr/obj/usr/src/sys/XENA Timecounter i8254 frequency 1193182 Hz CPU: AMD Athlon(tm) MP 1600+ (1393.79-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x662 Stepping = 2 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE AMD Features=0xc048MP,AMIE,DSP,3DNow! real memory = 1073676288 (1048512K bytes) avail memory = 1041649664 (1017236K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040010, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040010, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel kernel at 0xc035e000. Preloaded userconfig_script /boot/kernel.conf at 0xc035e09c. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 268435454 entries at 0xc00fdef0 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard IOAPIC #0 intpin 19 - irq 2 IOAPIC #0 intpin 16 - irq 5 IOAPIC #0 intpin 17 - irq 9 IOAPIC #0 intpin 18 - irq 10 pci0: PCI bus on pcib0 agp0: AMD 762 host to AGP bridge mem 0xfc00-0xfc000fff,0xf800-0xfbff at device 0.0 on pci0 pcib1: PCI to PCI bridge (vendor=1022 device=700d) at device 1.0 on pci0 pci1: PCI bus on pcib1 isab0: PCI to ISA bridge (vendor=1022 device=7410) at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: AMD 766 ATA100 controller port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 chip0: PCI to Other bridge (vendor=1022 device=7413) at device 7.3 on pci0 pci0: OHCI USB controller at 7.4 irq 2 asr0: Adaptec Caching SCSI RAID mem 0xf600-0xf7ff irq 5 at device 8.0 on pci0 asr0: major=154 asr0: ADAPTEC 2110S FW Rev. 380E, 1 channel, 256 CCBs, Protocol I2O pcib2: PCI to PCI bridge (vendor=1044 device=a500) at device 8.1 on pci0 pci2: PCI bus on pcib2 ahc0: Adaptec aic7899 Ultra160 SCSI adapter port 0x1000-0x10ff mem 0xf4001000-0xf4001fff irq 5 at device 13.0 on pci0 aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs ahc1: Adaptec aic7899 Ultra160 SCSI adapter port 0x1400-0x14ff mem 0xf4002000-0xf4002fff irq 9 at device 13.1 on pci0 aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs pci0: ATI Mach64-GR graphics accelerator at 14.0 xl0: 3Com 3c980C Fast Etherlink XL port 0x1c00-0x1c7f mem 0xf4004000-0xf400407f irq 10 at device 15.0 on pci0 xl0: Ethernet address: 00:e0:81:20:07:06 miibus0: MII bus on xl0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl1: 3Com 3c980C Fast Etherlink XL port 0x1c80-0x1cff mem 0xf4004400-0xf400447f irq 2 at device 16.0 on pci0 xl1: Ethernet address: 00:e0:81:20:07:07 miibus1: MII bus on xl1 ukphy1: Generic IEEE 802.3u media interface on miibus1 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto orm0: Option ROMs at iomem 0xc-0xc7fff,0xc8000-0xc87ff,0xc8800-0xc8fff,0xc 9000-0xcefff,0xe-0xe3fff on isa0 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console at flags 0x100 on
Re: PERFMON with Athlon breaks ata.
A custom kernel compiled with options PERFMON and cputype=athlon when ran on an athlon causes ATA to not probe devices on FreeBSD 6.0-RELEASE. dmesg seems normal except the ata probe is never done, so the only boot devices available is the floppy. AFAIR, PERFMON only supports Pentium and Pentium Pro CPUs. -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Your DriverGuide.com Inquiry
Greetings from DriverGuide.com. We're sorry. You replied to a notification-only address that cannot accept incoming e-mail. But that's OK--this automated response will direct you to the right place at DriverGuide.com to answer your question. Many common questions are answered in our FAQ, please visit: http://members.driverguide.com/index.php?action=faq If you have already registered but have not received your membership email, visit: http://members.driverguide.com/ums/index.php?action=rs If you have already registered but forgotten your password, visit: http://members.driverguide.com/ums/index.php?action=fd If you are having trouble with registration, visit: http://members.driverguide.com/index.php?action=feedbackid=27s=1 For all other questions or inquiries, visit: http://members.driverguide.com/index.php?action=feedback Thanks for using DriverGuide.com! Sincerely, DriverGuide team http://www.DriverGuide.com To unsubscribe from DriverGuide, click on this link: http://members.driverguide.com/ums/[EMAIL PROTECTED] P.S. You received this message because DriverGuide.com received a message with the following headers: From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Status Date: Fri, 18 Nov 2005 15:28:55 +0800 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
need help for ATM support on Freebsd 6.
Hi, I need help about ATM support on FreeBSD 6. The configuration was working on FreeBSD 5 Stable but was not working 6 stable. I have FORE PCA-200E ATM PCI card. And my kernel config as follows: # ATM Devices device atm device hfa # options NATM # ATM Related Settings ... options ATM_CORE#core ATM protocol family options ATM_SIGPVC #SIGPVC signalling manager options ATM_IP Can you point a way to correct this situation. I can use the following command till ifconfig .. # ATM Ayarlari - Basla /sbin/fore_dnld -d /etc /sbin/atm set netif hfa0 ni 4 /sbin/atm attach hfa0 sigpvc /sbin/ifconfig ni0 10.175.16.130 netmask 255.255.255.252 up and it just dumps and reboots. The error message is follows: Nov 18 08:47:55 nrouter savecore: reboot after panic: ipatm_nifstat: setaddr missing ip_nif Nov 18 08:47:55 nrouter savecore: writing core to vmcore.1 If needed I could supply additional data, also. Thanks in advance. Husnu Demir. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Why device sk (PCI Gigabit Ethernet) cannot use polling?
Hi, The sk device has no polling support, neither in 5 nor in 6. Is there a particular reason (maybe because it's a Gigabit device) ? Or is polling not supported because it simply has not yet been coded? If so, would it be straightforward to add the code? Thanks, Rob. __ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Why device sk (PCI Gigabit Ethernet) cannot use polling?
Hi, The sk device has no polling support, neither in 5 nor in 6. Is there a particular reason (maybe because it's a Gigabit device) ? Or is polling not supported because it simply has not yet been coded? If so, would it be straightforward to add the code? Thanks, Rob. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
