xl0 watchdog timeout?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Should I use device polling or there is another solution for this? dmesg: ... CPU: Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz (2135.06-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 Features=0xbfebfbff Features2=0xe3bd AMD Features=0x2010 AMD Features2=0x1 Cores per package: 2 ... xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xcc00-0xcc7f mem 0xfeaffc00-0xfeaffc7f irq 22 at device 1.0 on pci5 ... Nov 11 02:31:37 hub kernel: xl0: watchdog timeout Nov 11 02:31:37 hub kernel: xl0: link state changed to DOWN Nov 11 02:31:40 hub kernel: xl0: link state changed to UP Nov 11 10:39:46 hub kernel: xl0: watchdog timeout Nov 11 10:39:46 hub kernel: xl0: link state changed to DOWN Nov 11 10:39:48 hub kernel: xl0: link state changed to UP Nov 11 17:43:35 hub kernel: xl0: watchdog timeout Nov 11 17:43:35 hub kernel: xl0: link state changed to DOWN Nov 11 17:43:38 hub kernel: xl0: link state changed to UP Nov 11 23:51:50 hub kernel: xl0: watchdog timeout Nov 11 23:51:50 hub kernel: xl0: link state changed to DOWN Nov 11 23:51:52 hub kernel: xl0: link state changed to UP # uname -srm FreeBSD 6.2-STABLE i386 #pciconf -lv [EMAIL PROTECTED]:1:0: class=0x02 card=0x100010b7 chip=0x920010b7 rev=0x74 hdr=0x00 vendor = '3COM Corp, Networking Division' device = '3C905C-TX Fast EtherLink for PC Management NIC' class = network subclass = ethernet # vmstat -i interrupt total rate irq1: atkbd0 94 0 irq6: fdc0 7 0 irq19: uhci3+ 23496569 56 irq21: fwohci0 1 0 irq22: xl0 13068844 31 cpu0: timer795793798 1926 cpu1: timer795763796 1926 Total 1628123109 3941 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFHOA8fxJBWvpalMpkRAlZZAKCRjwe+fI284p6/hmF5lZk+UoR/AwCfb1zR phCE+/enUFXftI21+2TGHTA= =ijUo -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]"
[SiS180] SATA drives are not detected on >= 6.0
Hi, SATA drives on SiS 180 SATA150 (ASUS P4S800D mobo) controller are not detected on any release > 6.0, though they work on 5.5. I've attached dmesg from 5.5 and 7.0-BETA2 in case it may be helpful. It's kinda production system, so I couldn't play much with it. Any suggestions, hints on how to make system recognize drives are very appreciated. TIA, Yuri Copyright (c) 1992-2006 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 5.5-SECURITY #0: Thu Apr 26 11:43:48 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xc0a46000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0a4621c. Calibrating clock(s) ... i8254 clock: 1193254 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 2400690582 Hz CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2400.69-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 Features=0xbfebfbff real memory = 536018944 (511 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x0010 - 0x003f, 3145728 bytes (768 pages) 0x00c25000 - 0x1f602fff, 513662976 bytes (125406 pages) avail memory = 514846720 (490 MB) Table 'FACP' at 0x1ff30290 Table 'APIC' at 0x1ff30390 MADT: Found table at 0x1ff30390 APIC: Using the MADT enumerator. MADT: Found CPU APIC ID 0 ACPI ID 1: enabled MADT: Found CPU APIC ID 129 ACPI ID 2: disabled ACPI APIC Table: bios32: Found BIOS32 Service Directory header at 0xc00f bios32: Entry = 0xf0010 (c00f0010) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0x31 pnpbios: Found PnP BIOS data at 0xc00f68d0 pnpbios: Entry = f:74ca Rev = 1.0 Other BIOS signatures found: APIC: CPU 0 has ACPI ID 1 MADT: Found IO APIC ID 1, Interrupt 0 at 0xfec0 ioapic0: Changing APIC ID to 1 ioapic0: Routing external 8259A's -> intpin 0 ioapic0: intpin 0 -> ExtINT (edge, high) ioapic0: intpin 1 -> ISA IRQ 1 (edge, high) ioapic0: intpin 2 -> ISA IRQ 2 (edge, high) ioapic0: intpin 3 -> ISA IRQ 3 (edge, high) ioapic0: intpin 4 -> ISA IRQ 4 (edge, high) ioapic0: intpin 5 -> ISA IRQ 5 (edge, high) ioapic0: intpin 6 -> ISA IRQ 6 (edge, high) ioapic0: intpin 7 -> ISA IRQ 7 (edge, high) ioapic0: intpin 8 -> ISA IRQ 8 (edge, high) ioapic0: intpin 9 -> ISA IRQ 9 (edge, high) ioapic0: intpin 10 -> ISA IRQ 10 (edge, high) ioapic0: intpin 11 -> ISA IRQ 11 (edge, high) ioapic0: intpin 12 -> ISA IRQ 12 (edge, high) ioapic0: intpin 13 -> ISA IRQ 13 (edge, high) ioapic0: intpin 14 -> ISA IRQ 14 (edge, high) ioapic0: intpin 15 -> ISA IRQ 15 (edge, high) ioapic0: intpin 16 -> PCI IRQ 16 (level, low) ioapic0: intpin 17 -> PCI IRQ 17 (level, low) ioapic0: intpin 18 -> PCI IRQ 18 (level, low) ioapic0: intpin 19 -> PCI IRQ 19 (level, low) ioapic0: intpin 20 -> PCI IRQ 20 (level, low) ioapic0: intpin 21 -> PCI IRQ 21 (level, low) ioapic0: intpin 22 -> PCI IRQ 22 (level, low) ioapic0: intpin 23 -> PCI IRQ 23 (level, low) MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 -> intpin 2 ioapic0: intpin 2 trigger: edge ioapic0: intpin 2 polarity: high MADT: Interrupt override: source 9, irq 9 ioapic0: intpin 9 trigger: level ioapic0: intpin 9 polarity: low ioapic0 irqs 0-23 on motherboard cpu0 BSP: ID: 0x VER: 0x00050014 LDR: 0x0100 DFR: 0x0fff lint0: 0x00010700 lint1: 0x0400 TPR: 0x SVR: 0x01ff wlan: <802.11 Link Layer> random: io: mem: Pentium Pro MTRR support enabled null: npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: [MPSAFE] pci_open(1):mode 1 addr port (0x0cf8) is 0x800010c8 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=80] is there (id=06551039) pcibios: BIOS version 2.10 Found $PIR table, 10 entries at 0xc00f67a0 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs embedded02A 0x41 3 4 5 7 10 11 12 14 15 embedded02B 0x42 3 4 5 7 10 11 12 14 15 embedded02C 0x43 3 4 5 7 10 11 12 14 15 embedded02D 0x44 3 4 5 7 10 11 12 14 15 embedded03A 0x60 3 4 5 7 10 11 12 14 15 embedded03B 0x61 3 4 5 7 10 11 12 14 15 embedded03C 0x62 3 4 5 7 10 11 12 14 15 embedded03D 0x63 3 4 5 7 10 11 12 14 15 embedded05A 0x42 3 4 5 7 10 11 12 14 15 embedded01A 0x41 3 4 5 7 10 11 12 14 15 embedded01B 0x42 3 4 5 7 10 11 12 14 15 embedded01C 0x43 3 4 5 7 10 11 12 14 15 embedded01D 0x44 3 4 5 7 10 11 12 14 15 embedded04A 0x44 3 4 5 7 10 11 12 14 15 slot 1 08A 0x41 3 4 5 7 10 11 12 14 15 slot 1 08B 0x42 3 4 5 7 10 11 12 14 15 slot 1 08C 0
Re: 7.0-BETA2 Panic after ifconfig
Hi Robert ! > If you run this from single-user mode, do you get the same result? What is > the general network configuration of the system, and what sorts of services > are running? This is my laptop there is no services running... I use ipfw, natd, bridge and tap to work with qemu > > Could you confirm that you aren't using any third party kernel modules or > modules from ports, or that if you are, they've been update following the > upgrade to matching source? I had a long list of loadable modules, follow my loader.conf cpufreq_load="YES" snd_ich_load="YES" if_iwi_load="YES" iwi_bss_load="YES" iwi_ibss_load="YES" iwi_monitor_load="YES" wlan_load="YES" firmware_load="YES" wlan_ccmp_load="YES" wlan_tkip_load="YES" wlan_wep_load="YES" wlan_scan_sta_load="YES" ucom_load="YES" uftdi_load="YES" geom_label_load="YES" uvscom_load="YES" # # qemu modules if_tap_load="YES" kqemu_load="YES" bridge_load="YES" aio_load="YES" ipfw_load="YES" ipdivert_load="YES" # # kern.maxdsiz="1073741824" # 1GB kern.dfldsiz="1073741824" # 1GB kern.maxssiz="134217728" # 128MB # zfs vm.kern_size="768M" vm.kern_size_max="768M" legal.intel_iwi.license_ack=1 Before read your message I updated the system again (csup, buildworld, buildkernel, installkernel, installworld) and now I can reproduce the panic anymore. Thank you for your attention! Regards, ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [EMAIL PROTECTED]: Re: openpty() and jail in RELENG_7]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Christian, Christian S.J. Peron wrote: > Please try the attached patch. I have committed this to head > and it somehow slipped through the cracks in terms of an MFC > > (patch /etc/defaults/devfs.rules) Do we need to expose /dev/ptmx as well? A glance at the code seems to be necessary if we want to use pts, but I need to dig deeper to confirm. Cheers, - -- Xin LI <[EMAIL PROTECTED]> http://www.delphij.net/ FreeBSD - The Power to Serve! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFHONWxhcUczkLqiksRAhJmAKCv66+cvroD0mrTJcB5JII855dPtQCfZ0cj iIQ3fcYOtNY4m213YS8UNc4= =SGEr -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: rrdtool performance tuning (fwd)
> Dear colleagues, > > any hints to tune rrdtool with ~30k rrd files (approx 2k target > devices)? > > machine is mostly IO-bound, showing 100% disk load with 8 or sometimes > even 3 mB/s, 300-400 tps (it's 2 SATA300 disks in gmirror) Long and short of it, rrd sucks. I'm not sure whats sucks worse though, the architecture, the code, the data format, the fact that you have to exec open seek seek seek seek close for every one of those rrd files, or the 1 character long command line you get to throw at it to generate complex graphs. :) I was working on a complete rewrite of the rrd update code a couple months back, but got distracted by other bigger projects and haven't had time to finish it up. If anyone is interested, there is some alpha code (aka do not run this on any .rrd files you value) at: http://sourceforge.net/projects/librrd/ The goal was to implement an efficient C API which wouldn't open/close the file with every cycle, use entirely mmap() (in stock code even when you say to use mmap, there is still a ton of legacy code which seeks around unnecessarily), and implement fine grained read/write locking for concurrency. Personally though, I suspect the vast majority of the speed improvements would come from just general code improvement rather than any specific technique (e.g. removing 5 levels of indirection which are completely unnecessary to accomplish a step, and which only exist because the code is a running hack based on small contributions that "make it work" from 100 different people who primarily write perl, all without any overall design). Pretty sure the remaining bug is in the CDP (consolidated data points) code which creates missing data points in the event you've waited longer than a PDP interval between updates. But more to the point, everything in rrd_update_cdp() is something I haven't yet reverse engineered to figure out what the actual goal is. If you can figure this out, you can probably rewrite that entire block in 1/5th the code, like everywhere else. :) Please let me know if there is any interest in this, I'll be happy to help provide info on what I've done so far, until I find more free time. :) -- Richard A Steenbergen <[EMAIL PROTECTED]> http://www.e-gerbil.net/ras GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Jails and PF states on locahost
No-one with any clues or recommendations? :/ CCing to -stable too..
Thanks
--
Johan Ström
Stromnet
[EMAIL PROTECTED]
http://www.stromnet.se/
On Oct 29, 2007, at 09:37 , Johan Ström wrote:
Hello
I got a FreeBSD 6.2 box running a few jails, with a pretty strict
PF ruleset. I got a problem with traffic between two of the jails.
Both have public IPs (one of them have two using the jail-multiple-
ip-patch). The problem I have is when they are to talk with each
other. First let med describe the PF ruleset (somewhat stripped
down but this should be the relevant stuff)
jail1=xx.xx.xx.131
jail2a=xx.xx.xx.133
jail2b=xx.xx.xx.134
scrub in all
block drop in log
# base system talk to itself
pass in on lo0 inet from 127.0.0.1 to 127.0.0.1
# all can talk out
pass out on em0 proto tcp flags S/SA modulate state
pass out on em0 proto udp keep state
# jails talk to them selfs
pass in on lo0 inet from $jail1 to $jail1
pass in on lo0 inet from {$jail2a $jail2b} to {$jail2a $jail2b}
# let smtp in on jail1
pass in on {lo0 em0} inet proto tcp from any to $jail1 port smtp
flags S/SA modulate state
Okay, so the problem occurs when jail2 shall talk to jail1 on port
25 (smtp). From the above rules, when the traffic leaves jail2
(traffic comes from $jail2b it seems) it should match the last rule
and create a state. And so it does!
self tcp xx.xx.xx:25 <- xx.xx.xx.134:57557 SYN_SENT:ESTABLISHED
[3014249759 + 65536](+2074393365) wscale 1 [4121000179 + 65536]
(+541973245) wscale 1
age 00:01:03, expires in 00:00:01, 7:10 pkts, 384:640 bytes
So the SYN arives at $jail1, but the SYNACK fails to go back to
$jail2b (where the state should let the packet back in?), which is
also seen in the following row from pflog0:
09:30:34.370402 rule 1/0(match): block in on lo0: (tos 0x0, ttl
64, id 35618, offset 0, flags [DF], proto: TCP (6), length: 64)
xx.xx.xx.131.25 > xx.xx.xx.134.57557: S 793675827:793675827(0) ack
4121000179 win 65535
So.. What have I missed? The state is created but it doesnt seem to
match enough bytes or something? 384:640 matched packets, so et
matches in both directions?
Any clues are welcome! Thanks
--
Johan Ström
Stromnet
[EMAIL PROTECTED]
http://www.stromnet.se/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-pf
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Source upgrade from 5.5 to 6.X not safe?
On 11/11/2007, [LoN]Kamikaze <[EMAIL PROTECTED]> wrote: > > If a binary/library that is currently used gets removed/replaced, it will be > copied to memory. The process will not even recognize this. Only restarting > the process will remove the old version from memory and cause the new one to > be used. I thought every OS did it like that, so I'm surprised that there are > systems causing problems in this case. Wha, when did that happen? I was always under the impression that binaries/libraries were demand paged in and referenced as a VM object via VFS; you could unlink/rename the file and the currently open reference would still be valid. (Admittedly I looked at this last in 4.x VFS.) Doing a rename-replace-unlink shouldn't clobber existing binaries that are using the library. Doing an -overwrite- of the existing file will cause exciting results. man install. :) Adrian -- Adrian Chadd - [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Upgrading from FreeBSD 5.4 to 5.5 STABLE
Hello, I am trying to update my version of FreeBSD from 5.4 to 5.5-STABLE. This is one of the many things I've yet to get my feet wet with yet, and so I'm not entirely sure what it is I am doing. I've made a backup of my most critical work. Some links I've found describing this process: 1. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html 2. http://www.nabble.com/Upgrading-FreeBSD-Questions-t4716949.html So far I've run cvsup with a line in it: *default tag=RELENG_5_5_0_RELEASE After a long time it said that it finished successfully. Regardless, I'm not sure if the line I used is correct to get 5.5 STABLE. Then I ran: % make buildworld ===> gnu/usr.bin/cvs/contrib sed -e 's,@CSH@,/bin/csh,' -e '[EMAIL PROTECTED]@,/usr/bin/perl,' /usr/src/gnu/usr.bin/cvs/contrib/../../../../contrib/cvs/contrib/Makefile.in > Makefile "Makefile", line 15: Need an operator make: fatal errors encountered -- cannot continue *** Error code 1 Stop in usr/src/gnu/usr.bin/cvs. *** Error code 1 Stop in usr/src/gnu/usr.bin. *** Error code 1 Stop in usr/src/gnu. *** Error code 1 Stop in usr/src. *** Error code 1 Stop in usr/src. *** Error code 1 Stop in usr/src. *** Error code 1 Stop in usr/src. Unfortunately, I typed all that out by hand and so it is quite possible there is a typo or two, but that is the general jist of it all. Is there someone who knows what is going on with this? All answers/tips are greatly appreciated! Nic R. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading from FreeBSD 5.4 to 5.5 STABLE
On Tuesday 13 November 2007 06:08:10 Nic Reveles wrote: > Hello, > > I am trying to update my version of FreeBSD from 5.4 to 5.5-STABLE. This > is one of the many things I've yet to get my feet wet with yet, and so I'm > not entirely sure what it is I am doing. I've made a backup of my most > critical work. > > Some links I've found describing this process: > 1. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html > 2. http://www.nabble.com/Upgrading-FreeBSD-Questions-t4716949.html > > So far I've run cvsup with a line in it: > *default tag=RELENG_5_5_0_RELEASE > > After a long time it said that it finished successfully. Regardless, I'm > not sure if the line I used is correct to get 5.5 STABLE. No, correct tag for 5-STABLE is RELENG_5 (or, if by "5.5 STABLE" you mean 5.5 with security patches, tag should be RELENG_5_5). See http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html > > Then I ran: > % make buildworld > > ===> gnu/usr.bin/cvs/contrib > sed -e 's,@CSH@,/bin/csh,' -e '[EMAIL PROTECTED]@,/usr/bin/perl,' > /usr/src/gnu/usr.bin/cvs/contrib/../../../../contrib/cvs/contrib/Makefile.. >in > Makefile "Makefile", line 15: Need an operator > make: fatal errors encountered -- cannot continue > *** Error code 1 > > Stop in usr/src/gnu/usr.bin/cvs. > *** Error code 1 > > Stop in usr/src/gnu/usr.bin. > *** Error code 1 > > Stop in usr/src/gnu. > *** Error code 1 > > Stop in usr/src. > *** Error code 1 > > Stop in usr/src. > *** Error code 1 > > Stop in usr/src. > *** Error code 1 > > Stop in usr/src. > I've seen this error before, it has something to do with timestamps in src/contrib/cvs (I've copied source tree using cp). Try removing /usr/src/contrib/cvs directory and cvsup again. > Unfortunately, I typed all that out by hand and so it is quite possible > there is a typo or two, but that is the general jist of it all. Is there > someone who knows what is going on with this? All answers/tips are greatly > appreciated! > > Nic R. Yuri ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
7.0 beta2 vs. SATA DVD drive
Hi, I was trying to install 7.0 beta 2 on a system that has a SATA attached DVD drive. The system starts to the point where it waits for the SCSI devices to initialize. After that it starts reading from the install media and constantly gets read timeouts == no installation possible. Does anybody else see this problem? Tyan K8W (S2825), 2xOpteron 250, 2GB RAM 3ware 9500S-4LP with 2 WD disks LSI-1030 (mpt) with tape drive onboard SATA Controller: SiI 3114 only optical drive is a SATA DVD-Burner The problem occurs with 7.0b2 i386 and amd64. 6.2 RELEASE installs without problems, so I guess it is a bug?! Uwe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Source upgrade from 5.5 to 6.X not safe?
Adrian Chadd wrote: > On 11/11/2007, [LoN]Kamikaze <[EMAIL PROTECTED]> wrote: >> If a binary/library that is currently used gets removed/replaced, it will be >> copied to memory. The process will not even recognize this. Only restarting >> the process will remove the old version from memory and cause the new one to >> be used. I thought every OS did it like that, so I'm surprised that there are >> systems causing problems in this case. > > Wha, when did that happen? I was always under the impression that > binaries/libraries were demand paged in and referenced as a VM object > via VFS; you could unlink/rename the file and the currently open > reference would still be valid. I didn't know that binaries and libraries keep a reference to the file they were created from. Anyway, to the user the whole thing is transparent. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: amrd disk performance drop after running under high load
Hi. Panagiotis Christias wrote: In the "good" case you are getting a much higher interrupt rate but with the data you provided I can't tell where from. You need to run vmstat -i at regular intervals (e.g. every 10 seconds for a minute) during the "good" and "bad" times, since it only provides counters and an average rate over the uptime of the system. Now I'm running 10-process lighttpd and the problem became no so big. I collected interrupt stats and it shows no relation beetween ionterrupts and slowdowns. Here is it: http://83.167.98.162/gprof/intr-graph/ Also I have similiar statistics on mutex profiling and it shows there's no problem in mutexes. http://83.167.98.162/gprof/mtx-graph/mtxgifnew/ I have no idea what else to check. I don't know what this graph is showing me :) When precisely is the system behaving poorly? what is your RAID controller configuration (read ahead/cache/write policy)? I have seen weird/bogus numbers (~100% busy) reported by systat -v when read ahead was enabled on LSI/amr controllers. ** Existing Logical Drive Information By LSI Logic Corp.,USA ** [Note: For SATA-2, 4 and 6 channel controllers, please specify Ch=0 Id=0..15 for specifying physical drive(Ch=channel, Id=Target)] Logical Drive : 0( Adapter: 0 ): Status: OPTIMAL --- SpanDepth :01 RaidLevel: 5 RdAhead : Adaptive Cache: DirectIo StripSz :064KB Stripes : 6 WrPolicy: WriteBack Logical Drive 0 : SpanLevel_0 Disks Chnl Target StartBlock Blocks Physical Target Status -- -- -- -- 0 000x 0x22ec ONLINE 0 010x 0x22ec ONLINE 0 020x 0x22ec ONLINE 0 030x 0x22ec ONLINE 0 040x 0x22ec ONLINE 0 050x 0x22ec ONLINE I tried to run with disabled Read-ahead, but it didn't help. With best regards, Alexey Popov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
