Re: 12.2-RC2 synaptics "tap to click"

[Mark Saad]

2yt
  Can you provide us some details , what do you have in your
boot/loader.conf , etc/sysctl.conf
and what do you have in your Xorg config ?

On Sun, Oct 11, 2020 at 11:29 AM <2...@gmx.com> wrote:
>
> I use a Thinkpad X1 Carbon 4th gen. After upgrading to 12.2 from 12.1, I
> lost  "tap to click" which worked perfectly in past releases. Is this a
> know feature change? Is there a new sysctl variable that needs set?
>
> The other synaptics features are all working just fine.
>
> Thanks
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"



-- 
mark saad | nones...@longcount.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: CFT: if_bridge performance improvements

[Mark Saad]

Kristof 
  Up until a month ago I ran a set of FreeBSD based ap in my house and even 
long ago at work . They were Pc engines apu ‘s or Alix’s with one em/igb nic 
and one ath nic in a bridge .  They worked well for a long time however the 
need for more robust wifi setup caused me to swap them  out with cots aps from 
tp-link .  The major issues were the lack of WiFi features and standards that 
work oob on Linux based aps . 

So I always wanted to experiment with ng_bridge vs if_bridge for the same task 
. But I never got around to it . Do you have any insight into using one vs the 
other . Imho if_bridge is easier to setup and get working . 


---
Mark Saad | nones...@longcount.org

> On Apr 15, 2020, at 1:37 PM, Kristof Provost  wrote:
> 
> On 15 Apr 2020, at 19:16, Mark Saad wrote:
>> All
>>   Should this improve wifi to wired bridges in some way ? Has this been 
>> tested ?
>> 
> What sort of setup do you have to bridge wired and wireless? Is the FreeBSD 
> box also a wifi AP?
> 
> I’ve not done any tests involving wifi.
> 
> Best regards,
> Kristof
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: CFT: if_bridge performance improvements

[Mark Saad]

All
   Should this improve wifi to wired bridges in some way ? Has this been tested 
? 

---
Mark Saad | nones...@longcount.org

> On Apr 15, 2020, at 1:08 PM, Raúl Muñoz - CUSTOS via freebsd-stable 
>  wrote:
> 
> El 14/4/20 a las 11:53, Kristof Provost escribió:
> 
>> Patches for stable/12: https://people.freebsd.org/~kp/if_bridge/stable_12/
> 
> Bridges and taps here, r359859 with your if_bridge patches, happily
> running for more than two days ;).
> 
> Regards,
> Raúl
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: pkg breakage ?

[Mark Saad]

Mike 
  Not the best solution but switch from “latest” to “quarterly” in the pkg 
config . The quarterly repos are unaffected.  
---
Mark Saad | nones...@longcount.org

> On Mar 3, 2020, at 4:21 PM, mike tancsa  wrote:
> 
> I am preparing to upgrade a jail thats currently on RELENG_11 and moving
> to RELENG_12.  I imported the data from the 11 box to the 12 box (its
> qjail) and it worked fine.  I can spin up the jail etc.  However, when
> trying to upgrade the packages, I have run into this error
> 
> 
> # pkg upgrade -f
> Updating FreeBSD repository catalogue...
> [bullochtest] Fetching meta.txz: 100%916 B   0.9kB/s00:01   
> [bullochtest] Fetching packagesite.txz: 100%6 MiB   3.2MB/s00:02   
> Processing entries:  63%
> pkg: wrong architecture: FreeBSD:12.0:amd64 instead of FreeBSD:12:amd64
> pkg: repository FreeBSD contains packages with wrong ABI: FreeBSD:12.0:amd64
> Processing entries: 100%
> Unable to update repository FreeBSD
> Error updating repositories!
> 
> 
> Which seems to be related to this bug ?
> 
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244549
> 
> 
> Does anyone know of a work around ?
> 
> ---Mike
> 
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Kernel panic on 12-STABLE-r348203 amd64

[Mark Saad]

All
  I am going to try to reset the box to factory defaults and try to make it 
crash again today . I’ll update you with my outcome . 

---
Mark Saad | nones...@longcount.org

> On Jun 11, 2019, at 1:15 AM, Kubilay Kocak  wrote:
> 
>> On 6/06/2019 5:04 am, Mark Saad wrote:
>>> On Wed, Jun 5, 2019 at 2:42 PM Mark Saad  wrote:
>>> 
>>>> On Wed, Jun 5, 2019 at 12:29 PM Mark Saad  wrote:
>>>> 
>>>> All
>>>>  I was wondering if anyone could shed some light on this boot panic I
>>>> saw yesterday. This is on a Dell R630 with Bios 2.9.1  booting
>>>> 12.0-STABLE-r348203 amd64.
>>>> I reverted this back to 12.0-RELEASE-p4 and its fine .
>>>> 
>>>> The only custom options I had were in loader.conf
>>>> 
>>>> kern.geom.label.gptid.enable="0"
>>>> ipmi_load="YES"
>>>> boot_multicons="YES"
>>>> boot_serial="YES"
>>>> console="comconsole,vidconsole"
>>>> net.inet.tcp.tso="0"
>>>> cc_htcp_load="YES"
>>>> autoboot_delay="5"
>>>> hw.mfi.mrsas_enable="1"
>>>> hw.usb.no_pf="1"# Disable USB packet filtering
>>>> hw.usb.no_shutdown_wait="1"
>>>> hw.vga.textmode="1" # Text mode
>>>> machdep.hyperthreading_allowed="0"
>>>> 
>>>> Any ideas ?
>>>> 
>>>> Screen shot here
>>>> https://imgur.com/a/nGvHtIs
>>>> 
>>>> --
>>>> mark saad | nones...@longcount.org
>>> 
>>> Plain text version of the crash
>>> 
>>> Loading kernel...
>>> /boot/kernel/kernel text=0x168d811 data=0x1cf968+0x768c80
>>> syms=[0x8+0x1778e8+0x8   /
>>> +0x194f1d]
>>> Loading configured modules...
>>> /boot/kernel/ipmi.ko size 0x11e10 at 0x2645000
>>> loading required module 'smbus'
>>> /boot/kernel/smbus.ko size 0x2ef0 at 0x2657000
>>> /boot/entropy size=0x1000
>>> /boot/kernel/cc_httcp.ko size 0x2330 at 0x265b000
>>> ---<>---c_hmodule 'smbus'
>>> Copyright (c) 1992-2019 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 is a registered trademark of The FreeBSD Foundation.
>>> FreeBSD 12.0-STABLE r348693 GENERIC amd64
>>> FreeBSD clang version 8.0.0 (tags/RELEASE_800/final 356365) (based on
>>> LLVM 8.0.0)
>>> panic: UMA zone "UMA Zones": Increase vm.boot_pages
>>> cpuid = 0
>>> time = 1
>>> KDB: stack backtrace:
>>> #0 0x80c16df7 at ??+0
>>> #1 0x80bcaccd at ??+0
>>> #2 0x80bcab23 at ??+0
>>> #3 0x80f0b03c at ??+0
>>> #4 0x80f08d8d at ??+0
>>> #5 0x80f0bb3d at ??+0
>>> #6 0x80f0b301 at ??+0
>>> #7 0x80f0b3d1 at ??+0
>>> #8 0x80f066c4 at ??+0
>>> #9 0x80f0543f at ??+0
>>> #10 0x80f23aef at ??+0
>>> #11 0x80f1133b at ??+0
>>> #12 0x80b619c8 at ??+0
>>> #13 0x8036a02c at ??+0
>>> Uptime: 1s
>>> 
>>> 
>>> Also increasing the vm.boot_pages to 128 in the loader works. Anyone
>>> know why ? This box has 64G ram.
>>> 
>>> --
>>> mark saad | nones...@longcount.org
>> So after some poking in the bios this has to do with how the Dell NUMA
>> options are set. If the system is set Cluster On Die mode, you get a
>> kernel panic
>> Home Snoop or Early Snoop no issue.
> 
> Hi Mark,
> 
> Could you report this bug (Bugzilla) if you haven't already, providing:
> 
> - exact freebsd version(s) reproducible with
> - panic/backtrace output as an attachment. Ideally with a debug kernel
> - /var/run/dmesg.boot output (as an attachment) in a verbose boot
> - if you can test a current snapshot, that would be great
> - any other system information you believe might be helpful in isolating root 
> cause(s) or potential fixes
> 
> Thanks!
> Feel free to CC me on it
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Kernel panic on 12-STABLE-r348203 amd64

[Mark Saad]

On Wed, Jun 5, 2019 at 2:42 PM Mark Saad  wrote:
>
> On Wed, Jun 5, 2019 at 12:29 PM Mark Saad  wrote:
> >
> > All
> >  I was wondering if anyone could shed some light on this boot panic I
> > saw yesterday. This is on a Dell R630 with Bios 2.9.1  booting
> > 12.0-STABLE-r348203 amd64.
> > I reverted this back to 12.0-RELEASE-p4 and its fine .
> >
> > The only custom options I had were in loader.conf
> >
> > kern.geom.label.gptid.enable="0"
> > ipmi_load="YES"
> > boot_multicons="YES"
> > boot_serial="YES"
> > console="comconsole,vidconsole"
> > net.inet.tcp.tso="0"
> > cc_htcp_load="YES"
> > autoboot_delay="5"
> > hw.mfi.mrsas_enable="1"
> > hw.usb.no_pf="1"# Disable USB packet filtering
> > hw.usb.no_shutdown_wait="1"
> > hw.vga.textmode="1" # Text mode
> > machdep.hyperthreading_allowed="0"
> >
> > Any ideas ?
> >
> > Screen shot here
> > https://imgur.com/a/nGvHtIs
> >
> > --
> > mark saad | nones...@longcount.org
>
> Plain text version of the crash
>
> Loading kernel...
> /boot/kernel/kernel text=0x168d811 data=0x1cf968+0x768c80
> syms=[0x8+0x1778e8+0x8   /
> +0x194f1d]
> Loading configured modules...
> /boot/kernel/ipmi.ko size 0x11e10 at 0x2645000
> loading required module 'smbus'
> /boot/kernel/smbus.ko size 0x2ef0 at 0x2657000
> /boot/entropy size=0x1000
> /boot/kernel/cc_httcp.ko size 0x2330 at 0x265b000
> ---<>---c_hmodule 'smbus'
> Copyright (c) 1992-2019 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 is a registered trademark of The FreeBSD Foundation.
> FreeBSD 12.0-STABLE r348693 GENERIC amd64
> FreeBSD clang version 8.0.0 (tags/RELEASE_800/final 356365) (based on
> LLVM 8.0.0)
> panic: UMA zone "UMA Zones": Increase vm.boot_pages
> cpuid = 0
> time = 1
> KDB: stack backtrace:
> #0 0x80c16df7 at ??+0
> #1 0x80bcaccd at ??+0
> #2 0x80bcab23 at ??+0
> #3 0x80f0b03c at ??+0
> #4 0x80f08d8d at ??+0
> #5 0xffff80f0bb3d at ??+0
> #6 0x80f0b301 at ??+0
> #7 0x80f0b3d1 at ??+0
> #8 0x80f066c4 at ??+0
> #9 0x80f0543f at ??+0
> #10 0x80f23aef at ??+0
> #11 0x80f1133b at ??+0
> #12 0x80b619c8 at ??+0
> #13 0x8036a02c at ??+0
> Uptime: 1s
>
>
> Also increasing the vm.boot_pages to 128 in the loader works. Anyone
> know why ? This box has 64G ram.
>
> --
> mark saad | nones...@longcount.org

So after some poking in the bios this has to do with how the Dell NUMA
options are set. If the system is set Cluster On Die mode, you get a
kernel panic
Home Snoop or Early Snoop no issue.


-- 
mark saad | nones...@longcount.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Kernel panic on 12-STABLE-r348203 amd64

[Mark Saad]

On Wed, Jun 5, 2019 at 12:29 PM Mark Saad  wrote:
>
> All
>  I was wondering if anyone could shed some light on this boot panic I
> saw yesterday. This is on a Dell R630 with Bios 2.9.1  booting
> 12.0-STABLE-r348203 amd64.
> I reverted this back to 12.0-RELEASE-p4 and its fine .
>
> The only custom options I had were in loader.conf
>
> kern.geom.label.gptid.enable="0"
> ipmi_load="YES"
> boot_multicons="YES"
> boot_serial="YES"
> console="comconsole,vidconsole"
> net.inet.tcp.tso="0"
> cc_htcp_load="YES"
> autoboot_delay="5"
> hw.mfi.mrsas_enable="1"
> hw.usb.no_pf="1"# Disable USB packet filtering
> hw.usb.no_shutdown_wait="1"
> hw.vga.textmode="1" # Text mode
> machdep.hyperthreading_allowed="0"
>
> Any ideas ?
>
> Screen shot here
> https://imgur.com/a/nGvHtIs
>
> --
> mark saad | nones...@longcount.org

Plain text version of the crash

Loading kernel...
/boot/kernel/kernel text=0x168d811 data=0x1cf968+0x768c80
syms=[0x8+0x1778e8+0x8   /
+0x194f1d]
Loading configured modules...
/boot/kernel/ipmi.ko size 0x11e10 at 0x2645000
loading required module 'smbus'
/boot/kernel/smbus.ko size 0x2ef0 at 0x2657000
/boot/entropy size=0x1000
/boot/kernel/cc_httcp.ko size 0x2330 at 0x265b000
---<>---c_hmodule 'smbus'
Copyright (c) 1992-2019 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 is a registered trademark of The FreeBSD Foundation.
FreeBSD 12.0-STABLE r348693 GENERIC amd64
FreeBSD clang version 8.0.0 (tags/RELEASE_800/final 356365) (based on
LLVM 8.0.0)
panic: UMA zone "UMA Zones": Increase vm.boot_pages
cpuid = 0
time = 1
KDB: stack backtrace:
#0 0x80c16df7 at ??+0
#1 0x80bcaccd at ??+0
#2 0x80bcab23 at ??+0
#3 0x80f0b03c at ??+0
#4 0x80f08d8d at ??+0
#5 0x80f0bb3d at ??+0
#6 0x80f0b301 at ??+0
#7 0x80f0b3d1 at ??+0
#8 0x80f066c4 at ??+0
#9 0x80f0543f at ??+0
#10 0xffff80f23aef at ??+0
#11 0x80f1133b at ??+0
#12 0x80b619c8 at ??+0
#13 0x8036a02c at ??+0
Uptime: 1s


Also increasing the vm.boot_pages to 128 in the loader works. Anyone
know why ? This box has 64G ram.

-- 
mark saad | nones...@longcount.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Kernel panic on 12-STABLE-r348203 amd64

[Mark Saad]

All
 I was wondering if anyone could shed some light on this boot panic I
saw yesterday. This is on a Dell R630 with Bios 2.9.1  booting
12.0-STABLE-r348203 amd64.
I reverted this back to 12.0-RELEASE-p4 and its fine .

The only custom options I had were in loader.conf

kern.geom.label.gptid.enable="0"
ipmi_load="YES"
boot_multicons="YES"
boot_serial="YES"
console="comconsole,vidconsole"
net.inet.tcp.tso="0"
cc_htcp_load="YES"
autoboot_delay="5"
hw.mfi.mrsas_enable="1"
hw.usb.no_pf="1"# Disable USB packet filtering
hw.usb.no_shutdown_wait="1"
hw.vga.textmode="1" # Text mode
machdep.hyperthreading_allowed="0"

Any ideas ?

Screen shot here
https://imgur.com/a/nGvHtIs

-- 
mark saad | nones...@longcount.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Problem with STABLE-12

[Mark Saad]

Pete
  I have a Radeon cedar , running 12-stable from Monday . I had similar issues 
and reverted to older in kernel tree modules and deleted the port . This worked 
like a charm .  But I have no idea what broke .

---
Mark Saad | nones...@longcount.org

> On Apr 26, 2019, at 12:23 PM, Pete French  wrote:
> 
> 
> 
>> On 25/04/2019 15:07, Filippo Moretti via freebsd-stable wrote:
>>  Did you build world yesterday and now drm-kmod is working again?The only 
>> problem I have with legacy both drm and ati is that smplayer crashes the 
>> system and I have to reset via power switch.Filippo
> 
> Si, I just tried this after an udate and the new drm is still borken for me - 
> freezes at "loading kernel modules' during boot. Whats the best way to 
> inventisage this one ?
> 
> -pete.
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Anyone have a summary of what kernel option RSS does ? / netisr oddness .

[Mark Saad]

Hi all
 On a recount 11-STABLE I see that the interaction with netisr and rss has 
changed. Forgive me if this is clumsy but I don’t quite get what changes were.

On 10-Stable when I have a solarflare or intel Ixgbe card I would get a kernel 
thread per rss queue per card and a netirs queue:bucket thread per cpu ( or 
tuned to a value I define < ncpus ) . However on recent 11-STABLE about when 
the RSS kernel option was imported or added; I now get one netisr queue:bucket 
for the whole system and no tuning effects how many threads are created.  

Second part I started looking into the kernel rss option and I wanted the 
better understand what it was doing ?  Enabling it and the associate protocol 
block ? Option gave me 64 queues and no clear way to tune them or constrain 
them to the numa domain of the card companies consuming them I could not find 
options_rss.h either .  So is there a commit anyone can direct me to to for 
more insight? Is there a write up on it somewhere? 

Thanks again . 

---
Mark Saad | nones...@longcount.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: ATI video problem - slow desktop - 100% cpu load [semi-solved]

[Mark Saad]

Vincent
  I used the scfb driver in openbsd land for a work project . Currently I am 
using 11-STABLE with the Radeon driver but at one point I had a different card 
under 11.0 that didn’t work unless I used the scfb driver . 

---
Mark Saad | nones...@longcount.org

> On Jun 21, 2018, at 11:41 PM, Carl Johnson  wrote:
> 
> Vincent Stemen  writes:
> 
>> You must load radeonkms.ko after the system is fully booted.
>> 
>># kldload radeonkms
>> 
>> That automatically loads the other 3 modules and initializes the console 
>> where
>> the console text goes into higher resolution mode.  Then X and the desktop
>> environments work and seem to be fully functional, including transparency, 
>> etc.
>> 
>> So I can either put it in /etc/rc.local, to be run at boot time, or put it in
>> an X startup script wrapper.  Note that it must be run prior to startx 
>> because
>> it must be loaded before launching the X server.  So it cannot be put in
>> ~/.xinitrc.
> 
> Have you tried loading it with kld_list in /etc/rc.conf?  Those get
> loaded during boot, but it might be late enough to work.  That would be
> automated, so it might be a little more convenient.
> -- 
> Carl Johnsonca...@peak.org
> 
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: ATI video problem - extremely slow desktop - 100% cpu load

[Mark Saad]

On Wed, Jun 20, 2018 at 3:43 PM, Vincent Stemen  wrote:
> I have now tested with two additional ATI cards.
> A Radeon HD 5450 and and older card that shows as
> "RV370 [Radeon X300 SE]" in the PCI info.
>
> Same problem on all of them.  Before, it would come up and run correctly
> once in a while.  It doesn't seem to at all now.  This seems to be some
> kind of core radeon driver bug.
>

Vincent
 I am running 11.2-PRERELEASE with a Cedar PRO [Radeon HD 5450/6350]
and I dont have any issues like that

here is what I do to get it working for me; and I have used more or
less the same setup since 10.3-RELEASE

In my loader.conf I have

radeonkms_load="YES"
radeonkmsfw_CEDAR_pfp_load="YES"
radeonkmsfw_CEDAR_rlc_load="YES"
radeonkmsfw_CEDAR_me_load="YES"

I use a static xorg.conf as well  In there I have the following bits

  1 Section "ServerLayout"
  2 Identifier "X.org Configured"
  3 Screen  0  "Screen0" 0 0
  4 InputDevice"Mouse0" "CorePointer"
  5 InputDevice"Keyboard0" "CoreKeyboard"
  6 Option "AIGLX" "true"
  7 EndSection
...
 19 Section "Module"
 20 Load   "dbe"
 21 Load   "dri"
 22 Load   "dri2"
 23 Load   "extmod"
 24 Load   "record"
 25 Load   "freetype"
 26 Load   "bitmap"
 27 Load   "type1"
 28 Load   "glx"
 29 EndSection
...
 50 Section "Device"
 51 Option "AccelMethod" "EXA"
 52 Option "DRI" "true"
 53 Identifier  "Card0"
 54 Driver  "radeon"
 55 BusID   "PCI:3:0:0"
 56 EndSection
 57
...

Also if the redeon driver is not working for you try scfb . It works
better the vesa it some cases


msaad@ostrich:~ % pkg info xf86-video-scfb-0.0.4_5
xf86-video-scfb-0.0.4_5
Name   : xf86-video-scfb
Version: 0.0.4_5
Installed on   : Mon Sep 25 10:52:09 2017 EDT
Origin : x11-drivers/xf86-video-scfb
Architecture   : FreeBSD:11:amd64
Prefix : /usr/local
Categories : x11-drivers
Licenses   :
Maintainer : x...@freebsd.org
WWW: UNKNOWN
Comment: X.Org syscons display driver
Annotations:
repo_type  : binary
repository : FreeBSD
Flat size  : 21.4KiB
Description    :
This package contains the X.Org xf86-video-scfb driver.
Framebuffer access via FreeBSD syscons.




> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"



-- 
mark saad | nones...@longcount.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: problems with ssh-agent after running MATE desktop

[Mark Saad]

> On May 24, 2018, at 2:31 PM, Eugene Grosbein <eu...@grosbein.net> wrote:
> 
> 24.05.2018 21:41, tech-lists wrote:
> 
>> If I then run 'agent', prompts me for the keyphrase, then it works normally. 
>> But I have to repeat this in every single opened terminal.
> 
> You may like security/keychain port (or package). I use it because of its 
> universal way to run ssh-agent:
> no matter what DE or window manager you use and how do you start it or not at 
> all, working in ssh or console only.
> 
> One just adds single line to its login shell script, for bash it is 
> ~/.bash_login:
> 
> eval `keychain --eval $HOME/.ssh/id_rsa $HOME/.ssh/id_ed25519 
> $HOME/.ssh/id_dsa`
> 
> First time after machine reboots (sic!) it asks you for passphrase (if needed)
> when you log in starting interactive login shell (no matter which way: 
> ssh/X/console) and that's all.
> It won't ask you again until next reboot, or ssh-agent reset by some other 
> way.
> 
> You may even disconnect completely and it reuses started ssh-agent next time 
> you log in again.


I still use windowmaker as my primary desktop . However what I do in .xinitrc  
is ‘ ssh-agent wmaker’ . Ssh-agent’s man page states it can be used in place of 
exec in shell scripts to inject its environment into wmaker and its child 
processes like xterm or urxvt in my case .  You use to be able to do this in 
kde I am not 100% sure about gnome but it’s worth trying if you don’t like 
keyring.

---
Mark Saad | nones...@longcount.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Upgrade to 11.2-BETA1: vboxdrv kernel modulo load leads to panic unless vbox ports be rebuilt

[Mark Saad]

Jose
  If you have not rebuilt the virtualbox-ose-kmod package from ports with the 
11.2-beta1 sources on disk ; please do so .  This should resolve this issue .

---
Mark Saad | nones...@longcount.org

> On May 13, 2018, at 3:41 PM, Jose G. Juanino <jjuan...@gmail.com> wrote:
> 
>> On Sunday, May 13 at 15:53:28 CEST, Jose G. Juanino wrote:
>> Hi FreeBSD stable,
>> 
>> I have upgraded from 11.1 to 11.2-BETA1 right now. I use Virtualbox to
>> run Windows 7 from the FreeBSD box, and just after to complete the
>> upgrade and reboot, the system panics just after to load kernel module
>> vboxdrv.
>> 
>> The workaround is rebuild both emulators/virtualbox-ose and
>> emulators/virtualbox-ose-kmod ports from within 11.2-BETA1, and
>> after that everything works nicely as before the upgrade. I hope this
>> help other people suffering a similar issue. Best regards.
> 
> Full backtrace:
> 
> https://pastebin.com/raw/17UU5Mij
> 
> 
> -- 
> Jose G. Juanino
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: KBI unexpexted change in stable/11 ?

[Mark Saad]

> On Mar 28, 2018, at 9:09 AM, Slawa Olhovchenkov <s...@zxy.spb.ru> wrote:
> 
> I am upgrade system to latest -STABLE and now see kernel crash:
> 
> - loading virtualbox modules build on 11.1-RELEASE-p6
> - loading nvidia module build on 11.1-RELEASE-p6 and start xdm
> 
> Is this expected? I am mean about loading modules builded on
> 11.1-RELEASE on any 11.1-STABLE.
I had a similar issue and it caused a kernel coredump 
I tracked the virtualbox issue to something in the vbox network module . 
Rebuilding it fixes it but I am not sure what broke . I have a kernel core dump 
if anyone wants a peak. 


---
Mark Saad | nones...@longcount.org

> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Problem with USB <---> UPS management connection

[Mark Saad]

All
 I lost power at home and noticed that nut didn’t work right . I had a similar 
dmesg . My box is running 11.1-stable amd64 built from svn 7-8 days ago . When 
I get power back I’ll post details . 

---
Mark Saad | nones...@longcount.org

> On Mar 7, 2018, at 6:55 AM, wishmaster <artem...@ukr.net> wrote:
> 
> Hi, colleagues!
> 
> Something strange happens with a server. I am attempting to connect 
> management interface of UPS with server via USB.
> In console I see a lot of errors:
> 
> Mar  7 13:42:04 xxx kernel: ugen2.2:  at 
> usbus2
> Mar  7 13:42:05 xxx kernel: uhid0 on uhub6
> Mar  7 13:42:05 xxx kernel: uhid0:  0/0, rev 1.10/0.02, addr 2> on usbus2
> Mar  7 13:42:08 xxx kernel: ugen2.2:  at 
> usbus2 (disconnected)
> Mar  7 13:42:08 xxx kernel: uhid0: at uhub6, port 3, addr 2 (disconnected)
> Mar  7 13:42:08 xxx kernel: uhid0: detached
> Mar  7 13:42:12 xxx kernel: ugen2.2:  at 
> usbus2
> Mar  7 13:42:12 xxx kernel: uhid0 on uhub6
> Mar  7 13:42:12 xxx kernel: uhid0:  0/0, rev 1.10/0.02, addr 2> on usbus2
> Mar  7 13:42:16 xxx kernel: ugen2.2:  at 
> usbus2 (disconnected)
> Mar  7 13:42:16 xxx kernel: uhid0: at uhub6, port 3, addr 2 (disconnected)
> Mar  7 13:42:16 xxx kernel: uhid0: detached
> 
> I have changed USB-cables, USB port on the server - without success.
> On another server this problem is absent.
> 
> FreeBSD version: FreeBSD 11.1-STABLE #1 r329364M:
> 
> Any ideas?
> 
> --
> Vitaliy
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: HP Smart array P440 support

[Mark Saad]

Hello
  Have you tried to update the servers firmware using the hp spp or update tool 
. In the past with 9.3 and 10.0 I had boot issues until I updated the servers 
firmware.  I only have a ml10 with a p410 so I can't test much ; my job also 
moved to dell about 2 years ago . 


---
Mark Saad | nones...@longcount.org
  Sep 3, 2017, at 9:10 PM, Priyadarshana Chandrasena <v...@ulka.com.au> wrote:
> 
> I tried to install 11.1 but I still have the same error. UEFI boot mode does
> not see my usb bootable media as of type UEFI. So still the Legacy BIOS is
> the only option. Do I need to create the usb UEFI when I create the usb boot
> disk?. 
> 
> -Original Message-
> From: Maciej Suszko [mailto:mac...@suszko.eu] 
> Sent: Monday, 4 September 2017 4:49 AM
> To: Priyadarshana Chandrasena
> Cc: FreeBSD-stable@FreeBSD.org
> Subject: Re: HP Smart array P440 support
> 
> "Priyadarshana Chandrasena" <v...@ulka.com.au> wrote:
>> I have HP DL20 Gen 9 server. But I can not install FreeBSD 10.2 in it. 
>> I have a HP smart array P440 in my server. I can not find out anywhere 
>> if ciss driver support include HP Gen 9 storage controllers.  Could 
>> you please update the ciss driver in 10.3?
> 
> Hi,
> 
> Got two DL20 with P440, UEFI booted 11.0 to logical disk (raid array).
> In a few days I plan to boot it in HBA mode, we'll see if it's working.
> 
> A few messages:
> #v+
> root@storage-04:~ # uname -a
> FreeBSD storage-04.gr 11.0-RELEASE-p8 FreeBSD 11.0-RELEASE-p8 #0: Wed Feb 22
> 06:12:04 UTC 2017
> r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
> 
> root@storage-04:~ # grep ciss /var/run/dmesg.boot
> ciss0:  port 0x2000-0x20ff mem
> 0x92c0-0x92cf,0x92d0-0x92d003ff at device 0.0 numa-domain 0 on
> pci2
> ciss0: PERFORMANT Transport
> da2 at ciss0 bus 0 scbus2 target 0 lun 0
> 
> root@storage-04:~ # camcontrol inquiry da2
> pass2:  Fixed Direct Access SPC-3 SCSI device
> pass2: Serial Number PDNMF0ARH401MI
> pass2: 135.168MB/s transfers, Command Queueing Enabled
> #v-
> --
> regards, Maciej Suszko.
> 
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: HP Smart array P440 support

[Mark Saad]

All
Also don't forget to is install cciss_vol_status to monitor the array .

---
Mark Saad | nones...@longcount.org

On Sep 2, 2017, at 11:41 AM, sth...@nethelp.no wrote:

>>> I have HP DL20 Gen 9 server. But I can not install FreeBSD 10.2 in it. I
>>> have a HP smart array P440 in my server. I can not find out anywhere if ciss
>>> driver support include HP Gen 9 storage controllers.  Could you please
>>> update the ciss driver in 10.3?
>> 
>> Try 10.3
>> 
>> I know the release-notes say nothing about it, but I believe it is supported.
>> 
>> If not that, 11.0 surely does (even though the release-notes don$,1ry(Bt 
>> mention it, either)
> 
> I can confirm that 10.3 supports the P440 controller. From a DL360 Gen9
> server running 10.3 here:
> 
> ciss0:  port 0x2000-0x20ff mem 
> 0x92c0-0x92cf,0x92d0-0x92d003ff irq 16 at device 0.0 on pci3
> ciss0: PERFORMANT Transport
> ...
> da0 at ciss0 bus 0 scbus0 target 0 lun 0
> da0:  Fixed Direct Access SPC-3 SCSI device
> da0: Serial Number PDNLH0BRH8S3RF
> da0: 135.168MB/s transfers
> da0: Command Queueing enabled
> da0: 139979MB (286677120 512 byte sectors)
> 
> Steinar Haug, Nethelp consulting, sth...@nethelp.no
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Dell r630 UEFI Boot Issues on 11.1-BETA1

[Mark Saad]

All
 I ran in to this issue on stable/11 today . I feel like I saw this in
the past but I can't track it down.
This is a new install on a brand new Dell r630 fitted with 2x
e5-2699v4 cpus . Fresh install of 11.0-RELEASE amd64 install . The
install is a ZFS pool on a ssd. I checked out svn stable/11 and built
and installed world.  The subsequent reboot died with what appears to
be an issue with the ZFS EFI loader. I uploaded a screen shot to imgur
. http://imgur.com/t9clwXL

The Text is a follows

Start @ 0x80302000 ...
EFI framebuffer information:
addr, size   0x9000, 0x30
dimensions 1024 x 768
stride 1024
masks0x00ff, 0xff00, 0x00ff, 0xff00
bi_load_efi_data: GetMemoryMap error 5
_

Any one have any ideas here ?



-- 
mark saad | nones...@longcount.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Errors with ports on 9.3..

[Mark Saad]

> On Jun 3, 2017, at 3:10 PM, Mark Saad <nones...@longcount.org> wrote:
> 
> 
> 
>> On Jun 3, 2017, at 2:24 PM, Adam Vande More <amvandem...@gmail.com> wrote:
>> 
>>> On Sat, Jun 3, 2017 at 12:19 PM, Howard Leadmon <how...@leadmon.net> wrote:
>>>Thanks for the update, I had the feeling the issue was from it being to 
>>> old.   I have a question, not sure if you know, but I will toss it out.   
>>> As I mentioned I update using svn for both src and ports, and I am curious 
>>> to know if I can actually bring my src tree up to the most current 10.x 
>>> stable, recompile, and install and have it all run?
> 
> So here is my take on the update . For starters if you are using a stock 
> binary 9.3-RELEASE you can use freebsd-update to go 9.3 -> 10.1 , 10.1 -> 
> 10.3  , 10.3 -> 11.0 . In theory freebsd-update should allow for 9.x -> 10.x 
> but there was some breakage in the 10's FreeBSD updates that prevented this .
> 
> If you decided to do a source build you can go 9.x to 10.3 w/o much. 

I meant to say trouble but I accidentally hit send . 


Another option is to download the binary sets from ftp.freebsd.org 

ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/11.0-RELEASE/

Now with some care you can backup your 9 kernel to kernel.old and untar the 
kernel tar to /boot . Then reboot in single user . Backup your etc and extract 
the base tar and then using etcupdate for fixing etc or manually fix it with 
your backup . Then reboot and fix the ports using pkg -f install pkg && pkg 
upgrade .  However if you haven't done this before it can be error prone if . 

Also you can look into boot environments for zfs but if memory serves me right 
it's not fully baked into 9.x and it may not work right . 

> 
>>> 
>>>  In the past with much older versions, I know file system changes and such 
>>> make it pretty hard to jump major revisions,
>>> so have a little bit of fear about jumping from 9.x to 10.x, and possibly 
>>> even to 11.x if that is now stable.   I am using ZFS, so I guess that would 
>>> be one thing that is outside the norm, but should be part of the base 
>>> kernels now anyway.
>>> 
>>>  Any input on upgrading would be most appreciated...

Honestly 11 has been very stable . There are issues but nothing that has wanted 
me to roll back to 10 . 

I am using 10.3-STABLE from about a year ago for my routers and 11.0-STABLE 
from April for general use and it's been good and crash free. Knock on wood . 

One thing to remember is upgrading the zpool and zfs version/ feature flags . 
Al la zfs upgrade pool0/foo . This is a one time job ; with no way to go back . 
So save this for last after your box has settled down and you are comfortable. 

>> 
>> I don't know what you know I guess, but it should work following these 
>> instructions:
>> 
>> https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
>> 
>> or these:
>> 
>> https://www.freebsd.org/doc/handbook/updating-upgrading.html
>> 
>> or these:
>> 
>> https://www.freebsd.org/releases/11.0R/installation.html
>> 
>> It is probably wise to make a backup and do a test first.
>> 
>> -- 


>> Adam


---
Mark Saad | nones...@longcount.org


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Errors with ports on 9.3..

[Mark Saad]

> On Jun 3, 2017, at 2:24 PM, Adam Vande More  wrote:
> 
>> On Sat, Jun 3, 2017 at 12:19 PM, Howard Leadmon  wrote:
>>Thanks for the update, I had the feeling the issue was from it being to 
>> old.   I have a question, not sure if you know, but I will toss it out.   As 
>> I mentioned I update using svn for both src and ports, and I am curious to 
>> know if I can actually bring my src tree up to the most current 10.x stable, 
>> recompile, and install and have it all run?

So here is my take on the update . For starters if you are using a stock binary 
9.3-RELEASE you can use freebsd-update to go 9.3 -> 10.1 , 10.1 -> 10.3  , 10.3 
-> 11.0 . In theory freebsd-update should allow for 9.x -> 10.x but there was 
some breakage in the 10's FreeBSD updates that prevented this .

If you decided to do a source build you can go 9.x to 10.3 w/o much.


>> 
>>  In the past with much older versions, I know file system changes and such 
>> make it pretty hard to jump major revisions,
>> so have a little bit of fear about jumping from 9.x to 10.x, and possibly 
>> even to 11.x if that is now stable.   I am using ZFS, so I guess that would 
>> be one thing that is outside the norm, but should be part of the base 
>> kernels now anyway.
>> 
>>  Any input on upgrading would be most appreciated...
> 
> I don't know what you know I guess, but it should work following these 
> instructions:
> 
> https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
> 
> or these:
> 
> https://www.freebsd.org/doc/handbook/updating-upgrading.html
> 
> or these:
> 
> https://www.freebsd.org/releases/11.0R/installation.html
> 
> It is probably wise to make a backup and do a test first.
> 
> -- 
> Adam
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Errors with ports on 9.3..

[Mark Saad]

Howard 
 There are 3 options . One upgrade to 10.x or 11.x and ports/pkg will work . 
Support for the 9 series and 10.1 and 10.2 was removed from ports a few months 
ago . Two check out ports via svn and use the tag RELEASE_9_EOL and use that as 
your starting point . This is ports before the support for 9 was dropped . It's 
not up to date but it will work .Lastly you could use pkgsrc from netbsd not 
Joynet , and do a full rebuild of what you need . Pkgsrc also has a pkgsrc to 
ports conversion tool if you want the subsequent pkgsrc packages registered in 
a FreeBSD standard pkg dir . This would work if you haven't converted 9 to use 
pkgng . 

https://svnweb.freebsd.org/ports/tags/RELEASE_9_EOL/

https://www.pkgsrc.org/



---
Mark Saad | nones...@longcount.org

> On Jun 3, 2017, at 11:39 AM, Howard Leadmon <how...@leadmon.net> wrote:
> 
> I know 9.3 is kinda dated, but it had been running fine so I left the servers 
> alone as they were in a remote location many hours away.
> 
> That said, if I try and do anything with ports (I keep everything updated 
> using SVN), I get the following error:
> 
> "/usr/ports/Mk/bsd.port.mk", line 1038: Unknown directive
> 
> The line is:   .export LANG LC_ALL
> 
> 
> I even tried removing the ports tree, and bringing it all back down, but same 
> error.   Maybe my googlefu is failing me, but I couldn't find this exact 
> error listed anyplace.   I have a couple FBSD 9.3 machines still in 
> existence, and they all do this with anything in ports now.
> 
> Any ideas or suggestions?  Would just taking SVN to the current 10.x fix this?
> 
> ---
> Howard Leadmon
> PBW Communications, LLC
> http://www.pbwcomm.com
> 
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Update netmap for 11.1-RELEASE

[Mark Saad]

+1

On Wed, May 24, 2017 at 1:09 PM, George Amanakis via freebsd-stable
<freebsd-stable@freebsd.org> wrote:
> Regarding the upcoming 11.1-RELEASE:
> Could somebody update netmap from CURRENT to STABLE, so that it would make it 
> into 11.1-RELEASE?
> I would really like to see ptnet and ptnetmap in 11.1-RELEASE.
>
> Thank you!
> George
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"



-- 
mark saad | nones...@longcount.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Help! two machines ran out of swap and corrupted their zpools!

[Mark Saad]

On Mon, Nov 21, 2016 at 12:50 PM, Jan Bramkamp <cr...@rlwinm.de> wrote:
> On 21/11/2016 18:47, Pete French wrote:
>>
>> So, I am off sick and my colleagues decided to load test our set of five
>> servers excesively. All ran out of swap. So far so irritating, but whats
>> has
>> happened is that twoof them now will not boot, as it appears the ZFS pool
>> they are booting from has become corrupted.
>>
>> One starts to boot, then crases importing the root pool. The other doenst
>> even get that far with gptzfsboot saying it can't find the pool to boot
>> from!
>>
>> Now I can recover these, but I am a bit worried, that it got like this at
>> all, as I havent ever seen ZFS corrupt a pool like this. Anyone got any
>> insights,
>> or suggstions as to how to stop it happening again ?
>>
>> We are swapping to a separate partition, not to the pool by theway.
>
>
> How much trust do you put in your hardware? Have you ever put the hardware
> under full load for extended periods before e.g. run poudriere to build pkg
> repos?
>
> -- Jan Bramkamp
>
> _



Pete
   I am thinking like Jan, that this points to a hardware issue. What
can you tell us about the servers ? What sort of cpu, do you have ecc
ram ? How much ram what was running at the time ? Do you use a slog,
l2arc , whats
the zpool status -v show?


__
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"



-- 
mark saad | nones...@longcount.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: iicsmb

[Mark Saad]

On Thu, Oct 6, 2016 at 5:39 AM, Mark Dixon <mnd...@gmail.com> wrote:

> If I load the module on my laptop (Lenovo Thinkpad X1 Carbon), I get:
>
> iicsmb0:  on iicbus0
> iicsmb1:  on iicbus1
> iicsmb2:  on iicbus2
> iicsmb3:  on iicbus3
> iicsmb4:  on iicbus4
> iicsmb5:  on iicbus5
> iicsmb6:  on iicbus6
> iicsmb7:  on iicbus7
> iicsmb8:  on iicbus8
> iicsmb9:  on iicbus9
> iicsmb10:  on iicbus10
> iicsmb11:  on iicbus11
> smbus1:  on iicsmb0
> smbus2:  on iicsmb1
> smbus3:  on iicsmb2
> smbus4:  on iicsmb3
> smbus5:  on iicsmb4
> smbus6:  on iicsmb5
> smbus7:  on iicsmb6
> smbus8:  on iicsmb7
> smbus9:  on iicsmb8
> smbus10:  on iicsmb9
> smbus11:  on iicsmb10
> smbus12:  on iicsmb11
>
> I have no idea what this means though.
>
> Regards,
>
> Mark


Andriy
 Likewise I have devices that appear but not sure what they are. I am on
smbios.planar.maker="BIOSTAR Group"
smbios.planar.product="A68I-350 DELUXE"

iicsmb0:  on iicbus0
iicsmb1:  on iicbus1
iicsmb2:  on iicbus2
iicsmb3:  on iicbus3
iicsmb4:  on iicbus4
iicsmb5:  on iicbus5
iicsmb6:  on iicbus6
iicsmb7:  on iicbus7
smbus0:  on iicsmb0
smbus1:  on iicsmb1
smbus2:  on iicsmb2
smbus3:  on iicsmb3
smbus4:  on iicsmb4
smbus5:  on iicsmb5
smbus6:  on iicsmb6
smbus7:  on iicsmb7

root@ostrich:~ # ls -l /dev/iic*
crw---  1 root  wheel  0x6d Sep 26 16:21 /dev/iic0
crw---  1 root  wheel  0x6e Sep 26 16:21 /dev/iic1
crw---  1 root  wheel  0x6f Sep 26 16:21 /dev/iic2
crw---  1 root  wheel  0x70 Sep 26 16:21 /dev/iic3
crw---  1 root  wheel  0x71 Sep 26 16:21 /dev/iic4
crw---  1 root  wheel  0x72 Sep 26 16:21 /dev/iic5
crw---  1 root  wheel  0x73 Sep 26 16:21 /dev/iic6
crw---  1 root  wheel  0x77 Sep 26 16:21 /dev/iic7

probing them with smbmsg doesn't return any data.

-- 
mark saad | nones...@longcount.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: File Name Too Long?

[Mark Saad]

snapshot is /.zfs/snapshot/11.0-RELEASE-r306379-2016.09.28--bsnap
>>> >
>>> > So its not just the last component of the zfs dataset name, which is
>>> > in this case the same.
>>> >
>>> > I am trying to wrap my head around this and find where the limit is so
>>> > I can adjust my naming conventions used and actually get backups of
>>> > all of my data. Turns out all of my jail operating system paths aren't
>>> > being backed up, fortunately at least all of the data file systems for
>>> > the jails are.
>>>
>>> I found a solution, I was naming the snapshots with the dataset name,
>>> which I think was causing the issue.
>>>
>>> The following didn't seem to long to be an issue
>>> /jails/unifi/ROOT/.zfs/snapshot/11.0-RELEASE-r306379-2016.09.28--bsnap
>>>
>>> But apparently the snapshot name was
>>> zraid/jails/unifi/11.0-RELEASE-r306379-2016.09.28@11.0-
>>> RELEASE-r306379-2016.09.28--bsnap
>>>
>>> Still not sure how it adds up to too long, both full paths together
>>> aren't over 255, at 160, but apparently something else is added in
>>> there. I was able to easily modify my backup script to not include the
>>> last part of the dataset in the snapshot name and simply use -bsnap-, as
>>> the name. it appears to avoid all the issues, and my backups from last
>>> night include all the files.
>>>
>>> /jails/unifi/ROOT/.zfs/snapshot/-bsnap-
>>> zraid/jails/unifi/11.0-RELEASE-r306379-2016.09.28@-bsnap-
>>>
>>> The total path now only adds up to 98, I haven't done any testing yet to
>>> find out where the limit is hit, The longest combination of these I had
>>> last night would have added up to 135, and that worked
>>>
>>> --
>>> Thanks,
>>> Dean E. Weimer
>>> http://www.dweimer.net/
>>>
>>
>>
>> This may be related:
>>
>> http://iocage.readthedocs.io/en/latest/known-issues.html#cha
>> racter-mount-path-limitation
>>
>> Priyadarshan
>>
>
>
Having run into this before in nfs exports , and pulling my hair out; I ran
into this fix . I know its from a long time ago; but I am willing to put up
a bounty to get this bumped to 512

http://www.secnetix.de/olli/FreeBSD/mnamelen.hawk


> Thanks, that's probably it, the original snapshot name with its full data
> set path added up to 89, with that in mind I can edit my script to throw a
> warning if this limit is hit so that my backup logs will let me know if a
> data set gets missed. I need to edit it anyways so that a warning gets
> logged on the mount failure which was already occurring. It looks like I
> escaped the errors, so that the script returned successful and didn't make
> the Bacula backup job fail so that the data that did get mounted would be
> backed up, but forgot to write the error to the log.
>
> --
> Thanks,
>Dean E. Weimer
>http://www.dweimer.net/
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>



-- 
mark saad | nones...@longcount.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 10.3-BETA2 regression in MPT

[Mark Saad]

TMK,

On Fri, Feb 19, 2016 at 9:44 AM, Terry Kennedy <te...@glaver.org> wrote:

> > Can you get the status of the controller and disks via mptutil ? Also
> > what does camcontrol devlist -v show ?
>
>   8.4 (8-STABLE):
>
> # mptutil show adapter
> mpt0 Adapter:
>Board Name: SAS6IR
>Board Assembly:
> Chip Name: C1068E
> Chip Revision: UNUSED
>   RAID Levels: RAID0, RAID1, RAID1E
> RAID0 Stripes: 64k
>RAID1E Stripes: 64k
>  RAID0 Drives/Vol: 2-10
>  RAID1 Drives/Vol: 2
> RAID1E Drives/Vol: 3-10
>
> # mptutil show drives
> mpt0 Physical Drives:
>0 (  137G) ONLINE  SAS bus 0 id 1
>1 (  137G) ONLINE  SAS bus 0 id 9
>
> # mptutil show volumes
> mpt0 Volumes:
>   Id SizeLevel   Stripe  State  Write-Cache  Name
>  0 (  136G) RAID-1  OPTIMAL   Enabled
>
> # camcontrol devlist -v
> scbus0 on mpt0 bus 0:
>at scbus0 target 0 lun 0 (da0,pass0)
> at scbus0 target 8 lun 0 (ses0,pass1)
> <> at scbus0 target -1 lun -1 ()
> scbus1 on mpt0 bus 1:
>at scbus1 target 0 lun 0 (pass2)
> <> at scbus1 target -1 lun -1 ()
> scbus-1 on xpt0 bus 0:
> <> at scbus-1 target -1 lun -1 (xpt0)
>
> 10.3-BETA2:
>
> # mptutil show adapter
> mpt0 Adapter:
>Board Name: SAS6IR
>Board Assembly:
> Chip Name: C1068E
> Chip Revision: UNUSED
>   RAID Levels: RAID0, RAID1, RAID1E
> RAID0 Stripes: 64K
>RAID1E Stripes: 64K
>  RAID0 Drives/Vol: 2-10
>  RAID1 Drives/Vol: 2
> RAID1E Drives/Vol: 3-10
>
> # mptutil show drives
> mpt0 Physical Drives:
>0 (  137G) ONLINE  SAS bus 0 id 1
>1 (  137G) ONLINE  SAS bus 0 id 9
>
> # mptutil show volumes
> mpt0 Volumes:
>   Id SizeLevel   Stripe  State  Write-Cache  Name
>  0 (  136G) RAID-1  OPTIMAL   Enabled
>
> # camcontrol devlist -v
> scbus0 on mpt0 bus 0:
>at scbus0 target 0 lun 0 (pass0,da0)
> at scbus0 target 8 lun 0 (ses0,pass1)
> <> at scbus0 target -1 lun  ()
> scbus1 on mpt0 bus 1:
>at scbus1 target 0 lun 0 (pass2)
> <> at scbus1 target -1 lun  ()
> scbus2 on ata2 bus 0:
>at scbus2 target 1 lun 0 (pass3,cd0)
> <> at scbus2 target -1 lun  ()
> scbus3 on ata3 bus 0:
> <> at scbus3 target -1 lun  ()
> scbus4 on ata4 bus 0:
> <> at scbus4 target -1 lun  ()
> scbus5 on ata5 bus 0:
> <> at scbus5 target -1 lun  ()
> scbus-1 on xpt0 bus 0:
> <> at scbus-1 target -1 lun  (xpt0)
>
>   To clarify, things seem to work fine on 10.3-BETA2 after the system
> has booted, but there is a _long_ pause while the kernel is probing
> the mpt0 controller, followed by the spew of CAM error messages from
> the probes.
>
>   Let me know if you need any additional info.
>
> Terry Kennedy http://www.glaver.org  New York, NY USA
>


Can you build 10-STABLE and merge back the mpt driver prior to r285840 . It
looks like a change was merged in about 7 weeks ago that
has to do with probing the devices.

https://svnweb.freebsd.org/base/stable/10/sys/dev/mpt/mpt.c?view=log





  <https://svnweb.freebsd.org/base?view=revision=285840>

-- 
mark saad | nones...@longcount.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 10.3-BETA2 regression in MPT

[Mark Saad]

2 00 00 00 24 00 
> (probe1:mpt0:1:1:0): CAM status: Unrecoverable Host Bus Adapter Error
> (probe1:mpt0:1:1:0): Retrying command
> (probe1:mpt0:1:1:0): INQUIRY. CDB: 12 00 00 00 24 00 
> (probe1:mpt0:1:1:0): CAM status: Unrecoverable Host Bus Adapter Error
> (probe1:mpt0:1:1:0): Error 5, Retries exhausted
> da0 at mpt0 bus 0 scbus0 target 0 lun 0
> ses0 at mpt0 bus 0 scbus0 target 8 lun 0
> pass2 at mpt0 bus 1 scbus1 target 0 lun 0
> 
>  I can try to narrow down when this regression was introduced, but I fig-
> ured I'd report it in case somebody has an "ah-hah" moment from seeing it.
> 
>  Also, there has always been an issue with passthru on these controllers -
> as you can see above, there are 2 physical disks attached to the controller,
> used as a mirror volume. But only one of the members appears as a passN de-
> vice, which means that the other one can't be monitored with smartmontools.
> If I'm remembering correctly, a volume with more than 2 drives creates a
> passN device for all but one of the drives.
> 
>Terry Kennedy http://www.glaver.org  New York, NY USA
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


---
Mark Saad | nones...@longcount.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: ZFS ARC vs Inactive memory on 10-STABLE: is it Ok?

[Mark Saad]

On Mon, Feb 15, 2016 at 9:29 AM, Lev Serebryakov <l...@freebsd.org> wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
>
>  I have mostly-storage server with 8GB of physical RAM and 9TB (5x2TB
> HDD) raidz ZFS pool (so, about 6.5TB usable space).
>
>  ARC is limited to 3GB by vfs.zfs.arc_max.
>
>  This server runs Samba (of course), CrashPlan backup client (Linux
> Java!), and torrent client (transmission-daemon).
>
>
Wow someone else as crazy as I was. :)


>  And I'm noticing this regularly ("screenshot" of top(1)):
>
> Mem: 1712M Active, 3965M Inact, 2066M Wired, 137M Cache, 822M Buf,
> 4688K Free
> ARC: 421M Total, 132M MFU, 54M MRU, 1040K Anon, 7900K Header, 227M Other
> Swap: 4096M Total, 248M Used, 3848M Free, 6% Inuse
>
>  As you can see, here are almost 4G of Inactive memory and only 412M
> of ARC!
>
>  Is it Ok? Why Inactive memory (non-dirty buffers?) are pressed ARC
> out of memory?
>
>
Lev so I ran a similar setup on 10.1-RELEASE with 40TB in a raid 1+0 like
zpool . My top looked similar but its been a while
and i had 24G of ram. With a 12G Arc max. I always wondered what was going
on here but I suspected it was due to a interaction of java and arc
eviction.
The crash plan app is terrible and would "start doing something new" up and
look hung. Disk io went to hell etc . Then things would settle down and
start chugging away.
Keep in mind crash plan would take like a month to back up 2TB of changes
on this thing.  I eventually convinced management to move to a automated
tape library
and a normal backup client ( netbackup )  for the backups.  Also I
abandoned this project about 18 months ago too .



- --
> // Lev Serebryakov
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
>
> iQJ8BAEBCgBmBQJWweC0XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
> ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF
> QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePRTYP/RHajhE+EuvX3fCppShb/BSg
> vpJZ8F1jeInIOVXe/XLw07jht04uquTXHsMvw6F0J+WIIqsCld53q1bfj4CWAnl6
> 4TjULTZYUWANv3wK6KxItEN5eMmDEPOW6Eqls57OSCFcZA/32hyf/Y15Nec0L6JD
> sd8wpqUvQs0zb//frbUpjIRcfoVSMO2ip4doGPDtBv9IcE/kDz78IcmU9By2deXU
> IJE8Xlg2hDY+f/NhTR2sCuwtCSvpL9/mBztffYqsKQsAm8oIn0Sz9mNdjVzUR+rN
> lF4GoxcWf6c3HEM/LF4+dgOdb058YwO4amyUI7GoBSFBQq3OlJzvomGeOi2vPAvC
> BkWxOWOcWsmEwfk1b22k00yNAjvaXQsCx6r2L/6vyrAtoQ0moXF4Rks8+MLFRUTu
> FFke93UUPRQPXBdrBtlnFpXX6jpmlEm7g9pazarGc4hteYOKpvHajFvNvAB7RswI
> NQL70+QfLBgtaA5683scCuURNptStf/RfvhwjW/o5DPNLv+NHnT+nPk64MTDuaZD
> 4z9Kcj088KjB++xt9c6BXuCS4zlkyUhas5cNGG+SxupZajtIuaCBTeUv0QwjnDH5
> Pnu44Xe4MCvpDSt9odICdzytxO6yzwL7mLj70o2SsPs2ijN1w/fOlNqS46bekmJ/
> MtvVwObCRnoDg3aMRUL0
> =In6V
> -END PGP SIGNATURE-
> ___
> freebsd...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-fs
> To unsubscribe, send any mail to "freebsd-fs-unsubscr...@freebsd.org"
>



-- 
mark saad | nones...@longcount.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: dev/random warning on 10-STABLE after r292122 up till r292855

[Mark Saad]

On Tue, Jan 5, 2016 at 8:45 AM, Adam Vande More <amvandem...@gmail.com>
wrote:

> On Mon, Jan 4, 2016 at 3:44 PM, Mark Saad <nones...@longcount.org> wrote:
>
>> All
>>  At NYC*BUG we are looking into a warning seen on FreeBSD 10-STABLE amd64
>> starting at or about r292122  and still up till r292855.
>>
>> On boot dmesg logs the following warning not seen on 10.2-RELEASE amd64.
>>
>> random device not loaded; using insecure entropy
>>
>> The full dmesg can be seen here
>> http://dmesgd.nycbug.org/index.cgi?action=dmesgd=view=2871
>>
>> I checked in svn and there are no recent changes to sys/dev/random .
>>
>> Does anyone have any insight into this ?
>>
>
> It's more of an informational message about seeding the random number
> generator.  Probably man 4 random is the best explanation.
>
>
>
> --
> Adam
>

Adam
  Not sure why I didn't think of that, thanks for the pointer;  I didn't
see any change in the relevant default sysctls .

On a 10-RELEASE box no warning

[msaad@ny4-c108-nocbox ~]$ uname -a
FreeBSD ny4-c108-nocbox 10.2-RELEASE-p7 FreeBSD 10.2-RELEASE-p7 #0: Mon
Nov  2 14:19:39 UTC 2015
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
amd64
[msaad@ny4-c108-nocbox ~]$ sysctl kern.random
kern.random.sys.harvest.swi: 1
kern.random.sys.harvest.interrupt: 1
kern.random.sys.harvest.point_to_point: 1
kern.random.sys.harvest.ethernet: 1
kern.random.sys.seeded: 1
kern.random.yarrow.slowoverthresh: 2
kern.random.yarrow.slowthresh: 128
kern.random.yarrow.fastthresh: 96
kern.random.yarrow.bins: 10
kern.random.yarrow.gengateinterval: 10
kern.random.live_entropy_sources:
kern.random.active_adaptor: yarrow
kern.random.adaptors: yarrow,dummy


-
On 10-STABLE with warning

msaad@smokeping:~ % uname -a
FreeBSD smokeping 10.2-STABLE FreeBSD 10.2-STABLE #0 r292855: Tue Dec 29
06:17:50 UTC 2015
r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC
amd64
msaad@smokeping:~ % sysctl kern.random
kern.random.sys.harvest.swi: 1
kern.random.sys.harvest.interrupt: 1
kern.random.sys.harvest.point_to_point: 1
kern.random.sys.harvest.ethernet: 1
kern.random.sys.seeded: 1
kern.random.yarrow.slowoverthresh: 2
kern.random.yarrow.slowthresh: 128
kern.random.yarrow.fastthresh: 96
kern.random.yarrow.bins: 10
kern.random.yarrow.gengateinterval: 10
kern.random.live_entropy_sources:
kern.random.active_adaptor: yarrow
kern.random.adaptors: yarrow,dummy



-- 
mark saad | nones...@longcount.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: dev/random warning on 10-STABLE after r292122 up till r292855

[Mark Saad]

On Tue, Jan 5, 2016 at 2:00 PM, Peter Jeremy <pe...@rulingia.com> wrote:

> On 2016-Jan-04 16:44:49 -0500, Mark Saad <nones...@longcount.org> wrote:
> >On boot dmesg logs the following warning not seen on 10.2-RELEASE amd64.
> >
> >random device not loaded; using insecure entropy
>
> When I first noticed this, I investigated and worked out that it's
> related to how the random device initialises itself and its data and
> entropy sources.  In particular, it reflects the state of the random
> device at that point in time, not at any later point when random data
> is actually requested.
>
> I agree that the wording of this message could unnecessarily alarm a
> sysadmin and think it could be done better.  IMHO, this sort of
> alamist message should only be output if there is no decent entropy
> source available when the random device is unblocked.
>
> --
> Peter Jeremy
>

Peter
 I agree it looks like its not really a big deal; what I cant find is what
changed to make this even print out. The commits for this warning are from
a long time ago. Off hand they are from 2014 or 2012. There were no changes
to sys/dev/random in as much time; so I cant figure out what changed to
make this even print out.


-- 
mark saad | nones...@longcount.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

dev/random warning on 10-STABLE after r292122 up till r292855

[Mark Saad]

All
 At NYC*BUG we are looking into a warning seen on FreeBSD 10-STABLE amd64
starting at or about r292122  and still up till r292855.

On boot dmesg logs the following warning not seen on 10.2-RELEASE amd64.

random device not loaded; using insecure entropy

The full dmesg can be seen here
http://dmesgd.nycbug.org/index.cgi?action=dmesgd=view=2871

I checked in svn and there are no recent changes to sys/dev/random .

Does anyone have any insight into this ?



-- 
mark saad | nones...@longcount.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Interesting Boot failure on HEAD with a large number of IGB nics

[Mark Saad]

All
 I am wondering if anyone has run into this issue before , and if there is
a fix.
I have a Scalable Informatics siRouter with 24 Intel I350 igb nics and 8
intel 82599ES ixgbe/ix nic . The SiRouter is a Supermicro X9DRX+-F with a
bunch of intel nics.

On Head I run into a boot panic out of the box while plumbing the usb
controller . The box crashes with

ehci0: Intel Patsburg USB 2.0 controller mem 0xdd923000-0xdd9233ff irq 16
at device 26.0 on pci0
panic: Couldn't find an APIC vector for IRQ 16

However it has only probed 8 of the 24 igb when is crashes. Here is the
complete boot up with some additional info.

http://pastebin.com/MfbEwwg4

Now the interesting thing.

 DragonFly 4.2x boots fine  see the dmesg here
http://dmesgd.nycbug.org/index.cgi?action=dmesgddo=viewid=2778

OpenBSD boots and finds the nics as well see dmesg here
http://dmesgd.nycbug.org/index.cgi?action=dmesgddo=viewid=2777

NetBSD Pukes while probing something out of the box and I cant get the
serial console to work.

Linux 2.6 CentOS 6.6 works

OmniOS / Illumos-gate and Illumos-joyent work out of the box



So my goal here is to make the box boot FreeBSD . It had been used prior
running OmniOS and CentOS and well now I want to make it work. :)

Any ideas here ?

mark saad | nones...@longcount.org
___
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: Interesting Boot failure on HEAD with a large number of IGB nics

[Mark Saad]

On Wed, Jul 22, 2015 at 1:54 PM, Garrett Cooper yaneurab...@gmail.com
wrote:


  On Jul 22, 2015, at 10:14, Gary Palmer gpal...@freebsd.org wrote:

 ...

  I'm no expert, but you may want to try setting
 
  hw.igb.num_queues=1
 
  and maybe
 
  hw.ixgbe.num_queues=1
 
  in the boot loader and trying that.

 There was another discussion that took place around June on current that
 might be helpful. I think the solution boiled down to what Gary described
 above, because the driver auto tuning was broken...
 Thanks!
 -NGie


NGie
 I'll try the queues option but; why was does that kill my ehci hub ? Note

ehci0: Intel Patsburg USB 2.0 controller mem 0xdd923000-0xdd9233ff irq 16
at device 26.0 on pci0
panic: Couldn't find an APIC vector for IRQ 16


-- 
mark saad | nones...@longcount.org
___
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: nfsd CPU usage?

[Mark Saad]

 On Sep 19, 2013, at 2:50 AM, Eggert, Lars l...@netapp.com wrote:
 
 On Sep 11, 2013, at 15:08, Lars Eggert l...@netapp.com wrote:
 Thanks, I will watch out for the MFC and test.
 
 I've been running for a day or so after the MFC, and CPU loads are WAY down. 
 Plus, the cache issues I had haven't reappeared either.
 
 I need to bang on it some more, but for now it seems great.
 
 Lars


has this issue been brought to re@ for inclusion in 9.2 ? 

---
Mark saad | mark.s...@longcount.org

___
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: nfsd CPU usage?

[Mark Saad]

Rick
  Would this affect 9.2-RCn ? 

---
Mark saad | mark.s...@longcount.org


On Sep 11, 2013, at 7:54 AM, Rick Macklem rmack...@uoguelph.ca wrote:

 Lars Eggert wrote:
 Hi,
 
 I'm seeing extremely high CPU usage withssh-st the new nfsd:
 
  PID USERNAME   PRI NICE   SIZERES STATE   C   TIME   WCPU
  COMMAND
 2280 root   1020  9932K  1376K *nfs_c  0 320:11 100.00%
 nfsd{nfsd: service}
 2280 root   1020  9932K  1376K CPU77 319:47 100.00%
 nfsd{nfsd: service}
 2280 root   1020  9932K  1376K CPU55 318:25 100.00%
 nfsd{nfsd: service}
 2280 root   1020  9932K  1376K CPU66 318:20 100.00%
 nfsd{nfsd: service}
 2280 root520  9932K  1376K CPU00 317:32 100.00%
 nfsd{nfsd: service}
 2280 root   1020  9932K  1376K *nfs_c  1 315:41 99.17%
 nfsd{nfsd: service}
 2280 root520  9932K  1376K *nfs_c  4 320:22 98.78%
 nfsd{nfsd: master}
 2280 root   1020  9932K  1376K *nfs_c  1 317:10 98.10%
 nfsd{nfsd: service}
 
 And this is at a few hundred KB/s with only a few clients:
 
 ifstat -i igb1 10
   igb1
 KB/s in  KB/s out
  796.56208.66
  431.19232.36
  316.11280.31
 1005.96523.42
 1077.74342.25
  340.63217.73
 1067.96330.56
  487.91235.61
 
 Any ideas?
 
 FreeBSD stanley.muccbc.hq.netapp.com 9.2-PRERELEASE FreeBSD
 9.2-PRERELEASE #7: Wed Sep  4 11:06:31 CEST 2013
r...@stanley.muccbc.hq.netapp.com:/usr/obj/usr/src/sys/STANLEY
 amd64
 
 Thanks,
 Lars
 There is a patch in head (r254337) that I believe handles this.
 It will be MFC'd to stable/9 in about a week, unless someone finds
 problems with it before then.
 If you want a semantically equivalent (but uglier code) patch,
 you can find it here:
  http://people.freebsd.org/~rmacklem/drc4-stable9.patch
 After applying the patch, you need to set sysctl variable(s),
 to avoid the aggressive trimming of stale DRC entries. Garrett
 Wollman suggests the following for a large server:
 vfs.nfsd.tcphighwater=10
 vfs.nfsd.tcpcachetimeout=300 (5 minutes instead of default of several hrs)
 
 You can also use the sysctl
 vfs.nfsd.cachetcp=0
 to disable use of the DRC for TCP.
 
 The old nfs server did not use the DRC for TCP. The assumption being that
 TCP layer retransmits are good enough to maintain reliable RPC transport.
 Unfortuantely, you can get file corruption when the server reboots or
 there is a network partitioning, if the client chooses to redo the RPC
 over TCP (clients always do this after having to create a new TCP connection).
 In other words, vfs.nfsd.cachetcp=0 is roughly what the old nfsd did.
 
 If you don't want to patch the 9.2 code, you can edit the sources
 (sys/fs/nfsserver/nfs_nfsdcache.c) and change the line:
 static int nfsrc_tcpnonidempotent = 1;
 to
 static int nfsrc_tcpnonidempotent = 0;
 to do the same thing as vfs.nfsd.cachetcp=0
 
 rick
 ___
 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
___
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: svn commit: r255104 - stable/9/sys/ufs/ufs

[Mark Saad]

Kirk
  Will this be merged into 9.2-RC? Before the Release ?  

---
Mark saad | mark.s...@longcount.org


On Aug 31, 2013, at 1:38 PM, Kirk McKusick mckus...@freebsd.org wrote:

 Author: mckusick
 Date: Sat Aug 31 17:38:49 2013
 New Revision: 255104
 URL: http://svnweb.freebsd.org/changeset/base/255104
 
 Log:
  MFC of 253998:
 
  This bug fix is in a code path in rename taken when there is a
  collision between a rename and an open system call for the same
  target file. Here, rename releases its vnode references, waits for
  the open to finish, and then restarts by reacquiring its needed
  vnode locks. In this case, rename was unlocking but failing to
  release its reference to one of its held vnodes. The effect was
  that even after all the actual references to the vnode had gone,
  the vnode still showed active references. For files that had been
  removed, their space was not reclaimed until the filesystem was
  forcibly unmounted.
 
  This bug manifested itself in the Postgres server which would
  leak/lose hundreds of files per day amounting to many gigabytes of
  disk space. This bug required shutting down Postgres, forcibly
  unmounting its filesystem, remounting its filesystem and restarting
  Postgres every few days to recover the lost space.
 
  Reported by: Dan Thomas and Palle Girgensohn
  Bug-fix by:  kib
  Tested by:   Dan Thomas and Palle Girgensohn
 
 Modified:
  stable/9/sys/ufs/ufs/ufs_vnops.c
 Directory Properties:
  stable/9/sys/   (props changed)
 
 Modified: stable/9/sys/ufs/ufs/ufs_vnops.c
 ==
 --- stable/9/sys/ufs/ufs/ufs_vnops.cSat Aug 31 17:33:25 2013(r255103)
 +++ stable/9/sys/ufs/ufs/ufs_vnops.cSat Aug 31 17:38:49 2013(r255104)
 @@ -1271,7 +1271,7 @@ relock:
error = VFS_VGET(mp, ino, LK_EXCLUSIVE, nvp);
if (error != 0)
goto releout;
 -VOP_UNLOCK(nvp, 0);
 +vput(nvp);
atomic_add_int(rename_restarts, 1);
goto relock;
}
 ___
 svn-src-stabl...@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/svn-src-stable-9
 To unsubscribe, send any mail to svn-src-stable-9-unsubscr...@freebsd.org
___
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: Suggest changing dirhash defaults for FreeBSD 9.2.

[Mark Saad]

On Aug 28, 2013, at 3:59 PM, Robert_Burmeister robert.burmeis...@utoledo.edu 
wrote:

 Torfinn Ingolfsen-5 wrote
 On Tue, 27 Aug 2013 23:58:10 -0400
 Robert Burmeister lt;
 
 Robert.Burmeister@
 
 gt; wrote:
 
 As 64 bit platforms tend to have more RAM and use ZFS,
 Do you have any numbers for the 64 bit platforms tend to use ZFS?
 
 PCBSD and OSX both default to ZFS for their 64 bit installs,
 and anyone else wanting to use ZFS will choose 64 bit for the address space.
 

OSX abandoned zfs back in 10.7, I think you meant Solaris 10 update 5ish and 
newer use zfs root by default.  fwiw I am using ufs on amd64 too and have only 
some machines using zfs .

 Do to the kernel memory constraints, 
 ZFS takes some configuration jiggering to work stably on 32 bit.
 
 
 
 
 --
 View this message in context: 
 http://freebsd.1045724.n5.nabble.com/Suggest-changing-dirhash-defaults-for-FreeBSD-9-2-tp5839351p5839745.html
 Sent from the freebsd-stable mailing list archive at Nabble.com.
 ___
 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

Mark saad | mark.s...@longcount.org

___
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: NFS deadlock on 9.2-Beta1

[Mark Saad]

On Jul 29, 2013, at 10:48 PM, J David j.david.li...@gmail.com wrote:

 If it is helpful, we have 25 nodes testing the 9.2-BETA1 build and
 without especially trying to exercise this bug, we found
 sendfile()-using processes deadlocked in WCHAN newnfs on 5 of the 25
 nodes.  The ones with highest uptime (about 3 days) seem most
 affected, so it does seem like a sooner or later type of thing.
 Hopefully the fix is easy and it won't be an issue, but it definitely
 does seem like a problem 9.2-RELEASE would be better off without.
 
 Unfortunately we are not in a position to capture the requested
 debugging information at this time; none of those nodes are running a
 debug version of the kernel.  If Michael is unable to get the
 information as he hopes, we can try to do that, possibly over the
 weekend.  For the time being, we will convert half the machines to
 rollback r250907 to try to confirm that resolves the issue.
 
 Thanks all!  If one has to encounter a problem like this, it is nice
 to come to the list and find the research already so well underway!
 __

All
  Is there any updates on this issue ? Has anyone tested it or see it happen on 
the release candidate ? 
---
Mark saad | mark.s...@longcount.org

___
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: request for your comments on release documentation

[Mark Saad]

On Jun 12, 2013, at 5:31 PM, Ben Morrow b...@morrow.me.uk wrote:

 Quoth h...@freebsd.org:
 
 I would like your comments on release notes for each release.
 Although I have been working on editing them for years, the workflow
 is still not optimal and sometimes delay of the preparation became an
 obstacle for release process.  I would like to improve it, but before
 that I would like to know what are desired of the contents which
 people think.
 
 Release Notes is just listing the changes between the two releases.
 It includes user-visible change (bugfix and/or UI change), new
 functionality, and performance improvement.  Minor changes such as
 one in kernel internal structure are omitted.  I always try to keep
 these series of relnotes items are correct and reasonably
 comprehensive, but this lengthy list may be boring and
 technically-correct descriptions can be cryptic for average users.
 
 I find the lengthy list extremely valuable. It takes a little time to go
 through it carefully, but being able to be reasonably sure nothing
 important is missing makes upgrades easier, not harder.
 
 So, my questions are:
 
 1. What do you think about current granularity of the relnotes items?
Too detailed, good, or too rough?  Currently, judgment of what is
included or not is based on user-visible, new functionality, or
performance improvement.  Applicable changes are included as
relnotes items even if the changes are small,
 
 Seems pretty good to me. The only thing I might change is the order:
 generally speaking, I'm most interested in the 'User-visible
 incompatibilites' section, then in the userland and contrib changes, and
 then the kernel changes. The security advisories section is least
 useful, because it generally just lists advisories I've already seen and
 know have been already fixed; it's a good thing it's there, if only to
 make it clear the project takes security seriously, but I might move it
 to the end.
 
 2. Do you want technical details?  For example, just disk access
performance was improved by 50% or Feature A has been added.
This changes the old behavior because ..., and as a result, it
improves disk access performance by 50%.
 
 It's interesting, but IMHO only worth it if it's easy. It's not worth
 holding a release up for.
 
 3. Is there missing information which should be in the relnotes?
Probably there are some missing items for each release, but this
question is one at some abstraction level.  Link to commit log and
diff, detailed description of major incompatible changes, and so
on.
 
 The only important additional thing that might be useful would be links
 to relevant mailing-list threads in addition to the SVN links. I can see
 that might be quite a bit of work to compile, though, so it may not be
 possible.
 
 Although the other release documentations---Errata, Installation
 Notes, ReadMe, and Hardware Notes---also need some improvements,
 please focus on Release Notes only.  And you might think quality of
 English writing are not good, please leave that alone for now.
 
 There's nothing wrong with your English.
 
 Ben
 
 __

Two points. I like the details of the release notes . More detail here is 
always welcomed. As a professional FreeBSD SA it helps to have detailed notes.

Second, goes to item 3 noted above: a summary of pr' filed on the previous 
release and their current  state would be a huge help as well. Say in the case 
of 9.0 to 9.1 it would help if I could read pr's filed about 9.0 that were 
fixed / addressed, etc in 9.1 .  

---
Mark saad | mark.s...@longcount.org

___
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: Release ISO images have broken RockRidge data

[Mark Saad]

On Apr 9, 2013, at 7:00 AM, Eugene Grosbein egrosb...@rdtc.ru wrote:

 Hi!
 
 Release ISO images located at 
 ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/ISO-IMAGES/
 were generated with mkisofs until switch to makefs. For example,
 ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/ISO-IMAGES/8.2/FreeBSD-8.2-RELEASE-amd64-livefs.iso
 was generated with mkisofs and has correct RockRidge extended attributes.
 
 # isoinfo -d -R -i FreeBSD-8.2-RELEASE-amd64-livefs.iso
 System id: FreeBSD
 Volume id: FreeBSD_LiveFS
 Volume set id: 
 Publisher id: The FreeBSD Project.  http://www.freebsd.org/
 Data preparer id: 
 Application id: MKISOFS ISO 9660/HFS FILESYSTEM BUILDER  CDRECORD CD-R/DVD 
 CREATOR (C) 1993 E.YOUNGDALE (C) 1997 J.PEARSON/J.SCHILLING
 Copyright File id: 
 Abstract File id: 
 Bibliographic File id: 
 Rock Ridge signatures version 1 found
 Rock Ridge id 'RRIP_1991A'
 Eltorito validation header:
Hid 1
Bootid 88 (bootable)
 
 This image may be unrolled correctly with respect to hardlinks using xorriso 
 command from ports:
 
 # xorriso -for_backup -load volid \* -indev 
 ../FreeBSD-8.2-RELEASE-amd64-livefs.iso  -osirrox on -- -extract / livefs 
 -rollback_end
 
 Newer images (8.3 and later) were generated using makefs that seem to produce 
 incorrect RockRidge data:
 
 # isoinfo -d -R -i FreeBSD-8.4-BETA1-amd64-livefs.iso | grep id
 System id: NetBSD
 Volume id: FREEBSD_LIVEFS
 Volume set id: 
 Publisher id: 
 Data preparer id: 
 Application id: 
 Copyright File id: 
 Abstract File id: 
 Bibliographic File id: 
 Rock Ridge signatures version 1 found
 Rock Ridge id 'IEEE_P1282'
 Eltorito validation header:
Hid 1
Bootid 88 (bootable)
 
 Same xorriso command produces tons of following error messages and unrolls 
 the image
 without respect  to hardlinkg increasing size in nearly 3 times:
 
 libisofs: WARNING : Invalid TF entry
 Caused by: Wrong or damaged RR entry
 
 bsdtar from 8.3-STABLE shows lots of errors too, while extracting 
 FreeBSD-8.4-BETA1-amd64-livefs.iso
 mdconfig breaks hardlinks too.
 
 Is it possible to unroll this image respecting hardlinks?
 
 Eugene Grosbein
 

While not the same you can always do this 

mdconfig -a -t vnode -f yourfreebsd-version.iso

mount -t cd9660 /dev/md0 /cdrom 

Then use pax, cpio , cp, rsync etc to copy the data off the image .

Also if memory serves me right libarchive may be able to unpack an iso much 
like a tar or cpio archive . Double check that . 

Also makefs was imported from netbsd I would see if netbsd's isos have the same 
issues . 

Hope this helps 
---
Mark saad | mark.s...@longcount.org

___
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: Release ISO images have broken RockRidge data

[Mark Saad]

On Tue, Apr 9, 2013 at 9:21 AM, Mark Saad nones...@longcount.org wrote:


 On Apr 9, 2013, at 7:00 AM, Eugene Grosbein egrosb...@rdtc.ru wrote:

 Hi!

 Release ISO images located at 
 ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/ISO-IMAGES/
 were generated with mkisofs until switch to makefs. For example,
 ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/ISO-IMAGES/8.2/FreeBSD-8.2-RELEASE-amd64-livefs.iso
 was generated with mkisofs and has correct RockRidge extended attributes.

 # isoinfo -d -R -i FreeBSD-8.2-RELEASE-amd64-livefs.iso
 System id: FreeBSD
 Volume id: FreeBSD_LiveFS
 Volume set id:
 Publisher id: The FreeBSD Project.  http://www.freebsd.org/
 Data preparer id:
 Application id: MKISOFS ISO 9660/HFS FILESYSTEM BUILDER  CDRECORD CD-R/DVD 
 CREATOR (C) 1993 E.YOUNGDALE (C) 1997 J.PEARSON/J.SCHILLING
 Copyright File id:
 Abstract File id:
 Bibliographic File id:
 Rock Ridge signatures version 1 found
 Rock Ridge id 'RRIP_1991A'
 Eltorito validation header:
Hid 1
Bootid 88 (bootable)

 This image may be unrolled correctly with respect to hardlinks using xorriso 
 command from ports:

 # xorriso -for_backup -load volid \* -indev 
 ../FreeBSD-8.2-RELEASE-amd64-livefs.iso  -osirrox on -- -extract / livefs 
 -rollback_end

 Newer images (8.3 and later) were generated using makefs that seem to 
 produce incorrect RockRidge data:

 # isoinfo -d -R -i FreeBSD-8.4-BETA1-amd64-livefs.iso | grep id
 System id: NetBSD
 Volume id: FREEBSD_LIVEFS
 Volume set id:
 Publisher id:
 Data preparer id:
 Application id:
 Copyright File id:
 Abstract File id:
 Bibliographic File id:
 Rock Ridge signatures version 1 found
 Rock Ridge id 'IEEE_P1282'
 Eltorito validation header:
Hid 1
Bootid 88 (bootable)

 Same xorriso command produces tons of following error messages and unrolls 
 the image
 without respect  to hardlinkg increasing size in nearly 3 times:

 libisofs: WARNING : Invalid TF entry
 Caused by: Wrong or damaged RR entry

 bsdtar from 8.3-STABLE shows lots of errors too, while extracting 
 FreeBSD-8.4-BETA1-amd64-livefs.iso
 mdconfig breaks hardlinks too.

 Is it possible to unroll this image respecting hardlinks?

 Eugene Grosbein


 While not the same you can always do this

 mdconfig -a -t vnode -f yourfreebsd-version.iso

 mount -t cd9660 /dev/md0 /cdrom

 Then use pax, cpio , cp, rsync etc to copy the data off the image .

 Also if memory serves me right libarchive may be able to unpack an iso much 
 like a tar or cpio archive . Double check that .

 Also makefs was imported from netbsd I would see if netbsd's isos have the 
 same issues .

 Hope this helps
 ---
 Mark saad | mark.s...@longcount.org


So I did some testing and NetBSD's isos, which are generated much the
same way as FreeBSD's , have the same issue .


# xorriso -for_backup -load volid \* -indev
../NetBSD-6.1_RC2-amd64.iso -osirrox on -- -extract / netbsd
-rollback_en
...
libisofs: NOTE :   Caused by: Wrong or damaged RR entry
libisofs: WARNING : Invalid TF entry
libisofs: NOTE :   Caused by: Wrong or damaged RR entry
libisofs: WARNING : Invalid TF entry
libisofs: NOTE :   Caused by: Wrong or damaged RR entry
xorriso : UPDATE : 2004 nodes read in 1 seconds
libisofs: WARNING : Found hidden El-Torito image. Its size could not
be figure out, so image modify or boot image patching may lead to bad
results.
xorriso : NOTE : Detected El-Torito boot information which currently
is set to be discarded
Drive current: -indev '../NetBSD-6.1_RC2-amd64.iso'
Media current: stdio file, overwriteable
Media status : is written , is appendable
Boot record  : El Torito
Media summary: 1 session, 169279 data blocks,  331m data,  194g free
Volume id: 'NETBSD_61_RC2'
Copying of file objects from ISO image to disk filesystem is: Enabled
xorriso : UPDATE : 16 files restored ( 97911k) in 1 seconds , 63.7xD
xorriso : UPDATE : 22 files restored ( 173.5m) in 2 seconds , 52.2xD
xorriso : UPDATE : 30 files restored ( 252.6m) in 3 seconds , 53.3xD
xorriso : UPDATE : 458 files restored ( 297.2m) in 4 seconds , 33.8xD
xorriso : UPDATE : 1486 files restored ( 328.4m) in 5 seconds = 50.0xD
Extracted from ISO image: file '/'='/opt/home//Storage/extract/netbsd'

Also for what its worth, tar does work at extracting an iso as well

# tar -zxvf ../FreeBSD-7.4-RELEASE-i386-disc1.iso -C out
x .
x 7.4-RELEASE
x 7.4-RELEASE/base
x 7.4-RELEASE/catpages
x 7.4-RELEASE/manpages
x 7.4-RELEASE/games
x 7.4-RELEASE/proflibs
x 7.4-RELEASE/dict
x 7.4-RELEASE/info
x 7.4-RELEASE/doc
x 7.4-RELEASE/kernels
x 7.4-RELEASE/ports
x 7.4-RELEASE/src
x floppies
x boot
x boot/zfs
x boot/firmware
x boot/kernel
x boot/modules
x boot/defaults
x packages
x packages/All
x packages/converters
x packages/devel
x packages/gnome
x packages/emulators
x packages/linux
..


So , what issues does this cause ? Have your filed a pr with FreeBSD or NetBSD ?


-- 
mark saad | nones...@longcount.org
___
freebsd-stable@freebsd.org mailing

Re: Core Dump / panic sleeping thread

[Mark Saad]

Comments in line .
---


On Mar 19, 2013, at 1:45 PM, Michael Landin Hostbaek m...@freebsd.org wrote:

 
 On Mar 19, 2013, at 6:35 PM, Jeremy Chadwick j...@koitsu.org wrote:
 
 On Tue, Mar 19, 2013 at 06:18:06PM +0100, Michael Landin Hostbaek wrote:
 The kernel panic is happening in NFS-related code.  Rick Macklem (and/or
 John Baldwin) should be able to help with this; I've CC'd both here.
 
 OK, thanks. 
 
 
 
 You're going to need to provide the following details:
 
 1. Contents of /etc/rc.conf
 
 sshd_enable=YES
 ntpdate_enable=YES
 ntpdate_hosts=xx.xx.xx.xx
 fsck_y_enable=YES
 named_enable=YES
 dumpdev=AUTO
 nfs_client_enable=YES
 rpc_lockd_enable=YES
 rpc_statd_enable=YES
 ifconfig_em0=inet xx.xx.xx.xx netmask 255.255.255.0 broadcast xx.xx.xx.xx
 defaultrouter=xx.xx.xx.xx
 hostname=
 cloned_interfaces=vlan
 ifconfig_vlan=inet xx.xx.xx.xx netmask 255.240.0.0 broadcast xx.xx.xx.xx 
 vlan  vlandev em0
 apache22_enable=YES
 pureftpd_enable=YES
 revealcloud_enable=YES
 
 
 2. Contents of /etc/sysctl.conf (if modified)
 
 vm.pmap.shpgperproc=250
 

Small side note. This sysctl is no longer valid . It's had no effect after 7.2 
iirc . 



 3. Contents of /etc/fstab
 
 # DeviceMountpoint  FStype  Options DumpPass#
 /dev/mirror/gm0s1a/ufsrw11
 /dev/mirror/gm0s1bnoneswapsw00
 /dev/mirror/gm0s1d/varufsrw22
 /dev/mirror/gm0s1e/logsufsrw22
 /dev/mirror/gm0s1f/extraufsrw22
 /dev/mirror/gm0s1g/usrufsrw22
 proc/proc   procfs  rw  0   0
 xx.xx.xx.xx:/zpool-000xxx/www/mnt/wwwnfsrw00
 xx.xx.xx.xx:/zpool-000xxx/data/mnt/datanfsrw,tcp00
 linproc/compat/linux/proclinprocfsrw00
 
 
 4. ifconfig -a
 
 em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500

 options=4219bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO
ether 00:25:90:79:a5:ac
inet xx.xx.xx.xx netmask 0xff00 broadcast xx.xx.xx.xx
inet6 xx::a5ac%em0 prefixlen 64 scopeid 0x1 
nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL
media: Ethernet autoselect (1000baseT full-duplex)
status: active
 em1: flags=8c02BROADCAST,OACTIVE,SIMPLEX,MULTICAST metric 0 mtu 1500

 options=4219bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO
ether 00:25:90:79:a5:ad
nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL
media: Ethernet autoselect
status: no carrier
 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384
options=63RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6
inet6 ::1 prefixlen 128 
inet6 fe80::1%lo0 prefixlen 64 scopeid 0xb 
inet 127.0.0.1 netmask 0xff00 
nd6 options=21PERFORMNUD,AUTO_LINKLOCAL
 vlan: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500
options=103RXCSUM,TXCSUM,TSO4
ether 00:25:90:79:a5:ac
inet xx.xx.xx.xx netmask 0xfff0 broadcast xx.xx.xx.xx
inet6 x:::5ac%vlan prefixlen 64 scopeid 0xc 
nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL
media: Ethernet autoselect (1000baseT full-duplex)
status: active
vlan:  parent interface: em0
 
 
 5. OS used by the NFS server, and all configuration details pertaining
 to that system
 
 This is a hosted service, so I do not have access to this - though I believe 
 this is a ZFS fs.
 Here's more info about the product: http://help.ovh.co.uk/Nas
 
 
 
 You may also be asked to upgrade to 9.1-STABLE, as there may be fixes
 for whatever this is in base/stable/9 that are not in -RELEASE, but this
 is speculative on my part.
 
 That is not a problem. I would simply like to confirm the issue, before 
 upgrading. 
 
 
 Thanks, 
 
 /mich
 
 
 ___
 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


Mark saad | mark.s...@longcount.org

___
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: svn - but smaller?

[Mark Saad]

---


On Mar 11, 2013, at 9:20 PM, Michael Ross g...@ross.cx wrote:

 On Tue, 12 Mar 2013 00:15:35 +0100, John Mehr j...@visi.com wrote:
 
 
 On Mon, 11 Mar 2013 15:16:53 -0400
 Patrick McEvoy patmce...@mac.com wrote:
 Hello John,
 This is Patrick the BSDTV guy. If you have the time / inclination, would 
 you like to do a quick walk through svnup?**If you have a machine that will 
 run Skype, I could record you doing a walk through including all the things 
 you want to tell users about your port. Skype offers a share your screen 
 feature that I have found helpful for making such videos. If you are 
 interested, please let me know.
 Thank you for your support of the BSD community.
 **
 -- Patrick McEvoy
 patmce...@mac.com
 cell: 718 440-5104
 ___
 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
 
 Hello,
 
 I'm currently in the process of adding http/https support to svnup and once 
 I've got that working, the command line interface will be changing to be 
 more like the traditional svn client to make it easier for people to adopt 
 the tool [...]
 
 What'd you think about a syntax extension along the lines of
 
svnup --bsd-base
svnup --bsd-ports
svnup --bsd-all
 

What about using svnup on another BSD , or Linux ? 


 with automagic host selection, default to uname's major version stable branch 
 and default target dirs?
 
 
 The automagically selected host al la something like fastest-cvsup would be 
useful as the list of mirrors changes and the closest mirror may not be 
apparent .

 Regards,
 
 Michael
 ___
 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


___
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

netisr issues

[Mark Saad]

All
 I am looking for some guidance on how to turn netisr back on, on a
9.1-RELEASE and 9.1-STABLE box. It looks it stopped working as it did in
prior versions of FreeBSD .
I tested this on 9.1-RELEASE and  9.1-STABLE #0 r247804 built last monday.

My question is this. If I enable the direct option in boot/loader.conf via
this

net.isr.direct=1
net.isr.direct_force=1

I do not get any expected result.

root@chambers:~ # sysctl net.isr.direct
net.isr.direct: 0
root@chambers:~ # sysctl net.isr.direct_force
net.isr.direct_force: 0

root@chambers:~ # netstat -Q
Configuration:
SettingCurrentLimit
Thread count 11
Default queue limit25610240
Dispatch policy direct  n/a
Threads bound to CPUs disabled  n/a




Am I missing something ?


-- 
mark saad | nones...@longcount.org
___
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: netisr issues

[Mark Saad]

On Mon, Mar 11, 2013 at 12:11 PM, Freddie Cash fjwc...@gmail.com wrote:
 Works if you set them in /etc/sysctl.conf.  Haven't looked into it, but I
 think there's something in the startup that sets them to 0 after the kernel
 is loaded, so the loader.conf settings are overwritten.


 On Mon, Mar 11, 2013 at 7:42 AM, Mark Saad nones...@longcount.org wrote:

 All
  I am looking for some guidance on how to turn netisr back on, on a
 9.1-RELEASE and 9.1-STABLE box. It looks it stopped working as it did in
 prior versions of FreeBSD .
 I tested this on 9.1-RELEASE and  9.1-STABLE #0 r247804 built last monday.

 My question is this. If I enable the direct option in boot/loader.conf via
 this

 net.isr.direct=1
 net.isr.direct_force=1

 I do not get any expected result.

 root@chambers:~ # sysctl net.isr.direct
 net.isr.direct: 0
 root@chambers:~ # sysctl net.isr.direct_force
 net.isr.direct_force: 0

 root@chambers:~ # netstat -Q
 Configuration:
 SettingCurrentLimit
 Thread count 11
 Default queue limit25610240
 Dispatch policy direct  n/a
 Threads bound to CPUs disabled  n/a

 


 Am I missing something ?


 --
 mark saad | nones...@longcount.org
 ___
 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




 --
 Freddie Cash
 fjwc...@gmail.com

Freddie
  When I tried to set them in /etc/sysctl.conf , sysctl stated they
were read-only .

[root@mkr2 /etc]# sysctl -w net.isr.direct=1
sysctl: oid 'net.isr.direct' is read only


[root@mkr2 /etc]# sysctl -w net.isr.direct_force=1
sysctl: oid 'net.isr.direct_force' is read only

--
mark saad | nones...@longcount.org
___
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: netisr issues

[Mark Saad]

On Mon, Mar 11, 2013 at 12:26 PM, Freddie Cash fjwc...@gmail.com wrote:
 I seem to recall that the method for setting direct changed so that it's
 not a binary option (net.isr.direct), but instead is a policy setting now
 (net.isr.dispatch).  Try:

 net.isr.dispatch=direct

 That's what's set on our 9.1-STABLE systems:
 # sysctl net.isr
 net.isr.numthreads: 8
 net.isr.maxprot: 16
 net.isr.defaultqlimit: 256
 net.isr.maxqlimit: 10240
 net.isr.bindthreads: 1
 net.isr.maxthreads: 8
 net.isr.direct: 0
 net.isr.direct_force: 0
 net.isr.dispatch: direct

 # netstat -Q | head
 Configuration:
 SettingCurrentLimit
 Thread count 88

 Default queue limit25610240
 Dispatch policy direct  n/a
 Threads bound to CPUs  enabled  n/a



 On Mon, Mar 11, 2013 at 9:22 AM, Freddie Cash fjwc...@gmail.com wrote:

 You're right.  I was looking at different net.isr oids, not the _direct
 ones.  My bad.


 On Mon, Mar 11, 2013 at 9:17 AM, Mark Saad nones...@longcount.org wrote:

 On Mon, Mar 11, 2013 at 12:11 PM, Freddie Cash fjwc...@gmail.com wrote:
  Works if you set them in /etc/sysctl.conf.  Haven't looked into it, but
  I
  think there's something in the startup that sets them to 0 after the
  kernel
  is loaded, so the loader.conf settings are overwritten.
 
 
  On Mon, Mar 11, 2013 at 7:42 AM, Mark Saad nones...@longcount.org
  wrote:
 
  All
   I am looking for some guidance on how to turn netisr back on, on a
  9.1-RELEASE and 9.1-STABLE box. It looks it stopped working as it did
  in
  prior versions of FreeBSD .
  I tested this on 9.1-RELEASE and  9.1-STABLE #0 r247804 built last
  monday.
 
  My question is this. If I enable the direct option in boot/loader.conf
  via
  this
 
  net.isr.direct=1
  net.isr.direct_force=1
 
  I do not get any expected result.
 
  root@chambers:~ # sysctl net.isr.direct
  net.isr.direct: 0
  root@chambers:~ # sysctl net.isr.direct_force
  net.isr.direct_force: 0
 
  root@chambers:~ # netstat -Q
  Configuration:
  SettingCurrentLimit
  Thread count 11
  Default queue limit25610240
  Dispatch policy direct  n/a
  Threads bound to CPUs disabled  n/a
 
  
 
 
  Am I missing something ?
 
 
  --
  mark saad | nones...@longcount.org
  ___
  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
 
 
 
 
  --
  Freddie Cash
  fjwc...@gmail.com

 Freddie
   When I tried to set them in /etc/sysctl.conf , sysctl stated they
 were read-only .

 [root@mkr2 /etc]# sysctl -w net.isr.direct=1
 sysctl: oid 'net.isr.direct' is read only


 [root@mkr2 /etc]# sysctl -w net.isr.direct_force=1
 sysctl: oid 'net.isr.direct_force' is read only

 --
 mark saad | nones...@longcount.org
 ___
 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




 --
 Freddie Cash
 fjwc...@gmail.com




 --
 Freddie Cash
 fjwc...@gmail.com


Freddie
   So should I be adjusting the numbers of threads or is this
determined somewhere ?
-- 
mark saad | nones...@longcount.org
___
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: netisr issues

[Mark Saad]

On Mon, Mar 11, 2013 at 12:48 PM, Freddie Cash fjwc...@gmail.com wrote:
 On Mon, Mar 11, 2013 at 9:40 AM, Mark Saad nones...@longcount.org wrote:

 Freddie
So should I be adjusting the numbers of threads or is this
 determined somewhere ?

 I think it's supposed to be automatic, 1 thread per CPU, but I manually set
 it  via /boot/loader.conf:
 net.isr.bindthreads=1 # Bind netisr threads to CPU
 cores
 net.isr.maxthreads=8  # Set number of threads to
 number of CPU cores
 net.isr.numthreads=8  #

 The net.isr.dispatch is automatically set to direct on our systems.  Not
 sure if that's the default or not.  We used to set that via
 /boot/loader.conf as well, but it was removed in the upgrade to 9-STABLE
 something as it no longer did anything.

 --
 Freddie Cash
 fjwc...@gmail.com

Just so I am clear , prior to r49 by rwatson  net.isr.direct=1
enabled the same interaction as net.isr.dispatch=deferred after the
commit , with the latter commit enabling netisr to have mulch-threaded
support ?


-- 
mark saad | nones...@longcount.org
___
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: countdown from 31: helping with the FAQ

[Mark Saad]

Eitan
  In the section for need-to-run there should be a mention about setting
kern.cam.ctl.disable=1 in /boot/loader.conf , for systems with less then
256M of ram . Also I wonder if there are more low memory tunings that need
an mention here.

http://lists.freebsd.org/pipermail/freebsd-stable/2012-December/thread.html#71334



On Sat, Jan 26, 2013 at 3:00 PM, Eitan Adler li...@eitanadler.com wrote:

 Hey all,

 I've been working for past several months on improving the FAQ.  At
 the moment there are 31 unreviewed questions.

 Can you all help out by commenting on the yellow questions here:
 https://wiki.freebsd.org/ThwackAFAQ   - once the review stage is done
 we could continue fixing the red ones!

 --
 Eitan Adler
 ___
 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




-- 
mark saad | nones...@longcount.org
___
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: Will we get a RELEASE-9.1 for Christmas?

[Mark Saad]

So what is the short summary ? From what I can see, the wiki is out of date
again. the ISO are on the master server, and working out to the mirrors.
FreeBSD update is still not updated.  Does someone just need to just update
the wiki with the relevant info ?


On Tue, Dec 11, 2012 at 9:00 AM, Gary Palmer gpal...@freebsd.org wrote:

 On Mon, Dec 10, 2012 at 08:06:24PM -0800, Kevin Oberman wrote:
  On Mon, Dec 10, 2012 at 3:52 PM, Brett Glass br...@lariat.net wrote:
   At 04:29 PM 12/10/2012, Adrian Chadd wrote:
  
   There's politics in every organisation. There are ego clashes in every
   organisation. Sometimes you'll fit in, sometimes you won't. If you
   feel there are issues, find people inside the community who you do get
   along well with and talk with them about it.
  
   It sucks, yes. I'm one of those shut up and code already types and I
   deal badly with politics.
  
  
   Me, too. That's why I have been contributing code quietly through
 others
   rather than putting myself out in the front lines.
  
   In any event -- back to the original topic -- there should indeed be
 better
   communications between the Release Engineering team and the community.
   The time it takes to post updates -- especially as it gets close to
 release
   time -- would be recovered many times over because folks like me
 wouldn't
   have any need to e-mail regarding status and projected schedules. ;-)
 
  I whole-heatedly agree... but I know a little about release
  engineering for a large project, especially when the release team is
  unpaid and has to honor commitments to $real_job. Release engineering
  is very detail-oriented and unforgiving.  This is not really
  compatible with part-time work.
 
  The RE must be focused, first ans foremost, on getting a release out
  the door as quickly as possible and not to have any serious problems
  with that release. This makes it very had to pull bakc and make
  announcements or even update posted schedules. That is made even worse
  by hte desire to make such communication accurate or at least useful.
  Since there is a LOT of guessing involved in pulling together a
  release (how long will Joe take to fix this problem or why are there
  half a dozen reports of a serious issue with the RC, when no one else
  can reproduce it or even figure out what part of the system is causing
  it), RE folks are usually reticent about trying to give out any
  information since it will most likely be inaccurate.
 
  This is why I accept the line that it will be released when it is
  ready. I really think it's about ready, but not even the head of the
  9.1 RE team KNOWS when it will be ready, even if the  ISO builds are
  started. There is many a slip twixt the cup and the lip.

 I don't remember seeing any updates in e-mail, but the

 http://www.freebsd.org/news/2012-compromise.html

 url has been updated.  Its a litle out of date now (last update about 2
 weeks ago), but it does include information on the release of 9.1 and what
 is holding it up (specifically getting a minimal set of packages built).
 With the 2 branches tagged (ports and src) it is likely still a matter
 of getting stuff built in a known clean environment.

 Gary

 ___
 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




-- 
mark saad | nones...@longcount.org
___
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: Write Failed message with 9.1-RC3

[Mark Saad]

On Nov 26, 2012, at 4:01 PM, Reed A. Cartwright cartwri...@asu.edu wrote:

 I'm new to this list...
 
 I'm running a bioinformatics server using 9.1-RC3 (64 cores, 512GB
 ram).  I have a ZFS raid-z2 array attached to an LSI controller with a
 SSD cache drive.

Can you tell us more about this server . Can you post the output of pciconf -lv 
,
What do you have in loader.conf and sysctl.conf ? Do you se a custom kernel 
build;  What are the changes you made to that config ? 
 
 Since upgrading to 9.1-RC2/3 (for AVX support), I have been
 experiencing hard drive lockups with the message write failed
 printed to the console.  After this reading from the hard drives no
 longer work, but the machine is not locked up.  If the appropriate
 files are in the cache, I can log in and execute programs.  I know the
 LSI driver has been updated in 9.1 and I have updated my cards' bios
 to match.  It doesn't seem to make a difference.
 
 Once I was able to run top, and saw that many processes were stuck in
 the 'tx-tx' state.

What does your zfs config look like can you post the output if zpool status ? 
What zfz options have you set on pool and filesystens ?

Lastly In a shutdown -h now , does the system properly shutdown ,does it crash 
and dump core ?
 
 So far, no corruption appears to have occurred in the drives.
 
 I'm about to downgrade to 9.0, but I wanted to know if anyone has any
 idea what the issue is.
 
 --
 Reed A. Cartwright, PhD
 Assistant Professor of Genomics, Evolution, and Bioinformatics
 School of Life Sciences
 Center for Evolutionary Medicine and Informatics
 The Biodesign Institute
 Arizona State University
 ___
 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

---
Mark saad | mark.s...@longcount.org

___
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: Looking for bge(4) , bce(4) and igb(4) cards

[Mark Saad]

Andre
  I'll try to do it today or next monday when I get back from vacation . They 
are all hp branded nic's . I ordered them with in the last few years to use in 
place of bce nic's on the main boards of hp servers . 

---


On Nov 14, 2012, at 5:31 AM, Andre Oppermann an...@freebsd.org wrote:

 Hello
 
 I currently working on a number of drivers for popular network
 cards and extend them with automatic hybrid interrupt/polling
 ithread processing with life-lock prevention (so that the driver
 can't consume all CPU when under heavy load or attack).
 
 To properly test this I need the proper hardware as PCIe network
 cards:
 
 bge(4) Broadcom BCM57xx/BCM590x
 bce(4) Broadcom NetXtreme II (BCM5706/5708/5709/5716)
 igb(4) Intel PRO/1000 i82575, i82576, i82580, i210, i350
 
 If you have one of these and can spare it I'd be very glad if
 you could send it to me.  I'm located in Switzerland/Europe.
 I can reply to you privately to give you my shipping address.
 
 
 Of course if you have any other PCIe Gigabit Ethernet cards
 with a driver in FreeBSD I'm interested in receiving one as
 well.  Of particular interest are:
 
 em(4)  Intel i82571 to i82573
 lem(4) Intel i82540 to i82546
 age(4) Atheros L1 GigE
 ???anything else 1GigE with PCIe
 
 
 The same goes for 10 Gigabit Ethernet but the setup is a bit
 more involved and I haven't done that yet, but will do soon
 (the issue being expensive SPF+ optics):
 
 bxe(4)   Broadcom BCM5771x 10GigE
 cxbge(4) Chelsio T4 10GigE
 ixgbe(4) Intel i82598 and i82599 10GigE
 mxge(4)  Myricom Myri10G
 qlxgb(4) QLogic 3200 and 8200 10GigE
 sfxge(4) Solarflare
 
 Many thanks for your support!
 
 -- 
 Andre
 ___
 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
___
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: FreeBSD 9.1 stability/robustness?

[Mark Saad]

On Nov 2, 2012, at 3:15 PM, Rainer Duffner rai...@ultra-secure.de wrote:

 Am Fri, 2 Nov 2012 13:34:20 -0400
 schrieb Mark Saad nones...@longcount.org:
 
 
 
 
 On Nov 2, 2012, at 4:10 AM, Rainer Duffner rai...@ultra-secure.de
 wrote:
 
 Am Thu, 1 Nov 2012 20:14:51 -0600 (MDT)
 schrieb Brett Glass br...@lariat.net:
 
 I need to build up a few servers and routers, and am wondering how
 FreeBSD 9.1 is shaping up. Will it be likely to be more stable and
 robust than 9.0-RELEASE? Are there issues that will have to wait
 until 9.2-RELEASE to be fixed? Opinions welcome.
 
 
 If I'm not mistaken, the bge-stuff that makes the default NICs ins
 HP G8 servers (360+380) actually run will not make it back into 9.1.
 Intel cards work much better anyway...
 
 Did you swap out the bge nic daughter card in the g8 servers for an
 intel one or , do you mean in general the intel nic support is
 better ? 
 
 Both, actually.
 At least, Intel has drivers for FreeBSD on their website and IIRC, it's
 a Tier 1 OS for them.
 I don't want to dis the efforts of the people working on the bXe stuff,
 but from what I have read, they have much less support from the vendor.
 We have used HP servers even back when they were still Compaq-servers
 (and came with Intel NICs...) and this is really the first time we had
 to install Intel NICs with them (with FreeBSD - there was an earlier
 issue with Solaris, but that does not count...).
 
 Are there Intel daughter cards for this server?
 I thought, all the daugher-cards came with some sort of Broadcom
 chipset.

Hp did a presentation at work 2 weeks ago about the g8 . Hp said you can swap 
out a daughter card in the 360/380/580 for nic options like broadcom 4 port 
gigabit nic , melenox infinbabd, intel pro1000 4 port nic , qlogic 8Gb fc-al  
and others . They said its an FRU but I have not seen the parts yet . 

---
Mark saad | mark.s...@longcount.org

___
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: FreeBSD 9.1 stability/robustness?

[Mark Saad]

On Nov 2, 2012, at 4:10 AM, Rainer Duffner rai...@ultra-secure.de wrote:

 Am Thu, 1 Nov 2012 20:14:51 -0600 (MDT)
 schrieb Brett Glass br...@lariat.net:
 
 I need to build up a few servers and routers, and am wondering how
 FreeBSD 9.1 is shaping up. Will it be likely to be more stable and
 robust than 9.0-RELEASE? Are there issues that will have to wait
 until 9.2-RELEASE to be fixed? Opinions welcome.
 
 
 If I'm not mistaken, the bge-stuff that makes the default NICs ins HP
 G8 servers (360+380) actually run will not make it back into 9.1.
 Intel cards work much better anyway...
 
Did you swap out the bge nic daughter card in the g8 servers for an intel one 
or , do you mean in general the intel nic support is better ? 


 ___
 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
___
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: HP Smart Array B120i

[Mark Saad]

 Serguey
  I believe it's supported with geom_raid . I had a similar b1xx card in a hp 
dl165 and using graid was the only solution to setup raid 1 or 1+0. it's a 
hardware accelerated software raid , not a true smart array controller. 
---


On Oct 26, 2012, at 5:51 AM, S.N.Grigoriev serguey-grigor...@yandex.ru wrote:

 Hi list,
 
 who can say does FreeBSD 8.x/9.x support HP Smart Array B120i controller?
 
 Thanks,
 Serguey.
 ___
 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
___
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: Alert When Hardware Changes !

[Mark Saad]

On Oct 5, 2012, at 7:23 AM, Shiv. Nath prabh...@digital-infotech.net wrote:

 
 Dear Friends of List,
 
 Well, i understand perhaps someone will think if it is correct please to
 ask this question here. But i did not find the better place than here.
 Here is community of technical people and the question is technical as
 well.
 
 Question:
 
 Is anyone aware of such program (software) that can alert me when hardware
 changes? i.e. lets say i will monitor the hardware for a computer/server
 using a program (i.e. Zabbix / Nagios) may be different program. Can i
 receive the alert when hard disk for the computer has been changed?
 
 Any software anyone aware of?
 
 
 _

You could use dmidecode in a nagios check to get some data like that. For 
example when a memory module fails , CPU speed , number of CPUs , number of 
memory modules ; but it's quite hardware vendor specific . As for hard drives 
you would need to check if the box has a raid controller and some vendor 
specific way to probe it . For example I use cciss_vol_status in both FreeBSD 
and Linux to monitor hp raid array health in a nagios check and it works well . 
 For generic non raid controllers , Sata, IDE , scsi you can try using 
smartutils to monitor disk health . Other then that; if it's just a check to 
show if diskX is installed you could have a nagios check looking for the entry 
in /dev . Both modern FreeBSD and Linux use a devfs/udev system and add and 
remove entries in /dev when the device is attached or not .


Hope that helps


Mark saad | mark.s...@longcount.org

___
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: qmail-remote uses 100% CPU when delivering to certain hosts

[Mark Saad]

On Sep 28, 2012, at 10:12 PM, Boris Kochergin sp...@acm.poly.edu wrote:

 Hi.
 
 Firstly, my environment:
 
 FreeBSD isis.poly.edu 9.1-RC1 FreeBSD 9.1-RC1 #0: Thu Sep 20 23:42:23 EDT 
 2012 bo...@jails.isis.poly.edu:/usr/obj/usr/src/sys/GENERIC  amd64
 
 qmail-tls-1.03.20021228_4
 
 I have noticed that qmail-remote spins around using 100% CPU forever when 
 delivering mail to a select few hosts. I believe this all to be in userspace 
 as top reports that the CPU is busy with only userspace code. This has never 
 happened when the machine was running 8.0-RELEASE, but happens with 
 8.2-RELEASE and 9.1-RC1.
 
 The environment this happens in is a jail.
 
 Calling truss on the offending processes produces no output, with truss in 
 the wait state forever. I've tcpdumped the conversation between the 
 qmail-remote process and the remote host. It is attached with this e-mail.
 
 Thoughts?
 
 -Boris
 qmail-remote.pcap



Boris the messages that are in the delivery queue ,at this time, can you share 
any details on them are they big, small etc . Also what file system do you use 
for the hauls .___
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

Commit r240315 into 9.1-release

[Mark Saad]

All
 Can someone merge in r240315 into the 9.1 release. This fixes a few bugs in 
pc-sysinstall . I am planning on using pc-sysinstall for automated network 
installs of 9.1-RELEAE ( not pc-bsd ) much akin to jumpstart with sysinstall in 
past releases .  With out this commit a few options for disk layouts that were 
supported in all prior versions of sysinstall do not work in pc-sysinstall .


---
Mark saad | mark.s...@longcount.org

___
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: Geom label lost after expanding partition

[Mark Saad]

On Thu, Aug 16, 2012 at 12:30 PM, Kevin Oberman kob6...@gmail.com wrote:
 I have a GPT formatted disk where I recently expanded the size of a
 partition. I used gpart resize -i 6 ada1 first to expand the
 partition to use the remaining free space and then growfs to modify
 the FFS file system to use the full partition. This was all done in
 single-user mode, of course, but when I enter exit to bring the
 system up, it failed to mount /usr. This was because /dev/ufs/usr did
 not exist!

 I assumed that gpart lost the label when it resized the partition
 (which looked like a minor bug to me), but I have been completely
 unable to re-create the label. I first tried  tunefs and then glabel.
 (The handbook says glabel can be used, though the glabel man page is
 explicit that it can't.) Both complete with no errors, but neither
 fixes the problem. I still don't see any /dev/usf/usr. glabel list
 does not even list the geom.

 I do get the following GEOM messages in dmesg:
 GEOM: ada1p2: invalid disklabel.
 GEOM: ufsid/4df4feeda0ce6d5c: invalid disklabel.
 GEOM: ufs/root: invalid disklabel.
 GEOM: gpt/root: invalid disklabel.
 GEOM: gptid/43f0eafd-ba3a-11e0-b70a-f0def166a11e: invalid disklabel.

 but /dev/ufs/root works fine to mount /, and I have always seen these
 errors and have never been able to figure out what is causing them.

  I ended up entering the actual drive node (/dev/ada1p6) into my
 fstab. This works, but brings back the old issues of having to edit
 the fstab any time the drive is moved.

 Does anyone have any idea how to get the labels to work again? I'm not
 even sure what tool displays what label as I can label with glabel,
 tunefs, and newfs
 --
 R. Kevin Oberman, Network Engineer
 E-mail: kob6...@gmail.com
 ___
 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

Kevin
 I believe the UFS or geom_labels  are stuck at the end of the
partition so , I can see how it would wipe them out if you resized it.
Can you run glabel status and glabel list send us the results ?


-- 
mark saad | nones...@longcount.org
___
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: SOLVED: Time Clock Stops in FreeBSD 9.0 guest running under ESXi 5.0

[Mark Saad]

---


On Aug 3, 2012, at 3:59 AM, Adam Strohl adams-free...@ateamsystems.com wrote:

 Doh, correct URL for the forum post is:
 http://forums.freebsd.org/showthread.php?t=31929page=2
 
 On 8/3/2012 14:38, Adam Strohl wrote:
 Just a heads up on the original issue, which is FreeBSD's timer/clock
 stopping under ESXi 5.0 and some later versions of VMware Workstation.
 
 I've gotten a few direct messages that this thread ranks high on Google
 but people are missing the solution.  A few months ago I found this
 forum posting (I believe this was linked in this thread already)
 http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2012-03/msg00201.html
 
 
 The long and short of it is that changing the kern.timecounter sysctl
 value to ACPI-fast or (ACPI-safe if you're not running 9.x yet) fixes
 the hanging issue so far for us.
 
 To temporarily enable it under 9.x:
 sysctl kern.timecounter.hardware=ACPI-fast
 
 Pre 9.x (which doesn't have the ACPI-fast mode):
 sysctl kern.timecounter.hardware=ACPI-safe
 
 To make this persist across reboots and be enabled by default add this
 line to your /etc/sysctl.conf
 
 Under 9.x:
 kern.timecounter.hardware=ACPI-fast
 
 Pre 9.x:
 kern.timecounter.hardware=ACPI-safe
 
 Hope this helps anyone running across this issue.
 
 
 
 -- 
 Adam Strohl
 http://www.ateamsystems.com/
 ___
 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

Did you ask VMware to update this kb ?

http://kb.vmware.com/selfservice/microsites/search.do?language=en_UScmd=displayKCexternalId=1006427

They need to have a FreeBSD section . 

It's slightly sad VMware could. It figure this out . They have notes on 
disabling hpet due to screwy clock issues under Linux , wonder why they never 
tried to disable it under FreeBSD  ?

---
Mark saad | mark.s...@longcount.org

___
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: Recommendation for Hyervisor to host FreeBSD

[Mark Saad]

On Fri, Jul 6, 2012 at 11:44 AM, Ivan Voras ivo...@freebsd.org wrote:
 On 05/07/2012 14:21, Mark Saad wrote:

   I am using VMware esxi v4.01 with no issues for 6, 7, 8 and 9 . Esxi will 
 happily host amd64 installs and i386 provider the underlying hardware 
 supports it. The older esx 3.5 works as well on 32bit hardware but I am no 
 longer using it. Also I use virtualbox 4 hosted on a Mac and a 9-stable 
 amd64 box with little issue .

 Hello,

 Which type of workload do you run on FreeBSD under VMWare ESXi? e.g. web
 server, database, e-mail...?


Ivan
  We mainly use it to run development and testing instances of
services before re roll it out to real hardware.  The majority of this
would be web servers and database servers, content replication, ldap,
and email . As well as some windows vm for some vendor specific
specialized tasks .

In all I have 95 FreeBSD VMs on 3x HP DL380G6, 2x DL 360G5 and 1x
ML370G5 servers and about 120 total vm's give or take a few depending
on where people are in their cycle of using a vm.


-- 
mark saad | nones...@longcount.org
___
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: Recommendation for Hyervisor to host FreeBSD

[Mark Saad]

On Jul 5, 2012, at 7:43 AM, Pete French petefre...@ingresso.co.uk wrote:

 So, my work surprise for a Thursday morning is an urgent requirement to
 see if we can run a set of FreeBSD machines under virtualised servers.
 I have not done this before personally, but I notice from post here
 that it doesnt seem uncommon, and I see Xen related commits flowing
 past, so I am guessing it is doable.
 
 So, for running 8 or 9 STABLE can anyone recommend which hypervisor
 works best, and is 8 or 9 better as the OS to run ? Am doing a bit
 of research myself, but nothing beats persoanl experience in these
 matters!
 
 cheers,
 
 -pete.
 

Pete 
  I am using VMware esxi v4.01 with no issues for 6, 7, 8 and 9 . Esxi will 
happily host amd64 installs and i386 provider the underlying hardware supports 
it. The older esx 3.5 works as well on 32bit hardware but I am no longer using 
it. Also I use virtualbox 4 hosted on a Mac and a 9-stable amd64 box with 
little issue .


---
Mark saad | mark.s...@longcount.org

___
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: Recommendation for Hyervisor to host FreeBSD

[Mark Saad]

On Jul 5, 2012, at 8:43 AM, Rainer Duffner rai...@ultra-secure.de wrote:

 Am Thu, 05 Jul 2012 12:43:06 +0100
 schrieb Pete French petefre...@ingresso.co.uk:
 
 So, my work surprise for a Thursday morning is an urgent requirement
 to see if we can run a set of FreeBSD machines under virtualised
 servers. I have not done this before personally, but I notice from
 post here that it doesnt seem uncommon, and I see Xen related commits
 flowing past, so I am guessing it is doable.
 
 So, for running 8 or 9 STABLE can anyone recommend which hypervisor
 works best, and is 8 or 9 better as the OS to run ? Am doing a bit
 of research myself, but nothing beats persoanl experience in these
 matters!
 
 
 
 AFAIK, there are no VMware-tools for FreeBSD9 (yet).
 So, if you need to use ESXi/vSphere, then stay with 8.3 for the time
 being.

You can use the open-vmtools package which is in ports .


 There are KVM-drivers for FreeBSD 8.3 and 9.0 in the ports.
 
 Also, full, native support for MSFT-HyperV is coming to FreeBSD9.
 
 I wouldn'd bother with the free VMware-server.

Agree here it's very slow compared to all of the others . 

 
 AFAIK, the latest vcenter has a web-console, so you don't need a
 Windows VM just to manage your virtualized FreeBSD instances.
 Hopefully, someone else will have to do all the heavy-lifting of
 maintaining all the virtualization-infrastructure.
 

VMware with vsphere server , another product , seperate from esxi, provides a 
web based console but I still use the windows desktop tool , as it works more 
consistently then the web tool.  


 ___
 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
___
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: fsck_ufs running too often

[Mark Saad]

On Jun 22, 2012, at 5:47 PM, Leonardo M. Ramé martinr...@yahoo.com wrote:

 Hi, since a few of days ago, I noticed my home server turns very slow more 
 than once a day, so every time I run top to see what's processes are 
 running, I can see fsck_ufs at the very top, and the hard drive working like 
 mad.
 
 I've checked my crontab and there's nothing related to fsck_ufs, where can I 
 start searching for the cause of the problem?, I thought this process should 
 run only at boot or shutdown, but this time it is running -apparently- 
 without a cause.
 
  
 uname -a:
 FreeBSD server.my.local 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan  3 
 07:46:30 UTC 2012 
 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64
 
 
 Regards,
 Leonardo M. Ramé
 http://leonardorame.blogspot.com
 ___
 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

Can you tell us more about your server . Does its crash or reboot unexpectedly 
? Is this an ungraded server , was it FreeBSD 6,7, or 8 prior ? Also do you 
have any ufs1 file systems mounted?

Please send  the output from mount -t ufs and your dmesg . 

---
Mark saad | 
mark.saad@longcount.org___
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: su problem

[Mark Saad]

On Jun 9, 2012, at 2:45 PM, Sami Halabi sodyn...@gmail.com wrote:

 Hi,
 
 %sysctl kern.console
 kern.console: ttyv0,dcons,/dcons,ttyv0,uart,ucom,
 
 %tail /var/log/messages
 Jun  7 19:54:35 vps16 kernel: Trying to mount root from ufs:/dev/da0s1a
 Jun  7 19:54:36 vps16 kernel: bge0: link state changed to UP
 Jun  7 20:18:04 vps16 kernel: ugen0.2: vendor 0x09da at usbus0
 Jun  7 20:18:04 vps16 kernel: ukbd0: vendor 0x09da USB Keyboard, class
 0/0, rev 1.10/2.50, addr 2 on usbus0
 Jun  7 20:18:04 vps16 kernel: kbd2 at ukbd0
 Jun  7 20:18:05 vps16 kernel: uhid0: vendor 0x09da USB Keyboard, class
 0/0, rev 1.10/2.50, addr 2 on usbus0
 Jun  7 20:19:37 vps16 login: ROOT LOGIN (root) ON ttyv1
 Jun  7 20:21:19 vps16 kernel: ugen0.2: vendor 0x09da at usbus0
 (disconnected)
 Jun  7 20:21:19 vps16 kernel: ukbd0: at uhub0, port 1, addr 2 (disconnected)
 Jun  7 20:21:19 vps16 kernel: uhid0: at uhub0, port 1, addr 2 (disconnected)
 %
 
 the system was loaded with keyboard and disconnected later if i understand
 the logs...
 
 New ideas are appreciated, and thanks in advance,
 Sami
 
 On Sat, Jun 9, 2012 at 7:42 PM, Eugene Grosbein egrosb...@rdtc.ru wrote:
 
 09.06.2012 19:47, Sami Halabi пишет:
 %su -
 Password:
 load: 0.00  cmd: su 30588 [ttydcd] 0.91r 0.00u 0.00s 0% 2092k
 
 Perpaps, your system had no keyboard attached at boot time;
 or for some other reason it booted with /dev/console being serial console
 instead of vidconsole. su locks trying to access serial console
 that is /dev/ttyd0 by default and has Carrier Detect flag enabled.
 Hence, it waits for CD on the first serial port (miserably and hopelessly).
 
 You can check if it's true with sysctl kern.console command.
 You could ask someone to boot the system with keyboard attached -
 no need to type anything, though. The system should detect it
 and assingn /dev/ttyv0 as /dev/console instead of /dev/ttyd0.
 And su won't lock.
 
 Eugene Grosbein
 
 
 
 
 -- 
 Sami Halabi
 Information Systems Engineer
 NMS Projects Expert
 FreeBSD SysAdmin Expert
 ___
 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 

Check the permissions on the su binary it could be missing the suid but.

---
Mark saad | mark.s...@longcount.org

___
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: FreeBSD 9 gptboot: invalid backup GPT header error (boots fine though)

[Mark Saad]

On Wed, May 2, 2012 at 5:03 AM, Adam Strohl
adams-free...@ateamsystems.com wrote:
 Thanks Andrey,

 I've just recompiled /boot/gptboot after updating gpt.c and installed it
 via:

 gpart bootcode -p /boot/gptboot -i 1 da0

 I still see gptboot: invalid backup GPT header on boot (but it does still
 boot).


 On 5/2/2012 12:58, Andrey V. Elsukov wrote:

 On 30.04.2012 23:14, Adam Strohl wrote:

 da0 at tws0 bus 0 scbus0 target 0 lun 0
 da0:LSI 9750-8i    DISK 5.12  Fixed Direct Access SCSI-5 device
 da0: 6000.000MB/s transfers
 da0: 2860992MB (5859311616 512 byte sectors: 255H 63S/T 364725C)


 Let me know anyone wants to see anything else/has seen this/has any
 theories!


 Can you try patch from the r234693, update and reinstall gptboot, does it
 help?
        http://svnweb.freebsd.org/base?view=revisionrevision=234693


Did you try to repair the header ? I saw a similar issue on upgraded
boxes that were 7-STABLE upgraded to 9-STABLE. and recovering made the
warning go away . I may be way off here but just my 2 cents .

% gpart recover da0




-- 
mark saad | nones...@longcount.org


-- 
mark saad | nones...@longcount.org
___
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

Panic after converting Softupdates to journaled softupdates

[Mark Saad]

Hell All
 I wanted to share this with you before sending a pr . I did not find
anything that matched it and I wanted to see if I did something wrong
procedurally .

I upgraded a 7.4-RELEASE amd64 box to 9.0-STABLE sources from
yesterday 10 Apr 2012.

Every thing worked well. I was able to boot and run off 9.0-STABLE my
apps worked ; So I wanted to  swap out soft updates for journaed soft
updates.

The box used 3 UFS slices that were glabled. Note root and var had
softupdates but
/usr/local/mysql/data did not


# DeviceMountpoint  FStype  Options DumpPass#
/dev/label/rootfs   /   ufs rw  1   1
/dev/label/var  /varufs rw  2   2
/dev/label/SWAP noneswapsw  0   0
/dev/label/data /usr/local/mysql/data   ufs rw
 2   2


Here is what I did to convert them.

-

# tunefs -n disable /
tunefs: soft updates cleared
tunefs: file system reloaded
# tunefs -n disable /var
tunefs: soft updates cleared
# fsck -y /
** /dev/label/rootfs
** Last Mounted on /
** Root file system
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
271768 files, 4336411 used, 59997908 free (136692 frags, 7482652
blocks, 0.2% fragmentation)

* FILE SYSTEM IS CLEAN *
# fsck -y /var
** /dev/label/var
** Last Mounted on /var
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
24792 files, 141287 used, 3919776 free (1232 frags, 489818 blocks,
0.0% fragmentation)

* FILE SYSTEM IS CLEAN *

# fsck -y /usr/local/mysql/data
** /dev/label/data
** Last Mounted on /usr/local/mysql/data
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
89528 files, 18246873 used, 51166840 free (59080 frags, 6388470
blocks, 0.1% fragmentation)

* FILE SYSTEM IS CLEAN *

# tunefs -j enable /
Using inode 7 in cg 0 for 33554432 byte journal
tunefs: soft updates journaling set
tunefs: file system reloaded
# tunefs -j enable /var
Using inode 4 in cg 0 for 33554432 byte journal
tunefs: soft updates journaling set
# tunefs -j enable /usr/local/mysql/data
Using inode 425 in cg 0 for 33554432 byte journal
tunefs: soft updates journaling set
# reboot
Apr 11 11:08:58 init: single user shell terminated.
Waiting (max 60 seconds) for system process `vnlru' to stop...done
Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
Waiting (max 60 seconds) for system process `syncer' to stop...
Syncing disks, vnodes remaining...0 0 0 0 0 0 0 0 0 0 done
All buffers synced.
panic: /: ffs_sync: modification on read-only filesystem
cpuid = 0
KDB: stack backtrace:
#0 0x808c283e at kdb_backtrace+0x5e
#1 0x8088d017 at panic+0x187
#2 0x80abc51d at ffs_sync+0x50d
#3 0x809303e1 at vfs_write_suspend+0x111
#4 0x80abcbd8 at ffs_unmount+0x3f8
#5 0x8091b2ce at dounmount+0x26e
#6 0x80921ea2 at vfs_unmountall+0x42
#7 0x8088ce30 at kern_reboot+0x7a0
#8 0x8088d19c at sys_reboot+0x6c
#9 0x80b77260 at amd64_syscall+0x500
#10 0x80b62257 at Xfast_syscall+0xf7
Uptime: 6m38s
Automatic reboot in 15 seconds - press a key on the console to abort


Now the box locked up hard and It would not reboot automatically.

I am waiting to see if I can get a coredump after it comes back up. I
have walk over an kick it over manually now.

So does anyone have any insight into what happened here ?

-- 
mark saad | nones...@longcount.org
___
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: Panic after converting Softupdates to journaled softupdates

[Mark Saad]

On Wed, Apr 11, 2012 at 11:20 AM, Mark Saad nones...@longcount.org wrote:
 Hell All
  I wanted to share this with you before sending a pr . I did not find
 anything that matched it and I wanted to see if I did something wrong
 procedurally .

 I upgraded a 7.4-RELEASE amd64 box to 9.0-STABLE sources from
 yesterday 10 Apr 2012.

 Every thing worked well. I was able to boot and run off 9.0-STABLE my
 apps worked ; So I wanted to  swap out soft updates for journaed soft
 updates.

 The box used 3 UFS slices that were glabled. Note root and var had
 softupdates but
 /usr/local/mysql/data did not


 # Device                Mountpoint      FStype  Options         Dump    Pass#
 /dev/label/rootfs       /               ufs     rw              1       1
 /dev/label/var          /var            ufs     rw              2       2
 /dev/label/SWAP         none            swap    sw              0       0
 /dev/label/data         /usr/local/mysql/data           ufs     rw
         2       2


 Here is what I did to convert them.

 -

 # tunefs -n disable /
 tunefs: soft updates cleared
 tunefs: file system reloaded
 # tunefs -n disable /var
 tunefs: soft updates cleared
 # fsck -y /
 ** /dev/label/rootfs
 ** Last Mounted on /
 ** Root file system
 ** Phase 1 - Check Blocks and Sizes
 ** Phase 2 - Check Pathnames
 ** Phase 3 - Check Connectivity
 ** Phase 4 - Check Reference Counts
 ** Phase 5 - Check Cyl groups
 271768 files, 4336411 used, 59997908 free (136692 frags, 7482652
 blocks, 0.2% fragmentation)

 * FILE SYSTEM IS CLEAN *
 # fsck -y /var
 ** /dev/label/var
 ** Last Mounted on /var
 ** Phase 1 - Check Blocks and Sizes
 ** Phase 2 - Check Pathnames
 ** Phase 3 - Check Connectivity
 ** Phase 4 - Check Reference Counts
 ** Phase 5 - Check Cyl groups
 24792 files, 141287 used, 3919776 free (1232 frags, 489818 blocks,
 0.0% fragmentation)

 * FILE SYSTEM IS CLEAN *

 # fsck -y /usr/local/mysql/data
 ** /dev/label/data
 ** Last Mounted on /usr/local/mysql/data
 ** Phase 1 - Check Blocks and Sizes
 ** Phase 2 - Check Pathnames
 ** Phase 3 - Check Connectivity
 ** Phase 4 - Check Reference Counts
 ** Phase 5 - Check Cyl groups
 89528 files, 18246873 used, 51166840 free (59080 frags, 6388470
 blocks, 0.1% fragmentation)

 * FILE SYSTEM IS CLEAN *

 # tunefs -j enable /
 Using inode 7 in cg 0 for 33554432 byte journal
 tunefs: soft updates journaling set
 tunefs: file system reloaded
 # tunefs -j enable /var
 Using inode 4 in cg 0 for 33554432 byte journal
 tunefs: soft updates journaling set
 # tunefs -j enable /usr/local/mysql/data
 Using inode 425 in cg 0 for 33554432 byte journal
 tunefs: soft updates journaling set
 # reboot
 Apr 11 11:08:58 init: single user shell terminated.
 Waiting (max 60 seconds) for system process `vnlru' to stop...done
 Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
 Waiting (max 60 seconds) for system process `syncer' to stop...
 Syncing disks, vnodes remaining...0 0 0 0 0 0 0 0 0 0 done
 All buffers synced.
 panic: /: ffs_sync: modification on read-only filesystem
 cpuid = 0
 KDB: stack backtrace:
 #0 0x808c283e at kdb_backtrace+0x5e
 #1 0x8088d017 at panic+0x187
 #2 0x80abc51d at ffs_sync+0x50d
 #3 0x809303e1 at vfs_write_suspend+0x111
 #4 0x80abcbd8 at ffs_unmount+0x3f8
 #5 0x8091b2ce at dounmount+0x26e
 #6 0x80921ea2 at vfs_unmountall+0x42
 #7 0x8088ce30 at kern_reboot+0x7a0
 #8 0x8088d19c at sys_reboot+0x6c
 #9 0x80b77260 at amd64_syscall+0x500
 #10 0x80b62257 at Xfast_syscall+0xf7
 Uptime: 6m38s
 Automatic reboot in 15 seconds - press a key on the console to abort


 Now the box locked up hard and It would not reboot automatically.

 I am waiting to see if I can get a coredump after it comes back up. I
 have walk over an kick it over manually now.

 So does anyone have any insight into what happened here ?

 --
 mark saad | nones...@longcount.org

short follow up , savecore did not work no dump was saved to swap.
Also there was no apparent impact from this crash other then the need
to power cycle the box. So far su+j appears to be working. I will
stress the disks a bit more and pull the power to see if it actually
works later.

-- 
mark saad | nones...@longcount.org
___
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

ACPI Issues in 8-STABLE and on

[Mark Saad]

All
  I was wondering if anyone has looking into this ACPI issue noted
back in 2010.

http://lists.freebsd.org/pipermail/freebsd-acpi/2010-February/006332.html

I attempted to upgrade a 7-STABLE DL385g1 with 4G of ram to 9-STABLE
and it was a disaster.

The box was able to boot once and then on a normal reboot the root
filesystem was corrupted beyond repair ( most likely unrelated , but
some unknown issue with su+j *)
and the system would not get past the point noted in the a fore
mentioned thread . I tried to boot this box with 8.2-RELASE amd64 same
issue, 9.0-BETA1 , same issue, 9.0-RELEASE same issue , and 9.0-STABLE
as I pointed out worked intermittently.

So the end result is that this box now only reliably runs 7.0-RELEASE
- 7.4-RELEASE and 7-STABLE , 6.2-RELEASE - 6.4-RELEASE and 6-STABLE
but nothing else.

As a side test , NetBSD 6.0 beta amd64 boots with out issues on this
box as well as DragonFlyBSD 3.01 amd64.

So my solutions are to migrate back to 7-STABLE or use Net or Dfly.
Does anyone know what the root issue is here ?


* The su-j issue was most likely caused by me not properly converting
the old su slice to su+j . I think I may have done a tunefs -j enable
before I did a tunefs -n disable  fsck  .

-- 
mark saad | nones...@longcount.org
___
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

FreeBSD 9-STABLE can not mount root from a glabled device

[Mark Saad]

All
  I upgraded two of my 7-STABLE servers to 9-STABLE today and found
two foot shooters. I believe they are bugs only when you upgrade from
pre 8.0-RELEASE to 9.0-RELEASE or 9-STABLE

1. On 7.x I had been using glabel to label my root filesystem slice,
swap slice , and var slice . Like this

glabel label rootfs /dev/da0s1a
glabel label var /dev/da0s1d
glabel label SWAP /dev/da0s1b

Then in fstab I would have entries like this.
# DeviceMountpoint  FStype  Options DumpPass#
/dev/label/rootfs   /   ufs rw  1   1
/dev/label/var  /varufs rw  2   2
/dev/label/SWAP noneswapsw  0   0

This has worked for me in 6.x and 7.x however upon upgrading to
9-STABLE ( from yesterday ) or 9.0-RELEASE the boot loader could not
find the labeled device.
I had to manually set vfs.root.mountfrom=ufs:/dev/da0s1a or key that
in when the boot process bombed out.

2. After fixing the fstabs to use the real da names I wanted to see
what the boot loader would do with ufs labels. I rebooted my box into
single user mode and ran this

tunefs -L rootfs /dev/da0s1a
tunefs -L var /dev/da0s1d

Then edited the fstab to use the labeled filesystems and rebooted,
much to my surprise it failed in the same way.

I compared this to a new 9.0-STABLE install i  did which used gpt
labels that did would

# DeviceMountpoint  FStype  Options DumpPass#
/dev/label/SWAP noneswapsw  0   0
/dev/gpt/rootfs /   ufs rw  1   1
/dev/gpt/var/varufs rw  2   2
/dev/gpt/data   /data   ufs rw  2   2


So far as I can tell the only difference is that the fresh install
uses the GPT partitioning scheme where as the upgraded boxes us the
older mbr/fdisk setup.

Any ideas on what I can try to get past this ? I liked using
/dev/label as it made the devices sort of agnostic to what filesystem
or partitioning scheme was on them.

-- 
mark saad | nones...@longcount.org
___
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: Heavy fs corruption with 9.0-RELEASE

[Mark Saad]

On Mar 5, 2012, at 5:21 PM, Xin Li delp...@delphij.net wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA256
 
 On 03/05/12 14:12, Arnaud Lacombe wrote:
 Hi,
 
 I've been running a couple of system with 9.0-RELEASE since it is
 out. All the system were installed through the standard
 installation procedure. After unclean reboot, either crash or
 power-failure, I get a huge amount of really bad filesystem
 corruption (read: silent, fs-wide, corruptions). This happens
 with either i386 or amd64 build. Systems involved use compact flash
 as their system permanent storage medium.
 [...]
 I do not see this behavior when running 9.0-RELEASE on top of a 
 7.4-RELEASE userland (including FS). I've seen this behavior on 
 various CF, so a single bad card is unlikely to be the culprit.
 
 FWIW FS is part of kernel.  So technically you're running 9.0-RELEASE
 UFS with 7.4-RELEASE userland.
 
 Here are the currently mounted filesystem on the machine, as well
 as mount options:
 
 # mount /dev/ada0p2 on / (ufs, local, journaled soft-updates) devfs
 on /dev (devfs, local, multilabel)
 
 Any hints appreciated.
 
 My first step would be take out the journalling soft-updates to see if
 things improves.  Could you test if this happens using brand new
 9.0-RELEASE, but with journaled soft-updates disabled?
 
 (Hint: tunefs -j disable /; tunefs -n enable /; reboot in single user
 mode).
 
 Note that since you say 7.4-RELEASE userland wouldn't have similar
 issue, it might indicate a bug with the new journalled soft-updates's
 fsck implementation.
 
 How are you fsck'ng the 9.0 ufs ? Do you have a 9.0 fsck , tunefs , and mount 
?   Also was the file system created on 9.0 or 7.4 or better yet was it a 7.4 
newfs or 9.0 newfs ?  What options did you use ? 


 Cheers,
 - -- 
 Xin LI delp...@delphij.nethttps://www.delphij.net/
 FreeBSD - The Power to Serve!Live free or die
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v2.0.18 (FreeBSD)
 
 iQEcBAEBCAAGBQJPVTyCAAoJEG80Jeu8UPuzTsgIALvLdbzoNrmE/xUqDEJwGtC8
 zcfGl7tEVLU6BbE3i2ww2tUcMJmOMZwrAg1gZmFyyDhVQwEEQQ2zSTa1Uy3oiNRA
 ts1X31VicEXIMam1Mt5K2G3lMbFES6TvyDrNOit6C2FeUrixHZ2C1JZmA7yzGlsg
 7ZGco+3clwSy2yfKTf0ExjIibkC0Cgz60BgjpQKowpKjUCD5AzB/2EqmZk1pFz6S
 /NYOlF+YG/Y72V3GW1K5DTDFao5znzkulhc5Q/RUoD08o6hmdiaqiRHHmqjIP6Rt
 Gb8Dfggnm8XUBs+AzgUmssCSCvHMHYt9SEel2sB5gSVKzd5rIAXwLxaeKBco1Ws=
 =Hi9P
 -END PGP SIGNATURE-
 ___
 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

---
Mark saad | mark.s...@longcount.org

___
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: known problems with 8.x and HP DL16 G5 server?

[Mark Saad]

On Fri, Feb 10, 2012 at 8:23 AM, Slawa Olhovchenkov s...@zxy.spb.ru wrote:
 On Thu, Feb 09, 2012 at 10:24:11PM -0800, Jeremy Chadwick wrote:

 On Thu, Feb 09, 2012 at 04:02:12PM -0800, Julian Elischer wrote:
  On 2/9/12 1:56 PM, Jeremy Chadwick wrote:
  On Thu, Feb 09, 2012 at 01:48:29PM -0800, Julian Elischer wrote:
  does anyone know of problems with freebsd and this system?
  
  the kernel We tried to boot seems to stop somewhere in the ahci probing.
  Few things:
  
  1) Possible to get full console output (e.g. serial, etc.) from a verbose
  boot?
 
  it's freebsd 8.2 from a TrueNAS/FreeNAS. I'm actually at ix-systems
  at the
  moment.. but I wasnhoping someone could save us some time by saying
  Oh yeah, merge in change number xx
 
  2) Can you also provide the exact release/tag/kernel/thing you're trying
  to install or upgrade to (8.x is a little vague; there are all sorts
  of changes that happen between tags).  For example 8.1 is not going to
  behave the same necessarily as 8.2.
  
  3) When you say ahci probing, are you booting a standard installation
  CD/DVD/memstick of, say, 8.2?  If so, those won't make use of the
  AHCI-to-CAM translation layer (and that AHCI code is also different than
  the native-ATA-AHCI code), so you might try, when booting the system,
  dropping to the loader prompt and issuing load ahci.ko before typing
  boot.  See if that helps.  If it does, great, use it (ahci_load=yes
  in /boot/loader.conf) permanently (and benefit from things like NCQ
  too).
  let me forward you an image...
  4) If it's an Intel ESB2 controller, I believe there were some fixes or
  identification shims put in place for this in recent RELENG_8, which
  wouldn't be available in RELENG_8_2 or 8.2-RELEASE CD/DVDs.  I could be
  remembering the wrong controller though.  Hmm...
  
 
  that may be what we are looking for.
 
  I'll try get more info.

 For others: the last few lines in the kernel log are:

 acpi_hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0
 acpi_hpet0: vend: 0x8086 rev: 0x1 num: 3 hz: 14318180 opts: legacy_route 
 64-bit
 Timecounter HPET frequency 14318180 Hz quality 900
 acpi: wakeup code va 0xff848311d000 pa 0x4000
 ahc_isa_probe 0: ioport 0xc00 alloc failed

 I don't see any indication of AHCI problems here (or AHCI at all).
 ahc_isa_probe is for the ahc(4) controller -- Adaptec SCSI.

 A verbose boot might be more helpful.

 Can you tru hint.ahc.0.disabled=1 ?
 ___
 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

Is this a Dl165 G5 or a G5p .   Also have you tried to change the sata
settings in the bios from AHCI to RAID or compat ?  I am currently
using the G5 , G5p and G7 with 7.3 , 7.4 and 8.3 and , I have seen
this issue once or twice but I could not remember what the fix was.  I
think playing with the bios options for AHCI and reseatting the cables
and backplane resolved this for me the last time.

-- 
mark saad | nones...@longcount.org
___
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: Installworld broken with an NFS /tmp

[Mark Saad]

On Jan 19, 2012, at 5:25 AM, Sergey Kandaurov pluk...@gmail.com wrote:

 On 19 January 2012 13:11, Matt Burke mattbli...@icritical.com wrote:
 I've found the following thread from 2009 which matches what I've just come
 across while trying to install 9-RELEASE to disk on a machine with an NFS 
 root.
 
 http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2009-07/msg00084.html
 
 I've just worked around this by nullfs mounting the local disk's /tmp over
 the existing (nfs) /tmp, but is there a better way of doing this - an
 environment variable to specify an alternate to /tmp perhaps?
 
 
 To solve the sillyrename problem visible during installworld,
 I just add the following to rc.conf (nfs) once and for all:
 
 tmpmfs=YES
 varmfs=YES # why? probably needs for /var/tmp
 

I had to do the same thing, and to be honest I don't like the Nfs root setup. I 
like having all of the tools , but a smaller setup would work better for me . I 
want to see how hard it will be to do a 9 install via mfsbsd or a mfsroot akin 
to what was in 7 and 8 . Has anyone tried that ?

 -- 
 wbr,
 pluknet
 ___
 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

Mark Saad | 
mark.saad@longcount.org___
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: www/Apache22 fails to build when configured for LDAP and AUTHNZ_LDAP

[Mark Saad]

On Wed, Nov 30, 2011 at 11:44 AM, Shaun Meyer meye...@morningside.edu wrote:
 Hello,

 I have already built apache22 successfully on FreeBSD 8.2-RELEASE-p3
 amd64. I realized that I wanted authnz_ldap which wasn't turned on by
 default so I went into www/apache22 and did the following:

 # make clean
 # make config
 # make showconfig | grep LDAP
     LDAP=on Enable mod_ldap
     AUTHNZ_LDAP=on Enable mod_authnz_ldap
 # make

 LDAP and AUTHNZ_LDAP are the only adjusted knobs from the defaults.

 The operative build error is mod_authnz_ldap.c:41:2: error: #error
 mod_authnz_ldap requires APR-util to have LDAP support built  in. To
 fix add --with-ldap to ./configure.

 I have also tried removing and cleaning for the apr package. I see no
 other apache-related files installed and all this has been done
 against the latest, greatest ports collection using `portsnap`.

 This symptoms are identical to
 http://www.freebsd.org/cgi/query-pr.cgi?pr=124651 except, obviously,
 they have fixed that cause.

 Any advice is greatly appreciated,

 Shaun Meyer

You need to just rebuild the apr port with ldap. Confirm what version
of apr you have installed and then use make config in that port to add
ldap support. Remove the installed port and reinstall the new one with
ldap support . They you should be able to install apache with ldap
hooks.

-- 
mark saad | nones...@longcount.org
___
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: How to update like Debian

[Mark Saad]

On Thu, Sep 29, 2011 at 12:35 PM, Freddie Cash fjwc...@gmail.com wrote:
 On Thu, Sep 29, 2011 at 9:02 AM, Denny Schierz linuxm...@4lin.net wrote:

 I think, I do not understand, how to update (security/bugfixes) my 8.2
 machines :-) I searched a lot and tried, what I have found in the docs, but
 I had trouble ...

 What I have done (one thing was working, but didn't know, if it is
 correct):


 Updating FreeBSD is done is two separate processes, which can be done
 independently of one another.

 There is a clear separation between the base FreeBSD OS and third-party
 apps installed on top.  This is something that is missing in the land of
 the penguin, and tends to trip people up as they switch between FreeBSD and
 Linux (in either direction).

 To do a binary upgrade of the base OS, you use freebsd-update:
  # freebsd-update fetch
  # freebsd-update update

 See the freebsd-update man page for more details and options.

 That updates only the base OS (stuff under / and /usr; it does not touch
 anything under /usr/local).


 There are several different ways to update your installed third-party
 software (stuff installed via either pkg_add or the ports tree), depending
 on whether or not you want to compile software.  Since you want have a
 Debian-like experience, then you want to install via binary packages as much
 as possible.

 See the man page for pkg_add for information on doing the initial install of
 software, including remotely fetching software (this would be similar to
 apt-get install without any upgrade support).

Two other options to keep ports up to date are portupgrade in
ports-mgmt/portupgrade
and portmaster in ports-mgmt/portmaster .
To see some real world example of using it check the man page for each and
take a look at /usr/ports/UPDATING you will see some example of how to
upgrade major port changes

Check out the entry from 20110517 about upgrading to perl 5.14 and
removing the older version and fixing all the depends.

In the debian world there is no exact comparison for this , major
changes like this could/would be done by the maintainers and pushed
out as debs with some warnings.

portmaster and portupgrade both do the same relative tasks, the best
advice would be to try both and see which you like. Also stick to
using one port management tool . If you want to manually upgrade try
to do that, if you want a wrapper like portupgrade use portinstall /
portupgrade . Mixing and matching ports management tools for me imho a
bad idea for beginners.

 A nice tool for handling upgrades of binary packages, using only binary
 packages, is pkg_upgrade.  This is part of the bsdadminscripts package, so
 you'll need to install that first.  Using pkg_add and pkg_upgrade, you do
 not even need to install the ports tree (and can even rm -rf
 /usr/ports/*).

 That's about as close to a Debian-like experience as you'll get.
 --
 Freddie Cash
 fjwc...@gmail.com
 ___
 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




-- 
mark saad | nones...@longcount.org
___
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: non-responding processes after truss(1)ing

[Mark Saad]

On Tue, Sep 27, 2011 at 6:19 AM, Nikos Vassiliadis nv...@gmx.com wrote:
 On 9/27/2011 1:10 PM, Jeremy Chadwick wrote:

 kill -9 your truss processes; the underlying processes which you are
 truss'ing will probably resume.

 My experience for years has been that truss on FreeBSD is extremely
 buggy and cannot be relied upon (case in point).  Such is still the case
 on RELENG_8 as of today.

 Use ktrace(1) instead.  You'll find it to work pretty much in every
 situation.


What about using dtruss in place of truss is the dtrace implementation
of truss any better then the old libkvm ?


 Thanks, that worked. I'll use ktrace from now on.

 Nikos
 ___
 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




-- 
mark saad | nones...@longcount.org
___
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: xterm - truetype fonts and missing underscore

[Mark Saad]

Tony
nbsp;nbsp;What else is in you .Xresources file . Also have you tried using 
xft formated font names . Ie xft:luxi mono:size=10 ?



--
Mark Saad
Mark.saad@longcount.orgOn Aug 24, 2011 7:08 AM, Tony Maher 
lt;tonyma...@optusnet.com.augt; wrote: 

Hello,



recently (not sure exactly when) my xterms no longer showed the underscore 
character.

In my .Xresources I had (and have had this setting for years):



XTerm*faceName: Monospace

XTerm*faceSize: 10



I noticed when experimenting and modifying values that for one choice

the bottom part of letters like 'g' was missing.

So changed faceSize to 11 and all is good.



In gnome-terminal with Monospace/10 font underscores showed up fine

(and was ok in gnome font selector).  So it appears to be xterm specific.



Has anyone else experienced this?



cheers

-- 

Tony Maheremail: tonyma...@optusnet.com.au

___

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


___
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: UFS SU+J

[Mark Saad]

On Thu, Jun 16, 2011 at 9:01 AM, Bjoern A. Zeeb
bzeeb-li...@lists.zabbadoz.net wrote:
 On Jun 16, 2011, at 12:54 PM, nickolas...@gmail.com wrote:

 I' like to know, if there plans to MFC journaled softupdates to 8-stable?
 If yes, when it would be done?

 it cannot be done and will therefor not happen.  There used to be a branch
 in user/jeff/  or somewhere in the /user or /project area in svn with an
 older version of a backport but I am not sure if it was ever updated again.

 /bz

 --
 Bjoern A. Zeeb                                 You have to have visions!
         Stop bit received. Insert coin for new address family.

 ___
 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


The svn sources are here http://svn.freebsd.org/base/projects/suj/8/ .

Why would suj not make it into 8-STABLE ?


-- 
mark saad | nones...@longcount.org
___
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: Living on gmirror: need to reincarnate /etc/rc.early

[Mark Saad]

On Wed, Jan 26, 2011 at 9:17 AM, Alfred Bartsch bart...@dssgmbh.de wrote:
 Doug Barton schrieb:
 On 01/24/2011 23:20, Eugene Grosbein wrote:
 Hi!

 In RELENG_8, gmirror is good enough to keep whole HDD pair withing the
 mirror.
 Its performance, stability any pretty ease of maintainance allows
 to use it widely.

 With wide deployment of gmirror in production I've faced inability
 of RELENG_8 to store kernel crashdumps out-of-the-box.
 gmirror manual page documents a way to setup FreeBSD so that
 it would store crashdumps again but that way involves /etc/rc.early
 removed from RELENG_8. I've read about intentions - it was unsafe etc.
 But we still need working crashdump support.

 Easiest way is to reincarnate /etc/rc.d/early support making it better
 and safer
 and it should support gmirror's mechanics for crashdumps out-of-the-box.

 I'll tell you the same thing I told Kostik way back when I removed it.
 This is the only thing that anyone has ever suggested a use for in
 /etc/rc.early, and the solution in the man page is a hack. :)

 If this is something that is necessary to do then I'd prefer to do it
 properly and add an /etc/rc.d/gmirror that runs in the proper (early)
 position, and then figure out the proper location in rc.d to handle the
 second half of the configuration.

 I'm happy to review patches.  :)


 Doug

 Hi Doug,
 at our site we are using the following scripts in /etc/rc.d to deal with
 gmirror specials:

 First part (/etc/rc.d/gmirror1):
 
 #!/bin/sh

 # PROVIDE: gmirror1
 # BEFORE:  fsck
 # KEYWORD: nojail

 . /etc/rc.subr

 name=gmirror1
 start_cmd=gmirror1_start
 stop_cmd=:


 gmirror1_start()
 {
   echo gmirror configure -b prefer gm0
   gmirror configure -b prefer gm0
 }

 load_rc_config $name
 run_rc_command $1

 # run only if provider /dev/mirror/gm0 exists
 test -r /dev/mirror/gm0 || exit 0
 -
 Second part (/etc/rc.d/gmirror2):
 
 #!/bin/sh

 # PROVIDE: gmirror2
 # REQUIRE: DAEMON
 # BEFORE:  LOGIN
 # KEYWORD: nojail

 . /etc/rc.subr

 name=gmirror2
 start_cmd=gmirror2_start
 stop_cmd=:

 gmirror2_start()
 {
   echo gmirror configure -b round-robin gm0
   gmirror configure -b round-robin gm0
 }

 load_rc_config $name
 run_rc_command $1

 # run only if provider /dev/mirror/gm0 exists
 test -r /dev/mirror/gm0 || exit 0
 -

 In our environment, the name of the gmirror provider is always
 mirror/gm0. Variable naming of the provider should be added,
 eventually extracted from gmirror list command.

 --
 Alfred Bartsch

 ___
 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


On a side note without /etc/rc.early how would someone do the following tasks ?

1. On bootup relabel /dev/da2s1d to /dev/label/var where da2s1d is the
var for this box.

2. Convert  /usr from gjournal to su+j

Not each task is exactly the same from server to server do to how each
installer / admin decided to layout each disk.

As you may know you cant relabel via glabel label, tunefs -J disable,
gjournal off ..
on a disk that was mounted read / write . The old /etc/rc.early
allowed users to shoot quick scripts in there to fix systems on
a reboot, which is very useful for systems you do not have direct
console access to .
So are we supposed to make a rcng script for each task, is there
another way I am missing ?

-- 

mark saad | nones...@longcount.org
___
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: geom_label, fstab without device names swap partition?

[Mark Saad]

On Wed, Jan 12, 2011 at 1:54 PM, Freddie Cash fjwc...@gmail.com wrote:
 2011/1/12 Lev Serebryakov l...@serebryakov.spb.ru:
  Now, with newfs -L name, geom_label and /dev/ufs/* it is possible
 to not use device names for FSes in /etc/fstab at all. But what to
 do with swap partitions? How to say, that I want swap on
 /dev/ada0s1b or /dev/ad0s1b whatever name it has now?

 Use glabel(8) to label the device:

 # glabel label swap ada0s1b

On a side note there is not a simple way to glabel mounted filesystem


 Then point to the label in /etc/fstab:

 /dev/label/swap    swap   sw ...


 --
 Freddie Cash
 fjwc...@gmail.com
 ___
 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


glabel is also great for doing silly things like things like this

glabel label leftdrive0 /dev/ad4
glabel label rightdrive0 /dev/ad5
gmirror label -v -b load raid1  leftdrive0 rightdrive0

this way when you get a gmirror status you can easily tell which drive
is doing what, red rebuilding etc .




-- 

mark saad | nones...@longcount.org
___
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: geom_label, fstab without device names swap partition?

[Mark Saad]

On Wed, Jan 12, 2011 at 3:01 PM, Freddie Cash fjwc...@gmail.com wrote:
 On Wed, Jan 12, 2011 at 12:00 PM, Mark Saad nones...@longcount.org wrote:
 On Wed, Jan 12, 2011 at 1:54 PM, Freddie Cash fjwc...@gmail.com wrote:
 2011/1/12 Lev Serebryakov l...@serebryakov.spb.ru:
  Now, with newfs -L name, geom_label and /dev/ufs/* it is possible
 to not use device names for FSes in /etc/fstab at all. But what to
 do with swap partitions? How to say, that I want swap on
 /dev/ada0s1b or /dev/ad0s1b whatever name it has now?

 Use glabel(8) to label the device:

 # glabel label swap ada0s1b

 On a side note there is not a simple way to glabel mounted filesystem

 True, but for a swap partition, it's easy to disable swap, label the
 partition, and re-enable swap.  :)

 --
 Freddie Cash
 fjwc...@gmail.com


Well the thing is I like use glabel in place of a fs label as it makes
my devices all names something similar
/dev/label/thingie rather then have /dev/ufs/rootfs and
/dev/label/swap  , I'll have /dev/label/rootfs /dev/label/swap.
Also I dont think you can easily change a live label either .


-- 

mark saad | nones...@longcount.org
___
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: sed is broken under freebsd?

[Mark Saad]

On Wed, Jan 12, 2011 at 5:32 PM, Bob Willcox b...@immure.com wrote:
 On Tue, Jan 11, 2011 at 09:00:09PM -1000, Clifton Royston wrote:
 On Wed, Jan 12, 2011 at 02:32:52AM +0100, Oliver Pinter wrote:
  hi all!
 
  The freebsd versions of sed contained a bug/regression, when \n char
  can i subsitue, gsed not affected with this bug:

  FreeBSD xxx 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Mon Jul 19 02:55:53
  UTC 2010     r...@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
   i386
  a...@xxx ~ echo axa | sed s/x/\n/g
  ana
  a...@xxx ~ echo axa | sed s/x/'\n'/g
  ana

 Different than GNU is not a bug.

 I have 7.3 here.  It behaves as the above, which is how the man page says it
 should work.  The following is how the man page specifies you can substitute
 a newline, by prefacing a quoted actual newline with a backslash:

 $ echo axa | sed 's/x/\
  /g'
 a
 a

   That's how I remember classic sed behaving (Unix v7 or thereabouts.)
   -- Clifton

 FWI, AIX 6.1 sed works as the FreeBSD sed does.


 Solaris 2.6 and OSX 10.6 , do the same thing as FreeBSD as well.



-- 

mark saad | nones...@longcount.org
___
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: Enabling DDB prevent kernel from panicing

[Mark Saad]

On Mon, Jan 10, 2011 at 10:29 PM, Mark Saad nones...@longcount.org wrote:
 On Mon, Jan 10, 2011 at 9:13 PM, Jeremy Chadwick
 free...@jdc.parodius.com wrote:
 On Mon, Jan 10, 2011 at 07:42:21PM -0500, Mark Saad wrote:
 On Mon, Jan 10, 2011 at 6:59 PM,  nickolas...@gmail.com wrote:
  Hello, Mark
 
  2011/1/11 Mark Saad nones...@longcount.org:
  All
  This was originally posted to hackers@
 
  I have a good question that I cant find an answer for. I believe
  found a kernel bug in 7.3-RELEASE that prevents me from booting 64-bit
  kernels on HP's DL360 G4p . The kernel dies with Fatal trap 12: page
  fault while in kernel mode  . The hardware works fine in 7.2-RELEASE
  amd64, 7.1-RELEASE amd64, and 6.4-RELEASE amd64 .
 
  In 7.3-RELEASE amd64 I can not boot from cd or pxe correctly using the
  stock 7.3-RELEASE amd64 kernel however i386 works fine. To see if this
  issue was some how fixed in 7.3-RELEASE-p4 amd64 I rebuilt a GENERIC
  kernel using patches sources and tried to boot and I got the same
  crash.
 
   Next I rebuilt the kernel with KDB and DDB to see if I could get a
  core-dump of the system. I also set loader.conf to
 
  kernel=kernel.DEBUG
  kern.dumpdev=/dev/da0s1b
 
  Next I pxebooted  the box and the system does not crash on boot up, it
  will easily load a nfs root and work fine. So I copied my debug
  kernel, and loader.conf to the local disk and rebooted and it boots
  fine from the local disk .
 
  Looks like a race condition.
  Well, you don't need to compile KDB and DDB, just add
 
  makeoptions DEBUG=-g
 
  into your kernel config file and rebuild kernel.
 
  Then after you got a crash dump you can easy debug it (see FreeBSD
  Developers Handbok):
  http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html
 
 
  wbr,
  Nickolas
 

   Sorry let me clarify the issue, When you install a generic
 7.3-RELEASE amd64 on some of the HP servers I use, the kernel panics
 in boot up
 when it probes the sio driver . Here is a part of my dmesg.boot file

 atkbd0: [ITHREAD]
 psm0: PS/2 Mouse irq 12 on atkbdc0
 psm0: [GIANT-LOCKED]
 psm0: [ITHREAD]
 psm0: model Generic PS/2 mouse, device ID 0
 sio0: configured irq 4 not in bitmap of probed irqs 0
 sio0: port may not be enabled
 sio0: configured irq 4 not in bitmap of probed irqs 0
 sio0: port may not be enabled
 sio0: Standard PC COM port port 0x3f8-0x3ff irq 4 on acpi0
 sio0: type 16550A
 sio0: [FILTER]
 Say about here in the boot up , is where the box crashes with the
 above noted error.

 If I then boot the same box off a 7.1-RELEASE amd64 netboot server ,
 mount the local disks of the 7.3-RELEASE install and edit the
 /boot/device.hints and comment out the sio hints like this

 hint.vga.0.at=isa
 hint.sc.0.at=isa
 hint.sc.0.flags=0x100
 #hint.sio.0.at=isa
 #hint.sio.0.port=0x3F8
 #hint.sio.0.flags=0x10
 #hint.sio.0.irq=4
 #hint.sio.1.at=isa
 #hint.sio.1.port=0x2F8
 #hint.sio.1.irq=3
 #hint.sio.2.at=isa
 #hint.sio.2.disabled=1
 #hint.sio.2.port=0x3E8
 #hint.sio.2.irq=5
 #hint.sio.3.at=isa
 #hint.sio.3.disabled=1
 #hint.sio.3.port=0x2E8
 #hint.sio.3.irq=9
 hint.ppc.0.at=isa
 hint.ppc.0.irq=7

 then boot the server off the local disks , the server boots correctly.

 The odd thing was, I rebuilt a debug 7.3-RELEASE amd64 kernel on
 another working server, and installed it on the broken server and
 booted it off the local disks, with out any changes to the hints file
 and the server booted correctly and I was able to manually break out
 into the debugger , but nothing looked wrong .

 The sio(4) driver has been deprecated in RELENG_8, which uses uart(4).
 uart(4) is better in a lot of regards, and should also be available for
 use on RELENG_7 but you'll need to adjust /etc/ttys to refer to the new
 device names (ttyuX vs. ttydX), plus add the uart entries to
 /boot/device.hints.

 I found that too, and I was thinking about the change but its going to
 require a source build of the kernel to fix that along with a bunch of
 manual work
 on my side that  I would rather not do .

 I'm mentioning this as a workaround.

 Also worth considering is that the sio(4) ISA probe may be touching
 something Bad(tm) as a result, so you might try adding the following
 lines to your loader.conf (not a typo) to disable sio(4) entries
 entirely:

 hint.sio.0.disabled=1
 hint.sio.1.disabled=1

 And see if that improves things.  If it does, remove the sio.1.disabled
 entry and see if that suffices.

 I'll try the hint disabling but how is that different from removing
 the hint outright ?

so adding the hint to the loader.conf worked .  my understanding of
how the loader's 4th bits work make me believe
we can use either file for this hint . but I am still unsure of why
the stock hint breaks the box, where as no hint works
and disabling port via hint works. the other thing is the port works
in its intended way with no hint or disabled hint.


 So to sum this up there is something broken in 7.3-RELEASE but I cant
 figure out what. This server works

Enabling DDB prevent kernel from panicing

[Mark Saad]

All
This was originally posted to hackers@

I have a good question that I cant find an answer for. I believe
found a kernel bug in 7.3-RELEASE that prevents me from booting 64-bit
kernels on HP's DL360 G4p . The kernel dies with Fatal trap 12: page
fault while in kernel mode  . The hardware works fine in 7.2-RELEASE
amd64, 7.1-RELEASE amd64, and 6.4-RELEASE amd64 .

In 7.3-RELEASE amd64 I can not boot from cd or pxe correctly using the
stock 7.3-RELEASE amd64 kernel however i386 works fine. To see if this
issue was some how fixed in 7.3-RELEASE-p4 amd64 I rebuilt a GENERIC
kernel using patches sources and tried to boot and I got the same
crash.

 Next I rebuilt the kernel with KDB and DDB to see if I could get a
core-dump of the system. I also set loader.conf to

kernel=kernel.DEBUG
kern.dumpdev=/dev/da0s1b

Next I pxebooted  the box and the system does not crash on boot up, it
will easily load a nfs root and work fine. So I copied my debug
kernel, and loader.conf to the local disk and rebooted and it boots
fine from the local disk .

Rebooting the server and running off the local disks and debug kernel,
I cant find any issues.

Reboot the box into a GENERIC 7.3-RELEASE-p4 kernel and it crashes

With this error

Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x0
fault code = supervisor write data, page not present
instruction pointer = 0x8:0x800070fa
stack pointer= 0x10:0x8153cbe0
frame pointer= 0x10:0x8153cc50
code segment  = base 0x0, limit 0xf, type 0x1b
 = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags  = interrupt enabled, resume, IOPL = 0
current process   = 0 (swapper)
[thread pid 0 tid 10 ]
Stopped at  bzero+0xa: repe stosq   %es:(%rdi)


It was recommended to comment out the sio hints in /boot/device.hints
I did this and I can properly boot a GENERIC 7.3-RELEASE kernel.

I reran this same test using 7.4-RC1 the system boots with out any
changes to anything.

So my question, does anyone know what changed in stable/7 after the
creation of 7.3-RELEASE that could have
fixed this or does anyone know what  could be causing this issue. The
sio code does not look like its been changed in
a long while . Do we still need s the hits for the sio ports anyway
does omitting them from the hints file cause any
major issues, I can use the serial port for a console and to connect
to to other serial devices with out any issues.

-- 

mark saad | nones...@longcount.org
___
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: Enabling DDB prevent kernel from panicing

[Mark Saad]

On Mon, Jan 10, 2011 at 6:59 PM,  nickolas...@gmail.com wrote:
 Hello, Mark

 2011/1/11 Mark Saad nones...@longcount.org:
 All
 This was originally posted to hackers@

 I have a good question that I cant find an answer for. I believe
 found a kernel bug in 7.3-RELEASE that prevents me from booting 64-bit
 kernels on HP's DL360 G4p . The kernel dies with Fatal trap 12: page
 fault while in kernel mode  . The hardware works fine in 7.2-RELEASE
 amd64, 7.1-RELEASE amd64, and 6.4-RELEASE amd64 .

 In 7.3-RELEASE amd64 I can not boot from cd or pxe correctly using the
 stock 7.3-RELEASE amd64 kernel however i386 works fine. To see if this
 issue was some how fixed in 7.3-RELEASE-p4 amd64 I rebuilt a GENERIC
 kernel using patches sources and tried to boot and I got the same
 crash.

  Next I rebuilt the kernel with KDB and DDB to see if I could get a
 core-dump of the system. I also set loader.conf to

 kernel=kernel.DEBUG
 kern.dumpdev=/dev/da0s1b

 Next I pxebooted  the box and the system does not crash on boot up, it
 will easily load a nfs root and work fine. So I copied my debug
 kernel, and loader.conf to the local disk and rebooted and it boots
 fine from the local disk .

 Looks like a race condition.
 Well, you don't need to compile KDB and DDB, just add

 makeoptions DEBUG=-g

 into your kernel config file and rebuild kernel.

 Then after you got a crash dump you can easy debug it (see FreeBSD
 Developers Handbok):
 http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html


 wbr,
 Nickolas


  Sorry let me clarify the issue, When you install a generic
7.3-RELEASE amd64 on some of the HP servers I use, the kernel panics
in boot up
when it probes the sio driver . Here is a part of my dmesg.boot file

atkbd0: [ITHREAD]
psm0: PS/2 Mouse irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: [ITHREAD]
psm0: model Generic PS/2 mouse, device ID 0
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: Standard PC COM port port 0x3f8-0x3ff irq 4 on acpi0
sio0: type 16550A
sio0: [FILTER]
Say about here in the boot up , is where the box crashes with the
above noted error.

If I then boot the same box off a 7.1-RELEASE amd64 netboot server ,
mount the local disks of the 7.3-RELEASE install and edit the
/boot/device.hints and comment out the sio hints like this

hint.vga.0.at=isa
hint.sc.0.at=isa
hint.sc.0.flags=0x100
#hint.sio.0.at=isa
#hint.sio.0.port=0x3F8
#hint.sio.0.flags=0x10
#hint.sio.0.irq=4
#hint.sio.1.at=isa
#hint.sio.1.port=0x2F8
#hint.sio.1.irq=3
#hint.sio.2.at=isa
#hint.sio.2.disabled=1
#hint.sio.2.port=0x3E8
#hint.sio.2.irq=5
#hint.sio.3.at=isa
#hint.sio.3.disabled=1
#hint.sio.3.port=0x2E8
#hint.sio.3.irq=9
hint.ppc.0.at=isa
hint.ppc.0.irq=7

then boot the server off the local disks , the server boots correctly.

The odd thing was, I rebuilt a debug 7.3-RELEASE amd64 kernel on
another working server, and installed it on the broken server and
booted it off the local disks, with out any changes to the hints file
and the server booted correctly and I was able to manually break out
into the debugger , but nothing looked wrong .

So to sum this up there is something broken in 7.3-RELEASE but I cant
figure out what. This server works with a generic install of
7.1-RELEASE 7.2-RELEASE , 6.1-RELEASE, 6.2-RELEASE and 6.4-RELEASE in
both amd64 and i386 , but not 7.3-RELEASE in amd64 . It also worked in
7.4-RC1 .

avg recommended I see what changed from r212964  to r212994 I am
currently looking into this . Has anyone seen this before ?



-- 

mark saad | nones...@longcount.org
___
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: Enabling DDB prevent kernel from panicing

[Mark Saad]

On Mon, Jan 10, 2011 at 9:13 PM, Jeremy Chadwick
free...@jdc.parodius.com wrote:
 On Mon, Jan 10, 2011 at 07:42:21PM -0500, Mark Saad wrote:
 On Mon, Jan 10, 2011 at 6:59 PM,  nickolas...@gmail.com wrote:
  Hello, Mark
 
  2011/1/11 Mark Saad nones...@longcount.org:
  All
  This was originally posted to hackers@
 
  I have a good question that I cant find an answer for. I believe
  found a kernel bug in 7.3-RELEASE that prevents me from booting 64-bit
  kernels on HP's DL360 G4p . The kernel dies with Fatal trap 12: page
  fault while in kernel mode  . The hardware works fine in 7.2-RELEASE
  amd64, 7.1-RELEASE amd64, and 6.4-RELEASE amd64 .
 
  In 7.3-RELEASE amd64 I can not boot from cd or pxe correctly using the
  stock 7.3-RELEASE amd64 kernel however i386 works fine. To see if this
  issue was some how fixed in 7.3-RELEASE-p4 amd64 I rebuilt a GENERIC
  kernel using patches sources and tried to boot and I got the same
  crash.
 
   Next I rebuilt the kernel with KDB and DDB to see if I could get a
  core-dump of the system. I also set loader.conf to
 
  kernel=kernel.DEBUG
  kern.dumpdev=/dev/da0s1b
 
  Next I pxebooted  the box and the system does not crash on boot up, it
  will easily load a nfs root and work fine. So I copied my debug
  kernel, and loader.conf to the local disk and rebooted and it boots
  fine from the local disk .
 
  Looks like a race condition.
  Well, you don't need to compile KDB and DDB, just add
 
  makeoptions DEBUG=-g
 
  into your kernel config file and rebuild kernel.
 
  Then after you got a crash dump you can easy debug it (see FreeBSD
  Developers Handbok):
  http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html
 
 
  wbr,
  Nickolas
 

   Sorry let me clarify the issue, When you install a generic
 7.3-RELEASE amd64 on some of the HP servers I use, the kernel panics
 in boot up
 when it probes the sio driver . Here is a part of my dmesg.boot file

 atkbd0: [ITHREAD]
 psm0: PS/2 Mouse irq 12 on atkbdc0
 psm0: [GIANT-LOCKED]
 psm0: [ITHREAD]
 psm0: model Generic PS/2 mouse, device ID 0
 sio0: configured irq 4 not in bitmap of probed irqs 0
 sio0: port may not be enabled
 sio0: configured irq 4 not in bitmap of probed irqs 0
 sio0: port may not be enabled
 sio0: Standard PC COM port port 0x3f8-0x3ff irq 4 on acpi0
 sio0: type 16550A
 sio0: [FILTER]
 Say about here in the boot up , is where the box crashes with the
 above noted error.

 If I then boot the same box off a 7.1-RELEASE amd64 netboot server ,
 mount the local disks of the 7.3-RELEASE install and edit the
 /boot/device.hints and comment out the sio hints like this

 hint.vga.0.at=isa
 hint.sc.0.at=isa
 hint.sc.0.flags=0x100
 #hint.sio.0.at=isa
 #hint.sio.0.port=0x3F8
 #hint.sio.0.flags=0x10
 #hint.sio.0.irq=4
 #hint.sio.1.at=isa
 #hint.sio.1.port=0x2F8
 #hint.sio.1.irq=3
 #hint.sio.2.at=isa
 #hint.sio.2.disabled=1
 #hint.sio.2.port=0x3E8
 #hint.sio.2.irq=5
 #hint.sio.3.at=isa
 #hint.sio.3.disabled=1
 #hint.sio.3.port=0x2E8
 #hint.sio.3.irq=9
 hint.ppc.0.at=isa
 hint.ppc.0.irq=7

 then boot the server off the local disks , the server boots correctly.

 The odd thing was, I rebuilt a debug 7.3-RELEASE amd64 kernel on
 another working server, and installed it on the broken server and
 booted it off the local disks, with out any changes to the hints file
 and the server booted correctly and I was able to manually break out
 into the debugger , but nothing looked wrong .

 The sio(4) driver has been deprecated in RELENG_8, which uses uart(4).
 uart(4) is better in a lot of regards, and should also be available for
 use on RELENG_7 but you'll need to adjust /etc/ttys to refer to the new
 device names (ttyuX vs. ttydX), plus add the uart entries to
 /boot/device.hints.

I found that too, and I was thinking about the change but its going to
require a source build of the kernel to fix that along with a bunch of
manual work
on my side that  I would rather not do .

 I'm mentioning this as a workaround.

 Also worth considering is that the sio(4) ISA probe may be touching
 something Bad(tm) as a result, so you might try adding the following
 lines to your loader.conf (not a typo) to disable sio(4) entries
 entirely:

 hint.sio.0.disabled=1
 hint.sio.1.disabled=1

 And see if that improves things.  If it does, remove the sio.1.disabled
 entry and see if that suffices.

I'll try the hint disabling but how is that different from removing
the hint outright ?


 So to sum this up there is something broken in 7.3-RELEASE but I cant
 figure out what. This server works with a generic install of
 7.1-RELEASE 7.2-RELEASE , 6.1-RELEASE, 6.2-RELEASE and 6.4-RELEASE in
 both amd64 and i386 , but not 7.3-RELEASE in amd64 . It also worked in
 7.4-RC1 .

 avg recommended I see what changed from r212964  to r212994 I am
 currently looking into this . Has anyone seen this before ?

 If the server works fine with 7.4-PRERELEASE/RC1, why are you caring
 about 7.3?  Upgrade.  :-)


Can't just upgrade we did a bunch

make release in the subversion world

[Mark Saad]

All
  Are there any new ways to build a release using svn and to not use cvs at 
all? make release still requires a CVSROOT is there a work around for this ? 

--
Mark Saad
mark.s...@ymail.com
___
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

Dumpdev issue in 6.4-STABLE

[Mark Saad]

Hello Stable
  I have an issue with a kernel panic on bootup where the dumpdev loader 
variable is ignored.  

I rebuilt my 6.4-STABLE amd64 kernel with the following options to try an track 
down an issue with a patch.

options KDB
options DDB
options GDB
options BREAK_TO_DEBUGGER
options INVARIANTS
options INVARIANT_SUPPORT
options WITNESS
options DEBUG_VFS_LOCK

I then built and installed the resulting kernel.debug no issues there

I then set in /boot/loader.conf 

dumpdev=/dev/da0s1b

When I reboot and crash the box on the new kernel at the db prompt I cant 
call doadump to work or get an automated one from continue both complain 
about no dumpdev defined . 

Does anyone have a solution for this ?


--
Mark Saad
mark.s...@ymail.com
___
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: Dumpdev issue in 6.4-STABLE

[Mark Saad]

 wrote:
  I then set in /boot/loader.conf 
  
  dumpdev=/dev/da0s1b
 
 On 8-STABLE dumpdev should be defined in rc.conf(5). 
 Not sure about
 6-STABLE offhand.

The box dies before init is started so dumpdev in rc.conf is pointless. 
 
 
 -- 
 Benjamin Lee
 http://www.b1c1l1.com/
 
 

--
Mark Saad
mark.s...@ymail.com
___
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: Dumpdev issue in 6.4-STABLE

[Mark Saad]

 Mark Saad wrote:
   
wrote:
 I then set in /boot/loader.conf 
 
 dumpdev=/dev/da0s1b

On 8-STABLE dumpdev should be defined in
 rc.conf(5). 
Not sure about
6-STABLE offhand.
   
   The box dies before init is started so dumpdev in
 rc.conf is pointless. 
 
 I'm afraid you can't set dumpdev from the loader.
 
 In ancient times it was possible to hardcode the dumpdev
 via the kernel configuration, but that option is long
 gone, AFAIK.
 
Oliver so how do I get a core file of what the kernel is doing ? What is the 
new way of doing this ?

 Best regards
    Oliver
 
 -- 
 Oliver Fromme, secnetix GmbH  Co. KG, Marktplatz 29,
 85567 Grafing b. M.
 Handelsregister: Registergericht Muenchen, HRA 74606, 
 Geschäftsfuehrung:
 secnetix Verwaltungsgesellsch. mbH, Handelsregister:
 Registergericht Mün-
 chen, HRB 125758,  Geschäftsführer: Maik Bachmann,
 Olaf Erb, Ralf Gebhart
 
 FreeBSD-Dienstleistungen, -Produkte und mehr:  http://www.secnetix.de/bsd
 
 I started using PostgreSQL around a month ago, and the
 feeling is
 similar to the switch from Linux to FreeBSD in '96 --
 'wow!'.
         -- Oddbjorn Steffensen
 


--
Mark Saad
mark.s...@ymail.com
___
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: Current status of support for high end SAN hardware

[Mark Saad]

Andy
 I am currently using HP MSA1500cs SAN setups on FreeBSD 7 and 6.3
using qlogic cards in HP DL380G4 and G5 servers. I am not yet using
multipath fiber channel which is supported in 7 and I want to test this
out soon.  As for Redhat ES 4 and 5 I am also using the same hardware
setup , I have to say that RedHat ES4 works better for me the
Enterprise 5 .  ES5 has some odd ball networking issues, when you
upgrade from say update 0 - 1 or 1 - 2. For some reason Redhat decided
that it needed to remove your configs for eth0 as part of the upgrade.
I would say to look at using 64Bit FreeBSD 7-RELEASE and ZFS as the
filesystem on the SAN. ZFS is hands down better then EXT3+LVM .



Andy Kosela wrote:

Hi all,
What is the current status of support for high end SAN hardware in FreeBSD?
I'm especially interested in support for HP EVA/XP disk arrays, Qlogic
HBAs, multipathing.
How FreeBSD compares in this environment to RHEL 5?

--
Andy Kosela
ora et labora
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]




--
Mark Saad
Managed UNIX Support
DataPipe Managed Global IT Services

()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments



This message may contain confidential or privileged information.  If you are 
not the intended recipient, please advise us immediately and delete this 
message.  See http://www.datapipe.com/emaildisclaimer.aspx for further 
information on confidentiality and the risks of non-secure electronic 
communication. If you cannot access these links, please notify us by reply 
message and we will send the contents to you.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

: Re: Socket leak (Was: Re: What triggers No BufferSpace), ?Available

[Mark Saad]

Hello All
 This issue goes back some time, but I do not see a solution. Sorry 
about the cross post
not sure where this belongs. Here is an overview of my issue which is 
similar and I hope

someone can point me in the direction of a solution.

I have experiencing an odd socket related issue on a few servers i
manage. They are fairly large ftp servers for popular north american news
agency. They handle 1000's of ftp transactions per hour. Currently they are 
running
FreeBSD 6.3-Release-p1 . I have verified this happened on FreeBSD
6.1-Release 6.1-Stable 6.2-Release 6.2-Stable and 7.0-Release all 32bit
installs and in both SMP an UP kernels. Oddly this issue did not happen
on FreeBSD 4.x . I have a similar setup that has a 1400+ Day uptime
running FreeBSD 4.x-Release. 

The issue is after 7 to 14 days the servers lock up and will not create any new 
tcp sockets. The system used proftp with mysql for authentication of the ftp accounts.

The system is also running Apache 2.2.x , Postfix, Cyrus, clam-av, Diablo JDK 
1.5 for Resin Appserver
and daemontools .

The only sysctls that seem to help are kern.ipc.maxsockets and
kern.maxusers . Currently they are set to 65535 and 1024 .
Changing kern.ipc.maxsockbuf did not have any effect I tried bumping this 
up to 2Meg, 

In any case I started work on logging everything we could think 
of to see what was happening.


I started logging the values of kern.ipc.numopensockets and I noticed
that something is leaking sockets. Here is a sample of the log

2008-04-29--15:04.10  kern.ipc.numopensockets: 1501
2008-04-29--16:04.01  kern.ipc.numopensockets: 1535
2008-04-29--17:04.00  kern.ipc.numopensockets: 1617
2008-04-29--18:04.00  kern.ipc.numopensockets: 1710

This continues until kern.ipc.maxsockets its reached or the box is
rebooted.

The other thing we looked at was the output from vmstat -z
The first thing was the high amount of malloc 128 bucket failures

128 Bucket:524,0, 2489,   80, 8364, 23055239

I also logged the mbuf clusters, we never reached the max mbuf clusters

Its almost like there are stale sockets. Here is a snapshot of the server now

ewr# sockstat -4u |wc -l
139
ewr# sysctl kern.ipc.numopensockets
kern.ipc.numopensockets: 13935

ewr# uptime
7:30PM  up 6 days, 26 mins, 3 users, load averages: 0.18, 0.25, 0.17


My questions.

1. If I can not identify who / what is consuming all my tcp sockets
what will happen if I double or triple the value of kern.ipc.maxsockets ?

2. Could this be an issue with a low kern.maxusers . Its currently set
to 1024 . Also at times when I can not create a new socket I am not
pinned on mbuf clusters . I was able to verify this in the past.

3. I installed a debugging kernel, which I built on the server. I was able to
get a coredump of the server at the point in time we last had an issue.
But I am not sure what I can do with this, kernel debugging is way
beyond what I am capable of doing . Do I want to even pursue this ?

4. Does anyone have any system tunings you could recommend for a high volume
ftp site ? What does ftp.freebsd.org have ?


--
Mark Saad
[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: Socket leak (Was: Re: What triggers No BufferSpace), ?Available

[Mark Saad]

Hello All
 This issue goes back some time, but I do not see a solution. Sorry 
about the cross post
not sure where this belongs. Here is an overview of my issue which is 
similar and I hope

someone can point me in the direction of a solution.

I have experiencing an odd socket related issue on a few servers i
manage. They are fairly large ftp servers for popular north american news
agency. They handle 1000's of ftp transactions per hour. Currently they are 
running
FreeBSD 6.3-Release-p1 . I have verified this happened on FreeBSD
6.1-Release 6.1-Stable 6.2-Release 6.2-Stable and 7.0-Release all 32bit
installs and in both SMP an UP kernels. Oddly this issue did not happen
on FreeBSD 4.x . I have a similar setup that has a 1400+ Day uptime
running FreeBSD 4.x-Release. 

The issue is after 7 to 14 days the servers lock up and will not create any new 
tcp sockets. The system used proftp with mysql for authentication of the ftp accounts.

The system is also running Apache 2.2.x , Postfix, Cyrus, clam-av, Diablo JDK 
1.5 for Resin Appserver
and daemontools .

The only sysctls that seem to help are kern.ipc.maxsockets and
kern.maxusers . Currently they are set to 65535 and 1024 .
Changing kern.ipc.maxsockbuf did not have any effect I tried bumping this 
up to 2Meg, 

In any case I started work on logging everything we could think 
of to see what was happening.


I started logging the values of kern.ipc.numopensockets and I noticed
that something is leaking sockets. Here is a sample of the log

2008-04-29--15:04.10  kern.ipc.numopensockets: 1501
2008-04-29--16:04.01  kern.ipc.numopensockets: 1535
2008-04-29--17:04.00  kern.ipc.numopensockets: 1617
2008-04-29--18:04.00  kern.ipc.numopensockets: 1710

This continues until kern.ipc.maxsockets its reached or the box is
rebooted.

The other thing we looked at was the output from vmstat -z
The first thing was the high amount of malloc 128 bucket failures

128 Bucket:524,0, 2489,   80, 8364, 23055239

I also logged the mbuf clusters, we never reached the max mbuf clusters

Its almost like there are stale sockets. Here is a snapshot of the server now

ewr# sockstat -4u |wc -l
139
ewr# sysctl kern.ipc.numopensockets
kern.ipc.numopensockets: 13935

ewr# uptime
7:30PM  up 6 days, 26 mins, 3 users, load averages: 0.18, 0.25, 0.17


My questions.

1. If I can not identify who / what is consuming all my tcp sockets
what will happen if I double or triple the value of kern.ipc.maxsockets ?

2. Could this be an issue with a low kern.maxusers . Its currently set
to 1024 . Also at times when I can not create a new socket I am not
pinned on mbuf clusters . I was able to verify this in the past.

3. I installed a debugging kernel, which I built on the server. I was able to
get a coredump of the server at the point in time we last had an issue.
But I am not sure what I can do with this, kernel debugging is way
beyond what I am capable of doing . Do I want to even pursue this ?

4. Does anyone have any system tunings you could recommend for a high volume
ftp site ? What does ftp.freebsd.org have ?


--
Mark Saad
[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: mysql frequently crash on 6.2

[Mark Saad]

Hello
   In general This is what I use for my libmap.conf , it works fine 
for me any you may want to give it a try.


 [mysqld]
 libpthread.so libthr.so
 libpthread.so.2 libthr.so.2

Note nothing in MySQL 4.1 compiled on FreeBSD 6.2 should use libc_r.so . 
The other thing in your libmap that looks odd is the line  libthr.so.2 
libthr.so.2  not sure what that will do.



 In any event, my libmap.conf settings are now [located in 
/etc/libmap.conf]:



 [mysqld]
 libc_r.so libthr.so
 libc_r.so.6 libthr.so.2
 libthr.so.2 libthr.so.2
 libpthread.so libthr.so
 libpthread.so.2 libthr.so.2



One thing I normally turn off in MySQL is the query_cache . If your DB 
is constantly receiving updates the query_cache is flushed to with each 
update. This creates alot of useless overhead, in fact if set it very 
high like to 1G or so you will see some nasty side effects of how MySQL 
tries to flush the cache.


As for you log you may want to move that in to the [mysqld] section of 
the config. In this setup I beleive that mysqlhotcopy would be the only 
mysql* command using that directive.


table_cache should not be greater the amount of tables your databases 
have .


read_rnd_buffer_size = 524288 looks way to high your key_buffer_size is 
only 32M  Maybe you want to lower this to 64M of even leave it undefined 
to see what the default does for you.



 PPS. Here's the my.cnf settings for this machine:

 [mysqld]
 safe-show-database
 skip-innodb
 max_connections = 500
 key_buffer = 32M
 myisam_sort_buffer_size = 64M
 join_buffer_size = 1M
 read_buffer_size = 1M
 sort_buffer_size = 2M
 table_cache = 1800
 thread_cache_size = 384
 wait_timeout = 90
 connect_timeout = 10
 tmp_table_size = 64M
 max_heap_table_size = 64M
 max_allowed_packet = 16M
 max_connect_errors = 10
 read_rnd_buffer_size = 524288
 bulk_insert_buffer_size = 8M
 query_cache_limit = 3M
 query_cache_size = 80M
 query_cache_type = 1
 query_prealloc_size = 163840
 query_alloc_block_size = 32768
 skip-name-resolve

 [mysqld_safe]
 open_files_limit = 8192

 [mysqldump]
 quick
 max_allowed_packet = 16M

 [myisamchk]
 key_buffer = 16M
 sort_buffer = 16M
 read_buffer = 16M
 write_buffer = 16M

 [mysqlhotcopy]
 interactive-timeout

 log = /var/log/mysql/mysql_logfile






--
Mark Saad
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: mpt problems. (Re: Dell hardware raid 0 (sas5ir) or gmirror?)

[Mark Saad]

Hello
   So the HP DL320G4 servers come with a similar LSI Logic SAS 
controller. In 6.2-RELEASE  was seeing the same issue;
The fix I found was a firmware update from HP HP Firmware Update 7.6.0 . 
After applied the mpt messages went away .
I beelive this is a bug in the LSI firmware more then the FreeBSD OS, as 
this controller has been very odd regardless of what os I am running on it.


Josef Karthauser wrote:

On Sat, Jan 27, 2007 at 10:47:49PM +, Josef Karthauser wrote:

The error messages from mpt are attached in the file called 'messages'.
The kernel probe boot time log is attached as dmesg.log.




Jan 27 18:42:03 littoralis kernel: mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x01 
Depth 121
Jan 27 18:44:01 littoralis kernel: mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x00 
Depth 121
Jan 27 18:51:06 littoralis kernel: mpt0: request 0xca756328:48785 timed out for 
ccb 0xca8f0c00 (req-ccb 0xca8f0c00)
Jan 27 18:51:06 littoralis kernel: mpt0: attempting to abort req 
0xca756328:48785 function 0
Jan 27 18:51:06 littoralis kernel: mpt0: request 0xca755c28:48786 timed out for 
ccb 0xcc213800 (req-ccb 0xcc213800)


An update for anyone who's following this thread.

At Matthew Jacob's suggestion I tweaked the 'camcontrol tags'
settings for the drives, and with a particular choice of settings
the problems goes away.

So, at boot time both drives (da0|1) report that they have 255 tag
openings.  However you can see above in the logs that the mpt files
when the depth gets to 121.  If I manually set the tags for the
drives to anything 120 or above the drive controller complains under
load, and one of the disks goes away.  If I get it to 119 the server
runs all day without missing a beat.

Matt suggested quirking the drives to fix this.  I'm wondering though
where it is that the mpt controller get the queue size of 121 from, and
why the drives report 255 at boot time.  Is this because the control
isn't mediating this information properly, or is there a bug in the
controller firmware or driver?

Joe



--
Mark Saad
[EMAIL PROTECTED]
DataPipe Managed UNIX Support

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Failover-HA-Setup

[Mark Saad]

Ivan Voras wrote:

Dmitriy Kirhlarov wrote:

On Wed, Jan 17, 2007 at 03:20:32PM +0100, Richard Verwayen wrote:


Oh, should I have mentioned that it is a shared SCSI-Storage in between?

You can use gmirror(8) with ggated(8).


I think his problem is that you can't have two machines RW mounting the
same device (doesn't matter if it's FC, ggate or other...). So when one
machine fails, the other must mount the file system and THEN start
daemons...



This is kind of a side topic but does anyone know of a on disk clustered 
file system for FreeBSD; like OCFS2 or GFS . Both which would allow you 
to have more then one box attached read / write to the same scsi or fc 
storage array ?




--
Mark Saad
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]