Re: How to get my Dad's Win2k system to access internet through my FreeBSD 6.2 system

[Da Rock]

On Wed, 2008-10-15 at 22:22 -0700, mdh wrote:
> --- On Thu, 10/16/08, Da Rock <[EMAIL PROTECTED]> wrote:
> > From: Da Rock <[EMAIL PROTECTED]>
> > Subject: Re: How to get my Dad's Win2k system to access internet through my 
> > FreeBSD 6.2 system
> > To: freebsd-questions@freebsd.org
> > Date: Thursday, October 16, 2008, 1:04 AM
> >
> >  Actually I'm not sure... I'm just an
> > innocent bystander :)
> > 
> > Throughout the thread there was mention of enabling nat in
> > the rc.conf,
> > so whichever that was...
> > 
> > My consideration was just in general. Someone mentioned
> > enabling nat,
> > another said don't double nat, so I thought routed
> > would be better. But
> > it seems routed is not the way to go, but to keep
> > gateway_enable:
> > question remains as to whether to use nat or not (I suppose
> > in any form;
> > but if you can enlighten me with regard if one form of nat
> > is better
> > than another especially in the case of double nat then
> > I'd appreciate
> > the information).
> > 
> > The main reason I'm bring up this issue is to clarify
> > (and possibly the
> > OP will then get a better picture too) of precisely how to
> > accomplish
> > the result required. And maybe increase my knowledge of the
> > subject
> > too :) thats always a good thing.
> 
> Essentially, you need three things to accomplish nat'ing via the way I'm 
> going to describe.  There're several ways to do it, but I'll only cover one 
> here, because to describe others, I'd need to go look up docs, which you're 
> more than welcome to do for yourself if you don't like the way I'm going to 
> touch on.  
> 
> First, you need gateway_enable set to yes in /etc/rc.conf.  This is 
> universally true regardless of which method you use for nat'ing.  What this 
> does is instruct the kernel that it has multiple interfaces, and that it must 
> pass packets across them, acting as a router.  This has nothing to do with 
> various route discovery protocols, it only sets a sysctl which tells the 
> kernel to route packets across multiple interfaces.  The default behavior is 
> for the kernel not to do so.  
> 
> Second, you'll need some way for your NAT to get packets.  In some cases, the 
> NAT method is built into the way that it gets packets.  With the way I'm 
> discussing here, it's not.  In this case, we'll use `ipfw`.  You'll need a 
> kernel that supports ipfw for this to work, obviously.  The rule you'll need 
> should look something like this:
> divert 8668 ip4 from any to any via sis0
> Where sis0 is your EXTERNAL network interface (ie, the one facing your cable 
> modem, modem, or whatever else.)  The command to add this should look 
> something like: `ipfw add  divert 8668 ip4 from any to any via 
> ` where rule number is the rule number you'll use (it should be a 
> low one!) and interface is your external-facing network interface device.  
> 
> Third, you'll need natd itself.  natd can be enabled via - you guessed it - 
> the rc.conf variable natd_enable.  That's not all, though.  You'll also need 
> to (in rc.conf) set natd_interface to the interface you specified in the 
> firewall rule, and you'll almost certainly want to set natd_flags to "-u".  
> 
> So all in all, you'll need the ipfw rule, ipfw enabled in your kernel, and 
> the following lines in rc.conf:
> gateway_enable="YES"
> natd_program="/sbin/natd"
> natd_enable="YES"
> natd_interface="sis0"
> natd_flags="-u"
> 
> You may also need to run dhclient or somesuch to get an address from your 
> ISP, but that's a whole other story.  
> Enjoy.  
> 
> - mdh

Been there, done that before (at the time I was merely fumbling, but I
have greater experience now)... interesting point in that is the fact
that natd_enable tells the kernel to pass packets between interfaces.

I'm assuming the problem with double nat'ing is the confusion in packet
traffic. So if the OP is using his ADSL modem to connect to the net,
then it could be safe to assume the public IP would be to the modem
itself, and not his box (barring the possible use of USB), so then the
nat'ing would already be done. Therefore, the best and easiest way would
be to simply bridge his interfaces- correct? Less overheads, etc, plus
simplicity of setup.

Oh I love a good hypothetical- it lets me experiment with systems
without touching anything or breaking it :) The fact that someone else
might build on their knowledge is just a cherry on top. I've not come
across another list that so freely shares knowledge... its great!

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

Re: How to get my Dad's Win2k system to access internet through my FreeBSD 6.2 system

[mdh]

--- On Thu, 10/16/08, Da Rock <[EMAIL PROTECTED]> wrote:
> From: Da Rock <[EMAIL PROTECTED]>
> Subject: Re: How to get my Dad's Win2k system to access internet through my 
> FreeBSD 6.2 system
> To: freebsd-questions@freebsd.org
> Date: Thursday, October 16, 2008, 1:04 AM
>
>  Actually I'm not sure... I'm just an
> innocent bystander :)
> 
> Throughout the thread there was mention of enabling nat in
> the rc.conf,
> so whichever that was...
> 
> My consideration was just in general. Someone mentioned
> enabling nat,
> another said don't double nat, so I thought routed
> would be better. But
> it seems routed is not the way to go, but to keep
> gateway_enable:
> question remains as to whether to use nat or not (I suppose
> in any form;
> but if you can enlighten me with regard if one form of nat
> is better
> than another especially in the case of double nat then
> I'd appreciate
> the information).
> 
> The main reason I'm bring up this issue is to clarify
> (and possibly the
> OP will then get a better picture too) of precisely how to
> accomplish
> the result required. And maybe increase my knowledge of the
> subject
> too :) thats always a good thing.

Essentially, you need three things to accomplish nat'ing via the way I'm going 
to describe.  There're several ways to do it, but I'll only cover one here, 
because to describe others, I'd need to go look up docs, which you're more than 
welcome to do for yourself if you don't like the way I'm going to touch on.  

First, you need gateway_enable set to yes in /etc/rc.conf.  This is universally 
true regardless of which method you use for nat'ing.  What this does is 
instruct the kernel that it has multiple interfaces, and that it must pass 
packets across them, acting as a router.  This has nothing to do with various 
route discovery protocols, it only sets a sysctl which tells the kernel to 
route packets across multiple interfaces.  The default behavior is for the 
kernel not to do so.  

Second, you'll need some way for your NAT to get packets.  In some cases, the 
NAT method is built into the way that it gets packets.  With the way I'm 
discussing here, it's not.  In this case, we'll use `ipfw`.  You'll need a 
kernel that supports ipfw for this to work, obviously.  The rule you'll need 
should look something like this:
divert 8668 ip4 from any to any via sis0
Where sis0 is your EXTERNAL network interface (ie, the one facing your cable 
modem, modem, or whatever else.)  The command to add this should look something 
like: `ipfw add  divert 8668 ip4 from any to any via ` 
where rule number is the rule number you'll use (it should be a low one!) and 
interface is your external-facing network interface device.  

Third, you'll need natd itself.  natd can be enabled via - you guessed it - the 
rc.conf variable natd_enable.  That's not all, though.  You'll also need to (in 
rc.conf) set natd_interface to the interface you specified in the firewall 
rule, and you'll almost certainly want to set natd_flags to "-u".  

So all in all, you'll need the ipfw rule, ipfw enabled in your kernel, and the 
following lines in rc.conf:
gateway_enable="YES"
natd_program="/sbin/natd"
natd_enable="YES"
natd_interface="sis0"
natd_flags="-u"

You may also need to run dhclient or somesuch to get an address from your ISP, 
but that's a whole other story.  
Enjoy.  

- mdh



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

Re: How to get my Dad's Win2k system to access internet through my FreeBSD 6.2 system

[Da Rock]

On Wed, 2008-10-15 at 21:19 -0700, Jeremy Chadwick wrote:
> On Thu, Oct 16, 2008 at 10:15:49AM +1000, Da Rock wrote:
> > 
> > On Wed, 2008-10-15 at 04:10 -0700, Jeremy Chadwick wrote:
> > > On Wed, Oct 15, 2008 at 08:40:48PM +1000, Da Rock wrote:
> > > > 
> > > > On Tue, 2008-10-14 at 06:46 -0400, Michael Powell wrote:
> > > > > Jeremy Chadwick wrote:
> > > > > 
> > > > > > On Tue, Oct 14, 2008 at 04:55:11AM -0400, Michael Powell wrote:
> > > > > [snip] 
> > > > > >> Next, you will want to configure your FreeBSD machine as a NAT 
> > > > > >> gateway.
> > > > > >> In your /etc/rc.conf you will want something like 
> > > > > >> gateway_enable="YES"
> > > > > >> and some form of firewall initialization[1]. The gateway_enable is 
> > > > > >> what
> > > > > >> allows the forwarding of packets between your rl0 and your rl1, 
> > > > > >> but the
> > > > > >> activation of NAT functionality is usually a function contained 
> > > > > >> within a
> > > > > >> firewall. So conceptually, the firewall will be "in between" rl0 
> > > > > >> and rl1.
> > > > > >> 
> > > > > >> There are three different firewalls you can choose from. 
> > > > > >> Configuring the
> > > > > >> firewall is usually where the inexperienced get stuck. This subject
> > > > > >> material is beyond the scope of this missive, and you would do 
> > > > > >> well to
> > > > > >> start reading in the Handbook. But essentially, when you configure 
> > > > > >> NAT in
> > > > > >> the firewall your rl0 (connected to the ISP) will be assigned a 
> > > > > >> "Public"
> > > > > >> IP address and the NAT function will translate between "Public" and
> > > > > >> "Private".
> > > > > 
> > > > > With respect to "NAT", the caveat here is the assumption that your 
> > > > > DSL/Cable
> > > > > modem is *not* already performing NAT. The situation you do not want 
> > > > > to get
> > > > > into is having *two* NATs. The content herein is assuming that the 
> > > > > external
> > > > > (rl0) interface is getting assigned a "Public" IP from the ISP. 
> > > > >  
> > > > 
> > > > If this is the case wouldn't the OP set router_enable=YES instead of
> > > > gateway?
> > > 
> > > No.  router_enable causes routed(8) to run, which allows for
> > > announcements and withdraws of network routes via RIPv1/v2.  This is
> > > something completely different than forwarding packets.
> > > 
> > > What the OP wants is to route packets from his private LAN (e.g.
> > > 192.168.0.0/16) on to the Internet using NAT.  That means he has to have
> > > a NAT gateway of some kind that forwards and translates packets.  That
> > > means he needs gateway_enable="yes", which allows IPv4 forwarding
> > > to happen "through" the FreeBSD box.  In layman's terms, it allows
> > > the FreeBSD box to be used a "Gateway" for other computers which
> > > are connected to it directly.
> > > 
> > 
> > Ok, then. So it would be gateway_enable, but no nat_enable? (To avoid
> > double nat'ing)
> 
> Do you mean firewall_nat_enable, natd_enable, or ipnat_enable?  :-)
> See /etc/defaults/rc.conf.
> 

 Actually I'm not sure... I'm just an innocent bystander :)

Throughout the thread there was mention of enabling nat in the rc.conf,
so whichever that was...

My consideration was just in general. Someone mentioned enabling nat,
another said don't double nat, so I thought routed would be better. But
it seems routed is not the way to go, but to keep gateway_enable:
question remains as to whether to use nat or not (I suppose in any form;
but if you can enlighten me with regard if one form of nat is better
than another especially in the case of double nat then I'd appreciate
the information).

The main reason I'm bring up this issue is to clarify (and possibly the
OP will then get a better picture too) of precisely how to accomplish
the result required. And maybe increase my knowledge of the subject
too :) thats always a good thing.

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

Re: Interrupt storm detected on "irq10:"; throttling interrupt source

[Jeremy Chadwick]

On Wed, Oct 15, 2008 at 06:17:56PM -0700, mdh wrote:
> --- On Wed, 10/15/08, nazir <[EMAIL PROTECTED]> wrote:
> > From: nazir <[EMAIL PROTECTED]>
> > Subject: Interrupt storm detected on "irq10:"; throttling interrupt source
> > To: freebsd-questions@freebsd.org
> > Date: Wednesday, October 15, 2008, 8:44 PM
> > Hi,
> > 
> > I'm getting these on my HP-DL165 AMD Quad Qore
> > 
> > interrupt storm detected on "irq10:"; throttling
> > interrupt source
> 
> What is on IRQ 10?  You can determine this via the command:
> `dmesg |grep irq` then look for the line for IRQ 10 which specifies what 
> device is there.  It could be a driver problem, or it could be that the 
> hardware there is bunk.  
> - mdh

vmstat -i output would also come in handy here.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

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

Re: How to get my Dad's Win2k system to access internet through my FreeBSD 6.2 system

[Jeremy Chadwick]

On Thu, Oct 16, 2008 at 10:15:49AM +1000, Da Rock wrote:
> 
> On Wed, 2008-10-15 at 04:10 -0700, Jeremy Chadwick wrote:
> > On Wed, Oct 15, 2008 at 08:40:48PM +1000, Da Rock wrote:
> > > 
> > > On Tue, 2008-10-14 at 06:46 -0400, Michael Powell wrote:
> > > > Jeremy Chadwick wrote:
> > > > 
> > > > > On Tue, Oct 14, 2008 at 04:55:11AM -0400, Michael Powell wrote:
> > > > [snip] 
> > > > >> Next, you will want to configure your FreeBSD machine as a NAT 
> > > > >> gateway.
> > > > >> In your /etc/rc.conf you will want something like 
> > > > >> gateway_enable="YES"
> > > > >> and some form of firewall initialization[1]. The gateway_enable is 
> > > > >> what
> > > > >> allows the forwarding of packets between your rl0 and your rl1, but 
> > > > >> the
> > > > >> activation of NAT functionality is usually a function contained 
> > > > >> within a
> > > > >> firewall. So conceptually, the firewall will be "in between" rl0 and 
> > > > >> rl1.
> > > > >> 
> > > > >> There are three different firewalls you can choose from. Configuring 
> > > > >> the
> > > > >> firewall is usually where the inexperienced get stuck. This subject
> > > > >> material is beyond the scope of this missive, and you would do well 
> > > > >> to
> > > > >> start reading in the Handbook. But essentially, when you configure 
> > > > >> NAT in
> > > > >> the firewall your rl0 (connected to the ISP) will be assigned a 
> > > > >> "Public"
> > > > >> IP address and the NAT function will translate between "Public" and
> > > > >> "Private".
> > > > 
> > > > With respect to "NAT", the caveat here is the assumption that your 
> > > > DSL/Cable
> > > > modem is *not* already performing NAT. The situation you do not want to 
> > > > get
> > > > into is having *two* NATs. The content herein is assuming that the 
> > > > external
> > > > (rl0) interface is getting assigned a "Public" IP from the ISP. 
> > > >  
> > > 
> > > If this is the case wouldn't the OP set router_enable=YES instead of
> > > gateway?
> > 
> > No.  router_enable causes routed(8) to run, which allows for
> > announcements and withdraws of network routes via RIPv1/v2.  This is
> > something completely different than forwarding packets.
> > 
> > What the OP wants is to route packets from his private LAN (e.g.
> > 192.168.0.0/16) on to the Internet using NAT.  That means he has to have
> > a NAT gateway of some kind that forwards and translates packets.  That
> > means he needs gateway_enable="yes", which allows IPv4 forwarding
> > to happen "through" the FreeBSD box.  In layman's terms, it allows
> > the FreeBSD box to be used a "Gateway" for other computers which
> > are connected to it directly.
> > 
> 
> Ok, then. So it would be gateway_enable, but no nat_enable? (To avoid
> double nat'ing)

Do you mean firewall_nat_enable, natd_enable, or ipnat_enable?  :-)
See /etc/defaults/rc.conf.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

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

Re: Interrupt storm detected on "irq10:"; throttling interrupt source

[mdh]

--- On Wed, 10/15/08, nazir <[EMAIL PROTECTED]> wrote:
> From: nazir <[EMAIL PROTECTED]>
> Subject: Interrupt storm detected on "irq10:"; throttling interrupt source
> To: freebsd-questions@freebsd.org
> Date: Wednesday, October 15, 2008, 8:44 PM
> Hi,
> 
> I'm getting these on my HP-DL165 AMD Quad Qore
> 
> interrupt storm detected on "irq10:"; throttling
> interrupt source

What is on IRQ 10?  You can determine this via the command:
`dmesg |grep irq` then look for the line for IRQ 10 which specifies what device 
is there.  It could be a driver problem, or it could be that the hardware there 
is bunk.  
- mdh



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

Re: RAID 5 - serious problem

[Jon Theil Nielsen]

2008/10/15 Nejc Skoberne <[EMAIL PROTECTED]>

> Hello,
>
> > the drives to the other machine and try to make them online again. Do you
> > think I should try?
>
> If I were you, I would first buy/get a XXX GB SATA drive, create a
> filesystem there
> and copy all three disks block-by-block as three separate files (which will
> be
> the size of the disks). This way you'll still have the backup of your
> screwed up
> drives somewhere in case something goes even more wrong.
>
> However, I don't think your data is *physically* lost. I am almost sure
> that it
> is still on that drives, only the metadata could be fscked up. Now how to
> get the
> data back is another thing. In worst case scenario you could analyze the
> specification of the metadata format for you controller and then write a C
> program
> which would somehow put the bits together again using syscalls.
>
> Bye,
> Nejc
>
Hi again,

There are a lot of interesting statements and arguments in this thread. I am
impressed. But you have to understand that I am not a very advanced user of
FreeBSD and especially Linux. So I have to try to keep it simple. Thanks to
the low dollar course and the technological development, I think it is
reasonable for me to buy an extra disk just to try to fix my problems.
Actually, a 300 GB Raptor will do. And then I can install some Linux flavour
(which one should I prefer) to copy the contents of my "sick" disks
bit-by-bit. And then I can somehow try to bring the disks back online again.
Could you please spell it out for me, which tools I should use for that? My
board has both the Intel controller and a Marvell one. Can I just keep the
disks on the Intel one and disregard the offline status (if I understand you
right, I might lose all metadata if I try to change anything)?
AFAIK, the discussion of hardware vs. software RAID has been going on for a
very long time. And it really seems to be complicated. I recognise the
argument of having to stick with the same hardware. At the same time, it
seems at little pessimistic that a lot of people will end up with lots of
useless disks because the vendors decide to cut backward compatability. I
don't know.

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

Interrupt storm detected on "irq10:"; throttling interrupt source

[nazir]

Hi,

I'm getting these on my HP-DL165 AMD Quad Qore

interrupt storm detected on "irq10:"; throttling interrupt source
interrupt storm detected on "irq10:"; throttling interrupt source
interrupt storm detected on "irq10:"; throttling interrupt source
interrupt storm detected on "irq10:"; throttling interrupt source

# uname -a
FreeBSD intra.umt 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24
10:35:36 UTC 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  amd64

# sysctl hw.model
hw.model: Quad-Core AMD Opteron(tm) Processor 2352

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

Virtual mail and mailman

[Da Rock]

Before I go off rashly and join another mailing list or two, might I
enquire here regarding the difference between virtual alias' and virtual
mailboxes from mailman's point of view? I've been googling, but I'm as
confused as ever...

What I have is vmailboxes on postfix (with a courier frontend) and I
want to setup a mailing list server for at least some of the domains
postfix is hosting.

According to mailman docs it will only use virtual alias' to run. Based
on my current configuration (which I'd like to keep for simplicity), how
do I reconcile this?

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

Re: How to get my Dad's Win2k system to access internet through my FreeBSD 6.2 system

[Da Rock]

On Wed, 2008-10-15 at 04:10 -0700, Jeremy Chadwick wrote:
> On Wed, Oct 15, 2008 at 08:40:48PM +1000, Da Rock wrote:
> > 
> > On Tue, 2008-10-14 at 06:46 -0400, Michael Powell wrote:
> > > Jeremy Chadwick wrote:
> > > 
> > > > On Tue, Oct 14, 2008 at 04:55:11AM -0400, Michael Powell wrote:
> > > [snip] 
> > > >> Next, you will want to configure your FreeBSD machine as a NAT gateway.
> > > >> In your /etc/rc.conf you will want something like gateway_enable="YES"
> > > >> and some form of firewall initialization[1]. The gateway_enable is what
> > > >> allows the forwarding of packets between your rl0 and your rl1, but the
> > > >> activation of NAT functionality is usually a function contained within 
> > > >> a
> > > >> firewall. So conceptually, the firewall will be "in between" rl0 and 
> > > >> rl1.
> > > >> 
> > > >> There are three different firewalls you can choose from. Configuring 
> > > >> the
> > > >> firewall is usually where the inexperienced get stuck. This subject
> > > >> material is beyond the scope of this missive, and you would do well to
> > > >> start reading in the Handbook. But essentially, when you configure NAT 
> > > >> in
> > > >> the firewall your rl0 (connected to the ISP) will be assigned a 
> > > >> "Public"
> > > >> IP address and the NAT function will translate between "Public" and
> > > >> "Private".
> > > 
> > > With respect to "NAT", the caveat here is the assumption that your 
> > > DSL/Cable
> > > modem is *not* already performing NAT. The situation you do not want to 
> > > get
> > > into is having *two* NATs. The content herein is assuming that the 
> > > external
> > > (rl0) interface is getting assigned a "Public" IP from the ISP. 
> > >  
> > 
> > If this is the case wouldn't the OP set router_enable=YES instead of
> > gateway?
> 
> No.  router_enable causes routed(8) to run, which allows for
> announcements and withdraws of network routes via RIPv1/v2.  This is
> something completely different than forwarding packets.
> 
> What the OP wants is to route packets from his private LAN (e.g.
> 192.168.0.0/16) on to the Internet using NAT.  That means he has to have
> a NAT gateway of some kind that forwards and translates packets.  That
> means he needs gateway_enable="yes", which allows IPv4 forwarding
> to happen "through" the FreeBSD box.  In layman's terms, it allows
> the FreeBSD box to be used a "Gateway" for other computers which
> are connected to it directly.
> 

Ok, then. So it would be gateway_enable, but no nat_enable? (To avoid
double nat'ing)

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

Re: How to get my Dad's Win2k system to access internet through my FreeBSD 6.2 system

[Da Rock]

> Unless the question is as broad as 'how do I learn about FreeBSD' it
> is worthwhile to help the person aim that shotgun or exchange it
> for a rifle.

Interesting analogy- I like it :)

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

Re: RAID 5 - serious problem

[Dieter]

> > > I like Intel as much as I like AMD
> > 
> > That is your right.  Inthell has a long history of buggy products,
> > attempting to hide/ignore bugs, poor customer support, outright
> > theft, etc.  AMD isn't perfect, but the list of bad things is far
> > far shorter.  And there are other companies to consider besides
> > just inthell and AMD.
> 
> I'd rather not debate this, as it's off-topic.  We can take it up
> privately if you desire, but keep in mind that my ideal system would be
> an AMD processor on an Intel chipset board -- but I'll probably be dead
> by the time that ever happens.  Both companies could have much to learn
> from one another.

Inthell apparently has some good fab people.  If they were a designless
fab house they might not be on my black list.

> No administrator in their
> right mind is going to disable WC unless the disks are behind some form
> of controller that does caching.  (For NCQ stuff, see below.)

The only setup I have found that doesn't lose data is FFS+softdep+WC off.
So you think I am insane for wanting to not lose data?

> > > NCQ will not necessarily improve write performance.
> > 
> > I doubt it will help if you have the disk's write cache turned on.
> > I'm pretty sure it will help with write cache turned off.
> 
> One thing I haven't tested or experimented with is disabling write
> caching on a drive that has NCQ.  Since FreeBSD lacks NCQ right now, we
> could test this on Linux to see what the I/O difference is (I'm talking
> purely from a dd or bonnie++ perspective).

The filesystem may be significant, and last time I looked, linux
didn't support FFS r/w.

I read something indicating that recent disks do NCQ much better than
earlier ones, so "NCQ support" isn't binary.  This, and people testing
NCQ with the write cache on, could explain the results where NCQ
doesn't help.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Under heavy load internet gets killed, only a reboot can bring it back up

[Pyun YongHyeon]

On Wed, Oct 15, 2008 at 04:24:21PM +0200, Aniruddha wrote:
 > On Wed, 2008-10-15 at 21:09 +0900, PYUN Yong-Hyeon wrote:
 > > This controller is known to buggy one. See below.
 > > 
 > > [...]
 > > 
 > >  > > Trying to mount root from ufs:/dev/ad16s3a
 > >  > > WARNING: / was not properly dismounted
 > >  > > GEOM_LABEL: Label ext2fs/home removed.
 > >  > > GEOM_LABEL: Label ext2fs/data removed.
 > >  > > mskc0: Uncorrectable PCI Express error
 > >  > > mskc0: Uncorrectable PCI Express error
 > >  > 
 > >  > Those errors at the end of your dmesg don't look good; could be the sign
 > >  > of a NIC or motherboard that's going bad, or possibly a very strange
 > >  > driver problem.
 > > 
 > > I guess the message above could be safely ignored.
 > > 
 > >  > 
 > >  > Adding Yong-Hyeon PYUN to this thread, since he helps maintain the
 > >  > msk(4) driver.  Yong-Hyeon, do you know of any conditions where heavy
 > >  > network I/O could cause msk(4) to lock up or stop transmitting traffic,
 > >  > or possibly hard-lock on ifconfig down/up?
 > >  > 
 > > 
 > > I think workaround for the controller bug was committed to HEAD(SVN
 > > r183346). To original poster, would you try latest if_msk.c from
 > > HEAD?(Just copy if_msk.c/if_mskreg.h from HEAD to your box.)
 > > 
 > 
 > You got to help me a little bit here. How do I achieve this? Btw I am
 > running FreeBSD 7.1 BETA. Doesn't that mean the fix is already applied?
 > 

It seems that msk(4) in HEAD does not build correctly on RELENG_7.
Try attached patch.

Save attached patch to /path/to/patch
#cd /usr/src/sys/dev/msk
#patch -p0 < /path/to/patch/msk.watchdog.diff
And rebuild your kernel.

-- 
Regards,
Pyun YongHyeon
Index: if_msk.c
===
--- if_msk.c(revision 183165)
+++ if_msk.c(working copy)
@@ -244,6 +244,9 @@
 static int msk_handle_events(struct msk_softc *);
 static void msk_handle_hwerr(struct msk_if_softc *, uint32_t);
 static void msk_intr_hwerr(struct msk_softc *);
+#ifndef __NO_STRICT_ALIGNMENT
+static __inline void msk_fixup_rx(struct mbuf *);
+#endif
 static void msk_rxeof(struct msk_if_softc *, uint32_t, int);
 static void msk_jumbo_rxeof(struct msk_if_softc *, uint32_t, int);
 static void msk_txeof(struct msk_if_softc *, int);
@@ -783,7 +786,12 @@
return (ENOBUFS);
 
m->m_len = m->m_pkthdr.len = MCLBYTES;
-   m_adj(m, ETHER_ALIGN);
+   if ((sc_if->msk_flags & MSK_FLAG_RAMBUF) == 0)
+   m_adj(m, ETHER_ALIGN);
+#ifndef __NO_STRICT_ALIGNMENT
+   else
+   m_adj(m, MSK_RX_BUF_ALIGN);
+#endif
 
if (bus_dmamap_load_mbuf_sg(sc_if->msk_cdata.msk_rx_tag,
sc_if->msk_cdata.msk_rx_sparemap, m, segs, &nsegs,
@@ -840,7 +848,12 @@
return (ENOBUFS);
}
m->m_pkthdr.len = m->m_len = MSK_JLEN;
-   m_adj(m, ETHER_ALIGN);
+   if ((sc_if->msk_flags & MSK_FLAG_RAMBUF) == 0)
+   m_adj(m, ETHER_ALIGN);
+#ifndef __NO_STRICT_ALIGNMENT
+   else
+   m_adj(m, MSK_RX_BUF_ALIGN);
+#endif
 
if (bus_dmamap_load_mbuf_sg(sc_if->msk_cdata.msk_jumbo_rx_tag,
sc_if->msk_cdata.msk_jumbo_rx_sparemap, m, segs, &nsegs,
@@ -1041,14 +1054,16 @@
 {
int next;
int i;
-   uint8_t val;
 
/* Get adapter SRAM size. */
-   val = CSR_READ_1(sc, B2_E_0);
-   sc->msk_ramsize = (val == 0) ? 128 : val * 4;
+   sc->msk_ramsize = CSR_READ_1(sc, B2_E_0) * 4;
if (bootverbose)
device_printf(sc->msk_dev,
"RAM buffer size : %dKB\n", sc->msk_ramsize);
+   if (sc->msk_ramsize == 0)
+   return (0);
+
+   sc->msk_pflags |= MSK_FLAG_RAMBUF;
/*
 * Give receiver 2/3 of memory and round down to the multiple
 * of 1024. Tx/Rx RAM buffer size of Yukon II shoud be multiple
@@ -1412,6 +1427,7 @@
sc_if->msk_if_dev = dev;
sc_if->msk_port = port;
sc_if->msk_softc = sc;
+   sc_if->msk_flags = sc->msk_pflags;
sc->msk_if[port] = sc_if;
/* Setup Tx/Rx queue register offsets. */
if (port == MSK_PORT_A) {
@@ -1976,6 +1992,7 @@
struct msk_rxdesc *jrxd;
struct msk_jpool_entry *entry;
uint8_t *ptr;
+   bus_size_t rxalign;
int error, i;
 
mtx_init(&sc_if->msk_jlist_mtx, "msk_jlist_mtx", NULL, MTX_DEF);
@@ -2107,9 +2124,16 @@
goto fail;
}
 
+   rxalign = 1;
+   /*
+* Workaround hardware hang which seems to happen when Rx buffer
+* is not aligned on multiple of FIFO word(8 bytes).
+*/
+   if ((sc_if->msk_flags & MSK_FLAG_RAMBUF) != 0)
+   rxalign = MSK_RX_BUF_ALIGN;
/* Create tag for Rx buffers. */
error = bus_dma_tag_create(sc_if->msk_cdata.msk_parent_tag,/* parent */
-   1, 0,   /* alignment, boundary */
+   rxalign, 0, /* alignment, bo

Re: new install sunfire v100

[mdh]

--- On Wed, 10/15/08, Davenport, Steve M <[EMAIL PROTECTED]> wrote:
> From: Davenport, Steve M <[EMAIL PROTECTED]>
> Subject: new install sunfire v100
> To: freebsd-questions@freebsd.org
> Date: Wednesday, October 15, 2008, 1:53 PM
> I'm installing 7.0-RELEASE on a Sun Sunfire v100 server.
> I was able to
> boot the cd, and install through cd one. There is no
> framebuffer on the
> v100 (vt100 serial console interface only) so the install
> would not
> proceed past the first disk. I want to use this system as a
> nameserver
> and was able to download Bind 9.3.5-P2, compile, and run.
> My questions
> are:
>  
> 1) Can I manually complete the install process for items on
> CDs 2&3?
>  
> 2) In the /var/log/messages I see:
>  
> Oct  9 19:50:53 steve3 kernel: acd0: CDRW
>  at ata3-slave
> PIO4
> Oct  9 19:50:53 steve3 kernel: acd0: FAILURE - READ_BIG
> MEDIUM ERROR
> asc=0x11 as
> cq=0x00
> Oct  9 19:50:53 steve3 kernel: GEOM_LABEL: Label for
> provider acd0 is
> iso9660/Fr
> eeBSD_Install.
> Oct  9 19:50:53 steve3 kernel: acd0: FAILURE - READ_BIG
> MEDIUM ERROR
> asc=0x11 as
> cq=0x00
>  
> What is causing these cd errors?
>  
> Thanks for your assistance!

Hi Steve,
With regards to the install, the second and third CDs only include packages.  
You can just as easily run `sysinstall` from the command line while logged in 
as root and install additional packages from an HTTP or FTP server over the 
net, or use the CDs if they work alright.  Above and beyond that, you can also 
just (I prefer this, myself) build the software you want from ports and skip 
binary packages entirely for the most part.  
If your CD drive is functioning as you expect, those syslog errors can probably 
be safely ignored.  If the issue is in fact causing problems with reading CDs, 
you can perform your install of the additional packages via the net, and 
perhaps we can deal with the CD issue - unfortunately, I've never used a 
non-SCSI SPARC64 box with FreeBSD, so I don't know if I'll personally be able 
to help you too much there, but surely some folks here or on the sparc64 list 
would.  
As an aside, you may want to consider signing up for the FreeBSD sparc64 
mailing list.  
- mdh



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

Re: Breach of Contract Reported for FREEBSD.ORG

[David G Lawrence]

> Dear Customer,
> 
>  
> 
> It has been brought to our attention that some or all of the information
> associated with your domain name FREEBSD.ORG is outdated or incorrect.
> These types of complaints are brought to our attention in one of two
> ways. 
> 
>  
> 
> The most common type of complaint is received from the Internet
> Corporation for Assigned Names and Numbers (ICANN). ICANN is the
> non-profit corporation responsible for accrediting domain name
> registrars. ICANN requires domain name registration customers to keep
> their account information current. ICANN mandates that outdated contact
> information can be grounds for domain name cancellation.

Michelle,

   The registration information for freebsd.org is correct. The only thing
that is out of date is one of the email addresses ([EMAIL PROTECTED]), which I
have tried to change, but have been unable to due to a problem with the
Network Solutions website.
   I don't know who reported that the information was incorrect, but they
are mistaken. I will additionally follow up in the other ways mentioned
in your message.

-DG

Dr. David G. Lawrence
President
Download Technologies, Inc. - http://www.downloadtech.com - (866) 399 8500
Pave the road of life with opportunities.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: new install sunfire v100

[Henrik Hudson]

On Wednesday 15 October 2008, "Davenport, Steve M" <[EMAIL PROTECTED]> 
sent a missive stating: 
> I'm installing 7.0-RELEASE on a Sun Sunfire v100 server. I was able to
> boot the cd, and install through cd one. There is no framebuffer on the
> v100 (vt100 serial console interface only) so the install would not
> proceed past the first disk. I want to use this system as a nameserver
> and was able to download Bind 9.3.5-P2, compile, and run. My questions
> are:
>
> 1) Can I manually complete the install process for items on CDs 2&3?

You only need CD1 for a basic server. Bind is part of the base system, so you 
don't need to download it. You can remove it (see src.conf and build world) 
and use the ports system to install Bind from ports.

Henrik
-- 
Henrik Hudson
[EMAIL PROTECTED]
--
"God, root, what is difference?" Pitr; UF (http://www.userfriendly.org/)

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

Re: PF syntax error

[Peter Clark]

Yury Michurin wrote:

Hello,
I have in my pf.conf:
 pass in proto tcp from ! to any port www flags S/SA synproxy 
state (max-src-conn 20, max-src-conn-rate 30/60, overload  
flush global)


and it seems to work just fine...

Regards,
Yury.

On Wed, Oct 15, 2008 at 7:00 PM, Peter Clark <[EMAIL PROTECTED] 
> wrote:


Hello,

I am not sure if I should be here or over at a pf specific list but
here is my problem.

I am trying my hand at pf on a 7.0-p5 RELEASE box and one rule is
giving me problems.

pass in quick on $ext_if proto tcp from any to any port 22 flags S/SA \
 (max-src-conn 15, max-src-conn-rate 5/3, overload 
flush global)

Actually the "pass in" line does not generate the error. The next
line does.

/etc/pf.conf:71: syntax error
If I remove the line the error goes away (obviously). I have tried
using  the exact line from the FreeBSD pf.conf man page:

(max-src-conn-rate 100/10, overload  flush global)

(I changed  to )and that generates the same
error. I tried just using:
(max-src-conn-rate 100/10)

but that too gives me a syntax error.

Any help is appreciated.

Peter Clark

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


It is because I do not have a "keep state" directive in mine. I took it 
out because the pf 4.1 default is "flags S/SA keep state". Yours works 
because you have the synproxy state directive.


Thanks,
Peter Clark

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

Re: RAID 5 - serious problem

[Jeremy Chadwick]

On Wed, Oct 15, 2008 at 01:28:43PM +0100, Dieter wrote:
> > > My personal approach to avoiding data loss is (a) avoid buggy things like
> > > inthell and linux.
> > 
> > Interesting, being as we have another thread going as of late that seems
> > to link transparent data loss with AMD AM2-based systems with certain
> > models of Adaptec and possibly LSI Logic controller cards.
> 
> This is the SCSI with >= 4 GiB thread?  Sounds like an address map
> problem.

It's the "am2 MBs - 4g + SCSI wipes out root partition" thread.

> > I like Intel as much as I like AMD
> 
> That is your right.  Inthell has a long history of buggy products,
> attempting to hide/ignore bugs, poor customer support, outright
> theft, etc.  AMD isn't perfect, but the list of bad things is far
> far shorter.  And there are other companies to consider besides
> just inthell and AMD.

I'd rather not debate this, as it's off-topic.  We can take it up
privately if you desire, but keep in mind that my ideal system would be
an AMD processor on an Intel chipset board -- but I'll probably be dead
by the time that ever happens.  Both companies could have much to learn
from one another.

> > And I have no idea what your beef is with Linux.
> 
> The quality is crap.  Endless problems, including scrambled data.

I'm not even going to touch this one.

> >  If the OP is
> > successfully able to bring his array on-line using Linux, I would think
> > that says something about the state of things in FreeBSD, would you
> > agree?  Both OSes have their pros and cons.
> 
> It says linux got something right that FreeBSD got wrong.  I never said
> that BSD gets *everything* right, or that linux gets *everything*
> wrong.

I don't really consider it an issue of right or wrong; a very different,
and unique viewpoint you have!  (And I do mean that sincerely)

> > > (b) FFS with softdeps and the disk write cache turned off,
> > 
> > This has been fully discussed by developers, particularly Matt Dillon.
> > I can point you to a thread discussing why doing this is not only silly,
> > but a bad idea.  And if you'd like, I can show you just how bad the
> > performance is on disks with WC disabled using UFS2 + softupdates.  When
> > I say bad, I'm serious -- we're talking horrid.  And yes, I have tried
> > it -- see PR 127717 for evidence that I *have* tried it.  :-)
> 
> I am WELL aware of how bad write performance is on disks with the write
> cache turned off.  I get only about 10% of what the hardware can do,
> and with large files that is very noticeable.  :-(  But data integrity is
> important.

Your 10% claim is about right.  Here's some actual tests I just did
(filesystem layer is in the way, but you get the idea):

atapci0:  port 
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f irq 18 at device 31.2 on pci0
ata0:  on atapci0
ata0: [ITHREAD]
ad0: 114473MB  at ata0-master SATA150

testbox# ./atacontrol cap ad0 | grep write
write cacheyes  yes

testbox# dd if=/dev/zero of=/usr/testfile bs=1m count=1024
1024+0 records in
1024+0 records out
1073741824 bytes transferred in 20.199726 secs (53156257 bytes/sec)

testbox# ./atacontrol wc ad0 off
testbox# ./atacontrol cap ad0 | grep write
write cacheyes  no

testbox# dd if=/dev/zero of=/usr/testfile bs=1m count=1024
1024+0 records in
1024+0 records out
1073741824 bytes transferred in 155.745314 secs (6894216 bytes/sec)

That's about 13% of the full capability.  No administrator in their
right mind is going to disable WC unless the disks are behind some form
of controller that does caching.  (For NCQ stuff, see below.)

As for the reading material:

http://lists.freebsd.org/pipermail/freebsd-stable/2008-September/045495.html
http://lists.freebsd.org/pipermail/freebsd-stable/2008-September/045542.html

> > > (c) full backups.
> > 
> > I'm curious what your logic is here too -- this one is debatable, so I'd
> > like to hear your view.
> 
> Things go wrong, and when they do backups are useful.  The obvious problem
> is that a backup quickly becomes out of date as data changes.  RAID stays
> current, but doesn't help with accidental file deletions, in cases
> where the entire machine dies (fire. flood, etc.), and so on.  A proper
> RAID (that actually helps reliability rather than hurting it) plus
> off site backups gets you pretty close.  A RAID with an off site mirror
> plus off site backups would be about as reliable as you can get.  But if
> the rate of data changes is high the communication charges could be
> prohibitive.  It all comes down to how important your data is and how
> much money is available.

Ah sorry, I misinterpreted what you wrote!  For some reason I thought
you were advocating *not* performing full level-0 backups.  :-)

> > NCQ will not necessarily improve write performance.
> 
> I doubt it will help if you have the disk's write cache turned on.
> I'm pretty sure it will help with write cache turned off.

One thing I haven't tested or experimented with 

Re: PF syntax error

[Yury Michurin]

Hello,
I have in my pf.conf:
 pass in proto tcp from ! to any port www flags S/SA synproxy state
(max-src-conn 20, max-src-conn-rate 30/60, overload  flush global)

and it seems to work just fine...

Regards,
Yury.

On Wed, Oct 15, 2008 at 7:00 PM, Peter Clark <[EMAIL PROTECTED]> wrote:

> Hello,
>
> I am not sure if I should be here or over at a pf specific list but here is
> my problem.
>
> I am trying my hand at pf on a 7.0-p5 RELEASE box and one rule is giving me
> problems.
>
> pass in quick on $ext_if proto tcp from any to any port 22 flags S/SA \
>  (max-src-conn 15, max-src-conn-rate 5/3, overload  flush
> global)
>
> Actually the "pass in" line does not generate the error. The next line
> does.
>
> /etc/pf.conf:71: syntax error
> If I remove the line the error goes away (obviously). I have tried using
>  the exact line from the FreeBSD pf.conf man page:
>
> (max-src-conn-rate 100/10, overload  flush global)
>
> (I changed  to )and that generates the same error. I
> tried just using:
> (max-src-conn-rate 100/10)
>
> but that too gives me a syntax error.
>
> Any help is appreciated.
>
> Peter Clark
>
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> [EMAIL PROTECTED]"
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: System lockup when out of space in /usr

[Kris Kennaway]

Norberto Meijome wrote:

Hi,
FreeBSD ayiin.octantis.com.au 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #94: Wed
Oct 15 09:46:16 EST 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/AYIIN  i386

I've noticed when /usr becomes full (due to a large port build or other
reasons) that my computer becomes completely locked up - frozen. There is no
panic or crash, the system starts becoming more and pegged down  - load starts
to climb, then system blocks intermittently for ever longing periods, load
climbs over 30 and it never comes back from locked-land.

Other than "don't let the system run out of disk space", is there any other fix?


Depends on what the bug is.  See the developers handbook for the next 
steps in getting the debugging information for a developer to analyze.


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

Re: [Fwd: Suhosin Segmentation Fault]

[Alex Dupre]

Jeremy Chadwick wrote:

You are supposed to use one or the other: the patch, or the extension.


Nope, they can be used alone or mixed together (I use both on my 
servers). For a detailed explanation see: 
http://www.hardened-php.net/suhosin/why.html



I'm CC'ing ale@ on this thread, because he's probably not on -questions,
and this has now become a -ports thing.  He can comment on what to do
about these crashes.


Compile PHP in debug and post a backtrace. The suhosin author is a 
FreeBSD committer, so he can surely help solving the problem.



I'm of the opinion that security/php-suhosin should be nuked, especially
if the patch works fine for everyone but the extension causes problems.


See above.


If I disable all other extensions and load only suhosin.so in
/usr/local/etc/php/extensions.ini the apache processes are still crashing.


Apache version?

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

Re: Excuse me- just testing...

[Steven Susbauer]

Da Rock wrote:

Been having trouble posting with a new mail server (only to your server
mind)- just trying sort it out.

Cheers


Please consider sending these to the freebsd-test mailing list, as it is
made for test posts.


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

Re: PF syntax error

[Erik Osterholm]

On Wed, Oct 15, 2008 at 12:00:50PM -0500, Peter Clark wrote:
> Hello,
> 
> I am not sure if I should be here or over at a pf specific list but here 
> is my problem.
> 
> I am trying my hand at pf on a 7.0-p5 RELEASE box and one rule is giving 
> me problems.
> 
> pass in quick on $ext_if proto tcp from any to any port 22 flags S/SA \ 
> 
>  (max-src-conn 15, max-src-conn-rate 5/3, overload  flush 
> global)
> 
> Actually the "pass in" line does not generate the error. The next line does.
> 
> /etc/pf.conf:71: syntax error
> If I remove the line the error goes away (obviously). I have tried using 
>  the exact line from the FreeBSD pf.conf man page:
> 
> (max-src-conn-rate 100/10, overload  flush global)
> 
> (I changed  to )and that generates the same 
> error. I tried just using:
> (max-src-conn-rate 100/10)
> 
> but that too gives me a syntax error.
> 
> Any help is appreciated.
> 
> Peter Clark

The problem seems to be that your rule doesn't have "keep state" in
it.  I think this is a bug, since state is kept by default in FreeBSD
7.0.

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

Re: RAID 5 - serious problem

[Dieter]

> > My personal approach to avoiding data loss is (a) avoid buggy things like
> > inthell and linux.
> 
> Interesting, being as we have another thread going as of late that seems
> to link transparent data loss with AMD AM2-based systems with certain
> models of Adaptec and possibly LSI Logic controller cards.

This is the SCSI with >= 4 GiB thread?  Sounds like an address map
problem.

> I like Intel as much as I like AMD

That is your right.  Inthell has a long history of buggy products,
attempting to hide/ignore bugs, poor customer support, outright
theft, etc.  AMD isn't perfect, but the list of bad things is far
far shorter.  And there are other companies to consider besides
just inthell and AMD.

> -- but it's important to remember that it's
> becoming more and more difficult to provide "flawless" stability on
> things as the complexities increase.

Computers are complex devices and always have been.  Yes this makes it
difficult to get everything right.  Yet it is possible to achieve very
high levels of reliability, better than "5 9s".

> And I have no idea what your beef is with Linux.

The quality is crap.  Endless problems, including scrambled data.

>  If the OP is
> successfully able to bring his array on-line using Linux, I would think
> that says something about the state of things in FreeBSD, would you
> agree?  Both OSes have their pros and cons.

It says linux got something right that FreeBSD got wrong.  I never said
that BSD gets *everything* right, or that linux gets *everything*
wrong.

> > (b) FFS with softdeps and the disk write cache turned off,
> 
> This has been fully discussed by developers, particularly Matt Dillon.
> I can point you to a thread discussing why doing this is not only silly,
> but a bad idea.  And if you'd like, I can show you just how bad the
> performance is on disks with WC disabled using UFS2 + softupdates.  When
> I say bad, I'm serious -- we're talking horrid.  And yes, I have tried
> it -- see PR 127717 for evidence that I *have* tried it.  :-)

I am WELL aware of how bad write performance is on disks with the write
cache turned off.  I get only about 10% of what the hardware can do,
and with large files that is very noticeable.  :-(  But data integrity is
important.

> > (c) full backups.
> 
> I'm curious what your logic is here too -- this one is debatable, so I'd
> like to hear your view.

Things go wrong, and when they do backups are useful.  The obvious problem
is that a backup quickly becomes out of date as data changes.  RAID stays
current, but doesn't help with accidental file deletions, in cases
where the entire machine dies (fire. flood, etc.), and so on.  A proper
RAID (that actually helps reliability rather than hurting it) plus
off site backups gets you pretty close.  A RAID with an off site mirror
plus off site backups would be about as reliable as you can get.  But if
the rate of data changes is high the communication charges could be
prohibitive.  It all comes down to how important your data is and how
much money is available.

> NCQ will not necessarily improve write performance.

I doubt it will help if you have the disk's write cache turned on.
I'm pretty sure it will help with write cache turned off.

> I believe Andrey Elsukov is working on getting NCQ support working when
> AHCI is in use (assuming I remember correctly).

I look forward to having NCQ available.  Write performance without it
is really pathetic.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

PF syntax error

[Peter Clark]

Hello,

I am not sure if I should be here or over at a pf specific list but here 
is my problem.


I am trying my hand at pf on a 7.0-p5 RELEASE box and one rule is giving 
me problems.


pass in quick on $ext_if proto tcp from any to any port 22 flags S/SA \ 

 (max-src-conn 15, max-src-conn-rate 5/3, overload  flush 
global)


Actually the "pass in" line does not generate the error. The next line does.

/etc/pf.conf:71: syntax error
If I remove the line the error goes away (obviously). I have tried using 
 the exact line from the FreeBSD pf.conf man page:


(max-src-conn-rate 100/10, overload  flush global)

(I changed  to )and that generates the same 
error. I tried just using:

(max-src-conn-rate 100/10)

but that too gives me a syntax error.

Any help is appreciated.

Peter Clark

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

Re: [Fwd: Suhosin Segmentation Fault]

[Jeremy Chadwick]

On Wed, Oct 15, 2008 at 10:01:13PM +0200, Alain Wolf wrote:
> On 15.10.2008 20:55, Jeremy Chadwick wrote:
> > On Wed, Oct 15, 2008 at 07:25:08PM +0200, Alain Wolf wrote:
> >> Not much return on freebsd-isp.
> >> I try again here on freebsd-questions.
> >>
> >>  Original-Nachricht 
> >> Betreff: Suhosin Segmentation Fault
> >> Datum: Mon, 13 Oct 2008 09:49:09 +0200
> >> Von: Alain Wolf <[EMAIL PROTECTED]>
> >> An: [EMAIL PROTECTED]
> >> Newsgruppen: gmane.os.freebsd.isp
> >>
> >> After upgrading FreeBSD from 6.3-p3 to 6.3-p5 on our server, all
> >> websites just display a blank page and every HTTP request created a line
> >> as follows in the logs:
> >>
> >> child pid 80326 exit signal Segmentation fault (11)
> >>
> >> This same problem happened on another server a few months ago after the
> >> upgrade from 6.3-p3 to 6.3-p4, but after a rebuild of all FreeBSD ports
> >> all went back to normal. However several rebuilds of all ports did not
> >> solve the problem on this one.
> >>
> >> To narrow down the problem: After disabling the PHP module in Apache the
> >> problem disappears.
> >>
> >> Re-enabling PHP, but disabling the Suhosin extension also works fine.
> >>
> >> The trick found in this  forum, to load the Suhosin extension before all
> >> other PHP extensions in /usr/local/etc/php/extensions.ini does not help.
> >> In fact not loading any extension at all except Suhosin creates the
> >> segfault errors.
> > 
> > Suhosin is not an extension you load in extensions.ini; it's a patch
> > applied to the core of PHP.
> 
> Suhosin is *both*. A patch for php and a extension module for PHP.
> 
> >From http://www.hardened-php.net/suhosin/index.html:
> Suhosin comes in two independent parts, that can be used separately or
> in combination. The first part is a small patch against the PHP core,
> that implements a few low-level protections against bufferoverflows or
> format string vulnerabilities and the second part is a powerful PHP
> extension that implements all the other protections.

Except their own website contradicts themselves in many other places,
including on their forums *and* in other documentation.  I can refer you
to some documentation of theirs that states "Suhosin extension sometimes
causes other extensions to crash because they try to access internal
variables wrongly".

You are supposed to use one or the other: the patch, or the extension.
You've probably read my other mail by now, so you know that I advocate
use of the patch.

> The suhosin patch works fine on our servers. But the extension does not.

So disable it and use only the patch -- problem solved.

I'm CC'ing ale@ on this thread, because he's probably not on -questions,
and this has now become a -ports thing.  He can comment on what to do
about these crashes.

I'm of the opinion that security/php-suhosin should be nuked, especially
if the patch works fine for everyone but the extension causes problems.

> > The extension ordering problem, however, has been thoroughly discussed
> > on -ports in the past.  It happens to some and not others.  There is no
> > guaranteed way to determine what works and what doesn't.  You have to
> > literally enable line-by-line until you figure out which one is causing
> > the problem.
> 
> I tried enabling and disabling extensions. All of them work, as long as
> suhosin.so is not loaded. Regardless of the order.
> 
> If I disable all other extensions and load only suhosin.so in
> /usr/local/etc/php/extensions.ini the apache processes are still crashing.
> 
> > 
> > You can also try building lang/php5 with DEBUG enabled and then when PHP
> > segfaults, run gdb on the coredump and see if you can get a coherent
> > backtrace (sometimes difficult with Apache in the way) to see what sort
> > of functions are causing the crash; often each extension has its own
> > function names, so that might give you some clues.
> Hard for me, as this disrupts customer services. We are running without
> the extensions for now.
> 
> > 
> >> PHP (cli) seems to run fine at all times when called from the command-line.
> > 
> > Now that's very interesting, given as the CLI version also loads all the
> > extensions listed in extensions.ini.
> > 
> > Can you post your /usr/local/etc/php/extensions.ini?  You didn't list
> > off what extensions you have installed.
> > 
> 
> cat /usr/local/etc/php/extensions.ini
> extension=gd.so
> extension=ctype.so
> extension=pcre.so
> extension=session.so
> extension=bz2.so
> extension=openssl.so
> extension=zlib.so
> extension=mbstring.so
> extension=mysql.so
> extension=pdf.so
> extension=mcrypt.so
> extension=simplexml.so
> extension=spl.so
> extension=mysqli.so
> extension=xml.so
> extension=iconv.so
> extension=hash.so
> extension=tokenizer.so
> extension=calendar.so
> extension=ftp.so
> extension=xmlrpc.so
> extension=xmlwriter.so
> extension=zip.so
> extension=filter.so
> ;extension=suhosin.so
> extension=wddx.so
> extension=mhash.so
> extension=json.so
> extension=dom.so
>

Re: Under heavy load internet gets killed, only a reboot can bring it back up

[Jeremy Chadwick]

On Wed, Oct 15, 2008 at 10:02:46PM +0200, Aniruddha wrote:
> On Wed, 2008-10-15 at 11:49 -0700, Jeremy Chadwick wrote:
> > How exactly did you download the URLs I gave you?
> > 
> > Can you show me what's on line 241 of if_msk.c?
> > 
> > A 'grep ^#include if_msk.c' for me returns lines which only include
> > filenames surrounded with "" or <>.
>  
>  I downloaded the files this way:
> 
> wget 
> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/msk/if_msk.c?rev=1.34;content-type=text%2Fplain

This is wrong.  Your shell has interpreted variables in the URL, and you
ended up downloading the wrong URL, which caused HTML and other things
to appear in the file.  Is this your first time using UNIX?  This is a
little surprising.

You need to do (note the apostrophes, DO NOT use double-quotes):

$ wget -O if_msk.c 
'http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/msk/if_msk.c?rev=1.34;content-type=text%2Fplain'

And be sure to do the same for the include file (change the -O argument,
obviously).

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

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

Re: [Fwd: Suhosin Segmentation Fault]

[Jeremy Chadwick]

On Wed, Oct 15, 2008 at 02:47:00PM -0500, Matt wrote:
> On Wed, Oct 15, 2008 at 2:35 PM, Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
> > On Wed, Oct 15, 2008 at 08:26:09PM +0100, Matthew Seaman wrote:
> >> Jeremy Chadwick wrote:
> >>
> >>> Suhosin is not an extension you load in extensions.ini; it's a patch
> >>> applied to the core of PHP.
> >>
> >> % grep suhosin /usr/local/etc/php/extensions.ini
> >> extension=suhosin.so
> >>
> >> It's both a set of patches to the PHP core, and a loadable module.
> >>
> >>   Cheers,
> >>
> >>   Matthew
> >
> > Are you sure?
> 
> Yes - the suhosin extension is located in the ports tree at:
> /usr/ports/security/php-suhosin
> 
> Install instructions are at:
> http://www.hardened-php.net/suhosin/how_to_install_or_upgrade.html#installing_the_extension
> 
> It's been a while since I've looked at the suhosin options and I can't
> remember what the differences are between the extension and the
> core-php patch.

Deep within their forums, I found an answer in a thread.  The thread
pointed me to this:

http://www.hardened-php.net/suhosin/a_feature_list.html

"Engine Protection" is not available in security/php-suhosin.  Seems to
me that the benefits of using the patch version easily outweigh that of
the extension version, solely for protection against formatted string
vulnerabilities.

I also found this amusing tidbit, which is a sticky post on their forum:

http://forum.hardened-php.net/viewtopic.php?id=122

That sticky also states that pspell.so will cause Suhosin to crash,
advocating that pspell.so must come last in extension.so, but then also
advocates simply not using pspell at all.  I'm sure that does nothing
but confuse users.

Seems the OP has also posted there:

http://forum.hardened-php.net/viewtopic.php?id=501

It would be interesting to know if the segfaults people experience are
specific to the extension version of Suhosin.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

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

Re: [Fwd: Suhosin Segmentation Fault]

[Alain Wolf]

On 15.10.2008 20:55, Jeremy Chadwick wrote:
> On Wed, Oct 15, 2008 at 07:25:08PM +0200, Alain Wolf wrote:
>> Not much return on freebsd-isp.
>> I try again here on freebsd-questions.
>>
>>  Original-Nachricht 
>> Betreff: Suhosin Segmentation Fault
>> Datum: Mon, 13 Oct 2008 09:49:09 +0200
>> Von: Alain Wolf <[EMAIL PROTECTED]>
>> An: [EMAIL PROTECTED]
>> Newsgruppen: gmane.os.freebsd.isp
>>
>> After upgrading FreeBSD from 6.3-p3 to 6.3-p5 on our server, all
>> websites just display a blank page and every HTTP request created a line
>> as follows in the logs:
>>
>> child pid 80326 exit signal Segmentation fault (11)
>>
>> This same problem happened on another server a few months ago after the
>> upgrade from 6.3-p3 to 6.3-p4, but after a rebuild of all FreeBSD ports
>> all went back to normal. However several rebuilds of all ports did not
>> solve the problem on this one.
>>
>> To narrow down the problem: After disabling the PHP module in Apache the
>> problem disappears.
>>
>> Re-enabling PHP, but disabling the Suhosin extension also works fine.
>>
>> The trick found in this  forum, to load the Suhosin extension before all
>> other PHP extensions in /usr/local/etc/php/extensions.ini does not help.
>> In fact not loading any extension at all except Suhosin creates the
>> segfault errors.
> 
> Suhosin is not an extension you load in extensions.ini; it's a patch
> applied to the core of PHP.

Suhosin is *both*. A patch for php and a extension module for PHP.

>From http://www.hardened-php.net/suhosin/index.html:
Suhosin comes in two independent parts, that can be used separately or
in combination. The first part is a small patch against the PHP core,
that implements a few low-level protections against bufferoverflows or
format string vulnerabilities and the second part is a powerful PHP
extension that implements all the other protections.

The suhosin patch works fine on our servers. But the extension does not.

> 
> The extension ordering problem, however, has been thoroughly discussed
> on -ports in the past.  It happens to some and not others.  There is no
> guaranteed way to determine what works and what doesn't.  You have to
> literally enable line-by-line until you figure out which one is causing
> the problem.

I tried enabling and disabling extensions. All of them work, as long as
suhosin.so is not loaded. Regardless of the order.

If I disable all other extensions and load only suhosin.so in
/usr/local/etc/php/extensions.ini the apache processes are still crashing.

> 
> You can also try building lang/php5 with DEBUG enabled and then when PHP
> segfaults, run gdb on the coredump and see if you can get a coherent
> backtrace (sometimes difficult with Apache in the way) to see what sort
> of functions are causing the crash; often each extension has its own
> function names, so that might give you some clues.
Hard for me, as this disrupts customer services. We are running without
the extensions for now.

> 
>> PHP (cli) seems to run fine at all times when called from the command-line.
> 
> Now that's very interesting, given as the CLI version also loads all the
> extensions listed in extensions.ini.
> 
> Can you post your /usr/local/etc/php/extensions.ini?  You didn't list
> off what extensions you have installed.
> 

cat /usr/local/etc/php/extensions.ini
extension=gd.so
extension=ctype.so
extension=pcre.so
extension=session.so
extension=bz2.so
extension=openssl.so
extension=zlib.so
extension=mbstring.so
extension=mysql.so
extension=pdf.so
extension=mcrypt.so
extension=simplexml.so
extension=spl.so
extension=mysqli.so
extension=xml.so
extension=iconv.so
extension=hash.so
extension=tokenizer.so
extension=calendar.so
extension=ftp.so
extension=xmlrpc.so
extension=xmlwriter.so
extension=zip.so
extension=filter.so
;extension=suhosin.so
extension=wddx.so
extension=mhash.so
extension=json.so
extension=dom.so
extension=xmlreader.so
extension=exif.so
extension=ncurses.so
extension=gettext.so
extension=ldap.so
extension=pdo.so
extension=soap.so
extension=tidy.so
extension=pdo_sqlite.so
extension=apc.so
extension=readline.so
extension=xsl.so
extension=curl.so

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

Re: [Fwd: Suhosin Segmentation Fault]

[Chuck Swiger]

Hi, all--

On Oct 15, 2008, at 12:47 PM, Matt wrote:

It's been a while since I've looked at the suhosin options and I can't
remember what the differences are between the extension and the
core-php patch.


If you check the following, they discuss the difference in protection  
between using just the patch versus the extension:


http://www.hardened-php.net/suhosin/why.html
http://www.hardened-php.net/suhosin/a_feature_list.html

Regards,
--
-Chuck

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

Re: [Fwd: Suhosin Segmentation Fault]

[Matt]

On Wed, Oct 15, 2008 at 2:35 PM, Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
> On Wed, Oct 15, 2008 at 08:26:09PM +0100, Matthew Seaman wrote:
>> Jeremy Chadwick wrote:
>>
>>> Suhosin is not an extension you load in extensions.ini; it's a patch
>>> applied to the core of PHP.
>>
>> % grep suhosin /usr/local/etc/php/extensions.ini
>> extension=suhosin.so
>>
>> It's both a set of patches to the PHP core, and a loadable module.
>>
>>   Cheers,
>>
>>   Matthew
>
> Are you sure?

Yes - the suhosin extension is located in the ports tree at:
/usr/ports/security/php-suhosin

Install instructions are at:
http://www.hardened-php.net/suhosin/how_to_install_or_upgrade.html#installing_the_extension

It's been a while since I've looked at the suhosin options and I can't
remember what the differences are between the extension and the
core-php patch.

Matt
>
> # find /usr/local/lib/php -name "*suhosin*" -ls
> #
>
> # grep -i suhosin /var/db/ports/php5/options
> WITH_SUHOSIN=true
>
> # grep -i suhosin /usr/local/etc/php/extensions.ini
> #
>
> # pkg_version -v | grep php5
> php5-5.2.6_2=   up-to-date with port
> php5-extensions-1.1 =   up-to-date with port
> php5-mysql-5.2.6_2  =   up-to-date with port
> php5-pcre-5.2.6_2   =   up-to-date with port
> php5-simplexml-5.2.6_2  =   up-to-date with port
>
> # grep -i php5 /usr/local/etc/apache22/httpd.conf
> LoadModule php5_modulelibexec/apache22/libphp5.so
>
> # php -i | grep -i suhosin
> This server is protected with the Suhosin Patch 0.9.6.2
> suhosin.log.phpscript => 0 => 0
> suhosin.log.phpscript.is_safe => Off => Off
> suhosin.log.phpscript.name => no value => no value
> suhosin.log.sapi => no value => no value
> suhosin.log.script => no value => no value
> suhosin.log.script.name => no value => no value
> suhosin.log.syslog => no value => no value
> suhosin.log.syslog.facility => no value => no value
> suhosin.log.syslog.priority => no value => no value
> suhosin.log.use-x-forwarded-for => Off => Off
>
> :-)
>
> --
> | Jeremy Chadwickjdc at parodius.com |
> | Parodius Networking   http://www.parodius.com/ |
> | UNIX Systems Administrator  Mountain View, CA, USA |
> | Making life hard for others since 1977.  PGP: 4BD6C0CB |
>
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: [Fwd: Suhosin Segmentation Fault]

[Jeremy Chadwick]

On Wed, Oct 15, 2008 at 08:26:09PM +0100, Matthew Seaman wrote:
> Jeremy Chadwick wrote:
>
>> Suhosin is not an extension you load in extensions.ini; it's a patch
>> applied to the core of PHP.
>
> % grep suhosin /usr/local/etc/php/extensions.ini
> extension=suhosin.so
>
> It's both a set of patches to the PHP core, and a loadable module.
>
>   Cheers,
>
>   Matthew

Are you sure?

# find /usr/local/lib/php -name "*suhosin*" -ls
#

# grep -i suhosin /var/db/ports/php5/options
WITH_SUHOSIN=true

# grep -i suhosin /usr/local/etc/php/extensions.ini
#

# pkg_version -v | grep php5
php5-5.2.6_2=   up-to-date with port
php5-extensions-1.1 =   up-to-date with port
php5-mysql-5.2.6_2  =   up-to-date with port
php5-pcre-5.2.6_2   =   up-to-date with port
php5-simplexml-5.2.6_2  =   up-to-date with port

# grep -i php5 /usr/local/etc/apache22/httpd.conf
LoadModule php5_modulelibexec/apache22/libphp5.so

# php -i | grep -i suhosin
This server is protected with the Suhosin Patch 0.9.6.2
suhosin.log.phpscript => 0 => 0
suhosin.log.phpscript.is_safe => Off => Off
suhosin.log.phpscript.name => no value => no value
suhosin.log.sapi => no value => no value
suhosin.log.script => no value => no value
suhosin.log.script.name => no value => no value
suhosin.log.syslog => no value => no value
suhosin.log.syslog.facility => no value => no value
suhosin.log.syslog.priority => no value => no value
suhosin.log.use-x-forwarded-for => Off => Off

:-)

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

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

Re: [Fwd: Suhosin Segmentation Fault]

[Matthew Seaman]

Jeremy Chadwick wrote:


Suhosin is not an extension you load in extensions.ini; it's a patch
applied to the core of PHP.


% grep suhosin /usr/local/etc/php/extensions.ini
extension=suhosin.so

It's both a set of patches to the PHP core, and a loadable module.

Cheers,

Matthew

--
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
 Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
 Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature

Re: [Fwd: Suhosin Segmentation Fault]

[Jeremy Chadwick]

On Wed, Oct 15, 2008 at 07:25:08PM +0200, Alain Wolf wrote:
> Not much return on freebsd-isp.
> I try again here on freebsd-questions.
> 
>  Original-Nachricht 
> Betreff: Suhosin Segmentation Fault
> Datum: Mon, 13 Oct 2008 09:49:09 +0200
> Von: Alain Wolf <[EMAIL PROTECTED]>
> An: [EMAIL PROTECTED]
> Newsgruppen: gmane.os.freebsd.isp
> 
> After upgrading FreeBSD from 6.3-p3 to 6.3-p5 on our server, all
> websites just display a blank page and every HTTP request created a line
> as follows in the logs:
> 
> child pid 80326 exit signal Segmentation fault (11)
> 
> This same problem happened on another server a few months ago after the
> upgrade from 6.3-p3 to 6.3-p4, but after a rebuild of all FreeBSD ports
> all went back to normal. However several rebuilds of all ports did not
> solve the problem on this one.
> 
> To narrow down the problem: After disabling the PHP module in Apache the
> problem disappears.
> 
> Re-enabling PHP, but disabling the Suhosin extension also works fine.
> 
> The trick found in this  forum, to load the Suhosin extension before all
> other PHP extensions in /usr/local/etc/php/extensions.ini does not help.
> In fact not loading any extension at all except Suhosin creates the
> segfault errors.

Suhosin is not an extension you load in extensions.ini; it's a patch
applied to the core of PHP.

The extension ordering problem, however, has been thoroughly discussed
on -ports in the past.  It happens to some and not others.  There is no
guaranteed way to determine what works and what doesn't.  You have to
literally enable line-by-line until you figure out which one is causing
the problem.

You can also try building lang/php5 with DEBUG enabled and then when PHP
segfaults, run gdb on the coredump and see if you can get a coherent
backtrace (sometimes difficult with Apache in the way) to see what sort
of functions are causing the crash; often each extension has its own
function names, so that might give you some clues.

> PHP (cli) seems to run fine at all times when called from the command-line.

Now that's very interesting, given as the CLI version also loads all the
extensions listed in extensions.ini.

Can you post your /usr/local/etc/php/extensions.ini?  You didn't list
off what extensions you have installed.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

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

Re: Under heavy load internet gets killed, only a reboot can bring it back up

[Jeremy Chadwick]

On Wed, Oct 15, 2008 at 07:26:36PM +0200, Aniruddha wrote:
> On Wed, 2008-10-15 at 07:43 -0700, Jeremy Chadwick wrote:
> > Now you need to rebuild the kernel and install the kernel.  In this
> > scenario, when building the kernel DO NOT use any "-j" flags, as if the
> > driver doesn't build, you'll be scrolling back through pages of data to
> > try and find out why.
> > 
> > If the build doesn't occur successfully, paste the errors you get
> > here and one of us can try to figure out why.
> > 
> > Otherwise, installkernel and reboot.  You should not need to build world
> > for this.
> 
> Thanks for the extensive description. Unfortunately I got the following
> error:
>
> > param inline-unit-growth=100 --param large-function-growth=1000  
> > -mno-align-long
> > -strings -mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow -mno-sse 
> > -mno-sse2 -m
> > no-sse3 -ffreestanding
> > /usr/src/sys/dev/msk/if_msk.c:241:10: error: #include expects "FILENAME" or 
> > 

How exactly did you download the URLs I gave you?

Can you show me what's on line 241 of if_msk.c?

A 'grep ^#include if_msk.c' for me returns lines which only include
filenames surrounded with "" or <>.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

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

Re: RAID 5 - serious problem

[Jeremy Chadwick]

On Wed, Oct 15, 2008 at 10:14:42AM +0100, Dieter wrote:
> > FreeBSD 7.0-Release
> > Intel D975XBX2 motherboard (Intel Matrix Storage Technology)
> > 3 WD Raptor 74 GB in a RAID 5 array
> > 1 WD Raptor 150 GB as a standalone disk
> > / and /var mounted on the standalone,, /usr on the RAID 5
> > I believe what happened was that one of the disks didn't respond for such a
> > long time, that is was marked "bad". And afterwards the same thing happened
> > for the other disks. When I try to boot the system, all three disks are
> > marked "Offline".
> 
> > I am very desperate not to lose my data,
> 
> In that case, step one is to use dd(1) to make a bit-for-bit copy of the
> three drives to some trusted media.  Since they are marked bad/offline,
> you might need to move them to a controller that doesn't know anything
> about RAID.  (Note that there is risk here, and in almost anything you do
> at this point.)  Once you have this bit-for-bit backup, you can run any
> experiment you like to attempt to recover your data.  If the experiment
> goes bad, you can dd the exact original contents back using dd, then
> try a different experiment.  While you're at it, make a normal backup
> using dump(8) or whatever you normally use, of / and /var.  Once you have
> *everything* backed up, you can do risky experiments like booting linux.
> 
> My personal approach to avoiding data loss is (a) avoid buggy things like
> inthell and linux.

Interesting, being as we have another thread going as of late that seems
to link transparent data loss with AMD AM2-based systems with certain
models of Adaptec and possibly LSI Logic controller cards.  I like Intel
as much as I like AMD -- but it's important to remember that it's
becoming more and more difficult to provide "flawless" stability on
things as the complexities increase.

And I have no idea what your beef is with Linux.  If the OP is
successfully able to bring his array on-line using Linux, I would think
that says something about the state of things in FreeBSD, would you
agree?  Both OSes have their pros and cons.

> (b) FFS with softdeps and the disk write cache turned off,

This has been fully discussed by developers, particularly Matt Dillon.
I can point you to a thread discussing why doing this is not only silly,
but a bad idea.  And if you'd like, I can show you just how bad the
performance is on disks with WC disabled using UFS2 + softupdates.  When
I say bad, I'm serious -- we're talking horrid.  And yes, I have tried
it -- see PR 127717 for evidence that I *have* tried it.  :-)

There *may* be advantages to disabling a disk's write cache when using a
hardware RAID controller that offers its own on-board cache (DIMMs,
etc.), but that cache should be battery-backed for safety reasons.

> (c) full backups.

I'm curious what your logic is here too -- this one is debatable, so I'd
like to hear your view.

> I don't have enough ports to run RAID.  :-(  The downside is that
> FreeBSD doesn't have NCQ support yet (when? when? when?) so writes are
> slow.  :-(

NCQ will not necessarily improve write performance.  There have been
numerous studies done proving this fact, and I can point you to those as
well.  TCQ, on the other hand, does offer performance benefits when
there are a large number of simultaneous transactions occurring (think:
it's more like SCSI's command queueing).

I believe Andrey Elsukov is working on getting NCQ support working when
AHCI is in use (assuming I remember correctly).

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

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

Re: Testing - my emails don't seem to be getting through

[Chad Perrin]

On Wed, Oct 15, 2008 at 04:12:55AM -0700, Jeremy Chadwick wrote:
> On Wed, Oct 15, 2008 at 10:24:27AM +1000, Da Rock wrote:
> > I've been getting a lot of rejections: Helo command rejected: Host not
> > found (in reply to RCPT TO command). So now I'm running a test to see if
> > this one will get through.
> 
> I do not know why on earth you are testing this crap using a public
> mailing list, rather than mailing an account at Gmail or Hotmail
> or some such.  Sorry to sound sour about it, but it's rude.

Maybe he's testing it on a public mailing list because his Gmail or
Hotmail (or whatever) account doesn't reject his emails, but the public
mailing list does.  I think the correct response here would have been to
direct him to the freebsd-test mailing list:

  http://lists.freebsd.org/mailman/listinfo/freebsd-test

-- 
Chad Perrin [ content licensed PDL: http://pdl.apotheon.org ]
A: It reverses the normal flow of conversation. Q: What's wrong with
top-posting?


pgpMiJHFea9G5.pgp
Description: PGP signature

new install sunfire v100

[Davenport, Steve M]

I'm installing 7.0-RELEASE on a Sun Sunfire v100 server. I was able to
boot the cd, and install through cd one. There is no framebuffer on the
v100 (vt100 serial console interface only) so the install would not
proceed past the first disk. I want to use this system as a nameserver
and was able to download Bind 9.3.5-P2, compile, and run. My questions
are:
 
1) Can I manually complete the install process for items on CDs 2&3?
 
2) In the /var/log/messages I see:
 
Oct  9 19:50:53 steve3 kernel: acd0: CDRW  at ata3-slave
PIO4
Oct  9 19:50:53 steve3 kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR
asc=0x11 as
cq=0x00
Oct  9 19:50:53 steve3 kernel: GEOM_LABEL: Label for provider acd0 is
iso9660/Fr
eeBSD_Install.
Oct  9 19:50:53 steve3 kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR
asc=0x11 as
cq=0x00
 
What is causing these cd errors?
 
Thanks for your assistance!
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

[Fwd: Suhosin Segmentation Fault]

[Alain Wolf]

Not much return on freebsd-isp.
I try again here on freebsd-questions.

 Original-Nachricht 
Betreff: Suhosin Segmentation Fault
Datum: Mon, 13 Oct 2008 09:49:09 +0200
Von: Alain Wolf <[EMAIL PROTECTED]>
An: [EMAIL PROTECTED]
Newsgruppen: gmane.os.freebsd.isp

After upgrading FreeBSD from 6.3-p3 to 6.3-p5 on our server, all
websites just display a blank page and every HTTP request created a line
as follows in the logs:

child pid 80326 exit signal Segmentation fault (11)

This same problem happened on another server a few months ago after the
upgrade from 6.3-p3 to 6.3-p4, but after a rebuild of all FreeBSD ports
all went back to normal. However several rebuilds of all ports did not
solve the problem on this one.

To narrow down the problem: After disabling the PHP module in Apache the
problem disappears.

Re-enabling PHP, but disabling the Suhosin extension also works fine.

The trick found in this  forum, to load the Suhosin extension before all
other PHP extensions in /usr/local/etc/php/extensions.ini does not help.
In fact not loading any extension at all except Suhosin creates the
segfault errors.

Commenting out our Suhosin settings in php.ini to load it with default
values did not help.

FreeBSD 6.3-RELEASE-p5
Apache 2.2.9 (DAV/2 mod_python/3.3.1 Python/2.5.2 SVN/1.5.2)
PHP Version 5.2.6
Suhosin Patch 0.9.6.2
Suhosin PHP extension 0.9.27

All installed from the ports.

PHP (cli) seems to run fine at all times when called from the command-line.

Any suggestions?

Thanks

Alain Wolf, Zurich, Switzerland
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: RAID 5 - serious problem

[Dieter]

> FreeBSD 7.0-Release
> Intel D975XBX2 motherboard (Intel Matrix Storage Technology)
> 3 WD Raptor 74 GB in a RAID 5 array
> 1 WD Raptor 150 GB as a standalone disk
> / and /var mounted on the standalone,, /usr on the RAID 5
> I believe what happened was that one of the disks didn't respond for such a
> long time, that is was marked "bad". And afterwards the same thing happened
> for the other disks. When I try to boot the system, all three disks are
> marked "Offline".

> I am very desperate not to lose my data,

In that case, step one is to use dd(1) to make a bit-for-bit copy of the
three drives to some trusted media.  Since they are marked bad/offline,
you might need to move them to a controller that doesn't know anything
about RAID.  (Note that there is risk here, and in almost anything you do
at this point.)  Once you have this bit-for-bit backup, you can run any
experiment you like to attempt to recover your data.  If the experiment
goes bad, you can dd the exact original contents back using dd, then
try a different experiment.  While you're at it, make a normal backup
using dump(8) or whatever you normally use, of / and /var.  Once you have
*everything* backed up, you can do risky experiments like booting linux.

My personal approach to avoiding data loss is (a) avoid buggy things like
inthell and linux. (b) FFS with softdeps and the disk write cache turned off,
(c) full backups.  I don't have enough ports to run RAID.  :-(  The downside
is that FreeBSD doesn't have NCQ support yet (when? when? when?) so writes
are slow.  :-(
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Under heavy load internet gets killed, only a reboot can bring it back up

[Aniruddha]

On Wed, 2008-10-15 at 07:43 -0700, Jeremy Chadwick wrote:
> Now you need to rebuild the kernel and install the kernel.  In this
> scenario, when building the kernel DO NOT use any "-j" flags, as if the
> driver doesn't build, you'll be scrolling back through pages of data to
> try and find out why.
> 
> If the build doesn't occur successfully, paste the errors you get
> here and one of us can try to figure out why.
> 
> Otherwise, installkernel and reboot.  You should not need to build world
> for this.

Thanks for the extensive description. Unfortunately I got the following
error:


> 
> param inline-unit-growth=100 --param large-function-growth=1000  
> -mno-align-long
> -strings -mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow -mno-sse -mno-sse2 
> -m
> no-sse3 -ffreestanding
> /usr/src/sys/dev/msk/if_msk.c:241:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:244:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:245:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:246:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:247:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:248:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:249:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:250:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:251:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:252:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:253:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:254:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:255:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:256:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:258:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:259:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:260:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:261:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:262:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:263:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:264:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:265:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:267:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:268:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:269:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:270:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:271:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:273:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:274:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:275:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:276:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:278:10: error: #include expects "FILENAME" or 
>  ENAME>
> /usr/src/sys/dev/msk/if_msk.c:279:10: error: #include expects "FILENAME" or 
>
> ENAME>
> /usr/src/sys/dev/msk/if_msk.c:280:10: error: #include expects "FILENAME" or 
>
> ENAME>
> /usr/src/sys/dev/msk/if_msk.c:282:10: error: #include expects "FILENAME" or 
>
> ENAME>
> /usr/src/sys/dev/msk/if_msk.c:283:10: error: #include expects "FILENAME" or 
>
> ENAME>
> /usr/src/sys/dev/msk/if_msk.c:285:10: error: #include expects "FILENAME" or 
>
> ENAME>
> /usr/src/sys/dev/msk/if_msk.c:292:10: error: #include expects "FILENAME" or 
>
> ENAME>
> mkdep: compile failed
> *** Error code 1
> 
> Stop in /usr/obj/usr/src/sys/MYKERNEL.
> *** Error code 1
> 
> Stop in /usr/src.
> *** Error code 1
> 
> Stop in /usr/src.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-qu

Re: RAID 5 - serious problem

[Nejc Skoberne]

Hello,

> the drives to the other machine and try to make them online again. Do you
> think I should try?

If I were you, I would first buy/get a XXX GB SATA drive, create a filesystem 
there
and copy all three disks block-by-block as three separate files (which will be
the size of the disks). This way you'll still have the backup of your screwed up
drives somewhere in case something goes even more wrong.

However, I don't think your data is *physically* lost. I am almost sure that it
is still on that drives, only the metadata could be fscked up. Now how to get 
the
data back is another thing. In worst case scenario you could analyze the
specification of the metadata format for you controller and then write a C 
program
which would somehow put the bits together again using syscalls.

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

Re: FreeBSD 7 and ESXi (SOLVED)

[scuba]

All,

It's working with FBSD amd64 now.
I had to enable the "Virtualization Technology" on the PowerEdge 
BIOS.
Although I understand that this option could enhance some 
virtualization features, it's not clear that I HAVE to enable it to run 
64bits OSs.

Thank you all,

- Marcelo

On Tue, 14 Oct 2008, Steve Polyack wrote:

|[EMAIL PROTECTED] wrote:
|> Jeremy,
|> 
|> On Mon, 13 Oct 2008, Jeremy Chadwick wrote:
|> 
|> |On Tue, Oct 14, 2008 at 02:44:13AM -0300, [EMAIL PROTECTED] wrote:
|> |> On Mon, 13 Oct 2008, Jeremy Chadwick wrote:
|> |> |> |On Tue, Oct 14, 2008 at 02:04:07AM -0300, [EMAIL PROTECTED] wrote:
|> |> |> Jeremy,
|> |> |> |> |> On Mon, 13 Oct 2008, Jeremy Chadwick wrote:
|> |> |> |> |> |On Tue, Oct 14, 2008 at 12:54:26AM -0300, [EMAIL PROTECTED]
|> wrote:
|> |> |> |> I'm facing some problems trying to install a FreeBSD |> |> |>
|> 7.0-RELEASE-amd64, on a Dell PE 2950III, dual Xeon Quad core, 8GB RAM.
|> |> |> |> After (FBSD) boot menu count down, it shows a dump of the CPU
|> |> |> |> registers and a message: BTX Halted. No matter what is changed in VM
|> |> |> |> setup.
|> |> |> |
|> |> |> |Can you please download the 7.1-BETA2 ISO and try it instead?  There
|> |> |> |have been changes to the FreeBSD boot loader between 7.0-RELEASE and
|> |> |> |7.1-BETA2 which may improve things for you.  The 7.1-BETA2 ISOs are
|> |> |> |available here:
|> |> |> |> |>  The same behavior with 7.1-BETA2.
|> |> |
|> |> |I'm not sure what to do at this point, or what to tell you, since the
|> |> |kernel can't even load.
|> |> |
|> |> |Are you installing this off of CD, and is the CD drive hooked up to
|> |> |the PC via ATA/SATA (rather than USB or something else)?
|> |> |>It's a bit more complicated, since, for some reason the Vmware
|> |> client is unable to boot the VM from CD on the host server. It's |>
|> booting an ISO image on the client machine.
|> |>   I already read something saying that it's a known issue of the |> ESXi.
|> |>   Without the virtulization layer, the amd64 CD boots without |> problems
|> in this machine. |
|> |Ah, so the truth comes out... :-)
|> |
|> |Have you brought this fact up with the VMware folks?  They're quite a
|> |nice bunch, I wouldn't be surprised if they provided a hotfix for you
|> |for this problem.
|> 
|>  This will be my next step.
|>  I sent here first, once it's a boot loader problem, specific to 64bits
|> version of Fbsd. I thought someone could faced the same and came with a howto
|> to workaround.
|> 
|> Thank you anyway. :-)
|> 
|> - Marcelo
|> 
|> ___
|>   
|Also, to eliminate any chance of this being hardware-related, I am also running
|this on a Dell PE2950 with a similar configuration.
|


- Marcelo

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

Re: Under heavy load internet gets killed, only a reboot can bring it back up

[Jeremy Chadwick]

On Wed, Oct 15, 2008 at 04:24:21PM +0200, Aniruddha wrote:
> On Wed, 2008-10-15 at 21:09 +0900, PYUN Yong-Hyeon wrote:
> > This controller is known to buggy one. See below.
> > 
> > [...]
> > 
> >  > > Trying to mount root from ufs:/dev/ad16s3a
> >  > > WARNING: / was not properly dismounted
> >  > > GEOM_LABEL: Label ext2fs/home removed.
> >  > > GEOM_LABEL: Label ext2fs/data removed.
> >  > > mskc0: Uncorrectable PCI Express error
> >  > > mskc0: Uncorrectable PCI Express error
> >  > 
> >  > Those errors at the end of your dmesg don't look good; could be the sign
> >  > of a NIC or motherboard that's going bad, or possibly a very strange
> >  > driver problem.
> > 
> > I guess the message above could be safely ignored.
> > 
> >  > 
> >  > Adding Yong-Hyeon PYUN to this thread, since he helps maintain the
> >  > msk(4) driver.  Yong-Hyeon, do you know of any conditions where heavy
> >  > network I/O could cause msk(4) to lock up or stop transmitting traffic,
> >  > or possibly hard-lock on ifconfig down/up?
> >  > 
> > 
> > I think workaround for the controller bug was committed to HEAD(SVN
> > r183346). To original poster, would you try latest if_msk.c from
> > HEAD?(Just copy if_msk.c/if_mskreg.h from HEAD to your box.)
> > 
> 
> You got to help me a little bit here. How do I achieve this? Btw I am
> running FreeBSD 7.1 BETA. Doesn't that mean the fix is already applied?

FreeBSD 7.1-BETA == RELENG_7 in CVS tag terms.
FreeBSD 8.0 == CURRENT == HEAD in CVS tag terms.

You need to download the data at the below links and save the output
in files shown on the left:

   if_msk.c -- 
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/msk/if_msk.c?rev=1.34;content-type=text%2Fplain
if_mskreg.h -- 
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/msk/if_mskreg.h?rev=1.13;content-type=text%2Fplain

These are the msk(4) Ethernet driver in CURRENT.

*DO NOT* visit those web pages in a browser then copy/paste the output
into a file.  Use a tool like fetch(1) or wget(1) to do the work for you.
It's not hard.

Once you have those two files, you will need to replace your existing
driver code with the new files.  First make backups:

$ cd /usr/src/sys/dev/msk
$ cp -p if_msk.c if_msk.c.orig
$ cp -p if_mskreg.h if_mskreg.h.orig

Now replace the old code with the new:

$ cd /wherever/you/downloaded/the/files
$ mv if_msk.c /usr/src/sys/dev/msk
$ mv if_mskreg.h /usr/src/sys/dev/msk

Now you need to rebuild the kernel and install the kernel.  In this
scenario, when building the kernel DO NOT use any "-j" flags, as if the
driver doesn't build, you'll be scrolling back through pages of data to
try and find out why.

If the build doesn't occur successfully, paste the errors you get
here and one of us can try to figure out why.

Otherwise, installkernel and reboot.  You should not need to build world
for this.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

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

Re: Under heavy load internet gets killed, only a reboot can bring it back up

[Aniruddha]

On Wed, 2008-10-15 at 21:09 +0900, PYUN Yong-Hyeon wrote:
> This controller is known to buggy one. See below.
> 
> [...]
> 
>  > > Trying to mount root from ufs:/dev/ad16s3a
>  > > WARNING: / was not properly dismounted
>  > > GEOM_LABEL: Label ext2fs/home removed.
>  > > GEOM_LABEL: Label ext2fs/data removed.
>  > > mskc0: Uncorrectable PCI Express error
>  > > mskc0: Uncorrectable PCI Express error
>  > 
>  > Those errors at the end of your dmesg don't look good; could be the sign
>  > of a NIC or motherboard that's going bad, or possibly a very strange
>  > driver problem.
> 
> I guess the message above could be safely ignored.
> 
>  > 
>  > Adding Yong-Hyeon PYUN to this thread, since he helps maintain the
>  > msk(4) driver.  Yong-Hyeon, do you know of any conditions where heavy
>  > network I/O could cause msk(4) to lock up or stop transmitting traffic,
>  > or possibly hard-lock on ifconfig down/up?
>  > 
> 
> I think workaround for the controller bug was committed to HEAD(SVN
> r183346). To original poster, would you try latest if_msk.c from
> HEAD?(Just copy if_msk.c/if_mskreg.h from HEAD to your box.)
> 

You got to help me a little bit here. How do I achieve this? Btw I am
running FreeBSD 7.1 BETA. Doesn't that mean the fix is already applied?


-- 
Regards,

Aniruddha




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

Re: RAID 5 - serious problem

[Jeremy Chadwick]

On Wed, Oct 15, 2008 at 03:51:19PM +0200, Jon Theil Nielsen wrote:
> 2008/10/15 Jeremy Chadwick <[EMAIL PROTECTED]>
> 
> > On Wed, Oct 15, 2008 at 02:32:25PM +0200, Jon Theil Nielsen wrote:
> > > Dear list,
> > >
> > > Something happened that I don't think should be possible. I "lost" all
> > three
> > > disks in my RAID 5 array simultaneously after approx. two years without
> > any
> > > problem. And I fear I will never see my data again. But I really hope
> > some
> > > of you clever persons can give me some hints. My system is:
> > > FreeBSD 7.0-Release
> > > Intel D975XBX2 motherboard (Intel Matrix Storage Technology)
> >
> > Are you using the Matrix Storage Technology?  If so, immediately stop.
> > FreeBSD's support for this is very, very bad, and will nearly guarantee
> > data loss.  There are many of us who have tried it, and it's known to
> > be buggy on FreeBSD.
> >
> > http://wiki.freebsd.org/JeremyChadwick/ATA_issues_and_troubleshooting
> >
> > I recommend you stop using this feature and start using ZFS or gvinum
> > for what you need.
> >
> > > 3 WD Raptor 74 GB in a RAID 5 array
> > > 1 WD Raptor 150 GB as a standalone disk
> > > / and /var mounted on the standalone,, /usr on the RAID 5
> > > I believe what happened was that one of the disks didn't respond for such
> > a
> > > long time, that is was marked "bad". And afterwards the same thing
> > happened
> > > for the other disks. When I try to boot the system, all three disks are
> > > marked "Offline".
> > > The BIOS utility for the host controller has no option to force the disks
> > > back online.
> > > I have another machine with a S5000XVN board and Intel Embedded Server
> > RAID
> > > Technology II. The BIOS configuration utility on this board has the
> > option
> > > to force offline drives back online.
> >
> > Any "embedded" RAID is usually BIOS RAID managed by either a "software
> > RAID IC" (e.g. an IC on the motherboard that handles LBA/CHS addressing
> > for creating a pseudo-array, but the OS still does all of the management
> > and does not off-load anything).
> >
> > > I am very desperate not to lose my data, so I don't know if I dare moving
> > > the drives to the other machine and try to make them online again. Do you
> > > think I should try?
> >
> > No, but you might not have any choice.  It honestly sounds like the
> > metadata on your disks is in a bad state.
> >
> > I would recommend you try booting Linux, since their support for
> > MatrixRAID is significantly better/more advanced.  Ideally, you should
> > be able to bring the RAID members back online using their tools, then
> > reboot into FreeBSD and cross your fingers that your data becomes
> > accessible.  Once accessible, offload it somewhere immediately, and
> > follow my above recommendations.
> >
> > > In general, are there any procedures I can try to recover my RAID array?
> > Or
> > > is the offline status definitive ? and all data definitely lost? I guess
> > > some specialized companies have the expertise to recover lost data from a
> > > broken RAID array, but I don't know. And I don't know the price of such a
> > > service.
> > > I would really, really appreciate any kind of help.
> > > I have backups of most user data, but not of the system configuration
> > (and
> > > maybe even not the databases).  This is of course pretty stupid. In the
> > > future, I will not rely on RAID 5 as a foolproof solution?
> >
> > RAID 5 is a fine solution, but you have learned a very valuable lesson,
> > one which I will enclose in asterisks to make it crystal clear: ***RAID
> > DOES NOT REPLACE BACKUPS***.  Repeat this mantra over and over until you
> > accept it.  :-)
> >
> > --
> > | Jeremy Chadwickjdc at parodius.com |
> > | Parodius Networking   http://www.parodius.com/ |
> > | UNIX Systems Administrator  Mountain View, CA, USA |
> > | Making life hard for others since 1977.  PGP: 4BD6C0CB |
> >
> > Hi Jeremy,
> 
> Thanks for your advice. As I understand you, the best bet is to boot from
> Linux and try to repair.

> And that trying with my other controller might be the second best.

You risk corrupting or losing the metadata using another controller.
The two controllers are *not* identical; just because they're Intel
doesn't mean they speak the same metadata format.  :-)

> Would it be an idea to try to run som sort of Linux live cd?  I have
> no machines with Linux installed.

Yes, absolutely.  I assume any Linux distribution which uses libata
should be able to speak to Intel MatrixRAID disks and BIOSes.  Linux
refers to this feature as "Intel SATA RAID" or "Intel Software RAID",
Any present-day 2.6.x kernel uses libata; the newer the better.

I do not know how to manipulate or interface with MatrixRAID on Linux.
You will have to Google for how to get support in that regard.  My
quick searches turn up the following useful links:

http://linux-ata.org/faq-sata-raid.html
http://gentoo-wiki

Re: RAID 5 - serious problem

[Jon Theil Nielsen]

2008/10/15 Jeremy Chadwick <[EMAIL PROTECTED]>

> On Wed, Oct 15, 2008 at 02:32:25PM +0200, Jon Theil Nielsen wrote:
> > Dear list,
> >
> > Something happened that I don't think should be possible. I "lost" all
> three
> > disks in my RAID 5 array simultaneously after approx. two years without
> any
> > problem. And I fear I will never see my data again. But I really hope
> some
> > of you clever persons can give me some hints. My system is:
> > FreeBSD 7.0-Release
> > Intel D975XBX2 motherboard (Intel Matrix Storage Technology)
>
> Are you using the Matrix Storage Technology?  If so, immediately stop.
> FreeBSD's support for this is very, very bad, and will nearly guarantee
> data loss.  There are many of us who have tried it, and it's known to
> be buggy on FreeBSD.
>
> http://wiki.freebsd.org/JeremyChadwick/ATA_issues_and_troubleshooting
>
> I recommend you stop using this feature and start using ZFS or gvinum
> for what you need.
>
> > 3 WD Raptor 74 GB in a RAID 5 array
> > 1 WD Raptor 150 GB as a standalone disk
> > / and /var mounted on the standalone,, /usr on the RAID 5
> > I believe what happened was that one of the disks didn't respond for such
> a
> > long time, that is was marked "bad". And afterwards the same thing
> happened
> > for the other disks. When I try to boot the system, all three disks are
> > marked "Offline".
> > The BIOS utility for the host controller has no option to force the disks
> > back online.
> > I have another machine with a S5000XVN board and Intel Embedded Server
> RAID
> > Technology II. The BIOS configuration utility on this board has the
> option
> > to force offline drives back online.
>
> Any "embedded" RAID is usually BIOS RAID managed by either a "software
> RAID IC" (e.g. an IC on the motherboard that handles LBA/CHS addressing
> for creating a pseudo-array, but the OS still does all of the management
> and does not off-load anything).
>
> > I am very desperate not to lose my data, so I don't know if I dare moving
> > the drives to the other machine and try to make them online again. Do you
> > think I should try?
>
> No, but you might not have any choice.  It honestly sounds like the
> metadata on your disks is in a bad state.
>
> I would recommend you try booting Linux, since their support for
> MatrixRAID is significantly better/more advanced.  Ideally, you should
> be able to bring the RAID members back online using their tools, then
> reboot into FreeBSD and cross your fingers that your data becomes
> accessible.  Once accessible, offload it somewhere immediately, and
> follow my above recommendations.
>
> > In general, are there any procedures I can try to recover my RAID array?
> Or
> > is the offline status definitive ? and all data definitely lost? I guess
> > some specialized companies have the expertise to recover lost data from a
> > broken RAID array, but I don't know. And I don't know the price of such a
> > service.
> > I would really, really appreciate any kind of help.
> > I have backups of most user data, but not of the system configuration
> (and
> > maybe even not the databases).  This is of course pretty stupid. In the
> > future, I will not rely on RAID 5 as a foolproof solution?
>
> RAID 5 is a fine solution, but you have learned a very valuable lesson,
> one which I will enclose in asterisks to make it crystal clear: ***RAID
> DOES NOT REPLACE BACKUPS***.  Repeat this mantra over and over until you
> accept it.  :-)
>
> --
> | Jeremy Chadwickjdc at parodius.com |
> | Parodius Networking   http://www.parodius.com/ |
> | UNIX Systems Administrator  Mountain View, CA, USA |
> | Making life hard for others since 1977.  PGP: 4BD6C0CB |
>
> Hi Jeremy,

Thanks for your advice. As I understand you, the best bet is to boot from
Linux and try to repair. And that trying with my other controller might be
the second best. Would it be an idea to try to run som sort of Linux live
cd? I have no machines with Linux installed.

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

Re: How to get my Dad's Win2k system to access internet through my FreeBSD 6.2 system

[Mike M]

On 10/14/2008 at 12:03 PM [EMAIL PROTECTED] wrote:

|Manish Jain <[EMAIL PROTECTED]> writes:
|
|> I am poor at networking and need a little bit of help. My dad has a
|> Windows 2000 machine with a network card but does not have a connection
|> to the internet.
|
|When I started writing this, I thought that system had been abandoned
|already, but it appears Microsoft will offer a measure of support
|through next year sometime.  Do see that the system gets properly
|updated before you put it on the net.
 =


Important advice.

I also run Windows 2000 on my home PCs (the ones that are still in the Windows 
world).Security updates are still being offered by Microsoft (through next 
June, I believe).

It is important to bring your Dad's install of Windows 2000 up to the current 
patch level.  A visit to Windows Update will do the trick for the Windows 
software.   Other things (e.g., Adobe's Flash, Acrobat reader, etc.) may also 
need a version refresh to be safe for the 'Net.





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

Re: RAID 5 - serious problem

[Jeremy Chadwick]

On Wed, Oct 15, 2008 at 02:32:25PM +0200, Jon Theil Nielsen wrote:
> Dear list,
> 
> Something happened that I don't think should be possible. I "lost" all three
> disks in my RAID 5 array simultaneously after approx. two years without any
> problem. And I fear I will never see my data again. But I really hope some
> of you clever persons can give me some hints. My system is:
> FreeBSD 7.0-Release
> Intel D975XBX2 motherboard (Intel Matrix Storage Technology)

Are you using the Matrix Storage Technology?  If so, immediately stop.
FreeBSD's support for this is very, very bad, and will nearly guarantee
data loss.  There are many of us who have tried it, and it's known to
be buggy on FreeBSD.

http://wiki.freebsd.org/JeremyChadwick/ATA_issues_and_troubleshooting

I recommend you stop using this feature and start using ZFS or gvinum
for what you need.

> 3 WD Raptor 74 GB in a RAID 5 array
> 1 WD Raptor 150 GB as a standalone disk
> / and /var mounted on the standalone,, /usr on the RAID 5
> I believe what happened was that one of the disks didn't respond for such a
> long time, that is was marked "bad". And afterwards the same thing happened
> for the other disks. When I try to boot the system, all three disks are
> marked "Offline".
> The BIOS utility for the host controller has no option to force the disks
> back online.
> I have another machine with a S5000XVN board and Intel Embedded Server RAID
> Technology II. The BIOS configuration utility on this board has the option
> to force offline drives back online.

Any "embedded" RAID is usually BIOS RAID managed by either a "software
RAID IC" (e.g. an IC on the motherboard that handles LBA/CHS addressing
for creating a pseudo-array, but the OS still does all of the management
and does not off-load anything).

> I am very desperate not to lose my data, so I don't know if I dare moving
> the drives to the other machine and try to make them online again. Do you
> think I should try?

No, but you might not have any choice.  It honestly sounds like the
metadata on your disks is in a bad state.

I would recommend you try booting Linux, since their support for
MatrixRAID is significantly better/more advanced.  Ideally, you should
be able to bring the RAID members back online using their tools, then
reboot into FreeBSD and cross your fingers that your data becomes
accessible.  Once accessible, offload it somewhere immediately, and
follow my above recommendations.

> In general, are there any procedures I can try to recover my RAID array? Or
> is the offline status definitive ? and all data definitely lost? I guess
> some specialized companies have the expertise to recover lost data from a
> broken RAID array, but I don't know. And I don't know the price of such a
> service.
> I would really, really appreciate any kind of help.
> I have backups of most user data, but not of the system configuration (and
> maybe even not the databases).  This is of course pretty stupid. In the
> future, I will not rely on RAID 5 as a foolproof solution?

RAID 5 is a fine solution, but you have learned a very valuable lesson,
one which I will enclose in asterisks to make it crystal clear: ***RAID
DOES NOT REPLACE BACKUPS***.  Repeat this mantra over and over until you
accept it.  :-)

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

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

RAID 5 - serious problem

[Jon Theil Nielsen]

Dear list,

Something happened that I don't think should be possible. I "lost" all three
disks in my RAID 5 array simultaneously after approx. two years without any
problem. And I fear I will never see my data again. But I really hope some
of you clever persons can give me some hints. My system is:
FreeBSD 7.0-Release
Intel D975XBX2 motherboard (Intel Matrix Storage Technology)
3 WD Raptor 74 GB in a RAID 5 array
1 WD Raptor 150 GB as a standalone disk
/ and /var mounted on the standalone,, /usr on the RAID 5
I believe what happened was that one of the disks didn't respond for such a
long time, that is was marked "bad". And afterwards the same thing happened
for the other disks. When I try to boot the system, all three disks are
marked "Offline".
The BIOS utility for the host controller has no option to force the disks
back online.
I have another machine with a S5000XVN board and Intel Embedded Server RAID
Technology II. The BIOS configuration utility on this board has the option
to force offline drives back online.
I am very desperate not to lose my data, so I don't know if I dare moving
the drives to the other machine and try to make them online again. Do you
think I should try?
In general, are there any procedures I can try to recover my RAID array? Or
is the offline status definitive – and all data definitely lost? I guess
some specialized companies have the expertise to recover lost data from a
broken RAID array, but I don't know. And I don't know the price of such a
service.
I would really, really appreciate any kind of help.
I have backups of most user data, but not of the system configuration (and
maybe even not the databases).  This is of course pretty stupid. In the
future, I will not rely on RAID 5 as a foolproof solution…

Regards,
Jon
-- 
*Jon Theil Nielsen*
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Binding SCTP sockets to the IPv6 lopback address

[Bruce Cran]

I've been writing some basic SCTP socket code and have found that SCTP 
doesn't bind to the loopback IPv6 address - it binds to all the other 
addresses, including the external IPv6, link-local and IPv4 loopback 
addresses.  Is there something about the way SCTP works that means it 
doesn't work over IPv6 loopback?


The code I'm running calls getaddrinfo with the hints to set AF_UNSPEC, 
SOCK_STREAM, AI_PASSIVE and then it calls bind with the protocol set to 
IPPROTO_SCTP.


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

Re: Under heavy load internet gets killed, only a reboot can bring it back up

[Jeremy Chadwick]

On Wed, Oct 15, 2008 at 09:09:11PM +0900, PYUN Yong-Hyeon wrote:
> On Wed, Oct 15, 2008 at 04:31:01AM -0700, Jeremy Chadwick wrote:
>  > On Wed, Oct 15, 2008 at 01:17:58PM +0200, Aniruddha wrote:
>  > > On Wed, 2008-10-15 at 00:26 -0700, Jeremy Chadwick wrote:
>  > > > On Wed, Oct 15, 2008 at 09:13:00AM +0200, Aniruddha wrote:
>  > > > > Each time  my internet connection is under heavy lead it gets killed
>  > > > > after a minute of 10. I tried the following commands to get the 
> internet
>  > > > > back up, but nothing helped:
>  > > > > 
>  > > > > /etc/rc.d/netif restart
>  > > > > ifconfig mynic down
>  > > > > ifconfig mynic up
>  > > > > 
>  > > > > Even worse the last time I issued a '/etc/rc.d/netif restart' my 
> whole
>  > > > > system hardlocked (wasn't responding to capslock presses). So far the
>  > > > > only solution has been te reboot the computer. Is there any way I can
>  > > > > prevent my internet connection from getting killed? How do I get it 
> back
>  > > > > up after it has been killed? Thanks in advance!
>  > > > 
>  > > > What network card are you using?  Can you provide output from the
>  > > > following commands?
>  > > > 
>  > > > dmesg
>  > > > vmstat -i
>  > > > netstat -in
>  > > > 
>  > > I have a Marvell Yukon onboard nic.
>  > > 
>  > > 
>  > > Here's the output:
>  > > 
>  > > netstat -in
>  > > 
>  > > NameMtu Network   Address  Ipkts IerrsOpkts
>  > > Oerrs  Coll
>  > > msk0   1500  29 0   25 0 0
>  > > msk0   1500 :0 -5 - -
>  > > msk0   1500 192.168.2.0/2 192.168.2.111  16 -   14 -
>  > > -
>  > > fwe0*  1500   0 00 0 0
>  > > fwip0  1500   0 00 0 0
>  > > lo0   163840 00
>  > > 0 0
>  > > lo0   16384 ::1/128   ::1  0 -0
>  > > - -
>  > > lo0   16384 ::1/64 0 -0 - -
>  > > lo0   16384 127.0.0.0/8   127.0.0.10 -0
>  > > - -
>  > 
>  > This looks okay.  I see no interface errors, which is good.
>  > 
>  > > vmstat -i
>  > > interrupt  total   rate
>  > > irq17: atapci0+   13  0
>  > > irq18: atapci1+ 1045  5
>  > > irq20: uhci0 ehci0 13462 69
>  > > irq21: fwohci0 3  0
>  > > irq23: atapci3102718529
>  > > cpu0: timer   386229   1990
>  > > irq256: mskc0 46  0
>  > > cpu1: timer   376453   1940
>  > > Total 879969   4535
>  > 
>  > msk(4) appears to be using MSI/MSI-X here.
>  > 
>  > One thing worth trying would be to disable MSI/MSI-X.  You can disable
>  > these by adding the following to your /boot/loader.conf :
>  > 
>  > hw.pci.enable_msix="0"
>  > hw.pci.enable_msi="0"
> 
> The command above will disable all MSI/MSIX capability of box.
> If the intention is to disable MSI feature of Marvell network
> controller add "hw.msk.msi_disable="1" to /boot/loader.conf.
> But I don't think you need to disable MSI capability unless you
> have buggy PCI bridges. Without MSI msk(4) would normally share 
> interrupts with other devices(e.g. USB).

Based on your below conclusion (about this particular Marvell NIC and/or
PHY being buggy), I don't think disabling MSI/MSI-X will do any good.

>  > > mskc0:  port 0xb800-0xb8ff mem 
> 0xff8fc000-0xff8f irq 19 at device 0.0 on pci3
>  > > msk0:  on mskc0
>  > > msk0: Ethernet address: 00:1e:8c:5a:62:da
>  > > miibus0:  on msk0
>  > > e1000phy0:  PHY 0 on miibus0
>  > > e1000phy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 
> 1000baseTX-FDX, auto
>  > > mskc0: [FILTER]
> 
> This controller is known to buggy one. See below.
> 
>  > Adding Yong-Hyeon PYUN to this thread, since he helps maintain the
>  > msk(4) driver.  Yong-Hyeon, do you know of any conditions where heavy
>  > network I/O could cause msk(4) to lock up or stop transmitting traffic,
>  > or possibly hard-lock on ifconfig down/up?
>  > 
> 
> I think workaround for the controller bug was committed to HEAD(SVN
> r183346). To original poster, would you try latest if_msk.c from
> HEAD?(Just copy if_msk.c/if_mskreg.h from HEAD to your box.)

As usual, thanks much for the explanation.  :-)

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

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

Re: Under heavy load internet gets killed, only a reboot can bring it back up

[PYUN Yong-Hyeon]

On Wed, Oct 15, 2008 at 04:31:01AM -0700, Jeremy Chadwick wrote:
 > On Wed, Oct 15, 2008 at 01:17:58PM +0200, Aniruddha wrote:
 > > On Wed, 2008-10-15 at 00:26 -0700, Jeremy Chadwick wrote:
 > > > On Wed, Oct 15, 2008 at 09:13:00AM +0200, Aniruddha wrote:
 > > > > Each time  my internet connection is under heavy lead it gets killed
 > > > > after a minute of 10. I tried the following commands to get the 
 > > > > internet
 > > > > back up, but nothing helped:
 > > > > 
 > > > > /etc/rc.d/netif restart
 > > > > ifconfig mynic down
 > > > > ifconfig mynic up
 > > > > 
 > > > > Even worse the last time I issued a '/etc/rc.d/netif restart' my whole
 > > > > system hardlocked (wasn't responding to capslock presses). So far the
 > > > > only solution has been te reboot the computer. Is there any way I can
 > > > > prevent my internet connection from getting killed? How do I get it 
 > > > > back
 > > > > up after it has been killed? Thanks in advance!
 > > > 
 > > > What network card are you using?  Can you provide output from the
 > > > following commands?
 > > > 
 > > > dmesg
 > > > vmstat -i
 > > > netstat -in
 > > > 
 > > I have a Marvell Yukon onboard nic.
 > > 
 > > 
 > > Here's the output:
 > > 
 > > netstat -in
 > > 
 > > NameMtu Network   Address  Ipkts IerrsOpkts
 > > Oerrs  Coll
 > > msk0   1500  29 0   25 0 0
 > > msk0   1500 :0 -5 - -
 > > msk0   1500 192.168.2.0/2 192.168.2.111  16 -   14 -
 > > -
 > > fwe0*  1500   0 00 0 0
 > > fwip0  1500   0 00 0 0
 > > lo0   163840 00
 > > 0 0
 > > lo0   16384 ::1/128   ::1  0 -0
 > > - -
 > > lo0   16384 ::1/64 0 -0 - -
 > > lo0   16384 127.0.0.0/8   127.0.0.10 -0
 > > - -
 > 
 > This looks okay.  I see no interface errors, which is good.
 > 
 > > vmstat -i
 > > interrupt  total   rate
 > > irq17: atapci0+   13  0
 > > irq18: atapci1+ 1045  5
 > > irq20: uhci0 ehci0 13462 69
 > > irq21: fwohci0 3  0
 > > irq23: atapci3102718529
 > > cpu0: timer   386229   1990
 > > irq256: mskc0 46  0
 > > cpu1: timer   376453   1940
 > > Total 879969   4535
 > 
 > msk(4) appears to be using MSI/MSI-X here.
 > 
 > One thing worth trying would be to disable MSI/MSI-X.  You can disable
 > these by adding the following to your /boot/loader.conf :
 > 
 > hw.pci.enable_msix="0"
 > hw.pci.enable_msi="0"

The command above will disable all MSI/MSIX capability of box.
If the intention is to disable MSI feature of Marvell network
controller add "hw.msk.msi_disable="1" to /boot/loader.conf.
But I don't think you need to disable MSI capability unless you
have buggy PCI bridges. Without MSI msk(4) would normally share 
interrupts with other devices(e.g. USB).

 > 
 > > Copyright (c) 1992-2008 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 7.1-BETA #0: Sun Sep  7 13:49:18 UTC 2008
 > > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
 > > Timecounter "i8254" frequency 1193182 Hz quality 0
 > > CPU: Intel(R) Core(TM)2 Duo CPU E8400  @ 3.00GHz (3001.18-MHz 
 > > 686-class CPU)

[...]

 > > mskc0:  port 0xb800-0xb8ff mem 
 > > 0xff8fc000-0xff8f irq 19 at device 0.0 on pci3
 > > msk0:  on mskc0
 > > msk0: Ethernet address: 00:1e:8c:5a:62:da
 > > miibus0:  on msk0
 > > e1000phy0:  PHY 0 on miibus0
 > > e1000phy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 
 > > 1000baseTX-FDX, auto
 > > mskc0: [FILTER]

This controller is known to buggy one. See below.

[...]

 > > Trying to mount root from ufs:/dev/ad16s3a
 > > WARNING: / was not properly dismounted
 > > GEOM_LABEL: Label ext2fs/home removed.
 > > GEOM_LABEL: Label ext2fs/data removed.
 > > mskc0: Uncorrectable PCI Express error
 > > mskc0: Uncorrectable PCI Express error
 > 
 > Those errors at the end of your dmesg don't look good; could be the sign
 > of a NIC or motherboard that's going bad, or possibly a very strange
 > driver problem.

I guess the message above could be safely ignored.

 > 
 > Adding Yong-Hyeon PYUN to this thread, since he helps maintain the
 > msk(4) driver.  Yong-Hyeon, do you know of any conditions where heavy
 > network I/O could cause msk(4) to lock up or stop transmitting traffic,
 > or possibly hard-lock on ifconfig down/up?
 > 

I think workaround for the controller bug was committed to HEAD(SVN
r183346). T

locore.s: suffix or operands invalid for mov

[Unga]

Hi all

I get an error when compiling the RELENG_7 kernel on i386.

cc -c -x assembler-with-cpp -DLOCORE -O -pipe  -std=c99 -g -Wall 
-Wredundant-decls -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes 
-Wpointer-arith -Winline -Wcast-qual  -Wundef -Wno-pointer-sign 
-fformat-extensions -nostdinc  -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq 
-D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common 
-finline-limit=8000 --param inline-unit-growth=100 --param 
large-function-growth=1000  -mno-align-long-strings 
-mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 
-ffreestanding -Werror /usr/src/sys/i386/i386/locore.s
/usr/src/sys/i386/i386/locore.s: Assembler messages:
/usr/src/sys/i386/i386/locore.s:341: Error: suffix or operands invalid for `mov'
/usr/src/sys/i386/i386/locore.s:358: Error: suffix or operands invalid for `mov'
*** Error code 1

Btw, I'm using a gcc 4.2.1 patched by myself. This error doesn't happen using 
the gcc ship with FreeBSD.

What could be the cause of this error? 

Appreciate your reply in this regard.

Kind regards
Unga



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

Re: Under heavy load internet gets killed, only a reboot can bring it back up

[Aniruddha]

On Wed, 2008-10-15 at 00:26 -0700, Jeremy Chadwick wrote:
> On Wed, Oct 15, 2008 at 09:13:00AM +0200, Aniruddha wrote:
> > Each time  my internet connection is under heavy lead it gets killed
> > after a minute of 10. I tried the following commands to get the internet
> > back up, but nothing helped:
> > 
> > /etc/rc.d/netif restart
> > ifconfig mynic down
> > ifconfig mynic up
> > 
> > Even worse the last time I issued a '/etc/rc.d/netif restart' my whole
> > system hardlocked (wasn't responding to capslock presses). So far the
> > only solution has been te reboot the computer. Is there any way I can
> > prevent my internet connection from getting killed? How do I get it back
> > up after it has been killed? Thanks in advance!
> 
> What network card are you using?  Can you provide output from the
> following commands?
> 
> dmesg
> vmstat -i
> netstat -in
> 
I have a Marvell Yukon onboard nic.


Here's the output:

netstat -in

NameMtu Network   Address  Ipkts IerrsOpkts
Oerrs  Coll
msk0   1500  29 0   25 0 0
msk0   1500 :0 -5 - -
msk0   1500 192.168.2.0/2 192.168.2.111  16 -   14 -
-
fwe0*  1500   0 00 0 0
fwip0  1500   0 00 0 0
lo0   163840 00
0 0
lo0   16384 ::1/128   ::1  0 -0
- -
lo0   16384 ::1/64 0 -0 - -
lo0   16384 127.0.0.0/8   127.0.0.10 -0
- -

vmstat -i
interrupt  total   rate
irq17: atapci0+   13  0
irq18: atapci1+ 1045  5
irq20: uhci0 ehci0 13462 69
irq21: fwohci0 3  0
irq23: atapci3102718529
cpu0: timer   386229   1990
irq256: mskc0 46  0
cpu1: timer   376453   1940
Total 879969   4535
Copyright (c) 1992-2008 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 7.1-BETA #0: Sun Sep  7 13:49:18 UTC 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Core(TM)2 Duo CPU E8400  @ 3.00GHz (3001.18-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x10676  Stepping = 6
  
Features=0xbfebfbff
  
Features2=0x8e3fd>
  AMD Features=0x2000
  AMD Features2=0x1
  Cores per package: 2
real memory  = 3220701184 (3071 MB)
avail memory = 3146145792 (3000 MB)
ACPI APIC Table: 
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
ioapic0  irqs 0-23 on motherboard
kbd1 at kbdmux0
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
acpi0:  on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: reservation of 0, a (3) failed
acpi0: reservation of 10, bff0 (3) failed
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
pcib0:  port 0xcf8-0xcff on acpi0
pci0:  on pcib0
pcib1:  irq 16 at device 1.0 on pci0
pci5:  on pcib1
vgapci0:  port 0xc800-0xc8ff mem 
0xd000-0xdfff,0xff9f-0xff9f irq 16 at device 0.0 on pci5
pci5:  at device 0.1 (no driver attached)
pci0:  at device 27.0 (no driver attached)
pcib2:  irq 16 at device 28.0 on pci0
pci4:  on pcib2
pcib3:  irq 19 at device 28.3 on pci0
pci3:  on pcib3
mskc0:  port 0xb800-0xb8ff mem 
0xff8fc000-0xff8f irq 19 at device 0.0 on pci3
msk0:  on mskc0
msk0: Ethernet address: 00:1e:8c:5a:62:da
miibus0:  on msk0
e1000phy0:  PHY 0 on miibus0
e1000phy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto
mskc0: [FILTER]
pcib4:  irq 17 at device 28.5 on pci0
pci2:  on pcib4
atapci0:  mem 0xff7fe000-0xff7f irq 17 at device 
0.0 on pci2
atapci0: [ITHREAD]
atapci0: AHCI Version 01.00 controller with 2 ports detected
ata2:  on atapci0
ata2: [ITHREAD]
ata3:  on atapci0
ata3: [ITHREAD]
atapci1:  port 
0xac00-0xac07,0xa880-0xa883,0xa800-0xa807,0xa480-0xa483,0xa400-0xa40f at device 
0.1 on pci2
atapci1: [ITHREAD]
ata4:  on atapci1
ata4: [ITHREAD]
uhci0:  port 0xe480-0xe49f irq 20 at device 29.0 
on pci0
uhci0: [GIANT-LOCKED]
uhci0: [ITHREAD]
usb0:  on uhci0
usb0: USB revision 1.0
uhub0:  on usb0
uhub0: 2 ports with 2 removable, self powered
uhci1:  port 0xe800-0xe81f irq 17 at device 29.1 
on pci0
uhci1: [GIANT-LOCKED]
uhci1: [ITHREAD]
usb1:  on uhci1
usb1: USB revision 1.0
uhub1:  on usb1
uhub1: 2 ports with 2 removable, self powered
uhci2:  port 0xe880-0xe89f irq 18 at device 29.2 
on pci0
uhci2: [GIANT-LOCKED]
uhci2: [ITHREAD]
usb2

Re: Under heavy load internet gets killed, only a reboot can bring it back up

[Jeremy Chadwick]

On Wed, Oct 15, 2008 at 01:40:45PM +0200, Wojciech Puchar wrote:
>>
>> One thing worth trying would be to disable MSI/MSI-X.  You can disable
>> these by adding the following to your /boot/loader.conf :
>>
>> hw.pci.enable_msix="0"
>> hw.pci.enable_msi="0"
>
> what's wrong in MSI interrupts?

Nothing -- but there are known compatibility problems with MSI/MSI-X on
some boards.  I remember reading about this with regards to em(4) not
too long ago.  It's worth ruling out, especially since his problem is
reproducible (if disabling MSI doesn't fix the problem, he can simply
remove those two loader.conf variables and we've ruled out one
possibility).

>>> mskc0: Uncorrectable PCI Express error
>>> mskc0: Uncorrectable PCI Express error
>>
>> Those errors at the end of your dmesg don't look good; could be the sign
>> of a NIC or motherboard that's going bad, or possibly a very strange
>> driver problem.
>
> or just connectors should be cleaner or card isn't fitted well - contact  
> problems.

I'm under the impression his NIC is on-board, not a physical PCI-E card.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

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

Re: Under heavy load internet gets killed, only a reboot can bring it back up

[Wojciech Puchar]

One thing worth trying would be to disable MSI/MSI-X.  You can disable
these by adding the following to your /boot/loader.conf :

hw.pci.enable_msix="0"
hw.pci.enable_msi="0"


what's wrong in MSI interrupts?


mskc0: Uncorrectable PCI Express error
mskc0: Uncorrectable PCI Express error


Those errors at the end of your dmesg don't look good; could be the sign
of a NIC or motherboard that's going bad, or possibly a very strange
driver problem.


or just connectors should be cleaner or card isn't fitted well - contact 
problems.

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

Re: Under heavy load internet gets killed, only a reboot can bring it back up

[Jeremy Chadwick]

On Wed, Oct 15, 2008 at 01:17:58PM +0200, Aniruddha wrote:
> On Wed, 2008-10-15 at 00:26 -0700, Jeremy Chadwick wrote:
> > On Wed, Oct 15, 2008 at 09:13:00AM +0200, Aniruddha wrote:
> > > Each time  my internet connection is under heavy lead it gets killed
> > > after a minute of 10. I tried the following commands to get the internet
> > > back up, but nothing helped:
> > > 
> > > /etc/rc.d/netif restart
> > > ifconfig mynic down
> > > ifconfig mynic up
> > > 
> > > Even worse the last time I issued a '/etc/rc.d/netif restart' my whole
> > > system hardlocked (wasn't responding to capslock presses). So far the
> > > only solution has been te reboot the computer. Is there any way I can
> > > prevent my internet connection from getting killed? How do I get it back
> > > up after it has been killed? Thanks in advance!
> > 
> > What network card are you using?  Can you provide output from the
> > following commands?
> > 
> > dmesg
> > vmstat -i
> > netstat -in
> > 
> I have a Marvell Yukon onboard nic.
> 
> 
> Here's the output:
> 
> netstat -in
> 
> NameMtu Network   Address  Ipkts IerrsOpkts
> Oerrs  Coll
> msk0   1500  29 0   25 0 0
> msk0   1500 :0 -5 - -
> msk0   1500 192.168.2.0/2 192.168.2.111  16 -   14 -
> -
> fwe0*  1500   0 00 0 0
> fwip0  1500   0 00 0 0
> lo0   163840 00
> 0 0
> lo0   16384 ::1/128   ::1  0 -0
> - -
> lo0   16384 ::1/64 0 -0 - -
> lo0   16384 127.0.0.0/8   127.0.0.10 -0
> - -

This looks okay.  I see no interface errors, which is good.

> vmstat -i
> interrupt  total   rate
> irq17: atapci0+   13  0
> irq18: atapci1+ 1045  5
> irq20: uhci0 ehci0 13462 69
> irq21: fwohci0 3  0
> irq23: atapci3102718529
> cpu0: timer   386229   1990
> irq256: mskc0 46  0
> cpu1: timer   376453   1940
> Total 879969   4535

msk(4) appears to be using MSI/MSI-X here.

One thing worth trying would be to disable MSI/MSI-X.  You can disable
these by adding the following to your /boot/loader.conf :

hw.pci.enable_msix="0"
hw.pci.enable_msi="0"

> Copyright (c) 1992-2008 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 7.1-BETA #0: Sun Sep  7 13:49:18 UTC 2008
> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
> Timecounter "i8254" frequency 1193182 Hz quality 0
> CPU: Intel(R) Core(TM)2 Duo CPU E8400  @ 3.00GHz (3001.18-MHz 686-class 
> CPU)
>   Origin = "GenuineIntel"  Id = 0x10676  Stepping = 6
>   
> Features=0xbfebfbff
>   
> Features2=0x8e3fd>
>   AMD Features=0x2000
>   AMD Features2=0x1
>   Cores per package: 2
> real memory  = 3220701184 (3071 MB)
> avail memory = 3146145792 (3000 MB)
> ACPI APIC Table: 
> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
>  cpu0 (BSP): APIC ID:  0
>  cpu1 (AP): APIC ID:  1
> ioapic0  irqs 0-23 on motherboard
> kbd1 at kbdmux0
> ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
> acpi0:  on motherboard
> acpi0: [ITHREAD]
> acpi0: Power Button (fixed)
> acpi0: reservation of 0, a (3) failed
> acpi0: reservation of 10, bff0 (3) failed
> Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
> acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
> pcib0:  port 0xcf8-0xcff on acpi0
> pci0:  on pcib0
> pcib1:  irq 16 at device 1.0 on pci0
> pci5:  on pcib1
> vgapci0:  port 0xc800-0xc8ff mem 
> 0xd000-0xdfff,0xff9f-0xff9f irq 16 at device 0.0 on pci5
> pci5:  at device 0.1 (no driver attached)
> pci0:  at device 27.0 (no driver attached)
> pcib2:  irq 16 at device 28.0 on pci0
> pci4:  on pcib2
> pcib3:  irq 19 at device 28.3 on pci0
> pci3:  on pcib3
> mskc0:  port 0xb800-0xb8ff mem 
> 0xff8fc000-0xff8f irq 19 at device 0.0 on pci3
> msk0:  on mskc0
> msk0: Ethernet address: 00:1e:8c:5a:62:da
> miibus0:  on msk0
> e1000phy0:  PHY 0 on miibus0
> e1000phy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, 
> auto
> mskc0: [FILTER]
> pcib4:  irq 17 at device 28.5 on pci0
> pci2:  on pcib4
> atapci0:  mem 0xff7fe000-0xff7f irq 17 at device 
> 0.0 on pci2
> atapci0: [ITHREAD]
> atapci0: AHCI Version 01.00 controller with 2 ports detected
> ata2:  on atapci0
> ata2: [ITHREAD]
> ata3:  on atapci0
> ata3: [ITHREAD]
> atapci1:  port 
> 0xac00-0xac07,0xa880-0xa883,0xa800-0xa807,0xa480-0xa483,0x

Re: Under heavy load internet gets killed, only a reboot can bring it back up

[Wojciech Puchar]

netstat -in


I have a Marvell Yukon onboard nic.


that's normal ;) but some NORMAL working NIC.

you may try to disable some features on that nic too
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: freebsd7 & kde4 & performance

[Jeff Laine]

Agreed with t-u-t. I tried new pc-bsd7 on my old laptop (Celeron
1,6GHz/1.5G RAM/15GB dedicated on HDD/Intel GME video) and it runs
rather good (with almost all desctop effects disabled). Not so blazing
fast of course, but still enough for doing everyday stuff.

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

Re: Compiling curl 7.19

[Jeremy Chadwick]

On Wed, Oct 15, 2008 at 12:39:25PM +0200, Artifex Maximus wrote:
> On Wed, Oct 15, 2008 at 10:32 AM, Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
> > On Wed, Oct 15, 2008 at 10:02:44AM +0200, Artifex Maximus wrote:
> >> I would like to upgrade my curl to the latest 7.19.0 version because
> >> it is fixes some problems that 7.18.0 has. I would like to upgrade via
> >> ports system for future "compatibility". I have written to the port
> >> maintainer a week ago but no change.
> > The ports maintainer timeout is 2 weeks for PRs; I'm not sure if you
> > opened a PR on this request or not.  With a PR, the maintainer needs to
> > reply within 2 weeks.
> I see and I do not know that. I wrote to him directly not through PR.

Then AFAIK, the "timeout" does not apply.  If you'd like to open a PR on
for this upgrade, that would be ideal.  Let me know the PR number so
that in the case roam@ is busy, I can do it.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

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

Re: Testing - my emails don't seem to be getting through

[Jeremy Chadwick]

On Wed, Oct 15, 2008 at 10:24:27AM +1000, Da Rock wrote:
> I've been getting a lot of rejections: Helo command rejected: Host not
> found (in reply to RCPT TO command). So now I'm running a test to see if
> this one will get through.

I do not know why on earth you are testing this crap using a public
mailing list, rather than mailing an account at Gmail or Hotmail
or some such.  Sorry to sound sour about it, but it's rude.

The error you're receiving would be because your mail server during the
SMTP handshake is saying "HELO i.am.bob" and the remote SMTP server
attempts to resolve i.am.bob but cannot.  By "i.am.bob", I *literally*
mean "i.am.bob".  If you're forwarding mail around on a private network
on your LAN, your computer probably thinks its hostname is
"myfreebsdbox.my.lan", which isn't a publicly-resolvable hostname.

There are ways in sendmail and postfix to solve this problem.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

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

Re: How to get my Dad's Win2k system to access internet through my FreeBSD 6.2 system

[Jeremy Chadwick]

On Wed, Oct 15, 2008 at 08:40:48PM +1000, Da Rock wrote:
> 
> On Tue, 2008-10-14 at 06:46 -0400, Michael Powell wrote:
> > Jeremy Chadwick wrote:
> > 
> > > On Tue, Oct 14, 2008 at 04:55:11AM -0400, Michael Powell wrote:
> > [snip] 
> > >> Next, you will want to configure your FreeBSD machine as a NAT gateway.
> > >> In your /etc/rc.conf you will want something like gateway_enable="YES"
> > >> and some form of firewall initialization[1]. The gateway_enable is what
> > >> allows the forwarding of packets between your rl0 and your rl1, but the
> > >> activation of NAT functionality is usually a function contained within a
> > >> firewall. So conceptually, the firewall will be "in between" rl0 and rl1.
> > >> 
> > >> There are three different firewalls you can choose from. Configuring the
> > >> firewall is usually where the inexperienced get stuck. This subject
> > >> material is beyond the scope of this missive, and you would do well to
> > >> start reading in the Handbook. But essentially, when you configure NAT in
> > >> the firewall your rl0 (connected to the ISP) will be assigned a "Public"
> > >> IP address and the NAT function will translate between "Public" and
> > >> "Private".
> > 
> > With respect to "NAT", the caveat here is the assumption that your DSL/Cable
> > modem is *not* already performing NAT. The situation you do not want to get
> > into is having *two* NATs. The content herein is assuming that the external
> > (rl0) interface is getting assigned a "Public" IP from the ISP. 
> >  
> 
> If this is the case wouldn't the OP set router_enable=YES instead of
> gateway?

No.  router_enable causes routed(8) to run, which allows for
announcements and withdraws of network routes via RIPv1/v2.  This is
something completely different than forwarding packets.

What the OP wants is to route packets from his private LAN (e.g.
192.168.0.0/16) on to the Internet using NAT.  That means he has to have
a NAT gateway of some kind that forwards and translates packets.  That
means he needs gateway_enable="yes", which allows IPv4 forwarding
to happen "through" the FreeBSD box.  In layman's terms, it allows
the FreeBSD box to be used a "Gateway" for other computers which
are connected to it directly.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

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

Testing - my emails don't seem to be getting through

[Da Rock]

I've been getting a lot of rejections: Helo command rejected: Host not
found (in reply to RCPT TO command). So now I'm running a test to see if
this one will get through.

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

Auto Backup Data and Delete for Account Expired

[Kalpin Erlangga Silaen]

Dear all,

is there any routines to check if some accounts expire then system would
like to do backup all data to certain directory and then delete the account.

Any help would be appreciate.

Thank you


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

Re: Compiling curl 7.19

[Artifex Maximus]

Hello!

On Wed, Oct 15, 2008 at 10:32 AM, Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
> On Wed, Oct 15, 2008 at 10:02:44AM +0200, Artifex Maximus wrote:
>> I would like to upgrade my curl to the latest 7.19.0 version because
>> it is fixes some problems that 7.18.0 has. I would like to upgrade via
>> ports system for future "compatibility". I have written to the port
>> maintainer a week ago but no change.
> The ports maintainer timeout is 2 weeks for PRs; I'm not sure if you
> opened a PR on this request or not.  With a PR, the maintainer needs to
> reply within 2 weeks.
I see and I do not know that. I wrote to him directly not through PR.

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

Re: How to get my Dad's Win2k system to access internet through my FreeBSD 6.2 system

[Da Rock]

On Tue, 2008-10-14 at 06:46 -0400, Michael Powell wrote:
> Jeremy Chadwick wrote:
> 
> > On Tue, Oct 14, 2008 at 04:55:11AM -0400, Michael Powell wrote:
> [snip] 
> >> Next, you will want to configure your FreeBSD machine as a NAT gateway.
> >> In your /etc/rc.conf you will want something like gateway_enable="YES"
> >> and some form of firewall initialization[1]. The gateway_enable is what
> >> allows the forwarding of packets between your rl0 and your rl1, but the
> >> activation of NAT functionality is usually a function contained within a
> >> firewall. So conceptually, the firewall will be "in between" rl0 and rl1.
> >> 
> >> There are three different firewalls you can choose from. Configuring the
> >> firewall is usually where the inexperienced get stuck. This subject
> >> material is beyond the scope of this missive, and you would do well to
> >> start reading in the Handbook. But essentially, when you configure NAT in
> >> the firewall your rl0 (connected to the ISP) will be assigned a "Public"
> >> IP address and the NAT function will translate between "Public" and
> >> "Private".
> 
> With respect to "NAT", the caveat here is the assumption that your DSL/Cable
> modem is *not* already performing NAT. The situation you do not want to get
> into is having *two* NATs. The content herein is assuming that the external
> (rl0) interface is getting assigned a "Public" IP from the ISP. 
>  

If this is the case wouldn't the OP set router_enable=YES instead of
gateway?

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

Re: uptime 2 years!

[Da Rock]

> I love the direction this thread has taken. First, humorous,
then it
> will turn into flames.  I bet all my US$:-)
> 

Unfortunately that doesn't really offer much value anymore with
the
recent market downturn- got anything else to offer?

Sorry- couldn't resist... :P



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

Re: uptime 2 years!

[Da Rock]

On Thu, 2008-10-09 at 10:03 -0500, Paul Schmehl wrote:
> --On Thursday, October 09, 2008 09:34:02 -0500 Jerry
McAllister 
> <[EMAIL PROTECTED]> wrote:
> 
> >
> > On Thu, Oct 09, 2008 at 07:07:31AM -0700, Chad Marshall
wrote:
> >
> >>
> >>  Sorry to bother you...You know, you could just leave well
enough
> >> alone if you don't care. There goes any future donations
from me and
> >> my organization as this is more than the first untactful
email I
> >> recieved from this, I'll donate and use other platforms.
Please don't
> >> send any other emails
> >>
> >
> > Kind of touchy, wouldn't you think?
> > People are giving you some perspective.
> > Well, anyway, you have the choice of using a superior system
> > or let scratchy responses lead you to something less
suitable.
> >
> 
> When I was a young boy, I went on vacation with my family to a
lake in upper 
> Minnesota.  (My mother's ancestral home.)  The weather was
beautiful, the water 
> was warm and inviting, the swimming was thoroughly enjoyable
and the cabin we 
> stayed in was luxurious (by the standards of a little boy.)
> 
> However, my mother said something to me that mad me angry.  To
"punish" her, I 
> stomped off in a huff and spent the remainder of the vacation
scowling in the 
> cabin.  I refused to swim until she corrected the perceived
injustice. 
> Needless to say, my "punishment" caused me a great deal more
consternation than 
> it did her, or my siblings who were all happily enjoying the
water and the 
> boating and the entire lovely vacation while I fumed in the
cabin.
> 
> Self-inflicted wounds are often the most painful of all.
> 

You do present a very good point here, but in some ways the OP
has a
point. This list is by far the most supportive and helpful lists
I've
come across, it would be nice to keep this attribute and not
slip off
into the "geeks only" attitude.

That said, the post probably should have been sent to the chat
list and
not here.

I'm not trying to start an argument, just offer an outside
perspective.



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

Re: uptime 2 years!

[Da Rock]

On Thu, 2008-10-09 at 07:50 -0700, Chad Marshall wrote:
> Here's what I said to the last guy who says my skin is thin,
just  
> leave well enough alone and drop it please. Seems your skin is
thin as  
> well if you can't handle a little back talk :)
> 
> Well, I can always except critism. The problem is that I don't
need  
> rude responses for something I thought would be something to
share for  
> your organization, a success story of FreeBSD. Only for people
to call  
> me lazy and say "Big Deal". If it's not a big deal, than say
nothing.   
> Maybe you should put someone in charge of answering emails who
aren't  
> cocky and smug, some responses were nice and at least
supportive.
> 
> I still believe in FreeBSD and it's a great OS. It's the nix I
started  
> and learned with  but I think your community is full of
conceited,  
> pompous asses,  the reason I don't like to associate with IT
people.  
> I'd rather not give money to someone who has to insult me. If
you go  
> to a restaurant and you get a rude waiter, what do you do? I
don't go  
> back or give them a crap tip.

Maybe you should try the fedora list then? You'll be wishing you
hadn't
left this one... :)



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

Re: uptime 2 years!

[Da Rock]

On Thu, 2008-10-09 at 10:52 -0400, Mikel King wrote:
> On Oct 8, 2008, at 9:00 PM, Chad Marshall wrote:
> 
> > No Problem, I figured that there are other systems out there
with a  
> > longer uptime. I have this server as a
postfix/courier-imap/ 
> > squirrelmail  (60+ accounts and 30-40 forwards) mailserver
with  
> > apache/php/mysql.  Also use it as a slave authoritative
nameserver  
> > for over 100 zones (one zone with a 60sec TTL on a high
volume  
> > production website) as well. Plus use it as a primary
nameserver for  
> > our entire office (300+ workstations). I was lazy with it
(Upgrading  
> > or Replacing) and when it hit a year, I decided to hold off
doing  
> > anything with it as I wanted to see how long I could let it
go.   
> > It's a celeron 2.4ghz server with 512m Ram and has been a
champ  
> > server in it's performance and stability. I use CentOS for
most of  
> > my other systems and find that as easy as it is for
administration  
> > and upgrading, it lacks FreeBSD's performance. With the
memory leaks  
> > that CentOS has, I usually have to end up restarting the  
> > machine(s).  With FreeBSD I can just restart the services,
and got  
> > my memory back and reduce the amount of swap being used.
> >
> > Regardless of the first email I got back (Which was a little
rude),  
> > I will continue to run this server as long as I can and
monitor the  
> > security risks using DenyHosts and other security measures.
> >
> > Thanks,
> >
> >
> >
> > On Oct 8, 2008, at 3:39 PM, Frank Shute wrote:
> >
> >> On Wed, Oct 08, 2008 at 08:54:47AM -0700, Chad Marshall
wrote:
> >>>
> >>>
> >>> Hello,
> >>>
> >>> Would like to share a success story which I'm sure you've
had in the
> >>> past but one of my servers running FreeBSD will have an
uptime of 2
> >>> years tomorrow. I plan on putting on my blog but as it
doesn't have
> >>> much reach but wanted to share with you since your
community has  
> >>> made
> >>> this possible. Please indicate where I could post this to
have a bit
> >>> more reach or if you'd like to put a link to my blog, I'd
be more  
> >>> than
> >>> happy to provide that.
> >>>
> >>>
> >>> Best Regards,
> >>>
> >>
> >> Sorry to rain on your parade:
> >>
> >>
http://lists.freebsd.org/pipermail/freebsd-chat/2008-October/005719.html
> >>
> >>
> >> Regards,
> >>
> >> -- 
> >>
> >> Frank
> >>
> >>
> 
> I think this is good news, and thanks for posting it. While it
may not  
> be a record holder, from an advocacy point of view it's nice
to see.  
> It means there one more rock solid server out there.

Here, here...



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

Excuse me- just testing...

[Da Rock]

Been having trouble posting with a new mail server (only to your server
mind)- just trying sort it out.

Cheers

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

Re: An endian error [SOLVED]

[Unga]

--- On Tue, 10/14/08, Unga <[EMAIL PROTECTED]> wrote:

> From: Unga <[EMAIL PROTECTED]>
> Subject: An endian error
> To: freebsd-questions@freebsd.org
> Date: Tuesday, October 14, 2008, 8:00 PM
> Hi all
> 
> I'm trying to compile RELENG_7 kernel on i386.
> 
> The "make buildkernel" develops an endian related
> error:
> 
> ===> xl (depend)
> @ -> /usr/src/sys
> machine -> /usr/src/sys/i386/include
> awk -f @/tools/makeobjops.awk @/kern/device_if.m -h
> awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h
> awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h
> awk -f @/tools/makeobjops.awk @/dev/mii/miibus_if.m -h
> rm -f .depend
> mkdep -f .depend -a   -nostdinc -D_KERNEL -DKLD_MODULE
> -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq
> /usr/src/sys/modules/xl/../../pci/if_xl.c
> ===> zfs (depend)
> @ -> /usr/src/sys
> machine -> /usr/src/sys/i386/include
> awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -p
> awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -q
> awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -h
> rm -f .depend
> mkdep -f .depend -a   -nostdinc -DFREEBSD_NAMECACHE
> -D_SOLARIS_C_SOURCE -D_KERNEL -DKLD_MODULE
> -I/usr/src/sys/modules/zfs/../../cddl/compat/opensolaris 
> :
> :
> /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_geom.c
> 
> /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/rpc/xdr.c:63:2:
> error: #error "Only one of _BIG_ENDIAN or
> _LITTLE_ENDIAN may be defined"
> mkdep: compile failed
> *** Error code 1
> 
> Stop in /usr/src/sys/modules/zfs.
> *** Error code 1
> 

This was due to a wrong CFLAGS given. Without any CFLAGS, the "make 
buildkernel" passes this point.

Regards
Unga



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

Re: Compiling curl 7.19

[Jeremy Chadwick]

On Wed, Oct 15, 2008 at 10:02:44AM +0200, Artifex Maximus wrote:
> Hello!
> 
> I would like to upgrade my curl to the latest 7.19.0 version because
> it is fixes some problems that 7.18.0 has. I would like to upgrade via
> ports system for future "compatibility". I have written to the port
> maintainer a week ago but no change.

The ports maintainer timeout is 2 weeks for PRs; I'm not sure if you
opened a PR on this request or not.  With a PR, the maintainer needs to
reply within 2 weeks.

> Is anyone have a folder ftp/curl for 7.19.0 with patches? I have tried
> to "adjust" 7.18.0 ftp/curl patches but I got errors. Although Curl
> 7.19.0 is successfully compiled without patches, I am not sure that
> version is fully working because some patches change system function
> calls.

I'll see about getting this port updated assuming roam@ doesn't have the
time.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

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

Compiling curl 7.19

[Artifex Maximus]

Hello!

I would like to upgrade my curl to the latest 7.19.0 version because
it is fixes some problems that 7.18.0 has. I would like to upgrade via
ports system for future "compatibility". I have written to the port
maintainer a week ago but no change.

Is anyone have a folder ftp/curl for 7.19.0 with patches? I have tried
to "adjust" 7.18.0 ftp/curl patches but I got errors. Although Curl
7.19.0 is successfully compiled without patches, I am not sure that
version is fully working because some patches change system function
calls.

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

error compiling kdenetwork4

[shinjii]

Running AMD64 on FreeBSD7.1-PRERelease KDE4.1.2 ..

Below is the error when trying to compile it-

usr/ports/net/kdenetwork4/work/kdenetwork-4.1.2/kopete/kopete/contactlist/kopetegroupviewitem.h:53:
warning:   by 'QString KopeteGroupViewItem::toolTip() const'
In file included from
/usr/ports/net/kdenetwork4/work/kdenetwork-4.1.2/kopete/kopete/contactlist/kopetemetacontactlvi.cpp:65:
/usr/ports/net/kdenetwork4/work/kdenetwork-4.1.2/kopete/kopete/systemtray.h:
In member function 'bool KopeteSystemTray::isBlinking() const':
/usr/ports/net/kdenetwork4/work/kdenetwork-4.1.2/kopete/kopete/systemtray.h:57:
error: 'movie' was not declared in this scope
*** Error code 1

Stop in /usr/ports/net/kdenetwork4/work/kdenetwork-4.1.2/build.
*** Error code 1

Stop in /usr/ports/net/kdenetwork4/work/kdenetwork-4.1.2/build.
*** Error code 1

Stop in /usr/ports/net/kdenetwork4/work/kdenetwork-4.1.2/build.
*** Error code 1

Stop in /usr/ports/net/kdenetwork4.


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

[fixed?] Re: Minor problems with Xfce

[James Butler]

Just a followup...

2008/10/14 Manolis Kiagias <[EMAIL PROTECTED]>:
> James Butler wrote:
>>
>> Greetings all,
>>
>> I'm using 7-stable on my Thinkpad X31, with Xfce recently (2 weeks or
>> so) installed from packages. I have two minor problems with Xfce, at
>> least one of which could be HAL/DBUS related - I'd appreciate some
>> advice to rule out misconfiguration on my part.
>>
>> Firstly, when I bring up the Xfce Exit dialog, the Restart and
>> Shutdown buttons are greyed out. I have read the Xfce FAQ on the
>> subject, which mentions that the session manager tries HAL shutdown
>> methods first, then falls back to sudo. I don't have sudo installed,
>> but I have both hald and dbus (system and session) running.
>>
>> Checking the xsession error log after an attempted Exit reveals:
>>
>> ** Message: xfsm-shutdown-helper.c:215: HAL not available or does not
>> permit to shutdown/reboot the computer, trying sudo fallback instead.
>>
>> and (as expected):
>>
>> ** (xfce4-session:1066): WARNING **: sudo was not found. You will not
>> be able to shutdown your system from within Xfce
>>
>> Looking at xfsm-shutdown-helper.c I see that the session manager
>> probes HAL for shutdown support by trying a dummy method call:
>>
>> /* this is a simple trick to check whether we are allowed to
>>   * use the org.freedesktop.Hal.Device.SystemPowerManagement
>>   * interface without shutting down/rebooting now.
>>   */
>>  message = dbus_message_new_method_call ("org.freedesktop.Hal",
>>
>> "/org/freedesktop/Hal/devices/computer",
>>
>> "org.freedesktop.Hal.Device.SystemPowerManagement",
>>  "ThisMethodMustNotExistInHal");
>>
>> [snip]

I decided to build xfce4-session from ports, and add a debugging
printf() between these lines to see exactly which error dbus was
returning. So I installed it, and selected 'Quit' from the menu while
tail-ing the error log... and the shutdown/reboot buttons came up
enabled!! It all seems to work fine now. Does this mean there's
something wrong with the package builds? I guess I could file a PR.

>>
>> /* if we receive org.freedesktop.DBus.Error.UnknownMethod, then
>>   * we are allowed to shutdown/reboot the computer via HAL.
>>   */
>>  if (strcmp (error.name, "org.freedesktop.DBus.Error.UnknownMethod") == 0)
>>
>> So out of curiosity I tried this manually and got the 'correct' error:
>>
>> $ dbus-send --system --print-reply  --dest=org.freedesktop.Hal
>> /org/freedesktop/Hal/devices/computer
>>
>> org.freedesktop.Hal.Device.SystemPowerManagement.ThisMethodMustNotExistInHal
>> Error org.freedesktop.DBus.Error.UnknownMethod: Method
>> "ThisMethodMustNotExistInHal" with signature "" on interface
>> "org.freedesktop.Hal.Device.SystemPowerManagement" doesn't exist
>>
>> Now I don't claim to understand much of this, so any help would be
>> greatly appreciated. I have provided the output of various commands
>> from the freebsd-gnome Bugging guide at
>> http://homepages.ihug.co.nz/~sweetnavelorange/.
>>
>> My other problem is possibly unrelated, but any actions I perform
>> which would remove or update icons on the desktop (deleting a file,
>> emptying Trash) don't take effect until xfdesktop is restarted or I
>> log out and then in. Any ideas? Notably, automatic detection and
>> mounting of USB drives, which seems to be a fragile area for many HAL
>> users, works perfectly for me.
>>
>> Thanks in advance,
>> -James Butler
>>
>
> Insert something like the following in your
> /usr/local/etc/PolicyKit/PolicyKit.conf (between the  tags):
>
>   
>  
> 
>  
>   
>   
>  
> 
>  
>   
>
> Have a look at /usr/local/share/PolicyKit/policy. Examine the contents of
> the files there to see possible actions.
> It may also help to have a look at this page, if you haven't already:
>
> http://www.freebsd.org/gnome/docs/halfaq.html
>
> I have some annoyances with XFCE myself, but I haven't bothered seriously to
> fix them. I have the same no-icon-update problem on my desktop. I keep
> pressing F5 as a workaround. Like in your case, USB flash drive mounting
> works perfectly. Another thing that does not work for me, is clicking an
> http link in an app: it will not open firefox. Weird, as firefox is selected
> as the default / preferred browser.
>

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

Re: Under heavy load internet gets killed, only a reboot can bring it back up

[Jeremy Chadwick]

On Wed, Oct 15, 2008 at 09:13:00AM +0200, Aniruddha wrote:
> Each time  my internet connection is under heavy lead it gets killed
> after a minute of 10. I tried the following commands to get the internet
> back up, but nothing helped:
> 
> /etc/rc.d/netif restart
> ifconfig mynic down
> ifconfig mynic up
> 
> Even worse the last time I issued a '/etc/rc.d/netif restart' my whole
> system hardlocked (wasn't responding to capslock presses). So far the
> only solution has been te reboot the computer. Is there any way I can
> prevent my internet connection from getting killed? How do I get it back
> up after it has been killed? Thanks in advance!

What network card are you using?  Can you provide output from the
following commands?

dmesg
vmstat -i
netstat -in

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

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

Re: FreeBSD do dbus & hal work?

[Jeremy Chadwick]

On Wed, Oct 15, 2008 at 09:03:00AM +0200, Aniruddha wrote:
> On Tue, 2008-10-14 at 23:43 -0700, Jeremy Chadwick wrote:
> > > Thanks, I followed the faq to the letter and it show a dialog when I
> > > insert a USB stick. Unfortunately when I insert an sdcard still nothing
> > > happens.
> > 
> > Can anyone confirm that dbus and/or hald have anything to do with this?
> > (I thought those were specific to X...)
> > 
> > When attaching a USB device to a USB port, the kernel will notice the
> > device has been added and will do the proper enumeration.  For example,
> > when adding a USB hard disk or a USB pen drive, a umass device will be
> > found, then a daX device should be created (which is what you use to
> > access the disk; USB storage devices appear as SCSI disks).
> > 
> > But in the case of a USB device that's already attached to the bus, e.g.
> > one of those 7-in-1 card readers, I cannot see how adding a SD/MMC card
> > would cause the hard disk to suddenly show up.
> > 
> > You would need to run "camcontrol rescan 0", to cause the device to be
> > re-scanned for any media which was inserted.
> 
> Thanks for the quick and extensive answer. I'll check the exact behavior of  
> the 7-in-1 card reader somewhat more.

The card reader is already attached to the USB bus once the kernel
loads.  To find actual inserted/removed media, you will need to
do the camcontrol command I listed off.

Also: ALWAYS be sure to use "umount" to unmount the filesystems *BEFORE*
removing the media.  Not doing so will result in a kernel panic.
Consider yourself warned.

Supposedly this has been fixed in CURRENT/HEAD.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

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

Under heavy load internet gets killed, only a reboot can bring it back up

[Aniruddha]

Each time  my internet connection is under heavy lead it gets killed
after a minute of 10. I tried the following commands to get the internet
back up, but nothing helped:

/etc/rc.d/netif restart
ifconfig mynic down
ifconfig mynic up

Even worse the last time I issued a '/etc/rc.d/netif restart' my whole
system hardlocked (wasn't responding to capslock presses). So far the
only solution has been te reboot the computer. Is there any way I can
prevent my internet connection from getting killed? How do I get it back
up after it has been killed? Thanks in advance!




-- 
Regards,

Aniruddha




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

Re: FreeBSD do dbus & hal work?

[Aniruddha]

On Tue, 2008-10-14 at 23:43 -0700, Jeremy Chadwick wrote:
> > Thanks, I followed the faq to the letter and it show a dialog when I
> > insert a USB stick. Unfortunately when I insert an sdcard still nothing
> > happens.
> 
> Can anyone confirm that dbus and/or hald have anything to do with this?
> (I thought those were specific to X...)
> 
> When attaching a USB device to a USB port, the kernel will notice the
> device has been added and will do the proper enumeration.  For example,
> when adding a USB hard disk or a USB pen drive, a umass device will be
> found, then a daX device should be created (which is what you use to
> access the disk; USB storage devices appear as SCSI disks).
> 
> But in the case of a USB device that's already attached to the bus, e.g.
> one of those 7-in-1 card readers, I cannot see how adding a SD/MMC card
> would cause the hard disk to suddenly show up.
> 
> You would need to run "camcontrol rescan 0", to cause the device to be
> re-scanned for any media which was inserted.

Thanks for the quick and extensive answer. I'll check the exact behavior of  
the 7-in-1 card reader somewhat more.


-- 
Regards,

Aniruddha




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