Re: Unable to boot 9 stable/release on HP EliteBook 8560p
On Jun 18, 2012 9:34 PM, "Matthias Gamsjager" wrote: > > On Mon, Jun 18, 2012 at 1:38 PM, Quentin Schwerkolt < > develloper.u...@hotmail.fr> wrote: > > > I have had a similar problem with my HP Elitebook 8540p and I solved it > > by moving the sata controller from ahci to ide in the bios. > > I've had several problems with Linux on HP machines lately that have been fixed with BIOS upgrades. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Load when idl on stable
On Jun 1, 2012 11:27 PM, "Albert Shih" wrote: > > Hi > > I already post a message about my problem > > I've three PC, all are Dell. Two laptop and one desktop. > > All run FreeBSD 9-Stable amd64 > > Since 1 or 2 months I notice the load is never drop down 0.8-0.9 event when > nothing running but only on those laptop. > > I update today my desktop to last csup src and everything is fine on the > desktop. > > On both laptop the load is still at 0.8 - 0.9 > > And in same time the usb mouse on the laptop stop working meaning I can > use the touchpad, but if I plug a usb mouse, the kernel see the device but > the mouse not working on xorg. > > Is' not block my work so I can live with that. I just want report those > problems. > > Regards. > > JAS Is this due to a high rate of interrupts ? i.e. can you see this with "systat -vm 1" with a large number in the "intr" field. If yes, run "vmstat -i" to see what interrupt is being hit. Then tell us what hardware is on that irq (from grep irq /var/run/dmesg.boot). Matt ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: top not restoring terminal echo/icanon correctly
On Apr 18, 2012 3:54 AM, "Jeremy Chadwick" wrote: > > (Please keep me CC'd as I'm not subscribed to the list) > > I'd like to request that folks running RELENG_8 (and RELENG_9, though I > do not use it) please check the behaviour of their terminal after each > of following commands are run (check terminal after each command): > > top -a (press "q" after 1 screen refresh) > top -b > > If you find that your input characters in your shell aren't being echo'd > back after one of the above commands, blindly type "stty icanon echo" > and hit and things should be back to normal. > > What I'm looking for is confirmation from others of the problem. > > Also very important: please provide uname -a output, specifically world > rebuild date. It greatly matters, because a commit was recently done > where now -b functions fine (was previously busted in this way), but now > -a behaves like -b did. So src/world date matters. Both commands work fine with no terminal problems. This is when connected to the machine via SSH from an Android 4.0.3 device running ConnectBot. $ uname -a FreeBSD nas 9.0-STABLE FreeBSD 9.0-STABLE #11 r233966: Sat Apr 7 13:09:45 CST 2012 root@nas:/usr/obj/usr/src/sys/GENERIC amd64 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: kernel panic while detecting cpu in FreeBSD 9
On Apr 18, 2012 2:23 AM, "Chad C" wrote: > > The first suggestion from a forum poster was bad memory but I swapped out the memory and still received the panics. Also tested the memory with memtest86+ and the bios memory test feature. Both reported no errors. I finally was able to get it to boot and install by breaking to the loader prompt and typing "kern.smp.disabled=1". But the installed system also panics at the same point during boot and the only way to get it to boot is by disabling smp at the loader prompt. > Please update your BIOS/UEFI and try again. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 157k interrupts per second causing 60% CPU load on idle system
On Apr 16, 2012 5:42 AM, "Ronald Klop" wrote: > > On Sun, 15 Apr 2012 15:09:34 +0200, Matt Thyer wrote: > >> On Apr 15, 2012 6:27 PM, "Ronald Klop" wrote: >>> >>> >>>> The problem does not occur with 9-STABLE. >>>> >>>> Who knows what the problem was ? USB maybe ? >>> >>> >>> >>> Do you still have the same hardware on the same interrupts on 9-STABLE? >>> Are there changes in the use of MSI(-X)? >>> >> I made no hardware or BIOS changes and I'm running a GENERIC kernel in all >> testing. > > > That does not mean FreeBSD 9 can't put devices on other interrupts than 8 did. > 'dmesg | grep irq' like you did before might show a difference with your previous output. > I'm just guessing here for a clue on the result you are seeing, but without any data I cannot answer you (and I guess nobody can). > Ronald, The irqs seem to be the same: $ grep irq\ 16 /var/run/dmesg.boot pcib1: irq 16 at device 1.0 on pci0 mps0: port 0xee00-0xeeff mem 0xfbdfc000-0xfbdf,0xfbd8-0xfbdb irq 16 at device 0.0 on pci1 vgapci0: port 0xff00-0xff07 mem 0xfb40-0xfb7f,0xe000-0xefff irq 16 at device 2.0 on pci0 uhci0: port 0xfe00-0xfe1f irq 16 at device 26.0 on pci0 pcib2: irq 16 at device 28.0 on pci0 pcib3: irq 16 at device 28.4 on pci0 atapci0: port 0xdf00-0xdf07,0xde00-0xde03,0xd00-0xdd07,0xdc00-0xdc03,0xdb00-0xdb0f irq 16 at device 0.0 on pci3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 157k interrupts per second causing 60% CPU load on idle system
On Apr 15, 2012 6:27 PM, "Ronald Klop" wrote: > >> The problem does not occur with 9-STABLE. >> >> Who knows what the problem was ? USB maybe ? > > > Do you still have the same hardware on the same interrupts on 9-STABLE? > Are there changes in the use of MSI(-X)? > I made no hardware or BIOS changes and I'm running a GENERIC kernel in all testing. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 157k interrupts per second causing 60% CPU load on idle system
On Apr 7, 2012 2:38 PM, "Matt Thyer" wrote: > > On 7 April 2012 14:31, Matt Thyer wrote: >> Since moving the SATA 3 disk to the onboard Intel SATA 2 controller I'm no longer having that disk evicted from the raidz2 pool with write errors and I thought that the high interrupt rate issue had also been solved but it's back again. >> >> This is on 8-STABLE at revision 230921 (before the new driver hit 8-STABLE). >> >> So now I need to go back to trying to determine what the cause is. >> > vmstat -i has shown that the issue was on irq 16. > > Unfortunately there seems to be a lot of things on irq 16: > > $ dmesg | grep "irq 16" > > pcib1: irq 16 at device 1.0 on pci0 > mps0: port 0xee00-0xeeff mem 0xfbdfc000-0xfbdf,0xfbd8-0xfbdb irq 16 at device 0.0 on pci1 > vgapci0: port 0xff00-0xff07 mem 0xfb40-0xfb7f,0xe000-0xefff irq 16 at device 2.0 on pci0 > uhci0: port 0xfe00-0xfe1f irq 16 at device 26.0 on pci0 > pcib2: irq 16 at device 28.0 on pci0 > pcib3: irq 16 at device 28.4 on pci0 > atapci0: port 0xdf00-0xdf07,0xde00-0xde03,0xdd00-0xdd07,0xdc00-0xdc03,0xdb00-0xdb0f irq 16 at device 0.0 on pci3 > > Any idea how to isolate which bit of hardware could be triggering the interrupts ? > > Unfortunately the only device I could remove would be the SuperMicro AOC-USAS2-L8i (so yes I could eliminate that). > > My biggest problem right now is not knowing how to trigger the issue. > > At this stage I'm going to upgrade to 9-STABLE and see if it returns. The problem does not occur with 9-STABLE. Who knows what the problem was ? USB maybe ? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 157k interrupts per second causing 60% CPU load on idle system
On 7 April 2012 14:31, Matt Thyer wrote: > On 5 April 2012 01:18, Freddie Cash wrote: > >> On Wed, Apr 4, 2012 at 5:19 AM, Matt Thyer wrote: >> > So it seems that both the old and new mps driver have a problem with the >> > Western Digital WD20EARX SATA 3 drive on a SuperMicro AOC-USAS2-L8i (SAS >> > 6G) controller (flashed with -IT firmware). >> >> I wouldn't say the driver has a problem with that specific drive. >> More that it might have a problem with a mixed SATA2/SATA3 setup. >> >> Sorry, that's what I meant to say but it now seems that the 157K > interrupts per second is probably not due to the SuperMicro AOC-USAS2-L8i. > > Since moving the SATA 3 disk to the onboard Intel SATA 2 controller I'm no > longer having that disk evicted from the raidz2 pool with write errors and > I thought that the high interrupt rate issue had also been solved but it's > back again. > > This is on 8-STABLE at revision 230921 (before the new driver hit > 8-STABLE). > > So now I need to go back to trying to determine what the cause is. > > I'll stop posting in this thread as I don't think it's anything to do with > either the old or new version of this driver. > Oops... wrong thread I thought I was replying in -CURRENT. So on to the root cause. vmstat -i has shown that the issue was on irq 16. Unfortunately there seems to be a lot of things on irq 16: $ dmesg | grep "irq 16" pcib1: irq 16 at device 1.0 on pci0 mps0: port 0xee00-0xeeff mem 0xfbdfc000-0xfbdf,0xfbd8-0xfbdb irq 16 at device 0.0 on pci1 vgapci0: port 0xff00-0xff07 mem 0xfb40-0xfb7f,0xe000-0xefff irq 16 at device 2.0 on pci0 uhci0: port 0xfe00-0xfe1f irq 16 at device 26.0 on pci0 pcib2: irq 16 at device 28.0 on pci0 pcib3: irq 16 at device 28.4 on pci0 atapci0: port 0xdf00-0xdf07,0xde00-0xde03,0xdd00-0xdd07,0xdc00-0xdc03,0xdb00-0xdb0f irq 16 at device 0.0 on pci3 pcib1: irq 16 at device 1.0 on pci0 mps0: port 0xee00-0xeeff mem 0xfbdfc000-0xfbdf,0xfbd8-0xfbdb irq 16 at device 0.0 on pci1 vgapci0: port 0xff00-0xff07 mem 0xfb40-0xfb7f,0xe000-0xefff irq 16 at device 2.0 on pci0 uhci0: port 0xfe00-0xfe1f irq 16 at device 26.0 on pci0 pcib2: irq 16 at device 28.0 on pci0 pcib3: irq 16 at device 28.4 on pci0 atapci0: port 0xdf00-0xdf07,0xde00-0xde03,0xdd00-0xdd07,0xdc00-0xdc03,0xdb00-0xdb0f irq 16 at device 0.0 on pci3 Any idea how to isolate which bit of hardware could be triggering the interrupts ? Unfortunately the only device I could remove would be the SuperMicro AOC-USAS2-L8i (so yes I could eliminate that). My biggest problem right now is not knowing how to trigger the issue. At this stage I'm going to upgrade to 9-STABLE and see if it returns. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 157k interrupts per second causing 60% CPU load on idle system
On 5 April 2012 01:18, Freddie Cash wrote: > On Wed, Apr 4, 2012 at 5:19 AM, Matt Thyer wrote: > > So it seems that both the old and new mps driver have a problem with the > > Western Digital WD20EARX SATA 3 drive on a SuperMicro AOC-USAS2-L8i (SAS > > 6G) controller (flashed with -IT firmware). > > I wouldn't say the driver has a problem with that specific drive. > More that it might have a problem with a mixed SATA2/SATA3 setup. > > Sorry, that's what I meant to say but it now seems that the 157K interrupts per second is probably not due to the SuperMicro AOC-USAS2-L8i. Since moving the SATA 3 disk to the onboard Intel SATA 2 controller I'm no longer having that disk evicted from the raidz2 pool with write errors and I thought that the high interrupt rate issue had also been solved but it's back again. This is on 8-STABLE at revision 230921 (before the new driver hit 8-STABLE). So now I need to go back to trying to determine what the cause is. I'll stop posting in this thread as I don't think it's anything to do with either the old or new version of this driver. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 157k interrupts per second causing 60% CPU load on idle system
On 4 April 2012 21:55, Desai, Kashyap wrote: > Mike, > Have your purchase LSI controller through Channel or OEM ? > It would be a difficult for developers to help you without any support > channel invovoled ? > If possible can you contact LSI support channel ? > Kashyap, It's me, Matt, not Mike reporting this problem. I purchased the Super Micro card off eBay through a seller with good reputation. I've bought a couple of said cards through him now. I'm not sure why you are thinking the lack of middle men would be a problem. I hope that Super Micro & LSI would both be interested in a detailed report of a problem. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 157k interrupts per second causing 60% CPU load on idle system
On 25 March 2012 22:26, Matt Thyer wrote: > > Does anyone know if and when this driver was merged from current to > 8-STABLE ? > > If I can work out what revision that occurred in I'll go back to just > before then to confirm if the problem exists. > In the -CURRENT list I've been told that the new driver was introduced into 8-STABLE at revision 230921. I reverted to that revision but the problem was still apparent. So I've now tried: - Previous BIOS - Updating the controller firmware from phase 7 to phase 11 - Going back to the old (pre LSI authored) mps driver But all to no avail. What has worked is to move the single SATA 3 (6 Gbps) drive (the other 7 drives are SATA 2) to the onboard SATA 2 Intel controller. So it seems that both the old and new mps driver have a problem with the Western Digital WD20EARX SATA 3 drive on a SuperMicro AOC-USAS2-L8i (SAS 6G) controller (flashed with -IT firmware). I'll continue this in the -CURRENT list in the thread about the new driver as that's where the main discussion has been. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ESCape codes displayed instead of processed in pager
On Mar 31, 2012 5:02 AM, "Jim Bryant" @ gmail.com > wrote: > > Matt Thyer wrote: > >> >> On Mar 29, 2012 5:18 AM, "Jim Bryant" >> @ gmail.com @ gmail.com >> wrote: >> > >> > Ever since I have upgraded to 9-stable, I have noticed that the manpages seem to be munged up with displayed instead of processed ESCape codes. >> >> I believe that this is due to the terminal type of the console changing from "cons25" to "xterm". If you fix your /etc/ttys to reflect this things should be OK. >> > 1:27:57pm argus(19): tty > /dev/pts/7 > 1:28:03pm argus(20): setenv TERM xterm > 1:28:05pm argus(21): man man > > MAN(1) FreeBSD General Commands Manual MAN(1) > > ESC[1mNAMEESC[0m >ESC[1mman ESC[22m-- display online manual documentation pages > > same thing going on. that's after switching every vty and the console to xterm in /etc/ttys as well. > > i'm kinda lost on this one. i have determined that somehow, it's the pager... hang on a sec... lemme try vi. > > vi seems to be working properly... it's not the termcap/terminfo... the only thing causing this seems to be more and less, both. > > when i pipe man into cat, everything gets properly interpreted by the tty/vty/pty, when i use the pager, i get this crapargh.. > Some suggestions: Test with a clean environment (most easily done by creating a new user account). If that doesn't fix it then you have a problem with your upgrade that may be fixed by mergemaster. You may need to back up your data and do a clean install. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ESCape codes displayed instead of processed in pager
On Mar 29, 2012 5:18 AM, "Jim Bryant" wrote: > > Ever since I have upgraded to 9-stable, I have noticed that the manpages seem to be munged up with displayed instead of processed ESCape codes. I believe that this is due to the terminal type of the console changing from "cons25" to "xterm". If you fix your /etc/ttys to reflect this things should be OK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 157k interrupts per second causing 60% CPU load on idle system
On 23 March 2012 01:16, Mike Tancsa wrote: > Sorry, what I was getting at was that a bad bios (eg latest could have > introduced a regression) can cause the symptoms you are seeing. The bios > change sure seemed to fix my problem. > I've updated the firmware of the SuperMicro AOC-USAS2-L8i to the latest -IT firmware on the Supermicro FTP site (this is version 11 and I was on 7 before) but this made no difference. I then tried downgrading the motherboard BIOS to the F3 release that I was running previously but again this made no difference. So it would seem that this is a problem is to do with a change in FreeBSD-STABLE between r225723 and r232477. I'm wondering whether this is due to the new LSI authored driver for chips such as the LSI SAS2008 that are used in the SuperMicro AOC-USAS2-L8i. I know this driver is in CURRENT but do not know if it's in 8-STABLE. Does anyone know if and when this driver was merged from current to 8-STABLE ? If I can work out what revision that occurred in I'll go back to just before then to confirm if the problem exists. Matt ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 157k interrupts per second causing 60% CPU load on idle system
On Mar 22, 2012 10:14 AM, "Mike Tancsa" wrote: > > On 3/20/2012 1:26 AM, Matt Thyer wrote: > > I've upgraded my FreeBSD-STABLE NAS from r225723 (22nd Sept 2011) to > > r232477 (4th Mar 2012) and am finding that a system process called "intr" > > is now constantly using about 60% of 1 CPU starting a short time after > > reboot (possibly triggered by use of the samba server). > > > > When this starts, systat -vm 1 says that the system is 85% idle and 14% > > interrupt handling. > > It says that there's around 157k interrupts per second. > > > > Any idea what could be the cause ? > > This sounds like the problem I had with my intel board. BIOS update > fixed it. What chipset and MB vendor do you have ? The original post tells you this. I've already updated to the latest BIOS and this could have caused the problem. I think I should try updating the firmware of the SAS/SATA HBA but not until I've confirmed if a BIOS downgrade works. Unfortunately it's very hard to get downtime on this system so it may be some time before I can report any news. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 157k interrupts per second causing 60% CPU load on idle system
On 21 March 2012 00:03, Gary Palmer wrote: > On Tue, Mar 20, 2012 at 11:10:10PM +1030, Matt Thyer wrote: > > On 20 March 2012 22:24, Ivan Voras wrote: > > > > > On 20 March 2012 12:52, Matt Thyer wrote: > > > > On 20 March 2012 21:12, Ivan Voras wrote: > > > >> > > > >> On 20/03/2012 06:26, Matt Thyer wrote: > > > >> > I've upgraded my FreeBSD-STABLE NAS from r225723 (22nd Sept 2011) > to > > > >> > r232477 (4th Mar 2012) and am finding that a system process called > > > >> > "intr" > > > >> > is now constantly using about 60% of 1 CPU starting a short time > after > > > >> > reboot (possibly triggered by use of the samba server). > > > >> > > > > >> > When this starts, systat -vm 1 says that the system is 85% idle > and > > > 14% > > > >> > interrupt handling. > > > >> > It says that there's around 157k interrupts per second. > > > >> > > > > >> > > > >> Ok, but *which* interrupt is getting triggered? Please send the > output > > > >> of "vmstat -i". > > > >> > > > >> > > > > interrupt total rate > > > > irq16: uhci0+ 3392184862 126692 > > > > > > Ok, something's probably wrong with USB. Can you disable it in BIOS? > > > > > > > > > > cpu0: timer 53549677 1999 > > > > irq256: mps0 2643187 98 > > > > irq257: re0 5508108205 > > > > irq258: ahci0 160717 6 > > > > cpu1: timer 53525300 1999 > > > > cpu2: timer 53525300 1999 > > > > cpu3: timer 53525296 1999 > > > > Total 3614622447 134999 > > > > > > > > > > > I did just update the BIOS at about the same time so the difference may > be > > due to that change. > > > > I'll try a few things such as: > > > > - Unplugging any USB things (I've only got a keyboard plugged in). > > - Downgrade BIOS. > > > > I'll get back to you all soon. > > It would be interesting to know if there are other devices on irq16 also. > > grep 'irq 16' /var/run/dmesg.boot > > I think the '+' on the irq16 line from vmstat means the interrupt is > shared, but the man page doesn't mention it so I'm not 100% sure > > Thanks, > > Gary > Good point... pcib1: irq 16 at device 1.0 on pci0 mps0: port 0xee00-0xeeff mem 0xfbdfc000-0xfbdf,0xfbd8-0xfbdb irq 16 at device 0.0 on pci1 vgapci0: port 0xff00-0xff07 mem 0xfb40-0xfb7f,0xe000-0xefff irq 16 at device 2.0 on pci0 uhci0: port 0xfe00-0xfe1f irq 16 at device 26.0 on pci0 pcib2: irq 16 at device 28.0 on pci0 pcib3: irq 16 at device 28.4 on pci0 atapci0: port 0xdf00-0xdf07,0xde00-0xde03,0xdd00-0xdd07,0xdc00-0xdc03,0xdb00-0xdb0f irq 16 at device 0.0 on pci3 I'd suspect the SAS/SATA HBA using the mps0 driver as that's where I have the raidz2 on 8 drives. Is this still the old driver or has the new LSI authored driver been added to -STABLE yet ? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 157k interrupts per second causing 60% CPU load on idle system
On 20 March 2012 22:24, Ivan Voras wrote: > On 20 March 2012 12:52, Matt Thyer wrote: > > On 20 March 2012 21:12, Ivan Voras wrote: > >> > >> On 20/03/2012 06:26, Matt Thyer wrote: > >> > I've upgraded my FreeBSD-STABLE NAS from r225723 (22nd Sept 2011) to > >> > r232477 (4th Mar 2012) and am finding that a system process called > >> > "intr" > >> > is now constantly using about 60% of 1 CPU starting a short time after > >> > reboot (possibly triggered by use of the samba server). > >> > > >> > When this starts, systat -vm 1 says that the system is 85% idle and > 14% > >> > interrupt handling. > >> > It says that there's around 157k interrupts per second. > >> > > >> > >> Ok, but *which* interrupt is getting triggered? Please send the output > >> of "vmstat -i". > >> > >> > > interrupt total rate > > irq16: uhci0+ 3392184862 126692 > > Ok, something's probably wrong with USB. Can you disable it in BIOS? > > > > cpu0: timer 53549677 1999 > > irq256: mps0 2643187 98 > > irq257: re0 5508108205 > > irq258: ahci0 160717 6 > > cpu1: timer 53525300 1999 > > cpu2: timer 53525300 1999 > > cpu3: timer 53525296 1999 > > Total 3614622447 134999 > > > I did just update the BIOS at about the same time so the difference may be due to that change. I'll try a few things such as: - Unplugging any USB things (I've only got a keyboard plugged in). - Downgrade BIOS. I'll get back to you all soon. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 157k interrupts per second causing 60% CPU load on idle system
On 20 March 2012 21:12, Ivan Voras wrote: > On 20/03/2012 06:26, Matt Thyer wrote: > > I've upgraded my FreeBSD-STABLE NAS from r225723 (22nd Sept 2011) to > > r232477 (4th Mar 2012) and am finding that a system process called "intr" > > is now constantly using about 60% of 1 CPU starting a short time after > > reboot (possibly triggered by use of the samba server). > > > > When this starts, systat -vm 1 says that the system is 85% idle and 14% > > interrupt handling. > > It says that there's around 157k interrupts per second. > > > > Ok, but *which* interrupt is getting triggered? Please send the output > of "vmstat -i". > > > interrupt total rate irq16: uhci0+ 3392184862 126692 cpu0: timer 53549677 1999 irq256: mps0 2643187 98 irq257: re0 5508108205 irq258: ahci0 160717 6 cpu1: timer 53525300 1999 cpu2: timer 53525300 1999 cpu3: timer 53525296 1999 Total 3614622447 134999 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
157k interrupts per second causing 60% CPU load on idle system
I've upgraded my FreeBSD-STABLE NAS from r225723 (22nd Sept 2011) to r232477 (4th Mar 2012) and am finding that a system process called "intr" is now constantly using about 60% of 1 CPU starting a short time after reboot (possibly triggered by use of the samba server). When this starts, systat -vm 1 says that the system is 85% idle and 14% interrupt handling. It says that there's around 157k interrupts per second. After a reboot the system is back to it's normal state doing between 3 and 250 or so interrupts per second. The hardware is an Intel Core i3-530 (dual core @ 2.93 GHz with Hyperthreading) with 8 GB RAM (2x4GB) on a Gigabyte H55M-D2H rev 1.3 motherboard running the latest BIOS (F4). The system runs a GENERIC kernel with the following significant items in /boot/loader.conf: zfs_load="YES" aio_load="YES" ahci_load="YES" geom_mirror_load="YES" vfs.root.mountfrom="zfs:zroot" vboxdrv_load="YES" It has 2 x 300 GB disks for the system with GPT partitioning and zmirror for the OS ala http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror I have swap on a gmirror as I want swap to survive the loss of one system disk. The NAS data is on a raidz2 pool of 8 disks connected to a SuperMicro AOC-USAS2-L8i (flashed to behave as an AOC-USAS2-L8e). The system is basically a CIFS NAS with ports/net/samba36 built with AIO_SUPPORT and configured like: socket options = SO_RCVBUF=131072 SO_SNDBUF=131072 TCP_NODELAY min receivefile size=16384 use sendfile=true aio read size = 16384 aio write size = 16384 aio write behind = true The only other interesting workload on the box is a java Minecraft server using ports/java/jdk16. I'm going to try to reproduce the problem in a VM and binary search down to the revision where it started as soon as I can work out a reliable way to trigger the behaviour (as it doesn't start at boot time). Any idea what could be the cause ? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: PCIe SATA HBA for ZFS on -STABLE
On 8 June 2011 20:55, Matt Thyer wrote: > On 7 June 2011 12:03, Matthew Dillon wrote: > >>The absolute cheapest solution is to buy a Sil-3132 PCIe card >>(providing 2 E-SATA ports), and then connect an external port >> multiplier >>to each port. External port multiplier enclosures typically support >>5 drives each so that would give you your 10 drives. >> > > I've decided to avoid issues with port multiplication by going for a > Supermicro AOC-USAS2-L8i and then to flash it to IT (as opposed to IR) mode > to make it run as a standard non-RAID HBA. > > As I've got 8 x 2 TB drives for the ZFS raidz2 I'll put them all on the > AOC-USAS2-L8i and save my onboard SATA-II ports for my 2 x 1TB drives for > the FreeBSD O.S. and any eSATA use. > > Now the only remaining issue is whether to go with the Supermicro firmware > or the generic Lsi Logic firmware as some have reported better performance > with the version 9 Lsi Logic firmware. > > I'll report on my experiences (as I keep a record of the revision of my > -STABLE build this should actually be useful!). > > I could not be happier with the result. As planned, I've put all 8 2TB Western Digital WD20EARS drives on the 8 lane PCIe 2.0 AOC-USAS2-L8i (flashed with the latest SuperMicro firmware to behave as an AOC-USAS2-L8e). Many of you are now screaming "Why is he using the dreaded WD20EARS ?". The answer is that I bought the first 4 drives before I knew their issues and later decided to continue with them once I knew how to mitigate their issues by: - Using the DOS based WDIDLE3.EXE utility to change the default "park the heads after 8 seconds of idle time" to the maximum of 5 minutes - Avoiding alignment problems by putting ZFS on the whole disks (with no GPT or MBR partition table) - Convincing ZFS to use 4KiB transfers by creating the pool on top of 4KiB block sized devices created with "gnop -S 4096" And the resulting performance... Previously I could sustain about 45 MiB/s writing from high powered Windows 7 machines (via Samba using asynchronous I/O) on to my old arrangement of 4 drives in raidz1 (using only the Intel on-board SATA ports on the H55 chipset motherboard). I can now sustain 90 MiB/s over the network with the 8 drive raidz2 but that's only because the Windows 7 machines can't feed the data fast enough. I can see from "zpool iostat pool 1" that ZFS is idle for about 5-7 seconds and then it will write at around 390 - 410 MB/s for about 3 seconds. dd tests are: > sudo dd if=/dev/zero of=/export/1G bs=1M count=1024 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 3.218604 secs (333604841 bytes/sec) > sudo dd if=/dev/random of=/export/1G bs=1M count=1024 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 15.531615 secs (69132658 bytes/sec) So I'm very happy that I can keep my home network users happy with the limits now being due to my gigabit ethernet network (and I'm not going 10 GbE any time soon!). This is on 8-STABLE at r220359 (~ 5th of April 2011). ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: PCIe SATA HBA for ZFS on -STABLE
On 7 June 2011 12:03, Matthew Dillon wrote: >The absolute cheapest solution is to buy a Sil-3132 PCIe card >(providing 2 E-SATA ports), and then connect an external port multiplier >to each port. External port multiplier enclosures typically support >5 drives each so that would give you your 10 drives. > I've decided to avoid issues with port multiplication by going for a Supermicro AOC-USAS2-L8i and then to flash it to IT (as opposed to IR) mode to make it run as a standard non-RAID HBA. As I've got 8 x 2 TB drives for the ZFS raidz2 I'll put them all on the AOC-USAS2-L8i and save my onboard SATA-II ports for my 2 x 1TB drives for the FreeBSD O.S. and any eSATA use. Now the only remaining issue is whether to go with the Supermicro firmware or the generic Lsi Logic firmware as some have reported better performance with the version 9 Lsi Logic firmware. I'll report on my experiences (as I keep a record of the revision of my -STABLE build this should actually be useful!). ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: PCIe SATA HBA for ZFS on -STABLE
On 1 June 2011 17:37, Jeremy Chadwick wrote: > On Wed, Jun 01, 2011 at 02:34:55PM +0800, TJ Varghese wrote: > > On Tue, May 31, 2011 at 10:31 PM, Freddie Cash > wrote: > [snip] > > > SuperMicro AOC-USAS2-L8i works exceptionally well. These are 8-port > HBAs > > > using the LSI1068 chipset, supported by the mpt(4) driver. Support 3 > Gpbs > > > SATA/SAS, using multi-lane cables (2 connectors on the card, each > connector > > > supports 4 SATA ports), hot-plug, hot-swap. > > > > > > > > The USAS2 (6Gbps) is supported by the mps driver (on -CURRENT, not sure > if > > it's in 8-STABLE yet). Perhaps you're referring to the earlier USAS which > > does 3Gbps and is supported by the mpt driver. > > Folks considering use of mps(4), which was committed to RELENG_8 roughly > around 2011/02/18 (thus is not in 8.2-RELEASE), should read the below > threads just in case. Always good to be educated. Of course, the > mailing lists are usually filled with complaints rather than success > stories, so the tone of my mail here will therefore sound negative; I > don't mean it that way, I just ask that people "be aware". > > * 2011/04/29 -- mps driver instability under stable/8 > > http://lists.freebsd.org/pipermail/freebsd-stable/2011-April/thread.html#62507 > > http://lists.freebsd.org/pipermail/freebsd-stable/2011-May/thread.html#62518 > > * 2011/04/27 -- MPS driver: force bus rescan after remove SAS cable > > http://lists.freebsd.org/pipermail/freebsd-stable/2011-April/thread.html#62438 > > http://lists.freebsd.org/pipermail/freebsd-stable/2011-April/thread.html#62443 > > * 2011/03/10 -- LSI SAS2008 performance with mps(4) driver > > http://lists.freebsd.org/pipermail/freebsd-stable/2011-March/thread.html#61862 > Those threads assure me that the SuperMicro AOC-USAS2-L8i with version 9 firmware and the mps(4) driver work very well as long as I'm running FreeBSD 9-CURRENT or 8-STABLE (not 8.2-RELEASE). As I'm running -STABLE I'm quite happy to give it a go. To the OP (Matt Thyer): > > Sadly I don't have a recommendation for you, since you effectively want > a 6-port SATA300 controller that's reliable, you're almost certainly > going to be paying Big Bucks(tm) given the number of ports and your > requirement that it be PCIe-based. You state quite boldly "not wanting > to break the bank", but what you're asking for almost certainly WILL > break the bank. > Jeremy, I think you need to have another look at current prices. I have now bought a SuperMicro AOC-USAS2-L8i on EBay from bakamuzko with the cables I need for only $US 210.99 (I do know about the UIO bracket). For example, an "affordable" controller might be one driven by Silicon > Image's SiI3124 chip -- four (4) SATA300 ports, but it's only hooked to > PCI or PCI-X, not PCIe, which means you're susceptible to a much more > severe bus bottleneck than with PCIe: > I defintely would not consider PCI for part of a ZFS array with 4 drives on that one controller. <http://www.siliconimage.com/products/family.aspx?id=3> > I tend to avoid consumer-grade Marvell and JMicron SATA chipsets like > the plague, however. That's based on my experiences with them under > Windows, where I would expect (truly) the drivers to be rock solid given > the marketing demographic of the chips in question. > I've had the same bad experiences. Good luck, and please let us know what controller you *do* end up going > with and your experience with it! Positives are as important as > negatives. > I'll let you know how it works out. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
PCIe SATA HBA for ZFS on -STABLE
I'm not on the -STABLE list so please reply to me. I'm using an Intel Core i3-530 on a Gigabyte H55M-D2H motherboard with 8 x 2TB drives & 2 x 1TB drives. The plan is to have the 1 TB drives in a zmirror and the 8 in a raidz2. Now the Intel chipset has only 6 on board SATA II ports so ideally I'm looking for a non RAID SATA II HBA to give me 6 extra ports (4 min). Why 6 extra ? Well the case I'm using has 2 x eSATA ports so 6 would be ideal, 5 OK, and 4 the minimum I need to do the job. So... What do people recommend for 8-STABLE as a PCIe SATA II HBA for someone using ZFS ? Not wanting to break the bank. Not interested in SATA III 6GB at this time... though it could be useful if I add an SSD for... (is it ZIL ?). Can this be added at any time ? The main issue is I need at least 10 ports total for all existing drives... ZIL would require 11 so ideally we are talking a 6 port HBA. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
