From pyunyh at gmail.com  Wed Jul  1 02:47:44 2009
From: pyunyh at gmail.com (Pyun YongHyeon)
Date: Wed Jul  1 02:47:53 2009
Subject: problem with if_re on RELENG_7
In-Reply-To: <4A4A70F6.1080808@therek.net>
References: <20090414174527.145c6448@notebook>
	<20090415041516.GF65724@michelle.cdnetworks.co.kr>
	<20090415100456.55bbe358@tiger.minsk.domain>
	<20090415074144.GH65724@michelle.cdnetworks.co.kr>
	<20090415114343.6a72784d@tiger.minsk.domain>
	<20090415103026.GJ65724@michelle.cdnetworks.co.kr>
	<20090415133820.42211c98@notebook>
	<20090415104831.GK65724@michelle.cdnetworks.co.kr>
	<4A4A70F6.1080808@therek.net>
Message-ID: <20090701021220.GD13137@michelle.cdnetworks.co.kr>

On Tue, Jun 30, 2009 at 10:09:26PM +0200, Cezary Morga wrote:
> Pyun YongHyeon pisze:
> >Ok, I think you've have to live without MSI. I'll rearrange re(4)
> >to disable MSI on RTL8168 SPIN2 device.
> >Thanks for testing!
> 
> Silly question, but what is this MSI on a network card?
> 

MSI stands for Message Signaled Interrupt. Virtually any controller 
that honors PCI 2.2 or higher and PCI express can have MSI
capability. One of user visible change would be no more interrupt
sharing among devices. Goodle is your friend.
From rsmith at xs4all.nl  Wed Jul  1 04:01:04 2009
From: rsmith at xs4all.nl (Roland Smith)
Date: Wed Jul  1 04:01:12 2009
Subject: Vulnerability question
In-Reply-To: <20090630223504.GA77577@in-addr.com>
References: <20090628205654.GA6237@pollux.local.net>
	<20090629184052.GB3248@slackbox.xs4all.nl>
	<20090630150832.GA2650@pollux.local.net>
	<20090630173237.GB39520@slackbox.xs4all.nl>
	<20090630223504.GA77577@in-addr.com>
Message-ID: <20090701040101.GA59008@slackbox.xs4all.nl>

On Tue, Jun 30, 2009 at 06:35:04PM -0400, Gary Palmer wrote:
> > > > Are you running a linux binary of mplayer? Because a native mplayer
> > > > binary does not require linux-pango! It just uses the native pango.
> > > 
> > > In fact, it's lxdvdrip which requires linux-pango [via linux-gtk2].
> > > lxdvdrip is happy with the native mplayer.
> > 
> > Looking at the port Makefile [/usr/ports/multimedia/lxdvdrip/Makefile]
> > and Freshports entries [http://www.freshports.org/multimedia/lxdvdrip/]
> > for lxdvdrip, there is no sign of it directly requiring pango, let alone
> > the Linux version. It is mplayer that depends on pango:

> I am not the OP, however I also ran into warnings about mplayer and
> linux-pango.  I believe the problem comes from linux-realplayer
> 
> # cd /usr/ports/multimedia/mplayer
> # make run-depends-list
<snip>
> /usr/ports/multimedia/linux-realplayer
> /usr/ports/multimedia/mplayer-skins
> /usr/ports/multimedia/win32-codecs
<snip>
> # grep REAL /var/db/ports/mplayer/options 
> WITH_REALPLAYER=true

Good catch! I think that is indeed the problem. I disabled realplayer
support for mplayer ages ago, so it doesn't show up in my list. 

Harald, re-build mplayer with realplayer support disabled (if you can do
without it), and you should probably loose the dependency on
linux-pango.

> There may be more than one path to the linux-pango dependency however
> :-(

I don't think so, looking at the Makefiles of the other dependencies of
lxdvdrip. 

Roland
-- 
R.F.Smith                                   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090701/694e7ef7/attachment.pgp
From hawei at free.fr  Wed Jul  1 08:50:45 2009
From: hawei at free.fr (Harald Weis)
Date: Wed Jul  1 08:50:52 2009
Subject: Vulnerability question
In-Reply-To: <20090701040101.GA59008@slackbox.xs4all.nl>
References: <20090628205654.GA6237@pollux.local.net>
	<20090629184052.GB3248@slackbox.xs4all.nl>
	<20090630150832.GA2650@pollux.local.net>
	<20090630173237.GB39520@slackbox.xs4all.nl>
	<20090630223504.GA77577@in-addr.com>
	<20090701040101.GA59008@slackbox.xs4all.nl>
Message-ID: <20090701085036.GA1846@pollux.local.net>

On Wed, Jul 01, 2009 at 06:01:01AM +0200, Roland Smith wrote:
> On Tue, Jun 30, 2009 at 06:35:04PM -0400, Gary Palmer wrote:
 
> > I am not the OP, however I also ran into warnings about mplayer and
> > linux-pango.  I believe the problem comes from linux-realplayer
> > 
> > # cd /usr/ports/multimedia/mplayer
> > # make run-depends-list
> <snip>
> > /usr/ports/multimedia/linux-realplayer
> > /usr/ports/multimedia/mplayer-skins
> > /usr/ports/multimedia/win32-codecs
> <snip>
> > # grep REAL /var/db/ports/mplayer/options 
> > WITH_REALPLAYER=true
> 
> Good catch! I think that is indeed the problem. I disabled realplayer
> support for mplayer ages ago, so it doesn't show up in my list. 
> 
> Harald, re-build mplayer with realplayer support disabled (if you can do
> without it), and you should probably loose the dependency on
> linux-pango.
> 
> > There may be more than one path to the linux-pango dependency however
> > :-(
> 
> I don't think so, looking at the Makefiles of the other dependencies of
> lxdvdrip. 

Yes, it is the ``real player plugin'' option for mplayer which
was responsible for linux-pango (and probably for all other linux stuff)
requested during the reinstallation of lxdvdrip a week ago using
DISABLE_VULNERABILITIES=yes .

I've found this 5 minutes after my reply to Roland yesterday when trying
to reinstall first just mplayer alone, and then lxdvdrip.
But, I had absolutely no time to signal this to the list before now.

Many thanks to all of you. It's a great relief that I have finally
recuperated lxdvdrip.

Harald

From jh at saunalahti.fi  Wed Jul  1 09:08:27 2009
From: jh at saunalahti.fi (Jaakko Heinonen)
Date: Wed Jul  1 09:08:35 2009
Subject: kern/135412: [zfs] [nfs] zfs(v13)+nfs and open(...,
	O_WRONLY|O_CREAT|O_EXCL, ...)
In-Reply-To: <4A4A6358.1010806@bit0.com>
References: <E1MLbya-000P4e-Qd@kabab.cs.huji.ac.il>
	<20090630155437.GA42783@a91-153-125-115.elisa-laajakaista.fi>
	<4A4A6358.1010806@bit0.com>
Message-ID: <20090701090818.GA1391@a91-153-125-115.elisa-laajakaista.fi>

On 2009-06-30, Mike Andrews wrote:
> Jaakko Heinonen wrote:
> > On 2009-06-30, Danny Braniss wrote:
> >> 	This pr is realy holding me back, I can't upgrade this server, and
> >> telling serveral tens of users to us cp, etc is not an option. The open
> >> works fine if not using O_EXCL. 
> > 
> > I guess that r185586 needs to be MFCd to stable/7. Here's an untested
> > patch against stable/7:
> 
> The patch doesn't help over here, sorry.
> 
> Simply doing 'touch' or 'mv' to an NFSv3 mount (using either a v6 or v13 
> zpool) is the test case I've been using; touch doesn't even use O_EXCL as 
> far as I can tell.

I could reproduce the problem with O_EXCL and verified that the patch
fixes it. However I couldn't reproduce the problem you are seeing with
touch and mv.

-- 
Jaakko
From danny at cs.huji.ac.il  Wed Jul  1 09:24:07 2009
From: danny at cs.huji.ac.il (Danny Braniss)
Date: Wed Jul  1 09:24:17 2009
Subject: kern/135412: [zfs] [nfs] zfs(v13)+nfs and open(..., 
 O_WRONLY|O_CREAT|O_EXCL, ...)
In-Reply-To: <20090701090818.GA1391@a91-153-125-115.elisa-laajakaista.fi> 
References: <E1MLbya-000P4e-Qd@kabab.cs.huji.ac.il> 
	<20090630155437.GA42783@a91-153-125-115.elisa-laajakaista.fi> 
	<4A4A6358.1010806@bit0.com>
	<20090701090818.GA1391@a91-153-125-115.elisa-laajakaista.fi>
Message-ID: <E1MLw2u-000Bi0-K1@kabab.cs.huji.ac.il>

> On 2009-06-30, Mike Andrews wrote:
> > Jaakko Heinonen wrote:
> > > On 2009-06-30, Danny Braniss wrote:
> > >> 	This pr is realy holding me back, I can't upgrade this server, and
> > >> telling serveral tens of users to us cp, etc is not an option. The open
> > >> works fine if not using O_EXCL. 
> > > 
> > > I guess that r185586 needs to be MFCd to stable/7. Here's an untested
> > > patch against stable/7:
> > 
> > The patch doesn't help over here, sorry.
> > 
> > Simply doing 'touch' or 'mv' to an NFSv3 mount (using either a v6 or v13 
> > zpool) is the test case I've been using; touch doesn't even use O_EXCL as 
> > far as I can tell.
> 
> I could reproduce the problem with O_EXCL and verified that the patch
> fixes it. However I couldn't reproduce the problem you are seeing with
> touch and mv.

same here, touch worked before too - so i think it's unrelated,
btw, it seems that the problem does not exist on i386, though
I'm pretty sure I tried there too, oh well, 

thanks!
	danny


From david.keller at litchis.fr  Wed Jul  1 10:24:36 2009
From: david.keller at litchis.fr (david.keller@litchis.fr)
Date: Wed Jul  1 10:24:43 2009
Subject: 7.2-RELEASE amd64 panic when starting Xorg
Message-ID: <a81be6c932dc40247d0e7023319e36fa@litchis.fr>

Hi,

Using an ATI Radeon X850, the system restarts when starting Xorg.

The coredump says that it's a page related error.

This bug seems related to this one:
http://lists.freebsd.org/pipermail/freebsd-stable/2009-April/049618.html
which provides some informations. Do you need more ?

What can I do to help ?

From sagara at tomahawk.com.sg  Wed Jul  1 10:48:39 2009
From: sagara at tomahawk.com.sg (Sagara Wijetunga)
Date: Wed Jul  1 10:48:46 2009
Subject: FreeBSD child process die for root 
Message-ID: <20090701070409.7740.qmail@us1.tomahawkonline.net>

Hi 

I'm Sagara Wijetunga from Tomahawk Computers from Singapore, makers of the 
Tomahawk Desktop, a FreeBSD based desktop operating system 
(http://www.tomahawkcomputers.com/) which is free for personal use. 

Ever since we upgraded our Tomahawk Core OS to the FreeBSD 7.2 sources, we 
experienced a strange issue as follows: 

   1. The root cannot login from the console, child process forked die with 
?uid 0: exited on signal 11?.
   2. Normal users can log in, no issue.
   3. Normal users can type ?su? and become root, but ?su -l? 
results child process forked die with ?uid 0: exited on signal 11?.
   4. The /var/log/messages shows ?(cron), uid 0: exited on signal 11 
(core dumped)? 

We use a different build method to create Tomahawk Core OS, therefore, we 
earlier decided not to complain about this issue till we release the beta 
version as we were thinking without having access to our OS it may be 
difficult to diagnose this issue. 

Then we saw ?Deadlock in a multi-threaded program during fork(2)? on 
FreeBSD website and upgraded our sources to the latest and rebuilt the 
Tomahawk Core OS but the problem we face did not go away. 

Appreciate if the FreeBSD community could give us a helping hand to identify 
the cause of the issue we are facing. 

Kind regards
Sagara Wijetunga
From hawei at free.fr  Wed Jul  1 11:14:46 2009
From: hawei at free.fr (Harald Weis)
Date: Wed Jul  1 11:14:52 2009
Subject: Vulnerability question
In-Reply-To: <20090701040101.GA59008@slackbox.xs4all.nl>
References: <20090628205654.GA6237@pollux.local.net>
	<20090629184052.GB3248@slackbox.xs4all.nl>
	<20090630150832.GA2650@pollux.local.net>
	<20090630173237.GB39520@slackbox.xs4all.nl>
	<20090630223504.GA77577@in-addr.com>
	<20090701040101.GA59008@slackbox.xs4all.nl>
Message-ID: <20090701111437.GB1846@pollux.local.net>

On Wed, Jul 01, 2009 at 06:01:01AM +0200, Roland Smith wrote:
 
> Good catch! I think that is indeed the problem. I disabled realplayer
> support for mplayer ages ago, so it doesn't show up in my list. 
 
How do you do that precisely ?
``WITH_REALPLAYER=no'' in /etc/make.conf ?

Thanks
Harald
From sos at deepcore.dk  Wed Jul  1 12:58:25 2009
From: sos at deepcore.dk (=?ISO-8859-1?Q?S=F8ren_Schmidt?=)
Date: Wed Jul  1 12:58:32 2009
Subject: ATA driver update for 7.2RELEASE available
In-Reply-To: <20090627132941.5d212017@tau.draftnet>
References: <8EB69F68-8ED2-469C-B83E-2555A72630B4@deepcore.dk>
	<20090627132941.5d212017@tau.draftnet>
Message-ID: <4202EA69-6973-4638-8A0B-040F4FAA0B27@deepcore.dk>

On 27Jun, 2009, at 14:29 , Bruce Cran wrote:

> On Fri, 26 Jun 2009 22:11:08 +0200
> S?ren Schmidt <sos@deepcore.dk> wrote:
>
>> This is a total replacement of the ATA driver, modulerized as in -
>> current, but based on my WIP not from what might have happend to -
>> current since I gave up maintainership.
>
> It's great to see the driver be modularised since removing unneeded
> drivers (for example, on powerpc and embedded platforms) can save
> ~200KB.

Yep, thats the main idea behind this move, minimizing the footprint.
With this and some of the _NO_ options to the world build an almost  
reasonable sized FreeBSD can be made.
FreeBSD seems to have grown *alot* of fat over the last years, not to  
mention ports where installing one small application gets you both a  
pony and a barn to keep it in as a "bonus" 8^)

> Could you add some documentation for the modules in /sys/conf/NOTES
> please?  I looked through the sources and put together the patch for
> 8.0 which is avaiable at
> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/133162 but it sounds
> like some more drivers will need to be added for 7.2.

Good catch, included in my WIP here, when/if I get to put up another  
release of this it will be in there, thanks!

PS: For official inclusion in FreeBSD someone with a commit bit will  
have to look into this.

-S?ren
--









From rnoland at FreeBSD.org  Wed Jul  1 13:45:15 2009
From: rnoland at FreeBSD.org (Robert Noland)
Date: Wed Jul  1 13:45:23 2009
Subject: 7.2-RELEASE amd64 panic when starting Xorg
In-Reply-To: <a81be6c932dc40247d0e7023319e36fa@litchis.fr>
References: <a81be6c932dc40247d0e7023319e36fa@litchis.fr>
Message-ID: <1246455905.1855.31.camel@balrog.2hip.net>

On Wed, 2009-07-01 at 10:25 +0000, david.keller@litchis.fr wrote:
> Hi,
> 
> Using an ATI Radeon X850, the system restarts when starting Xorg.
> 
> The coredump says that it's a page related error.
> 
> This bug seems related to this one:
> http://lists.freebsd.org/pipermail/freebsd-stable/2009-April/049618.html
> which provides some informations. Do you need more ?
> 
> What can I do to help ?

I don't see that we resolved that one... It looks like drm_open is
returning "no such file or directory".  Check the permissions on the drm
device.  That said, it still shouldn't panic,  I'm suspicious that it
may be related to copyin/copyout with locks held.  See if the following
patch still applies cleanly.

http://people.freebsd.org/~rnoland/drm_radeon-copyin-fix-try2.patch

robert.

> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
-- 
Robert Noland <rnoland@FreeBSD.org>
FreeBSD
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090701/c323fd61/attachment.pgp
From oberman at es.net  Wed Jul  1 17:00:16 2009
From: oberman at es.net (Kevin Oberman)
Date: Wed Jul  1 17:00:28 2009
Subject: Vulnerability question 
In-Reply-To: Your message of "Wed, 01 Jul 2009 13:14:37 +0200."
	<20090701111437.GB1846@pollux.local.net> 
Message-ID: <20090701170012.CAF421CC09@ptavv.es.net>

> Date: Wed, 1 Jul 2009 13:14:37 +0200
> From: Harald Weis <hawei@free.fr>
> Sender: owner-freebsd-stable@freebsd.org
> 
> On Wed, Jul 01, 2009 at 06:01:01AM +0200, Roland Smith wrote:
>  
> > Good catch! I think that is indeed the problem. I disabled realplayer
> > support for mplayer ages ago, so it doesn't show up in my list. 
>  
> How do you do that precisely ?
> ``WITH_REALPLAYER=no'' in /etc/make.conf ?

cd /us/ports/multimedia/mplayer
make config
Scroll down to the "REALPLAYER  Enable real player plugin" line
<SPACE> to un-check the line
<TAB><ENTER>
make
make deinstall
make reinstall
make clean

Or use 'portupgrade -f' AFTER the 'make config'.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@es.net			Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4  EADA 927D EBB3 987B 3751
From rsmith at xs4all.nl  Wed Jul  1 17:49:34 2009
From: rsmith at xs4all.nl (Roland Smith)
Date: Wed Jul  1 17:49:41 2009
Subject: FreeBSD child process die for root
In-Reply-To: <20090701070409.7740.qmail@us1.tomahawkonline.net>
References: <20090701070409.7740.qmail@us1.tomahawkonline.net>
Message-ID: <20090701174930.GC37269@slackbox.xs4all.nl>

On Wed, Jul 01, 2009 at 02:04:09AM -0500, Sagara Wijetunga wrote:
> Hi 
> 
> I'm Sagara Wijetunga from Tomahawk Computers from Singapore, makers of the 
> Tomahawk Desktop, a FreeBSD based desktop operating system 
> (http://www.tomahawkcomputers.com/) which is free for personal use. 
> 
> Ever since we upgraded our Tomahawk Core OS to the FreeBSD 7.2 sources, we 
> experienced a strange issue as follows: 
> 
>    1. The root cannot login from the console, child process forked die with 
> ?uid 0: exited on signal 11?.
>    2. Normal users can log in, no issue.
>    3. Normal users can type ?su? and become root, but ?su -l? 
> results child process forked die with ?uid 0: exited on signal 11?.
>    4. The /var/log/messages shows ?(cron), uid 0: exited on signal 11 
> (core dumped)? 

Based on your symptoms, it looks like something in the restart commands
file for root causes the shell to crash...

What shell are you using for root?

Roland
-- 
R.F.Smith                                   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090701/f5165597/attachment.pgp
From Andre.Albsmeier at siemens.com  Wed Jul  1 19:56:11 2009
From: Andre.Albsmeier at siemens.com (Andre Albsmeier)
Date: Wed Jul  1 19:56:18 2009
Subject: net/iwi-firmware refuses to build on 7.2-STABLE 
Message-ID: <20090701193410.GA19202@curry.mchp.siemens.de>

Today I wanted to build net/iwi-firmware on 7.2-STABLE and I got

===>  iwi-firmware-2.4_8 is configured with iwicontrol(8) which you don't need, use 'make rmconfig' and uncheck CONTROL.

While the firmware itself is in the base system, iwicontrol(8)
is not. The port should be modified to cope with this but I
have no idea in what way. Some ideas:

1. Remove the build restrictions
2. Just build iwicontrol on systems where the fw is not needed
3. Make an extra port just to build iwicontrol
4. ???

Any suggestions? Thanks,

	-Andre
From amarat at ksu.ru  Wed Jul  1 20:41:51 2009
From: amarat at ksu.ru (Marat N.Afanasyev)
Date: Wed Jul  1 20:41:59 2009
Subject: net/iwi-firmware refuses to build on 7.2-STABLE
In-Reply-To: <20090701193410.GA19202@curry.mchp.siemens.de>
References: <20090701193410.GA19202@curry.mchp.siemens.de>
Message-ID: <4A4BC767.5080100@ksu.ru>

Andre Albsmeier wrote:
> Today I wanted to build net/iwi-firmware on 7.2-STABLE and I got
> 
> ===>  iwi-firmware-2.4_8 is configured with iwicontrol(8) which you don't need, use 'make rmconfig' and uncheck CONTROL.
> 
> While the firmware itself is in the base system, iwicontrol(8)
> is not. The port should be modified to cope with this but I
> have no idea in what way. Some ideas:
> 
> 1. Remove the build restrictions
> 2. Just build iwicontrol on systems where the fw is not needed
> 3. Make an extra port just to build iwicontrol
> 4. ???
> 
> Any suggestions? Thanks,
> 
> 	-Andre
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
> 
iwicontrol is obsoleted by ifconfig, afaik

-- 
SY, Marat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3221 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090701/09e6db0b/smime.bin
From sam at freebsd.org  Wed Jul  1 20:47:42 2009
From: sam at freebsd.org (Sam Leffler)
Date: Wed Jul  1 20:47:48 2009
Subject: net/iwi-firmware refuses to build on 7.2-STABLE
In-Reply-To: <20090701193410.GA19202@curry.mchp.siemens.de>
References: <20090701193410.GA19202@curry.mchp.siemens.de>
Message-ID: <4A4BC709.6060709@freebsd.org>

Andre Albsmeier wrote:
> Today I wanted to build net/iwi-firmware on 7.2-STABLE and I got
> 
> ===>  iwi-firmware-2.4_8 is configured with iwicontrol(8) which you don't need, use 'make rmconfig' and uncheck CONTROL.
> 
> While the firmware itself is in the base system, iwicontrol(8)
> is not. The port should be modified to cope with this but I
> have no idea in what way. Some ideas:
> 
> 1. Remove the build restrictions
> 2. Just build iwicontrol on systems where the fw is not needed
> 3. Make an extra port just to build iwicontrol
> 4. ???
> 
> Any suggestions? Thanks,

man iwi; the firmware is automatically loaded by the driver

	Sam
From sales at worldcrown.net  Wed Jul  1 20:52:26 2009
From: sales at worldcrown.net (WORLD CROWN ELECTRONICS LTD)
Date: Wed Jul  1 20:52:35 2009
Subject: Card Reader at USD 0.59/pc 1K pcs up (CR35)
Message-ID: <DS10301086905ecdf748678f12b51656ec9065@DS1030>

                                                                                                                       Promotional gift   with YOUR OWN LOGO  

 Card Reader at USD 0.59/pc 1K pcs up CR35  

 ( http://rs-tr.com//t.aspx/subid/7648016/camid/25556/rs-tr.com//t.aspx/subid/6782126/camid/25489/www.worldcrown.net/product_info.asp?id=529 ) ( http://rs-tr.com//t.aspx/subid/7648016/camid/25556/rs-tr.com//t.aspx/subid/6782126/camid/25489/worldcrown.net/product_info.asp?id=539 ) ( http://rs-tr.com//t.aspx/subid/7648016/camid/25556/rs-tr.com//t.aspx/subid/6782126/camid/25489/https/rspd_col///www.reasonablespread.com/Management/Campaign/AddCampaignContent.aspx?campaign_id=15518 ) 	 ( http://rs-tr.com//t.aspx/subid/7648016/camid/25556/rs-tr.com//t.aspx/subid/6782126/camid/25489/worldcrown.net/product_info.asp?id=592 ) 	 ( http://rs-tr.com//t.aspx/subid/7648016/camid/25556/rs-tr.com//t.aspx/subid/6782126/camid/25489/www.am730.com.hk/ )  

CR25  	

CR60  	

CR66      

	  	

	                       CR53 	                          CR29 	

                          CR35     

	  	

	                    CR55 	                        CR23 	

                          CR21     

For more product details, please visit http://worldcrown.net ( http://rs-tr.com//t.aspx/subid/7648016/camid/25556/rs-tr.com//t.aspx/subid/6782126/camid/25489/worldcrown.net/ )   

Please tell me your MSN or Skype so we can discuss directly. My MSN is world.crown@hotmail.com (  ) and Skype is sales3_worldcrown.net 

Ms Li _________________________ Direct Line: (852) 31870298 , Email:  li@worldcrown.net (  ), Skype: sales3_worldcrown.net, MSN: world.crown@hotmail.com (  )  

WORLD CROWN ELECTRONICS LTD 

Hong Kong  

Office & Showroom: Unit 371-374, 3/F., Sino Industrial Plaza, 9 Kai Cheung Road, Kowloon Bay, Kowloon, Hong Kong  

Tel: (852) 3187 0228 (18 Lines)    Fax:(852) 2155 0985 (3 Lines)  

China  

Office Address: Unit A516, Automobile Building, 45 Zhenhua Road, Futian District, Shenzhen, China  Factory Adddress: 6/F., B7 Building, Xujingchang Industry Park, Fuyuanyi Road, Xinhe Community, Fuyong Street, Bao An District, Shenzhen, China.  

	 		 	

	 		 	

	 		 	

	 		 	

They trust and rely on us with their important promotional projects. How about you? Please make your first step to contact our sales department. You are ensured that your requirements will be our first priority.    

Forward this email ( http://rs-ar.com/2400-25556/.newsletter/Card_Reader_at_USD_0.59pc_1K_pcs_up_(CR35)/forward.aspx )

	 Update Email & Profile ( http://rs-sub.com/SubscribeFormDetail.aspx?ens=dZQ92So05yHCJAsV4/KOpw==&type=profile ) | Unsubscribe ( http://rs-sub.com/Unsubscribe.aspx?sub=7648016&user=2400&campid=25556&type=p ) 	  ( http://rs-w.com/about.aspx?subid=7648016&campid=25556 )       
From hawei at free.fr  Wed Jul  1 21:05:38 2009
From: hawei at free.fr (Harald Weis)
Date: Wed Jul  1 21:05:45 2009
Subject: Vulnerability question
In-Reply-To: <20090701170012.CAF421CC09@ptavv.es.net>
References: <20090701111437.GB1846@pollux.local.net>
	<20090701170012.CAF421CC09@ptavv.es.net>
Message-ID: <20090701210528.GC1846@pollux.local.net>

On Wed, Jul 01, 2009 at 10:00:12AM -0700, Kevin Oberman wrote:

> > > Good catch! I think that is indeed the problem. I disabled realplayer
> > > support for mplayer ages ago, so it doesn't show up in my list. 
> >  
> > How do you do that precisely ?
> > ``WITH_REALPLAYER=no'' in /etc/make.conf ?
> 
> cd /us/ports/multimedia/mplayer
> make config
> Scroll down to the "REALPLAYER  Enable real player plugin" line
> <SPACE> to un-check the line
> <TAB><ENTER>
> make
> make deinstall
> make reinstall
> make clean
> 
> Or use 'portupgrade -f' AFTER the 'make config'.

That's not what I meant.
Every time I do ``portsnap fetch update'' mplayer's Makefile contains
the ``real player plugin'' option set to ``on''.
If for some reason I've got to reinstall mplayer with (my preferred)
``portmaster --force-config [-d|-D] multimedia/mplayer'', then
I would like to have the realplay option already unchecked.
This is the way I interpreted Roland's ``so it doesn't show up in my
list''.
I thought the WITH_REALPLAYER=no line in make.conf could do this job,
couldn't it?

Harald
From rsmith at xs4all.nl  Wed Jul  1 21:24:22 2009
From: rsmith at xs4all.nl (Roland Smith)
Date: Wed Jul  1 21:24:30 2009
Subject: Vulnerability question
In-Reply-To: <20090701210528.GC1846@pollux.local.net>
References: <20090701111437.GB1846@pollux.local.net>
	<20090701170012.CAF421CC09@ptavv.es.net>
	<20090701210528.GC1846@pollux.local.net>
Message-ID: <20090701212420.GA43923@slackbox.xs4all.nl>

On Wed, Jul 01, 2009 at 11:05:28PM +0200, Harald Weis wrote:
> > > How do you do that precisely ?
> > > ``WITH_REALPLAYER=no'' in /etc/make.conf ?
> > 
> > cd /us/ports/multimedia/mplayer
> > make config
> > Scroll down to the "REALPLAYER  Enable real player plugin" line
> > <SPACE> to un-check the line
> > <TAB><ENTER>
> > make
> > make deinstall
> > make reinstall
> > make clean
> > 
> > Or use 'portupgrade -f' AFTER the 'make config'.
> 
> That's not what I meant.
> Every time I do ``portsnap fetch update'' mplayer's Makefile contains
> the ``real player plugin'' option set to ``on''.
> If for some reason I've got to reinstall mplayer with (my preferred)
> ``portmaster --force-config [-d|-D] multimedia/mplayer'', then
> I would like to have the realplay option already unchecked.
<snip>
> I thought the WITH_REALPLAYER=no line in make.conf could do this job,

The config values given in the Makefile are defaults. If you change
them, the options values are saved in /var/db/ports/<portname>/options. These
values override the defaults, and you will not be shown the dialog again
unless extra options have been added to the Makefile or --force-config is used.

Another method is to put variables in /etc/make.conf, but to prevent mistakes
you should only put those varialbes in /etc/make.conf that are not
supported by options. E.g. for mplayer I have the following in make.conf:

.if ${.CURDIR:M*/multimedia/mplayer}
WITH_DVD_DEVICE=/dev/cd1
WITH_CDROM_DEVICE=/dev/cd1
.endif

The if-construction is used to set these variables only when invoked in
the mplayer port directory, to prevent possible conflicts with other ports.
These particular variables have to be set in make.conf because the
options mechanism currently only supports yes/no values.

Roland
-- 
R.F.Smith                                   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090701/5a0ea27a/attachment.pgp
From sagara at tomahawk.com.sg  Thu Jul  2 04:41:43 2009
From: sagara at tomahawk.com.sg (Sagara Wijetunga)
Date: Thu Jul  2 04:41:50 2009
Subject: FreeBSD child process die for root
In-Reply-To: <20090701174930.GC37269@slackbox.xs4all.nl>
References: <20090701070409.7740.qmail@us1.tomahawkonline.net>
	<20090701174930.GC37269@slackbox.xs4all.nl>
Message-ID: <20090702012352.17934.qmail@us1.tomahawkonline.net>

Roland Smith writes: 

> On Wed, Jul 01, 2009 at 02:04:09AM -0500, Sagara Wijetunga wrote:
>> Hi  
>> 
>> I'm Sagara Wijetunga from Tomahawk Computers from Singapore, makers of the 
>> Tomahawk Desktop, a FreeBSD based desktop operating system 
>> (http://www.tomahawkcomputers.com/) which is free for personal use.  
>> 
>> Ever since we upgraded our Tomahawk Core OS to the FreeBSD 7.2 sources, we 
>> experienced a strange issue as follows:  
>> 
>>    1. The root cannot login from the console, child process forked die with 
>> ?uid 0: exited on signal 11?.
>>    2. Normal users can log in, no issue.
>>    3. Normal users can type ?su? and become root, but ?su -l? 
>> results child process forked die with ?uid 0: exited on signal 11?.
>>    4. The /var/log/messages shows ?(cron), uid 0: exited on signal 11 
>> (core dumped)? 
> 
> Based on your symptoms, it looks like something in the restart commands
> file for root causes the shell to crash... 
> 
> What shell are you using for root? 
> 

Hi Roland, thank you for the reply. 

I have tested with bash, sh and csh. It seems the child process forked 
simply die irrespective of the shell. 

There  is no change in the dot files for root:
[root@tds sagara]# diff /root/.cshrc /usr/src/etc/root/dot.cshrc
[root@tds sagara]# diff /root/.login /usr/src/etc/root/dot.login
[root@tds sagara]# diff /root/.profile /usr/src/etc/root/dot.profile 

Here is the log message for "su -l":
Jul  2 12:38:17 tds kernel: pid 943 (su), uid 0: exited on signal 11 

Btw, what is "restart commands file for root"? 

Regards
Sagara
From Andre.Albsmeier at siemens.com  Thu Jul  2 05:28:57 2009
From: Andre.Albsmeier at siemens.com (Andre Albsmeier)
Date: Thu Jul  2 05:29:03 2009
Subject: net/iwi-firmware refuses to build on 7.2-STABLE
In-Reply-To: <4A4BC709.6060709@freebsd.org>
References: <20090701193410.GA19202@curry.mchp.siemens.de>
	<4A4BC709.6060709@freebsd.org>
Message-ID: <20090702050212.GA21954@curry.mchp.siemens.de>

On Wed, 01-Jul-2009 at 13:28:57 -0700, Sam Leffler wrote:
> Andre Albsmeier wrote:
> > Today I wanted to build net/iwi-firmware on 7.2-STABLE and I got
> > 
> > ===>  iwi-firmware-2.4_8 is configured with iwicontrol(8) which you don't need, use 'make rmconfig' and uncheck CONTROL.
> > 
> > While the firmware itself is in the base system, iwicontrol(8)
> > is not. The port should be modified to cope with this but I
> > have no idea in what way. Some ideas:
> > 
> > 1. Remove the build restrictions
> > 2. Just build iwicontrol on systems where the fw is not needed
> > 3. Make an extra port just to build iwicontrol
> > 4. ???
> > 
> > Any suggestions? Thanks,
> 
> man iwi; the firmware is automatically loaded by the driver

Yes, I know.  I don't want to load the firmware, I want to
query the state of the hardware switch which enables the
transmitter (iwicontrol iwi0 -r).

Thanks,

	-Andre

-- 
Never argue with an idiot. They drag you down to
their level, then beat you with their experience.
From rsmith at xs4all.nl  Thu Jul  2 06:27:41 2009
From: rsmith at xs4all.nl (Roland Smith)
Date: Thu Jul  2 06:27:48 2009
Subject: FreeBSD child process die for root
In-Reply-To: <20090702012352.17934.qmail@us1.tomahawkonline.net>
References: <20090701070409.7740.qmail@us1.tomahawkonline.net>
	<20090701174930.GC37269@slackbox.xs4all.nl>
	<20090702012352.17934.qmail@us1.tomahawkonline.net>
Message-ID: <20090702062738.GA58158@slackbox.xs4all.nl>

On Wed, Jul 01, 2009 at 08:23:52PM -0500, Sagara Wijetunga wrote:
> Roland Smith writes: 
> 
> > On Wed, Jul 01, 2009 at 02:04:09AM -0500, Sagara Wijetunga wrote:
> >> Hi  
> >> 
> >> I'm Sagara Wijetunga from Tomahawk Computers from Singapore, makers of the 
> >> Tomahawk Desktop, a FreeBSD based desktop operating system 
> >> (http://www.tomahawkcomputers.com/) which is free for personal use.  
> >> 
> >> Ever since we upgraded our Tomahawk Core OS to the FreeBSD 7.2 sources, we 
> >> experienced a strange issue as follows:  
> >> 
> >>    1. The root cannot login from the console, child process forked die with 
> >> ?uid 0: exited on signal 11?.
> >>    2. Normal users can log in, no issue.
> >>    3. Normal users can type ?su? and become root, but ?su -l? 
> >> results child process forked die with ?uid 0: exited on signal 11?.
> >>    4. The /var/log/messages shows ?(cron), uid 0: exited on signal 11 
> >> (core dumped)? 
> > 
> > Based on your symptoms, it looks like something in the restart commands
> > file for root causes the shell to crash... 
> > 
> > What shell are you using for root? 
> > 
> 
> Hi Roland, thank you for the reply. 
> 
> I have tested with bash, sh and csh. It seems the child process forked 
> simply die irrespective of the shell. 

Ok, so it's probably not a shell problem
 
> There  is no change in the dot files for root:
> [root@tds sagara]# diff /root/.cshrc /usr/src/etc/root/dot.cshrc
> [root@tds sagara]# diff /root/.login /usr/src/etc/root/dot.login
> [root@tds sagara]# diff /root/.profile /usr/src/etc/root/dot.profile 

/root/.login executes the fortune program. Can you su to root and then
run '/usr/games/fortune -s'?

> Here is the log message for "su -l":
> Jul  2 12:38:17 tds kernel: pid 943 (su), uid 0: exited on signal 11 

It could be a hardware problem. Signal 11 can be a sign of bad memory.
Can you reproduce the problem on multiple machines?

> Btw, what is "restart commands file for root"? 

The "rc" in .shrc stands for restart commands.

Roland
-- 
R.F.Smith                                   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090702/1d138598/attachment.pgp
From sagara at tomahawk.com.sg  Thu Jul  2 07:34:59 2009
From: sagara at tomahawk.com.sg (Sagara Wijetunga)
Date: Thu Jul  2 07:35:05 2009
Subject: FreeBSD child process die for root
In-Reply-To: <20090702062738.GA58158@slackbox.xs4all.nl>
References: <20090701070409.7740.qmail@us1.tomahawkonline.net>
	<20090701174930.GC37269@slackbox.xs4all.nl>
	<20090702012352.17934.qmail@us1.tomahawkonline.net>
	<20090702062738.GA58158@slackbox.xs4all.nl>
Message-ID: <20090702041707.19651.qmail@us1.tomahawkonline.net>

Roland Smith writes: 

>> 
>> I have tested with bash, sh and csh. It seems the child process forked 
>> simply die irrespective of the shell. 
> 
> Ok, so it's probably not a shell problem
>  
>> There  is no change in the dot files for root:
>> [root@tds sagara]# diff /root/.cshrc /usr/src/etc/root/dot.cshrc
>> [root@tds sagara]# diff /root/.login /usr/src/etc/root/dot.login
>> [root@tds sagara]# diff /root/.profile /usr/src/etc/root/dot.profile 
> 
> /root/.login executes the fortune program. Can you su to root and then
> run '/usr/games/fortune -s'? 
> 

/root/.login is completely commented out. 

[root@tds sagara]# /usr/games/fortune -s
After years of research, scientists recently reported that there is,
indeed, arroz in Spanish Harlem. 

Different runs displays different messages. 


>> Here is the log message for "su -l":
>> Jul  2 12:38:17 tds kernel: pid 943 (su), uid 0: exited on signal 11 
> 
> It could be a hardware problem. Signal 11 can be a sign of bad memory.
> Can you reproduce the problem on multiple machines? 
> 

I have taken the hard disk out and fixed on different machines, the symptoms 
are still the same. So it may not be a hardware error. 

Regards
Sagara
From hawei at free.fr  Thu Jul  2 08:13:08 2009
From: hawei at free.fr (Harald Weis)
Date: Thu Jul  2 08:13:15 2009
Subject: Vulnerability question
In-Reply-To: <20090701212420.GA43923@slackbox.xs4all.nl>
References: <20090701111437.GB1846@pollux.local.net>
	<20090701170012.CAF421CC09@ptavv.es.net>
	<20090701210528.GC1846@pollux.local.net>
	<20090701212420.GA43923@slackbox.xs4all.nl>
Message-ID: <20090702081302.GA1476@pollux.local.net>

On Wed, Jul 01, 2009 at 11:24:20PM +0200, Roland Smith wrote:
<snip>

Thank you very much indeed, Roland, for your explanation.

Harald
From freebsd at chillt.de  Thu Jul  2 09:32:06 2009
From: freebsd at chillt.de (Bartosz Fabianowski)
Date: Thu Jul  2 09:32:32 2009
Subject: net/iwi-firmware refuses to build on 7.2-STABLE
In-Reply-To: <20090702050212.GA21954@curry.mchp.siemens.de>
References: <20090701193410.GA19202@curry.mchp.siemens.de>	<4A4BC709.6060709@freebsd.org>
	<20090702050212.GA21954@curry.mchp.siemens.de>
Message-ID: <4A4C78F9.1090804@chillt.de>

iwicontrol is not used on 7 any more. You can use sysctl to query the
hardware switch instead:

sysctl dev.iwi.0.radio

- Bartosz
From ivan.kurzweg at gmail.com  Thu Jul  2 16:36:12 2009
From: ivan.kurzweg at gmail.com (ikare.run)
Date: Thu Jul  2 16:36:19 2009
Subject: FBSD on Xen 3.1
Message-ID: <4A4CDB9C.2090909@gmail.com>

Hi

I need to virtualize FBSD7 on Xen3.1/i386/NetBSD5_Dom0/HVM ....

Does anyone have a solution for the "xen bug 622", aka "BTX halted" ?

Thks

PS : the xen server will also host OpenBSD and .. and M$ .. so HVM is 
needed..

-- 
Ivan Kurzweg
Mail : ivan.kurzweg@gmail.com
Web : http://www.kurzweg.info
-------------------
Citation aleatoire :

Si la certitude est plus apaisante, le doute est plus noble.
[Sal?mah M?ssa - L'education]



From rsmith at xs4all.nl  Thu Jul  2 17:57:26 2009
From: rsmith at xs4all.nl (Roland Smith)
Date: Thu Jul  2 17:57:34 2009
Subject: FreeBSD child process die for root
In-Reply-To: <20090702041707.19651.qmail@us1.tomahawkonline.net>
References: <20090701070409.7740.qmail@us1.tomahawkonline.net>
	<20090701174930.GC37269@slackbox.xs4all.nl>
	<20090702012352.17934.qmail@us1.tomahawkonline.net>
	<20090702062738.GA58158@slackbox.xs4all.nl>
	<20090702041707.19651.qmail@us1.tomahawkonline.net>
Message-ID: <20090702175722.GA75808@slackbox.xs4all.nl>

On Wed, Jul 01, 2009 at 11:17:07PM -0500, Sagara Wijetunga wrote:
> Roland Smith writes: 
> 
> >> 
> >> I have tested with bash, sh and csh. It seems the child process forked 
> >> simply die irrespective of the shell. 
> > 
> > Ok, so it's probably not a shell problem
> >  
> >> There  is no change in the dot files for root:
> >> [root@tds sagara]# diff /root/.cshrc /usr/src/etc/root/dot.cshrc
> >> [root@tds sagara]# diff /root/.login /usr/src/etc/root/dot.login
> >> [root@tds sagara]# diff /root/.profile /usr/src/etc/root/dot.profile 
> > 
> > /root/.login executes the fortune program. Can you su to root and then
> > run '/usr/games/fortune -s'? 
> > 
> 
> /root/.login is completely commented out. 

You're right. I missed that. :-)

> >> Here is the log message for "su -l":
> >> Jul  2 12:38:17 tds kernel: pid 943 (su), uid 0: exited on signal 11 

Is there anything else from su in the logfiles? That might help narrow down
where it crashes.

Are you using the standard FreeBSD su? If not, check your
modifications. Does the version of the userland that you are using match
the version of the kernel?

I've verified that 'su -l' works fine on FreeBSD 7.2-RELEASE-p2 on the
amd64 architecture. 

What you could do is run 'su -l' under a debugger. 

> > It could be a hardware problem. Signal 11 can be a sign of bad memory.
> > Can you reproduce the problem on multiple machines? 
> 
> I have taken the hard disk out and fixed on different machines, the symptoms 
> are still the same. So it may not be a hardware error. 

Ok. So it is probably a software bug then.

Roland
-- 
R.F.Smith                                   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090702/7eea335f/attachment.pgp
From Andre.Albsmeier at siemens.com  Thu Jul  2 18:59:04 2009
From: Andre.Albsmeier at siemens.com (Andre Albsmeier)
Date: Thu Jul  2 18:59:12 2009
Subject: net/iwi-firmware refuses to build on 7.2-STABLE
In-Reply-To: <4A4C78F9.1090804@chillt.de>
References: <20090701193410.GA19202@curry.mchp.siemens.de>
	<4A4BC709.6060709@freebsd.org>
	<20090702050212.GA21954@curry.mchp.siemens.de>
	<4A4C78F9.1090804@chillt.de>
Message-ID: <20090702185901.GA46427@curry.mchp.siemens.de>

On Thu, 02-Jul-2009 at 11:08:09 +0200, Bartosz Fabianowski wrote:
> iwicontrol is not used on 7 any more. You can use sysctl to query the
> hardware switch instead:
> 
> sysctl dev.iwi.0.radio

That did it, thanks a lot,

	-Andre
From santosh at fastsoft.com  Thu Jul  2 19:19:44 2009
From: santosh at fastsoft.com (Santosh Rao Gururajan)
Date: Thu Jul  2 19:19:50 2009
Subject: Patch for FreeBSD 7.0 deadlock
Message-ID: <D13CB108B048BD47B69C0CA1E0B5C032C4C89D@hq-es.FASTSOFT.COM>

> Hi Kris.
> I currently cannot upgrade from FreeBSD 7.0 because it breaks some
other
> parts of my project and also for some other non-technical reasons. It
> would be a lot easier for me if I had the changeset. So if it is not
too
> much bother can you send me a link to the changeset/MFC?
> Thanks,
> -santosh

Hi,
Can someone please point me to the patch for this problem? Again, I
cannot upgrade to later versions of FreeBSD and this issue has become a
big problem for me.
I would really appreciate a response.
Thanks,
-santosh
From mandrews at bit0.com  Thu Jul  2 20:08:29 2009
From: mandrews at bit0.com (Mike Andrews)
Date: Thu Jul  2 20:08:36 2009
Subject: kern/135412: [zfs] [nfs] zfs(v13)+nfs and open(..., 
 O_WRONLY|O_CREAT|O_EXCL, ...)
In-Reply-To: <E1MLw2u-000Bi0-K1@kabab.cs.huji.ac.il>
References: <E1MLbya-000P4e-Qd@kabab.cs.huji.ac.il>
	<20090630155437.GA42783@a91-153-125-115.elisa-laajakaista.fi>
	<4A4A6358.1010806@bit0.com>
	<20090701090818.GA1391@a91-153-125-115.elisa-laajakaista.fi>
	<E1MLw2u-000Bi0-K1@kabab.cs.huji.ac.il>
Message-ID: <alpine.BSF.2.00.0907021607130.63453@beast.int.bit0.com>

On Wed, 1 Jul 2009, Danny Braniss wrote:

>> On 2009-06-30, Mike Andrews wrote:
>>> Jaakko Heinonen wrote:
>>>> On 2009-06-30, Danny Braniss wrote:
>>>>> 	This pr is realy holding me back, I can't upgrade this server, and
>>>>> telling serveral tens of users to us cp, etc is not an option. The open
>>>>> works fine if not using O_EXCL.
>>>>
>>>> I guess that r185586 needs to be MFCd to stable/7. Here's an untested
>>>> patch against stable/7:
>>>
>>> The patch doesn't help over here, sorry.
>>>
>>> Simply doing 'touch' or 'mv' to an NFSv3 mount (using either a v6 or v13
>>> zpool) is the test case I've been using; touch doesn't even use O_EXCL as
>>> far as I can tell.
>>
>> I could reproduce the problem with O_EXCL and verified that the patch
>> fixes it. However I couldn't reproduce the problem you are seeing with
>> touch and mv.
>
> same here, touch worked before too - so i think it's unrelated,
> btw, it seems that the problem does not exist on i386, though
> I'm pretty sure I tried there too, oh well,
>
> thanks!
> 	danny

I'm not sure if what was commited to stable/7 yesterday is substantially 
different from that patch (and if not, what in the world I was doing 
wrong/stupid in testing), but everything now works for me... thanks :)

From unixmania at gmail.com  Thu Jul  2 23:54:08 2009
From: unixmania at gmail.com (Carlos A. M. dos Santos)
Date: Thu Jul  2 23:54:14 2009
Subject: FreeBSD child process die for root
In-Reply-To: <20090702041707.19651.qmail@us1.tomahawkonline.net>
References: <20090701070409.7740.qmail@us1.tomahawkonline.net>
	<20090701174930.GC37269@slackbox.xs4all.nl>
	<20090702012352.17934.qmail@us1.tomahawkonline.net>
	<20090702062738.GA58158@slackbox.xs4all.nl>
	<20090702041707.19651.qmail@us1.tomahawkonline.net>
Message-ID: <e71790db0907021628k19f9ebxcc89f94d56a903cd@mail.gmail.com>

On Thu, Jul 2, 2009 at 1:17 AM, Sagara Wijetunga<sagara@tomahawk.com.sg> wrote:
> Roland Smith writes:
>> It could be a hardware problem. Signal 11 can be a sign of bad memory.
>> Can you reproduce the problem on multiple machines?
>
> I have taken the hard disk out and fixed on different machines, the symptoms
> are still the same. So it may not be a hardware error.
> Regards
> Sagara

Try to *rebuild* the system on another machine. Signal 11 is usually
associated to bad hardware (RAM) so if you build FreeBSD on faulty
hardware the resulting program may be broken.

Try to debug the "login" program:

(become root)
# cd /usr/src/usr.bin/login
# make clean
# make CFLAGS=-g
# gdb /usr/obj/usr/src/usr.bin/login/login
(supposing that "sagara" is your user name)
#run sagara
(fill-in the password name, if requested)

If the signal 11 is caught, issue "bt" command in gcc. It will show
you where the break happened.

-- 
My preferred quotation of Robert Louis Stevenson is "You cannot
make an omelette without breaking eggs". Not because I like the
omelettes, but because I like the sound of eggs being broken.
From kamikaze at bsdforen.de  Fri Jul  3 09:21:44 2009
From: kamikaze at bsdforen.de (Dominic Fandrey)
Date: Fri Jul  3 09:21:53 2009
Subject: mergemaster merge left/right
Message-ID: <4A4DC67C.3010804@bsdforen.de>

I'd really like mergemaster to tell me whether the left
or the right side is the new file.

# $FreeBSD: src/etc/devd.conf,v 1.38. |	# $FreeBSD: src/etc/devd.conf,v 1.38.

Like this I have no idea which one to pick.
From ianjhart at ntlworld.com  Fri Jul  3 09:22:20 2009
From: ianjhart at ntlworld.com (Ian J Hart)
Date: Fri Jul  3 09:22:29 2009
Subject: trap 12
Message-ID: <20090703100627.197838cphjnil82s@10.248.192.16>

Is this likely to be hardware? Details will follow if not.

[copied from a screen dump]

Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0x0
fault code = supervisor write data, page not present
instruction pointer = 0x8:0xffffffff807c6c12
stack pointer = 0x10:0xffffffff510e7890
frame pointer = 0x10:0xffffff00054a6c90
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, long 1 def32 0, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 75372 (printf)
trap number = 12
panic: page fault
cpuid = 1
uptime: 8m2s
Cannot dump. No dump device defined.


-- 
ian j hart


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


From dan.naumov at gmail.com  Fri Jul  3 09:28:26 2009
From: dan.naumov at gmail.com (Dan Naumov)
Date: Fri Jul  3 09:28:35 2009
Subject: mergemaster merge left/right
In-Reply-To: <4A4DC67C.3010804@bsdforen.de>
References: <4A4DC67C.3010804@bsdforen.de>
Message-ID: <cf9b1ee00907030228w704acaf7u4925b17f73bb9a09@mail.gmail.com>

Speaking of mergemaster, it would be really really nice to have
"freebsd-update install" get the following functionality/options from
mergemaster:

-i   Automatically install any files that do not exist in the
destination directory.
-F   If the files differ only by VCS Id ($FreeBSD) install the new file.

This would help avoid having to manually approve installation of
hundreds of files in /etc when you upgrade to new releases using
freebsd-update.

- Sincerely,
Dan Naumov



On Fri, Jul 3, 2009 at 11:51 AM, Dominic Fandrey<kamikaze@bsdforen.de> wrote:
> I'd really like mergemaster to tell me whether the left
> or the right side is the new file.
>
> # $FreeBSD: src/etc/devd.conf,v 1.38. | # $FreeBSD: src/etc/devd.conf,v 1.38.
>
> Like this I have no idea which one to pick.
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>
From cristiano.deana at gmail.com  Fri Jul  3 10:03:24 2009
From: cristiano.deana at gmail.com (Cristiano Deana)
Date: Fri Jul  3 10:03:31 2009
Subject: mergemaster merge left/right
In-Reply-To: <4A4DC67C.3010804@bsdforen.de>
References: <4A4DC67C.3010804@bsdforen.de>
Message-ID: <d8a4930a0907030234v7359642ehe0cf2a86ad7ef6d4@mail.gmail.com>

On Fri, Jul 3, 2009 at 10:51 AM, Dominic Fandrey<kamikaze@bsdforen.de> wrote:

> I'd really like mergemaster to tell me whether the left
> or the right side is the new file.
>
> # $FreeBSD: src/etc/devd.conf,v 1.38. | # $FreeBSD: src/etc/devd.conf,v 1.38.

"From" -> "To"

The new one is *always* the right one.

-- 
Cris, member of G.U.F.I
Italian FreeBSD User Group
http://www.gufi.org/
From kamikaze at bsdforen.de  Fri Jul  3 10:14:13 2009
From: kamikaze at bsdforen.de (Dominic Fandrey)
Date: Fri Jul  3 10:14:20 2009
Subject: good old intel troubles
Message-ID: <4A4DD9E9.6080206@bsdforen.de>

Now that the intel driver is stable and performs well, again, it's
time to start complainig about all the things that still do not work.

This is basically going to the console and back. Well, it actually
works but X will entirely lock up unless the mouse is in motion.
It's not hard to imagine that this is really bad. With violent mouse
movement I can get glxgears to render 0.3 frames per second.
That's it. 1 frame every 3 seconds.

Back on the console everything is fine, so it's really just X
misbehaving. No scheduling issue or the like.

Oh, btw, when I switch to the Konsole I get the following message
on my dmesg.
error: [drm:pid1318:i915_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0

My system is a core2duo (amd64) running RELENG_7 (sources are from
~2 hours ago).

Maybe this snippet from my Xorg.0.log is also of interest:
(--) Using syscons driver with X support (version 2.0)
(--) using VT number 9
(--) PCI:*(0@0:2:0) Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller rev 12, Mem @ 0xe4600000/1048576, 0xd0000000/268435456, I/O @ 0x00004000/8, BIOS @ 0x????????/65536
(--) PCI: (0@0:2:1) Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller rev 12, Mem @ 0xe4700000/1048576

I'm running X without HAL.
(**) Option "AllowEmptyInput" "off"
(**) Option "AutoAddDevices" "off"
From kamikaze at bsdforen.de  Fri Jul  3 10:17:40 2009
From: kamikaze at bsdforen.de (Dominic Fandrey)
Date: Fri Jul  3 10:17:47 2009
Subject: mergemaster merge left/right
In-Reply-To: <d8a4930a0907030234v7359642ehe0cf2a86ad7ef6d4@mail.gmail.com>
References: <4A4DC67C.3010804@bsdforen.de>
	<d8a4930a0907030234v7359642ehe0cf2a86ad7ef6d4@mail.gmail.com>
Message-ID: <4A4DDAB8.3080804@bsdforen.de>

Cristiano Deana wrote:
> On Fri, Jul 3, 2009 at 10:51 AM, Dominic Fandrey<kamikaze@bsdforen.de> wrote:
> 
>> I'd really like mergemaster to tell me whether the left
>> or the right side is the new file.
>>
>> # $FreeBSD: src/etc/devd.conf,v 1.38. | # $FreeBSD: src/etc/devd.conf,v 1.38.
> 
> "From" -> "To"
> 
> The new one is *always* the right one.

I don't have to merge files all that often. mergmaster is pretty easy to
use, apart from the lack of that information. It wouldn't be very hard to
print "<old file> | <new file>" at the beginning of a merge.

From lstewart at freebsd.org  Fri Jul  3 11:23:05 2009
From: lstewart at freebsd.org (Lawrence Stewart)
Date: Fri Jul  3 11:23:13 2009
Subject: good old intel troubles
In-Reply-To: <4A4DD9E9.6080206@bsdforen.de>
References: <4A4DD9E9.6080206@bsdforen.de>
Message-ID: <4A4DE53D.2010704@freebsd.org>

Dominic Fandrey wrote:
> Now that the intel driver is stable and performs well, again, it's
> time to start complainig about all the things that still do not work.
> 
> This is basically going to the console and back. Well, it actually
> works but X will entirely lock up unless the mouse is in motion.
> It's not hard to imagine that this is really bad. With violent mouse
> movement I can get glxgears to render 0.3 frames per second.
> That's it. 1 frame every 3 seconds.
> 
> Back on the console everything is fine, so it's really just X
> misbehaving. No scheduling issue or the like.
> 

These issues have been recently addressed in 8-CURRENT. I assume some 
MFCs will happen at some point.

Cheers,
Lawrence
From rnoland at FreeBSD.org  Fri Jul  3 12:22:50 2009
From: rnoland at FreeBSD.org (Robert Noland)
Date: Fri Jul  3 12:22:59 2009
Subject: mergemaster merge left/right
In-Reply-To: <4A4DC67C.3010804@bsdforen.de>
References: <4A4DC67C.3010804@bsdforen.de>
Message-ID: <1246623757.1855.54.camel@balrog.2hip.net>

On Fri, 2009-07-03 at 10:51 +0200, Dominic Fandrey wrote:
> I'd really like mergemaster to tell me whether the left
> or the right side is the new file.
> 
> # $FreeBSD: src/etc/devd.conf,v 1.38. |	# $FreeBSD: src/etc/devd.conf,v 1.38.
> 
> Like this I have no idea which one to pick.

The right hand side is always the new file.

robert.

> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
-- 
Robert Noland <rnoland@FreeBSD.org>
FreeBSD
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090703/a3e984eb/attachment.pgp
From rnoland at FreeBSD.org  Fri Jul  3 12:27:17 2009
From: rnoland at FreeBSD.org (Robert Noland)
Date: Fri Jul  3 12:27:23 2009
Subject: trap 12
In-Reply-To: <20090703100627.197838cphjnil82s@10.248.192.16>
References: <20090703100627.197838cphjnil82s@10.248.192.16>
Message-ID: <1246624029.1855.58.camel@balrog.2hip.net>

On Fri, 2009-07-03 at 10:06 +0100, Ian J Hart wrote:
> Is this likely to be hardware? Details will follow if not.
> 
> [copied from a screen dump]
> 
> Fatal trap 12: page fault while in kernel mode
> cpuid = 1; apic id = 01
> fault virtual address = 0x0
> fault code = supervisor write data, page not present
> instruction pointer = 0x8:0xffffffff807c6c12
> stack pointer = 0x10:0xffffffff510e7890
> frame pointer = 0x10:0xffffff00054a6c90
> code segment = base 0x0, limit 0xfffff, type 0x1b
> = DPL 0, pres 1, long 1 def32 0, gran 1
> processor eflags = interrupt enabled, resume, IOPL = 0
> current process = 75372 (printf)
> trap number = 12
> panic: page fault
> cpuid = 1
> uptime: 8m2s
> Cannot dump. No dump device defined.
> 

I would doubt it.  Are you using drm, with the radeon driver?  There are
a few corner cases where this can happen.
http://people.freebsd.org/~rnoland/drm_radeon-copyin-fix-try2.patch
should help if this is the case.

robert.

-- 
Robert Noland <rnoland@FreeBSD.org>
FreeBSD
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090703/6de24031/attachment.pgp
From rnoland at FreeBSD.org  Fri Jul  3 12:35:26 2009
From: rnoland at FreeBSD.org (Robert Noland)
Date: Fri Jul  3 12:35:32 2009
Subject: good old intel troubles
In-Reply-To: <4A4DD9E9.6080206@bsdforen.de>
References: <4A4DD9E9.6080206@bsdforen.de>
Message-ID: <1246624516.1855.65.camel@balrog.2hip.net>

On Fri, 2009-07-03 at 12:14 +0200, Dominic Fandrey wrote:
> Now that the intel driver is stable and performs well, again, it's
> time to start complainig about all the things that still do not work.
> 
> This is basically going to the console and back. Well, it actually
> works but X will entirely lock up unless the mouse is in motion.
> It's not hard to imagine that this is really bad. With violent mouse
> movement I can get glxgears to render 0.3 frames per second.
> That's it. 1 frame every 3 seconds.
> 
> Back on the console everything is fine, so it's really just X
> misbehaving. No scheduling issue or the like.
> 
> Oh, btw, when I switch to the Konsole I get the following message
> on my dmesg.
> error: [drm:pid1318:i915_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0

This is still harmless, though I hope that I have caught most of the
cases where it occurs.  Userland (mesa) may still call this ioctl with
the wrong or both crtc's though.  It is converted back to a debug
message in HEAD.

> My system is a core2duo (amd64) running RELENG_7 (sources are from
> ~2 hours ago).

This is all fixed in HEAD.  It is waiting jhb@ to MFC r194644 to get
-STABLE fixed up.  I have additional MFC's to cleanup vblank support
issues, but the primary issue is that msi interrupts don't work after a
vt switch without the above MFC.

robert.

> Maybe this snippet from my Xorg.0.log is also of interest:
> (--) Using syscons driver with X support (version 2.0)
> (--) using VT number 9
> (--) PCI:*(0@0:2:0) Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller rev 12, Mem @ 0xe4600000/1048576, 0xd0000000/268435456, I/O @ 0x00004000/8, BIOS @ 0x????????/65536
> (--) PCI: (0@0:2:1) Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller rev 12, Mem @ 0xe4700000/1048576
> 
> I'm running X without HAL.
> (**) Option "AllowEmptyInput" "off"
> (**) Option "AutoAddDevices" "off"
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
-- 
Robert Noland <rnoland@FreeBSD.org>
FreeBSD
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090703/9dc66ce4/attachment.pgp
From Johan at double-l.nl  Fri Jul  3 12:43:43 2009
From: Johan at double-l.nl (Johan Hendriks)
Date: Fri Jul  3 12:43:51 2009
Subject: From 7.1 to 7.2 ezjail jails mergemaster not working.
Message-ID: <57200BF94E69E54880C9BB1AF714BBCB0111B7@w2003s01.double-l.local>

Hello all
I have just updated my 7.1 machine to 7.2.
I have updated the 7.1 machine several times with a builworld to follow the Security issues, and always use the same approuch.

cd /us/src
make cleanworld && make buildworld && make kernel
mergemaster -p
shutdown now
cd /usr/src
make installworld
mergemaster -iU 

ezjail-admin update -i
mergemaster -iU -D /usr/jails/jail1
mergemaster -iU -D /usr/jails/jail2

this has been working from 7.0 where this machine came from.

After my update to 7.2 and after the ezjail-admin update -i i did the mergemaster step and here it goes wrong.

this is what i get after the command mergemaster -iU -D /usr/jails/jail1

There is no installed version of ./boot/device.hints

install: mkdir /usr.jails/jail1//boot : File exists
install: /usr/jails/jail1//boot: no such file or directory
*** FATAL ERROR : unable to install ./boot/device.hints to /usr/jails/jail1//boot.
 
what am i doing wrong or what am i forgotten.

Thanks for your time.
regards,
Johan Hendriks
From hausen at punkt.de  Fri Jul  3 14:25:31 2009
From: hausen at punkt.de (Patrick M. Hausen)
Date: Fri Jul  3 14:25:43 2009
Subject: What is /boot/kernel/*.symbols?
Message-ID: <20090703142528.GA11039@hugo10.ka.punkt.de>

Hi, all, 

When I upgraded some of our machines from 6.x to 7.2
I noticed that the root filesystems seemed to fill up.

I thought this might come from

makeoptions     DEBUG=-g

in the kernel config, but somehow that doesn't make sense,
since our older systems have the same option present.

6.3-System:
-----------
makeoptions     DEBUG=-g

$ du -sk /boot/kernel
27920	/boot/kernel

No *.symbols files in /boot/kernel.


7.2-System:
-----------
makeoptions     DEBUG=-g

$ du -sk /boot/kernel
214778	/boot/kernel

Lots of those files filling /boot/kernel.


On a current server with 512 MB /, the filesystem is at
97% after installing a new kernel twice. Can I get rid of
these files somehow or are they necessary, in which case
I will need way bigger root filesystems?

I mean, get rid automatically and never install them again.
I know the chflags and rm commands ;-) But then the question
of they are needed is still open.


Thanks,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
info@punkt.de       http://www.punkt.de
Gf: J?rgen Egeling      AG Mannheim 108285
From kamikaze at bsdforen.de  Fri Jul  3 14:25:52 2009
From: kamikaze at bsdforen.de (Dominic Fandrey)
Date: Fri Jul  3 14:26:03 2009
Subject: mergemaster merge left/right
In-Reply-To: <1246623757.1855.54.camel@balrog.2hip.net>
References: <4A4DC67C.3010804@bsdforen.de>
	<1246623757.1855.54.camel@balrog.2hip.net>
Message-ID: <4A4E14ED.5010309@bsdforen.de>

Robert Noland wrote:
> On Fri, 2009-07-03 at 10:51 +0200, Dominic Fandrey wrote:
>> I'd really like mergemaster to tell me whether the left
>> or the right side is the new file.
>>
>> # $FreeBSD: src/etc/devd.conf,v 1.38. |	# $FreeBSD: src/etc/devd.conf,v 1.38.
>>
>> Like this I have no idea which one to pick.
> 
> The right hand side is always the new file.

I know. Trial and error can tell you that. But I want
mergemaster to tell me.
From rick at havokmon.com  Fri Jul  3 14:28:41 2009
From: rick at havokmon.com (Rick Romero)
Date: Fri Jul  3 14:28:48 2009
Subject: kern/135412: [zfs] [nfs] zfs(v13)+nfs and open(..., 
	O_WRONLY|O_CREAT|O_EXCL, ...)
In-Reply-To: <alpine.BSF.2.00.0907021607130.63453@beast.int.bit0.com>
References: <E1MLbya-000P4e-Qd@kabab.cs.huji.ac.il>
	<20090630155437.GA42783@a91-153-125-115.elisa-laajakaista.fi>
	<4A4A6358.1010806@bit0.com>
	<20090701090818.GA1391@a91-153-125-115.elisa-laajakaista.fi>
	<E1MLw2u-000Bi0-K1@kabab.cs.huji.ac.il>
	<alpine.BSF.2.00.0907021607130.63453@beast.int.bit0.com>
Message-ID: <1246631215.3268.10.camel@rickxp>

On Thu, 2009-07-02 at 16:08 -0400, Mike Andrews wrote:
> On Wed, 1 Jul 2009, Danny Braniss wrote:
> 
> >> On 2009-06-30, Mike Andrews wrote:
> >>> Jaakko Heinonen wrote:
> >>>> On 2009-06-30, Danny Braniss wrote:
> >>>>> 	This pr is realy holding me back, I can't upgrade this server, and
> >>>>> telling serveral tens of users to us cp, etc is not an option. The open
> >>>>> works fine if not using O_EXCL.
> >>>>
> >>>> I guess that r185586 needs to be MFCd to stable/7. Here's an untested
> >>>> patch against stable/7:
> >>>
> >>> The patch doesn't help over here, sorry.
> >>>
> >>> Simply doing 'touch' or 'mv' to an NFSv3 mount (using either a v6 or v13
> >>> zpool) is the test case I've been using; touch doesn't even use O_EXCL as
> >>> far as I can tell.
> >>
> >> I could reproduce the problem with O_EXCL and verified that the patch
> >> fixes it. However I couldn't reproduce the problem you are seeing with
> >> touch and mv.
> >
> > same here, touch worked before too - so i think it's unrelated,
> > btw, it seems that the problem does not exist on i386, though
> > I'm pretty sure I tried there too, oh well,
> >
> > thanks!
> > 	danny
> 
> I'm not sure if what was commited to stable/7 yesterday is substantially 
> different from that patch (and if not, what in the world I was doing 
> wrong/stupid in testing), but everything now works for me... thanks :)

Looks like it's working pretty well to me. 

It's almost not worth mentioning, but I have an old FreeBSD 4.8 server
(which is the midst of being retired) that is still having an issue
related to this.
When I edit a file with vim 7.0, it creates the swapfile with no perms
(which causes it to complain that the file already exists, and not clean
up after itself)

This only occurs from a 4.8 client, not 5.2.1, 6.2, or 7.2.  

Vim is the only program that replicates the problem on that box. touch
works, mv works, procmail works.

I only mention because maybe there's another OS, that's still supported,
that might still have the same issues.

Rick



From dimitry at andric.com  Fri Jul  3 14:35:58 2009
From: dimitry at andric.com (Dimitry Andric)
Date: Fri Jul  3 14:36:05 2009
Subject: What is /boot/kernel/*.symbols?
In-Reply-To: <20090703142528.GA11039@hugo10.ka.punkt.de>
References: <20090703142528.GA11039@hugo10.ka.punkt.de>
Message-ID: <4A4E174A.1050207@andric.com>

On 2009-07-03 16:25, Patrick M. Hausen wrote:
> On a current server with 512 MB /, the filesystem is at
> 97% after installing a new kernel twice. Can I get rid of
> these files somehow or are they necessary, in which case
> I will need way bigger root filesystems?
> 
> I mean, get rid automatically and never install them again.
> I know the chflags and rm commands ;-) But then the question
> of they are needed is still open.

You can find this in /usr/src/UPDATING:

20060118:
        This actually occured some time ago, but installing the kernel
        now also installs a bunch of symbol files for the kernel modules.
        This increases the size of /boot/kernel to about 67Mbytes. You
        will need twice this if you will eventually back this up to kernel.old
        on your next install.
        If you have a shortage of room in your root partition, you should add
        -DINSTALL_NODEBUG to your make arguments or add INSTALL_NODEBUG="yes"
        to your /etc/make.conf.

However, you should consider increasing the size of your root
partition, if possible.  It can be extremely handy to have symbol files
available whenever there's a crash.  :)
From lstewart at freebsd.org  Fri Jul  3 14:36:46 2009
From: lstewart at freebsd.org (Lawrence Stewart)
Date: Fri Jul  3 14:36:53 2009
Subject: mergemaster merge left/right
In-Reply-To: <4A4E14ED.5010309@bsdforen.de>
References: <4A4DC67C.3010804@bsdforen.de>	<1246623757.1855.54.camel@balrog.2hip.net>
	<4A4E14ED.5010309@bsdforen.de>
Message-ID: <4A4E1769.3090209@freebsd.org>

Dominic Fandrey wrote:
> Robert Noland wrote:
>> On Fri, 2009-07-03 at 10:51 +0200, Dominic Fandrey wrote:
>>> I'd really like mergemaster to tell me whether the left
>>> or the right side is the new file.
>>>
>>> # $FreeBSD: src/etc/devd.conf,v 1.38. |	# $FreeBSD: src/etc/devd.conf,v 1.38.
>>>
>>> Like this I have no idea which one to pick.
>> The right hand side is always the new file.
> 
> I know. Trial and error can tell you that. But I want
> mergemaster to tell me.

I'm sure Doug would be very happy to receive a patch to review. 
Mergemaster is a shell script so shouldn't be too difficult to hack 
something up.

Cheers,
Lawrence
From hausen at punkt.de  Fri Jul  3 14:41:35 2009
From: hausen at punkt.de (Patrick M. Hausen)
Date: Fri Jul  3 14:41:42 2009
Subject: What is /boot/kernel/*.symbols?
In-Reply-To: <4A4E174A.1050207@andric.com>
References: <20090703142528.GA11039@hugo10.ka.punkt.de>
	<4A4E174A.1050207@andric.com>
Message-ID: <20090703144121.GC11039@hugo10.ka.punkt.de>

Hello,

On Fri, Jul 03, 2009 at 04:35:54PM +0200, Dimitry Andric wrote:
> You can find this in /usr/src/UPDATING:
> 
> 20060118:
>         This actually occured some time ago, but installing the kernel
>         now also installs a bunch of symbol files for the kernel modules.
>         This increases the size of /boot/kernel to about 67Mbytes. You
>         will need twice this if you will eventually back this up to kernel.old
>         on your next install.
>         If you have a shortage of room in your root partition, you should add
>         -DINSTALL_NODEBUG to your make arguments or add INSTALL_NODEBUG="yes"
>         to your /etc/make.conf.

Thanks a lot. I've been searching the handbook and Google for at
least one hour.

> However, you should consider increasing the size of your root
> partition, if possible.  It can be extremely handy to have symbol files
> available whenever there's a crash.  :)

But I thought, they were in the kernel itself?

%file /boot/kernel/kernel
/boot/kernel/kernel: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), dynamically linked (uses shared libs), not stripped

"not stripped" - i.e. "with debug symbols". Wrong? Since when?

Thanks,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
info@punkt.de       http://www.punkt.de
Gf: J?rgen Egeling      AG Mannheim 108285
From dimitry at andric.com  Fri Jul  3 15:05:11 2009
From: dimitry at andric.com (Dimitry Andric)
Date: Fri Jul  3 15:05:19 2009
Subject: What is /boot/kernel/*.symbols?
In-Reply-To: <20090703144121.GC11039@hugo10.ka.punkt.de>
References: <20090703142528.GA11039@hugo10.ka.punkt.de>	<4A4E174A.1050207@andric.com>
	<20090703144121.GC11039@hugo10.ka.punkt.de>
Message-ID: <4A4E1E24.3020303@andric.com>

On 2009-07-03 16:41, Patrick M. Hausen wrote:
> But I thought, they were in the kernel itself?
> 
> %file /boot/kernel/kernel
> /boot/kernel/kernel: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), dynamically linked (uses shared libs), not stripped
> 
> "not stripped" - i.e. "with debug symbols". Wrong? Since when?

Well, only the debug symbols have been stripped, not any others.  If you
look in /usr/src/sys/conf/kern.post.mk, you will see this fragment:

${KERNEL_KO}: ${FULLKERNEL} ${KERNEL_KO}.symbols
	${OBJCOPY} --strip-debug --add-gnu-debuglink=${KERNEL_KO}.symbols\
	    ${FULLKERNEL} ${.TARGET}
${KERNEL_KO}.symbols: ${FULLKERNEL}
	${OBJCOPY} --only-keep-debug ${FULLKERNEL} ${.TARGET}

E.g. the debug stuff is put into the .symbols files.  The kernel itself
still contains the function and data names, though:

$ objdump -t /boot/kernel/kernel

/boot/kernel/kernel:     file format elf32-i386-freebsd

SYMBOL TABLE:
c092de00 l       .data  00000000 tmpstk
c092de58 l       .data  00000000 physfree
c092de64 l       .data  00000000 proc0uarea
[...]

If you want to build absolutely without any symbols whatsover, remove
the "makeoptions DEBUG=-g" line from your kernel config file.
From hausen at punkt.de  Fri Jul  3 15:21:52 2009
From: hausen at punkt.de (Patrick M. Hausen)
Date: Fri Jul  3 15:22:01 2009
Subject: What is /boot/kernel/*.symbols?
In-Reply-To: <4A4E1E24.3020303@andric.com>
References: <20090703142528.GA11039@hugo10.ka.punkt.de>
	<4A4E174A.1050207@andric.com>
	<20090703144121.GC11039@hugo10.ka.punkt.de>
	<4A4E1E24.3020303@andric.com>
Message-ID: <20090703152150.GE11039@hugo10.ka.punkt.de>

Hi!

On Fri, Jul 03, 2009 at 05:05:08PM +0200, Dimitry Andric wrote:
> E.g. the debug stuff is put into the .symbols files.  The kernel itself
> still contains the function and data names, though:

Understood. Thanks. No, I don't want the kernel to be void
of any information ;-)

Kind regards,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
info@punkt.de       http://www.punkt.de
Gf: J?rgen Egeling      AG Mannheim 108285
From sagara at tomahawk.com.sg  Fri Jul  3 15:45:00 2009
From: sagara at tomahawk.com.sg (Sagara Wijetunga)
Date: Fri Jul  3 15:45:07 2009
Subject: FreeBSD child process die for root
In-Reply-To: <e71790db0907021628k19f9ebxcc89f94d56a903cd@mail.gmail.com>
References: <20090701070409.7740.qmail@us1.tomahawkonline.net>
	<20090701174930.GC37269@slackbox.xs4all.nl>
	<20090702012352.17934.qmail@us1.tomahawkonline.net>
	<20090702062738.GA58158@slackbox.xs4all.nl>
	<20090702041707.19651.qmail@us1.tomahawkonline.net>
	<e71790db0907021628k19f9ebxcc89f94d56a903cd@mail.gmail.com>
Message-ID: <20090703122705.6456.qmail@us1.tomahawkonline.net>

Carlos A. M. dos Santos writes: 

> Try to debug the "login" program: 
> 
> (become root)
> # cd /usr/src/usr.bin/login
> # make clean
> # make CFLAGS=-g
> # gdb /usr/obj/usr/src/usr.bin/login/login
> (supposing that "sagara" is your user name)
> #run sagara
> (fill-in the password name, if requested) 
> 
> If the signal 11 is caught, issue "bt" command in gcc. It will show
> you where the break happened. 
> 

I tried to debug the login program, here are the results:
1. For normal users, gdb exists "Program exited normally." 

2. For root, gdb says "Login incorrect".
   On /var/log/messages:
   login: pam_acct_mgmt(): authentication error
   login: 1 LOGIN FAILURE ON ttyp0 

Btw, I have mentioned in my first post that I do not have an issue with 
normal user logins. Its only root has a problem. 

When try to "su -l" from a normal user, there is no "pam_acct_mgmt(): 
authentication error" on logs. Its only a "(su), uid 0: exited on signal 
11". 

Regards
Sagara
From sagara at tomahawk.com.sg  Fri Jul  3 16:09:42 2009
From: sagara at tomahawk.com.sg (Sagara Wijetunga)
Date: Fri Jul  3 16:09:49 2009
Subject: FreeBSD child process die for root
In-Reply-To: <20090702175722.GA75808@slackbox.xs4all.nl>
References: <20090701070409.7740.qmail@us1.tomahawkonline.net>
	<20090701174930.GC37269@slackbox.xs4all.nl>
	<20090702012352.17934.qmail@us1.tomahawkonline.net>
	<20090702062738.GA58158@slackbox.xs4all.nl>
	<20090702041707.19651.qmail@us1.tomahawkonline.net>
	<20090702175722.GA75808@slackbox.xs4all.nl>
Message-ID: <20090703125147.6649.qmail@us1.tomahawkonline.net>

Roland Smith writes: 

> 
> Is there anything else from su in the logfiles? That might help narrow down
> where it crashes. 
>
No, other than the same ?uid 0: exited on signal 11? for login, su and 
cron. What we see is after the fork, child process run for some time and 
crashes. 


> Are you using the standard FreeBSD su? If not, check your
> modifications. Does the version of the userland that you are using match
> the version of the kernel? 
> 
Our su is slightly modified. Tomorrow, I can try with standard su. Our 
userland is in some areas different. We normally try to use newer versions 
wherever possible. Our build method used to produce acceptable systems till 
FreeBSD 7.0. Its only on FreeBSD 7.2 now this issue. Other than that there 
is no other noticeable issue. 


> I've verified that 'su -l' works fine on FreeBSD 7.2-RELEASE-p2 on the
> amd64 architecture.  
> 
> What you could do is run 'su -l' under a debugger.  
> 

I just ran our normal su (without debugging info) under gdb:
gdb /usr/bin/su
GNU gdb 6.6
This GDB was configured as "i386-unknown-freebsd7.2"...
(no debugging symbols found)
(gdb) run -l
Starting program: /usr/bin/su -l
(no debugging symbols found)
(no debugging symbols found)
su: not running setuid 

Program exited with code 01. 


ls -l /usr/bin/su
 -r-sr-xr-x  1 root  freebsd  14452 Jun 28 13:50 /usr/bin/su 

This shows su is setuid root. 

Anyway, I'll run su with debugging info tomorrow. 

regards
Sagara
From sagara at tomahawk.com.sg  Sat Jul  4 12:49:39 2009
From: sagara at tomahawk.com.sg (Sagara Wijetunga)
Date: Sat Jul  4 12:49:45 2009
Subject: FreeBSD child process die for root [SOLVED]
In-Reply-To: <e71790db0907021628k19f9ebxcc89f94d56a903cd@mail.gmail.com>
References: <20090701070409.7740.qmail@us1.tomahawkonline.net>	
	<20090701174930.GC37269@slackbox.xs4all.nl>	
	<20090702012352.17934.qmail@us1.tomahawkonline.net>	
	<20090702062738.GA58158@slackbox.xs4all.nl>	
	<20090702041707.19651.qmail@us1.tomahawkonline.net>
	<e71790db0907021628k19f9ebxcc89f94d56a903cd@mail.gmail.com>
Message-ID: <4A4F51B0.2050103@tomahawk.com.sg>


   Dear all
   The issue was solved. It was a our side mistake. On a modification we
   made to libutils, we execute following line without checking whether
   the group is empty or not. In our case, it was empty, therefore,
   crashes:
   running = strdup(*(grp->gr_mem));
   So that now login, su and cron work well.
   Thank you for all those who helped us.
   Best regards
   Sagara
From rwatson at FreeBSD.org  Sat Jul  4 16:56:55 2009
From: rwatson at FreeBSD.org (Robert Watson)
Date: Sat Jul  4 16:57:01 2009
Subject: trap 12
In-Reply-To: <20090703100627.197838cphjnil82s@10.248.192.16>
References: <20090703100627.197838cphjnil82s@10.248.192.16>
Message-ID: <alpine.BSF.2.00.0907041755250.52152@fledge.watson.org>


On Fri, 3 Jul 2009, Ian J Hart wrote:

> Is this likely to be hardware? Details will follow if not.

This looks like a kernel NULL pointer deference (faulting address 0x0), which 
means it is most likely a kernel bug, although it could be triggered by a 
hardare problem.  If this early in the boot or a diskless box, hence no dump 
device?

Robert N M Watson
Computer Laboratory
University of Cambridge

>
> [copied from a screen dump]
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 1; apic id = 01
> fault virtual address = 0x0
> fault code = supervisor write data, page not present
> instruction pointer = 0x8:0xffffffff807c6c12
> stack pointer = 0x10:0xffffffff510e7890
> frame pointer = 0x10:0xffffff00054a6c90
> code segment = base 0x0, limit 0xfffff, type 0x1b
> = DPL 0, pres 1, long 1 def32 0, gran 1
> processor eflags = interrupt enabled, resume, IOPL = 0
> current process = 75372 (printf)
> trap number = 12
> panic: page fault
> cpuid = 1
> uptime: 8m2s
> Cannot dump. No dump device defined.
>
>
> -- 
> ian j hart
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
From vwe at freebsd.org  Sat Jul  4 18:30:30 2009
From: vwe at freebsd.org (vwe@freebsd.org)
Date: Sat Jul  4 18:30:38 2009
Subject: trap 12
In-Reply-To: <20090703100627.197838cphjnil82s@10.248.192.16>
References: <20090703100627.197838cphjnil82s@10.248.192.16>
Message-ID: <4A4E6273.8060905@freebsd.org>

On 12/23/-58 20:59, Ian J Hart wrote:
> Is this likely to be hardware? Details will
> follow if not.
> 
> [copied from a screen dump]
> 
> Fatal trap 12: page fault while in kernel mode
> cpuid = 1; apic id = 01
> fault virtual address = 0x0
> fault code = supervisor write data, page not present
> instruction pointer = 0x8:0xffffffff807c6c12
> stack pointer = 0x10:0xffffffff510e7890
> frame pointer = 0x10:0xffffff00054a6c90
> code segment = base 0x0, limit 0xfffff, type 0x1b
> = DPL 0, pres 1, long 1 def32 0, gran 1
> processor eflags = interrupt enabled, resume, IOPL = 0
> current process = 75372 (printf)
> trap number = 12
> panic: page fault
> cpuid = 1
> uptime: 8m2s
> Cannot dump. No dump device defined.
> 
> 

Ian,

it doesn't look like it's hardware. The message basically means, some
code in the kernel was trying to use a NULL pointer (which is by
definition a bad pointer) and tried to do something with it. Do you
experience that message often? Can you reproduce it easily?

To tell you more, we need a backtrace and I'm wondering if you can
manage to get the kernel dump being written and have us getting the
stack backtrace and more debugging information.

If, by any chance, you're using a recent 7.x system, you may want to
enable textdump(4) (AFAIR introduced before 7.1, also look at ddb(8)).
For setting up your system for kernel crashdumps, please have a look at
the handbook and savecore(8). For getting infos out of a kernel
crashdump, please check the developers handbook.

Please try to get us some debug information and we can then most likely
suggest something.

HTH

Volker
From exemys at exemys.com  Sat Jul  4 20:19:12 2009
From: exemys at exemys.com (Exemys)
Date: Sat Jul  4 20:19:23 2009
Subject: WiFi + Inputs and Outputs (Digital and Analog)
Message-ID: <899ec6d540554d574eac8c9ad47bf47b@www.hostmailing.com>

This is a message in multipart MIME format.  Your mail client should not be displaying this. Consider upgrading your mail client to view this message correctly.

From dan.naumov at gmail.com  Sat Jul  4 21:55:35 2009
From: dan.naumov at gmail.com (Dan Naumov)
Date: Sat Jul  4 21:55:44 2009
Subject: ZFS and df weirdness
Message-ID: <cf9b1ee00907041455v57b1e1eatf7b4cf0a060b938c@mail.gmail.com>

Hello list.

I have a single 2tb disk used on a 7.2-release/amd64 system with a
small part of it given to UFS and most of the disk given to a single
"simple" zfs pool with several filesystems without redundancy. I've
noticed a really weird thing regarding what "df" reports regarding the
"total space" of one of my filesystems:

atom# zpool list
NAME                    SIZE    USED   AVAIL    CAP  HEALTH     ALTROOT
tank                   1.80T    294G   1.51T    15%  ONLINE     -

atom# zfs list
NAME              USED  AVAIL  REFER  MOUNTPOINT
tank              294G  1.48T    18K  none
tank/DATA         292G  1.48T   292G  /DATA
tank/home         216K  1.48T    21K  /home
tank/home/jago    132K  1.48T   132K  /home/jago
tank/home/karni    62K  1.48T    62K  /home/karni
tank/usr         1.33G  1.48T    18K  none
tank/usr/local    455M  1.48T   455M  /usr/local
tank/usr/obj       18K  1.48T    18K  /usr/obj
tank/usr/ports    412M  1.48T   412M  /usr/ports
tank/usr/src      495M  1.48T   495M  /usr/src
tank/var          320K  1.48T    18K  none
tank/var/log      302K  1.48T   302K  /var/log

atom# df
Filesystem      1K-blocks       Used      Avail Capacity  Mounted on
/dev/ad12s1a      16244334   1032310   13912478     7%    /
devfs                    1         1          0   100%    /dev
linprocfs                4         4          0   100%    /usr/compat/linux/proc
tank/DATA       1897835904 306397056 1591438848    16%    /DATA
tank/home       1591438848         0 1591438848     0%    /home
tank/home/jago  1591438976       128 1591438848     0%    /home/jago
tank/home/karni 1591438848         0 1591438848     0%    /home/karni
tank/usr/local  1591905024    466176 1591438848     0%    /usr/local
tank/usr/obj    1591438848         0 1591438848     0%    /usr/obj
tank/usr/ports  1591860864    422016 1591438848     0%    /usr/ports
tank/usr/src    1591945600    506752 1591438848     0%    /usr/src
tank/var/log    1591439104       256 1591438848     0%    /var/log

atom# df -h
Filesystem         Size    Used   Avail Capacity  Mounted on
/dev/ad12s1a        15G    1.0G     13G     7%    /
devfs              1.0K    1.0K      0B   100%    /dev
linprocfs          4.0K    4.0K      0B   100%    /usr/compat/linux/proc
tank/DATA          1.8T    292G    1.5T    16%    /DATA
tank/home          1.5T      0B    1.5T     0%    /home
tank/home/jago     1.5T    128K    1.5T     0%    /home/jago
tank/home/karni    1.5T      0B    1.5T     0%    /home/karni
tank/usr/local     1.5T    455M    1.5T     0%    /usr/local
tank/usr/obj       1.5T      0B    1.5T     0%    /usr/obj
tank/usr/ports     1.5T    412M    1.5T     0%    /usr/ports
tank/usr/src       1.5T    495M    1.5T     0%    /usr/src
tank/var/log       1.5T    256K    1.5T     0%    /var/log

Considering that every single filesystem is part of the exact same
pool, with no custom options whatsoever used during filesystem
creation (except for mountpoints), why is the size of tank/DATA 1.8T
while the others are 1.5T?


- Sincerely,
Dan Naumov
From fjwcash at gmail.com  Sat Jul  4 23:26:03 2009
From: fjwcash at gmail.com (Freddie Cash)
Date: Sat Jul  4 23:26:10 2009
Subject: ZFS and df weirdness
In-Reply-To: <cf9b1ee00907041455v57b1e1eatf7b4cf0a060b938c@mail.gmail.com>
References: <cf9b1ee00907041455v57b1e1eatf7b4cf0a060b938c@mail.gmail.com>
Message-ID: <b269bc570907041626j53d4b3f6y5f710d2f55631ef4@mail.gmail.com>

On Sat, Jul 4, 2009 at 2:55 PM, Dan Naumov <dan.naumov@gmail.com> wrote:

> Hello list.
>
> I have a single 2tb disk used on a 7.2-release/amd64 system with a
> small part of it given to UFS and most of the disk given to a single
> "simple" zfs pool with several filesystems without redundancy. I've
> noticed a really weird thing regarding what "df" reports regarding the
> "total space" of one of my filesystems:
>
> atom# df -h
> Filesystem         Size    Used   Avail Capacity  Mounted on
> /dev/ad12s1a        15G    1.0G     13G     7%    /
> devfs              1.0K    1.0K      0B   100%    /dev
> linprocfs          4.0K    4.0K      0B   100%    /usr/compat/linux/proc
> tank/DATA          1.8T    292G    1.5T    16%    /DATA
> tank/home          1.5T      0B    1.5T     0%    /home
> tank/home/jago     1.5T    128K    1.5T     0%    /home/jago
> tank/home/karni    1.5T      0B    1.5T     0%    /home/karni
> tank/usr/local     1.5T    455M    1.5T     0%    /usr/local
> tank/usr/obj       1.5T      0B    1.5T     0%    /usr/obj
> tank/usr/ports     1.5T    412M    1.5T     0%    /usr/ports
> tank/usr/src       1.5T    495M    1.5T     0%    /usr/src
> tank/var/log       1.5T    256K    1.5T     0%    /var/log
>
> Considering that every single filesystem is part of the exact same
> pool, with no custom options whatsoever used during filesystem
> creation (except for mountpoints), why is the size of tank/DATA 1.8T
> while the others are 1.5T?
>

Did you set a reservation for any of the other filesystems?  Reserved space
is not listed in the "general" pool.

-- 
Freddie Cash
fjwcash@gmail.com
From dan.naumov at gmail.com  Sat Jul  4 23:31:00 2009
From: dan.naumov at gmail.com (Dan Naumov)
Date: Sat Jul  4 23:31:08 2009
Subject: ZFS and df weirdness
In-Reply-To: <b269bc570907041626j53d4b3f6y5f710d2f55631ef4@mail.gmail.com>
References: <cf9b1ee00907041455v57b1e1eatf7b4cf0a060b938c@mail.gmail.com>
	<b269bc570907041626j53d4b3f6y5f710d2f55631ef4@mail.gmail.com>
Message-ID: <cf9b1ee00907041630u12e68e58l1bb317b42a6ea5fc@mail.gmail.com>

On Sun, Jul 5, 2009 at 2:26 AM, Freddie Cash<fjwcash@gmail.com> wrote:
>
>
> On Sat, Jul 4, 2009 at 2:55 PM, Dan Naumov <dan.naumov@gmail.com> wrote:
>>
>> Hello list.
>>
>> I have a single 2tb disk used on a 7.2-release/amd64 system with a
>> small part of it given to UFS and most of the disk given to a single
>> "simple" zfs pool with several filesystems without redundancy. I've
>> noticed a really weird thing regarding what "df" reports regarding the
>> "total space" of one of my filesystems:
>>
>> atom# df -h
>> Filesystem ? ? ? ? Size ? ?Used ? Avail Capacity ?Mounted on
>> /dev/ad12s1a ? ? ? ?15G ? ?1.0G ? ? 13G ? ? 7% ? ?/
>> devfs ? ? ? ? ? ? ?1.0K ? ?1.0K ? ? ?0B ? 100% ? ?/dev
>> linprocfs ? ? ? ? ?4.0K ? ?4.0K ? ? ?0B ? 100% ? ?/usr/compat/linux/proc
>> tank/DATA ? ? ? ? ?1.8T ? ?292G ? ?1.5T ? ?16% ? ?/DATA
>> tank/home ? ? ? ? ?1.5T ? ? ?0B ? ?1.5T ? ? 0% ? ?/home
>> tank/home/jago ? ? 1.5T ? ?128K ? ?1.5T ? ? 0% ? ?/home/jago
>> tank/home/karni ? ?1.5T ? ? ?0B ? ?1.5T ? ? 0% ? ?/home/karni
>> tank/usr/local ? ? 1.5T ? ?455M ? ?1.5T ? ? 0% ? ?/usr/local
>> tank/usr/obj ? ? ? 1.5T ? ? ?0B ? ?1.5T ? ? 0% ? ?/usr/obj
>> tank/usr/ports ? ? 1.5T ? ?412M ? ?1.5T ? ? 0% ? ?/usr/ports
>> tank/usr/src ? ? ? 1.5T ? ?495M ? ?1.5T ? ? 0% ? ?/usr/src
>> tank/var/log ? ? ? 1.5T ? ?256K ? ?1.5T ? ? 0% ? ?/var/log
>>
>> Considering that every single filesystem is part of the exact same
>> pool, with no custom options whatsoever used during filesystem
>> creation (except for mountpoints), why is the size of tank/DATA 1.8T
>> while the others are 1.5T?
>
> Did you set a reservation for any of the other filesystems?? Reserved space
> is not listed in the "general" pool.

no custom options whatsoever were used during filesystem creation
(except for mountpoints).

- Dan
From cptsalek at gmail.com  Sat Jul  4 23:39:02 2009
From: cptsalek at gmail.com (Christian Walther)
Date: Sat Jul  4 23:39:09 2009
Subject: ZFS and df weirdness
In-Reply-To: <cf9b1ee00907041455v57b1e1eatf7b4cf0a060b938c@mail.gmail.com>
References: <cf9b1ee00907041455v57b1e1eatf7b4cf0a060b938c@mail.gmail.com>
Message-ID: <14989d6e0907041609q62257ecdn6b80fd3b99b40df8@mail.gmail.com>

Hi Dan,

basically the "size" in df shows the current free space plus the used
space of the specific filesystem. This makes sense: Since per default
all disk space is shared, and thus can be used by all filesystems, all
filesystems need to report it as free space. Well, and used space has
to be added to the complete size, of course.

In your setup, there are 1.5TB available, but DATA uses 292GB (rounded
to 300GB). Both value add up to 1.8TB, giving the overall size of your
pool. (There is another rounding error because of your other
filesystems, but they are rather small.)
If you, say, add 400GB to tank/home/jago your df would look something like this:

> tank/DATA          1.4T    292G    1.1T    16%    /DATA
> tank/home/jago     1.1T    400G    1.1T     0%    /home/jago

It needs some time to get used to the way df displays data. IMO things
are getting easier when one remembers that the OS actually treats
every Z Filesystem like an individual device.
And BTW: The real fun starts when you add reservation and quotas to
some of your filesystems. ;-)

HTH
Christian
From ianjhart at ntlworld.com  Sat Jul  4 23:39:14 2009
From: ianjhart at ntlworld.com (Ian J Hart)
Date: Sat Jul  4 23:39:22 2009
Subject: What is /boot/kernel/*.symbols?
In-Reply-To: <20090703152150.GE11039@hugo10.ka.punkt.de>
References: <20090703142528.GA11039@hugo10.ka.punkt.de>
	<4A4E174A.1050207@andric.com>
	<20090703144121.GC11039@hugo10.ka.punkt.de>
	<4A4E1E24.3020303@andric.com>
	<20090703152150.GE11039@hugo10.ka.punkt.de>
Message-ID: <20090705003834.12211k8697td2o74@webmail.private.lan>

Quoting "Patrick M. Hausen" <hausen@punkt.de>:

> Hi!
>
> On Fri, Jul 03, 2009 at 05:05:08PM +0200, Dimitry Andric wrote:
>> E.g. the debug stuff is put into the .symbols files.  The kernel itself
>> still contains the function and data names, though:
>
> Understood. Thanks. No, I don't want the kernel to be void
> of any information ;-)
>
> Kind regards,
> Patrick
> --
> punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
> Tel. 0721 9109 0 * Fax 0721 9109 100
> info@punkt.de       http://www.punkt.de
> Gf: J?rgen Egeling      AG Mannheim 108285
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>

I just had an installworld fail due to this (/rescue).

Given that many people will have chosen the default root size offered  
by sysinstall a different build default would seem prudent.

In any case sysinstall needs to be updated (1GB?). Let's not put off  
new users anymore than we have to.


-- 
ian j hart

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


From amarat at ksu.ru  Sun Jul  5 18:06:56 2009
From: amarat at ksu.ru (Marat N.Afanasyev)
Date: Sun Jul  5 18:07:37 2009
Subject: bug in ufs?
Message-ID: <4A50E947.9020608@ksu.ru>

hello!

i have a strange problem with writing data to my ufs2+su filesystem.

1. i made a 1T gpt partition on my storage server, and formatted it:
newfs -U -m 0 -o time -i 32768 /dev/da1p3a

2. i tried to move data from other servers to this filesystem, total 
size of files is slightly less than 1T

3. i encountered a 'No space left on device' while i still have 11G of 
free space and about 13 million free inodes on the filesystem:

#df -ih
Filesystem     Size    Used   Avail Capacity  iused    ifree %iused 
Mounted on
/dev/da1p3a    1.0T    1.0T     11G    99% 20397465 13363173   60% 
/mnt/45_114

all i want to know is whether this is a bug or a feature? and if such a 
behavior is well-known, where can i read about it?

-- 
SY, Marat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3221 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090705/bf7122dc/smime.bin
From dan.naumov at gmail.com  Sun Jul  5 18:59:17 2009
From: dan.naumov at gmail.com (Dan Naumov)
Date: Sun Jul  5 18:59:23 2009
Subject: bug in ufs?
In-Reply-To: <4A50E947.9020608@ksu.ru>
References: <4A50E947.9020608@ksu.ru>
Message-ID: <cf9b1ee00907051159w5807a9f1y34104bdd3925969e@mail.gmail.com>

2009/7/5 Marat N.Afanasyev <amarat@ksu.ru>:
> hello!
>
> i have a strange problem with writing data to my ufs2+su filesystem.
>
> 1. i made a 1T gpt partition on my storage server, and formatted it:
> newfs -U -m 0 -o time -i 32768 /dev/da1p3a
>
> 2. i tried to move data from other servers to this filesystem, total size of
> files is slightly less than 1T
>
> 3. i encountered a 'No space left on device' while i still have 11G of free
> space and about 13 million free inodes on the filesystem:
>
> #df -ih
> Filesystem ? ? Size ? ?Used ? Avail Capacity ?iused ? ?ifree %iused Mounted
> on
> /dev/da1p3a ? ?1.0T ? ?1.0T ? ? 11G ? ?99% 20397465 13363173 ? 60%
> /mnt/45_114
>
> all i want to know is whether this is a bug or a feature? and if such a
> behavior is well-known, where can i read about it?

By default, a part of a filesystem is reserved, the amount reserved
has historically varied between 5-8%. This is adjustable. See the "-m"
switch to tunefs.

- Sincerely,
Dan Naumov
From amarat at ksu.ru  Sun Jul  5 19:31:28 2009
From: amarat at ksu.ru (Marat N.Afanasyev)
Date: Sun Jul  5 19:31:35 2009
Subject: bug in ufs?
In-Reply-To: <cf9b1ee00907051159w5807a9f1y34104bdd3925969e@mail.gmail.com>
References: <4A50E947.9020608@ksu.ru>
	<cf9b1ee00907051159w5807a9f1y34104bdd3925969e@mail.gmail.com>
Message-ID: <4A50FF6F.2080106@ksu.ru>

Dan Naumov wrote:
> 2009/7/5 Marat N.Afanasyev <amarat@ksu.ru>:
>> hello!
>>
>> i have a strange problem with writing data to my ufs2+su filesystem.
>>
>> 1. i made a 1T gpt partition on my storage server, and formatted it:
>> newfs -U -m 0 -o time -i 32768 /dev/da1p3a
>>
>> 2. i tried to move data from other servers to this filesystem, total size of
>> files is slightly less than 1T
>>
>> 3. i encountered a 'No space left on device' while i still have 11G of free
>> space and about 13 million free inodes on the filesystem:
>>
>> #df -ih
>> Filesystem     Size    Used   Avail Capacity  iused    ifree %iused Mounted
>> on
>> /dev/da1p3a    1.0T    1.0T     11G    99% 20397465 13363173   60%
>> /mnt/45_114
>>
>> all i want to know is whether this is a bug or a feature? and if such a
>> behavior is well-known, where can i read about it?
> 
> By default, a part of a filesystem is reserved, the amount reserved
> has historically varied between 5-8%. This is adjustable. See the "-m"
> switch to tunefs.
> 
> - Sincerely,
> Dan Naumov
> 

as you can see from newfs commandline (1.) I already diminished this 
root reserve to zero percent.

and i'm sorry i forgot to mention that i'm trying to move my data using 
root account, of course.

-- 
SY, Marat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3221 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090705/aba5dbd9/smime.bin
From mail25 at bzerk.org  Mon Jul  6 07:39:48 2009
From: mail25 at bzerk.org (Ruben de Groot)
Date: Mon Jul  6 07:39:55 2009
Subject: What is /boot/kernel/*.symbols?
In-Reply-To: <20090705003834.12211k8697td2o74@webmail.private.lan>
References: <20090703142528.GA11039@hugo10.ka.punkt.de>
	<4A4E174A.1050207@andric.com>
	<20090703144121.GC11039@hugo10.ka.punkt.de>
	<4A4E1E24.3020303@andric.com>
	<20090703152150.GE11039@hugo10.ka.punkt.de>
	<20090705003834.12211k8697td2o74@webmail.private.lan>
Message-ID: <20090706073941.GA78371@ei.bzerk.org>

On Sun, Jul 05, 2009 at 12:38:34AM +0100, Ian J Hart typed:
> 
> I just had an installworld fail due to this (/rescue).
> 
> Given that many people will have chosen the default root size offered  
> by sysinstall a different build default would seem prudent.
> 
> In any case sysinstall needs to be updated (1GB?). Let's not put off  
> new users anymore than we have to.

The default root partition created by sysinstall (provided the disk is large
enough) is 512 MB, which is more than enough.

#define ROOT_DEFAULT_SIZE               512

Ruben

From hausen at punkt.de  Mon Jul  6 07:43:01 2009
From: hausen at punkt.de (Patrick M. Hausen)
Date: Mon Jul  6 07:43:28 2009
Subject: What is /boot/kernel/*.symbols?
In-Reply-To: <20090706073941.GA78371@ei.bzerk.org>
References: <20090703142528.GA11039@hugo10.ka.punkt.de>
	<4A4E174A.1050207@andric.com>
	<20090703144121.GC11039@hugo10.ka.punkt.de>
	<4A4E1E24.3020303@andric.com>
	<20090703152150.GE11039@hugo10.ka.punkt.de>
	<20090705003834.12211k8697td2o74@webmail.private.lan>
	<20090706073941.GA78371@ei.bzerk.org>
Message-ID: <20090706074256.GD6306@hugo10.ka.punkt.de>

Hello,

On Mon, Jul 06, 2009 at 09:39:41AM +0200, Ruben de Groot wrote:
> On Sun, Jul 05, 2009 at 12:38:34AM +0100, Ian J Hart typed:
> > 
> > I just had an installworld fail due to this (/rescue).
> > 
> > Given that many people will have chosen the default root size offered  
> > by sysinstall a different build default would seem prudent.
> > 
> > In any case sysinstall needs to be updated (1GB?). Let's not put off  
> > new users anymore than we have to.
> 
> The default root partition created by sysinstall (provided the disk is large
> enough) is 512 MB, which is more than enough.
> 
> #define ROOT_DEFAULT_SIZE               512

IMHO it is not. If you install a kernel with *.symbols present
twice (i.e. kernel and kernel.old contain symbol files), your
root partition will be > 95% full.

That's why I started this discussion in the first place and
decided not to install the symbols on production machines
for now.

Kind regards,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
info@punkt.de       http://www.punkt.de
Gf: J?rgen Egeling      AG Mannheim 108285
From dimitry at andric.com  Mon Jul  6 08:34:45 2009
From: dimitry at andric.com (Dimitry Andric)
Date: Mon Jul  6 08:34:52 2009
Subject: What is /boot/kernel/*.symbols?
In-Reply-To: <20090706074256.GD6306@hugo10.ka.punkt.de>
References: <20090703142528.GA11039@hugo10.ka.punkt.de>
	<4A4E174A.1050207@andric.com>
	<20090703144121.GC11039@hugo10.ka.punkt.de>
	<4A4E1E24.3020303@andric.com>
	<20090703152150.GE11039@hugo10.ka.punkt.de>
	<20090705003834.12211k8697td2o74@webmail.private.lan>
	<20090706073941.GA78371@ei.bzerk.org>
	<20090706074256.GD6306@hugo10.ka.punkt.de>
Message-ID: <4A51B721.5020505@andric.com>

On 2009-07-06 09:42, Patrick M. Hausen wrote:
>> #define ROOT_DEFAULT_SIZE               512
> 
> IMHO it is not. If you install a kernel with *.symbols present
> twice (i.e. kernel and kernel.old contain symbol files), your
> root partition will be > 95% full.

I'm not sure how you arrive at this number; even with -CURRENT (on i386,
with all debug symbols), I could store about 4 complete kernels on such
a filesystem:

$ du -hs /boot/kernel*
122M    /boot/kernel
122M    /boot/kernel.20090629a
121M    /boot/kernel.20090630a
122M    /boot/kernel.20090702a
121M    /boot/kernel.20090703a

All other files on my root filesystem use up an additional ~25 MiB, so
in practice, it would be limited to 3 kernels, with more than enough
breathing room.
From dan.naumov at gmail.com  Mon Jul  6 08:41:41 2009
From: dan.naumov at gmail.com (Dan Naumov)
Date: Mon Jul  6 08:41:49 2009
Subject: What is /boot/kernel/*.symbols?
In-Reply-To: <4A51B721.5020505@andric.com>
References: <20090703142528.GA11039@hugo10.ka.punkt.de>
	<4A4E174A.1050207@andric.com>
	<20090703144121.GC11039@hugo10.ka.punkt.de>
	<4A4E1E24.3020303@andric.com>
	<20090703152150.GE11039@hugo10.ka.punkt.de>
	<20090705003834.12211k8697td2o74@webmail.private.lan>
	<20090706073941.GA78371@ei.bzerk.org>
	<20090706074256.GD6306@hugo10.ka.punkt.de>
	<4A51B721.5020505@andric.com>
Message-ID: <cf9b1ee00907060141w110e36c3p5922d31b3acd1f62@mail.gmail.com>

On Mon, Jul 6, 2009 at 11:34 AM, Dimitry Andric<dimitry@andric.com> wrote:
> On 2009-07-06 09:42, Patrick M. Hausen wrote:
>>> #define ROOT_DEFAULT_SIZE ? ? ? ? ? ? ? 512
>>
>> IMHO it is not. If you install a kernel with *.symbols present
>> twice (i.e. kernel and kernel.old contain symbol files), your
>> root partition will be > 95% full.
>
> I'm not sure how you arrive at this number; even with -CURRENT (on i386,
> with all debug symbols), I could store about 4 complete kernels on such
> a filesystem:
>
> $ du -hs /boot/kernel*
> 122M ? ?/boot/kernel
> 122M ? ?/boot/kernel.20090629a
> 121M ? ?/boot/kernel.20090630a
> 122M ? ?/boot/kernel.20090702a
> 121M ? ?/boot/kernel.20090703a
>
> All other files on my root filesystem use up an additional ~25 MiB, so
> in practice, it would be limited to 3 kernels, with more than enough
> breathing room.

atom# uname -a
FreeBSD atom.localdomain 7.2-RELEASE-p1 FreeBSD 7.2-RELEASE-p1 #0: Tue
Jun  9 18:02:21 UTC 2009
root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64

atom# du -hs /boot/kernel*
205M    /boot/kernel


This is on a stock 7.2-release/amd64 updated to -p1 with
freebsd-update, 2 kernels is the maximum that would fit into the
default 512mb partition size for /, a bit too tight for my liking.


- Sincerely,
Dan Naumov
From emikulic at gmail.com  Mon Jul  6 08:42:49 2009
From: emikulic at gmail.com (Emil Mikulic)
Date: Mon Jul  6 08:42:56 2009
Subject: What is /boot/kernel/*.symbols?
In-Reply-To: <4A51B721.5020505@andric.com>
References: <20090703142528.GA11039@hugo10.ka.punkt.de>
	<4A4E174A.1050207@andric.com>
	<20090703144121.GC11039@hugo10.ka.punkt.de>
	<4A4E1E24.3020303@andric.com>
	<20090703152150.GE11039@hugo10.ka.punkt.de>
	<20090705003834.12211k8697td2o74@webmail.private.lan>
	<20090706073941.GA78371@ei.bzerk.org>
	<20090706074256.GD6306@hugo10.ka.punkt.de>
	<4A51B721.5020505@andric.com>
Message-ID: <20090706084245.GA38494@dmr.ath.cx>

On Mon, Jul 06, 2009 at 10:34:41AM +0200, Dimitry Andric wrote:
> I'm not sure how you arrive at this number; even with -CURRENT (on i386,
> with all debug symbols), I could store about 4 complete kernels on such
> a filesystem:
> 
> $ du -hs /boot/kernel*
> 122M    /boot/kernel

I get about the same on an i386:
119M    /boot/kernel

However, on amd64:
227M    /boot/kernel

--Emil
From dimitry at andric.com  Mon Jul  6 08:46:53 2009
From: dimitry at andric.com (Dimitry Andric)
Date: Mon Jul  6 08:47:00 2009
Subject: What is /boot/kernel/*.symbols?
In-Reply-To: <cf9b1ee00907060141w110e36c3p5922d31b3acd1f62@mail.gmail.com>
References: <20090703142528.GA11039@hugo10.ka.punkt.de>	
	<4A4E174A.1050207@andric.com>	
	<20090703144121.GC11039@hugo10.ka.punkt.de>	
	<4A4E1E24.3020303@andric.com>	
	<20090703152150.GE11039@hugo10.ka.punkt.de>	
	<20090705003834.12211k8697td2o74@webmail.private.lan>	
	<20090706073941.GA78371@ei.bzerk.org>	
	<20090706074256.GD6306@hugo10.ka.punkt.de>	
	<4A51B721.5020505@andric.com>
	<cf9b1ee00907060141w110e36c3p5922d31b3acd1f62@mail.gmail.com>
Message-ID: <4A51B9FA.9010906@andric.com>

On 2009-07-06 10:41, Dan Naumov wrote:
> atom# uname -a
> FreeBSD atom.localdomain 7.2-RELEASE-p1 FreeBSD 7.2-RELEASE-p1 #0: Tue
> Jun  9 18:02:21 UTC 2009
> root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
> 
> atom# du -hs /boot/kernel*
> 205M    /boot/kernel

Right, so it's a lot bigger on amd64.  I guess those 64-bit pointers
aren't entirely free. :)

So indeed, on amd64 and possibly some other 'big' architectures (ia64?),
cranking the default root filesystem size to e.g. 1024M would be nice.
From petefrench at ticketswitch.com  Mon Jul  6 08:53:47 2009
From: petefrench at ticketswitch.com (Pete French)
Date: Mon Jul  6 08:53:54 2009
Subject: What is /boot/kernel/*.symbols?
In-Reply-To: <cf9b1ee00907060141w110e36c3p5922d31b3acd1f62@mail.gmail.com>
Message-ID: <E1MNjxG-00094l-II@dilbert.ticketswitch.com>

> > I'm not sure how you arrive at this number; even with -CURRENT (on i386,
> > with all debug symbols), I could store about 4 complete kernels on such
> > a filesystem:
> >
> > $ du -hs /boot/kernel*
> > 122M  /boot/kernel
>
> atom# du -hs /boot/kernel*
> 205M    /boot/kernel

i386:	127 meg
amd64:	208 meg

those are machines built from identical source, only differeing in
the architecture. unless you are constrained to using i386 for some
reason then 512 meg is going to be a bit small.

-pete.

From marck at rinet.ru  Mon Jul  6 08:54:05 2009
From: marck at rinet.ru (Dmitry Morozovsky)
Date: Mon Jul  6 08:54:20 2009
Subject: What is /boot/kernel/*.symbols?
In-Reply-To: <20090703142528.GA11039@hugo10.ka.punkt.de>
References: <20090703142528.GA11039@hugo10.ka.punkt.de>
Message-ID: <alpine.BSF.2.00.0907061253120.12926@woozle.rinet.ru>

Hi there Patrick,

On Fri, 3 Jul 2009, Patrick M. Hausen wrote:

PMH> 7.2-System:
PMH> -----------
PMH> makeoptions     DEBUG=-g
PMH> 
PMH> $ du -sk /boot/kernel
PMH> 214778	/boot/kernel
PMH> 
PMH> Lots of those files filling /boot/kernel.
PMH> 
PMH> 
PMH> On a current server with 512 MB /, the filesystem is at
PMH> 97% after installing a new kernel twice. Can I get rid of
PMH> these files somehow or are they necessary, in which case
PMH> I will need way bigger root filesystems?

Define INSTALL_NODEBUG somewhere (on installkernel commandline or maybe even in 
/etc/make.conf)

-- 
Sincerely,
D.Marck                                     [DM5020, MCK-RIPE, DM3-RIPN]
[ FreeBSD committer:                                 marck@FreeBSD.org ]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru ***
------------------------------------------------------------------------
From mail25 at bzerk.org  Mon Jul  6 09:39:10 2009
From: mail25 at bzerk.org (Ruben de Groot)
Date: Mon Jul  6 09:39:17 2009
Subject: What is /boot/kernel/*.symbols?
In-Reply-To: <4A51B9FA.9010906@andric.com>
References: <4A4E174A.1050207@andric.com>
	<20090703144121.GC11039@hugo10.ka.punkt.de>
	<4A4E1E24.3020303@andric.com>
	<20090703152150.GE11039@hugo10.ka.punkt.de>
	<20090705003834.12211k8697td2o74@webmail.private.lan>
	<20090706073941.GA78371@ei.bzerk.org>
	<20090706074256.GD6306@hugo10.ka.punkt.de>
	<4A51B721.5020505@andric.com>
	<cf9b1ee00907060141w110e36c3p5922d31b3acd1f62@mail.gmail.com>
	<4A51B9FA.9010906@andric.com>
Message-ID: <20090706093904.GA79434@ei.bzerk.org>

On Mon, Jul 06, 2009 at 10:46:50AM +0200, Dimitry Andric typed:
> On 2009-07-06 10:41, Dan Naumov wrote:
> > atom# uname -a
> > FreeBSD atom.localdomain 7.2-RELEASE-p1 FreeBSD 7.2-RELEASE-p1 #0: Tue
> > Jun  9 18:02:21 UTC 2009
> > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
> > 
> > atom# du -hs /boot/kernel*
> > 205M    /boot/kernel
> 
> Right, so it's a lot bigger on amd64.  I guess those 64-bit pointers
> aren't entirely free. :)

I'm not sure where the size difference comes from. I have some sparc64
systems running -current with symbols and the size of /boot/kernel is
more comparable to i386, even with the 8-byte pointer size:

> uname -p
sparc64
> du -sk /boot/kernel
137918  /boot/kernel

> So indeed, on amd64 and possibly some other 'big' architectures (ia64?),
> cranking the default root filesystem size to e.g. 1024M would be nice.

Indeed.

From dimitry at andric.com  Mon Jul  6 11:32:55 2009
From: dimitry at andric.com (Dimitry Andric)
Date: Mon Jul  6 11:33:02 2009
Subject: What is /boot/kernel/*.symbols?
In-Reply-To: <20090706093904.GA79434@ei.bzerk.org>
References: <4A4E174A.1050207@andric.com>	<20090703144121.GC11039@hugo10.ka.punkt.de>	<4A4E1E24.3020303@andric.com>	<20090703152150.GE11039@hugo10.ka.punkt.de>	<20090705003834.12211k8697td2o74@webmail.private.lan>	<20090706073941.GA78371@ei.bzerk.org>	<20090706074256.GD6306@hugo10.ka.punkt.de>	<4A51B721.5020505@andric.com>	<cf9b1ee00907060141w110e36c3p5922d31b3acd1f62@mail.gmail.com>	<4A51B9FA.9010906@andric.com>
	<20090706093904.GA79434@ei.bzerk.org>
Message-ID: <4A51E0E4.4020707@andric.com>

On 2009-07-06 11:39, Ruben de Groot wrote:
>>> root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
>>>
>>> atom# du -hs /boot/kernel*
>>> 205M    /boot/kernel
>>
>> Right, so it's a lot bigger on amd64.  I guess those 64-bit pointers
>> aren't entirely free. :)
> 
> I'm not sure where the size difference comes from. I have some sparc64
> systems running -current with symbols and the size of /boot/kernel is
> more comparable to i386, even with the 8-byte pointer size:
> 
>> uname -p
> sparc64
>> du -sk /boot/kernel
> 137918  /boot/kernel

It looks like on amd64, the kernel is compiled with optimization flags:

  -O2 -frename-registers -pipe -fno-strict-aliasing

by default, while on i386, they are just:

  -O -pipe

Maybe this accounts for the huge difference?  Does -O2 do a lot more
inlining?

In any case, it's a weird inconstency, if you ask me.  But it's
intentional, as /usr/src/sys/conf/kern.pre.mk says:

. if ${MACHINE_ARCH} == "amd64"
COPTFLAGS?=-O2 -frename-registers -pipe
. else
COPTFLAGS?=${_MINUS_O} -pipe
. endif

where ${_MINUS_O} is by default just "-O", since DEBUG is enabled...
From ianjhart at ntlworld.com  Mon Jul  6 13:54:52 2009
From: ianjhart at ntlworld.com (Ian J Hart)
Date: Mon Jul  6 13:55:01 2009
Subject: trap 12
Message-ID: <20090706145404.18961bxcol12mmm8@10.248.192.16>

Quoting Ian J Hart <ianjhart@ntlworld.com>:

> Is this likely to be hardware? Details will follow if not.
>
> [copied from a screen dump]
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 1; apic id = 01
> fault virtual address = 0x0
> fault code = supervisor write data, page not present
> instruction pointer = 0x8:0xffffffff807c6c12
> stack pointer = 0x10:0xffffffff510e7890
> frame pointer = 0x10:0xffffff00054a6c90
> code segment = base 0x0, limit 0xfffff, type 0x1b
> = DPL 0, pres 1, long 1 def32 0, gran 1
> processor eflags = interrupt enabled, resume, IOPL = 0
> current process = 75372 (printf)
> trap number = 12
> panic: page fault
> cpuid = 1
> uptime: 8m2s
> Cannot dump. No dump device defined.
>
>

Some suggestions (off list) that it may not be hardware, so here's the  
follow up.

supermicro 5015b-mt (super X7SBi mobo)
Intel Q6600
8GB ECC DDR2
4x Seagate 320GB, two gmirror, two idle.

issues so far

1 OK) 7.x doesn't boot without hw.ata.atapi_dma=0. Not recently tested.
2 OK) disks enumerate differently 6.x to 7.x. Painful if you hardwired  
the providor into your mirror.
3) 6.3 and 7.2 remote dump over ssh fails with 'Disconnecting:  
Corrupted MAC on input.'
4) On 7.2 (AFAICT from logs) random reboots under load. e.g. the above  
generated by a portupgrade run.

I had dumpdev=none as I hadn't setup rc.early to allow savecore to work.

In the interests of full disclosure I should say that this box was  
migrated from older hardware and then source upgraded from i386 to  
amd64 (6.3). Only one issue with that, format of accounting  
file.Upgrade to 7.2 and a rebuild or two since then.

This box is our email server and there's no load. An identical box  
running as a gateway/firewall backup dumps okay and doesn't reboot.  
That box does drop network connections when running a cvsup server  
(treelist write), but when configured to pass through these  
connections (using balance) runs okay. But that's a story for another  
day as it's still on 6.x.

Anyway, I put the two gmirror disks in another chassis and the remote  
dumps are now completing.This at least does seem to be hardware.

Before I moved the two gmirror disks I synced a third disk. I can now  
test (most of) the original hardware and software.

I was unable to make this single disk system crash, so I added two new  
disks and synced them.Now a 3 disk mirror, one disk idle.

I've disabled sendmail and the email server so as not to clash.

A portupgrade run caused a crash. I've setup coredumps so I can now  
test. Remote backup dumps do fail.

xmail# kldstat
Id Refs Address            Size     Name
  1    2 0xffffffff80100000 bd23e0   kernel
  2    1 0xffffffff80cd3000 20608    geom_mirror.ko

I did have ipfw module loaded, but I got the crash without it so I've  
removed it (firewall_type=OPEN).

Ran crashinfo, now have much more info than I need ;)

Starting another portupgrade run now to see how reproducable this is.

Later BIOS waiting in USB floppy.

dmesg after sig.

Thanks

-- 
ian j hart

Copyright (c) 1992-2009 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.2-RELEASE-p1 #0: Tue Jun 16 18:03:10 BST 2009
     mungethis@hostname:/usr/obj/usr/src/sys/GENERIC
Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff80cf5000.
Preloaded elf obj module "/boot/kernel/geom_mirror.ko" at 0xffffffff80cf5220.
Calibrating clock(s) ... i8254 clock: 1193168 Hz
CLK_USE_I8254_CALIBRATION not specified - using default frequency
Timecounter "i8254" frequency 1193182 Hz quality 0
Calibrating TSC clock ... TSC clock: 2394010944 Hz
CPU: Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz (2394.01-MHz  
K8-class CPU)
   Origin = "GenuineIntel"  Id = 0x6fb  Stepping = 11
    
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
   Features2=0xe3bd<SSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM>
   AMD Features=0x20100800<SYSCALL,NX,LM>
   AMD Features2=0x1<LAHF>
   Cores per package: 4
usable memory = 8575127552 (8177 MB)
Physical memory chunk(s):
0x0000000000001000 - 0x0000000000098fff, 622592 bytes (152 pages)
0x0000000000d27000 - 0x00000000cfe6ffff, 3474231296 bytes (848201 pages)
0x0000000100000000 - 0x000000021f8b3fff, 4824186880 bytes (1177780 pages)
avail memory  = 8273580032 (7890 MB)
ACPI APIC Table: <PTLTD          APIC  >
INTR: Adding local APIC 1 as a target
INTR: Adding local APIC 2 as a target
INTR: Adding local APIC 3 as a target
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
  cpu0 (BSP): APIC ID:  0
  cpu1 (AP): APIC ID:  1
  cpu2 (AP): APIC ID:  2
  cpu3 (AP): APIC ID:  3
APIC: CPU 0 has ACPI ID 0
APIC: CPU 1 has ACPI ID 1
APIC: CPU 2 has ACPI ID 2
APIC: CPU 3 has ACPI ID 3
ULE: setup cpu group 0
ULE: setup cpu 0
ULE: adding cpu 0 to group 0: cpus 1 mask 0x1
ULE: setup cpu group 1
ULE: setup cpu 1
ULE: adding cpu 1 to group 1: cpus 1 mask 0x2
ULE: setup cpu group 2
ULE: setup cpu 2
ULE: adding cpu 2 to group 2: cpus 1 mask 0x4
ULE: setup cpu group 3
ULE: setup cpu 3
ULE: adding cpu 3 to group 3: cpus 1 mask 0x8
ACPI: RSDP @ 0x0xf69a0/0x0024 (v  2 PTLTD )
ACPI: XSDT @ 0x0xcfe77290/0x00A4 (v  1 PTLTD     XSDT   0x06040000   
LTP 0x00000000)
ACPI: FACP @ 0x0xcfe80d60/0x00F4 (v  3 INTEL           0x06040000 PTL   
0x00000002)
ACPI: DSDT @ 0x0xcfe7a435/0x68B7 (v  1  INTEL BEARLAKE 0x06040000 MSFT  
0x03000000)
ACPI: FACS @ 0x0xcfe83fc0/0x0040
ACPI: _MAR @ 0x0xcfe80e54/0x0030 (v  1 Intel  OEMDMAR  0x06040000 LOHR  
0x00000001)
ACPI: MCFG @ 0x0xcfe80e84/0x003C (v  1 PTLTD    MCFG   0x06040000  LTP  
0x00000000)
ACPI: HPET @ 0x0xcfe80ec0/0x0038 (v  1 PTLTD  HPETTBL  0x06040000  LTP  
0x00000001)
ACPI: APIC @ 0x0xcfe80ef8/0x0090 (v  1 PTLTD     APIC   0x06040000   
LTP 0x00000000)
ACPI: BOOT @ 0x0xcfe80f88/0x0028 (v  1 PTLTD  $SBFTBL$ 0x06040000  LTP  
0x00000001)
ACPI: SPCR @ 0x0xcfe80fb0/0x0050 (v  1 PTLTD  $UCRTBL$ 0x06040000 PTL   
0x00000001)
ACPI: SSDT @ 0x0xcfe78ba7/0x025F (v  1  PmRef  Cpu0Tst 0x00003000 INTL  
0x20050228)
ACPI: SSDT @ 0x0xcfe78b01/0x00A6 (v  1  PmRef  Cpu7Tst 0x00003000 INTL  
0x20050228)
ACPI: SSDT @ 0x0xcfe78a5b/0x00A6 (v  1  PmRef  Cpu6Tst 0x00003000 INTL  
0x20050228)
ACPI: SSDT @ 0x0xcfe789b5/0x00A6 (v  1  PmRef  Cpu5Tst 0x00003000 INTL  
0x20050228)
ACPI: SSDT @ 0x0xcfe7890f/0x00A6 (v  1  PmRef  Cpu4Tst 0x00003000 INTL  
0x20050228)
ACPI: SSDT @ 0x0xcfe78869/0x00A6 (v  1  PmRef  Cpu3Tst 0x00003000 INTL  
0x20050228)
ACPI: SSDT @ 0x0xcfe787c3/0x00A6 (v  1  PmRef  Cpu2Tst 0x00003000 INTL  
0x20050228)
ACPI: SSDT @ 0x0xcfe7871d/0x00A6 (v  1  PmRef  Cpu1Tst 0x00003000 INTL  
0x20050228)
ACPI: SSDT @ 0x0xcfe77334/0x13E9 (v  1  PmRef    CpuPm 0x00003000 INTL  
0x20050228)
MADT: Found IO APIC ID 4, Interrupt 0 at 0xfec00000
ioapic0: Routing external 8259A's -> intpin 0
MADT: Found IO APIC ID 5, Interrupt 24 at 0xfecc0000
lapic0: Routing NMI -> LINT1
lapic0: LINT1 trigger: edge
lapic0: LINT1 polarity: high
lapic1: Routing NMI -> LINT1
lapic1: LINT1 trigger: edge
lapic1: LINT1 polarity: high
lapic2: Routing NMI -> LINT1
lapic2: LINT1 trigger: edge
lapic2: LINT1 polarity: high
lapic3: Routing NMI -> LINT1
lapic3: LINT1 trigger: edge
lapic3: LINT1 polarity: high
MADT: Interrupt override: source 0, irq 2
ioapic0: Routing IRQ 0 -> intpin 2
MADT: Interrupt override: source 9, irq 9
ioapic0: intpin 9 trigger: level
ioapic0 <Version 2.0> irqs 0-23 on motherboard
ioapic1 <Version 2.0> irqs 24-47 on motherboard
cpu0 BSP:
      ID: 0x00000000   VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff
   lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff
   timer: 0x000100ef therm: 0x00000200 err: 0x00010000 pcm: 0x00010000
wlan_amrr: <AMRR Transmit Rate Control Algorithm>
wlan: <802.11 Link Layer>
null: <null device, zero device>
random: <entropy source, Software, Yarrow>
nfslock: pseudo-device
kbd: new array size 4
kbd1 at kbdmux0
mem: <memory>
io: <I/O>
hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2 (Jun 16 2009 18:03:00)
acpi0: <PTLTD    XSDT> on motherboard
ioapic0: routing intpin 9 (ISA IRQ 9) to vector 48
acpi0: [MPSAFE]
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
AcpiOsDerivePciId: \\_SB_.PCI0.REGS -> bus 0 dev 0 func 0
AcpiOsDerivePciId: \\_SB_.PCI0.IGD0.IGDP -> bus 0 dev 2 func 0
AcpiOsDerivePciId: \\_SB_.PCI0.LPC0.REGS -> bus 0 dev 31 func 0
AcpiOsDerivePciId: \\_SB_.PCI0.LPC0.PIRX -> bus 0 dev 31 func 0
AcpiOsDerivePciId: \\_SB_.PCI0.LPC0.PIRY -> bus 0 dev 31 func 0
ACPI timer: 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 -> 10
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
pci_link0:        Index  IRQ  Rtd  Ref  IRQs
   Initial Probe       0    5   N     0  3 4 5 6 7 10 11 12 14 15
   Validation          0    5   N     0  3 4 5 6 7 10 11 12 14 15
   After Disable       0  255   N     0  3 4 5 6 7 10 11 12 14 15
pci_link1:        Index  IRQ  Rtd  Ref  IRQs
   Initial Probe       0   10   N     0  3 4 5 6 7 10 11 12 14 15
   Validation          0   10   N     0  3 4 5 6 7 10 11 12 14 15
   After Disable       0  255   N     0  3 4 5 6 7 10 11 12 14 15
pci_link2:        Index  IRQ  Rtd  Ref  IRQs
   Initial Probe       0   11   N     0  3 4 5 6 7 10 11 12 14 15
   Validation          0   11   N     0  3 4 5 6 7 10 11 12 14 15
   After Disable       0  255   N     0  3 4 5 6 7 10 11 12 14 15
pci_link3:        Index  IRQ  Rtd  Ref  IRQs
   Initial Probe       0  255   N     0  3 4 5 6 7 10 11 12 14 15
   Validation          0  255   N     0  3 4 5 6 7 10 11 12 14 15
   After Disable       0  255   N     0  3 4 5 6 7 10 11 12 14 15
pci_link4:        Index  IRQ  Rtd  Ref  IRQs
   Initial Probe       0  255   N     0  3 4 5 6 7 10 11 12 14 15
   Validation          0  255   N     0  3 4 5 6 7 10 11 12 14 15
   After Disable       0  255   N     0  3 4 5 6 7 10 11 12 14 15
pci_link5:        Index  IRQ  Rtd  Ref  IRQs
   Initial Probe       0  255   N     0  3 4 5 6 7 10 11 12 14 15
   Validation          0  255   N     0  3 4 5 6 7 10 11 12 14 15
   After Disable       0  255   N     0  3 4 5 6 7 10 11 12 14 15
pci_link6:        Index  IRQ  Rtd  Ref  IRQs
   Initial Probe       0   11   N     0  3 4 5 6 7 10 11 12 14 15
   Validation          0   11   N     0  3 4 5 6 7 10 11 12 14 15
   After Disable       0  255   N     0  3 4 5 6 7 10 11 12 14 15
pci_link7:        Index  IRQ  Rtd  Ref  IRQs
   Initial Probe       0   10   N     0  3 4 5 6 7 10 11 12 14 15
   Validation          0   10   N     0  3 4 5 6 7 10 11 12 14 15
   After Disable       0  255   N     0  3 4 5 6 7 10 11 12 14 15
acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
acpi_hpet0: vend: 0x8086 rev: 0x1 num: 3 hz: 14318180 opts:  
legacy_route 64-bit
Timecounter "HPET" frequency 14318180 Hz quality 900
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pci0: domain=0, physical bus=0
found-> vendor=0x8086, dev=0x29f0, revid=0x01
         domain=0, bus=0, slot=0, func=0
         class=06-00-00, hdrtype=0x00, mfdev=0
         cmdreg=0x0106, statreg=0x2090, cachelnsz=0 (dwords)
         lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
found-> vendor=0x8086, dev=0x29f1, revid=0x01
         domain=0, bus=0, slot=1, func=0
         class=06-04-00, hdrtype=0x01, mfdev=0
         cmdreg=0x0107, statreg=0x0010, cachelnsz=8 (dwords)
         lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns)
         intpin=a, irq=5
         powerspec 3  supports D0 D3  current D0
         MSI supports 1 message
pcib0: matched entry for 0.1.INTA
pcib0: slot 1 INTA hardwired to IRQ 16
found-> vendor=0x8086, dev=0x2937, revid=0x02
         domain=0, bus=0, slot=26, func=0
         class=0c-03-00, hdrtype=0x00, mfdev=1
         cmdreg=0x0005, statreg=0x0290, cachelnsz=0 (dwords)
         lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
         intpin=a, irq=5
         map[20]: type I/O Port, range 32, base 0x1820, size  5, enabled
pcib0: matched entry for 0.26.INTA
pcib0: slot 26 INTA hardwired to IRQ 16
found-> vendor=0x8086, dev=0x2938, revid=0x02
         domain=0, bus=0, slot=26, func=1
         class=0c-03-00, hdrtype=0x00, mfdev=0
         cmdreg=0x0005, statreg=0x0290, cachelnsz=0 (dwords)
         lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
         intpin=b, irq=10
         map[20]: type I/O Port, range 32, base 0x1840, size  5, enabled
pcib0: matched entry for 0.26.INTB
pcib0: slot 26 INTB hardwired to IRQ 17
found-> vendor=0x8086, dev=0x2939, revid=0x02
         domain=0, bus=0, slot=26, func=2
         class=0c-03-00, hdrtype=0x00, mfdev=0
         cmdreg=0x0005, statreg=0x0290, cachelnsz=0 (dwords)
         lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
         intpin=c, irq=11
         map[20]: type I/O Port, range 32, base 0x1860, size  5, enabled
pcib0: matched entry for 0.26.INTC
pcib0: slot 26 INTC hardwired to IRQ 18
found-> vendor=0x8086, dev=0x293c, revid=0x02
         domain=0, bus=0, slot=26, func=7
         class=0c-03-20, hdrtype=0x00, mfdev=0
         cmdreg=0x0106, statreg=0x0290, cachelnsz=0 (dwords)
         lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
         intpin=c, irq=11
         powerspec 2  supports D0 D3  current D0
         map[10]: type Memory, range 32, base 0xd8601800, size 10, enabled
pcib0: matched entry for 0.26.INTC
pcib0: slot 26 INTC hardwired to IRQ 18
found-> vendor=0x8086, dev=0x2940, revid=0x02
         domain=0, bus=0, slot=28, func=0
         class=06-04-00, hdrtype=0x01, mfdev=1
         cmdreg=0x0000, statreg=0x0010, cachelnsz=8 (dwords)
         lattimer=0x00 (0 ns), mingnt=0x40 (16000 ns), maxlat=0x00 (0 ns)
         intpin=a, irq=5
         powerspec 2  supports D0 D3  current D0
         MSI supports 1 message
pcib0: matched entry for 0.28.INTA
pcib0: slot 28 INTA hardwired to IRQ 16
found-> vendor=0x8086, dev=0x2948, revid=0x02
         domain=0, bus=0, slot=28, func=4
         class=06-04-00, hdrtype=0x01, mfdev=1
         cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords)
         lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns)
         intpin=a, irq=5
         powerspec 2  supports D0 D3  current D0
         MSI supports 1 message
pcib0: matched entry for 0.28.INTA
pcib0: slot 28 INTA hardwired to IRQ 16
found-> vendor=0x8086, dev=0x294a, revid=0x02
         domain=0, bus=0, slot=28, func=5
         class=06-04-00, hdrtype=0x01, mfdev=1
         cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords)
         lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns)
         intpin=b, irq=10
         powerspec 2  supports D0 D3  current D0
         MSI supports 1 message
pcib0: matched entry for 0.28.INTB
pcib0: slot 28 INTB hardwired to IRQ 17
found-> vendor=0x8086, dev=0x2934, revid=0x02
         domain=0, bus=0, slot=29, func=0
         class=0c-03-00, hdrtype=0x00, mfdev=1
         cmdreg=0x0005, statreg=0x0290, cachelnsz=0 (dwords)
         lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
         intpin=a, irq=10
         map[20]: type I/O Port, range 32, base 0x1880, size  5, enabled
pcib0: matched entry for 0.29.INTA
pcib0: slot 29 INTA hardwired to IRQ 23
found-> vendor=0x8086, dev=0x2935, revid=0x02
         domain=0, bus=0, slot=29, func=1
         class=0c-03-00, hdrtype=0x00, mfdev=0
         cmdreg=0x0005, statreg=0x0290, cachelnsz=0 (dwords)
         lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
         intpin=b, irq=11
         map[20]: type I/O Port, range 32, base 0x18a0, size  5, enabled
pcib0: matched entry for 0.29.INTB
pcib0: slot 29 INTB hardwired to IRQ 22
found-> vendor=0x8086, dev=0x2936, revid=0x02
         domain=0, bus=0, slot=29, func=2
         class=0c-03-00, hdrtype=0x00, mfdev=0
         cmdreg=0x0005, statreg=0x0290, cachelnsz=0 (dwords)
         lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
         intpin=c, irq=11
         map[20]: type I/O Port, range 32, base 0x18c0, size  5, enabled
pcib0: matched entry for 0.29.INTC
pcib0: slot 29 INTC hardwired to IRQ 18
found-> vendor=0x8086, dev=0x293a, revid=0x02
         domain=0, bus=0, slot=29, func=7
         class=0c-03-20, hdrtype=0x00, mfdev=0
         cmdreg=0x0106, statreg=0x0290, cachelnsz=0 (dwords)
         lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
         intpin=a, irq=10
         powerspec 2  supports D0 D3  current D0
         map[10]: type Memory, range 32, base 0xd8601c00, size 10, enabled
pcib0: matched entry for 0.29.INTA
pcib0: slot 29 INTA hardwired to IRQ 23
found-> vendor=0x8086, dev=0x244e, revid=0x92
         domain=0, bus=0, slot=30, func=0
         class=06-04-01, hdrtype=0x01, mfdev=0
         cmdreg=0x0107, statreg=0x0010, cachelnsz=0 (dwords)
         lattimer=0x00 (0 ns), mingnt=0x0c (3000 ns), maxlat=0x00 (0 ns)
found-> vendor=0x8086, dev=0x2916, revid=0x02
         domain=0, bus=0, slot=31, func=0
         class=06-01-00, hdrtype=0x00, mfdev=1
         cmdreg=0x0007, statreg=0x0210, cachelnsz=0 (dwords)
         lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
found-> vendor=0x8086, dev=0x2922, revid=0x02
         domain=0, bus=0, slot=31, func=2
         class=01-06-01, hdrtype=0x00, mfdev=0
         cmdreg=0x0007, statreg=0x02b0, cachelnsz=0 (dwords)
         lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
         intpin=b, irq=10
         powerspec 3  supports D0 D3  current D0
         MSI supports 16 messages
         map[10]: type I/O Port, range 32, base 0x1c50, size  3, enabled
         map[14]: type I/O Port, range 32, base 0x1c44, size  2, enabled
         map[18]: type I/O Port, range 32, base 0x1c48, size  3, enabled
         map[1c]: type I/O Port, range 32, base 0x1c40, size  2, enabled
         map[20]: type I/O Port, range 32, base 0x18e0, size  5, enabled
         map[24]: type Memory, range 32, base 0xd8601000, size 11, enabled
pcib0: matched entry for 0.31.INTB
pcib0: slot 31 INTB hardwired to IRQ 17
found-> vendor=0x8086, dev=0x2930, revid=0x02
         domain=0, bus=0, slot=31, func=3
         class=0c-05-00, hdrtype=0x00, mfdev=0
         cmdreg=0x0001, statreg=0x0280, cachelnsz=0 (dwords)
         lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
         intpin=b, irq=10
         map[10]: type Memory, range 64, base 0xd8602000, size  8,  
memory disabled
         map[20]: type I/O Port, range 32, base 0x1100, size  5, enabled
pcib0: matched entry for 0.31.INTB
pcib0: slot 31 INTB hardwired to IRQ 17
found-> vendor=0x8086, dev=0x2932, revid=0x02
         domain=0, bus=0, slot=31, func=6
         class=11-80-00, hdrtype=0x00, mfdev=0
         cmdreg=0x0002, statreg=0x0010, cachelnsz=0 (dwords)
         lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
         intpin=a, irq=5
         powerspec 3  supports D0 D3  current D0
         map[10]: type Memory, range 64, base 0xd8600000, size 12, enabled
pcib0: matched entry for 0.31.INTA
pcib0: slot 31 INTA hardwired to IRQ 16
pcib1: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci0
pcib1:   domain            0
pcib1:   secondary bus     1
pcib1:   subordinate bus   2
pcib1:   I/O decode        0xf000-0xfff
pcib1:   memory decode     0xd8100000-0xd81fffff
pcib1:   no prefetched decode
pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.PEG_  
- AE_NOT_FOUND
pci1: <ACPI PCI bus> on pcib1
pci1: domain=0, physical bus=1
found-> vendor=0x8086, dev=0x032c, revid=0x09
         domain=0, bus=1, slot=0, func=0
         class=06-04-00, hdrtype=0x01, mfdev=1
         cmdreg=0x0107, statreg=0x0010, cachelnsz=16 (dwords)
         lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns)
         powerspec 2  supports D0 D3  current D0
         MSI supports 1 message, 64 bit
found-> vendor=0x8086, dev=0x0326, revid=0x09
         domain=0, bus=1, slot=0, func=1
         class=08-00-20, hdrtype=0x00, mfdev=1
         cmdreg=0x0106, statreg=0x0010, cachelnsz=0 (dwords)
         lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
         powerspec 2  supports D0 D3  current D0
         map[10]: type Memory, range 32, base 0xd8100000, size 12, enabled
pcib1: requested memory range 0xd8100000-0xd8100fff: good
pcib2: <ACPI PCI-PCI bridge> at device 0.0 on pci1
pcib2:   domain            0
pcib2:   secondary bus     2
pcib2:   subordinate bus   2
pcib2:   I/O decode        0xf000-0xfff
pcib2:   no prefetched decode
pci2: <ACPI PCI bus> on pcib2
pci2: domain=0, physical bus=2
uhci0: <UHCI (generic) USB controller> port 0x1820-0x183f irq 16 at  
device 26.0 on pci0
uhci0: Reserved 0x20 bytes for rid 0x20 type 4 at 0x1820
ioapic0: routing intpin 16 (PCI IRQ 16) to vector 49
uhci0: [GIANT-LOCKED]
uhci0: [ITHREAD]
usb0: <UHCI (generic) USB controller> on uhci0
usb0: USB revision 1.0
uhub0: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
uhub0: 2 ports with 2 removable, self powered
uhci1: <UHCI (generic) USB controller> port 0x1840-0x185f irq 17 at  
device 26.1 on pci0
uhci1: Reserved 0x20 bytes for rid 0x20 type 4 at 0x1840
ioapic0: routing intpin 17 (PCI IRQ 17) to vector 50
uhci1: [GIANT-LOCKED]
uhci1: [ITHREAD]
usb1: <UHCI (generic) USB controller> on uhci1
usb1: USB revision 1.0
uhub1: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1
uhub1: 2 ports with 2 removable, self powered
uhci2: <UHCI (generic) USB controller> port 0x1860-0x187f irq 18 at  
device 26.2 on pci0
uhci2: Reserved 0x20 bytes for rid 0x20 type 4 at 0x1860
ioapic0: routing intpin 18 (PCI IRQ 18) to vector 51
uhci2: [GIANT-LOCKED]
uhci2: [ITHREAD]
usb2: <UHCI (generic) USB controller> on uhci2
usb2: USB revision 1.0
uhub2: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2
uhub2: 2 ports with 2 removable, self powered
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xd8601800-0xd8601bff  
irq 18 at device 26.7 on pci0
ehci0: Reserved 0x400 bytes for rid 0x10 type 3 at 0xd8601800
ehci0: [GIANT-LOCKED]
ehci0: [ITHREAD]
usb3: EHCI version 1.0
usb3: companion controllers, 2 ports each: usb0 usb1 usb2
usb3: <EHCI (generic) USB 2.0 controller> on ehci0
usb3: USB revision 2.0
uhub3: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb3
uhub3: 6 ports with 6 removable, self powered
pcib3: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
pcib3:   domain            0
pcib3:   secondary bus     5
pcib3:   subordinate bus   5
pcib3:   I/O decode        0x0-0x0
pcib3:   no prefetched decode
pci5: <ACPI PCI bus> on pcib3
pci5: domain=0, physical bus=5
pcib4: <ACPI PCI-PCI bridge> irq 16 at device 28.4 on pci0
pcib4:   domain            0
pcib4:   secondary bus     13
pcib4:   subordinate bus   13
pcib4:   I/O decode        0x2000-0x2fff
pcib4:   memory decode     0xd8000000-0xd80fffff
pcib4:   no prefetched decode
pci13: <ACPI PCI bus> on pcib4
pci13: domain=0, physical bus=13
found-> vendor=0x8086, dev=0x108c, revid=0x03
         domain=0, bus=13, slot=0, func=0
         class=02-00-00, hdrtype=0x00, mfdev=0
         cmdreg=0x0107, statreg=0x0010, cachelnsz=8 (dwords)
         lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
         intpin=a, irq=5
         powerspec 2  supports D0 D3  current D0
         MSI supports 1 message, 64 bit
         map[10]: type Memory, range 32, base 0xd8000000, size 17, enabled
pcib4: requested memory range 0xd8000000-0xd801ffff: good
         map[18]: type I/O Port, range 32, base 0x2000, size  5, enabled
pcib4: requested I/O range 0x2000-0x201f: in range
pcib4: matched entry for 13.0.INTA
pcib4: slot 0 INTA hardwired to IRQ 16
em0: <Intel(R) PRO/1000 Network Connection 6.9.6> port 0x2000-0x201f  
mem 0xd8000000-0xd801ffff irq 16 at device 0.0 on pci13
em0: Reserved 0x20000 bytes for rid 0x10 type 3 at 0xd8000000
em0: attempting to allocate 1 MSI vectors (1 supported)
msi: routing MSI IRQ 256 to vector 52
em0: using IRQ 256 for MSI
em0: Using MSI interrupt
em0: [FILTER]
em0: bpf attached
em0: Ethernet address: 00:30:48:66:83:a0
pcib5: <ACPI PCI-PCI bridge> irq 17 at device 28.5 on pci0
pcib5:   domain            0
pcib5:   secondary bus     15
pcib5:   subordinate bus   15
pcib5:   I/O decode        0x3000-0x3fff
pcib5:   memory decode     0xd8200000-0xd82fffff
pcib5:   no prefetched decode
pci15: <ACPI PCI bus> on pcib5
pci15: domain=0, physical bus=15
found-> vendor=0x8086, dev=0x109a, revid=0x00
         domain=0, bus=15, slot=0, func=0
         class=02-00-00, hdrtype=0x00, mfdev=0
         cmdreg=0x0107, statreg=0x0010, cachelnsz=8 (dwords)
         lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
         intpin=a, irq=10
         powerspec 2  supports D0 D3  current D0
         MSI supports 1 message, 64 bit
         map[10]: type Memory, range 32, base 0xd8200000, size 17, enabled
pcib5: requested memory range 0xd8200000-0xd821ffff: good
         map[18]: type I/O Port, range 32, base 0x3000, size  5, enabled
pcib5: requested I/O range 0x3000-0x301f: in range
pcib5: matched entry for 15.0.INTA
pcib5: slot 0 INTA hardwired to IRQ 17
em1: <Intel(R) PRO/1000 Network Connection 6.9.6> port 0x3000-0x301f  
mem 0xd8200000-0xd821ffff irq 17 at device 0.0 on pci15
em1: Reserved 0x20000 bytes for rid 0x10 type 3 at 0xd8200000
em1: attempting to allocate 1 MSI vectors (1 supported)
msi: routing MSI IRQ 257 to vector 53
em1: using IRQ 257 for MSI
em1: Using MSI interrupt
em1: [FILTER]
em1: bpf attached
em1: Ethernet address: 00:30:48:66:83:a1
uhci3: <UHCI (generic) USB controller> port 0x1880-0x189f irq 23 at  
device 29.0 on pci0
uhci3: Reserved 0x20 bytes for rid 0x20 type 4 at 0x1880
ioapic0: routing intpin 23 (PCI IRQ 23) to vector 54
uhci3: [GIANT-LOCKED]
uhci3: [ITHREAD]
usb4: <UHCI (generic) USB controller> on uhci3
usb4: USB revision 1.0
uhub4: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb4
uhub4: 2 ports with 2 removable, self powered
uhci4: <UHCI (generic) USB controller> port 0x18a0-0x18bf irq 22 at  
device 29.1 on pci0
uhci4: Reserved 0x20 bytes for rid 0x20 type 4 at 0x18a0
ioapic0: routing intpin 22 (PCI IRQ 22) to vector 55
uhci4: [GIANT-LOCKED]
uhci4: [ITHREAD]
usb5: <UHCI (generic) USB controller> on uhci4
usb5: USB revision 1.0
uhub5: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb5
uhub5: 2 ports with 2 removable, self powered
uhci5: <UHCI (generic) USB controller> port 0x18c0-0x18df irq 18 at  
device 29.2 on pci0
uhci5: Reserved 0x20 bytes for rid 0x20 type 4 at 0x18c0
uhci5: [GIANT-LOCKED]
uhci5: [ITHREAD]
usb6: <UHCI (generic) USB controller> on uhci5
usb6: USB revision 1.0
uhub6: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb6
uhub6: 2 ports with 2 removable, self powered
ehci1: <EHCI (generic) USB 2.0 controller> mem 0xd8601c00-0xd8601fff  
irq 23 at device 29.7 on pci0
ehci1: Reserved 0x400 bytes for rid 0x10 type 3 at 0xd8601c00
ehci1: [GIANT-LOCKED]
ehci1: [ITHREAD]
usb7: EHCI version 1.0
usb7: companion controllers, 2 ports each: usb4 usb5 usb6
usb7: <EHCI (generic) USB 2.0 controller> on ehci1
usb7: USB revision 2.0
uhub7: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb7
uhub7: 6 ports with 6 removable, self powered
pcib6: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pcib6:   domain            0
pcib6:   secondary bus     17
pcib6:   subordinate bus   17
pcib6:   I/O decode        0x4000-0x4fff
pcib6:   memory decode     0xd8300000-0xd83fffff
pcib6:   prefetched decode 0xd0000000-0xd7ffffff
pcib6:   Subtractively decoded bridge.
pci17: <ACPI PCI bus> on pcib6
pci17: domain=0, physical bus=17
found-> vendor=0x1002, dev=0x515e, revid=0x02
         domain=0, bus=17, slot=3, func=0
         class=03-00-00, hdrtype=0x00, mfdev=0
         cmdreg=0x0187, statreg=0x0290, cachelnsz=8 (dwords)
         lattimer=0x42 (1980 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns)
         intpin=a, irq=11
         powerspec 2  supports D0 D1 D2 D3  current D0
         map[10]: type Prefetchable Memory, range 32, base 0xd0000000,  
size 27, enabled
pcib6: requested memory range 0xd0000000-0xd7ffffff: good
         map[14]: type I/O Port, range 32, base 0x4000, size  8, enabled
pcib6: requested I/O range 0x4000-0x40ff: in range
         map[18]: type Memory, range 32, base 0xd8300000, size 16, enabled
pcib6: requested memory range 0xd8300000-0xd830ffff: good
pcib6: matched entry for 17.3.INTA
pcib6: slot 3 INTA hardwired to IRQ 22
found-> vendor=0x1283, dev=0x8213, revid=0x00
         domain=0, bus=17, slot=4, func=0
         class=01-01-85, hdrtype=0x00, mfdev=0
         cmdreg=0x0007, statreg=0x0210, cachelnsz=0 (dwords)
         lattimer=0x40 (1920 ns), mingnt=0x08 (2000 ns), maxlat=0x08 (2000 ns)
         intpin=a, irq=10
         powerspec 2  supports D0 D3  current D0
         map[10]: type I/O Port, range 32, base 0x4420, size  3, enabled
pcib6: requested I/O range 0x4420-0x4427: in range
         map[14]: type I/O Port, range 32, base 0x4414, size  2, enabled
pcib6: requested I/O range 0x4414-0x4417: in range
         map[18]: type I/O Port, range 32, base 0x4418, size  3, enabled
pcib6: requested I/O range 0x4418-0x441f: in range
         map[1c]: type I/O Port, range 32, base 0x4410, size  2, enabled
pcib6: requested I/O range 0x4410-0x4413: in range
         map[20]: type I/O Port, range 32, base 0x4400, size  4, enabled
pcib6: requested I/O range 0x4400-0x440f: in range
pcib6: matched entry for 17.4.INTA
pcib6: slot 4 INTA hardwired to IRQ 23
vgapci0: <VGA-compatible display> port 0x4000-0x40ff mem  
0xd0000000-0xd7ffffff,0xd8300000-0xd830ffff irq 22 at device 3.0 on  
pci17
atapci0: <ITE IT8213F UDMA133 controller> port  
0x4420-0x4427,0x4414-0x4417,0x4418-0x441f,0x4410-0x4413,0x4400-0x440f  
irq 23 at device 4.0 on pci17
atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0x4400
atapci0: [MPSAFE]
atapci0: [ITHREAD]
ata2: <ATA channel 0> on atapci0
atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x4420
atapci0: Reserved 0x4 bytes for rid 0x14 type 4 at 0x4414
ata2: reset tp1 mask=03 ostat0=60 ostat1=50
ata2: stat0=0x20 err=0x20 lsb=0x20 msb=0x20
ata2: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb
ata2: reset tp2 stat0=20 stat1=00 devices=0x8<ATAPI_SLAVE>
ata2: [MPSAFE]
ata2: [ITHREAD]
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci1: <Intel (ID=29228086) AHCI controller> port  
0x1c50-0x1c57,0x1c44-0x1c47,0x1c48-0x1c4f,0x1c40-0x1c43,0x18e0-0x18ff  
mem 0xd8601000-0xd86017ff irq 17 at device 31.2 on pci0
atapci1: Reserved 0x20 bytes for rid 0x20 type 4 at 0x18e0
atapci1: Reserved 0x800 bytes for rid 0x24 type 3 at 0xd8601000
atapci1: [MPSAFE]
atapci1: [ITHREAD]
atapci1: AHCI Version 01.20 controller with 6 ports detected
ata3: <ATA channel 0> on atapci1
ata3: SATA connect time=0ms
ata3: SIGNATURE: 00000101
ata3: ahci_reset devices=0x1<ATA_MASTER>
ata3: [MPSAFE]
ata3: [ITHREAD]
ata4: <ATA channel 1> on atapci1
ata4: SATA connect time=0ms
ata4: SIGNATURE: 00000101
ata4: ahci_reset devices=0x1<ATA_MASTER>
ata4: [MPSAFE]
ata4: [ITHREAD]
ata5: <ATA channel 2> on atapci1
ata5: SATA connect time=0ms
ata5: SIGNATURE: 00000101
ata5: ahci_reset devices=0x1<ATA_MASTER>
ata5: [MPSAFE]
ata5: [ITHREAD]
ata6: <ATA channel 3> on atapci1
ata6: SATA connect time=0ms
ata6: SIGNATURE: 00000101
ata6: ahci_reset devices=0x1<ATA_MASTER>
ata6: [MPSAFE]
ata6: [ITHREAD]
ata7: <ATA channel 4> on atapci1
ata7: port not implemented
ata7: [MPSAFE]
ata7: [ITHREAD]
ata8: <ATA channel 5> on atapci1
ata8: port not implemented
ata8: [MPSAFE]
ata8: [ITHREAD]
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
pci0: <dasp> at device 31.6 (no driver attached)
acpi_button0: <Power Button> on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
atkbd: the current kbd controller command byte 0047
atkbd: keyboard ID 0x41ab (2)
kbd0 at atkbd0
kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000
ioapic0: routing intpin 1 (ISA IRQ 1) to vector 56
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
psm0: unable to allocate IRQ
psmcpnp0: <PS/2 mouse port> irq 12 on acpi0
psm0: current command byte:0047
psm0: <PS/2 Mouse> irq 12 on atkbdc0
ioapic0: routing intpin 12 (ISA IRQ 12) to vector 57
psm0: [GIANT-LOCKED]
psm0: [ITHREAD]
psm0: model IntelliMouse Explorer, device ID 4-00, 5 buttons
psm0: config:00000000, flags:00000008, packet size:4
psm0: syncmask:08, syncbits:00
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: irq maps: 0 0 0 0
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: irq maps: 0 0 0 0
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A
ioapic0: routing intpin 4 (ISA IRQ 4) to vector 58
sio0: [FILTER]
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
sio1: irq maps: 0 0 0 0
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
sio1: irq maps: 0 0 0 0
sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
ioapic0: routing intpin 3 (ISA IRQ 3) to vector 59
sio1: [FILTER]
fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
fdc0: ic_type 90 part_id 80
ioapic0: routing intpin 6 (ISA IRQ 6) to vector 60
fdc0: [FILTER]
ppc0: using extended I/O port range
ppc0: ECP SPP ECP+EPP SPP
ppc0: <Parallel port> port 0x378-0x37f,0x778-0x77f irq 7 drq 3 on acpi0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/9 bytes threshold
ppbus0: <Parallel port bus> on ppc0
ioapic0: routing intpin 7 (ISA IRQ 7) to vector 61
ppbus0: [MPSAFE]
ppbus0: [ITHREAD]
plip0: <PLIP network interface> on ppbus0
plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag
plip0: bpf attached
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
ppc0: [GIANT-LOCKED]
ppc0: [ITHREAD]
cpu0: <ACPI CPU> on acpi0
ACPI: SSDT @ 0x0xcfe78e06/0x01DD (v  1  PmRef  Cpu0Ist 0x00003000 INTL  
0x20050228)
cpu0: switching to generic Cx mode
est0: <Enhanced SpeedStep Frequency Control> on cpu0
est0: Invalid id16 (set, cur) = (1563, 2344)
est0: Invalid freq 1600, ignored.
p4tcc0: <CPU Frequency Thermal Control> on cpu0
cpu1: <ACPI CPU> on acpi0
ACPI: SSDT @ 0x0xcfe78fe3/0x016E (v  1  PmRef  Cpu1Ist 0x00003000 INTL  
0x20050228)
est1: <Enhanced SpeedStep Frequency Control> on cpu1
est1: Invalid id16 (set, cur) = (1563, 2344)
est1: Invalid freq 1600, ignored.
p4tcc1: <CPU Frequency Thermal Control> on cpu1
cpu2: <ACPI CPU> on acpi0
ACPI: SSDT @ 0x0xcfe79151/0x016E (v  1  PmRef  Cpu2Ist 0x00003000 INTL  
0x20050228)
est2: <Enhanced SpeedStep Frequency Control> on cpu2
est2: Invalid id16 (set, cur) = (1563, 2344)
est2: Invalid freq 1600, ignored.
p4tcc2: <CPU Frequency Thermal Control> on cpu2
cpu3: <ACPI CPU> on acpi0
ACPI: SSDT @ 0x0xcfe792bf/0x016E (v  1  PmRef  Cpu3Ist 0x00003000 INTL  
0x20050228)
est3: <Enhanced SpeedStep Frequency Control> on cpu3
est3: Invalid id16 (set, cur) = (1563, 2344)
est3: Invalid freq 1600, ignored.
p4tcc3: <CPU Frequency Thermal Control> on cpu3
ex_isa_identify()
atkbdc: atkbdc0 already exists; skipping it
fdc: fdc0 already exists; skipping it
ppc: ppc0 already exists; skipping it
sio: sio0 already exists; skipping it
sio: sio1 already exists; skipping it
ahc_isa_probe 1: ioport 0x1c00 alloc failed
sc: sc0 already exists; skipping it
vga: vga0 already exists; skipping it
isa_probe_children: disabling PnP devices
isa_probe_children: probing non-PnP devices
orm0: <ISA Option ROM> at iomem 0xc0000-0xcafff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sc0: fb0, kbd1, terminal emulator: sc (syscons terminal)
sio2: not probed (disabled)
sio3: not probed (disabled)
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
isa_probe_children: probing PnP devices
umass0: <Y-E DATA USB Floppy Drive, class 0/0, rev 1.10/5.01, addr 2> on uhub0
umass0:0:0:-1: Attached to scbus0
Device configuration finished.
Reducing kern.maxvnodes 343811 -> 100000
procfs registered
lapic: Divisor 2, Frequency 133000612 hz
Timecounter "TSC" frequency 2394010944 Hz quality -100
Timecounters tick every 1.000 msec
lo0: bpf attached
hptrr: no controller detected.
ata2-slave: pio=PIO4 wdma=WDMA2 udma=UDMA33 cable=80 wire
acd0: setting PIO4 on IT8213F chip
acd0: <DVD-ROM UJDA780/1.50> DVDROM drive at ata2 as slave
acd0: read 4134KB/s (4134KB/s), 2048KB buffer, PIO4
acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, DVDRAM, packet
acd0: Writes:
acd0: Audio: play, 256 volume levels
acd0: Mechanism: ejectable tray, unlocked
acd0: Medium: CD-R 120mm data disc
ata3-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire
ad6: 305245MB <Seagate ST3320620AS 3.AAK> at ata3-master SATA300
ad6: 625142448 sectors [620181C/16H/63S] 16 sectors/interrupt 1 depth queue
ad6: Intel check1 failed
ad6: Adaptec check1 failed
ad6: LSI (v3) check1 failed
ad6: LSI (v2) check1 failed
ad6: FreeBSD check1 failed
ata4-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire
ad8: 305245MB <Seagate ST3320620AS 3.AAK> at ata4-master SATA300
ad8: 625142448 sectors [620181C/16H/63S] 16 sectors/interrupt 1 depth queue
ad8: Intel check1 failed
ad8: Adaptec check1 failed
ad8: LSI (v3) check1 failed
ad8: LSI (v2) check1 failed
ad8: FreeBSD check1 failed
ata5-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire
ad10: 305245MB <Seagate ST3320620AS 3.AAC> at ata5-master SATA300
ad10: 625142448 sectors [620181C/16H/63S] 16 sectors/interrupt 1 depth queue
ad10: Intel check1 failed
ad10: Adaptec check1 failed
ad10: LSI (v3) check1 failed
ad10: LSI (v2) check1 failed
ad10: FreeBSD check1 failed
ata6-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire
ad12: 305245MB <Seagate ST3320620AS 3.AAC> at ata6-master SATA300
ad12: 625142448 sectors [620181C/16H/63S] 16 sectors/interrupt 1 depth queue
ad12: Intel check1 failed
ad12: Adaptec check1 failed
ad12: LSI (v3) check1 failed
ad12: LSI (v2) check1 failed
ad12: FreeBSD check1 failed
(probe0:umass-sim0:0:0:0): Down reving Protocol Version from 2 to 0?
acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00
(probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
(probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
(probe0:umass-sim0:0:0:0): SCSI Status: Check Condition
(probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0
(probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed
(probe0:umass-sim0:0:0:0): (probe0:umass-sim0:0:0:0): TEST UNIT READY.  
CDB: 0 0 0 0 0 0
(probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0
(probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed
Retrying Command (per Sense Data)
(probe0:umass-sim0:0:0:0): Retrying Command
pass0 at umass-sim0 bus 0 target 0 lun 0
pass0: <Y-E DATA USB-FDU 5.01> Removable Direct Access SCSI-0 device
pass0: 20KB/s transfers
ATA PseudoRAID loaded
SMP: AP CPU #1 Launched!
cpu1 AP:
      ID: 0x01000000   VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff
   lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff
   timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000
SMP: AP CPU #3 Launched!
cpu3 AP:
      ID: 0x03000000   VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff
   lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff
   timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000
SMP: AP CPU #2 Launched!
cpu2 AP:
      ID: 0x02000000   VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff
   lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff
   timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000
ioapic0: Assigning ISA IRQ 1 to local APIC 0
ioapic0: Assigning ISA IRQ 3 to local APIC 1
ioapic0: Assigning ISA IRQ 4 to local APIC 2
ioapic0: Assigning ISA IRQ 6 to local APIC 3
ioapic0: Assigning ISA IRQ 7 to local APIC 0
ioapic0: Assigning ISA IRQ 9 to local APIC 1
ioapic0: Assigning ISA IRQ 12 to local APIC 2
ioapic0: Assigning PCI IRQ 16 to local APIC 3
ioapic0: Assigning PCI IRQ 17 to local APIC 0
ioapic0: Assigning PCI IRQ 18 to local APIC 1
ioapic0: Assigning PCI IRQ 22 to local APIC 2
ioapic0: Assigning PCI IRQ 23 to local APIC 3
msi: Assigning MSI IRQ 256 to local APIC 0
msi: Assigning MSI IRQ 257 to local APIC 1
da0 at umass-sim0 bus 0 target 0 lun 0
da0: <Y-E DATA USB-FDU 5.01> Removable Direct Access SCSI-0 device
da0: 20KB/s transfers
da0: 1MB (2880 512 byte sectors: 64H 32S/T 1C)
acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00
GEOM_LABEL: Label for provider acd0 is iso9660/FreeBSD_Install.
GEOM: new disk ad6
acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00
acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00
GEOM: new disk ad8
GEOM: new disk ad10
GEOM: new disk ad12
GEOM: new disk da0
acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00
GEOM_MIRROR: Device mirror/gm0 launched (3/3).
GEOM_LABEL: Label for provider ad12s1 is ufsid/488efb68e5c53bb1.
GEOM_LABEL: Label for provider mirror/gm0s1a is ufsid/489cb5723873a365.
GEOM_LABEL: Label for provider mirror/gm0s1d is ufsid/489cb5806d417263.
GEOM_LABEL: Label for provider mirror/gm0s1e is ufsid/489cb5847a0f8baa.
GEOM_LABEL: Label for provider mirror/gm0s1f is ufsid/489cb58839896589.
GEOM_LABEL: Label for provider mirror/gm0s1g is ufsid/489cb58c07734311.
Trying to mount root from ufs:/dev/mirror/gm0s1a
start_init: trying /sbin/init
GEOM_LABEL: Label ufsid/489cb5723873a365 removed.
GEOM_LABEL: Label for provider mirror/gm0s1a is ufsid/489cb5723873a365.
GEOM_LABEL: Label ufsid/489cb5806d417263 removed.
GEOM_LABEL: Label for provider mirror/gm0s1d is ufsid/489cb5806d417263.
GEOM_LABEL: Label ufsid/489cb5847a0f8baa removed.
GEOM_LABEL: Label for provider mirror/gm0s1e is ufsid/489cb5847a0f8baa.
GEOM_LABEL: Label ufsid/489cb58839896589 removed.
GEOM_LABEL: Label for provider mirror/gm0s1f is ufsid/489cb58839896589.
GEOM_LABEL: Label ufsid/489cb58c07734311 removed.
GEOM_LABEL: Label for provider mirror/gm0s1g is ufsid/489cb58c07734311.
GEOM_LABEL: Label ufsid/489cb5723873a365 removed.
GEOM_LABEL: Label ufsid/489cb5806d417263 removed.
GEOM_LABEL: Label ufsid/489cb5847a0f8baa removed.
GEOM_LABEL: Label ufsid/489cb58839896589 removed.
GEOM_LABEL: Label ufsid/489cb58c07734311 removed.
em1: Link is up 1000 Mbps Full Duplex
em0: Link is up 1000 Mbps Full Duplex
em0: link state changed to UP



-- 
ian j hart

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


From bms at incunabulum.net  Mon Jul  6 14:30:05 2009
From: bms at incunabulum.net (Bruce Simpson)
Date: Mon Jul  6 14:30:14 2009
Subject: Merging a GCC bug fix to RELENG_7 - how?
Message-ID: <4A520A69.4010000@incunabulum.net>

Hi all,

This GCC bug bites us in the Boost regression tests in a number of places.

Uh oh, I've stepped on the one-line fix bomb:
    http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31899
    http://gcc.gnu.org/viewcvs?view=rev&revision=129199

What's funny is that COPYING in the root of that branch is GPLv2, but 
the affected file's license is GPLv3.

So what on earth do we do?

thanks,
BMS
From miklosovic.freebsd at gmail.com  Mon Jul  6 16:07:35 2009
From: miklosovic.freebsd at gmail.com (Stefan Miklosovic)
Date: Mon Jul  6 16:07:42 2009
Subject: acer aspire 3613 acpi problem
Message-ID: <f99a79ec0907060841s74cb46c8xc80e2f14582bb4d2@mail.gmail.com>

hi all,

I have a problem with acpi at acer aspire 3613.
While it boot, errors appears.

Here are links for more information. I did like
is written in acpi handbook for freebsd.

I also run iasl command, but nothing changed.

http://dexter.kmit.sk/~stewe/asl_output<http://dexter.kmit.sk/%7Estewe/asl_output>
http://dexter.kmit.sk/~stewe/hw.acpi<http://dexter.kmit.sk/%7Estewe/hw.acpi>
http://dexter.kmit.sk/~stewe/stewe-freebsd72.asl<http://dexter.kmit.sk/%7Estewe/stewe-freebsd72.asl>
http://dexter.kmit.sk/~stewe/dmesg_verbose<http://dexter.kmit.sk/%7Estewe/dmesg_verbose>

thank you

have a nice day
From sulfurfff at gmail.com  Mon Jul  6 16:33:56 2009
From: sulfurfff at gmail.com (Ishmael F.E.)
Date: Mon Jul  6 16:34:03 2009
Subject: upgrading ports without recompiling
Message-ID: <ed5c0bbe0907060904m2a93aab7r9b17b8b5529dd8f0@mail.gmail.com>

Hi there
.
?How can I upgrade my ports without having to recompile everything?
.
I allready did
# freebsd-update -r 7.2-RELEASE upgrade install
# reboot
# freebsd-update install
.
But it didn'nt upgrade the ports, so I tryed
# portupgrade -af
but it tried to compile everything
.
I also tried
# portsnap fetch
# portsnap extract
# portsnap fetch update
# portupgrade -a --batch -u -P
.
but it also tried to compile everything
.
so, ?how can I upgrade the ports?
unfortunatley I don't have time to compile my 64bit system
.
.
-- 
[============================]
[En muchos lugares, tomar fotos es visto como]
[una costumbre vil y reprensible                      ]
[============================]
From mike at jellydonut.org  Mon Jul  6 17:16:39 2009
From: mike at jellydonut.org (Michael Proto)
Date: Mon Jul  6 17:16:45 2009
Subject: upgrading ports without recompiling
In-Reply-To: <ed5c0bbe0907060904m2a93aab7r9b17b8b5529dd8f0@mail.gmail.com>
References: <ed5c0bbe0907060904m2a93aab7r9b17b8b5529dd8f0@mail.gmail.com>
Message-ID: <1de79840907060947j6cdf96f6k7966a866ef02a13b@mail.gmail.com>

On Mon, Jul 6, 2009 at 12:04 PM, Ishmael F.E.<sulfurfff@gmail.com> wrote:
> Hi there
> .
> ?How can I upgrade my ports without having to recompile everything?
> .
> I allready did
> # freebsd-update -r 7.2-RELEASE upgrade install
> # reboot
> # freebsd-update install
> .
> But it didn'nt upgrade the ports, so I tryed
> # portupgrade -af
> but it tried to compile everything
> .
> I also tried
> # portsnap fetch
> # portsnap extract
> # portsnap fetch update
> # portupgrade -a --batch -u -P
> .
> but it also tried to compile everything
> .
> so, ?how can I upgrade the ports?
> unfortunatley I don't have time to compile my 64bit system


You could use packages provided by the FreeBSD package repositories...

portupgrade -aP

Although those packages will contain the standard port options, which
may differ from your installed ports if you compiled them originally
and changed any of the options screens. If you're looking to upgrade
ports with custom options applied, then rebuilding your ports from
source is your only real option.


-Proto
From mike at jellydonut.org  Mon Jul  6 17:20:17 2009
From: mike at jellydonut.org (Michael Proto)
Date: Mon Jul  6 17:20:24 2009
Subject: upgrading ports without recompiling
In-Reply-To: <1de79840907060947j6cdf96f6k7966a866ef02a13b@mail.gmail.com>
References: <ed5c0bbe0907060904m2a93aab7r9b17b8b5529dd8f0@mail.gmail.com>
	<1de79840907060947j6cdf96f6k7966a866ef02a13b@mail.gmail.com>
Message-ID: <1de79840907060948o28bfc23fu2aa325cb11802997@mail.gmail.com>

On Mon, Jul 6, 2009 at 12:47 PM, Michael Proto<mike@jellydonut.org> wrote:

> You could use packages provided by the FreeBSD package repositories...
>
> portupgrade -aP
>
> Although those packages will contain the standard port options, which
> may differ from your installed ports if you compiled them originally
> and changed any of the options screens. If you're looking to upgrade
> ports with custom options applied, then rebuilding your ports from
> source is your only real option.
>
>
> -Proto
>

Sorry, try "portupgrade -aPP" to use ONLY precompiled packages.


-Proto
From tevans.uk at googlemail.com  Mon Jul  6 17:28:13 2009
From: tevans.uk at googlemail.com (Tom Evans)
Date: Mon Jul  6 17:28:20 2009
Subject: upgrading ports without recompiling
In-Reply-To: <ed5c0bbe0907060904m2a93aab7r9b17b8b5529dd8f0@mail.gmail.com>
References: <ed5c0bbe0907060904m2a93aab7r9b17b8b5529dd8f0@mail.gmail.com>
Message-ID: <1246899446.2437.227.camel@strangepork.london.mintel.ad>

On Mon, 2009-07-06 at 11:04 -0500, Ishmael F.E. wrote:
> Hi there
> .
> ?How can I upgrade my ports without having to recompile everything?
> .
> I allready did
> # freebsd-update -r 7.2-RELEASE upgrade install
> # reboot
> # freebsd-update install
> .
> But it didn'nt upgrade the ports, so I tryed
> # portupgrade -af
> but it tried to compile everything
> .
> I also tried
> # portsnap fetch
> # portsnap extract
> # portsnap fetch update
> # portupgrade -a --batch -u -P
> .
> but it also tried to compile everything
> .
> so, ?how can I upgrade the ports?
> unfortunatley I don't have time to compile my 64bit system
> .
> .

portupgrade will use packages where available with the -P flag, and will
only use packages with the -PP flag. However, since you say it failed to
find packages with -P, falling back to recompiling, then it will
probably fail even more with -PP.

man portupgrade for more details.

Cheers

Tom

From amarat at ksu.ru  Mon Jul  6 17:46:29 2009
From: amarat at ksu.ru (Marat N.Afanasyev)
Date: Mon Jul  6 17:47:00 2009
Subject: bug in ufs?
In-Reply-To: <4A523518.7050008@gmx.de>
References: <4A50E947.9020608@ksu.ru> <4A523518.7050008@gmx.de>
Message-ID: <4A523849.1070001@ksu.ru>

Ralf Folkerts wrote:
> Marat N.Afanasyev wrote:
>> hello!
>>
>> i have a strange problem with writing data to my ufs2+su filesystem.
>>
>> 1. i made a 1T gpt partition on my storage server, and formatted it:
>> newfs -U -m 0 -o time -i 32768 /dev/da1p3a
>>
>> 2. i tried to move data from other servers to this filesystem, total 
>> size of files is slightly less than 1T
>>
>> 3. i encountered a 'No space left on device' while i still have 11G of 
>> free space and about 13 million free inodes on the filesystem:
>>
>> #df -ih
>> Filesystem     Size    Used   Avail Capacity  iused    ifree %iused 
>> Mounted on
>> /dev/da1p3a    1.0T    1.0T     11G    99% 20397465 13363173   60% 
>> /mnt/45_114
>>
>> all i want to know is whether this is a bug or a feature? and if such 
>> a behavior is well-known, where can i read about it?
> Hi Marat,
> 
> just a guess: Are there sparse Files on the Source System that are not 
> being detected by the Tool you used to restore the data? If you used 
> (bsd)tar, did you try -S?
> 
> A while ago I ran into a similar Problem when copying 
> Oracle-Database-Files (on Linux, though) and the -S - Option came to 
> rescue.
> 
> Cheers,
> _ralf_

i have a huge amount of small files on the source systems, as you can 
see they have about 20 million files and almost each of them is jpeg or 
gif. afaik, there are no sparse files at all.

i still cannot figure out what is it: a free space leak in ufs2+su or 
bug in statfs(3), that is used in df, or something else.

-- 
SY, Marat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3221 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090706/cfe596e6/smime.bin
From tkjacobsen at gmail.com  Mon Jul  6 18:25:15 2009
From: tkjacobsen at gmail.com (Troels Kofoed Jacobsen)
Date: Mon Jul  6 18:25:21 2009
Subject: upgrading ports without recompiling
In-Reply-To: <1246899446.2437.227.camel@strangepork.london.mintel.ad>
References: <ed5c0bbe0907060904m2a93aab7r9b17b8b5529dd8f0@mail.gmail.com>
	<1246899446.2437.227.camel@strangepork.london.mintel.ad>
Message-ID: <200907061951.56023.tkjacobsen@gmail.com>

On Monday 06 July 2009 18:57:26 Tom Evans wrote:
> On Mon, 2009-07-06 at 11:04 -0500, Ishmael F.E. wrote:
> > Hi there
> > .
> > ?How can I upgrade my ports without having to recompile everything?
> > .
> > I allready did
> > # freebsd-update -r 7.2-RELEASE upgrade install
> > # reboot
> > # freebsd-update install
> > .
> > But it didn'nt upgrade the ports, so I tryed
> > # portupgrade -af
> > but it tried to compile everything
> > .
> > I also tried
> > # portsnap fetch
> > # portsnap extract
> > # portsnap fetch update
> > # portupgrade -a --batch -u -P
> > .
> > but it also tried to compile everything
> > .
> > so, ?how can I upgrade the ports?
> > unfortunatley I don't have time to compile my 64bit system
> > .
> > .
>
> portupgrade will use packages where available with the -P flag, and will
> only use packages with the -PP flag. However, since you say it failed to
> find packages with -P, falling back to recompiling, then it will
> probably fail even more with -PP.
>
> man portupgrade for more details.
>
> Cheers
>
> Tom
>
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"

Have a look at pkg_upgrade from bsdadminscripts (sysutils/bsdadminscripts).

From man page:
DESCRIPTION
     The pkg_upgrade script allows the updating, installing and replacing of
     packages without using a local copy of the ports tree. Instead most
     required information is listed in an INDEX file that is kept in sync with
     the package server by uma(1).

I found it to be the best solution when still using packages on my laptop.

Best regards
Troels Kofoed Jacobsen
From ianjhart at ntlworld.com  Mon Jul  6 19:01:27 2009
From: ianjhart at ntlworld.com (Ian J Hart)
Date: Mon Jul  6 19:01:36 2009
Subject: trap 12
In-Reply-To: <20090703100627.197838cphjnil82s@10.248.192.16>
References: <20090703100627.197838cphjnil82s@10.248.192.16>
Message-ID: <20090706200115.1411150frxepkbuo@webmail.private.lan>

Quoting Ian J Hart <ianjhart@ntlworld.com>:

> Is this likely to be hardware? Details will follow if not.
>
> [copied from a screen dump]
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 1; apic id = 01
> fault virtual address = 0x0
> fault code = supervisor write data, page not present
> instruction pointer = 0x8:0xffffffff807c6c12
> stack pointer = 0x10:0xffffffff510e7890
> frame pointer = 0x10:0xffffff00054a6c90
> code segment = base 0x0, limit 0xfffff, type 0x1b
> = DPL 0, pres 1, long 1 def32 0, gran 1
> processor eflags = interrupt enabled, resume, IOPL = 0
> current process = 75372 (printf)
> trap number = 12
> panic: page fault
> cpuid = 1
> uptime: 8m2s
> Cannot dump. No dump device defined.
>
>

[First attempt apparently went into a blackhole. Apologies in you get  
this  twice.]

Some suggestions (off list) that it may not be hardware, so here's the  
follow up.

  supermicro 5015b-mt (super X7SBi mobo)
  Intel Q6600
  8GB ECC DDR2
  4x Seagate 320GB, two gmirror, two idle.

  issues so far

  1 OK) 7.x doesn't boot without hw.ata.atapi_dma=0. Not recently tested.
  2 OK) disks enumerate differently 6.x to 7.x. Painful if you  
hardwired the providor into your mirror.
  3) 6.3 and 7.2 remote dump over ssh fails with 'Disconnecting:  
Corrupted MAC on input.'
  4) On 7.2 (AFAICT from logs) random reboots under load. e.g. the  
above generated by a portupgrade run.

  I had dumpdev=none as I hadn't setup rc.early to allow savecore to work.

  In the interests of full disclosure I should say that this box was  
migrated from older hardware and then source upgraded from i386 to  
amd64 (6.3). Only one issue with that, format of accounting  
file.Upgrade to 7.2 and a rebuild or two since then.

  This box is our email server and there's no load. An identical box  
running as a gateway/firewall backup dumps okay and doesn't reboot.  
That box does drop network connections when running a cvsup server  
(treelist write), but when configured to pass through these  
connections (using balance) runs okay. But that's a story for another  
day as it's still on 6.x.

  Anyway, I put the two gmirror disks in another chassis and the  
remote dumps are now completing.This at least does seem to be hardware.

  Before I moved the two gmirror disks I synced a third disk. I can  
now test (most of) the original hardware and software.

  I was unable to make this single disk system crash, so I added two  
new disks and synced them.Now a 3 disk mirror, one disk idle.

  I've disabled sendmail and the email server so as not to clash.

  A portupgrade run caused a crash. I've setup coredumps so I can now  
test. Remote backup dumps do fail.

  xmail# kldstat
  Id Refs Address            Size     Name
   1    2 0xffffffff80100000 bd23e0   kernel
   2    1 0xffffffff80cd3000 20608    geom_mirror.ko

  I did have ipfw module loaded, but I got the crash without it so  
I've removed it (firewall_type=OPEN).

  Ran crashinfo, now have much more info than I need ;)

  Starting another portupgrade run now to see how reproducable this is.

  Later BIOS waiting in USB floppy.

  Copyright (c) 1992-2009 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.2-RELEASE-p1 #0: Tue Jun 16 18:03:10 BST 2009
      mungethis@hostname:/usr/obj/usr/src/sys/GENERIC
  Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff80cf5000.
  Preloaded elf obj module "/boot/kernel/geom_mirror.ko" at 0xffffffff80cf5220.
  Calibrating clock(s) ... i8254 clock: 1193168 Hz
  CLK_USE_I8254_CALIBRATION not specified - using default frequency
  Timecounter "i8254" frequency 1193182 Hz quality 0
  Calibrating TSC clock ... TSC clock: 2394010944 Hz
  CPU: Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz (2394.01-MHz  
K8-class CPU)
    Origin = "GenuineIntel"  Id = 0x6fb  Stepping = 11
     
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
    Features2=0xe3bd<SSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM>
    AMD Features=0x20100800<SYSCALL,NX,LM>
    AMD Features2=0x1<LAHF>
    Cores per package: 4
  usable memory = 8575127552 (8177 MB)
  Physical memory chunk(s):
  0x0000000000001000 - 0x0000000000098fff, 622592 bytes (152 pages)
  0x0000000000d27000 - 0x00000000cfe6ffff, 3474231296 bytes (848201 pages)
  0x0000000100000000 - 0x000000021f8b3fff, 4824186880 bytes (1177780 pages)
  avail memory  = 8273580032 (7890 MB)
  ACPI APIC Table: <PTLTD          APIC  >
  INTR: Adding local APIC 1 as a target
  INTR: Adding local APIC 2 as a target
  INTR: Adding local APIC 3 as a target
  FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
   cpu0 (BSP): APIC ID:  0
   cpu1 (AP): APIC ID:  1
   cpu2 (AP): APIC ID:  2
   cpu3 (AP): APIC ID:  3
  APIC: CPU 0 has ACPI ID 0
  APIC: CPU 1 has ACPI ID 1
  APIC: CPU 2 has ACPI ID 2
  APIC: CPU 3 has ACPI ID 3
  ULE: setup cpu group 0
  ULE: setup cpu 0
  ULE: adding cpu 0 to group 0: cpus 1 mask 0x1
  ULE: setup cpu group 1
  ULE: setup cpu 1
  ULE: adding cpu 1 to group 1: cpus 1 mask 0x2
  ULE: setup cpu group 2
  ULE: setup cpu 2
  ULE: adding cpu 2 to group 2: cpus 1 mask 0x4
  ULE: setup cpu group 3
  ULE: setup cpu 3
  ULE: adding cpu 3 to group 3: cpus 1 mask 0x8
  ACPI: RSDP @ 0x0xf69a0/0x0024 (v  2 PTLTD )
  ACPI: XSDT @ 0x0xcfe77290/0x00A4 (v  1 PTLTD     XSDT   0x06040000   
LTP 0x00000000)
  ACPI: FACP @ 0x0xcfe80d60/0x00F4 (v  3 INTEL           0x06040000  
PTL  0x00000002)
  ACPI: DSDT @ 0x0xcfe7a435/0x68B7 (v  1  INTEL BEARLAKE 0x06040000  
MSFT 0x03000000)
  ACPI: FACS @ 0x0xcfe83fc0/0x0040
  ACPI: _MAR @ 0x0xcfe80e54/0x0030 (v  1 Intel  OEMDMAR  0x06040000  
LOHR 0x00000001)
  ACPI: MCFG @ 0x0xcfe80e84/0x003C (v  1 PTLTD    MCFG   0x06040000   
LTP 0x00000000)
  ACPI: HPET @ 0x0xcfe80ec0/0x0038 (v  1 PTLTD  HPETTBL  0x06040000   
LTP 0x00000001)
  ACPI: APIC @ 0x0xcfe80ef8/0x0090 (v  1 PTLTD     APIC   0x06040000   
LTP 0x00000000)
  ACPI: BOOT @ 0x0xcfe80f88/0x0028 (v  1 PTLTD  $SBFTBL$ 0x06040000   
LTP 0x00000001)
  ACPI: SPCR @ 0x0xcfe80fb0/0x0050 (v  1 PTLTD  $UCRTBL$ 0x06040000  
PTL  0x00000001)
  ACPI: SSDT @ 0x0xcfe78ba7/0x025F (v  1  PmRef  Cpu0Tst 0x00003000  
INTL 0x20050228)
  ACPI: SSDT @ 0x0xcfe78b01/0x00A6 (v  1  PmRef  Cpu7Tst 0x00003000  
INTL 0x20050228)
  ACPI: SSDT @ 0x0xcfe78a5b/0x00A6 (v  1  PmRef  Cpu6Tst 0x00003000  
INTL 0x20050228)
  ACPI: SSDT @ 0x0xcfe789b5/0x00A6 (v  1  PmRef  Cpu5Tst 0x00003000  
INTL 0x20050228)
  ACPI: SSDT @ 0x0xcfe7890f/0x00A6 (v  1  PmRef  Cpu4Tst 0x00003000  
INTL 0x20050228)
  ACPI: SSDT @ 0x0xcfe78869/0x00A6 (v  1  PmRef  Cpu3Tst 0x00003000  
INTL 0x20050228)
  ACPI: SSDT @ 0x0xcfe787c3/0x00A6 (v  1  PmRef  Cpu2Tst 0x00003000  
INTL 0x20050228)
  ACPI: SSDT @ 0x0xcfe7871d/0x00A6 (v  1  PmRef  Cpu1Tst 0x00003000  
INTL 0x20050228)
  ACPI: SSDT @ 0x0xcfe77334/0x13E9 (v  1  PmRef    CpuPm 0x00003000  
INTL 0x20050228)
  MADT: Found IO APIC ID 4, Interrupt 0 at 0xfec00000
  ioapic0: Routing external 8259A's -> intpin 0
  MADT: Found IO APIC ID 5, Interrupt 24 at 0xfecc0000
  lapic0: Routing NMI -> LINT1
  lapic0: LINT1 trigger: edge
  lapic0: LINT1 polarity: high
  lapic1: Routing NMI -> LINT1
  lapic1: LINT1 trigger: edge
  lapic1: LINT1 polarity: high
  lapic2: Routing NMI -> LINT1
  lapic2: LINT1 trigger: edge
  lapic2: LINT1 polarity: high
  lapic3: Routing NMI -> LINT1
  lapic3: LINT1 trigger: edge
  lapic3: LINT1 polarity: high
  MADT: Interrupt override: source 0, irq 2
  ioapic0: Routing IRQ 0 -> intpin 2
  MADT: Interrupt override: source 9, irq 9
  ioapic0: intpin 9 trigger: level
  ioapic0 <Version 2.0> irqs 0-23 on motherboard
  ioapic1 <Version 2.0> irqs 24-47 on motherboard
  cpu0 BSP:
       ID: 0x00000000   VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff
    lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff
    timer: 0x000100ef therm: 0x00000200 err: 0x00010000 pcm: 0x00010000
  wlan_amrr: <AMRR Transmit Rate Control Algorithm>
  wlan: <802.11 Link Layer>
  null: <null device, zero device>
  random: <entropy source, Software, Yarrow>
  nfslock: pseudo-device
  kbd: new array size 4
  kbd1 at kbdmux0
  mem: <memory>
  io: <I/O>
  hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2 (Jun 16 2009  
18:03:00)
  acpi0: <PTLTD    XSDT> on motherboard
  ioapic0: routing intpin 9 (ISA IRQ 9) to vector 48
  acpi0: [MPSAFE]
  acpi0: [ITHREAD]
  acpi0: Power Button (fixed)
  AcpiOsDerivePciId: \\_SB_.PCI0.REGS -> bus 0 dev 0 func 0
  AcpiOsDerivePciId: \\_SB_.PCI0.IGD0.IGDP -> bus 0 dev 2 func 0
  AcpiOsDerivePciId: \\_SB_.PCI0.LPC0.REGS -> bus 0 dev 31 func 0
  AcpiOsDerivePciId: \\_SB_.PCI0.LPC0.PIRX -> bus 0 dev 31 func 0
  AcpiOsDerivePciId: \\_SB_.PCI0.LPC0.PIRY -> bus 0 dev 31 func 0
  ACPI timer: 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 -> 10
  Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
  acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
  pci_link0:        Index  IRQ  Rtd  Ref  IRQs
    Initial Probe       0    5   N     0  3 4 5 6 7 10 11 12 14 15
    Validation          0    5   N     0  3 4 5 6 7 10 11 12 14 15
    After Disable       0  255   N     0  3 4 5 6 7 10 11 12 14 15
  pci_link1:        Index  IRQ  Rtd  Ref  IRQs
    Initial Probe       0   10   N     0  3 4 5 6 7 10 11 12 14 15
    Validation          0   10   N     0  3 4 5 6 7 10 11 12 14 15
    After Disable       0  255   N     0  3 4 5 6 7 10 11 12 14 15
  pci_link2:        Index  IRQ  Rtd  Ref  IRQs
    Initial Probe       0   11   N     0  3 4 5 6 7 10 11 12 14 15
    Validation          0   11   N     0  3 4 5 6 7 10 11 12 14 15
    After Disable       0  255   N     0  3 4 5 6 7 10 11 12 14 15
  pci_link3:        Index  IRQ  Rtd  Ref  IRQs
    Initial Probe       0  255   N     0  3 4 5 6 7 10 11 12 14 15
    Validation          0  255   N     0  3 4 5 6 7 10 11 12 14 15
    After Disable       0  255   N     0  3 4 5 6 7 10 11 12 14 15
  pci_link4:        Index  IRQ  Rtd  Ref  IRQs
    Initial Probe       0  255   N     0  3 4 5 6 7 10 11 12 14 15
    Validation          0  255   N     0  3 4 5 6 7 10 11 12 14 15
    After Disable       0  255   N     0  3 4 5 6 7 10 11 12 14 15
  pci_link5:        Index  IRQ  Rtd  Ref  IRQs
    Initial Probe       0  255   N     0  3 4 5 6 7 10 11 12 14 15
    Validation          0  255   N     0  3 4 5 6 7 10 11 12 14 15
    After Disable       0  255   N     0  3 4 5 6 7 10 11 12 14 15
  pci_link6:        Index  IRQ  Rtd  Ref  IRQs
    Initial Probe       0   11   N     0  3 4 5 6 7 10 11 12 14 15
    Validation          0   11   N     0  3 4 5 6 7 10 11 12 14 15
    After Disable       0  255   N     0  3 4 5 6 7 10 11 12 14 15
  pci_link7:        Index  IRQ  Rtd  Ref  IRQs
    Initial Probe       0   10   N     0  3 4 5 6 7 10 11 12 14 15
    Validation          0   10   N     0  3 4 5 6 7 10 11 12 14 15
    After Disable       0  255   N     0  3 4 5 6 7 10 11 12 14 15
  acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
  acpi_hpet0: vend: 0x8086 rev: 0x1 num: 3 hz: 14318180 opts:  
legacy_route 64-bit
  Timecounter "HPET" frequency 14318180 Hz quality 900
  pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
  pci0: <ACPI PCI bus> on pcib0
  pci0: domain=0, physical bus=0
  found-> vendor=0x8086, dev=0x29f0, revid=0x01
          domain=0, bus=0, slot=0, func=0
          class=06-00-00, hdrtype=0x00, mfdev=0
          cmdreg=0x0106, statreg=0x2090, cachelnsz=0 (dwords)
          lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
  found-> vendor=0x8086, dev=0x29f1, revid=0x01
          domain=0, bus=0, slot=1, func=0
          class=06-04-00, hdrtype=0x01, mfdev=0
          cmdreg=0x0107, statreg=0x0010, cachelnsz=8 (dwords)
          lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns)
          intpin=a, irq=5
          powerspec 3  supports D0 D3  current D0
          MSI supports 1 message
  pcib0: matched entry for 0.1.INTA
  pcib0: slot 1 INTA hardwired to IRQ 16
  found-> vendor=0x8086, dev=0x2937, revid=0x02
          domain=0, bus=0, slot=26, func=0
          class=0c-03-00, hdrtype=0x00, mfdev=1
          cmdreg=0x0005, statreg=0x0290, cachelnsz=0 (dwords)
          lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
          intpin=a, irq=5
          map[20]: type I/O Port, range 32, base 0x1820, size  5, enabled
  pcib0: matched entry for 0.26.INTA
  pcib0: slot 26 INTA hardwired to IRQ 16
  found-> vendor=0x8086, dev=0x2938, revid=0x02
          domain=0, bus=0, slot=26, func=1
          class=0c-03-00, hdrtype=0x00, mfdev=0
          cmdreg=0x0005, statreg=0x0290, cachelnsz=0 (dwords)
          lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
          intpin=b, irq=10
          map[20]: type I/O Port, range 32, base 0x1840, size  5, enabled
  pcib0: matched entry for 0.26.INTB
  pcib0: slot 26 INTB hardwired to IRQ 17
  found-> vendor=0x8086, dev=0x2939, revid=0x02
          domain=0, bus=0, slot=26, func=2
          class=0c-03-00, hdrtype=0x00, mfdev=0
          cmdreg=0x0005, statreg=0x0290, cachelnsz=0 (dwords)
          lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
          intpin=c, irq=11
          map[20]: type I/O Port, range 32, base 0x1860, size  5, enabled
  pcib0: matched entry for 0.26.INTC
  pcib0: slot 26 INTC hardwired to IRQ 18
  found-> vendor=0x8086, dev=0x293c, revid=0x02
          domain=0, bus=0, slot=26, func=7
          class=0c-03-20, hdrtype=0x00, mfdev=0
          cmdreg=0x0106, statreg=0x0290, cachelnsz=0 (dwords)
          lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
          intpin=c, irq=11
          powerspec 2  supports D0 D3  current D0
          map[10]: type Memory, range 32, base 0xd8601800, size 10, enabled
  pcib0: matched entry for 0.26.INTC
  pcib0: slot 26 INTC hardwired to IRQ 18
  found-> vendor=0x8086, dev=0x2940, revid=0x02
          domain=0, bus=0, slot=28, func=0
          class=06-04-00, hdrtype=0x01, mfdev=1
          cmdreg=0x0000, statreg=0x0010, cachelnsz=8 (dwords)
          lattimer=0x00 (0 ns), mingnt=0x40 (16000 ns), maxlat=0x00 (0 ns)
          intpin=a, irq=5
          powerspec 2  supports D0 D3  current D0
          MSI supports 1 message
  pcib0: matched entry for 0.28.INTA
  pcib0: slot 28 INTA hardwired to IRQ 16
  found-> vendor=0x8086, dev=0x2948, revid=0x02
          domain=0, bus=0, slot=28, func=4
          class=06-04-00, hdrtype=0x01, mfdev=1
          cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords)
          lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns)
          intpin=a, irq=5
          powerspec 2  supports D0 D3  current D0
          MSI supports 1 message
  pcib0: matched entry for 0.28.INTA
  pcib0: slot 28 INTA hardwired to IRQ 16
  found-> vendor=0x8086, dev=0x294a, revid=0x02
          domain=0, bus=0, slot=28, func=5
          class=06-04-00, hdrtype=0x01, mfdev=1
          cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords)
          lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns)
          intpin=b, irq=10
          powerspec 2  supports D0 D3  current D0
          MSI supports 1 message
  pcib0: matched entry for 0.28.INTB
  pcib0: slot 28 INTB hardwired to IRQ 17
  found-> vendor=0x8086, dev=0x2934, revid=0x02
          domain=0, bus=0, slot=29, func=0
          class=0c-03-00, hdrtype=0x00, mfdev=1
          cmdreg=0x0005, statreg=0x0290, cachelnsz=0 (dwords)
          lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
          intpin=a, irq=10
          map[20]: type I/O Port, range 32, base 0x1880, size  5, enabled
  pcib0: matched entry for 0.29.INTA
  pcib0: slot 29 INTA hardwired to IRQ 23
  found-> vendor=0x8086, dev=0x2935, revid=0x02
          domain=0, bus=0, slot=29, func=1
          class=0c-03-00, hdrtype=0x00, mfdev=0
          cmdreg=0x0005, statreg=0x0290, cachelnsz=0 (dwords)
          lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
          intpin=b, irq=11
          map[20]: type I/O Port, range 32, base 0x18a0, size  5, enabled
  pcib0: matched entry for 0.29.INTB
  pcib0: slot 29 INTB hardwired to IRQ 22
  found-> vendor=0x8086, dev=0x2936, revid=0x02
          domain=0, bus=0, slot=29, func=2
          class=0c-03-00, hdrtype=0x00, mfdev=0
          cmdreg=0x0005, statreg=0x0290, cachelnsz=0 (dwords)
          lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
          intpin=c, irq=11
          map[20]: type I/O Port, range 32, base 0x18c0, size  5, enabled
  pcib0: matched entry for 0.29.INTC
  pcib0: slot 29 INTC hardwired to IRQ 18
  found-> vendor=0x8086, dev=0x293a, revid=0x02
          domain=0, bus=0, slot=29, func=7
          class=0c-03-20, hdrtype=0x00, mfdev=0
          cmdreg=0x0106, statreg=0x0290, cachelnsz=0 (dwords)
          lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
          intpin=a, irq=10
          powerspec 2  supports D0 D3  current D0
          map[10]: type Memory, range 32, base 0xd8601c00, size 10, enabled
  pcib0: matched entry for 0.29.INTA
  pcib0: slot 29 INTA hardwired to IRQ 23
  found-> vendor=0x8086, dev=0x244e, revid=0x92
          domain=0, bus=0, slot=30, func=0
          class=06-04-01, hdrtype=0x01, mfdev=0
          cmdreg=0x0107, statreg=0x0010, cachelnsz=0 (dwords)
          lattimer=0x00 (0 ns), mingnt=0x0c (3000 ns), maxlat=0x00 (0 ns)
  found-> vendor=0x8086, dev=0x2916, revid=0x02
          domain=0, bus=0, slot=31, func=0
          class=06-01-00, hdrtype=0x00, mfdev=1
          cmdreg=0x0007, statreg=0x0210, cachelnsz=0 (dwords)
          lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
  found-> vendor=0x8086, dev=0x2922, revid=0x02
          domain=0, bus=0, slot=31, func=2
          class=01-06-01, hdrtype=0x00, mfdev=0
          cmdreg=0x0007, statreg=0x02b0, cachelnsz=0 (dwords)
          lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
          intpin=b, irq=10
          powerspec 3  supports D0 D3  current D0
          MSI supports 16 messages
          map[10]: type I/O Port, range 32, base 0x1c50, size  3, enabled
          map[14]: type I/O Port, range 32, base 0x1c44, size  2, enabled
          map[18]: type I/O Port, range 32, base 0x1c48, size  3, enabled
          map[1c]: type I/O Port, range 32, base 0x1c40, size  2, enabled
          map[20]: type I/O Port, range 32, base 0x18e0, size  5, enabled
          map[24]: type Memory, range 32, base 0xd8601000, size 11, enabled
  pcib0: matched entry for 0.31.INTB
  pcib0: slot 31 INTB hardwired to IRQ 17
  found-> vendor=0x8086, dev=0x2930, revid=0x02
          domain=0, bus=0, slot=31, func=3
          class=0c-05-00, hdrtype=0x00, mfdev=0
          cmdreg=0x0001, statreg=0x0280, cachelnsz=0 (dwords)
          lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
          intpin=b, irq=10
          map[10]: type Memory, range 64, base 0xd8602000, size  8,  
memory disabled
          map[20]: type I/O Port, range 32, base 0x1100, size  5, enabled
  pcib0: matched entry for 0.31.INTB
  pcib0: slot 31 INTB hardwired to IRQ 17
  found-> vendor=0x8086, dev=0x2932, revid=0x02
          domain=0, bus=0, slot=31, func=6
          class=11-80-00, hdrtype=0x00, mfdev=0
          cmdreg=0x0002, statreg=0x0010, cachelnsz=0 (dwords)
          lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
          intpin=a, irq=5
          powerspec 3  supports D0 D3  current D0
          map[10]: type Memory, range 64, base 0xd8600000, size 12, enabled
  pcib0: matched entry for 0.31.INTA
  pcib0: slot 31 INTA hardwired to IRQ 16
  pcib1: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci0
  pcib1:   domain            0
  pcib1:   secondary bus     1
  pcib1:   subordinate bus   2
  pcib1:   I/O decode        0xf000-0xfff
  pcib1:   memory decode     0xd8100000-0xd81fffff
  pcib1:   no prefetched decode
  pcib1: could not get PCI interrupt routing table for  
\\_SB_.PCI0.PEG_ - AE_NOT_FOUND
  pci1: <ACPI PCI bus> on pcib1
  pci1: domain=0, physical bus=1
  found-> vendor=0x8086, dev=0x032c, revid=0x09
          domain=0, bus=1, slot=0, func=0
          class=06-04-00, hdrtype=0x01, mfdev=1
          cmdreg=0x0107, statreg=0x0010, cachelnsz=16 (dwords)
          lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns)
          powerspec 2  supports D0 D3  current D0
          MSI supports 1 message, 64 bit
  found-> vendor=0x8086, dev=0x0326, revid=0x09
          domain=0, bus=1, slot=0, func=1
          class=08-00-20, hdrtype=0x00, mfdev=1
          cmdreg=0x0106, statreg=0x0010, cachelnsz=0 (dwords)
          lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
          powerspec 2  supports D0 D3  current D0
          map[10]: type Memory, range 32, base 0xd8100000, size 12, enabled
  pcib1: requested memory range 0xd8100000-0xd8100fff: good
  pcib2: <ACPI PCI-PCI bridge> at device 0.0 on pci1
  pcib2:   domain            0
  pcib2:   secondary bus     2
  pcib2:   subordinate bus   2
  pcib2:   I/O decode        0xf000-0xfff
  pcib2:   no prefetched decode
  pci2: <ACPI PCI bus> on pcib2
  pci2: domain=0, physical bus=2
  uhci0: <UHCI (generic) USB controller> port 0x1820-0x183f irq 16 at  
device 26.0 on pci0
  uhci0: Reserved 0x20 bytes for rid 0x20 type 4 at 0x1820
  ioapic0: routing intpin 16 (PCI IRQ 16) to vector 49
  uhci0: [GIANT-LOCKED]
  uhci0: [ITHREAD]
  usb0: <UHCI (generic) USB controller> on uhci0
  usb0: USB revision 1.0
  uhub0: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
  uhub0: 2 ports with 2 removable, self powered
  uhci1: <UHCI (generic) USB controller> port 0x1840-0x185f irq 17 at  
device 26.1 on pci0
  uhci1: Reserved 0x20 bytes for rid 0x20 type 4 at 0x1840
  ioapic0: routing intpin 17 (PCI IRQ 17) to vector 50
  uhci1: [GIANT-LOCKED]
  uhci1: [ITHREAD]
  usb1: <UHCI (generic) USB controller> on uhci1
  usb1: USB revision 1.0
  uhub1: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1
  uhub1: 2 ports with 2 removable, self powered
  uhci2: <UHCI (generic) USB controller> port 0x1860-0x187f irq 18 at  
device 26.2 on pci0
  uhci2: Reserved 0x20 bytes for rid 0x20 type 4 at 0x1860
  ioapic0: routing intpin 18 (PCI IRQ 18) to vector 51
  uhci2: [GIANT-LOCKED]
  uhci2: [ITHREAD]
  usb2: <UHCI (generic) USB controller> on uhci2
  usb2: USB revision 1.0
  uhub2: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2
  uhub2: 2 ports with 2 removable, self powered
  ehci0: <EHCI (generic) USB 2.0 controller> mem 0xd8601800-0xd8601bff  
irq 18 at device 26.7 on pci0
  ehci0: Reserved 0x400 bytes for rid 0x10 type 3 at 0xd8601800
  ehci0: [GIANT-LOCKED]
  ehci0: [ITHREAD]
  usb3: EHCI version 1.0
  usb3: companion controllers, 2 ports each: usb0 usb1 usb2
  usb3: <EHCI (generic) USB 2.0 controller> on ehci0
  usb3: USB revision 2.0
  uhub3: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb3
  uhub3: 6 ports with 6 removable, self powered
  pcib3: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
  pcib3:   domain            0
  pcib3:   secondary bus     5
  pcib3:   subordinate bus   5
  pcib3:   I/O decode        0x0-0x0
  pcib3:   no prefetched decode
  pci5: <ACPI PCI bus> on pcib3
  pci5: domain=0, physical bus=5
  pcib4: <ACPI PCI-PCI bridge> irq 16 at device 28.4 on pci0
  pcib4:   domain            0
  pcib4:   secondary bus     13
  pcib4:   subordinate bus   13
  pcib4:   I/O decode        0x2000-0x2fff
  pcib4:   memory decode     0xd8000000-0xd80fffff
  pcib4:   no prefetched decode
  pci13: <ACPI PCI bus> on pcib4
  pci13: domain=0, physical bus=13
  found-> vendor=0x8086, dev=0x108c, revid=0x03
          domain=0, bus=13, slot=0, func=0
          class=02-00-00, hdrtype=0x00, mfdev=0
          cmdreg=0x0107, statreg=0x0010, cachelnsz=8 (dwords)
          lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
          intpin=a, irq=5
          powerspec 2  supports D0 D3  current D0
          MSI supports 1 message, 64 bit
          map[10]: type Memory, range 32, base 0xd8000000, size 17, enabled
  pcib4: requested memory range 0xd8000000-0xd801ffff: good
          map[18]: type I/O Port, range 32, base 0x2000, size  5, enabled
  pcib4: requested I/O range 0x2000-0x201f: in range
  pcib4: matched entry for 13.0.INTA
  pcib4: slot 0 INTA hardwired to IRQ 16
  em0: <Intel(R) PRO/1000 Network Connection 6.9.6> port 0x2000-0x201f  
mem 0xd8000000-0xd801ffff irq 16 at device 0.0 on pci13
  em0: Reserved 0x20000 bytes for rid 0x10 type 3 at 0xd8000000
  em0: attempting to allocate 1 MSI vectors (1 supported)
  msi: routing MSI IRQ 256 to vector 52
  em0: using IRQ 256 for MSI
  em0: Using MSI interrupt
  em0: [FILTER]
  em0: bpf attached
  em0: Ethernet address: 00:30:48:66:83:a0
  pcib5: <ACPI PCI-PCI bridge> irq 17 at device 28.5 on pci0
  pcib5:   domain            0
  pcib5:   secondary bus     15
  pcib5:   subordinate bus   15
  pcib5:   I/O decode        0x3000-0x3fff
  pcib5:   memory decode     0xd8200000-0xd82fffff
  pcib5:   no prefetched decode
  pci15: <ACPI PCI bus> on pcib5
  pci15: domain=0, physical bus=15
  found-> vendor=0x8086, dev=0x109a, revid=0x00
          domain=0, bus=15, slot=0, func=0
          class=02-00-00, hdrtype=0x00, mfdev=0
          cmdreg=0x0107, statreg=0x0010, cachelnsz=8 (dwords)
          lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
          intpin=a, irq=10
          powerspec 2  supports D0 D3  current D0
          MSI supports 1 message, 64 bit
          map[10]: type Memory, range 32, base 0xd8200000, size 17, enabled
  pcib5: requested memory range 0xd8200000-0xd821ffff: good
          map[18]: type I/O Port, range 32, base 0x3000, size  5, enabled
  pcib5: requested I/O range 0x3000-0x301f: in range
  pcib5: matched entry for 15.0.INTA
  pcib5: slot 0 INTA hardwired to IRQ 17
  em1: <Intel(R) PRO/1000 Network Connection 6.9.6> port 0x3000-0x301f  
mem 0xd8200000-0xd821ffff irq 17 at device 0.0 on pci15
  em1: Reserved 0x20000 bytes for rid 0x10 type 3 at 0xd8200000
  em1: attempting to allocate 1 MSI vectors (1 supported)
  msi: routing MSI IRQ 257 to vector 53
  em1: using IRQ 257 for MSI
  em1: Using MSI interrupt
  em1: [FILTER]
  em1: bpf attached
  em1: Ethernet address: 00:30:48:66:83:a1
  uhci3: <UHCI (generic) USB controller> port 0x1880-0x189f irq 23 at  
device 29.0 on pci0
  uhci3: Reserved 0x20 bytes for rid 0x20 type 4 at 0x1880
  ioapic0: routing intpin 23 (PCI IRQ 23) to vector 54
  uhci3: [GIANT-LOCKED]
  uhci3: [ITHREAD]
  usb4: <UHCI (generic) USB controller> on uhci3
  usb4: USB revision 1.0
  uhub4: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb4
  uhub4: 2 ports with 2 removable, self powered
  uhci4: <UHCI (generic) USB controller> port 0x18a0-0x18bf irq 22 at  
device 29.1 on pci0
  uhci4: Reserved 0x20 bytes for rid 0x20 type 4 at 0x18a0
  ioapic0: routing intpin 22 (PCI IRQ 22) to vector 55
  uhci4: [GIANT-LOCKED]
  uhci4: [ITHREAD]
  usb5: <UHCI (generic) USB controller> on uhci4
  usb5: USB revision 1.0
  uhub5: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb5
  uhub5: 2 ports with 2 removable, self powered
  uhci5: <UHCI (generic) USB controller> port 0x18c0-0x18df irq 18 at  
device 29.2 on pci0
  uhci5: Reserved 0x20 bytes for rid 0x20 type 4 at 0x18c0
  uhci5: [GIANT-LOCKED]
  uhci5: [ITHREAD]
  usb6: <UHCI (generic) USB controller> on uhci5
  usb6: USB revision 1.0
  uhub6: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb6
  uhub6: 2 ports with 2 removable, self powered
  ehci1: <EHCI (generic) USB 2.0 controller> mem 0xd8601c00-0xd8601fff  
irq 23 at device 29.7 on pci0
  ehci1: Reserved 0x400 bytes for rid 0x10 type 3 at 0xd8601c00
  ehci1: [GIANT-LOCKED]
  ehci1: [ITHREAD]
  usb7: EHCI version 1.0
  usb7: companion controllers, 2 ports each: usb4 usb5 usb6
  usb7: <EHCI (generic) USB 2.0 controller> on ehci1
  usb7: USB revision 2.0
  uhub7: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb7
  uhub7: 6 ports with 6 removable, self powered
  pcib6: <ACPI PCI-PCI bridge> at device 30.0 on pci0
  pcib6:   domain            0
  pcib6:   secondary bus     17
  pcib6:   subordinate bus   17
  pcib6:   I/O decode        0x4000-0x4fff
  pcib6:   memory decode     0xd8300000-0xd83fffff
  pcib6:   prefetched decode 0xd0000000-0xd7ffffff
  pcib6:   Subtractively decoded bridge.
  pci17: <ACPI PCI bus> on pcib6
  pci17: domain=0, physical bus=17
  found-> vendor=0x1002, dev=0x515e, revid=0x02
          domain=0, bus=17, slot=3, func=0
          class=03-00-00, hdrtype=0x00, mfdev=0
          cmdreg=0x0187, statreg=0x0290, cachelnsz=8 (dwords)
          lattimer=0x42 (1980 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns)
          intpin=a, irq=11
          powerspec 2  supports D0 D1 D2 D3  current D0
          map[10]: type Prefetchable Memory, range 32, base  
0xd0000000, size 27, enabled
  pcib6: requested memory range 0xd0000000-0xd7ffffff: good
          map[14]: type I/O Port, range 32, base 0x4000, size  8, enabled
  pcib6: requested I/O range 0x4000-0x40ff: in range
          map[18]: type Memory, range 32, base 0xd8300000, size 16, enabled
  pcib6: requested memory range 0xd8300000-0xd830ffff: good
  pcib6: matched entry for 17.3.INTA
  pcib6: slot 3 INTA hardwired to IRQ 22
  found-> vendor=0x1283, dev=0x8213, revid=0x00
          domain=0, bus=17, slot=4, func=0
          class=01-01-85, hdrtype=0x00, mfdev=0
          cmdreg=0x0007, statreg=0x0210, cachelnsz=0 (dwords)
          lattimer=0x40 (1920 ns), mingnt=0x08 (2000 ns), maxlat=0x08 (2000 ns)
          intpin=a, irq=10
          powerspec 2  supports D0 D3  current D0
          map[10]: type I/O Port, range 32, base 0x4420, size  3, enabled
  pcib6: requested I/O range 0x4420-0x4427: in range
          map[14]: type I/O Port, range 32, base 0x4414, size  2, enabled
  pcib6: requested I/O range 0x4414-0x4417: in range
          map[18]: type I/O Port, range 32, base 0x4418, size  3, enabled
  pcib6: requested I/O range 0x4418-0x441f: in range
          map[1c]: type I/O Port, range 32, base 0x4410, size  2, enabled
  pcib6: requested I/O range 0x4410-0x4413: in range
          map[20]: type I/O Port, range 32, base 0x4400, size  4, enabled
  pcib6: requested I/O range 0x4400-0x440f: in range
  pcib6: matched entry for 17.4.INTA
  pcib6: slot 4 INTA hardwired to IRQ 23
  vgapci0: <VGA-compatible display> port 0x4000-0x40ff mem  
0xd0000000-0xd7ffffff,0xd8300000-0xd830ffff irq 22 at device 3.0 on  
pci17
  atapci0: <ITE IT8213F UDMA133 controller> port  
0x4420-0x4427,0x4414-0x4417,0x4418-0x441f,0x4410-0x4413,0x4400-0x440f  
irq 23 at device 4.0 on pci17
  atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0x4400
  atapci0: [MPSAFE]
  atapci0: [ITHREAD]
  ata2: <ATA channel 0> on atapci0
  atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x4420
  atapci0: Reserved 0x4 bytes for rid 0x14 type 4 at 0x4414
  ata2: reset tp1 mask=03 ostat0=60 ostat1=50
  ata2: stat0=0x20 err=0x20 lsb=0x20 msb=0x20
  ata2: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb
  ata2: reset tp2 stat0=20 stat1=00 devices=0x8<ATAPI_SLAVE>
  ata2: [MPSAFE]
  ata2: [ITHREAD]
  isab0: <PCI-ISA bridge> at device 31.0 on pci0
  isa0: <ISA bus> on isab0
  atapci1: <Intel (ID=29228086) AHCI controller> port  
0x1c50-0x1c57,0x1c44-0x1c47,0x1c48-0x1c4f,0x1c40-0x1c43,0x18e0-0x18ff  
mem 0xd8601000-0xd86017ff irq 17 at device 31.2 on pci0
  atapci1: Reserved 0x20 bytes for rid 0x20 type 4 at 0x18e0
  atapci1: Reserved 0x800 bytes for rid 0x24 type 3 at 0xd8601000
  atapci1: [MPSAFE]
  atapci1: [ITHREAD]
  atapci1: AHCI Version 01.20 controller with 6 ports detected
  ata3: <ATA channel 0> on atapci1
  ata3: SATA connect time=0ms
  ata3: SIGNATURE: 00000101
  ata3: ahci_reset devices=0x1<ATA_MASTER>
  ata3: [MPSAFE]
  ata3: [ITHREAD]
  ata4: <ATA channel 1> on atapci1
  ata4: SATA connect time=0ms
  ata4: SIGNATURE: 00000101
  ata4: ahci_reset devices=0x1<ATA_MASTER>
  ata4: [MPSAFE]
  ata4: [ITHREAD]
  ata5: <ATA channel 2> on atapci1
  ata5: SATA connect time=0ms
  ata5: SIGNATURE: 00000101
  ata5: ahci_reset devices=0x1<ATA_MASTER>
  ata5: [MPSAFE]
  ata5: [ITHREAD]
  ata6: <ATA channel 3> on atapci1
  ata6: SATA connect time=0ms
  ata6: SIGNATURE: 00000101
  ata6: ahci_reset devices=0x1<ATA_MASTER>
  ata6: [MPSAFE]
  ata6: [ITHREAD]
  ata7: <ATA channel 4> on atapci1
  ata7: port not implemented
  ata7: [MPSAFE]
  ata7: [ITHREAD]
  ata8: <ATA channel 5> on atapci1
  ata8: port not implemented
  ata8: [MPSAFE]
  ata8: [ITHREAD]
  pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
  pci0: <dasp> at device 31.6 (no driver attached)
  acpi_button0: <Power Button> on acpi0
  atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
  atkbd0: <AT Keyboard> irq 1 on atkbdc0
  atkbd: the current kbd controller command byte 0047
  atkbd: keyboard ID 0x41ab (2)
  kbd0 at atkbd0
  kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000
  ioapic0: routing intpin 1 (ISA IRQ 1) to vector 56
  atkbd0: [GIANT-LOCKED]
  atkbd0: [ITHREAD]
  psm0: unable to allocate IRQ
  psmcpnp0: <PS/2 mouse port> irq 12 on acpi0
  psm0: current command byte:0047
  psm0: <PS/2 Mouse> irq 12 on atkbdc0
  ioapic0: routing intpin 12 (ISA IRQ 12) to vector 57
  psm0: [GIANT-LOCKED]
  psm0: [ITHREAD]
  psm0: model IntelliMouse Explorer, device ID 4-00, 5 buttons
  psm0: config:00000000, flags:00000008, packet size:4
  psm0: syncmask:08, syncbits:00
  sio0: configured irq 4 not in bitmap of probed irqs 0
  sio0: port may not be enabled
  sio0: irq maps: 0 0 0 0
  sio0: configured irq 4 not in bitmap of probed irqs 0
  sio0: port may not be enabled
  sio0: irq maps: 0 0 0 0
  sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
  sio0: type 16550A
  ioapic0: routing intpin 4 (ISA IRQ 4) to vector 58
  sio0: [FILTER]
  sio1: configured irq 3 not in bitmap of probed irqs 0
  sio1: port may not be enabled
  sio1: irq maps: 0 0 0 0
  sio1: configured irq 3 not in bitmap of probed irqs 0
  sio1: port may not be enabled
  sio1: irq maps: 0 0 0 0
  sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
  sio1: type 16550A
  ioapic0: routing intpin 3 (ISA IRQ 3) to vector 59
  sio1: [FILTER]
  fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
  fdc0: ic_type 90 part_id 80
  ioapic0: routing intpin 6 (ISA IRQ 6) to vector 60
  fdc0: [FILTER]
  ppc0: using extended I/O port range
  ppc0: ECP SPP ECP+EPP SPP
  ppc0: <Parallel port> port 0x378-0x37f,0x778-0x77f irq 7 drq 3 on acpi0
  ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
  ppc0: FIFO with 16/16/9 bytes threshold
  ppbus0: <Parallel port bus> on ppc0
  ioapic0: routing intpin 7 (ISA IRQ 7) to vector 61
  ppbus0: [MPSAFE]
  ppbus0: [ITHREAD]
  plip0: <PLIP network interface> on ppbus0
  plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag
  plip0: bpf attached
  lpt0: <Printer> on ppbus0
  lpt0: Interrupt-driven port
  ppi0: <Parallel I/O> on ppbus0
  ppc0: [GIANT-LOCKED]
  ppc0: [ITHREAD]
  cpu0: <ACPI CPU> on acpi0
  ACPI: SSDT @ 0x0xcfe78e06/0x01DD (v  1  PmRef  Cpu0Ist 0x00003000  
INTL 0x20050228)
  cpu0: switching to generic Cx mode
  est0: <Enhanced SpeedStep Frequency Control> on cpu0
  est0: Invalid id16 (set, cur) = (1563, 2344)
  est0: Invalid freq 1600, ignored.
  p4tcc0: <CPU Frequency Thermal Control> on cpu0
  cpu1: <ACPI CPU> on acpi0
  ACPI: SSDT @ 0x0xcfe78fe3/0x016E (v  1  PmRef  Cpu1Ist 0x00003000  
INTL 0x20050228)
  est1: <Enhanced SpeedStep Frequency Control> on cpu1
  est1: Invalid id16 (set, cur) = (1563, 2344)
  est1: Invalid freq 1600, ignored.
  p4tcc1: <CPU Frequency Thermal Control> on cpu1
  cpu2: <ACPI CPU> on acpi0
  ACPI: SSDT @ 0x0xcfe79151/0x016E (v  1  PmRef  Cpu2Ist 0x00003000  
INTL 0x20050228)
  est2: <Enhanced SpeedStep Frequency Control> on cpu2
  est2: Invalid id16 (set, cur) = (1563, 2344)
  est2: Invalid freq 1600, ignored.
  p4tcc2: <CPU Frequency Thermal Control> on cpu2
  cpu3: <ACPI CPU> on acpi0
  ACPI: SSDT @ 0x0xcfe792bf/0x016E (v  1  PmRef  Cpu3Ist 0x00003000  
INTL 0x20050228)
  est3: <Enhanced SpeedStep Frequency Control> on cpu3
  est3: Invalid id16 (set, cur) = (1563, 2344)
  est3: Invalid freq 1600, ignored.
  p4tcc3: <CPU Frequency Thermal Control> on cpu3
  ex_isa_identify()
  atkbdc: atkbdc0 already exists; skipping it
  fdc: fdc0 already exists; skipping it
  ppc: ppc0 already exists; skipping it
  sio: sio0 already exists; skipping it
  sio: sio1 already exists; skipping it
  ahc_isa_probe 1: ioport 0x1c00 alloc failed
  sc: sc0 already exists; skipping it
  vga: vga0 already exists; skipping it
  isa_probe_children: disabling PnP devices
  isa_probe_children: probing non-PnP devices
  orm0: <ISA Option ROM> at iomem 0xc0000-0xcafff on isa0
  sc0: <System console> at flags 0x100 on isa0
  sc0: VGA <16 virtual consoles, flags=0x300>
  sc0: fb0, kbd1, terminal emulator: sc (syscons terminal)
  sio2: not probed (disabled)
  sio3: not probed (disabled)
  vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
  isa_probe_children: probing PnP devices
  umass0: <Y-E DATA USB Floppy Drive, class 0/0, rev 1.10/5.01, addr  
2> on uhub0
  umass0:0:0:-1: Attached to scbus0
  Device configuration finished.
  Reducing kern.maxvnodes 343811 -> 100000
  procfs registered
  lapic: Divisor 2, Frequency 133000612 hz
  Timecounter "TSC" frequency 2394010944 Hz quality -100
  Timecounters tick every 1.000 msec
  lo0: bpf attached
  hptrr: no controller detected.
  ata2-slave: pio=PIO4 wdma=WDMA2 udma=UDMA33 cable=80 wire
  acd0: setting PIO4 on IT8213F chip
  acd0: <DVD-ROM UJDA780/1.50> DVDROM drive at ata2 as slave
  acd0: read 4134KB/s (4134KB/s), 2048KB buffer, PIO4
  acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, DVDRAM, packet
  acd0: Writes:
  acd0: Audio: play, 256 volume levels
  acd0: Mechanism: ejectable tray, unlocked
  acd0: Medium: CD-R 120mm data disc
  ata3-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire
  ad6: 305245MB <Seagate ST3320620AS 3.AAK> at ata3-master SATA300
  ad6: 625142448 sectors [620181C/16H/63S] 16 sectors/interrupt 1 depth queue
  ad6: Intel check1 failed
  ad6: Adaptec check1 failed
  ad6: LSI (v3) check1 failed
  ad6: LSI (v2) check1 failed
  ad6: FreeBSD check1 failed
  ata4-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire
  ad8: 305245MB <Seagate ST3320620AS 3.AAK> at ata4-master SATA300
  ad8: 625142448 sectors [620181C/16H/63S] 16 sectors/interrupt 1 depth queue
  ad8: Intel check1 failed
  ad8: Adaptec check1 failed
  ad8: LSI (v3) check1 failed
  ad8: LSI (v2) check1 failed
  ad8: FreeBSD check1 failed
  ata5-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire
  ad10: 305245MB <Seagate ST3320620AS 3.AAC> at ata5-master SATA300
  ad10: 625142448 sectors [620181C/16H/63S] 16 sectors/interrupt 1 depth queue
  ad10: Intel check1 failed
  ad10: Adaptec check1 failed
  ad10: LSI (v3) check1 failed
  ad10: LSI (v2) check1 failed
  ad10: FreeBSD check1 failed
  ata6-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire
  ad12: 305245MB <Seagate ST3320620AS 3.AAC> at ata6-master SATA300
  ad12: 625142448 sectors [620181C/16H/63S] 16 sectors/interrupt 1 depth queue
  ad12: Intel check1 failed
  ad12: Adaptec check1 failed
  ad12: LSI (v3) check1 failed
  ad12: LSI (v2) check1 failed
  ad12: FreeBSD check1 failed
  (probe0:umass-sim0:0:0:0): Down reving Protocol Version from 2 to 0?
  acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00
  (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
  (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
  (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition
  (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0
  (probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed
  (probe0:umass-sim0:0:0:0): (probe0:umass-sim0:0:0:0): TEST UNIT  
READY. CDB: 0 0 0 0 0 0
  (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0
  (probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed
  Retrying Command (per Sense Data)
  (probe0:umass-sim0:0:0:0): Retrying Command
  pass0 at umass-sim0 bus 0 target 0 lun 0
  pass0: <Y-E DATA USB-FDU 5.01> Removable Direct Access SCSI-0 device
  pass0: 20KB/s transfers
  ATA PseudoRAID loaded
  SMP: AP CPU #1 Launched!
  cpu1 AP:
       ID: 0x01000000   VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff
    lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff
    timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000
  SMP: AP CPU #3 Launched!
  cpu3 AP:
       ID: 0x03000000   VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff
    lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff
    timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000
  SMP: AP CPU #2 Launched!
  cpu2 AP:
       ID: 0x02000000   VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff
    lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff
    timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000
  ioapic0: Assigning ISA IRQ 1 to local APIC 0
  ioapic0: Assigning ISA IRQ 3 to local APIC 1
  ioapic0: Assigning ISA IRQ 4 to local APIC 2
  ioapic0: Assigning ISA IRQ 6 to local APIC 3
  ioapic0: Assigning ISA IRQ 7 to local APIC 0
  ioapic0: Assigning ISA IRQ 9 to local APIC 1
  ioapic0: Assigning ISA IRQ 12 to local APIC 2
  ioapic0: Assigning PCI IRQ 16 to local APIC 3
  ioapic0: Assigning PCI IRQ 17 to local APIC 0
  ioapic0: Assigning PCI IRQ 18 to local APIC 1
  ioapic0: Assigning PCI IRQ 22 to local APIC 2
  ioapic0: Assigning PCI IRQ 23 to local APIC 3
  msi: Assigning MSI IRQ 256 to local APIC 0
  msi: Assigning MSI IRQ 257 to local APIC 1
  da0 at umass-sim0 bus 0 target 0 lun 0
  da0: <Y-E DATA USB-FDU 5.01> Removable Direct Access SCSI-0 device
  da0: 20KB/s transfers
  da0: 1MB (2880 512 byte sectors: 64H 32S/T 1C)
  acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00
  GEOM_LABEL: Label for provider acd0 is iso9660/FreeBSD_Install.
  GEOM: new disk ad6
  acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00
  acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00
  GEOM: new disk ad8
  GEOM: new disk ad10
  GEOM: new disk ad12
  GEOM: new disk da0
  acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00
  GEOM_MIRROR: Device mirror/gm0 launched (3/3).
  GEOM_LABEL: Label for provider ad12s1 is ufsid/488efb68e5c53bb1.
  GEOM_LABEL: Label for provider mirror/gm0s1a is ufsid/489cb5723873a365.
  GEOM_LABEL: Label for provider mirror/gm0s1d is ufsid/489cb5806d417263.
  GEOM_LABEL: Label for provider mirror/gm0s1e is ufsid/489cb5847a0f8baa.
  GEOM_LABEL: Label for provider mirror/gm0s1f is ufsid/489cb58839896589.
  GEOM_LABEL: Label for provider mirror/gm0s1g is ufsid/489cb58c07734311.
  Trying to mount root from ufs:/dev/mirror/gm0s1a
  start_init: trying /sbin/init
  GEOM_LABEL: Label ufsid/489cb5723873a365 removed.
  GEOM_LABEL: Label for provider mirror/gm0s1a is ufsid/489cb5723873a365.
  GEOM_LABEL: Label ufsid/489cb5806d417263 removed.
  GEOM_LABEL: Label for provider mirror/gm0s1d is ufsid/489cb5806d417263.
  GEOM_LABEL: Label ufsid/489cb5847a0f8baa removed.
  GEOM_LABEL: Label for provider mirror/gm0s1e is ufsid/489cb5847a0f8baa.
  GEOM_LABEL: Label ufsid/489cb58839896589 removed.
  GEOM_LABEL: Label for provider mirror/gm0s1f is ufsid/489cb58839896589.
  GEOM_LABEL: Label ufsid/489cb58c07734311 removed.
  GEOM_LABEL: Label for provider mirror/gm0s1g is ufsid/489cb58c07734311.
  GEOM_LABEL: Label ufsid/489cb5723873a365 removed.
  GEOM_LABEL: Label ufsid/489cb5806d417263 removed.
  GEOM_LABEL: Label ufsid/489cb5847a0f8baa removed.
  GEOM_LABEL: Label ufsid/489cb58839896589 removed.
  GEOM_LABEL: Label ufsid/489cb58c07734311 removed.
  em1: Link is up 1000 Mbps Full Duplex
  em0: Link is up 1000 Mbps Full Duplex
  em0: link state changed to UP

-- 
ian j hart

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


From rizzo at iet.unipi.it  Mon Jul  6 19:10:34 2009
From: rizzo at iet.unipi.it (Luigi Rizzo)
Date: Mon Jul  6 19:10:42 2009
Subject: Merging a GCC bug fix to RELENG_7 - how?
In-Reply-To: <4A520A69.4010000@incunabulum.net>
References: <4A520A69.4010000@incunabulum.net>
Message-ID: <20090706191617.GC35071@onelab2.iet.unipi.it>

On Mon, Jul 06, 2009 at 03:30:01PM +0100, Bruce Simpson wrote:
> Hi all,
> 
> This GCC bug bites us in the Boost regression tests in a number of places.
> 
> Uh oh, I've stepped on the one-line fix bomb:
>    http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31899
>    http://gcc.gnu.org/viewcvs?view=rev&revision=129199
> 
> What's funny is that COPYING in the root of that branch is GPLv2, but 
> the affected file's license is GPLv3.
> 
> So what on earth do we do?

the whole change is one line

-    gcc_unreachable ();
+    return *tp;

and according to the dates bugzilla and the repository,
when the patch was submitted the file was still marked as GPLv2.

So I would think that taking the v2 file and the v2 patch
still makes a v2 file, doesn't it ?

cheers
luigi
From kostikbel at gmail.com  Mon Jul  6 19:37:00 2009
From: kostikbel at gmail.com (Kostik Belousov)
Date: Mon Jul  6 19:37:07 2009
Subject: bug in ufs?
In-Reply-To: <4A523849.1070001@ksu.ru>
References: <4A50E947.9020608@ksu.ru> <4A523518.7050008@gmx.de>
	<4A523849.1070001@ksu.ru>
Message-ID: <20090706193653.GU2884@deviant.kiev.zoral.com.ua>

On Mon, Jul 06, 2009 at 09:45:45PM +0400, Marat N.Afanasyev wrote:
> Ralf Folkerts wrote:
> >Marat N.Afanasyev wrote:
> >>hello!
> >>
> >>i have a strange problem with writing data to my ufs2+su filesystem.
> >>
> >>1. i made a 1T gpt partition on my storage server, and formatted it:
> >>newfs -U -m 0 -o time -i 32768 /dev/da1p3a
> >>
> >>2. i tried to move data from other servers to this filesystem, total 
> >>size of files is slightly less than 1T
> >>
> >>3. i encountered a 'No space left on device' while i still have 11G of 
> >>free space and about 13 million free inodes on the filesystem:
> >>
> >>#df -ih
> >>Filesystem     Size    Used   Avail Capacity  iused    ifree %iused 
> >>Mounted on
> >>/dev/da1p3a    1.0T    1.0T     11G    99% 20397465 13363173   60% 
> >>/mnt/45_114
> >>
> >>all i want to know is whether this is a bug or a feature? and if such 
> >>a behavior is well-known, where can i read about it?
> >Hi Marat,
> >
> >just a guess: Are there sparse Files on the Source System that are not 
> >being detected by the Tool you used to restore the data? If you used 
> >(bsd)tar, did you try -S?
> >
> >A while ago I ran into a similar Problem when copying 
> >Oracle-Database-Files (on Linux, though) and the -S - Option came to 
> >rescue.
> >
> >Cheers,
> >_ralf_
> 
> i have a huge amount of small files on the source systems, as you can 
> see they have about 20 million files and almost each of them is jpeg or 
> gif. afaik, there are no sparse files at all.
> 
> i still cannot figure out what is it: a free space leak in ufs2+su or 
> bug in statfs(3), that is used in df, or something else.

My guess that it is due to fragmentation.
As an experiment, try to create 1-byte file. Does it work on the filesystem
in described state ?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090706/bc2c00ad/attachment.pgp
From marck at rinet.ru  Mon Jul  6 19:54:51 2009
From: marck at rinet.ru (Dmitry Morozovsky)
Date: Mon Jul  6 19:54:59 2009
Subject: bug in ufs?
In-Reply-To: <20090706193653.GU2884@deviant.kiev.zoral.com.ua>
References: <4A50E947.9020608@ksu.ru> <4A523518.7050008@gmx.de>
	<4A523849.1070001@ksu.ru>
	<20090706193653.GU2884@deviant.kiev.zoral.com.ua>
Message-ID: <alpine.BSF.2.00.0907062351100.12926@woozle.rinet.ru>

On Mon, 6 Jul 2009, Kostik Belousov wrote:

KB> > >>i have a strange problem with writing data to my ufs2+su filesystem.
KB> > >>
KB> > >>1. i made a 1T gpt partition on my storage server, and formatted it:
KB> > >>newfs -U -m 0 -o time -i 32768 /dev/da1p3a
KB> > >>
KB> > >>2. i tried to move data from other servers to this filesystem, total 
KB> > >>size of files is slightly less than 1T
KB> > >>
KB> > >>3. i encountered a 'No space left on device' while i still have 11G of 
KB> > >>free space and about 13 million free inodes on the filesystem:
KB> > >>
KB> > >>#df -ih
KB> > >>Filesystem     Size    Used   Avail Capacity  iused    ifree %iused 
KB> > >>Mounted on
KB> > >>/dev/da1p3a    1.0T    1.0T     11G    99% 20397465 13363173   60% 
KB> > >>/mnt/45_114
KB> > >>
KB> > >>all i want to know is whether this is a bug or a feature? and if such 
KB> > >>a behavior is well-known, where can i read about it?
KB> > >Hi Marat,
KB> > >
KB> > >just a guess: Are there sparse Files on the Source System that are not 
KB> > >being detected by the Tool you used to restore the data? If you used 
KB> > >(bsd)tar, did you try -S?
KB> > >
KB> > >A while ago I ran into a similar Problem when copying 
KB> > >Oracle-Database-Files (on Linux, though) and the -S - Option came to 
KB> > >rescue.
KB> > >
KB> > >Cheers,
KB> > >_ralf_
KB> > 
KB> > i have a huge amount of small files on the source systems, as you can 
KB> > see they have about 20 million files and almost each of them is jpeg or 
KB> > gif. afaik, there are no sparse files at all.
KB> > 
KB> > i still cannot figure out what is it: a free space leak in ufs2+su or 
KB> > bug in statfs(3), that is used in df, or something else.
KB> 
KB> My guess that it is due to fragmentation.
KB> As an experiment, try to create 1-byte file. Does it work on the filesystem
KB> in described state ?

Doesn't UFS store one-byte (or several-bytes, like PID file) file entirely in 
the inode, not consuming any data blocks?

-- 
Sincerely,
D.Marck                                     [DM5020, MCK-RIPE, DM3-RIPN]
[ FreeBSD committer:                                 marck@FreeBSD.org ]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru ***
------------------------------------------------------------------------
From kostikbel at gmail.com  Mon Jul  6 20:01:17 2009
From: kostikbel at gmail.com (Kostik Belousov)
Date: Mon Jul  6 20:01:23 2009
Subject: bug in ufs?
In-Reply-To: <alpine.BSF.2.00.0907062351100.12926@woozle.rinet.ru>
References: <4A50E947.9020608@ksu.ru> <4A523518.7050008@gmx.de>
	<4A523849.1070001@ksu.ru>
	<20090706193653.GU2884@deviant.kiev.zoral.com.ua>
	<alpine.BSF.2.00.0907062351100.12926@woozle.rinet.ru>
Message-ID: <20090706200110.GX2884@deviant.kiev.zoral.com.ua>

On Mon, Jul 06, 2009 at 11:54:48PM +0400, Dmitry Morozovsky wrote:
> On Mon, 6 Jul 2009, Kostik Belousov wrote:
> 
> KB> > >>i have a strange problem with writing data to my ufs2+su filesystem.
> KB> > >>
> KB> > >>1. i made a 1T gpt partition on my storage server, and formatted it:
> KB> > >>newfs -U -m 0 -o time -i 32768 /dev/da1p3a
> KB> > >>
> KB> > >>2. i tried to move data from other servers to this filesystem, total 
> KB> > >>size of files is slightly less than 1T
> KB> > >>
> KB> > >>3. i encountered a 'No space left on device' while i still have 11G of 
> KB> > >>free space and about 13 million free inodes on the filesystem:
> KB> > >>
> KB> > >>#df -ih
> KB> > >>Filesystem     Size    Used   Avail Capacity  iused    ifree %iused 
> KB> > >>Mounted on
> KB> > >>/dev/da1p3a    1.0T    1.0T     11G    99% 20397465 13363173   60% 
> KB> > >>/mnt/45_114
> KB> > >>
> KB> > >>all i want to know is whether this is a bug or a feature? and if such 
> KB> > >>a behavior is well-known, where can i read about it?
> KB> > >Hi Marat,
> KB> > >
> KB> > >just a guess: Are there sparse Files on the Source System that are not 
> KB> > >being detected by the Tool you used to restore the data? If you used 
> KB> > >(bsd)tar, did you try -S?
> KB> > >
> KB> > >A while ago I ran into a similar Problem when copying 
> KB> > >Oracle-Database-Files (on Linux, though) and the -S - Option came to 
> KB> > >rescue.
> KB> > >
> KB> > >Cheers,
> KB> > >_ralf_
> KB> > 
> KB> > i have a huge amount of small files on the source systems, as you can 
> KB> > see they have about 20 million files and almost each of them is jpeg or 
> KB> > gif. afaik, there are no sparse files at all.
> KB> > 
> KB> > i still cannot figure out what is it: a free space leak in ufs2+su or 
> KB> > bug in statfs(3), that is used in df, or something else.
> KB> 
> KB> My guess that it is due to fragmentation.
> KB> As an experiment, try to create 1-byte file. Does it work on the filesystem
> KB> in described state ?
> 
> Doesn't UFS store one-byte (or several-bytes, like PID file) file entirely in 
> the inode, not consuming any data blocks?

No, 1-byte file is stored in fragment. Long write tries to allocate whole
block. This is why I wrote about fragmentation.

Answering your question, it is short symlinks that are stored in inode
in the data block pointers.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090706/3e3e1b01/attachment.pgp
From amarat at ksu.ru  Mon Jul  6 20:16:28 2009
From: amarat at ksu.ru (Marat N.Afanasyev)
Date: Mon Jul  6 20:16:35 2009
Subject: bug in ufs?
In-Reply-To: <20090706193653.GU2884@deviant.kiev.zoral.com.ua>
References: <4A50E947.9020608@ksu.ru> <4A523518.7050008@gmx.de>
	<4A523849.1070001@ksu.ru>
	<20090706193653.GU2884@deviant.kiev.zoral.com.ua>
Message-ID: <4A525B72.1010808@ksu.ru>

Kostik Belousov wrote:
> On Mon, Jul 06, 2009 at 09:45:45PM +0400, Marat N.Afanasyev wrote:
>> i have a huge amount of small files on the source systems, as you can 
>> see they have about 20 million files and almost each of them is jpeg or 
>> gif. afaik, there are no sparse files at all.
>>
>> i still cannot figure out what is it: a free space leak in ufs2+su or 
>> bug in statfs(3), that is used in df, or something else.
> 
> My guess that it is due to fragmentation.
> As an experiment, try to create 1-byte file. Does it work on the filesystem
> in described state ?

I can create small files, as many as i have patience, maximum size of 
such "small file" is 14336, so. it seems that if file is no greater than 
(block_size-2048) it can be created. larger file cannot be created.

imho, fragmentation on filesystem should be very low, there were no 
deletions on it, just creations.

-- 
SY, Marat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3221 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090706/1756f23b/smime.bin
From marck at rinet.ru  Mon Jul  6 20:20:58 2009
From: marck at rinet.ru (Dmitry Morozovsky)
Date: Mon Jul  6 20:21:05 2009
Subject: bug in ufs?
In-Reply-To: <20090706200110.GX2884@deviant.kiev.zoral.com.ua>
References: <4A50E947.9020608@ksu.ru> <4A523518.7050008@gmx.de>
	<4A523849.1070001@ksu.ru>
	<20090706193653.GU2884@deviant.kiev.zoral.com.ua>
	<alpine.BSF.2.00.0907062351100.12926@woozle.rinet.ru>
	<20090706200110.GX2884@deviant.kiev.zoral.com.ua>
Message-ID: <alpine.BSF.2.00.0907070020090.12926@woozle.rinet.ru>

On Mon, 6 Jul 2009, Kostik Belousov wrote:

KB> > KB> My guess that it is due to fragmentation.
KB> > KB> As an experiment, try to create 1-byte file. Does it work on the filesystem
KB> > KB> in described state ?
KB> > 
KB> > Doesn't UFS store one-byte (or several-bytes, like PID file) file entirely in 
KB> > the inode, not consuming any data blocks?
KB> 
KB> No, 1-byte file is stored in fragment. Long write tries to allocate whole
KB> block. This is why I wrote about fragmentation.
KB> 
KB> Answering your question, it is short symlinks that are stored in inode
KB> in the data block pointers.

Ah yes, I somehow mixed these two cases, thank you for clarification.

-- 
Sincerely,
D.Marck                                     [DM5020, MCK-RIPE, DM3-RIPN]
[ FreeBSD committer:                                 marck@FreeBSD.org ]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru ***
------------------------------------------------------------------------
From tech at unixteacher.org  Mon Jul  6 20:21:37 2009
From: tech at unixteacher.org (Amza Marian)
Date: Mon Jul  6 20:21:44 2009
Subject: hw.realmem in stable.
Message-ID: <0475D596F44442839D969C59B5E93F84@workstation>

 Hello,

 I running 7.2-RELEASE i386 and i seem to have some problems with my system.
hw.realmem does not report correctly the memory. 
Anybody know whatis the problem ?

lsg ~ # sysctl -a | grep hw.*mem
hw.physmem: 4214419456
hw.usermem: 3941974016
hw.realmem: 603979776
hw.firewire.fwmem.speed: 2
hw.firewire.fwmem.eui64_lo: 0
hw.firewire.fwmem.eui64_hi: 0
hw.cbb.start_memory: 2281701376
hw.pci.host_mem_start: 2147483648
lsg ~ # 

lsg ~ # uname -rm
7.2-RELEASE i386
lsg ~ #


Thank you.

      Regards,
      Amza Marian 
From kostikbel at gmail.com  Mon Jul  6 20:34:34 2009
From: kostikbel at gmail.com (Kostik Belousov)
Date: Mon Jul  6 20:34:40 2009
Subject: bug in ufs?
In-Reply-To: <4A525B72.1010808@ksu.ru>
References: <4A50E947.9020608@ksu.ru> <4A523518.7050008@gmx.de>
	<4A523849.1070001@ksu.ru>
	<20090706193653.GU2884@deviant.kiev.zoral.com.ua>
	<4A525B72.1010808@ksu.ru>
Message-ID: <20090706203427.GZ2884@deviant.kiev.zoral.com.ua>

On Tue, Jul 07, 2009 at 12:15:46AM +0400, Marat N.Afanasyev wrote:
> Kostik Belousov wrote:
> >On Mon, Jul 06, 2009 at 09:45:45PM +0400, Marat N.Afanasyev wrote:
> >>i have a huge amount of small files on the source systems, as you can 
> >>see they have about 20 million files and almost each of them is jpeg or 
> >>gif. afaik, there are no sparse files at all.
> >>
> >>i still cannot figure out what is it: a free space leak in ufs2+su or 
> >>bug in statfs(3), that is used in df, or something else.
> >
> >My guess that it is due to fragmentation.
> >As an experiment, try to create 1-byte file. Does it work on the filesystem
> >in described state ?
> 
> I can create small files, as many as i have patience, maximum size of 
> such "small file" is 14336, so. it seems that if file is no greater than 
> (block_size-2048) it can be created. larger file cannot be created.
> 
> imho, fragmentation on filesystem should be very low, there were no 
> deletions on it, just creations.

The fragmentation on UFS usually means using fragments for the file tails,
not having file sequential blocks allocated in the non-sequential disk
blocks.

You experiment confirms my hypothesis.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090706/5d9fac15/attachment.pgp
From tech at unixteacher.org  Mon Jul  6 20:58:09 2009
From: tech at unixteacher.org (Amza Marian)
Date: Mon Jul  6 20:58:15 2009
Subject: hw.realmem in stable.
In-Reply-To: <alpine.BSO.1.00.0907062240390.13690@isl-s-02.htw-saarland.de>
References: <0475D596F44442839D969C59B5E93F84@workstation>
	<alpine.BSO.1.00.0907062240390.13690@isl-s-02.htw-saarland.de>
Message-ID: <42650195230C4DE4B7816F944EB3B464@workstation>


I have the kernel compiled with PAE option but anyway, the system report 
only 600 MB ram


lsg ~ # sysctl -a | grep hw.*mem
hw.physmem: 4214419456
hw.usermem: 3997806592
hw.realmem: 603979776
hw.firewire.fwmem.speed: 2
hw.firewire.fwmem.eui64_lo: 0
hw.firewire.fwmem.eui64_hi: 0
hw.cbb.start_memory: 2281701376
hw.pci.host_mem_start: 2147483648

lsg ~ # grep memory /var/run/dmesg.boot
real memory  = 4898947072 (4672 MB)
avail memory = 4117958656 (3927 MB)
lsg ~ #


Thank you.

Regards,
Amza Marian

>
>> hw.realmem does not report correctly the memory.
> Might be this...
> http://www.freebsd.org/doc/en/books/faq/compatibility-memory.html
>
> Regards
>
>  Damian
>
> --
> Damian Weber, <http://www-crypto.htw-saarland.de>
>              <http://tinyurl.com/8zvtj>
>
> On Mon, 6 Jul 2009, Amza Marian wrote:
>
>> Date: Mon, 6 Jul 2009 22:03:31 +0200
>> From: Amza Marian <tech@unixteacher.org>
>> To: freebsd-stable@freebsd.org
>> Subject: hw.realmem in stable.
>>
>>  Hello,
>>
>>  I running 7.2-RELEASE i386 and i seem to have some problems with my 
>> system.
>> hw.realmem does not report correctly the memory.
>> Anybody know whatis the problem ?
>>
>> lsg ~ # sysctl -a | grep hw.*mem
>> hw.physmem: 4214419456
>> hw.usermem: 3941974016
>> hw.realmem: 603979776
>> hw.firewire.fwmem.speed: 2
>> hw.firewire.fwmem.eui64_lo: 0
>> hw.firewire.fwmem.eui64_hi: 0
>> hw.cbb.start_memory: 2281701376
>> hw.pci.host_mem_start: 2147483648
>> lsg ~ #
>>
>> lsg ~ # uname -rm
>> 7.2-RELEASE i386
>> lsg ~ #
>>
>>
>> Thank you.
>>
>>       Regards,
>>       Amza Marian
>> _______________________________________________
>> freebsd-stable@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>>
>>
>> 

From dimitry at andric.com  Mon Jul  6 21:03:18 2009
From: dimitry at andric.com (Dimitry Andric)
Date: Mon Jul  6 21:03:25 2009
Subject: hw.realmem in stable.
In-Reply-To: <42650195230C4DE4B7816F944EB3B464@workstation>
References: <0475D596F44442839D969C59B5E93F84@workstation>	<alpine.BSO.1.00.0907062240390.13690@isl-s-02.htw-saarland.de>
	<42650195230C4DE4B7816F944EB3B464@workstation>
Message-ID: <4A526693.5020401@andric.com>

On 2009-07-06 22:57, Amza Marian wrote:
> I have the kernel compiled with PAE option but anyway, the system report 
> only 600 MB ram
...
> hw.realmem: 603979776
...
> lsg ~ # grep memory /var/run/dmesg.boot
> real memory  = 4898947072 (4672 MB)
> avail memory = 4117958656 (3927 MB)

This looks like a wraparound issue, your realmem doesn't fit into a
32-bit integer:

4,672 MB - 2^32 = 4,898,947,072 - 4,294,967,296 = 603,979,776
From rick-freebsd2008 at kiwi-computer.com  Mon Jul  6 21:20:47 2009
From: rick-freebsd2008 at kiwi-computer.com (Rick C. Petty)
Date: Mon Jul  6 21:20:55 2009
Subject: What is /boot/kernel/*.symbols?
In-Reply-To: <20090706093904.GA79434@ei.bzerk.org>
References: <20090703144121.GC11039@hugo10.ka.punkt.de>
	<4A4E1E24.3020303@andric.com>
	<20090703152150.GE11039@hugo10.ka.punkt.de>
	<20090705003834.12211k8697td2o74@webmail.private.lan>
	<20090706073941.GA78371@ei.bzerk.org>
	<20090706074256.GD6306@hugo10.ka.punkt.de>
	<4A51B721.5020505@andric.com>
	<cf9b1ee00907060141w110e36c3p5922d31b3acd1f62@mail.gmail.com>
	<4A51B9FA.9010906@andric.com> <20090706093904.GA79434@ei.bzerk.org>
Message-ID: <20090706212045.GA91095@keira.kiwi-computer.com>

On Mon, Jul 06, 2009 at 11:39:04AM +0200, Ruben de Groot wrote:
> On Mon, Jul 06, 2009 at 10:46:50AM +0200, Dimitry Andric typed:
> > 
> > Right, so it's a lot bigger on amd64.  I guess those 64-bit pointers
> > aren't entirely free. :)
> 
> I'm not sure where the size difference comes from. I have some sparc64
> systems running -current with symbols and the size of /boot/kernel is
> more comparable to i386, even with the 8-byte pointer size:

Um, probably there are a lot of devices on amd64 that aren't available for
sparc64?

-- Rick C. Petty
From tech at unixteacher.org  Mon Jul  6 21:22:34 2009
From: tech at unixteacher.org (Amza Marian)
Date: Mon Jul  6 21:22:45 2009
Subject: hw.realmem in stable.
In-Reply-To: <4A526693.5020401@andric.com>
References: <0475D596F44442839D969C59B5E93F84@workstation>	<alpine.BSO.1.00.0907062240390.13690@isl-s-02.htw-saarland.de>
	<42650195230C4DE4B7816F944EB3B464@workstation>
	<4A526693.5020401@andric.com>
Message-ID: <785FFA80D58E4B5194F2DCFE15488903@workstation>


Thank you sir.

 Is there any solution for this issue ? (because applications does not work 
correctly. - like mysql.)

(sorry for my english.)

----- Original Message ----- 
From: "Dimitry Andric" <dimitry@andric.com>
To: "Amza Marian" <tech@unixteacher.org>
Cc: <freebsd-stable@freebsd.org>
Sent: Monday, July 06, 2009 11:03 PM
Subject: Re: hw.realmem in stable.


> On 2009-07-06 22:57, Amza Marian wrote:
>> I have the kernel compiled with PAE option but anyway, the system report
>> only 600 MB ram
> ...
>> hw.realmem: 603979776
> ...
>> lsg ~ # grep memory /var/run/dmesg.boot
>> real memory  = 4898947072 (4672 MB)
>> avail memory = 4117958656 (3927 MB)
>
> This looks like a wraparound issue, your realmem doesn't fit into a
> 32-bit integer:
>
> 4,672 MB - 2^32 = 4,898,947,072 - 4,294,967,296 = 603,979,776 

From amarat at ksu.ru  Mon Jul  6 22:08:27 2009
From: amarat at ksu.ru (Marat N.Afanasyev)
Date: Mon Jul  6 22:08:34 2009
Subject: bug in ufs?
In-Reply-To: <20090706203427.GZ2884@deviant.kiev.zoral.com.ua>
References: <4A50E947.9020608@ksu.ru> <4A523518.7050008@gmx.de>
	<4A523849.1070001@ksu.ru>
	<20090706193653.GU2884@deviant.kiev.zoral.com.ua>
	<4A525B72.1010808@ksu.ru>
	<20090706203427.GZ2884@deviant.kiev.zoral.com.ua>
Message-ID: <4A5275C0.50607@ksu.ru>

Kostik Belousov wrote:
> On Tue, Jul 07, 2009 at 12:15:46AM +0400, Marat N.Afanasyev wrote:
>> Kostik Belousov wrote:
>>> On Mon, Jul 06, 2009 at 09:45:45PM +0400, Marat N.Afanasyev wrote:
>>>> i have a huge amount of small files on the source systems, as you can 
>>>> see they have about 20 million files and almost each of them is jpeg or 
>>>> gif. afaik, there are no sparse files at all.
>>>>
>>>> i still cannot figure out what is it: a free space leak in ufs2+su or 
>>>> bug in statfs(3), that is used in df, or something else.
>>> My guess that it is due to fragmentation.
>>> As an experiment, try to create 1-byte file. Does it work on the filesystem
>>> in described state ?
>> I can create small files, as many as i have patience, maximum size of 
>> such "small file" is 14336, so. it seems that if file is no greater than 
>> (block_size-2048) it can be created. larger file cannot be created.
>>
>> imho, fragmentation on filesystem should be very low, there were no 
>> deletions on it, just creations.
> 
> The fragmentation on UFS usually means using fragments for the file tails,
> not having file sequential blocks allocated in the non-sequential disk
> blocks.
> 
> You experiment confirms my hypothesis.

is there any way to change this behavior? and i wonder why even if i can 
create a reasonable number of small files i cannot create a slightly 
larger file joining two unallocated parts of different blocks even if no 
fully free block exists? ;)

-- 
SY, Marat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3221 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090706/5e0af2ec/smime.bin
From pj at smo.de  Mon Jul  6 23:18:39 2009
From: pj at smo.de (Philipp Ost)
Date: Mon Jul  6 23:18:46 2009
Subject: upgrading ports without recompiling
In-Reply-To: <ed5c0bbe0907060904m2a93aab7r9b17b8b5529dd8f0@mail.gmail.com>
References: <ed5c0bbe0907060904m2a93aab7r9b17b8b5529dd8f0@mail.gmail.com>
Message-ID: <4A523185.90007@smo.de>

Ishmael F.E. wrote:
[...]
> .
> so, ?how can I upgrade the ports?
> unfortunatley I don't have time to compile my 64bit system

Have you looked at the -PP option of portupgrade?
I don't know how portmaster handles upgrades using packages only.

HTH,
Philipp
From dan at langille.org  Tue Jul  7 00:42:06 2009
From: dan at langille.org (Dan Langille)
Date: Tue Jul  7 00:42:14 2009
Subject: interrupt storm on MSI IXP600 based motherboards
In-Reply-To: <7697CDAB-B4E7-480A-B31A-1F54275B8D54@langille.org>
References: <E1LNnFa-0003ze-7k@dilbert.ticketswitch.com>	<49774BAE.3000809@ksu.ru>
	<20090122071845.GF4881@alf.bsdes.net>
	<4978A10A.9060006@langille.org>
	<7697CDAB-B4E7-480A-B31A-1F54275B8D54@langille.org>
Message-ID: <4A529537.8070206@langille.org>

Dan Langille wrote:
> 
> On Jan 22, 2009, at 11:38 AM, Dan Langille wrote:
> 
>> Victor Balada Diaz wrote:
>>> On Wed, Jan 21, 2009 at 07:22:06PM +0300, Marat N.Afanasyev wrote:
>>>>>> trouble with onboard re(4) was resolved in -CURRENT and -STABLE, 
>>>>>> but storms are not bound to ethernet only. storm may appear on any 
>>>>>> device. if any device generates enough interrupts rate, storm will 
>>>>>> arrive.
>>>>> Yes, I just got another storm, on my ATA controller this time. Ah
>>>>> well, so much for the idea of disabling unneeded devices!
>>>>>
>>>>> -pete.
>>>>>
>>>> it's a kind of magic, really. I built a new kernel with KDB and DDB 
>>>> and after 1 day, 13:15 I'm still waiting for storm to arrive. And I 
>>>> added
>>>> hw.acpi.osname="Linux" to /boot/loader.conf.
>>> Try doing lots of IO and you will get the problem soon. You might
>>> want to try:
>>> while true; do dd if=/dev/zero of=BAH bs=1M count=1024; sync; done
>>
>> FWIW, last night I changed the address of the comm port IO in my BIOS. 
>> Then I ran the Bacula regression test suite (lots of IO).  For my 
>> machine, once the interrupt storm starts, it continues.  I do not know 
>> if that happens to everyone.
>>
>> Since changing the address, I have had no interrupt storms. I have 
>> been running the above IO loop for about ten minutes.
>>
>> No storm yet (knock on wood).
> 
> 
> And it's back:
> 
> Jan 22 17:21:46 polo kernel: interrupt storm detected on "irq22:"; 
> throttling interrupt source
> Jan 22 17:23:19 polo kernel: interrupt storm detected on "irq22:"; 
> throttling interrupt source
> Jan 22 17:28:20 polo kernel: interrupt storm detected on "irq22:"; 
> throttling interrupt source
> Jan 22 17:33:20 polo kernel: interrupt storm detected on "irq22:"; 
> throttling interrupt source
> Jan 22 17:38:20 polo kernel: interrupt storm detected on "irq22:"; 
> throttling interrupt source
> 
> I shall try the hw.acpi.osname="Linux" option now.
> 
>  From dmsg: Jan 22 18:10:07 polo kernel: ACPI: Overriding _OS definition 
> with "Linux"

The problem returns:
Jul  6 20:12:10 polo kernel: interrupt storm detected on "irq22:"; 
throttling interrupt source
Jul  6 20:12:41 polo last message repeated 31 times
Jul  6 20:14:42 polo last message repeated 121 times
Jul  6 20:17:09 polo last message repeated 147 times


FreeBSD polo.example.org 7.2-STABLE FreeBSD 7.2-STABLE #10: Mon Jun  1 
19:19:13 EDT 2009 dan@example.org:/usr/obj/usr/src/sys/PHENOM amd64


Copyright (c) 1992-2009 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.2-STABLE #10: Mon Jun  1 19:19:13 EDT 2009
     dan@example.org:/usr/obj/usr/src/sys/PHENOM
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Phenom(tm) 9600 Quad-Core Processor (2300.17-MHz K8-class CPU)
   Origin = "AuthenticAMD"  Id = 0x100f22  Stepping = 2
 
Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
   Features2=0x802009<SSE3,MON,CX16,<b23>>
   AMD 
Features=0xee500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM,3DNow!+,3DNow!>
   AMD 
Features2=0x7ff<LAHF,CMP,SVM,ExtAPIC,CR8,<b5>,<b6>,<b7>,Prefetch,<b9>,<b10>>
   TSC: P-state invariant
   Cores per package: 4
usable memory = 4281012224 (4082 MB)
avail memory  = 4108423168 (3918 MB)
ACPI APIC Table: <122107 APIC0947>
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
  cpu0 (BSP): APIC ID:  0
  cpu1 (AP): APIC ID:  1
  cpu2 (AP): APIC ID:  2
  cpu3 (AP): APIC ID:  3
ioapic0 <Version 2.1> irqs 0-23 on motherboard
kbd1 at kbdmux0
acpi0: <122107 RSDT0947> on motherboard
ACPI: Overriding _OS definition with "Linux"
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: reservation of fee00000, 1000 (3) failed
acpi0: reservation of ffb80000, 80000 (3) failed
acpi0: reservation of 0, a0000 (3) failed
acpi0: reservation of 100000, cff00000 (3) failed
ACPI HPET table warning: Sequence is non-zero (2)
Timecounter "ACPI-safe" frequency 3579545 Hz quality 850
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on 
acpi0
Timecounter "HPET" frequency 14318180 Hz quality 900
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 11.0 on pci0
pci1: <ACPI PCI bus> on pcib1
vgapci0: <VGA-compatible display> port 0xd800-0xd87f mem 
0xfd000000-0xfdffffff,0xd0000000-0xdfffffff,0xfa000000-0xfbffffff irq 19 
at device 0.0 on pci1
atapci0: <ATI IXP600 SATA300 controller> port 
0xc000-0xc007,0xb000-0xb003,0xa000-0xa007,0x9000-0x9003,0x8000-0x800f 
mem 0xf9fff800-0xf9fffbff irq 22 at device 18.0 on pci0
atapci0: [ITHREAD]
atapci0: AHCI Version 01.10 controller with 4 ports detected
ata2: <ATA channel 0> on atapci0
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci0
ata3: [ITHREAD]
ata4: <ATA channel 2> on atapci0
ata4: [ITHREAD]
ata5: <ATA channel 3> on atapci0
ata5: [ITHREAD]
ohci0: <OHCI (generic) USB controller> mem 0xf9ffe000-0xf9ffefff irq 16 
at device 19.0 on pci0
ohci0: [GIANT-LOCKED]
ohci0: [ITHREAD]
usb0: OHCI version 1.0, legacy support
usb0: SMM does not respond, resetting
usb0: <OHCI (generic) USB controller> on ohci0
usb0: USB revision 1.0
uhub0: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
uhub0: 2 ports with 2 removable, self powered
ohci1: <OHCI (generic) USB controller> mem 0xf9ffd000-0xf9ffdfff irq 17 
at device 19.1 on pci0
ohci1: [GIANT-LOCKED]
ohci1: [ITHREAD]
usb1: OHCI version 1.0, legacy support
usb1: SMM does not respond, resetting
usb1: <OHCI (generic) USB controller> on ohci1
usb1: USB revision 1.0
uhub1: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1
uhub1: 2 ports with 2 removable, self powered
ohci2: <OHCI (generic) USB controller> mem 0xf9ffc000-0xf9ffcfff irq 18 
at device 19.2 on pci0
ohci2: [GIANT-LOCKED]
ohci2: [ITHREAD]
usb2: OHCI version 1.0, legacy support
usb2: SMM does not respond, resetting
usb2: <OHCI (generic) USB controller> on ohci2
usb2: USB revision 1.0
uhub2: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2
uhub2: 2 ports with 2 removable, self powered
ohci3: <OHCI (generic) USB controller> mem 0xf9ffb000-0xf9ffbfff irq 17 
at device 19.3 on pci0
ohci3: [GIANT-LOCKED]
ohci3: [ITHREAD]
usb3: OHCI version 1.0, legacy support
usb3: SMM does not respond, resetting
usb3: <OHCI (generic) USB controller> on ohci3
usb3: USB revision 1.0
uhub3: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb3
uhub3: 2 ports with 2 removable, self powered
ohci4: <OHCI (generic) USB controller> mem 0xf9ffa000-0xf9ffafff irq 18 
at device 19.4 on pci0
ohci4: [GIANT-LOCKED]
ohci4: [ITHREAD]
usb4: OHCI version 1.0, legacy support
usb4: SMM does not respond, resetting
usb4: <OHCI (generic) USB controller> on ohci4
usb4: USB revision 1.0
uhub4: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb4
uhub4: 2 ports with 2 removable, self powered
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xf9fff000-0xf9fff0ff irq 
19 at device 19.5 on pci0
ehci0: [GIANT-LOCKED]
ehci0: [ITHREAD]
usb5: EHCI version 1.0
usb5: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4
usb5: <EHCI (generic) USB 2.0 controller> on ehci0
usb5: USB revision 2.0
uhub5: <ATI EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb5
uhub5: 10 ports with 10 removable, self powered
pci0: <serial bus, SMBus> at device 20.0 (no driver attached)
atapci1: <ATI IXP600 UDMA133 controller> port 
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 20.1 on pci0
ata0: <ATA channel 0> on atapci1
ata0: [ITHREAD]
hdac0: <ATI SB600 High Definition Audio Controller> mem 
0xf9ff4000-0xf9ff7fff irq 16 at device 20.2 on pci0
hdac0: HDA Driver Revision: 20090329_0131
hdac0: [ITHREAD]
isab0: <PCI-ISA bridge> at device 20.3 on pci0
isa0: <ISA bus> on isab0
pcib2: <ACPI PCI-PCI bridge> at device 20.4 on pci0
pci2: <ACPI PCI bus> on pcib2
fwohci0: <VIA Fire II (VT6306)> port 0xe800-0xe87f mem 
0xfebff800-0xfebfffff irq 23 at device 0.0 on pci2
fwohci0: [FILTER]
fwohci0: OHCI version 1.10 (ROM=1)
fwohci0: No. of Isochronous channels is 4.
fwohci0: EUI64 00:dc:10:00:01:53:a0:bc
fwohci0: Phy 1394a available S400, 2 ports.
fwohci0: Link S400, max_rec 2048 bytes.
firewire0: <IEEE1394(FireWire) bus> on fwohci0
dcons_crom0: <dcons configuration ROM> on firewire0
dcons_crom0: bus_addr 0x1464000
fwe0: <Ethernet over FireWire> on firewire0
if_fwe0: Fake Ethernet address: 02:dc:10:53:a0:bc
fwe0: Ethernet address: 02:dc:10:53:a0:bc
fwip0: <IP over FireWire> on firewire0
fwip0: Firewire address: 00:dc:10:00:01:53:a0:bc @ 0xfffe00000000, S400, 
maxrec 2048
sbp0: <SBP-2/SCSI over FireWire> on firewire0
fwohci0: Initiate bus reset
fwohci0: BUS reset
fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode
fxp0: <Intel 82559 Pro/100 Ethernet> port 0xe400-0xe43f mem 
0xfebfe000-0xfebfefff,0xfea00000-0xfeafffff irq 22 at device 2.0 on pci2
miibus0: <MII bus> on fxp0
inphy0: <i82555 10/100 media interface> PHY 1 on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp0: Ethernet address: 00:04:ac:d3:78:23
fxp0: [ITHREAD]
acpi_button0: <Power Button> on acpi0
sio0: configured irq 3 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: configured irq 3 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 flags 0x10 on 
acpi0
sio0: type 16550A
sio0: [FILTER]
fdc0: <floppy drive controller (FDE)> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 
on acpi0
fdc0: [FILTER]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: [ITHREAD]
psm0: model IntelliMouse, device ID 3
cpu0: <ACPI CPU> on acpi0
acpi_throttle0: <ACPI CPU Throttling> on cpu0
acpi_throttle0: CLK_VAL field overlaps THT_EN bit
device_attach: acpi_throttle0 attach returned 6
cpu1: <ACPI CPU> on acpi0
cpu2: <ACPI CPU> on acpi0
cpu3: <ACPI CPU> on acpi0
ppc0: cannot reserve I/O port range
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
ugen0: <American Power Conversion Back-UPS XS 1200 FW:8.g1 .D USB FW:g1, 
class 0/0, rev 1.10/1.06, addr 2> on uhub4
Timecounters tick every 1.000 msec
firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me)
firewire0: bus manager 0 (me)
acd0: CDRW <HL-DT-ST GCE-8523B/1.01> at ata0-slave UDMA33
ad4: 476940MB <WDC WD5000AAKS-00YGA0 12.01C02> at ata2-master SATA300
ad6: 476940MB <WDC WD5000AAKS-00YGA0 12.01C02> at ata3-master SATA300
hdac0: HDA Codec #0: Realtek ALC888
pcm0: <HDA Realtek ALC888 PCM #0 Analog> at cad 0 nid 1 on hdac0
pcm1: <HDA Realtek ALC888 PCM #1 Analog> at cad 0 nid 1 on hdac0
pcm2: <HDA Realtek ALC888 PCM #2 Digital> at cad 0 nid 1 on hdac0
GEOM_MIRROR: Device mirror/gm0 launched (2/2).
GEOM_LABEL: Label for provider mirror/gm0s1a is ufsid/47c95ad36ed40e80.
GEOM_LABEL: Label for provider mirror/gm0s1d is ufsid/47c95ae2ac3d5ead.
GEOM_LABEL: Label for provider mirror/gm0s1e is ufsid/47c95ad3fa3660aa.
GEOM_LABEL: Label for provider mirror/gm0s1f is ufsid/47c95ad37ffedafc.
acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00
(probe0:ata0:0:1:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
(probe0:ata0:0:1:0): CAM Status: SCSI Status Error
(probe0:ata0:0:1:0): SCSI Status: Check Condition
(probe0:ata0:0:1:0): NOT READY asc:3a,1
(probe0:ata0:0:1:0): Medium not present - tray closed
(probe0:ata0:0:1:0): Unretryable error
acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00
cd0 at ata0 bus 0 target 1 lun 0
cd0: <HL-DT-ST CD-RW GCE-8523B 1.01> Removable CD-ROM SCSI-0 device
cd0: 33.000MB/s transfers
cd0: Attempt to query device size failed: NOT READY, Medium not present 
- tray closed
SMP: AP CPU #1 Launched!
SMP: AP CPU #2 Launched!
SMP: AP CPU #3 Launched!
Trying to mount root from ufs:/dev/mirror/gm0s1a
GEOM_LABEL: Label ufsid/47c95ad36ed40e80 removed.
GEOM_LABEL: Label for provider mirror/gm0s1a is ufsid/47c95ad36ed40e80.
GEOM_LABEL: Label ufsid/47c95ad3fa3660aa removed.
GEOM_LABEL: Label for provider mirror/gm0s1e is ufsid/47c95ad3fa3660aa.
GEOM_LABEL: Label ufsid/47c95ad37ffedafc removed.
GEOM_LABEL: Label for provider mirror/gm0s1f is ufsid/47c95ad37ffedafc.
GEOM_LABEL: Label ufsid/47c95ae2ac3d5ead removed.
GEOM_LABEL: Label for provider mirror/gm0s1d is ufsid/47c95ae2ac3d5ead.
GEOM_LABEL: Label ufsid/47c95ad36ed40e80 removed.
GEOM_LABEL: Label ufsid/47c95ad3fa3660aa removed.
GEOM_LABEL: Label ufsid/47c95ad37ffedafc removed.
GEOM_LABEL: Label ufsid/47c95ae2ac3d5ead removed.
[dan@polo:/usr/home/dan] $
From kensmith at cse.Buffalo.EDU  Tue Jul  7 00:51:13 2009
From: kensmith at cse.Buffalo.EDU (Ken Smith)
Date: Tue Jul  7 00:51:21 2009
Subject: FreeBSD 8.0-BETA1 Available
Message-ID: <1246926782.11597.23.camel@bauer.cse.buffalo.edu>


The first public test build of the FreeBSD 8.0-RELEASE test cycle is now
available, 8.0-BETA1.  Through the next week or so more information
about the release will be posted but here is the current target schedule
for the other 'major events':

	BETA2:	July 13, 2009
	BETA3:	July 20, 2009
	RC1:	July 27, 2009
	RC2:	August 17, 2009
	RELEASE:August 31, 2009

People with the resources to do so (test machines...) are encouraged to
give 8.0-BETA1 a try.  At this point it is not quite ready for
production systems but mostly because there is still some ongoing work
in a few areas that may cause some changes in things like ABI/API.
Debugging support (WITNESS, malloc debugging, etc.) are also still
turned on and those tend to cause a performance hit.  As far as we know
there are no known issues that would cause data corruption or anything
like that, just the issues with performance and potential for changes
caused by ongoing work.  If you find problems they can be reported
through the normal Gnats based PR system or posted to the mailing lists.

Note that for BETA1 no packages were included with any of the images.

The amd64 and i386 architectures include a file named:

	8.0-BETA1-<arch>-memstick.img

If you copy that to a USB memory stick newer machines should be able to
boot from it and use it to install from.  Note that you need to
overwrite the contents of the memory stick completely, not copy it into
an existing filesystem on the memory stick.  Exactly how you do that
depends on your machine but just to give you an example this works on
the machine I tested it with:

  dd if=8.0-BETA1-amd64-memstick.img of=/dev/da0 bs=10240 conv=sync

Be careful if you have SCSI drives, more USB disks than just the memory
stick, etc - make sure /dev/da0 (or whatever you use) is the memory
stick.  Using this image for livefs based rescue mode is known to not
work, that is one of the things still being worked on.

FreeBSD Update was not ready for updates to 8.0 at the point this
message was sent but it is also being worked on.  A separate message
will be posted when it's ready.

Checksums for the images:

MD5 (8.0-BETA1-amd64-bootonly.iso) = e7cc0b3b022775f6be058044f171e3d2
MD5 (8.0-BETA1-amd64-disc1.iso) = ad259bc0d57e1a7ae1afdc04bbb87cfd
MD5 (8.0-BETA1-amd64-dvd1.iso) = f240e48be3db47ed338bb157244b874d
MD5 (8.0-BETA1-amd64-livefs.iso) = 2a0f06d61d2722efe68cf8c6a14de0c6
MD5 (8.0-BETA1-amd64-memstick.img) = 10bc42a388c213497f03aadad30e0486

MD5 (8.0-BETA1-i386-bootonly.iso) = cadcdb82377705061a0d464569ecfef7
MD5 (8.0-BETA1-i386-disc1.iso) = 9e19a4edcc3b2d7f594cbcdc7fcabace
MD5 (8.0-BETA1-i386-dvd1.iso) = 98a2f5e05391eb4ab2b421443296cd7b
MD5 (8.0-BETA1-i386-livefs.iso) = c1d35cd8a15434b2af0bc1f27ddb48a1
MD5 (8.0-BETA1-i386-memstick.img) = c6a0fbe8e31b2987b5da47c52705fa8e

MD5 (8.0-BETA1-ia64-bootonly.iso) = d40385e657477566100ae66485a98bb3
MD5 (8.0-BETA1-ia64-disc1.iso) = 216b4e54536bb41c5a9543ce88f288bc
MD5 (8.0-BETA1-ia64-disc2.iso) = 790eb3e163aee02c7c6dddcfa54cc167
MD5 (8.0-BETA1-ia64-disc3.iso) = b59510898c2ce1cfe594620cc2f9de97
MD5 (8.0-BETA1-ia64-dvd1.iso) = ce7d5abec2aaed9028b82c66445e2734
MD5 (8.0-BETA1-ia64-livefs.iso) = 5021774a2349d960e859082065c1bc86

MD5 (8.0-BETA1-pc98-bootonly.iso) = 9a421562167c5d6806784151c26694fe
MD5 (8.0-BETA1-pc98-disc1.iso) = b5ca7555697677eb23057fffe2c47062
MD5 (8.0-BETA1-pc98-livefs.iso) = 0c8a405c394651ea61dee34d9637b47e

MD5 (8.0-BETA1-powerpc-bootonly.iso) = e982f204c4024c544f88753b400007a5
MD5 (8.0-BETA1-powerpc-disc1.iso) = 0e59688100a8288e2bee87c4d0f9b0ee
MD5 (8.0-BETA1-powerpc-disc2.iso) = 1426a523d1b2480c4f546422934d1cc4
MD5 (8.0-BETA1-powerpc-disc3.iso) = d6b7505441c756be547b4587331af6b9
MD5 (8.0-BETA1-powerpc-livefs.iso) = 2dbf7c3543fcd35c834fd19f64f240cf

MD5 (8.0-BETA1-sparc64-bootonly.iso) = 24004c2014edcbafb68f09399db1b74d
MD5 (8.0-BETA1-sparc64-disc1.iso) = 96e7a0b14581fac7ab845a4e9916d393
MD5 (8.0-BETA1-sparc64-dvd1.iso) = efcc5a4923f335cd483d76395333b639

SHA256 (8.0-BETA1-amd64-bootonly.iso) = d49e8651f71c1a4a4d2ad9b4e391e7dfea2fec159a716876c4c0a547b346d34d
SHA256 (8.0-BETA1-amd64-disc1.iso) = 692eb89c0ba07dc161ad2ea366516a2210c5d5e5cf90a48ed6316e67b7ebb5e4
SHA256 (8.0-BETA1-amd64-dvd1.iso) = eaf4a18c269589af516f6c96af164f918345a34e2fb1e5273762479a7779c4cd
SHA256 (8.0-BETA1-amd64-livefs.iso) = b9e68d7944707f73f0894e0f610ff73ff5c5350e9dbc15d980a4d9413d61daf8
SHA256 (8.0-BETA1-amd64-memstick.img) = c3ece618be54d4c51400945d8922f6724547453a133c32450ac2ebbacaabaa65

SHA256 (8.0-BETA1-i386-bootonly.iso) = d82918557e595fdb76ae8d4158e0f5738a3879985d6c5109b944d382c9f767af
SHA256 (8.0-BETA1-i386-disc1.iso) = 398a93e851088391fc1cca6c3ff50494afc4e5471791cff12204ef8673b81472
SHA256 (8.0-BETA1-i386-dvd1.iso) = b61e14733e498fe83e482010b036f3aabb8d7dace2ed5fb8b8dbe371141a2caa
SHA256 (8.0-BETA1-i386-livefs.iso) = 6d47e830bea1a96d851490d41b4a47248a03ec2a6c39df534ca407aba2daf58a
SHA256 (8.0-BETA1-i386-memstick.img) = b7561c27ea789447e368a1e2398249282ae46e8752a82bbb3614cb5db3d606e7

SHA256 (8.0-BETA1-ia64-bootonly.iso) = 6e9b9cc92a82b062cc5d9d51da7652a79097894b16e8c2cf8bcdb7b51c3aa576
SHA256 (8.0-BETA1-ia64-disc1.iso) = 52ca59f0129cda5651bf0aad3daa57a07a719580c3ece28be63178e40e6f0613
SHA256 (8.0-BETA1-ia64-disc2.iso) = f6e1bded3aec557e19ef0249b9c3b17ba3c5e0aca99d98ae697e6107c9bb3061
SHA256 (8.0-BETA1-ia64-disc3.iso) = b8b8e5ce0cca5eb3dd0dc8ea05b7de399cb937ecc4b960eb092e621cda22bbd5
SHA256 (8.0-BETA1-ia64-dvd1.iso) = 29d5852bef2d09c73075242ea2e2d35072a51b30b624d5229ed8aec6737cfbc5
SHA256 (8.0-BETA1-ia64-livefs.iso) = 0a92eb0f09dfd4f4ab0694fd94482e4682eded3425186737bd0e2440e957dd3b

SHA256 (8.0-BETA1-pc98-bootonly.iso) = 5d77d1fb6a5d7e819b0d90d1848f7d029d64ce456ca550e3049d63eb5fc8891a
SHA256 (8.0-BETA1-pc98-disc1.iso) = 5e11719fd24d8f8a9fd0fd4ce07c72509c197e48b1e45060d931b0f8bcad9335
SHA256 (8.0-BETA1-pc98-livefs.iso) = 271056add63d5e82f85a482cfd0efcfaaacb1b5941337fc459782e97577f3e0e

SHA256 (8.0-BETA1-powerpc-bootonly.iso) = 60c984e47d8e71eb87ae382cb1bc19a0abd982095b5906dafb539e799ad0a51e
SHA256 (8.0-BETA1-powerpc-disc1.iso) = 647b51471e71a8de9ab4a0c42fa94d869fae33a2f5f3a0aaa07592bb9854a49f
SHA256 (8.0-BETA1-powerpc-disc2.iso) = 9a46aecda07f6b6fa040bf7c852c3a99eb27e8db529c8f26974d5a9a2ecf0b8d
SHA256 (8.0-BETA1-powerpc-disc3.iso) = efe792cb535ea2a6ee821cdcd5fd1e5306e116e32b57e2f1e6d4309f672830ab
SHA256 (8.0-BETA1-powerpc-livefs.iso) = 1b8e5c401bf5b14c0a14d91b21895ed2273287158e59a158313bcec43aead8ff

SHA256 (8.0-BETA1-sparc64-bootonly.iso) = 2775ceec218f5fef0bc2d17ea80e1492f423307f27cec38df352b1e9ee6f96a4
SHA256 (8.0-BETA1-sparc64-disc1.iso) = 9eac5684c3c650e2cac01343c7933931aef0227bdb6e9a4931402ad0dd41b9c8
SHA256 (8.0-BETA1-sparc64-dvd1.iso) = 207268ec113811213d73b571c2322585c26cf6beae88e27e5680e77c93e249b2

-- 
                                                Ken Smith
- From there to here, from here to      |       kensmith@cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090707/a58c784d/attachment.pgp
From dan.naumov at gmail.com  Tue Jul  7 01:12:15 2009
From: dan.naumov at gmail.com (Dan Naumov)
Date: Tue Jul  7 01:12:22 2009
Subject: 7.2-release/amd64: panic, spin lock held too long
Message-ID: <cf9b1ee00907061812r3da70018i1c8d8d12bb038a80@mail.gmail.com>

I just got a panic following by a reboot a few seconds after running
"portsnap update", /var/log/messages shows the following:

Jul  7 03:49:38 atom syslogd: kernel boot file is /boot/kernel/kernel
Jul  7 03:49:38 atom kernel: spin lock 0xffffffff80b3edc0 (sched lock
1) held by 0xffffff00017d8370 (tid 100054) too long
Jul  7 03:49:38 atom kernel: panic: spin lock held too long

/var/crash looks empty. This is a system running official 7.2-p1
binaries since I am using freebsd-update to keep up with the patches
(just updated to -p2 after this panic) running with very low load,
mostly serving files to my home network over Samba and running a few
irssi instances in a screen. What do I need to do to catch more
information if/when this happens again?

- Sincerely,
Dan Naumov
From attilio at freebsd.org  Tue Jul  7 01:18:11 2009
From: attilio at freebsd.org (Attilio Rao)
Date: Tue Jul  7 01:18:19 2009
Subject: 7.2-release/amd64: panic, spin lock held too long
In-Reply-To: <cf9b1ee00907061812r3da70018i1c8d8d12bb038a80@mail.gmail.com>
References: <cf9b1ee00907061812r3da70018i1c8d8d12bb038a80@mail.gmail.com>
Message-ID: <3bbf2fe10907061818v245abd0cgc3ca5073cb93aea4@mail.gmail.com>

2009/7/7 Dan Naumov <dan.naumov@gmail.com>:
> I just got a panic following by a reboot a few seconds after running
> "portsnap update", /var/log/messages shows the following:
>
> Jul  7 03:49:38 atom syslogd: kernel boot file is /boot/kernel/kernel
> Jul  7 03:49:38 atom kernel: spin lock 0xffffffff80b3edc0 (sched lock
> 1) held by 0xffffff00017d8370 (tid 100054) too long
> Jul  7 03:49:38 atom kernel: panic: spin lock held too long

That's a known bug, affecting -CURRENT as well.
The cpustop IPI is handled though an NMI, which means it could
interrupt a CPU in any moment, even while holding a spinlock,
violating one well known FreeBSD rule.
That means that the cpu can stop itself while the thread was holding
the sched lock spinlock and not releasing it (there is no way, modulo
highly hackish, to fix that).
In the while hardclock() wants to schedule something else to run and
got stuck on the thread lock.

Ideal fix would involve not using a NMI for serving the cpustop while
having a cheap way (not making the common path too hard) to tell
hardclock() to avoid scheduling while cpustop is in flight.

Thanks,
Attilio


-- 
Peace can only be achieved by understanding - A. Einstein
From dan.naumov at gmail.com  Tue Jul  7 01:25:08 2009
From: dan.naumov at gmail.com (Dan Naumov)
Date: Tue Jul  7 01:25:16 2009
Subject: 7.2-release/amd64: panic, spin lock held too long
In-Reply-To: <3bbf2fe10907061818v245abd0cgc3ca5073cb93aea4@mail.gmail.com>
References: <cf9b1ee00907061812r3da70018i1c8d8d12bb038a80@mail.gmail.com>
	<3bbf2fe10907061818v245abd0cgc3ca5073cb93aea4@mail.gmail.com>
Message-ID: <cf9b1ee00907061825r34165c48x6727c50b3219d5fb@mail.gmail.com>

On Tue, Jul 7, 2009 at 4:18 AM, Attilio Rao<attilio@freebsd.org> wrote:
> 2009/7/7 Dan Naumov <dan.naumov@gmail.com>:
>> I just got a panic following by a reboot a few seconds after running
>> "portsnap update", /var/log/messages shows the following:
>>
>> Jul ?7 03:49:38 atom syslogd: kernel boot file is /boot/kernel/kernel
>> Jul ?7 03:49:38 atom kernel: spin lock 0xffffffff80b3edc0 (sched lock
>> 1) held by 0xffffff00017d8370 (tid 100054) too long
>> Jul ?7 03:49:38 atom kernel: panic: spin lock held too long
>
> That's a known bug, affecting -CURRENT as well.
> The cpustop IPI is handled though an NMI, which means it could
> interrupt a CPU in any moment, even while holding a spinlock,
> violating one well known FreeBSD rule.
> That means that the cpu can stop itself while the thread was holding
> the sched lock spinlock and not releasing it (there is no way, modulo
> highly hackish, to fix that).
> In the while hardclock() wants to schedule something else to run and
> got stuck on the thread lock.
>
> Ideal fix would involve not using a NMI for serving the cpustop while
> having a cheap way (not making the common path too hard) to tell
> hardclock() to avoid scheduling while cpustop is in flight.
>
> Thanks,
> Attilio

Any idea if a fix is being worked on and how unlucky must one be to
run into this issue, should I expect it to happen again? Is it
basically completely random?


- Sincerely,
Dan Naumov
From attilio at freebsd.org  Tue Jul  7 01:27:51 2009
From: attilio at freebsd.org (Attilio Rao)
Date: Tue Jul  7 01:28:00 2009
Subject: 7.2-release/amd64: panic, spin lock held too long
In-Reply-To: <cf9b1ee00907061825r34165c48x6727c50b3219d5fb@mail.gmail.com>
References: <cf9b1ee00907061812r3da70018i1c8d8d12bb038a80@mail.gmail.com>
	<3bbf2fe10907061818v245abd0cgc3ca5073cb93aea4@mail.gmail.com>
	<cf9b1ee00907061825r34165c48x6727c50b3219d5fb@mail.gmail.com>
Message-ID: <3bbf2fe10907061827g35eaeb49g26cf6fdb64436ca7@mail.gmail.com>

2009/7/7 Dan Naumov <dan.naumov@gmail.com>:
> On Tue, Jul 7, 2009 at 4:18 AM, Attilio Rao<attilio@freebsd.org> wrote:
>> 2009/7/7 Dan Naumov <dan.naumov@gmail.com>:
>>> I just got a panic following by a reboot a few seconds after running
>>> "portsnap update", /var/log/messages shows the following:
>>>
>>> Jul  7 03:49:38 atom syslogd: kernel boot file is /boot/kernel/kernel
>>> Jul  7 03:49:38 atom kernel: spin lock 0xffffffff80b3edc0 (sched lock
>>> 1) held by 0xffffff00017d8370 (tid 100054) too long
>>> Jul  7 03:49:38 atom kernel: panic: spin lock held too long
>>
>> That's a known bug, affecting -CURRENT as well.
>> The cpustop IPI is handled though an NMI, which means it could
>> interrupt a CPU in any moment, even while holding a spinlock,
>> violating one well known FreeBSD rule.
>> That means that the cpu can stop itself while the thread was holding
>> the sched lock spinlock and not releasing it (there is no way, modulo
>> highly hackish, to fix that).
>> In the while hardclock() wants to schedule something else to run and
>> got stuck on the thread lock.
>>
>> Ideal fix would involve not using a NMI for serving the cpustop while
>> having a cheap way (not making the common path too hard) to tell
>> hardclock() to avoid scheduling while cpustop is in flight.
>>
>> Thanks,
>> Attilio
>
> Any idea if a fix is being worked on and how unlucky must one be to
> run into this issue, should I expect it to happen again? Is it
> basically completely random?

I'd like to work on that issue before BETA3 (and backport to
STABLE_7), I'm just time-constrained right now.
it is completely random.

Thanks,
Attilio


-- 
Peace can only be achieved by understanding - A. Einstein
From cmdlnkid at gmail.com  Tue Jul  7 02:16:03 2009
From: cmdlnkid at gmail.com (CmdLnKid)
Date: Tue Jul  7 02:16:14 2009
Subject: upgrading ports without recompiling
In-Reply-To: <4A523185.90007@smo.de>
References: <ed5c0bbe0907060904m2a93aab7r9b17b8b5529dd8f0@mail.gmail.com>
	<4A523185.90007@smo.de>
Message-ID: <alpine.BSF.2.00.0907062211190.95659@qvzrafvba.5c.ybpny>

On Mon, 6 Jul 2009 13:16 -0000, pj wrote:

> Ishmael F.E. wrote:
> [...]
>> .
>> so, ?how can I upgrade the ports?
>> unfortunatley I don't have time to compile my 64bit system
>
> Have you looked at the -PP option of portupgrade?
> I don't know how portmaster handles upgrades using packages only.
>

You could look into devel/ccache & devel/distcc if you would like to 
speed up your compile times. Of course your first compile will always 
be the slowest one but everyone after that will be faster. This is not 
always advised as a good solution and has been known to throw some 
pretty weird compiler bugs and also fail while compiling certain ports 
but that is tweakable through /etc/make.conf*.

Best regards.
J. Hellenthal
From admin at kkip.pl  Tue Jul  7 06:38:59 2009
From: admin at kkip.pl (Bartosz Stec)
Date: Tue Jul  7 06:39:07 2009
Subject: upgrading ports without recompiling
In-Reply-To: <alpine.BSF.2.00.0907062211190.95659@qvzrafvba.5c.ybpny>
References: <ed5c0bbe0907060904m2a93aab7r9b17b8b5529dd8f0@mail.gmail.com>	<4A523185.90007@smo.de>
	<alpine.BSF.2.00.0907062211190.95659@qvzrafvba.5c.ybpny>
Message-ID: <4A52ED7F.5030904@kkip.pl>

CmdLnKid pisze:
> On Mon, 6 Jul 2009 13:16 -0000, pj wrote:
>
>> Ishmael F.E. wrote:
>> [...]
>>> .
>>> so, ?how can I upgrade the ports?
>>> unfortunatley I don't have time to compile my 64bit system
You don't need to compile whole OS to compile ports, if this is what you 
had in mind.
>>
>> Have you looked at the -PP option of portupgrade?
>> I don't know how portmaster handles upgrades using packages only.
>>
>
> You could look into devel/ccache & devel/distcc if you would like to 
> speed up your compile times. Of course your first compile will always 
> be the slowest one but everyone after that will be faster. This is not 
> always advised as a good solution and has been known to throw some 
> pretty weird compiler bugs and also fail while compiling certain ports 
> but that is tweakable through /etc/make.conf*.
>
Well, I heard about some problems with ccache, although I personally 
experienced only one of them - fail when building world on AMD64. Here's 
my make.conf, feel free to give it try after installing ccache (Try to 
set MAKEOPTS = CPU cores +1, and set appropriate CPUTYPE):

    CPUTYPE=athlon64
    MAKEOPTS=-j3

    # USE CCACHE
    .if !defined(NOCCACHE)
    CC=/usr/local/libexec/ccache/world-cc
    CXX=/usr/local/libexec/ccache/world-c++
    .endif

    # default build settings for ports collection
    .if ${.CURDIR:M*/ports/*}
    CFLAGS= -O2 -fno-strict-aliasing -pipe -funroll-loops
    -fomit-frame-pointer
    CXXFLAGS= -O2 -fno-strict-aliasing -pipe -funroll-loops
    .endif

    # default build settings for base system
    .if ${.CURDIR:M*/usr/src/*} || ${.CURDIR:M*/usr/obj/*}
    CFLAGS=-O2 -fno-strict-aliasing -pipe
    COPTFLAGS=-O2 -fno-strict-aliasing -pipe
    CXXFLAGS=${CFLAGS}
    .endif

In case of any problem with specific port (or world) type in shell:

    # setenv NOCCACHE

before build. This should give you maximum compile speed in case when 
package is unavailable while using portupgrade -afP

-- 
Bartosz Stec


From pluknet at gmail.com  Tue Jul  7 07:10:28 2009
From: pluknet at gmail.com (pluknet)
Date: Tue Jul  7 07:10:35 2009
Subject: bug in ufs?
In-Reply-To: <4A5275C0.50607@ksu.ru>
References: <4A50E947.9020608@ksu.ru> <4A523518.7050008@gmx.de>
	<4A523849.1070001@ksu.ru>
	<20090706193653.GU2884@deviant.kiev.zoral.com.ua>
	<4A525B72.1010808@ksu.ru>
	<20090706203427.GZ2884@deviant.kiev.zoral.com.ua>
	<4A5275C0.50607@ksu.ru>
Message-ID: <a31046fc0907070010t45e36c92hf913b38eaa43f45a@mail.gmail.com>

2009/7/7 Marat N.Afanasyev <amarat@ksu.ru>:
> Kostik Belousov wrote:
>>
>> On Tue, Jul 07, 2009 at 12:15:46AM +0400, Marat N.Afanasyev wrote:
>>>
>>> Kostik Belousov wrote:
>>>>
>>>> On Mon, Jul 06, 2009 at 09:45:45PM +0400, Marat N.Afanasyev wrote:
>>>>>
>>>>> i have a huge amount of small files on the source systems, as you can
>>>>> see they have about 20 million files and almost each of them is jpeg or gif.
>>>>> afaik, there are no sparse files at all.
>>>>>
>>>>> i still cannot figure out what is it: a free space leak in ufs2+su or
>>>>> bug in statfs(3), that is used in df, or something else.
>>>>
>>>> My guess that it is due to fragmentation.
>>>> As an experiment, try to create 1-byte file. Does it work on the
>>>> filesystem
>>>> in described state ?
>>>
>>> I can create small files, as many as i have patience, maximum size of
>>> such "small file" is 14336, so. it seems that if file is no greater than
>>> (block_size-2048) it can be created. larger file cannot be created.
>>>
>>> imho, fragmentation on filesystem should be very low, there were no
>>> deletions on it, just creations.
>>
>> The fragmentation on UFS usually means using fragments for the file tails,
>> not having file sequential blocks allocated in the non-sequential disk
>> blocks.
>>
>> You experiment confirms my hypothesis.
>
> i cannot create a slightly larger
> file joining two unallocated parts of different blocks even if no fully free
> block exists? ;)

You can't.

As far as I remember, ffs_alloc() tries to populate a number of whole blocks
and then only packs a remain data tail into a partially allocated block (one,
two, .. seven fragments), thus creating a block fragmentation.
In other words, it's impossible to partially allocate several blocks
for a one file.
Can you show your dumpfs output (superblock part)?

-- 
wbr,
pluknet
From peterjeremy at optushome.com.au  Tue Jul  7 08:17:12 2009
From: peterjeremy at optushome.com.au (Peter Jeremy)
Date: Tue Jul  7 08:17:21 2009
Subject: bug in ufs?
In-Reply-To: <4A50E947.9020608@ksu.ru>
References: <4A50E947.9020608@ksu.ru>
Message-ID: <20090707081658.GA68385@server.vk2pj.dyndns.org>

On 2009-Jul-05 21:56:23 +0400, "Marat N.Afanasyev" <amarat@ksu.ru> wrote:
>i have a strange problem with writing data to my ufs2+su filesystem.

Overall, I think you are pushing UFS and have hit one of its limits.

>1. i made a 1T gpt partition on my storage server, and formatted it:
>newfs -U -m 0 -o time -i 32768 /dev/da1p3a

'-m 0' is undesirable.  The default 8% free space is intended to hide
the sort of effect you've run into.  Unless you can find a slightly
bigger disk, I suggest you try building an 8K/1K filesystem by adding
'-b 8192 -f 1024' - this will be slightly slower than the default
16K/2K but will hopefully allow you to fit slightly more files in.

>2. i tried to move data from other servers to this filesystem, total 
>size of files is slightly less than 1T

Can you be more accurate than "slightly less than 1T" (ie how many
MiB) and what is the size distribution of the files?  The average size
is 48KiB but are they all roughly the same size or do they vary widely?
Are there many files <16KiB?

>3. i encountered a 'No space left on device' while i still have 11G of 
>free space and about 13 million free inodes on the filesystem:
>
>#df -ih
>Filesystem     Size    Used   Avail Capacity  iused    ifree %iused 
>Mounted on
>/dev/da1p3a    1.0T    1.0T     11G    99% 20397465 13363173   60% 
>/mnt/45_114

More significant figures are needed.  How about 'df -im' or 'df -ik'.
How close are you to fitting in all the files you want?

>all i want to know is whether this is a bug or a feature? and if such a 
>behavior is well-known, where can i read about it?

Have a read of /usr/share/doc/smm/05.fastfs/paper.ascii.gz - especially
the bits about "fragments".  Whilst this paper talks about the original
UFS and a 4K/1K configuration, the principles remain the same in UFS2.

-- 
Peter Jeremy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4029 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090707/2eaf789e/smime-0001.bin
From ivoras at freebsd.org  Tue Jul  7 08:37:09 2009
From: ivoras at freebsd.org (Ivan Voras)
Date: Tue Jul  7 08:37:42 2009
Subject: hw.realmem in stable.
In-Reply-To: <785FFA80D58E4B5194F2DCFE15488903@workstation>
References: <0475D596F44442839D969C59B5E93F84@workstation>	<alpine.BSO.1.00.0907062240390.13690@isl-s-02.htw-saarland.de>	<42650195230C4DE4B7816F944EB3B464@workstation>	<4A526693.5020401@andric.com>
	<785FFA80D58E4B5194F2DCFE15488903@workstation>
Message-ID: <h2v1f5$3ls$1@ger.gmane.org>

Amza Marian wrote:
> 
> Thank you sir.
> 
> Is there any solution for this issue ? (because applications does not 
> work correctly. - like mysql.)

Why wouldn't MySQL work correctly? Does it inspect FreeBSD sysctls? (why 
would it, since you can configure its memory usage through its 
configuration files)

From petefrench at ticketswitch.com  Tue Jul  7 08:59:27 2009
From: petefrench at ticketswitch.com (Pete French)
Date: Tue Jul  7 08:59:34 2009
Subject: interrupt storm on MSI IXP600 based motherboards
In-Reply-To: <4A529537.8070206@langille.org>
Message-ID: <E1MO6Vu-000GSe-IB@dilbert.ticketswitch.com>

> The problem returns:
> Jul  6 20:12:10 polo kernel: interrupt storm detected on "irq22:"; 
> throttling interrupt source

Six months is a long gap! I was hooinh the problem had gone away. I
havent seen it on here since I started running 7.2-STABLE, and
before that I made it go away by using a debug kernel.

-pete.
From mail25 at bzerk.org  Tue Jul  7 09:25:00 2009
From: mail25 at bzerk.org (Ruben de Groot)
Date: Tue Jul  7 09:25:22 2009
Subject: What is /boot/kernel/*.symbols?
In-Reply-To: <20090706212045.GA91095@keira.kiwi-computer.com>
References: <4A4E1E24.3020303@andric.com>
	<20090703152150.GE11039@hugo10.ka.punkt.de>
	<20090705003834.12211k8697td2o74@webmail.private.lan>
	<20090706073941.GA78371@ei.bzerk.org>
	<20090706074256.GD6306@hugo10.ka.punkt.de>
	<4A51B721.5020505@andric.com>
	<cf9b1ee00907060141w110e36c3p5922d31b3acd1f62@mail.gmail.com>
	<4A51B9FA.9010906@andric.com> <20090706093904.GA79434@ei.bzerk.org>
	<20090706212045.GA91095@keira.kiwi-computer.com>
Message-ID: <20090707092451.GA92743@ei.bzerk.org>

On Mon, Jul 06, 2009 at 04:20:45PM -0500, Rick C. Petty typed:
> On Mon, Jul 06, 2009 at 11:39:04AM +0200, Ruben de Groot wrote:
> > On Mon, Jul 06, 2009 at 10:46:50AM +0200, Dimitry Andric typed:
> > > 
> > > Right, so it's a lot bigger on amd64.  I guess those 64-bit pointers
> > > aren't entirely free. :)
> > 
> > I'm not sure where the size difference comes from. I have some sparc64
> > systems running -current with symbols and the size of /boot/kernel is
> > more comparable to i386, even with the 8-byte pointer size:
> 
> Um, probably there are a lot of devices on amd64 that aren't available for
> sparc64?

Yes, That's probably it.

From ianjhart at ntlworld.com  Tue Jul  7 09:51:08 2009
From: ianjhart at ntlworld.com (Ian J Hart)
Date: Tue Jul  7 09:51:16 2009
Subject: trap 12
In-Reply-To: <20090706200115.1411150frxepkbuo@webmail.private.lan>
References: <20090703100627.197838cphjnil82s@10.248.192.16>
	<20090706200115.1411150frxepkbuo@webmail.private.lan>
Message-ID: <20090707105103.946813hdks2mra80@10.248.192.16>

Quoting Ian J Hart <ianjhart@ntlworld.com>:

> Quoting Ian J Hart <ianjhart@ntlworld.com>:
>
>> Is this likely to be hardware? Details will follow if not.
>>
>> [copied from a screen dump]
>>
>> Fatal trap 12: page fault while in kernel mode
>> cpuid = 1; apic id = 01
>> fault virtual address = 0x0
>> fault code = supervisor write data, page not present
>> instruction pointer = 0x8:0xffffffff807c6c12
>> stack pointer = 0x10:0xffffffff510e7890
>> frame pointer = 0x10:0xffffff00054a6c90
>> code segment = base 0x0, limit 0xfffff, type 0x1b
>> = DPL 0, pres 1, long 1 def32 0, gran 1
>> processor eflags = interrupt enabled, resume, IOPL = 0
>> current process = 75372 (printf)
>> trap number = 12
>> panic: page fault
>> cpuid = 1
>> uptime: 8m2s
>> Cannot dump. No dump device defined.
>>
>>
>
> [First attempt apparently went into a blackhole. Apologies in you  
> get this  twice.]
>
> Some suggestions (off list) that it may not be hardware, so here's  
> the follow up.
>
>  supermicro 5015b-mt (super X7SBi mobo)
>  Intel Q6600
>  8GB ECC DDR2
>  4x Seagate 320GB, two gmirror, two idle.
>
>  issues so far
>
>  1 OK) 7.x doesn't boot without hw.ata.atapi_dma=0. Not recently tested.
>  2 OK) disks enumerate differently 6.x to 7.x. Painful if you  
> hardwired the providor into your mirror.
>  3) 6.3 and 7.2 remote dump over ssh fails with 'Disconnecting:  
> Corrupted MAC on input.'
>  4) On 7.2 (AFAICT from logs) random reboots under load. e.g. the  
> above generated by a portupgrade run.
>
>  I had dumpdev=none as I hadn't setup rc.early to allow savecore to work.
>
>  In the interests of full disclosure I should say that this box was  
> migrated from older hardware and then source upgraded from i386 to  
> amd64 (6.3). Only one issue with that, format of accounting  
> file.Upgrade to 7.2 and a rebuild or two since then.
>
>  This box is our email server and there's no load. An identical box  
> running as a gateway/firewall backup dumps okay and doesn't reboot.  
> That box does drop network connections when running a cvsup server  
> (treelist write), but when configured to pass through these  
> connections (using balance) runs okay. But that's a story for  
> another day as it's still on 6.x.
>
>  Anyway, I put the two gmirror disks in another chassis and the  
> remote dumps are now completing.This at least does seem to be  
> hardware.
>
>  Before I moved the two gmirror disks I synced a third disk. I can  
> now test (most of) the original hardware and software.
>
>  I was unable to make this single disk system crash, so I added two  
> new disks and synced them.Now a 3 disk mirror, one disk idle.
>
>  I've disabled sendmail and the email server so as not to clash.
>
>  A portupgrade run caused a crash. I've setup coredumps so I can now  
> test. Remote backup dumps do fail.
>
>  xmail# kldstat
>  Id Refs Address            Size     Name
>   1    2 0xffffffff80100000 bd23e0   kernel
>   2    1 0xffffffff80cd3000 20608    geom_mirror.ko
>
>  I did have ipfw module loaded, but I got the crash without it so  
> I've removed it (firewall_type=OPEN).
>
>  Ran crashinfo, now have much more info than I need ;)
>
>  Starting another portupgrade run now to see how reproducable this is.
>
>  Later BIOS waiting in USB floppy.
>
[snip dmesg]

It took 2 runs of portupgrade -af.Some corruption in the dbs may have  
to pkg_delete -a.

FreeBSD * 7.2-RELEASE-p1 FreeBSD 7.2-RELEASE-p1 #0: Tue Jun 16  
18:03:10 BST 2009     *@*:/usr/obj/usr/src/sys/GENERIC  amd64

panic: page fault

GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "amd64-marcel-freebsd"...

Unread portion of the kernel message buffer:


Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address   = 0xfffffffff5555570
fault code              = supervisor write data, page not present
instruction pointer     = 0x8:0xffffffff807c429b
stack pointer           = 0x10:0xffffffff511e4710
frame pointer           = 0x10:0x20
code segment            = base 0x0, limit 0xfffff, type 0x1b
                         = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 69996 (mkdir)
trap number             = 12
panic: page fault
cpuid = 1
Uptime: 19h16m41s
Physical memory: 8177 MB
Dumping 730 MB: 715 699 683 667 651 635 619 603 587 571 555 539 523  
507 491 475 459 443 427 411 395 379 363 347 331 315 299 283 267 251  
235 219 203 187 171 155 139 123 107 91 75 59 43 27 11

Reading symbols from /boot/kernel/geom_mirror.ko...Reading symbols  
from /boot/kernel/geom_mirror.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/geom_mirror.ko
#0  doadump () at pcpu.h:195
195     pcpu.h: No such file or directory.
         in pcpu.h
(kgdb) #0  doadump () at pcpu.h:195
#1  0x0000000000000004 in ?? ()
#2  0xffffffff8050df19 in boot (howto=260)
     at /usr/src/sys/kern/kern_shutdown.c:418
#3  0xffffffff8050e322 in panic (fmt=0x104 <Address 0x104 out of bounds>)
     at /usr/src/sys/kern/kern_shutdown.c:574
#4  0xffffffff807d21f3 in trap_fatal (frame=0xffffff0005f94a50,  
eva=Variable "eva" is not available.
)
     at /usr/src/sys/amd64/amd64/trap.c:757
#5  0xffffffff807d25c5 in trap_pfault (frame=0xffffffff511e4660, usermode=0)
     at /usr/src/sys/amd64/amd64/trap.c:673
#6  0xffffffff807d2f04 in trap (frame=0xffffffff511e4660)
     at /usr/src/sys/amd64/amd64/trap.c:444
#7  0xffffffff807b706e in calltrap ()
     at /usr/src/sys/amd64/amd64/exception.S:209
#8  0xffffffff807c429b in free_pv_entry (pmap=0xffffffff80b66c80,  
pv=Variable "pv" is not available.
)
     at /usr/src/sys/amd64/amd64/pmap.c:1905
#9  0xffffffff807c4403 in pmap_remove_entry (pmap=Variable "pmap" is  
not available.
)
     at /usr/src/sys/amd64/amd64/pmap.c:2131
#10 0xffffffff807c6447 in pmap_remove_pte (pmap=0xffffffff80b66c80,
     ptq=0xaaaaaaa8, va=18446744070506639360, ptepde=23601251,
     free=0xffffffff511e4790) at /usr/src/sys/amd64/amd64/pmap.c:2366
#11 0xffffffff807cab87 in pmap_remove (pmap=0xffffffff80b66c80,
     sva=18446744070506639360, eva=18446744070506909696)
     at /usr/src/sys/amd64/amd64/pmap.c:2510
#12 0xffffffff8073bf80 in vm_map_delete (map=0xffffff00016830f8,
     start=18446744070506639360, end=18446744070506909696)
     at /usr/src/sys/vm/vm_map.c:2400
#13 0xffffffff80739905 in kmem_free_wakeup (map=0xffffff00016830f8,
     addr=18446744070506639360, size=267264) at /usr/src/sys/vm/vm_kern.c:462
#14 0xffffffff804e648d in exec_free_args (args=0xffffffff511e4b00)
     at /usr/src/sys/kern/kern_exec.c:1098
#15 0xffffffff804e784a in kern_execve (td=0xffffff0005f94a50,
     args=0xffffffff511e4b00, mac_p=Variable "mac_p" is not available.
) at /usr/src/sys/kern/kern_exec.c:836
#16 0xffffffff804e7fd7 in execve (td=0xffffff0005f94a50, uap=Variable  
"uap" is not available.
)
     at /usr/src/sys/kern/kern_exec.c:202
#17 0xffffffff807d2847 in syscall (frame=0xffffffff511e4c80)
     at /usr/src/sys/amd64/amd64/trap.c:900
#18 0xffffffff807b727b in Xfast_syscall ()
     at /usr/src/sys/amd64/amd64/exception.S:330
#19 0x00000008005044b0 in ?? ()
Previous frame inner to this frame (corrupt stack?)
(kgdb)


-- 
ian j hart

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


From tonix at interazioni.it  Tue Jul  7 11:20:29 2009
From: tonix at interazioni.it (Tonix (Antonio Nati))
Date: Tue Jul  7 11:20:36 2009
Subject: CARP in standard kernel?
Message-ID: <4A532938.2020207@interazioni.it>

I saw in the past requests for adding carp in standard kernel.
As of today, is there any chance to have it in kernel, as loadable module?
It would semplify a lot usage of freebsd-ipdate, instead of rebuilduing 
a custom kernel each time.

Thanks,

Tonino

-- 
------------------------------------------------------------
        Inter@zioni            Interazioni di Antonio Nati 
   http://www.interazioni.it      tonix@interazioni.it           
------------------------------------------------------------

From matheus at eternamente.info  Tue Jul  7 11:59:35 2009
From: matheus at eternamente.info (Nenhum_de_Nos)
Date: Tue Jul  7 11:59:43 2009
Subject: CARP in standard kernel?
In-Reply-To: <4A532938.2020207@interazioni.it>
References: <4A532938.2020207@interazioni.it>
Message-ID: <31e543efcd95f2d24d071467f4df04b4.squirrel@cygnus.homeunix.com>


On Tue, July 7, 2009 07:53, Tonix (Antonio Nati) wrote:
> I saw in the past requests for adding carp in standard kernel.
> As of today, is there any chance to have it in kernel, as loadable module?
> It would semplify a lot usage of freebsd-ipdate, instead of rebuilduing
> a custom kernel each time.

would be a great deal to me if I could have CARP and ALTQ built-in. no
need to recompile, just use freebsd-update :)

matheus


-- 
We will call you cygnus,
The God of balance you shall be

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

http://en.wikipedia.org/wiki/Posting_style
From dan.naumov at gmail.com  Tue Jul  7 13:05:34 2009
From: dan.naumov at gmail.com (Dan Naumov)
Date: Tue Jul  7 13:05:46 2009
Subject: FreeBSD 8.0-BETA1 Available
In-Reply-To: <1246926782.11597.23.camel@bauer.cse.buffalo.edu>
References: <1246926782.11597.23.camel@bauer.cse.buffalo.edu>
Message-ID: <cf9b1ee00907070605r727b98d2y915942cd96c25abc@mail.gmail.com>

On Tue, Jul 7, 2009 at 3:33 AM, Ken Smith<kensmith@cse.buffalo.edu> wrote:

> Be careful if you have SCSI drives, more USB disks than just the memory
> stick, etc - make sure /dev/da0 (or whatever you use) is the memory
> stick. ?Using this image for livefs based rescue mode is known to not
> work, that is one of the things still being worked on.

Hey

Just wanted a small clarification, does livefs based rescue mode mean
"fixit environment" or not? I would like to do some configuration
testing with 8.0-beta1, but applying the configuration pretty much
requires working in FIXIT, since sysinstall isn't exactly up to the
task.

- Sincerely,
Dan Naumov
From sagara at tomahawk.com.sg  Tue Jul  7 14:13:54 2009
From: sagara at tomahawk.com.sg (Sagara Wijetunga)
Date: Tue Jul  7 14:14:02 2009
Subject: FreeBSD 8.0-BETA1 Available
In-Reply-To: <1246926782.11597.23.camel@bauer.cse.buffalo.edu>
References: <1246926782.11597.23.camel@bauer.cse.buffalo.edu>
Message-ID: <20090707105550.23013.qmail@us1.tomahawkonline.net>

Ken Smith writes: 

> 
> The first public test build of the FreeBSD 8.0-RELEASE test cycle is now
> available, 8.0-BETA1.  Through the next week or so more information
> about the release will be posted but here is the current target schedule
> for the other 'major events': 
> 
> 	BETA2:	July 13, 2009
> 	BETA3:	July 20, 2009
> 	RC1:	July 27, 2009
> 	RC2:	August 17, 2009
> 	RELEASE:August 31, 2009 
> 

Hi all 

Congratulations! This is a very good news though we did not expect FreeBSD 
8.0 this soon. We planed our Tomahawk Desktop 3.0 to be based on FreeBSD 
8.0. Now days we are very busy finalising the Tomahawk Desktop 2.0 beta to 
be released somewhere in August. Will sure give FreeBSD 8.0 a try after we 
released our 2.0 beta. We wish good luck to FreeBSD 8.0 team. 

Best regards
Sagara
From petefrench at ticketswitch.com  Tue Jul  7 14:18:02 2009
From: petefrench at ticketswitch.com (Pete French)
Date: Tue Jul  7 14:18:09 2009
Subject: interrupt storm on MSI IXP600 based motherboards
Message-ID: <E1MOBUa-0000Ns-Br@dilbert.ticketswitch.com>

Oh FFS! This morning I sent the following email..

> Six months is a long gap! I was hooinh the problem had gone away. I
> havent seen it on here since I started running 7.2-STABLE, and
> before that I made it go away by using a debug kernel.

...and within an hour of typing that I also started seeing these
messages again for the first time in 6 months! That's one hell of
a co-inicdence. Surely it cant be date related ?

-pete.
From rick-freebsd2008 at kiwi-computer.com  Tue Jul  7 16:09:30 2009
From: rick-freebsd2008 at kiwi-computer.com (Rick C. Petty)
Date: Tue Jul  7 16:09:40 2009
Subject: What is /boot/kernel/*.symbols?
In-Reply-To: <20090707092451.GA92743@ei.bzerk.org>
References: <20090703152150.GE11039@hugo10.ka.punkt.de>
	<20090705003834.12211k8697td2o74@webmail.private.lan>
	<20090706073941.GA78371@ei.bzerk.org>
	<20090706074256.GD6306@hugo10.ka.punkt.de>
	<4A51B721.5020505@andric.com>
	<cf9b1ee00907060141w110e36c3p5922d31b3acd1f62@mail.gmail.com>
	<4A51B9FA.9010906@andric.com> <20090706093904.GA79434@ei.bzerk.org>
	<20090706212045.GA91095@keira.kiwi-computer.com>
	<20090707092451.GA92743@ei.bzerk.org>
Message-ID: <20090707160928.GA1662@keira.kiwi-computer.com>

On Tue, Jul 07, 2009 at 11:24:51AM +0200, Ruben de Groot wrote:
> On Mon, Jul 06, 2009 at 04:20:45PM -0500, Rick C. Petty typed:
> > On Mon, Jul 06, 2009 at 11:39:04AM +0200, Ruben de Groot wrote:
> > > On Mon, Jul 06, 2009 at 10:46:50AM +0200, Dimitry Andric typed:
> > > > 
> > > > Right, so it's a lot bigger on amd64.  I guess those 64-bit pointers
> > > > aren't entirely free. :)
> > > 
> > > I'm not sure where the size difference comes from. I have some sparc64
> > > systems running -current with symbols and the size of /boot/kernel is
> > > more comparable to i386, even with the 8-byte pointer size:
> > 
> > Um, probably there are a lot of devices on amd64 that aren't available for
> > sparc64?
> 
> Yes, That's probably it.

It was just a theory; I don't have sparc64.  What's your output of
"ls -1 /boot/kernel | wc"?

-- Rick C. Petty
From dan.naumov at gmail.com  Tue Jul  7 16:29:26 2009
From: dan.naumov at gmail.com (Dan Naumov)
Date: Tue Jul  7 16:29:32 2009
Subject: What is /boot/kernel/*.symbols?
In-Reply-To: <20090707160928.GA1662@keira.kiwi-computer.com>
References: <20090703152150.GE11039@hugo10.ka.punkt.de>
	<20090706073941.GA78371@ei.bzerk.org>
	<20090706074256.GD6306@hugo10.ka.punkt.de>
	<4A51B721.5020505@andric.com>
	<cf9b1ee00907060141w110e36c3p5922d31b3acd1f62@mail.gmail.com>
	<4A51B9FA.9010906@andric.com> <20090706093904.GA79434@ei.bzerk.org>
	<20090706212045.GA91095@keira.kiwi-computer.com>
	<20090707092451.GA92743@ei.bzerk.org>
	<20090707160928.GA1662@keira.kiwi-computer.com>
Message-ID: <cf9b1ee00907070929s6bf10465l8ab9eca24dfb0b51@mail.gmail.com>

On Tue, Jul 7, 2009 at 7:09 PM, Rick C.
Petty<rick-freebsd2008@kiwi-computer.com> wrote:
> On Tue, Jul 07, 2009 at 11:24:51AM +0200, Ruben de Groot wrote:
>> On Mon, Jul 06, 2009 at 04:20:45PM -0500, Rick C. Petty typed:
>> > On Mon, Jul 06, 2009 at 11:39:04AM +0200, Ruben de Groot wrote:
>> > > On Mon, Jul 06, 2009 at 10:46:50AM +0200, Dimitry Andric typed:
>> > > >
>> > > > Right, so it's a lot bigger on amd64. ?I guess those 64-bit pointers
>> > > > aren't entirely free. :)
>> > >
>> > > I'm not sure where the size difference comes from. I have some sparc64
>> > > systems running -current with symbols and the size of /boot/kernel is
>> > > more comparable to i386, even with the 8-byte pointer size:
>> >
>> > Um, probably there are a lot of devices on amd64 that aren't available for
>> > sparc64?
>>
>> Yes, That's probably it.
>
> It was just a theory; I don't have sparc64. ?What's your output of
> "ls -1 /boot/kernel | wc"?
>
> -- Rick C. Petty

atom# uname -a
FreeBSD atom.localdomain 7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #0: Wed
Jun 24 00:14:35 UTC 2009
root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64

atom# ls -1 /boot/kernel | wc
    1011    1011   15243

- Sincerely,
Dan Naumov
From sulfurfff at gmail.com  Tue Jul  7 16:45:34 2009
From: sulfurfff at gmail.com (Ishmael F.E.)
Date: Tue Jul  7 16:45:41 2009
Subject: upgrading ports without recompiling
In-Reply-To: <4A52ED7F.5030904@kkip.pl>
References: <ed5c0bbe0907060904m2a93aab7r9b17b8b5529dd8f0@mail.gmail.com>
	<4A523185.90007@smo.de>
	<alpine.BSF.2.00.0907062211190.95659@qvzrafvba.5c.ybpny>
	<4A52ED7F.5030904@kkip.pl>
Message-ID: <ed5c0bbe0907070945w34b0d4cagf300b2574145dc60@mail.gmail.com>

portupgrade -aPP seems to have worked, thougth I got LOTS of warnings and
plenty of packages weren't upgraded to the latest version (like gstreamer*
which latest version seems to be 0.10.22 but I still have 0.10.20 as
dependency
for pidgin)
.
As for compiling, I think it's not worth unless the OS is being twicked
which is
not the case for me at this moment.
.
Tanks for your help
.
.
2009/7/7 Bartosz Stec

>  CmdLnKid pisze:
>
> On Mon, 6 Jul 2009 13:16 -0000, pj wrote:
>
> Ishmael F.E. wrote:
> [...]
>
> .
> so, ?how can I upgrade the ports?
> unfortunatley I don't have time to compile my 64bit system
>
>  You don't need to compile whole OS to compile ports, if this is what you
> had in mind.
>
>
> Have you looked at the -PP option of portupgrade?
> I don't know how portmaster handles upgrades using packages only.
>
>
> You could look into devel/ccache & devel/distcc if you would like to speed
> up your compile times. Of course your first compile will always be the
> slowest one but everyone after that will be faster. This is not always
> advised as a good solution and has been known to throw some pretty weird
> compiler bugs and also fail while compiling certain ports but that is
> tweakable through /etc/make.conf*.
>
>  Well, I heard about some problems with ccache, although I personally
> experienced only one of them - fail when building world on AMD64. Here's my
> make.conf, feel free to give it try after installing ccache (Try to set
> MAKEOPTS = CPU cores +1, and set appropriate CPUTYPE):
>
> CPUTYPE=athlon64
> MAKEOPTS=-j3
>
> # USE CCACHE
> .if !defined(NOCCACHE)
> CC=/usr/local/libexec/ccache/world-cc
> CXX=/usr/local/libexec/ccache/world-c++
> .endif
>
> # default build settings for ports collection
> .if ${.CURDIR:M*/ports/*}
> CFLAGS= -O2 -fno-strict-aliasing -pipe -funroll-loops -fomit-frame-pointer
> CXXFLAGS= -O2 -fno-strict-aliasing -pipe -funroll-loops
> .endif
>
> # default build settings for base system
> .if ${.CURDIR:M*/usr/src/*} || ${.CURDIR:M*/usr/obj/*}
> CFLAGS=-O2 -fno-strict-aliasing -pipe
> COPTFLAGS=-O2 -fno-strict-aliasing -pipe
> CXXFLAGS=${CFLAGS}
> .endif
>
>  In case of any problem with specific port (or world) type in shell:
>
> # setenv NOCCACHE
>
> before build. This should give you maximum compile speed in case when
> package is unavailable while using portupgrade -afP
>
> --
> Bartosz Stec
>
>
>


-- 
[============================]
[En muchos lugares, tomar fotos es visto como]
[una costumbre vil y reprensible                      ]
[============================]
From kensmith at cse.Buffalo.EDU  Tue Jul  7 18:07:49 2009
From: kensmith at cse.Buffalo.EDU (Ken Smith)
Date: Tue Jul  7 18:07:56 2009
Subject: FreeBSD 8.0-BETA1 Available
In-Reply-To: <cf9b1ee00907070605r727b98d2y915942cd96c25abc@mail.gmail.com>
References: <1246926782.11597.23.camel@bauer.cse.buffalo.edu>
	<cf9b1ee00907070605r727b98d2y915942cd96c25abc@mail.gmail.com>
Message-ID: <1246990063.25765.18.camel@bauer.cse.buffalo.edu>

On Tue, 2009-07-07 at 16:05 +0300, Dan Naumov wrote:
> Just wanted a small clarification, does livefs based rescue mode mean
> "fixit environment" or not?

Yes, that's what it means.  It's known to not work at the moment but
it's being worked on.  I wanted to mention that because it might have
been confusing given what I put onto it (the files needed for livefs
mode are on it, sysinstall itself needs a bit more work though).  But
once that is working this is my guess as to what people would find most
useful on such an image so I wanted to give people a feel for roughly
how big they'll wind up being.  It will basically be the dvd minus
packages.

-- 
                                                Ken Smith
- From there to here, from here to      |       kensmith@cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090707/6df82179/attachment.pgp
From mahlon at martini.nu  Tue Jul  7 20:22:56 2009
From: mahlon at martini.nu (Mahlon E. Smith)
Date: Tue Jul  7 20:23:03 2009
Subject: ZFS: drive replacement performance
Message-ID: <20090707195614.GA24326@martini.nu>


I've got a 9 sata drive raidz1 array, started at version 6, upgraded to
version 13.  I had an apparent drive failure, and then at some point, a
kernel panic (unrelated to ZFS.)  The reboot caused the device numbers
to shuffle, so I did an 'export/import' to re-read the metadata and get
the array back up.

Once I swapped drives, I issued a 'zpool replace'.

That was 4 days ago now.  The progress in a 'zpool status' looks like
this, as of right now:

 scrub: resilver in progress for 0h0m, 0.00% done, 2251h0m to go

... which is a little concerning, since a) it appears to have not moved
since I started it, and b) I'm in a DEGRADED state until it finishes...
if it finishes.

So, I reach out to the list!

 - Is the resilver progress notification in a known weird state under
   FreeBSD?

 - Anything I can do to kick this in the pants?  Tuning params?

 - This was my first drive failure under ZFS -- anything I should have
   done differently?  Such as NOT doing the export/import? (Not sure
   what else I could have done there.)


Some additional info is below.  Drives are at about 20% busy, according
to vmstat.  Seem to have bandwidth to spare.

This is a FreeBSD 7.2-STABLE system from the end of May -- 32 bit, 2G of
RAM.  I have the luxury of this being a test machine (for exactly stuff
like this), so I'm willing to try whatever without worrying about
production data or SLA.  :)

--
Mahlon E. Smith  
http://www.martini.nu/contact.html



-----------------------------------------------------------------------

% zfs list store
NAME    USED  AVAIL  REFER  MOUNTPOINT
store  1.22T  2.36T  32.0K  none

-----------------------------------------------------------------------

% cat /boot/loader.conf
vm.kmem_size_max="768M"
vm.kmem_size="768M"
vfs.zfs.arc_max="256M"

-----------------------------------------------------------------------

% zpool status store
  pool: store
 state: DEGRADED
status: One or more devices is currently being resilvered.  The pool will
        continue to function, possibly in a degraded state.
action: Wait for the resilver to complete.
 scrub: resilver in progress for 0h0m, 0.00% done, 2251h0m to go
config:

        NAME                       STATE     READ WRITE CKSUM
        store                      DEGRADED     0     0     0
          raidz1                   DEGRADED     0     0     0
            da0                    ONLINE       0     0     0  274K resilvered
            da1                    ONLINE       0     0     0  282K resilvered
            replacing              DEGRADED     0     0     0
              2025342973333799752  UNAVAIL      3 4.11K     0  was /dev/da2
              da8                  ONLINE       0     0     0  418K resilvered
            da2                    ONLINE       0     0     0  280K resilvered
            da3                    ONLINE       0     0     0  269K resilvered
            da4                    ONLINE       0     0     0  266K resilvered
            da5                    ONLINE       0     0     0  270K resilvered
            da6                    ONLINE       0     0     0  270K resilvered
            da7                    ONLINE       0     0     0  267K resilvered

errors: No known data errors


-----------------------------------------------------------------------


% zpool iostat -v
                              capacity     operations    bandwidth
pool                        used  avail   read  write   read  write
-------------------------  -----  -----  -----  -----  -----  -----
store                      1.37T  2.72T     49    106   138K   543K
  raidz1                   1.37T  2.72T     49    106   138K   543K
    da0                        -      -     15     62  1017K  79.9K
    da1                        -      -     15     62  1020K  80.3K
    replacing                  -      -      0    103      0  88.3K
      2025342973333799752      -      -      0      0  1.45K    261
      da8                      -      -      0     79  1.45K  98.2K
    da2                        -      -     14     62   948K  80.3K
    da3                        -      -     13     62   894K  80.0K
    da4                        -      -     14     63   942K  80.3K
    da5                        -      -     15     62   992K  80.4K
    da6                        -      -     15     62  1000K  80.1K
    da7                        -      -     15     62  1022K  80.1K
-------------------------  -----  -----  -----  -----  -----  -----

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 155 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090707/7ac75b29/attachment.pgp
From fjwcash at gmail.com  Tue Jul  7 20:54:02 2009
From: fjwcash at gmail.com (Freddie Cash)
Date: Tue Jul  7 20:54:10 2009
Subject: ZFS: drive replacement performance
In-Reply-To: <20090707195614.GA24326@martini.nu>
References: <20090707195614.GA24326@martini.nu>
Message-ID: <b269bc570907071354r36015689ha362ba83413efc46@mail.gmail.com>

On Tue, Jul 7, 2009 at 12:56 PM, Mahlon E. Smith <mahlon@martini.nu> wrote:

> I've got a 9 sata drive raidz1 array, started at version 6, upgraded to
> version 13.  I had an apparent drive failure, and then at some point, a
> kernel panic (unrelated to ZFS.)  The reboot caused the device numbers
> to shuffle, so I did an 'export/import' to re-read the metadata and get
> the array back up.
>

This is why we've started using glabel(8) to label our drives, and then add
the labels to the pool:
  # zpool create store raidz1 label/disk01 label/disk02 label/disk03

That way, it does matter where the kernel detects the drives or what the
physical device node is called, GEOM picks up the label, and ZFS uses the
label.


> Once I swapped drives, I issued a 'zpool replace'.
>

See comment at the end:  what's the replace command that you used?


>
> That was 4 days ago now.  The progress in a 'zpool status' looks like
> this, as of right now:
>
>  scrub: resilver in progress for 0h0m, 0.00% done, 2251h0m to go
>
> ... which is a little concerning, since a) it appears to have not moved
> since I started it, and b) I'm in a DEGRADED state until it finishes...
> if it finishes.
>

There's something wrong here.  It definitely should be incrementing.  Even
when we did the foolish thing of creating a 24-drive raidz2 vdev and had to
replace a drive, the progress bar did change.  Never got above 39% as it
kept restarting, but it did increment.


>
> So, I reach out to the list!
>
>  - Is the resilver progress notification in a known weird state under
>   FreeBSD?
>
>  - Anything I can do to kick this in the pants?  Tuning params?
>

I'd redo the replace command, and check the output of "zpool status" to make
sure it's showing the proper device node and not some random string of
numbers like it is.


>  - This was my first drive failure under ZFS -- anything I should have
>   done differently?  Such as NOT doing the export/import? (Not sure
>   what else I could have done there.)
>

If you knew which drive it was, I'd have shutdown the server and replaced
it, so that the drives came back up renumbered correctly.

This happened to us once when I was playing around with simulating dead
drives (pulling drives) and rebooting.  That's when I moved over to using
glabels.


% zpool status store
>  pool: store
>  state: DEGRADED
> status: One or more devices is currently being resilvered.  The pool will
>        continue to function, possibly in a degraded state.
> action: Wait for the resilver to complete.
>  scrub: resilver in progress for 0h0m, 0.00% done, 2251h0m to go
> config:
>
>        NAME                       STATE     READ WRITE CKSUM
>        store                      DEGRADED     0     0     0
>          raidz1                   DEGRADED     0     0     0
>            da0                    ONLINE       0     0     0  274K
> resilvered
>            da1                    ONLINE       0     0     0  282K
> resilvered
>            replacing              DEGRADED     0     0     0
>              2025342973333799752  UNAVAIL      3 4.11K     0  was /dev/da2
>              da8                  ONLINE       0     0     0  418K
> resilvered
>            da2                    ONLINE       0     0     0  280K
> resilvered
>            da3                    ONLINE       0     0     0  269K
> resilvered
>            da4                    ONLINE       0     0     0  266K
> resilvered
>            da5                    ONLINE       0     0     0  270K
> resilvered
>            da6                    ONLINE       0     0     0  270K
> resilvered
>            da7                    ONLINE       0     0     0  267K
> resilvered
>
> errors: No known data errors
>
>
> -----------------------------------------------------------------------
>
>
> % zpool iostat -v
>                              capacity     operations    bandwidth
> pool                        used  avail   read  write   read  write
> -------------------------  -----  -----  -----  -----  -----  -----
> store                      1.37T  2.72T     49    106   138K   543K
>  raidz1                   1.37T  2.72T     49    106   138K   543K
>    da0                        -      -     15     62  1017K  79.9K
>    da1                        -      -     15     62  1020K  80.3K
>    replacing                  -      -      0    103      0  88.3K
>      2025342973333799752      -      -      0      0  1.45K    261
>      da8                      -      -      0     79  1.45K  98.2K
>    da2                        -      -     14     62   948K  80.3K
>    da3                        -      -     13     62   894K  80.0K
>    da4                        -      -     14     63   942K  80.3K
>    da5                        -      -     15     62   992K  80.4K
>    da6                        -      -     15     62  1000K  80.1K
>    da7                        -      -     15     62  1022K  80.1K
> -------------------------  -----  -----  -----  -----  -----  -----
>

That definitely doesn't look right.   It should be showing the device name
there in the "replacing" section.

What's the exact "zpool replace" command that you used?



-- 
Freddie Cash
fjwcash@gmail.com
From brooks at freebsd.org  Tue Jul  7 21:17:36 2009
From: brooks at freebsd.org (Brooks Davis)
Date: Tue Jul  7 21:17:43 2009
Subject: ZFS: drive replacement performance
In-Reply-To: <20090707195614.GA24326@martini.nu>
References: <20090707195614.GA24326@martini.nu>
Message-ID: <20090707205357.GA2415@lor.one-eyed-alien.net>

On Tue, Jul 07, 2009 at 12:56:14PM -0700, Mahlon E. Smith wrote:
> 
> I've got a 9 sata drive raidz1 array, started at version 6, upgraded to
> version 13.  I had an apparent drive failure, and then at some point, a
> kernel panic (unrelated to ZFS.)  The reboot caused the device numbers
> to shuffle, so I did an 'export/import' to re-read the metadata and get
> the array back up.
> 
> Once I swapped drives, I issued a 'zpool replace'.
> 
> That was 4 days ago now.  The progress in a 'zpool status' looks like
> this, as of right now:
> 
>  scrub: resilver in progress for 0h0m, 0.00% done, 2251h0m to go
> 
> ... which is a little concerning, since a) it appears to have not moved
> since I started it, and b) I'm in a DEGRADED state until it finishes...
> if it finishes.
> 
> So, I reach out to the list!
> 
>  - Is the resilver progress notification in a known weird state under
>    FreeBSD?
> 
>  - Anything I can do to kick this in the pants?  Tuning params?
> 
>  - This was my first drive failure under ZFS -- anything I should have
>    done differently?  Such as NOT doing the export/import? (Not sure
>    what else I could have done there.)

I'm seeing essentially the same think on an 8.0-BETA1 box with an 8-disk
raidz1 pool.  Every once in a while the system makes it to 0.05% done
and gives a vaguely reasonable rebuild time, but it quickly drops back
to reports 0.00% and it's basically not making any forward progress.  In
my case this is a copy of a mirror so while it would be a bit annoying
to rebuild, the system could be rebuilt fairly easily.

On thing I did just notice is that my zpool version is 13, but my file
systems are all v1 rather than the latest (v3).  I don't know if this is
relevant or not.

-- Brooks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090707/d66e898b/attachment.pgp
From mahlon at martini.nu  Tue Jul  7 22:26:32 2009
From: mahlon at martini.nu (Mahlon E. Smith)
Date: Tue Jul  7 22:26:39 2009
Subject: ZFS: drive replacement performance
In-Reply-To: <b269bc570907071354r36015689ha362ba83413efc46@mail.gmail.com>
References: <20090707195614.GA24326@martini.nu>
	<b269bc570907071354r36015689ha362ba83413efc46@mail.gmail.com>
Message-ID: <20090707222631.GA70750@martini.nu>

On Tue, Jul 07, 2009, Freddie Cash wrote:
> 
> This is why we've started using glabel(8) to label our drives, and then add
> the labels to the pool:
>   # zpool create store raidz1 label/disk01 label/disk02 label/disk03
> 
> That way, it does matter where the kernel detects the drives or what the
> physical device node is called, GEOM picks up the label, and ZFS uses the
> label.

Ah, slick.  I'll definitely be doing that moving forward.  Wonder if I
could do it piecemeal now via a shell game, labeling and replacing each
individual drive?  Will put that on my "try it" list.


> > Once I swapped drives, I issued a 'zpool replace'.
> >
> 
> See comment at the end:  what's the replace command that you used?


After the reboot that shuffled device order, the 'da2' changed to that
ID number.  To have it accept the replace command, I had to use the
number itself -- I couldn't use 'da2' since that was now elsewhere, in
use, on the raidz1.  Surprisingly, it worked.  Or at least, it appeared
to.

    % zpool replace store 2025342973333799752 da8


> There's something wrong here.  It definitely should be incrementing.  Even
> when we did the foolish thing of creating a 24-drive raidz2 vdev and had to
> replace a drive, the progress bar did change.  Never got above 39% as it
> kept restarting, but it did increment.

Strangely, the ETA is jumping all over the place, from 50 hours to 2000+
hours.  Never seen the percent complete over 0.01% done, but then it
goes back to 0.00%.


> I'd redo the replace command, and check the output of "zpool status"
> to make sure it's showing the proper device node and not some random
> string of numbers like it is.

Hmm, I'm hunting for it but I don't see it -- know of any way to stop a
replace in progress?

Thanks for the quick reply, Freddie!

--
Mahlon E. Smith  
http://www.martini.nu/contact.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 155 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090707/5198eb35/attachment.pgp
From fjwcash at gmail.com  Tue Jul  7 22:32:29 2009
From: fjwcash at gmail.com (Freddie Cash)
Date: Tue Jul  7 22:32:36 2009
Subject: ZFS: drive replacement performance
In-Reply-To: <20090707222631.GA70750@martini.nu>
References: <20090707195614.GA24326@martini.nu>
	<b269bc570907071354r36015689ha362ba83413efc46@mail.gmail.com>
	<20090707222631.GA70750@martini.nu>
Message-ID: <b269bc570907071532ub95af78i6ad3a09e8c6887d7@mail.gmail.com>

On Tue, Jul 7, 2009 at 3:26 PM, Mahlon E. Smith <mahlon@martini.nu> wrote:

> On Tue, Jul 07, 2009, Freddie Cash wrote:
> >
> > This is why we've started using glabel(8) to label our drives, and then
> add
> > the labels to the pool:
> >   # zpool create store raidz1 label/disk01 label/disk02 label/disk03
> >
> > That way, it does matter where the kernel detects the drives or what the
> > physical device node is called, GEOM picks up the label, and ZFS uses the
> > label.
>
> Ah, slick.  I'll definitely be doing that moving forward.  Wonder if I
> could do it piecemeal now via a shell game, labeling and replacing each
> individual drive?  Will put that on my "try it" list.
>

Yes, this can be done piecemeal, after the fact, on an already configured
pool.  That's how I did it on one of our servers.  It was originally
configured using the device node names (da0, da1, etc).  Then I set up the
second server, but used labels.  Then I went back to the first server,
labelled the drives, and did "zpool replace storage da0 label/disk01" for
each drive.  Doesn't take long to resilver, as it knows that it's the same
device.


>
>
> > > Once I swapped drives, I issued a 'zpool replace'.
> > >
> > See comment at the end:  what's the replace command that you used?
>
>
> After the reboot that shuffled device order, the 'da2' changed to that
> ID number.  To have it accept the replace command, I had to use the
> number itself -- I couldn't use 'da2' since that was now elsewhere, in
> use, on the raidz1.  Surprisingly, it worked.  Or at least, it appeared
> to.
>
>    % zpool replace store 2025342973333799752 da8
>

Hmm, you might be able to use glabel here, to label this new drive, and then
do the replace command using the label.

I think (never tried) you can use "zpool scrub -s store" to stop the
resilver.  If not, you should be able to re-do the replace command.


>
>
> > There's something wrong here.  It definitely should be incrementing.
>  Even
> > when we did the foolish thing of creating a 24-drive raidz2 vdev and had
> to
> > replace a drive, the progress bar did change.  Never got above 39% as it
> > kept restarting, but it did increment.
>
> Strangely, the ETA is jumping all over the place, from 50 hours to 2000+
> hours.  Never seen the percent complete over 0.01% done, but then it
> goes back to 0.00%.
>

Hrm, odd.

-- 
Freddie Cash
fjwcash@gmail.com
From dan.naumov at gmail.com  Tue Jul  7 22:40:06 2009
From: dan.naumov at gmail.com (Dan Naumov)
Date: Tue Jul  7 22:40:14 2009
Subject: ZFS: drive replacement performance
In-Reply-To: <b269bc570907071532ub95af78i6ad3a09e8c6887d7@mail.gmail.com>
References: <20090707195614.GA24326@martini.nu>
	<b269bc570907071354r36015689ha362ba83413efc46@mail.gmail.com>
	<20090707222631.GA70750@martini.nu>
	<b269bc570907071532ub95af78i6ad3a09e8c6887d7@mail.gmail.com>
Message-ID: <cf9b1ee00907071540u41128d3p528e1b240050d2f8@mail.gmail.com>

On Wed, Jul 8, 2009 at 1:32 AM, Freddie Cash<fjwcash@gmail.com> wrote:
> On Tue, Jul 7, 2009 at 3:26 PM, Mahlon E. Smith <mahlon@martini.nu> wrote:
>
>> On Tue, Jul 07, 2009, Freddie Cash wrote:
>> >
>> > This is why we've started using glabel(8) to label our drives, and then
>> add
>> > the labels to the pool:
>> > ? # zpool create store raidz1 label/disk01 label/disk02 label/disk03
>> >
>> > That way, it does matter where the kernel detects the drives or what the
>> > physical device node is called, GEOM picks up the label, and ZFS uses the
>> > label.
>>
>> Ah, slick. ?I'll definitely be doing that moving forward. ?Wonder if I
>> could do it piecemeal now via a shell game, labeling and replacing each
>> individual drive? ?Will put that on my "try it" list.

Not to derail this discussion, but can anyone explain if the actual
glabel metadata is protected in any way? If I use glabel to label a
disk and then create a pool using /dev/label/disklabel, won't ZFS
eventually overwrite the glabel metadata in the last sector since the
disk in it's entirety is given to the pool? Or is every filesystem
used by FreeBSD (ufs, zfs, etc) hardcoded to ignore the last few
sectors of any disk and/or partition and not write data to it to avoid
such issues?


- Sincerely,
Dan Naumov
From brooks at freebsd.org  Tue Jul  7 22:50:21 2009
From: brooks at freebsd.org (Brooks Davis)
Date: Tue Jul  7 22:50:27 2009
Subject: ZFS: drive replacement performance
In-Reply-To: <cf9b1ee00907071540u41128d3p528e1b240050d2f8@mail.gmail.com>
References: <20090707195614.GA24326@martini.nu>
	<b269bc570907071354r36015689ha362ba83413efc46@mail.gmail.com>
	<20090707222631.GA70750@martini.nu>
	<b269bc570907071532ub95af78i6ad3a09e8c6887d7@mail.gmail.com>
	<cf9b1ee00907071540u41128d3p528e1b240050d2f8@mail.gmail.com>
Message-ID: <20090707224916.GB2415@lor.one-eyed-alien.net>

On Wed, Jul 08, 2009 at 01:40:02AM +0300, Dan Naumov wrote:
> On Wed, Jul 8, 2009 at 1:32 AM, Freddie Cash<fjwcash@gmail.com> wrote:
> > On Tue, Jul 7, 2009 at 3:26 PM, Mahlon E. Smith <mahlon@martini.nu> wrote:
> >
> >> On Tue, Jul 07, 2009, Freddie Cash wrote:
> >> >
> >> > This is why we've started using glabel(8) to label our drives, and then
> >> add
> >> > the labels to the pool:
> >> > ? # zpool create store raidz1 label/disk01 label/disk02 label/disk03
> >> >
> >> > That way, it does matter where the kernel detects the drives or what the
> >> > physical device node is called, GEOM picks up the label, and ZFS uses the
> >> > label.
> >>
> >> Ah, slick. ?I'll definitely be doing that moving forward. ?Wonder if I
> >> could do it piecemeal now via a shell game, labeling and replacing each
> >> individual drive? ?Will put that on my "try it" list.
> 
> Not to derail this discussion, but can anyone explain if the actual
> glabel metadata is protected in any way? If I use glabel to label a
> disk and then create a pool using /dev/label/disklabel, won't ZFS
> eventually overwrite the glabel metadata in the last sector since the
> disk in it's entirety is given to the pool? Or is every filesystem
> used by FreeBSD (ufs, zfs, etc) hardcoded to ignore the last few
> sectors of any disk and/or partition and not write data to it to avoid
> such issues?

Disks labeled with glabel lose their last sector to the label.  It is not
accessible by ZFS.  Disks with bsdlabel partition tables are at risk due to
the brain dead decision to allow partitions to overlap the first sector,
but modern designs like glabel avoid this mistake.

-- Brooks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090707/4fa08f7f/attachment.pgp
From andrew at modulus.org  Tue Jul  7 22:53:01 2009
From: andrew at modulus.org (Andrew Snow)
Date: Tue Jul  7 22:53:09 2009
Subject: ZFS: drive replacement performance
In-Reply-To: <20090707222631.GA70750@martini.nu>
References: <20090707195614.GA24326@martini.nu>	<b269bc570907071354r36015689ha362ba83413efc46@mail.gmail.com>
	<20090707222631.GA70750@martini.nu>
Message-ID: <4A53CCEC.7010808@modulus.org>

Mahlon E. Smith wrote:

> Strangely, the ETA is jumping all over the place, from 50 hours to 2000+
> hours.  Never seen the percent complete over 0.01% done, but then it
> goes back to 0.00%.

Are you taking snapshots from crontab?  Older versions of the ZFS code 
re-started scrubbing whenever a snapshot was taken.
From brooks at freebsd.org  Tue Jul  7 23:10:42 2009
From: brooks at freebsd.org (Brooks Davis)
Date: Tue Jul  7 23:10:48 2009
Subject: ZFS: drive replacement performance
In-Reply-To: <4A53CCEC.7010808@modulus.org>
References: <20090707195614.GA24326@martini.nu>
	<b269bc570907071354r36015689ha362ba83413efc46@mail.gmail.com>
	<20090707222631.GA70750@martini.nu> <4A53CCEC.7010808@modulus.org>
Message-ID: <20090707230936.GC2415@lor.one-eyed-alien.net>

On Wed, Jul 08, 2009 at 08:32:12AM +1000, Andrew Snow wrote:
> Mahlon E. Smith wrote:
> 
>> Strangely, the ETA is jumping all over the place, from 50 hours to 2000+
>> hours.  Never seen the percent complete over 0.01% done, but then it
>> goes back to 0.00%.
> 
> Are you taking snapshots from crontab?  Older versions of the ZFS code 
> re-started scrubbing whenever a snapshot was taken.

I know I'm not doing anything to mine.  It's just sitting there unused.

-- Brooks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090707/bf72f7e3/attachment.pgp
From dan.naumov at gmail.com  Tue Jul  7 23:20:09 2009
From: dan.naumov at gmail.com (Dan Naumov)
Date: Tue Jul  7 23:20:16 2009
Subject: glabel metadata protection (WAS: ZFS: drive replacement performance)
Message-ID: <cf9b1ee00907071620i7a571be4w73aec90e97b3712a@mail.gmail.com>

>> Not to derail this discussion, but can anyone explain if the actual
>> glabel metadata is protected in any way? If I use glabel to label a
>> disk and then create a pool using /dev/label/disklabel, won't ZFS
>> eventually overwrite the glabel metadata in the last sector since the
>> disk in it's entirety is given to the pool? Or is every filesystem
>> used by FreeBSD (ufs, zfs, etc) hardcoded to ignore the last few
>> sectors of any disk and/or partition and not write data to it to avoid
>> such issues?
>
> Disks labeled with glabel lose their last sector to the label. ?It is not
> accessible by ZFS. ?Disks with bsdlabel partition tables are at risk due to
> the brain dead decision to allow partitions to overlap the first sector,
> but modern designs like glabel avoid this mistake.
>
> -- Brooks

So what happens if I was to do the following (for the same of example):

gpart create -s GPT /dev/ad1
glabel label -v disk01 /dev/ad1
gpart add -b 1 -s <ENTIREDISK> -t freebsd-zfs /dev/ad1

Does "gpart add" automatically somehow recognize that the last sector
of <ENTIREDISK> contains the glabel and automatically re-adjusts this
command to make the freebsd-zfs partition take "entiredisk minus last
sector" ? I can understand the logic of metadata being protected if I
do a: "gpart add -b 1 -s <ENTIREDISK> -t freebsd-zfs
/dev/label/disk01" since gpart will have to go through the actual
label first, but what actually happens if I issue a gpart directly to
the /dev/device?

- Sincerely,
Dan Naumov
From mahlon at martini.nu  Wed Jul  8 00:13:38 2009
From: mahlon at martini.nu (Mahlon E. Smith)
Date: Wed Jul  8 00:13:45 2009
Subject: ZFS: drive replacement performance
In-Reply-To: <b269bc570907071532ub95af78i6ad3a09e8c6887d7@mail.gmail.com>
References: <20090707195614.GA24326@martini.nu>
	<b269bc570907071354r36015689ha362ba83413efc46@mail.gmail.com>
	<20090707222631.GA70750@martini.nu>
	<b269bc570907071532ub95af78i6ad3a09e8c6887d7@mail.gmail.com>
Message-ID: <20090708001336.GA95670@martini.nu>

On Tue, Jul 07, 2009, Freddie Cash wrote:
> 
> I think (never tried) you can use "zpool scrub -s store" to stop the
> resilver.  If not, you should be able to re-do the replace command.

Hmm.  I think I may be stuck.

% zpool scrub -s store

% zpool status | grep scrub
   scrub: resilver in progress for 0h0m, 0.00% done, 745h41m to go

% zpool replace store 2025342973333799752 da8
  invalid vdev specification
  use '-f' to override the following errors:
  /dev/da8 is part of active pool 'store'
  
% zpool replace -f store 2025342973333799752 da8
  invalid vdev specification
  the following errors must be manually repaired:
  /dev/da8 is part of active pool 'store'

% zpool detach store da8
  cannot detach da8: no valid replicas

% zpool detach store 2025342973333799752
  cannot detach 2025342973333799752: no valid replicas



I also tried another export/import cycle, in the random hope that would
stop the active replace -- no dice.  *However*, on the import, now I see
this flooding my console (wasn't there previously, strangely):

Jul  7 16:50:15 disobedience root: ZFS: vdev I/O failure, zpool=store path=/dev/da2 offset=262144 size=8192 error=6
Jul  7 16:50:15 disobedience root: ZFS: vdev I/O failure, zpool=store path=/dev/da2 offset=499988824064 size=8192 error=6

I now have to wonder if that's really the active da2 it is complaining
about (the one claiming to be online with 0 errors) or the one I'm
trying to replace with da8.  The current da2 doesn't seem to be
having any additional problems, like the checksum mismatches or other
associated console errors I've come to expect, but of course the old one
is no longer attached to the machine.  In any event, I'd wager that
isn't something I normally want to see, and I may have something else
going on here.  (Bad controller, etc?)

Serves me right for naming a machine 'disobedience', I guess.  Next one
is getting named 'subservience.'

Going to halt and pull da8 under the assumption that will at least stop
the resilver, and try the detach again.  I'll holler back if I get stuff
going again, but this is looking more like a hardware problem.

Thanks again for the insight!

-Mahlon

--
Mahlon E. Smith  
http://www.martini.nu/contact.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 155 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090708/c5c33ed4/attachment.pgp
From dan.naumov at gmail.com  Wed Jul  8 00:57:30 2009
From: dan.naumov at gmail.com (Dan Naumov)
Date: Wed Jul  8 00:57:37 2009
Subject: 7.2-release/amd64: panic, spin lock held too long
In-Reply-To: <3bbf2fe10907061827g35eaeb49g26cf6fdb64436ca7@mail.gmail.com>
References: <cf9b1ee00907061812r3da70018i1c8d8d12bb038a80@mail.gmail.com>
	<3bbf2fe10907061818v245abd0cgc3ca5073cb93aea4@mail.gmail.com>
	<cf9b1ee00907061825r34165c48x6727c50b3219d5fb@mail.gmail.com>
	<3bbf2fe10907061827g35eaeb49g26cf6fdb64436ca7@mail.gmail.com>
Message-ID: <cf9b1ee00907071757i169d2a82la260798f364054f9@mail.gmail.com>

On Tue, Jul 7, 2009 at 4:27 AM, Attilio Rao<attilio@freebsd.org> wrote:
> 2009/7/7 Dan Naumov <dan.naumov@gmail.com>:
>> On Tue, Jul 7, 2009 at 4:18 AM, Attilio Rao<attilio@freebsd.org> wrote:
>>> 2009/7/7 Dan Naumov <dan.naumov@gmail.com>:
>>>> I just got a panic following by a reboot a few seconds after running
>>>> "portsnap update", /var/log/messages shows the following:
>>>>
>>>> Jul ?7 03:49:38 atom syslogd: kernel boot file is /boot/kernel/kernel
>>>> Jul ?7 03:49:38 atom kernel: spin lock 0xffffffff80b3edc0 (sched lock
>>>> 1) held by 0xffffff00017d8370 (tid 100054) too long
>>>> Jul ?7 03:49:38 atom kernel: panic: spin lock held too long
>>>
>>> That's a known bug, affecting -CURRENT as well.
>>> The cpustop IPI is handled though an NMI, which means it could
>>> interrupt a CPU in any moment, even while holding a spinlock,
>>> violating one well known FreeBSD rule.
>>> That means that the cpu can stop itself while the thread was holding
>>> the sched lock spinlock and not releasing it (there is no way, modulo
>>> highly hackish, to fix that).
>>> In the while hardclock() wants to schedule something else to run and
>>> got stuck on the thread lock.
>>>
>>> Ideal fix would involve not using a NMI for serving the cpustop while
>>> having a cheap way (not making the common path too hard) to tell
>>> hardclock() to avoid scheduling while cpustop is in flight.
>>>
>>> Thanks,
>>> Attilio
>>
>> Any idea if a fix is being worked on and how unlucky must one be to
>> run into this issue, should I expect it to happen again? Is it
>> basically completely random?
>
> I'd like to work on that issue before BETA3 (and backport to
> STABLE_7), I'm just time-constrained right now.
> it is completely random.
>
> Thanks,
> Attilio

Ok, this is getting pretty bad, 23 hours later, I get the same kind of
panic, the only difference is that instead of "portsnap update", this
was triggered by "portsnap cron" which I have running between 3 and 4
am every day:

Jul  8 03:03:49 atom kernel: ssppiinn  lloocckk
00xxffffffffffffffff8800bb33eeddc400  ((sscchheedd  lloocck k1 )0 )h
ehledl db yb y 0x0xfffffffffff0f00001081735339760e 0( t(itdi d
10100006070)5 )t otoo ol olnogng
Jul  8 03:03:49 atom kernel: p
Jul  8 03:03:49 atom kernel: anic: spin lock held too long
Jul  8 03:03:49 atom kernel: cpuid = 0
Jul  8 03:03:49 atom kernel: Uptime: 23h2m38s

- Sincerely,
Dan Naumov
From bp at barryp.org  Wed Jul  8 01:07:17 2009
From: bp at barryp.org (Barry Pederson)
Date: Wed Jul  8 01:07:29 2009
Subject: glabel metadata protection (WAS: ZFS: drive replacement
	performance)
In-Reply-To: <cf9b1ee00907071620i7a571be4w73aec90e97b3712a@mail.gmail.com>
References: <cf9b1ee00907071620i7a571be4w73aec90e97b3712a@mail.gmail.com>
Message-ID: <4A53ED2D.4070309@barryp.org>

Dan Naumov wrote:
>>> If I use glabel to label a
>>> disk and then create a pool using /dev/label/disklabel, won't ZFS
>>> eventually overwrite the glabel metadata in the last sector since the
>>> disk in it's entirety is given to the pool? 

I would say in this case you're *not* giving the entire disk to the 
pool, you're giving ZFS a geom that's one sector smaller than the disk. 
  ZFS never sees or can touch the glabel metadata.


> So what happens if I was to do the following (for the same of example):
> 
> gpart create -s GPT /dev/ad1
> glabel label -v disk01 /dev/ad1
> gpart add -b 1 -s <ENTIREDISK> -t freebsd-zfs /dev/ad1
> 
> Does "gpart add" automatically somehow recognize that the last sector
> of <ENTIREDISK> contains the glabel and automatically re-adjusts this
> command to make the freebsd-zfs partition take "entiredisk minus last
> sector" ? I can understand the logic of metadata being protected if I
> do a: "gpart add -b 1 -s <ENTIREDISK> -t freebsd-zfs
> /dev/label/disk01" since gpart will have to go through the actual
> label first, but what actually happens if I issue a gpart directly to
> the /dev/device?

I'd guess bad stuff would happen here, with a conflict between what gpt 
and glabel would want to do with the end of the disk.

If you wanted to use glabel with a GPT partition, I'd think you'd want to

   gpart create -s GPT /dev/ad1
   (use "gpart show" to see what space is now available for GPT
    partitions, it won't start at 1 and won't go to the very end of the
    disk)
   gpart add -b 34 -s <REMAININGDISK> -t freebsd-zfs /dev/ad1
   glabel label -v disk01 /dev/ad1p1

   (and then use label/disk01 in a zpool)

	Barry
From emikulic at gmail.com  Wed Jul  8 01:53:20 2009
From: emikulic at gmail.com (Emil Mikulic)
Date: Wed Jul  8 01:53:27 2009
Subject: ZFS: drive replacement performance
In-Reply-To: <20090707205357.GA2415@lor.one-eyed-alien.net>
References: <20090707195614.GA24326@martini.nu>
	<20090707205357.GA2415@lor.one-eyed-alien.net>
Message-ID: <20090708015317.GA47872@dmr.ath.cx>

On Tue, Jul 07, 2009 at 03:53:58PM -0500, Brooks Davis wrote:
> I'm seeing essentially the same think on an 8.0-BETA1 box with an 8-disk
> raidz1 pool.  Every once in a while the system makes it to 0.05% done
> and gives a vaguely reasonable rebuild time, but it quickly drops back
> to reports 0.00% and it's basically not making any forward progress.

You're not creating or deleting snapshots, are you?
AFAICT doing that will make scrub (and resilver) start from scratch.

--Emil
From drew at mykitchentable.net  Wed Jul  8 02:20:15 2009
From: drew at mykitchentable.net (Drew Tomlinson)
Date: Wed Jul  8 02:20:22 2009
Subject: Help With Custom Disk Layout For New Install
Message-ID: <4A53FC1B.5090303@mykitchentable.net>

I have a new box and have been trying to install 7.2 amd64 on it for the
past week.  I now see that 8.0-BETA1 is available and would be willing
to install it if it supports my intended config below.

I'm using this page as a guide but am at the console so I'm just using
the Fix It CD:

http://www.freebsd.org/doc/en/articles/remote-install/installation.html

I'm having two problems.  gmirror fails silently (i.e. nothing exists in
/dev/mirror).  zpool command complains about libraries not being
available or something to that effect.

I only want to use FreeBSD on this box and I want to dedicate all drives
to FreeBSD.  The box has 4 SATA drives detected as follows:

ad6 - 750 GB
ad8 - 500 GB
ad12 - 500 GB
ad14 - 500 GB

My thought is to break the disks up as so:

ad6
a: 500M
b: 500M
d: 465G
e: 225G (rest of drive)

ad8
a: 500M
b: 500M
d: 465G (rest of drive)

ad12
b: 1000M
d: 465G (rest of drive)

ad14
b: 1000M
d: 465G (rest of drive)

Then to install, I want to use gmirror and zfs as so:

/ - mirror ad6a and ad8a

swap - all the b: partitions (if that's the right term) for a total of 3
GB swap.

zfs - make a raid1z zpool with ad6d, ad8d, ad12d, and ad14d.  in this
pool I will create /usr and /var

ad6e will just be extra space for some other use.

So does my plan make sense?  And if so, how can I best accomplish it? Is
there a better guide somewhere?  Should I use gpart and glabel instead
of fdisk and bsdlabel?  I've read the man pages for gpart and glabel but
didn't really get it and thus returned to the more familiar fdisk and
bsdlabel.

Thanks,

Drew

-- 
Be a Great Magician!
Visit The Alchemist's Warehouse

http://www.alchemistswarehouse.com

From brooks at freebsd.org  Wed Jul  8 05:46:21 2009
From: brooks at freebsd.org (Brooks Davis)
Date: Wed Jul  8 05:46:27 2009
Subject: ZFS: drive replacement performance
In-Reply-To: <20090708015317.GA47872@dmr.ath.cx>
References: <20090707195614.GA24326@martini.nu>
	<20090707205357.GA2415@lor.one-eyed-alien.net>
	<20090708015317.GA47872@dmr.ath.cx>
Message-ID: <20090708054516.GA14211@lor.one-eyed-alien.net>

On Wed, Jul 08, 2009 at 11:53:17AM +1000, Emil Mikulic wrote:
> On Tue, Jul 07, 2009 at 03:53:58PM -0500, Brooks Davis wrote:
> > I'm seeing essentially the same think on an 8.0-BETA1 box with an 8-disk
> > raidz1 pool.  Every once in a while the system makes it to 0.05% done
> > and gives a vaguely reasonable rebuild time, but it quickly drops back
> > to reports 0.00% and it's basically not making any forward progress.
> 
> You're not creating or deleting snapshots, are you?
> AFAICT doing that will make scrub (and resilver) start from scratch.

As far as I know, no snapshots are being created or deleted.

-- Brooks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090708/0b664c2f/attachment.pgp
From mail25 at bzerk.org  Wed Jul  8 06:54:59 2009
From: mail25 at bzerk.org (Ruben de Groot)
Date: Wed Jul  8 06:55:06 2009
Subject: What is /boot/kernel/*.symbols?
In-Reply-To: <cf9b1ee00907070929s6bf10465l8ab9eca24dfb0b51@mail.gmail.com>
References: <20090706073941.GA78371@ei.bzerk.org>
	<20090706074256.GD6306@hugo10.ka.punkt.de>
	<4A51B721.5020505@andric.com>
	<cf9b1ee00907060141w110e36c3p5922d31b3acd1f62@mail.gmail.com>
	<4A51B9FA.9010906@andric.com> <20090706093904.GA79434@ei.bzerk.org>
	<20090706212045.GA91095@keira.kiwi-computer.com>
	<20090707092451.GA92743@ei.bzerk.org>
	<20090707160928.GA1662@keira.kiwi-computer.com>
	<cf9b1ee00907070929s6bf10465l8ab9eca24dfb0b51@mail.gmail.com>
Message-ID: <20090708065452.GB2904@ei.bzerk.org>

On Tue, Jul 07, 2009 at 07:29:24PM +0300, Dan Naumov typed:
> On Tue, Jul 7, 2009 at 7:09 PM, Rick C.
> Petty<rick-freebsd2008@kiwi-computer.com> wrote:
> > On Tue, Jul 07, 2009 at 11:24:51AM +0200, Ruben de Groot wrote:
> >> On Mon, Jul 06, 2009 at 04:20:45PM -0500, Rick C. Petty typed:
> >> > On Mon, Jul 06, 2009 at 11:39:04AM +0200, Ruben de Groot wrote:
> >> > > On Mon, Jul 06, 2009 at 10:46:50AM +0200, Dimitry Andric typed:
> >> > > >
> >> > > > Right, so it's a lot bigger on amd64. ?I guess those 64-bit pointers
> >> > > > aren't entirely free. :)
> >> > >
> >> > > I'm not sure where the size difference comes from. I have some sparc64
> >> > > systems running -current with symbols and the size of /boot/kernel is
> >> > > more comparable to i386, even with the 8-byte pointer size:
> >> >
> >> > Um, probably there are a lot of devices on amd64 that aren't available for
> >> > sparc64?
> >>
> >> Yes, That's probably it.
> >
> > It was just a theory; I don't have sparc64. ?What's your output of
> > "ls -1 /boot/kernel | wc"?
> >
> > -- Rick C. Petty
> 
> atom# uname -a
> FreeBSD atom.localdomain 7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #0: Wed
> Jun 24 00:14:35 UTC 2009
> root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
> 
> atom# ls -1 /boot/kernel | wc
>     1011    1011   15243

On sparc:

morninglightmountain# uname -pr
8.0-CURRENT sparc64
morninglightmountain# ls /boot/kernel | wc
     853     853   13045
morninglightmountain# wc -l /usr/src/sys/sparc64/conf/GENERIC /usr/src/sys/amd64/conf/GENERIC
     247 /usr/src/sys/sparc64/conf/GENERIC
     322 /usr/src/sys/amd64/conf/GENERIC
     569 total

So, fewer drivers and also less devices in GENERIC, as might be expected.

regards,
Ruben

From dan.naumov at gmail.com  Wed Jul  8 07:18:57 2009
From: dan.naumov at gmail.com (Dan Naumov)
Date: Wed Jul  8 07:19:04 2009
Subject: 7.2-release/amd64: panic, spin lock held too long
In-Reply-To: <cf9b1ee00907071757i169d2a82la260798f364054f9@mail.gmail.com>
References: <cf9b1ee00907061812r3da70018i1c8d8d12bb038a80@mail.gmail.com>
	<3bbf2fe10907061818v245abd0cgc3ca5073cb93aea4@mail.gmail.com>
	<cf9b1ee00907061825r34165c48x6727c50b3219d5fb@mail.gmail.com>
	<3bbf2fe10907061827g35eaeb49g26cf6fdb64436ca7@mail.gmail.com>
	<cf9b1ee00907071757i169d2a82la260798f364054f9@mail.gmail.com>
Message-ID: <cf9b1ee00907080018s3f32c8afr4f65f01ce9ff1f25@mail.gmail.com>

On Wed, Jul 8, 2009 at 3:57 AM, Dan Naumov<dan.naumov@gmail.com> wrote:
> On Tue, Jul 7, 2009 at 4:27 AM, Attilio Rao<attilio@freebsd.org> wrote:
>> 2009/7/7 Dan Naumov <dan.naumov@gmail.com>:
>>> On Tue, Jul 7, 2009 at 4:18 AM, Attilio Rao<attilio@freebsd.org> wrote:
>>>> 2009/7/7 Dan Naumov <dan.naumov@gmail.com>:
>>>>> I just got a panic following by a reboot a few seconds after running
>>>>> "portsnap update", /var/log/messages shows the following:
>>>>>
>>>>> Jul ?7 03:49:38 atom syslogd: kernel boot file is /boot/kernel/kernel
>>>>> Jul ?7 03:49:38 atom kernel: spin lock 0xffffffff80b3edc0 (sched lock
>>>>> 1) held by 0xffffff00017d8370 (tid 100054) too long
>>>>> Jul ?7 03:49:38 atom kernel: panic: spin lock held too long
>>>>
>>>> That's a known bug, affecting -CURRENT as well.
>>>> The cpustop IPI is handled though an NMI, which means it could
>>>> interrupt a CPU in any moment, even while holding a spinlock,
>>>> violating one well known FreeBSD rule.
>>>> That means that the cpu can stop itself while the thread was holding
>>>> the sched lock spinlock and not releasing it (there is no way, modulo
>>>> highly hackish, to fix that).
>>>> In the while hardclock() wants to schedule something else to run and
>>>> got stuck on the thread lock.
>>>>
>>>> Ideal fix would involve not using a NMI for serving the cpustop while
>>>> having a cheap way (not making the common path too hard) to tell
>>>> hardclock() to avoid scheduling while cpustop is in flight.
>>>>
>>>> Thanks,
>>>> Attilio
>>>
>>> Any idea if a fix is being worked on and how unlucky must one be to
>>> run into this issue, should I expect it to happen again? Is it
>>> basically completely random?
>>
>> I'd like to work on that issue before BETA3 (and backport to
>> STABLE_7), I'm just time-constrained right now.
>> it is completely random.
>>
>> Thanks,
>> Attilio
>
> Ok, this is getting pretty bad, 23 hours later, I get the same kind of
> panic, the only difference is that instead of "portsnap update", this
> was triggered by "portsnap cron" which I have running between 3 and 4
> am every day:
>
> Jul ?8 03:03:49 atom kernel: ssppiinn ?lloocckk
> 00xxffffffffffffffff8800bb33eeddc400 ?((sscchheedd ?lloocck k1 )0 )h
> ehledl db yb y 0x0xfffffffffff0f00001081735339760e 0( t(itdi d
> 10100006070)5 )t otoo ol olnogng
> Jul ?8 03:03:49 atom kernel: p
> Jul ?8 03:03:49 atom kernel: anic: spin lock held too long
> Jul ?8 03:03:49 atom kernel: cpuid = 0
> Jul ?8 03:03:49 atom kernel: Uptime: 23h2m38s

I have now tried repeating the problem by running "stress --cpu 8 --io
8 --vm 4 --vm-bytes 1024M --timeout 600s --verbose" which pushed
system load into the 15.50 ballpark and simultaneously running
"portsnap fetch" and "portsnap update" but I couldn't manually trigger
the panic, it seems that this problem is indeed random (although it
baffles me why is it specifically portsnap triggering it). I have now
disabled powerd to check whether that makes any difference to system
stability.

The only other things running on the system are: sshd, ntpd, smartd,
smbd/nmdb and a few instances of irssi in screens.

- Sincerely,
Dan Naumov
From tonix at interazioni.it  Wed Jul  8 08:10:30 2009
From: tonix at interazioni.it (Tonix (Antonio Nati))
Date: Wed Jul  8 08:10:37 2009
Subject: CARP in standard kernel?
In-Reply-To: <4A532938.2020207@interazioni.it>
References: <4A532938.2020207@interazioni.it>
Message-ID: <4A54546E.2070908@interazioni.it>

Tonix (Antonio Nati) ha scritto:
> I saw in the past requests for adding carp in standard kernel.
> As of today, is there any chance to have it in kernel, as loadable 
> module?
> It would semplify a lot usage of freebsd-ipdate, instead of 
> rebuilduing a custom kernel each time.
>
> Thanks,
>
> Tonino
>
May CARP be a loadable module, or does it need to 'stay' inside base kernel?

Tonino

-- 
------------------------------------------------------------
        Inter@zioni            Interazioni di Antonio Nati 
   http://www.interazioni.it      tonix@interazioni.it           
------------------------------------------------------------

From ronald-freebsd8 at klop.yi.org  Wed Jul  8 08:19:41 2009
From: ronald-freebsd8 at klop.yi.org (Ronald Klop)
Date: Wed Jul  8 08:19:53 2009
Subject: Zfs on usb-disk checksum errors?
Message-ID: <op.uwqpe0sn8527sy@82-170-177-25.ip.telfort.nl>

Hi.

I put zfs on my external usb-disk, so I can backup my harddisk with zfs  
send/receive.
I now have corruption on this volume.

[root@sjakie ~]# zpool status -v
   pool: extern
  state: ONLINE
status: One or more devices has experienced an error resulting in data
         corruption.  Applications may be affected.
action: Restore the file in question if possible.  Otherwise restore the
         entire pool from backup.
    see: http://www.sun.com/msg/ZFS-8000-8A
  scrub: scrub completed after 0h2m with 0 errors on Wed Jul  8 00:35:09  
2009
config:

         NAME        STATE     READ WRITE CKSUM
         extern      ONLINE       1     0     0
           da0       ONLINE       9     0     0

errors: Permanent errors have been detected in the following files:

         <0x3f>:<0xf5d6>

I don't really understand which files have corruption. :-(
In my syslog is this: (repeated quite often)
Jul  8 10:00:37 sjakie kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE  
CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0
Jul  8 10:00:37 sjakie kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI  
Status Error
Jul  8 10:00:37 sjakie kernel: (da0:umass-sim0:0:0:0): SCSI Status: Check  
Condition
Jul  8 10:00:37 sjakie kernel: (da0:umass-sim0:0:0:0): ILLEGAL REQUEST  
asc:20,0
Jul  8 10:00:37 sjakie kernel: (da0:umass-sim0:0:0:0): Invalid command  
operation code
Jul  8 10:00:37 sjakie kernel: (da0:umass-sim0:0:0:0): Unretryable error

and sometimes
Jul  8 10:00:35 sjakie root: ZFS: vdev I/O failure, zpool=extern  
path=/dev/da0 offset=127558877184 size=3072 error=5
Jul  8 10:00:35 sjakie root: ZFS: vdev I/O failure, zpool=extern  
path=/dev/da0 offset=127558877184 size=3072 error=5
Jul  8 10:00:35 sjakie root: ZFS: zpool I/O failure, zpool=extern error=5
With varying offsets and sizes.

What can I conclude from this? Is the disk failing? Is the 'Invalid  
command operation code' something to worry about? It didn't show up when  
the disk was UFS.

I reinstalled the pool but the read-errors showed up again.

Thanks for any advice,

Ronald.
From petefrench at ticketswitch.com  Wed Jul  8 08:38:05 2009
From: petefrench at ticketswitch.com (Pete French)
Date: Wed Jul  8 08:38:14 2009
Subject: glabel metadata protection (WAS: ZFS: drive replacement
	performance)
In-Reply-To: <4A53ED2D.4070309@barryp.org>
Message-ID: <E1MOSfB-0004Rl-GS@dilbert.ticketswitch.com>

> I would say in this case you're *not* giving the entire disk to the 
> pool, you're giving ZFS a geom that's one sector smaller than the disk. 
>   ZFS never sees or can touch the glabel metadata.

Is ZFS happy if the size of it's disc changes underneath it ? I have
expanded a zpool a couple of times simply by changing the size of
the partition and rebooting the machine - it comes up with the new
amount of free space fine. Never tried it the other way though. The
reason I mention it is that someone suggested glabeling a drive in
an existing pool and using replace to swap it over. Which should be good
I guess unless the last sector was in use. ZFS spreads stuff all over the
disc as I unserdtand it though, so that might not be a good assumption,
even on a fairly empty filesystem.

-pete.
From john.marshall at riverwillow.com.au  Wed Jul  8 09:07:10 2009
From: john.marshall at riverwillow.com.au (John Marshall)
Date: Wed Jul  8 09:07:45 2009
Subject: sshd GSSAPIAuthentication broken after 8.0-BETA1 upgrade
Message-ID: <20090708085202.GS1025@rwpc12.mby.riverwillow.net.au>

I source upgraded a (test) server here (i386) from 7.2-RELEASE-p2 to
8.0-BETA1 this morning.  I use GSSAPI as the primary authentication
method for sshd on that server.  After the upgrade GSSAPI authentication
stopped working and I can't get enough information to figure out why.
Perhaps the newer version of Heimdal behaves differently?  Perhaps the
newer version of sshd behaves differently?

If I run sshd with debug "-ddd" I see the following:

debug1: attempt 1 failures 0
debug2: input_userauth_request: try method gssapi-with-mic
debug3: mm_request_send entering: type 37
debug3: mm_request_receive_expect entering: type 38
debug3: mm_request_receive entering
debug3: monitor_read: checking request 37
debug3: mm_request_send entering: type 38
debug3: mm_request_receive entering
Postponed gssapi-with-mic for john from 192.0.2.123 port 57225 ssh2
debug3: mm_request_send entering: type 39
debug3: mm_request_receive_expect entering: type 40
debug3: mm_request_receive entering
debug3: monitor_read: checking request 39
debug1: Received some client credentials
debug3: mm_request_send entering: type 40
debug3: mm_request_receive entering
debug3: mm_request_send entering: type 43
debug3: mm_request_receive_expect entering: type 44
debug3: mm_request_receive entering
debug3: monitor_read: checking request 43
debug3: mm_request_send entering: type 44
debug3: mm_request_receive entering
GSSAPI MIC check failed

On the client side (with ssh -vvv) I see:

debug3: preferred gssapi-with-mic,publickey,keyboard-interactive,password
debug3: authmethod_lookup gssapi-with-mic
debug3: remaining preferred: publickey,keyboard-interactive,password
debug3: authmethod_is_enabled gssapi-with-mic
debug1: Next authentication method: gssapi-with-mic
debug2: we sent a gssapi-with-mic packet, wait for reply
debug1: Delegating credentials
debug1: Delegating credentials
debug1: Authentications that can continue: publickey,gssapi-with-mic,keyboard-interactive
debug2: we did not send a packet, disable method

Does anybody know of changes between existing STABLE releases and 8.0
which would cause this behaviour - and how to accommodate it?  Do any
strange Kerberos things need to be done as part of the upgrade?

The client still happily authenticates via GSSAPI to sshd on our other
7.2-RELEASE servers.  Subsequent authentication methods succeed on the
8.0-BETA1 sshd server, it's just GSSAPI that isn't working.

Thanks.

-- 
John Marshall
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090708/f52bfe77/attachment-0001.pgp
From attilio at freebsd.org  Wed Jul  8 09:50:37 2009
From: attilio at freebsd.org (Attilio Rao)
Date: Wed Jul  8 09:50:44 2009
Subject: 7.2-release/amd64: panic, spin lock held too long
In-Reply-To: <cf9b1ee00907080018s3f32c8afr4f65f01ce9ff1f25@mail.gmail.com>
References: <cf9b1ee00907061812r3da70018i1c8d8d12bb038a80@mail.gmail.com>
	<3bbf2fe10907061818v245abd0cgc3ca5073cb93aea4@mail.gmail.com>
	<cf9b1ee00907061825r34165c48x6727c50b3219d5fb@mail.gmail.com>
	<3bbf2fe10907061827g35eaeb49g26cf6fdb64436ca7@mail.gmail.com>
	<cf9b1ee00907071757i169d2a82la260798f364054f9@mail.gmail.com>
	<cf9b1ee00907080018s3f32c8afr4f65f01ce9ff1f25@mail.gmail.com>
Message-ID: <3bbf2fe10907080250q35899d3dhc2f101b62c6e5306@mail.gmail.com>

2009/7/8 Dan Naumov <dan.naumov@gmail.com>:
> On Wed, Jul 8, 2009 at 3:57 AM, Dan Naumov<dan.naumov@gmail.com> wrote:
>> On Tue, Jul 7, 2009 at 4:27 AM, Attilio Rao<attilio@freebsd.org> wrote:
>>> 2009/7/7 Dan Naumov <dan.naumov@gmail.com>:
>>>> On Tue, Jul 7, 2009 at 4:18 AM, Attilio Rao<attilio@freebsd.org> wrote:
>>>>> 2009/7/7 Dan Naumov <dan.naumov@gmail.com>:
>>>>>> I just got a panic following by a reboot a few seconds after running
>>>>>> "portsnap update", /var/log/messages shows the following:
>>>>>>
>>>>>> Jul  7 03:49:38 atom syslogd: kernel boot file is /boot/kernel/kernel
>>>>>> Jul  7 03:49:38 atom kernel: spin lock 0xffffffff80b3edc0 (sched lock
>>>>>> 1) held by 0xffffff00017d8370 (tid 100054) too long
>>>>>> Jul  7 03:49:38 atom kernel: panic: spin lock held too long
>>>>>
>>>>> That's a known bug, affecting -CURRENT as well.
>>>>> The cpustop IPI is handled though an NMI, which means it could
>>>>> interrupt a CPU in any moment, even while holding a spinlock,
>>>>> violating one well known FreeBSD rule.
>>>>> That means that the cpu can stop itself while the thread was holding
>>>>> the sched lock spinlock and not releasing it (there is no way, modulo
>>>>> highly hackish, to fix that).
>>>>> In the while hardclock() wants to schedule something else to run and
>>>>> got stuck on the thread lock.
>>>>>
>>>>> Ideal fix would involve not using a NMI for serving the cpustop while
>>>>> having a cheap way (not making the common path too hard) to tell
>>>>> hardclock() to avoid scheduling while cpustop is in flight.
>>>>>
>>>>> Thanks,
>>>>> Attilio
>>>>
>>>> Any idea if a fix is being worked on and how unlucky must one be to
>>>> run into this issue, should I expect it to happen again? Is it
>>>> basically completely random?
>>>
>>> I'd like to work on that issue before BETA3 (and backport to
>>> STABLE_7), I'm just time-constrained right now.
>>> it is completely random.
>>>
>>> Thanks,
>>> Attilio
>>
>> Ok, this is getting pretty bad, 23 hours later, I get the same kind of
>> panic, the only difference is that instead of "portsnap update", this
>> was triggered by "portsnap cron" which I have running between 3 and 4
>> am every day:
>>
>> Jul  8 03:03:49 atom kernel: ssppiinn  lloocckk
>> 00xxffffffffffffffff8800bb33eeddc400  ((sscchheedd  lloocck k1 )0 )h
>> ehledl db yb y 0x0xfffffffffff0f00001081735339760e 0( t(itdi d
>> 10100006070)5 )t otoo ol olnogng
>> Jul  8 03:03:49 atom kernel: p
>> Jul  8 03:03:49 atom kernel: anic: spin lock held too long
>> Jul  8 03:03:49 atom kernel: cpuid = 0
>> Jul  8 03:03:49 atom kernel: Uptime: 23h2m38s
>
> I have now tried repeating the problem by running "stress --cpu 8 --io
> 8 --vm 4 --vm-bytes 1024M --timeout 600s --verbose" which pushed
> system load into the 15.50 ballpark and simultaneously running
> "portsnap fetch" and "portsnap update" but I couldn't manually trigger
> the panic, it seems that this problem is indeed random (although it
> baffles me why is it specifically portsnap triggering it). I have now
> disabled powerd to check whether that makes any difference to system
> stability.

But is that happening at reboot time?

Thanks,
Attilio


-- 
Peace can only be achieved by understanding - A. Einstein
From lstewart at freebsd.org  Wed Jul  8 10:01:48 2009
From: lstewart at freebsd.org (Lawrence Stewart)
Date: Wed Jul  8 10:01:54 2009
Subject: CARP in standard kernel?
In-Reply-To: <4A532938.2020207@interazioni.it>
References: <4A532938.2020207@interazioni.it>
Message-ID: <4A546E73.4050603@freebsd.org>

Tonix (Antonio Nati) wrote:
> I saw in the past requests for adding carp in standard kernel.
> As of today, is there any chance to have it in kernel, as loadable module?
> It would semplify a lot usage of freebsd-ipdate, instead of rebuilduing 
> a custom kernel each time.

See the freebsd-net@ "CARP as a module; followup thoughts" thread for a 
link to a patch.

Cheers,
Lawrence
From hlh at restart.be  Wed Jul  8 10:18:43 2009
From: hlh at restart.be (Henri Hennebert)
Date: Wed Jul  8 10:18:50 2009
Subject: Zfs on usb-disk checksum errors?
In-Reply-To: <op.uwqpe0sn8527sy@82-170-177-25.ip.telfort.nl>
References: <op.uwqpe0sn8527sy@82-170-177-25.ip.telfort.nl>
Message-ID: <4A54727D.9080205@restart.be>

Ronald Klop wrote:
> Hi.
> 
> I put zfs on my external usb-disk, so I can backup my harddisk with zfs 
> send/receive.
> I now have corruption on this volume.
> 
> [root@sjakie ~]# zpool status -v
>   pool: extern
>  state: ONLINE
> status: One or more devices has experienced an error resulting in data
>         corruption.  Applications may be affected.
> action: Restore the file in question if possible.  Otherwise restore the
>         entire pool from backup.
>    see: http://www.sun.com/msg/ZFS-8000-8A
>  scrub: scrub completed after 0h2m with 0 errors on Wed Jul  8 00:35:09 
> 2009
> config:
> 
>         NAME        STATE     READ WRITE CKSUM
>         extern      ONLINE       1     0     0
>           da0       ONLINE       9     0     0
> 
> errors: Permanent errors have been detected in the following files:
> 
>         <0x3f>:<0xf5d6>
> 
> I don't really understand which files have corruption. :-(
> In my syslog is this: (repeated quite often)
> Jul  8 10:00:37 sjakie kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE 
> CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0
> Jul  8 10:00:37 sjakie kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI 
> Status Error
> Jul  8 10:00:37 sjakie kernel: (da0:umass-sim0:0:0:0): SCSI Status: 
> Check Condition
> Jul  8 10:00:37 sjakie kernel: (da0:umass-sim0:0:0:0): ILLEGAL REQUEST 
> asc:20,0
> Jul  8 10:00:37 sjakie kernel: (da0:umass-sim0:0:0:0): Invalid command 
> operation code
> Jul  8 10:00:37 sjakie kernel: (da0:umass-sim0:0:0:0): Unretryable error
> 
I experience the same error with 'Kingston DataTraveler II 1.13'. I 
simply add in /usr/src/sys/dev/usb/usbdevs:

product KINGSTON DATATRAVELER_2 0x1600 DAtaTraveler II

(VENDOR was already in the file).

and  in sys/dev/usb/storage/umass.c:

            { USB_VENDOR_KINGSTON, USB_PRODUCT_KINGSTON_DATATRAVELER_2, 
RID_WILDCARD, 

              UMASS_PROTO_SCSI | UMASS_PROTO_BBB, 
 

              NO_SYNCHRONIZE_CACHE 
 

            }, 


Note the flag NO_SYNCHRONIZE_CACHE and everything return to normal.

PS - I encounter this problem on 7.2_STABLE with the MFC of ZFS v13.

Henri

> and sometimes
> Jul  8 10:00:35 sjakie root: ZFS: vdev I/O failure, zpool=extern 
> path=/dev/da0 offset=127558877184 size=3072 error=5
> Jul  8 10:00:35 sjakie root: ZFS: vdev I/O failure, zpool=extern 
> path=/dev/da0 offset=127558877184 size=3072 error=5
> Jul  8 10:00:35 sjakie root: ZFS: zpool I/O failure, zpool=extern error=5
> With varying offsets and sizes.
> 
> What can I conclude from this? Is the disk failing? Is the 'Invalid 
> command operation code' something to worry about? It didn't show up when 
> the disk was UFS.
> 
> I reinstalled the pool but the read-errors showed up again.
> 
> Thanks for any advice,
> 
> Ronald.
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"

From Hans.F.Nordhaug at hiMolde.no  Wed Jul  8 12:11:33 2009
From: Hans.F.Nordhaug at hiMolde.no (Hans F. Nordhaug)
Date: Wed Jul  8 12:11:39 2009
Subject: portsnap and freebsd-update (metadata) failure
Message-ID: <20090708114127.GA22749@hiMolde.no>

Hi!

Quick question: Is it just me and my freshly installed FreeBSD 7.2
that fails when running freebsd-update or portsnap right now? With
freebsd-update I tried update4 and update1. Just ask for more info, if
it's needed to debug the problem.

Best regards,
Hans Nordhaug
From tonix at interazioni.it  Wed Jul  8 12:22:13 2009
From: tonix at interazioni.it (Tonix (Antonio Nati))
Date: Wed Jul  8 12:22:21 2009
Subject: CARP in standard kernel?
In-Reply-To: <4A546E73.4050603@freebsd.org>
References: <4A532938.2020207@interazioni.it> <4A546E73.4050603@freebsd.org>
Message-ID: <4A548F72.6070601@interazioni.it>

Lawrence Stewart ha scritto:
> Tonix (Antonio Nati) wrote:
>> I saw in the past requests for adding carp in standard kernel.
>> As of today, is there any chance to have it in kernel, as loadable 
>> module?
>> It would semplify a lot usage of freebsd-ipdate, instead of 
>> rebuilduing a custom kernel each time.
>
> See the freebsd-net@ "CARP as a module; followup thoughts" thread for 
> a link to a patch.
>

Conclusion of linked thread is not clear. CARP cannot be loadable, ok, 
but why cannot be included in standard kernel?

The same for AltQ, IPFW, PF, or other features widely used.
The most of ISP like me using FreeBSD will use at least one of these 
features, so we are excluded from freebsd-update.

Thanks,

Tonino


> Cheers,
> Lawrence
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>


-- 
------------------------------------------------------------
        Inter@zioni            Interazioni di Antonio Nati 
   http://www.interazioni.it      tonix@interazioni.it           
------------------------------------------------------------

From tonix at interazioni.it  Wed Jul  8 12:27:37 2009
From: tonix at interazioni.it (Tonix (Antonio Nati))
Date: Wed Jul  8 12:27:44 2009
Subject: CARP in standard kernel?
In-Reply-To: <4A548F72.6070601@interazioni.it>
References: <4A532938.2020207@interazioni.it> <4A546E73.4050603@freebsd.org>
	<4A548F72.6070601@interazioni.it>
Message-ID: <4A5490B5.4000708@interazioni.it>

Read again the linked thread, about loadable CARP.
It can be done, patch is for version 8, but it is not sure it will be 
included.
Any hope to have it, loadable or static doesn't matter, in 7.3?

Thanks,

Tonino

Tonix (Antonio Nati) ha scritto:
> Lawrence Stewart ha scritto:
>> Tonix (Antonio Nati) wrote:
>>> I saw in the past requests for adding carp in standard kernel.
>>> As of today, is there any chance to have it in kernel, as loadable 
>>> module?
>>> It would semplify a lot usage of freebsd-ipdate, instead of 
>>> rebuilduing a custom kernel each time.
>>
>> See the freebsd-net@ "CARP as a module; followup thoughts" thread for 
>> a link to a patch.
>>
>
> Conclusion of linked thread is not clear. CARP cannot be loadable, ok, 
> but why cannot be included in standard kernel?
>
> The same for AltQ, IPFW, PF, or other features widely used.
> The most of ISP like me using FreeBSD will use at least one of these 
> features, so we are excluded from freebsd-update.
>
> Thanks,
>
> Tonino
>
>
>> Cheers,
>> Lawrence
>> _______________________________________________
>> freebsd-stable@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to 
>> "freebsd-stable-unsubscribe@freebsd.org"
>>
>
>


-- 
------------------------------------------------------------
        Inter@zioni            Interazioni di Antonio Nati 
   http://www.interazioni.it      tonix@interazioni.it           
------------------------------------------------------------

From info at classicalsubjects.com  Wed Jul  8 16:36:04 2009
From: info at classicalsubjects.com (Classical Academic Press)
Date: Wed Jul  8 16:36:11 2009
Subject: New Poetry and Bible Texts for Homeschoolers
Message-ID: <9501410.1247069086350.KadaSegment.225.1@mta16br.cmpgnr.com>


   
   		
   			 [1]3D"" 
   July 2009
   		
   		
      [2][=] 
   Shipping by the end of July!   If you have ever felt mystified by, or unable to enjoy the signific   ance of poetry, this text will lead you step by step to an
   understanding an   gifted poet and teacher.    school or high school curric   reading a poem slowly and carefully, in   elements of poetry (such as imagery and metaphor) a   that can make a poem, from sonnet to open verse. In the b   practice is the best way to learn, this book is rich with explic   ations, exercises, and activities. A biography of each poet is also
   includ   poems. Also    containing explications of e   Art of Poetry Offered Online<   to study poetry with Christine Perr   the high school and college level (at Messi   offering an online course for 15 qualified students this   interested, please contact Christine directly at czperrin@gma   [3]Pre-Order and View Sample Chapters!

   Pre-Order Today! Song School Greek<
   [4][www.classicalacademicp=] 
   Shipping by    Song School Greek is a lively and gentle in   Greek, the language of the New Testament, designed for    the early elementary grades. Each of the thirty-two weekly less   includes songs, fun vocabulary, illustrations, handwriting practice,
   st   introduced i   A lively musical C   included in the program!    DVD for parents and teachers, wi   for teachers who do not know Greek thems   [5]Pre-Order and View Sample Chapters!

   <   class='bold2
   [6][ggcOT1_M=] 
   [7][ima=] God's Great Covenant, Old   which means that the entire Old Testam   series. God's Great Covenant is a grammar    classical in it's pedagogy. It teaches the facts o   elementary students in a clear chronological narrative, with   the main character.
   The texts are Reformed and Covenantal in the   and emphasize God's faithfulness through all histo   are told with simple elegance, appropriate for children, b   compromising on the heart of the Biblical text, or God's character a   nd his justice and mercy.
   If you have been looking for a meaty and chron   devotional study of the Bible for your children, this may be    what you are looking for!
   And two texts teaching the New Testam   Look for God's Great Covenant: New Testam   will focus entirely on Jesus' life in the Gosp
   			
   			 								
   				
   				   				
   [9][3D"http:=]
   
   <   [10][3D"htt=]
   
   
   
   [11]   
   			
   				
   			 				?Classical Academic Press3920 Market Street
   Camp Hill, PA 17011
   ph: 866-730-0711
   fax: 71   email: info@classicalsubjects.com
   www.classicalacademicpre   					
   		

   		
   You are subscribed as stable@freebsd.org. To unsubscribe please
   [12]click here.
   [aa_MED.jpg"] 
References

   Visible links
   1. 3D"http://cmpgnr.com/r.html?c=149   2. 3D"http://cmpgnr.com/r.html?c=1496458&r=1495115&t=1   3. 3D"http://cmpgnr.com/r.html?c=1496458&r=1495   4. 3D"http://cmpgnr.com/r.html?c=1496458&r=   5. 3D"http://cmpgnr.com/r.html?c=1496458&r=1495115&t   6. 3D"http://cmpgnr.com/r.html?c=14964   7. 3D"http://cmpgnr.com/r.html?c=1496   8. 3D"http://cmpgnr.com/r.html?c=1496458&r=1495115&t   9. 3D"http://cmpgnr=/
  10. 3D"http://cmpgnr.c=/
  11. ="http://cmpgnr.com/r.html?c=1496458&r=1495115&t=1717761457&l=1&d  12. file://localhost/tmp/3D
   Hidden links:
  13. 3D"http://=/
From info at classicalsubjects.com  Wed Jul  8 16:38:24 2009
From: info at classicalsubjects.com (Classical Academic Press)
Date: Wed Jul  8 16:38:30 2009
Subject: New Poetry and Bible Texts for Homeschoolers
Message-ID: <19118957.1247069146530.KadaSegment.227.3@mta21br.cmpgnr.com>


   
   		
   			 [1]3D"" 
   July 2009
   		
   		
      [2][=] 
   Shipping by the end of July!   If you have ever felt mystified by, or unable to enjoy the signific   ance of poetry, this text will lead you step by step to an
   understanding an   gifted poet and teacher.    school or high school curric   reading a poem slowly and carefully, in   elements of poetry (such as imagery and metaphor) a   that can make a poem, from sonnet to open verse. In the b   practice is the best way to learn, this book is rich with explic   ations, exercises, and activities. A biography of each poet is also
   includ   poems. Also    containing explications of e   Art of Poetry Offered Online<   to study poetry with Christine Perr   the high school and college level (at Messi   offering an online course for 15 qualified students this   interested, please contact Christine directly at czperrin@gma   [3]Pre-Order and View Sample Chapters!

   Pre-Order Today! Song School Greek<
   [4][www.classicalacademicp=] 
   Shipping by    Song School Greek is a lively and gentle in   Greek, the language of the New Testament, designed for    the early elementary grades. Each of the thirty-two weekly less   includes songs, fun vocabulary, illustrations, handwriting practice,
   st   introduced i   A lively musical C   included in the program!    DVD for parents and teachers, wi   for teachers who do not know Greek thems   [5]Pre-Order and View Sample Chapters!

   <   class='bold2
   [6][ggcOT1_M=] 
   [7][ima=] God's Great Covenant, Old   which means that the entire Old Testam   series. God's Great Covenant is a grammar    classical in it's pedagogy. It teaches the facts o   elementary students in a clear chronological narrative, with   the main character.
   The texts are Reformed and Covenantal in the   and emphasize God's faithfulness through all histo   are told with simple elegance, appropriate for children, b   compromising on the heart of the Biblical text, or God's character a   nd his justice and mercy.
   If you have been looking for a meaty and chron   devotional study of the Bible for your children, this may be    what you are looking for!
   And two texts teaching the New Testam   Look for God's Great Covenant: New Testam   will focus entirely on Jesus' life in the Gosp
   			
   			 								
   				
   				   				
   [9][3D"http:=]
   
   <   [10][3D"htt=]
   
   
   
   [11]   
   			
   				
   			 				?Classical Academic Press3920 Market Street
   Camp Hill, PA 17011
   ph: 866-730-0711
   fax: 71   email: info@classicalsubjects.com
   www.classicalacademicpre   					
   		

   		
   You are subscribed as stable@freebsd.org. To unsubscribe please
   [12]click here.
   [aa_MED.jpg"] 
References

   Visible links
   1. 3D"http://cmpgnr.com/r.html?c=149   2. 3D"http://cmpgnr.com/r.html?c=1496464&r=1495121&t=1   3. 3D"http://cmpgnr.com/r.html?c=1496464&r=1495   4. 3D"http://cmpgnr.com/r.html?c=1496464&r=   5. 3D"http://cmpgnr.com/r.html?c=1496464&r=1495121&t   6. 3D"http://cmpgnr.com/r.html?c=14964   7. 3D"http://cmpgnr.com/r.html?c=1496   8. 3D"http://cmpgnr.com/r.html?c=1496464&r=1495121&t   9. 3D"http://cmpgnr=/
  10. 3D"http://cmpgnr.c=/
  11. ="http://cmpgnr.com/r.html?c=1496464&r=1495121&t=1717748658&l=1&d  12. file://localhost/tmp/3D
   Hidden links:
  13. 3D"http://=/
From tex at unixteacher.org  Wed Jul  8 18:12:56 2009
From: tex at unixteacher.org (Amza Marian)
Date: Wed Jul  8 18:13:03 2009
Subject: New Poetry and Bible Texts for Homeschoolers
In-Reply-To: <19118957.1247069146530.KadaSegment.227.3@mta21br.cmpgnr.com>
References: <19118957.1247069146530.KadaSegment.227.3@mta21br.cmpgnr.com>
Message-ID: <F76F9B7ECB1C4BF19DD88B7CA66C500A@workstation>


 You are idiot ?
That is email address for FreeBSD discussions.

"You are subscribed as stable@freebsd.org. To unsubscribe please click .."

 In your bible there is no rules abut spammers  :-P


----- Original Message ----- 
From: "Classical Academic Press" <info@classicalsubjects.com>
To: <stable@freebsd.org>
Sent: Wednesday, July 08, 2009 6:05 PM
Subject: New Poetry and Bible Texts for Homeschoolers



   =09


   [1]3D""
   July 2009


   =09 The Art of Poetry by Christine Perrin, MFA   [2][=
   Shipping by the end of July!=
   If you have ever felt mystified by, or unable to enjoy the signific 
ance of poetry, this text will lead you step by step to an
   understanding an= love of this branch of literature, guided by a
   gifted poet and teacher. =he Art of Poetry is a excellent middle
   school or high school curric=lum; it will teach the practice of
   reading a poem slowly and carefully, in=roduce students to the
   elements of poetry (such as imagery and metaphor) a=d the many forms
   that can make a poem, from sonnet to open verse. In the b=lief that
   practice is the best way to learn, this book is rich with explic 
ations, exercises, and activities. A biography of each poet is also
   includ=d, along with an audio CD featuring a reading of many of the
   poems. Also =vailable is a corresponding teacher's edition
   containing explications of e=ery poem in the student text.
   Art of Poetry Offered Online<=r>Do you have a student who would like
   to study poetry with Christine Perr=n? Christine teaches poetry at
   the high school and college level (at Messi=h College) and is
   offering an online course for 15 qualified students this=all. If
   interested, please contact Christine directly at czperrin@gma=l.com.
   [3]Pre-Order and View Sample Chapters!

   Pre-Order Today! Song School Greek<=font>

   [4][www.classicalacademicp=
   Shipping by =he end of July!
   Song School Greek is a lively and gentle in=roduction to Koine
   Greek, the language of the New Testament, designed for =hildren in
   the early elementary grades. Each of the thirty-two weekly less=ns
   includes songs, fun vocabulary, illustrations, handwriting practice,
   st=ries, games and activities. Enjoyable, everyday vocabulary is
   introduced i= weekly lessons to encourage and engage young students.
   A lively musical C=, with a track corresponding to each chapter, is
   included in the program! =he Teacher's Edition will also include a
   DVD for parents and teachers, wi=h extra instruction, particularly
   for teachers who do not know Greek thems=lves!
   [5]Pre-Order and View Sample Chapters!

   <=ont face='Verdana,Arial, Helvetica,sans-serif' size='2'
   class='bold2=>Now Available! God's Great Covenant Book =.

   [6][ggcOT1_M=
   [7][ima=God's Great Covenant, Old=estament Two is now available,
   which means that the entire Old Testam=nt is now taught in the
   series. God's Great Covenant is a grammar =tage Bible curriculum,
   classical in it's pedagogy. It teaches the facts o= the Bible to
   elementary students in a clear chronological narrative, with=od as
   the main character.
   The texts are Reformed and Covenantal in the=r theological approach,
   and emphasize God's faithfulness through all histo=y. The stories
   are told with simple elegance, appropriate for children, b=t not
   compromising on the heart of the Biblical text, or God's character a   nd 
his justice and mercy.
   If you have been looking for a meaty and chron=logical, yet
   devotional study of the Bible for your children, this may be =ust
   what you are looking for!
   And two texts teaching the New Testam=nt are on their way as well!
   Look for God's Great Covenant: New Testam=nt One next spring! It
   will focus entirely on Jesus' life in the Gosp=ls.




   =09 [8] 3D""

   [9][3D"http:=

   <= name="contentBlock1004">
   [10][3D"htt=



   [11]=aa_MED.jpg"]



   ?Classical Academic Press3920 Market Street
   Camp Hill, PA 17011
   ph: 866-730-0711
   fax: 71=-730-0721
   email: info@classicalsubjects.com
   www.classicalacademicpre=s.com




   You are subscribed as stable@freebsd.org. To unsubscribe please
   [12]click here.
   [aa_MED.jpg"]
References

   Visible links
   1. 3D"http://cmpgnr.com/r.html?c=149   2. 
3D"http://cmpgnr.com/r.html?c=1496464&r=1495121&t=1   3. 
3D"http://cmpgnr.com/r.html?c=1496464&r=1495   4. 
3D"http://cmpgnr.com/r.html?c=1496464&r=   5. 
3D"http://cmpgnr.com/r.html?c=1496464&r=1495121&t   6. 
3D"http://cmpgnr.com/r.html?c=14964   7. 3D"http://cmpgnr.com/r.html?c=1496 
8. 3D"http://cmpgnr.com/r.html?c=1496464&r=1495121&t   9. 3D"http://cmpgnr=
  10. 3D"http://cmpgnr.c=
  11. ="http://cmpgnr.com/r.html?c=1496464&r=1495121&t=1717748658&l=1&d  12. 
file://localhost/tmp/3D
   Hidden links:
  13. 3D"http://=
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" 

From cm at therek.net  Wed Jul  8 19:45:33 2009
From: cm at therek.net (Cezary Morga)
Date: Wed Jul  8 19:45:40 2009
Subject: New Poetry and Bible Texts for Homeschoolers
In-Reply-To: <F76F9B7ECB1C4BF19DD88B7CA66C500A@workstation>
References: <19118957.1247069146530.KadaSegment.227.3@mta21br.cmpgnr.com>
	<F76F9B7ECB1C4BF19DD88B7CA66C500A@workstation>
Message-ID: <4A54F462.4050800@therek.net>

Amza Marian pisze:
>  You are idiot ?
> That is email address for FreeBSD discussions.
> 
> "You are subscribed as stable@freebsd.org. To unsubscribe please click .."
> 
>  In your bible there is no rules abut spammers  :-P

Way to go tiger!
Answering an obvious spam is not very smart. Are you an eye-dee-ten-tee too?

-- 
Cezary Morga
"Middle age is when you've met so many people that every new person you 
meet reminds you of someone else." (Ogden Nash)
From andreast-list at fgznet.ch  Wed Jul  8 20:27:04 2009
From: andreast-list at fgznet.ch (Andreas Tobler)
Date: Wed Jul  8 20:27:17 2009
Subject: FreeBSD 8.0-BETA1 Available
In-Reply-To: <1246926782.11597.23.camel@bauer.cse.buffalo.edu>
References: <1246926782.11597.23.camel@bauer.cse.buffalo.edu>
Message-ID: <4A54FB33.8060705@fgznet.ch>

Ken Smith wrote:

> The amd64 and i386 architectures include a file named:
> 
> 	8.0-BETA1-<arch>-memstick.img
> 
> If you copy that to a USB memory stick newer machines should be able to
> boot from it and use it to install from.  Note that you need to
> overwrite the contents of the memory stick completely, not copy it into
> an existing filesystem on the memory stick.  Exactly how you do that
> depends on your machine but just to give you an example this works on
> the machine I tested it with:
> 
>   dd if=8.0-BETA1-amd64-memstick.img of=/dev/da0 bs=10240 conv=sync
> 
> Be careful if you have SCSI drives, more USB disks than just the memory
> stick, etc - make sure /dev/da0 (or whatever you use) is the memory
> stick.  Using this image for livefs based rescue mode is known to not
> work, that is one of the things still being worked on.

Unfortunately my biggest mem stick has only 512MB. So I tried to dd to 
an usb drive. (Will get a bigger stick tomorrow)

I was successful in installing the image, although, a few packages did 
not install. I did a kern developer package. I guess the packages are 
missing on the .img?

Right now I'm installing the other things via net.

Is this method equal to an usb stick install at all?

Below the top of dmesg.

TIA,
Andreas

---
Copyright (c) 1992-2009 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 8.0-BETA1 #0: Sat Jul  4 03:55:14 UTC 2009
     root@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
WARNING: WITNESS option enabled, expect reduced performance.
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2793.01-MHz 686-class CPU)
   Origin = "GenuineIntel"  Id = 0xf29  Stepping = 9
 
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
   Features2=0x4400<CNXT-ID,xTPR>
real memory  = 536870912 (512 MB)
avail memory = 473395200 (451 MB)
---
From thomas at ronner.org  Wed Jul  8 21:00:25 2009
From: thomas at ronner.org (Thomas Ronner)
Date: Wed Jul  8 21:00:33 2009
Subject: ZFS: zpool scrub lockup
Message-ID: <1247085058.6197.18.camel@bugstore>

Hello,

I don't know whether this is the right list; maybe freebsd-fs is more
appropriate. So please redirect me there if this isn't the right place.

My system (i386, Athlon XP) locks hard when scrubbing a certain pool. It
has been doing this for at least a couple of months now. For this reason
I upgraded to 7.2-STABLE recently as this had the latest ZFS bits, but
this doesn't help. It even makes the problem worse: in previous versions
I just hit the reset button and forgot about it, but now it "remembers"
that it was scrubbing (I presume) and tries to resume at the exact same
place, locking up again. This means I haven't been able to mount these
ZFS volumes successfully: the moment I do a /etc/rc.d/zfs start from
single user mode (I have my /, /var and /usr on UFS) it locks up in a
couple of seconds. And by locks up I really mean locks up. No panic,
nothing. Pressing the reset button on the chassis is the only way to
reboot. 

Details about my system:
Athlon XP 2400+
Asus K7V-880 (VIA chipset; 2 IDE, 2 SATA ports)
2 GB RAM
Promise Ultra133-TX2 (2 port IDE controller)
Promise SATA150 4 port SATA controller
Promise SATA300 4 port SATA controller
4 Maxtor 300 GB IDE disks
1 Maxtor 300 GB SATA disk
1 WD 320 GB SATA disk
6 Samsung 1 TB SATA disks

The Samsung disks form the pool I'm having trouble with. They are
connected to the Promise controllers.

Does anyone know how I can debug this? I'm not even sure whether it is a
software or a hardware problem. Any help is greatly appreciated!


Regards,
Thomas

From john.marshall at riverwillow.com.au  Thu Jul  9 03:41:47 2009
From: john.marshall at riverwillow.com.au (John Marshall)
Date: Thu Jul  9 03:41:54 2009
Subject: 8.0-BETA1 Source Upgrade breaks NTP configuration
Message-ID: <20090709021119.GA26896@rwpc12.mby.riverwillow.net.au>

Yesterday I source-upgraded a 7.2-RELEASE-p2 test i386 server to
8.0-BETA1.  I have just discovered that it broke that server's NTP
service.

PROBLEM 1 - Existing /etc/ntp.conf overwritten

For source upgrades I run "mergemaster -iCPU" and it has served me well
until now.  Mergemaster appeared to run "as normal" for this upgrade,
prompting me for decisions on how to deal with the handful of usual
files.  It didn't tell me that it had decided to overwrite my existing
/etc/ntp.conf with the new default version from the source tree!  (OK,
perhaps it told me in the big, long list at the end but it didn't prompt
me to supersede my existing file).

Looking at the mergemaster(8) man page, I can't see how the options I
use would have resulted in my existing /etc/ntp.conf being overwritten
with the version from the source tree - but obviously there is a woops
factor there, either with me or mergemaster.

Digging deeper, it looks like it may be due to the fact that this is a
new supplied file and an entry for /etc/ntp.conf didn't exist in
/var/db/mergemaster.mtree from the previous (7.2-RELEASE) run.  How
should this be handled?

PROBLEM 2 - Default ntp.conf uses LOCAL clock

So, having had the FreeBSD upgrade magically re-configure my NTP server
(no, I wasn't prompted to overwrite ntp.conf), I find that my NTP server
is now synchronizing with it's own (potentially wrong) local system
clock!  Our firewall is configured to allow NTP traffic between our
internal NTP servers and specific upstream NTP servers.  The default
configuration file specifies different servers which we don't use, so
this NTP server couldn't "see" them.

The new default configuration file includes "127.127.1.0" as a
configured server.  Because we could see no "real" NTP servers, we
synchronized with our local system clock.  That means that we think we
are synchronized to a reliable upstream source.  Rather than losing
synch and discovering the problem, we think we are synchronized to a
reliable source and we and our clients drift away from reality in
blissful ignorance.  Surely this violates POLA!

Could we *please* at least comment out the LOCAL server config in the
supplied ntp.conf?  Personally I would rather see it removed.  It is one
thing to tell people where the gun is if they want to shoot themselves
in the foot; it's another thing to load it and fire it for them.

I think it is good to have a default ntp.conf to help new users get
started.  I think it is a bad thing to include potentially dangerous
elements in that configuration which could cause grief to a novice NTP
administrator.  If the default configuration provides scope for such
surprises, they will (rightly) blame FreeBSD.

-- 
John Marshall
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090709/70be3dea/attachment.pgp
From kensmith at cse.Buffalo.EDU  Thu Jul  9 03:42:38 2009
From: kensmith at cse.Buffalo.EDU (Ken Smith)
Date: Thu Jul  9 03:42:45 2009
Subject: FreeBSD 8.0-BETA1 Available
In-Reply-To: <4A54FB33.8060705@fgznet.ch>
References: <1246926782.11597.23.camel@bauer.cse.buffalo.edu>
	<4A54FB33.8060705@fgznet.ch>
Message-ID: <1247107223.31816.7.camel@bauer.cse.buffalo.edu>

On Wed, 2009-07-08 at 22:01 +0200, Andreas Tobler wrote:
> I was successful in installing the image, although, a few packages did 
> not install. I did a kern developer package. I guess the packages are 
> missing on the .img?

Correct, no packages with BETA1.  It's probably the documentation
packages it went looking for and couldn't find.  I'll be providing at
least the docs packages with BETA2.  Not sure if I'll start trying to
provide a larger set of packages for the DVD or wait for BETA3 for that
(leaning towards waiting at the moment).

-- 
                                                Ken Smith
- From there to here, from here to      |       kensmith@cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090709/9cb60c7c/attachment.pgp
From jonathan at kc8onw.net  Thu Jul  9 04:43:35 2009
From: jonathan at kc8onw.net (Jonathan)
Date: Thu Jul  9 04:43:44 2009
Subject: ZFS: drive replacement performance
In-Reply-To: <20090708001336.GA95670@martini.nu>
References: <20090707195614.GA24326@martini.nu>	<b269bc570907071354r36015689ha362ba83413efc46@mail.gmail.com>	<20090707222631.GA70750@martini.nu>	<b269bc570907071532ub95af78i6ad3a09e8c6887d7@mail.gmail.com>
	<20090708001336.GA95670@martini.nu>
Message-ID: <4A5541E9.2050801@kc8onw.net>

On 7/7/2009 8:13 PM, Mahlon E. Smith wrote:
> I also tried another export/import cycle, in the random hope that would
> stop the active replace -- no dice.  *However*, on the import, now I see
> this flooding my console (wasn't there previously, strangely):
>
> Jul  7 16:50:15 disobedience root: ZFS: vdev I/O failure, zpool=store path=/dev/da2 offset=262144 size=8192 error=6
> Jul  7 16:50:15 disobedience root: ZFS: vdev I/O failure, zpool=store path=/dev/da2 offset=499988824064 size=8192 error=6

I actually just had this exact issue with a dead drive, controller 
renumbering, and vdev I/O failure.  I eventually shut the system down 
completely, pulled the new drive, checked all the drive connections, 
powered the machine back up without the new drive.  Then I inserted the 
new drive and initiated a scan for it.  Apparently ZFS doesn't realize 
when a resilver is partially done because it resilvered in a matter of 
seconds at this point.  I then did a scrub which found several million 
checksum errors but successfully corrected the pool without any vdev I/O 
failure errors.

I hope this helps,
Jonathan Stewart
From aw1 at stade.co.uk  Thu Jul  9 07:15:44 2009
From: aw1 at stade.co.uk (Adrian Wontroba)
Date: Thu Jul  9 07:15:52 2009
Subject: Help With Custom Disk Layout For New Install
In-Reply-To: <4A53FC1B.5090303@mykitchentable.net>
References: <4A53FC1B.5090303@mykitchentable.net>
Message-ID: <20090708224921.GA81685@steerpike.hanley.stade.co.uk>

On Tue, Jul 07, 2009 at 06:53:31PM -0700, Drew Tomlinson wrote:

>  ... gmirror fails silently (i.e. nothing exists in /dev/mirror). ...

I can't speak for the rest of your post but have you got the following
in /boot/loader.conf?

geom_mirror_load="YES"

-- 
Adrian Wontroba
It is far better to be deceived than to be undeceived by those we love.
From vince at unsane.co.uk  Thu Jul  9 11:05:12 2009
From: vince at unsane.co.uk (Vincent Hoffman)
Date: Thu Jul  9 11:05:20 2009
Subject: 8.0-BETA1 Source Upgrade breaks NTP configuration
In-Reply-To: <20090709021119.GA26896@rwpc12.mby.riverwillow.net.au>
References: <20090709021119.GA26896@rwpc12.mby.riverwillow.net.au>
Message-ID: <4A55CEDF.6010702@unsane.co.uk>

John Marshall wrote:
> Yesterday I source-upgraded a 7.2-RELEASE-p2 test i386 server to
> 8.0-BETA1.  I have just discovered that it broke that server's NTP
> service.
> 
> PROBLEM 1 - Existing /etc/ntp.conf overwritten
> 
> 
> Digging deeper, it looks like it may be due to the fact that this is a
> new supplied file and an entry for /etc/ntp.conf didn't exist in
> /var/db/mergemaster.mtree from the previous (7.2-RELEASE) run.  How
> should this be handled?
you are correct, There was a thread on -CURRENT about this recently see
http://lists.freebsd.org/pipermail/freebsd-current/2009-July/008968.html
 I think there was discussion of a patch to mergemaster.
> 
> PROBLEM 2 - Default ntp.conf uses LOCAL clock
> 

Again much discussed, a new improved version using freebsd.pool.ntp.org
and commenting out the LOCAL option was posted to the freebsd-net list
not long ago by David MAlone, hopefully to be applied soon.

Vince
From hausen at punkt.de  Thu Jul  9 11:25:15 2009
From: hausen at punkt.de (Patrick M. Hausen)
Date: Thu Jul  9 11:25:24 2009
Subject: ZFS - thanks
Message-ID: <20090709112512.GA44158@hugo10.ka.punkt.de>

Hi, all,

I just wanted to say a big big thank you to Kip and all the
developers who made ZFS on FreeBSD real.

And to everyone who provided helpful comments in the
last couple of days.

I had to delete and rebuild my zpool to switch from a
12-disk raidz2 to two 6-disk ones, but yesterday I could
replace the raw devices with glabel devices and practice
replacing a failed disk at the same time. ;-)

So now we have this setup:

	NAME               STATE     READ WRITE CKSUM
	zfs                ONLINE       0     0     0
	  raidz2           ONLINE       0     0     0
	    label/disk100  ONLINE       0     0     0
	    label/disk101  ONLINE       0     0     0
	    label/disk102  ONLINE       0     0     0
	    label/disk103  ONLINE       0     0     0
	    label/disk104  ONLINE       0     0     0
	    label/disk105  ONLINE       0     0     0
	  raidz2           ONLINE       0     0     0
	    label/disk106  ONLINE       0     0     0
	    label/disk107  ONLINE       0     0     0
	    label/disk108  ONLINE       0     0     0
	    label/disk109  ONLINE       0     0     0
	    label/disk110  ONLINE       0     0     0
	    label/disk111  ONLINE       0     0     0

which will get another enclosure with 6 750-GB-disks, soon.

I really like the way I can manage storage from the operating
system without propriatary controller management software or
even rebooting into the BIOS.

Kind regards,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
info@punkt.de       http://www.punkt.de
Gf: J?rgen Egeling      AG Mannheim 108285
From matheus at eternamente.info  Thu Jul  9 12:17:44 2009
From: matheus at eternamente.info (Nenhum_de_Nos)
Date: Thu Jul  9 12:17:52 2009
Subject: ZFS - thanks
In-Reply-To: <20090709112512.GA44158@hugo10.ka.punkt.de>
References: <20090709112512.GA44158@hugo10.ka.punkt.de>
Message-ID: <73a41d4b72d62b0bfe3d0fb7206376a8.squirrel@cygnus.homeunix.com>


On Thu, July 9, 2009 08:25, Patrick M. Hausen wrote:
> Hi, all,
>
> I just wanted to say a big big thank you to Kip and all the
> developers who made ZFS on FreeBSD real.
>
> And to everyone who provided helpful comments in the
> last couple of days.
>
> I had to delete and rebuild my zpool to switch from a
> 12-disk raidz2 to two 6-disk ones, but yesterday I could
> replace the raw devices with glabel devices and practice
> replacing a failed disk at the same time. ;-)
>
> So now we have this setup:
>
> 	NAME               STATE     READ WRITE CKSUM
> 	zfs                ONLINE       0     0     0
> 	  raidz2           ONLINE       0     0     0
> 	    label/disk100  ONLINE       0     0     0
> 	    label/disk101  ONLINE       0     0     0
> 	    label/disk102  ONLINE       0     0     0
> 	    label/disk103  ONLINE       0     0     0
> 	    label/disk104  ONLINE       0     0     0
> 	    label/disk105  ONLINE       0     0     0
> 	  raidz2           ONLINE       0     0     0
> 	    label/disk106  ONLINE       0     0     0
> 	    label/disk107  ONLINE       0     0     0
> 	    label/disk108  ONLINE       0     0     0
> 	    label/disk109  ONLINE       0     0     0
> 	    label/disk110  ONLINE       0     0     0
> 	    label/disk111  ONLINE       0     0     0
>
> which will get another enclosure with 6 750-GB-disks, soon.
>
> I really like the way I can manage storage from the operating
> system without propriatary controller management software or
> even rebooting into the BIOS.
>
> Kind regards,
> Patrick

I've always been curious about this. is said not good to have many disks
in one pool. ok then. but this layout you're using in here will have the
same effect as the twelve disks in only one pool ? (the space here is the
sum of both pools ?)

thanks,

matheus

-- 
We will call you cygnus,
The God of balance you shall be

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

http://en.wikipedia.org/wiki/Posting_style
From dan.naumov at gmail.com  Thu Jul  9 12:25:43 2009
From: dan.naumov at gmail.com (Dan Naumov)
Date: Thu Jul  9 12:26:25 2009
Subject: ZFS - thanks
In-Reply-To: <73a41d4b72d62b0bfe3d0fb7206376a8.squirrel@cygnus.homeunix.com>
References: <20090709112512.GA44158@hugo10.ka.punkt.de>
	<73a41d4b72d62b0bfe3d0fb7206376a8.squirrel@cygnus.homeunix.com>
Message-ID: <cf9b1ee00907090525t7a337775q71aa01e6a3173de5@mail.gmail.com>

On Thu, Jul 9, 2009 at 3:17 PM, Nenhum_de_Nos<matheus@eternamente.info> wrote:
>
> On Thu, July 9, 2009 08:25, Patrick M. Hausen wrote:
>> Hi, all,
>>
>> I just wanted to say a big big thank you to Kip and all the
>> developers who made ZFS on FreeBSD real.
>>
>> And to everyone who provided helpful comments in the
>> last couple of days.
>>
>> I had to delete and rebuild my zpool to switch from a
>> 12-disk raidz2 to two 6-disk ones, but yesterday I could
>> replace the raw devices with glabel devices and practice
>> replacing a failed disk at the same time. ;-)
>>
>> So now we have this setup:
>>
>> ? ? ? NAME ? ? ? ? ? ? ? STATE ? ? READ WRITE CKSUM
>> ? ? ? zfs ? ? ? ? ? ? ? ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>> ? ? ? ? raidz2 ? ? ? ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0
>> ? ? ? ? ? label/disk100 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>> ? ? ? ? ? label/disk101 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>> ? ? ? ? ? label/disk102 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>> ? ? ? ? ? label/disk103 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>> ? ? ? ? ? label/disk104 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>> ? ? ? ? ? label/disk105 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>> ? ? ? ? raidz2 ? ? ? ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0
>> ? ? ? ? ? label/disk106 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>> ? ? ? ? ? label/disk107 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>> ? ? ? ? ? label/disk108 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>> ? ? ? ? ? label/disk109 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>> ? ? ? ? ? label/disk110 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>> ? ? ? ? ? label/disk111 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>
>> which will get another enclosure with 6 750-GB-disks, soon.
>>
>> I really like the way I can manage storage from the operating
>> system without propriatary controller management software or
>> even rebooting into the BIOS.
>>
>> Kind regards,
>> Patrick
>
> I've always been curious about this. is said not good to have many disks
> in one pool. ok then. but this layout you're using in here will have the
> same effect as the twelve disks in only one pool ? (the space here is the
> sum of both pools ?)

Having an enormous pool consisting of dozens of disks is not the
actual problem. Having the pool consist of large (> 9 disks)
raidz/raidz2 "groups" is.

A single pool consising of 5 x 8 disk raidz (40 disks total) is fine.
A single pool consisting of a 40 (or any amount bigger than 9) disk
raidz is not.

- Sincerely,
Dan Naumov
From matheus at eternamente.info  Thu Jul  9 12:30:45 2009
From: matheus at eternamente.info (Nenhum_de_Nos)
Date: Thu Jul  9 12:30:52 2009
Subject: ZFS - thanks
In-Reply-To: <cf9b1ee00907090525t7a337775q71aa01e6a3173de5@mail.gmail.com>
References: <20090709112512.GA44158@hugo10.ka.punkt.de>
	<73a41d4b72d62b0bfe3d0fb7206376a8.squirrel@cygnus.homeunix.com>
	<cf9b1ee00907090525t7a337775q71aa01e6a3173de5@mail.gmail.com>
Message-ID: <84665df87e93a6ccf24d9837cbc53eba.squirrel@cygnus.homeunix.com>


On Thu, July 9, 2009 09:25, Dan Naumov wrote:
> On Thu, Jul 9, 2009 at 3:17 PM, Nenhum_de_Nos<matheus@eternamente.info>
> wrote:
>>
>> On Thu, July 9, 2009 08:25, Patrick M. Hausen wrote:
>>> Hi, all,
>>>
>>> I just wanted to say a big big thank you to Kip and all the
>>> developers who made ZFS on FreeBSD real.
>>>
>>> And to everyone who provided helpful comments in the
>>> last couple of days.
>>>
>>> I had to delete and rebuild my zpool to switch from a
>>> 12-disk raidz2 to two 6-disk ones, but yesterday I could
>>> replace the raw devices with glabel devices and practice
>>> replacing a failed disk at the same time. ;-)
>>>
>>> So now we have this setup:
>>>
>>> ? ? ? NAME ? ? ? ? ? ? ? STATE ? ? READ WRITE CKSUM
>>> ? ? ? zfs ? ? ? ? ? ? ? ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>> ? ? ? ? raidz2 ? ? ? ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>> ? ? ? ? ? label/disk100 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>> ? ? ? ? ? label/disk101 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>> ? ? ? ? ? label/disk102 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>> ? ? ? ? ? label/disk103 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>> ? ? ? ? ? label/disk104 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>> ? ? ? ? ? label/disk105 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>> ? ? ? ? raidz2 ? ? ? ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>> ? ? ? ? ? label/disk106 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>> ? ? ? ? ? label/disk107 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>> ? ? ? ? ? label/disk108 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>> ? ? ? ? ? label/disk109 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>> ? ? ? ? ? label/disk110 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>> ? ? ? ? ? label/disk111 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>>
>>> which will get another enclosure with 6 750-GB-disks, soon.
>>>
>>> I really like the way I can manage storage from the operating
>>> system without propriatary controller management software or
>>> even rebooting into the BIOS.
>>>
>>> Kind regards,
>>> Patrick
>>
>> I've always been curious about this. is said not good to have many disks
>> in one pool. ok then. but this layout you're using in here will have the
>> same effect as the twelve disks in only one pool ? (the space here is
>> the
>> sum of both pools ?)
>
> Having an enormous pool consisting of dozens of disks is not the
> actual problem. Having the pool consist of large (> 9 disks)
> raidz/raidz2 "groups" is.
>
> A single pool consising of 5 x 8 disk raidz (40 disks total) is fine.
> A single pool consisting of a 40 (or any amount bigger than 9) disk
> raidz is not.

thanks. but the final file system in both these cases are the same ? (what
I'll see in df -h).

matheus

-- 
We will call you cygnus,
The God of balance you shall be

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

http://en.wikipedia.org/wiki/Posting_style
From hausen at punkt.de  Thu Jul  9 12:34:39 2009
From: hausen at punkt.de (Patrick M. Hausen)
Date: Thu Jul  9 12:34:45 2009
Subject: ZFS - thanks
In-Reply-To: <73a41d4b72d62b0bfe3d0fb7206376a8.squirrel@cygnus.homeunix.com>
References: <20090709112512.GA44158@hugo10.ka.punkt.de>
	<73a41d4b72d62b0bfe3d0fb7206376a8.squirrel@cygnus.homeunix.com>
Message-ID: <20090709123434.GC46563@hugo10.ka.punkt.de>

Hello,

On Thu, Jul 09, 2009 at 09:17:35AM -0300, Nenhum_de_Nos wrote:

> > So now we have this setup:
> >
> > 	NAME               STATE     READ WRITE CKSUM
> > 	zfs                ONLINE       0     0     0
> > 	  raidz2           ONLINE       0     0     0
> > 	    label/disk100  ONLINE       0     0     0
> > 	    label/disk101  ONLINE       0     0     0
> > 	    label/disk102  ONLINE       0     0     0
> > 	    label/disk103  ONLINE       0     0     0
> > 	    label/disk104  ONLINE       0     0     0
> > 	    label/disk105  ONLINE       0     0     0
> > 	  raidz2           ONLINE       0     0     0
> > 	    label/disk106  ONLINE       0     0     0
> > 	    label/disk107  ONLINE       0     0     0
> > 	    label/disk108  ONLINE       0     0     0
> > 	    label/disk109  ONLINE       0     0     0
> > 	    label/disk110  ONLINE       0     0     0
> > 	    label/disk111  ONLINE       0     0     0
> >
> > which will get another enclosure with 6 750-GB-disks, soon.

> I've always been curious about this. is said not good to have many disks
> in one pool. ok then. but this layout you're using in here will have the
> same effect as the twelve disks in only one pool ? (the space here is the
> sum of both pools ?)

It is not good to have too many disks in one group. What you see
above is one pool with two raidz2 groups.

As far as I understood the documentation after that helpful
comment on this list, this is the recommended configuration.

-------------------------------
http://www.solarisinternals.com/wiki/index.php/ZFS_Best_Practices_Guide

"The recommended number of disks per group is between 3 and 9.
 If you have more disks, use multiple groups."
-------------------------------

The result is, of course, one big pool with lots of storage
space, but the overhead necessary for redundancy is roughly
twice that of my "dangerous" twelve-disk configuration.

So I lost the equivalent of two disks or about 1 TB here.
Fast, reliable, cheap - pick any two ;-)

Kind regards,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
info@punkt.de       http://www.punkt.de
Gf: J?rgen Egeling      AG Mannheim 108285
From dan.naumov at gmail.com  Thu Jul  9 12:39:37 2009
From: dan.naumov at gmail.com (Dan Naumov)
Date: Thu Jul  9 12:39:44 2009
Subject: ZFS - thanks
In-Reply-To: <84665df87e93a6ccf24d9837cbc53eba.squirrel@cygnus.homeunix.com>
References: <20090709112512.GA44158@hugo10.ka.punkt.de>
	<73a41d4b72d62b0bfe3d0fb7206376a8.squirrel@cygnus.homeunix.com>
	<cf9b1ee00907090525t7a337775q71aa01e6a3173de5@mail.gmail.com>
	<84665df87e93a6ccf24d9837cbc53eba.squirrel@cygnus.homeunix.com>
Message-ID: <cf9b1ee00907090539i70bf97eq32fe0aa960e9dc52@mail.gmail.com>

On Thu, Jul 9, 2009 at 3:30 PM, Nenhum_de_Nos<matheus@eternamente.info> wrote:
>
> On Thu, July 9, 2009 09:25, Dan Naumov wrote:
>> On Thu, Jul 9, 2009 at 3:17 PM, Nenhum_de_Nos<matheus@eternamente.info>
>> wrote:
>>>
>>> On Thu, July 9, 2009 08:25, Patrick M. Hausen wrote:
>>>> Hi, all,
>>>>
>>>> I just wanted to say a big big thank you to Kip and all the
>>>> developers who made ZFS on FreeBSD real.
>>>>
>>>> And to everyone who provided helpful comments in the
>>>> last couple of days.
>>>>
>>>> I had to delete and rebuild my zpool to switch from a
>>>> 12-disk raidz2 to two 6-disk ones, but yesterday I could
>>>> replace the raw devices with glabel devices and practice
>>>> replacing a failed disk at the same time. ;-)
>>>>
>>>> So now we have this setup:
>>>>
>>>> ? ? ? NAME ? ? ? ? ? ? ? STATE ? ? READ WRITE CKSUM
>>>> ? ? ? zfs ? ? ? ? ? ? ? ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>>> ? ? ? ? raidz2 ? ? ? ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>>> ? ? ? ? ? label/disk100 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>>> ? ? ? ? ? label/disk101 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>>> ? ? ? ? ? label/disk102 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>>> ? ? ? ? ? label/disk103 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>>> ? ? ? ? ? label/disk104 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>>> ? ? ? ? ? label/disk105 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>>> ? ? ? ? raidz2 ? ? ? ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>>> ? ? ? ? ? label/disk106 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>>> ? ? ? ? ? label/disk107 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>>> ? ? ? ? ? label/disk108 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>>> ? ? ? ? ? label/disk109 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>>> ? ? ? ? ? label/disk110 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>>> ? ? ? ? ? label/disk111 ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
>>>>
>>>> which will get another enclosure with 6 750-GB-disks, soon.
>>>>
>>>> I really like the way I can manage storage from the operating
>>>> system without propriatary controller management software or
>>>> even rebooting into the BIOS.
>>>>
>>>> Kind regards,
>>>> Patrick
>>>
>>> I've always been curious about this. is said not good to have many disks
>>> in one pool. ok then. but this layout you're using in here will have the
>>> same effect as the twelve disks in only one pool ? (the space here is
>>> the
>>> sum of both pools ?)
>>
>> Having an enormous pool consisting of dozens of disks is not the
>> actual problem. Having the pool consist of large (> 9 disks)
>> raidz/raidz2 "groups" is.
>>
>> A single pool consising of 5 x 8 disk raidz (40 disks total) is fine.
>> A single pool consisting of a 40 (or any amount bigger than 9) disk
>> raidz is not.
>
> thanks. but the final file system in both these cases are the same ? (what
> I'll see in df -h).

No.

A single pool consisting of 5 x 8 disk raidz will have 40 disks total,
35 disks worth of space
A single pool consisting of 5 x 8 disk raidz2 will have 40 disks
total, 30 disks worth of space

A single 40 disk raidz (DO NOT DO THIS) will have 40 disks total, 39
disks worth of space and will definately explode on you sooner rather
than later (probably on the first import, export or scrub).

- Sincerely,
Dan Naumov
From dudu at dudu.ro  Thu Jul  9 13:13:46 2009
From: dudu at dudu.ro (Vlad Galu)
Date: Thu Jul  9 13:13:54 2009
Subject: pw groupadd/useradd fail when the nscd cache is used for name/group
	resolution
Message-ID: <ad79ad6b0907090613t78cf8540n5fcd3934cadde526@mail.gmail.com>

I've stumbled upon this while installing postgres. In
/etc/nsswitch.conf I had "group: cache files compat" and "passwd:
cache files compat". Once I commented them out things started working
again. Before the change, this is how it looked like:

-- cut here --
[root@vgalu /usr/ports/databases/postgresql84-server]# pw group add pgsql -g 70
pw: group disappeared during update
[root@vgalu /usr/ports/databases/postgresql84-server]# pw group add pgsql -g 70
pw: group 'pgsql' already exists
[root@vgalu /usr/ports/databases/postgresql84-server]#
-- and here --

Shouldn't 'files' be used upon a cache miss? If this is a PEBKAC,
sorry for the noise.
From tonix at interazioni.it  Thu Jul  9 13:21:55 2009
From: tonix at interazioni.it (Tonix (Antonio Nati))
Date: Thu Jul  9 13:22:02 2009
Subject: ZFS - thanks
In-Reply-To: <20090709123434.GC46563@hugo10.ka.punkt.de>
References: <20090709112512.GA44158@hugo10.ka.punkt.de>	<73a41d4b72d62b0bfe3d0fb7206376a8.squirrel@cygnus.homeunix.com>
	<20090709123434.GC46563@hugo10.ka.punkt.de>
Message-ID: <4A55EEEC.3030007@interazioni.it>

Patrick M. Hausen ha scritto:
> Hello,
>
> On Thu, Jul 09, 2009 at 09:17:35AM -0300, Nenhum_de_Nos wrote:
>
>   
>>> So now we have this setup:
>>>
>>> 	NAME               STATE     READ WRITE CKSUM
>>> 	zfs                ONLINE       0     0     0
>>> 	  raidz2           ONLINE       0     0     0
>>> 	    label/disk100  ONLINE       0     0     0
>>> 	    label/disk101  ONLINE       0     0     0
>>> 	    label/disk102  ONLINE       0     0     0
>>> 	    label/disk103  ONLINE       0     0     0
>>> 	    label/disk104  ONLINE       0     0     0
>>> 	    label/disk105  ONLINE       0     0     0
>>> 	  raidz2           ONLINE       0     0     0
>>> 	    label/disk106  ONLINE       0     0     0
>>> 	    label/disk107  ONLINE       0     0     0
>>> 	    label/disk108  ONLINE       0     0     0
>>> 	    label/disk109  ONLINE       0     0     0
>>> 	    label/disk110  ONLINE       0     0     0
>>> 	    label/disk111  ONLINE       0     0     0
>>>
>>> which will get another enclosure with 6 750-GB-disks, soon.
>>>       
>
>   
>> I've always been curious about this. is said not good to have many disks
>> in one pool. ok then. but this layout you're using in here will have the
>> same effect as the twelve disks in only one pool ? (the space here is the
>> sum of both pools ?)
>>     
>
> It is not good to have too many disks in one group. What you see
> above is one pool with two raidz2 groups.
>
> As far as I understood the documentation after that helpful
> comment on this list, this is the recommended configuration.
>
> -------------------------------
> http://www.solarisinternals.com/wiki/index.php/ZFS_Best_Practices_Guide
>
> "The recommended number of disks per group is between 3 and 9.
>  If you have more disks, use multiple groups."
> -------------------------------
>
> The result is, of course, one big pool with lots of storage
> space, but the overhead necessary for redundancy is roughly
> twice that of my "dangerous" twelve-disk configuration.
>
> So I lost the equivalent of two disks or about 1 TB here.
> Fast, reliable, cheap - pick any two ;-)
>
> Kind regards,
> Patrick
>   

I see a lot of people advicing to use ZFS RAID instead of HW RAID.
I'm going to use HP duplicated iSCSI subsystems, which have autonomous 
RAID, so I'm confused about this advice.
Following the ZFS RAID stream, should I keep each disk alone in iSCSI 
and let the ZFS make the RAID job?
Should not HW RAID to be (a lot) more efficient?
Which would be the wrong side of using HW RAID with ZFS?

Thanks,

Tonino




-- 
------------------------------------------------------------
        Inter@zioni            Interazioni di Antonio Nati 
   http://www.interazioni.it      tonix@interazioni.it           
------------------------------------------------------------

From hausen at punkt.de  Thu Jul  9 13:43:04 2009
From: hausen at punkt.de (Patrick M. Hausen)
Date: Thu Jul  9 13:43:11 2009
Subject: ZFS - thanks
In-Reply-To: <4A55EEEC.3030007@interazioni.it>
References: <20090709112512.GA44158@hugo10.ka.punkt.de>
	<73a41d4b72d62b0bfe3d0fb7206376a8.squirrel@cygnus.homeunix.com>
	<20090709123434.GC46563@hugo10.ka.punkt.de>
	<4A55EEEC.3030007@interazioni.it>
Message-ID: <20090709134302.GA50485@hugo10.ka.punkt.de>

Hello,

On Thu, Jul 09, 2009 at 03:21:48PM +0200, Tonix (Antonio Nati) wrote:

> I see a lot of people advicing to use ZFS RAID instead of HW RAID.
> I'm going to use HP duplicated iSCSI subsystems, which have autonomous 
> RAID, so I'm confused about this advice.
> Following the ZFS RAID stream, should I keep each disk alone in iSCSI and 
> let the ZFS make the RAID job?
> Should not HW RAID to be (a lot) more efficient?

You cannot escape the poor write performance of RAID 5 and
comparable setups with or without hardware. No matter how
much you cache, one time a block must be written to disk.

And for RAID 1 or 1+0 we found the impact on modern CPUs
negligible.

So we switched to GEOM for mirroring a long time ago for
one simple reason: hardware replacement.

With a "hardware RAID" you need the precise brand and model
of the controller (worst case) to read a disk with valuable
data on it in case of a complete machine failure and replacement.
What, if that's not avaliable any more?

With software you just need an arbitrary machine with the
matching HDD interface (P-ATA, S-ATA, SCSI, ...)

This is my first attempt at software RAID-other-than-1,
but I'm really pleased with the results so far.

The system is a Fujitsu (former Fujitsu Siemens) SX 40
JBOD with a SAS host interface and SAS or S-ATA disks.
You can daisy chain 3 of these boxes with twelve disks
each to one server.
The host adapter in my server  doesn't have any RAID functions.
LSI something, easily replaced.

Reasonably priced, nice, scalable solution for our needs.
It's a datastore, so it doesn't do anything but backup
and restore. I would not use ZFS for something that needs
to be "up" 24x7 just yet. We had a couple of crashes before
we changed some memory parameters.

Kind regards,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
info@punkt.de       http://www.punkt.de
Gf: J?rgen Egeling      AG Mannheim 108285
From steve at ibctech.ca  Thu Jul  9 13:47:15 2009
From: steve at ibctech.ca (Steve Bertrand)
Date: Thu Jul  9 13:47:22 2009
Subject: ZFS - thanks
In-Reply-To: <20090709134302.GA50485@hugo10.ka.punkt.de>
References: <20090709112512.GA44158@hugo10.ka.punkt.de>	<73a41d4b72d62b0bfe3d0fb7206376a8.squirrel@cygnus.homeunix.com>	<20090709123434.GC46563@hugo10.ka.punkt.de>	<4A55EEEC.3030007@interazioni.it>
	<20090709134302.GA50485@hugo10.ka.punkt.de>
Message-ID: <4A55F4DC.5010504@ibctech.ca>

Patrick M. Hausen wrote:

> So we switched to GEOM for mirroring a long time ago for
> one simple reason: hardware replacement.

Amen.

Steve
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3233 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090709/b5e95fa3/smime.bin
From avg at icyb.net.ua  Thu Jul  9 14:06:39 2009
From: avg at icyb.net.ua (Andriy Gapon)
Date: Thu Jul  9 14:06:49 2009
Subject: ZFS: zpool scrub lockup
In-Reply-To: <1247085058.6197.18.camel@bugstore>
References: <1247085058.6197.18.camel@bugstore>
Message-ID: <4A55F96B.6070303@icyb.net.ua>

on 08/07/2009 23:30 Thomas Ronner said the following:
> Hello,
> 
> I don't know whether this is the right list; maybe freebsd-fs is more
> appropriate. So please redirect me there if this isn't the right place.
> 
> My system (i386, Athlon XP) locks hard when scrubbing a certain pool. It
> has been doing this for at least a couple of months now. For this reason
> I upgraded to 7.2-STABLE recently as this had the latest ZFS bits, but
> this doesn't help. It even makes the problem worse: in previous versions
> I just hit the reset button and forgot about it, but now it "remembers"
> that it was scrubbing (I presume) and tries to resume at the exact same
> place, locking up again. This means I haven't been able to mount these
> ZFS volumes successfully: the moment I do a /etc/rc.d/zfs start from
> single user mode (I have my /, /var and /usr on UFS) it locks up in a
> couple of seconds. And by locks up I really mean locks up. No panic,
> nothing. Pressing the reset button on the chassis is the only way to
> reboot. 

You can try adding SW_WATCHDOG option to your kernel which might help catching the
lockup. Things like INVARIANTS and WITNESS might help th debugging too.
Serial console for remote debugging would be very useful too.

-- 
Andriy Gapon
From thomas at ronner.org  Thu Jul  9 15:35:13 2009
From: thomas at ronner.org (Thomas Ronner)
Date: Thu Jul  9 15:35:22 2009
Subject: ZFS: zpool scrub lockup
In-Reply-To: <4A55F96B.6070303@icyb.net.ua>
References: <1247085058.6197.18.camel@bugstore> <4A55F96B.6070303@icyb.net.ua>
Message-ID: <4A560E2F.1050906@ronner.org>

Hi Andriy,

Andriy Gapon wrote:
> on 08/07/2009 23:30 Thomas Ronner said the following:
>> Hello,
>>
>> I don't know whether this is the right list; maybe freebsd-fs is more
>> appropriate. So please redirect me there if this isn't the right place.
>>
>> My system (i386, Athlon XP) locks hard when scrubbing a certain pool. It
>> has been doing this for at least a couple of months now. For this reason
>> I upgraded to 7.2-STABLE recently as this had the latest ZFS bits, but
>> this doesn't help. It even makes the problem worse: in previous versions
>> I just hit the reset button and forgot about it, but now it "remembers"
>> that it was scrubbing (I presume) and tries to resume at the exact same
>> place, locking up again. This means I haven't been able to mount these
>> ZFS volumes successfully: the moment I do a /etc/rc.d/zfs start from
>> single user mode (I have my /, /var and /usr on UFS) it locks up in a
>> couple of seconds. And by locks up I really mean locks up. No panic,
>> nothing. Pressing the reset button on the chassis is the only way to
>> reboot. 
> 
> You can try adding SW_WATCHDOG option to your kernel which might help catching the
> lockup. Things like INVARIANTS and WITNESS might help th debugging too.
> Serial console for remote debugging would be very useful too.
> 

I'll definitely try those and report back on this list. Thanks for your 
answer!


Regards, Thomas
From thomas at ronner.org  Thu Jul  9 17:21:03 2009
From: thomas at ronner.org (Thomas Ronner)
Date: Thu Jul  9 17:21:13 2009
Subject: ZFS: zpool scrub lockup
In-Reply-To: <4A560E2F.1050906@ronner.org>
References: <1247085058.6197.18.camel@bugstore> <4A55F96B.6070303@icyb.net.ua>
	<4A560E2F.1050906@ronner.org>
Message-ID: <4A5626FC.5000306@ronner.org>

Thomas Ronner wrote:
> Hi Andriy,
> 
> Andriy Gapon wrote:
>> on 08/07/2009 23:30 Thomas Ronner said the following:
>>> Hello,
>>>
>>> I don't know whether this is the right list; maybe freebsd-fs is more
>>> appropriate. So please redirect me there if this isn't the right place.
>>>
>>> My system (i386, Athlon XP) locks hard when scrubbing a certain pool. It
>>> has been doing this for at least a couple of months now. For this reason
>>> I upgraded to 7.2-STABLE recently as this had the latest ZFS bits, but
>>> this doesn't help. It even makes the problem worse: in previous versions
>>> I just hit the reset button and forgot about it, but now it "remembers"
>>> that it was scrubbing (I presume) and tries to resume at the exact same
>>> place, locking up again. This means I haven't been able to mount these
>>> ZFS volumes successfully: the moment I do a /etc/rc.d/zfs start from
>>> single user mode (I have my /, /var and /usr on UFS) it locks up in a
>>> couple of seconds. And by locks up I really mean locks up. No panic,
>>> nothing. Pressing the reset button on the chassis is the only way to
>>> reboot. 
>>
>> You can try adding SW_WATCHDOG option to your kernel which might help 
>> catching the
>> lockup. Things like INVARIANTS and WITNESS might help th debugging too.
>> Serial console for remote debugging would be very useful too.
>>
> 
> I'll definitely try those and report back on this list. Thanks for your 
> answer!

I put the following in my kernel config:

# debugging
options         KDB
options         DDB
options         GDB
options         BREAK_TO_DEBUGGER
options         INVARIANTS
options         INVARIANT_SUPPORT
options         WITNESS
options         WITNESS_KDB
options         DEBUG_VFS_LOCKS
options         DIAGNOSTIC
options         SW_WATCHDOG

When I send a BREAK from my serial console it enters the debugger, so 
that works. But when I start ZFS (/etc/rc.d/zfs start) it freezes again 
and BREAK doesn't enter the debugger. I'll try playing with the watchdog 
now, but I doubt this will help. Any clues?


Thanks,
Thomas
From avg at icyb.net.ua  Thu Jul  9 17:35:10 2009
From: avg at icyb.net.ua (Andriy Gapon)
Date: Thu Jul  9 17:35:17 2009
Subject: ZFS: zpool scrub lockup
In-Reply-To: <4A5626FC.5000306@ronner.org>
References: <1247085058.6197.18.camel@bugstore> <4A55F96B.6070303@icyb.net.ua>
	<4A560E2F.1050906@ronner.org> <4A5626FC.5000306@ronner.org>
Message-ID: <4A562A4A.2000201@icyb.net.ua>

on 09/07/2009 20:21 Thomas Ronner said the following:
> I put the following in my kernel config:
> 
> # debugging
> options         KDB
> options         DDB
> options         GDB
> options         BREAK_TO_DEBUGGER
> options         INVARIANTS
> options         INVARIANT_SUPPORT
> options         WITNESS
> options         WITNESS_KDB
> options         DEBUG_VFS_LOCKS
> options         DIAGNOSTIC
> options         SW_WATCHDOG
> 
> When I send a BREAK from my serial console it enters the debugger, so
> that works. But when I start ZFS (/etc/rc.d/zfs start) it freezes again
> and BREAK doesn't enter the debugger. I'll try playing with the watchdog
> now, but I doubt this will help. Any clues?
> 

For watchdog to fire it first needs to be enabled, e.g. by starting watchdogd.
Try to run /etc/rd.d/watchdogd onestart before zfs start and then wait for about
16 seconds (default timeout).
If that doesn't help, then it seems that the only option would be debugging via
serial console. Or manually generating NMI, if your system has an NMI
button/switch/jumper.

-- 
Andriy Gapon
From thomas at ronner.org  Thu Jul  9 18:25:45 2009
From: thomas at ronner.org (Thomas Ronner)
Date: Thu Jul  9 18:25:52 2009
Subject: ZFS: zpool scrub lockup
In-Reply-To: <4A562A4A.2000201@icyb.net.ua>
References: <1247085058.6197.18.camel@bugstore>
	<4A55F96B.6070303@icyb.net.ua>	<4A560E2F.1050906@ronner.org>
	<4A5626FC.5000306@ronner.org> <4A562A4A.2000201@icyb.net.ua>
Message-ID: <4A563627.7040407@ronner.org>

Andriy Gapon wrote:

> For watchdog to fire it first needs to be enabled, e.g. by starting watchdogd.
> Try to run /etc/rd.d/watchdogd onestart before zfs start and then wait for about
> 16 seconds (default timeout).

I tried this. When only running 'watchdog' (without starting the daemon) 
it enters the debugger in 16 seconds. The only way to continue is 
issuing the 'watchdog' debugger command (I presume this disables the 
watchdog?), followed by 'c'.

But when re-enabling the watchdog by running /etc/rc.d/watchdogd start 
(I already added watchdogd to rc.conf)



> If that doesn't help, then it seems that the only option would be debugging via
> serial console. Or manually generating NMI, if your system has an NMI
> button/switch/jumper.

No, I don't have a manual NMI thingy.

Is this: 
http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-online-gdb.html 
(10.6 On-Line Kernel Debugging Using Remote GDB) the debugging via 
serial console you're referring to?



Thanks,
Thomas
From andreast-list at fgznet.ch  Thu Jul  9 18:52:33 2009
From: andreast-list at fgznet.ch (Andreas Tobler)
Date: Thu Jul  9 18:52:46 2009
Subject: FreeBSD 8.0-BETA1 Available
In-Reply-To: <1247107223.31816.7.camel@bauer.cse.buffalo.edu>
References: <1246926782.11597.23.camel@bauer.cse.buffalo.edu>	
	<4A54FB33.8060705@fgznet.ch>
	<1247107223.31816.7.camel@bauer.cse.buffalo.edu>
Message-ID: <4A563C65.20402@fgznet.ch>

Ken Smith wrote:
> On Wed, 2009-07-08 at 22:01 +0200, Andreas Tobler wrote:
>> I was successful in installing the image, although, a few packages did 
>> not install. I did a kern developer package. I guess the packages are 
>> missing on the .img?
> 
> Correct, no packages with BETA1.  It's probably the documentation
> packages it went looking for and couldn't find.  I'll be providing at
> least the docs packages with BETA2.  Not sure if I'll start trying to
> provide a larger set of packages for the DVD or wait for BETA3 for that
> (leaning towards waiting at the moment).

Ok, that means no doc/dict/docproj/man/ports/src (and the ones I didn't 
choose) in the BETA1?

I did the install again with a real stick and everything went fine 
besides not finding the above packages.

Thanks,
Andreas
From mi+thun at aldan.algebra.com  Thu Jul  9 19:18:27 2009
From: mi+thun at aldan.algebra.com (Mikhail T.)
Date: Thu Jul  9 19:18:34 2009
Subject: process stuck in "umtxn"
Message-ID: <4A563FF2.3010305@aldan.algebra.com>

Hello!

I noticed, that my build of KDE4 ports got suspiciously quiet...
Pressing Ctrl-T shows:

    load: 0.01  cmd: automoc4 78507 [umtxn] 0.00u 0.00s 0% 3552k

According to gdb, the process' stack is:

    #0  0x0000000800d9620a in __error () from /lib/libthr.so.3
    #1  0x0000000800d95f0c in __error () from /lib/libthr.so.3
    #2  0x0000000800d911eb in pthread_mutex_getyieldloops_np () from
    /lib/libthr.so.3
    #3  0x0000000800f0941b in _malloc_postfork () from /lib/libc.so.7
    #4  0x0000000800d93c60 in fork () from /lib/libthr.so.3
    #5  0x0000000800778e4a in QProcessPrivate::startProcess () from
    /opt/lib/qt4/libQtCore.so.4
    #6  0x000000080073f2c6 in QProcess::start () from
    /opt/lib/qt4/libQtCore.so.4
    ....

My system is 7.2-PRERELEASE/amd64 from April 9th. Please, advise.
Thanks! Yours,

    -mi

From mike at sentex.net  Thu Jul  9 19:25:10 2009
From: mike at sentex.net (Mike Tancsa)
Date: Thu Jul  9 19:25:25 2009
Subject: pppoe on a VLAN interface issues (RELENG_7)
Message-ID: <200907091922.n69JMYvS067578@lava.sentex.ca>

I wanted to share a DSL modem that is in bridge mode between two 
FreeBSD boxes that make use of many VLANs on a pair of em 
interfaces.  In other words, I cant dedicate a physical interface to 
just using the DSL.  Normally, when creating vlans, I like to create them as so

/sbin/ifconfig em1.172 create 192.168.1.3/24


em1.172: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
         options=3<RXCSUM,TXCSUM>
         ether 00:30:48:d2:d6:11
         inet 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255
         media: Ethernet autoselect (1000baseTX <full-duplex>)
         status: active
         vlan: 172 parent interface: em1

However, if I try and bring up pppoe using em1.10 as the PPPoE 
device, it does not work.


Jul  9 14:34:17 fw02 ppp[1484]: tun0: Phase: deflink: closed -> opening
Jul  9 14:34:17 fw02 kernel: ng_ether_attach: can't name node em1.10
Jul  9 14:34:17 fw02 kernel: ng_ether_attach: can't name node em1.172
Jul  9 14:34:17 fw02 kernel: ng_ether_attach: can't name node em1.24
Jul  9 14:34:17 fw02 kernel: WARNING: attempt to 
net_add_domain(netgraph) after domainfinalize()
Jul  9 14:34:17 fw02 kernel: Jul  9 14:34:17 fw02 kernel: 
ng_ether_attach: can't name node em1.10
Jul  9 14:34:17 fw02 kernel: Jul  9 14:34:17 fw02 kernel: 
ng_ether_attach: can't name node em1.172
Jul  9 14:34:17 fw02 kernel: Jul  9 14:34:17 fw02 kernel: 
ng_ether_attach: can't name node em1.24
Jul  9 14:34:17 fw02 ppp[1484]: tun0: Warning: em1.172: Cannot send a 
netgraph message: Invalid argument
Jul  9 14:34:17 fw02 ppp[1484]: tun0: Chat: Failed to open device
Jul  9 14:34:17 fw02 ppp[1484]: tun0: Phase: deflink: Enter pause 
(30) for redialing.
Jul  9 14:34:47 fw02 ppp[1484]: tun0: Chat: deflink: Redial timer expired.
Jul  9 14:34:47 fw02 ppp[1484]: tun0: Warning: em1.172: Cannot send a 
netgraph message: Invalid argument
Jul  9 14:34:47 fw02 ppp[1484]: tun0: Warning: deflink: PPPoE: unknown host
Jul  9 14:34:47 fw02 ppp[1484]: tun0: Warning: deflink: PPPoE: unknown host
Jul  9 14:34:47 fw02 ppp[1484]: tun0: Warning: deflink: Device 
(PPPoE:em1.172) must begin with a '/', a '!' or contain at least one ':'
Jul  9 14:34:47 fw02 ppp[1484]: tun0: Chat: Failed to open device
Jul  9 14:34:47 fw02 ppp[1484]: tun0: Phase: deflink: Enter pause 
(30) for redialing.
Jul  9 14:34:50 fw02 ppp[1484]: tun0: Phase: Signal 15, terminate.


BUT, if I make the vlan device the "old way"

/sbin/ifconfig vlan172 create 192.168.1.3/24 vlandev em1 vlan 172

it works


It still complains about the other 2 interfaces, but it does not seem 
to interfere with the PPPoE connection

Jul  9 14:48:15 macs-fw02 kernel: ng_ether_attach: can't name node em1.10
Jul  9 14:48:15 macs-fw02 kernel: ng_ether_attach: can't name node em1.24
Jul  9 14:48:15 macs-fw02 kernel: Jul  9 14:48:15 macs-fw02 kernel: 
ng_ether_attach: can't name node em1.10
Jul  9 14:48:15 macs-fw02 kernel: Jul  9 14:48:15 macs-fw02 kernel: 
ng_ether_attach: can't name node em1.24
Jul  9 14:48:16 macs-fw02 kernel: WARNING: attempt to 
net_add_domain(netgraph) after domainfinalize()

Is there some reason this does not work ?

         ---Mike



--------------------------------------------------------------------
Mike Tancsa,                                      tel +1 519 651 3400
Sentex Communications,                            mike@sentex.net
Providing Internet since 1994                    www.sentex.net
Cambridge, Ontario Canada                         www.sentex.net/mike

From dnelson at allantgroup.com  Thu Jul  9 20:45:52 2009
From: dnelson at allantgroup.com (Dan Nelson)
Date: Thu Jul  9 20:46:04 2009
Subject: process stuck in "umtxn"
In-Reply-To: <4A563FF2.3010305@aldan.algebra.com>
References: <4A563FF2.3010305@aldan.algebra.com>
Message-ID: <20090709200148.GD63413@dan.emsphone.com>

In the last episode (Jul 09), Mikhail T. said:
> I noticed, that my build of KDE4 ports got suspiciously quiet...  Pressing
> Ctrl-T shows:
> 
>     load: 0.01  cmd: automoc4 78507 [umtxn] 0.00u 0.00s 0% 3552k
> 
> According to gdb, the process' stack is:
> 
>     #0  0x0000000800d9620a in __error () from /lib/libthr.so.3
>     #1  0x0000000800d95f0c in __error () from /lib/libthr.so.3
>     #2  0x0000000800d911eb in pthread_mutex_getyieldloops_np () from /lib/libthr.so.3
>     #3  0x0000000800f0941b in _malloc_postfork () from /lib/libc.so.7
>     #4  0x0000000800d93c60 in fork () from /lib/libthr.so.3
>     #5  0x0000000800778e4a in QProcessPrivate::startProcess () from /opt/lib/qt4/libQtCore.so.4
>     #6  0x000000080073f2c6 in QProcess::start () from /opt/lib/qt4/libQtCore.so.4
>     ....
> 
> My system is 7.2-PRERELEASE/amd64 from April 9th. Please, advise.
> Thanks! Yours,

That could be due to the following bug, fixed after 7.2 was released. 
Appliying the patch and rebuilding libc should be all you need to fix it:

http://security.freebsd.org/advisories/FreeBSD-EN-09:04.fork.asc

-- 
	Dan Nelson
	dnelson@allantgroup.com
From andrew at modulus.org  Thu Jul  9 23:13:36 2009
From: andrew at modulus.org (Andrew Snow)
Date: Thu Jul  9 23:13:44 2009
Subject: ZFS - thanks
In-Reply-To: <20090709134302.GA50485@hugo10.ka.punkt.de>
References: <20090709112512.GA44158@hugo10.ka.punkt.de>	<73a41d4b72d62b0bfe3d0fb7206376a8.squirrel@cygnus.homeunix.com>	<20090709123434.GC46563@hugo10.ka.punkt.de>	<4A55EEEC.3030007@interazioni.it>
	<20090709134302.GA50485@hugo10.ka.punkt.de>
Message-ID: <4A567919.8000704@modulus.org>

Patrick M. Hausen wrote:
> You cannot escape the poor write performance of RAID 5 and
> comparable setups with or without hardware. No matter how
> much you cache, one time a block must be written to disk.

ZFS RAIDZ works differently:  It is based on variable-sized blocks 
written to the disks based on incoming data stream, grouped into 
transactions.

This makes it very efficient for clustering multi-threaded random I/O 
writes together into large physical disk writes.

(The downside is it has to read the entire "stripe" even if you are only 
reading one byte, in order to calculate and verify the checksum.)


- Andrew
From oliver.pntr at gmail.com  Fri Jul 10 00:55:31 2009
From: oliver.pntr at gmail.com (Oliver Pinter)
Date: Fri Jul 10 00:55:38 2009
Subject: smbfs panic when lost connection or unmount --force
Message-ID: <6101e8c40907091755n5aefe289r6eec14cf7f4287dc@mail.gmail.com>

Hi all!

It is a kernel panic, when force unmount the smbfs volume or lost the
connection with the samba server.

--
Thes OS is:


kern.ostype: FreeBSD
kern.osrelease: 7.2-STABLE
kern.osrevision: 199506
kern.version: FreeBSD 7.2-STABLE #4: Sat Jun 27 21:44:32 CEST 2009
    root@oliverp:/usr/obj/usr/src/sys/stable
kern.osreldate: 702103

--
make.conf:


CPUTYPE?=core2
CFLAGS= -O2 -fno-strict-aliasing -pipe
MODULES_OVERRIDE=smbfs libiconv libmchain zfs opensolaris drm cd9660
cd9660_iconv

--
panic message:

Jul 10 01:58:39 oliverp syslogd: kernel boot file is /boot/kernel/kernel
Jul 10 01:58:39 oliverp kernel: kernel trap 12 with interrupts disabled
Jul 10 01:58:39 oliverp kernel:
Jul 10 01:58:39 oliverp kernel:
Jul 10 01:58:39 oliverp kernel: Fatal trap 12: page fault while in kernel mode
Jul 10 01:58:39 oliverp kernel: cpuid = 2; apic id = 02
Jul 10 01:58:39 oliverp kernel: fault virtual address	= 0x30
Jul 10 01:58:39 oliverp kernel: fault code		= supervisor read data,
page not present
Jul 10 01:58:39 oliverp kernel: instruction pointer	= 0x8:0xffffffff80327fd0
Jul 10 01:58:39 oliverp kernel: stack pointer	        = 0x10:0xffffff8078360940
Jul 10 01:58:39 oliverp kernel: frame pointer	        = 0x10:0xffffff0004c31390
Jul 10 01:58:39 oliverp kernel: code segment		= base 0x0, limit
0xfffff, type 0x1b
Jul 10 01:58:39 oliverp kernel: = DPL 0, pres 1, long 1, def32 0, gran 1
Jul 10 01:58:39 oliverp kernel: processor eflags	= resume, IOPL = 0
Jul 10 01:58:39 oliverp kernel: current process		= 60406 (smbiod0)
Jul 10 01:58:39 oliverp kernel: trap number		= 12
Jul 10 01:58:39 oliverp kernel: panic: page fault
Jul 10 01:58:39 oliverp kernel: cpuid = 2
Jul 10 01:58:39 oliverp kernel: Uptime: 6h51m16s
Jul 10 01:58:39 oliverp kernel: Physical memory: 4087 MB
Jul 10 01:58:39 oliverp kernel: Dumping 2448 MB:Copyright (c)
1992-2009 The FreeBSD Project.
From attilio at freebsd.org  Fri Jul 10 00:59:21 2009
From: attilio at freebsd.org (Attilio Rao)
Date: Fri Jul 10 00:59:28 2009
Subject: smbfs panic when lost connection or unmount --force
In-Reply-To: <6101e8c40907091755n5aefe289r6eec14cf7f4287dc@mail.gmail.com>
References: <6101e8c40907091755n5aefe289r6eec14cf7f4287dc@mail.gmail.com>
Message-ID: <3bbf2fe10907091759g1f1f9502tb498382c5f3b48d6@mail.gmail.com>

2009/7/10 Oliver Pinter <oliver.pntr@gmail.com>:
> Hi all!
>
> It is a kernel panic, when force unmount the smbfs volume or lost the
> connection with the samba server.
>
> --
> Thes OS is:
>
>
> kern.ostype: FreeBSD
> kern.osrelease: 7.2-STABLE
> kern.osrevision: 199506
> kern.version: FreeBSD 7.2-STABLE #4: Sat Jun 27 21:44:32 CEST 2009
>    root@oliverp:/usr/obj/usr/src/sys/stable
> kern.osreldate: 702103
>
> --
> make.conf:
>
>
> CPUTYPE?=core2
> CFLAGS= -O2 -fno-strict-aliasing -pipe
> MODULES_OVERRIDE=smbfs libiconv libmchain zfs opensolaris drm cd9660
> cd9660_iconv
>
> --
> panic message:
>
> Jul 10 01:58:39 oliverp syslogd: kernel boot file is /boot/kernel/kernel
> Jul 10 01:58:39 oliverp kernel: kernel trap 12 with interrupts disabled
> Jul 10 01:58:39 oliverp kernel:
> Jul 10 01:58:39 oliverp kernel:
> Jul 10 01:58:39 oliverp kernel: Fatal trap 12: page fault while in kernel mode
> Jul 10 01:58:39 oliverp kernel: cpuid = 2; apic id = 02
> Jul 10 01:58:39 oliverp kernel: fault virtual address   = 0x30
> Jul 10 01:58:39 oliverp kernel: fault code              = supervisor read data,
> page not present
> Jul 10 01:58:39 oliverp kernel: instruction pointer     = 0x8:0xffffffff80327fd0
> Jul 10 01:58:39 oliverp kernel: stack pointer           = 0x10:0xffffff8078360940
> Jul 10 01:58:39 oliverp kernel: frame pointer           = 0x10:0xffffff0004c31390
> Jul 10 01:58:39 oliverp kernel: code segment            = base 0x0, limit
> 0xfffff, type 0x1b
> Jul 10 01:58:39 oliverp kernel: = DPL 0, pres 1, long 1, def32 0, gran 1
> Jul 10 01:58:39 oliverp kernel: processor eflags        = resume, IOPL = 0
> Jul 10 01:58:39 oliverp kernel: current process         = 60406 (smbiod0)
> Jul 10 01:58:39 oliverp kernel: trap number             = 12
> Jul 10 01:58:39 oliverp kernel: panic: page fault
> Jul 10 01:58:39 oliverp kernel: cpuid = 2
> Jul 10 01:58:39 oliverp kernel: Uptime: 6h51m16s
> Jul 10 01:58:39 oliverp kernel: Physical memory: 4087 MB
> Jul 10 01:58:39 oliverp kernel: Dumping 2448 MB:Copyright (c)
> 1992-2009 The FreeBSD Project.

Can you at least produce a backtrace for that?

Thanks,
Attilio


-- 
Peace can only be achieved by understanding - A. Einstein
From invitations at boxbe.com  Fri Jul 10 03:01:29 2009
From: invitations at boxbe.com (ahmad syarifudin)
Date: Fri Jul 10 03:01:38 2009
Subject: ahmad syarifudin added you as a friend on Boxbe
Message-ID: <1389727859.11369011.1247192955785.JavaMail.prod@app002.boxbe.com>

Skipped content of type multipart/related
From vm at vm.net.ua  Fri Jul 10 07:35:42 2009
From: vm at vm.net.ua (=?UTF-8?B?0JLQuNGC0LDQu9C40Lkg0JzQvtC40YHQtdC10LI=?=)
Date: Fri Jul 10 07:35:50 2009
Subject: pppoe on a VLAN interface issues (RELENG_7)
In-Reply-To: <200907091922.n69JMYvS067578@lava.sentex.ca>
References: <200907091922.n69JMYvS067578@lava.sentex.ca>
Message-ID: <d8e2594b0907100028w51d037dcs2d135d2fb19be8b8@mail.gmail.com>

2009/7/9 Mike Tancsa <mike@sentex.net>

Jul  9 14:34:17 fw02 kernel: ng_ether_attach: can't name node em1.10
> Jul  9 14:34:17 fw02 kernel: ng_ether_attach: can't name node em1.172
> Jul  9 14:34:17 fw02 kernel: ng_ether_attach: can't name node em1.24
>
> Is there some reason this does not work ?
>

reason - interfaces names with "." :)

-- 
WBR, ??????? ???????, vm@vm.net.ua
Nick-hdl: VM347-RIPE, VM265-UANIC
ICQ# 111222168
From vm at vm.net.ua  Fri Jul 10 07:48:15 2009
From: vm at vm.net.ua (=?UTF-8?B?0JLQuNGC0LDQu9C40Lkg0JzQvtC40YHQtdC10LI=?=)
Date: Fri Jul 10 07:48:22 2009
Subject: pppoe on a VLAN interface issues (RELENG_7)
In-Reply-To: <200907091922.n69JMYvS067578@lava.sentex.ca>
References: <200907091922.n69JMYvS067578@lava.sentex.ca>
Message-ID: <d8e2594b0907100020p55e04f39r7e2b30327fb71cfc@mail.gmail.com>

2009/7/9 Mike Tancsa <mike@sentex.net>

 Jul  9 14:34:17 fw02 kernel: ng_ether_attach: can't name node em1.10
> Jul  9 14:34:17 fw02 kernel: ng_ether_attach: can't name node em1.172
> Jul  9 14:34:17 fw02 kernel: ng_ether_attach: can't name node em1.24
>


> Is there some reason this does not work ?


reason - names of interfaces with "." :)
-- 
WBR, ??????? ???????, vm@vm.net.ua
Nick-hdl: VM347-RIPE, VM265-UANIC
ICQ# 111222168
From rwatson at FreeBSD.org  Fri Jul 10 11:10:04 2009
From: rwatson at FreeBSD.org (Robert Watson)
Date: Fri Jul 10 11:10:11 2009
Subject: smbfs panic when lost connection or unmount --force
In-Reply-To: <6101e8c40907091755n5aefe289r6eec14cf7f4287dc@mail.gmail.com>
References: <6101e8c40907091755n5aefe289r6eec14cf7f4287dc@mail.gmail.com>
Message-ID: <alpine.BSF.2.00.0907101209350.10745@fledge.watson.org>


On Fri, 10 Jul 2009, Oliver Pinter wrote:

> It is a kernel panic, when force unmount the smbfs volume or lost the 
> connection with the samba server.

This is a NULL pointer dereference in the kernel.  Per Attilio's e-mail, a 
stack trace should help us track it down.  Thanks!

Robert N M Watson
Computer Laboratory
University of Cambridge

>
> --
> Thes OS is:
>
>
> kern.ostype: FreeBSD
> kern.osrelease: 7.2-STABLE
> kern.osrevision: 199506
> kern.version: FreeBSD 7.2-STABLE #4: Sat Jun 27 21:44:32 CEST 2009
>    root@oliverp:/usr/obj/usr/src/sys/stable
> kern.osreldate: 702103
>
> --
> make.conf:
>
>
> CPUTYPE?=core2
> CFLAGS= -O2 -fno-strict-aliasing -pipe
> MODULES_OVERRIDE=smbfs libiconv libmchain zfs opensolaris drm cd9660
> cd9660_iconv
>
> --
> panic message:
>
> Jul 10 01:58:39 oliverp syslogd: kernel boot file is /boot/kernel/kernel
> Jul 10 01:58:39 oliverp kernel: kernel trap 12 with interrupts disabled
> Jul 10 01:58:39 oliverp kernel:
> Jul 10 01:58:39 oliverp kernel:
> Jul 10 01:58:39 oliverp kernel: Fatal trap 12: page fault while in kernel mode
> Jul 10 01:58:39 oliverp kernel: cpuid = 2; apic id = 02
> Jul 10 01:58:39 oliverp kernel: fault virtual address	= 0x30
> Jul 10 01:58:39 oliverp kernel: fault code		= supervisor read data,
> page not present
> Jul 10 01:58:39 oliverp kernel: instruction pointer	= 0x8:0xffffffff80327fd0
> Jul 10 01:58:39 oliverp kernel: stack pointer	        = 0x10:0xffffff8078360940
> Jul 10 01:58:39 oliverp kernel: frame pointer	        = 0x10:0xffffff0004c31390
> Jul 10 01:58:39 oliverp kernel: code segment		= base 0x0, limit
> 0xfffff, type 0x1b
> Jul 10 01:58:39 oliverp kernel: = DPL 0, pres 1, long 1, def32 0, gran 1
> Jul 10 01:58:39 oliverp kernel: processor eflags	= resume, IOPL = 0
> Jul 10 01:58:39 oliverp kernel: current process		= 60406 (smbiod0)
> Jul 10 01:58:39 oliverp kernel: trap number		= 12
> Jul 10 01:58:39 oliverp kernel: panic: page fault
> Jul 10 01:58:39 oliverp kernel: cpuid = 2
> Jul 10 01:58:39 oliverp kernel: Uptime: 6h51m16s
> Jul 10 01:58:39 oliverp kernel: Physical memory: 4087 MB
> Jul 10 01:58:39 oliverp kernel: Dumping 2448 MB:Copyright (c)
> 1992-2009 The FreeBSD Project.
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>
From raul at pop.isdefe.es  Fri Jul 10 11:38:49 2009
From: raul at pop.isdefe.es (Raul)
Date: Fri Jul 10 11:38:56 2009
Subject: regression on releng_7 (and 8 beta1 vs proliant dl 385)
Message-ID: <4A57244A.1090109@pop.isdefe.es>

Hello,

I've tried an 8 beta 1 (from usb image, and source upgrade) and releng_7 
(both amd64) from today on a hp's proliant 385 with the same 
misbehaviors, kernel hung during boot at exactly the same point. Last 
message on the console is: 'pci0: <ACPI PCI bus> on pcib0' and the disk 
led activity is solid on. After some trial / error and looking for more 
information, I've tried verbose boot and surprisingly the machines 
finish the boot process flawlessly and ask for credentials.

verbose dmesg availables at:

http://pastebin.com/m1918b1db
http://pastebin.com/m5edd8d03

Both boxes used to run releng_7_2 perfectly, and are ready to try 
whatever you ask me ;).

Thanks a lot in advance.

Regards,
Raul.


From avg at icyb.net.ua  Fri Jul 10 12:09:54 2009
From: avg at icyb.net.ua (Andriy Gapon)
Date: Fri Jul 10 12:10:02 2009
Subject: ZFS: zpool scrub lockup
In-Reply-To: <4A563627.7040407@ronner.org>
References: <1247085058.6197.18.camel@bugstore>
	<4A55F96B.6070303@icyb.net.ua>	<4A560E2F.1050906@ronner.org>
	<4A5626FC.5000306@ronner.org> <4A562A4A.2000201@icyb.net.ua>
	<4A563627.7040407@ronner.org>
Message-ID: <4A572F8E.6040004@icyb.net.ua>

on 09/07/2009 21:25 Thomas Ronner said the following:
> Is this:
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-online-gdb.html
> (10.6 On-Line Kernel Debugging Using Remote GDB) the debugging via
> serial console you're referring to?

Yes.

-- 
Andriy Gapon
From oliver.pntr at gmail.com  Fri Jul 10 12:17:44 2009
From: oliver.pntr at gmail.com (Oliver Pinter)
Date: Fri Jul 10 12:17:53 2009
Subject: smbfs panic when lost connection or unmount --force
In-Reply-To: <alpine.BSF.2.00.0907101209350.10745@fledge.watson.org>
References: <6101e8c40907091755n5aefe289r6eec14cf7f4287dc@mail.gmail.com>
	<alpine.BSF.2.00.0907101209350.10745@fledge.watson.org>
Message-ID: <6101e8c40907100517q2d2e5891m62b0b7d57496b10@mail.gmail.com>

Hello!

I know, that the bt is useful, but ddb works with usb keyboard?
At nigth then I send the log.

//sorry for bad english

ps.: attached the config

On 7/10/09, Robert Watson <rwatson@freebsd.org> wrote:
>
> On Fri, 10 Jul 2009, Oliver Pinter wrote:
>
>> It is a kernel panic, when force unmount the smbfs volume or lost the
>> connection with the samba server.
>
> This is a NULL pointer dereference in the kernel.  Per Attilio's e-mail, a
> stack trace should help us track it down.  Thanks!
>
> Robert N M Watson
> Computer Laboratory
> University of Cambridge
>
>>
>> --
>> Thes OS is:
>>
>>
>> kern.ostype: FreeBSD
>> kern.osrelease: 7.2-STABLE
>> kern.osrevision: 199506
>> kern.version: FreeBSD 7.2-STABLE #4: Sat Jun 27 21:44:32 CEST 2009
>>    root@oliverp:/usr/obj/usr/src/sys/stable
>> kern.osreldate: 702103
>>
>> --
>> make.conf:
>>
>>
>> CPUTYPE?=core2
>> CFLAGS= -O2 -fno-strict-aliasing -pipe
>> MODULES_OVERRIDE=smbfs libiconv libmchain zfs opensolaris drm cd9660
>> cd9660_iconv
>>
>> --
>> panic message:
>>
>> Jul 10 01:58:39 oliverp syslogd: kernel boot file is /boot/kernel/kernel
>> Jul 10 01:58:39 oliverp kernel: kernel trap 12 with interrupts disabled
>> Jul 10 01:58:39 oliverp kernel:
>> Jul 10 01:58:39 oliverp kernel:
>> Jul 10 01:58:39 oliverp kernel: Fatal trap 12: page fault while in kernel
>> mode
>> Jul 10 01:58:39 oliverp kernel: cpuid = 2; apic id = 02
>> Jul 10 01:58:39 oliverp kernel: fault virtual address	= 0x30
>> Jul 10 01:58:39 oliverp kernel: fault code		= supervisor read data,
>> page not present
>> Jul 10 01:58:39 oliverp kernel: instruction pointer	=
>> 0x8:0xffffffff80327fd0
>> Jul 10 01:58:39 oliverp kernel: stack pointer	        =
>> 0x10:0xffffff8078360940
>> Jul 10 01:58:39 oliverp kernel: frame pointer	        =
>> 0x10:0xffffff0004c31390
>> Jul 10 01:58:39 oliverp kernel: code segment		= base 0x0, limit
>> 0xfffff, type 0x1b
>> Jul 10 01:58:39 oliverp kernel: = DPL 0, pres 1, long 1, def32 0, gran 1
>> Jul 10 01:58:39 oliverp kernel: processor eflags	= resume, IOPL = 0
>> Jul 10 01:58:39 oliverp kernel: current process		= 60406 (smbiod0)
>> Jul 10 01:58:39 oliverp kernel: trap number		= 12
>> Jul 10 01:58:39 oliverp kernel: panic: page fault
>> Jul 10 01:58:39 oliverp kernel: cpuid = 2
>> Jul 10 01:58:39 oliverp kernel: Uptime: 6h51m16s
>> Jul 10 01:58:39 oliverp kernel: Physical memory: 4087 MB
>> Jul 10 01:58:39 oliverp kernel: Dumping 2448 MB:Copyright (c)
>> 1992-2009 The FreeBSD Project.
>> _______________________________________________
>> freebsd-stable@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>>
>
-------------- next part --------------
#
# GENERIC -- Generic kernel configuration file for FreeBSD/amd64
#
# For more information on this file, please read the handbook section on
# Kernel Configuration Files:
#
#    http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
#
# The handbook is also available locally in /usr/share/doc/handbook
# if you've installed the doc distribution, otherwise always see the
# FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the
# latest information.
#
# An exhaustive list of options and more detailed explanations of the
# device lines is also present in the ../../conf/NOTES and NOTES files.
# If you are in doubt as to the purpose or necessity of a line, check first
# in NOTES.
#
# $FreeBSD: src/sys/amd64/conf/GENERIC,v 1.484.2.14 2008/08/29 18:54:35 jhb Exp $

cpu		HAMMER
ident		sTaBlE-debug

# To statically compile in device wiring instead of /boot/device.hints
#hints		"GENERIC.hints"		# Default places to look for devices.

makeoptions	DEBUG=-g		# Build kernel with gdb(1) debug symbols

# Debugging for use in -current
options         KDB                     # Enable kernel debugger support.
options         DDB                     # Support DDB.
options         GDB                     # Support remote GDB.
options         INVARIANTS              # Enable calls of extra sanity checking
options         INVARIANT_SUPPORT       # Extra sanity checks of internal struct
# ures, required by INVARIANTS
options         WITNESS                 # Enable checks to detect deadlocks and
# cycles
#


options 	SCHED_ULE		# ULE scheduler
options 	PREEMPTION		# Enable kernel thread preemption
options 	INET			# InterNETworking
options 	INET6			# IPv6 communications protocols
options 	SCTP			# Stream Control Transmission Protocol 
options 	FFS			# Berkeley Fast Filesystem
options 	SOFTUPDATES		# Enable FFS soft updates support
options         UFS_EXTATTR
options         UFS_EXTATTR_AUTOSTART
options 	UFS_ACL			# Support for access control lists
options 	UFS_DIRHASH		# Improve performance on big directories
options 	UFS_GJOURNAL		# Enable gjournal-based UFS journaling
options 	MD_ROOT			# MD is a potential root device
#options 	NFSCLIENT		# Network Filesystem Client
#options 	NFSSERVER		# Network Filesystem Server
#options 	NFSLOCKD		# Network Lock Manager
#options 	NFS_ROOT		# NFS usable as /, requires NFSCLIENT
#options 	NTFS			# NT File System
options 	MSDOSFS			# MSDOS Filesystem
options 	CD9660			# ISO 9660 Filesystem
options 	PROCFS			# Process filesystem (requires PSEUDOFS)
options 	PSEUDOFS		# Pseudo-filesystem framework
options 	GEOM_PART_GPT		# GUID Partition Tables.
options 	GEOM_LABEL		# Provides labelization
options 	COMPAT_43TTY		# BSD 4.3 TTY compat [KEEP THIS!]
options 	COMPAT_IA32		# Compatible with i386 binaries
options 	COMPAT_FREEBSD4		# Compatible with FreeBSD4
options 	COMPAT_FREEBSD5		# Compatible with FreeBSD5
options 	COMPAT_FREEBSD6		# Compatible with FreeBSD6
options 	SCSI_DELAY=5000		# Delay (in ms) before probing SCSI
options 	KTRACE			# ktrace(1) support
options 	STACK			# stack(9) support
options 	SYSVSHM			# SYSV-style shared memory
options 	SYSVMSG			# SYSV-style message queues
options 	SYSVSEM			# SYSV-style semaphores
options 	_KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions
options 	KBD_INSTALL_CDEV	# install a CDEV entry in /dev
options 	ADAPTIVE_GIANT		# Giant mutex is adaptive.
options 	STOP_NMI		# Stop CPUS using NMI instead of IPI
options 	AUDIT			# Security event auditing
#options 	KDTRACE_FRAME		# Ensure frames are compiled in
#options 	KDTRACE_HOOKS		# Kernel DTrace hooks

# Make an SMP-capable kernel by default
options 	SMP			# Symmetric MultiProcessor Kernel

options         HZ=100

# CPU frequency control
device		cpufreq

# Bus support.
device		acpi
device		pci

# Floppy drives
#device		fdc

# ATA and ATAPI devices
device		ata
device		atadisk		# ATA disk drives
device		ataraid		# ATA RAID drives
device		atapicd		# ATAPI CDROM drives
#device		atapifd		# ATAPI floppy drives
#device		atapist		# ATAPI tape drives
options 	ATA_STATIC_ID	# Static device numbering

# SCSI Controllers
#device		ahc		# AHA2940 and onboard AIC7xxx devices
#options 	AHC_REG_PRETTY_PRINT	# Print register bitfields in debug
					# output.  Adds ~128k to driver.
#device		ahd		# AHA39320/29320 and onboard AIC79xx devices
#options 	AHD_REG_PRETTY_PRINT	# Print register bitfields in debug
					# output.  Adds ~215k to driver.
#device		amd		# AMD 53C974 (Tekram DC-390(T))
#device		hptiop		# Highpoint RocketRaid 3xxx series
#device		isp		# Qlogic family
#device 	ispfw		# Firmware for QLogic HBAs- normally a module
#device		mpt		# LSI-Logic MPT-Fusion
#device		ncr		# NCR/Symbios Logic
#device		sym		# NCR/Symbios Logic (newer chipsets + those of `ncr')
#device		trm		# Tekram DC395U/UW/F DC315U adapters

#device		adv		# Advansys SCSI adapters
#device		adw		# Advansys wide SCSI adapters
#device		aic		# Adaptec 15[012]x SCSI adapters, AIC-6[23]60.
#device		bt		# Buslogic/Mylex MultiMaster SCSI adapters


# SCSI peripherals
device		scbus		# SCSI bus (required for SCSI)
device		ch		# SCSI media changers
device		da		# Direct Access (disks)
#device		sa		# Sequential Access (tape etc)
device		cd		# CD
device		pass		# Passthrough device (direct SCSI access)
device		ses		# SCSI Environmental Services (and SAF-TE)

# RAID controllers interfaced to the SCSI subsystem
#device		amr		# AMI MegaRAID
#device		arcmsr		# Areca SATA II RAID
#device		ciss		# Compaq Smart RAID 5*
#device		dpt		# DPT Smartcache III, IV - See NOTES for options
#device		hptmv		# Highpoint RocketRAID 182x
#device		hptrr		# Highpoint RocketRAID 17xx, 22xx, 23xx, 25xx
device		iir		# Intel Integrated RAID
#device		ips		# IBM (Adaptec) ServeRAID
#device		mly		# Mylex AcceleRAID/eXtremeRAID
#device		twa		# 3ware 9000 series PATA/SATA RAID

# RAID controllers
#device		aac		# Adaptec FSA RAID
#device		aacp		# SCSI passthrough for aac (requires CAM)
#device		ida		# Compaq Smart RAID
#device		mfi		# LSI MegaRAID SAS
#device		mlx		# Mylex DAC960 family
#XXX pointer/int warnings
#device		pst		# Promise Supertrak SX6000
#device		twe		# 3ware ATA RAID

# atkbdc0 controls both the keyboard and the PS/2 mouse
device		atkbdc		# AT keyboard controller
device		atkbd		# AT keyboard
device		psm		# PS/2 mouse

device		kbdmux		# keyboard multiplexer

device		vga		# VGA video card driver

device		splash		# Splash screen and screen saver support

# syscons is the default console driver, resembling an SCO console
device		sc

device		agp		# support several AGP chipsets

# PCCARD (PCMCIA) support
# PCMCIA and cardbus bridge support
#device		cbb		# cardbus (yenta) bridge
#device		pccard		# PC Card (16-bit) bus
#device		cardbus		# CardBus (32-bit) bus

# Serial (COM) ports
device		sio		# 8250, 16[45]50 based serial ports
device		uart		# Generic UART driver

# Parallel port
device		ppc
device		ppbus		# Parallel port bus (required)
device		lpt		# Printer
device		plip		# TCP/IP over parallel
device		ppi		# Parallel port interface device
#device		vpo		# Requires scbus and da

# If you've got a "dumb" serial or parallel PCI card that is
# supported by the puc(4) glue driver, uncomment the following
# line to enable it (connects to sio, uart and/or ppc drivers):
#device		puc

# PCI Ethernet NICs.
#device		de		# DEC/Intel DC21x4x (``Tulip'')
#device		em		# Intel PRO/1000 Gigabit Ethernet Family
#device		igb		# Intel PRO/1000 PCIE Server Gigabit Family
#device		ixgb		# Intel PRO/10GbE Ethernet Card
#device		le		# AMD Am7900 LANCE and Am79C9xx PCnet
#device		txp		# 3Com 3cR990 (``Typhoon'')
#device		vx		# 3Com 3c590, 3c595 (``Vortex'')

# PCI Ethernet NICs that use the common MII bus controller code.
# NOTE: Be sure to keep the 'device miibus' line in order to use these NICs!
device		miibus		# MII bus support
#device		age		# Attansic/Atheros L1 Gigabit Ethernet
#device		bce		# Broadcom BCM5706/BCM5708 Gigabit Ethernet
#device		bfe		# Broadcom BCM440x 10/100 Ethernet
#device		bge		# Broadcom BCM570xx Gigabit Ethernet
#device		dc		# DEC/Intel 21143 and various workalikes
#device		et		# Agere ET1310 10/100/Gigabit Ethernet
#device		fxp		# Intel EtherExpress PRO/100B (82557, 82558)
#device		jme		# JMicron JMC250 Gigabit/JMC260 Fast Ethernet
#device		lge		# Level 1 LXT1001 gigabit Ethernet
device		msk		# Marvell/SysKonnect Yukon II Gigabit Ethernet
#device		nfe		# nVidia nForce MCP on-board Ethernet
#device		nge		# NatSemi DP83820 gigabit Ethernet
#device		nve		# nVidia nForce MCP on-board Ethernet Networking
#device		pcn		# AMD Am79C97x PCI 10/100 (precedence over 'le')
#device		re		# RealTek 8139C+/8169/8169S/8110S
#device		rl		# RealTek 8129/8139
#device		sf		# Adaptec AIC-6915 (``Starfire'')
#device		sis		# Silicon Integrated Systems SiS 900/SiS 7016
device		sk		# SysKonnect SK-984x & SK-982x gigabit Ethernet
#device		ste		# Sundance ST201 (D-Link DFE-550TX)
#device		ti		# Alteon Networks Tigon I/II gigabit Ethernet
#device		tl		# Texas Instruments ThunderLAN
#device		tx		# SMC EtherPower II (83c170 ``EPIC'')
#device		vge		# VIA VT612x gigabit Ethernet
#device		vr		# VIA Rhine, Rhine II
#device		wb		# Winbond W89C840F
#device		xl		# 3Com 3c90x (``Boomerang'', ``Cyclone'')

# ISA Ethernet NICs.  pccard NICs included.
#device		cs		# Crystal Semiconductor CS89x0 NIC
# 'device ed' requires 'device miibus'
#device		ed		# NE[12]000, SMC Ultra, 3c503, DS8390 cards
#device		ex		# Intel EtherExpress Pro/10 and Pro/10+
#device		ep		# Etherlink III based cards
#device		fe		# Fujitsu MB8696x based cards
#device		sn		# SMC's 9000 series of Ethernet chips
#device		xe		# Xircom pccard Ethernet

# Wireless NIC cards
#device		wlan		# 802.11 support
#device		wlan_wep	# 802.11 WEP support
#device		wlan_ccmp	# 802.11 CCMP support
#device		wlan_tkip	# 802.11 TKIP support
#device		wlan_amrr	# AMRR transmit rate control algorithm
#device		wlan_scan_ap	# 802.11 AP mode scanning
#device		wlan_scan_sta	# 802.11 STA mode scanning
#device		an		# Aironet 4500/4800 802.11 wireless NICs.
#device		ath		# Atheros pci/cardbus NIC's
#device		ath_hal		# Atheros HAL (Hardware Access Layer)
#device		ath_rate_sample	# SampleRate tx rate control for ath
#device		awi		# BayStack 660 and others
#device		ral		# Ralink Technology RT2500 wireless NICs.
#device		wi		# WaveLAN/Intersil/Symbol 802.11 wireless NICs.

# Pseudo devices.
device		loop		# Network loopback
device		random		# Entropy device
device		ether		# Ethernet support
device		sl		# Kernel SLIP
#device		ppp		# Kernel PPP
device		tun		# Packet tunnel.
device		pty		# Pseudo-ttys (telnet etc)
device		md		# Memory "disks"
device		gif		# IPv6 and IPv4 tunneling
device		faith		# IPv6-to-IPv4 relaying (translation)
device		firmware	# firmware assist module

# The `bpf' device enables the Berkeley Packet Filter.
# Be aware of the administrative consequences of enabling this!
# Note that 'bpf' is required for DHCP.
device		bpf		# Berkeley packet filter

# USB support
device		uhci		# UHCI PCI->USB interface
device		ohci		# OHCI PCI->USB interface
device		ehci		# EHCI PCI->USB interface (USB 2.0)
device		usb		# USB Bus (required)
#device		udbp		# USB Double Bulk Pipe devices
device		ugen		# Generic
device		uhid		# "Human Interface Devices"
device		ukbd		# Keyboard
device		ulpt		# Printer
device		umass		# Disks/Mass storage - Requires scbus and da
device		ums		# Mouse
#device		ural		# Ralink Technology RT2500USB wireless NICs
#device		urio		# Diamond Rio 500 MP3 player
device		uscanner	# Scanners
# USB Serial devices
device		ucom		# Generic com ttys
#device		uark		# Technologies ARK3116 based serial adapters
#device		ubsa		# Belkin F5U103 and compatible serial adapters
#device		ubser		# BWCT console serial adapters
#device		uftdi		# For FTDI usb serial adapters
#device		uipaq		# Some WinCE based devices
#device		uplcom		# Prolific PL-2303 serial adapters
#device		uslcom		# SI Labs CP2101/CP2102 serial adapters
#device		uvisor		# Visor and Palm devices
#device		uvscom		# USB serial support for DDI pocket's PHS
# USB Ethernet, requires miibus
#device		aue		# ADMtek USB Ethernet
#device		axe		# ASIX Electronics USB Ethernet
#device		cdce		# Generic USB over Ethernet
#device		cue		# CATC USB Ethernet
#device		kue		# Kawasaki LSI USB Ethernet
#device		rue		# RealTek RTL8150 USB Ethernet

# FireWire support
device		firewire	# FireWire bus code
device		sbp		# SCSI over FireWire (Requires scbus and da)
device		fwe		# Ethernet over FireWire (non-standard!)
device		fwip		# IP over FireWire (RFC 2734,3146)
device		dcons		# Dumb console driver
device		dcons_crom	# Configuration ROM for dcons

device          sound
device		snd_hda

device		coretemp
device		atapicam
options		VFS_AIO
options		SC_DISABLE_REBOOT # Ctrl-Alt-Del
options		IPFIREWALL
options 	IPFIREWALL_VERBOSE
options 	IPFIREWALL_VERBOSE_LIMIT=10
options 	IPSTEALTH
device		cpuctl
device		acpi_aiboost
options		MAC
options		MAC_BSDEXTENDED
From hlh at restart.be  Fri Jul 10 12:32:08 2009
From: hlh at restart.be (Henri Hennebert)
Date: Fri Jul 10 12:32:14 2009
Subject: 8.0-BETA1 - for the record - different paths followed by IPv4 and
 IPv6 for 'local' connections
Message-ID: <4A5734C3.3000806@restart.be>

Hello,

After upgrading from 7.2-STABLE to 8.0-BETA1 I encounter a problem when 
connecting with firefox to a local apache server using the global 
unicast IPv6 address of the local machine. pf.conf must be updated!

My configuration:

[root@avoriaz ~]# ifconfig em0

em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4>
	ether 00:1d:60:ad:2a:ce
	inet 192.168.24.1 netmask 0xffffff00 broadcast 192.168.24.255
	inet6 fe80::21d:60ff:fead:2ace%em0 prefixlen 64 scopeid 0x1
	inet6 2001:41d0:2:2d29:1:1:: prefixlen 80
	media: Ethernet 100baseTX (100baseTX <half-duplex>)
	status: active

[root@avoriaz ~]# host www.restart.bel
www.restart.bel is an alias for avoriaz.restart.bel.
avoriaz.restart.bel has address 192.168.24.1
avoriaz.restart.bel has IPv6 address 2001:41d0:2:2d29:1:1::

pf.conf:

int_if="em0"
block in  log all
block out log all
set skip on lo0
antispoof quick for $int_if inet
# Allow trafic with physical internal network
pass in quick on $int_if from ($int_if:network) to ($int_if) keep state
pass out quick on $int_if from ($int_if) to ($int_if:network) keep state

The problem:

[root@avoriaz ~]# telnet -4 www.restart.bel 80
Trying 192.168.24.1...
Connected to avoriaz.restart.bel.
Escape character is '^]'.
^]
telnet> quit
Connection closed.
[root@avoriaz ~]# telnet -6 www.restart.bel 80
Trying 2001:41d0:2:2d29:1:1::...
--->Never connect and get a timeout!

tcpdump and logging in pf show me that

For a IPv4 connection:
the packet from telnet to apache pass 2 times on lo0 (out and in)
the answer packet from apache to telnet pass 2 times on lo0 (out and in)

So no problem, there is `set skip on lo0'

For a IPv6 connection:
The first packet from telnet to apache pass 2 times on lo0 (out and in)
The answer packet from apache to telnet path on em0  and is rejected
due to the default flags S/SA.

So I have to change pf.conf and replace the last line:
pass out quick on $int_if from ($int_if) to ($int_if:network) \
keep state flags any

Then all is OK

By the way, on 7.2

netstat -rn display

192.168.24.1        00:1d:60:ad:2a:ce
....
2001:41d0:2:2d29:1:1::            00:1d:60:ad:2a:ce


On 8.0-BETA1 there is an assymetry:

netstat -rn display

192.168.24.1       link#3
....
no entry for 2001:41d0:2:2d29:1:1::

Hope it may help someone

Henri

From hlh at restart.be  Fri Jul 10 12:35:34 2009
From: hlh at restart.be (Henri Hennebert)
Date: Fri Jul 10 12:35:41 2009
Subject: 8.0-BETA1 - for the record - different paths followed by IPv4 and
 IPv6 for 'local' connections
Message-ID: <4A573591.1000506@restart.be>

Hello,

After upgrading from 7.2-STABLE to 8.0-BETA1 I encounter a problem when
connecting with firefox to a local apache server using the global
unicast IPv6 address of the local machine. pf.conf must be updated!

My configuration:

[root@avoriaz ~]# ifconfig em0

em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4>
	ether 00:1d:60:ad:2a:ce
	inet 192.168.24.1 netmask 0xffffff00 broadcast 192.168.24.255
	inet6 fe80::21d:60ff:fead:2ace%em0 prefixlen 64 scopeid 0x1
	inet6 2001:41d0:2:2d29:1:1:: prefixlen 80
	media: Ethernet 100baseTX (100baseTX <half-duplex>)
	status: active

[root@avoriaz ~]# host www.restart.bel
www.restart.bel is an alias for avoriaz.restart.bel.
avoriaz.restart.bel has address 192.168.24.1
avoriaz.restart.bel has IPv6 address 2001:41d0:2:2d29:1:1::

pf.conf:

int_if="em0"
block in  log all
block out log all
set skip on lo0
antispoof quick for $int_if inet
# Allow trafic with physical internal network
pass in quick on $int_if from ($int_if:network) to ($int_if) keep state
pass out quick on $int_if from ($int_if) to ($int_if:network) keep state

The problem:

[root@avoriaz ~]# telnet -4 www.restart.bel 80
Trying 192.168.24.1...
Connected to avoriaz.restart.bel.
Escape character is '^]'.
^]
telnet> quit
Connection closed.
[root@avoriaz ~]# telnet -6 www.restart.bel 80
Trying 2001:41d0:2:2d29:1:1::...
--->Never connect and get a timeout!

tcpdump and logging in pf show me that

For a IPv4 connection:
the packet from telnet to apache pass 2 times on lo0 (out and in)
the answer packet from apache to telnet pass 2 times on lo0 (out and in)

So no problem, there is `set skip on lo0'

For a IPv6 connection:
The first packet from telnet to apache pass 2 times on lo0 (out and in)
The answer packet from apache to telnet path on em0  and is rejected
due to the default flags S/SA.

So I have to change pf.conf and replace the last line:
pass out quick on $int_if from ($int_if) to ($int_if:network) \
keep state flags any

Then all is OK

By the way, on 7.2

netstat -rn display

192.168.24.1        00:1d:60:ad:2a:ce
....
2001:41d0:2:2d29:1:1::            00:1d:60:ad:2a:ce


On 8.0-BETA1 there is an assymetry:

netstat -rn display

192.168.24.1       link#3
....
no entry for 2001:41d0:2:2d29:1:1::

Hope it may help someone

Henri


From thomas at ronner.org  Fri Jul 10 13:54:18 2009
From: thomas at ronner.org (Thomas Ronner)
Date: Fri Jul 10 13:54:26 2009
Subject: ZFS: zpool scrub lockup
In-Reply-To: <4A572F8E.6040004@icyb.net.ua>
References: <1247085058.6197.18.camel@bugstore>
	<4A55F96B.6070303@icyb.net.ua>	<4A560E2F.1050906@ronner.org>
	<4A5626FC.5000306@ronner.org> <4A562A4A.2000201@icyb.net.ua>
	<4A563627.7040407@ronner.org>  <4A572F8E.6040004@icyb.net.ua>
Message-ID: <1247234055.5197.0.camel@bugstore>

On Fri, 2009-07-10 at 15:09 +0300, Andriy Gapon wrote:
> on 09/07/2009 21:25 Thomas Ronner said the following:
> > Is this:
> > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-online-gdb.html
> > (10.6 On-Line Kernel Debugging Using Remote GDB) the debugging via
> > serial console you're referring to?
> 
> Yes.
> 

Thanks. I'll try that in a couple of weeks when I return from vacation.


Thomas

From oliver.pntr at gmail.com  Fri Jul 10 15:01:25 2009
From: oliver.pntr at gmail.com (Oliver Pinter)
Date: Fri Jul 10 15:01:32 2009
Subject: smbfs panic when lost connection or unmount --force
In-Reply-To: <alpine.BSF.2.00.0907101209350.10745@fledge.watson.org>
References: <6101e8c40907091755n5aefe289r6eec14cf7f4287dc@mail.gmail.com>
	<alpine.BSF.2.00.0907101209350.10745@fledge.watson.org>
Message-ID: <6101e8c40907100801r382ded4boddd853f771867bd0@mail.gmail.com>

Hello!

Here is the bt:
http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01845.JPG
http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01846.JPG
http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01847.JPG

steps to reproduce:
1) mount_smbfs -I server //biz@foo.bar.baz /media/biz
2) generate IO from smb (cp somewate ..)
3) under IO pull down the network cable
4)
  a) wait to panic
  b) umount -f /media/biz, and the system faster panics


On 7/10/09, Robert Watson <rwatson@freebsd.org> wrote:
>
> On Fri, 10 Jul 2009, Oliver Pinter wrote:
>
>> It is a kernel panic, when force unmount the smbfs volume or lost the
>> connection with the samba server.
>
> This is a NULL pointer dereference in the kernel.  Per Attilio's e-mail, a
> stack trace should help us track it down.  Thanks!
>
> Robert N M Watson
> Computer Laboratory
> University of Cambridge
>
>>
>> --
>> Thes OS is:
>>
>>
>> kern.ostype: FreeBSD
>> kern.osrelease: 7.2-STABLE
>> kern.osrevision: 199506
>> kern.version: FreeBSD 7.2-STABLE #4: Sat Jun 27 21:44:32 CEST 2009
>>    root@oliverp:/usr/obj/usr/src/sys/stable
>> kern.osreldate: 702103
>>
>> --
>> make.conf:
>>
>>
>> CPUTYPE?=core2
>> CFLAGS= -O2 -fno-strict-aliasing -pipe
>> MODULES_OVERRIDE=smbfs libiconv libmchain zfs opensolaris drm cd9660
>> cd9660_iconv
>>
>> --
>> panic message:
>>
>> Jul 10 01:58:39 oliverp syslogd: kernel boot file is /boot/kernel/kernel
>> Jul 10 01:58:39 oliverp kernel: kernel trap 12 with interrupts disabled
>> Jul 10 01:58:39 oliverp kernel:
>> Jul 10 01:58:39 oliverp kernel:
>> Jul 10 01:58:39 oliverp kernel: Fatal trap 12: page fault while in kernel
>> mode
>> Jul 10 01:58:39 oliverp kernel: cpuid = 2; apic id = 02
>> Jul 10 01:58:39 oliverp kernel: fault virtual address	= 0x30
>> Jul 10 01:58:39 oliverp kernel: fault code		= supervisor read data,
>> page not present
>> Jul 10 01:58:39 oliverp kernel: instruction pointer	=
>> 0x8:0xffffffff80327fd0
>> Jul 10 01:58:39 oliverp kernel: stack pointer	        =
>> 0x10:0xffffff8078360940
>> Jul 10 01:58:39 oliverp kernel: frame pointer	        =
>> 0x10:0xffffff0004c31390
>> Jul 10 01:58:39 oliverp kernel: code segment		= base 0x0, limit
>> 0xfffff, type 0x1b
>> Jul 10 01:58:39 oliverp kernel: = DPL 0, pres 1, long 1, def32 0, gran 1
>> Jul 10 01:58:39 oliverp kernel: processor eflags	= resume, IOPL = 0
>> Jul 10 01:58:39 oliverp kernel: current process		= 60406 (smbiod0)
>> Jul 10 01:58:39 oliverp kernel: trap number		= 12
>> Jul 10 01:58:39 oliverp kernel: panic: page fault
>> Jul 10 01:58:39 oliverp kernel: cpuid = 2
>> Jul 10 01:58:39 oliverp kernel: Uptime: 6h51m16s
>> Jul 10 01:58:39 oliverp kernel: Physical memory: 4087 MB
>> Jul 10 01:58:39 oliverp kernel: Dumping 2448 MB:Copyright (c)
>> 1992-2009 The FreeBSD Project.
>> _______________________________________________
>> freebsd-stable@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>>
>
From jensrasmus at gmail.com  Fri Jul 10 18:20:59 2009
From: jensrasmus at gmail.com (Jens Rasmus Liland)
Date: Fri Jul 10 18:21:07 2009
Subject: Error when using 'portupgrade -ay'.
Message-ID: <63e02e980907101100o5c9e0ca1uaba843be033f8869@mail.gmail.com>

Hello!

I had an error just now running 'portupgrade -ay'. Got this output:

---OUTPUT START---

--->  Session started at: Fri, 10 Jul 2009 18:58:30 +0200
** Port directory not found: x11-drivers/xf86-video-vga
** Port marked as IGNORE: x11-drivers/xf86-video-via:
    requires pciVideoPtr typedef
** Port directory not found: x11/xorg-protos
** Port directory not found: x11/xphelloworld
--->  Skipping 'x11-drivers/xorg-drivers' (xorg-drivers-7.3_3) because a
requisite package 'xf86-video-vga-4.1.0_2' (x11-drivers/xf86-video-vga)
failed (specify -k to force)
--->  ** Upgrade tasks 3: 0 done, 4 ignored, 1 skipped and 0 failed
--->  Skipping 'x11/xorg-apps' (xorg-apps-7.3) because a requisite package
'xphelloworld-1.0.1_1' (x11/xphelloworld) failed (specify -k to force)
--->  ** Upgrade tasks 3: 0 done, 4 ignored, 2 skipped and 0 failed
--->  Skipping 'x11/xorg' (xorg-7.3_2) because a requisite package
'xorg-drivers-7.3_3' (x11-drivers/xorg-drivers) failed (specify -k to force)
--->  ** Upgrade tasks 3: 0 done, 4 ignored, 3 skipped and 0 failed
--->  Listing the results (+:done / -:ignored / *:skipped / !:failed)
    - x11-drivers/xf86-video-vga (port directory error)
    - x11-drivers/xf86-video-via (marked as IGNORE)
    - x11/xorg-protos (port directory error)
    - x11/xphelloworld (port directory error)
    * x11-drivers/xorg-drivers (xorg-drivers-7.3_3)
    * x11/xorg-apps (xorg-apps-7.3)
    * x11/xorg (xorg-7.3_2)
--->  Packages processed: 0 done, 4 ignored, 3 skipped and 0 failed
--->  Session ended at: Fri, 10 Jul 2009 18:58:46 +0200 (consumed 00:00:15)

---OUTPUT STOP---

I've never got an error like this. What am I to do to make it work correctly
again?

/Rasmus
From quakelee at geekcn.org  Fri Jul 10 18:40:09 2009
From: quakelee at geekcn.org (Chao Shin)
Date: Fri Jul 10 18:40:18 2009
Subject: weird sata DMA error
Message-ID: <4A578AB6.3000600@geekcn.org>

Hi all,

I have a dell optiplex 755 box.  I plug a second disk on it for backup
logs.
It always report error message like below when heavy read load.

ad9: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=1511796863
ad9: TIMEOUT - READ_DMA48 retrying (0 retries left) LBA=1511796863
ad9: FAILURE - READ_DMA48 timed out LBA=1511796863
g_vfs_done():ad9s1d[READ(offset=774039961600, length=16384)]error = 5
ad9: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=1513678143
ad9: TIMEOUT - READ_DMA48 retrying (0 retries left) LBA=1513678143
ad9: FAILURE - READ_DMA48 timed out LBA=1513678143
g_vfs_done():ad9s1d[READ(offset=775003176960, length=16384)]error = 5

We had changed another disk, sata cable, box and upgrade freebsd from
7.1-RELEASE-p5 to 7.2-RELEASE. but error message still come out.

I have tried smartctl to send self-test command to disk, but it didn't
start test, I have no idea
about that now.

There is smart message and dmesg below:

# smartctl -a /dev/ad9
smartctl version 5.38 [amd64-portbld-freebsd7.2] Copyright (C) 2002-8
Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD15EADS-00R6B0
Serial Number:    WD-WCAVY0256398
Firmware Version: 01.00A01
User Capacity:    1,500,301,910,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Thu Jul  9 13:42:22 2009 CST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x85)    Offline data collection activity
                    was aborted by an interrupting command from host.
                    Auto Offline Data Collection: Enabled.
Self-test execution status:      ( 249)    Self-test routine in progress...
                    90% of test remaining.
Total time to complete Offline
data collection:          (32400) seconds.
Offline data collection
capabilities:              (0x7b) SMART execute Offline immediate.
                    Auto Offline data collection on/off support.
                    Suspend Offline collection upon new
                    command.
                    Offline surface scan supported.
                    Self-test supported.
                    Conveyance Self-test supported.
                    Selective Self-test supported.
SMART capabilities:            (0x0003)    Saves SMART data before entering
                    power-saving mode.
                    Supports SMART auto save timer.
Error logging capability:        (0x01)    Error logging supported.
                    General Purpose Logging supported.
Short self-test routine
recommended polling time:      (   2) minutes.
Extended self-test routine
recommended polling time:      ( 255) minutes.
Conveyance self-test routine
recommended polling time:      (   5) minutes.
SCT capabilities:            (0x303f)    SCT Status supported.
                    SCT Feature Control supported.
                    SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE
UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   198   195   051    Pre-fail
Always       -       20340
  3 Spin_Up_Time            0x0027   155   144   021    Pre-fail
Always       -       9250
  4 Start_Stop_Count        0x0032   100   100   000    Old_age
Always       -       22
  5 Reallocated_Sector_Ct   0x0033   193   193   140    Pre-fail
Always       -       52
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age
Always       -       0
  9 Power_On_Hours          0x0032   099   099   000    Old_age
Always       -       904
 10 Spin_Retry_Count        0x0032   100   253   000    Old_age
Always       -       0
 11 Calibration_Retry_Count 0x0032   100   253   000    Old_age
Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age
Always       -       20
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age
Always       -       4
193 Load_Cycle_Count        0x0032   200   200   000    Old_age
Always       -       18
194 Temperature_Celsius     0x0022   115   100   000    Old_age
Always       -       37
196 Reallocated_Event_Count 0x0032   149   149   000    Old_age
Always       -       51
197 Current_Pending_Sector  0x0032   196   195   000    Old_age
Always       -       1213
198 Offline_Uncorrectable   0x0030   200   196   000    Old_age
Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age
Always       -       0
200 Multi_Zone_Error_Rate   0x0008   006   006   000    Old_age
Offline      -       38929

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

There is hardware info,

Copyright (c) 1992-2009 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.2-RELEASE-p2 #0: Thu Jul  9 12:46:37 CST 2009
    root@birdspark1.intra.umessage.com.cn:/usr/obj/usr/src/sys/BIRD
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Core(TM)2 Duo CPU     E6550  @ 2.33GHz (2327.50-MHz
K8-class CPU)
  Origin = "GenuineIntel"  Id = 0x6fb  Stepping = 11

Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>

Features2=0xe3fd<SSE3,RSVD2,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM>
  AMD Features=0x20100800<SYSCALL,NX,LM>
  AMD Features2=0x1<LAHF>
  Cores per package: 2
usable memory = 6287015936 (5995 MB)
avail memory  = 6046175232 (5766 MB)
ACPI APIC Table: <DELL   B9K    >
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
ioapic0: Changing APIC ID to 8
ioapic0 <Version 2.0> irqs 0-23 on motherboard
lapic0: Forcing LINT1 to edge trigger
kbd1 at kbdmux0
acpi0: <DELL B9K    > on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on
acpi0
Timecounter "HPET" frequency 14318180 Hz quality 900
acpi_button0: <Power Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
vgapci0: <VGA-compatible display> port 0xec90-0xec97 mem
0xfea00000-0xfea7ffff,0xd0000000-0xdfffffff,0xfeb00000-0xfebfffff irq 16
at device 2.0 on pci0
agp0: <Intel Q35 SVGA controller> on vgapci0
agp0: detected 7164k stolen memory
agp0: aperture size is 256M
vgapci1: <VGA-compatible display> mem 0xfea80000-0xfeafffff at device
2.1 on pci0
pci0: <simple comms> at device 3.0 (no driver attached)
atapci0: <Intel ATA controller> port
0xfe80-0xfe87,0xfe90-0xfe93,0xfea0-0xfea7,0xfeb0-0xfeb3,0xfef0-0xfeff
irq 18 at device 3.2 on pci0
atapci0: [ITHREAD]
ata2: <ATA channel 0> on atapci0
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci0
ata3: [ITHREAD]
pci0: <simple comms, UART> at device 3.3 (no driver attached)
em0: <Intel(R) PRO/1000 Network Connection 6.9.6> port 0xecc0-0xecdf mem
0xfe9e0000-0xfe9fffff,0xfe9db000-0xfe9dbfff irq 21 at device 25.0 on pci0
em0: Using MSI interrupt
em0: [FILTER]
em0: Ethernet address: 00:1a:a0:d9:35:9b
uhci0: <UHCI (generic) USB controller> port 0xff20-0xff3f irq 16 at
device 26.0 on pci0
uhci0: [GIANT-LOCKED]
uhci0: [ITHREAD]
usb0: <UHCI (generic) USB controller> on uhci0
usb0: USB revision 1.0
uhub0: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
uhub0: 2 ports with 2 removable, self powered
uhci1: <UHCI (generic) USB controller> port 0xff00-0xff1f irq 17 at
device 26.1 on pci0
uhci1: [GIANT-LOCKED]
uhci1: [ITHREAD]
usb1: <UHCI (generic) USB controller> on uhci1
usb1: USB revision 1.0
uhub1: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1
uhub1: 2 ports with 2 removable, self powered
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xfe9d9c00-0xfe9d9fff irq
22 at device 26.7 on pci0
ehci0: [GIANT-LOCKED]
ehci0: [ITHREAD]
usb2: waiting for BIOS to give up control
usb2: EHCI version 1.0
usb2: wrong number of companions (3 != 2)
usb2: companion controllers, 2 ports each: usb0 usb1
usb2: <EHCI (generic) USB 2.0 controller> on ehci0
usb2: USB revision 2.0
uhub2: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb2
uhub2: 6 ports with 6 removable, self powered
pci0: <multimedia, HDA> at device 27.0 (no driver attached)
pcib2: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
pci2: <ACPI PCI bus> on pcib2
uhci2: <UHCI (generic) USB controller> port 0xff80-0xff9f irq 23 at
device 29.0 on pci0
uhci2: [GIANT-LOCKED]
uhci2: [ITHREAD]
usb3: <UHCI (generic) USB controller> on uhci2
usb3: USB revision 1.0
uhub3: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb3
uhub3: 2 ports with 2 removable, self powered
uhci3: <UHCI (generic) USB controller> port 0xff60-0xff7f irq 17 at
device 29.1 on pci0
uhci3: [GIANT-LOCKED]
uhci3: [ITHREAD]
usb4: <UHCI (generic) USB controller> on uhci3
usb4: USB revision 1.0
uhub4: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb4
uhub4: 2 ports with 2 removable, self powered
uhci4: <UHCI (generic) USB controller> port 0xff40-0xff5f irq 18 at
device 29.2 on pci0
uhci4: [GIANT-LOCKED]
uhci4: [ITHREAD]
usb5: <UHCI (generic) USB controller> on uhci4
usb5: USB revision 1.0
uhub5: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb5
uhub5: 2 ports with 2 removable, self powered
ehci1: <EHCI (generic) USB 2.0 controller> mem 0xff980800-0xff980bff irq
23 at device 29.7 on pci0
ehci1: [GIANT-LOCKED]
ehci1: [ITHREAD]
usb6: waiting for BIOS to give up control
usb6: timed out waiting for BIOS
usb6: EHCI version 1.0
usb6: companion controllers, 2 ports each: usb3 usb4 usb5
usb6: <EHCI (generic) USB 2.0 controller> on ehci1
usb6: USB revision 2.0
uhub6: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb6
uhub6: 6 ports with 6 removable, self powered
pcib3: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci3: <ACPI PCI bus> on pcib3
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci1: <Intel ICH9 SATA300 controller> port
0xfe00-0xfe07,0xfe10-0xfe13,0xfe20-0xfe27,0xfe30-0xfe33,0xfec0-0xfecf,0xeca0-0xecaf
irq 18 at device 31.2 on pci0
atapci1: [ITHREAD]
ata4: <ATA channel 0> on atapci1
ata4: [ITHREAD]
ata5: <ATA channel 1> on atapci1
ata5: [ITHREAD]
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
atapci2: <Intel ICH9 SATA300 controller> port
0xfe40-0xfe47,0xfe50-0xfe53,0xfe60-0xfe67,0xfe70-0xfe73,0xfed0-0xfedf,0xecb0-0xecbf
irq 18 at device 31.5 on pci0
atapci2: [ITHREAD]
ata6: <ATA channel 0> on atapci2
ata6: [ITHREAD]
ata7: <ATA channel 1> on atapci2
ata7: [ITHREAD]
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on
acpi0
sio0: type 16550A
sio0: [FILTER]
cpu0: <ACPI CPU> on acpi0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 724072406000724
device_attach: est0 attach returned 6
p4tcc0: <CPU Frequency Thermal Control> on cpu0
cpu1: <ACPI CPU> on acpi0
est1: <Enhanced SpeedStep Frequency Control> on cpu1
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 724072406000724
device_attach: est1 attach returned 6
p4tcc1: <CPU Frequency Thermal Control> on cpu1
orm0: <ISA Option ROMs> at iomem
0xc0000-0xcb7ff,0xcb800-0xcd7ff,0xcd800-0xcffff on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Timecounters tick every 1.000 msec
ad8: 152587MB <WDC WD1600AAJS-75PSA0 05.06H05> at ata4-master SATA300
ad9: 1430799MB <WDC WD15EADS-00R6B0 01.00A01> at ata4-slave SATA300



From dan.naumov at gmail.com  Fri Jul 10 18:50:11 2009
From: dan.naumov at gmail.com (Dan Naumov)
Date: Fri Jul 10 18:50:22 2009
Subject: Error when using 'portupgrade -ay'.
In-Reply-To: <63e02e980907101100o5c9e0ca1uaba843be033f8869@mail.gmail.com>
References: <63e02e980907101100o5c9e0ca1uaba843be033f8869@mail.gmail.com>
Message-ID: <cf9b1ee00907101150y276ed211t9c1f9112fe032302@mail.gmail.com>

On Fri, Jul 10, 2009 at 9:00 PM, Jens Rasmus Liland<jensrasmus@gmail.com> wrote:
> Hello!
>
> I had an error just now running 'portupgrade -ay'. Got this output:
>
> ---OUTPUT START---
>
> ---> ?Session started at: Fri, 10 Jul 2009 18:58:30 +0200
> ** Port directory not found: x11-drivers/xf86-video-vga
> ** Port marked as IGNORE: x11-drivers/xf86-video-via:
> ? ?requires pciVideoPtr typedef
> ** Port directory not found: x11/xorg-protos
> ** Port directory not found: x11/xphelloworld
> ---> ?Skipping 'x11-drivers/xorg-drivers' (xorg-drivers-7.3_3) because a
> requisite package 'xf86-video-vga-4.1.0_2' (x11-drivers/xf86-video-vga)
> failed (specify -k to force)
> ---> ?** Upgrade tasks 3: 0 done, 4 ignored, 1 skipped and 0 failed
> ---> ?Skipping 'x11/xorg-apps' (xorg-apps-7.3) because a requisite package
> 'xphelloworld-1.0.1_1' (x11/xphelloworld) failed (specify -k to force)
> ---> ?** Upgrade tasks 3: 0 done, 4 ignored, 2 skipped and 0 failed
> ---> ?Skipping 'x11/xorg' (xorg-7.3_2) because a requisite package
> 'xorg-drivers-7.3_3' (x11-drivers/xorg-drivers) failed (specify -k to force)
> ---> ?** Upgrade tasks 3: 0 done, 4 ignored, 3 skipped and 0 failed
> ---> ?Listing the results (+:done / -:ignored / *:skipped / !:failed)
> ? ?- x11-drivers/xf86-video-vga (port directory error)
> ? ?- x11-drivers/xf86-video-via (marked as IGNORE)
> ? ?- x11/xorg-protos (port directory error)
> ? ?- x11/xphelloworld (port directory error)
> ? ?* x11-drivers/xorg-drivers (xorg-drivers-7.3_3)
> ? ?* x11/xorg-apps (xorg-apps-7.3)
> ? ?* x11/xorg (xorg-7.3_2)
> ---> ?Packages processed: 0 done, 4 ignored, 3 skipped and 0 failed
> ---> ?Session ended at: Fri, 10 Jul 2009 18:58:46 +0200 (consumed 00:00:15)
>
> ---OUTPUT STOP---
>
> I've never got an error like this. What am I to do to make it work correctly
> again?

What is the method you use for updating your ports tree? What happens
if you nuke /usr/ports from orbit and run: "portsnap fetch; portsnap
extract" and try running 'portupgrade -ay' again?

- Sincerely,
Dan Naumov
From attilio at freebsd.org  Fri Jul 10 20:49:40 2009
From: attilio at freebsd.org (Attilio Rao)
Date: Fri Jul 10 20:49:48 2009
Subject: smbfs panic when lost connection or unmount --force
In-Reply-To: <6101e8c40907100801r382ded4boddd853f771867bd0@mail.gmail.com>
References: <6101e8c40907091755n5aefe289r6eec14cf7f4287dc@mail.gmail.com>
	<alpine.BSF.2.00.0907101209350.10745@fledge.watson.org>
	<6101e8c40907100801r382ded4boddd853f771867bd0@mail.gmail.com>
Message-ID: <3bbf2fe10907101349t64bc0acav371498aed580b6bd@mail.gmail.com>

2009/7/10 Oliver Pinter <oliver.pntr@gmail.com>:
> Hello!
>
> Here is the bt:
> http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01845.JPG
> http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01846.JPG
> http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01847.JPG

Could you please add in this informations registers state and locked vnodes?

Thanks,
Attilio


-- 
Peace can only be achieved by understanding - A. Einstein
From oliver.pntr at gmail.com  Fri Jul 10 22:01:55 2009
From: oliver.pntr at gmail.com (Oliver Pinter)
Date: Fri Jul 10 22:02:02 2009
Subject: smbfs panic when lost connection or unmount --force
In-Reply-To: <3bbf2fe10907101349t64bc0acav371498aed580b6bd@mail.gmail.com>
References: <6101e8c40907091755n5aefe289r6eec14cf7f4287dc@mail.gmail.com>
	<alpine.BSF.2.00.0907101209350.10745@fledge.watson.org>
	<6101e8c40907100801r382ded4boddd853f771867bd0@mail.gmail.com>
	<3bbf2fe10907101349t64bc0acav371498aed580b6bd@mail.gmail.com>
Message-ID: <6101e8c40907101501k36d757fch61b27f6a78a559d6@mail.gmail.com>

regs and vnodes:

http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01854.JPG
http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01855.JPG
http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01856.JPG
http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01857.JPG
http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01858.JPG
http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01859.JPG
http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01860.JPG

On 7/10/09, Attilio Rao <attilio@freebsd.org> wrote:
> 2009/7/10 Oliver Pinter <oliver.pntr@gmail.com>:
>> Hello!
>>
>> Here is the bt:
>> http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01845.JPG
>> http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01846.JPG
>> http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01847.JPG
>
> Could you please add in this informations registers state and locked
> vnodes?
>
> Thanks,
> Attilio
>
>
> --
> Peace can only be achieved by understanding - A. Einstein
>
From qing.li at bluecoat.com  Fri Jul 10 22:03:25 2009
From: qing.li at bluecoat.com (Li, Qing)
Date: Fri Jul 10 22:03:32 2009
Subject: 8.0-BETA1 - for the record - different paths followed by IPv4
	and IPv6 for 'local' connections
References: <4A5734C3.3000806@restart.be>
Message-ID: <B583FBF374231F4A89607B4D08578A4304673660@bcs-mail03.internal.cacheflow.com>


Hi,

Please try patch-7-10 in my home directory http://people.freebsd.org/~qingli/
and let me know how it works out for you. I thought I had committed the patch 
but turned out I didn't.

>
> On 8.0-BETA1 there is an assymetry:
>
> netstat -rn display
> 
> 192.168.24.1       link#3
> ....
> no entry for 2001:41d0:2:2d29:1:1::
> 

This is by design as part of the new architecture in 8.0, which maintains 
the L2 ARP/ND6 and L3 routing tables separately.

-- Qing



-----Original Message-----
From: owner-freebsd-stable@freebsd.org on behalf of Henri Hennebert
Sent: Fri 7/10/2009 5:32 AM
To: freebsd-stable@freebsd.org; freebsd-st@freebsd.org
Subject: 8.0-BETA1 - for the record - different paths followed by IPv4 and IPv6 for 'local' connections
 
Hello,

After upgrading from 7.2-STABLE to 8.0-BETA1 I encounter a problem when 
connecting with firefox to a local apache server using the global 
unicast IPv6 address of the local machine. pf.conf must be updated!

My configuration:

[root@avoriaz ~]# ifconfig em0

em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4>
	ether 00:1d:60:ad:2a:ce
	inet 192.168.24.1 netmask 0xffffff00 broadcast 192.168.24.255
	inet6 fe80::21d:60ff:fead:2ace%em0 prefixlen 64 scopeid 0x1
	inet6 2001:41d0:2:2d29:1:1:: prefixlen 80
	media: Ethernet 100baseTX (100baseTX <half-duplex>)
	status: active

[root@avoriaz ~]# host www.restart.bel
www.restart.bel is an alias for avoriaz.restart.bel.
avoriaz.restart.bel has address 192.168.24.1
avoriaz.restart.bel has IPv6 address 2001:41d0:2:2d29:1:1::

pf.conf:

int_if="em0"
block in  log all
block out log all
set skip on lo0
antispoof quick for $int_if inet
# Allow trafic with physical internal network
pass in quick on $int_if from ($int_if:network) to ($int_if) keep state
pass out quick on $int_if from ($int_if) to ($int_if:network) keep state

The problem:

[root@avoriaz ~]# telnet -4 www.restart.bel 80
Trying 192.168.24.1...
Connected to avoriaz.restart.bel.
Escape character is '^]'.
^]
telnet> quit
Connection closed.
[root@avoriaz ~]# telnet -6 www.restart.bel 80
Trying 2001:41d0:2:2d29:1:1::...
--->Never connect and get a timeout!

tcpdump and logging in pf show me that

For a IPv4 connection:
the packet from telnet to apache pass 2 times on lo0 (out and in)
the answer packet from apache to telnet pass 2 times on lo0 (out and in)

So no problem, there is `set skip on lo0'

For a IPv6 connection:
The first packet from telnet to apache pass 2 times on lo0 (out and in)
The answer packet from apache to telnet path on em0  and is rejected
due to the default flags S/SA.

So I have to change pf.conf and replace the last line:
pass out quick on $int_if from ($int_if) to ($int_if:network) \
keep state flags any

Then all is OK

By the way, on 7.2

netstat -rn display

192.168.24.1        00:1d:60:ad:2a:ce
....
2001:41d0:2:2d29:1:1::            00:1d:60:ad:2a:ce


On 8.0-BETA1 there is an assymetry:

netstat -rn display

192.168.24.1       link#3
....
no entry for 2001:41d0:2:2d29:1:1::

Hope it may help someone

Henri

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

From attilio at freebsd.org  Sat Jul 11 00:58:38 2009
From: attilio at freebsd.org (Attilio Rao)
Date: Sat Jul 11 00:58:45 2009
Subject: smbfs panic when lost connection or unmount --force
In-Reply-To: <6101e8c40907101501k36d757fch61b27f6a78a559d6@mail.gmail.com>
References: <6101e8c40907091755n5aefe289r6eec14cf7f4287dc@mail.gmail.com>
	<alpine.BSF.2.00.0907101209350.10745@fledge.watson.org>
	<6101e8c40907100801r382ded4boddd853f771867bd0@mail.gmail.com>
	<3bbf2fe10907101349t64bc0acav371498aed580b6bd@mail.gmail.com>
	<6101e8c40907101501k36d757fch61b27f6a78a559d6@mail.gmail.com>
Message-ID: <3bbf2fe10907101758x81d926bo5eb9f5adb9c80e25@mail.gmail.com>

2009/7/11 Oliver Pinter <oliver.pntr@gmail.com>:
> regs and vnodes:
>
> http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01854.JPG
> http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01855.JPG
> http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01856.JPG
> http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01857.JPG
> http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01858.JPG
> http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01859.JPG
> http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01860.JPG

Sorry, maybe I wasn't clear, you should spell them 'lockedvnods'.

Thanks,
Attilio



-- 
Peace can only be achieved by understanding - A. Einstein
From peterjeremy at optushome.com.au  Sat Jul 11 08:40:46 2009
From: peterjeremy at optushome.com.au (Peter Jeremy)
Date: Sat Jul 11 08:40:53 2009
Subject: ZFS - thanks
In-Reply-To: <cf9b1ee00907090539i70bf97eq32fe0aa960e9dc52@mail.gmail.com>
References: <20090709112512.GA44158@hugo10.ka.punkt.de>
	<73a41d4b72d62b0bfe3d0fb7206376a8.squirrel@cygnus.homeunix.com>
	<cf9b1ee00907090525t7a337775q71aa01e6a3173de5@mail.gmail.com>
	<84665df87e93a6ccf24d9837cbc53eba.squirrel@cygnus.homeunix.com>
	<cf9b1ee00907090539i70bf97eq32fe0aa960e9dc52@mail.gmail.com>
Message-ID: <20090711084042.GA77702@server.vk2pj.dyndns.org>

On 2009-Jul-09 15:39:35 +0300, Dan Naumov <dan.naumov@gmail.com> wrote:
>A single 40 disk raidz (DO NOT DO THIS) will have 40 disks total, 39
>disks worth of space and will definately explode on you sooner rather
>than later (probably on the first import, export or scrub).

Can you provide a reference for this statement.  AFAIK, the only
reason for the upper recommended limit of 9 disks is performance.

-- 
Peter Jeremy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090711/eff18dbf/attachment.pgp
From dan.naumov at gmail.com  Sat Jul 11 08:44:10 2009
From: dan.naumov at gmail.com (Dan Naumov)
Date: Sat Jul 11 08:44:17 2009
Subject: ZFS - thanks
In-Reply-To: <20090711084042.GA77702@server.vk2pj.dyndns.org>
References: <20090709112512.GA44158@hugo10.ka.punkt.de>
	<73a41d4b72d62b0bfe3d0fb7206376a8.squirrel@cygnus.homeunix.com>
	<cf9b1ee00907090525t7a337775q71aa01e6a3173de5@mail.gmail.com>
	<84665df87e93a6ccf24d9837cbc53eba.squirrel@cygnus.homeunix.com>
	<cf9b1ee00907090539i70bf97eq32fe0aa960e9dc52@mail.gmail.com>
	<20090711084042.GA77702@server.vk2pj.dyndns.org>
Message-ID: <cf9b1ee00907110144g3c9bfc5dn911df4a15167e537@mail.gmail.com>

On Sat, Jul 11, 2009 at 11:40 AM, Peter
Jeremy<peterjeremy@optushome.com.au> wrote:
> On 2009-Jul-09 15:39:35 +0300, Dan Naumov <dan.naumov@gmail.com> wrote:
>>A single 40 disk raidz (DO NOT DO THIS) will have 40 disks total, 39
>>disks worth of space and will definately explode on you sooner rather
>>than later (probably on the first import, export or scrub).
>
> Can you provide a reference for this statement. ?AFAIK, the only
> reason for the upper recommended limit of 9 disks is performance.
>
> --
> Peter Jeremy

Searching the different FreeBSD mailing lists (which have had
discussions about such cases) and googling should yield results.

- Sincerely,
Dan Naumov
From hlh at restart.be  Sat Jul 11 10:09:50 2009
From: hlh at restart.be (Henri Hennebert)
Date: Sat Jul 11 10:09:57 2009
Subject: 8.0-BETA1 - for the record - different paths followed by IPv4
 and IPv6 for 'local' connections
In-Reply-To: <B583FBF374231F4A89607B4D08578A4304673660@bcs-mail03.internal.cacheflow.com>
References: <4A5734C3.3000806@restart.be>
	<B583FBF374231F4A89607B4D08578A4304673660@bcs-mail03.internal.cacheflow.com>
Message-ID: <4A5864DC.1070106@restart.be>

Li, Qing wrote:
> Hi,
> 
> Please try patch-7-10 in my home directory http://people.freebsd.org/~qingli/
> and let me know how it works out for you. I thought I had committed the patch 
> but turned out I didn't.

I apply the patch, reset my pf.conf to its previous content and all is 
running smoothly. By the way, I discover after my post that my 
"solution" was not working for long (many bytes) connections and this is 
solved too.

Many thank for your time

Henri

PS please commit as soon as possible

> 
>> On 8.0-BETA1 there is an assymetry:
>>
>> netstat -rn display
>>
>> 192.168.24.1       link#3
>> ....
>> no entry for 2001:41d0:2:2d29:1:1::
>>
> 
> This is by design as part of the new architecture in 8.0, which maintains 
> the L2 ARP/ND6 and L3 routing tables separately.
> 
> -- Qing
> 
> 
> 
> -----Original Message-----
> From: owner-freebsd-stable@freebsd.org on behalf of Henri Hennebert
> Sent: Fri 7/10/2009 5:32 AM
> To: freebsd-stable@freebsd.org; freebsd-st@freebsd.org
> Subject: 8.0-BETA1 - for the record - different paths followed by IPv4 and IPv6 for 'local' connections
>  
> Hello,
> 
> After upgrading from 7.2-STABLE to 8.0-BETA1 I encounter a problem when 
> connecting with firefox to a local apache server using the global 
> unicast IPv6 address of the local machine. pf.conf must be updated!
> 
> My configuration:
> 
> [root@avoriaz ~]# ifconfig em0
> 
> em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
> 	options=19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4>
> 	ether 00:1d:60:ad:2a:ce
> 	inet 192.168.24.1 netmask 0xffffff00 broadcast 192.168.24.255
> 	inet6 fe80::21d:60ff:fead:2ace%em0 prefixlen 64 scopeid 0x1
> 	inet6 2001:41d0:2:2d29:1:1:: prefixlen 80
> 	media: Ethernet 100baseTX (100baseTX <half-duplex>)
> 	status: active
> 
> [root@avoriaz ~]# host www.restart.bel
> www.restart.bel is an alias for avoriaz.restart.bel.
> avoriaz.restart.bel has address 192.168.24.1
> avoriaz.restart.bel has IPv6 address 2001:41d0:2:2d29:1:1::
> 
> pf.conf:
> 
> int_if="em0"
> block in  log all
> block out log all
> set skip on lo0
> antispoof quick for $int_if inet
> # Allow trafic with physical internal network
> pass in quick on $int_if from ($int_if:network) to ($int_if) keep state
> pass out quick on $int_if from ($int_if) to ($int_if:network) keep state
> 
> The problem:
> 
> [root@avoriaz ~]# telnet -4 www.restart.bel 80
> Trying 192.168.24.1...
> Connected to avoriaz.restart.bel.
> Escape character is '^]'.
> ^]
> telnet> quit
> Connection closed.
> [root@avoriaz ~]# telnet -6 www.restart.bel 80
> Trying 2001:41d0:2:2d29:1:1::...
> --->Never connect and get a timeout!
> 
> tcpdump and logging in pf show me that
> 
> For a IPv4 connection:
> the packet from telnet to apache pass 2 times on lo0 (out and in)
> the answer packet from apache to telnet pass 2 times on lo0 (out and in)
> 
> So no problem, there is `set skip on lo0'
> 
> For a IPv6 connection:
> The first packet from telnet to apache pass 2 times on lo0 (out and in)
> The answer packet from apache to telnet path on em0  and is rejected
> due to the default flags S/SA.
> 
> So I have to change pf.conf and replace the last line:
> pass out quick on $int_if from ($int_if) to ($int_if:network) \
> keep state flags any
> 
> Then all is OK
> 
> By the way, on 7.2
> 
> netstat -rn display
> 
> 192.168.24.1        00:1d:60:ad:2a:ce
> ....
> 2001:41d0:2:2d29:1:1::            00:1d:60:ad:2a:ce
> 
> 
> On 8.0-BETA1 there is an assymetry:
> 
> netstat -rn display
> 
> 192.168.24.1       link#3
> ....
> no entry for 2001:41d0:2:2d29:1:1::
> 
> Hope it may help someone
> 
> Henri
> 
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
> 

From dimitry at andric.com  Sat Jul 11 14:15:29 2009
From: dimitry at andric.com (Dimitry Andric)
Date: Sat Jul 11 14:15:36 2009
Subject: ZFS - thanks
In-Reply-To: <20090711084042.GA77702@server.vk2pj.dyndns.org>
References: <20090709112512.GA44158@hugo10.ka.punkt.de>	<73a41d4b72d62b0bfe3d0fb7206376a8.squirrel@cygnus.homeunix.com>	<cf9b1ee00907090525t7a337775q71aa01e6a3173de5@mail.gmail.com>	<84665df87e93a6ccf24d9837cbc53eba.squirrel@cygnus.homeunix.com>	<cf9b1ee00907090539i70bf97eq32fe0aa960e9dc52@mail.gmail.com>
	<20090711084042.GA77702@server.vk2pj.dyndns.org>
Message-ID: <4A589E80.10901@andric.com>

On 2009-07-11 10:40, Peter Jeremy wrote:
> On 2009-Jul-09 15:39:35 +0300, Dan Naumov <dan.naumov@gmail.com> wrote:
>> A single 40 disk raidz (DO NOT DO THIS) will have 40 disks total, 39
>> disks worth of space and will definately explode on you sooner rather
>> than later (probably on the first import, export or scrub).
> 
> Can you provide a reference for this statement.  AFAIK, the only
> reason for the upper recommended limit of 9 disks is performance.

The more disks you use in one RAID set, the higher the probability that
more than one disk will fail at the same time.  An interesting read can
be found here: http://blogs.zdnet.com/storage/?p=162
From oliver.pntr at gmail.com  Sat Jul 11 14:48:32 2009
From: oliver.pntr at gmail.com (Oliver Pinter)
Date: Sat Jul 11 14:48:39 2009
Subject: smbfs panic when lost connection or unmount --force
In-Reply-To: <3bbf2fe10907101758x81d926bo5eb9f5adb9c80e25@mail.gmail.com>
References: <6101e8c40907091755n5aefe289r6eec14cf7f4287dc@mail.gmail.com>
	<alpine.BSF.2.00.0907101209350.10745@fledge.watson.org>
	<6101e8c40907100801r382ded4boddd853f771867bd0@mail.gmail.com>
	<3bbf2fe10907101349t64bc0acav371498aed580b6bd@mail.gmail.com>
	<6101e8c40907101501k36d757fch61b27f6a78a559d6@mail.gmail.com>
	<3bbf2fe10907101758x81d926bo5eb9f5adb9c80e25@mail.gmail.com>
Message-ID: <6101e8c40907110748n602a03frb3519abe2e251d72@mail.gmail.com>

the good vnods

On 7/11/09, Attilio Rao <attilio@freebsd.org> wrote:
> 2009/7/11 Oliver Pinter <oliver.pntr@gmail.com>:
>> regs and vnodes:
>>
>> http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01854.JPG
>> http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01855.JPG
>> http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01856.JPG
>> http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01857.JPG
>> http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01858.JPG
>> http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01859.JPG
>> http://centaur.sch.bme.hu/~oliverp/freebsd/smbfs_panic/DSC01860.JPG
>
> Sorry, maybe I wasn't clear, you should spell them 'lockedvnods'.
>
> Thanks,
> Attilio
>
>
>
> --
> Peace can only be achieved by understanding - A. Einstein
>
From ronald-freebsd8 at klop.yi.org  Sat Jul 11 15:05:15 2009
From: ronald-freebsd8 at klop.yi.org (Ronald Klop)
Date: Sat Jul 11 15:05:27 2009
Subject: Zfs on usb-disk checksum errors?
In-Reply-To: <4A54727D.9080205@restart.be>
References: <op.uwqpe0sn8527sy@82-170-177-25.ip.telfort.nl>
	<4A54727D.9080205@restart.be>
Message-ID: <op.uwwr6xed8527sy@82-170-177-25.ip.telfort.nl>

On Wed, 08 Jul 2009 12:18:37 +0200, Henri Hennebert <hlh@restart.be> wrote:

> Ronald Klop wrote:
>> Hi.
>>  I put zfs on my external usb-disk, so I can backup my harddisk with  
>> zfs send/receive.
>> I now have corruption on this volume.
>>  [root@sjakie ~]# zpool status -v
>>   pool: extern
>>  state: ONLINE
>> status: One or more devices has experienced an error resulting in data
>>         corruption.  Applications may be affected.
>> action: Restore the file in question if possible.  Otherwise restore the
>>         entire pool from backup.
>>    see: http://www.sun.com/msg/ZFS-8000-8A
>>  scrub: scrub completed after 0h2m with 0 errors on Wed Jul  8 00:35:09  
>> 2009
>> config:
>>          NAME        STATE     READ WRITE CKSUM
>>         extern      ONLINE       1     0     0
>>           da0       ONLINE       9     0     0
>>  errors: Permanent errors have been detected in the following files:
>>          <0x3f>:<0xf5d6>
>>  I don't really understand which files have corruption. :-(
>> In my syslog is this: (repeated quite often)
>> Jul  8 10:00:37 sjakie kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE  
>> CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0
>> Jul  8 10:00:37 sjakie kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI  
>> Status Error
>> Jul  8 10:00:37 sjakie kernel: (da0:umass-sim0:0:0:0): SCSI Status:  
>> Check Condition
>> Jul  8 10:00:37 sjakie kernel: (da0:umass-sim0:0:0:0): ILLEGAL REQUEST  
>> asc:20,0
>> Jul  8 10:00:37 sjakie kernel: (da0:umass-sim0:0:0:0): Invalid command  
>> operation code
>> Jul  8 10:00:37 sjakie kernel: (da0:umass-sim0:0:0:0): Unretryable error
>>
> I experience the same error with 'Kingston DataTraveler II 1.13'. I  
> simply add in /usr/src/sys/dev/usb/usbdevs:
>
> product KINGSTON DATATRAVELER_2 0x1600 DAtaTraveler II
>
> (VENDOR was already in the file).
>
> and  in sys/dev/usb/storage/umass.c:
>
>             { USB_VENDOR_KINGSTON, USB_PRODUCT_KINGSTON_DATATRAVELER_2,  
> RID_WILDCARD,               UMASS_PROTO_SCSI | UMASS_PROTO_BBB,   
>               NO_SYNCHRONIZE_CACHE              },  
> Note the flag NO_SYNCHRONIZE_CACHE and everything return to normal.
>
> PS - I encounter this problem on 7.2_STABLE with the MFC of ZFS v13.
>
> Henri

Thanks a lot. I owe you a beer! It works great now.

Ronald.
From cperciva at freebsd.org  Sat Jul 11 16:10:10 2009
From: cperciva at freebsd.org (Colin Percival)
Date: Sat Jul 11 16:10:23 2009
Subject: FreeBSD 8.0-BETA1 available via FreeBSD Update
Message-ID: <4A58B960.8050204@freebsd.org>

Hi all,

The FreeBSD Update bits for FreeBSD 8.0-BETA1 are now available.  Sorry for
the delay.

I've posted a step-by-step guide to my blog at
   http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html
and I'm asking people to leave comments on that page if they encounter any
problems -- I'm aware of two systems already which didn't manage to reboot after
installing 8.0-BETA1 kernels, so this is definitely a case of "here be dragons".

-- 
Colin Percival
Security Officer, FreeBSD | freebsd.org | The power to serve
Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid
From fjwcash at gmail.com  Sat Jul 11 20:07:55 2009
From: fjwcash at gmail.com (Freddie Cash)
Date: Sat Jul 11 20:08:02 2009
Subject: ZFS - thanks
In-Reply-To: <20090711084042.GA77702@server.vk2pj.dyndns.org>
References: <20090709112512.GA44158@hugo10.ka.punkt.de>
	<73a41d4b72d62b0bfe3d0fb7206376a8.squirrel@cygnus.homeunix.com>
	<cf9b1ee00907090525t7a337775q71aa01e6a3173de5@mail.gmail.com>
	<84665df87e93a6ccf24d9837cbc53eba.squirrel@cygnus.homeunix.com>
	<cf9b1ee00907090539i70bf97eq32fe0aa960e9dc52@mail.gmail.com>
	<20090711084042.GA77702@server.vk2pj.dyndns.org>
Message-ID: <b269bc570907111307y6d0f33a8g440a0f7d34367260@mail.gmail.com>

On Sat, Jul 11, 2009 at 1:40 AM, Peter Jeremy
<peterjeremy@optushome.com.au>wrote:

> On 2009-Jul-09 15:39:35 +0300, Dan Naumov <dan.naumov@gmail.com> wrote:
> >A single 40 disk raidz (DO NOT DO THIS) will have 40 disks total, 39
> >disks worth of space and will definately explode on you sooner rather
> >than later (probably on the first import, export or scrub).
>
> Can you provide a reference for this statement.  AFAIK, the only
> reason for the upper recommended limit of 9 disks is performance.
>

We found it impossible to re-silver a new/replacement drive in a 24-drive
raidz2 vdev.  Even after almost two weeks of trying, it never got above
20-30% complete before restarting.

That led me to do a bunch of web searches, and found several blogs by Sun
people that went over how the raidz implementation works, what the
limitations are (limited to the IOps of a single drive), and the
recommendation to never use more than 8 or 9 drives in any single vdev.

-- 
Freddie Cash
fjwcash@gmail.com
From rwatson at freebsd.org  Sun Jul 12 19:18:19 2009
From: rwatson at freebsd.org (Robert N. M. Watson)
Date: Sun Jul 12 19:18:26 2009
Subject: smbfs panic when lost connection or unmount --force
In-Reply-To: <6101e8c40907100517q2d2e5891m62b0b7d57496b10@mail.gmail.com>
References: <6101e8c40907091755n5aefe289r6eec14cf7f4287dc@mail.gmail.com>
	<alpine.BSF.2.00.0907101209350.10745@fledge.watson.org>
	<6101e8c40907100517q2d2e5891m62b0b7d57496b10@mail.gmail.com>
Message-ID: <E68D3F39-5E26-43C3-A2A7-C0425B605309@freebsd.org>


On 10 Jul 2009, at 13:17, Oliver Pinter wrote:

> I know, that the bt is useful, but ddb works with usb keyboard?
> At nigth then I send the log.

Unfortunately, a known issue with FreeBSD 8.0 is that the new USB  
stack, while a vast improvement over the previous USB stack in  
countless ways, does not support polled access from DDB. You will need  
to use a serial port, firewire port, ps/2, or AT keyboard in order to  
get interactive DDB support.

If that's not feasible, or if it's just easier, you may be able to use  
the DDB scripting facility + textdumps to run DDB commands  
automatically on panic to produce useful debugging output. Take a look  
at the textdump(4) man page for details. This can be combined with a  
traditional crashdump to capture both DDB output and normal dump data  
for use with kgdb.

Robert

>
> //sorry for bad english
>
> ps.: attached the config
>
> On 7/10/09, Robert Watson <rwatson@freebsd.org> wrote:
>>
>> On Fri, 10 Jul 2009, Oliver Pinter wrote:
>>
>>> It is a kernel panic, when force unmount the smbfs volume or lost  
>>> the
>>> connection with the samba server.
>>
>> This is a NULL pointer dereference in the kernel.  Per Attilio's e- 
>> mail, a
>> stack trace should help us track it down.  Thanks!
>>
>> Robert N M Watson
>> Computer Laboratory
>> University of Cambridge
>>
>>>
>>> --
>>> Thes OS is:
>>>
>>>
>>> kern.ostype: FreeBSD
>>> kern.osrelease: 7.2-STABLE
>>> kern.osrevision: 199506
>>> kern.version: FreeBSD 7.2-STABLE #4: Sat Jun 27 21:44:32 CEST 2009
>>>   root@oliverp:/usr/obj/usr/src/sys/stable
>>> kern.osreldate: 702103
>>>
>>> --
>>> make.conf:
>>>
>>>
>>> CPUTYPE?=core2
>>> CFLAGS= -O2 -fno-strict-aliasing -pipe
>>> MODULES_OVERRIDE=smbfs libiconv libmchain zfs opensolaris drm cd9660
>>> cd9660_iconv
>>>
>>> --
>>> panic message:
>>>
>>> Jul 10 01:58:39 oliverp syslogd: kernel boot file is /boot/kernel/ 
>>> kernel
>>> Jul 10 01:58:39 oliverp kernel: kernel trap 12 with interrupts  
>>> disabled
>>> Jul 10 01:58:39 oliverp kernel:
>>> Jul 10 01:58:39 oliverp kernel:
>>> Jul 10 01:58:39 oliverp kernel: Fatal trap 12: page fault while in  
>>> kernel
>>> mode
>>> Jul 10 01:58:39 oliverp kernel: cpuid = 2; apic id = 02
>>> Jul 10 01:58:39 oliverp kernel: fault virtual address	= 0x30
>>> Jul 10 01:58:39 oliverp kernel: fault code		= supervisor read data,
>>> page not present
>>> Jul 10 01:58:39 oliverp kernel: instruction pointer	=
>>> 0x8:0xffffffff80327fd0
>>> Jul 10 01:58:39 oliverp kernel: stack pointer	        =
>>> 0x10:0xffffff8078360940
>>> Jul 10 01:58:39 oliverp kernel: frame pointer	        =
>>> 0x10:0xffffff0004c31390
>>> Jul 10 01:58:39 oliverp kernel: code segment		= base 0x0, limit
>>> 0xfffff, type 0x1b
>>> Jul 10 01:58:39 oliverp kernel: = DPL 0, pres 1, long 1, def32 0,  
>>> gran 1
>>> Jul 10 01:58:39 oliverp kernel: processor eflags	= resume, IOPL = 0
>>> Jul 10 01:58:39 oliverp kernel: current process		= 60406 (smbiod0)
>>> Jul 10 01:58:39 oliverp kernel: trap number		= 12
>>> Jul 10 01:58:39 oliverp kernel: panic: page fault
>>> Jul 10 01:58:39 oliverp kernel: cpuid = 2
>>> Jul 10 01:58:39 oliverp kernel: Uptime: 6h51m16s
>>> Jul 10 01:58:39 oliverp kernel: Physical memory: 4087 MB
>>> Jul 10 01:58:39 oliverp kernel: Dumping 2448 MB:Copyright (c)
>>> 1992-2009 The FreeBSD Project.
>>> _______________________________________________
>>> freebsd-stable@freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org 
>>> "
>>>
>>
> <kernel_conf.txt>

From qing.li at bluecoat.com  Sun Jul 12 19:28:30 2009
From: qing.li at bluecoat.com (Li, Qing)
Date: Sun Jul 12 19:28:42 2009
Subject: 8.0-BETA1 - for the record - different paths followed by IPv4
	and IPv6 for 'local' connections
References: <4A5734C3.3000806@restart.be>
	<B583FBF374231F4A89607B4D08578A4304673660@bcs-mail03.internal.cacheflow.com>
	<4A5864DC.1070106@restart.be>
Message-ID: <B583FBF374231F4A89607B4D08578A4304673665@bcs-mail03.internal.cacheflow.com>


The patch has been committed, svn revision 195643.

Thanks,

-- Qing


-----Original Message-----
From: Henri Hennebert [mailto:hlh@restart.be]
Sent: Sat 7/11/2009 3:09 AM
To: Li, Qing
Cc: freebsd-stable@freebsd.org; freebsd-net@freebsd.org
Subject: Re: 8.0-BETA1 - for the record - different paths followed by IPv4 and IPv6 for 'local' connections
 
Li, Qing wrote:
> Hi,
> 
> Please try patch-7-10 in my home directory http://people.freebsd.org/~qingli/
> and let me know how it works out for you. I thought I had committed the patch 
> but turned out I didn't.

I apply the patch, reset my pf.conf to its previous content and all is 
running smoothly. By the way, I discover after my post that my 
"solution" was not working for long (many bytes) connections and this is 
solved too.

Many thank for your time

Henri

PS please commit as soon as possible

> 
>> On 8.0-BETA1 there is an assymetry:
>>
>> netstat -rn display
>>
>> 192.168.24.1       link#3
>> ....
>> no entry for 2001:41d0:2:2d29:1:1::
>>
> 
> This is by design as part of the new architecture in 8.0, which maintains 
> the L2 ARP/ND6 and L3 routing tables separately.
> 
> -- Qing
> 
> 
> 
> -----Original Message-----
> From: owner-freebsd-stable@freebsd.org on behalf of Henri Hennebert
> Sent: Fri 7/10/2009 5:32 AM
> To: freebsd-stable@freebsd.org; freebsd-st@freebsd.org
> Subject: 8.0-BETA1 - for the record - different paths followed by IPv4 and IPv6 for 'local' connections
>  
> Hello,
> 
> After upgrading from 7.2-STABLE to 8.0-BETA1 I encounter a problem when 
> connecting with firefox to a local apache server using the global 
> unicast IPv6 address of the local machine. pf.conf must be updated!
> 
> My configuration:
> 
> [root@avoriaz ~]# ifconfig em0
> 
> em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
> 	options=19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4>
> 	ether 00:1d:60:ad:2a:ce
> 	inet 192.168.24.1 netmask 0xffffff00 broadcast 192.168.24.255
> 	inet6 fe80::21d:60ff:fead:2ace%em0 prefixlen 64 scopeid 0x1
> 	inet6 2001:41d0:2:2d29:1:1:: prefixlen 80
> 	media: Ethernet 100baseTX (100baseTX <half-duplex>)
> 	status: active
> 
> [root@avoriaz ~]# host www.restart.bel
> www.restart.bel is an alias for avoriaz.restart.bel.
> avoriaz.restart.bel has address 192.168.24.1
> avoriaz.restart.bel has IPv6 address 2001:41d0:2:2d29:1:1::
> 
> pf.conf:
> 
> int_if="em0"
> block in  log all
> block out log all
> set skip on lo0
> antispoof quick for $int_if inet
> # Allow trafic with physical internal network
> pass in quick on $int_if from ($int_if:network) to ($int_if) keep state
> pass out quick on $int_if from ($int_if) to ($int_if:network) keep state
> 
> The problem:
> 
> [root@avoriaz ~]# telnet -4 www.restart.bel 80
> Trying 192.168.24.1...
> Connected to avoriaz.restart.bel.
> Escape character is '^]'.
> ^]
> telnet> quit
> Connection closed.
> [root@avoriaz ~]# telnet -6 www.restart.bel 80
> Trying 2001:41d0:2:2d29:1:1::...
> --->Never connect and get a timeout!
> 
> tcpdump and logging in pf show me that
> 
> For a IPv4 connection:
> the packet from telnet to apache pass 2 times on lo0 (out and in)
> the answer packet from apache to telnet pass 2 times on lo0 (out and in)
> 
> So no problem, there is `set skip on lo0'
> 
> For a IPv6 connection:
> The first packet from telnet to apache pass 2 times on lo0 (out and in)
> The answer packet from apache to telnet path on em0  and is rejected
> due to the default flags S/SA.
> 
> So I have to change pf.conf and replace the last line:
> pass out quick on $int_if from ($int_if) to ($int_if:network) \
> keep state flags any
> 
> Then all is OK
> 
> By the way, on 7.2
> 
> netstat -rn display
> 
> 192.168.24.1        00:1d:60:ad:2a:ce
> ....
> 2001:41d0:2:2d29:1:1::            00:1d:60:ad:2a:ce
> 
> 
> On 8.0-BETA1 there is an assymetry:
> 
> netstat -rn display
> 
> 192.168.24.1       link#3
> ....
> no entry for 2001:41d0:2:2d29:1:1::
> 
> Hope it may help someone
> 
> Henri
> 
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
> 


From amarat at ksu.ru  Sun Jul 12 20:00:26 2009
From: amarat at ksu.ru (Marat N.Afanasyev)
Date: Sun Jul 12 20:00:34 2009
Subject: bug in ufs?
In-Reply-To: <4A50E947.9020608@ksu.ru>
References: <4A50E947.9020608@ksu.ru>
Message-ID: <4A5A40A3.1080202@ksu.ru>

Marat N.Afanasyev wrote:

> 
> all i want to know is whether this is a bug or a feature? and if such a 
> behavior is well-known, where can i read about it?
> 

thanks everybody, i have resolved this as my misunderstanding of UFS 
basics, so it was pretty good lesson for me :)

-- 
SY, Marat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3221 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090712/833c858a/smime.bin
From oliver.pntr at gmail.com  Sun Jul 12 20:21:12 2009
From: oliver.pntr at gmail.com (Oliver Pinter)
Date: Sun Jul 12 20:21:19 2009
Subject: smbfs panic when lost connection or unmount --force
In-Reply-To: <E68D3F39-5E26-43C3-A2A7-C0425B605309@freebsd.org>
References: <6101e8c40907091755n5aefe289r6eec14cf7f4287dc@mail.gmail.com>
	<alpine.BSF.2.00.0907101209350.10745@fledge.watson.org>
	<6101e8c40907100517q2d2e5891m62b0b7d57496b10@mail.gmail.com>
	<E68D3F39-5E26-43C3-A2A7-C0425B605309@freebsd.org>
Message-ID: <6101e8c40907121321v3e307e06l27c318ed3956197@mail.gmail.com>

On 7/12/09, Robert N. M. Watson <rwatson@freebsd.org> wrote:
>
> On 10 Jul 2009, at 13:17, Oliver Pinter wrote:
>
>> I know, that the bt is useful, but ddb works with usb keyboard?
>> At nigth then I send the log.
>
> Unfortunately, a known issue with FreeBSD 8.0 is that the new USB
> stack, while a vast improvement over the previous USB stack in
> countless ways, does not support polled access from DDB. You will need
> to use a serial port, firewire port, ps/2, or AT keyboard in order to
> get interactive DDB support.
>
it worked with usb keyboard, the pictured and the last log is made
with usb keyboard..

> If that's not feasible, or if it's just easier, you may be able to use
> the DDB scripting facility + textdumps to run DDB commands
> automatically on panic to produce useful debugging output. Take a look
> at the textdump(4) man page for details. This can be combined with a
> traditional crashdump to capture both DDB output and normal dump data
> for use with kgdb.
jeah, I readed the man (ddb and textdump), and I used a small script..

>
> Robert
>

thanks for the help
>>
>> //sorry for bad english
>>
>> ps.: attached the config
>>
>> On 7/10/09, Robert Watson <rwatson@freebsd.org> wrote:
>>>
>>> On Fri, 10 Jul 2009, Oliver Pinter wrote:
>>>
>>>> It is a kernel panic, when force unmount the smbfs volume or lost
>>>> the
>>>> connection with the samba server.
>>>
>>> This is a NULL pointer dereference in the kernel.  Per Attilio's e-
>>> mail, a
>>> stack trace should help us track it down.  Thanks!
>>>
>>> Robert N M Watson
>>> Computer Laboratory
>>> University of Cambridge
>>>
>>>>
>>>> --
>>>> Thes OS is:
>>>>
>>>>
>>>> kern.ostype: FreeBSD
>>>> kern.osrelease: 7.2-STABLE
>>>> kern.osrevision: 199506
>>>> kern.version: FreeBSD 7.2-STABLE #4: Sat Jun 27 21:44:32 CEST 2009
>>>>   root@oliverp:/usr/obj/usr/src/sys/stable
>>>> kern.osreldate: 702103
>>>>
>>>> --
>>>> make.conf:
>>>>
>>>>
>>>> CPUTYPE?=core2
>>>> CFLAGS= -O2 -fno-strict-aliasing -pipe
>>>> MODULES_OVERRIDE=smbfs libiconv libmchain zfs opensolaris drm cd9660
>>>> cd9660_iconv
>>>>
>>>> --
>>>> panic message:
>>>>
>>>> Jul 10 01:58:39 oliverp syslogd: kernel boot file is /boot/kernel/
>>>> kernel
>>>> Jul 10 01:58:39 oliverp kernel: kernel trap 12 with interrupts
>>>> disabled
>>>> Jul 10 01:58:39 oliverp kernel:
>>>> Jul 10 01:58:39 oliverp kernel:
>>>> Jul 10 01:58:39 oliverp kernel: Fatal trap 12: page fault while in
>>>> kernel
>>>> mode
>>>> Jul 10 01:58:39 oliverp kernel: cpuid = 2; apic id = 02
>>>> Jul 10 01:58:39 oliverp kernel: fault virtual address	= 0x30
>>>> Jul 10 01:58:39 oliverp kernel: fault code		= supervisor read data,
>>>> page not present
>>>> Jul 10 01:58:39 oliverp kernel: instruction pointer	=
>>>> 0x8:0xffffffff80327fd0
>>>> Jul 10 01:58:39 oliverp kernel: stack pointer	        =
>>>> 0x10:0xffffff8078360940
>>>> Jul 10 01:58:39 oliverp kernel: frame pointer	        =
>>>> 0x10:0xffffff0004c31390
>>>> Jul 10 01:58:39 oliverp kernel: code segment		= base 0x0, limit
>>>> 0xfffff, type 0x1b
>>>> Jul 10 01:58:39 oliverp kernel: = DPL 0, pres 1, long 1, def32 0,
>>>> gran 1
>>>> Jul 10 01:58:39 oliverp kernel: processor eflags	= resume, IOPL = 0
>>>> Jul 10 01:58:39 oliverp kernel: current process		= 60406 (smbiod0)
>>>> Jul 10 01:58:39 oliverp kernel: trap number		= 12
>>>> Jul 10 01:58:39 oliverp kernel: panic: page fault
>>>> Jul 10 01:58:39 oliverp kernel: cpuid = 2
>>>> Jul 10 01:58:39 oliverp kernel: Uptime: 6h51m16s
>>>> Jul 10 01:58:39 oliverp kernel: Physical memory: 4087 MB
>>>> Jul 10 01:58:39 oliverp kernel: Dumping 2448 MB:Copyright (c)
>>>> 1992-2009 The FreeBSD Project.
>>>> _______________________________________________
>>>> freebsd-stable@freebsd.org mailing list
>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>>>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org
>>>>
>>>> "
>>>>
>>>
>> <kernel_conf.txt>
>
>
From exemys-mkt at exemys.com  Sun Jul 12 23:36:59 2009
From: exemys-mkt at exemys.com (Mkt-Exemys)
Date: Sun Jul 12 23:37:08 2009
Subject: Industrial Intelligent Wi-Fi (I2W)
Message-ID: <f429e26954849de1d3aa2828a9244c91@www.hostmailing.com>

This is a message in multipart MIME format.  Your mail client should not be displaying this. Consider upgrading your mail client to view this message correctly.

From grarpamp at gmail.com  Mon Jul 13 05:23:03 2009
From: grarpamp at gmail.com (grarpamp)
Date: Mon Jul 13 05:23:10 2009
Subject: FreeBSD RoadMap
Message-ID: <d2e731a10907122155v525691cdv236462d5227f3139@mail.gmail.com>

Is there a general roadmap of what's planned
for future major releases? I don't mean minor
stuff like driver or contributed version bumps.
But bigger, or just plain cool things, like as SMP,
soft updates, ZFS, netgraph, pf, etc, were in the past.

I poked around the website and  wiki a bit and didn't
see any sort of all in one document.

Some sort of dynamic non-binding wiki doc with direction
or work as to how the next two [or 3] majors after the
current one [8] would be interesting. And could be used
by those looking at investing in FreeBSD as a future
or continuing platform. Certainly core/committers have
thoughts on this that are publishable. Something so
people can see where all the projects fit into the whole.
From andrew-freebsd at areilly.bpc-users.org  Mon Jul 13 07:55:35 2009
From: andrew-freebsd at areilly.bpc-users.org (Andrew Reilly)
Date: Mon Jul 13 07:55:42 2009
Subject: FreeBSD RoadMap
In-Reply-To: <d2e731a10907122155v525691cdv236462d5227f3139@mail.gmail.com>
References: <d2e731a10907122155v525691cdv236462d5227f3139@mail.gmail.com>
Message-ID: <20090713075527.GA11259@duncan.reilly.home>

On Mon, Jul 13, 2009 at 12:55:19AM -0400, grarpamp wrote:
> Is there a general roadmap of what's planned
> for future major releases? I don't mean minor
> stuff like driver or contributed version bumps.
> But bigger, or just plain cool things, like as SMP,
> soft updates, ZFS, netgraph, pf, etc, were in the past.

I doubt that there's much "big" in the ambit of "Unix-like OS"
that isn't already in the 8-current series.

In a project like FreeBSD, "what's in the roadmap" equates
pretty closely with "what are the developers working on", and
that is summarised in the quarterly status reports, such as this
one:
http://www.freebsd.org/news/status/report-2009-01-2009-03.html

As for when any of this will "hit the tree" and find its way
into a release, that's very much a "how long is a piece of
string" sort of question; not really the way FreeBSD works.
Particularly since it moved to a calendar-based release
schedule.

IMO, YMMV, i-do-not-speak-for-freebsd, etc.

Cheers,

-- 
Andrew
From pluknet at gmail.com  Mon Jul 13 11:19:34 2009
From: pluknet at gmail.com (pluknet)
Date: Mon Jul 13 11:19:41 2009
Subject: [quota] quotacheck wont go with geom_label
Message-ID: <a31046fc0907130419g28346fc6u6b36412b776e1686@mail.gmail.com>

Hi.

I found that a file system mounted through /dev/label/name doesn't
work with quotacheck. It turned out that quotacheck after looking
at fstab tries to open /dev/label/name and then receives EPERM (6.2, 7.2),
while it works fine with ordinary device-mounted file systems.

Is there a fix? Should I file a PR?

-- 
wbr,
pluknet
From oliver.pntr at gmail.com  Mon Jul 13 13:30:48 2009
From: oliver.pntr at gmail.com (Oliver Pinter)
Date: Mon Jul 13 13:30:57 2009
Subject: ZFS, unionfs - Operation not supported
Message-ID: <6101e8c40907130600j528bd4d5ue348563e89c7ffa3@mail.gmail.com>

Hi all!

It is the problematic FS:
zpower on /mnt/zpower (zfs, local)
/usr/src on /mnt/zpower/jail/default/ports (nullfs, local)

and the failed command:
mount_unionfs -o below /mnt/zpower/jail/default/ports/
/mnt/zpower/jail/www/usr/ports/

(truss mount_unionfs -o below /mnt/zpower/jail/default/ports/
/mnt/zpower/jail/www/usr/ports/ ) > & /tmp/unionfs.log

Have I any chance, to unionmount ZFS with UFS or ZFS not supported
this operations?
From sagara at tomahawk.com.sg  Mon Jul 13 15:25:50 2009
From: sagara at tomahawk.com.sg (Sagara Wijetunga)
Date: Mon Jul 13 15:25:57 2009
Subject: FreeBSD 7.2 USB stack info needed
Message-ID: <20090713120732.31803.qmail@us1.tomahawkonline.net>

Hi FreeBSD community 

After an USB thumb drive id pluged in, the devd prints following line: 

+umass0 vendor=0x0781 product=0x5406 devclass=0x00 devsubclass=0x00 
release=0x0200 sernum="087663165D8139E6" intclass=0x08 intsubclass=0x06 at 
port=0 interface=0 vendor=0x0781 product=0x5406 devclass=0x00 
devsubclass=0x00 release=0x0200 sernum="087663165D8139E6" intclass=0x08 
intsubclass=0x06 on uhub4 


1. Could I know which exact program print above line on /dev/devctl ? 

2. I want to print another line with "daN" as the device-name, where N is 0 
to 9, with minimum vendor and product ids once the allocated device-name is 
known for USB Mass Storage devices. Your additional ideas/feedback/help is 
most welcomed. 

Kind regards
Sagara
From uqs at spoerlein.net  Mon Jul 13 16:39:27 2009
From: uqs at spoerlein.net (Ulrich =?utf-8?B?U3DDtnJsZWlu?=)
Date: Mon Jul 13 16:39:34 2009
Subject: mergemaster merge left/right
In-Reply-To: <4A4DC67C.3010804@bsdforen.de>
References: <4A4DC67C.3010804@bsdforen.de>
Message-ID: <20090713163922.GM2145@acme.spoerlein.net>

On Fri, 03.07.2009 at 10:51:08 +0200, Dominic Fandrey wrote:
> I'd really like mergemaster to tell me whether the left
> or the right side is the new file.
> 
> # $FreeBSD: src/etc/devd.conf,v 1.38. |	# $FreeBSD: src/etc/devd.conf,v 1.38.
> 
> Like this I have no idea which one to pick.

When using X, maximize your xterm horizontally and use mergemaster -w100
or something like that. It will probe the tty again and offer the "real"
width, so I usually just run mergemaster -w1 and hit enter.

hth,
Ulrich Sp?rlein
From uqs at spoerlein.net  Mon Jul 13 16:57:20 2009
From: uqs at spoerlein.net (Ulrich =?utf-8?B?U3DDtnJsZWlu?=)
Date: Mon Jul 13 16:57:26 2009
Subject: pw groupadd/useradd fail when the nscd cache is used for
 name/group resolution
In-Reply-To: <ad79ad6b0907090613t78cf8540n5fcd3934cadde526@mail.gmail.com>
References: <ad79ad6b0907090613t78cf8540n5fcd3934cadde526@mail.gmail.com>
Message-ID: <20090713165717.GN2145@acme.spoerlein.net>

On Thu, 09.07.2009 at 16:13:25 +0300, Vlad Galu wrote:
> I've stumbled upon this while installing postgres. In
> /etc/nsswitch.conf I had "group: cache files compat" and "passwd:
> cache files compat". Once I commented them out things started working
> again. Before the change, this is how it looked like:
> 
> -- cut here --
> [root@vgalu /usr/ports/databases/postgresql84-server]# pw group add pgsql -g 70
> pw: group disappeared during update
> [root@vgalu /usr/ports/databases/postgresql84-server]# pw group add pgsql -g 70
> pw: group 'pgsql' already exists
> [root@vgalu /usr/ports/databases/postgresql84-server]#
> -- and here --
> 
> Shouldn't 'files' be used upon a cache miss? If this is a PEBKAC,
> sorry for the noise.

Just a me too. This is most likely because nscd is also caching negative
lookups. The usual workaround would be to restart it using
/etc/rc.d/nscd restart

Cheers,
Ulrich Sp?rlein
From mike at jellydonut.org  Mon Jul 13 17:28:14 2009
From: mike at jellydonut.org (Michael Proto)
Date: Mon Jul 13 17:28:21 2009
Subject: pw groupadd/useradd fail when the nscd cache is used for 
	name/group resolution
In-Reply-To: <20090713165717.GN2145@acme.spoerlein.net>
References: <ad79ad6b0907090613t78cf8540n5fcd3934cadde526@mail.gmail.com>
	<20090713165717.GN2145@acme.spoerlein.net>
Message-ID: <1de79840907131028n5b8f21deyd968639732c651a4@mail.gmail.com>

On Mon, Jul 13, 2009 at 12:57 PM, Ulrich Sp?rlein<uqs@spoerlein.net> wrote:
> On Thu, 09.07.2009 at 16:13:25 +0300, Vlad Galu wrote:
>> I've stumbled upon this while installing postgres. In
>> /etc/nsswitch.conf I had "group: cache files compat" and "passwd:
>> cache files compat". Once I commented them out things started working
>> again. Before the change, this is how it looked like:
>>
>> -- cut here --
>> [root@vgalu /usr/ports/databases/postgresql84-server]# pw group add pgsql -g 70
>> pw: group disappeared during update
>> [root@vgalu /usr/ports/databases/postgresql84-server]# pw group add pgsql -g 70
>> pw: group 'pgsql' already exists
>> [root@vgalu /usr/ports/databases/postgresql84-server]#
>> -- and here --
>>
>> Shouldn't 'files' be used upon a cache miss? If this is a PEBKAC,
>> sorry for the noise.
>
> Just a me too. This is most likely because nscd is also caching negative
> lookups. The usual workaround would be to restart it using
> /etc/rc.d/nscd restart
>

A slightly lower-impact alternative would be to use "nscd -i passwd"
to invalidate the password cache.


-Proto
From mcdouga9 at egr.msu.edu  Mon Jul 13 17:43:53 2009
From: mcdouga9 at egr.msu.edu (Adam McDougall)
Date: Mon Jul 13 17:44:02 2009
Subject: pw groupadd/useradd fail when the nscd cache is used for
 name/group resolution
In-Reply-To: <1de79840907131028n5b8f21deyd968639732c651a4@mail.gmail.com>
References: <ad79ad6b0907090613t78cf8540n5fcd3934cadde526@mail.gmail.com>	<20090713165717.GN2145@acme.spoerlein.net>
	<1de79840907131028n5b8f21deyd968639732c651a4@mail.gmail.com>
Message-ID: <4A5B7257.1010202@egr.msu.edu>

Michael Proto wrote:
> On Mon, Jul 13, 2009 at 12:57 PM, Ulrich Sp?rlein<uqs@spoerlein.net> wrote:
>   
>> On Thu, 09.07.2009 at 16:13:25 +0300, Vlad Galu wrote:
>>     
>>> I've stumbled upon this while installing postgres. In
>>> /etc/nsswitch.conf I had "group: cache files compat" and "passwd:
>>> cache files compat". Once I commented them out things started working
>>> again. Before the change, this is how it looked like:
>>>
>>> -- cut here --
>>> [root@vgalu /usr/ports/databases/postgresql84-server]# pw group add pgsql -g 70
>>> pw: group disappeared during update
>>> [root@vgalu /usr/ports/databases/postgresql84-server]# pw group add pgsql -g 70
>>> pw: group 'pgsql' already exists
>>> [root@vgalu /usr/ports/databases/postgresql84-server]#
>>> -- and here --
>>>
>>> Shouldn't 'files' be used upon a cache miss? If this is a PEBKAC,
>>> sorry for the noise.
>>>       
>> Just a me too. This is most likely because nscd is also caching negative
>> lookups. The usual workaround would be to restart it using
>> /etc/rc.d/nscd restart
>>
>>     
>
> A slightly lower-impact alternative would be to use "nscd -i passwd"
> to invalidate the password cache.
>
>
> -Proto
> _______________________________________________
>   

I was intending to report this soon as well (its been on my list for a 
while) as a problematic
issue while installing ports.  The other issue I had was Java would 
crash immediately if I had
nscd running (configured to cache YP).  I plan to report that soon if it 
still happens with 1.6.
I probably tested with 1.4 or 1.5. 
From masoom.shaikh at gmail.com  Mon Jul 13 18:51:55 2009
From: masoom.shaikh at gmail.com (Masoom Shaikh)
Date: Mon Jul 13 18:52:02 2009
Subject: FreeBSD RoadMap
In-Reply-To: <20090713075527.GA11259@duncan.reilly.home>
References: <d2e731a10907122155v525691cdv236462d5227f3139@mail.gmail.com>
	<20090713075527.GA11259@duncan.reilly.home>
Message-ID: <b10011eb0907131126l76cedbe9n954e539d6ca35504@mail.gmail.com>

can this help ?

http://ivoras.sharanet.org/freebsd/freebsd8.html

On Mon, Jul 13, 2009 at 7:55 AM, Andrew Reilly <
andrew-freebsd@areilly.bpc-users.org> wrote:

> On Mon, Jul 13, 2009 at 12:55:19AM -0400, grarpamp wrote:
> > Is there a general roadmap of what's planned
> > for future major releases? I don't mean minor
> > stuff like driver or contributed version bumps.
> > But bigger, or just plain cool things, like as SMP,
> > soft updates, ZFS, netgraph, pf, etc, were in the past.
>
> I doubt that there's much "big" in the ambit of "Unix-like OS"
> that isn't already in the 8-current series.
>
> In a project like FreeBSD, "what's in the roadmap" equates
> pretty closely with "what are the developers working on", and
> that is summarised in the quarterly status reports, such as this
> one:
> http://www.freebsd.org/news/status/report-2009-01-2009-03.html
>
> As for when any of this will "hit the tree" and find its way
> into a release, that's very much a "how long is a piece of
> string" sort of question; not really the way FreeBSD works.
> Particularly since it moved to a calendar-based release
> schedule.
>
> IMO, YMMV, i-do-not-speak-for-freebsd, etc.
>
> Cheers,
>
> --
> Andrew
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>
From jhb at freebsd.org  Mon Jul 13 19:26:33 2009
From: jhb at freebsd.org (John Baldwin)
Date: Mon Jul 13 19:26:41 2009
Subject: trap 12
In-Reply-To: <20090707105103.946813hdks2mra80@10.248.192.16>
References: <20090703100627.197838cphjnil82s@10.248.192.16>
	<20090706200115.1411150frxepkbuo@webmail.private.lan>
	<20090707105103.946813hdks2mra80@10.248.192.16>
Message-ID: <200907131515.59195.jhb@freebsd.org>

On Tuesday 07 July 2009 5:51:03 am Ian J Hart wrote:
> Quoting Ian J Hart <ianjhart@ntlworld.com>:
> 
> > Quoting Ian J Hart <ianjhart@ntlworld.com>:
> >
> >> Is this likely to be hardware? Details will follow if not.
> >>
> >> [copied from a screen dump]
> >>
> >> Fatal trap 12: page fault while in kernel mode
> >> cpuid = 1; apic id = 01
> >> fault virtual address = 0x0
> >> fault code = supervisor write data, page not present
> >> instruction pointer = 0x8:0xffffffff807c6c12
> >> stack pointer = 0x10:0xffffffff510e7890
> >> frame pointer = 0x10:0xffffff00054a6c90
> >> code segment = base 0x0, limit 0xfffff, type 0x1b
> >> = DPL 0, pres 1, long 1 def32 0, gran 1
> >> processor eflags = interrupt enabled, resume, IOPL = 0
> >> current process = 75372 (printf)
> >> trap number = 12
> >> panic: page fault
> >> cpuid = 1
> >> uptime: 8m2s
> >> Cannot dump. No dump device defined.
> >>
> >>
> >  Ran crashinfo, now have much more info than I need ;)
> >
> >  Starting another portupgrade run now to see how reproducable this is.
> >
> >  Later BIOS waiting in USB floppy.
> >
> [snip dmesg]
> 
> It took 2 runs of portupgrade -af.Some corruption in the dbs may have  
> to pkg_delete -a.
> 
> FreeBSD * 7.2-RELEASE-p1 FreeBSD 7.2-RELEASE-p1 #0: Tue Jun 16  
> 18:03:10 BST 2009     *@*:/usr/obj/usr/src/sys/GENERIC  amd64
> 
> panic: page fault
> 
> GNU gdb 6.1.1 [FreeBSD]
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain 
conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "amd64-marcel-freebsd"...
> 
> Unread portion of the kernel message buffer:
> 
> 
> Fatal trap 12: page fault while in kernel mode
> cpuid = 1; apic id = 01
> fault virtual address   = 0xfffffffff5555570
> fault code              = supervisor write data, page not present
> instruction pointer     = 0x8:0xffffffff807c429b
> stack pointer           = 0x10:0xffffffff511e4710
> frame pointer           = 0x10:0x20
> code segment            = base 0x0, limit 0xfffff, type 0x1b
>                          = DPL 0, pres 1, long 1, def32 0, gran 1
> processor eflags        = interrupt enabled, resume, IOPL = 0
> current process         = 69996 (mkdir)
> trap number             = 12
> panic: page fault

This one does look like a hardware issue from the stack trace.  It's hard to 
know if the first panic you saw was a hardware issue as well without the 
stack trace information.

> #7  0xffffffff807b706e in calltrap ()
>      at /usr/src/sys/amd64/amd64/exception.S:209
> #8  0xffffffff807c429b in free_pv_entry (pmap=0xffffffff80b66c80,  
> pv=Variable "pv" is not available.
> )
>      at /usr/src/sys/amd64/amd64/pmap.c:1905
> #9  0xffffffff807c4403 in pmap_remove_entry (pmap=Variable "pmap" is  
> not available.
> )
>      at /usr/src/sys/amd64/amd64/pmap.c:2131
> #10 0xffffffff807c6447 in pmap_remove_pte (pmap=0xffffffff80b66c80,
>      ptq=0xaaaaaaa8, va=18446744070506639360, ptepde=23601251,
>      free=0xffffffff511e4790) at /usr/src/sys/amd64/amd64/pmap.c:2366
> #11 0xffffffff807cab87 in pmap_remove (pmap=0xffffffff80b66c80,
>      sva=18446744070506639360, eva=18446744070506909696)
>      at /usr/src/sys/amd64/amd64/pmap.c:2510

-- 
John Baldwin
From marketing at donateshoes.org  Mon Jul 13 19:28:30 2009
From: marketing at donateshoes.org (Soles4Souls and Nine West)
Date: Mon Jul 13 19:28:38 2009
Subject: Introducing the Vintage America Collection with Nine West
	Benefitting Soles4Souls
Message-ID: <20090713102238.783555046@donateshoes.org>

Introducing the Vintage America Collection with Nine West Benefitting Soles4Souls
From wolfgang at lyxys.ka.sub.org  Mon Jul 13 19:50:18 2009
From: wolfgang at lyxys.ka.sub.org (Wolfgang Zenker)
Date: Mon Jul 13 19:50:27 2009
Subject: FreeBSD RoadMap
In-Reply-To: <b10011eb0907131126l76cedbe9n954e539d6ca35504@mail.gmail.com>
References: <d2e731a10907122155v525691cdv236462d5227f3139@mail.gmail.com>
	<20090713075527.GA11259@duncan.reilly.home>
	<b10011eb0907131126l76cedbe9n954e539d6ca35504@mail.gmail.com>
Message-ID: <20090713193903.GA49591@lyxys.ka.sub.org>

* Masoom Shaikh <masoom.shaikh@gmail.com> [090713 20:26]:
> On Mon, Jul 13, 2009 at 7:55 AM, Andrew Reilly <andrew-freebsd@areilly.bpc-users.org> wrote:
>> On Mon, Jul 13, 2009 at 12:55:19AM -0400, grarpamp wrote:
>>> Is there a general roadmap of what's planned
>>> for future major releases? I don't mean minor
>>> stuff like driver or contributed version bumps.
>>> But bigger, or just plain cool things, like as SMP,
>>> soft updates, ZFS, netgraph, pf, etc, were in the past.

>> I doubt that there's much "big" in the ambit of "Unix-like OS"
>> that isn't already in the 8-current series.

>> In a project like FreeBSD, "what's in the roadmap" equates
>> pretty closely with "what are the developers working on", and
>> that is summarised in the quarterly status reports, such as this
>> one:
>> http://www.freebsd.org/news/status/report-2009-01-2009-03.html

>> As for when any of this will "hit the tree" and find its way
>> into a release, that's very much a "how long is a piece of
>> string" sort of question; not really the way FreeBSD works.
>> Particularly since it moved to a calendar-based release
>> schedule.

>> IMO, YMMV, i-do-not-speak-for-freebsd, etc.

> can this help ?

> http://ivoras.sharanet.org/freebsd/freebsd8.html

or you could visit this years eurobsdcon and listen to
http://www.ukuug.org/events/eurobsdcon2009/talks/#mckusick

:-)
From graham at menhennitt.com.au  Mon Jul 13 23:24:40 2009
From: graham at menhennitt.com.au (Graham Menhennitt)
Date: Mon Jul 13 23:25:13 2009
Subject: problem with Soekris net5501 and USB hub
Message-ID: <4A5BBD50.2020408@menhennitt.com.au>

I originally sent this to the Soekris list thinking it was platform 
specific. I got a couple of replies suggesting that it's a FreeBSD 
problem instead. So, if anybody can offer any insights, I would most 
appreciate it.

I have a Soekris net5501 running FreeBSD 7-Stable. I want to connect a 
number of USB devices to it:
- a HP Laserjet 1020 printer
- an APC Back UPS 350 UPS
- a 6-in-one card reader (not so fussed about this one).
The Soekris box has only one USB port brought out to a connector on the 
case, so rather than mod the box to add another port, I thought I would 
just use an external hub.

If I plug any of the devcies directly into the Soekris's USB port it 
works fine. However, if I use a USB hub then it doesn't work at all. 
I've tried it with two different hubs and two different cables. I've 
tried the hubs both with a plug pack, and being powered from the USB 
bus. The only thing common to the failures is the Soefkis and freeBSD. 
The hubs are both USB 2.0 according to their advertising.

The hub itself is recognised (although I don't have the output from
usbdevs available at the moment). The UPS doesn't ever seem to be
recognised when connected via the hub - there's nothing in dmesg and
nothing in usbdevs. Ditto for the 6-in-one card reader - the LED on the
front of it doesn't even light up.

The printer sometimes gets partially recognised. The output from
"usbdevs -v" when the printer is connected directly and working properly
looks like:

     Controller /dev/usb0:
    addr 1: full speed, self powered, config 1, OHCI root hub(0x0000), 
AMD(0x0000), rev 1.00
     port 1 powered
     port 2 powered
     port 3 powered
     port 4 powered
    Controller /dev/usb1:
    addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), 
AMD(0x0000), rev 1.00
     port 1 addr 2: high speed, self powered, config 1, HP LaserJet 
1020(0x2b17), Hewlett-Packard(0x03f0), rev 1.00
     port 2 powered
     port 3 powered
     port 4 powered

However, if I connect it via the hub, it sometimes doesn't show it at 
all, while other times it says something like (doing this from memory):

    port 1 addr 2: high speed, self powered, config 1, 0x2b17(0x2b17), 
vendor 0x03f0(0x03f0), rev 1.00

So, it can see it but it doesn't resolve the vendor or device ids. It 
looks like the Soekris can see whatever is directly connected to it, but 
  can't (reliably) see things that more than one step away.

My (custom) kernel has:

    device          usb             # USB Bus (required)
    device          umass           # Disks/Mass storage - Requires 
scbus and da
    device          scbus           # SCSI bus (required for SCSI)
    device          da              # Direct Access (disks)
    device          uhci            # UHCI PCI->USB interface
    device          ohci            # OHCI PCI->USB interface
    device          ehci            # EHCI PCI->USB interface (USB 2.0)
    device          ugen            # Generic

So, does anybody have any ideas about how to fix this.

Thanks for any help,
  Graham
From pprocacci at datapipe.net  Mon Jul 13 23:43:27 2009
From: pprocacci at datapipe.net (Paul A. Procacci)
Date: Mon Jul 13 23:43:37 2009
Subject: problem with Soekris net5501 and USB hub
In-Reply-To: <4A5BBD50.2020408@menhennitt.com.au>
References: <4A5BBD50.2020408@menhennitt.com.au>
Message-ID: <4A5BC379.7040004@datapipe.net>

Hello,

I recently (just yesterday) had a similar problem with 7-STABLE not 
being able to detect devices attached to a hub.  I immediately upgraded 
to 8-BETA1 and the problem is gone, though I've run into a number of 
other issues unrelated to usb devices.  The sokeris will more than 
likely fair better on FBSD 8 than my multipurpose machine, but it may be 
worth a try.

~Paul

Graham Menhennitt wrote:
> I originally sent this to the Soekris list thinking it was platform 
> specific. I got a couple of replies suggesting that it's a FreeBSD 
> problem instead. So, if anybody can offer any insights, I would most 
> appreciate it.
>
> I have a Soekris net5501 running FreeBSD 7-Stable. I want to connect a 
> number of USB devices to it:
> - a HP Laserjet 1020 printer
> - an APC Back UPS 350 UPS
> - a 6-in-one card reader (not so fussed about this one).
> The Soekris box has only one USB port brought out to a connector on the 
> case, so rather than mod the box to add another port, I thought I would 
> just use an external hub.
>
> If I plug any of the devcies directly into the Soekris's USB port it 
> works fine. However, if I use a USB hub then it doesn't work at all. 
> I've tried it with two different hubs and two different cables. I've 
> tried the hubs both with a plug pack, and being powered from the USB 
> bus. The only thing common to the failures is the Soefkis and freeBSD. 
> The hubs are both USB 2.0 according to their advertising.
>
> The hub itself is recognised (although I don't have the output from
> usbdevs available at the moment). The UPS doesn't ever seem to be
> recognised when connected via the hub - there's nothing in dmesg and
> nothing in usbdevs. Ditto for the 6-in-one card reader - the LED on the
> front of it doesn't even light up.
>
> The printer sometimes gets partially recognised. The output from
> "usbdevs -v" when the printer is connected directly and working properly
> looks like:
>
>      Controller /dev/usb0:
>     addr 1: full speed, self powered, config 1, OHCI root hub(0x0000), 
> AMD(0x0000), rev 1.00
>      port 1 powered
>      port 2 powered
>      port 3 powered
>      port 4 powered
>     Controller /dev/usb1:
>     addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), 
> AMD(0x0000), rev 1.00
>      port 1 addr 2: high speed, self powered, config 1, HP LaserJet 
> 1020(0x2b17), Hewlett-Packard(0x03f0), rev 1.00
>      port 2 powered
>      port 3 powered
>      port 4 powered
>
> However, if I connect it via the hub, it sometimes doesn't show it at 
> all, while other times it says something like (doing this from memory):
>
>     port 1 addr 2: high speed, self powered, config 1, 0x2b17(0x2b17), 
> vendor 0x03f0(0x03f0), rev 1.00
>
> So, it can see it but it doesn't resolve the vendor or device ids. It 
> looks like the Soekris can see whatever is directly connected to it, but 
>   can't (reliably) see things that more than one step away.
>
> My (custom) kernel has:
>
>     device          usb             # USB Bus (required)
>     device          umass           # Disks/Mass storage - Requires 
> scbus and da
>     device          scbus           # SCSI bus (required for SCSI)
>     device          da              # Direct Access (disks)
>     device          uhci            # UHCI PCI->USB interface
>     device          ohci            # OHCI PCI->USB interface
>     device          ehci            # EHCI PCI->USB interface (USB 2.0)
>     device          ugen            # Generic
>
> So, does anybody have any ideas about how to fix this.
>
> Thanks for any help,
>   Graham
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>   

From dougb at FreeBSD.org  Tue Jul 14 04:34:12 2009
From: dougb at FreeBSD.org (Doug Barton)
Date: Tue Jul 14 04:34:19 2009
Subject: mergemaster merge left/right
In-Reply-To: <20090713163922.GM2145@acme.spoerlein.net>
References: <4A4DC67C.3010804@bsdforen.de>
	<20090713163922.GM2145@acme.spoerlein.net>
Message-ID: <4A5C0AAF.1090604@FreeBSD.org>

Ulrich Sp?rlein wrote:
> When using X, maximize your xterm horizontally and use mergemaster -w100
> or something like that. It will probe the tty again and offer the "real"
> width, so I usually just run mergemaster -w1 and hit enter.

Making the window wider is good advice, but the -w option is not
needed. If you're running mergemaster in any sort of tty it will
automatically set the column width for sdiff for you.


hth,

Doug
From sagara at tomahawk.com.sg  Tue Jul 14 05:42:54 2009
From: sagara at tomahawk.com.sg (Sagara Wijetunga)
Date: Tue Jul 14 05:43:00 2009
Subject: FreeBSD 7.2 USB stack info needed
In-Reply-To: <20090713120732.31803.qmail@us1.tomahawkonline.net>
References: <20090713120732.31803.qmail@us1.tomahawkonline.net>
Message-ID: <20090714022435.7844.qmail@us1.tomahawkonline.net>

Sagara Wijetunga writes: 

> Hi FreeBSD community  
> 
> After an USB thumb drive id pluged in, the devd prints following line:  
> 
> +umass0 vendor=0x0781 product=0x5406 devclass=0x00 devsubclass=0x00 
> release=0x0200 sernum="087663165D8139E6" intclass=0x08 intsubclass=0x06 at 
> port=0 interface=0 vendor=0x0781 product=0x5406 devclass=0x00 
> devsubclass=0x00 release=0x0200 sernum="087663165D8139E6" intclass=0x08 
> intsubclass=0x06 on uhub4  
> 
> 
> 1. Could I know which exact program print above line on /dev/devctl ?  
> 
> 2. I want to print another line with "daN" as the device-name, where N is 
> 0 to 9, with minimum vendor and product ids once the allocated device-name 
> is known for USB Mass Storage devices. Your additional ideas/feedback/help 
> is most welcomed.  
> 

There is a typing mistake: "After an USB thumb drive id pluged in" should be 
corrected as "After an USB thumb drive is plugged in". Very sorry for the 
mistake. 

Btw, I have started looking at umass.c and will have a look at later at 
usb.c of /usr/src/sys/dev/usb/. 

Any help is still very much appreciated. 

Best regards
Sagara
From Hans.F.Nordhaug at hiMolde.no  Tue Jul 14 08:41:16 2009
From: Hans.F.Nordhaug at hiMolde.no (Hans F. Nordhaug)
Date: Tue Jul 14 08:41:25 2009
Subject: portsnap and freebsd-update (metadata) failure
In-Reply-To: <20090708114127.GA22749@hiMolde.no>
References: <20090708114127.GA22749@hiMolde.no>
Message-ID: <20090714084113.GA19867@hiMolde.no>

* Hans F. Nordhaug <Hans.F.Nordhaug@hiMolde.no> [2009-07-08]:
> Hi!
> 
> Quick question: Is it just me and my freshly installed FreeBSD 7.2
> that fails when running freebsd-update or portsnap right now? With
> freebsd-update I tried update4 and update1. Just ask for more info, if
> it's needed to debug the problem.

Apperently it was only meand my machine ;-) I reinstalled FreeBSD 7.2
on a newer computer and then freebsd-update or portsnap worked nicely.

Best regards,
Hans Nordhaug
From ivoras at freebsd.org  Tue Jul 14 09:38:05 2009
From: ivoras at freebsd.org (Ivan Voras)
Date: Tue Jul 14 09:38:12 2009
Subject: ZFS, unionfs - Operation not supported
In-Reply-To: <6101e8c40907130600j528bd4d5ue348563e89c7ffa3@mail.gmail.com>
References: <6101e8c40907130600j528bd4d5ue348563e89c7ffa3@mail.gmail.com>
Message-ID: <h3hjld$sig$1@ger.gmane.org>

Oliver Pinter wrote:
> Hi all!
> 
> It is the problematic FS:
> zpower on /mnt/zpower (zfs, local)
> /usr/src on /mnt/zpower/jail/default/ports (nullfs, local)
> 
> and the failed command:
> mount_unionfs -o below /mnt/zpower/jail/default/ports/
> /mnt/zpower/jail/www/usr/ports/
> 
> (truss mount_unionfs -o below /mnt/zpower/jail/default/ports/
> /mnt/zpower/jail/www/usr/ports/ ) > & /tmp/unionfs.log
> 
> Have I any chance, to unionmount ZFS with UFS or ZFS not supported
> this operations?

Yes, unionfs is not supported with ZFS.

From gavin at FreeBSD.org  Tue Jul 14 13:03:02 2009
From: gavin at FreeBSD.org (Gavin Atkinson)
Date: Tue Jul 14 13:03:12 2009
Subject: pw groupadd/useradd fail when the nscd cache is used for
	name/group resolution
In-Reply-To: <4A5B7257.1010202@egr.msu.edu>
References: <ad79ad6b0907090613t78cf8540n5fcd3934cadde526@mail.gmail.com>
	<20090713165717.GN2145@acme.spoerlein.net>
	<1de79840907131028n5b8f21deyd968639732c651a4@mail.gmail.com>
	<4A5B7257.1010202@egr.msu.edu>
Message-ID: <1247574703.82683.17.camel@buffy.york.ac.uk>

On Mon, 2009-07-13 at 13:43 -0400, Adam McDougall wrote:
> Michael Proto wrote:
> > On Mon, Jul 13, 2009 at 12:57 PM, Ulrich Sp?rlein<uqs@spoerlein.net> wrote:
> >   
> >> On Thu, 09.07.2009 at 16:13:25 +0300, Vlad Galu wrote:
> >>     
> >>> I've stumbled upon this while installing postgres. In
> >>> /etc/nsswitch.conf I had "group: cache files compat" and "passwd:
> >>> cache files compat". Once I commented them out things started working
> >>> again. Before the change, this is how it looked like:
> >>>
> >>> -- cut here --
> >>> [root@vgalu /usr/ports/databases/postgresql84-server]# pw group add pgsql -g 70
> >>> pw: group disappeared during update
> >>> [root@vgalu /usr/ports/databases/postgresql84-server]# pw group add pgsql -g 70
> >>> pw: group 'pgsql' already exists
> >>> [root@vgalu /usr/ports/databases/postgresql84-server]#
> >>> -- and here --
> >>>
> >>> Shouldn't 'files' be used upon a cache miss? If this is a PEBKAC,
> >>> sorry for the noise.
> >>>       
> >> Just a me too. This is most likely because nscd is also caching negative
> >> lookups. The usual workaround would be to restart it using
> >> /etc/rc.d/nscd restart
> >>
> >>     
> > A slightly lower-impact alternative would be to use "nscd -i passwd"
> > to invalidate the password cache.
> >
> >
> I was intending to report this soon as well (its been on my list for a 
> while) as a problematic
> issue while installing ports.  The other issue I had was Java would 
> crash immediately if I had
> nscd running (configured to cache YP).  I plan to report that soon if it 
> still happens with 1.6.
> I probably tested with 1.4 or 1.5. 

This is a known problem with nscd(8), see ports/125330 and bin/119695.
If you have any further information (or even a patch) it's probably best
to append it to the second of those PRs.

Thanks,

Gavin
From ianjhart at ntlworld.com  Tue Jul 14 13:51:17 2009
From: ianjhart at ntlworld.com (Ian J Hart)
Date: Tue Jul 14 13:51:24 2009
Subject: trap 12
Message-ID: <20090714145101.60515vh49s7o7c4k@10.248.192.16>

Quoting John Baldwin <jhb@freebsd.org>:

> On Tuesday 07 July 2009 5:51:03 am Ian J Hart wrote:
>> Quoting Ian J Hart <ianjhart@ntlworld.com>:
>>
>>> Quoting Ian J Hart <ianjhart@ntlworld.com>:
>>>
>>>> Is this likely to be hardware? Details will follow if not.
>>>>
>>>> [copied from a screen dump]
>>>>
>>>> Fatal trap 12: page fault while in kernel mode
>>>> cpuid = 1; apic id = 01
>>>> fault virtual address = 0x0
>>>> fault code = supervisor write data, page not present
>>>> instruction pointer = 0x8:0xffffffff807c6c12
>>>> stack pointer = 0x10:0xffffffff510e7890
>>>> frame pointer = 0x10:0xffffff00054a6c90
>>>> code segment = base 0x0, limit 0xfffff, type 0x1b
>>>> = DPL 0, pres 1, long 1 def32 0, gran 1
>>>> processor eflags = interrupt enabled, resume, IOPL = 0
>>>> current process = 75372 (printf)
>>>> trap number = 12
>>>> panic: page fault
>>>> cpuid = 1
>>>> uptime: 8m2s
>>>> Cannot dump. No dump device defined.
>>>>
>>>>
>>>  Ran crashinfo, now have much more info than I need ;)
>>>
>>>  Starting another portupgrade run now to see how reproducable this is.
>>>
>>>  Later BIOS waiting in USB floppy.
>>>
>> [snip dmesg]
>>
>> It took 2 runs of portupgrade -af.Some corruption in the dbs may have
>> to pkg_delete -a.
>>
>> FreeBSD * 7.2-RELEASE-p1 FreeBSD 7.2-RELEASE-p1 #0: Tue Jun 16
>> 18:03:10 BST 2009     *@*:/usr/obj/usr/src/sys/GENERIC  amd64
>>
>> panic: page fault
>>
>> GNU gdb 6.1.1 [FreeBSD]
>> Copyright 2004 Free Software Foundation, Inc.
>> GDB is free software, covered by the GNU General Public License, and you are
>> welcome to change it and/or distribute copies of it under certain
> conditions.
>> Type "show copying" to see the conditions.
>> There is absolutely no warranty for GDB.  Type "show warranty" for details.
>> This GDB was configured as "amd64-marcel-freebsd"...
>>
>> Unread portion of the kernel message buffer:
>>
>>
>> Fatal trap 12: page fault while in kernel mode
>> cpuid = 1; apic id = 01
>> fault virtual address   = 0xfffffffff5555570
>> fault code              = supervisor write data, page not present
>> instruction pointer     = 0x8:0xffffffff807c429b
>> stack pointer           = 0x10:0xffffffff511e4710
>> frame pointer           = 0x10:0x20
>> code segment            = base 0x0, limit 0xfffff, type 0x1b
>>                         = DPL 0, pres 1, long 1, def32 0, gran 1
>> processor eflags        = interrupt enabled, resume, IOPL = 0
>> current process         = 69996 (mkdir)
>> trap number             = 12
>> panic: page fault
>
> This one does look like a hardware issue from the stack trace.  It's hard to
> know if the first panic you saw was a hardware issue as well without the
> stack trace information.
>
>> #7  0xffffffff807b706e in calltrap ()
>>     at /usr/src/sys/amd64/amd64/exception.S:209
>> #8  0xffffffff807c429b in free_pv_entry (pmap=0xffffffff80b66c80,
>> pv=Variable "pv" is not available.
>> )
>>     at /usr/src/sys/amd64/amd64/pmap.c:1905
>> #9  0xffffffff807c4403 in pmap_remove_entry (pmap=Variable "pmap" is
>> not available.
>> )
>>     at /usr/src/sys/amd64/amd64/pmap.c:2131
>> #10 0xffffffff807c6447 in pmap_remove_pte (pmap=0xffffffff80b66c80,
>>     ptq=0xaaaaaaa8, va=18446744070506639360, ptepde=23601251,
>>     free=0xffffffff511e4790) at /usr/src/sys/amd64/amd64/pmap.c:2366
>> #11 0xffffffff807cab87 in pmap_remove (pmap=0xffffffff80b66c80,
>>     sva=18446744070506639360, eva=18446744070506909696)
>>     at /usr/src/sys/amd64/amd64/pmap.c:2510
>
> --
> John Baldwin
>

The remote backup continues to run so there was definitely some issue  
there. No more reboots, but it wasn't doing that regularly without  
some additional load.

Hopefully I can swap parts around until I find the offending item.

Thanks for your input.

-- 
ian j hart


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


From amarat at ksu.ru  Tue Jul 14 16:49:36 2009
From: amarat at ksu.ru (Marat N.Afanasyev)
Date: Tue Jul 14 16:49:47 2009
Subject: problem with Soekris net5501 and USB hub
In-Reply-To: <4A5BBD50.2020408@menhennitt.com.au>
References: <4A5BBD50.2020408@menhennitt.com.au>
Message-ID: <4A5CB6FB.4090808@ksu.ru>

Graham Menhennitt wrote:
> I originally sent this to the Soekris list thinking it was platform 
> specific. I got a couple of replies suggesting that it's a FreeBSD 
> problem instead. So, if anybody can offer any insights, I would most 
> appreciate it.
> 
> I have a Soekris net5501 running FreeBSD 7-Stable. I want to connect a 
> number of USB devices to it:
> - a HP Laserjet 1020 printer
> - an APC Back UPS 350 UPS
> - a 6-in-one card reader (not so fussed about this one).
> The Soekris box has only one USB port brought out to a connector on the 
> case, so rather than mod the box to add another port, I thought I would 
> just use an external hub.
> 
> If I plug any of the devcies directly into the Soekris's USB port it 
> works fine. However, if I use a USB hub then it doesn't work at all. 
> I've tried it with two different hubs and two different cables. I've 
> tried the hubs both with a plug pack, and being powered from the USB 
> bus. The only thing common to the failures is the Soefkis and freeBSD. 
> The hubs are both USB 2.0 according to their advertising.
> 
> The hub itself is recognised (although I don't have the output from
> usbdevs available at the moment). The UPS doesn't ever seem to be
> recognised when connected via the hub - there's nothing in dmesg and
> nothing in usbdevs. Ditto for the 6-in-one card reader - the LED on the
> front of it doesn't even light up.
> 
> The printer sometimes gets partially recognised. The output from
> "usbdevs -v" when the printer is connected directly and working properly
> looks like:
> 
>     Controller /dev/usb0:
>    addr 1: full speed, self powered, config 1, OHCI root hub(0x0000), 
> AMD(0x0000), rev 1.00
>     port 1 powered
>     port 2 powered
>     port 3 powered
>     port 4 powered
>    Controller /dev/usb1:
>    addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), 
> AMD(0x0000), rev 1.00
>     port 1 addr 2: high speed, self powered, config 1, HP LaserJet 
> 1020(0x2b17), Hewlett-Packard(0x03f0), rev 1.00
>     port 2 powered
>     port 3 powered
>     port 4 powered
> 
> However, if I connect it via the hub, it sometimes doesn't show it at 
> all, while other times it says something like (doing this from memory):
> 
>    port 1 addr 2: high speed, self powered, config 1, 0x2b17(0x2b17), 
> vendor 0x03f0(0x03f0), rev 1.00
> 
> So, it can see it but it doesn't resolve the vendor or device ids. It 
> looks like the Soekris can see whatever is directly connected to it, but 
>  can't (reliably) see things that more than one step away.
> 
> My (custom) kernel has:
> 
>    device          usb             # USB Bus (required)
>    device          umass           # Disks/Mass storage - Requires scbus 
> and da
>    device          scbus           # SCSI bus (required for SCSI)
>    device          da              # Direct Access (disks)
>    device          uhci            # UHCI PCI->USB interface
>    device          ohci            # OHCI PCI->USB interface
>    device          ehci            # EHCI PCI->USB interface (USB 2.0)
>    device          ugen            # Generic
> 
> So, does anybody have any ideas about how to fix this.
> 
> Thanks for any help,
>  Graham
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
> 
see http://www.freebsd.org/cgi/query-pr.cgi?pr=131074 i think your case 
is very similar to mine

-- 
SY, Marat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3221 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090714/8171c86b/smime.bin
From jhb at freebsd.org  Tue Jul 14 17:39:19 2009
From: jhb at freebsd.org (John Baldwin)
Date: Tue Jul 14 17:39:30 2009
Subject: trap 12
In-Reply-To: <20090714145101.60515vh49s7o7c4k@10.248.192.16>
References: <20090714145101.60515vh49s7o7c4k@10.248.192.16>
Message-ID: <200907141300.16634.jhb@freebsd.org>

On Tuesday 14 July 2009 9:51:01 am Ian J Hart wrote:
> Quoting John Baldwin <jhb@freebsd.org>:
> 
> > On Tuesday 07 July 2009 5:51:03 am Ian J Hart wrote:
> >> Quoting Ian J Hart <ianjhart@ntlworld.com>:
> >>
> >>> Quoting Ian J Hart <ianjhart@ntlworld.com>:
> >>>
> >>>> Is this likely to be hardware? Details will follow if not.
> >>>>
> >>>> [copied from a screen dump]
> >>>>
> >>>> Fatal trap 12: page fault while in kernel mode
> >>>> cpuid = 1; apic id = 01
> >>>> fault virtual address = 0x0
> >>>> fault code = supervisor write data, page not present
> >>>> instruction pointer = 0x8:0xffffffff807c6c12
> >>>> stack pointer = 0x10:0xffffffff510e7890
> >>>> frame pointer = 0x10:0xffffff00054a6c90
> >>>> code segment = base 0x0, limit 0xfffff, type 0x1b
> >>>> = DPL 0, pres 1, long 1 def32 0, gran 1
> >>>> processor eflags = interrupt enabled, resume, IOPL = 0
> >>>> current process = 75372 (printf)
> >>>> trap number = 12
> >>>> panic: page fault
> >>>> cpuid = 1
> >>>> uptime: 8m2s
> >>>> Cannot dump. No dump device defined.
> >>>>
> >>>>
> >>>  Ran crashinfo, now have much more info than I need ;)
> >>>
> >>>  Starting another portupgrade run now to see how reproducable this is.
> >>>
> >>>  Later BIOS waiting in USB floppy.
> >>>
> >> [snip dmesg]
> >>
> >> It took 2 runs of portupgrade -af.Some corruption in the dbs may have
> >> to pkg_delete -a.
> >>
> >> FreeBSD * 7.2-RELEASE-p1 FreeBSD 7.2-RELEASE-p1 #0: Tue Jun 16
> >> 18:03:10 BST 2009     *@*:/usr/obj/usr/src/sys/GENERIC  amd64
> >>
> >> panic: page fault
> >>
> >> GNU gdb 6.1.1 [FreeBSD]
> >> Copyright 2004 Free Software Foundation, Inc.
> >> GDB is free software, covered by the GNU General Public License, and you 
are
> >> welcome to change it and/or distribute copies of it under certain
> > conditions.
> >> Type "show copying" to see the conditions.
> >> There is absolutely no warranty for GDB.  Type "show warranty" for 
details.
> >> This GDB was configured as "amd64-marcel-freebsd"...
> >>
> >> Unread portion of the kernel message buffer:
> >>
> >>
> >> Fatal trap 12: page fault while in kernel mode
> >> cpuid = 1; apic id = 01
> >> fault virtual address   = 0xfffffffff5555570
> >> fault code              = supervisor write data, page not present
> >> instruction pointer     = 0x8:0xffffffff807c429b
> >> stack pointer           = 0x10:0xffffffff511e4710
> >> frame pointer           = 0x10:0x20
> >> code segment            = base 0x0, limit 0xfffff, type 0x1b
> >>                         = DPL 0, pres 1, long 1, def32 0, gran 1
> >> processor eflags        = interrupt enabled, resume, IOPL = 0
> >> current process         = 69996 (mkdir)
> >> trap number             = 12
> >> panic: page fault
> >
> > This one does look like a hardware issue from the stack trace.  It's hard 
to
> > know if the first panic you saw was a hardware issue as well without the
> > stack trace information.
> >
> >> #7  0xffffffff807b706e in calltrap ()
> >>     at /usr/src/sys/amd64/amd64/exception.S:209
> >> #8  0xffffffff807c429b in free_pv_entry (pmap=0xffffffff80b66c80,
> >> pv=Variable "pv" is not available.
> >> )
> >>     at /usr/src/sys/amd64/amd64/pmap.c:1905
> >> #9  0xffffffff807c4403 in pmap_remove_entry (pmap=Variable "pmap" is
> >> not available.
> >> )
> >>     at /usr/src/sys/amd64/amd64/pmap.c:2131
> >> #10 0xffffffff807c6447 in pmap_remove_pte (pmap=0xffffffff80b66c80,
> >>     ptq=0xaaaaaaa8, va=18446744070506639360, ptepde=23601251,
> >>     free=0xffffffff511e4790) at /usr/src/sys/amd64/amd64/pmap.c:2366
> >> #11 0xffffffff807cab87 in pmap_remove (pmap=0xffffffff80b66c80,
> >>     sva=18446744070506639360, eva=18446744070506909696)
> >>     at /usr/src/sys/amd64/amd64/pmap.c:2510
> >
> > --
> > John Baldwin
> >
> 
> The remote backup continues to run so there was definitely some issue  
> there. No more reboots, but it wasn't doing that regularly without  
> some additional load.
> 
> Hopefully I can swap parts around until I find the offending item.
> 
> Thanks for your input.

I would try running memtest86 to check your RAM.

-- 
John Baldwin
From randy at psg.com  Wed Jul 15 09:08:21 2009
From: randy at psg.com (Randy Bush)
Date: Wed Jul 15 09:08:28 2009
Subject: boot crash with ddb & break_to_debugger
Message-ID: <m2eisiz533.wl%randy@psg.com>

i386 cvsupped as of yesterday

 ???????????????????????????????????????????
 ?                                         ?
 ?                                         ?               ,        ,
 ?                                         ?              /(        )`
 ?          Welcome to FreeBSD!            ?              \ \___   / |
 ?                                         ?              /- _  `-/  '
 ?                                         ?             (/\/ \ \   /\
 ?  1. Boot FreeBSD [default]              ?             / /   | `    \
 ?  2. Boot FreeBSD with ACPI disabled     ?             O O   ) /    |
 ?  3. Boot FreeBSD in Safe Mode           ?             `-^--'`<     '
 ?  4. Boot FreeBSD in single user mode    ?            (_.)  _  )   /
 ?  5. Boot FreeBSD with verbose logging   ?             `.___/`    /       
 ?  6. Escape to loader prompt             ?               `-----' /
 ?  7. Reboot                              ?  <----.     __ / __   \
 ?                                         ?  <----|====O)))==) \) /====|
 ?                                         ?  <----'    `--' `.__,' \
 ?                                         ?               |        |
 ?                                         ?                \       /       /\
 ?  Select option, [Enter] for default     ?           ______( (_  / \______/
 ?  or [Space] to pause timer  -1          ?         ,'  ,-----'   |
 ???????????????????????????????????????????         `--{__________) 

KDB: debugger backends: ddb
KDB: current backend: ddb
131072K of memory above 4GB ignored
Copyright (c) 1992-2009 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.2-STABLE #28: Wed Jul 15 08:11:56 GMT 2009
    root@psg.com:/usr/obj/usr/src/sys/PSG
kmem_suballoc: bad status return of 3.
panic: kmem_suballoc
cpuid = 0
KDB: enter: panic
[thread pid 0 tid 0 ]
Stopped at      kdb_enter_why+0x3a:     movl    $0,kdb_why
db> trace
Tracing pid 0 tid 0 td 0xc07fad60
kdb_enter_why(c078b1b8,c078b1b8,c079e7a8,c0c20d04,0,...) at kdb_enter_why+0x3a
panic(c079e7a8,3,0,0,c07fb8a0,...) at panic+0x138
kmem_suballoc(c1071000,c07fb8a0,c07fb8a4,40000000,1,...) at kmem_suballoc+0x91
kmeminit(0,c1ec00,c1ec00,c1e000,c25000,...) at kmeminit+0x18a
mi_startup() at mi_startup+0xa6
begin() at begin+0x2c
db>
From amarat at ksu.ru  Wed Jul 15 09:34:42 2009
From: amarat at ksu.ru (Marat N.Afanasyev)
Date: Wed Jul 15 09:34:54 2009
Subject: ATA driver update for 7.2RELEASE available
In-Reply-To: <8EB69F68-8ED2-469C-B83E-2555A72630B4@deepcore.dk>
References: <8EB69F68-8ED2-469C-B83E-2555A72630B4@deepcore.dk>
Message-ID: <4A5DA250.9000902@ksu.ru>

S?ren Schmidt wrote:
> Over the past months I've gotten huge amounts of requests for ATA 
> related things, so I've whipped up what I use here for FreeBSD 7.2-Release.
> 
> This is a total replacement of the ATA driver, modulerized as in 
> -current, but based on my WIP not from what might have happend to 
> -current since I gave up maintainership.
> 
> There is a number of new chipsets supported in here that I dont think is 
> in any of the official sources (havn't checked in quite some time 
> though), mostly newish ATI, nVidia and Marvell chips (yeah those buggers 
> with both ATA & SATA ports).
> 
> You can find and install.sh script and a tarball of the needed files at:
> 
> http://www.deepcore.dk/pub/ATA
> 
> Put both in /usr/src and run install.sh.
> 
> As I dont subscribe to any of the mailing lists nor does my FreeBSD.org 
> mail address seem to work anymore, you will need to reply to me directly 
> if needed.
> 
> As always - Enjoy!
> 
> -S?ren

i think i'm dumb, but can you tell me how can atapicam be enabled with 
this implementation of ata? i couldn't still find a way :(

-- 
SY, Marat

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3221 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090715/5e5e9146/smime.bin
From Johan at double-l.nl  Wed Jul 15 10:45:29 2009
From: Johan at double-l.nl (Johan Hendriks)
Date: Wed Jul 15 10:45:35 2009
Subject: mergemaster ezjails. different behaviour between 7.1 and 7.2 and up
Message-ID: <57200BF94E69E54880C9BB1AF714BBCB5DEA56@w2003s01.double-l.local>

Hello all .

 

I have an issue using mergemaster and ezjail after the update to FreeBSD
7.2 from 7.1

I have several boxes running ezjails from FreeBSD 7.0 to 7.1 and i
always use the same way to update these machines.

 

First a buildworld cycle.
then reboot and make sure jails are not running.
then ezjail-admin update -i
After that i do a mergemaster of the jails.



#mergemaster -iU -D /usr/jails/jail1

on a 7.2 and above system i get the following error.

cd /usr/src/etc/..; install -o root -g wheel -m 444  COPYRIGHT
/var/tmp/temproot/
install -o root -g wheel -m 444
/usr/src/etc/../sys/amd64/conf/GENERIC.hints
 /var/tmp/temproot/boot/device.hints



*** Beginning comparison



   *** Checking /usr/jails/test//etc/rc.d for stale files



   *** No stale files found



  *** There is no installed version of ./boot/device.hints



install: mkdir /usr/jails/test//boot: File exists
install: /usr/jails/test//boot: No such file or directory
*** FATAL ERROR: Unable to install ./boot/device.hints to
/usr/jails/test//boot



jailhost_co test #

 

And it drops me to the commandline again.

On the old 7.0 and 7.1 it works well.
It does not drop to commandline but carries on like the example below.

cd /usr/src/etc/..; install -o root -g wheel -m 444  COPYRIGHT
/var/tmp/temproot/
install -o root -g wheel -m 444
/usr/src/etc/../sys/i386/conf/GENERIC.hints
 /var/tmp/temproot/boot/device.hints



*** Beginning comparison

   *** Checking /usr/jails/ftp/etc/rc.d for stale files

   *** No stale files found


  *** There is no installed version of ./boot/device.hints




install: mkdir /usr/jails/ftp/boot: File exists
install: /usr/jails/ftp/boot: No such file or directory
   *** Problem installing ./boot/device.hints, it will remain to merge
by hand
 *** Temp ./etc/bluetooth/hcsecd.conf and installed have the same CVS
Id, deleting



Here it comes with the

*** Problem installing ./boot/device.hints, it will remain to merge by
hand line
On 7.2 and up (also 8.0BETA1) ir gives me this 
*** FATAL ERROR: Unable to install ./boot/device.hints to
/usr/jails/test//boot



Do i need another option i need to give mergemaster?

 

I hope things are clear, i am not that good in explaining things in
another language.



Regards,

Johan

 

 





From graham at menhennitt.com.au  Wed Jul 15 11:14:14 2009
From: graham at menhennitt.com.au (Graham Menhennitt)
Date: Wed Jul 15 11:14:24 2009
Subject: problem with Soekris net5501 and USB hub
In-Reply-To: <4A5CB6FB.4090808@ksu.ru>
References: <4A5BBD50.2020408@menhennitt.com.au> <4A5CB6FB.4090808@ksu.ru>
Message-ID: <4A5DA2D7.6080709@menhennitt.com.au>

Marat N.Afanasyev wrote:
> Graham Menhennitt wrote:
>> I originally sent this to the Soekris list thinking it was platform
>> specific. I got a couple of replies suggesting that it's a FreeBSD
>> problem instead. So, if anybody can offer any insights, I would most
>> appreciate it.
>>
>> I have a Soekris net5501 running FreeBSD 7-Stable. I want to connect
>> a number of USB devices to it:
>> - a HP Laserjet 1020 printer
>> - an APC Back UPS 350 UPS
>> - a 6-in-one card reader (not so fussed about this one).
>> The Soekris box has only one USB port brought out to a connector on
>> the case, so rather than mod the box to add another port, I thought I
>> would just use an external hub.
>>
>> If I plug any of the devcies directly into the Soekris's USB port it
>> works fine. However, if I use a USB hub then it doesn't work at all.
> see http://www.freebsd.org/cgi/query-pr.cgi?pr=131074 i think your
> case is very similar to mine
Thanks Marat (and the others that replied). It is the same problem as in
that PR - if the devices are connected at boot time everything works. If
I power them on later it doesn't. For now that will be my workaround.
I'll look at upgrading to 8 some time soon.

Thanks again,
  Graham
From ianjhart at ntlworld.com  Wed Jul 15 13:48:25 2009
From: ianjhart at ntlworld.com (Ian J Hart)
Date: Wed Jul 15 13:48:32 2009
Subject: trap 12
In-Reply-To: <200907141300.16634.jhb@freebsd.org>
References: <20090714145101.60515vh49s7o7c4k@10.248.192.16>
	<200907141300.16634.jhb@freebsd.org>
Message-ID: <20090715144756.107076ji8zo2oh0k@10.248.192.16>

Quoting John Baldwin <jhb@freebsd.org>:

> On Tuesday 14 July 2009 9:51:01 am Ian J Hart wrote:
>> Quoting John Baldwin <jhb@freebsd.org>:
>>
>> > On Tuesday 07 July 2009 5:51:03 am Ian J Hart wrote:
>> >> Quoting Ian J Hart <ianjhart@ntlworld.com>:
>> >>
>> >>> Quoting Ian J Hart <ianjhart@ntlworld.com>:
>> >>>
>> >>>> Is this likely to be hardware? Details will follow if not.
>> >>>>
>> >>>> [copied from a screen dump]
>> >>>>
>> >>>> Fatal trap 12: page fault while in kernel mode
>> >>>> cpuid = 1; apic id = 01
>> >>>> fault virtual address = 0x0
>> >>>> fault code = supervisor write data, page not present
>> >>>> instruction pointer = 0x8:0xffffffff807c6c12
>> >>>> stack pointer = 0x10:0xffffffff510e7890
>> >>>> frame pointer = 0x10:0xffffff00054a6c90
>> >>>> code segment = base 0x0, limit 0xfffff, type 0x1b
>> >>>> = DPL 0, pres 1, long 1 def32 0, gran 1
>> >>>> processor eflags = interrupt enabled, resume, IOPL = 0
>> >>>> current process = 75372 (printf)
>> >>>> trap number = 12
>> >>>> panic: page fault
>> >>>> cpuid = 1
>> >>>> uptime: 8m2s
>> >>>> Cannot dump. No dump device defined.
>> >>>>
>> >>>>
>> >>>  Ran crashinfo, now have much more info than I need ;)
>> >>>
>> >>>  Starting another portupgrade run now to see how reproducable this is.
>> >>>
>> >>>  Later BIOS waiting in USB floppy.
>> >>>
>> >> [snip dmesg]
>> >>
>> >> It took 2 runs of portupgrade -af.Some corruption in the dbs may have
>> >> to pkg_delete -a.
>> >>
>> >> FreeBSD * 7.2-RELEASE-p1 FreeBSD 7.2-RELEASE-p1 #0: Tue Jun 16
>> >> 18:03:10 BST 2009     *@*:/usr/obj/usr/src/sys/GENERIC  amd64
>> >>
>> >> panic: page fault
>> >>
>> >> GNU gdb 6.1.1 [FreeBSD]
>> >> Copyright 2004 Free Software Foundation, Inc.
>> >> GDB is free software, covered by the GNU General Public License, and you
> are
>> >> welcome to change it and/or distribute copies of it under certain
>> > conditions.
>> >> Type "show copying" to see the conditions.
>> >> There is absolutely no warranty for GDB.  Type "show warranty" for
> details.
>> >> This GDB was configured as "amd64-marcel-freebsd"...
>> >>
>> >> Unread portion of the kernel message buffer:
>> >>
>> >>
>> >> Fatal trap 12: page fault while in kernel mode
>> >> cpuid = 1; apic id = 01
>> >> fault virtual address   = 0xfffffffff5555570
>> >> fault code              = supervisor write data, page not present
>> >> instruction pointer     = 0x8:0xffffffff807c429b
>> >> stack pointer           = 0x10:0xffffffff511e4710
>> >> frame pointer           = 0x10:0x20
>> >> code segment            = base 0x0, limit 0xfffff, type 0x1b
>> >>                         = DPL 0, pres 1, long 1, def32 0, gran 1
>> >> processor eflags        = interrupt enabled, resume, IOPL = 0
>> >> current process         = 69996 (mkdir)
>> >> trap number             = 12
>> >> panic: page fault
>> >
>> > This one does look like a hardware issue from the stack trace.  It's hard
> to
>> > know if the first panic you saw was a hardware issue as well without the
>> > stack trace information.
>> >
>> >> #7  0xffffffff807b706e in calltrap ()
>> >>     at /usr/src/sys/amd64/amd64/exception.S:209
>> >> #8  0xffffffff807c429b in free_pv_entry (pmap=0xffffffff80b66c80,
>> >> pv=Variable "pv" is not available.
>> >> )
>> >>     at /usr/src/sys/amd64/amd64/pmap.c:1905
>> >> #9  0xffffffff807c4403 in pmap_remove_entry (pmap=Variable "pmap" is
>> >> not available.
>> >> )
>> >>     at /usr/src/sys/amd64/amd64/pmap.c:2131
>> >> #10 0xffffffff807c6447 in pmap_remove_pte (pmap=0xffffffff80b66c80,
>> >>     ptq=0xaaaaaaa8, va=18446744070506639360, ptepde=23601251,
>> >>     free=0xffffffff511e4790) at /usr/src/sys/amd64/amd64/pmap.c:2366
>> >> #11 0xffffffff807cab87 in pmap_remove (pmap=0xffffffff80b66c80,
>> >>     sva=18446744070506639360, eva=18446744070506909696)
>> >>     at /usr/src/sys/amd64/amd64/pmap.c:2510
>> >
>> > --
>> > John Baldwin
>> >
>>
>> The remote backup continues to run so there was definitely some issue
>> there. No more reboots, but it wasn't doing that regularly without
>> some additional load.
>>
>> Hopefully I can swap parts around until I find the offending item.
>>
>> Thanks for your input.
>
> I would try running memtest86 to check your RAM.
>
> --
> John Baldwin
>

It's ECC and was extensively tested when new so I suspect it's  
something else, but I'll memtest it overnight anyway.

Sat at a panic when I went to put the floppy in.No debugger prompt and  
unresponsive so I power cycled it :(

-- 
ian j hart

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


From sos at deepcore.dk  Wed Jul 15 14:48:55 2009
From: sos at deepcore.dk (=?ISO-8859-1?Q?S=F8ren_Schmidt?=)
Date: Wed Jul 15 14:49:03 2009
Subject: ATA driver update for 7.2RELEASE available
In-Reply-To: <4A5DA250.9000902@ksu.ru>
References: <8EB69F68-8ED2-469C-B83E-2555A72630B4@deepcore.dk>
	<4A5DA250.9000902@ksu.ru>
Message-ID: <E2602E41-651C-44FA-9290-F4CD8EB3B724@deepcore.dk>

On 15Jul, 2009, at 11:33 , Marat N.Afanasyev wrote:

> S?ren Schmidt wrote:
>> Over the past months I've gotten huge amounts of requests for ATA  
>> related things, so I've whipped up what I use here for FreeBSD 7.2- 
>> Release.
>> This is a total replacement of the ATA driver, modulerized as in - 
>> current, but based on my WIP not from what might have happend to - 
>> current since I gave up maintainership.
>> There is a number of new chipsets supported in here that I dont  
>> think is in any of the official sources (havn't checked in quite  
>> some time though), mostly newish ATI, nVidia and Marvell chips  
>> (yeah those buggers with both ATA & SATA ports).
>> You can find and install.sh script and a tarball of the needed  
>> files at:
>> http://www.deepcore.dk/pub/ATA
>> Put both in /usr/src and run install.sh.
>> As I dont subscribe to any of the mailing lists nor does my  
>> FreeBSD.org mail address seem to work anymore, you will need to  
>> reply to me directly if needed.
>> As always - Enjoy!
>> -S?ren
>
> i think i'm dumb, but can you tell me how can atapicam be enabled  
> with this implementation of ata? i couldn't still find a way :(


You could just grap atapi-cam.c from stock 7.2 and use that I guess  
(as a module or compiled in), newer used it though...

-S?ren
--









From hiyorin at gmail.com  Thu Jul 16 07:06:02 2009
From: hiyorin at gmail.com (C. C. Tang)
Date: Thu Jul 16 07:06:09 2009
Subject: 7.2-release/amd64: panic, spin lock held too long
In-Reply-To: <3bbf2fe10907080250q35899d3dhc2f101b62c6e5306@mail.gmail.com>
References: <cf9b1ee00907061812r3da70018i1c8d8d12bb038a80@mail.gmail.com>	<3bbf2fe10907061818v245abd0cgc3ca5073cb93aea4@mail.gmail.com>	<cf9b1ee00907061825r34165c48x6727c50b3219d5fb@mail.gmail.com>	<3bbf2fe10907061827g35eaeb49g26cf6fdb64436ca7@mail.gmail.com>	<cf9b1ee00907071757i169d2a82la260798f364054f9@mail.gmail.com>	<cf9b1ee00907080018s3f32c8afr4f65f01ce9ff1f25@mail.gmail.com>
	<3bbf2fe10907080250q35899d3dhc2f101b62c6e5306@mail.gmail.com>
Message-ID: <4A5ECC8C.7030808@gmail.com>

Attilio Rao wrote:
> 2009/7/8 Dan Naumov <dan.naumov@gmail.com>:
>> On Wed, Jul 8, 2009 at 3:57 AM, Dan Naumov<dan.naumov@gmail.com> wrote:
>>> On Tue, Jul 7, 2009 at 4:27 AM, Attilio Rao<attilio@freebsd.org> wrote:
>>>> 2009/7/7 Dan Naumov <dan.naumov@gmail.com>:
>>>>> On Tue, Jul 7, 2009 at 4:18 AM, Attilio Rao<attilio@freebsd.org> wrote:
>>>>>> 2009/7/7 Dan Naumov <dan.naumov@gmail.com>:
>>>>>>> I just got a panic following by a reboot a few seconds after running
>>>>>>> "portsnap update", /var/log/messages shows the following:
>>>>>>>
>>>>>>> Jul  7 03:49:38 atom syslogd: kernel boot file is /boot/kernel/kernel
>>>>>>> Jul  7 03:49:38 atom kernel: spin lock 0xffffffff80b3edc0 (sched lock
>>>>>>> 1) held by 0xffffff00017d8370 (tid 100054) too long
>>>>>>> Jul  7 03:49:38 atom kernel: panic: spin lock held too long
>>>>>> That's a known bug, affecting -CURRENT as well.
>>>>>> The cpustop IPI is handled though an NMI, which means it could
>>>>>> interrupt a CPU in any moment, even while holding a spinlock,
>>>>>> violating one well known FreeBSD rule.
>>>>>> That means that the cpu can stop itself while the thread was holding
>>>>>> the sched lock spinlock and not releasing it (there is no way, modulo
>>>>>> highly hackish, to fix that).
>>>>>> In the while hardclock() wants to schedule something else to run and
>>>>>> got stuck on the thread lock.
>>>>>>
>>>>>> Ideal fix would involve not using a NMI for serving the cpustop while
>>>>>> having a cheap way (not making the common path too hard) to tell
>>>>>> hardclock() to avoid scheduling while cpustop is in flight.
>>>>>>
>>>>>> Thanks,
>>>>>> Attilio
>>>>> Any idea if a fix is being worked on and how unlucky must one be to
>>>>> run into this issue, should I expect it to happen again? Is it
>>>>> basically completely random?
>>>> I'd like to work on that issue before BETA3 (and backport to
>>>> STABLE_7), I'm just time-constrained right now.
>>>> it is completely random.
>>>>
>>>> Thanks,
>>>> Attilio
>>> Ok, this is getting pretty bad, 23 hours later, I get the same kind of
>>> panic, the only difference is that instead of "portsnap update", this
>>> was triggered by "portsnap cron" which I have running between 3 and 4
>>> am every day:
>>>
>>> Jul  8 03:03:49 atom kernel: ssppiinn  lloocckk
>>> 00xxffffffffffffffff8800bb33eeddc400  ((sscchheedd  lloocck k1 )0 )h
>>> ehledl db yb y 0x0xfffffffffff0f00001081735339760e 0( t(itdi d
>>> 10100006070)5 )t otoo ol olnogng
>>> Jul  8 03:03:49 atom kernel: p
>>> Jul  8 03:03:49 atom kernel: anic: spin lock held too long
>>> Jul  8 03:03:49 atom kernel: cpuid = 0
>>> Jul  8 03:03:49 atom kernel: Uptime: 23h2m38s
>> I have now tried repeating the problem by running "stress --cpu 8 --io
>> 8 --vm 4 --vm-bytes 1024M --timeout 600s --verbose" which pushed
>> system load into the 15.50 ballpark and simultaneously running
>> "portsnap fetch" and "portsnap update" but I couldn't manually trigger
>> the panic, it seems that this problem is indeed random (although it
>> baffles me why is it specifically portsnap triggering it). I have now
>> disabled powerd to check whether that makes any difference to system
>> stability.
> 
> But is that happening at reboot time?
> 
> Thanks,
> Attilio
> 

I think I am also having similar problem on my Atom machine. 
(FreeBSD-7.2-Release-p1)
It does not happen at boot/reboot but panic randomly.
And I found that it remains stable for more than a month now after I 
disabled powerd... (although I want to have it enabled)

--
C.C.
From pluknet at gmail.com  Thu Jul 16 07:08:06 2009
From: pluknet at gmail.com (pluknet)
Date: Thu Jul 16 07:09:37 2009
Subject: [bce] panic on boot in bce(4) on 7.2: invalid ife->ifm_data (0xa)
Message-ID: <a31046fc0907160008x7263d78esdddcaf3efc1ea5f8@mail.gmail.com>

Hi.

I got the following kernel panic on boot:
invalid ife->ifm_data (0xa) in mii_phy_setmedia

This is near /sys/dev/mii/mii_physubr.c:126
        KASSERT(ife->ifm_data >=0 && ife->ifm_data < MII_NMEDIA,
            ("invalid ife->ifm_data (0x%x) in mii_phy_setmedia",
            ife->ifm_data));

Kernel is 7.2 GENERIC plus debug options:
options         KDB
options         DDB
options         LOCK_PROFILING
options         INVARIANTS              # Enable calls of extra sanity checking
options         INVARIANT_SUPPORT       # Extra sanity checks of
internal structures, required by INVARIANTS
options         WITNESS                 # Enable checks to detect
deadlocks and cycles
options         DEBUG_LOCKS
options         DEBUG_VFS_LOCKS
options         DIAGNOSTIC
options         BREAK_TO_DEBUGGER
options         STACK

I have no the serial connection on this box this time,
so ddb pictures captured with a camera are here:
http://test.myrz.ru/tmp/panic_on_bce/

Verbose dmesg from stock GENERIC attached.

bce0@pci0:11:0:0:       class=0x020000 card=0x03a91014 chip=0x163914e4
rev=0x20 hdr=0x00
    vendor     = 'Broadcom Corporation'
    device     = 'NetXtreme II BCM5709 Gigabit Ethernet'
    class      = network
    subclass   = ethernet
bce1@pci0:11:0:1:       class=0x020000 card=0x03a91014 chip=0x163914e4
rev=0x20 hdr=0x00
    vendor     = 'Broadcom Corporation'
    device     = 'NetXtreme II BCM5709 Gigabit Ethernet'
    class      = network
    subclass   = ethernet


-- 
wbr,
pluknet
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dmesg.verbose
Type: application/octet-stream
Size: 55464 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090716/0a6f23d3/dmesg.obj
From dan.naumov at gmail.com  Thu Jul 16 08:54:46 2009
From: dan.naumov at gmail.com (Dan Naumov)
Date: Thu Jul 16 08:54:53 2009
Subject: 7.2-release/amd64: panic, spin lock held too long
In-Reply-To: <4A5ECC8C.7030808@gmail.com>
References: <cf9b1ee00907061812r3da70018i1c8d8d12bb038a80@mail.gmail.com>
	<3bbf2fe10907061818v245abd0cgc3ca5073cb93aea4@mail.gmail.com>
	<cf9b1ee00907061825r34165c48x6727c50b3219d5fb@mail.gmail.com>
	<3bbf2fe10907061827g35eaeb49g26cf6fdb64436ca7@mail.gmail.com>
	<cf9b1ee00907071757i169d2a82la260798f364054f9@mail.gmail.com>
	<cf9b1ee00907080018s3f32c8afr4f65f01ce9ff1f25@mail.gmail.com>
	<3bbf2fe10907080250q35899d3dhc2f101b62c6e5306@mail.gmail.com>
	<4A5ECC8C.7030808@gmail.com>
Message-ID: <cf9b1ee00907160154j4311483by9d391d3d536995d6@mail.gmail.com>

>> But is that happening at reboot time?
>>
>> Thanks,
>> Attilio
>>
>
> I think I am also having similar problem on my Atom machine.
> (FreeBSD-7.2-Release-p1)
> It does not happen at boot/reboot but panic randomly.
> And I found that it remains stable for more than a month now after I
> disabled powerd... (although I want to have it enabled)

I hope you can get some crash dumps for the developers to look at,
Attilio was trying to help me but sadly the machine had to be put into
active use so I could no longer play with FreeBSD due to unsolved
instability.

- Sincerely,
Dan Naumov
From amarat at ksu.ru  Thu Jul 16 09:43:06 2009
From: amarat at ksu.ru (Marat N.Afanasyev)
Date: Thu Jul 16 09:43:14 2009
Subject: coretemp(4) build broken in recent STABLE?
Message-ID: <4A5EF609.10000@ksu.ru>

i have 7.2-S csupped to today midnight and while trying to build kernel 
i have the following error:

===> coretemp (all)
cc -O2 -fno-strict-aliasing -pipe -O2 -pipe -msse2 -msse3 -m3dnow 
-march=athlon64  -D_KERNEL -DKLD_MODULE -std=c99 -nostdinc 
-DHAVE_KERNEL_OPTION_HEADERS -include 
/usr/obj/usr/src/sys/ZEALOT/opt_global.h -I. -I@ -I@/contrib/altq 
-finline-limit=8000 --param inline-unit-growth=100 --param 
large-function-growth=1000 -fno-common -g -fno-omit-frame-pointer 
-I/usr/obj/usr/src/sys/ZEALOT -mcmodel=kernel -mno-red-zone 
-mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow  -msoft-float 
-fno-asynchronous-unwind-tables -ffreestanding -Wall -Wredundant-decls 
-Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes 
-Wpointer-arith -Winline -Wcast-qual  -Wundef -Wno-pointer-sign 
-fformat-extensions -c 
/usr/src/sys/modules/coretemp/../../dev/coretemp/coretemp.c
/usr/src/sys/modules/coretemp/../../dev/coretemp/coretemp.c: In function 
'coretemp_identify':
/usr/src/sys/modules/coretemp/../../dev/coretemp/coretemp.c:98: error: 
'cpu_vendor_id' undeclared (first use in this function)
/usr/src/sys/modules/coretemp/../../dev/coretemp/coretemp.c:98: error: 
(Each undeclared identifier is reported only once
/usr/src/sys/modules/coretemp/../../dev/coretemp/coretemp.c:98: error: 
for each function it appears in.)
/usr/src/sys/modules/coretemp/../../dev/coretemp/coretemp.c:98: error: 
'CPU_VENDOR_INTEL' undeclared (first use in this function)
*** Error code 1

Stop in /usr/src/sys/modules/coretemp.
*** Error code 1

i've tried to find either cpu_vendor_id or CPU_VENDOR_INTEL in source 
tree, but didn't succeeded. can anybody reproduce this error? and can 
anybody tell how to fix it? :)

-- 
SY, Marat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3221 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090716/09029807/smime.bin
From avg at freebsd.org  Thu Jul 16 11:05:46 2009
From: avg at freebsd.org (Andriy Gapon)
Date: Thu Jul 16 11:05:53 2009
Subject: coretemp(4) build broken in recent STABLE?
In-Reply-To: <4A5EF609.10000@ksu.ru>
References: <4A5EF609.10000@ksu.ru>
Message-ID: <4A5F0958.4050504@freebsd.org>

on 16/07/2009 12:42 Marat N.Afanasyev said the following:
> i have 7.2-S csupped to today midnight and while trying to build kernel
> i have the following error:
[snip]
> i've tried to find either cpu_vendor_id or CPU_VENDOR_INTEL in source
> tree, but didn't succeeded. can anybody reproduce this error? and can
> anybody tell how to fix it? :)

It seems that you are using CVSup server with out-of-sync data.
This has already been discussed, but not on the public mailing lists.
In that case the offending server was cvsup7.ru.FreeBSD.org

-- 
Andriy Gapon
From amarat at ksu.ru  Thu Jul 16 11:16:05 2009
From: amarat at ksu.ru (Marat N.Afanasyev)
Date: Thu Jul 16 11:16:23 2009
Subject: coretemp(4) build broken in recent STABLE?
In-Reply-To: <4A5F0958.4050504@freebsd.org>
References: <4A5EF609.10000@ksu.ru> <4A5F0958.4050504@freebsd.org>
Message-ID: <4A5F0BD2.6060105@ksu.ru>

Andriy Gapon wrote:
> on 16/07/2009 12:42 Marat N.Afanasyev said the following:
>> i have 7.2-S csupped to today midnight and while trying to build kernel
>> i have the following error:
> [snip]
>> i've tried to find either cpu_vendor_id or CPU_VENDOR_INTEL in source
>> tree, but didn't succeeded. can anybody reproduce this error? and can
>> anybody tell how to fix it? :)
> 
> It seems that you are using CVSup server with out-of-sync data.
> This has already been discussed, but not on the public mailing lists.
> In that case the offending server was cvsup7.ru.FreeBSD.org
> 
it seems so

-- 
SY, Marat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3221 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090716/f8966b43/smime.bin
From jb000003 at mr-happy.com  Thu Jul 16 19:01:47 2009
From: jb000003 at mr-happy.com (Jeff Blank)
Date: Thu Jul 16 19:01:55 2009
Subject: 7.2-STABLE amd64 panic at/after mount root (ZFS)
Message-ID: <20090716190144.GB88257@mr-happy.com>

Hi,

I've built RELENG_7 from sources csupped at around 0700 UTC today.
'make installkernel', reboot, panic:

=====
Trying to mount root from zfs:zgm0/root


Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x0
fault code              = supervisor read data, page not present
instruction pointer     = 0x8:0xffffffff80da14fd
stack pointer           = 0x10:0xffffff800001efd0
frame pointer           = 0x10:0xffffff800001f020
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 1 (swapper)
trap number             = 12
panic: page fault
cpuid = 0
GEOM_MIRROR: Device gm0: rebuilding provider ad4 stopped.
Uptime: 8s
Cannot dump. No dump device defined.
Automatic reboot in 15 seconds - press a key on the console to abort
=====

My ZFS pool is from well before the recent ZFS MFC.  The full text of
the boot-up is below, along with loader.conf.

As maybe something of a side note, I rebuilt the kernel with

options         DDB
options         KDB
options         KDB_UNATTENDED
options         BREAK_TO_DEBUGGER

added to GENERIC, but I'm unable to access the debugger fully.  Using
vidconsole, a USB keyboard is non-responsive once the panic occurs,
and this system has no PS/2 ports.  I tried using comconsole, but this
system appears to have squirrely serial as well, so while I can "press
a key" and get a ddb prompt, what I type does not show up or shows up
as something else, as though there's a baud-rate mismatch.
(comconsole works fine from the loader to the ddb prompt, but it fails
to be useful once that point is reached.)  Does anyone have any
suggestions as to how I can access the debugger?

Thank you for any help with any of this.

Jeff



/boot/loader.conf:
=====
beastie_disable=YES
atapicam_load=YES
snd_hda_load=YES
snd_driver_load=NO
linux_load=YES
geom_mirror_load=YES
hw.pci.enable_msi=0
zfs_load=YES
vfs.zfs.arc_max=256M
vfs.root.mountfrom="zfs:zgm0/root"
=====

console output:
=====
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 1992-2009 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.2-STABLE #0: Thu Jul 16 13:26:59 EDT 2009
    root@bender.tc.mtu.edu:/usr/obj/usr/src/sys/DEBUG
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 5600+ (2906.09-MHz K8-class CPU)
  Origin = "AuthenticAMD"  Id = 0x60fb2  Stepping = 2
  Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,C
MOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
  Features2=0x2001<SSE3,CX16>
  AMD Features=0xea500800<SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow!>
  AMD Features2=0x11f<LAHF,CMP,SVM,ExtAPIC,CR8,Prefetch>
  TSC: P-state invariant
  Cores per package: 2
usable memory = 4277772288 (4079 MB)
avail memory  = 4097368064 (3907 MB)
ACPI APIC Table: <DELL   bMk    >
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
This module (opensolaris) contains code covered by the
Common Development and Distribution License (CDDL)
see http://opensolaris.org/os/licensing/opensolaris_license/
ioapic0: Changing APIC ID to 4
ioapic0 <Version 1.1> irqs 0-23 on motherboard
kbd0 at kbdmux0
acpi0: <DELL bMk    > on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: reservation of 0, a0000 (3) failed
acpi0: reservation of 100000, bfdd0000 (3) failed
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
acpi_hpet0: <High Precision Event Timer> iomem 0xfeff0000-0xfeff03ff on acpi0
Timecounter "HPET" frequency 25000000 Hz quality 900
acpi_button0: <Power Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pci0: <memory, RAM> at device 0.0 (no driver attached)
pci0: <memory, RAM> at device 0.1 (no driver attached)
pci0: <memory, RAM> at device 0.2 (no driver attached)
pci0: <memory, RAM> at device 0.3 (no driver attached)
pci0: <memory, RAM> at device 0.4 (no driver attached)
pci0: <memory, RAM> at device 0.5 (no driver attached)
pci0: <memory, RAM> at device 0.6 (no driver attached)
pci0: <memory, RAM> at device 0.7 (no driver attached)
pcib1: <ACPI PCI-PCI bridge> at device 2.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pcib2: <ACPI PCI-PCI bridge> at device 3.0 on pci0
pci2: <ACPI PCI bus> on pcib2
bge0: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0xb002> mem 0xf
d8f0000-0xfd8fffff irq 16 at device 0.0 on pci2
miibus0: <MII bus> on bge0
brgphy0: <BCM5787 10/100/1000baseTX PHY> PHY 1 on miibus0
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-F
DX, auto
bge0: Ethernet address: 00:1e:c9:44:30:14
bge0: [ITHREAD]
pcib3: <ACPI PCI-PCI bridge> at device 4.0 on pci0
pci3: <ACPI PCI bus> on pcib3
vgapci0: <VGA-compatible display> port 0xbc00-0xbcff mem 0xd0000000-0xdfffffff,0
xfddf0000-0xfddfffff irq 16 at device 0.0 on pci3
vgapci1: <VGA-compatible display> mem 0xfdde0000-0xfddeffff at device 0.1 on pci
3
pci0: <memory, RAM> at device 9.0 (no driver attached)
isab0: <PCI-ISA bridge> port 0x1d00-0x1dff at device 10.0 on pci0
isa0: <ISA bus> on isab0
pci0: <serial bus, SMBus> at device 10.1 (no driver attached)
pci0: <memory, RAM> at device 10.2 (no driver attached)
ohci0: <OHCI (generic) USB controller> mem 0xfe02f000-0xfe02ffff irq 21 at devic
e 11.0 on pci0
ohci0: [GIANT-LOCKED]
ohci0: [ITHREAD]
usb0: OHCI version 1.0, legacy support
usb0: SMM does not respond, resetting
usb0: <OHCI (generic) USB controller> on ohci0
usb0: USB revision 1.0
uhub0: <nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
uhub0: 8 ports with 8 removable, self powered
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xfe02e000-0xfe02e0ff irq 22 at d
evice 11.1 on pci0
ehci0: [GIANT-LOCKED]
ehci0: [ITHREAD]
usb1: EHCI version 1.0
usb1: companion controller, 8 ports each: usb0
usb1: <EHCI (generic) USB 2.0 controller> on ehci0
usb1: USB revision 2.0
uhub1: <nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb1
uhub1: 8 ports with 8 removable, self powered
atapci0: <nVidia nForce MCP51 SATA300 controller> port 0x9f0-0x9f7,0xbf0-0xbf3,0
x970-0x977,0xb70-0xb73,0xe000-0xe00f mem 0xfe02d000-0xfe02dfff irq 23 at device 
14.0 on pci0
atapci0: [ITHREAD]
ata2: <ATA channel 0> on atapci0
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci0
ata3: [ITHREAD]
atapci1: <nVidia nForce MCP51 SATA300 controller> port 0x9e0-0x9e7,0xbe0-0xbe3,0
x960-0x967,0xb60-0xb63,0xcc00-0xcc0f mem 0xfe02c000-0xfe02cfff irq 20 at device 
15.0 on pci0
atapci1: [ITHREAD]
ata4: <ATA channel 0> on atapci1
ata4: [ITHREAD]
ata5: <ATA channel 1> on atapci1
ata5: [ITHREAD]
pcib4: <ACPI PCI-PCI bridge> at device 16.0 on pci0
pci4: <ACPI PCI bus> on pcib4
txp0: <3Com 3cR990-SRV-97 Etherlink Server with 3XP Processor> port 0x9c00-0x9c7
f mem 0xfdcc0000-0xfdcfffff irq 16 at device 8.0 on pci4
txp0: Typhoon 1.0 sleep image (2000/07/07)
txp0: Ethernet address: 00:04:76:f8:0c:b2
txp0: [FILTER]
hdac0: <NVidia MCP51 High Definition Audio Controller> mem 0xfe024000-0xfe027fff
 irq 21 at device 16.1 on pci0
hdac0: HDA Driver Revision: 20090624_0136
hdac0: [ITHREAD]
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A, console
sio0: [FILTER]
ppc0: <Parallel port> port 0x378-0x37f irq 7 on acpi0
ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
ppbus0: <Parallel port bus> on ppc0
ppbus0: [ITHREAD]
ppi0: <Parallel I/O> on ppbus0
plip0: <PLIP network interface> on ppbus0
plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppc0: [GIANT-LOCKED]
ppc0: [ITHREAD]
cpu0: <ACPI CPU> on acpi0
powernow0: <PowerNow! K8> on cpu0
cpu1: <ACPI CPU> on acpi0
powernow1: <PowerNow! K8> on cpu1
orm0: <ISA Option ROM> at iomem 0xc0000-0xcf7ff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
ukbd0: <vendor 0x0757 product 0x0a00, class 0/0, rev 1.10/0.01, addr 2> on uhub0
kbd1 at ukbd0
ums0: <vendor 0x0757 product 0x0a00, class 0/0, rev 1.10/0.01, addr 2> on uhub0
ums0: 3 buttons and Z dir.
ums1: <Contour Design Contour Perfit Mouse, class 0/0, rev 1.10/0.01, addr 3> on
 uhub0
ums1: 5 buttons and Z dir.
WARNING: ZFS is considered to be an experimental feature in FreeBSD.
Timecounters tick every 1.000 msec
ZFS filesystem version 13
ZFS storage pool version 13
ad4: 152587MB <SAMSUNG HE160HJ JF800-24> at ata2-master SATA300
ad6: 152587MB <SAMSUNG HE160HJ JF800-24> at ata3-master SATA300
GEOM_MIRROR: Device mirror/gm0 launched (1/2).
GEOM_MIRROR: Device gm0: rebuilding provider ad4.
acd0: CDROM <PBDS CD-ROM DH-48N1S/BD11> at ata4-master SATA150
acd1: CDRW <TSSTcorp CD-RW/DVD-ROM TS-H493B/D200> at ata5-master SATA150
hdac0: HDA Codec #0: Sigmatel STAC9220
pcm0: <HDA Sigmatel STAC9220 PCM #0 Analog> at cad 0 nid 1 on hdac0
acd1: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 
(probe1:ata3:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 
(probe1:ata3:0:0:0): CAM Status: SCSI Status Error
(probe1:ata3:0:0:0): SCSI Status: Check Condition
(probe1:ata3:0:0:0): NOT READY asc:3a,1
(probe1:ata3:0:0:0): Medium not present - tray closed
(probe1:ata3:0:0:0): Unretryable error
acd1: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 
acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 
(probe0:ata2:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 
(probe0:ata2:0:0:0): CAM Status: SCSI Status Error
(probe0:ata2:0:0:0): SCSI Status: Check Condition
(probe0:ata2:0:0:0): NOT READY asc:3a,0
(probe0:ata2:0:0:0): Medium not present
(probe0:ata2:0:0:0): Unretryable error
acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 
cd1 at ata3 bus 0 target 0 lun 0
cd1: <TSSTcorp CDRWDVD TS-H493B D200> Removable CD-ROM SCSI-0 device 
cd1: 3.300MB/s transfers
cd1: Attempt to query device size failed: NOT READY, Medium not present - tray c
losed
SMP: AP CPU #1 Launched!
cd0 at ata2 bus 0 target 0 lun 0
cd0: <PBDS CD-ROM DH-48N1S BD11> Removable CD-ROM SCSI-0 device 
cd0: 3.300MB/s transfers
cd0: Attempt to query device size failed: NOT READY, Medium not present
Trying to mount root from zfs:zgm0/root


Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x0
fault code              = supervisor read data, page not present
instruction pointer     = 0x8:0xffffffff80da14fd
stack pointer           = 0x10:0xffffff800001efd0
frame pointer           = 0x10:0xffffff800001f020
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 1 (swapper)
trap number             = 12
panic: page fault
cpuid = 0
GEOM_MIRROR: Device gm0: rebuilding provider ad4 stopped.
Uptime: 8s
Cannot dump. No dump device defined.
Automatic reboot in 15 seconds - press a key on the console to abort
=====
From oberman at es.net  Thu Jul 16 19:11:30 2009
From: oberman at es.net (Kevin Oberman)
Date: Thu Jul 16 19:11:37 2009
Subject: 8.0-BETA1 Source Upgrade breaks NTP configuration 
In-Reply-To: Your message of "Thu, 09 Jul 2009 12:11:19 +1000."
	<20090709021119.GA26896@rwpc12.mby.riverwillow.net.au> 
Message-ID: <20090716191129.13B041CC0D@ptavv.es.net>

> Date: Thu, 9 Jul 2009 12:11:19 +1000
> From: John Marshall <john.marshall@riverwillow.com.au>
> Sender: owner-freebsd-stable@freebsd.org
> 
> Yesterday I source-upgraded a 7.2-RELEASE-p2 test i386 server to
> 8.0-BETA1.  I have just discovered that it broke that server's NTP
> service.
> 
> PROBLEM 1 - Existing /etc/ntp.conf overwritten
> 
> For source upgrades I run "mergemaster -iCPU" and it has served me well
> until now.  Mergemaster appeared to run "as normal" for this upgrade,
> prompting me for decisions on how to deal with the handful of usual
> files.  It didn't tell me that it had decided to overwrite my existing
> /etc/ntp.conf with the new default version from the source tree!  (OK,
> perhaps it told me in the big, long list at the end but it didn't prompt
> me to supersede my existing file).
> 
> Looking at the mergemaster(8) man page, I can't see how the options I
> use would have resulted in my existing /etc/ntp.conf being overwritten
> with the version from the source tree - but obviously there is a woops
> factor there, either with me or mergemaster.
> 
> Digging deeper, it looks like it may be due to the fact that this is a
> new supplied file and an entry for /etc/ntp.conf didn't exist in
> /var/db/mergemaster.mtree from the previous (7.2-RELEASE) run.  How
> should this be handled?
> 
> PROBLEM 2 - Default ntp.conf uses LOCAL clock
> 
> So, having had the FreeBSD upgrade magically re-configure my NTP server
> (no, I wasn't prompted to overwrite ntp.conf), I find that my NTP server
> is now synchronizing with it's own (potentially wrong) local system
> clock!  Our firewall is configured to allow NTP traffic between our
> internal NTP servers and specific upstream NTP servers.  The default
> configuration file specifies different servers which we don't use, so
> this NTP server couldn't "see" them.
> 
> The new default configuration file includes "127.127.1.0" as a
> configured server.  Because we could see no "real" NTP servers, we
> synchronized with our local system clock.  That means that we think we
> are synchronized to a reliable upstream source.  Rather than losing
> synch and discovering the problem, we think we are synchronized to a
> reliable source and we and our clients drift away from reality in
> blissful ignorance.  Surely this violates POLA!
> 
> Could we *please* at least comment out the LOCAL server config in the
> supplied ntp.conf?  Personally I would rather see it removed.  It is one
> thing to tell people where the gun is if they want to shoot themselves
> in the foot; it's another thing to load it and fire it for them.
> 
> I think it is good to have a default ntp.conf to help new users get
> started.  I think it is a bad thing to include potentially dangerous
> elements in that configuration which could cause grief to a novice NTP
> administrator.  If the default configuration provides scope for such
> surprises, they will (rightly) blame FreeBSD.
> 
> -- 
> John Marshall

John,

Both of these problems have been reported and Doug is working on a fix
for mergemaster to deal with the case where a new file is added to /etc
but a file of the same named already exists.

I also reported the issue with LOCAL and a fix for this is also in the
pipe. When 8.0 is released, I'm pretty sure that ntp.conf will look a
bit different from what you see and it won't overwrite the existing file
(at least without asking).
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@es.net			Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4  EADA 927D EBB3 987B 3751
From oberman at es.net  Thu Jul 16 19:16:29 2009
From: oberman at es.net (Kevin Oberman)
Date: Thu Jul 16 19:16:36 2009
Subject: Posts regarding 8.0-beta
Message-ID: <20090716191624.50BFB1CC0D@ptavv.es.net>

Just a reminder...there is no 8-stable as of today nor is there a
RELENG_8 branch in CVS. Posts regarding 8.0 should go to current@. The
folks who are most likely able to help with 8.0 problems are more likely
to see it there and, if you are watching current@, you may see that the
issue you are reporting has already been discussed.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@es.net			Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4  EADA 927D EBB3 987B 3751
From bms at incunabulum.net  Thu Jul 16 19:48:34 2009
From: bms at incunabulum.net (Bruce Simpson)
Date: Thu Jul 16 19:48:40 2009
Subject: FreeBSD 7.2 USB stack info needed
In-Reply-To: <20090713120732.31803.qmail@us1.tomahawkonline.net>
References: <20090713120732.31803.qmail@us1.tomahawkonline.net>
Message-ID: <4A5F840D.4050408@incunabulum.net>

Sagara Wijetunga wrote:
>
> 1. Could I know which exact program print above line on /dev/devctl ?

The kernel...

> 2. I want to print another line with "daN" as the device-name, where N 
> is 0 to 9, with minimum vendor and product ids once the allocated 
> device-name is known for USB Mass Storage devices. Your additional 
> ideas/feedback/help is most welcomed. 

rwatson had a patch for something like this somewhere.

cheers
BMS


From matheus at eternamente.info  Fri Jul 17 04:08:23 2009
From: matheus at eternamente.info (Nenhum_de_Nos)
Date: Fri Jul 17 04:08:31 2009
Subject: gstripe problem
Message-ID: <20090717010813.03477b27.matheus@eternamente.info>

hail,

I have a problem with gstripe on today stable. I created this stripe using a bit more old stable (two weeks tops) and it can't be read on old stable (from 30/12/2008). So I recreated in 8-BETA1 and I could mount and see files. When I tried again on 30/12/2008 stable and todays, on PII machine (i386):

[root@xxx ~]# gstripe status
          Name  Status  Components
stripe/stripe0      UP  ad4s2
                        ad6s2
[root@xxx ~]# gstripe list  
Geom name: stripe0
State: UP
Status: Total=2, Online=2
Type: MANUAL
Stripesize: 4096
ID: 2302026851
Providers:
1. Name: stripe/stripe0
   Mediasize: 1242615693312 (1.1T)
   Sectorsize: 512
   Mode: r0w0e0
Consumers:
1. Name: ad4s2
   Mediasize: 621307846656 (579G)
   Sectorsize: 512
   Mode: r0w0e0
   Number: 0
2. Name: ad6s2
   Mediasize: 621307846656 (579G)
   Sectorsize: 512
   Mode: r0w0e0
   Number: 1
[root@xxx ~]# ls /dev/stripe/
stripe0		stripe0c
[root@xxx ~]# mount /dev/stripe/stripe0 /null 
mount: /dev/stripe/stripe0 : Invalid argument

on 8-BETA1 it works, but can't create stripe on it and use on this stable box though. the stripe already has files ! so anything weird could make me loose my data ...

the 8-BETA1 is amd64 and core 2 quad cpu.

any hints ?

thanks,

matheus

-- 
We will call you cygnus,
The God of balance you shall be

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

http://en.wikipedia.org/wiki/Posting_style
From graham at menhennitt.com.au  Fri Jul 17 06:57:41 2009
From: graham at menhennitt.com.au (Graham Menhennitt)
Date: Fri Jul 17 06:57:47 2009
Subject: ath0: stuck beacon; resetting (bmiss count 4)
Message-ID: <4A6020E1.9010600@menhennitt.com.au>

I'me getting the message "ath0: stuck beacon; resetting (bmiss count 4)"
logged to syslog every so often. I have a Soekris net5501 with a Wistron
CM9  mini-PCI wireless card. I'm running FreeBSD 7.2-stable and "dmesg |
grep ath0" gives:

ath0: <Atheros 5212> mem 0xa0010000-0xa001ffff irq 15 at device 17.0 on pci0
ath0: [ITHREAD]
ath0: WARNING: using obsoleted if_watchdog interface
ath0: Ethernet address: 00:0b:6b:36:99:93
ath0: mac 5.9 phy 4.3 radio 3.6
ath0: ath_chan_set: unable to reset channel 6 (2437 Mhz, flags 0x490 hal
flags 0x150), hal status 12

I've seen Sam Leffler's reply to a previous question about the same log
message at
http://lists.freebsd.org/pipermail/freebsd-current/2009-March/004196.html.

Looking at the source code of if_ath.c in stable:

if (sc->sc_bmisscount > 3)        /* NB: 3 is a guess */
            taskqueue_enqueue(sc->sc_tq, &sc->sc_bstucktask);\

Now, in head the 3 has been made a variable but it doesn't seem to be
able to be tuned in any reasonable way.

I've tied increasing it to 20 and it doesn't seem to have any obvious
bad effects.

So, my questions:
- is 3 really a good guess?
- can it be increased safely?
- what sort of values should I try?
- are there any consequences of increasing it?
- could it be made a sysctl tunable?

Thanks for any help,
  Graham

From ivoras at freebsd.org  Fri Jul 17 10:20:30 2009
From: ivoras at freebsd.org (Ivan Voras)
Date: Fri Jul 17 10:20:38 2009
Subject: gstripe problem
In-Reply-To: <20090717010813.03477b27.matheus@eternamente.info>
References: <20090717010813.03477b27.matheus@eternamente.info>
Message-ID: <h3pj8p$3ce$1@ger.gmane.org>

Nenhum_de_Nos wrote:
> hail,
> 
> I have a problem with gstripe on today stable. I created this stripe using a bit more old stable (two weeks tops) and it can't be read on old stable (from 30/12/2008). So I recreated in 8-BETA1 and I could mount and see files. When I tried again on 30/12/2008 stable and todays, on PII machine (i386):

So your problem is that:

a) you created a gstripe array on a recent STABLE (two weeks ago) and it 
was fine
b) you tried to use it with an old STABLE (30.12.2008.) and it didn't work
c) you tried to use it with today's STABLE and it didn't work
d) it works with 8-BETA1

?

The only thing that comes to my mind is that during your tests you have 
changed the stripe size, making the file system data unusable (and 
unmountable).

> [root@xxx ~]# gstripe status
>           Name  Status  Components
> stripe/stripe0      UP  ad4s2
>                         ad6s2

> mount: /dev/stripe/stripe0 : Invalid argument
> 
> on 8-BETA1 it works, but can't create stripe on it and use on this stable box though. the stripe already has files ! so anything weird could make me loose my data ...

Are you saying you won't use 8-BETA1 because you fear there may be 
problems with it? If so, you shouldn't worry so much - 8-CURRENT is very 
stable.


From matheus at eternamente.info  Fri Jul 17 12:07:56 2009
From: matheus at eternamente.info (Nenhum_de_Nos)
Date: Fri Jul 17 12:08:04 2009
Subject: gstripe problem
In-Reply-To: <h3pj8p$3ce$1@ger.gmane.org>
References: <20090717010813.03477b27.matheus@eternamente.info>
	<h3pj8p$3ce$1@ger.gmane.org>
Message-ID: <0a394f735684111014877d2b39783693.squirrel@cygnus.homeunix.com>


On Fri, July 17, 2009 07:20, Ivan Voras wrote:
> Nenhum_de_Nos wrote:
>> hail,
>>
>> I have a problem with gstripe on today stable. I created this stripe
>> using a bit more old stable (two weeks tops) and it can't be read on old
>> stable (from 30/12/2008). So I recreated in 8-BETA1 and I could mount
>> and see files. When I tried again on 30/12/2008 stable and todays, on
>> PII machine (i386):
>
> So your problem is that:
>
> a) you created a gstripe array on a recent STABLE (two weeks ago) and it
> was fine
> b) you tried to use it with an old STABLE (30.12.2008.) and it didn't work
> c) you tried to use it with today's STABLE and it didn't work
> d) it works with 8-BETA1
> ?

its quite this. the stripe just vanishes when I try to see it in any
stable. and if I create in stable, a reboot makes it go way :(

> The only thing that comes to my mind is that during your tests you have
> changed the stripe size, making the file system data unusable (and
> unmountable).
>
>> [root@xxx ~]# gstripe status
>>           Name  Status  Components
>> stripe/stripe0      UP  ad4s2
>>                         ad6s2
>
>> mount: /dev/stripe/stripe0 : Invalid argument
>>
>> on 8-BETA1 it works, but can't create stripe on it and use on this
>> stable box though. the stripe already has files ! so anything weird
>> could make me loose my data ...
>
> Are you saying you won't use 8-BETA1 because you fear there may be
> problems with it? If so, you shouldn't worry so much - 8-CURRENT is very
> stable.

I know it is. 8-CURRENT is great really (I use it in other places). my
main concern is that this is a server with mail/dns/dhcp/apache/some other
services I forgot and changing to 8-BETA may need to recompile all things,
and need time I don't have right now ...

can I just update and use all software compiled for 7.1-PRERELEASE ?

thanks,

matheus

-- 
We will call you cygnus,
The God of balance you shall be

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

http://en.wikipedia.org/wiki/Posting_style
From pluknet at gmail.com  Fri Jul 17 13:42:39 2009
From: pluknet at gmail.com (pluknet)
Date: Fri Jul 17 13:42:47 2009
Subject: [rfc] MFC 7.x bce(4) to 6.x
Message-ID: <a31046fc0907170642s67281e43mf14532105b8fbedf@mail.gmail.com>

Hi.

Is there a planned MFC of bce(4) changes between 6.4 and 7.2 to RELENG_6?

We need this at work in order to support Broadcom BCM5709 in (post-)6.4.

I could able to backport recent 7.x changes to 6.4.
I'm not sure about MSI and/or TSO4 stability here since there are
changes since 6.x in bce(4).
What I did is checkout RELENG_7 bce sources plus small hackish patch
to compile this on 6.x.

# uname -a
FreeBSD  6.4-RELEASE FreeBSD 6.4-RELEASE #0: Fri Jul 17 21:08:32 MSD
2009     root@:/usr/obj/usr/src/sys/SMP  i386

It seems to work good. I have a network access to the box now.

after kldload if_bce:
bce0: <Broadcom NetXtreme II BCM5709 1000Base-T (C0)> mem 0x92000000-0x93ffffff
irq 28 at device 0.0 on pci11
miibus0: <MII bus> on bce0
ukphy0: <Generic IEEE 802.3u media interface> on miibus0
ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FD
X, auto
bce0: Ethernet address: 00:1a:64:e5:13:ec
bce0: link state changed to DOWN
bce0: ASIC (0x57092003); Rev (C0); Bus (PCIe x2, 5Gbps); B/C (0x04060705); Flags
( MFW MSI )
bce1: <Broadcom NetXtreme II BCM5709 1000Base-T (C0)> mem 0x94000000-0x95ffffff
irq 40 at device 0.1 on pci11
miibus1: <MII bus> on bce1
ukphy1: <Generic IEEE 802.3u media interface> on miibus1
ukphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FD
X, auto
bce1: Ethernet address: 00:1a:64:e5:13:ee
bce1: ASIC (0x
bce1: link state changed to DOWN
57092003); Rev (C0); Bus (PCIe x2, 5Gbps); B/C (0x04060705); Flags( MFW MSI )
bce0: link state changed to UP
bce0: link state changed to DOWN
bce0: link state changed to UP

The patch (against if_bce.c,v 1.34.2.9):

--- /home/pluknet/cvs-7/src/sys/dev/bce/if_bce.c        Wed Jun  3 13:42:55 2009
+++ bce/if_bce.c        Fri Jul 17 15:26:00 2009
@@ -54,6 +54,12 @@ __FBSDID("$FreeBSD: src/sys/dev/bce/if_b
 #include <dev/bce/if_bcereg.h>
 #include <dev/bce/if_bcefw.h>

+/* From sys/mbuf.h */
+#define CSUM_TSO       0x0020          /* will do TSO */
+
+/* From net/if.h */
+#define IFCAP_TSO4     0x00100         /* can do TCP Segmentation Offload */
+
 /****************************************************************************/
 /* BCE Debug Options                                                        */
 /****************************************************************************/
@@ -1059,7 +1065,7 @@ bce_attach(device_t dev)

        /* Hookup IRQ last. */
        rc = bus_setup_intr(dev, sc->bce_res_irq, INTR_TYPE_NET | INTR_MPSAFE,
-               NULL, bce_intr, sc, &sc->bce_intrhand);
+               bce_intr, sc, &sc->bce_intrhand);

        if (rc) {
                BCE_PRINTF("%s(%d): Failed to setup IRQ!\n",
@@ -6391,13 +6397,24 @@ bce_tx_encap(struct bce_softc *sc, struc
        bus_dma_segment_t segs[BCE_MAX_SEGMENTS];
        bus_dmamap_t map;
        struct tx_bd *txbd = NULL;
+#if __FreeBSD_version <= 700022
+       struct m_tag *mtag;
+#endif
        struct mbuf *m0;
+#if __FreeBSD_version > 700022
        struct ether_vlan_header *eh;
        struct ip *ip;
        struct tcphdr *th;
-       u16 prod, chain_prod, etype, mss = 0, vlan_tag = 0, flags = 0;
+#endif
+       u16 prod, chain_prod,
+#if __FreeBSD_version > 700022
+       etype,
+#endif
+       mss = 0, vlan_tag = 0, flags = 0;
        u32 prod_bseq;
+#if __FreeBSD_version > 700022
        int hdr_len = 0, e_hlen = 0, ip_hlen = 0, tcp_hlen = 0, ip_len = 0;
+#endif

 #ifdef BCE_DEBUG
        u16 debug_prod;
@@ -6418,6 +6435,7 @@ bce_tx_encap(struct bce_softc *sc, struc
                        flags |= TX_BD_FLAGS_IP_CKSUM;
                if (m0->m_pkthdr.csum_flags & (CSUM_TCP | CSUM_UDP))
                        flags |= TX_BD_FLAGS_TCP_UDP_CKSUM;
+#if __FreeBSD_version > 700022
                if (m0->m_pkthdr.csum_flags & CSUM_TSO) {
                        /* For TSO the controller needs two pieces of info, */
                        /* the MSS and the IP+TCP options length.           */
@@ -6481,14 +6499,23 @@ bce_tx_encap(struct bce_softc *sc, struc
 bce_tx_encap_skip_tso:
                        DBRUN(sc->requested_tso_frames++);
                }
+#endif
        }

        /* Transfer any VLAN tags to the bd. */
+#if __FreeBSD_version > 700022
        if (m0->m_flags & M_VLANTAG) {
                flags |= TX_BD_FLAGS_VLAN_TAG;
                vlan_tag = m0->m_pkthdr.ether_vtag;
        }

+#else
+        mtag = VLAN_OUTPUT_TAG(sc->bce_ifp, m0);
+        if (mtag != NULL) {
+                flags |= TX_BD_FLAGS_VLAN_TAG;
+                vlan_tag = VLAN_TAG_VALUE(mtag);
+        }
+#endif
        /* Map the mbuf into DMAable memory. */
        prod = sc->tx_prod;
        chain_prod = TX_CHAIN_IDX(prod);

-- 
wbr,
pluknet
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bce.7-down-to-6.patch
Type: application/octet-stream
Size: 2710 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090717/1bb9863a/bce.7-down-to-6.obj
From pluknet at gmail.com  Fri Jul 17 13:46:17 2009
From: pluknet at gmail.com (pluknet)
Date: Fri Jul 17 13:46:24 2009
Subject: [rfc] MFC 7.x bce(4) to 6.x
In-Reply-To: <a31046fc0907170642s67281e43mf14532105b8fbedf@mail.gmail.com>
References: <a31046fc0907170642s67281e43mf14532105b8fbedf@mail.gmail.com>
Message-ID: <a31046fc0907170646r1789f3abva2b5676fa95771d5@mail.gmail.com>

2009/7/17 pluknet <pluknet@gmail.com>:
> Hi.
>
> Is there a planned MFC of bce(4) changes between 6.4 and 7.2 to RELENG_6?
>
> We need this at work in order to support Broadcom BCM5709 in (post-)6.4.
>
> I could able to backport recent 7.x changes to 6.4.
> I'm not sure about MSI and/or TSO4 stability here since there are
> changes since 6.x in bce(4).
> What I did is checkout RELENG_7 bce sources plus small hackish patch
> to compile this on 6.x.
>
> # uname -a
> FreeBSD ?6.4-RELEASE FreeBSD 6.4-RELEASE #0: Fri Jul 17 21:08:32 MSD
> 2009 ? ? root@:/usr/obj/usr/src/sys/SMP ?i386
>
> It seems to work good. I have a network access to the box now.
>
> after kldload if_bce:
> bce0: <Broadcom NetXtreme II BCM5709 1000Base-T (C0)> mem 0x92000000-0x93ffffff
> irq 28 at device 0.0 on pci11
> miibus0: <MII bus> on bce0
> ukphy0: <Generic IEEE 802.3u media interface> on miibus0
> ukphy0: ?10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FD
> X, auto
> bce0: Ethernet address: 00:1a:64:e5:13:ec
> bce0: link state changed to DOWN
> bce0: ASIC (0x57092003); Rev (C0); Bus (PCIe x2, 5Gbps); B/C (0x04060705); Flags
> ( MFW MSI )
> bce1: <Broadcom NetXtreme II BCM5709 1000Base-T (C0)> mem 0x94000000-0x95ffffff
> irq 40 at device 0.1 on pci11
> miibus1: <MII bus> on bce1
> ukphy1: <Generic IEEE 802.3u media interface> on miibus1
> ukphy1: ?10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FD
> X, auto
> bce1: Ethernet address: 00:1a:64:e5:13:ee
> bce1: ASIC (0x
> bce1: link state changed to DOWN
> 57092003); Rev (C0); Bus (PCIe x2, 5Gbps); B/C (0x04060705); Flags( MFW MSI )
> bce0: link state changed to UP
> bce0: link state changed to DOWN
> bce0: link state changed to UP

Ah, yes. Forgot to show dmesg from 7.2 for comparison:
bce0: <Broadcom NetXtreme II BCM5709 1000Base-T (C0)> mem
0x92000000-0x93ffffff irq 28 at device 0.0 on pci11
bce0: Reserved 0x2000000 bytes for rid 0x10 type 3 at 0x92000000
bce0: attempting to allocate 1 MSI vectors (16 supported)
bce0: using IRQ 256 for MSI
miibus0: <MII bus> on bce0
bce0: bpf attached
bce0: Ethernet address: 00:1a:64:e5:13:ec
bce0: [MPSAFE]
bce0: [ITHREAD]
bce0: ASIC (0x57092003); Rev (C0); Bus (PCIe x2, 5Gbps); B/C
(0x04060705); Flags( MFW MSI )
bce1: <Broadcom NetXtreme II BCM5709 1000Base-T (C0)> mem
0x94000000-0x95ffffff irq 40 at device 0.1 on pci11
bce1: Reserved 0x2000000 bytes for rid 0x10 type 3 at 0x94000000
bce1: attempting to allocate 1 MSI vectors (16 supported)
bce1: using IRQ 257 for MSI
miibus1: <MII bus> on bce1
bce1: bpf attached
bce1: Ethernet address: 00:1a:64:e5:13:ee
bce1: [MPSAFE]
bce1: [ITHREAD]
bce1: ASIC (0x57092003); Rev (C0); Bus (PCIe x2, 5Gbps); B/C
(0x04060705); Flags( MFW MSI )
bce0: link state changed to UP


>
> The patch (against if_bce.c,v 1.34.2.9):
>
> --- /home/pluknet/cvs-7/src/sys/dev/bce/if_bce.c ? ? ? ?Wed Jun ?3 13:42:55 2009
> +++ bce/if_bce.c ? ? ? ?Fri Jul 17 15:26:00 2009
> @@ -54,6 +54,12 @@ __FBSDID("$FreeBSD: src/sys/dev/bce/if_b
> ?#include <dev/bce/if_bcereg.h>
> ?#include <dev/bce/if_bcefw.h>
>
> +/* From sys/mbuf.h */
> +#define CSUM_TSO ? ? ? 0x0020 ? ? ? ? ?/* will do TSO */
> +
> +/* From net/if.h */
> +#define IFCAP_TSO4 ? ? 0x00100 ? ? ? ? /* can do TCP Segmentation Offload */
> +
> ?/****************************************************************************/
> ?/* BCE Debug Options ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?*/
> ?/****************************************************************************/
> @@ -1059,7 +1065,7 @@ bce_attach(device_t dev)
>
> ? ? ? ?/* Hookup IRQ last. */
> ? ? ? ?rc = bus_setup_intr(dev, sc->bce_res_irq, INTR_TYPE_NET | INTR_MPSAFE,
> - ? ? ? ? ? ? ? NULL, bce_intr, sc, &sc->bce_intrhand);
> + ? ? ? ? ? ? ? bce_intr, sc, &sc->bce_intrhand);
>
> ? ? ? ?if (rc) {
> ? ? ? ? ? ? ? ?BCE_PRINTF("%s(%d): Failed to setup IRQ!\n",
> @@ -6391,13 +6397,24 @@ bce_tx_encap(struct bce_softc *sc, struc
> ? ? ? ?bus_dma_segment_t segs[BCE_MAX_SEGMENTS];
> ? ? ? ?bus_dmamap_t map;
> ? ? ? ?struct tx_bd *txbd = NULL;
> +#if __FreeBSD_version <= 700022
> + ? ? ? struct m_tag *mtag;
> +#endif
> ? ? ? ?struct mbuf *m0;
> +#if __FreeBSD_version > 700022
> ? ? ? ?struct ether_vlan_header *eh;
> ? ? ? ?struct ip *ip;
> ? ? ? ?struct tcphdr *th;
> - ? ? ? u16 prod, chain_prod, etype, mss = 0, vlan_tag = 0, flags = 0;
> +#endif
> + ? ? ? u16 prod, chain_prod,
> +#if __FreeBSD_version > 700022
> + ? ? ? etype,
> +#endif
> + ? ? ? mss = 0, vlan_tag = 0, flags = 0;
> ? ? ? ?u32 prod_bseq;
> +#if __FreeBSD_version > 700022
> ? ? ? ?int hdr_len = 0, e_hlen = 0, ip_hlen = 0, tcp_hlen = 0, ip_len = 0;
> +#endif
>
> ?#ifdef BCE_DEBUG
> ? ? ? ?u16 debug_prod;
> @@ -6418,6 +6435,7 @@ bce_tx_encap(struct bce_softc *sc, struc
> ? ? ? ? ? ? ? ? ? ? ? ?flags |= TX_BD_FLAGS_IP_CKSUM;
> ? ? ? ? ? ? ? ?if (m0->m_pkthdr.csum_flags & (CSUM_TCP | CSUM_UDP))
> ? ? ? ? ? ? ? ? ? ? ? ?flags |= TX_BD_FLAGS_TCP_UDP_CKSUM;
> +#if __FreeBSD_version > 700022
> ? ? ? ? ? ? ? ?if (m0->m_pkthdr.csum_flags & CSUM_TSO) {
> ? ? ? ? ? ? ? ? ? ? ? ?/* For TSO the controller needs two pieces of info, */
> ? ? ? ? ? ? ? ? ? ? ? ?/* the MSS and the IP+TCP options length. ? ? ? ? ? */
> @@ -6481,14 +6499,23 @@ bce_tx_encap(struct bce_softc *sc, struc
> ?bce_tx_encap_skip_tso:
> ? ? ? ? ? ? ? ? ? ? ? ?DBRUN(sc->requested_tso_frames++);
> ? ? ? ? ? ? ? ?}
> +#endif
> ? ? ? ?}
>
> ? ? ? ?/* Transfer any VLAN tags to the bd. */
> +#if __FreeBSD_version > 700022
> ? ? ? ?if (m0->m_flags & M_VLANTAG) {
> ? ? ? ? ? ? ? ?flags |= TX_BD_FLAGS_VLAN_TAG;
> ? ? ? ? ? ? ? ?vlan_tag = m0->m_pkthdr.ether_vtag;
> ? ? ? ?}
>
> +#else
> + ? ? ? ?mtag = VLAN_OUTPUT_TAG(sc->bce_ifp, m0);
> + ? ? ? ?if (mtag != NULL) {
> + ? ? ? ? ? ? ? ?flags |= TX_BD_FLAGS_VLAN_TAG;
> + ? ? ? ? ? ? ? ?vlan_tag = VLAN_TAG_VALUE(mtag);
> + ? ? ? ?}
> +#endif
> ? ? ? ?/* Map the mbuf into DMAable memory. */
> ? ? ? ?prod = sc->tx_prod;
> ? ? ? ?chain_prod = TX_CHAIN_IDX(prod);
>
> --
> wbr,
> pluknet
>



-- 
wbr,
pluknet
From pmc at citylink.dinoex.sub.org  Fri Jul 17 20:09:08 2009
From: pmc at citylink.dinoex.sub.org (Peter Much)
Date: Fri Jul 17 20:09:16 2009
Subject: Can an app crash from a single TCP packet lost in transmission?
Message-ID: <KMxxC7.32y@citylink.dinoex.sub.org>


The first thing I noticed was that my nameserver had gone. 
I searched for the reason and found:

>Jul 15 04:04:52 <kern.crit> edge kernel: swap_pager_getswapspace(3): failed
< ... hundreds more of these ... >
>Jul 15 04:05:07 <kern.err> edge kernel: pid 47113 (named), uid 53, was 
                killed: out of swap space

That didn't make sense - the machine has enough swapspace.
But since this did repeat every other night, I started logging
ps output minutely.
And so I found a postgres database backup going weird:

03:23   70 78433 78432   0  96  0  8220  4196 -      R     ??    0:22.84 pg_dump -b 
< ... >
03:49   70 78433 78432   0  96  0  8220  4024 -      R     ??   17:06.61 pg_dump -b 
03:50   70 78433 78432   0  96  0  8220  4024 -      R     ??   17:46.15 pg_dump -b 
03:51   70 78433 78432   0  96  0  8220  4024 -      R     ??   18:26.69 pg_dump -b 
03:52   70 78433 78432   0  47  0 139292 57888 select S     ??   18:37.65 pg_dump -b 
03:53   70 78433 78432   0  48  0 139292 57828 select S     ??   18:40.36 pg_dump -b 
03:54   70 78433 78432   0 -20  0 401436 69092 swread DL    ??   18:42.49 pg_dump -b 
03:55   70 78433 78432   0 -20  0 401436 63232 swread DL    ??   18:43.99 pg_dump -b 

That process starts with 8MB memory, and runs so for half an hour,
then suddenly between 03:51 and 03:52 memory usage explodes.
And in that night it did not run out of swap space - instead it gave an
error message:

>pg_dump: Error message from server: lost synchronization with server: 
>         got message type "0", length 154143043
>pg_dump: The command was: COPY public.file (fileid, fileindex, jobid, 
>         pathid, filenameid, markid, lstat, md5) TO stdout;

But that database backup is at that time quite in the middle of 
dumping a db table containing lots of small records - there is no 
reason why a 154 MB "message" should be transferred between server 
and client while copying records of ~60 Bytes each.

One other thing did happen between 03:51 and 03:52 - the DSL 
internet connection did disconnect/reconnect and obtained a new 
IP adress. Afterwards, a script does flush and reload an ipfw table()
with the new local adresses - and during this process one(!) packet
of the database session was dropped.

I could verify that relation: every night when there were memory
problems, few packets from the database backup were lost during the
firewall reconfigure - in nights when no packets were lost, there were
no memory problems.

I will now change the firewall handling to get rid of that packet loss, 
but also, I need some refresh on how TCP works:

I thought TCP would not be disturbed by a lost packet, but would 
automatically resend that packet until ACK received; and I thought
this would happen below the application, so practically the application
CANNOT go weird from a lost packet...

Is there any reason why this would not be true on a localhost connection?


rgds, 
PMc
From cswiger at mac.com  Fri Jul 17 20:49:11 2009
From: cswiger at mac.com (Chuck Swiger)
Date: Fri Jul 17 20:49:18 2009
Subject: Can an app crash from a single TCP packet lost in transmission?
In-Reply-To: <KMxxC7.32y@citylink.dinoex.sub.org>
References: <KMxxC7.32y@citylink.dinoex.sub.org>
Message-ID: <7090AD67-2082-4AFA-B130-C20A7DC970FA@mac.com>

On Jul 17, 2009, at 12:12 PM, Peter Much wrote:
[ ... ]
> One other thing did happen between 03:51 and 03:52 - the DSL
> internet connection did disconnect/reconnect and obtained a new
> IP adress. Afterwards, a script does flush and reload an ipfw table()
> with the new local adresses - and during this process one(!) packet
> of the database session was dropped.

Well, there you go: having your IP change is certainly going to break  
existing network connections; I don't believe there is anything which  
is going to move the existing connection state in a NAT translation  
layer or whatever over to the new IP.  Presumably you can obtain a  
static IP and avoid such issues.

-- 
-Chuck

From pmc at citylink.dinoex.sub.org  Fri Jul 17 23:13:35 2009
From: pmc at citylink.dinoex.sub.org (Peter Much)
Date: Fri Jul 17 23:13:42 2009
Subject: Can an app crash from a single TCP packet lost in transmission?
References: <KMxxC7.32y@citylink.dinoex.sub.org>
	<7090AD67-2082-4AFA-B130-C20A7DC970FA@mac.com>
Message-ID: <KMy52x.8Kp@citylink.dinoex.sub.org>

<cswiger@mac.com> aka Chuck Swiger  schrieb
mit Datum Fri, 17 Jul 2009 13:49:10 -0700 in m2n.fbsd.stable:

|On Jul 17, 2009, at 12:12 PM, Peter Much wrote:
|[ ... ]
|> One other thing did happen between 03:51 and 03:52 - the DSL
|> internet connection did disconnect/reconnect and obtained a new
|> IP adress. Afterwards, a script does flush and reload an ipfw table()
|> with the new local adresses - and during this process one(!) packet
|> of the database session was dropped.
|
|Well, there you go: having your IP change is certainly going to break  
|existing network connections; 

Uh, is that so? 
Maybe I wasnt clear enough: the failing database connection is a 
LOCALHOST-LOCALHOST connection - and it uses the (fixed) IP of one 
of the LAN interfaces, not the dynamic internet IP on the tun/PPP 
interface.

Changing the IP on one interface while using another interface is,
to all my knowledge, normal business.

And even IF there were problem with that, then I would expect the 
connection to timeout and fail, I would NOT expect a memory leak
to appear and drive the system out of swap within seconds.

!I don't believe there is anything which  
|is going to move the existing connection state in a NAT translation  
|layer or whatever over to the new IP. 

Nay, that doesnt work.

|Presumably you can obtain a  
|static IP and avoid such issues.

I have a static internet IP on the machine, also, for HTTPS. I have 
lots of interfaces there.

And I did run some tests in the meantime. The problem is in the 
PostgresQL library; it doesnt depend on a changed IP; - I only need
to steal one packet out of the transmission, then the database client
will grow to VSZ=1500GB and bigger. That's perfect reproduceable.

The postgresQL is 8.2, rather old by now - but I really wonder that
noone else did get into this during all the time.

rgds,
PMc
From matheus at eternamente.info  Sat Jul 18 00:01:22 2009
From: matheus at eternamente.info (Nenhum_de_Nos)
Date: Sat Jul 18 00:01:28 2009
Subject: gstripe problem
In-Reply-To: <0a394f735684111014877d2b39783693.squirrel@cygnus.homeunix.com>
References: <20090717010813.03477b27.matheus@eternamente.info>
	<h3pj8p$3ce$1@ger.gmane.org>
	<0a394f735684111014877d2b39783693.squirrel@cygnus.homeunix.com>
Message-ID: <2fd30e75fbd3e231117ab9f2459f896b.squirrel@10.1.1.10>


On Fri, July 17, 2009 09:07, Nenhum_de_Nos wrote:
>
> On Fri, July 17, 2009 07:20, Ivan Voras wrote:
>> Nenhum_de_Nos wrote:
>>> hail,
>>>
>>> I have a problem with gstripe on today stable. I created this stripe
>>> using a bit more old stable (two weeks tops) and it can't be read on
>>> old
>>> stable (from 30/12/2008). So I recreated in 8-BETA1 and I could mount
>>> and see files. When I tried again on 30/12/2008 stable and todays, on
>>> PII machine (i386):
>>
>> So your problem is that:
>>
>> a) you created a gstripe array on a recent STABLE (two weeks ago) and it
>> was fine
>> b) you tried to use it with an old STABLE (30.12.2008.) and it didn't
>> work
>> c) you tried to use it with today's STABLE and it didn't work
>> d) it works with 8-BETA1
>> ?
>
> its quite this. the stripe just vanishes when I try to see it in any
> stable. and if I create in stable, a reboot makes it go way :(
>
>> The only thing that comes to my mind is that during your tests you have
>> changed the stripe size, making the file system data unusable (and
>> unmountable).
>>
>>> [root@xxx ~]# gstripe status
>>>           Name  Status  Components
>>> stripe/stripe0      UP  ad4s2
>>>                         ad6s2
>>
>>> mount: /dev/stripe/stripe0 : Invalid argument
>>>
>>> on 8-BETA1 it works, but can't create stripe on it and use on this
>>> stable box though. the stripe already has files ! so anything weird
>>> could make me loose my data ...
>>
>> Are you saying you won't use 8-BETA1 because you fear there may be
>> problems with it? If so, you shouldn't worry so much - 8-CURRENT is very
>> stable.
>
> I know it is. 8-CURRENT is great really (I use it in other places). my
> main concern is that this is a server with mail/dns/dhcp/apache/some other
> services I forgot and changing to 8-BETA may need to recompile all things,
> and need time I don't have right now ...
>
> can I just update and use all software compiled for 7.1-PRERELEASE ?
>
> thanks,
>
> matheus

thins here just got weird. I did updated to 8-BETA2. same problem though.
so I just thought it was problem when I create a stripe in amd64 machine
and try to use it on i386.

I then put the drives in the amd64 machine, and it did worked fine, after
another gstripe create command. so I rebooted the amd64 machine to see if
after reboot the stripe would be there. guess what ... nothing there ...

I used gmirror and gstripe for about an year, no problem. couple of months
ago I had a problem and had to change the pc (dead one). so all changed,
using sil3114 sata pci card now and PII 300 MHz. now the disks behave like
this.

if anyone has any leads, I'm moving data from the disks now ... can test
though.

thanks,

matheus

-- 
We will call you cygnus,
The God of balance you shall be

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

http://en.wikipedia.org/wiki/Posting_style
From kensmith at cse.Buffalo.EDU  Sat Jul 18 03:29:36 2009
From: kensmith at cse.Buffalo.EDU (Ken Smith)
Date: Sat Jul 18 03:29:44 2009
Subject: 8.0-BETA2 Available
Message-ID: <1247887759.14210.18.camel@neo.cse.buffalo.edu>


The second of the BETA builds for the FreeBSD-8.0 release cycle is now
available.  There are still a few things being finished up so a couple
more moderately large commits are coming but we seem to be making good
progress.  The target date for the last of the things still being worked
on is BETA3.  In the meantime we appreciate the feedback we have
received from people who have started testing and some of those problems
have been fixed as well.

As was the case with BETA1, BETA2 is still a little bit "rough around
the edges" and we still have various debugging tools enabled that cause
the system to perform worse than it will when those debugging tools get
disabled.  We don't know of any issues that will "eat your data" or
anything like that so in that regard it's safe but we don't recommend it
for production use quite yet.  If you notice problems you can report
them through the normal Gnats PR system or on the freebsd-current
mailing list.  Sorry for not specifying that in the BETA1 announcement.
With the X.0 releases I make the announcements of how the release is
progressing on both freebsd-current and freebsd-stable because what's
being released is "about to become a stable branch" so some people who
only read freebsd-stable might be interested.  But when it comes to
watching for discussions about the release the developer community tends
to pay more attention to the freebsd-current mailing list.

ISO images for all supported architectures are available on the FTP
sites, and a "memory stick" image is available for amd64/i386
architectures.  For amd64/i386 architectures the DVD and memstick images
include the documentation packages this time but no other packages yet.
None of the other images included packages.  The memstick image should
now work in "fixit" mode (livefs).

If you are using csup/cvsup methods to update an older system the branch
tag to use is still head (".").

The freebsd-update(8) utility supports binary upgrades of i386 and amd64
systems running earlier FreeBSD releases. Systems running 7.0-RELEASE,
7.1-RELEASE, 7.2-RELEASE, or 8.0-BETA2 can upgrade as follows:
  
# freebsd-update upgrade -r 8.0-BETA2
  
During this process, FreeBSD Update may ask the user to help by merging some
configuration files or by confirming that the automatically performed merging
was done correctly.
  
# freebsd-update install
  
The system must be rebooted with the newly installed kernel before continuing.
  
# shutdown -r now
   
After rebooting, freebsd-update needs to be run again to install the new
userland components:

# freebsd-update install
   
At this point, users of systems being upgraded from FreeBSD 7.x will be
prompted by freebsd-update to rebuild all third-party applications (e.g.,
ports installed from the ports tree) due to updates in system libraries.  See
  http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html
for mode details.  After updating installed third-party applications (and
again, only if freebsd-update printed a message indicating that this was
necessary), run freebsd-update again so that it can delete the old (no longer
used) system libraries:
# freebsd-update install
   
Finally, reboot into 8.0-BETA2:
   
# shutdown -r now

MD5/SHA256 checksums for the image files:

MD5 (8.0-BETA2-amd64-bootonly.iso) = 7e389124bfa5c216324b12660664a41d
MD5 (8.0-BETA2-amd64-disc1.iso) = c5a8391ec3eda90e310590c6e9352e43
MD5 (8.0-BETA2-amd64-dvd1.iso) = c148d1eac8fbafce3dc26a5186a3c7c6
MD5 (8.0-BETA2-amd64-livefs.iso) = 24e2da8a58e8df86a1a72d3fd2aa95a1
MD5 (8.0-BETA2-amd64-memstick.img) = 06d466ba9cf5c3a22aee92586fa96d7f

MD5 (8.0-BETA2-i386-bootonly.iso) = 4279dec2239df09ec7b93e52f96e55bb
MD5 (8.0-BETA2-i386-disc1.iso) = 16173fee72aa8cdd7d39d8ce3238276c
MD5 (8.0-BETA2-i386-dvd1.iso) = 3a04d48154c702021e9abac271e9a700
MD5 (8.0-BETA2-i386-livefs.iso) = 6ca1813b3ac7cc9abe8f44c9875a50bf
MD5 (8.0-BETA2-i386-memstick.img) = 5db506264c4b2d60b902d63ebc49a317

MD5 (8.0-BETA2-ia64-bootonly.iso) = baac960edebc8a10131db8debe961168
MD5 (8.0-BETA2-ia64-disc1.iso) = 77ecfb115e4dbc5eaaad6d42e8e93bae
MD5 (8.0-BETA2-ia64-disc2.iso) = 77fe3b112b74858abc9586e5ac0c8355
MD5 (8.0-BETA2-ia64-disc3.iso) = ddc874a6e67d290a6af96221a025e90a
MD5 (8.0-BETA2-ia64-dvd1.iso) = ac85730dfabea642cf91471954f541dd
MD5 (8.0-BETA2-ia64-livefs.iso) = 5806ddd76a778bcde03e3c92f0005173

MD5 (8.0-BETA2-pc98-bootonly.iso) = b0c5c41251242483c2048b77dadc7a76
MD5 (8.0-BETA2-pc98-disc1.iso) = 49a0974e0abd5e63618ea99634313bbe
MD5 (8.0-BETA2-pc98-livefs.iso) = dddfdb2e0f6ffd0497f9ce9a00812c24

MD5 (8.0-BETA2-powerpc-bootonly.iso) = 2bd42f619809aedbd3ac6a5b1beeec6d
MD5 (8.0-BETA2-powerpc-disc1.iso) = 329c5d3082fe3479545018092d3a0850
MD5 (8.0-BETA2-powerpc-disc2.iso) = ba7d5337e9c1cc9c356372a7d7f4015d
MD5 (8.0-BETA2-powerpc-disc3.iso) = 46567950c6e6d969ec584637641e042c

MD5 (8.0-BETA2-sparc64-bootonly.iso) = 47bba49d0f4ea3c58163db9146c46d6c
MD5 (8.0-BETA2-sparc64-disc1.iso) = 93af6d6d1164276d83c3e8c67a904422
MD5 (8.0-BETA2-sparc64-dvd1.iso) = 269ebf61580485eb8fc3abb063b5a309

SHA256 (8.0-BETA2-amd64-bootonly.iso) = c11389094ee73389eb3e3ad22e165f158cce0003431a88eb27ae253fd76b70a8
SHA256 (8.0-BETA2-amd64-disc1.iso) = 49121108535986690eebc7c894a56bdd1e4b5afc8ed1470afb0ebc79debb2c1e
SHA256 (8.0-BETA2-amd64-dvd1.iso) = d3f36481fd022bad67cc020eeb19f261330c279592a0062c43804fdc32a0c08d
SHA256 (8.0-BETA2-amd64-livefs.iso) = 35d02c1b6bdcc54721f955f3beb68c6e67b610554a2e28c28391041cdab75ddf
SHA256 (8.0-BETA2-amd64-memstick.img) = 66eb336e4de03cc68f1929db233d3edb37fc05b814cde68fe8f618340b91cb66

SHA256 (8.0-BETA2-i386-bootonly.iso) = 904b8aa5380ea81604ea81c9c88b3bb3ade744a45cececa512fc78b07c1bbacd
SHA256 (8.0-BETA2-i386-disc1.iso) = 5699c6e4f8a7084dc6d6fe835c1c40cc7b01614091b057df07d72537e8e33ef4
SHA256 (8.0-BETA2-i386-dvd1.iso) = f5cc663850f6e20ece9e7e2c6b9503b8f9599acfdd20e5a19ffad4541d33fc7f
SHA256 (8.0-BETA2-i386-livefs.iso) = f2a50f00ba9f30c564fd7be320c7bc1111af2b192a47e036cd97fa72092435e3
SHA256 (8.0-BETA2-i386-memstick.img) = 6d66fee850102d966b00123590f139fb38e6d33d818ff8c6ce58c4ae3853e209

SHA256 (8.0-BETA2-ia64-bootonly.iso) = 69da5d8fb3d17bade7b596f5bd81bacfb1c178bf184be462661786e99ac3f80d
SHA256 (8.0-BETA2-ia64-disc1.iso) = c59b03585d364ad0b305eb3d71c168c0d1e0b100270802ed22efdc80de59f792
SHA256 (8.0-BETA2-ia64-disc2.iso) = 7f398777025c970f265446d18bb7f571a2078e147843bd1345827164a040b9f3
SHA256 (8.0-BETA2-ia64-disc3.iso) = cf4a0bb280892cc09af10f138aa3a8df7045380e63946427d582c8217ed3231c
SHA256 (8.0-BETA2-ia64-dvd1.iso) = e1379d207a0659ab4397c1c84e7193e1efe0d04db96b21c712b1bdc9e86079ad
SHA256 (8.0-BETA2-ia64-livefs.iso) = 3881e3eaba4988c23a3cf19d04c2e055b861288d938ad8c4352dacfd6a97c35a

SHA256 (8.0-BETA2-pc98-bootonly.iso) = fc2f234ed68e0a3c1a254771485b012bf124009cb1a928e67204a2f1aad63519
SHA256 (8.0-BETA2-pc98-disc1.iso) = 7b5450fc0ae04ec80788a91b8d6caf449c22ed2e373ebf89263d2affebe74cf8
SHA256 (8.0-BETA2-pc98-livefs.iso) = cf9c823eb58fee48421c16900c270b97fefb61a1f90501791e88b74102862763

SHA256 (8.0-BETA2-powerpc-bootonly.iso) = 99d50bc3c35b36b41fe0871d3505d702c75a8025178dbc33603b77c9886d23af
SHA256 (8.0-BETA2-powerpc-disc1.iso) = 4afdc4e8be4ea178ce791b5c3e1881538cc118b336c5337ce15d811e245a926d
SHA256 (8.0-BETA2-powerpc-disc2.iso) = a7c21ffb213e0b73e24e5d9a317599445ac8c69cb37efa554768692622b176cc
SHA256 (8.0-BETA2-powerpc-disc3.iso) = 6213f6a5e19a4146d6e20bffb36d6e1a7d3aa192db83f14f6ec599fa38472a6f

SHA256 (8.0-BETA2-sparc64-bootonly.iso) = 998fcc77ec2675e7eb7d826ae87897bead56189cc79ede57b214d3357d56499d
SHA256 (8.0-BETA2-sparc64-disc1.iso) = 22d61fc13dd544af390de56940e1a4c041abe18249cdc110ae02613d1f5d761a
SHA256 (8.0-BETA2-sparc64-dvd1.iso) = 2478e8c3508e8b8f8b9f0ed6a9c67c0469375cb2ba224114583fe14da6fb237e

-- 
                                                Ken Smith
- From there to here, from here to      |       kensmith@cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090718/51b3d298/attachment.pgp
From ari at ish.com.au  Sat Jul 18 04:13:35 2009
From: ari at ish.com.au (Aristedes Maniatis)
Date: Sat Jul 18 04:13:42 2009
Subject: 8.0-BETA2 Available
In-Reply-To: <1247887759.14210.18.camel@neo.cse.buffalo.edu>
References: <1247887759.14210.18.camel@neo.cse.buffalo.edu>
Message-ID: <4A614957.4060703@ish.com.au>

On 18/07/09 1:29 PM, Ken Smith wrote:
> # freebsd-update upgrade -r 8.0-BETA2
>
> During this process, FreeBSD Update may ask the user to help by merging some
> configuration files or by confirming that the automatically performed merging
> was done correctly.
>
> # freebsd-update install
>
> The system must be rebooted with the newly installed kernel before continuing.
>
> # shutdown -r now


FreeBSD 7 users who have /usr /var, etc on ZFS should not follow these 
instructions exactly. Rebooting into a new kernel with the old userland 
ZFS tools will result in the system not being able to mount the ZFS 
filesystems and therefore not being able to reboot. [1]

Ari Maniatis


[1] See my more detailed comment at the bottom here: 
http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html




-------------------------->
ish
http://www.ish.com.au
Level 1, 30 Wilson Street Newtown 2042 Australia
phone +61 2 9550 5001   fax +61 2 9550 4001
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
From bh at izb.knu.ac.kr  Sat Jul 18 07:30:41 2009
From: bh at izb.knu.ac.kr (Byung-Hee HWANG)
Date: Sat Jul 18 07:30:51 2009
Subject: 8.0-BETA2 Available
In-Reply-To: <1247887759.14210.18.camel@neo.cse.buffalo.edu> (Ken Smith's
	message of "Fri, 17 Jul 2009 23:29:19 -0400")
References: <1247887759.14210.18.camel@neo.cse.buffalo.edu>
Message-ID: <86zlb2o3cc.fsf@betla.izb.knu.ac.kr>

Ken Smith <kensmith@cse.Buffalo.EDU> writes:

> The second of the BETA builds for the FreeBSD-8.0 release cycle is now
> available.  There are still a few things being finished up so a couple
> more moderately large commits are coming but we seem to be making good
> progress.  The target date for the last of the things still being worked
> on is BETA3.  In the meantime we appreciate the feedback we have
> received from people who have started testing and some of those problems
> have been fixed as well.
[...]
For some reason, i'll start to test with BETA3 instead of BETA2. Until
that time, good job, Ken!

Sincerely,

-- 
Byung-Hee HWANG, KNU
? WWW: http://izb.knu.ac.kr/~bh/

"Don't tell me a big movie star like Johnny Fontane has to ask your father for
a favor?"
		-- Kay Adams, "Chapter 1", page 42
From njm at njm.me.uk  Sat Jul 18 08:06:58 2009
From: njm at njm.me.uk (N.J. Mann)
Date: Sat Jul 18 08:07:06 2009
Subject: 8.0-BETA2 Available
In-Reply-To: <1247887759.14210.18.camel@neo.cse.buffalo.edu>
References: <1247887759.14210.18.camel@neo.cse.buffalo.edu>
Message-ID: <20090718074013.GA42796@titania.njm.me.uk>

In message <1247887759.14210.18.camel@neo.cse.buffalo.edu>,
	Ken Smith (kensmith@cse.Buffalo.EDU) wrote:
> 
> The second of the BETA builds for the FreeBSD-8.0 release cycle is now
> available.  There are still a few things being finished up so a couple
> more moderately large commits are coming but we seem to be making good
> progress.  The target date for the last of the things still being worked
> on is BETA3.  In the meantime we appreciate the feedback we have
> received from people who have started testing and some of those problems
> have been fixed as well.
> 
> As was the case with BETA1, BETA2 is still a little bit "rough around
> the edges" and we still have various debugging tools enabled that cause
> the system to perform worse than it will when those debugging tools get
> disabled.  We don't know of any issues that will "eat your data" or
> anything like that so in that regard it's safe but we don't recommend it
> for production use quite yet.  If you notice problems you can report
> them through the normal Gnats PR system or on the freebsd-current
> mailing list.  Sorry for not specifying that in the BETA1 announcement.
> With the X.0 releases I make the announcements of how the release is
> progressing on both freebsd-current and freebsd-stable because what's
> being released is "about to become a stable branch" so some people who
> only read freebsd-stable might be interested.  But when it comes to
> watching for discussions about the release the developer community tends
> to pay more attention to the freebsd-current mailing list.
> 
> ISO images for all supported architectures are available on the FTP
> sites, and a "memory stick" image is available for amd64/i386
> architectures.  For amd64/i386 architectures the DVD and memstick images
> include the documentation packages this time but no other packages yet.
> None of the other images included packages.  The memstick image should
> now work in "fixit" mode (livefs).
> 
> If you are using csup/cvsup methods to update an older system the branch
> tag to use is still head (".").
> 
> The freebsd-update(8) utility supports binary upgrades of i386 and amd64
> systems running earlier FreeBSD releases. Systems running 7.0-RELEASE,
> 7.1-RELEASE, 7.2-RELEASE, or 8.0-BETA2 can upgrade as follows:

                               ^^^^^^^^^
I think in this one instance you actually mean 8.0-BETA1.


Cheers,
       Nick.
-- 

From info at martenvijn.nl  Sat Jul 18 16:22:33 2009
From: info at martenvijn.nl (Marten Vijn)
Date: Sat Jul 18 16:22:50 2009
Subject: make distribution Re: 8.0-BETA2 Available
In-Reply-To: <1247887759.14210.18.camel@neo.cse.buffalo.edu>
References: <1247887759.14210.18.camel@neo.cse.buffalo.edu>
Message-ID: <1247933100.14935.20.camel@mvn-desktop>

cd /usr/src
make distribution gives an error

data below,

kidn regards,
Marten

make installworld DESTDIR=/usr/tftpboot1/
<snip><ok>
make installkernel DESTDIR=/usr/tftpboot1/
<snip>ok>


# make distribution DESTDIR=/usr/tftpboot1/
cd /usr/src/etc; MAKEOBJDIRPREFIX=/usr/obj  MACHINE_ARCH=i386
MACHINE=i386  CPUTYPE=
GROFF_BIN_PATH=/usr/obj/usr/src/tmp/legacy/usr/bin
GROFF_FONT_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/groff_font
GROFF_TMAC_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/tmac
PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin make distribution
cd /usr/src/etc;  install -o root -g wheel -m 644  auth.conf  crontab
devd.conf devfs.conf  ddb.conf dhclient.conf disktab fbtab  ftpusers
gettytab group  hosts hosts.allow hosts.equiv  inetd.conf libalias.conf
login.access login.conf mac.conf motd  netconfig network.subr networks
newsyslog.conf nsswitch.conf  phones profile protocols  rc
rc.bsdextended rc.firewall rc.firewall6 rc.initdiskless  rc.sendmail
rc.shutdown  rc.subr remote rpc services shells  sysctl.conf syslog.conf
etc.i386/ttys amd.map apmd.conf snmpd.config
freebsd-update.conf /usr/src/etc/../usr.bin/locate/locate/locate.rc
hosts.lpd
printcap /usr/src/etc/../usr.bin/mail/misc/mail.rc /usr/src/etc/../gnu/usr.bin/man/manpath/manpath.config ntp.conf nscd.conf portsnap.conf pf.os csh.cshrc csh.login csh.logout regdomain.xml /usr/tftpboot1//etc;  cap_mkdb -l /usr/tftpboot1//etc/login.conf;  install -o root -g wheel -m 755  netstart pccard_ether rc.suspend rc.resume /usr/tftpboot1//etc;  install -o root -g wheel -m 600  master.passwd nsmb.conf opieaccess /usr/tftpboot1//etc;
pwd_mkdb -L -i -p
-d /usr/tftpboot1//etc  /usr/tftpboot1//etc/master.passwd
cd /usr/src/etc/bluetooth; make install
install -o root  -g wheel -m 600
hcsecd.conf  /usr/tftpboot1//etc/bluetooth/hcsecd.conf
install -o root  -g wheel -m 644
hosts  /usr/tftpboot1//etc/bluetooth/hosts
install -o root -g wheel  -m 444 protocols /usr/tftpboot1//etc/bluetooth
cd /usr/src/etc/defaults; make install
install -o root -g wheel  -m 444 bluetooth.device.conf devfs.rules
periodic.conf rc.conf /usr/tftpboot1//etc/defaults
cd /usr/src/etc/devd; make install
install -o root -g wheel  -m 644 asus.conf /usr/tftpboot1//etc/devd
cd /usr/src/etc/gss; make install
install -o root -g wheel  -m 444 mech qop /usr/tftpboot1//etc/gss
cd /usr/src/etc/periodic; make install
===> daily (install)
install -o root -g wheel  -m 755 100.clean-disks 110.clean-tmps
120.clean-preserve 200.backup-passwd 330.news 400.status-disks
404.status-zfs 405.status-ata-raid 406.status-gmirror 407.status-graid3
408.status-gstripe 409.status-gconcat 420.status-network
450.status-security 999.local 310.accounting 470.status-named
300.calendar 130.clean-msgs 480.status-ntpd 140.clean-rwho
430.status-rwho 150.clean-hoststat 210.backup-aliases 440.status-mailq
460.status-mail-rejects 500.queuerun /usr/tftpboot1//etc/periodic/daily
===> security (install)
install -o root -g wheel  -m 755 100.chksetuid 200.chkmounts 300.chkuid0
400.passwdless 410.logincheck 700.kernelmsg 800.loginfail 900.tcpwrap
security.functions 510.ipfdenied 500.ipfwdenied 550.ipfwlimit
520.pfdenied /usr/tftpboot1//etc/periodic/security
===> weekly (install)
install -o root -g wheel  -m 755 340.noid 999.local 310.locate
320.whatis 330.catman 400.status-pkg /usr/tftpboot1//etc/periodic/weekly
===> monthly (install)
install -o root -g wheel  -m 755 999.local
200.accounting /usr/tftpboot1//etc/periodic/monthly
cd /usr/src/etc/rc.d; make install
install -o root -g wheel  -m 555 DAEMON FILESYSTEMS LOGIN NETWORKING
SERVERS abi accounting addswap adjkerntz amd apm apmd archdep atm1 atm2
atm3 auditd auto_linklocal bgfsck bluetooth bootparams bridge bsnmpd
bthidd ccd cleanvar cleartmp cron ddb defaultroute devd devfs dhclient
dmesg dumpon encswap fsck ftp-proxy ftpd gbde geli geli2 gssd hcsecd
hostapd hostid hostname inetd initrandom ip6addrctl ip6fw ipfilter ipfs
ipfw ipmon ipnat ipsec ipxrouted jail kadmind kerberos keyserv kldxref
kpasswdd ldconfig local localpkg lockd lpd mixer motd mountcritlocal
mountcritremote mountlate mdconfig mdconfig2 mountd moused mroute6d
mrouted msgs named natd netif netoptions network_ipv6 newsyslog
nfsclient nfscbd nfsd nfsserver nfsuserd nisdomain nsswitch ntpd ntpdate
othermta pf pflog pfsync powerd power_profile ppp pppoed pwcheck quota
random rarpd resolv rfcomm_pppd_server root route6d routed routing
rpcbind rtadvd rwho savecore sdpd securelevel sendmail serial sppp statd
swap1 syscons sysctl syslogd timed tmp ugidfw var virecover watchdogd
wpa_supplicant ypbind yppasswdd ypserv ypset ypupdated ypxfrd zfs sshd
nscd /usr/tftpboot1//etc/rc.d
cd /usr/src/etc/../gnu/usr.bin/send-pr; make etc-gnats-freefall
install -o root -g wheel -m
0644  /usr/src/gnu/usr.bin/send-pr/categories  /usr/tftpboot1//etc/gnats/freefall
cd /usr/src/etc/../share/termcap; make etc-termcap
ln -fs /usr/share/misc/termcap /usr/tftpboot1//etc/termcap
cd /usr/src/etc/../usr.sbin/rmt; make etc-rmt
rm -f /usr/tftpboot1//etc/rmt
ln -s /usr/sbin/rmt /usr/tftpboot1//etc/rmt
cd /usr/src/etc/pam.d; make install
install -o root  -g wheel -m 444
README  /usr/tftpboot1//etc/pam.d/README
make: don't know how to make gdm. Stop
*** Error code 2

Stop in /usr/src/etc.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.

# dmesg 
Copyright (c) 1992-2009 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 8.0-BETA2 #7 r195750: Sat Jul 18 12:18:02 UTC 2009
    root@:/usr/obj/usr/src/sys/GENERIC
WARNING: WITNESS option enabled, expect reduced performance.
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Celeron(R) CPU          440  @ 2.00GHz (1995.01-MHz
686-class CPU)
  Origin = "GenuineIntel"  Id = 0x10661  Stepping = 1

Features=0xafebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE>
  Features2=0xe31d<SSE3,DTES64,MON,DS_CPL,TM2,SSSE3,CX16,xTPR,PDCM>
  AMD Features=0x20100000<NX,LM>
  AMD Features2=0x1<LAHF>
  TSC: P-state invariant
real memory  = 536870912 (512 MB)
avail memory = 1022689280 (975 MB)
ACPI APIC Table: <IntelR AWRDACPI>
ioapic0 <Version 2.0> irqs 0-23 on motherboard
kbd1 at kbdmux0
acpi0: <IntelR AWRDACPI> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: reservation of 0, a0000 (3) failed
acpi0: reservation of 100000, 3f5e0000 (3) failed
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
acpi_button0: <Power Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <PCI-PCI bridge> irq 16 at device 1.0 on pci0
pci1: <PCI bus> on pcib1
pcib2: <PCI-PCI bridge> at device 0.0 on pci1
pci2: <PCI bus> on pcib2
pcib3: <PCI-PCI bridge> at device 0.2 on pci1
pci3: <PCI bus> on pcib3
vgapci0: <VGA-compatible display> port 0xff00-0xff07 mem
0xfcc00000-0xfccfffff,0xd0000000-0xdfffffff irq 16 at device 2.0 on pci0
agp0: <Intel Q965 SVGA controller> on vgapci0
agp0: detected 7676k stolen memory
agp0: aperture size is 256M
pcib4: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
pci4: <ACPI PCI bus> on pcib4
em0: <Intel(R) PRO/1000 Network Connection 6.9.14> port 0x5f00-0x5f1f
mem 0xfdee0000-0xfdefffff irq 16 at device 0.0 on pci4
em0: Using MSI interrupt
em0: [FILTER]
em0: Ethernet address: 00:10:f3:15:ae:e8
pcib5: <ACPI PCI-PCI bridge> irq 17 at device 28.1 on pci0
pci5: <ACPI PCI bus> on pcib5
em1: <Intel(R) PRO/1000 Network Connection 6.9.14> port 0xdf00-0xdf1f
mem 0xfdce0000-0xfdcfffff irq 17 at device 0.0 on pci5
em1: Using MSI interrupt
em1: [FILTER]
em1: Ethernet address: 00:10:f3:15:ae:e9
pcib6: <ACPI PCI-PCI bridge> irq 18 at device 28.2 on pci0
pci6: <ACPI PCI bus> on pcib6
em2: <Intel(R) PRO/1000 Network Connection 6.9.14> port 0xcf00-0xcf1f
mem 0xfdae0000-0xfdafffff irq 18 at device 0.0 on pci6
em2: Using MSI interrupt
em2: [FILTER]
em2: Ethernet address: 00:10:f3:15:ae:ea
pcib7: <ACPI PCI-PCI bridge> irq 19 at device 28.3 on pci0
pci7: <ACPI PCI bus> on pcib7
em3: <Intel(R) PRO/1000 Network Connection 6.9.14> port 0xaf00-0xaf1f
mem 0xfd8e0000-0xfd8fffff irq 19 at device 0.0 on pci7
em3: Using MSI interrupt
em3: [FILTER]
em3: Ethernet address: 00:10:f3:15:ae:eb
pcib8: <ACPI PCI-PCI bridge> irq 16 at device 28.4 on pci0
pci8: <ACPI PCI bus> on pcib8
em4: <Intel(R) PRO/1000 Network Connection 6.9.14> port 0x9f00-0x9f1f
mem 0xfd6e0000-0xfd6fffff irq 16 at device 0.0 on pci8
em4: Using MSI interrupt
em4: [FILTER]
em4: Ethernet address: 00:10:f3:15:ae:ec
pcib9: <ACPI PCI-PCI bridge> irq 17 at device 28.5 on pci0
pci9: <ACPI PCI bus> on pcib9
em5: <Intel(R) PRO/1000 Network Connection 6.9.14> port 0x8f00-0x8f1f
mem 0xfd4e0000-0xfd4fffff irq 17 at device 0.0 on pci9
em5: Using MSI interrupt
em5: [FILTER]
em5: Ethernet address: 00:10:f3:15:ae:ed
uhci0: <Intel 82801H (ICH8) USB controller USB-A> port 0xfe00-0xfe1f irq
23 at device 29.0 on pci0
uhci0: [ITHREAD]
uhci0: LegSup = 0x003b
usbus0: <Intel 82801H (ICH8) USB controller USB-A> on uhci0
uhci1: <Intel 82801H (ICH8) USB controller USB-B> port 0xfd00-0xfd1f irq
20 at device 29.1 on pci0
uhci1: [ITHREAD]
uhci1: LegSup = 0x0010
usbus1: <Intel 82801H (ICH8) USB controller USB-B> on uhci1
ehci0: <Intel 82801H (ICH8) USB 2.0 controller USB2-A> mem
0xfdfff000-0xfdfff3ff irq 23 at device 29.7 on pci0
ehci0: [ITHREAD]
usbus2: EHCI version 1.0
usbus2: <Intel 82801H (ICH8) USB 2.0 controller USB2-A> on ehci0
pcib10: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci10: <ACPI PCI bus> on pcib10
em6: <Intel(R) PRO/1000 Network Connection 6.9.14> port 0xbf00-0xbf3f
mem 0xfd0e0000-0xfd0fffff,0xfd0c0000-0xfd0dffff irq 18 at device 14.0 on
pci10
em6: [FILTER]
em6: Ethernet address: 00:10:f3:15:ae:ee
em7: <Intel(R) PRO/1000 Network Connection 6.9.14> port 0xbe00-0xbe3f
mem 0xfd0a0000-0xfd0bffff,0xfd080000-0xfd09ffff irq 17 at device 15.0 on
pci10
em7: [FILTER]
em7: Ethernet address: 00:10:f3:15:ae:ef
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel ICH8 SATA300 controller> port
0xfa00-0xfa07,0xf900-0xf903,0xf800-0xf807,0xf700-0xf703,0xf600-0xf60f,0xf500-0xf50f irq 19 at device 31.2 on pci0
atapci0: [ITHREAD]
ata2: <ATA channel 0> on atapci0
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci0
ata3: [ITHREAD]
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
atapci1: <Intel ICH8 SATA300 controller> port
0xf300-0xf307,0xf200-0xf203,0xf100-0xf107,0xf000-0xf003,0xef00-0xef0f,0xee00-0xee0f irq 19 at device 31.5 on pci0
atapci1: [ITHREAD]
ata4: <ATA channel 0> on atapci1
ata4: [ITHREAD]
ata5: <ATA channel 1> on atapci1
ata5: [ITHREAD]
acpi_tz0: <Thermal Zone> on acpi0
atrtc0: <AT realtime clock> port 0x70-0x73 irq 8 on acpi0
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
uart0: [FILTER]
uart0: console (9600,n,8,1)
uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
uart1: [FILTER]
ppc0: <Parallel port> port 0x378-0x37f irq 7 on acpi0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
ppc0: [ITHREAD]
ppbus0: <Parallel port bus> on ppc0
plip0: <PLIP network interface> on ppbus0
plip0: [ITHREAD]
lpt0: <Printer> on ppbus0
lpt0: [ITHREAD]
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
cpu0: <ACPI CPU> on acpi0
p4tcc0: <CPU Frequency Thermal Control> on cpu0
pmtimer0 on isa0
orm0: <ISA Option ROMs> at iomem
0xc0000-0xcafff,0xcc000-0xccfff,0xef000-0xeffff pnpid ORM0000 on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on
isa0
ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0
ata0: [ITHREAD]
ata1 at port 0x170-0x177,0x376 irq 15 on isa0
ata1: [ITHREAD]
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
Timecounter "TSC" frequency 1995012830 Hz quality 800
Timecounters tick every 1.000 msec
usbus0: 12Mbps Full Speed USB v1.0
usbus1: 12Mbps Full Speed USB v1.0
usbus2: 480Mbps High Speed USB v2.0
ad4: FAILURE - SET_MULTI status=51<READY,DSC,ERROR> error=4<ABORTED>
ad4: 1943MB <TRANSCEND 20070418> at ata2-master SATA150
ugen0.1: <Intel> at usbus0
uhub0: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
ugen1.1: <Intel> at usbus1
uhub1: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1
ugen2.1: <Intel> at usbus2
uhub2: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus2
ad8: 305245MB <SAMSUNG HD321KJ CP100-10> at ata4-master SATA300
WARNING: WITNESS option enabled, expect reduced performance.
GEOM: ad8s1: geometry does not match label (255h,63s != 16h,63s).
Root mount waiting for: usbus2 usbus1 usbus0
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
Root mount waiting for: usbus2
Root mount waiting for: usbus2
uhub2: 6 ports with 6 removable, self powered
Trying to mount root from ufs:/dev/ad8s1a
WARNING: /tmp was not properly dismounted
WARNING: /usr was not properly dismounted
WARNING: /var was not properly dismounted
em0: link state changed to UP
lock order reversal:
 1st 0xc4caead0 ufs (ufs) @ /usr/src/sys/ufs/ffs/ffs_snapshot.c:423
 2nd 0xd85133a0 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2558
 3rd 0xc4a6f594 ufs (ufs) @ /usr/src/sys/ufs/ffs/ffs_snapshot.c:544
KDB: stack backtrace:
db_trace_self_wrapper(c0c6bc14,e6cec408,c08bc9d5,c08ad71b,c0c6eac2,...)
at db_trace_self_wrapper+0x26
kdb_backtrace(c08ad71b,c0c6eac2,c452be90,c452efb8,e6cec464,...) at
kdb_backtrace+0x29
_witness_debugger(c0c6eac2,c4a6f594,c0c617fd,c452efb8,c0c8d400,...) at
_witness_debugger+0x25
witness_checkorder(c4a6f594,9,c0c8d400,220,0,...) at witness_checkorder
+0x839
__lockmgr_args(c4a6f594,80100,c4a6f5b0,0,0,...) at __lockmgr_args+0x7a7
ffs_lock(e6cec574,c0efbb18,c4ca6764,80100,c4a6f53c,...) at ffs_lock+0x8a
VOP_LOCK1_APV(c0d6e900,e6cec574,e6cec594,c0d87380,c4a6f53c,...) at
VOP_LOCK1_APV+0xb5
_vn_lock(c4a6f53c,80100,c0c8d400,220,c455b600,...) at _vn_lock+0x5e
ffs_snapshot(c49dca10,c49db620,c0c8ed65,15f,c0c7506a,...) at
ffs_snapshot+0x150b
ffs_mount(c49dca10,0,c0c75557,3d2,0,...) at ffs_mount+0x14aa
vfs_donmount(c4ca66c0,211000,c45b5b00,c45b5b00,bfbfecb4,...) at
vfs_donmount+0x1012
nmount(c4ca66c0,e6ceccf8,c,c4ca66c0,c0d4fe38,...) at nmount+0x75
syscall(e6cecd38) at syscall+0x2a3
Xint0x80_syscall() at Xint0x80_syscall+0x20
--- syscall (378, FreeBSD ELF32, nmount), eip = 0x280ee76b, esp =
0xbfbfeadc, ebp = 0xbfbfee28 ---
lock order reversal:
 1st 0xd85133a0 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2558
 2nd 0xc4a21bdc snaplk (snaplk)
@ /usr/src/sys/ufs/ffs/ffs_snapshot.c:793
KDB: stack backtrace:
db_trace_self_wrapper(c0c6bc14,e6cec408,c08bc9d5,c08ad71b,c0c6eaa9,...)
at db_trace_self_wrapper+0x26
kdb_backtrace(c08ad71b,c0c6eaa9,c452be90,c452f2f8,e6cec464,...) at
kdb_backtrace+0x29
_witness_debugger(c0c6eaa9,c4a21bdc,c0c8d462,c452f2f8,c0c8d400,...) at
_witness_debugger+0x25
witness_checkorder(c4a21bdc,9,c0c8d400,319,c4caeaec,...) at
witness_checkorder+0x839
__lockmgr_args(c4a21bdc,80400,c4caeaec,0,0,...) at __lockmgr_args+0x7a7
ffs_lock(e6cec574,0,0,80400,c4caea78,...) at ffs_lock+0x8a
VOP_LOCK1_APV(c0d6e900,e6cec574,c195cb90,c0d87380,c4caea78,...) at
VOP_LOCK1_APV+0xb5
_vn_lock(c4caea78,80400,c0c8d400,319,0,...) at _vn_lock+0x5e
ffs_snapshot(c49dca10,c49db620,c0c8ed65,15f,c0c7506a,...) at
ffs_snapshot+0x28b6
ffs_mount(c49dca10,0,c0c75557,3d2,0,...) at ffs_mount+0x14aa
vfs_donmount(c4ca66c0,211000,c45b5b00,c45b5b00,bfbfecb4,...) at
vfs_donmount+0x1012
nmount(c4ca66c0,e6ceccf8,c,c4ca66c0,c0d4fe38,...) at nmount+0x75
syscall(e6cecd38) at syscall+0x2a3
Xint0x80_syscall() at Xint0x80_syscall+0x20
--- syscall (378, FreeBSD ELF32, nmount), eip = 0x280ee76b, esp =
0xbfbfeadc, ebp = 0xbfbfee28 ---
lock order reversal:
 1st 0xc4a21bdc snaplk (snaplk) @ /usr/src/sys/kern/vfs_vnops.c:296
 2nd 0xc4caead0 ufs (ufs) @ /usr/src/sys/ufs/ffs/ffs_snapshot.c:1587
KDB: stack backtrace:
db_trace_self_wrapper(c0c6bc14,e6cec8b8,c08bc9d5,c08ad71b,c0c6eaa9,...)
at db_trace_self_wrapper+0x26
kdb_backtrace(c08ad71b,c0c6eaa9,c452f2f8,c452efb8,e6cec914,...) at
kdb_backtrace+0x29
_witness_debugger(c0c6eaa9,c4caead0,c0c617fd,c452efb8,c0c8d400,...) at
_witness_debugger+0x25
witness_checkorder(c4caead0,9,c0c8d400,633,0,...) at witness_checkorder
+0x839
__lockmgr_args(c4caead0,80000,0,0,0,...) at __lockmgr_args+0x7a7
ffs_snapremove(c4caea78,c49dca10,0,c0c76f01,41d,...) at ffs_snapremove
+0x11f
softdep_releasefile(c4b6dd24,e6ceca9c,2,c0efbae8,c0d553dc,...) at
softdep_releasefile+0x3b
ufs_inactive(e6cecadc,c4caeaec,c4caea78,c4caeaec,e6cecaf4,...) at
ufs_inactive+0x1bc
VOP_INACTIVE_APV(c0d6e900,e6cecadc,c0c75d38,924,c0d87340,...) at
VOP_INACTIVE_APV+0xa5
vinactive(c0d6e900,e6cecb10,c0c75d38,8aa,128,...) at vinactive+0x8e
vput(c4caea78,e6cecb4c,c0c76f01,128,0,...) at vput+0x1cd
vn_close(c4caea78,1,c456d100,c4ca66c0,0,...) at vn_close+0x19a
vn_closefile(c49f0620,c4ca66c0,3,0,c49f0620,...) at vn_closefile+0xe4
_fdrop(c49f0620,c4ca66c0,e6cecc18,c08bc81c,0,c4ca6764,c0efbae8,c0d569c0,c0c63538,c4ca302c,45b,c0c63538,e6cecc40,c0883a80,c4ca302c,8,c0c63538,45b) at _fdrop+0x43
closef(c49f0620,c4ca66c0,45b,440,c4ca302c,...) at closef+0x290
kern_close(c4ca66c0,4,e6cecd2c,c0ba8e93,c4ca66c0,...) at kern_close
+0x117
close(c4ca66c0,e6ceccf8,4,c0c6f8c2,c0d4d588,...) at close+0x1a
syscall(e6cecd38) at syscall+0x2a3
Xint0x80_syscall() at Xint0x80_syscall+0x20
--- syscall (6, FreeBSD ELF32, close), eip = 0x28192253, esp =
0xbfbfeadc, ebp = 0xbfbfee28 ---
lock order reversal:
 1st 0xd858bbb0 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2558
 2nd 0xc49a1a00 dirhash (dirhash)
@ /usr/src/sys/ufs/ufs/ufs_dirhash.c:285
KDB: stack backtrace:
db_trace_self_wrapper(c0c6bc14,e6cfca74,c08bc9d5,c08ad71b,c0c6eaa9,...)
at db_trace_self_wrapper+0x26
kdb_backtrace(c08ad71b,c0c6eaa9,c452be90,c452f020,e6cfcad0,...) at
kdb_backtrace+0x29
_witness_debugger(c0c6eaa9,c49a1a00,c0c8f887,c452f020,c0c8f520,...) at
_witness_debugger+0x25
witness_checkorder(c49a1a00,9,c0c8f520,11d,0,...) at witness_checkorder
+0x839
_sx_xlock(c49a1a00,0,c0c8f520,11d,da6cd018,...) at _sx_xlock+0x85
ufsdirhash_acquire(0,e,c47a6000,d858bb50,da6cd018,...) at
ufsdirhash_acquire+0x35
ufsdirhash_remove(c4dd31d0,da6cd018,18,e6cfcb60,e6cfcb5c,...) at
ufsdirhash_remove+0x14
ufs_dirremove(c4dd6a78,c4def658,500800c,0,c4dd6a78,...) at ufs_dirremove
+0xe5
ufs_remove(e6cfcc34,0,0,0,c4decb84,...) at ufs_remove+0x6e
VOP_REMOVE_APV(c0d6e900,e6cfcc34,c4decb84,e6cfcc0c,28216238,...) at
VOP_REMOVE_APV+0xa5
kern_unlinkat(c4ca5d80,ffffff9c,28216238,0,e6cfcc80,...) at
kern_unlinkat+0x181
kern_unlink(c4ca5d80,28216238,0,e6cfcd2c,c0ba8e93,...) at kern_unlink
+0x27
unlink(c4ca5d80,e6cfccf8,4,c0c89eb5,c0d4d5f8,...) at unlink+0x22
syscall(e6cfcd38) at syscall+0x2a3
Xint0x80_syscall() at Xint0x80_syscall+0x20
--- syscall (10, FreeBSD ELF32, unlink), eip = 0x28168d6f, esp =
0xbfbfec5c, ebp = 0xbfbfec88 ---
# 



From danger at FreeBSD.org  Sat Jul 18 17:04:31 2009
From: danger at FreeBSD.org (Daniel Gerzo)
Date: Sat Jul 18 17:05:03 2009
Subject: make distribution Re: 8.0-BETA2 Available
In-Reply-To: <1247933100.14935.20.camel@mvn-desktop>
References: <1247887759.14210.18.camel@neo.cse.buffalo.edu>
	<1247933100.14935.20.camel@mvn-desktop>
Message-ID: <4A61FCC0.4040303@FreeBSD.org>

Marten Vijn wrote:
> cd /usr/src
> make distribution gives an error
> 
> data below,
> 

> README  /usr/tftpboot1//etc/pam.d/README
> make: don't know how to make gdm. Stop
> *** Error code 2
> 
> Stop in /usr/src/etc.
> *** Error code 1
> 
> Stop in /usr/src.
> *** Error code 1
> 
> Stop in /usr/src.

I believe r195753 fixes this problem. Please update your sources.

-- 
S pozdravom / Best regards
   Daniel Gerzo, FreeBSD committer
From info at martenvijn.nl  Sat Jul 18 17:14:37 2009
From: info at martenvijn.nl (Marten Vijn)
Date: Sat Jul 18 17:14:50 2009
Subject: make distribution Re: 8.0-BETA2 Available
In-Reply-To: <4A61FCC0.4040303@FreeBSD.org>
References: <1247887759.14210.18.camel@neo.cse.buffalo.edu>
	<1247933100.14935.20.camel@mvn-desktop> <4A61FCC0.4040303@FreeBSD.org>
Message-ID: <1247937267.14935.23.camel@mvn-desktop>

On Sat, 2009-07-18 at 18:48 +0200, Daniel Gerzo wrote:
> Marten Vijn wrote:
> > cd /usr/src
> > make distribution gives an error
> > 
> > data below,
> > 
> 
> > README  /usr/tftpboot1//etc/pam.d/README
> > make: don't know how to make gdm. Stop
> > *** Error code 2
> > 
> > Stop in /usr/src/etc.
> > *** Error code 1
> > 
> > Stop in /usr/src.
> > *** Error code 1
> > 
> > Stop in /usr/src.
> 
> I believe r195753 fixes this problem. Please update your sources.

I should have mentioned my rev: 

Last Changed Rev: 195752

updating to

Last Changed Rev: 195754 Fixes the issues
thanks,

Marten


> 
-- 
http://martenvijn.nl                 Marten Vijn 
http://martenvijn.nl/trac/wiki/soas  Sugar on a Stick
http://bsd.wifisoft.org/nek/         The Network Event Kit
http://har2009.org                   13th-16th August 
http://opencommunitycamp.org         26th Jul - 2nd August

From bjsptyltdstore at sify.com  Sun Jul 19 03:47:04 2009
From: bjsptyltdstore at sify.com (Bryan James)
Date: Sun Jul 19 03:47:10 2009
Subject: Order To New Zealand
Message-ID: <200907182120.n6ILKteX023842@n22.sivit.org>

<<< No Message Collected >>>
From mkhitrov at gmail.com  Sun Jul 19 14:51:41 2009
From: mkhitrov at gmail.com (Maxim Khitrov)
Date: Sun Jul 19 14:51:48 2009
Subject: twa (3ware 9690SA) error on shutdown
Message-ID: <26ddd1750907190727o59d49a9bm4bc730592c898389@mail.gmail.com>

I'm playing around with the 3ware 9690SA raid controller. At first, I
was using FreeBSD 8.0-BETA2, but it kept encountering errors after
start-up and on shutdown. There is no 8.x driver on the 3ware site, so
I decided to go back to 7.2-RELEASE. This, however, did not solve the
problem. The major one that I'm having right now is that the system
refuses to reboot. After issuing the command, this is what I see
toward the end:

Uptime: 9h41m43s
twa0: ERROR: (0x15: 0x1104): Internal request timed out: request =
0xfffffffe80223a28
twa0: INFO: (0x16: 0x1108): Resetting Controller...:
twa0: INFO: (0x04: 0x0001): Controller reset occurred: resets=1
twa0: INFO: (0x16: 0x1107): Controller reset done!:
twa0: ERROR: (0x15: 0x1015): Can't close connection with controller: error = 60
twa0: ERROR: (0x05: 0x2015): Failed to shutdown Common
Layer/controller: error = 60

Here the system freezes and I have to hold the power button for 5 sec
to turn the power off and then restart. This happened with the default
twa driver, so I downloaded the 9.5.2 code set from 3ware website and
tried to use the twa.ko that comes with that release (for amd64). This
also did not fix the problem.

There is one other issue that may be related to this one. The verify
process for a newly created array is never finished. When the system
is started, I see a "verify started" message and the activity leds of
the drivers connected to the controller light up. If I reboot the
system at this point, the first problem does not occur. On other hand,
if I wait maybe 5 minutes the activity lights turn off, indicating
that something happens to the verify process, and at this point I can
no longer reboot the system.

My guess is that the verify process causes some sort of a problem for
the driver or the controller itself, which then prevents normal
communication during shutdown. Has anyone else encountered this
problem or has a solution for it?

- Max
From kensmith at cse.Buffalo.EDU  Sun Jul 19 18:17:10 2009
From: kensmith at cse.Buffalo.EDU (Ken Smith)
Date: Sun Jul 19 18:17:30 2009
Subject: HEADS-UP: Shared Library Versions bumped...
Message-ID: <1248027417.14210.110.camel@neo.cse.buffalo.edu>


First I want to apologize.  This should have happened a bit sooner in
our release cycle than now.  To be honest I had slipped into "We have
symbol versioning for our libraries now" mode.  But only a few of the
libraries currently have that turned on and I sorta forgot we still need
to deal with all the shared libraries that do not have symbol versioning
enabled yet.  Sorry for the hassle this will cause.

Today with svn commit 195767 I bumped the version number of all
non-symbol-version-ed shared libraries in preparation for 8.0-REL.  We
do this just in case API/ABI changes occured in head between 7.0 and
now, it lets us provide the older library versions as "compatibility
library ports" in the ports tree.

The problem is that as of the next time you update a machine that had
been running -current you are best off reinstalling all ports or other
applications you have on the machine.  When you reboot after doing the
update to the base system everything you have installed will still work
because the old shared library versions will still be there.  However
anything you build on the machine after its base system gets updated
would be linked against the newer base system shared libraries but any
libraries that are part of ports or other applications (e.g. the Xorg
libraries) would have been linked against the older library versions.
You really don't want to leave things that way.

The ports folks will be starting up a fresh package build now but it
takes some time for full package runs like this to complete, get
uploaded, and then propagate out to the mirrors.  If you tend to use
pre-built packages instead of building them as ports yourself you might
want to just hold off on updating anything until they let us know a
fresh set of packages is available.  And BETA3 will definitely be
scheduled for after the fresh set of packages becomes available.

And again - sorry for the hassle.

-- 
                                                Ken Smith
- From there to here, from here to      |       kensmith@cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090719/bfa02e69/attachment.pgp
From kensmith at cse.Buffalo.EDU  Sun Jul 19 18:33:58 2009
From: kensmith at cse.Buffalo.EDU (Ken Smith)
Date: Sun Jul 19 18:34:12 2009
Subject: HEADS-UP: Shared Library Versions bumped...
In-Reply-To: <58F0204B-ECE6-479A-AAC2-7868E71ABB43@exscape.org>
References: <1248027417.14210.110.camel@neo.cse.buffalo.edu>
	<58F0204B-ECE6-479A-AAC2-7868E71ABB43@exscape.org>
Message-ID: <1248028426.14210.114.camel@neo.cse.buffalo.edu>

On Sun, 2009-07-19 at 20:26 +0200, Thomas Backman wrote:
> On Jul 19, 2009, at 20:16, Ken Smith wrote:
> > The problem is that as of the next time you update a machine that had
> > been running -current you are best off reinstalling all ports or other
> > applications you have on the machine.  When you reboot after doing the
> > update to the base system everything you have installed will still  
> > work
> > because the old shared library versions will still be there.  However
> > anything you build on the machine after its base system gets updated
> > would be linked against the newer base system shared libraries but any
> > libraries that are part of ports or other applications (e.g. the Xorg
> > libraries) would have been linked against the older library versions.
> > You really don't want to leave things that way.
> So, to be clear: a fresh ports tree and "portupgrade -af" after  
> building and installing r195767+ should be enough to solve any  
> problems? (installkernel, installworld, reboot, portupgrade -af)
> 

Correct for those of you who let portupgrade do all the building for you
(which the example command you give does).  The reason I'm being careful
is portupgrade can also be told to fetch pre-built packages.  At the
moment that will not work, if you use that approach please hold off
until the ports folks let us know the packages have been rebuilt.

-- 
                                                Ken Smith
- From there to here, from here to      |       kensmith@cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090719/dd7b3c33/attachment.pgp
From serenity at exscape.org  Sun Jul 19 18:41:48 2009
From: serenity at exscape.org (Thomas Backman)
Date: Sun Jul 19 18:41:57 2009
Subject: HEADS-UP: Shared Library Versions bumped...
In-Reply-To: <1248027417.14210.110.camel@neo.cse.buffalo.edu>
References: <1248027417.14210.110.camel@neo.cse.buffalo.edu>
Message-ID: <58F0204B-ECE6-479A-AAC2-7868E71ABB43@exscape.org>

On Jul 19, 2009, at 20:16, Ken Smith wrote:
> The problem is that as of the next time you update a machine that had
> been running -current you are best off reinstalling all ports or other
> applications you have on the machine.  When you reboot after doing the
> update to the base system everything you have installed will still  
> work
> because the old shared library versions will still be there.  However
> anything you build on the machine after its base system gets updated
> would be linked against the newer base system shared libraries but any
> libraries that are part of ports or other applications (e.g. the Xorg
> libraries) would have been linked against the older library versions.
> You really don't want to leave things that way.
So, to be clear: a fresh ports tree and "portupgrade -af" after  
building and installing r195767+ should be enough to solve any  
problems? (installkernel, installworld, reboot, portupgrade -af)

Regards,
Thomas
From romain at blogreen.org  Sun Jul 19 20:26:40 2009
From: romain at blogreen.org (Romain =?iso-8859-1?Q?Tarti=E8re?=)
Date: Sun Jul 19 20:26:48 2009
Subject: Value of $? lost in the beginning of a function.
Message-ID: <20090719202638.GA85228@blogreen.org>

Hi!

Simple test case:

----8<----------------------
#!/bin/sh
foo()
{
  echo "\$?=$? \$1=$1"
}
false
foo $?
----8<----------------------

% sh foo.sh
$?=0 $1=1
% zsh foo.sh
$?=1 $1=1
% bash foo.sh
$?=1 $1=1

As you can see, the value of $? is ? lost ? when FreeBSD sh enters a
function.  Is this supposed to behave this way?

Thanks,
Romain

-- 
Romain Tarti?re <romain@blogreen.org>        http://romain.blogreen.org/
pgp: 8DAB A124 0DA4 7024 F82A  E748 D8E9 A33F FF56 FF43 (ID: 0xFF56FF43)
(plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090719/929bb0cc/attachment.pgp
From glen.j.barber at gmail.com  Sun Jul 19 20:32:30 2009
From: glen.j.barber at gmail.com (Glen Barber)
Date: Sun Jul 19 20:32:37 2009
Subject: Value of $? lost in the beginning of a function.
In-Reply-To: <20090719202638.GA85228@blogreen.org>
References: <20090719202638.GA85228@blogreen.org>
Message-ID: <4ad871310907191332r2f933a33l36c121903bc0742f@mail.gmail.com>

2009/7/19 Romain Tarti?re <romain@blogreen.org>:
> Hi!
>
> Simple test case:
>
> ----8<----------------------
> #!/bin/sh
> foo()
> {
> ?echo "\$?=$? \$1=$1"
> }
> false
> foo $?
> ----8<----------------------
>
> % sh foo.sh
> $?=0 $1=1
> % zsh foo.sh
> $?=1 $1=1
> % bash foo.sh
> $?=1 $1=1
>
> As you can see, the value of $? is ? lost ? when FreeBSD sh enters a
> function. ?Is this supposed to behave this way?
>

Hi.

I'm no expert at shell scripting, but my first presumption is that
since you have '#!/bin/sh' at the beginning of the script, it is
creating a new subshell, and overwriting the value.  What happens if
you replace '#!/bin/sh' with '#!/usr/local/bin/zsh' ?

-- 
Glen Barber
From romain at blogreen.org  Sun Jul 19 20:45:00 2009
From: romain at blogreen.org (Romain =?iso-8859-1?Q?Tarti=E8re?=)
Date: Sun Jul 19 20:45:07 2009
Subject: Value of $? lost in the beginning of a function.
In-Reply-To: <4ad871310907191332r2f933a33l36c121903bc0742f@mail.gmail.com>
References: <20090719202638.GA85228@blogreen.org>
	<4ad871310907191332r2f933a33l36c121903bc0742f@mail.gmail.com>
Message-ID: <20090719204458.GD85228@blogreen.org>

Hi Glen,

On Sun, Jul 19, 2009 at 04:32:28PM -0400, Glen Barber wrote:
> > % sh foo.sh
> > % zsh foo.sh
> > % bash foo.sh
> What happens if you replace '#!/bin/sh' with '#!/usr/local/bin/zsh' ?

This is not related to my problem since I am not running the script
using ./foo.sh but directly using the proper shell.  sh just behaves
differently, that looks odd so I would like to know if it is a bug in sh
or if there is no specification for this and the behaviour depends of
the implementation of each shell, in which case I have to tweak the
script I am porting to avoid this construct (passing $? as an argument
for example).

Romain

-- 
Romain Tarti?re <romain@blogreen.org>        http://romain.blogreen.org/
pgp: 8DAB A124 0DA4 7024 F82A  E748 D8E9 A33F FF56 FF43 (ID: 0xFF56FF43)
(plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090719/fdd0cf0e/attachment.pgp
From jilles at stack.nl  Sun Jul 19 20:47:56 2009
From: jilles at stack.nl (Jilles Tjoelker)
Date: Sun Jul 19 20:48:04 2009
Subject: Value of $? lost in the beginning of a function.
In-Reply-To: <20090719202638.GA85228@blogreen.org>
References: <20090719202638.GA85228@blogreen.org>
Message-ID: <20090719204755.GA94947@stack.nl>

On Sun, Jul 19, 2009 at 10:26:38PM +0200, Romain Tarti?re wrote:
> Hi!
> 
> Simple test case:
> 
> ----8<----------------------
> #!/bin/sh
> foo()
> {
>   echo "\$?=$? \$1=$1"
> }
> false
> foo $?
> ----8<----------------------
> 
> % sh foo.sh
> $?=0 $1=1
> % zsh foo.sh
> $?=1 $1=1
> % bash foo.sh
> $?=1 $1=1
> 
> As you can see, the value of $? is ? lost ? when FreeBSD sh enters a
> function.  Is this supposed to behave this way?

This has been fixed in 8.x:

Revision 185231 - Directory Listing
Modified Sun Nov 23 20:23:57 2008 UTC (7 months, 3 weeks ago) by stefanf

Fix $? at the first command of a function.  The previous exit status was saved
twice and thus lost.

-- 
Jilles Tjoelker
From glen.j.barber at gmail.com  Sun Jul 19 20:48:17 2009
From: glen.j.barber at gmail.com (Glen Barber)
Date: Sun Jul 19 20:48:24 2009
Subject: Value of $? lost in the beginning of a function.
In-Reply-To: <20090719204458.GD85228@blogreen.org>
References: <20090719202638.GA85228@blogreen.org>
	<4ad871310907191332r2f933a33l36c121903bc0742f@mail.gmail.com>
	<20090719204458.GD85228@blogreen.org>
Message-ID: <4ad871310907191348n6f43cffpaf391990b35b9c19@mail.gmail.com>

2009/7/19 Romain Tarti?re <romain@blogreen.org>:
> Hi Glen,
>
> On Sun, Jul 19, 2009 at 04:32:28PM -0400, Glen Barber wrote:
>> > % sh foo.sh
>> > % zsh foo.sh
>> > % bash foo.sh
>> What happens if you replace '#!/bin/sh' with '#!/usr/local/bin/zsh' ?
>
> This is not related to my problem since I am not running the script
> using ./foo.sh but directly using the proper shell. ?sh just behaves
> differently, that looks odd so I would like to know if it is a bug in sh
> or if there is no specification for this and the behaviour depends of
> the implementation of each shell, in which case I have to tweak the
> script I am porting to avoid this construct (passing $? as an argument
> for example).
>
> Romain
>

My understanding was this:

If you specify 'sh foo.sh' at the shell, the script will be run in a
/bin/sh shell, _unless_ you override the shell _in_ the script.

Ie, 'sh foo.sh' containing '#!/bin/sh' being redundant, but 'zsh
foo.sh' containing '#!/bin/sh' would execute using zsh.


-- 
Glen Barber
From romain at blogreen.org  Sun Jul 19 20:53:25 2009
From: romain at blogreen.org (Romain =?iso-8859-1?Q?Tarti=E8re?=)
Date: Sun Jul 19 20:53:32 2009
Subject: Value of $? lost in the beginning of a function.
In-Reply-To: <20090719204755.GA94947@stack.nl>
References: <20090719202638.GA85228@blogreen.org>
	<20090719204755.GA94947@stack.nl>
Message-ID: <20090719205324.GG85228@blogreen.org>

On Sun, Jul 19, 2009 at 10:47:55PM +0200, Jilles Tjoelker wrote:
> This has been fixed in 8.x:
Cool, thanks!

-- 
Romain Tarti?re <romain@blogreen.org>        http://romain.blogreen.org/
pgp: 8DAB A124 0DA4 7024 F82A  E748 D8E9 A33F FF56 FF43 (ID: 0xFF56FF43)
(plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090719/bfd2d134/attachment.pgp
From nox at jelal.kn-bremen.de  Sun Jul 19 22:19:31 2009
From: nox at jelal.kn-bremen.de (Juergen Lock)
Date: Sun Jul 19 22:19:39 2009
Subject: new umass panic on 7-stable built today
Message-ID: <20090719215224.GA2271@triton.kn-bremen.de>

Hi!

 So I wanted to use an usb key on this freshly updated 7-stable box,
and got a panic just after plugging it in: :(

zsh triton# kgdb /boot/kernel/kernel.symbols /var/crash/vmcore.9
...
umass0: <OCZ Technology ATV, class 0/0, rev 2.00/11.00, addr 2> on uhub5
umass0:1:0:-1: Attached to scbus1


Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address	= 0x290
fault code		= supervisor read data, page not present
instruction pointer	= 0x8:0xffffffff804d67d4
stack pointer	        = 0x10:0xffffff8085487da0
frame pointer	        = 0x10:0xffffff8085487de0
code segment		= base 0x0, limit 0xfffff, type 0x1b
			= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags	= interrupt enabled, resume, IOPL = 0
current process		= 38 (usb5)
trap number		= 12
panic: page fault
cpuid = 0
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2a
panic() at panic+0x182
trap_fatal() at trap_fatal+0x2b3
trap_pfault() at trap_pfault+0x294
trap() at trap+0x312
calltrap() at calltrap+0x8
--- trap 0xc, rip = 0xffffffff804d67d4, rsp = 0xffffff8085487da0, rbp = 0xffffff8085487de0 ---
usb_transfer_complete() at usb_transfer_complete+0x1d4
bus_dmamap_load() at bus_dmamap_load+0x314
usbd_transfer() at usbd_transfer+0xee
usbd_do_request_flags_pipe() at usbd_do_request_flags_pipe+0x8f
usbd_do_request_flags() at usbd_do_request_flags+0x25
usbd_get_string_desc() at usbd_get_string_desc+0x9b
usbd_get_string() at usbd_get_string+0x83
uhub_child_pnpinfo_str() at uhub_child_pnpinfo_str+0xd9
devaddq() at devaddq+0xd5
device_attach() at device_attach+0x13a
usbd_new_device() at usbd_new_device+0x821
uhub_explore() at uhub_explore+0x1bd
usb_discover() at usb_discover+0x38
usb_event_thread() at usb_event_thread+0x8a
fork_exit() at fork_exit+0x11f
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp = 0xffffff8085488d30, rbp = 0 ---
Uptime: 1m1s
Physical memory: 8176 MB
Dumping 4605 MB: 4590 4574 4558 4542 4526 4510 4494 4478 4462 4446 4430 4414 4398 4382 4366 4350 4334 4318 4302 4286 4270 4254 4238 4222 4206 4190 4174 4158 4142 4126 4110 4094 4078 4062 4046 4030 4014 3998 3982 3966 3950 3934 3918 3902 3886 3870 3854 3838 3822 3806 3790 3774 3758 3742 3726 3710 3694 3678 3662 3646 3630 3614 3598 3582 3566 3550 3534 3518 3502 3486 3470 3454 3438 3422 3406 3390 3374 3358 3342 3326 3310 3294 3278 3262 3246 3230 3214 3198 3182 3166 3150 3134 3118 3102 3086 3070 3054 3038 3022 3006 2990 2974 2958 2942 2926 2910 2894 2878 2862 2846 2830 2814 2798 2782 2766 2750 2734 2718 2702 2686 2670 2654 2638 2622 2606 2590 2574 2558 2542 2526 2510 2494 2478 2462 2446 2430 2414 2398 2382 2366 2350 2334 2318 2302 2286 2270 2254 2238 2222 2206 2190 2174 2158 2142 2126 2110 2094 2078 2062 2046 2030 2014 1998 1982 1966 1950 1934 1918 1902 1886 1870 1854 1838 1822 1806 1790 1774 1758 1742 1726 1710 1694 1678 1662 1646 1630 1614 1598 1582 1566 1550 1534 1518 1502 1486 1470 1454 1438 1422 1406 1390 1374 1358 1342 1326 1310 1294 1278 1262 1246 1230 1214 1198 1182 1166 1150 1134 1118 1102 1086 1070 1054 1038 1022 1006 990 974 958 942 926 910 894 878 862 846 830 814 798 782 766 750 734 718 702 686 670 654 638 622 606 590 574 558 542 526 510 494 478 462 446 430 414 398 382 366 350 334 318 302 286 270 254 238 222 206 190 174 158 142 126 110 94 78 62 46 30 14

Reading symbols from /boot/kernel/umass.ko...Reading symbols from /boot/kernel/umass.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/umass.ko
#0  doadump () at pcpu.h:195
195		__asm __volatile("movq %%gs:0,%0" : "=r" (td));
(kgdb) bt
#0  doadump () at pcpu.h:195
#1  0xffffffff80567248 in boot (howto=260)
    at /usr/home/nox/src72s2/src/sys/kern/kern_shutdown.c:418
#2  0xffffffff805676ac in panic (fmt=Variable "fmt" is not available.
)
    at /usr/home/nox/src72s2/src/sys/kern/kern_shutdown.c:574
#3  0xffffffff8082f953 in trap_fatal (frame=0xc, eva=Variable "eva" is not available.
)
    at /usr/home/nox/src72s2/src/sys/amd64/amd64/trap.c:756
#4  0xffffffff8082fd34 in trap_pfault (frame=0xffffff8085487cf0, usermode=0)
    at /usr/home/nox/src72s2/src/sys/amd64/amd64/trap.c:672
#5  0xffffffff808306e2 in trap (frame=0xffffff8085487cf0)
    at /usr/home/nox/src72s2/src/sys/amd64/amd64/trap.c:443
#6  0xffffffff80819cce in calltrap ()
    at /usr/home/nox/src72s2/src/sys/amd64/amd64/exception.S:218
#7  0xffffffff804d67d4 in usb_transfer_complete (xfer=0xffffff00046b1000)
    at /usr/home/nox/src72s2/src/sys/dev/usb/usbdi.c:949
#8  0xffffffff80815bf4 in bus_dmamap_load (dmat=0xffffff0004499880, 
    map=0xffffff000478ec00, buf=0xffffff8085487fe0, buflen=0, 
    callback=0xffffffff804d68b0 <usbd_start_transfer>, 
    callback_arg=0xffffff00046b1000, flags=0)
    at /usr/home/nox/src72s2/src/sys/amd64/amd64/busdma_machdep.c:738
#9  0xffffffff804d6f2e in usbd_transfer (xfer=0xffffff00046b1000)
    at /usr/home/nox/src72s2/src/sys/dev/usb/usbdi.c:312
#10 0xffffffff804d717f in usbd_do_request_flags_pipe (dev=0xffffff0004751600, 
---Type <return> to continue, or q <return> to quit---
    pipe=0xffffff000474cd80, req=0xffffff8085487f80, data=0xffffff8085487fe0, 
    flags=Variable "flags" is not available.
) at /usr/home/nox/src72s2/src/sys/dev/usb/usbdi.c:1100
#11 0xffffffff804d72b5 in usbd_do_request_flags (dev=Variable "dev" is not available.
)
    at /usr/home/nox/src72s2/src/sys/dev/usb/usbdi.c:1070
#12 0xffffffff804d518b in usbd_get_string_desc (dev=0xffffff0004751600, sindex=Variable "sindex" is not available.

) at /usr/home/nox/src72s2/src/sys/dev/usb/usb_subr.c:171
#13 0xffffffff804d6473 in usbd_get_string (dev=0xffffff0004751600, si=3, 
    buf=0xffffff8085488160 "", len=128)
    at /usr/home/nox/src72s2/src/sys/dev/usb/usbdi.c:1353
#14 0xffffffff804cdb49 in uhub_child_pnpinfo_str (cbdev=Variable "cbdev" is not available.
)
    at /usr/home/nox/src72s2/src/sys/dev/usb/uhub.c:658
#15 0xffffffff80590ce5 in devaddq (type=0xffffffff8090dccf "+", 
    what=0xffffff00046b0000 "umass0 vendor=0x0325 product=0xac02 devclass=0x00 devsubclass=0x00 release=0x1100 sernum=\"AA04012700152689\" intclass=0x08 intsubclass=0x06", dev=0xffffff00046c0200)
    at /usr/home/nox/src72s2/src/sys/kern/subr_bus.c:625
#16 0xffffffff805914ba in device_attach (dev=0xffffff00046c0200)
    at /usr/home/nox/src72s2/src/sys/kern/subr_bus.c:668
#17 0xffffffff804d5b41 in usbd_new_device (parent=0xffffff00044a0200, 
    bus=0xffffff0004472000, depth=Variable "depth" is not available.
)
    at /usr/home/nox/src72s2/src/sys/dev/usb/usb_subr.c:926
#18 0xffffffff804cd79d in uhub_explore (dev=0xffffff00044a0300)
    at /usr/home/nox/src72s2/src/sys/dev/usb/uhub.c:523
---Type <return> to continue, or q <return> to quit---
#19 0xffffffff804d23e8 in usb_discover (v=Variable "v" is not available.
)
    at /usr/home/nox/src72s2/src/sys/dev/usb/usb.c:724
#20 0xffffffff804d33aa in usb_event_thread (arg=Variable "arg" is not available.
)
    at /usr/home/nox/src72s2/src/sys/dev/usb/usb.c:440
#21 0xffffffff8054115f in fork_exit (
    callout=0xffffffff804d3320 <usb_event_thread>, arg=0xffffff00044b1580, 
    frame=0xffffff8085488c80)
    at /usr/home/nox/src72s2/src/sys/kern/kern_fork.c:811
#22 0xffffffff8081a0ae in fork_trampoline ()
    at /usr/home/nox/src72s2/src/sys/amd64/amd64/exception.S:554
#23 0x0000000000000000 in ?? ()
#24 0x0000000000000000 in ?? ()
#25 0x0000000000000001 in ?? ()
#26 0x0000000000000000 in ?? ()
#27 0x0000000000000000 in ?? ()
#28 0x0000000000000000 in ?? ()
#29 0x0000000000000000 in ?? ()
#30 0x0000000000000000 in ?? ()
#31 0x0000000000000000 in ?? ()
#32 0x0000000000000000 in ?? ()
#33 0x0000000000000000 in ?? ()
#34 0x0000000000000000 in ?? ()
#35 0x0000000000000000 in ?? ()
---Type <return> to continue, or q <return> to quit---
#36 0x0000000000000000 in ?? ()
#37 0x0000000000000000 in ?? ()
#38 0x0000000000000000 in ?? ()
#39 0x0000000000000000 in ?? ()
#40 0x0000000000000000 in ?? ()
#41 0x0000000000000000 in ?? ()
#42 0x0000000000000000 in ?? ()
#43 0x0000000000000000 in ?? ()
#44 0x0000000000000000 in ?? ()
#45 0x0000000000000000 in ?? ()
#46 0x0000000000000000 in ?? ()
#47 0x0000000000d84000 in ?? ()
#48 0x0000000000000001 in ?? ()
#49 0xffffffff80bba848 in sleepq_chains ()
#50 0xffffff00044a5720 in ?? ()
#51 0xffffff00044a5a70 in ?? ()
#52 0xffffff8085487da0 in ?? ()
#53 0xffffff8085487d38 in ?? ()
#54 0xffffff00044a5720 in ?? ()
#55 0xffffffff8058b01e in sched_switch (td=0x0, newtd=Cannot access memory at address 0xffffffffffffffa8
)
    at /usr/home/nox/src72s2/src/sys/kern/sched_ule.c:1938
Previous frame inner to this frame (corrupt stack?)
(kgdb) fr 7
#7  0xffffffff804d67d4 in usb_transfer_complete (xfer=0xffffff00046b1000)
    at /usr/home/nox/src72s2/src/sys/dev/usb/usbdi.c:949
949			STAILQ_REMOVE_HEAD(&pipe->queue, next);
(kgdb) p pipe
$1 = 0xffffff000474cd80
(kgdb) p *pipe
$2 = {iface = 0x0, device = 0xffffff0004751600, endpoint = 0xffffff0004751638, 
  refcnt = 1, running = 0 '\0', aborting = 0 '\0', queue = {stqh_first = 0x0, 
    stqh_last = 0xffffff000474cda0}, next = {le_next = 0x0, le_prev = 0x0}, 
  intrxfer = 0x0, repeat = 0 '\0', interval = -1, methods = 0xffffffff80afbf00}
(kgdb) q
zsh triton# 

 Suggestions/patches welcome...

 Thanx,
	Juergen
From oliver.pntr at gmail.com  Sun Jul 19 23:36:16 2009
From: oliver.pntr at gmail.com (Oliver Pinter)
Date: Sun Jul 19 23:36:23 2009
Subject: Value of $? lost in the beginning of a function.
In-Reply-To: <20090719205324.GG85228@blogreen.org>
References: <20090719202638.GA85228@blogreen.org>
	<20090719204755.GA94947@stack.nl>
	<20090719205324.GG85228@blogreen.org>
Message-ID: <6101e8c40907191636l60141229vc171116969c7e25d@mail.gmail.com>

do you plan to MFC this fix?


On 7/19/09, Romain Tarti?re <romain@blogreen.org> wrote:
> On Sun, Jul 19, 2009 at 10:47:55PM +0200, Jilles Tjoelker wrote:
>> This has been fixed in 8.x:
> Cool, thanks!
>
> --
> Romain Tarti?re <romain@blogreen.org>        http://romain.blogreen.org/
> pgp: 8DAB A124 0DA4 7024 F82A  E748 D8E9 A33F FF56 FF43 (ID: 0xFF56FF43)
> (plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated)
>
From bh at izb.knu.ac.kr  Sun Jul 19 23:47:01 2009
From: bh at izb.knu.ac.kr (Byung-Hee HWANG)
Date: Sun Jul 19 23:47:14 2009
Subject: HEADS-UP: Shared Library Versions bumped...
In-Reply-To: <1248027417.14210.110.camel@neo.cse.buffalo.edu> (Ken Smith's
	message of "Sun, 19 Jul 2009 14:16:57 -0400")
References: <1248027417.14210.110.camel@neo.cse.buffalo.edu>
Message-ID: <864ot8s0bf.fsf@betla.izb.knu.ac.kr>

Ken Smith <kensmith@cse.Buffalo.EDU> writes:

> First I want to apologize.  This should have happened a bit sooner in
> our release cycle than now.  To be honest I had slipped into "We have
> symbol versioning for our libraries now" mode.  But only a few of the
> libraries currently have that turned on and I sorta forgot we still need
> to deal with all the shared libraries that do not have symbol versioning
> enabled yet.  Sorry for the hassle this will cause.
>
> Today with svn commit 195767 I bumped the version number of all
> non-symbol-version-ed shared libraries in preparation for 8.0-REL.  We
> do this just in case API/ABI changes occured in head between 7.0 and
> now, it lets us provide the older library versions as "compatibility
> library ports" in the ports tree.
>
> The problem is that as of the next time you update a machine that had
> been running -current you are best off reinstalling all ports or other
> applications you have on the machine.  When you reboot after doing the
> update to the base system everything you have installed will still work
> because the old shared library versions will still be there.  However
> anything you build on the machine after its base system gets updated
> would be linked against the newer base system shared libraries but any
> libraries that are part of ports or other applications (e.g. the Xorg
> libraries) would have been linked against the older library versions.
> You really don't want to leave things that way.
>
> The ports folks will be starting up a fresh package build now but it
> takes some time for full package runs like this to complete, get
> uploaded, and then propagate out to the mirrors.  If you tend to use
> pre-built packages instead of building them as ports yourself you might
> want to just hold off on updating anything until they let us know a
> fresh set of packages is available.  And BETA3 will definitely be
> scheduled for after the fresh set of packages becomes available.
>
> And again - sorry for the hassle.

In my case, there is no upgrade with servers -- i have two servers
(4.11-STABLE, 6.3-RELEASE). So plz don't worry. Only what i do upgrade
is client which is my main desktop -- currently it runs as
7.2-RELEASE. Though! Don't worry because always i do upgrade as follow: 
=> csup => make world => reboot
=> (after coffee time)  
=> pkg_delete -af => pkg_add -r -v gnome (with several package)

That's very fine and fast for me, anyway...

-- 
Byung-Hee HWANG, KNU
? WWW: http://izb.knu.ac.kr/~bh/

"Come on, stick it in. Stick it in, Johnny, that's what you really want."
		-- Margot Ashton, "Chapter 1", page 12
From glen.j.barber at gmail.com  Mon Jul 20 00:17:24 2009
From: glen.j.barber at gmail.com (Glen Barber)
Date: Mon Jul 20 00:17:31 2009
Subject: Shell execution ( [was] Re: Value of $? lost in the beginning of a 
	function.)
Message-ID: <4ad871310907191717g1ed90be7y92250f2addc38d43@mail.gmail.com>

Possibly off-topic...


2009/7/19 Glen Barber <glen.j.barber@gmail.com>:
> 2009/7/19 Romain Tarti?re <romain@blogreen.org>:
>> Hi Glen,
>>
>> On Sun, Jul 19, 2009 at 04:32:28PM -0400, Glen Barber wrote:
>>> > % sh foo.sh
>>> > % zsh foo.sh
>>> > % bash foo.sh
>>> What happens if you replace '#!/bin/sh' with '#!/usr/local/bin/zsh' ?
>>
>> This is not related to my problem since I am not running the script
>> using ./foo.sh but directly using the proper shell. ?sh just behaves
>> differently, that looks odd so I would like to know if it is a bug in sh
>> or if there is no specification for this and the behaviour depends of
>> the implementation of each shell, in which case I have to tweak the
>> script I am porting to avoid this construct (passing $? as an argument
>> for example).
>>
>> Romain
>>
>
> My understanding was this:
>
> If you specify 'sh foo.sh' at the shell, the script will be run in a
> /bin/sh shell, _unless_ you override the shell _in_ the script.
>
> Ie, 'sh foo.sh' containing '#!/bin/sh' being redundant, but 'zsh
> foo.sh' containing '#!/bin/sh' would execute using zsh.
>
>

I meant to say in the last line: "'#!/bin/sh' would override the 'zsh' shell."

Can someone enlighten me if I am wrong about this?

-- 
Glen Barber
From marka at isc.org  Mon Jul 20 01:02:50 2009
From: marka at isc.org (Mark Andrews)
Date: Mon Jul 20 01:02:56 2009
Subject: Shell execution ( [was] Re: Value of $? lost in the beginning
	of a function.) 
In-Reply-To: Your message of "Sun, 19 Jul 2009 20:17:22 -0400."
	<4ad871310907191717g1ed90be7y92250f2addc38d43@mail.gmail.com> 
References: <4ad871310907191717g1ed90be7y92250f2addc38d43@mail.gmail.com> 
Message-ID: <200907200102.n6K12h1Y048534@drugs.dv.isc.org>


In message <4ad871310907191717g1ed90be7y92250f2addc38d43@mail.gmail.com>, Glen 
Barber writes:
> Possibly off-topic...
> 
> 
> 2009/7/19 Glen Barber <glen.j.barber@gmail.com>:
> > 2009/7/19 Romain Tarti=E8re <romain@blogreen.org>:
> >> Hi Glen,
> >>
> >> On Sun, Jul 19, 2009 at 04:32:28PM -0400, Glen Barber wrote:
> >>> > % sh foo.sh
> >>> > % zsh foo.sh
> >>> > % bash foo.sh
> >>> What happens if you replace '#!/bin/sh' with '#!/usr/local/bin/zsh' ?
> >>
> >> This is not related to my problem since I am not running the script
> >> using ./foo.sh but directly using the proper shell. =A0sh just behaves
> >> differently, that looks odd so I would like to know if it is a bug in sh
> >> or if there is no specification for this and the behaviour depends of
> >> the implementation of each shell, in which case I have to tweak the
> >> script I am porting to avoid this construct (passing $? as an argument
> >> for example).
> >>
> >> Romain
> >>
> >
> > My understanding was this:
> >
> > If you specify 'sh foo.sh' at the shell, the script will be run in a
> > /bin/sh shell, _unless_ you override the shell _in_ the script.
> >
> > Ie, 'sh foo.sh' containing '#!/bin/sh' being redundant, but 'zsh
> > foo.sh' containing '#!/bin/sh' would execute using zsh.
> >
> >
> 
> I meant to say in the last line: "'#!/bin/sh' would override the 'zsh' shel=
> l."
> 
> Can someone enlighten me if I am wrong about this?
> 
> --=20
> Glen Barber
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"

"#!" is used to define the interpretor when the file is exec'd.

perl, AFAIK, is the only interpretor that will look at what is after
the "#!" and modify it's behaviour.  All other a interpretors (shells)
treat "#!" as a comment.

Some shells used to examine the executable about to be called and
looked for "#!" and invoke the correct interpretor.  This was how
"#!" was supported before kernels has support for "#!".  It was all
done in userland.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
From glen.j.barber at gmail.com  Mon Jul 20 01:08:05 2009
From: glen.j.barber at gmail.com (Glen Barber)
Date: Mon Jul 20 01:08:12 2009
Subject: Shell execution ( [was] Re: Value of $? lost in the beginning
	of a function.)
In-Reply-To: <200907200102.n6K12h1Y048534@drugs.dv.isc.org>
References: <4ad871310907191717g1ed90be7y92250f2addc38d43@mail.gmail.com>
	<200907200102.n6K12h1Y048534@drugs.dv.isc.org>
Message-ID: <4ad871310907191808g8a81107wa17799284be176a@mail.gmail.com>

On Sun, Jul 19, 2009 at 9:02 PM, Mark Andrews<marka@isc.org> wrote:
>
> In message <4ad871310907191717g1ed90be7y92250f2addc38d43@mail.gmail.com>, Glen
> Barber writes:
>> Possibly off-topic...
>>
>>
>> 2009/7/19 Glen Barber <glen.j.barber@gmail.com>:
>> > 2009/7/19 Romain Tarti=E8re <romain@blogreen.org>:
>> >> Hi Glen,
>> >>
>> >> On Sun, Jul 19, 2009 at 04:32:28PM -0400, Glen Barber wrote:
>> >>> > % sh foo.sh
>> >>> > % zsh foo.sh
>> >>> > % bash foo.sh
>> >>> What happens if you replace '#!/bin/sh' with '#!/usr/local/bin/zsh' ?
>> >>
>> >> This is not related to my problem since I am not running the script
>> >> using ./foo.sh but directly using the proper shell. =A0sh just behaves
>> >> differently, that looks odd so I would like to know if it is a bug in sh
>> >> or if there is no specification for this and the behaviour depends of
>> >> the implementation of each shell, in which case I have to tweak the
>> >> script I am porting to avoid this construct (passing $? as an argument
>> >> for example).
>> >>
>> >> Romain
>> >>
>> >
>> > My understanding was this:
>> >
>> > If you specify 'sh foo.sh' at the shell, the script will be run in a
>> > /bin/sh shell, _unless_ you override the shell _in_ the script.
>> >
>> > Ie, 'sh foo.sh' containing '#!/bin/sh' being redundant, but 'zsh
>> > foo.sh' containing '#!/bin/sh' would execute using zsh.
>> >
>> >
>>
>> I meant to say in the last line: "'#!/bin/sh' would override the 'zsh' shel=
>> l."
>>
>> Can someone enlighten me if I am wrong about this?
>>
>
> "#!" is used to define the interpretor when the file is exec'd.
>
> perl, AFAIK, is the only interpretor that will look at what is after
> the "#!" and modify it's behaviour. ?All other a interpretors (shells)
> treat "#!" as a comment.
>
> Some shells used to examine the executable about to be called and
> looked for "#!" and invoke the correct interpretor. ?This was how
> "#!" was supported before kernels has support for "#!". ?It was all
> done in userland.
>

Hi, Mark.

You've given me enough information to point me in the right direction
on digging further into this.  Thanks, and I appreciate the response!


-- 
Glen Barber
From smithi at nimnet.asn.au  Mon Jul 20 03:17:06 2009
From: smithi at nimnet.asn.au (Ian Smith)
Date: Mon Jul 20 03:17:14 2009
Subject: Shell execution ( [was] Re: Value of $? lost in the beginning
 of a function.) 
In-Reply-To: <200907200102.n6K12h1Y048534@drugs.dv.isc.org>
References: <4ad871310907191717g1ed90be7y92250f2addc38d43@mail.gmail.com> 
	<200907200102.n6K12h1Y048534@drugs.dv.isc.org>
Message-ID: <20090720120342.H6107@sola.nimnet.asn.au>

On Mon, 20 Jul 2009, Mark Andrews wrote:
 > In message <4ad871310907191717g1ed90be7y92250f2addc38d43@mail.gmail.com>, Glen 
 > Barber writes:
 > > Possibly off-topic...
[..]
 > > > My understanding was this:
 > > >
 > > > If you specify 'sh foo.sh' at the shell, the script will be run in a
 > > > /bin/sh shell, _unless_ you override the shell _in_ the script.
 > > >
 > > > Ie, 'sh foo.sh' containing '#!/bin/sh' being redundant, but 'zsh
 > > > foo.sh' containing '#!/bin/sh' would execute using zsh.
 > > >
 > > >
 > > 
 > > I meant to say in the last line: "'#!/bin/sh' would override the 'zsh' shel=
 > > l."
 > > 
 > > Can someone enlighten me if I am wrong about this?
 >
 > "#!" is used to define the interpretor when the file is exec'd.
 > 
 > perl, AFAIK, is the only interpretor that will look at what is after
 > the "#!" and modify it's behaviour.  All other a interpretors (shells)
 > treat "#!" as a comment.
 > 
 > Some shells used to examine the executable about to be called and
 > looked for "#!" and invoke the correct interpretor.  This was how
 > "#!" was supported before kernels has support for "#!".  It was all
 > done in userland.

Some rexx scripts begin with this cute trick so they may be executed in 
any (UNIXish) shell as 'program', or specifically as 'rexx program', 
where it's just a regular rexx comment:

/*usr/bin/true;exec rexx -x "$0" "$@";exit# ReXX */
  /* Take a measure of REXX clauses-per-second (CPS)                 */
  /* Mike Cowlishaw (mfc@ibm.com).  Multi-platform.                  */
  /* 1.0 17 Jan 89 Original version                                  */

though I never understood why an exit would be needed after an exec .. 
just making sure I guess, or maybe catering for some variant or other.

cheers, Ian
From bh at izb.knu.ac.kr  Mon Jul 20 08:11:45 2009
From: bh at izb.knu.ac.kr (Byung-Hee HWANG)
Date: Mon Jul 20 08:11:53 2009
Subject: [OT] perfer mailer (MUA)
Message-ID: <86vdlnlqoe.fsf@betla.izb.knu.ac.kr>

First of all, this is pretty off topic. At once, i sent one email on
subject "Which one is best MTA for me?" in here stable@. At that time,
Postfix won, according to my memory..;;

Today i would like to fire about prefer mailer. Because i just like very
much about email stuff -- MTA, MUA, Mail routing, Email Internet
Draft.. and so on.. ;;

I use Gnome Desktop under FreeBSD 7.2-RELEASE. Since i moved to Gnus my
mailer, Gnome Desktop's prefer application does not allow to use Gnus as
default mailer (with "mailto:" link). However, Last night i solved the
problem by helping GNU mailing lists, info-gnus-english@gnu.org ..;;

When i started to use email with Gnome desktop, i use Evolution as default
mailer by Pav's recommendation. Pav, he does work for gnome@freebsd.org
; BTW, someday i discover some word "berkeley-unix" in an email header
on this freebsd mailing lists. The word "berkeley-unix" give me quite
excitement because "berkeley" is origin of FreeBSD in the history. 

At any rate, i did investgate about the mailer. After all, i knew the
mailer's name is Gnus from GNU/Emacs. From that day, i became Emacs's
fan! Now, i'm writing email on Gnus. While i go with Gnus (of
GNU/Emacs), i'm so happy as if i discover new utopia.  

OK, now i want to here your voice about prefer mailer. As mentioned
above, my prefer mailer (MUA) is Gnus ..;; 

Sincerely,
 
-- 
Byung-Hee HWANG
? WWW: http://izb.knu.ac.kr/~bh/

Lampone had not said a word all day, had not even glanced at the two men in
the back seat. He had opened the door for the Don, the car had been in front
of the bank when they emerged, he had done everything correctly but no more
than any well-trained chauffeur might do.
		-- The author's narration, "Chapter 20", page 292-293
From stark at mapper.nl  Mon Jul 20 10:08:43 2009
From: stark at mapper.nl (Mark Stapper)
Date: Mon Jul 20 10:08:50 2009
Subject: ZFS RAIDZ and atacontrol spindown settings
Message-ID: <4A643F5B.8080806@mapper.nl>

Good day,

I am the proud user of a FreeBSD 7.2 AMD64 system housing, amongst other
things, a data server.
My "server"(It's called "Yoshi") runs FreeBSD from a mirrored system
disc, and has a zfs RAIDZ array with 4 discs for bulky data.
As it is a home server, and I work during the day, these four discs were
spinning happily all day long without much use for them doing so.
To save the world(and money) I issued the command "atacontrol spindown
1800" for all the discs in my array spinning them down after thirty
minutes of idle spinning.
So far so good, me very happy! However, when I access the array after
the discs have been spun down, it spins up the discs one after the other...
Mind you one AFTER the other, taking 4*9 seconds to do a "ls" command on
my music directory.
Content as I am with the smooth down- and upspinning of the disks, I
would like it better if the four discs would spin up simultaneously.
Thus my  question: "Is it possible to \"group\" discs to be spun up
together, or to issue a custom command upon upspinning of a disc such as
to spin up other disks?"
Thanks!
Greetz,
Mark

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 259 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090720/4dc93b20/signature.pgp
From freebsd-stable-local at be-well.ilk.org  Mon Jul 20 11:29:35 2009
From: freebsd-stable-local at be-well.ilk.org (Lowell Gilbert)
Date: Mon Jul 20 11:29:42 2009
Subject: Shell execution ( [was] Re: Value of $? lost in the beginning
	of a function.)
In-Reply-To: <4ad871310907191717g1ed90be7y92250f2addc38d43@mail.gmail.com>
	(Glen Barber's message of "Sun\, 19 Jul 2009 20\:17\:22 -0400")
References: <4ad871310907191717g1ed90be7y92250f2addc38d43@mail.gmail.com>
Message-ID: <44tz17k46h.fsf@lowell-desk.lan>

Glen Barber <glen.j.barber@gmail.com> writes:

> Possibly off-topic...
>
>
> 2009/7/19 Glen Barber <glen.j.barber@gmail.com>:
>> 2009/7/19 Romain Tarti?re <romain@blogreen.org>:
>>> Hi Glen,
>>>
>>> On Sun, Jul 19, 2009 at 04:32:28PM -0400, Glen Barber wrote:
>>>> > % sh foo.sh
>>>> > % zsh foo.sh
>>>> > % bash foo.sh
>>>> What happens if you replace '#!/bin/sh' with '#!/usr/local/bin/zsh' ?
>>>
>>> This is not related to my problem since I am not running the script
>>> using ./foo.sh but directly using the proper shell. ?sh just behaves
>>> differently, that looks odd so I would like to know if it is a bug in sh
>>> or if there is no specification for this and the behaviour depends of
>>> the implementation of each shell, in which case I have to tweak the
>>> script I am porting to avoid this construct (passing $? as an argument
>>> for example).
>>>
>>> Romain
>>>
>>
>> My understanding was this:
>>
>> If you specify 'sh foo.sh' at the shell, the script will be run in a
>> /bin/sh shell, _unless_ you override the shell _in_ the script.
>>
>> Ie, 'sh foo.sh' containing '#!/bin/sh' being redundant, but 'zsh
>> foo.sh' containing '#!/bin/sh' would execute using zsh.
>>
>>
>
> I meant to say in the last line: "'#!/bin/sh' would override the 'zsh' shell."
>
> Can someone enlighten me if I am wrong about this?

The person to whom you were responding had it closer.

The shell specified in the "#!" first line is only consulted if you run
it as "./foo.sh".  Otherwise, it's input to the shell that you started,
and the line is only a comment.
From hlh at restart.be  Mon Jul 20 12:57:56 2009
From: hlh at restart.be (Henri Hennebert)
Date: Mon Jul 20 12:58:04 2009
Subject: 8.0-BETA1 - for the record - different paths followed by IPv4
 and IPv6 for 'local' connections
In-Reply-To: <B583FBF374231F4A89607B4D08578A4304673665@bcs-mail03.internal.cacheflow.com>
References: <4A5734C3.3000806@restart.be>	<B583FBF374231F4A89607B4D08578A4304673660@bcs-mail03.internal.cacheflow.com>	<4A5864DC.1070106@restart.be>
	<B583FBF374231F4A89607B4D08578A4304673665@bcs-mail03.internal.cacheflow.com>
Message-ID: <4A6469CE.4060907@restart.be>

Li, Qing wrote:
> The patch has been committed, svn revision 195643.
> 
> Thanks,
> 
> -- Qing
> 
Just another case where the route must be created:

[root@avoriaz ~]# ifconfig gif0
gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> metric 0 mtu 1280
	tunnel inet 212.239.166.57 --> 94.23.44.41
	inet6 fe80::21d:60ff:fead:2ace%gif0 prefixlen 64 scopeid 0x4
	inet6 2001:41d0:2:2d29:1:ffff:: --> 2001:41d0:2:2d29:0:ffff:: prefixlen 
128
	options=1<ACCEPT_REV_ETHIP_VER>

[root@avoriaz ~]# ping6 2001:41d0:2:2d29:1:ffff::
PING6(56=40+8+8 bytes) 2001:41d0:2:2d29:1:ffff:: --> 
2001:41d0:2:2d29:1:ffff::
^C
--- 2001:41d0:2:2d29:1:ffff:: ping6 statistics ---
4 packets transmitted, 0 packets received, 100.0% packet loss

[root@avoriaz ~]# route add -inet6 2001:41d0:2:2d29:1:ffff:: -interface lo0
add host 2001:41d0:2:2d29:1:ffff::: gateway lo0

[root@avoriaz ~]# ping6 2001:41d0:2:2d29:1:ffff::
PING6(56=40+8+8 bytes) 2001:41d0:2:2d29:1:ffff:: --> 
2001:41d0:2:2d29:1:ffff::
16 bytes from ::1, icmp_seq=0 hlim=64 time=0.531 ms
16 bytes from ::1, icmp_seq=1 hlim=64 time=0.884 ms
16 bytes from ::1, icmp_seq=2 hlim=64 time=0.748 ms
^C
--- 2001:41d0:2:2d29:1:ffff:: ping6 statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.531/0.721/0.884/0.145 ms

Thanks

Henri
> 
> -----Original Message-----
> From: Henri Hennebert [mailto:hlh@restart.be]
> Sent: Sat 7/11/2009 3:09 AM
> To: Li, Qing
> Cc: freebsd-stable@freebsd.org; freebsd-net@freebsd.org
> Subject: Re: 8.0-BETA1 - for the record - different paths followed by IPv4 and IPv6 for 'local' connections
>  
> Li, Qing wrote:
>> Hi,
>>
>> Please try patch-7-10 in my home directory http://people.freebsd.org/~qingli/
>> and let me know how it works out for you. I thought I had committed the patch 
>> but turned out I didn't.
> 
> I apply the patch, reset my pf.conf to its previous content and all is 
> running smoothly. By the way, I discover after my post that my 
> "solution" was not working for long (many bytes) connections and this is 
> solved too.
> 
> Many thank for your time
> 
> Henri
> 
> PS please commit as soon as possible
> 
>>> On 8.0-BETA1 there is an assymetry:
>>>
>>> netstat -rn display
>>>
>>> 192.168.24.1       link#3
>>> ....
>>> no entry for 2001:41d0:2:2d29:1:1::
>>>
>> This is by design as part of the new architecture in 8.0, which maintains 
>> the L2 ARP/ND6 and L3 routing tables separately.
>>
>> -- Qing
>>
>>
>>
>> -----Original Message-----
>> From: owner-freebsd-stable@freebsd.org on behalf of Henri Hennebert
>> Sent: Fri 7/10/2009 5:32 AM
>> To: freebsd-stable@freebsd.org; freebsd-st@freebsd.org
>> Subject: 8.0-BETA1 - for the record - different paths followed by IPv4 and IPv6 for 'local' connections
>>  
>> Hello,
>>
>> After upgrading from 7.2-STABLE to 8.0-BETA1 I encounter a problem when 
>> connecting with firefox to a local apache server using the global 
>> unicast IPv6 address of the local machine. pf.conf must be updated!
>>
>> My configuration:
>>
>> [root@avoriaz ~]# ifconfig em0
>>
>> em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
>> 	options=19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4>
>> 	ether 00:1d:60:ad:2a:ce
>> 	inet 192.168.24.1 netmask 0xffffff00 broadcast 192.168.24.255
>> 	inet6 fe80::21d:60ff:fead:2ace%em0 prefixlen 64 scopeid 0x1
>> 	inet6 2001:41d0:2:2d29:1:1:: prefixlen 80
>> 	media: Ethernet 100baseTX (100baseTX <half-duplex>)
>> 	status: active
>>
>> [root@avoriaz ~]# host www.restart.bel
>> www.restart.bel is an alias for avoriaz.restart.bel.
>> avoriaz.restart.bel has address 192.168.24.1
>> avoriaz.restart.bel has IPv6 address 2001:41d0:2:2d29:1:1::
>>
>> pf.conf:
>>
>> int_if="em0"
>> block in  log all
>> block out log all
>> set skip on lo0
>> antispoof quick for $int_if inet
>> # Allow trafic with physical internal network
>> pass in quick on $int_if from ($int_if:network) to ($int_if) keep state
>> pass out quick on $int_if from ($int_if) to ($int_if:network) keep state
>>
>> The problem:
>>
>> [root@avoriaz ~]# telnet -4 www.restart.bel 80
>> Trying 192.168.24.1...
>> Connected to avoriaz.restart.bel.
>> Escape character is '^]'.
>> ^]
>> telnet> quit
>> Connection closed.
>> [root@avoriaz ~]# telnet -6 www.restart.bel 80
>> Trying 2001:41d0:2:2d29:1:1::...
>> --->Never connect and get a timeout!
>>
>> tcpdump and logging in pf show me that
>>
>> For a IPv4 connection:
>> the packet from telnet to apache pass 2 times on lo0 (out and in)
>> the answer packet from apache to telnet pass 2 times on lo0 (out and in)
>>
>> So no problem, there is `set skip on lo0'
>>
>> For a IPv6 connection:
>> The first packet from telnet to apache pass 2 times on lo0 (out and in)
>> The answer packet from apache to telnet path on em0  and is rejected
>> due to the default flags S/SA.
>>
>> So I have to change pf.conf and replace the last line:
>> pass out quick on $int_if from ($int_if) to ($int_if:network) \
>> keep state flags any
>>
>> Then all is OK
>>
>> By the way, on 7.2
>>
>> netstat -rn display
>>
>> 192.168.24.1        00:1d:60:ad:2a:ce
>> ....
>> 2001:41d0:2:2d29:1:1::            00:1d:60:ad:2a:ce
>>
>>
>> On 8.0-BETA1 there is an assymetry:
>>
>> netstat -rn display
>>
>> 192.168.24.1       link#3
>> ....
>> no entry for 2001:41d0:2:2d29:1:1::
>>
>> Hope it may help someone
>>
>> Henri
>>
>> _______________________________________________
>> freebsd-stable@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>>
> 
> 
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"

From cristiano.deana at gmail.com  Mon Jul 20 13:25:19 2009
From: cristiano.deana at gmail.com (Cristiano Deana)
Date: Mon Jul 20 13:25:29 2009
Subject: ftpd - Logging and resolving IP
Message-ID: <d8a4930a0907200552h59d371d1g3514deabfac5126e@mail.gmail.com>

Hi,

i use ftpd (base system), logging login, xfer, auth failure. What i
need is to log the IP address of the client, not the hostname.
I looked in ftpd(8) ma it seems it's not possible to disable the
reverse resolution.

Any idea?

Thanks in advance

-- 
Cris, member of G.U.F.I
Italian FreeBSD User Group
http://www.gufi.org/
From glen.j.barber at gmail.com  Mon Jul 20 14:02:25 2009
From: glen.j.barber at gmail.com (Glen Barber)
Date: Mon Jul 20 14:02:32 2009
Subject: Shell execution ( [was] Re: Value of $? lost in the beginning
	of a function.)
In-Reply-To: <44tz17k46h.fsf@lowell-desk.lan>
References: <4ad871310907191717g1ed90be7y92250f2addc38d43@mail.gmail.com>
	<44tz17k46h.fsf@lowell-desk.lan>
Message-ID: <4ad871310907200702q6d13a44bqaeb2242d65866b16@mail.gmail.com>

Hi, Lowell

On Mon, Jul 20, 2009 at 7:02 AM, Lowell
Gilbert<freebsd-stable-local@be-well.ilk.org> wrote:
> Glen Barber <glen.j.barber@gmail.com> writes:
>
>> Possibly off-topic...
>>
>>
>> 2009/7/19 Glen Barber <glen.j.barber@gmail.com>:
>>> 2009/7/19 Romain Tarti?re <romain@blogreen.org>:
>>>> Hi Glen,
>>>>
>>>> On Sun, Jul 19, 2009 at 04:32:28PM -0400, Glen Barber wrote:
>>>>> > % sh foo.sh
>>>>> > % zsh foo.sh
>>>>> > % bash foo.sh
>>>>> What happens if you replace '#!/bin/sh' with '#!/usr/local/bin/zsh' ?
>>>>
>>>> This is not related to my problem since I am not running the script
>>>> using ./foo.sh but directly using the proper shell. ?sh just behaves
>>>> differently, that looks odd so I would like to know if it is a bug in sh
>>>> or if there is no specification for this and the behaviour depends of
>>>> the implementation of each shell, in which case I have to tweak the
>>>> script I am porting to avoid this construct (passing $? as an argument
>>>> for example).
>>>>
>>>> Romain
>>>>
>>>
>>> My understanding was this:
>>>
>>> If you specify 'sh foo.sh' at the shell, the script will be run in a
>>> /bin/sh shell, _unless_ you override the shell _in_ the script.
>>>
>>> Ie, 'sh foo.sh' containing '#!/bin/sh' being redundant, but 'zsh
>>> foo.sh' containing '#!/bin/sh' would execute using zsh.
>>>
>>>
>>
>> I meant to say in the last line: "'#!/bin/sh' would override the 'zsh' shell."
>>
>> Can someone enlighten me if I am wrong about this?
>
> The person to whom you were responding had it closer.
>
> The shell specified in the "#!" first line is only consulted if you run
> it as "./foo.sh". ?Otherwise, it's input to the shell that you started,
> and the line is only a comment.
>

I suppose that makes sense, but what if the script location is in the
user's $PATH?

-- 
Glen Barber
From kostikbel at gmail.com  Mon Jul 20 14:34:55 2009
From: kostikbel at gmail.com (Kostik Belousov)
Date: Mon Jul 20 14:35:04 2009
Subject: HEADS-UP: Shared Library Versions bumped...
In-Reply-To: <367b2c980907200729s57eafbbfw83c8ae5a94f41ffc@mail.gmail.com>
References: <1248027417.14210.110.camel@neo.cse.buffalo.edu>
	<58F0204B-ECE6-479A-AAC2-7868E71ABB43@exscape.org>
	<367b2c980907200729s57eafbbfw83c8ae5a94f41ffc@mail.gmail.com>
Message-ID: <20090720143439.GL55190@deviant.kiev.zoral.com.ua>

On Mon, Jul 20, 2009 at 04:29:39PM +0200, Olivier SMEDTS wrote:
> 2009/7/19 Thomas Backman <serenity@exscape.org>:
> > So, to be clear: a fresh ports tree and "portupgrade -af" after building and
> > installing r195767+ should be enough to solve any problems? (installkernel,
> > installworld, reboot, portupgrade -af)
> 
> But there won't be any problem until you do a "make delete-old-libs"
> in /usr/src/, right ?

Cherry-picking of the ports to upgrade is also problematic, as well as
a compilation of third party software.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090720/d61ef660/attachment.pgp
From olivier at gid0.org  Mon Jul 20 14:50:00 2009
From: olivier at gid0.org (Olivier SMEDTS)
Date: Mon Jul 20 14:50:08 2009
Subject: HEADS-UP: Shared Library Versions bumped...
In-Reply-To: <58F0204B-ECE6-479A-AAC2-7868E71ABB43@exscape.org>
References: <1248027417.14210.110.camel@neo.cse.buffalo.edu>
	<58F0204B-ECE6-479A-AAC2-7868E71ABB43@exscape.org>
Message-ID: <367b2c980907200729s57eafbbfw83c8ae5a94f41ffc@mail.gmail.com>

2009/7/19 Thomas Backman <serenity@exscape.org>:
> On Jul 19, 2009, at 20:16, Ken Smith wrote:
>>
>> The problem is that as of the next time you update a machine that had
>> been running -current you are best off reinstalling all ports or other
>> applications you have on the machine. ?When you reboot after doing the
>> update to the base system everything you have installed will still work
>> because the old shared library versions will still be there. ?However
>> anything you build on the machine after its base system gets updated
>> would be linked against the newer base system shared libraries but any
>> libraries that are part of ports or other applications (e.g. the Xorg
>> libraries) would have been linked against the older library versions.
>> You really don't want to leave things that way.
>
> So, to be clear: a fresh ports tree and "portupgrade -af" after building and
> installing r195767+ should be enough to solve any problems? (installkernel,
> installworld, reboot, portupgrade -af)

But there won't be any problem until you do a "make delete-old-libs"
in /usr/src/, right ?

Olivier

>
> Regards,
> Thomas
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>

-- 
Olivier Smedts                                                 _
                                        ASCII ribbon campaign ( )
e-mail: olivier@gid0.org        - against HTML email & vCards  X
www: http://www.gid0.org    - against proprietary attachments / \

  "Il y a seulement 10 sortes de gens dans le monde :
  ceux qui comprennent le binaire,
  et ceux qui ne le comprennent pas."
From pluknet at gmail.com  Mon Jul 20 15:03:10 2009
From: pluknet at gmail.com (pluknet)
Date: Mon Jul 20 15:03:17 2009
Subject: ftpd - Logging and resolving IP
In-Reply-To: <d8a4930a0907200552h59d371d1g3514deabfac5126e@mail.gmail.com>
References: <d8a4930a0907200552h59d371d1g3514deabfac5126e@mail.gmail.com>
Message-ID: <a31046fc0907200734v6588f11i7129611d87c91c7b@mail.gmail.com>

2009/7/20 Cristiano Deana <cristiano.deana@gmail.com>:
> Hi,
>
> i use ftpd (base system), logging login, xfer, auth failure. What i
> need is to log the IP address of the client, not the hostname.
> I looked in ftpd(8) ma it seems it's not possible to disable the
> reverse resolution.
>
> Any idea?
>
> Thanks in advance
>

I hope it's still applicable.

--- libexec/tftpd/tftpd.c.orig  2007-11-09 06:13:22.000000000 +0300
+++ libexec/tftpd/tftpd.c       2007-11-09 06:13:49.000000000 +0300
@@ -487,7 +487,7 @@
                char hbuf[NI_MAXHOST];

                getnameinfo((struct sockaddr *)&from, from.ss_len,
-                           hbuf, sizeof(hbuf), NULL, 0, 0);
+                           hbuf, sizeof(hbuf), NULL, 0, NI_NUMERICHOST);
                syslog(LOG_INFO, "%s: %s request for %s: %s", hbuf,
                        tp->th_opcode == WRQ ? "write" : "read",
                        filename, errtomsg(ecode));

-- 
wbr,
pluknet
From ivoras at freebsd.org  Mon Jul 20 15:16:02 2009
From: ivoras at freebsd.org (Ivan Voras)
Date: Mon Jul 20 15:16:10 2009
Subject: ZFS RAIDZ and atacontrol spindown settings
In-Reply-To: <4A643F5B.8080806@mapper.nl>
References: <4A643F5B.8080806@mapper.nl>
Message-ID: <h421n2$1kt$1@ger.gmane.org>

Mark Stapper wrote:
> Good day,
> 
> I am the proud user of a FreeBSD 7.2 AMD64 system housing, amongst other
> things, a data server.
> My "server"(It's called "Yoshi") runs FreeBSD from a mirrored system
> disc, and has a zfs RAIDZ array with 4 discs for bulky data.
> As it is a home server, and I work during the day, these four discs were
> spinning happily all day long without much use for them doing so.
> To save the world(and money) I issued the command "atacontrol spindown
> 1800" for all the discs in my array spinning them down after thirty
> minutes of idle spinning.
> So far so good, me very happy! However, when I access the array after
> the discs have been spun down, it spins up the discs one after the other...
> Mind you one AFTER the other, taking 4*9 seconds to do a "ls" command on
> my music directory.
> Content as I am with the smooth down- and upspinning of the disks, I
> would like it better if the four discs would spin up simultaneously.
> Thus my  question: "Is it possible to \"group\" discs to be spun up
> together, or to issue a custom command upon upspinning of a disc such as
> to spin up other disks?"

Good question but the answer is probably no - it really only depends on 
how ZFS accesses the drives; if it accesses them in sequence, you can't 
change it.

From exemys-mkt at exemys.com  Mon Jul 20 17:25:28 2009
From: exemys-mkt at exemys.com (Exemys Mkt)
Date: Mon Jul 20 17:25:35 2009
Subject: Industrial Wireless: Cellular or Wi-Fi ?
Message-ID: <b1bc707c04fc4b8fa8b4068296581e87@www.hostmailing.com>

This is a message in multipart MIME format.  Your mail client should not be displaying this. Consider upgrading your mail client to view this message correctly.

From freebsd-stable-local at be-well.ilk.org  Mon Jul 20 17:56:15 2009
From: freebsd-stable-local at be-well.ilk.org (Lowell Gilbert)
Date: Mon Jul 20 17:56:22 2009
Subject: Shell execution ( [was] Re: Value of $? lost in the beginning
	of a function.)
In-Reply-To: <4ad871310907200702q6d13a44bqaeb2242d65866b16@mail.gmail.com>
	(Glen Barber's message of "Mon\, 20 Jul 2009 10\:02\:23 -0400")
References: <4ad871310907191717g1ed90be7y92250f2addc38d43@mail.gmail.com>
	<44tz17k46h.fsf@lowell-desk.lan>
	<4ad871310907200702q6d13a44bqaeb2242d65866b16@mail.gmail.com>
Message-ID: <44k523fdc4.fsf@be-well.ilk.org>

Glen Barber <glen.j.barber@gmail.com> writes:

> Hi, Lowell
>
> On Mon, Jul 20, 2009 at 7:02 AM, Lowell
> Gilbert<freebsd-stable-local@be-well.ilk.org> wrote:
>> Glen Barber <glen.j.barber@gmail.com> writes:
>>
>>> Possibly off-topic...
>>>
>>>
>>> 2009/7/19 Glen Barber <glen.j.barber@gmail.com>:
>>>> 2009/7/19 Romain Tarti?re <romain@blogreen.org>:
>>>>> Hi Glen,
>>>>>
>>>>> On Sun, Jul 19, 2009 at 04:32:28PM -0400, Glen Barber wrote:
>>>>>> > % sh foo.sh
>>>>>> > % zsh foo.sh
>>>>>> > % bash foo.sh
>>>>>> What happens if you replace '#!/bin/sh' with '#!/usr/local/bin/zsh' ?
>>>>>
>>>>> This is not related to my problem since I am not running the script
>>>>> using ./foo.sh but directly using the proper shell. ?sh just behaves
>>>>> differently, that looks odd so I would like to know if it is a bug in sh
>>>>> or if there is no specification for this and the behaviour depends of
>>>>> the implementation of each shell, in which case I have to tweak the
>>>>> script I am porting to avoid this construct (passing $? as an argument
>>>>> for example).
>>>>>
>>>>> Romain
>>>>>
>>>>
>>>> My understanding was this:
>>>>
>>>> If you specify 'sh foo.sh' at the shell, the script will be run in a
>>>> /bin/sh shell, _unless_ you override the shell _in_ the script.
>>>>
>>>> Ie, 'sh foo.sh' containing '#!/bin/sh' being redundant, but 'zsh
>>>> foo.sh' containing '#!/bin/sh' would execute using zsh.
>>>>
>>>>
>>>
>>> I meant to say in the last line: "'#!/bin/sh' would override the 'zsh' shell."
>>>
>>> Can someone enlighten me if I am wrong about this?
>>
>> The person to whom you were responding had it closer.
>>
>> The shell specified in the "#!" first line is only consulted if you run
>> it as "./foo.sh". ?Otherwise, it's input to the shell that you started,
>> and the line is only a comment.
>>
>
> I suppose that makes sense, but what if the script location is in the
> user's $PATH?

That would be the same as "./foo.sh".  
The distinction is between whether the file is treated as an executable
or as input to a script.  You might find the manual page for execve(2)
useful for more detail on how the former case is handled.


From parv at pair.com  Mon Jul 20 18:03:57 2009
From: parv at pair.com (parv@pair.com)
Date: Mon Jul 20 18:04:04 2009
Subject: pkg_delete dumps core while deinstalling old libgtkhtml
Message-ID: <20090720174900.GA5299@holstein.holy.cow>

Hi,

While deinstalling libgtkhtml-2.11.1, pkg_delete (FreeBSD
6-STABLE/i386) dies due to segfault ...

  gdb /usr/sbin/pkg_delete -c /var/db/package/libgtkhtml-2.11.1/pkg_delete.core
  GNU gdb 6.1.1 [FreeBSD]
  ...
  This GDB was configured as "i386-marcel-freebsd"...(no debugging symbols found)...
  Core was generated by `pkg_delete'.
  Program terminated with signal 11, Segmentation fault.
  Reading symbols from /lib/libmd.so.3...(no debugging symbols found)...done.
  Loaded symbols for /lib/libmd.so.3
  Reading symbols from /lib/libutil.so.5...(no debugging symbols found)...done.
  Loaded symbols for /lib/libutil.so.5
  Reading symbols from /lib/libc.so.6...(no debugging symbols found)...done.
  Loaded symbols for /lib/libc.so.6
  Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done.
  Loaded symbols for /libexec/ld-elf.so.1
  #0  0x78152f52 in strcmp () from /lib/libc.so.6
  (gdb) bt
  #0  0x78152f52 in strcmp () from /lib/libc.so.6
  #1  0x0804b3e3 in ?? ()
  #2  0x08052060 in ?? ()
  #3  0x00000000 in ?? ()
  #4  0x00000000 in ?? ()
  #5  0x00000000 in ?? ()
  #6  0x00000000 in ?? ()
  #7  0x00000000 in ?? ()
  #8  0x00000000 in ?? ()
  #9  0x00000000 in ?? ()
  #10 0x08052040 in ?? ()
  #11 0x08056b60 in ?? ()
  #12 0xbfbfda08 in ?? ()
  #13 0x0804ad65 in ?? ()
  #14 0x00000000 in ?? ()
  #15 0x0000000c in ?? ()
  #16 0xbfbfd870 in ?? ()
  #17 0x78168518 in __sfvwrite () from /lib/libc.so.6


... if anybody needs missing symbols, could you please tell me what I
would need to do?

I could (write a program) myself (to) handle the file deletion, unless
there is already an existing program besides pkg_delete itself.  Is
there one?


  - Parv

-- 

From oberman at es.net  Mon Jul 20 18:13:36 2009
From: oberman at es.net (Kevin Oberman)
Date: Mon Jul 20 18:13:43 2009
Subject: HEADS-UP: Shared Library Versions bumped... 
In-Reply-To: Your message of "Mon, 20 Jul 2009 16:29:39 +0200."
	<367b2c980907200729s57eafbbfw83c8ae5a94f41ffc@mail.gmail.com> 
Message-ID: <20090720181313.DAA6C1CC0B@ptavv.es.net>

> Date: Mon, 20 Jul 2009 16:29:39 +0200
> From: Olivier SMEDTS <olivier@gid0.org>
> Sender: owner-freebsd-current@freebsd.org
> 
> 2009/7/19 Thomas Backman <serenity@exscape.org>:
> > On Jul 19, 2009, at 20:16, Ken Smith wrote:
> >>
> >> The problem is that as of the next time you update a machine that had
> >> been running -current you are best off reinstalling all ports or other
> >> applications you have on the machine.  When you reboot after doing the
> >> update to the base system everything you have installed will still work
> >> because the old shared library versions will still be there.  However
> >> anything you build on the machine after its base system gets updated
> >> would be linked against the newer base system shared libraries but any
> >> libraries that are part of ports or other applications (e.g. the Xorg
> >> libraries) would have been linked against the older library versions.
> >> You really don't want to leave things that way.
> >
> > So, to be clear: a fresh ports tree and "portupgrade -af" after building and
> > installing r195767+ should be enough to solve any problems? (installkernel,
> > installworld, reboot, portupgrade -af)
> 
> But there won't be any problem until you do a "make delete-old-libs"
> in /usr/src/, right ?

Wrong. As soon as you start updating ports you will start getting apps
which link to both old and new versions and that does not work. If you
don't update any ports which provide shared libs, you are OK.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@es.net			Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4  EADA 927D EBB3 987B 3751
From glen.j.barber at gmail.com  Mon Jul 20 18:25:10 2009
From: glen.j.barber at gmail.com (Glen Barber)
Date: Mon Jul 20 18:25:17 2009
Subject: Shell execution ( [was] Re: Value of $? lost in the beginning
	of a function.)
In-Reply-To: <44k523fdc4.fsf@be-well.ilk.org>
References: <4ad871310907191717g1ed90be7y92250f2addc38d43@mail.gmail.com>
	<44tz17k46h.fsf@lowell-desk.lan>
	<4ad871310907200702q6d13a44bqaeb2242d65866b16@mail.gmail.com>
	<44k523fdc4.fsf@be-well.ilk.org>
Message-ID: <4ad871310907201125u42789ff9h57c74c26b0538c18@mail.gmail.com>

On Mon, Jul 20, 2009 at 1:56 PM, Lowell
Gilbert<freebsd-stable-local@be-well.ilk.org> wrote:
> Glen Barber <glen.j.barber@gmail.com> writes:
>>> The shell specified in the "#!" first line is only consulted if you run
>>> it as "./foo.sh". ?Otherwise, it's input to the shell that you started,
>>> and the line is only a comment.
>>>
>>
>> I suppose that makes sense, but what if the script location is in the
>> user's $PATH?
>
> That would be the same as "./foo.sh".
> The distinction is between whether the file is treated as an executable
> or as input to a script. ?You might find the manual page for execve(2)
> useful for more detail on how the former case is handled.
>
>
>

Aha!  Yes, I will have a look.  Thanks for the point in the right direction.

-- 
Glen Barber
From glen.j.barber at gmail.com  Mon Jul 20 19:19:33 2009
From: glen.j.barber at gmail.com (Glen Barber)
Date: Mon Jul 20 19:19:40 2009
Subject: Shell execution ( [was] Re: Value of $? lost in the beginning
	of a function.)
In-Reply-To: <4A64C1A6.3080607@FreeBSD.org>
References: <4ad871310907191717g1ed90be7y92250f2addc38d43@mail.gmail.com>
	<4A64C1A6.3080607@FreeBSD.org>
Message-ID: <4ad871310907201219x42ea0f2ave0c288170ed56a96@mail.gmail.com>

On Mon, Jul 20, 2009 at 3:12 PM, Doug Barton<dougb@freebsd.org> wrote:
> Glen Barber wrote:
>> Possibly off-topic...
>
> It's very off topic for -stable. If you want to follow up on this,
> please do so in -hackers.
>
>> I meant to say in the last line: "'#!/bin/sh' would override the 'zsh' shell."
>>
>> Can someone enlighten me if I am wrong about this?
>
> It's trivial to create an example to test it yourself, don't ask when
> you can do. :)
>
> #!/bin/foo
> echo yes
>
> $ ./foo
> bash: ./foo: /bin/foo: bad interpreter: No such file or directory
>
> $ sh foo
> yes
>
> $ bash foo
> yes
>
>
> Now it's your turn. :)
>

Hi, Doug.

The test I was going to run was:
---------------------
#!/bin/sh
echo $SHELL
---------------------

which I would execute from $PATH and from 'sh/csh/zsh foo.sh', but I
haven't had much time to play around with it.  I plan on having time
later today after ${JOB}.


-- 
Glen Barber
From cdillon at wolves.k12.mo.us  Mon Jul 20 19:31:35 2009
From: cdillon at wolves.k12.mo.us (Chris Dillon)
Date: Mon Jul 20 19:31:42 2009
Subject: HEADS-UP: Shared Library Versions bumped...
In-Reply-To: <1248027417.14210.110.camel@neo.cse.buffalo.edu>
References: <1248027417.14210.110.camel@neo.cse.buffalo.edu>
Message-ID: <20090720141156.357757p2m3l4sxoc@www.wolves.k12.mo.us>

Quoting Ken Smith <kensmith@cse.Buffalo.EDU>:

> First I want to apologize.  This should have happened a bit sooner in
> our release cycle than now.  To be honest I had slipped into "We have
> symbol versioning for our libraries now" mode.  But only a few of the
> libraries currently have that turned on and I sorta forgot we still need
> to deal with all the shared libraries that do not have symbol versioning
> enabled yet.  Sorry for the hassle this will cause.
...snip...

Wouldn't this be a great opportunity to fix kern/133926 by bumping up  
the max username length?



-- 

Chris Dillon - NetEng/SysAdm
Reeds Spring R-IV School District
Technology Department
175 Elementary Rd.
Reeds Spring, MO  65737
Voice: 417-272-8266   Fax: 417-272-0015


From dougb at FreeBSD.org  Mon Jul 20 19:39:23 2009
From: dougb at FreeBSD.org (Doug Barton)
Date: Mon Jul 20 19:39:31 2009
Subject: Shell execution ( [was] Re: Value of $? lost in the beginning
 of a 	function.)
In-Reply-To: <4ad871310907191717g1ed90be7y92250f2addc38d43@mail.gmail.com>
References: <4ad871310907191717g1ed90be7y92250f2addc38d43@mail.gmail.com>
Message-ID: <4A64C1A6.3080607@FreeBSD.org>

Glen Barber wrote:
> Possibly off-topic...

It's very off topic for -stable. If you want to follow up on this,
please do so in -hackers.

> I meant to say in the last line: "'#!/bin/sh' would override the 'zsh' shell."
> 
> Can someone enlighten me if I am wrong about this?

It's trivial to create an example to test it yourself, don't ask when
you can do. :)

#!/bin/foo
echo yes

$ ./foo
bash: ./foo: /bin/foo: bad interpreter: No such file or directory

$ sh foo
yes

$ bash foo
yes


Now it's your turn. :)

Doug

-- 

    This .signature sanitized for your protection

From hiyorin at gmail.com  Tue Jul 21 03:05:09 2009
From: hiyorin at gmail.com (=?UTF-8?B?6Zue?=)
Date: Tue Jul 21 03:05:20 2009
Subject: 7.2-release/amd64: panic, spin lock held too long
In-Reply-To: <cf9b1ee00907160154j4311483by9d391d3d536995d6@mail.gmail.com>
References: <cf9b1ee00907061812r3da70018i1c8d8d12bb038a80@mail.gmail.com>
	<3bbf2fe10907061818v245abd0cgc3ca5073cb93aea4@mail.gmail.com>
	<cf9b1ee00907061825r34165c48x6727c50b3219d5fb@mail.gmail.com>
	<3bbf2fe10907061827g35eaeb49g26cf6fdb64436ca7@mail.gmail.com>
	<cf9b1ee00907071757i169d2a82la260798f364054f9@mail.gmail.com>
	<cf9b1ee00907080018s3f32c8afr4f65f01ce9ff1f25@mail.gmail.com>
	<3bbf2fe10907080250q35899d3dhc2f101b62c6e5306@mail.gmail.com>
	<4A5ECC8C.7030808@gmail.com>
	<cf9b1ee00907160154j4311483by9d391d3d536995d6@mail.gmail.com>
Message-ID: <c3670bd10907202005o7474f7c0m2ded1598f60a63d1@mail.gmail.com>

> I hope you can get some crash dumps for the developers to look at,
> Attilio was trying to help me but sadly the machine had to be put into
> active use so I could no longer play with FreeBSD due to unsolved
> instability.

I want to help investigate this problem also but I remembered that the
/var/crash was empty after the panic.. Just the same as your
situation.
So is there other ways to get the crash dumps?
My machine is also put into service now but I think it should be OK
for a short down time.

Regards,
C.C.
From barbara.xxx1975 at libero.it  Tue Jul 21 06:14:26 2009
From: barbara.xxx1975 at libero.it (barbara)
Date: Tue Jul 21 06:14:33 2009
Subject: 7.2-release/amd64: panic, spin lock held too long
Message-ID: <KN4BGI$40ABF3E58EAD1201403C9DA561E2402F@libero.it>

> > I hope you can get some crash dumps for the developers to look at,
> > Attilio was trying to help me but sadly the machine had to be put into
> > active use so I could no longer play with FreeBSD due to unsolved
> > instability.
> 
> I want to help investigate this problem also but I remembered that the
> /var/crash was empty after the panic.. Just the same as your
> situation.
> So is there other ways to get the crash dumps?
> My machine is also put into service now but I think it should be OK
> for a short down time.

Could that one (on i386) be related?
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/134584


From stark at mapper.nl  Tue Jul 21 08:53:54 2009
From: stark at mapper.nl (Mark Stapper)
Date: Tue Jul 21 08:54:02 2009
Subject: ZFS RAIDZ and atacontrol spindown settings
In-Reply-To: <9bbcef730907210137udf7f90ax21aa530ab859f8a6@mail.gmail.com>
References: <4A643F5B.8080806@mapper.nl> <h421n2$1kt$1@ger.gmane.org>
	<4A656076.2060205@mapper.nl>
	<9bbcef730907210137udf7f90ax21aa530ab859f8a6@mail.gmail.com>
Message-ID: <4A658205.5000709@mapper.nl>



Ivan Voras wrote:
> 2009/7/21 Mark Stapper <stark@mapper.nl>:
>   
>> Ivan Voras wrote:
>>     
>>> Mark Stapper wrote:
>>>       
>>>> Good day,
>>>>
>>>> I am the proud user of a FreeBSD 7.2 AMD64 system housing, amongst other
>>>> things, a data server.
>>>> My "server"(It's called "Yoshi") runs FreeBSD from a mirrored system
>>>> disc, and has a zfs RAIDZ array with 4 discs for bulky data.
>>>> As it is a home server, and I work during the day, these four discs were
>>>> spinning happily all day long without much use for them doing so.
>>>> To save the world(and money) I issued the command "atacontrol spindown
>>>> 1800" for all the discs in my array spinning them down after thirty
>>>> minutes of idle spinning.
>>>> So far so good, me very happy! However, when I access the array after
>>>> the discs have been spun down, it spins up the discs one after the
>>>> other...
>>>> Mind you one AFTER the other, taking 4*9 seconds to do a "ls" command on
>>>> my music directory.
>>>> Content as I am with the smooth down- and upspinning of the disks, I
>>>> would like it better if the four discs would spin up simultaneously.
>>>> Thus my  question: "Is it possible to \"group\" discs to be spun up
>>>> together, or to issue a custom command upon upspinning of a disc such as
>>>> to spin up other disks?"
>>>>         
>>> Good question but the answer is probably no - it really only depends
>>> on how ZFS accesses the drives; if it accesses them in sequence, you
>>> can't change it.
>>>       
>> I've been looking at writing a shell script which monitors
>> /var/log/messages.
>> something like:
>>
>> If last line in /var/log/messages is like "request while spun down.
>> Starting."
>>    spinup disks
>>
>> couple of problems though, I should probably poll the kernel messages
>> every second or so, but if I only check the last linee, I could miss the
>> spinup message.
>> I could count the number of lines in /var/log/messages and keep count of
>> the number of lines i've seen. Problem with this approach is that it's
>> not very efficient.
>> So I was hoping there is a way to receive this kernel message directly.
>> I am now thinking in the lines of a program which received a signal on
>> new kernel messages available or something similar.
>>
>> Any thoughts?
>>     
>
> You could do what "tail -f" does and simply hook a kqueue to get new
> messages from the /var/log/messages file.
>   
I'll try that! thanks!

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 259 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090721/5679ad08/signature.pgp
From arnaud.houdelette at tzim.net  Tue Jul 21 14:19:50 2009
From: arnaud.houdelette at tzim.net (Arnaud Houdelette)
Date: Tue Jul 21 14:19:57 2009
Subject: ZFS RAIDZ and atacontrol spindown settings
In-Reply-To: <4A658205.5000709@mapper.nl>
References: <4A643F5B.8080806@mapper.nl>
	<h421n2$1kt$1@ger.gmane.org>	<4A656076.2060205@mapper.nl>	<9bbcef730907210137udf7f90ax21aa530ab859f8a6@mail.gmail.com>
	<4A658205.5000709@mapper.nl>
Message-ID: <4A65CE7F.8040906@tzim.net>

Mark Stapper a ?crit :
> Ivan Voras wrote:
>   
>> 2009/7/21 Mark Stapper <stark@mapper.nl>:
>>   
>>     
>>> Ivan Voras wrote:
>>>     
>>>       
>>>> Mark Stapper wrote:
>>>>       
>>>>         
>>>>> Good day,
>>>>>
>>>>> I am the proud user of a FreeBSD 7.2 AMD64 system housing, amongst other
>>>>> things, a data server.
>>>>> My "server"(It's called "Yoshi") runs FreeBSD from a mirrored system
>>>>> disc, and has a zfs RAIDZ array with 4 discs for bulky data.
>>>>> As it is a home server, and I work during the day, these four discs were
>>>>> spinning happily all day long without much use for them doing so.
>>>>> To save the world(and money) I issued the command "atacontrol spindown
>>>>> 1800" for all the discs in my array spinning them down after thirty
>>>>> minutes of idle spinning.
>>>>> So far so good, me very happy! However, when I access the array after
>>>>> the discs have been spun down, it spins up the discs one after the
>>>>> other...
>>>>> Mind you one AFTER the other, taking 4*9 seconds to do a "ls" command on
>>>>> my music directory.
>>>>> Content as I am with the smooth down- and upspinning of the disks, I
>>>>> would like it better if the four discs would spin up simultaneously.
>>>>> Thus my  question: "Is it possible to \"group\" discs to be spun up
>>>>> together, or to issue a custom command upon upspinning of a disc such as
>>>>> to spin up other disks?"
>>>>>         
>>>>>           
>>>> Good question but the answer is probably no - it really only depends
>>>> on how ZFS accesses the drives; if it accesses them in sequence, you
>>>> can't change it.
>>>>       
>>>>         
>>> I've been looking at writing a shell script which monitors
>>> /var/log/messages.
>>> something like:
>>>
>>> If last line in /var/log/messages is like "request while spun down.
>>> Starting."
>>>    spinup disks
>>>
>>> couple of problems though, I should probably poll the kernel messages
>>> every second or so, but if I only check the last linee, I could miss the
>>> spinup message.
>>> I could count the number of lines in /var/log/messages and keep count of
>>> the number of lines i've seen. Problem with this approach is that it's
>>> not very efficient.
>>> So I was hoping there is a way to receive this kernel message directly.
>>> I am now thinking in the lines of a program which received a signal on
>>> new kernel messages available or something similar.
>>>
>>> Any thoughts?
>>>     
>>>       
>> You could do what "tail -f" does and simply hook a kqueue to get new
>> messages from the /var/log/messages file.
>>   
>>     
> I'll try that! thanks!
>
>   
As I get quite the same issue with a 4 disk raidz pool, could you please 
tell me the result of your tries ? which command do you use to force the 
disks to spin up ?

Thanks
From ohartman at mail.zedat.fu-berlin.de  Tue Jul 21 21:04:11 2009
From: ohartman at mail.zedat.fu-berlin.de (O. Hartmann)
Date: Tue Jul 21 21:04:17 2009
Subject: HEADS-UP: Shared Library Versions bumped...
In-Reply-To: <367b2c980907200729s57eafbbfw83c8ae5a94f41ffc@mail.gmail.com>
References: <1248027417.14210.110.camel@neo.cse.buffalo.edu>	<58F0204B-ECE6-479A-AAC2-7868E71ABB43@exscape.org>
	<367b2c980907200729s57eafbbfw83c8ae5a94f41ffc@mail.gmail.com>
Message-ID: <4A6628F0.6080802@mail.zedat.fu-berlin.de>

Olivier SMEDTS wrote:
> 2009/7/19 Thomas Backman <serenity@exscape.org>:
>> On Jul 19, 2009, at 20:16, Ken Smith wrote:
>>> The problem is that as of the next time you update a machine that had
>>> been running -current you are best off reinstalling all ports or other
>>> applications you have on the machine. ?When you reboot after doing the
>>> update to the base system everything you have installed will still work
>>> because the old shared library versions will still be there. ?However
>>> anything you build on the machine after its base system gets updated
>>> would be linked against the newer base system shared libraries but any
>>> libraries that are part of ports or other applications (e.g. the Xorg
>>> libraries) would have been linked against the older library versions.
>>> You really don't want to leave things that way.
>> So, to be clear: a fresh ports tree and "portupgrade -af" after building and
>> installing r195767+ should be enough to solve any problems? (installkernel,
>> installworld, reboot, portupgrade -af)
> 
> But there won't be any problem until you do a "make delete-old-libs"
> in /usr/src/, right ?
> 
> Olivier
> 
>> Regards,
>> Thomas
>> _______________________________________________
>> freebsd-current@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>>
> 


Real fun this moment. It took appoximately 13 hours on a two socket, 8
core Dell PowerEdge 1950 III at 2,5 GHz with 16 GB RAM for 453 ports to
be recompiled.

I have another box (of many) running FreeBSD 8.0-BETA2/amd64 with 2 GB
RAM and a Athlon64 2,2GHz CPU having 800(!) ports installed. Can you
imagine how long this box will be occupied by 'portupgrade -af'? I guess
'cherry-picking' is the only solution.

FreeBSD 8.0 on AMD64 does have serious performance issues these days,
try to compile a compiler (gcc44, for instance) and watch how bumpy your
X11 or how network traffic on a 'headless' server becomes. Kernel
compilation time has been increased by approx 10 minutes on the 8 core
box with 16 GB RAM since ~ 4 months now. I know, this is a kind of off
topic for the questiojns discussed at the moment, but I guess those
problems and fun are guaranteed for those having lots of ports, FreeBSD
8 running on AMD64 ;-))

Regards,
Oliver

From sgk at troutmask.apl.washington.edu  Tue Jul 21 21:52:12 2009
From: sgk at troutmask.apl.washington.edu (Steve Kargl)
Date: Tue Jul 21 21:52:19 2009
Subject: HEADS-UP: Shared Library Versions bumped...
In-Reply-To: <4A6628F0.6080802@mail.zedat.fu-berlin.de>
References: <1248027417.14210.110.camel@neo.cse.buffalo.edu>
	<58F0204B-ECE6-479A-AAC2-7868E71ABB43@exscape.org>
	<367b2c980907200729s57eafbbfw83c8ae5a94f41ffc@mail.gmail.com>
	<4A6628F0.6080802@mail.zedat.fu-berlin.de>
Message-ID: <20090721215201.GA61999@troutmask.apl.washington.edu>

On Tue, Jul 21, 2009 at 10:45:36PM +0200, O. Hartmann wrote:
> 
> I have another box (of many) running FreeBSD 8.0-BETA2/amd64 with 2 GB
> RAM and a Athlon64 2,2GHz CPU having 800(!) ports installed. Can you
> imagine how long this box will be occupied by 'portupgrade -af'? I guess
> 'cherry-picking' is the only solution.

How many of those 800 ports are actually necessary and used?
It would be better to get generate a complete list of your
installed ports, use pkg_deinstall or pkg_delete to remove
all ports, and then selectively re-install ports that are
actually used.

> FreeBSD 8.0 on AMD64 does have serious performance issues these days,
> try to compile a compiler (gcc44, for instance) and watch how bumpy your
> X11 or how network traffic on a 'headless' server becomes. Kernel
> compilation time has been increased by approx 10 minutes on the 8 core
> box with 16 GB RAM since ~ 4 months now. I know, this is a kind of off
> topic for the questiojns discussed at the moment, but I guess those
> problems and fun are guaranteed for those having lots of ports, FreeBSD
> 8 running on AMD64 ;-))
> 

I compile gcc trunk on my 2 cpu amd64 based system almost
everyday.  I don't see the performance issue you seem to
have.  Do you use ULE?  If yes, then switch to 4BSD.

-- 
Steve
From hiyorin at gmail.com  Wed Jul 22 02:07:41 2009
From: hiyorin at gmail.com (C. C. Tang)
Date: Wed Jul 22 02:07:48 2009
Subject: 7.2-release/amd64: panic, spin lock held too long
In-Reply-To: <KN4BGI$40ABF3E58EAD1201403C9DA561E2402F@libero.it>
References: <KN4BGI$40ABF3E58EAD1201403C9DA561E2402F@libero.it>
Message-ID: <4A667469.1080805@gmail.com>

 > Could that one (on i386) be related?
 > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/134584
 >

I have no idea about it but I can tell the difference...
My machine panic randomly rather than on shutdown and I remembered that 
it failed to write core dump. It also failed to reboot automatically..

Regards,
CC
From sagara at tomahawk.com.sg  Wed Jul 22 05:39:05 2009
From: sagara at tomahawk.com.sg (Sagara Wijetunga)
Date: Wed Jul 22 05:39:12 2009
Subject: SCSI device not created upon a CF card plug in
Message-ID: <20090722022027.12059.qmail@us1.tomahawkonline.net>

Hi FreeBSD community 

The SCSI device (eg. da1s1) is not created automatically upon a CF card plug 
in on an USB multi-card reader on FreeBSD 7.2 (i386) but the SCSI device 
(eg. da1s1) is created automatically if I reboot the computer while the CF 
card is plug in. 

Here are detail:
$ camcontrol devlist
<GENERIC USB Storage-SMC 010D>     at scbus0 target 0 lun 0 (pass0,da0)
<GENERIC USB Storage-CFC 010D>     at scbus0 target 0 lun 1 (pass1,da1)
<GENERIC USB Storage-MMC 010D>     at scbus0 target 0 lun 2 (pass2,da2)
<GENERIC USB Storage-MSC 010D>     at scbus0 target 0 lun 3 (pass3,da3) 

After the CF card is plugged in:
$ ls -l /dev/ | grep da
crw-r-----  1 root    operator    0, 105 Jul 22 13:18 da0
crw-r-----  1 root    operator    0, 106 Jul 22 13:18 da1
crw-r-----  1 root    operator    0, 107 Jul 22 13:18 da2
crw-r-----  1 root    operator    0, 108 Jul 22 13:18 da3 

After reboot while the CF card is plugged in:
$ ls -l /dev/ | grep da
crw-r-----  1 root    operator    0, 105 Jul 22 13:24 da0
crw-r-----  1 root    operator    0, 106 Jul 22 13:24 da1
crw-r-----  1 root    operator    0, 110 Jul 22 13:24 da1s1
crw-r-----  1 root    operator    0, 107 Jul 22 13:24 da2
crw-r-----  1 root    operator    0, 108 Jul 22 13:24 da3 

My questions in this regards are:
1. Is this an error/bug in FreeBSD 7.2? 

2. Or, does it require some configuration tweak? 

If this is an error/bug in FreeBSD 7.2, could somebody please develop a 
patch against the FreeBSD 7.2 sources? 

Kind regards
Sagara
From freebsd-stable at dino.sk  Wed Jul 22 06:09:38 2009
From: freebsd-stable at dino.sk (Milan Obuch)
Date: Wed Jul 22 06:09:46 2009
Subject: SCSI device not created upon a CF card plug in
In-Reply-To: <20090722022027.12059.qmail@us1.tomahawkonline.net>
References: <20090722022027.12059.qmail@us1.tomahawkonline.net>
Message-ID: <200907220759.22608.freebsd-stable@dino.sk>

On Wednesday 22 July 2009 04:20:27 Sagara Wijetunga wrote:
> Hi FreeBSD community
>
> The SCSI device (eg. da1s1) is not created automatically upon a CF card
> plug in on an USB multi-card reader on FreeBSD 7.2 (i386) but the SCSI
> device (eg. da1s1) is created automatically if I reboot the computer while
> the CF card is plug in.
>
> Here are detail:
> $ camcontrol devlist
> <GENERIC USB Storage-SMC 010D>     at scbus0 target 0 lun 0 (pass0,da0)
> <GENERIC USB Storage-CFC 010D>     at scbus0 target 0 lun 1 (pass1,da1)
> <GENERIC USB Storage-MMC 010D>     at scbus0 target 0 lun 2 (pass2,da2)
> <GENERIC USB Storage-MSC 010D>     at scbus0 target 0 lun 3 (pass3,da3)
>
> After the CF card is plugged in:
> $ ls -l /dev/ | grep da
> crw-r-----  1 root    operator    0, 105 Jul 22 13:18 da0
> crw-r-----  1 root    operator    0, 106 Jul 22 13:18 da1
> crw-r-----  1 root    operator    0, 107 Jul 22 13:18 da2
> crw-r-----  1 root    operator    0, 108 Jul 22 13:18 da3
>
> After reboot while the CF card is plugged in:
> $ ls -l /dev/ | grep da
> crw-r-----  1 root    operator    0, 105 Jul 22 13:24 da0
> crw-r-----  1 root    operator    0, 106 Jul 22 13:24 da1
> crw-r-----  1 root    operator    0, 110 Jul 22 13:24 da1s1
> crw-r-----  1 root    operator    0, 107 Jul 22 13:24 da2
> crw-r-----  1 root    operator    0, 108 Jul 22 13:24 da3
>
> My questions in this regards are:
> 1. Is this an error/bug in FreeBSD 7.2?
>

This is known limitation of, I think, GEOM stack.

> 2. Or, does it require some configuration tweak?
>

After plugging in your CF card, issue

true > /dev/da1

command. After writing zero bytes (nothing gets actually written into your 
media, thus it is not changed at all) GEOM reads some data from media and 
creates desired device(s).

Regards,
Milan
From stark at mapper.nl  Wed Jul 22 07:01:36 2009
From: stark at mapper.nl (Mark Stapper)
Date: Wed Jul 22 07:01:44 2009
Subject: ZFS RAIDZ and atacontrol spindown settings
In-Reply-To: <4A65CE7F.8040906@tzim.net>
References: <4A643F5B.8080806@mapper.nl>	<h421n2$1kt$1@ger.gmane.org>	<4A656076.2060205@mapper.nl>	<9bbcef730907210137udf7f90ax21aa530ab859f8a6@mail.gmail.com>	<4A658205.5000709@mapper.nl>
	<4A65CE7F.8040906@tzim.net>
Message-ID: <4A66B92C.8000800@mapper.nl>

Arnaud Houdelette wrote:
> Mark Stapper a ?crit :
>> Ivan Voras wrote:
>>  
>>> 2009/7/21 Mark Stapper <stark@mapper.nl>:
>>>      
>>>> Ivan Voras wrote:
>>>>          
>>>>> Mark Stapper wrote:
>>>>>              
>>>>>> Good day,
>>>>>>
>>>>>> I am the proud user of a FreeBSD 7.2 AMD64 system housing,
>>>>>> amongst other
>>>>>> things, a data server.
>>>>>> My "server"(It's called "Yoshi") runs FreeBSD from a mirrored system
>>>>>> disc, and has a zfs RAIDZ array with 4 discs for bulky data.
>>>>>> As it is a home server, and I work during the day, these four
>>>>>> discs were
>>>>>> spinning happily all day long without much use for them doing so.
>>>>>> To save the world(and money) I issued the command "atacontrol
>>>>>> spindown
>>>>>> 1800" for all the discs in my array spinning them down after thirty
>>>>>> minutes of idle spinning.
>>>>>> So far so good, me very happy! However, when I access the array
>>>>>> after
>>>>>> the discs have been spun down, it spins up the discs one after the
>>>>>> other...
>>>>>> Mind you one AFTER the other, taking 4*9 seconds to do a "ls"
>>>>>> command on
>>>>>> my music directory.
>>>>>> Content as I am with the smooth down- and upspinning of the disks, I
>>>>>> would like it better if the four discs would spin up simultaneously.
>>>>>> Thus my  question: "Is it possible to \"group\" discs to be spun up
>>>>>> together, or to issue a custom command upon upspinning of a disc
>>>>>> such as
>>>>>> to spin up other disks?"
>>>>>>                   
>>>>> Good question but the answer is probably no - it really only depends
>>>>> on how ZFS accesses the drives; if it accesses them in sequence, you
>>>>> can't change it.
>>>>>               
>>>> I've been looking at writing a shell script which monitors
>>>> /var/log/messages.
>>>> something like:
>>>>
>>>> If last line in /var/log/messages is like "request while spun down.
>>>> Starting."
>>>>    spinup disks
>>>>
>>>> couple of problems though, I should probably poll the kernel messages
>>>> every second or so, but if I only check the last linee, I could
>>>> miss the
>>>> spinup message.
>>>> I could count the number of lines in /var/log/messages and keep
>>>> count of
>>>> the number of lines i've seen. Problem with this approach is that it's
>>>> not very efficient.
>>>> So I was hoping there is a way to receive this kernel message
>>>> directly.
>>>> I am now thinking in the lines of a program which received a signal on
>>>> new kernel messages available or something similar.
>>>>
>>>> Any thoughts?
>>>>           
>>> You could do what "tail -f" does and simply hook a kqueue to get new
>>> messages from the /var/log/messages file.
>>>       
>> I'll try that! thanks!
>>
>>   
> As I get quite the same issue with a 4 disk raidz pool, could you
> please tell me the result of your tries ? which command do you use to
> force the disks to spin up ?
>
> Thanks
I have been using a shell script containing:
#!/bin.sh
dd if=/dev/ad4 of=/dev/null count=1&
dd if=/dev/ad6 of=/dev/null count=1&
dd if=/dev/ad8 of=/dev/null count=1&
dd if=/dev/ad10 of=/dev/null count=1&


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 259 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090722/4896626a/signature.pgp
From sagara at tomahawk.com.sg  Wed Jul 22 07:11:01 2009
From: sagara at tomahawk.com.sg (Sagara Wijetunga)
Date: Wed Jul 22 07:11:08 2009
Subject: SCSI device not created upon a CF card plug in
In-Reply-To: <200907220759.22608.freebsd-stable@dino.sk>
References: <20090722022027.12059.qmail@us1.tomahawkonline.net>
	<200907220759.22608.freebsd-stable@dino.sk>
Message-ID: <20090722035223.13148.qmail@us1.tomahawkonline.net>

Milan Obuch writes: 

> On Wednesday 22 July 2009 04:20:27 Sagara Wijetunga wrote:
>> Hi FreeBSD community 
>>
>> The SCSI device (eg. da1s1) is not created automatically upon a CF card
>> plug in on an USB multi-card reader on FreeBSD 7.2 (i386) but the SCSI
>> device (eg. da1s1) is created automatically if I reboot the computer while
>> the CF card is plug in. 
>>
>> Here are detail:
>> $ camcontrol devlist
>> <GENERIC USB Storage-SMC 010D>     at scbus0 target 0 lun 0 (pass0,da0)
>> <GENERIC USB Storage-CFC 010D>     at scbus0 target 0 lun 1 (pass1,da1)
>> <GENERIC USB Storage-MMC 010D>     at scbus0 target 0 lun 2 (pass2,da2)
>> <GENERIC USB Storage-MSC 010D>     at scbus0 target 0 lun 3 (pass3,da3) 
>>
>> After the CF card is plugged in:
>> $ ls -l /dev/ | grep da
>> crw-r-----  1 root    operator    0, 105 Jul 22 13:18 da0
>> crw-r-----  1 root    operator    0, 106 Jul 22 13:18 da1
>> crw-r-----  1 root    operator    0, 107 Jul 22 13:18 da2
>> crw-r-----  1 root    operator    0, 108 Jul 22 13:18 da3 
>>
>> After reboot while the CF card is plugged in:
>> $ ls -l /dev/ | grep da
>> crw-r-----  1 root    operator    0, 105 Jul 22 13:24 da0
>> crw-r-----  1 root    operator    0, 106 Jul 22 13:24 da1
>> crw-r-----  1 root    operator    0, 110 Jul 22 13:24 da1s1
>> crw-r-----  1 root    operator    0, 107 Jul 22 13:24 da2
>> crw-r-----  1 root    operator    0, 108 Jul 22 13:24 da3 
>>
>> My questions in this regards are:
>> 1. Is this an error/bug in FreeBSD 7.2? 
>>
> 
> This is known limitation of, I think, GEOM stack. 
> 
>> 2. Or, does it require some configuration tweak? 
>>
> 
> After plugging in your CF card, issue 
> 
> true > /dev/da1 
> 
> command. After writing zero bytes (nothing gets actually written into your 
> media, thus it is not changed at all) GEOM reads some data from media and 
> creates desired device(s). 
> 

Hi Milan, thanks for the reply. 

Yep, your suggestion works but it simply unacceptable for end users. We are 
the makers of the Tomahawk Desktop (http://www.tomahawkcomputers.com/). 

Anybody in the FreeBSD community care to develop a patch to make it possible 
to use multi-card readers under FreeBSD? 

Best regards
Sagara
From ivoras at freebsd.org  Wed Jul 22 07:39:07 2009
From: ivoras at freebsd.org (Ivan Voras)
Date: Wed Jul 22 07:39:15 2009
Subject: SCSI device not created upon a CF card plug in
In-Reply-To: <200907220759.22608.freebsd-stable@dino.sk>
References: <20090722022027.12059.qmail@us1.tomahawkonline.net>
	<200907220759.22608.freebsd-stable@dino.sk>
Message-ID: <h46fma$k5q$1@ger.gmane.org>

Milan Obuch wrote:
> On Wednesday 22 July 2009 04:20:27 Sagara Wijetunga wrote:
>> Hi FreeBSD community
>>
>> The SCSI device (eg. da1s1) is not created automatically upon a CF card
>> plug in on an USB multi-card reader on FreeBSD 7.2 (i386) but the SCSI
>> device (eg. da1s1) is created automatically if I reboot the computer while
>> the CF card is plug in.
>>
>> Here are detail:
>> $ camcontrol devlist
>> <GENERIC USB Storage-SMC 010D>     at scbus0 target 0 lun 0 (pass0,da0)
>> <GENERIC USB Storage-CFC 010D>     at scbus0 target 0 lun 1 (pass1,da1)
>> <GENERIC USB Storage-MMC 010D>     at scbus0 target 0 lun 2 (pass2,da2)
>> <GENERIC USB Storage-MSC 010D>     at scbus0 target 0 lun 3 (pass3,da3)
>>
>> After the CF card is plugged in:
>> $ ls -l /dev/ | grep da
>> crw-r-----  1 root    operator    0, 105 Jul 22 13:18 da0
>> crw-r-----  1 root    operator    0, 106 Jul 22 13:18 da1
>> crw-r-----  1 root    operator    0, 107 Jul 22 13:18 da2
>> crw-r-----  1 root    operator    0, 108 Jul 22 13:18 da3
>>
>> After reboot while the CF card is plugged in:
>> $ ls -l /dev/ | grep da
>> crw-r-----  1 root    operator    0, 105 Jul 22 13:24 da0
>> crw-r-----  1 root    operator    0, 106 Jul 22 13:24 da1
>> crw-r-----  1 root    operator    0, 110 Jul 22 13:24 da1s1
>> crw-r-----  1 root    operator    0, 107 Jul 22 13:24 da2
>> crw-r-----  1 root    operator    0, 108 Jul 22 13:24 da3
>>
>> My questions in this regards are:
>> 1. Is this an error/bug in FreeBSD 7.2?
> 
> This is known limitation of, I think, GEOM stack.

No, it is certainly not. What would be the point?

The problem the OP is not that the CF device itself is not detected - 
the device being /dev/da1 - but that the partition on the device (da1s1) 
is not detected. It is possibly malformed.

The OP should nuke the device (overwrite with dd if=/dev/zero 
of=/dev/da1 bs=1m), re-create the partition table and see if that helps.

From tevans.uk at googlemail.com  Wed Jul 22 08:49:36 2009
From: tevans.uk at googlemail.com (Tom Evans)
Date: Wed Jul 22 08:49:42 2009
Subject: SCSI device not created upon a CF card plug in
In-Reply-To: <20090722035223.13148.qmail@us1.tomahawkonline.net>
References: <20090722022027.12059.qmail@us1.tomahawkonline.net>
	<200907220759.22608.freebsd-stable@dino.sk>
	<20090722035223.13148.qmail@us1.tomahawkonline.net>
Message-ID: <1248252570.2291.3.camel@strangepork.london.mintel.ad>

On Wed, 2009-07-22 at 11:52 +0800, Sagara Wijetunga wrote:
> Hi Milan, thanks for the reply. 
> 
> Yep, your suggestion works but it simply unacceptable for end users. We are 
> the makers of the Tomahawk Desktop (http://www.tomahawkcomputers.com/). 
> 
> Anybody in the FreeBSD community care to develop a patch to make it possible 
> to use multi-card readers under FreeBSD? 
> 
> Best regards
> Sagara

Perhaps that could be what the Tomahawk Desktop contributes back to
FreeBSD? Seems to be your itch...

Regards

Tom

From freebsd-stable at dino.sk  Wed Jul 22 09:21:22 2009
From: freebsd-stable at dino.sk (Milan Obuch)
Date: Wed Jul 22 09:21:29 2009
Subject: SCSI device not created upon a CF card plug in
In-Reply-To: <20090722035223.13148.qmail@us1.tomahawkonline.net>
References: <20090722022027.12059.qmail@us1.tomahawkonline.net>
	<200907220759.22608.freebsd-stable@dino.sk>
	<20090722035223.13148.qmail@us1.tomahawkonline.net>
Message-ID: <200907221121.10004.freebsd-stable@dino.sk>

On Wednesday 22 July 2009 08:11:23 Sagara Wijetunga wrote:
> Milan Obuch writes:
> > On Wednesday 22 July 2009 04:20:27 Sagara Wijetunga wrote:
> >> Hi FreeBSD community
> >>
> >> The SCSI device (eg. da1s1) is not created automatically upon a CF card
> >> plug in on an USB multi-card reader on FreeBSD 7.2 (i386) but the SCSI
> >> device (eg. da1s1) is created automatically if I reboot the computer
> >> while the CF card is plug in.
> >>

Which kind of reader is it?Is it something built-in or standalone connected 
via USB cable to (externally accessible) USB port on your computer? If the 
latter, could you try the difference between plugging first reader into USB 
port, than CF into reader and plugging first CF into reader and than connect 
reader into USB port?

Regards,
Milan
From freebsd-stable at dino.sk  Wed Jul 22 09:32:48 2009
From: freebsd-stable at dino.sk (Milan Obuch)
Date: Wed Jul 22 09:32:55 2009
Subject: SCSI device not created upon a CF card plug in
In-Reply-To: <h46fma$k5q$1@ger.gmane.org>
References: <20090722022027.12059.qmail@us1.tomahawkonline.net>
	<200907220759.22608.freebsd-stable@dino.sk>
	<h46fma$k5q$1@ger.gmane.org>
Message-ID: <200907221132.35462.freebsd-stable@dino.sk>

On Wednesday 22 July 2009 09:38:50 Ivan Voras wrote:

[ snip ]

> >> After the CF card is plugged in:
> >> $ ls -l /dev/ | grep da
> >> crw-r-----  1 root    operator    0, 105 Jul 22 13:18 da0
> >> crw-r-----  1 root    operator    0, 106 Jul 22 13:18 da1
> >> crw-r-----  1 root    operator    0, 107 Jul 22 13:18 da2
> >> crw-r-----  1 root    operator    0, 108 Jul 22 13:18 da3
> >>
> >> After reboot while the CF card is plugged in:
> >> $ ls -l /dev/ | grep da
> >> crw-r-----  1 root    operator    0, 105 Jul 22 13:24 da0
> >> crw-r-----  1 root    operator    0, 106 Jul 22 13:24 da1
> >> crw-r-----  1 root    operator    0, 110 Jul 22 13:24 da1s1
> >> crw-r-----  1 root    operator    0, 107 Jul 22 13:24 da2
> >> crw-r-----  1 root    operator    0, 108 Jul 22 13:24 da3
> >>
> >> My questions in this regards are:
> >> 1. Is this an error/bug in FreeBSD 7.2?
> >
> > This is known limitation of, I think, GEOM stack.
>
> No, it is certainly not. What would be the point?
>

Please re-iterate :)

When GEOM is signalled about new device, it tries to understand data 
structures - MBR, partition table, etc. The key is 'when signalled'. So this 
is not limitation of GEOM per se, just missing signalling of new device/data 
media arrival.

> The problem the OP is not that the CF device itself is not detected -
> the device being /dev/da1 - but that the partition on the device (da1s1)
> is not detected. It is possibly malformed.
>

Not true. While not totally clear from original posting, problem is most 
probably no notion of medium (CF) present in reader, similar to medium (CD) 
in CD-ROM drive.

> The OP should nuke the device (overwrite with dd if=/dev/zero
> of=/dev/da1 bs=1m), re-create the partition table and see if that helps.
>

Again, maybe not clear from original posting, most probably this is not 
necessary. To me it looks like commonly used CF with msdosfs. If we are able 
to tell 'new media inserted into reader' event, maybe to devd, we could hook 
simple script fro this event. Problem is, currently, devfs tells 'new device 
umass0 detected', but this does not correspond clearly with 'new device daX 
detected', and, in case of multireader, you can't tell which one (CF, SD, 
other card) is actually inserted.

At least for now, I have no simple idea how to solve this trouble.

Regards,
Milan
From ivoras at freebsd.org  Wed Jul 22 10:10:48 2009
From: ivoras at freebsd.org (Ivan Voras)
Date: Wed Jul 22 10:10:55 2009
Subject: SCSI device not created upon a CF card plug in
In-Reply-To: <200907221132.35462.freebsd-stable@dino.sk>
References: <20090722022027.12059.qmail@us1.tomahawkonline.net>	<200907220759.22608.freebsd-stable@dino.sk>	<h46fma$k5q$1@ger.gmane.org>
	<200907221132.35462.freebsd-stable@dino.sk>
Message-ID: <h46oih$eh5$1@ger.gmane.org>

Milan Obuch wrote:
> On Wednesday 22 July 2009 09:38:50 Ivan Voras wrote:
> 
> [ snip ]
> 
>>>> After the CF card is plugged in:
>>>> $ ls -l /dev/ | grep da
>>>> crw-r-----  1 root    operator    0, 105 Jul 22 13:18 da0
>>>> crw-r-----  1 root    operator    0, 106 Jul 22 13:18 da1
>>>> crw-r-----  1 root    operator    0, 107 Jul 22 13:18 da2
>>>> crw-r-----  1 root    operator    0, 108 Jul 22 13:18 da3
>>>>
>>>> After reboot while the CF card is plugged in:
>>>> $ ls -l /dev/ | grep da
>>>> crw-r-----  1 root    operator    0, 105 Jul 22 13:24 da0
>>>> crw-r-----  1 root    operator    0, 106 Jul 22 13:24 da1
>>>> crw-r-----  1 root    operator    0, 110 Jul 22 13:24 da1s1
>>>> crw-r-----  1 root    operator    0, 107 Jul 22 13:24 da2
>>>> crw-r-----  1 root    operator    0, 108 Jul 22 13:24 da3
>>>>
>>>> My questions in this regards are:
>>>> 1. Is this an error/bug in FreeBSD 7.2?
>>> This is known limitation of, I think, GEOM stack.
>> No, it is certainly not. What would be the point?
>>
> 
> Please re-iterate :)
> 
> When GEOM is signalled about new device, it tries to understand data 
> structures - MBR, partition table, etc. The key is 'when signalled'. So this 
> is not limitation of GEOM per se, just missing signalling of new device/data 
> media arrival.

Ah yes, if the reader always signals the device present but doesn't 
signal media insertion, it would lead to the described problem.

I agree there isn't a good solution apart from polling.

From sagara at tomahawk.com.sg  Wed Jul 22 10:23:49 2009
From: sagara at tomahawk.com.sg (Sagara Wijetunga)
Date: Wed Jul 22 10:23:56 2009
Subject: SCSI device not created upon a CF card plug in
In-Reply-To: <200907221121.10004.freebsd-stable@dino.sk>
References: <20090722022027.12059.qmail@us1.tomahawkonline.net>
	<200907220759.22608.freebsd-stable@dino.sk>
	<20090722035223.13148.qmail@us1.tomahawkonline.net>
	<200907221121.10004.freebsd-stable@dino.sk>
Message-ID: <20090722070510.15945.qmail@us1.tomahawkonline.net>

Milan Obuch writes: 

> On Wednesday 22 July 2009 08:11:23 Sagara Wijetunga wrote:
>> Milan Obuch writes:
>> > On Wednesday 22 July 2009 04:20:27 Sagara Wijetunga wrote:
>> >> Hi FreeBSD community
>> >>
>> >> The SCSI device (eg. da1s1) is not created automatically upon a CF card
>> >> plug in on an USB multi-card reader on FreeBSD 7.2 (i386) but the SCSI
>> >> device (eg. da1s1) is created automatically if I reboot the computer
>> >> while the CF card is plug in.
>> >>
> 
> Which kind of reader is it?Is it something built-in or standalone connected 
> via USB cable to (externally accessible) USB port on your computer? If the 
> latter, could you try the difference between plugging first reader into USB 
> port, than CF into reader and plugging first CF into reader and than connect 
> reader into USB port? 
> 

1. This is an internal multi-card reader. 

2. The CF card is not malformed. I have tried with a brand new CF card, 
FreeBSD does not create a daXs1 slice device node even for the new CF card. 

3. Tried both cards under Linux 2.6, they work fine. No issue at all. The 
moment the card is plug in, Linux creates the sdc1 device node, the moment 
the CF card is taken out of the reader, the Linux removes the sdc1 node. 

4. Both cards factory formatted to msdos file system. 

Regards
Sagara
From sagara at tomahawk.com.sg  Wed Jul 22 10:33:30 2009
From: sagara at tomahawk.com.sg (Sagara Wijetunga)
Date: Wed Jul 22 10:33:38 2009
Subject: SCSI device not created upon a CF card plug in
In-Reply-To: <h46oih$eh5$1@ger.gmane.org>
References: <20090722022027.12059.qmail@us1.tomahawkonline.net>
	<200907220759.22608.freebsd-stable@dino.sk>
	<h46fma$k5q$1@ger.gmane.org>
	<200907221132.35462.freebsd-stable@dino.sk>
	<h46oih$eh5$1@ger.gmane.org>
Message-ID: <20090722071452.16078.qmail@us1.tomahawkonline.net>

Ivan Voras writes: 

> Milan Obuch wrote:
>> On Wednesday 22 July 2009 09:38:50 Ivan Voras wrote: 
>> 
>> [ snip ] 
>> 
>>>>> After the CF card is plugged in:
>>>>> $ ls -l /dev/ | grep da
>>>>> crw-r-----  1 root    operator    0, 105 Jul 22 13:18 da0
>>>>> crw-r-----  1 root    operator    0, 106 Jul 22 13:18 da1
>>>>> crw-r-----  1 root    operator    0, 107 Jul 22 13:18 da2
>>>>> crw-r-----  1 root    operator    0, 108 Jul 22 13:18 da3 
>>>>> 
>>>>> After reboot while the CF card is plugged in:
>>>>> $ ls -l /dev/ | grep da
>>>>> crw-r-----  1 root    operator    0, 105 Jul 22 13:24 da0
>>>>> crw-r-----  1 root    operator    0, 106 Jul 22 13:24 da1
>>>>> crw-r-----  1 root    operator    0, 110 Jul 22 13:24 da1s1
>>>>> crw-r-----  1 root    operator    0, 107 Jul 22 13:24 da2
>>>>> crw-r-----  1 root    operator    0, 108 Jul 22 13:24 da3 
>>>>> 
>>>>> My questions in this regards are:
>>>>> 1. Is this an error/bug in FreeBSD 7.2?
>>>> This is known limitation of, I think, GEOM stack.
>>> No, it is certainly not. What would be the point? 
>>> 
>> 
>> Please re-iterate :) 
>> 
>> When GEOM is signalled about new device, it tries to understand data 
>> structures - MBR, partition table, etc. The key is 'when signalled'. So 
>> this is not limitation of GEOM per se, just missing signalling of new 
>> device/data media arrival.
> 
> Ah yes, if the reader always signals the device present but doesn't signal 
> media insertion, it would lead to the described problem. 
> 
> I agree there isn't a good solution apart from polling. 
> 

I have earlier posted my tests with Linux. All tests were done with same CF 
cards and the very same multi-card reader on the same computer. They work on 
Linux. That is, nothing wrong with the multi-card reader, it does it's job 
of signaling well. 

Regards
Sagara
From petefrench at ticketswitch.com  Wed Jul 22 10:38:44 2009
From: petefrench at ticketswitch.com (Pete French)
Date: Wed Jul 22 10:38:50 2009
Subject: SCSI device not created upon a CF card plug in
In-Reply-To: <20090722071452.16078.qmail@us1.tomahawkonline.net>
Message-ID: <E1MTZDd-00020n-Te@dilbert.ticketswitch.com>

> I have earlier posted my tests with Linux. All tests were done with same CF 
> cards and the very same multi-card reader on the same computer. They work on 
> Linux. That is, nothing wrong with the multi-card reader, it does it's job 
> of signaling well. 

What makes you sure that Linux is using signalling ? It might be that
they recognise the card reader does not signal and simply poll it every
few seconds.

Is it possible for you to use a non USB based card reader and see how
that performs ?

-pete.
From sagara at tomahawk.com.sg  Wed Jul 22 10:58:53 2009
From: sagara at tomahawk.com.sg (Sagara Wijetunga)
Date: Wed Jul 22 10:59:00 2009
Subject: SCSI device not created upon a CF card plug in
In-Reply-To: <E1MTZDd-00020n-Te@dilbert.ticketswitch.com>
References: <E1MTZDd-00020n-Te@dilbert.ticketswitch.com>
Message-ID: <20090722074014.16439.qmail@us1.tomahawkonline.net>

Pete French writes: 

>> I have earlier posted my tests with Linux. All tests were done with same CF 
>> cards and the very same multi-card reader on the same computer. They work on 
>> Linux. That is, nothing wrong with the multi-card reader, it does it's job 
>> of signaling well. 
> 
> What makes you sure that Linux is using signalling ? It might be that
> they recognise the card reader does not signal and simply poll it every
> few seconds. 
> 
On Linux it does not take even a second, its instant. 


> Is it possible for you to use a non USB based card reader and see how
> that performs ? 
> 
Almost all multi-card readers targeted for consumers are USB type. I'm not 
sure whether there are non-USB based multi-card readers available. 

Do USB multi-card readers work on FreeBSD in first place? Taking few seconds 
to create necessary device is alright, but asking people to reboot the 
computer after plug in a card is unacceptable. 

Regards
Sagara
From pmc at citylink.dinoex.sub.org  Wed Jul 22 11:13:44 2009
From: pmc at citylink.dinoex.sub.org (Peter Much)
Date: Wed Jul 22 11:13:53 2009
Subject: 7.2-STABLE ZFS: mv: set flags (was: 00000000): Invalid argument
Message-ID: <Kn6GqG.1I72@citylink.dinoex.sub.org>


Hi ZFS gurus!

After upgrading my system from 7.2-PRERELEASE to 7.2-STABLE (as
of last week), and accordingly upgrading my Pools from Version
6 to Version 13, I get this error when moving arbitrary files
between different ZFS filesystems.

While this seems not to do much harm (mv returns with 0), it is
annoying. 
Does anybody know an explanation or fix, or is there some work in
progress?

rgds,
PMc
From jhb at freebsd.org  Wed Jul 22 13:21:06 2009
From: jhb at freebsd.org (John Baldwin)
Date: Wed Jul 22 13:21:24 2009
Subject: HEADS-UP: Shared Library Versions bumped...
In-Reply-To: <20090721215201.GA61999@troutmask.apl.washington.edu>
References: <1248027417.14210.110.camel@neo.cse.buffalo.edu>
	<4A6628F0.6080802@mail.zedat.fu-berlin.de>
	<20090721215201.GA61999@troutmask.apl.washington.edu>
Message-ID: <200907220814.38246.jhb@freebsd.org>

On Tuesday 21 July 2009 5:52:01 pm Steve Kargl wrote:
> On Tue, Jul 21, 2009 at 10:45:36PM +0200, O. Hartmann wrote:
> > 
> > I have another box (of many) running FreeBSD 8.0-BETA2/amd64 with 2 GB
> > RAM and a Athlon64 2,2GHz CPU having 800(!) ports installed. Can you
> > imagine how long this box will be occupied by 'portupgrade -af'? I guess
> > 'cherry-picking' is the only solution.
> 
> How many of those 800 ports are actually necessary and used?
> It would be better to get generate a complete list of your
> installed ports, use pkg_deinstall or pkg_delete to remove
> all ports, and then selectively re-install ports that are
> actually used.

Xorg takes up ~200 ports alone (not including dependencies like perl, etc.) 
since the Xorg decided release engineering was too hard.  Throw in things 
like KDE, OOo, Firefox, etc. for a desktop and you can get a fairly high 
package count. :-/

-- 
John Baldwin
From eugen at kuzbass.ru  Wed Jul 22 14:20:38 2009
From: eugen at kuzbass.ru (Eugene Grosbein)
Date: Wed Jul 22 14:20:46 2009
Subject: SCSI device not created upon a CF card plug in
In-Reply-To: <20090722022027.12059.qmail@us1.tomahawkonline.net>
References: <20090722022027.12059.qmail@us1.tomahawkonline.net>
Message-ID: <20090722142033.GA13316@svzserv.kemerovo.su>

On Wed, Jul 22, 2009 at 10:20:27AM +0800, Sagara Wijetunga wrote:

> My questions in this regards are:
> 1. Is this an error/bug in FreeBSD 7.2? 

This is regression from pre-5.x days. In 4.x and earlier,
you can have static device nodes and access them just fine.

> 2. Or, does it require some configuration tweak? 

As a workaround, you should drop cardreader.conf into /usr/local/etc/devd/
(create directory if it does not exist) with contents like:

attach 1000 {
        device-name "umass[0-9]+";
        action "/usr/local/libexec/umass/attach-umass $device-name";
};

Script /usr/local/libexec/umass/attach-umass is invoked
when umassX appears:

#!/bin/sh

PATH=/bin:/sbin:/usr/bin:/usr/sbin
DEV=/dev
p=`dirname $0`

[ -z "$1" ] && exit 1
u="$1"

# wait until dust settles
i=1;
while [ $i -le 10 ]	
do
  sleep 1
  device=`$p/umass2da $u`
  if [ $? = 0 ]; then
    : > $DEV/${device}
    break
  fi
  i=$(($i+1))
done

This script calls /usr/local/libexec/umass/umass2da helper
to translate umassX to daY (in hope this translation is possible):

#!/bin/sh
PATH=/sbin:/usr/bin

camcontrol devlist -v | awk -v u=$1 '\
BEGIN { s = ""; e = 1; }
$3 ~ /umass-sim[0-9]+/ { s = $3; sub("-sim","",s); }
/[,(]da[0-9]+.*\)$/ {
  if(s == u) {
    match($NF, /da[0-9]+/);
    print substr($NF, RSTART, RLENGTH);
    e=0; exit 0;
  }
}
END { exit e; }'

Eugene Grosbein
From ABekaAcademy at promo.abeka.com  Wed Jul 22 15:45:18 2009
From: ABekaAcademy at promo.abeka.com (A Beka Academy)
Date: Wed Jul 22 15:45:25 2009
Subject: ABA K4 Video Program $350 or Save $100 on New K5-12 Enrollments!
Message-ID: <20090722085925.6D47986129664C2E@promo.abeka.com>

K4 Video Program (www.abekaacademy.org/k4offer.html)

A Beka Academy K4 Video Program contains over 400 instructional hours 
using age-appropriate, eye-catching visuals.

Children gain knowledge in Phonics, Numbers, Poetry, Reading, Readiness 
Skills, Drama, Writing, Music, Language Development, Bible, and Art.

Student materials, parent manual, support materials, shipping, and taxes 
are all included! The $350 special introductory price...
     - is available with Internet Video Streaming or DVD format
       ($75 fully-refundable retainer fee for DVD.)
     - includes all enrollments-Internet at www.abekaacademy.org/enroll, 
       Home School Materials Displays at abeka.com/MaterialsDisplay, 
       phone (1-800-874-3592), or mail.
     - includes shipping and sales tax for continental U.S.A.
     - is available to International customers at the same price 
       (additional retainer fee, shipping charges, and custom fees may 
       apply).
     - may not be combined with any other Discount or Savings and does not 
       include Payment Plan.

New ABA K5-12 Enrollments (www.abekaacademy.org/NewEnrollmentOffer.html)

Save $100 per student* when you enroll in A Beka Academy video at a Home 
School Materials Display at www.abeka.com/MaterialsDisplay or enroll 
online at www.abekaacademy.org/enroll and save $50 per student*.


*Offer limited to new video students and former video students not 
enrolled after 3/28/08.  Full-grade enrollments only. This promotional 
offer may not be combined with any other discount or rebates.
From vova at fbsd.ru  Wed Jul 22 16:07:13 2009
From: vova at fbsd.ru (Vladimir Grebenschikov)
Date: Wed Jul 22 16:07:20 2009
Subject: HEADS-UP: Shared Library Versions bumped...
In-Reply-To: <20090721215201.GA61999@troutmask.apl.washington.edu>
References: <1248027417.14210.110.camel@neo.cse.buffalo.edu>
	<58F0204B-ECE6-479A-AAC2-7868E71ABB43@exscape.org>
	<367b2c980907200729s57eafbbfw83c8ae5a94f41ffc@mail.gmail.com>
	<4A6628F0.6080802@mail.zedat.fu-berlin.de>
	<20090721215201.GA61999@troutmask.apl.washington.edu>
Message-ID: <1248277420.8644.70.camel@localhost>

? ??, 21/07/2009 ? 14:52 -0700, Steve Kargl ?????:
> On Tue, Jul 21, 2009 at 10:45:36PM +0200, O. Hartmann wrote:
> > 
> > I have another box (of many) running FreeBSD 8.0-BETA2/amd64 with 2 GB
> > RAM and a Athlon64 2,2GHz CPU having 800(!) ports installed. Can you
> > imagine how long this box will be occupied by 'portupgrade -af'? I guess
> > 'cherry-picking' is the only solution.
> 
> How many of those 800 ports are actually necessary and used?
> It would be better to get generate a complete list of your
> installed ports, use pkg_deinstall or pkg_delete to remove
> all ports, and then selectively re-install ports that are
> actually used.

I've found that much faster and cleaner way is to just remove
whole /usr/local (preserving /usr/local/etc), and /var/db/pkg

and then just install required ports, such process goes much faster.
Also it removes all unused ports.

As for ports number, it is really crazy, I have 1435 ports for notebook
used as usual desktop and as multi-purpose development machine.

PS.
I am on i386, so can't say anything about amd64 specific performance
problems.

-- 
Vladimir B. Grebenschikov
vova@fbsd.ru
From attilio at freebsd.org  Wed Jul 22 16:30:49 2009
From: attilio at freebsd.org (Attilio Rao)
Date: Wed Jul 22 16:30:56 2009
Subject: 7.2-release/amd64: panic, spin lock held too long
In-Reply-To: <4A667469.1080805@gmail.com>
References: <KN4BGI$40ABF3E58EAD1201403C9DA561E2402F@libero.it>
	<4A667469.1080805@gmail.com>
Message-ID: <3bbf2fe10907220930y27b5da04sd0a71d57b6a9d191@mail.gmail.com>

2009/7/22 C. C. Tang <hiyorin@gmail.com>:
>> Could that one (on i386) be related?
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/134584
>>
>
> I have no idea about it but I can tell the difference...
> My machine panic randomly rather than on shutdown and I remembered that it
> failed to write core dump. It also failed to reboot automatically..

Is your problem on -CURRENT and amd64?
At some point there has been a problem with PAT support (and
tlb_shootdowns() could lead to a livelock hanging forever, leading to
such a bug) but I expect it is fixed now.
Can you try with a fresh new -CURRENT if any?

Thanks,
Attilio



-- 
Peace can only be achieved by understanding - A. Einstein
From pprocacci at datapipe.net  Wed Jul 22 19:05:52 2009
From: pprocacci at datapipe.net (Paul A. Procacci)
Date: Wed Jul 22 19:05:59 2009
Subject: ue0 dhclient FBSD8-BETA2
Message-ID: <4A676307.8090503@datapipe.net>

Gents,

Since the name changed for my cdce device, booting up the OS fails to 
obtain an address via dhcp on this interface.  dhclient works normally 
after the machine is booted and I provide the command on the command line.

I've got the following in my rc.conf which I would have thought to be 
enough, but it doesn't matter as dhclient never gets run,

ifconfig_ue0="DHCP"

This isn't a deal breaker by any means, but would like to inquire about 
about the proper steps for getting dhclient to physically work on the 
ue0 interface.  Docs on this subject (usb ethernet changes) at this 
point are scarce and I'm not sure what specifically needs to be done.

Thanks,
Paul
From brooks at freebsd.org  Wed Jul 22 19:28:43 2009
From: brooks at freebsd.org (Brooks Davis)
Date: Wed Jul 22 19:28:50 2009
Subject: ue0 dhclient FBSD8-BETA2
In-Reply-To: <4A676307.8090503@datapipe.net>
References: <4A676307.8090503@datapipe.net>
Message-ID: <20090722192850.GB94204@lor.one-eyed-alien.net>

On Wed, Jul 22, 2009 at 02:05:43PM -0500, Paul A. Procacci wrote:
> Gents,
> 
> Since the name changed for my cdce device, booting up the OS fails to 
> obtain an address via dhcp on this interface.  dhclient works normally 
> after the machine is booted and I provide the command on the command line.
> 
> I've got the following in my rc.conf which I would have thought to be 
> enough, but it doesn't matter as dhclient never gets run,
> 
> ifconfig_ue0="DHCP"
> 
> This isn't a deal breaker by any means, but would like to inquire about 
> about the proper steps for getting dhclient to physically work on the ue0 
> interface.  Docs on this subject (usb ethernet changes) at this point are 
> scarce and I'm not sure what specifically needs to be done.

This generally means that ue0 never reports a link up event which means
dhclient never gets run.  If so, the driver is broken, but you may be
able to work around it by changing DHCP to SYNCDHCP.  In that case
it may work if the cable is plugged in when the device it attached.

-- Brooks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090722/5bca2eb4/attachment.pgp
From pprocacci at datapipe.net  Wed Jul 22 20:06:31 2009
From: pprocacci at datapipe.net (Paul A. Procacci)
Date: Wed Jul 22 20:06:38 2009
Subject: ue0 dhclient FBSD8-BETA2
In-Reply-To: <20090722192850.GB94204@lor.one-eyed-alien.net>
References: <4A676307.8090503@datapipe.net>
	<20090722192850.GB94204@lor.one-eyed-alien.net>
Message-ID: <4A677148.6070506@datapipe.net>

Brooks,


I appreciate the quick follow up.  You were right, and this now work 
perfectly.  Thank you for taking the time to respond to my question.

Thanks,
Paul

Brooks Davis wrote:
> On Wed, Jul 22, 2009 at 02:05:43PM -0500, Paul A. Procacci wrote:
>   
>> Gents,
>>
>> Since the name changed for my cdce device, booting up the OS fails to 
>> obtain an address via dhcp on this interface.  dhclient works normally 
>> after the machine is booted and I provide the command on the command line.
>>
>> I've got the following in my rc.conf which I would have thought to be 
>> enough, but it doesn't matter as dhclient never gets run,
>>
>> ifconfig_ue0="DHCP"
>>
>> This isn't a deal breaker by any means, but would like to inquire about 
>> about the proper steps for getting dhclient to physically work on the ue0 
>> interface.  Docs on this subject (usb ethernet changes) at this point are 
>> scarce and I'm not sure what specifically needs to be done.
>>     
>
> This generally means that ue0 never reports a link up event which means
> dhclient never gets run.  If so, the driver is broken, but you may be
> able to work around it by changing DHCP to SYNCDHCP.  In that case
> it may work if the cable is plugged in when the device it attached.
>
> -- Brooks
>   

From das at FreeBSD.ORG  Wed Jul 22 20:07:04 2009
From: das at FreeBSD.ORG (David Schultz)
Date: Wed Jul 22 20:07:11 2009
Subject: HEADS-UP: Shared Library Versions bumped...
In-Reply-To: <1248277420.8644.70.camel@localhost>
References: <1248027417.14210.110.camel@neo.cse.buffalo.edu>
	<58F0204B-ECE6-479A-AAC2-7868E71ABB43@exscape.org>
	<367b2c980907200729s57eafbbfw83c8ae5a94f41ffc@mail.gmail.com>
	<4A6628F0.6080802@mail.zedat.fu-berlin.de>
	<20090721215201.GA61999@troutmask.apl.washington.edu>
	<1248277420.8644.70.camel@localhost>
Message-ID: <20090722193033.GA83848@zim.MIT.EDU>

On Wed, Jul 22, 2009, Vladimir Grebenschikov wrote:
> ? ??, 21/07/2009 ? 14:52 -0700, Steve Kargl ?????:
> > On Tue, Jul 21, 2009 at 10:45:36PM +0200, O. Hartmann wrote:
> > > 
> > > I have another box (of many) running FreeBSD 8.0-BETA2/amd64 with 2 GB
> > > RAM and a Athlon64 2,2GHz CPU having 800(!) ports installed. Can you
> > > imagine how long this box will be occupied by 'portupgrade -af'? I guess
> > > 'cherry-picking' is the only solution.
> > 
> > How many of those 800 ports are actually necessary and used?
> > It would be better to get generate a complete list of your
> > installed ports, use pkg_deinstall or pkg_delete to remove
> > all ports, and then selectively re-install ports that are
> > actually used.
> 
> I've found that much faster and cleaner way is to just remove
> whole /usr/local (preserving /usr/local/etc), and /var/db/pkg
> 
> and then just install required ports, such process goes much faster.
> Also it removes all unused ports.

I do the same thing.  I wish the ports system kept track of which
ports were installed explicitly by me, and which were only
dependencies.  Then it would be possible to garbage collect ports
that are no longer needed.
From gaijin.k at gmail.com  Wed Jul 22 20:15:20 2009
From: gaijin.k at gmail.com (Alexandre "Sunny" Kovalenko)
Date: Wed Jul 22 20:15:28 2009
Subject: HEADS-UP: Shared Library Versions bumped...
In-Reply-To: <20090722193033.GA83848@zim.MIT.EDU>
References: <1248027417.14210.110.camel@neo.cse.buffalo.edu>
	<58F0204B-ECE6-479A-AAC2-7868E71ABB43@exscape.org>
	<367b2c980907200729s57eafbbfw83c8ae5a94f41ffc@mail.gmail.com>
	<4A6628F0.6080802@mail.zedat.fu-berlin.de>
	<20090721215201.GA61999@troutmask.apl.washington.edu>
	<1248277420.8644.70.camel@localhost>
	<20090722193033.GA83848@zim.MIT.EDU>
Message-ID: <1248292364.1479.16.camel@RabbitsDen>

On Wed, 2009-07-22 at 15:30 -0400, David Schultz wrote:
> On Wed, Jul 22, 2009, Vladimir Grebenschikov wrote:
> > ? ??, 21/07/2009 ? 14:52 -0700, Steve Kargl ?????:
> > > On Tue, Jul 21, 2009 at 10:45:36PM +0200, O. Hartmann wrote:
> > > > 
> > > > I have another box (of many) running FreeBSD 8.0-BETA2/amd64 with 2 GB
> > > > RAM and a Athlon64 2,2GHz CPU having 800(!) ports installed. Can you
> > > > imagine how long this box will be occupied by 'portupgrade -af'? I guess
> > > > 'cherry-picking' is the only solution.
> > > 
> > > How many of those 800 ports are actually necessary and used?
> > > It would be better to get generate a complete list of your
> > > installed ports, use pkg_deinstall or pkg_delete to remove
> > > all ports, and then selectively re-install ports that are
> > > actually used.
> > 
> > I've found that much faster and cleaner way is to just remove
> > whole /usr/local (preserving /usr/local/etc), and /var/db/pkg
> > 
> > and then just install required ports, such process goes much faster.
> > Also it removes all unused ports.
> 
> I do the same thing.  I wish the ports system kept track of which
> ports were installed explicitly by me, and which were only
> dependencies.  
ports-mgmt/pkg_cutleaves does not quite do that, but IMHO is pretty
close. I does not detect build-time dependencies, though.

> Then it would be possible to garbage collect ports
> that are no longer needed.
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

-- 
Alexandre Kovalenko (????????? ?????????)


From grarpamp at gmail.com  Wed Jul 22 20:20:07 2009
From: grarpamp at gmail.com (grarpamp)
Date: Wed Jul 22 20:20:14 2009
Subject: MAKE_DVD=1 make release
Message-ID: <d2e731a10907221320p52b92e38xec92114ea997953e@mail.gmail.com>

I'm not seeing a way to make the dvd image with:

# $FreeBSD: src/release/Makefile,v 1.924.2.9 2009/04/15 03:42:59 kensmith Exp $

Am I missing the proper way to do this?
Or can someone commit 'MAKE_DVD=' into 'MAKE_DVD+=' on lines 195 and 225?
Or commit a more suitable update to src/release/Makefile?
Thanks.
From nakaji at jp.freebsd.org  Wed Jul 22 23:23:57 2009
From: nakaji at jp.freebsd.org (NAKAJI Hiroyuki)
Date: Wed Jul 22 23:24:03 2009
Subject: 7.2-release/amd64: panic, spin lock held too long
In-Reply-To: <4A667469.1080805@gmail.com> (C. C. Tang's message of "Wed, 22
	Jul 2009 10:07:37 +0800")
References: <KN4BGI$40ABF3E58EAD1201403C9DA561E2402F@libero.it>
	<4A667469.1080805@gmail.com>
Message-ID: <864ot4xpxl.fsf@ra333.heimat.gr.jp>

>>>>> In <4A667469.1080805@gmail.com> 
>>>>>	"C. C. Tang" <hiyorin@gmail.com> wrote:
> > Could that one (on i386) be related?
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/134584
> >

> I have no idea about it but I can tell the difference...
> My machine panic randomly rather than on shutdown and I remembered
> that it failed to write core dump. It also failed to reboot
> automatically..

I also have trouble like yours.
http://lists.freebsd.org/pipermail/freebsd-stable/2009-June/050526.html

I've heard from Attilio Rao that he had found the problem and is working
on it.

You can see Attilio's guide to collect debug informations:
http://lists.freebsd.org/pipermail/freebsd-stable/2009-June/050528.html
-- 
NAKAJI Hiroyuki
From tzim at tzim.net  Wed Jul 22 23:49:23 2009
From: tzim at tzim.net (Arnaud Houdelette)
Date: Wed Jul 22 23:49:31 2009
Subject: ZFS RAIDZ and atacontrol spindown settings
In-Reply-To: <4A66B92C.8000800@mapper.nl>
References: <4A643F5B.8080806@mapper.nl>	<h421n2$1kt$1@ger.gmane.org>	<4A656076.2060205@mapper.nl>	<9bbcef730907210137udf7f90ax21aa530ab859f8a6@mail.gmail.com>	<4A658205.5000709@mapper.nl>
	<4A65CE7F.8040906@tzim.net> <4A66B92C.8000800@mapper.nl>
Message-ID: <4A67A582.8040702@tzim.net>

Mark Stapper wrote:
> Arnaud Houdelette wrote:
>   
>> Mark Stapper a ?crit :
>>     
>>> Ivan Voras wrote:
>>>  
>>>       
>>>> 2009/7/21 Mark Stapper <stark@mapper.nl>:
>>>>      
>>>>         
>>>>> Ivan Voras wrote:
>>>>>          
>>>>>           
>>>>>> Mark Stapper wrote:
>>>>>>              
>>>>>>             
>>>>>>> Good day,
>>>>>>>
>>>>>>> I am the proud user of a FreeBSD 7.2 AMD64 system housing,
>>>>>>> amongst other
>>>>>>> things, a data server.
>>>>>>> My "server"(It's called "Yoshi") runs FreeBSD from a mirrored system
>>>>>>> disc, and has a zfs RAIDZ array with 4 discs for bulky data.
>>>>>>> As it is a home server, and I work during the day, these four
>>>>>>> discs were
>>>>>>> spinning happily all day long without much use for them doing so.
>>>>>>> To save the world(and money) I issued the command "atacontrol
>>>>>>> spindown
>>>>>>> 1800" for all the discs in my array spinning them down after thirty
>>>>>>> minutes of idle spinning.
>>>>>>> So far so good, me very happy! However, when I access the array
>>>>>>> after
>>>>>>> the discs have been spun down, it spins up the discs one after the
>>>>>>> other...
>>>>>>> Mind you one AFTER the other, taking 4*9 seconds to do a "ls"
>>>>>>> command on
>>>>>>> my music directory.
>>>>>>> Content as I am with the smooth down- and upspinning of the disks, I
>>>>>>> would like it better if the four discs would spin up simultaneously.
>>>>>>> Thus my  question: "Is it possible to \"group\" discs to be spun up
>>>>>>> together, or to issue a custom command upon upspinning of a disc
>>>>>>> such as
>>>>>>> to spin up other disks?"
>>>>>>>                   
>>>>>>>               
>>>>>> Good question but the answer is probably no - it really only depends
>>>>>> on how ZFS accesses the drives; if it accesses them in sequence, you
>>>>>> can't change it.
>>>>>>               
>>>>>>             
>>>>> I've been looking at writing a shell script which monitors
>>>>> /var/log/messages.
>>>>> something like:
>>>>>
>>>>> If last line in /var/log/messages is like "request while spun down.
>>>>> Starting."
>>>>>    spinup disks
>>>>>
>>>>> couple of problems though, I should probably poll the kernel messages
>>>>> every second or so, but if I only check the last linee, I could
>>>>> miss the
>>>>> spinup message.
>>>>> I could count the number of lines in /var/log/messages and keep
>>>>> count of
>>>>> the number of lines i've seen. Problem with this approach is that it's
>>>>> not very efficient.
>>>>> So I was hoping there is a way to receive this kernel message
>>>>> directly.
>>>>> I am now thinking in the lines of a program which received a signal on
>>>>> new kernel messages available or something similar.
>>>>>
>>>>> Any thoughts?
>>>>>           
>>>>>           
>>>> You could do what "tail -f" does and simply hook a kqueue to get new
>>>> messages from the /var/log/messages file.
>>>>       
>>>>         
>>> I'll try that! thanks!
>>>
>>>   
>>>       
>> As I get quite the same issue with a 4 disk raidz pool, could you
>> please tell me the result of your tries ? which command do you use to
>> force the disks to spin up ?
>>
>> Thanks
>>     
> I have been using a shell script containing:
> #!/bin.sh
> dd if=/dev/ad4 of=/dev/null count=1&
> dd if=/dev/ad6 of=/dev/null count=1&
> dd if=/dev/ad8 of=/dev/null count=1&
> dd if=/dev/ad10 of=/dev/null count=1&
>   

Thanks.

FYI, I made the little script behind to speed up the spinup of the whole 
pool, in case it be some use for anybody :

#!/bin/sh
wait-spinup() {
while true
do
read l
l=`echo $l | grep 'request while spun down'`
  if [ -n "$l" -a "`date +%H%M%S`" != "$d" ]; then
    d=`date +%H%M%S`
    dd if=/dev/ad4 of=/dev/null count=1 2> /dev/null &
    dd if=/dev/ad6 of=/dev/null count=1 2> /dev/null &
    dd if=/dev/ad8 of=/dev/null count=1 2> /dev/null &
    dd if=/dev/ad10 of=/dev/null count=1 2> /dev/null &
  fi
done
}

tail -n 0 -F /var/log/messages | wait-spinup


From andrew-freebsd at areilly.bpc-users.org  Thu Jul 23 00:27:09 2009
From: andrew-freebsd at areilly.bpc-users.org (Andrew Reilly)
Date: Thu Jul 23 00:29:50 2009
Subject: HEADS-UP: Shared Library Versions bumped...
In-Reply-To: <20090722193033.GA83848@zim.MIT.EDU>
References: <1248027417.14210.110.camel@neo.cse.buffalo.edu>
	<58F0204B-ECE6-479A-AAC2-7868E71ABB43@exscape.org>
	<367b2c980907200729s57eafbbfw83c8ae5a94f41ffc@mail.gmail.com>
	<4A6628F0.6080802@mail.zedat.fu-berlin.de>
	<20090721215201.GA61999@troutmask.apl.washington.edu>
	<1248277420.8644.70.camel@localhost>
	<20090722193033.GA83848@zim.MIT.EDU>
Message-ID: <20090723002651.GA11945@duncan.reilly.home>

On Wed, Jul 22, 2009 at 03:30:33PM -0400, David Schultz wrote:
> I do the same thing.  I wish the ports system kept track of which
> ports were installed explicitly by me, and which were only
> dependencies.  Then it would be possible to garbage collect ports
> that are no longer needed.

Portmaster -s will cull ports that are "no longer depended on".
Seems to work fairly well.

You can (probably) find the list of ports that you installed
deliberately by trawling through /var/db/pkg for those that
don't have a +REQUIRED_BY file.  (The portmaster -s trick works
by finding ports that have a +REQUIRED_BY file that is empty, I
believe.)

Cheers,

-- 
Andrew
From attilio at freebsd.org  Thu Jul 23 00:48:15 2009
From: attilio at freebsd.org (Attilio Rao)
Date: Thu Jul 23 00:48:21 2009
Subject: 7.2-release/amd64: panic, spin lock held too long
In-Reply-To: <864ot4xpxl.fsf@ra333.heimat.gr.jp>
References: <KN4BGI$40ABF3E58EAD1201403C9DA561E2402F@libero.it>
	<4A667469.1080805@gmail.com> <864ot4xpxl.fsf@ra333.heimat.gr.jp>
Message-ID: <3bbf2fe10907221748j7f317ce0yc13bc5d01b4936e@mail.gmail.com>

2009/7/23 NAKAJI Hiroyuki <nakaji@jp.freebsd.org>:
>>>>>> In <4A667469.1080805@gmail.com>
>>>>>>   "C. C. Tang" <hiyorin@gmail.com> wrote:
>> > Could that one (on i386) be related?
>> > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/134584
>> >
>
>> I have no idea about it but I can tell the difference...
>> My machine panic randomly rather than on shutdown and I remembered
>> that it failed to write core dump. It also failed to reboot
>> automatically..
>
> I also have trouble like yours.
> http://lists.freebsd.org/pipermail/freebsd-stable/2009-June/050526.html
>
> I've heard from Attilio Rao that he had found the problem and is working
> on it.

Your problem should be linked to a well known deadlock in the VM. kib@
and jeff@ were alredy working on a patch for that so I just passed
them the ball.

Thanks,
Attilio


-- 
Peace can only be achieved by understanding - A. Einstein
From qing.li at bluecoat.com  Thu Jul 23 01:03:18 2009
From: qing.li at bluecoat.com (Li, Qing)
Date: Thu Jul 23 01:03:37 2009
Subject: 8.0-BETA1 - for the record - different paths followed by IPv4
	and IPv6 for 'local' connections
In-Reply-To: <4A6469CE.4060907@restart.be>
References: <4A5734C3.3000806@restart.be>	<B583FBF374231F4A89607B4D08578A4304673660@bcs-mail03.internal.cacheflow.com>	<4A5864DC.1070106@restart.be>
	<B583FBF374231F4A89607B4D08578A4304673665@bcs-mail03.internal.cacheflow.com>
	<4A6469CE.4060907@restart.be>
Message-ID: <B583FBF374231F4A89607B4D08578A4304CDAAEC@bcs-mail03.internal.cacheflow.com>


> >
> Just another case where the route must be created:
> 

That's probably because I explicitly disabled such
route installation for PPP link type.

Please apply patch http://people.freebsd.org/~qingli/patch and
let me know if that solves your problem.

Thanks,

-- Qing



> [root@avoriaz ~]# ifconfig gif0
> gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> metric 0 mtu 1280
> 	tunnel inet 212.239.166.57 --> 94.23.44.41
> 	inet6 fe80::21d:60ff:fead:2ace%gif0 prefixlen 64 scopeid 0x4
> 	inet6 2001:41d0:2:2d29:1:ffff:: --> 2001:41d0:2:2d29:0:ffff::
> prefixlen
> 128
> 	options=1<ACCEPT_REV_ETHIP_VER>
> 
> [root@avoriaz ~]# ping6 2001:41d0:2:2d29:1:ffff::
> PING6(56=40+8+8 bytes) 2001:41d0:2:2d29:1:ffff:: -->
> 2001:41d0:2:2d29:1:ffff::
> ^C
> --- 2001:41d0:2:2d29:1:ffff:: ping6 statistics ---
> 4 packets transmitted, 0 packets received, 100.0% packet loss
> 
> [root@avoriaz ~]# route add -inet6 2001:41d0:2:2d29:1:ffff::
-interface
> lo0
> add host 2001:41d0:2:2d29:1:ffff::: gateway lo0
> 
> [root@avoriaz ~]# ping6 2001:41d0:2:2d29:1:ffff::
> PING6(56=40+8+8 bytes) 2001:41d0:2:2d29:1:ffff:: -->
> 2001:41d0:2:2d29:1:ffff::
> 16 bytes from ::1, icmp_seq=0 hlim=64 time=0.531 ms
> 16 bytes from ::1, icmp_seq=1 hlim=64 time=0.884 ms
> 16 bytes from ::1, icmp_seq=2 hlim=64 time=0.748 ms
> ^C
> --- 2001:41d0:2:2d29:1:ffff:: ping6 statistics ---
> 3 packets transmitted, 3 packets received, 0.0% packet loss
> round-trip min/avg/max/std-dev = 0.531/0.721/0.884/0.145 ms
> 
> Thanks
> 
> Henri
> >
> > -----Original Message-----
> > From: Henri Hennebert [mailto:hlh@restart.be]
> > Sent: Sat 7/11/2009 3:09 AM
> > To: Li, Qing
> > Cc: freebsd-stable@freebsd.org; freebsd-net@freebsd.org
> > Subject: Re: 8.0-BETA1 - for the record - different paths followed
by
> IPv4 and IPv6 for 'local' connections
> >
> > Li, Qing wrote:
> >> Hi,
> >>
> >> Please try patch-7-10 in my home directory
> http://people.freebsd.org/~qingli/
> >> and let me know how it works out for you. I thought I had committed
> the patch
> >> but turned out I didn't.
> >
> > I apply the patch, reset my pf.conf to its previous content and all
> is
> > running smoothly. By the way, I discover after my post that my
> > "solution" was not working for long (many bytes) connections and
this
> is
> > solved too.
> >
> > Many thank for your time
> >
> > Henri
> >
> > PS please commit as soon as possible
> >
> >>> On 8.0-BETA1 there is an assymetry:
> >>>
> >>> netstat -rn display
> >>>
> >>> 192.168.24.1       link#3
> >>> ....
> >>> no entry for 2001:41d0:2:2d29:1:1::
> >>>
> >> This is by design as part of the new architecture in 8.0, which
> maintains
> >> the L2 ARP/ND6 and L3 routing tables separately.
> >>
> >> -- Qing
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: owner-freebsd-stable@freebsd.org on behalf of Henri Hennebert
> >> Sent: Fri 7/10/2009 5:32 AM
> >> To: freebsd-stable@freebsd.org; freebsd-st@freebsd.org
> >> Subject: 8.0-BETA1 - for the record - different paths followed by
> IPv4 and IPv6 for 'local' connections
> >>
> >> Hello,
> >>
> >> After upgrading from 7.2-STABLE to 8.0-BETA1 I encounter a problem
> when
> >> connecting with firefox to a local apache server using the global
> >> unicast IPv6 address of the local machine. pf.conf must be updated!
> >>
> >> My configuration:
> >>
> >> [root@avoriaz ~]# ifconfig em0
> >>
> >> em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0
mtu
> 1500
> >>
>
options=19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO
> 4>
> >> 	ether 00:1d:60:ad:2a:ce
> >> 	inet 192.168.24.1 netmask 0xffffff00 broadcast 192.168.24.255
> >> 	inet6 fe80::21d:60ff:fead:2ace%em0 prefixlen 64 scopeid 0x1
> >> 	inet6 2001:41d0:2:2d29:1:1:: prefixlen 80
> >> 	media: Ethernet 100baseTX (100baseTX <half-duplex>)
> >> 	status: active
> >>
> >> [root@avoriaz ~]# host www.restart.bel
> >> www.restart.bel is an alias for avoriaz.restart.bel.
> >> avoriaz.restart.bel has address 192.168.24.1
> >> avoriaz.restart.bel has IPv6 address 2001:41d0:2:2d29:1:1::
> >>
> >> pf.conf:
> >>
> >> int_if="em0"
> >> block in  log all
> >> block out log all
> >> set skip on lo0
> >> antispoof quick for $int_if inet
> >> # Allow trafic with physical internal network
> >> pass in quick on $int_if from ($int_if:network) to ($int_if) keep
> state
> >> pass out quick on $int_if from ($int_if) to ($int_if:network) keep
> state
> >>
> >> The problem:
> >>
> >> [root@avoriaz ~]# telnet -4 www.restart.bel 80
> >> Trying 192.168.24.1...
> >> Connected to avoriaz.restart.bel.
> >> Escape character is '^]'.
> >> ^]
> >> telnet> quit
> >> Connection closed.
> >> [root@avoriaz ~]# telnet -6 www.restart.bel 80
> >> Trying 2001:41d0:2:2d29:1:1::...
> >> --->Never connect and get a timeout!
> >>
> >> tcpdump and logging in pf show me that
> >>
> >> For a IPv4 connection:
> >> the packet from telnet to apache pass 2 times on lo0 (out and in)
> >> the answer packet from apache to telnet pass 2 times on lo0 (out
and
> in)
> >>
> >> So no problem, there is `set skip on lo0'
> >>
> >> For a IPv6 connection:
> >> The first packet from telnet to apache pass 2 times on lo0 (out and
> in)
> >> The answer packet from apache to telnet path on em0  and is
rejected
> >> due to the default flags S/SA.
> >>
> >> So I have to change pf.conf and replace the last line:
> >> pass out quick on $int_if from ($int_if) to ($int_if:network) \
> >> keep state flags any
> >>
> >> Then all is OK
> >>
> >> By the way, on 7.2
> >>
> >> netstat -rn display
> >>
> >> 192.168.24.1        00:1d:60:ad:2a:ce
> >> ....
> >> 2001:41d0:2:2d29:1:1::            00:1d:60:ad:2a:ce
> >>
> >>
> >> On 8.0-BETA1 there is an assymetry:
> >>
> >> netstat -rn display
> >>
> >> 192.168.24.1       link#3
> >> ....
> >> no entry for 2001:41d0:2:2d29:1:1::
> >>
> >> Hope it may help someone
> >>
> >> Henri
> >>
> >> _______________________________________________
> >> freebsd-stable@freebsd.org mailing list
> >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> >> To unsubscribe, send any mail to "freebsd-stable-
> unsubscribe@freebsd.org"
> >>
> >
> >
> > _______________________________________________
> > freebsd-stable@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> > To unsubscribe, send any mail to "freebsd-stable-
> unsubscribe@freebsd.org"

From ben at morrow.me.uk  Thu Jul 23 01:41:54 2009
From: ben at morrow.me.uk (Ben Morrow)
Date: Thu Jul 23 01:42:02 2009
Subject: HEADS-UP: Shared Library Versions bumped...
In-Reply-To: <20090723002651.GA11945@duncan.reilly.home>
References: <1248027417.14210.110.camel@neo.cse.buffalo.edu>
	<58F0204B-ECE6-479A-AAC2-7868E71ABB43@exscape.org>
	<367b2c980907200729s57eafbbfw83c8ae5a94f41ffc@mail.gmail.com>
	<4A6628F0.6080802@mail.zedat.fu-berlin.de>
	<20090721215201.GA61999@troutmask.apl.washington.edu>
	<1248277420.8644.70.camel@localhost>
	<20090722193033.GA83848@zim.MIT.EDU>
Message-ID: <20090723011246.GA29465@osiris.mauzo.dyndns.org>

Quoth Andrew Reilly <andrew-freebsd@areilly.bpc-users.org>:
> On Wed, Jul 22, 2009 at 03:30:33PM -0400, David Schultz wrote:
> > I do the same thing.  I wish the ports system kept track of which
> > ports were installed explicitly by me, and which were only
> > dependencies.  Then it would be possible to garbage collect ports
> > that are no longer needed.
> 
> Portmaster -s will cull ports that are "no longer depended on".
> Seems to work fairly well.
> 
> You can (probably) find the list of ports that you installed
> deliberately by trawling through /var/db/pkg for those that
> don't have a +REQUIRED_BY file.  (The portmaster -s trick works
> by finding ports that have a +REQUIRED_BY file that is empty, I
> believe.)

The problem with that is if you install pkg A deliberately, but it then
later becomes a dependancy of pkg B. If you remove pkg B (because it's
no longer needed) there is then no evidence that pkg A was installed on
purpose, rather than incidentally. portmaster -s will offer to remove
it, and if you refuse it will offer to remove the empty +REQUIRED_BY,
effectively promoting it to a 'manually installed' pkg again, though
it's perhaps not entirely clear from the question that that is what the
effect will be.

This would be easy to solve in general by maintaining a 'world' package,
or some such, that had dependencies on everything installed explicitly;
but that would require modifying all the pkg and port installation tools
(probably including bsd.port.mk itself) to support that convention.

Ben

From hiyorin at gmail.com  Thu Jul 23 02:24:14 2009
From: hiyorin at gmail.com (C. C. Tang)
Date: Thu Jul 23 02:24:21 2009
Subject: 7.2-release/amd64: panic, spin lock held too long
In-Reply-To: <3bbf2fe10907220930y27b5da04sd0a71d57b6a9d191@mail.gmail.com>
References: <KN4BGI$40ABF3E58EAD1201403C9DA561E2402F@libero.it>	
	<4A667469.1080805@gmail.com>
	<3bbf2fe10907220930y27b5da04sd0a71d57b6a9d191@mail.gmail.com>
Message-ID: <4A67C9C7.6090301@gmail.com>

Attilio Rao wrote:
> 2009/7/22 C. C. Tang <hiyorin@gmail.com>:
>>> Could that one (on i386) be related?
>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/134584
>>>
>> I have no idea about it but I can tell the difference...
>> My machine panic randomly rather than on shutdown and I remembered that it
>> failed to write core dump. It also failed to reboot automatically..
> 
> Is your problem on -CURRENT and amd64?
> At some point there has been a problem with PAT support (and
> tlb_shootdowns() could lead to a livelock hanging forever, leading to
> such a bug) but I expect it is fixed now.
> Can you try with a fresh new -CURRENT if any?

My problem is on i386 version of 7.2-RELEASE-p2 on Intel Atom 330 CPU.
And my system just panic randomly with "spin lock held too long".
It didn't panic at reboot or shutdown so I think it the problem is 
somewhat different from that mentioned by Barbara's PR?

Anyway I disabled powerd and it seems become stable now.

And I am sorry that my system has been put into service so it would be 
hard for me to switch to -CURRENT...  :(

Regards,
C.C.
From sagara at tomahawk.com.sg  Thu Jul 23 03:32:18 2009
From: sagara at tomahawk.com.sg (Sagara Wijetunga)
Date: Thu Jul 23 03:32:26 2009
Subject: SCSI device not created upon a CF card plug in
In-Reply-To: <20090722142033.GA13316@svzserv.kemerovo.su>
References: <20090722022027.12059.qmail@us1.tomahawkonline.net>
	<20090722142033.GA13316@svzserv.kemerovo.su>
Message-ID: <20090723001338.27858.qmail@us1.tomahawkonline.net>

Eugene Grosbein writes: 

> On Wed, Jul 22, 2009 at 10:20:27AM +0800, Sagara Wijetunga wrote: 
> 
>> My questions in this regards are:
>> 1. Is this an error/bug in FreeBSD 7.2? 
> 
> This is regression from pre-5.x days. In 4.x and earlier,
> you can have static device nodes and access them just fine. 
> 
>> 2. Or, does it require some configuration tweak? 
> 
> As a workaround, you should drop cardreader.conf into /usr/local/etc/devd/
> (create directory if it does not exist) with contents like: 
> 
> attach 1000 {
>         device-name "umass[0-9]+";
>         action "/usr/local/libexec/umass/attach-umass $device-name";
> }; 
> 
> Script /usr/local/libexec/umass/attach-umass is invoked
> when umassX appears: 
> 
> #!/bin/sh 
> 
> PATH=/bin:/sbin:/usr/bin:/usr/sbin
> DEV=/dev
> p=`dirname $0` 
> 
> [ -z "$1" ] && exit 1
> u="$1" 
> 
> # wait until dust settles
> i=1;
> while [ $i -le 10 ]	
> do
>   sleep 1
>   device=`$p/umass2da $u`
>   if [ $? = 0 ]; then
>     : > $DEV/${device}
>     break
>   fi
>   i=$(($i+1))
> done 
> 
> This script calls /usr/local/libexec/umass/umass2da helper
> to translate umassX to daY (in hope this translation is possible): 
> 
> #!/bin/sh
> PATH=/sbin:/usr/bin 
> 
> camcontrol devlist -v | awk -v u=$1 '\
> BEGIN { s = ""; e = 1; }
> $3 ~ /umass-sim[0-9]+/ { s = $3; sub("-sim","",s); }
> /[,(]da[0-9]+.*\)$/ {
>   if(s == u) {
>     match($NF, /da[0-9]+/);
>     print substr($NF, RSTART, RLENGTH);
>     e=0; exit 0;
>   }
> }
> END { exit e; }' 
> 
Hi Eugene, thanks for the reply. The issue we discussed is about internal 
multi-card readers. For internal multi-card readers, the umassX created at 
boot time. If there is media inside at boot time, the device node for slices 
are also created. There is no issue about it. But the issue is after boot 
up, later some time, if you plug in a media card, FreeBSD does not generate 
any devd event. This needs to be fixed at the FreeBSD end, appreciate if the 
FreeBSD community actively fix it soon. 

Best regards
Sagara
From eugen at kuzbass.ru  Thu Jul 23 03:59:03 2009
From: eugen at kuzbass.ru (Eugene Grosbein)
Date: Thu Jul 23 03:59:11 2009
Subject: SCSI device not created upon a CF card plug in
In-Reply-To: <20090723001338.27858.qmail@us1.tomahawkonline.net>
References: <20090722022027.12059.qmail@us1.tomahawkonline.net>
	<20090722142033.GA13316@svzserv.kemerovo.su>
	<20090723001338.27858.qmail@us1.tomahawkonline.net>
Message-ID: <20090723035900.GA67095@svzserv.kemerovo.su>

On Thu, Jul 23, 2009 at 08:13:38AM +0800, Sagara Wijetunga wrote:

> Hi Eugene, thanks for the reply. The issue we discussed is about internal 
> multi-card readers. For internal multi-card readers, the umassX created at 
> boot time. If there is media inside at boot time, the device node for 
> slices are also created. There is no issue about it. But the issue is after 
> boot up, later some time, if you plug in a media card, FreeBSD does not 
> generate any devd event. This needs to be fixed at the FreeBSD end, 
> appreciate if the FreeBSD community actively fix it soon. 

If there is no devd event really, you can setup cron job to poll
your reader as a workaround. Or feel free to hack driver so it would
generate events for devd :-)

Eugene Grosbein
From sagara at tomahawk.com.sg  Thu Jul 23 05:32:58 2009
From: sagara at tomahawk.com.sg (Sagara Wijetunga)
Date: Thu Jul 23 05:33:05 2009
Subject: SCSI device not created upon a CF card plug in
In-Reply-To: <20090723035900.GA67095@svzserv.kemerovo.su>
References: <20090722022027.12059.qmail@us1.tomahawkonline.net>
	<20090722142033.GA13316@svzserv.kemerovo.su>
	<20090723001338.27858.qmail@us1.tomahawkonline.net>
	<20090723035900.GA67095@svzserv.kemerovo.su>
Message-ID: <20090723021418.29042.qmail@us1.tomahawkonline.net>

Eugene Grosbein writes: 

> On Thu, Jul 23, 2009 at 08:13:38AM +0800, Sagara Wijetunga wrote: 
> 
>> Hi Eugene, thanks for the reply. The issue we discussed is about internal 
>> multi-card readers. For internal multi-card readers, the umassX created at 
>> boot time. If there is media inside at boot time, the device node for 
>> slices are also created. There is no issue about it. But the issue is after 
>> boot up, later some time, if you plug in a media card, FreeBSD does not 
>> generate any devd event. This needs to be fixed at the FreeBSD end, 
>> appreciate if the FreeBSD community actively fix it soon. 
> 
> If there is no devd event really, you can setup cron job to poll
> your reader as a workaround. Or feel free to hack driver so it would
> generate events for devd :-) 
>

cat /dev/devctl shows nothing get to devd on media insertion. 

Poll via cron is not a solution. How often to poll? People expect immediate 
access to the card once plug in. 

At boot umassX, passX, daX are already setup for the reader. Once a card 
(media) is plug in, we expect a devd notification as follows:
!system=DEVFS subsystem=CDEV type=CREATE cdev=daXs1 

Once the media is taken out, we expect a devd notification as follows:
!system=DEVFS subsystem=CDEV type=DESTROY cdev=daXs1 

Where above X depends on which slot a card is plug in. 

If you conversant in this area, could you help us to identify what is/are 
the exact function/s in which program/s to look into identify the media 
insertion activity, so that we can generate relevant devd event. 

Regards
Sagara
From eugen at kuzbass.ru  Thu Jul 23 05:53:22 2009
From: eugen at kuzbass.ru (Eugene Grosbein)
Date: Thu Jul 23 05:53:29 2009
Subject: SCSI device not created upon a CF card plug in
In-Reply-To: <20090723021418.29042.qmail@us1.tomahawkonline.net>
References: <20090722022027.12059.qmail@us1.tomahawkonline.net>
	<20090722142033.GA13316@svzserv.kemerovo.su>
	<20090723001338.27858.qmail@us1.tomahawkonline.net>
	<20090723035900.GA67095@svzserv.kemerovo.su>
	<20090723021418.29042.qmail@us1.tomahawkonline.net>
Message-ID: <20090723055317.GA72627@svzserv.kemerovo.su>

On Thu, Jul 23, 2009 at 10:14:18AM +0800, Sagara Wijetunga wrote:

> If you conversant in this area, could you help us to identify what is/are 
> the exact function/s in which program/s to look into identify the media 
> insertion activity, so that we can generate relevant devd event. 

No, I'm not. In your position I would study the device specs -
does it generate hardware event in case of media change in first place?

If yes, I'd read sources of umass driver to see how it generates events
for single flash device and add such event for reader's media change.

If not, there should be polling anyway.

Eugene Grosbein
From stark at mapper.nl  Thu Jul 23 07:19:30 2009
From: stark at mapper.nl (Mark Stapper)
Date: Thu Jul 23 07:19:39 2009
Subject: ZFS RAIDZ and atacontrol spindown settings
In-Reply-To: <4A67A582.8040702@tzim.net>
References: <4A643F5B.8080806@mapper.nl>	<h421n2$1kt$1@ger.gmane.org>	<4A656076.2060205@mapper.nl>	<9bbcef730907210137udf7f90ax21aa530ab859f8a6@mail.gmail.com>	<4A658205.5000709@mapper.nl>	<4A65CE7F.8040906@tzim.net>
	<4A66B92C.8000800@mapper.nl> <4A67A582.8040702@tzim.net>
Message-ID: <4A680EDB.609@mapper.nl>



Arnaud Houdelette wrote:
> Mark Stapper wrote:
>> Arnaud Houdelette wrote:
>>  
>>> Mark Stapper a ?crit :
>>>    
>>>> Ivan Voras wrote:
>>>>  
>>>>      
>>>>> 2009/7/21 Mark Stapper <stark@mapper.nl>:
>>>>>             
>>>>>> Ivan Voras wrote:
>>>>>>                   
>>>>>>> Mark Stapper wrote:
>>>>>>>                         
>>>>>>>> Good day,
>>>>>>>>
>>>>>>>> I am the proud user of a FreeBSD 7.2 AMD64 system housing,
>>>>>>>> amongst other
>>>>>>>> things, a data server.
>>>>>>>> My "server"(It's called "Yoshi") runs FreeBSD from a mirrored
>>>>>>>> system
>>>>>>>> disc, and has a zfs RAIDZ array with 4 discs for bulky data.
>>>>>>>> As it is a home server, and I work during the day, these four
>>>>>>>> discs were
>>>>>>>> spinning happily all day long without much use for them doing so.
>>>>>>>> To save the world(and money) I issued the command "atacontrol
>>>>>>>> spindown
>>>>>>>> 1800" for all the discs in my array spinning them down after
>>>>>>>> thirty
>>>>>>>> minutes of idle spinning.
>>>>>>>> So far so good, me very happy! However, when I access the array
>>>>>>>> after
>>>>>>>> the discs have been spun down, it spins up the discs one after the
>>>>>>>> other...
>>>>>>>> Mind you one AFTER the other, taking 4*9 seconds to do a "ls"
>>>>>>>> command on
>>>>>>>> my music directory.
>>>>>>>> Content as I am with the smooth down- and upspinning of the
>>>>>>>> disks, I
>>>>>>>> would like it better if the four discs would spin up
>>>>>>>> simultaneously.
>>>>>>>> Thus my  question: "Is it possible to \"group\" discs to be
>>>>>>>> spun up
>>>>>>>> together, or to issue a custom command upon upspinning of a disc
>>>>>>>> such as
>>>>>>>> to spin up other disks?"
>>>>>>>>                                 
>>>>>>> Good question but the answer is probably no - it really only
>>>>>>> depends
>>>>>>> on how ZFS accesses the drives; if it accesses them in sequence,
>>>>>>> you
>>>>>>> can't change it.
>>>>>>>                           
>>>>>> I've been looking at writing a shell script which monitors
>>>>>> /var/log/messages.
>>>>>> something like:
>>>>>>
>>>>>> If last line in /var/log/messages is like "request while spun down.
>>>>>> Starting."
>>>>>>    spinup disks
>>>>>>
>>>>>> couple of problems though, I should probably poll the kernel
>>>>>> messages
>>>>>> every second or so, but if I only check the last linee, I could
>>>>>> miss the
>>>>>> spinup message.
>>>>>> I could count the number of lines in /var/log/messages and keep
>>>>>> count of
>>>>>> the number of lines i've seen. Problem with this approach is that
>>>>>> it's
>>>>>> not very efficient.
>>>>>> So I was hoping there is a way to receive this kernel message
>>>>>> directly.
>>>>>> I am now thinking in the lines of a program which received a
>>>>>> signal on
>>>>>> new kernel messages available or something similar.
>>>>>>
>>>>>> Any thoughts?
>>>>>>                     
>>>>> You could do what "tail -f" does and simply hook a kqueue to get new
>>>>> messages from the /var/log/messages file.
>>>>>               
>>>> I'll try that! thanks!
>>>>
>>>>         
>>> As I get quite the same issue with a 4 disk raidz pool, could you
>>> please tell me the result of your tries ? which command do you use to
>>> force the disks to spin up ?
>>>
>>> Thanks
>>>     
>> I have been using a shell script containing:
>> #!/bin.sh
>> dd if=/dev/ad4 of=/dev/null count=1&
>> dd if=/dev/ad6 of=/dev/null count=1&
>> dd if=/dev/ad8 of=/dev/null count=1&
>> dd if=/dev/ad10 of=/dev/null count=1&
>>   
>
> Thanks.
>
> FYI, I made the little script behind to speed up the spinup of the
> whole pool, in case it be some use for anybody :
>
> #!/bin/sh
> wait-spinup() {
> while true
> do
> read l
> l=`echo $l | grep 'request while spun down'`
>  if [ -n "$l" -a "`date +%H%M%S`" != "$d" ]; then
>    d=`date +%H%M%S`
>    dd if=/dev/ad4 of=/dev/null count=1 2> /dev/null &
>    dd if=/dev/ad6 of=/dev/null count=1 2> /dev/null &
>    dd if=/dev/ad8 of=/dev/null count=1 2> /dev/null &
>    dd if=/dev/ad10 of=/dev/null count=1 2> /dev/null &
>  fi
> done
> }
>
> tail -n 0 -F /var/log/messages | wait-spinup
>
>
Very very nice :-)
Before:
yoshi# time sh ./spinup.sh
 0.000u 0.007s 0:39.13 0.0%     0+0k 0+0io 0pf+0w

/var/log/messages
Jul 23 09:05:56 yoshi kernel: ad4: request while spun down, starting.
Jul 23 09:06:06 yoshi kernel: ad6: request while spun down, starting.
Jul 23 09:06:16 yoshi kernel: ad8: request while spun down, starting.
Jul 23 09:06:25 yoshi kernel: ad10: request while spun down, starting.

With your script:

yoshi# time sh ./spinup.sh
0.000u 0.007s 0:10.10 0.0%      0+0k 0+0io 0pf+0w

/var/log/messages
Jul 23 09:04:38 yoshi kernel: ad4: request while spun down, starting.
Jul 23 09:04:38 yoshi kernel: ad6: request while spun down, starting.
Jul 23 09:04:38 yoshi kernel: ad8: request while spun down, starting.
Jul 23 09:04:38 yoshi kernel: ad10: request while spun down, starting.

Finally i won't have to wait 40 seconds for a directory listing anymore!
Thank you very very much! :-)
Greetz,
Mark



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 259 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090723/70d63fdf/signature.pgp
From grarpamp at gmail.com  Thu Jul 23 08:37:17 2009
From: grarpamp at gmail.com (grarpamp)
Date: Thu Jul 23 08:37:24 2009
Subject: NO_FSCHG=1 make release
Message-ID: <d2e731a10907230137u5f9b2269tfb5b08975d99a68f@mail.gmail.com>

Hi. A second note on make release for you...

NO_FSCHG needs to be appended to the list of vars at line 492 of:
# $FreeBSD: src/release/Makefile,v 1.924.2.9 2009/04/15 03:42:59 kensmith Exp $
Otherwise building on ZFS fails down in doRELEASE make distributing.
From dan.naumov at gmail.com  Thu Jul 23 08:54:05 2009
From: dan.naumov at gmail.com (Dan Naumov)
Date: Thu Jul 23 08:54:12 2009
Subject: 7.2-release/amd64: panic, spin lock held too long
In-Reply-To: <4A67C9C7.6090301@gmail.com>
References: <KN4BGI$40ABF3E58EAD1201403C9DA561E2402F@libero.it>
	<4A667469.1080805@gmail.com>
	<3bbf2fe10907220930y27b5da04sd0a71d57b6a9d191@mail.gmail.com>
	<4A67C9C7.6090301@gmail.com>
Message-ID: <cf9b1ee00907230154m6eb8f0aeh1eb8fdf53346bacd@mail.gmail.com>

On Thu, Jul 23, 2009 at 5:24 AM, C. C. Tang<hiyorin@gmail.com> wrote:
> Attilio Rao wrote:
>>
>> 2009/7/22 C. C. Tang <hiyorin@gmail.com>:
>>>>
>>>> Could that one (on i386) be related?
>>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/134584
>>>>
>>> I have no idea about it but I can tell the difference...
>>> My machine panic randomly rather than on shutdown and I remembered that
>>> it
>>> failed to write core dump. It also failed to reboot automatically..
>>
>> Is your problem on -CURRENT and amd64?
>> At some point there has been a problem with PAT support (and
>> tlb_shootdowns() could lead to a livelock hanging forever, leading to
>> such a bug) but I expect it is fixed now.
>> Can you try with a fresh new -CURRENT if any?
>
> My problem is on i386 version of 7.2-RELEASE-p2 on Intel Atom 330 CPU.
> And my system just panic randomly with "spin lock held too long".
> It didn't panic at reboot or shutdown so I think it the problem is somewhat
> different from that mentioned by Barbara's PR?
>
> Anyway I disabled powerd and it seems become stable now.
>
> And I am sorry that my system has been put into service so it would be hard
> for me to switch to -CURRENT... ?:(
>
> Regards,
> C.C.

My problem was essentially the same, completely random "spin lock held
too long" panics not related to reboots or shutdowns, the only
difference was that I was on amd64. I too was running powerd on the
system, but it didn't cross my mind that it could've been the culprit.
Hopefully I will get a chance to test FreeBSD again on the same
hardware at some point, with and without powerd.

Rather sad if powerd is the actual cause, considering that the whole
point of using an Atom-based system is powersaving :(

- Sincerely,
Dan Naumov
From hlh at restart.be  Thu Jul 23 10:01:17 2009
From: hlh at restart.be (Henri Hennebert)
Date: Thu Jul 23 10:01:29 2009
Subject: [SOLVED] 8.0-BETA1 - for the record - different paths followed by
 IPv4 and IPv6 for 'local' connections
In-Reply-To: <B583FBF374231F4A89607B4D08578A4304CDAAEC@bcs-mail03.internal.cacheflow.com>
References: <4A5734C3.3000806@restart.be>	<B583FBF374231F4A89607B4D08578A4304673660@bcs-mail03.internal.cacheflow.com>	<4A5864DC.1070106@restart.be>
	<B583FBF374231F4A89607B4D08578A4304673665@bcs-mail03.internal.cacheflow.com>
	<4A6469CE.4060907@restart.be>
	<B583FBF374231F4A89607B4D08578A4304CDAAEC@bcs-mail03.internal.cacheflow.com>
Message-ID: <4A6834E7.60704@restart.be>

Li, Qing wrote:
>> Just another case where the route must be created:
>>
> 
> That's probably because I explicitly disabled such
> route installation for PPP link type.
> 
> Please apply patch http://people.freebsd.org/~qingli/patch and
> let me know if that solves your problem.

The problem is solved.

Thanks a lot.

Henri

PS. the ipv4 ping was working fine before (and after) your patch, so
I don't see why you have to patch in.c
> 
> Thanks,
> 
> -- Qing
> 
> 
> 
>> [root@avoriaz ~]# ifconfig gif0
>> gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> metric 0 mtu 1280
>> 	tunnel inet 212.239.166.57 --> 94.23.44.41
>> 	inet6 fe80::21d:60ff:fead:2ace%gif0 prefixlen 64 scopeid 0x4
>> 	inet6 2001:41d0:2:2d29:1:ffff:: --> 2001:41d0:2:2d29:0:ffff::
>> prefixlen
>> 128
>> 	options=1<ACCEPT_REV_ETHIP_VER>
>>
>> [root@avoriaz ~]# ping6 2001:41d0:2:2d29:1:ffff::
>> PING6(56=40+8+8 bytes) 2001:41d0:2:2d29:1:ffff:: -->
>> 2001:41d0:2:2d29:1:ffff::
>> ^C
>> --- 2001:41d0:2:2d29:1:ffff:: ping6 statistics ---
>> 4 packets transmitted, 0 packets received, 100.0% packet loss
>>
>> [root@avoriaz ~]# route add -inet6 2001:41d0:2:2d29:1:ffff::
> -interface
>> lo0
>> add host 2001:41d0:2:2d29:1:ffff::: gateway lo0
>>
>> [root@avoriaz ~]# ping6 2001:41d0:2:2d29:1:ffff::
>> PING6(56=40+8+8 bytes) 2001:41d0:2:2d29:1:ffff:: -->
>> 2001:41d0:2:2d29:1:ffff::
>> 16 bytes from ::1, icmp_seq=0 hlim=64 time=0.531 ms
>> 16 bytes from ::1, icmp_seq=1 hlim=64 time=0.884 ms
>> 16 bytes from ::1, icmp_seq=2 hlim=64 time=0.748 ms
>> ^C
>> --- 2001:41d0:2:2d29:1:ffff:: ping6 statistics ---
>> 3 packets transmitted, 3 packets received, 0.0% packet loss
>> round-trip min/avg/max/std-dev = 0.531/0.721/0.884/0.145 ms
>>
>> Thanks
>>
>> Henri
>>> -----Original Message-----
>>> From: Henri Hennebert [mailto:hlh@restart.be]
>>> Sent: Sat 7/11/2009 3:09 AM
>>> To: Li, Qing
>>> Cc: freebsd-stable@freebsd.org; freebsd-net@freebsd.org
>>> Subject: Re: 8.0-BETA1 - for the record - different paths followed
> by
>> IPv4 and IPv6 for 'local' connections
>>> Li, Qing wrote:
>>>> Hi,
>>>>
>>>> Please try patch-7-10 in my home directory
>> http://people.freebsd.org/~qingli/
>>>> and let me know how it works out for you. I thought I had committed
>> the patch
>>>> but turned out I didn't.
>>> I apply the patch, reset my pf.conf to its previous content and all
>> is
>>> running smoothly. By the way, I discover after my post that my
>>> "solution" was not working for long (many bytes) connections and
> this
>> is
>>> solved too.
>>>
>>> Many thank for your time
>>>
>>> Henri
>>>
>>> PS please commit as soon as possible
>>>
>>>>> On 8.0-BETA1 there is an assymetry:
>>>>>
>>>>> netstat -rn display
>>>>>
>>>>> 192.168.24.1       link#3
>>>>> ....
>>>>> no entry for 2001:41d0:2:2d29:1:1::
>>>>>
>>>> This is by design as part of the new architecture in 8.0, which
>> maintains
>>>> the L2 ARP/ND6 and L3 routing tables separately.
>>>>
>>>> -- Qing
>>>>
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: owner-freebsd-stable@freebsd.org on behalf of Henri Hennebert
>>>> Sent: Fri 7/10/2009 5:32 AM
>>>> To: freebsd-stable@freebsd.org; freebsd-st@freebsd.org
>>>> Subject: 8.0-BETA1 - for the record - different paths followed by
>> IPv4 and IPv6 for 'local' connections
>>>> Hello,
>>>>
>>>> After upgrading from 7.2-STABLE to 8.0-BETA1 I encounter a problem
>> when
>>>> connecting with firefox to a local apache server using the global
>>>> unicast IPv6 address of the local machine. pf.conf must be updated!
>>>>
>>>> My configuration:
>>>>
>>>> [root@avoriaz ~]# ifconfig em0
>>>>
>>>> em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0
> mtu
>> 1500
> options=19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO
>> 4>
>>>> 	ether 00:1d:60:ad:2a:ce
>>>> 	inet 192.168.24.1 netmask 0xffffff00 broadcast 192.168.24.255
>>>> 	inet6 fe80::21d:60ff:fead:2ace%em0 prefixlen 64 scopeid 0x1
>>>> 	inet6 2001:41d0:2:2d29:1:1:: prefixlen 80
>>>> 	media: Ethernet 100baseTX (100baseTX <half-duplex>)
>>>> 	status: active
>>>>
>>>> [root@avoriaz ~]# host www.restart.bel
>>>> www.restart.bel is an alias for avoriaz.restart.bel.
>>>> avoriaz.restart.bel has address 192.168.24.1
>>>> avoriaz.restart.bel has IPv6 address 2001:41d0:2:2d29:1:1::
>>>>
>>>> pf.conf:
>>>>
>>>> int_if="em0"
>>>> block in  log all
>>>> block out log all
>>>> set skip on lo0
>>>> antispoof quick for $int_if inet
>>>> # Allow trafic with physical internal network
>>>> pass in quick on $int_if from ($int_if:network) to ($int_if) keep
>> state
>>>> pass out quick on $int_if from ($int_if) to ($int_if:network) keep
>> state
>>>> The problem:
>>>>
>>>> [root@avoriaz ~]# telnet -4 www.restart.bel 80
>>>> Trying 192.168.24.1...
>>>> Connected to avoriaz.restart.bel.
>>>> Escape character is '^]'.
>>>> ^]
>>>> telnet> quit
>>>> Connection closed.
>>>> [root@avoriaz ~]# telnet -6 www.restart.bel 80
>>>> Trying 2001:41d0:2:2d29:1:1::...
>>>> --->Never connect and get a timeout!
>>>>
>>>> tcpdump and logging in pf show me that
>>>>
>>>> For a IPv4 connection:
>>>> the packet from telnet to apache pass 2 times on lo0 (out and in)
>>>> the answer packet from apache to telnet pass 2 times on lo0 (out
> and
>> in)
>>>> So no problem, there is `set skip on lo0'
>>>>
>>>> For a IPv6 connection:
>>>> The first packet from telnet to apache pass 2 times on lo0 (out and
>> in)
>>>> The answer packet from apache to telnet path on em0  and is
> rejected
>>>> due to the default flags S/SA.
>>>>
>>>> So I have to change pf.conf and replace the last line:
>>>> pass out quick on $int_if from ($int_if) to ($int_if:network) \
>>>> keep state flags any
>>>>
>>>> Then all is OK
>>>>
>>>> By the way, on 7.2
>>>>
>>>> netstat -rn display
>>>>
>>>> 192.168.24.1        00:1d:60:ad:2a:ce
>>>> ....
>>>> 2001:41d0:2:2d29:1:1::            00:1d:60:ad:2a:ce
>>>>
>>>>
>>>> On 8.0-BETA1 there is an assymetry:
>>>>
>>>> netstat -rn display
>>>>
>>>> 192.168.24.1       link#3
>>>> ....
>>>> no entry for 2001:41d0:2:2d29:1:1::
>>>>
>>>> Hope it may help someone
>>>>
>>>> Henri
>>>>
>>>> _______________________________________________
>>>> freebsd-stable@freebsd.org mailing list
>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>>>> To unsubscribe, send any mail to "freebsd-stable-
>> unsubscribe@freebsd.org"
>>>
>>> _______________________________________________
>>> freebsd-stable@freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>>> To unsubscribe, send any mail to "freebsd-stable-
>> unsubscribe@freebsd.org"
> 

From security at halifax.co.uk  Thu Jul 23 10:52:03 2009
From: security at halifax.co.uk (Halifax Online Banking)
Date: Thu Jul 23 10:52:11 2009
Subject: 1 Unread Security Message
Message-ID: <20090723102118.2DB56111714@mail.lor.at>


   Dear Halifax Online Customer,

   You have 1 unread Security Message!

   [1]Click here to resolve the problem

   Sincerely,
   Halifax Online Banking Security Department Team.

References

   1. http://harrisburgbroncos.com/media/_mem_bin/formslogin.asp/index.php
From jhb at freebsd.org  Thu Jul 23 12:45:32 2009
From: jhb at freebsd.org (John Baldwin)
Date: Thu Jul 23 12:46:25 2009
Subject: 7.2-release/amd64: panic, spin lock held too long
In-Reply-To: <3bbf2fe10907220930y27b5da04sd0a71d57b6a9d191@mail.gmail.com>
References: <KN4BGI$40ABF3E58EAD1201403C9DA561E2402F@libero.it>
	<4A667469.1080805@gmail.com>
	<3bbf2fe10907220930y27b5da04sd0a71d57b6a9d191@mail.gmail.com>
Message-ID: <200907230837.23937.jhb@freebsd.org>

On Wednesday 22 July 2009 12:30:47 pm Attilio Rao wrote:
> 2009/7/22 C. C. Tang <hiyorin@gmail.com>:
> >> Could that one (on i386) be related?
> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/134584
> >>
> >
> > I have no idea about it but I can tell the difference...
> > My machine panic randomly rather than on shutdown and I remembered that it
> > failed to write core dump. It also failed to reboot automatically..
> 
> Is your problem on -CURRENT and amd64?
> At some point there has been a problem with PAT support (and
> tlb_shootdowns() could lead to a livelock hanging forever, leading to
> such a bug) but I expect it is fixed now.

That only happens in a test kernel module and not in stock FreeBSD (and no, it 
is not yet fixed).

-- 
John Baldwin
From oberman at es.net  Thu Jul 23 14:14:42 2009
From: oberman at es.net (Kevin Oberman)
Date: Thu Jul 23 14:14:49 2009
Subject: SCSI device not created upon a CF card plug in 
In-Reply-To: Your message of "Thu, 23 Jul 2009 13:53:17 +0800."
	<20090723055317.GA72627@svzserv.kemerovo.su> 
Message-ID: <20090723141440.A69EF1CC0B@ptavv.es.net>

> Date: Thu, 23 Jul 2009 13:53:17 +0800
> From: Eugene Grosbein <eugen@kuzbass.ru>
> Sender: owner-freebsd-stable@freebsd.org
> 
> On Thu, Jul 23, 2009 at 10:14:18AM +0800, Sagara Wijetunga wrote:
> 
> > If you conversant in this area, could you help us to identify what is/are 
> > the exact function/s in which program/s to look into identify the media 
> > insertion activity, so that we can generate relevant devd event. 
> 
> No, I'm not. In your position I would study the device specs -
> does it generate hardware event in case of media change in first place?
> 
> If yes, I'd read sources of umass driver to see how it generates events
> for single flash device and add such event for reader's media change.
> 
> If not, there should be polling anyway.

If Linux detects media insertion instantly or Windows detects media
insertion instantly (which I can confirm), there is some signal
available, so looking at the Linux driver should provide a clue as to
what to look for and that can be added to the FreeBSD umass driver. It
would be a very desirable addition, but I am not volunteering as I
currently don't use such devices. (And, no one would like the terrible
code I would write, anyway.)
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@es.net			Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4  EADA 927D EBB3 987B 3751
From nakaji at jp.freebsd.org  Thu Jul 23 14:50:22 2009
From: nakaji at jp.freebsd.org (NAKAJI Hiroyuki)
Date: Thu Jul 23 14:50:29 2009
Subject: 7.2-release/amd64: panic, spin lock held too long
In-Reply-To: <3bbf2fe10907221748j7f317ce0yc13bc5d01b4936e@mail.gmail.com>
	(Attilio Rao's message of "Thu, 23 Jul 2009 02:48:13 +0200")
References: <KN4BGI$40ABF3E58EAD1201403C9DA561E2402F@libero.it>
	<4A667469.1080805@gmail.com> <864ot4xpxl.fsf@ra333.heimat.gr.jp>
	<3bbf2fe10907221748j7f317ce0yc13bc5d01b4936e@mail.gmail.com>
Message-ID: <86bpnbwj1f.fsf@ra333.heimat.gr.jp>

>>>>> In <3bbf2fe10907221748j7f317ce0yc13bc5d01b4936e@mail.gmail.com> 
>>>>>	Attilio Rao <attilio@freebsd.org> wrote:
> 2009/7/23 NAKAJI Hiroyuki <nakaji@jp.freebsd.org>:
> >>>>>> In <4A667469.1080805@gmail.com>
> >>>>>>   "C. C. Tang" <hiyorin@gmail.com> wrote:
> >> > Could that one (on i386) be related?
> >> > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/134584
> >> >
> >
> >> I have no idea about it but I can tell the difference...
> >> My machine panic randomly rather than on shutdown and I remembered
> >> that it failed to write core dump. It also failed to reboot
> >> automatically..
> >
> > I also have trouble like yours.
> > http://lists.freebsd.org/pipermail/freebsd-stable/2009-June/050526.html
> >
> > I've heard from Attilio Rao that he had found the problem and is working
> > on it.

> Your problem should be linked to a well known deadlock in the VM. kib@
> and jeff@ were alredy working on a patch for that so I just passed
> them the ball.

Oops. Thanks for correction. I'm ready to test the patch.
-- 
NAKAJI Hiroyuki
From avg at icyb.net.ua  Thu Jul 23 15:24:59 2009
From: avg at icyb.net.ua (Andriy Gapon)
Date: Thu Jul 23 15:25:05 2009
Subject: SCSI device not created upon a CF card plug in
In-Reply-To: <20090723141440.A69EF1CC0B@ptavv.es.net>
References: <20090723055317.GA72627@svzserv.kemerovo.su>
	<20090723141440.A69EF1CC0B@ptavv.es.net>
Message-ID: <4A6880A1.3010003@icyb.net.ua>

on 23/07/2009 17:14 Kevin Oberman said the following:
> If Linux detects media insertion instantly or Windows detects media
> insertion instantly (which I can confirm), there is some signal
> available, so looking at the Linux driver should provide a clue as to
> what to look for and that can be added to the FreeBSD umass driver. It
> would be a very desirable addition, but I am not volunteering as I
> currently don't use such devices. (And, no one would like the terrible
> code I would write, anyway.)

Just a note of caution: human "instant" is different from "computer instant".
If OS driver polls, say, every 0.2 seconds, you won't be able to tell the difference.

-- 
Andriy Gapon
From avg at icyb.net.ua  Thu Jul 23 15:41:43 2009
From: avg at icyb.net.ua (Andriy Gapon)
Date: Thu Jul 23 15:41:52 2009
Subject: SCSI device not created upon a CF card plug in
In-Reply-To: <20090723153338.GA31463@cesium.hyperfine.info>
References: <20090723055317.GA72627@svzserv.kemerovo.su>
	<20090723141440.A69EF1CC0B@ptavv.es.net>
	<4A6880A1.3010003@icyb.net.ua>
	<20090723153338.GA31463@cesium.hyperfine.info>
Message-ID: <4A6884A0.5000906@icyb.net.ua>

on 23/07/2009 18:33 Peter C. Lai said the following:
> GEOM should pick up the state change, but the bug may continue to exist
> because the CF reader is tagged as a storage device with invalid media
> when umass attaches to it on startup; there wasn't a really good way to
> actually enumerate the slice table upon insertion because the device
> does not send a disconnect/reconnect to the bus when you insert the
> card. At the time, the workaround was to tickle the device by attempting
> a mount against the whole disk, then the slice table will be enumerated.

It definitely doesn't do disconnect/reconnect, the question is does it send other
kind of notification on media insertion/change?

> Example, CF card reader on boot will be picked up as /dev/da4
> You insert card, no state change can be detected because the device
> doesn't get reset on the bus.
> mount /dev/da0 /mnt <-- will fail for obvious reasons, but now slices
> are enumerated
> mount /dev/da0s1f /mnt/mycfcard <-- ok

$ true > /dev/da0
looks cleaner and is safer way to trigger the re-tasting.
Still, this is a sub-case of polling.

-- 
Andriy Gapon
From peter at simons-rock.edu  Thu Jul 23 15:59:01 2009
From: peter at simons-rock.edu (Peter C. Lai)
Date: Thu Jul 23 15:59:19 2009
Subject: SCSI device not created upon a CF card plug in
In-Reply-To: <4A6880A1.3010003@icyb.net.ua>
References: <20090723055317.GA72627@svzserv.kemerovo.su>
	<20090723141440.A69EF1CC0B@ptavv.es.net>
	<4A6880A1.3010003@icyb.net.ua>
Message-ID: <20090723153338.GA31463@cesium.hyperfine.info>

GEOM should pick up the state change, but the bug may continue to exist
because the CF reader is tagged as a storage device with invalid media
when umass attaches to it on startup; there wasn't a really good way to
actually enumerate the slice table upon insertion because the device
does not send a disconnect/reconnect to the bus when you insert the
card. At the time, the workaround was to tickle the device by attempting
a mount against the whole disk, then the slice table will be enumerated.

Example, CF card reader on boot will be picked up as /dev/da4
You insert card, no state change can be detected because the device
doesn't get reset on the bus.
mount /dev/da0 /mnt <-- will fail for obvious reasons, but now slices
are enumerated
mount /dev/da0s1f /mnt/mycfcard <-- ok

On 2009-07-23 06:24:17PM +0300, Andriy Gapon wrote:
> on 23/07/2009 17:14 Kevin Oberman said the following:
> > If Linux detects media insertion instantly or Windows detects media
> > insertion instantly (which I can confirm), there is some signal
> > available, so looking at the Linux driver should provide a clue as to
> > what to look for and that can be added to the FreeBSD umass driver. It
> > would be a very desirable addition, but I am not volunteering as I
> > currently don't use such devices. (And, no one would like the terrible
> > code I would write, anyway.)
> 
> Just a note of caution: human "instant" is different from "computer instant".
> If OS driver polls, say, every 0.2 seconds, you won't be able to tell the difference.
> 
> -- 
> Andriy Gapon
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"

-- 
===========================================================
Peter C. Lai                 | Bard College at Simon's Rock
Systems Administrator        | 84 Alford Rd.
Information Technology Svcs. | Gt. Barrington, MA 01230 USA
peter AT simons-rock.edu     | (413) 528-7428
===========================================================

From bms at incunabulum.net  Thu Jul 23 18:57:38 2009
From: bms at incunabulum.net (Bruce Simpson)
Date: Thu Jul 23 18:57:45 2009
Subject: ataraid's revenge! (Was: Re: A nasty ataraid experience.)
In-Reply-To: <46acbb3e-71bc-4cff-93d7-59b48a1a9302@exchange01.ecp.noc>
References: <200901232244.n0NMiRmM098646@lurza.secnetix.de>
	<46acbb3e-71bc-4cff-93d7-59b48a1a9302@exchange01.ecp.noc>
Message-ID: <4A68B2A0.8050509@incunabulum.net>

6 months on, ataraid(4) did it again.

    This time, I was lucky -- I caught in in time, but the damage to the 
filesystem meant having to use fsdb to NULL out the affected inodes; 
mounting read-only, tarring, and untarring across the network, after a 
newfs, let me save the affected partition.
    All I was doing at the time was srm'ing a few sensitive files; all 
the processes wedged in WCHAN getblk. It seems ataraid(4) is not robust 
against temporary drive/controller problems. The SMART logs on the 
affected array drives all check out just fine, there are no bad block 
remaps.

So, time to either buy a hardware RAID controller, or move to ZFS...
From bms at incunabulum.net  Thu Jul 23 18:59:14 2009
From: bms at incunabulum.net (Bruce Simpson)
Date: Thu Jul 23 18:59:20 2009
Subject: SCSI device not created upon a CF card plug in
In-Reply-To: <20090723055317.GA72627@svzserv.kemerovo.su>
References: <20090722022027.12059.qmail@us1.tomahawkonline.net>	<20090722142033.GA13316@svzserv.kemerovo.su>	<20090723001338.27858.qmail@us1.tomahawkonline.net>	<20090723035900.GA67095@svzserv.kemerovo.su>	<20090723021418.29042.qmail@us1.tomahawkonline.net>
	<20090723055317.GA72627@svzserv.kemerovo.su>
Message-ID: <4A68B2FD.5090807@incunabulum.net>

Eugene Grosbein wrote:
> On Thu, Jul 23, 2009 at 10:14:18AM +0800, Sagara Wijetunga wrote
>> If you conversant in this area, could you help us to identify what is/are 
>> the exact function/s in which program/s to look into identify the media 
>> insertion activity, so that we can generate relevant devd event. 
>>     
>
> No, I'm not. In your position I would study the device specs -
> does it generate hardware event in case of media change in first place?
>
> If yes, I'd read sources of umass driver to see how it generates events
> for single flash device and add such event for reader's media change.
>   

rwatson@ has or has had a patch to do something like this.

It is complicated by the fact that GEOM and NEWBUS don't necessarily 
talk to each other directly.

I agree something needs to be done about removable volume management in 
FreeBSD.

cheers,
BMS
From scf at FreeBSD.org  Thu Jul 23 20:42:49 2009
From: scf at FreeBSD.org (Sean C. Farley)
Date: Thu Jul 23 20:42:56 2009
Subject: ataraid's revenge! (Was: Re: A nasty ataraid experience.)
In-Reply-To: <4A68B2A0.8050509@incunabulum.net>
References: <200901232244.n0NMiRmM098646@lurza.secnetix.de>
	<46acbb3e-71bc-4cff-93d7-59b48a1a9302@exchange01.ecp.noc>
	<4A68B2A0.8050509@incunabulum.net>
Message-ID: <alpine.BSF.2.00.0907231536350.78159@thor.farley.org>

On Thu, 23 Jul 2009, Bruce Simpson wrote:

> 6 months on, ataraid(4) did it again.
>
>   This time, I was lucky -- I caught in in time, but the damage to the 
> filesystem meant having to use fsdb to NULL out the affected inodes; 
> mounting read-only, tarring, and untarring across the network, after a 
> newfs, let me save the affected partition.
>   All I was doing at the time was srm'ing a few sensitive files; all 
> the processes wedged in WCHAN getblk. It seems ataraid(4) is not 
> robust against temporary drive/controller problems. The SMART logs on 
> the affected array drives all check out just fine, there are no bad 
> block remaps.
>
> So, time to either buy a hardware RAID controller, or move to ZFS...

Out of fear of what ataraid may do to me especially with Intel 
MatrixRAID[1], I switched to using gmirror awhile back, and it has 
worked well.  When I buy some new drives soon, I am considering using 
gvinum with 8.0, but I need to find out more.

Anyone know if I can boot off of a gvinum partition and/or how it works 
(or does not) with various label schemes?

Sean
   1. http://wiki.freebsd.org/JeremyChadwick/ATA_issues_and_troubleshooting
-- 
scf@FreeBSD.org
From grarpamp at gmail.com  Thu Jul 23 20:45:57 2009
From: grarpamp at gmail.com (grarpamp)
Date: Thu Jul 23 20:46:04 2009
Subject: MAKE_DVD=1 make release
Message-ID: <d2e731a10907231345s58f8e9deid509a1e4ea0dfd13@mail.gmail.com>

Oops, DVD is made by default.
I was reading '.if defined(MAKE_DVD)' as 'if not null', not 'if defined'.
I retract this errant report :)
The one about NO_FSCHG is still good though.
From rick-freebsd2008 at kiwi-computer.com  Thu Jul 23 23:24:45 2009
From: rick-freebsd2008 at kiwi-computer.com (Rick C. Petty)
Date: Thu Jul 23 23:24:52 2009
Subject: ataraid's revenge! (Was: Re: A nasty ataraid experience.)
In-Reply-To: <alpine.BSF.2.00.0907231536350.78159@thor.farley.org>
References: <200901232244.n0NMiRmM098646@lurza.secnetix.de>
	<46acbb3e-71bc-4cff-93d7-59b48a1a9302@exchange01.ecp.noc>
	<4A68B2A0.8050509@incunabulum.net>
	<alpine.BSF.2.00.0907231536350.78159@thor.farley.org>
Message-ID: <20090723232443.GA72486@keira.kiwi-computer.com>

This question should have been directed to freebsd-geom.

On Thu, Jul 23, 2009 at 03:42:47PM -0500, Sean C. Farley wrote:
> 
> Anyone know if I can boot off of a gvinum partition and/or how it works 
> (or does not) with various label schemes?

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/vinum-root.html

There are some downsides.  First of all, when you mount your root partition
under vinum, you can't unload the geom_vinum module (for obvious reasons).
If you decide to relocate volumes in the future, you won't be able to
remove the disks from the vinum.  The reason is because you're not allowed
to change the bsdlabel if there's a vinum slice while vinum is loaded, and
you cannot remove a "device" from vinum even if it has no subdisks.  I know
lulf@ was looking into the second part.

I used to do this on all my machines.  Sometime soon after 7.1-release, I
noticed a significant slowdown in disk performance, perhaps due to disk
scheduling.  Basically while any moderate I/O hit one gvinum volume, all
other I/O on that disk was essentially suspended until the the heavier I/O
completed.  What this meant was that if I did an rsync to or from a volume
whose subdisk resided on the same physical disk as my root and /usr
partitions, I could not run any commands until the rsync finished or was
killed (with control-C, since I couldn't even get a "killall" to execute).
After that I switched all my machines to use gmirror which helped slightly.
During that switch is when I discovered you need to be pretty clever to go
away from "vinum root".

I don't mean to say not to use gvinum.  I put a lot of time into it,
submitted some patches, and did a lot of testing with Ulf's deltas.  There
were still a couple of bugs when I stopped using it, but that doesn't mean
they won't be fixed by 8.0.  I just couldn't deal with the I/O performance
issues which I was never able to track down.  I need my workstations to be
responsive while I'm rsyncing stuff around, and with 4 cores and 8 GB of
RAM, I expected it to behave better.  YMMV.

FYI, the trick I used when migrating mirrors in vinum to gmirror:
1). Pick one disk to convert to gmirror first.  I'll call this disk0.
2). Remove all subdisks which are attached to the device using disk0.
3). Reboot into single-user with vinum unloaded, specifying the raw device
root (from disk1) instead of /dev/gvinum/root-volume.
4). Wipe sector 8 of the vinum slice on disk0.
5). Create a gmirror with disk0, re-bsdlabel, create new filesystems, etc.
6). Load geom_vinum kernel module.  This may panic the kernel.  If so,
reboot normally using the vinum root volume.
7). Mount the new filesystems.
8). Mount the volumes you want moved to the mirror and rsync them over to
the filesystems mounted on disk0.
9). Unmount all vinum volumes and try to unload the geom_vinum module.  If
this panics the kernel, or if there was a panic in step 6, you'll need to
reboot into single-user again with geom_vinum unloaded.
10). Wipe sector 8 of the vinum slick on disk1.
11). Add disk1 to the gmirror, which should start a sync.
12). Load the geom_vinum module again, if you have other volumes not part
of this mirror.  If this panics the kernel, or if the kernel panicked after
step 11, a normal restart might be successful.

-- Rick C. Petty
From mike at sentex.net  Fri Jul 24 01:02:53 2009
From: mike at sentex.net (Mike Tancsa)
Date: Fri Jul 24 01:03:03 2009
Subject: ataraid's revenge! (Was: Re: A nasty ataraid experience.)
In-Reply-To: <4A68B2A0.8050509@incunabulum.net>
References: <200901232244.n0NMiRmM098646@lurza.secnetix.de>
	<46acbb3e-71bc-4cff-93d7-59b48a1a9302@exchange01.ecp.noc>
	<4A68B2A0.8050509@incunabulum.net>
Message-ID: <200907240100.n6O10693094691@lava.sentex.ca>

At 02:57 PM 7/23/2009, Bruce Simpson wrote:

>So, time to either buy a hardware RAID controller, or move to ZFS...

I have gone through 4 bad disk replacements with ZFS (one totally 
dead, 3 throwing numerous errors), and numerous replacements with 
various 3ware and areca controllers.  But so far so good with ZFS.

         ---Mike



--------------------------------------------------------------------
Mike Tancsa,                                      tel +1 519 651 3400
Sentex Communications,                            mike@sentex.net
Providing Internet since 1994                    www.sentex.net
Cambridge, Ontario Canada                         www.sentex.net/mike

From doconnor at gsoft.com.au  Fri Jul 24 07:28:56 2009
From: doconnor at gsoft.com.au (Daniel O'Connor)
Date: Fri Jul 24 07:29:03 2009
Subject: HEADS-UP: Shared Library Versions bumped...
In-Reply-To: <200907220814.38246.jhb@freebsd.org>
References: <1248027417.14210.110.camel@neo.cse.buffalo.edu>
	<20090721215201.GA61999@troutmask.apl.washington.edu>
	<200907220814.38246.jhb@freebsd.org>
Message-ID: <200907241625.16312.doconnor@gsoft.com.au>

On Wed, 22 Jul 2009, John Baldwin wrote:
> > How many of those 800 ports are actually necessary and used?
> > It would be better to get generate a complete list of your
> > installed ports, use pkg_deinstall or pkg_delete to remove
> > all ports, and then selectively re-install ports that are
> > actually used.
>
> Xorg takes up ~200 ports alone (not including dependencies like perl,
> etc.) since the Xorg decided release engineering was too hard.  Throw
> in things like KDE, OOo, Firefox, etc. for a desktop and you can get
> a fairly high package count. :-/

Ooh I only have 1315 on mine, but a 1.4GHz Pentium-M is pretty slow 
these days :(

Perhaps there needs to be a psuedo port for 'base' (or a few) so that 
you can easily determine if you have already upgraded something against 
the new base you installed.

Certainly I find it difficult to leave my laptop on for long enough to 
recompile everything when I upgrade -current (since I actually use it 
for work), and portupgrade -fa has no way to tell if it's already done 
something. If there were pseudo base ports you could tell it to force 
upgrade everything that depends on the old base port and it would DTRT.

I, of course, have no patches for such a thing :)

I've deleted /usr/local & /var/db/pkg in the past, it can be very 
therapeutic :) However it is not so good when your mp3 collection is 
mounted on /usr/local/mp3 and you forgot to unmount it first.. :(
-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: This is a digitally signed message part.
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090724/b9bb018a/attachment.pgp
From mel.flynn+fbsd.current at mailing.thruhere.net  Fri Jul 24 07:52:39 2009
From: mel.flynn+fbsd.current at mailing.thruhere.net (Mel Flynn)
Date: Fri Jul 24 07:52:46 2009
Subject: HEADS-UP: Shared Library Versions bumped...
In-Reply-To: <200907241625.16312.doconnor@gsoft.com.au>
References: <1248027417.14210.110.camel@neo.cse.buffalo.edu>
	<200907220814.38246.jhb@freebsd.org>
	<200907241625.16312.doconnor@gsoft.com.au>
Message-ID: <200907232335.54973.mel.flynn+fbsd.current@mailing.thruhere.net>

On Thursday 23 July 2009 22:55:07 Daniel O'Connor wrote:
> On Wed, 22 Jul 2009, John Baldwin wrote:
> > > How many of those 800 ports are actually necessary and used?
> > > It would be better to get generate a complete list of your
> > > installed ports, use pkg_deinstall or pkg_delete to remove
> > > all ports, and then selectively re-install ports that are
> > > actually used.
> >
> > Xorg takes up ~200 ports alone (not including dependencies like perl,
> > etc.) since the Xorg decided release engineering was too hard.  Throw
> > in things like KDE, OOo, Firefox, etc. for a desktop and you can get
> > a fairly high package count. :-/
>
> Ooh I only have 1315 on mine, but a 1.4GHz Pentium-M is pretty slow
> these days :(
>
> Perhaps there needs to be a psuedo port for 'base' (or a few) so that
> you can easily determine if you have already upgraded something against
> the new base you installed.
>
> Certainly I find it difficult to leave my laptop on for long enough to
> recompile everything when I upgrade -current (since I actually use it
> for work), and portupgrade -fa has no way to tell if it's already done
> something. If there were pseudo base ports you could tell it to force
> upgrade everything that depends on the old base port and it would DTRT.

I wrapped portmaster, since -af has the same problem when something screws the 
build (mostly plist problems and $me wanting backup packages, but also 
classics like using sudo as PM_SU_CMD and trying to reinstall it).

Basically, I made a list of all the installed ports and sorted dep order, then 
called portmaster -u for every port and if successful put an empty file 
+PM_DONE in /var/db/pkg/<pkgname>/. On a restart the ports containing a 
+PM_DONE file are skipped.

If the entire process finishes successfully, all +PM_DONE files are removed. I 
briefly looked into building it into portmaster, but that looked to take 
longer then I had time for. The main loop is at the bottom, perhaps Doug likes 
the idea and has the time to integrate it.

> I, of course, have no patches for such a thing :)
>
> I've deleted /usr/local & /var/db/pkg in the past, it can be very
> therapeutic :) However it is not so good when your mp3 collection is
> mounted on /usr/local/mp3 and you forgot to unmount it first.. :(

Or your websites in /usr/local/www, your database in /usr/local/pgsql or your 
squid conf and cache in /usr/local/squid. Especially when pkg_delete -af does 
the right thing and leaves all this in tact, I don't see the value of rm -rf 
/usr/local, other then a few minutes on a process that's likely going to be 
several hours or days.
-- 
Mel

mark_done()
{          
        local _name
        _name=$1   
        if test -d ${PKG_DBDIR}/${_name}; then
                ${SUDO} ${TOUCH} ${PKG_DBDIR}/${_name}/+PM_DONE
        else                                                   
                return 1;                                      
        fi                                                     
        return 0;                                              
}                                                              

for origin in ${LIST}; do
        pkgname=$(make -C ${PORTSDIR}/${origin} -V PKGNAME)
        if test -f ${PKG_DBDIR}/${pkgname}/+PM_DONE; then
                echo "Already done: ${pkgname} (${LOOP}/${TOTAL})"
        else
                echo "===> Building ${pkgname}"
                portmaster -u ${PORTSDIR}/${origin}
                if test $? -eq 0; then
                        mark_done ${pkgname} || safe_abort
                else
                        FAILED=$((${FAILED} + 1))
                        echo "Failed, continue? [n]"
                        read CONT
                        case "${CONT}" in
                                [yY]|[yY][eE]|[yY][eE][sS])
                                echo "===> Marking state as done"
                                mark_done ${pkgname} || safe_abort
                                ;;
                                *) break;;
                        esac
                fi
        fi
done

if test ${FAILED} -eq 0; then
        echo "===> Removing state files"
        for FILE in ${PKG_DBDIR}/*/+PM_DONE; do
                ${SUDO} /bin/rm ${FILE}
        done
        echo "===> Removing origin list"
        /bin/rm ${LISTFILE}
fi

From gavin at FreeBSD.org  Fri Jul 24 08:30:12 2009
From: gavin at FreeBSD.org (Gavin Atkinson)
Date: Fri Jul 24 08:30:19 2009
Subject: ataraid's revenge! (Was: Re: A nasty ataraid experience.)
In-Reply-To: <4A68B2A0.8050509@incunabulum.net>
References: <200901232244.n0NMiRmM098646@lurza.secnetix.de>
	<46acbb3e-71bc-4cff-93d7-59b48a1a9302@exchange01.ecp.noc>
	<4A68B2A0.8050509@incunabulum.net>
Message-ID: <1248424208.50198.2.camel@buffy.york.ac.uk>

On Thu, 2009-07-23 at 19:57 +0100, Bruce Simpson wrote:
> 6 months on, ataraid(4) did it again.

Which ataraid(4) controller is this?  Seeing a verbose dmesg would help.
There are several patches in the PR database for ataraid problems, it
would be worth having a look.

Gavin

From pluknet at gmail.com  Fri Jul 24 13:11:14 2009
From: pluknet at gmail.com (pluknet)
Date: Fri Jul 24 13:11:22 2009
Subject: [geom] page fault in g_mbr_config()
Message-ID: <a31046fc0907240611g7e5c086ft9a7f5d0e5e4dc7e0@mail.gmail.com>

Hi.

I got a panic while performing a repetitive  'fdisk -BI aacd0',
where aacd0 is a disk on aac0: <IBM ServeRAID-8k>.
This means that the command was issued after filesystems
were already created on aacd (after the first fdisk -BI aacd0
iteration), and are in umount'ed state.

This is on 7.2-R, amd64. Config is a GENERIC plus ddb, carp, ipfw, quota.

Fatal trap 12: page fault while in kernel mode
cpuid = 5; apic id = 05
fault virtual address   = 0x20
fault code              = supervisor read data, page not present
instruction pointer     = 0x8:0xffffffff804cc554
stack pointer           = 0x10:0xfffffffe80079b80
frame pointer           = 0x10:0xfffffffe80079bd0
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 2 (g_event)
[thread pid 2 tid 100013 ]
Stopped at      g_mbr_config+0x64:      movq    0x20(%rax),%r15
db> bt
Tracing pid 2 tid 100013 td 0xffffff000144da50
g_mbr_config() at g_mbr_config+0x64
g_run_events() at g_run_events+0x1b8
g_event_procbody() at g_event_procbody+0x57
fork_exit() at fork_exit+0x11f
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp = 0xfffffffe80079d30, rbp = 0 ---


-- 
wbr,
pluknet
From pluknet at gmail.com  Fri Jul 24 13:16:36 2009
From: pluknet at gmail.com (pluknet)
Date: Fri Jul 24 13:16:42 2009
Subject: [geom] page fault in g_mbr_config()
In-Reply-To: <a31046fc0907240611g7e5c086ft9a7f5d0e5e4dc7e0@mail.gmail.com>
References: <a31046fc0907240611g7e5c086ft9a7f5d0e5e4dc7e0@mail.gmail.com>
Message-ID: <a31046fc0907240616n636dbbeam7ec2a3230c9562e4@mail.gmail.com>

2009/7/24 pluknet <pluknet@gmail.com>:
> Hi.
>
> I got a panic while performing a repetitive ?'fdisk -BI aacd0',
> where aacd0 is a disk on aac0: <IBM ServeRAID-8k>.
> This means that the command was issued after filesystems
> were already created on aacd (after the first fdisk -BI aacd0
> iteration), and are in umount'ed state.
>
> This is on 7.2-R, amd64. Config is a GENERIC plus ddb, carp, ipfw, quota.
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 5; apic id = 05
> fault virtual address ? = 0x20
> fault code ? ? ? ? ? ? ?= supervisor read data, page not present
> instruction pointer ? ? = 0x8:0xffffffff804cc554
> stack pointer ? ? ? ? ? = 0x10:0xfffffffe80079b80
> frame pointer ? ? ? ? ? = 0x10:0xfffffffe80079bd0
> code segment ? ? ? ? ? ?= base 0x0, limit 0xfffff, type 0x1b
> ? ? ? ? ? ? ? ? ? ? ? ?= DPL 0, pres 1, long 1, def32 0, gran 1
> processor eflags ? ? ? ?= interrupt enabled, resume, IOPL = 0
> current process ? ? ? ? = 2 (g_event)
> [thread pid 2 tid 100013 ]
> Stopped at ? ? ?g_mbr_config+0x64: ? ? ?movq ? ?0x20(%rax),%r15
> db> bt
> Tracing pid 2 tid 100013 td 0xffffff000144da50
> g_mbr_config() at g_mbr_config+0x64
> g_run_events() at g_run_events+0x1b8
> g_event_procbody() at g_event_procbody+0x57
> fork_exit() at fork_exit+0x11f
> fork_trampoline() at fork_trampoline+0xe
> --- trap 0, rip = 0, rsp = 0xfffffffe80079d30, rbp = 0 ---

And, of course...

db> show proc 818
Process 818 (fdisk) at 0xffffff0004ed1000:
 state: NORMAL
 uid: 0  gids: 0, 0, 5
 parent: pid 814 at 0xffffff00045c0478
 ABI: FreeBSD ELF64
 arguments: fdisk
 threads: 1
100169                   D       g_waitfo 0xffffff0004ec9100 fdisk
db> bt 818
Tracing pid 818 tid 100169 td 0xffffff0004fbf6e0
sched_switch() at sched_switch+0x1fe
mi_switch() at mi_switch+0x18e
sleepq_timedwait() at sleepq_timedwait+0x31
_sleep() at _sleep+0x354
g_waitfor_event() at g_waitfor_event+0x9a
g_ctl_ioctl() at g_ctl_ioctl+0x2df
giant_ioctl() at giant_ioctl+0x7d
devfs_ioctl_f() at devfs_ioctl_f+0x77
kern_ioctl() at kern_ioctl+0xa2
ioctl() at ioctl+0xf9
syscall() at syscall+0x256
Xfast_syscall() at Xfast_syscall+0xab
--- syscall (54, FreeBSD ELF64, ioctl), rip = 0x8008200ec, rsp =
0x7fffffffe1d8, rbp = 0x4 ---

-- 
wbr,
pluknet
From kutulu at kutulu.org  Fri Jul 24 21:08:16 2009
From: kutulu at kutulu.org (Mike Edenfield)
Date: Fri Jul 24 21:08:23 2009
Subject: Torrent clients bring pf-based firewall to its knees...?
Message-ID: <4A6A1FEB.9030001@kutulu.org>

I've recently begun running a torrent client after hours on a PC sitting 
behind our firewall (7.2-STABLE using pf).  I have added a 'rdr' rule to 
redirect incoming traffic to the client PC from the firewall, and as far 
as the client is concerned everything is fine.

However, after a short period of torrent activity, the machine running 
the firewall becomes extremely slow and lagged for all network traffic, 
but appears to be operating fine locally.  Remote connections via ssh 
become extremely unresponsive, and eventually connections start timing 
out, but when logged in at the console, there doesn't appear to be any 
problem.  Running tcpdump does not show nusually high volume of traffic, 
no more than I see during normal activity during the day.  The volume 
and length of connections doesn't seem to matter much -- trying to copy 
a BSD or Linux DVD with hundreds of connections breaks just as quickly 
as much smaller torrents with a handful of peers.

I know there are some cheap NAT-ing routers that get in trouble with 
torrents because of the heavy volume of state rules required, but I've 
never heard of anything like that being present in pf.  And I've used 
torrent clients at home behind a pf firewall with no issues, but not on 
this specific version of the FreeBSD.

I've tried shutting down the torrent client, clearing out the state and 
nat rules with pfctl, adding drop rules to reject the torrent traffic, 
and even bringing the network adapter down completely, but only a 
physical reboot (combined with not running the client ever again) seems 
to solve anything.

Has anyone experienced this kind of problem before?  Or alternatively, 
is there some way besides tcpdump and top (neither of which show 
anything unusual) that I can tell what exactly the machine is doing 
that's causing the network lag?

--Mike
From peter at simons-rock.edu  Fri Jul 24 21:18:15 2009
From: peter at simons-rock.edu (Peter C. Lai)
Date: Fri Jul 24 21:18:23 2009
Subject: Torrent clients bring pf-based firewall to its knees...?
In-Reply-To: <4A6A1FEB.9030001@kutulu.org>
References: <4A6A1FEB.9030001@kutulu.org>
Message-ID: <20090724211812.GI31463@cesium.hyperfine.info>

If only a reboot solves the problem sounds like a kernel problem?
mbuf leakage?

On 2009-07-24 04:56:11PM -0400, Mike Edenfield wrote:
> I've recently begun running a torrent client after hours on a PC sitting 
> behind our firewall (7.2-STABLE using pf).  I have added a 'rdr' rule to 
> redirect incoming traffic to the client PC from the firewall, and as far as 
> the client is concerned everything is fine.
> 
> However, after a short period of torrent activity, the machine running the 
> firewall becomes extremely slow and lagged for all network traffic, but 
> appears to be operating fine locally.  Remote connections via ssh become 
> extremely unresponsive, and eventually connections start timing out, but 
> when logged in at the console, there doesn't appear to be any problem.  
> Running tcpdump does not show nusually high volume of traffic, no more than 
> I see during normal activity during the day.  The volume and length of 
> connections doesn't seem to matter much -- trying to copy a BSD or Linux 
> DVD with hundreds of connections breaks just as quickly as much smaller 
> torrents with a handful of peers.
> 
> I know there are some cheap NAT-ing routers that get in trouble with 
> torrents because of the heavy volume of state rules required, but I've 
> never heard of anything like that being present in pf.  And I've used 
> torrent clients at home behind a pf firewall with no issues, but not on 
> this specific version of the FreeBSD.
> 
> I've tried shutting down the torrent client, clearing out the state and nat 
> rules with pfctl, adding drop rules to reject the torrent traffic, and even 
> bringing the network adapter down completely, but only a physical reboot 
> (combined with not running the client ever again) seems to solve anything.
> 
> Has anyone experienced this kind of problem before?  Or alternatively, is 
> there some way besides tcpdump and top (neither of which show anything 
> unusual) that I can tell what exactly the machine is doing that's causing 
> the network lag?
> 
> --Mike
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"

-- 
===========================================================
Peter C. Lai                 | Bard College at Simon's Rock
Systems Administrator        | 84 Alford Rd.
Information Technology Svcs. | Gt. Barrington, MA 01230 USA
peter AT simons-rock.edu     | (413) 528-7428
===========================================================

From tinderbox at freebsd.org  Fri Jul 24 23:38:29 2009
From: tinderbox at freebsd.org (FreeBSD Tinderbox)
Date: Fri Jul 24 23:38:36 2009
Subject: [releng_7 tinderbox] failure on amd64/amd64
Message-ID: <20090724232014.EA2F11B5060@freebsd-stable.sentex.ca>

TB --- 2009-07-24 21:39:39 - tinderbox 2.6 running on freebsd-stable.sentex.ca
TB --- 2009-07-24 21:39:39 - starting RELENG_7 tinderbox run for amd64/amd64
TB --- 2009-07-24 21:39:39 - cleaning the object tree
TB --- 2009-07-24 21:40:06 - cvsupping the source tree
TB --- 2009-07-24 21:40:06 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/amd64/amd64/supfile
TB --- 2009-07-24 21:40:15 - building world
TB --- 2009-07-24 21:40:15 - MAKEOBJDIRPREFIX=/obj
TB --- 2009-07-24 21:40:15 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2009-07-24 21:40:15 - TARGET=amd64
TB --- 2009-07-24 21:40:15 - TARGET_ARCH=amd64
TB --- 2009-07-24 21:40:15 - TZ=UTC
TB --- 2009-07-24 21:40:15 - __MAKE_CONF=/dev/null
TB --- 2009-07-24 21:40:15 - cd /src
TB --- 2009-07-24 21:40:15 - /usr/bin/make -B buildworld
>>> World build started on Fri Jul 24 21:40:16 UTC 2009
>>> Rebuilding the temporary build tree
>>> stage 1.1: legacy release compatibility shims
>>> stage 1.2: bootstrap tools
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3: cross tools
>>> stage 4.1: building includes
>>> stage 4.2: building libraries
>>> stage 4.3: make dependencies
>>> stage 4.4: building everything
>>> stage 5.1: building 32 bit shim libraries
>>> World build completed on Fri Jul 24 23:10:05 UTC 2009
TB --- 2009-07-24 23:10:05 - generating LINT kernel config
TB --- 2009-07-24 23:10:05 - cd /src/sys/amd64/conf
TB --- 2009-07-24 23:10:05 - /usr/bin/make -B LINT
TB --- 2009-07-24 23:10:05 - building LINT kernel
TB --- 2009-07-24 23:10:05 - MAKEOBJDIRPREFIX=/obj
TB --- 2009-07-24 23:10:05 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2009-07-24 23:10:05 - TARGET=amd64
TB --- 2009-07-24 23:10:05 - TARGET_ARCH=amd64
TB --- 2009-07-24 23:10:05 - TZ=UTC
TB --- 2009-07-24 23:10:05 - __MAKE_CONF=/dev/null
TB --- 2009-07-24 23:10:05 - cd /src
TB --- 2009-07-24 23:10:05 - /usr/bin/make -B buildkernel KERNCONF=LINT
>>> Kernel build for LINT started on Fri Jul 24 23:10:05 UTC 2009
>>> stage 1: configuring the kernel
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3.1: making dependencies
>>> stage 3.2: building everything
[...]
cc -c -O2 -frename-registers -pipe -fno-strict-aliasing  -std=c99  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc  -I. -I/src/sys -I/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 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone  -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow  -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/kern/inflate.c
cc -c -O2 -frename-registers -pipe -fno-strict-aliasing  -std=c99  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc  -I. -I/src/sys -I/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 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone  -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow  -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/kern/init_main.c
cc1: warnings being treated as errors
In file included from /src/sys/kern/init_main.c:71:
/src/sys/sys/sysproto.h:1705: warning: redundant redeclaration of 'lkmnosys'
/src/sys/sys/sysent.h:164: warning: previous declaration of 'lkmnosys' was here
/src/sys/sys/sysproto.h:1802: warning: redundant redeclaration of 'lkmressys'
/src/sys/sys/sysent.h:165: warning: previous declaration of 'lkmressys' was here
*** Error code 1

Stop in /obj/amd64/src/sys/LINT.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
TB --- 2009-07-24 23:20:14 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2009-07-24 23:20:14 - ERROR: failed to build lint kernel
TB --- 2009-07-24 23:20:14 - 5024.71 user 564.53 system 6035.52 real


http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-amd64-amd64.full
From rizzo at iet.unipi.it  Sat Jul 25 01:28:48 2009
From: rizzo at iet.unipi.it (Luigi Rizzo)
Date: Sat Jul 25 01:28:54 2009
Subject: status of flash9/flash10 support in RELENG_7 ?
Message-ID: <20090725013500.GC62402@onelab2.iet.unipi.it>

Does anyone know what is the status of flash9 or flash10 in RELENG_7 ?
Following the thread of a couple of months ago, i tried to:
- remove all linux-* ports
- set the following in /etc/make.conf
	OVERRIDE_LINUX_BASE_PORT=f8
	OVERRIDE_LINUX_NONBASE_PORTS=f8
- set the following in /etc/sysctl.conf
	compat.linux.osrelease=2.6.16
- set the following in /etc/fstab
	linproc /usr/compat/linux/proc  linprocfs       rw 0 0
- reinstall linux_base-f8-8_11
- reinstall linux-flashplugin-10.0r22 (which in turn brings in the
  relevant linux-f8-* ports)

- also install nspluginwrapper and create a firefox plugin
- upgrade firefox to firefox-3.5,1 (native), just in case
- run firefox with "limit stacksize 4megabytes" (or variants)
  as recommended to avoid npviewer growing/not dying

This was done on 3 different machines (one laptop with a centrino,
2 desktops with AMD X2 dual core running in i386 mode) with mixed
[in]success. On one machine thing started working well, but on the
other two they did not (the various packages were of course slightly
disaligned) and while trying to replicate the configuration i also
broke the good one without figuring out why.
Symptoms are that on certain sites or actions (e.g. switch to full
screen on youtube videos) i get firefox freezing like this

22381 luigi  13  96    0 82580K 57484K ucond   1   0:00  0.20% firefox-bin
22413 luigi   1  97    0 72920K 33448K futex   1   0:00  0.20% npviewer.bin
22414 luigi   1  97    0 72920K 33448K futex   1   0:00  0.20% npviewer.bin

and recovering control (but no video) after 10+seconds

I also get a lot of the following weak_unref warnings with various addresses

(firefox-bin:22381): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0x297ba9f0(0x2a10d110)

(but not sure how related is this, because it happens even without a
flash plugin).

I have also tried flash9 instead of flash10, o fc10 instead of fc8,
all with similar results.

Is there a recipe for a working flas9 or flash10 operation ?

cheers
luigi
From rivers at dignus.com  Sat Jul 25 02:15:36 2009
From: rivers at dignus.com (Thomas David Rivers)
Date: Sat Jul 25 02:15:43 2009
Subject: Torrent clients bring pf-based firewall to its knees...?
In-Reply-To: <20090724211812.GI31463@cesium.hyperfine.info>
References: <4A6A1FEB.9030001@kutulu.org>
	<20090724211812.GI31463@cesium.hyperfine.info>
Message-ID: <200907250142.n6P1gUQG011090@dave.dignus.com>

Is there a main() function in your program?

Are you building this for LE operation, or with the Systems/C runtime?

If it's Systems/C, are you using the RENT library (and the -frent
option on the compilation?)  If you want to build a non-RENT program
for USS, you can, but you have to set the appropriate environment
varible under USS to execute it; as a USS program is executed 
with the code sections marked READ-ONLY.

	- Dave Rivers -

--
rivers@dignus.com                        Work: (919) 676-0847
Get your mainframe programming tools at http://www.dignus.com
From cliftonr at lava.net  Sat Jul 25 06:35:08 2009
From: cliftonr at lava.net (Clifton Royston)
Date: Sat Jul 25 06:35:15 2009
Subject: Torrent clients bring pf-based firewall to its knees...?
In-Reply-To: <4A6A1FEB.9030001@kutulu.org>
References: <4A6A1FEB.9030001@kutulu.org>
Message-ID: <20090725063505.GA5216@lava.net>

On Fri, Jul 24, 2009 at 04:56:11PM -0400, Mike Edenfield wrote:
> I've recently begun running a torrent client after hours on a PC sitting 
> behind our firewall (7.2-STABLE using pf).  I have added a 'rdr' rule to 
> redirect incoming traffic to the client PC from the firewall, and as far 
> as the client is concerned everything is fine.

FWIW, I don't do torrents a lot, but I've had no problems running the
Vuze/Azureus torrent client behind a pfSense firewall (7.2-based with
pf)
  -- Clifton

-- 
    Clifton Royston  --  cliftonr@iandicomputing.com / cliftonr@lava.net
       President  - I and I Computing * http://www.iandicomputing.com/
 Custom programming, network design, systems and network consulting services
From dchagin at freebsd.org  Sat Jul 25 07:07:25 2009
From: dchagin at freebsd.org (Chagin Dmitry)
Date: Sat Jul 25 07:07:33 2009
Subject: status of flash9/flash10 support in RELENG_7 ?
In-Reply-To: <20090725013500.GC62402@onelab2.iet.unipi.it>
References: <20090725013500.GC62402@onelab2.iet.unipi.it>
Message-ID: <20090725063610.GA74076@dchagin.static.corbina.ru>

On Sat, Jul 25, 2009 at 03:35:00AM +0200, Luigi Rizzo wrote:
> Does anyone know what is the status of flash9 or flash10 in RELENG_7 ?
> Following the thread of a couple of months ago, i tried to:
> - remove all linux-* ports
> - set the following in /etc/make.conf
> 	OVERRIDE_LINUX_BASE_PORT=f8
> 	OVERRIDE_LINUX_NONBASE_PORTS=f8
> - set the following in /etc/sysctl.conf
> 	compat.linux.osrelease=2.6.16
> - set the following in /etc/fstab
> 	linproc /usr/compat/linux/proc  linprocfs       rw 0 0
> - reinstall linux_base-f8-8_11
> - reinstall linux-flashplugin-10.0r22 (which in turn brings in the
>   relevant linux-f8-* ports)
> 
> - also install nspluginwrapper and create a firefox plugin
> - upgrade firefox to firefox-3.5,1 (native), just in case
> - run firefox with "limit stacksize 4megabytes" (or variants)
>   as recommended to avoid npviewer growing/not dying
> 
> This was done on 3 different machines (one laptop with a centrino,
> 2 desktops with AMD X2 dual core running in i386 mode) with mixed
> [in]success. On one machine thing started working well, but on the
> other two they did not (the various packages were of course slightly
> disaligned) and while trying to replicate the configuration i also
> broke the good one without figuring out why.
> Symptoms are that on certain sites or actions (e.g. switch to full
> screen on youtube videos) i get firefox freezing like this
> 
> 22381 luigi  13  96    0 82580K 57484K ucond   1   0:00  0.20% firefox-bin
> 22413 luigi   1  97    0 72920K 33448K futex   1   0:00  0.20% npviewer.bin
> 22414 luigi   1  97    0 72920K 33448K futex   1   0:00  0.20% npviewer.bin
> 
> and recovering control (but no video) after 10+seconds
> 

hi, read:
http://lists.freebsd.org/pipermail/freebsd-emulation/2009-June/006431.html




> I also get a lot of the following weak_unref warnings with various addresses
> 
> (firefox-bin:22381): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0x297ba9f0(0x2a10d110)
> 
> (but not sure how related is this, because it happens even without a
> flash plugin).
> 
> I have also tried flash9 instead of flash10, o fc10 instead of fc8,
> all with similar results.
> 
> Is there a recipe for a working flas9 or flash10 operation ?
> 
> cheers
> luigi
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"

-- 
Have fun!
chd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090725/3a4bacef/attachment.pgp
From blackend at freebsd.org  Sat Jul 25 07:51:55 2009
From: blackend at freebsd.org (Marc Fonvieille)
Date: Sat Jul 25 07:52:02 2009
Subject: status of flash9/flash10 support in RELENG_7 ?
In-Reply-To: <20090725013500.GC62402@onelab2.iet.unipi.it>
References: <20090725013500.GC62402@onelab2.iet.unipi.it>
Message-ID: <20090725073805.GA11455@abigail.blackend.org>

On Sat, Jul 25, 2009 at 03:35:00AM +0200, Luigi Rizzo wrote:
> Does anyone know what is the status of flash9 or flash10 in RELENG_7 ?
> Following the thread of a couple of months ago, i tried to:
> - remove all linux-* ports
> - set the following in /etc/make.conf
> 	OVERRIDE_LINUX_BASE_PORT=f8
> 	OVERRIDE_LINUX_NONBASE_PORTS=f8
> - set the following in /etc/sysctl.conf
> 	compat.linux.osrelease=2.6.16
> - set the following in /etc/fstab
> 	linproc /usr/compat/linux/proc  linprocfs       rw 0 0
> - reinstall linux_base-f8-8_11
> - reinstall linux-flashplugin-10.0r22 (which in turn brings in the
>   relevant linux-f8-* ports)
> 
> - also install nspluginwrapper and create a firefox plugin
> - upgrade firefox to firefox-3.5,1 (native), just in case
> - run firefox with "limit stacksize 4megabytes" (or variants)
>   as recommended to avoid npviewer growing/not dying
> 
> This was done on 3 different machines (one laptop with a centrino,
> 2 desktops with AMD X2 dual core running in i386 mode) with mixed
> [in]success. On one machine thing started working well, but on the
> other two they did not (the various packages were of course slightly
> disaligned) and while trying to replicate the configuration i also
> broke the good one without figuring out why.
> Symptoms are that on certain sites or actions (e.g. switch to full
> screen on youtube videos) i get firefox freezing like this
> 
> 22381 luigi  13  96    0 82580K 57484K ucond   1   0:00  0.20% firefox-bin
> 22413 luigi   1  97    0 72920K 33448K futex   1   0:00  0.20% npviewer.bin
> 22414 luigi   1  97    0 72920K 33448K futex   1   0:00  0.20% npviewer.bin
> 
> and recovering control (but no video) after 10+seconds
> 
> I also get a lot of the following weak_unref warnings with various addresses
> 
> (firefox-bin:22381): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0x297ba9f0(0x2a10d110)
> 
> (but not sure how related is this, because it happens even without a
> flash plugin).
> 
> I have also tried flash9 instead of flash10, o fc10 instead of fc8,
> all with similar results.
> 
> Is there a recipe for a working flas9 or flash10 operation ?
>

The Handbook gives a reliable, i.e. reproductible one, recipe:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/desktop-browsers.html
6.2.3 Firefox and Macromedia? Flash Plugin

for running Flash 9 under 7.X and with default linux_base.

I'm also working on an update for 8.X

-- 
Marc
From avg at icyb.net.ua  Sat Jul 25 08:48:18 2009
From: avg at icyb.net.ua (Andriy Gapon)
Date: Sat Jul 25 08:48:25 2009
Subject: smartctl: Unrecognized command 13
Message-ID: <4A6AC6CD.9090005@icyb.net.ua>


This is stable/7 i386:

$ smartctl -t select,568157535-568159000 /dev/ad10
...
Unrecognized command 13 in ata_command_interface()
Please contact smartmontools-support@lists.sourceforge.net
Error Write Selective Self-Test Log failed: Function not implemented

In smartmontools sources this is command WRITE_LOG.
Is this something that can be patched in smartmontools or does it require
additional support from ata driver?

-- 
Andriy Gapon
From blackend at freebsd.org  Sat Jul 25 10:05:48 2009
From: blackend at freebsd.org (Marc Fonvieille)
Date: Sat Jul 25 10:06:07 2009
Subject: status of flash9/flash10 support in RELENG_7 ?
In-Reply-To: <20090725073805.GA11455@abigail.blackend.org>
References: <20090725013500.GC62402@onelab2.iet.unipi.it>
	<20090725073805.GA11455@abigail.blackend.org>
Message-ID: <20090725100542.GD11455@abigail.blackend.org>

On Sat, Jul 25, 2009 at 09:38:05AM +0200, Marc Fonvieille wrote:
> > 
> > Is there a recipe for a working flas9 or flash10 operation ?
> >
> 
> The Handbook gives a reliable, i.e. reproductible one, recipe:
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/desktop-browsers.html
> 6.2.3 Firefox and Macromedia? Flash Plugin
> 
> for running Flash 9 under 7.X and with default linux_base.
> 
> I'm also working on an update for 8.X
>

I just updated the Handbook for 8.X and Flash (I know it wasn't your
first question but it may help).

-- 
Marc
From rivers at dignus.com  Sat Jul 25 10:14:54 2009
From: rivers at dignus.com (Thomas David Rivers)
Date: Sat Jul 25 10:15:01 2009
Subject: Torrent clients bring pf-based firewall to its knees...?
In-Reply-To: <200907250142.n6P1gUQG011090@dave.dignus.com>
References: <4A6A1FEB.9030001@kutulu.org>
	<20090724211812.GI31463@cesium.hyperfine.info>
	<200907250142.n6P1gUQG011090@dave.dignus.com>
Message-ID: <200907251014.n6PAEnJp012598@dave.dignus.com>

My apologies all,

 This was clearly not  intended for this list :-)

	- Thanks -
	- Dave Rivers -

> 
> Is there a main() function in your program?
> 
> Are you building this for LE operation, or with the Systems/C runtime?
> 
> If it's Systems/C, are you using the RENT library (and the -frent
> option on the compilation?)  If you want to build a non-RENT program
> for USS, you can, but you have to set the appropriate environment
> varible under USS to execute it; as a USS program is executed 
> with the code sections marked READ-ONLY.
> 
> 	- Dave Rivers -
> 
> --
> rivers@dignus.com                        Work: (919) 676-0847
> Get your mainframe programming tools at http://www.dignus.com

--
rivers@dignus.com                        Work: (919) 676-0847
Get your mainframe programming tools at http://www.dignus.com
From rizzo at iet.unipi.it  Sat Jul 25 11:49:12 2009
From: rizzo at iet.unipi.it (Luigi Rizzo)
Date: Sat Jul 25 11:49:20 2009
Subject: status of flash9/flash10 support in RELENG_7 ?
In-Reply-To: <20090725073805.GA11455@abigail.blackend.org>
References: <20090725013500.GC62402@onelab2.iet.unipi.it>
	<20090725073805.GA11455@abigail.blackend.org>
Message-ID: <20090725115525.GA85767@onelab2.iet.unipi.it>

On Sat, Jul 25, 2009 at 09:38:05AM +0200, Marc Fonvieille wrote:
> On Sat, Jul 25, 2009 at 03:35:00AM +0200, Luigi Rizzo wrote:
> > Does anyone know what is the status of flash9 or flash10 in RELENG_7 ?
> > Following the thread of a couple of months ago, i tried to:
> > - remove all linux-* ports
> > - set the following in /etc/make.conf
> > 	OVERRIDE_LINUX_BASE_PORT=f8
> > 	OVERRIDE_LINUX_NONBASE_PORTS=f8
> > - set the following in /etc/sysctl.conf
> > 	compat.linux.osrelease=2.6.16
> > - set the following in /etc/fstab
> > 	linproc /usr/compat/linux/proc  linprocfs       rw 0 0
> > - reinstall linux_base-f8-8_11
> > - reinstall linux-flashplugin-10.0r22 (which in turn brings in the
> >   relevant linux-f8-* ports)
> > 
> > - also install nspluginwrapper and create a firefox plugin
> > - upgrade firefox to firefox-3.5,1 (native), just in case
> > - run firefox with "limit stacksize 4megabytes" (or variants)
> >   as recommended to avoid npviewer growing/not dying
> > 
> > This was done on 3 different machines (one laptop with a centrino,
> > 2 desktops with AMD X2 dual core running in i386 mode) with mixed
> > [in]success. On one machine thing started working well, but on the
> > other two they did not (the various packages were of course slightly
> > disaligned) and while trying to replicate the configuration i also
> > broke the good one without figuring out why.
> > Symptoms are that on certain sites or actions (e.g. switch to full
> > screen on youtube videos) i get firefox freezing like this
> > 
> > 22381 luigi  13  96    0 82580K 57484K ucond   1   0:00  0.20% firefox-bin
> > 22413 luigi   1  97    0 72920K 33448K futex   1   0:00  0.20% npviewer.bin
> > 22414 luigi   1  97    0 72920K 33448K futex   1   0:00  0.20% npviewer.bin
> > 
> > and recovering control (but no video) after 10+seconds
> > 
> > I also get a lot of the following weak_unref warnings with various addresses
> > 
> > (firefox-bin:22381): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0x297ba9f0(0x2a10d110)
> > 
> > (but not sure how related is this, because it happens even without a
> > flash plugin).
> > 
> > I have also tried flash9 instead of flash10, o fc10 instead of fc8,
> > all with similar results.
> > 
> > Is there a recipe for a working flas9 or flash10 operation ?
> >
> 
> The Handbook gives a reliable, i.e. reproductible one, recipe:
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/desktop-browsers.html
> 6.2.3 Firefox and Macromedia? Flash Plugin
> 
> for running Flash 9 under 7.X and with default linux_base.

from what i remember, flash9 with the default linux_base (fc4)
did not work for me (though i don't remember the details).
Are you positive that it is a working configuration on RELENG_7 ?

Especially, fc4 does not support skype (except skype1.2, which however
does not authenticate anymore), so using fc4 is not an option for
me and i suspect desktop users in general.


> I'm also working on an update for 8.X

i see that for 8.x you suggest using fc10, which is also something i
tried on RELENG_7 but had similar symptoms. Is there any known reason
why HEAD and RELENG_7 should be different in terms of linux_base support ?

cheers
luigi
From blackend at freebsd.org  Sat Jul 25 12:37:55 2009
From: blackend at freebsd.org (Marc Fonvieille)
Date: Sat Jul 25 12:38:03 2009
Subject: status of flash9/flash10 support in RELENG_7 ?
In-Reply-To: <20090725115525.GA85767@onelab2.iet.unipi.it>
References: <20090725013500.GC62402@onelab2.iet.unipi.it>
	<20090725073805.GA11455@abigail.blackend.org>
	<20090725115525.GA85767@onelab2.iet.unipi.it>
Message-ID: <20090725123749.GA26505@abigail.blackend.org>

On Sat, Jul 25, 2009 at 01:55:25PM +0200, Luigi Rizzo wrote:
> On Sat, Jul 25, 2009 at 09:38:05AM +0200, Marc Fonvieille wrote:
> > On Sat, Jul 25, 2009 at 03:35:00AM +0200, Luigi Rizzo wrote:
> > 
> > The Handbook gives a reliable, i.e. reproductible one, recipe:
> > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/desktop-browsers.html
> > 6.2.3 Firefox and Macromedia? Flash Plugin
> > 
> > for running Flash 9 under 7.X and with default linux_base.
> 
> from what i remember, flash9 with the default linux_base (fc4)
> did not work for me (though i don't remember the details).
> Are you positive that it is a working configuration on RELENG_7 ?
>

Yes, I did many installations of Flash9 with fc4 and firefox 2 or 3 on
various boxes without any issues.  Since it was reproductible, it's the
recipe I put in the Handbook.

> Especially, fc4 does not support skype (except skype1.2, which however
> does not authenticate anymore), so using fc4 is not an option for
> me and i suspect desktop users in general.
> 

I don't use skype, so I wasn't annoyed.

> 
> > I'm also working on an update for 8.X
> 
> i see that for 8.x you suggest using fc10, which is also something i
> tried on RELENG_7 but had similar symptoms. Is there any known reason
> why HEAD and RELENG_7 should be different in terms of linux_base support ?
> 

You should ask this question to bsam (CCed) which is our linux_base
expert.

The only reason I used in the Handbook fc4 for 7.X and f10 for 8.X it's
that they are the linux_base versions used on these respective branches.

-- 
Marc
From pmc at citylink.dinoex.sub.org  Sat Jul 25 13:13:51 2009
From: pmc at citylink.dinoex.sub.org (Peter Much)
Date: Sat Jul 25 13:13:59 2009
Subject: 7.2-STABLE ZFS: mv: set flags (was: 00000000): Invalid argument
References: <Kn6GqG.1I72@citylink.dinoex.sub.org>
Message-ID: <KnC8DG.4r0@citylink.dinoex.sub.org>

<pmc@citylink.dinoex.sub.org> aka Peter Much schrieb
mit Datum Wed, 22 Jul 2009 09:51:52 GMT in m2n.fbsd.stable:

|After upgrading my system from 7.2-PRERELEASE to 7.2-STABLE (as
|of last week), and accordingly upgrading my Pools from Version
|6 to Version 13, I get this error when moving arbitrary files
|between different ZFS filesystems.

.. found my mistake: there are *two* tasks in the upgrade.
Not only zfs pools need upgrade from version 6 to 13 (with
command "zpool"), also the zfs filesystems need upgrade from
version 1 to 3 (with command "zfs"). After doing both, the
message is gone.

rgds,
PMc
From bsam at ipt.ru  Sat Jul 25 13:19:54 2009
From: bsam at ipt.ru (Boris Samorodov)
Date: Sat Jul 25 13:20:01 2009
Subject: status of flash9/flash10 support in RELENG_7 ?
In-Reply-To: <20090725115525.GA85767@onelab2.iet.unipi.it> (Luigi Rizzo's
	message of "Sat\, 25 Jul 2009 13\:55\:25 +0200")
References: <20090725013500.GC62402@onelab2.iet.unipi.it>
	<20090725073805.GA11455@abigail.blackend.org>
	<20090725115525.GA85767@onelab2.iet.unipi.it>
Message-ID: <13015731@ipt.ru>

Luigi Rizzo <rizzo@iet.unipi.it> writes:

> i see that for 8.x you suggest using fc10

Just FYI: it is a new default for current 8.x.

-- 
WBR, bsam
From bsam at ipt.ru  Sat Jul 25 13:34:49 2009
From: bsam at ipt.ru (Boris Samorodov)
Date: Sat Jul 25 13:34:56 2009
Subject: status of flash9/flash10 support in RELENG_7 ?
In-Reply-To: <20090725123749.GA26505@abigail.blackend.org> (Marc Fonvieille's
	message of "Sat\, 25 Jul 2009 14\:37\:49 +0200")
References: <20090725013500.GC62402@onelab2.iet.unipi.it>
	<20090725073805.GA11455@abigail.blackend.org>
	<20090725115525.GA85767@onelab2.iet.unipi.it>
	<20090725123749.GA26505@abigail.blackend.org>
Message-ID: <46928623@ipt.ru>

Marc Fonvieille <blackend@freebsd.org> writes:
> On Sat, Jul 25, 2009 at 01:55:25PM +0200, Luigi Rizzo wrote:

>> i see that for 8.x you suggest using fc10, which is also something i
>> tried on RELENG_7 but had similar symptoms. Is there any known reason
>> why HEAD and RELENG_7 should be different in terms of linux_base support ?
>
> You should ask this question to bsam (CCed) which is our linux_base
> expert.

There are two cases here.

The first one is resolving issue. I'm not sure if all the needed changes
were done to RELENG_7 to let resolving work with linux_base-f10. If any
linux port/application that uses resolving (i.e. www/linux-firefox)
work at RELENG_7 then an MFC has been done. But that issue should not
influence flashplugin.

The second one (an absence of some syscalls) will not be resolved
at RELENG_7 due to an ABI changes. I'm not aware of linux applications
affected though. May be it's print/acroread9 but I'm not sure.

As for the original question. I don't use flash so can't be very
helpful here. But there are reports at emulation@ ML that both
linux-f8-flashplugin10 and linux-f10-flashplugin10 work better
then flashplugin[7|9].


-- 
WBR, bsam
From imb at protected-networks.net  Sat Jul 25 13:42:51 2009
From: imb at protected-networks.net (Michael Butler)
Date: Sat Jul 25 13:42:58 2009
Subject: regression with jexec?
Message-ID: <4A6B0BD3.6040206@protected-networks.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

After a clean rebuild ('rm -rf /usr/obj/*') ..

imb@aaron:/home/imb> uname -a
FreeBSD aaron.protected-networks.net 7.2-STABLE FreeBSD 7.2-STABLE #0:
Sat Jul 25 05:39:55 EDT 2009

imb@aaron:/home/imb> jls
   JID  IP Address      Hostname                      Path

 [ .. ]

     5  202.12.127.68   db.protected-networks.net
		/usr/local/jails/db.protected-networks.net

imb@aaron:/home/imb> sudo jexec 5 tcsh
jexec: Unable to parse jail ID.: No such file or directory

Huh?

	imb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (FreeBSD)

iEYEARECAAYFAkprC9MACgkQQv9rrgRC1JJ3KgCeLtnD97GwaDGnkUQ2QWBLjIqn
hU4AmwSIgRBmCXaweI7MRi3sjAfS0gci
=n2l2
-----END PGP SIGNATURE-----
From kabaev at gmail.com  Sat Jul 25 15:21:50 2009
From: kabaev at gmail.com (Alexander Kabaev)
Date: Sat Jul 25 15:22:15 2009
Subject: status of flash9/flash10 support in RELENG_7 ?
In-Reply-To: <46928623@ipt.ru>
References: <20090725013500.GC62402@onelab2.iet.unipi.it>
	<20090725073805.GA11455@abigail.blackend.org>
	<20090725115525.GA85767@onelab2.iet.unipi.it>
	<20090725123749.GA26505@abigail.blackend.org> <46928623@ipt.ru>
Message-ID: <20090725105020.66e281ee@kan.dnsalias.net>

On Sat, 25 Jul 2009 17:36:00 +0400
Boris Samorodov <bsam@ipt.ru> wrote:
> 
> As for the original question. I don't use flash so can't be very
> helpful here. But there are reports at emulation@ ML that both
> linux-f8-flashplugin10 and linux-f10-flashplugin10 work better
> then flashplugin[7|9].
> 

It does not work very well under Linux32 compat on -current - our futex
implementation seems to be too broken and causes frequent deadlock and
causes multiple threads to get stuck on process exit. One can easily
collect dozens of those stuck processes doing causal web browsing.

-- 
Alexander Kabaev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090725/c90b7714/signature.pgp
From nox at jelal.kn-bremen.de  Sat Jul 25 20:09:31 2009
From: nox at jelal.kn-bremen.de (Juergen Lock)
Date: Sat Jul 25 20:09:37 2009
Subject: status of flash9/flash10 support in RELENG_7 ?
In-Reply-To: <20090725013500.GC62402@onelab2.iet.unipi.it>
Message-ID: <200907251951.n6PJp5WW060965@triton.kn-bremen.de>

In article <20090725013500.GC62402@onelab2.iet.unipi.it> you write:
>Does anyone know what is the status of flash9 or flash10 in RELENG_7 ?
>Following the thread of a couple of months ago, i tried to:
>- remove all linux-* ports
>- set the following in /etc/make.conf
>	OVERRIDE_LINUX_BASE_PORT=f8
>	OVERRIDE_LINUX_NONBASE_PORTS=f8
>- set the following in /etc/sysctl.conf
>	compat.linux.osrelease=2.6.16
>- set the following in /etc/fstab
>	linproc /usr/compat/linux/proc  linprocfs       rw 0 0
>- reinstall linux_base-f8-8_11
>- reinstall linux-flashplugin-10.0r22 (which in turn brings in the
>  relevant linux-f8-* ports)
>
>- also install nspluginwrapper and create a firefox plugin
>- upgrade firefox to firefox-3.5,1 (native), just in case
>- run firefox with "limit stacksize 4megabytes" (or variants)
>  as recommended to avoid npviewer growing/not dying
>
>This was done on 3 different machines (one laptop with a centrino,
>2 desktops with AMD X2 dual core running in i386 mode) with mixed
>[in]success. On one machine thing started working well, but on the
>other two they did not (the various packages were of course slightly
>disaligned) and while trying to replicate the configuration i also
>broke the good one without figuring out why.
>Symptoms are that on certain sites or actions (e.g. switch to full
>screen on youtube videos) i get firefox freezing like this
>
>22381 luigi  13  96    0 82580K 57484K ucond   1   0:00  0.20% firefox-bin
>22413 luigi   1  97    0 72920K 33448K futex   1   0:00  0.20% npviewer.bin
>22414 luigi   1  97    0 72920K 33448K futex   1   0:00  0.20% npviewer.bin
>
>and recovering control (but no video) after 10+seconds
>
>I also get a lot of the following weak_unref warnings with various addresses
>
>(firefox-bin:22381): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0x297ba9f0(0x2a10d110)
>
>(but not sure how related is this, because it happens even without a
>flash plugin).
>
>I have also tried flash9 instead of flash10, o fc10 instead of fc8,
>all with similar results.
>
>Is there a recipe for a working flas9 or flash10 operation ?

Hmm.  All I can say is I'm not sure I can even remember flash hanging
since I lowered the stack limit using this nspluginwrapper patch:
	http://docs.freebsd.org/cgi/mid.cgi?20090630184146.GA39346
(btw still no words from the nspluginwrappper port maintainer about this,
or I missed them?  Cc'd again...)

 _When_ flash hung, I usually got it back to running by doing
`killall npviewer.bin' and optionally quitting ff and doing
`rm /tmp/_org_wrapper_NSPlugins_libflashplayer.so*' and then
restarting the browser.  (If you don't do that, remaining
npviewer.bin processes might interfere with later ff sessions
making flash appear more broken than it really is...)

 HTH,
	Juergen
From jamie at FreeBSD.org  Sun Jul 26 00:08:15 2009
From: jamie at FreeBSD.org (Jamie Gritton)
Date: Sun Jul 26 00:08:22 2009
Subject: regression with jexec?
In-Reply-To: <4A6B0BD3.6040206@protected-networks.net>
References: <4A6B0BD3.6040206@protected-networks.net>
Message-ID: <4A6B9A60.90302@FreeBSD.org>

Michael Butler wrote:

> After a clean rebuild ('rm -rf /usr/obj/*') ..
> 
> imb@aaron:/home/imb> uname -a
> FreeBSD aaron.protected-networks.net 7.2-STABLE FreeBSD 7.2-STABLE #0:
> Sat Jul 25 05:39:55 EDT 2009
> 
> imb@aaron:/home/imb> jls
>    JID  IP Address      Hostname                      Path
> 
>  [ .. ]
> 
>      5  202.12.127.68   db.protected-networks.net
> 		/usr/local/jails/db.protected-networks.net
> 
> imb@aaron:/home/imb> sudo jexec 5 tcsh
> jexec: Unable to parse jail ID.: No such file or directory
> 
> Huh?
> 
> 	imb


The symptom in jexec can be fixed by this little patch:

Index: usr.sbin/jexec/jexec.c
===================================================================
--- usr.sbin/jexec/jexec.c	(revision 195879)
+++ usr.sbin/jexec/jexec.c	(working copy)
@@ -248,6 +248,7 @@
  	if (argc < 2)
  		usage();
  	if (strlen(argv[0]) > 0) {
+		errno = 0;
  		jid = (int)strtol(argv[0], NULL, 10);
  		if (errno)
  			err(1, "Unable to parse jail ID.");

But the broader problem is malloc.  It's leaving errno set to
ENOENT when /etc/malloc.conf doesn't exist.  This seems like
wrong behavior to me.

- Jamie
From imb at protected-networks.net  Sun Jul 26 01:06:40 2009
From: imb at protected-networks.net (Michael Butler)
Date: Sun Jul 26 01:06:47 2009
Subject: regression with jexec?
In-Reply-To: <4A6B9A60.90302@FreeBSD.org>
References: <4A6B0BD3.6040206@protected-networks.net>
	<4A6B9A60.90302@FreeBSD.org>
Message-ID: <4A6BAC1A.5080303@protected-networks.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jamie Gritton wrote:
> Michael Butler wrote:
>> imb@aaron:/home/imb> sudo jexec 5 tcsh
>> jexec: Unable to parse jail ID.: No such file or directory

> 
> The symptom in jexec can be fixed by this little patch:
> 
> Index: usr.sbin/jexec/jexec.c
> ===================================================================
> --- usr.sbin/jexec/jexec.c    (revision 195879)
> +++ usr.sbin/jexec/jexec.c    (working copy)
> @@ -248,6 +248,7 @@
>      if (argc < 2)
>          usage();
>      if (strlen(argv[0]) > 0) {
> +        errno = 0;
>          jid = (int)strtol(argv[0], NULL, 10);
>          if (errno)
>              err(1, "Unable to parse jail ID.");

Thanks - this certainly cures the effect.

> But the broader problem is malloc.  It's leaving errno set to
> ENOENT when /etc/malloc.conf doesn't exist.  This seems like
> wrong behavior to me.

Seems like a POLA violation to me,

	imb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (FreeBSD)

iEYEARECAAYFAkprrBoACgkQQv9rrgRC1JIImwCdG2hjH00hKOzMRUHEqfXwu8FS
O6UAoJL/2iZf/Nz0Pp84q0p+RDkNIM+1
=iBx1
-----END PGP SIGNATURE-----
From oberman at es.net  Sun Jul 26 01:42:47 2009
From: oberman at es.net (Kevin Oberman)
Date: Sun Jul 26 01:42:53 2009
Subject: status of flash9/flash10 support in RELENG_7 ? 
In-Reply-To: Your message of "Sat, 25 Jul 2009 13:55:25 +0200."
	<20090725115525.GA85767@onelab2.iet.unipi.it> 
Message-ID: <20090726014244.D4C041CC0B@ptavv.es.net>

> Date: Sat, 25 Jul 2009 13:55:25 +0200
> From: Luigi Rizzo <rizzo@iet.unipi.it>
> Sender: owner-freebsd-stable@freebsd.org
> 
> On Sat, Jul 25, 2009 at 09:38:05AM +0200, Marc Fonvieille wrote:
> > On Sat, Jul 25, 2009 at 03:35:00AM +0200, Luigi Rizzo wrote:
> > > Does anyone know what is the status of flash9 or flash10 in RELENG_7 ?
> > > Following the thread of a couple of months ago, i tried to:
> > > - remove all linux-* ports
> > > - set the following in /etc/make.conf
> > > 	OVERRIDE_LINUX_BASE_PORT=f8
> > > 	OVERRIDE_LINUX_NONBASE_PORTS=f8
> > > - set the following in /etc/sysctl.conf
> > > 	compat.linux.osrelease=2.6.16
> > > - set the following in /etc/fstab
> > > 	linproc /usr/compat/linux/proc  linprocfs       rw 0 0
> > > - reinstall linux_base-f8-8_11
> > > - reinstall linux-flashplugin-10.0r22 (which in turn brings in the
> > >   relevant linux-f8-* ports)
> > > 
> > > - also install nspluginwrapper and create a firefox plugin
> > > - upgrade firefox to firefox-3.5,1 (native), just in case
> > > - run firefox with "limit stacksize 4megabytes" (or variants)
> > >   as recommended to avoid npviewer growing/not dying
> > > 
> > > This was done on 3 different machines (one laptop with a centrino,
> > > 2 desktops with AMD X2 dual core running in i386 mode) with mixed
> > > [in]success. On one machine thing started working well, but on the
> > > other two they did not (the various packages were of course slightly
> > > disaligned) and while trying to replicate the configuration i also
> > > broke the good one without figuring out why.
> > > Symptoms are that on certain sites or actions (e.g. switch to full
> > > screen on youtube videos) i get firefox freezing like this
> > > 
> > > 22381 luigi  13  96    0 82580K 57484K ucond   1   0:00  0.20% firefox-bin
> > > 22413 luigi   1  97    0 72920K 33448K futex   1   0:00  0.20% npviewer.bin
> > > 22414 luigi   1  97    0 72920K 33448K futex   1   0:00  0.20% npviewer.bin
> > > 
> > > and recovering control (but no video) after 10+seconds
> > > 
> > > I also get a lot of the following weak_unref warnings with various addresses
> > > 
> > > (firefox-bin:22381): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0x297ba9f0(0x2a10d110)
> > > 
> > > (but not sure how related is this, because it happens even without a
> > > flash plugin).
> > > 
> > > I have also tried flash9 instead of flash10, o fc10 instead of fc8,
> > > all with similar results.
> > > 
> > > Is there a recipe for a working flas9 or flash10 operation ?
> > >
> > 
> > The Handbook gives a reliable, i.e. reproductible one, recipe:
> > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/desktop-browsers.html
> > 6.2.3 Firefox and Macromedia? Flash Plugin
> > 
> > for running Flash 9 under 7.X and with default linux_base.
> 
> from what i remember, flash9 with the default linux_base (fc4)
> did not work for me (though i don't remember the details).
> Are you positive that it is a working configuration on RELENG_7 ?
> 
> Especially, fc4 does not support skype (except skype1.2, which however
> does not authenticate anymore), so using fc4 is not an option for
> me and i suspect desktop users in general.
> 
> 
> > I'm also working on an update for 8.X
> 
> i see that for 8.x you suggest using fc10, which is also something i
> tried on RELENG_7 but had similar symptoms. Is there any known reason
> why HEAD and RELENG_7 should be different in terms of linux_base support ?

Here is what is working for me for both Flash9 and Skype:
linux_base-f8-8_11
nspluginwrapper-1.2.2_2
skype-2.0.0.72,1
linux-flashplugin-9.0r159:

Be sure that your various linux packages are updated to the -f8-
versions, too. The upgrade for linux_base is the tricky one.

Once everything is at the correct version, the user needs to use
nspluginwrapper to set up the correct user mappings. I don't want the
Acrobat plugin, so I pick the plugins I want to wrap rather than use the
automatic option.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@es.net			Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4  EADA 927D EBB3 987B 3751
From rizzo at iet.unipi.it  Sun Jul 26 03:07:41 2009
From: rizzo at iet.unipi.it (Luigi Rizzo)
Date: Sun Jul 26 03:07:48 2009
Subject: status of flash9/flash10 support in RELENG_7 ?
In-Reply-To: <20090726014244.D4C041CC0B@ptavv.es.net>
References: <20090725115525.GA85767@onelab2.iet.unipi.it>
	<20090726014244.D4C041CC0B@ptavv.es.net>
Message-ID: <20090726031354.GA17719@onelab2.iet.unipi.it>

On Sat, Jul 25, 2009 at 06:42:44PM -0700, Kevin Oberman wrote:
...
> > i see that for 8.x you suggest using fc10, which is also something i
> > tried on RELENG_7 but had similar symptoms. Is there any known reason
> > why HEAD and RELENG_7 should be different in terms of linux_base support ?
> 
> Here is what is working for me for both Flash9 and Skype:
> linux_base-f8-8_11
> nspluginwrapper-1.2.2_2
> skype-2.0.0.72,1
> linux-flashplugin-9.0r159:
> 
> Be sure that your various linux packages are updated to the -f8-
> versions, too. The upgrade for linux_base is the tricky one.

Unfortunately I think there are many more details that one has
to consider, such as CPU type and number of cores/threads,
OS version, and presumably firefox version as well.
Can you tell me more on the above ?

I had flash9 working once, but it don't remember all the packages
(and something was stale for sure); it got broken while installing
skype (a mail thread mentioned an issue with some shared lib version,
which was exactly the problem i had with skype. The fix was to
either create a symlink on a library or install linux_base-f10 to fix it).

An example of the URLs that is giving me problems is the following

http://tv.repubblica.it/copertina/massa-colpito-da-un-detrito/35446?video

(basically all videos from that site cause the same problem). I would be
grateful if you cold check it.

cheers
luigi
From emikulic at gmail.com  Sun Jul 26 03:22:42 2009
From: emikulic at gmail.com (Emil Mikulic)
Date: Sun Jul 26 03:22:49 2009
Subject: Torrent clients bring pf-based firewall to its knees...?
In-Reply-To: <4A6A1FEB.9030001@kutulu.org>
References: <4A6A1FEB.9030001@kutulu.org>
Message-ID: <20090726032238.GA33220@dmr.ath.cx>

On Fri, Jul 24, 2009 at 04:56:11PM -0400, Mike Edenfield wrote:
> However, after a short period of torrent activity, the machine running  
> the firewall becomes extremely slow and lagged for all network traffic,  
> but appears to be operating fine locally.  Remote connections via ssh  
> become extremely unresponsive, and eventually connections start timing  
> out, but when logged in at the console, there doesn't appear to be any  
> problem.

This sounds exactly like a problem I had with a server running out of
space in the state table.

> I've tried shutting down the torrent client, clearing out the state and  
> nat rules with pfctl, adding drop rules to reject the torrent traffic,  
> and even bringing the network adapter down completely, but only a  
> physical reboot (combined with not running the client ever again) seems  
> to solve anything.

States and rules are separate in pf.  Did you clear out the *states* or
just the rules?  Check how many states are currently allocated
using "pfctl -s info" (or install pftop, it's awesome)

If you are indeed running out of states, add to pf.conf something like:
	set limit states 60000

The default is 10000.

--Emil
From oberman at es.net  Sun Jul 26 03:31:29 2009
From: oberman at es.net (Kevin Oberman)
Date: Sun Jul 26 03:31:39 2009
Subject: status of flash9/flash10 support in RELENG_7 ? 
In-Reply-To: Your message of "Sun, 26 Jul 2009 05:13:54 +0200."
	<20090726031354.GA17719@onelab2.iet.unipi.it> 
Message-ID: <20090726033127.02EFE1CC0B@ptavv.es.net>

> Date: Sun, 26 Jul 2009 05:13:54 +0200
> From: Luigi Rizzo <rizzo@iet.unipi.it>
> 
> On Sat, Jul 25, 2009 at 06:42:44PM -0700, Kevin Oberman wrote:
> ...
> > > i see that for 8.x you suggest using fc10, which is also something i
> > > tried on RELENG_7 but had similar symptoms. Is there any known reason
> > > why HEAD and RELENG_7 should be different in terms of linux_base support ?
> > 
> > Here is what is working for me for both Flash9 and Skype:
> > linux_base-f8-8_11
> > nspluginwrapper-1.2.2_2
> > skype-2.0.0.72,1
> > linux-flashplugin-9.0r159:
> > 
> > Be sure that your various linux packages are updated to the -f8-
> > versions, too. The upgrade for linux_base is the tricky one.
> 
> Unfortunately I think there are many more details that one has
> to consider, such as CPU type and number of cores/threads,
> OS version, and presumably firefox version as well.
> Can you tell me more on the above ?
> 
> I had flash9 working once, but it don't remember all the packages
> (and something was stale for sure); it got broken while installing
> skype (a mail thread mentioned an issue with some shared lib version,
> which was exactly the problem i had with skype. The fix was to
> either create a symlink on a library or install linux_base-f10 to fix it).
> 
> An example of the URLs that is giving me problems is the following
> 
> http://tv.repubblica.it/copertina/massa-colpito-da-un-detrito/35446?video
> 
> (basically all videos from that site cause the same problem). I would be
> grateful if you cold check it.

This all runs on my uni-processor ThinkPad 43 with 2GHz Pentium-M. I am
running week old RELENG_7, but it has been working since 7.0 days. not
knowing Italian, all I can say is that it shows a view of the front of a
race car, perhaps an F1 Ferrari, but I'm not too sure. In any case, it
plays fine for me.

Here is a list of the dependencies of nspluginwrapper:
Dependency: xineramaproto-1.1.2
Dependency: xextproto-7.0.5
Dependency: renderproto-0.9.3
Dependency: randrproto-1.3.0
Dependency: kbproto-1.0.3
Dependency: inputproto-1.5.0
Dependency: fixesproto-4.0
Dependency: damageproto-1.1.0_2
Dependency: compositeproto-0.4
Dependency: font-util-1.0.1
Dependency: encodings-1.0.2,1
Dependency: expat-2.0.1
Dependency: ca_root_nss-3.11.9_2
Dependency: hicolor-icon-theme-0.10_2
Dependency: python26-2.6.2_1
Dependency: xcb-proto-1.5
Dependency: perl-threaded-5.8.9_3
Dependency: png-1.2.37
Dependency: jpeg-7
Dependency: tiff-3.8.2_4
Dependency: jasper-1.900.1_8
Dependency: curl-7.19.5_1
Dependency: linux_base-f8-8_11
Dependency: linux-f8-tiff-3.8.2_1
Dependency: linux-f8-png-1.2.22_1
Dependency: linux-f8-jpeg-6b_1
Dependency: linux-f8-expat-2.0.1_1
Dependency: linux-f8-fontconfig-2.4.2_1
Dependency: linux-f8-xorg-libs-7.3_3
Dependency: linux-f8-cairo-1.4.14_1
Dependency: linux-f8-pango-1.18.4_1
Dependency: pkg-config-0.23_1
Dependency: xproto-7.0.15
Dependency: pixman-0.15.4
Dependency: libtasn1-2.1
Dependency: libfontenc-1.0.4
Dependency: libXdmcp-1.0.2_1
Dependency: libXau-1.0.4
Dependency: libICE-1.0.4_1,1
Dependency: libSM-1.1.0_1,1
Dependency: freetype2-2.3.9_1
Dependency: mkfontscale-1.0.6
Dependency: mkfontdir-1.0.4
Dependency: fontconfig-2.6.0,1
Dependency: font-misc-meltho-1.0.0_1
Dependency: font-misc-ethiopic-1.0.0
Dependency: font-bh-ttf-1.0.0
Dependency: bitstream-vera-1.10_4
Dependency: xorg-fonts-truetype-7.4
Dependency: pcre-7.9
Dependency: libpthread-stubs-0.1
Dependency: libxcb-1.3
Dependency: xcb-util-0.3.5
Dependency: libX11-1.2.1_1,1
Dependency: libXt-1.0.5_1
Dependency: libXrender-0.9.4_1
Dependency: libXft-2.1.13
Dependency: libXfixes-4.0.3_1
Dependency: libXext-1.0.5,1
Dependency: libXrandr-1.3.0
Dependency: libXinerama-1.0.3,1
Dependency: libXi-1.2.1,1
Dependency: libXdamage-1.1.1
Dependency: libXcursor-1.1.9_1
Dependency: libXcomposite-0.4.0,1
Dependency: cairo-1.8.8,1
Dependency: libiconv-1.13.1
Dependency: libxml2-2.7.3
Dependency: gettext-0.17_1
Dependency: libgpg-error-1.7
Dependency: libgcrypt-1.4.4
Dependency: glib-2.20.4
Dependency: gamin-0.1.10_3
Dependency: gio-fam-backend-2.20.4
Dependency: shared-mime-info-0.60_1
Dependency: pango-1.24.4
Dependency: lzo2-2.03_2
Dependency: gnutls-2.6.5
Dependency: cups-client-1.3.10_2
Dependency: linux-f8-atk-1.20.0_1
Dependency: linux-f8-gtk2-2.12.8_1
Dependency: atk-1.26.0
Dependency: gtk-2.16.5

Linux-flashplugin9.0r159 only requires:
ependency: linux_base-f8-8_11
Dependency: linux-openssl-0.9.7f_2
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@es.net			Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4  EADA 927D EBB3 987B 3751
From rizzo at iet.unipi.it  Sun Jul 26 03:41:30 2009
From: rizzo at iet.unipi.it (Luigi Rizzo)
Date: Sun Jul 26 03:41:38 2009
Subject: status of flash9/flash10 support in RELENG_7 ?
In-Reply-To: <20090726033127.02EFE1CC0B@ptavv.es.net>
References: <20090726031354.GA17719@onelab2.iet.unipi.it>
	<20090726033127.02EFE1CC0B@ptavv.es.net>
Message-ID: <20090726034744.GA19060@onelab2.iet.unipi.it>

On Sat, Jul 25, 2009 at 08:31:27PM -0700, Kevin Oberman wrote:
> > Date: Sun, 26 Jul 2009 05:13:54 +0200
> > From: Luigi Rizzo <rizzo@iet.unipi.it>
> > 
> > On Sat, Jul 25, 2009 at 06:42:44PM -0700, Kevin Oberman wrote:
> > ...
> > > > i see that for 8.x you suggest using fc10, which is also something i
> > > > tried on RELENG_7 but had similar symptoms. Is there any known reason
> > > > why HEAD and RELENG_7 should be different in terms of linux_base support ?
> > > 
> > > Here is what is working for me for both Flash9 and Skype:
> > > linux_base-f8-8_11
> > > nspluginwrapper-1.2.2_2
> > > skype-2.0.0.72,1
> > > linux-flashplugin-9.0r159:
> > > 
> > > Be sure that your various linux packages are updated to the -f8-
> > > versions, too. The upgrade for linux_base is the tricky one.
> > 
> > Unfortunately I think there are many more details that one has
> > to consider, such as CPU type and number of cores/threads,
> > OS version, and presumably firefox version as well.
> > Can you tell me more on the above ?
> > 
> > I had flash9 working once, but it don't remember all the packages
> > (and something was stale for sure); it got broken while installing
> > skype (a mail thread mentioned an issue with some shared lib version,
> > which was exactly the problem i had with skype. The fix was to
> > either create a symlink on a library or install linux_base-f10 to fix it).
> > 
> > An example of the URLs that is giving me problems is the following
> > 
> > http://tv.repubblica.it/copertina/massa-colpito-da-un-detrito/35446?video
> > 
> > (basically all videos from that site cause the same problem). I would be
> > grateful if you cold check it.
> 
> This all runs on my uni-processor ThinkPad 43 with 2GHz Pentium-M. I am
> running week old RELENG_7, but it has been working since 7.0 days. not
> knowing Italian, all I can say is that it shows a view of the front of a
> race car, perhaps an F1 Ferrari, but I'm not too sure. In any case, it
> plays fine for me.

ok thanks a lot for the info and also for the dependency list below.
I'll check on a UP machine (my laptop) to see if i can have it back
working there, and from there see how it goes on the desktop
(which are AMD dual code, running freebsd-i386)

cheers
luigi
From barbara.xxx1975 at libero.it  Sun Jul 26 06:31:28 2009
From: barbara.xxx1975 at libero.it (barbara)
Date: Sun Jul 26 06:31:35 2009
Subject: status of flash9/flash10 support in RELENG_7 ?
Message-ID: <KNDLLL$F3FF28F7BB21D7F36CB492E8D4CB6EA3@libero.it>

> On Sat, Jul 25, 2009 at 06:42:44PM -0700, Kevin Oberman wrote:
> ...
> > > i see that for 8.x you suggest using fc10, which is also something i
> > > tried on RELENG_7 but had similar symptoms. Is there any known reason
> > > why HEAD and RELENG_7 should be different in terms of linux_base support ?
> > 
> > Here is what is working for me for both Flash9 and Skype:
> > linux_base-f8-8_11
> > nspluginwrapper-1.2.2_2
> > skype-2.0.0.72,1
> > linux-flashplugin-9.0r159:
> > 
> > Be sure that your various linux packages are updated to the -f8-
> > versions, too. The upgrade for linux_base is the tricky one.
> 
> Unfortunately I think there are many more details that one has
> to consider, such as CPU type and number of cores/threads,
> OS version, and presumably firefox version as well.
> Can you tell me more on the above ?
> 
> I had flash9 working once, but it don't remember all the packages
> (and something was stale for sure); it got broken while installing
> skype (a mail thread mentioned an issue with some shared lib version,
> which was exactly the problem i had with skype. The fix was to
> either create a symlink on a library or install linux_base-f10 to fix it).
> 
> An example of the URLs that is giving me problems is the following
> 
> http://tv.repubblica.it/copertina/massa-colpito-da-un-detrito/35446?video
> 
> (basically all videos from that site cause the same problem). I would be
> grateful if you cold check it.
> 


The video looks fine here, even if I'm getting a warning about the flash version.
http://img24.imageshack.us/img24/2741/screenshotmassacolpitod.png

I've found that on 7, the better combination for me is linux-flashplugin9, linux_base-fc4 and compat.linux.osrelease=2.4.2.
On CURRENT, using linux_base-f10, I get much more stuck process, while on 7 it barely happens.

Barbara



From barbara.xxx1975 at libero.it  Sun Jul 26 06:46:58 2009
From: barbara.xxx1975 at libero.it (barbara)
Date: Sun Jul 26 06:47:07 2009
Subject: kern/134584: [panic] spin lock held too long
Message-ID: <KNDMU8$8EFE8DA350FF14C54F1F3D61C7265B47@libero.it>

It happened again, on shutdown.
As the previous time, it happened after a high (for a desktop) uptime and, if it could matter, after running net-p2p/transmission-gtk2 for several hours.
I don't know if it's related, but often quitting transmission, doesn't terminate the process. Sometimes it end after several minutes the gui exited, sometimes it's still running after hours.
I've noticed it as the destination folder is on a manually mounted device and I can't umount it as fstat reports the device used by a transmission process.
So I often have to kill it.
This happened both the time I had this kind of panic.

Barbara


Script started on Sun Jul 26 08:22:33 2009
You have mail.
satanasso# kgdb kernel.debug /var/crash/vmcore.17
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd"...

Unread portion of the kernel message buffer:
<118>Stopping devd.
<118>Writing entropy file:
<118>.
<118>Terminated
<118>.
<118>Jul 25 17:45:18 satanasso syslogd: exiting on signal 15
Waiting (max 60 seconds) for system process `vnlru' to stop...done
Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
Waiting (max 60 seconds) for system process `syncer' to stop...
Syncing disks, vnodes remaining...7 6 5 3 1 2 2 0 0 done
All buffers synced.
Uptime: 22h41m12s
Rebooting...
cpu_reset: Stopping other CPUs
spin lock 0xc08ae540 (sched lock 1) held by 0xc588f480 (tid 100006) too long
panic: spin lock held too long
cpuid = 0
Uptime: 22h41m14s
Physical memory: 2031 MB
Dumping 171 MB: (CTRL-C to abort)  156 140 124 108 92 76 60 44 28 12

Reading symbols from /boot/kernel/linux.ko...Reading symbols from /boot/kernel/linux.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/linux.ko
Reading symbols from /boot/modules/nvidia.ko...done.
Loaded symbols for /boot/modules/nvidia.ko
Reading symbols from /boot/kernel/acpi.ko...Reading symbols from /boot/kernel/acpi.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/acpi.ko
Reading symbols from /boot/kernel/linprocfs.ko...Reading symbols from /boot/kernel/linprocfs.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/linprocfs.ko
Reading symbols from /boot/kernel/logo_saver.ko...Reading symbols from /boot/kernel/logo_saver.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/logo_saver.ko
Reading symbols from /boot/kernel/ntfs.ko...Reading symbols from /boot/kernel/ntfs.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/ntfs.ko
#0  doadump () at pcpu.h:196
196		__asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb) bt
#0  doadump () at pcpu.h:196
#1  0xc059b097 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418
#2  0xc059b36c in panic (fmt=Variable "fmt" is not available.
) at /usr/src/sys/kern/kern_shutdown.c:574
#3  0xc058bd1f in _mtx_lock_spin_failed (m=0x0) at /usr/src/sys/kern/kern_mutex.c:449
#4  0xc058c425 in _thread_lock_flags (td=0xc588f480, opts=0, file=0xc08200c8 "/usr/src/sys/kern/kern_intr.c", line=801) at /usr/src/sys/kern/kern_mutex.c:537
#5  0xc0576787 in intr_event_schedule_thread (ie=Variable "ie" is not available.
) at /usr/src/sys/kern/kern_intr.c:801
#6  0xc0577aa5 in swi_sched (cookie=0xc5880e00, flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_intr.c:1028
#7  0xc055a6df in hardclock (usermode=0, pc=3229503748) at /usr/src/sys/kern/kern_clock.c:339
#8  0xc07ce23a in lapic_handle_timer (frame=0xc54aaba0) at /usr/src/sys/i386/i386/local_apic.c:705
#9  0xc07c6c9f in Xtimerint () at apic_vector.s:108
#10 0xc07e5104 in DELAY (n=1000000) at cpufunc.h:352
#11 0xc07e2c03 in cpu_reset () at /usr/src/sys/i386/i386/vm_machdep.c:594
#12 0xc059a753 in shutdown_reset (junk=0x0, howto=0) at /usr/src/sys/kern/kern_shutdown.c:493
#13 0xc059b117 in boot (howto=0) at /usr/src/sys/kern/kern_shutdown.c:421
#14 0xc059b247 in reboot (td=0xc588fd80, uap=0xc54aacfc) at /usr/src/sys/kern/kern_shutdown.c:172
#15 0xc07e07d5 in syscall (frame=0xc54aad38) at /usr/src/sys/i386/i386/trap.c:1089
#16 0xc07c6720 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:262
#17 0x00000033 in ?? ()
Previous frame inner to this frame (corrupt stack?)
(kgdb) thread apply all bt

Thread 52 (Thread 100051):
#0  sched_switch (td=0xc5c91d80, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05cf859 in sleepq_switch (wchan=Variable "wchan" is not available.
) at /usr/src/sys/kern/subr_sleepqueue.c:497
#3  0xc05d03d7 in sleepq_timedwait (wchan=0xc08bd300) at /usr/src/sys/kern/subr_sleepqueue.c:615
#4  0xc05a3483 in _sleep (ident=0xc08bd300, lock=0xc08bd2c0, priority=68, wmesg=0xc0833855 "sdflush", timo=1000) at /usr/src/sys/kern/kern_synch.c:226
#5  0xc076407e in softdep_flush () at /usr/src/sys/ufs/ffs/ffs_softdep.c:773
#6  0xc0574587 in fork_exit (callout=0xc0763cb0 <softdep_flush>, arg=0x0, frame=0xc5617d38) at /usr/src/sys/kern/kern_fork.c:811
#7  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 51 (Thread 100050):
#0  sched_switch (td=0xc5a616c0, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05cf859 in sleepq_switch (wchan=Variable "wchan" is not available.
) at /usr/src/sys/kern/subr_sleepqueue.c:497
#3  0xc05cfec6 in sleepq_wait (wchan=0xc5abe36c) at /usr/src/sys/kern/subr_sleepqueue.c:580
#4  0xc05a34a5 in _sleep (ident=0xc5abe36c, lock=0xc5abe350, priority=104, wmesg=0xc0820618 "ktsusp", timo=0) at /usr/src/sys/kern/kern_synch.c:230
#5  0xc057e632 in kthread_suspend_check (p=0xc5abe2c0) at /usr/src/sys/kern/kern_kthread.c:197
#6  0xc0620b1e in vnlru_proc () at /usr/src/sys/kern/vfs_subr.c:724
#7  0xc0574587 in fork_exit (callout=0xc0620ad0 <vnlru_proc>, arg=0x0, frame=0xc5614d38) at /usr/src/sys/kern/kern_fork.c:811
#8  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 50 (Thread 100049):
#0  sched_switch (td=0xc5a61900, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05cf859 in sleepq_switch (wchan=Variable "wchan" is not available.
) at /usr/src/sys/kern/subr_sleepqueue.c:497
#3  0xc05cfec6 in sleepq_wait (wchan=0xc5abe62c) at /usr/src/sys/kern/subr_sleepqueue.c:580
#4  0xc05a34a5 in _sleep (ident=0xc5abe62c, lock=0xc5abe610, priority=104, wmesg=0xc0820618 "ktsusp", timo=0) at /usr/src/sys/kern/kern_synch.c:230
#5  0xc057e632 in kthread_suspend_check (p=0xc5abe580) at /usr/src/sys/kern/kern_kthread.c:197
#6  0xc061f9c2 in sched_sync () at /usr/src/sys/kern/vfs_subr.c:1719
#7  0xc0574587 in fork_exit (callout=0xc061f8a0 <sched_sync>, arg=0x0, frame=0xc5611d38) at /usr/src/sys/kern/kern_fork.c:811
#8  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 49 (Thread 100048):
#0  sched_switch (td=0xc5a61b40, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05cf859 in sleepq_switch (wchan=Variable "wchan" is not available.
) at /usr/src/sys/kern/subr_sleepqueue.c:497
#3  0xc05cfec6 in sleepq_wait (wchan=0xc5abe8ec) at /usr/src/sys/kern/subr_sleepqueue.c:580
#4  0xc05a34a5 in _sleep (ident=0xc5abe8ec, lock=0xc5abe8d0, priority=104, wmesg=0xc0820618 "ktsusp", timo=0) at /usr/src/sys/kern/kern_synch.c:230
#5  0xc057e632 in kthread_suspend_check (p=0xc5abe840) at /usr/src/sys/kern/kern_kthread.c:197
#6  0xc0609c4b in buf_daemon () at /usr/src/sys/kern/vfs_bio.c:2155
#7  0xc0574587 in fork_exit (callout=0xc0609b70 <buf_daemon>, arg=0x0, frame=0xc560ed38) at /usr/src/sys/kern/kern_fork.c:811
#8  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 48 (Thread 100047):
#0  sched_switch (td=0xc5a61d80, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05cf859 in sleepq_switch (wchan=Variable "wchan" is not available.
) at /usr/src/sys/kern/subr_sleepqueue.c:497
#3  0xc05d03d7 in sleepq_timedwait (wchan=0xc08bdf14) at /usr/src/sys/kern/subr_sleepqueue.c:615
#4  0xc05a3483 in _sleep (ident=0xc08bdf14, lock=0xc08bdad0, priority=0, wmesg=0xc0836ae9 "pgzero", timo=300000) at /usr/src/sys/kern/kern_synch.c:226
#5  0xc07a155c in vm_pagezero (arg=0x0) at /usr/src/sys/vm/vm_zeroidle.c:136
#6  0xc0574587 in fork_exit (callout=0xc07a1480 <vm_pagezero>, arg=0x0, frame=0xc560bd38) at /usr/src/sys/kern/kern_fork.c:811
#7  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 47 (Thread 100046):
#0  sched_switch (td=0xc5aa1000, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05cf859 in sleepq_switch (wchan=Variable "wchan" is not available.
) at /usr/src/sys/kern/subr_sleepqueue.c:497
---Type <return> to continue, or q <return> to quit---
#3  0xc05cfec6 in sleepq_wait (wchan=0xc08bdb44) at /usr/src/sys/kern/subr_sleepqueue.c:580
#4  0xc05a34a5 in _sleep (ident=0xc08bdb44, lock=0xc08bdb48, priority=104, wmesg=0xc0826d0c "psleep", timo=0) at /usr/src/sys/kern/kern_synch.c:230
#5  0xc079c4e8 in vm_daemon () at /usr/src/sys/vm/vm_pageout.c:1535
#6  0xc0574587 in fork_exit (callout=0xc079c470 <vm_daemon>, arg=0x0, frame=0xc5608d38) at /usr/src/sys/kern/kern_fork.c:811
#7  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 46 (Thread 100045):
#0  sched_switch (td=0xc5aa1240, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05cf859 in sleepq_switch (wchan=Variable "wchan" is not available.
) at /usr/src/sys/kern/subr_sleepqueue.c:497
#3  0xc05d03d7 in sleepq_timedwait (wchan=0xc08bdb0c) at /usr/src/sys/kern/subr_sleepqueue.c:615
#4  0xc05a3483 in _sleep (ident=0xc08bdb0c, lock=0xc08bdad0, priority=68, wmesg=0xc0826d0c "psleep", timo=5000) at /usr/src/sys/kern/kern_synch.c:226
#5  0xc079ce6b in vm_pageout () at /usr/src/sys/vm/vm_pageout.c:1475
#6  0xc0574587 in fork_exit (callout=0xc079cb80 <vm_pageout>, arg=0x0, frame=0xc5605d38) at /usr/src/sys/kern/kern_fork.c:811
#7  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 45 (Thread 100044):
#0  sched_switch (td=0xc5aa1480, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05cf859 in sleepq_switch (wchan=Variable "wchan" is not available.
) at /usr/src/sys/kern/subr_sleepqueue.c:497
#3  0xc05cfec6 in sleepq_wait (wchan=0xc08b376c) at /usr/src/sys/kern/subr_sleepqueue.c:580
#4  0xc05a34a5 in _sleep (ident=0xc08b376c, lock=0xc08b3674, priority=0, wmesg=0xc082a92a "waiting_for_work", timo=0) at /usr/src/sys/kern/kern_synch.c:230
#5  0xc06693df in sctp_iterator_thread (v=0x0) at /usr/src/sys/netinet/sctp_bsd_addr.c:95
#6  0xc0574587 in fork_exit (callout=0xc0669360 <sctp_iterator_thread>, arg=0x0, frame=0xc55d2d38) at /usr/src/sys/kern/kern_fork.c:811
#7  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 44 (Thread 100043):
#0  fork_trampoline () at /usr/src/sys/i386/i386/exception.s:268
Current language:  auto; currently asm

Thread 43 (Thread 100042):
#0  sched_switch (td=0xc5aa1900, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc0577dbb in ithread_loop (arg=0xc5ab2c20) at /usr/src/sys/kern/kern_intr.c:1225
#3  0xc0574587 in fork_exit (callout=0xc0577ab0 <ithread_loop>, arg=0xc5ab2c20, frame=0xc55c9d38) at /usr/src/sys/kern/kern_fork.c:811
#4  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271
Current language:  auto; currently c

Thread 42 (Thread 100041):
#0  fork_trampoline () at /usr/src/sys/i386/i386/exception.s:268
Current language:  auto; currently asm

Thread 41 (Thread 100040):
#0  sched_switch (td=0xc5aa1d80, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05cf859 in sleepq_switch (wchan=Variable "wchan" is not available.
) at /usr/src/sys/kern/subr_sleepqueue.c:497
#3  0xc05d03d7 in sleepq_timedwait (wchan=0xc5a83c3c) at /usr/src/sys/kern/subr_sleepqueue.c:615
#4  0xc05a3483 in _sleep (ident=0xc5a83c3c, lock=0xc5a83cf0, priority=76, wmesg=0xc081c912 "-", timo=1000) at /usr/src/sys/kern/kern_synch.c:226
#5  0xc07b319d in fdc_thread (arg=dwarf2_read_address: Corrupted DWARF expression.
) at /usr/src/sys/dev/fdc/fdc.c:812
#6  0xc0574587 in fork_exit (callout=0xc07b2db0 <fdc_thread>, arg=0xc5a83c00, frame=0xc55c3d38) at /usr/src/sys/kern/kern_fork.c:811
#7  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271
Current language:  auto; currently c

Thread 40 (Thread 100039):
#0  sched_switch (td=0xc5aa2000, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc0577dbb in ithread_loop (arg=0xc5a8daa0) at /usr/src/sys/kern/kern_intr.c:1225
#3  0xc0574587 in fork_exit (callout=0xc0577ab0 <ithread_loop>, arg=0xc5a8daa0, frame=0xc55b6d38) at /usr/src/sys/kern/kern_fork.c:811
#4  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 39 (Thread 100038):
#0  sched_switch (td=0xc59b2d80, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
---Type <return> to continue, or q <return> to quit---
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc0577dbb in ithread_loop (arg=0xc5a8d1e0) at /usr/src/sys/kern/kern_intr.c:1225
#3  0xc0574587 in fork_exit (callout=0xc0577ab0 <ithread_loop>, arg=0xc5a8d1e0, frame=0xc559ed38) at /usr/src/sys/kern/kern_fork.c:811
#4  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 38 (Thread 100037):
#0  sched_switch (td=0xc5a60000, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05cf859 in sleepq_switch (wchan=Variable "wchan" is not available.
) at /usr/src/sys/kern/subr_sleepqueue.c:497
#3  0xc05d03d7 in sleepq_timedwait (wchan=0xc5999210) at /usr/src/sys/kern/subr_sleepqueue.c:615
#4  0xc05a3483 in _sleep (ident=0xc5999210, lock=0x0, priority=92, wmesg=0xc081bb4e "usbevt", timo=60000) at /usr/src/sys/kern/kern_synch.c:226
#5  0xc051cad5 in usb_event_thread (arg=0xc5a8f3c0) at /usr/src/sys/dev/usb/usb.c:445
#6  0xc0574587 in fork_exit (callout=0xc051c9e0 <usb_event_thread>, arg=0xc5a8f3c0, frame=0xc5597d38) at /usr/src/sys/kern/kern_fork.c:811
#7  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 37 (Thread 100036):
#0  sched_switch (td=0xc5a60240, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05cf859 in sleepq_switch (wchan=Variable "wchan" is not available.
) at /usr/src/sys/kern/subr_sleepqueue.c:497
#3  0xc05d03d7 in sleepq_timedwait (wchan=0xc5a7e210) at /usr/src/sys/kern/subr_sleepqueue.c:615
#4  0xc05a3483 in _sleep (ident=0xc5a7e210, lock=0x0, priority=92, wmesg=0xc081bb4e "usbevt", timo=60000) at /usr/src/sys/kern/kern_synch.c:226
#5  0xc051cad5 in usb_event_thread (arg=0xc5a57900) at /usr/src/sys/dev/usb/usb.c:445
#6  0xc0574587 in fork_exit (callout=0xc051c9e0 <usb_event_thread>, arg=0xc5a57900, frame=0xc5584d38) at /usr/src/sys/kern/kern_fork.c:811
#7  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 36 (Thread 100035):
#0  fork_trampoline () at /usr/src/sys/i386/i386/exception.s:268
Current language:  auto; currently asm

Thread 35 (Thread 100034):
#0  sched_switch (td=0xc5a606c0, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05cf859 in sleepq_switch (wchan=Variable "wchan" is not available.
) at /usr/src/sys/kern/subr_sleepqueue.c:497
#3  0xc05d03d7 in sleepq_timedwait (wchan=0xc5a65210) at /usr/src/sys/kern/subr_sleepqueue.c:615
#4  0xc05a3483 in _sleep (ident=0xc5a65210, lock=0x0, priority=92, wmesg=0xc081bb4e "usbevt", timo=60000) at /usr/src/sys/kern/kern_synch.c:226
#5  0xc051cad5 in usb_event_thread (arg=0xc5a62240) at /usr/src/sys/dev/usb/usb.c:445
#6  0xc0574587 in fork_exit (callout=0xc051c9e0 <usb_event_thread>, arg=0xc5a62240, frame=0xc557dd38) at /usr/src/sys/kern/kern_fork.c:811
#7  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271
Current language:  auto; currently c

Thread 34 (Thread 100033):
#0  sched_switch (td=0xc5a60900, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05cf859 in sleepq_switch (wchan=Variable "wchan" is not available.
) at /usr/src/sys/kern/subr_sleepqueue.c:497
#3  0xc05d03d7 in sleepq_timedwait (wchan=0xc5a6d210) at /usr/src/sys/kern/subr_sleepqueue.c:615
#4  0xc05a3483 in _sleep (ident=0xc5a6d210, lock=0x0, priority=92, wmesg=0xc081bb4e "usbevt", timo=60000) at /usr/src/sys/kern/kern_synch.c:226
#5  0xc051cad5 in usb_event_thread (arg=0xc5a62a80) at /usr/src/sys/dev/usb/usb.c:445
#6  0xc0574587 in fork_exit (callout=0xc051c9e0 <usb_event_thread>, arg=0xc5a62a80, frame=0xc5579d38) at /usr/src/sys/kern/kern_fork.c:811
#7  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 33 (Thread 100032):
#0  fork_trampoline () at /usr/src/sys/i386/i386/exception.s:268
Current language:  auto; currently asm

Thread 32 (Thread 100031):
#0  sched_switch (td=0xc5a60d80, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05cf859 in sleepq_switch (wchan=Variable "wchan" is not available.
) at /usr/src/sys/kern/subr_sleepqueue.c:497
#3  0xc05cfec6 in sleepq_wait (wchan=0xc08a1b54) at /usr/src/sys/kern/subr_sleepqueue.c:580
#4  0xc05a34a5 in _sleep (ident=0xc08a1b54, lock=0x0, priority=92, wmesg=0xc081bb40 "usbtsk", timo=0) at /usr/src/sys/kern/kern_synch.c:230
#5  0xc051c97e in usb_task_thread (arg=0xc08a1b54) at /usr/src/sys/dev/usb/usb.c:475
---Type <return> to continue, or q <return> to quit---
#6  0xc0574587 in fork_exit (callout=0xc051c900 <usb_task_thread>, arg=0xc08a1b54, frame=0xc5572d38) at /usr/src/sys/kern/kern_fork.c:811
#7  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271
Current language:  auto; currently c

Thread 31 (Thread 100030):
#0  sched_switch (td=0xc5a61000, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05cf859 in sleepq_switch (wchan=Variable "wchan" is not available.
) at /usr/src/sys/kern/subr_sleepqueue.c:497
#3  0xc05cfec6 in sleepq_wait (wchan=0xc08a1b40) at /usr/src/sys/kern/subr_sleepqueue.c:580
#4  0xc05a34a5 in _sleep (ident=0xc08a1b40, lock=0x0, priority=92, wmesg=0xc081bb40 "usbtsk", timo=0) at /usr/src/sys/kern/kern_synch.c:230
#5  0xc051c97e in usb_task_thread (arg=0xc08a1b40) at /usr/src/sys/dev/usb/usb.c:475
#6  0xc0574587 in fork_exit (callout=0xc051c900 <usb_task_thread>, arg=0xc08a1b40, frame=0xc556fd38) at /usr/src/sys/kern/kern_fork.c:811
#7  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 30 (Thread 100029):
#0  sched_switch (td=0xc5a61240, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05cf859 in sleepq_switch (wchan=Variable "wchan" is not available.
) at /usr/src/sys/kern/subr_sleepqueue.c:497
#3  0xc05d03d7 in sleepq_timedwait (wchan=0xc5a4c210) at /usr/src/sys/kern/subr_sleepqueue.c:615
#4  0xc05a3483 in _sleep (ident=0xc5a4c210, lock=0x0, priority=92, wmesg=0xc081bb4e "usbevt", timo=60000) at /usr/src/sys/kern/kern_synch.c:226
#5  0xc051cad5 in usb_event_thread (arg=0xc5a63500) at /usr/src/sys/dev/usb/usb.c:445
#6  0xc0574587 in fork_exit (callout=0xc051c9e0 <usb_event_thread>, arg=0xc5a63500, frame=0xc556cd38) at /usr/src/sys/kern/kern_fork.c:811
#7  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 29 (Thread 100028):
#0  sched_switch (td=0xc5a61480, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc0577dbb in ithread_loop (arg=0xc5a5b9d0) at /usr/src/sys/kern/kern_intr.c:1225
#3  0xc0574587 in fork_exit (callout=0xc0577ab0 <ithread_loop>, arg=0xc5a5b9d0, frame=0xc5568d38) at /usr/src/sys/kern/kern_fork.c:811
#4  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 28 (Thread 100027):
#0  sched_switch (td=0xc58da6c0, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc0577dbb in ithread_loop (arg=0xc5a5b220) at /usr/src/sys/kern/kern_intr.c:1225
#3  0xc0574587 in fork_exit (callout=0xc0577ab0 <ithread_loop>, arg=0xc5a5b220, frame=0xc5565d38) at /usr/src/sys/kern/kern_fork.c:811
#4  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 27 (Thread 100026):
#0  sched_switch (td=0xc58da900, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc0577dbb in ithread_loop (arg=0xc5a5b110) at /usr/src/sys/kern/kern_intr.c:1225
#3  0xc0574587 in fork_exit (callout=0xc0577ab0 <ithread_loop>, arg=0xc5a5b110, frame=0xc554fd38) at /usr/src/sys/kern/kern_fork.c:811
#4  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 26 (Thread 100025):
#0  sched_switch (td=0xc58dab40, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc0577dbb in ithread_loop (arg=0xc5a5b020) at /usr/src/sys/kern/kern_intr.c:1225
#3  0xc0574587 in fork_exit (callout=0xc0577ab0 <ithread_loop>, arg=0xc5a5b020, frame=0xc5513d38) at /usr/src/sys/kern/kern_fork.c:811
#4  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 25 (Thread 100024):
#0  fork_trampoline () at /usr/src/sys/i386/i386/exception.s:268
Current language:  auto; currently asm

Thread 24 (Thread 100023):
#0  sched_switch (td=0xc59b2000, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc0577dbb in ithread_loop (arg=0xc59fa980) at /usr/src/sys/kern/kern_intr.c:1225
---Type <return> to continue, or q <return> to quit---
#3  0xc0574587 in fork_exit (callout=0xc0577ab0 <ithread_loop>, arg=0xc59fa980, frame=0xc54fad38) at /usr/src/sys/kern/kern_fork.c:811
#4  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271
Current language:  auto; currently c

Thread 23 (Thread 100022):
#0  fork_trampoline () at /usr/src/sys/i386/i386/exception.s:268
Current language:  auto; currently asm

Thread 22 (Thread 100021):
#0  sched_switch (td=0xc59b2480, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05cf859 in sleepq_switch (wchan=Variable "wchan" is not available.
) at /usr/src/sys/kern/subr_sleepqueue.c:497
#3  0xc05cfec6 in sleepq_wait (wchan=0xc588bd80) at /usr/src/sys/kern/subr_sleepqueue.c:580
#4  0xc05a34a5 in _sleep (ident=0xc588bd80, lock=0xc588bd9c, priority=0, wmesg=0xc081c912 "-", timo=0) at /usr/src/sys/kern/kern_synch.c:230
#5  0xc05d1708 in taskqueue_thread_loop (arg=0xc08a279c) at /usr/src/sys/kern/subr_taskqueue.c:95
#6  0xc0574587 in fork_exit (callout=0xc05d1600 <taskqueue_thread_loop>, arg=0xc08a279c, frame=0xc54e6d38) at /usr/src/sys/kern/kern_fork.c:811
#7  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271
Current language:  auto; currently c

Thread 21 (Thread 100020):
#0  sched_switch (td=0xc59b26c0, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc0577dbb in ithread_loop (arg=0xc59a3290) at /usr/src/sys/kern/kern_intr.c:1225
#3  0xc0574587 in fork_exit (callout=0xc0577ab0 <ithread_loop>, arg=0xc59a3290, frame=0xc54e3d38) at /usr/src/sys/kern/kern_fork.c:811
#4  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 20 (Thread 100019):
#0  sched_switch (td=0xc59b2900, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc0577dbb in ithread_loop (arg=0xc59a32a0) at /usr/src/sys/kern/kern_intr.c:1225
#3  0xc0574587 in fork_exit (callout=0xc0577ab0 <ithread_loop>, arg=0xc59a32a0, frame=0xc54e0d38) at /usr/src/sys/kern/kern_fork.c:811
#4  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 19 (Thread 100018):
#0  sched_switch (td=0xc59b2b40, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05cf859 in sleepq_switch (wchan=Variable "wchan" is not available.
) at /usr/src/sys/kern/subr_sleepqueue.c:497
#3  0xc05cfec6 in sleepq_wait (wchan=0xc58ef000) at /usr/src/sys/kern/subr_sleepqueue.c:580
#4  0xc05a34a5 in _sleep (ident=0xc58ef000, lock=0xc58ef01c, priority=0, wmesg=0xc081c912 "-", timo=0) at /usr/src/sys/kern/kern_synch.c:230
#5  0xc05d1708 in taskqueue_thread_loop (arg=0xc1159f24) at /usr/src/sys/kern/subr_taskqueue.c:95
#6  0xc0574587 in fork_exit (callout=0xc05d1600 <taskqueue_thread_loop>, arg=0xc1159f24, frame=0xc54ddd38) at /usr/src/sys/kern/kern_fork.c:811
#7  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 18 (Thread 100017):
#0  sched_switch (td=0xc5891240, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05cf859 in sleepq_switch (wchan=Variable "wchan" is not available.
) at /usr/src/sys/kern/subr_sleepqueue.c:497
#3  0xc05cfec6 in sleepq_wait (wchan=0xc58ef000) at /usr/src/sys/kern/subr_sleepqueue.c:580
#4  0xc05a34a5 in _sleep (ident=0xc58ef000, lock=0xc58ef01c, priority=0, wmesg=0xc081c912 "-", timo=0) at /usr/src/sys/kern/kern_synch.c:230
#5  0xc05d1708 in taskqueue_thread_loop (arg=0xc1159f24) at /usr/src/sys/kern/subr_taskqueue.c:95
#6  0xc0574587 in fork_exit (callout=0xc05d1600 <taskqueue_thread_loop>, arg=0xc1159f24, frame=0xc54dad38) at /usr/src/sys/kern/kern_fork.c:811
#7  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 17 (Thread 100016):
#0  sched_switch (td=0xc5891480, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05cf859 in sleepq_switch (wchan=Variable "wchan" is not available.
) at /usr/src/sys/kern/subr_sleepqueue.c:497
#3  0xc05cfec6 in sleepq_wait (wchan=0xc58ef000) at /usr/src/sys/kern/subr_sleepqueue.c:580
#4  0xc05a34a5 in _sleep (ident=0xc58ef000, lock=0xc58ef01c, priority=0, wmesg=0xc081c912 "-", timo=0) at /usr/src/sys/kern/kern_synch.c:230
#5  0xc05d1708 in taskqueue_thread_loop (arg=0xc1159f24) at /usr/src/sys/kern/subr_taskqueue.c:95
#6  0xc0574587 in fork_exit (callout=0xc05d1600 <taskqueue_thread_loop>, arg=0xc1159f24, frame=0xc54d7d38) at /usr/src/sys/kern/kern_fork.c:811
---Type <return> to continue, or q <return> to quit---
#7  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 16 (Thread 100015):
#0  sched_switch (td=0xc58916c0, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05cf859 in sleepq_switch (wchan=Variable "wchan" is not available.
) at /usr/src/sys/kern/subr_sleepqueue.c:497
#3  0xc05cfec6 in sleepq_wait (wchan=0xc58ef080) at /usr/src/sys/kern/subr_sleepqueue.c:580
#4  0xc05a34a5 in _sleep (ident=0xc58ef080, lock=0xc58ef09c, priority=0, wmesg=0xc081c912 "-", timo=0) at /usr/src/sys/kern/kern_synch.c:230
#5  0xc05d1708 in taskqueue_thread_loop (arg=0xc08b061c) at /usr/src/sys/kern/subr_taskqueue.c:95
#6  0xc0574587 in fork_exit (callout=0xc05d1600 <taskqueue_thread_loop>, arg=0xc08b061c, frame=0xc54d4d38) at /usr/src/sys/kern/kern_fork.c:811
#7  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 15 (Thread 100014):
#0  fork_trampoline () at /usr/src/sys/i386/i386/exception.s:268
Current language:  auto; currently asm

Thread 14 (Thread 100013):
#0  sched_switch (td=0xc5891b40, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc0577dbb in ithread_loop (arg=0xc59a32e0) at /usr/src/sys/kern/kern_intr.c:1225
#3  0xc0574587 in fork_exit (callout=0xc0577ab0 <ithread_loop>, arg=0xc59a32e0, frame=0xc54ced38) at /usr/src/sys/kern/kern_fork.c:811
#4  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271
Current language:  auto; currently c

Thread 13 (Thread 100012):
#0  sched_switch (td=0xc5891d80, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05cf859 in sleepq_switch (wchan=Variable "wchan" is not available.
) at /usr/src/sys/kern/subr_sleepqueue.c:497
#3  0xc05cfec6 in sleepq_wait (wchan=0xc088d214) at /usr/src/sys/kern/subr_sleepqueue.c:580
#4  0xc05a34a5 in _sleep (ident=0xc088d214, lock=0xc088d22c, priority=76, wmesg=0xc0803242 "ccb_scanq", timo=0) at /usr/src/sys/kern/kern_synch.c:230
#5  0xc0446491 in xpt_scanner_thread (dummy=0x0) at /usr/src/sys/cam/cam_xpt.c:1399
#6  0xc0574587 in fork_exit (callout=0xc0446450 <xpt_scanner_thread>, arg=0x0, frame=0xc54cbd38) at /usr/src/sys/kern/kern_fork.c:811
#7  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 12 (Thread 100011):
#0  sched_switch (td=0xc58da000, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05cf859 in sleepq_switch (wchan=Variable "wchan" is not available.
) at /usr/src/sys/kern/subr_sleepqueue.c:497
#3  0xc05d03d7 in sleepq_timedwait (wchan=0xc08a44b4) at /usr/src/sys/kern/subr_sleepqueue.c:615
#4  0xc05a3483 in _sleep (ident=0xc08a44b4, lock=0x0, priority=0, wmesg=0xc081c912 "-", timo=100) at /usr/src/sys/kern/kern_synch.c:226
#5  0xc05a35a0 in pause (wmesg=0xc081c912 "-", timo=100) at /usr/src/sys/kern/kern_synch.c:334
#6  0xc04c3e72 in random_kthread (arg=0x0) at /usr/src/sys/dev/random/randomdev_soft.c:289
#7  0xc0574587 in fork_exit (callout=0xc04c3c40 <random_kthread>, arg=0x0, frame=0xc54c8d38) at /usr/src/sys/kern/kern_fork.c:811
#8  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 11 (Thread 100010):
#0  sched_switch (td=0xc58da240, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05cf859 in sleepq_switch (wchan=Variable "wchan" is not available.
) at /usr/src/sys/kern/subr_sleepqueue.c:497
#3  0xc05d03d7 in sleepq_timedwait (wchan=0xc08a1f0c) at /usr/src/sys/kern/subr_sleepqueue.c:615
#4  0xc05a3483 in _sleep (ident=0xc08a1f0c, lock=0xc08a1e28, priority=588, wmesg=0xc081c912 "-", timo=100) at /usr/src/sys/kern/kern_synch.c:226
#5  0xc053f22b in g_io_schedule_down (tp=0xc58da240) at /usr/src/sys/geom/geom_io.c:487
#6  0xc053f94c in g_down_procbody () at /usr/src/sys/geom/geom_kern.c:118
#7  0xc0574587 in fork_exit (callout=0xc053f8e0 <g_down_procbody>, arg=0x0, frame=0xc54c5d38) at /usr/src/sys/kern/kern_fork.c:811
#8  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 10 (Thread 100009):
#0  sched_switch (td=0xc58da480, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05cf859 in sleepq_switch (wchan=Variable "wchan" is not available.
) at /usr/src/sys/kern/subr_sleepqueue.c:497
---Type <return> to continue, or q <return> to quit---
#3  0xc05d03d7 in sleepq_timedwait (wchan=0xc08a1f08) at /usr/src/sys/kern/subr_sleepqueue.c:615
#4  0xc05a3483 in _sleep (ident=0xc08a1f08, lock=0xc08a1e68, priority=588, wmesg=0xc081c912 "-", timo=100) at /usr/src/sys/kern/kern_synch.c:226
#5  0xc053f532 in g_io_schedule_up (tp=0xc58da480) at /usr/src/sys/geom/geom_io.c:592
#6  0xc053f82c in g_up_procbody () at /usr/src/sys/geom/geom_kern.c:95
#7  0xc0574587 in fork_exit (callout=0xc053f7c0 <g_up_procbody>, arg=0x0, frame=0xc54c2d38) at /usr/src/sys/kern/kern_fork.c:811
#8  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 9 (Thread 100008):
#0  sched_switch (td=0xc588f000, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05cf859 in sleepq_switch (wchan=Variable "wchan" is not available.
) at /usr/src/sys/kern/subr_sleepqueue.c:497
#3  0xc05d03d7 in sleepq_timedwait (wchan=0xc08a1f00) at /usr/src/sys/kern/subr_sleepqueue.c:615
#4  0xc05a3483 in _sleep (ident=0xc08a1f00, lock=0x0, priority=76, wmesg=0xc081c912 "-", timo=100) at /usr/src/sys/kern/kern_synch.c:226
#5  0xc053f8da in g_event_procbody () at /usr/src/sys/geom/geom_kern.c:142
#6  0xc0574587 in fork_exit (callout=0xc053f830 <g_event_procbody>, arg=0x0, frame=0xc54bfd38) at /usr/src/sys/kern/kern_fork.c:811
#7  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 8 (Thread 100007):
#0  fork_trampoline () at /usr/src/sys/i386/i386/exception.s:268
Current language:  auto; currently asm

Thread 7 (Thread 100006):
#0  sched_switch (td=0xc588f480, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc07d4682 in ipi_bitmap_handler (frame=
      {tf_fs = 8, tf_es = 40, tf_ds = 40, tf_edi = -644953128, tf_esi = -980880256, tf_ebp = -984900488, tf_isp = -984900532, tf_ebx = -1064681904, tf_edx = -980877952, tf_ecx = -980877952, tf_eax = 4, tf_trapno = 0, tf_err = 0, tf_eip = -1067925921, tf_cs = 32, tf_eflags = 582, tf_esp = -1066191232, tf_ss = 0}) at /usr/src/sys/i386/i386/mp_machdep.c:1187
#3  0xc07c6dae in Xipi_intr_bitmap_handler () at apic_vector.s:284
#4  0xc058be5f in _mtx_lock_sleep (m=0xc08a3e50, tid=3314087040, opts=0, file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:349
#5  0xc05ad91b in softclock (dummy=0x0) at /usr/src/sys/kern/kern_timeout.c:241
#6  0xc0577c5b in ithread_loop (arg=0xc588c390) at /usr/src/sys/kern/kern_intr.c:1126
#7  0xc0574587 in fork_exit (callout=0xc0577ab0 <ithread_loop>, arg=0xc588c390, frame=0xc54b9d38) at /usr/src/sys/kern/kern_fork.c:811
#8  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271
Current language:  auto; currently c

Thread 6 (Thread 100005):
#0  sched_switch (td=0xc588f6c0, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc0577dbb in ithread_loop (arg=0xc588c3a0) at /usr/src/sys/kern/kern_intr.c:1225
#3  0xc0574587 in fork_exit (callout=0xc0577ab0 <ithread_loop>, arg=0xc588c3a0, frame=0xc54b6d38) at /usr/src/sys/kern/kern_fork.c:811
#4  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 5 (Thread 100004):
#0  sched_switch (td=0xc588f900, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05bcedd in critical_exit () at kern_switch.c:185
#3  0xc07ce2f5 in lapic_handle_timer (frame=0xc54b1c48) at /usr/src/sys/i386/i386/local_apic.c:724
#4  0xc07c6c9f in Xtimerint () at apic_vector.s:108
#5  0xc1149b15 in acpi_cpu_c1 () at /usr/src/sys/modules/acpi/acpi/../../../i386/acpica/acpi_machdep.c:550
#6  0xc1142a1d in acpi_cpu_idle () at /usr/src/sys/modules/acpi/acpi/../../../dev/acpica/acpi_cpu.c:912
#7  0xc07d0a58 in cpu_idle () at /usr/src/sys/i386/i386/machdep.c:1183
#8  0xc05bdd6b in sched_idletd (dummy=0x0) at /usr/src/sys/kern/sched_ule.c:2681
#9  0xc0574587 in fork_exit (callout=0xc05bdaa0 <sched_idletd>, arg=0x0, frame=0xc54b1d38) at /usr/src/sys/kern/kern_fork.c:811
#10 0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 4 (Thread 100003):
#0  sched_switch (td=0xc588fb40, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc07d4682 in ipi_bitmap_handler (frame=
      {tf_fs = 8, tf_es = 40, tf_ds = 40, tf_edi = 1, tf_esi = 15, tf_ebp = -984945472, tf_isp = -984945496, tf_ebx = -980878528, tf_edx = 256, tf_ecx = 16, tf_eax = 582, tf_trapno = 0, tf_err = 0, tf_e---Type <return> to continue, or q <return> to quit---
ip = -1065551975, tf_cs = 32, tf_eflags = 582, tf_esp = -1064663296, tf_ss = -984945420}) at /usr/src/sys/i386/i386/mp_machdep.c:1187
#3  0xc07c6dae in Xipi_intr_bitmap_handler () at apic_vector.s:284
#4  0xc07cf799 in spinlock_exit () at cpufunc.h:365
#5  0xc05bdcd6 in sched_idletd (dummy=0x0) at /usr/src/sys/kern/sched_ule.c:806
#6  0xc0574587 in fork_exit (callout=0xc05bdaa0 <sched_idletd>, arg=0x0, frame=0xc54aed38) at /usr/src/sys/kern/kern_fork.c:811
#7  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 3 (Thread 100002):
#0  doadump () at pcpu.h:196
#1  0xc059b097 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418
#2  0xc059b36c in panic (fmt=Variable "fmt" is not available.
) at /usr/src/sys/kern/kern_shutdown.c:574
#3  0xc058bd1f in _mtx_lock_spin_failed (m=0x0) at /usr/src/sys/kern/kern_mutex.c:449
#4  0xc058c425 in _thread_lock_flags (td=0xc588f480, opts=0, file=0xc08200c8 "/usr/src/sys/kern/kern_intr.c", line=801) at /usr/src/sys/kern/kern_mutex.c:537
#5  0xc0576787 in intr_event_schedule_thread (ie=Variable "ie" is not available.
) at /usr/src/sys/kern/kern_intr.c:801
#6  0xc0577aa5 in swi_sched (cookie=0xc5880e00, flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_intr.c:1028
#7  0xc055a6df in hardclock (usermode=0, pc=3229503748) at /usr/src/sys/kern/kern_clock.c:339
#8  0xc07ce23a in lapic_handle_timer (frame=0xc54aaba0) at /usr/src/sys/i386/i386/local_apic.c:705
#9  0xc07c6c9f in Xtimerint () at apic_vector.s:108
#10 0xc07e5104 in DELAY (n=1000000) at cpufunc.h:352
#11 0xc07e2c03 in cpu_reset () at /usr/src/sys/i386/i386/vm_machdep.c:594
#12 0xc059a753 in shutdown_reset (junk=0x0, howto=0) at /usr/src/sys/kern/kern_shutdown.c:493
#13 0xc059b117 in boot (howto=0) at /usr/src/sys/kern/kern_shutdown.c:421
#14 0xc059b247 in reboot (td=0xc588fd80, uap=0xc54aacfc) at /usr/src/sys/kern/kern_shutdown.c:172
#15 0xc07e07d5 in syscall (frame=0xc54aad38) at /usr/src/sys/i386/i386/trap.c:1089
#16 0xc07c6720 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:262
#17 0x00000033 in ?? ()
Previous frame inner to this frame (corrupt stack?)

Thread 2 (Thread 100001):
#0  sched_switch (td=0xc5891000, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05cf859 in sleepq_switch (wchan=Variable "wchan" is not available.
) at /usr/src/sys/kern/subr_sleepqueue.c:497
#3  0xc05cfec6 in sleepq_wait (wchan=0xc08bcd48) at /usr/src/sys/kern/subr_sleepqueue.c:580
#4  0xc055aaaf in _cv_wait (cvp=0xc08bcd48, lock=0xc08bcd28) at /usr/src/sys/kern/kern_condvar.c:137
#5  0xc0749e2f in audit_worker (arg=0x0) at /usr/src/sys/security/audit/audit_worker.c:410
#6  0xc0574587 in fork_exit (callout=0xc0749dc0 <audit_worker>, arg=0x0, frame=0xc54a7d38) at /usr/src/sys/kern/kern_fork.c:811
#7  0xc07c6730 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271

Thread 1 (Thread 100000):
#0  sched_switch (td=0xc08a2280, newtd=Variable "newtd" is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable "flags" is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05cf859 in sleepq_switch (wchan=Variable "wchan" is not available.
) at /usr/src/sys/kern/subr_sleepqueue.c:497
#3  0xc05d03d7 in sleepq_timedwait (wchan=0xc08a1fc0) at /usr/src/sys/kern/subr_sleepqueue.c:615
#4  0xc05a3483 in _sleep (ident=0xc08a1fc0, lock=0x0, priority=68, wmesg=0xc0823aef "sched", timo=10000) at /usr/src/sys/kern/kern_synch.c:226
#5  0xc078df39 in scheduler (dummy=0x0) at /usr/src/sys/vm/vm_glue.c:733
#6  0xc05577b6 in mi_startup () at /usr/src/sys/kern/init_main.c:251
#7  0xc0440685 in begin () at /usr/src/sys/i386/i386/locore.s:328
196		__asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb) quit


From blackend at freebsd.org  Sun Jul 26 08:32:18 2009
From: blackend at freebsd.org (Marc Fonvieille)
Date: Sun Jul 26 08:32:26 2009
Subject: status of flash9/flash10 support in RELENG_7 ?
In-Reply-To: <KNDLLL$F3FF28F7BB21D7F36CB492E8D4CB6EA3@libero.it>
References: <KNDLLL$F3FF28F7BB21D7F36CB492E8D4CB6EA3@libero.it>
Message-ID: <20090726083246.GA1251@gothic.blackend.org>

On Sun, Jul 26, 2009 at 08:20:09AM +0200, barbara wrote:
> > 
> > An example of the URLs that is giving me problems is the following
> > 
> > http://tv.repubblica.it/copertina/massa-colpito-da-un-detrito/35446?video
> > 
> > (basically all videos from that site cause the same problem). I would be
> > grateful if you cold check it.
> > 
> 
> 
> The video looks fine here, even if I'm getting a warning about the flash version.
> http://img24.imageshack.us/img24/2741/screenshotmassacolpitod.png
> 
> I've found that on 7, the better combination for me is
> linux-flashplugin9, linux_base-fc4 and compat.linux.osrelease=2.4.2.

Same here: the video plays fine on 7.2-S with linux_base-fc4 and
linux-flashplugin9

> On CURRENT, using linux_base-f10, I get much more stuck process, while
> on 7 it barely happens.

On 8-BETA2 with linux_base-f10 and linux-f10-flashplugin10 that video
makes npviewer "coredumping".

-- 
Marc
From kostikbel at gmail.com  Sun Jul 26 12:06:26 2009
From: kostikbel at gmail.com (Kostik Belousov)
Date: Sun Jul 26 12:06:35 2009
Subject: regression with jexec?
In-Reply-To: <4A6BAC1A.5080303@protected-networks.net>
References: <4A6B0BD3.6040206@protected-networks.net>
	<4A6B9A60.90302@FreeBSD.org>
	<4A6BAC1A.5080303@protected-networks.net>
Message-ID: <20090726120608.GE55190@deviant.kiev.zoral.com.ua>

On Sat, Jul 25, 2009 at 09:06:34PM -0400, Michael Butler wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Jamie Gritton wrote:
> > Michael Butler wrote:
> >> imb@aaron:/home/imb> sudo jexec 5 tcsh
> >> jexec: Unable to parse jail ID.: No such file or directory
> 
> > 
> > The symptom in jexec can be fixed by this little patch:
> > 
> > Index: usr.sbin/jexec/jexec.c
> > ===================================================================
> > --- usr.sbin/jexec/jexec.c    (revision 195879)
> > +++ usr.sbin/jexec/jexec.c    (working copy)
> > @@ -248,6 +248,7 @@
> >      if (argc < 2)
> >          usage();
> >      if (strlen(argv[0]) > 0) {
> > +        errno = 0;
> >          jid = (int)strtol(argv[0], NULL, 10);
> >          if (errno)
> >              err(1, "Unable to parse jail ID.");
> 
> Thanks - this certainly cures the effect.
> 
> > But the broader problem is malloc.  It's leaving errno set to
> > ENOENT when /etc/malloc.conf doesn't exist.  This seems like
> > wrong behavior to me.
> 
> Seems like a POLA violation to me,

No, this is how errno generally work, it is not changed if no error
happens.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090726/5987c343/attachment.pgp
From bzeeb-lists at lists.zabbadoz.net  Sun Jul 26 12:43:22 2009
From: bzeeb-lists at lists.zabbadoz.net (Bjoern A. Zeeb)
Date: Sun Jul 26 12:43:28 2009
Subject: regression with jexec?
In-Reply-To: <20090726120608.GE55190@deviant.kiev.zoral.com.ua>
References: <4A6B0BD3.6040206@protected-networks.net>
	<4A6B9A60.90302@FreeBSD.org>
	<4A6BAC1A.5080303@protected-networks.net>
	<20090726120608.GE55190@deviant.kiev.zoral.com.ua>
Message-ID: <20090726122230.E245@maildrop.int.zabbadoz.net>

On Sun, 26 Jul 2009, Kostik Belousov wrote:

> On Sat, Jul 25, 2009 at 09:06:34PM -0400, Michael Butler wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Jamie Gritton wrote:
>>> Michael Butler wrote:
>>>> imb@aaron:/home/imb> sudo jexec 5 tcsh
>>>> jexec: Unable to parse jail ID.: No such file or directory
>>
>>>
>>> The symptom in jexec can be fixed by this little patch:
>>>
>>> Index: usr.sbin/jexec/jexec.c
>>> ===================================================================
>>> --- usr.sbin/jexec/jexec.c    (revision 195879)
>>> +++ usr.sbin/jexec/jexec.c    (working copy)
>>> @@ -248,6 +248,7 @@
>>>      if (argc < 2)
>>>          usage();
>>>      if (strlen(argv[0]) > 0) {
>>> +        errno = 0;
>>>          jid = (int)strtol(argv[0], NULL, 10);
>>>          if (errno)
>>>              err(1, "Unable to parse jail ID.");
>>
>> Thanks - this certainly cures the effect.
>>
>>> But the broader problem is malloc.  It's leaving errno set to
>>> ENOENT when /etc/malloc.conf doesn't exist.  This seems like
>>> wrong behavior to me.
>>
>> Seems like a POLA violation to me,
>
> No, this is how errno generally work, it is not changed if no error
> happens.

I haven't really understood which part, when and why would set the errno in
first place so that it would still be there?  Is it something in jexec
that gets the errno in first place or is it something internal to
malloc that sets it returns successfully and doesn't clear it?

-- 
Bjoern A. Zeeb                      The greatest risk is not taking one.
From jamie at FreeBSD.org  Sun Jul 26 14:28:10 2009
From: jamie at FreeBSD.org (Jamie Gritton)
Date: Sun Jul 26 14:28:17 2009
Subject: regression with jexec?
In-Reply-To: <20090726122230.E245@maildrop.int.zabbadoz.net>
References: <4A6B0BD3.6040206@protected-networks.net>
	<4A6B9A60.90302@FreeBSD.org>
	<4A6BAC1A.5080303@protected-networks.net>
	<20090726120608.GE55190@deviant.kiev.zoral.com.ua>
	<20090726122230.E245@maildrop.int.zabbadoz.net>
Message-ID: <4A6C67F5.8080408@FreeBSD.org>

Bjoern A. Zeeb wrote:
> On Sun, 26 Jul 2009, Kostik Belousov wrote:
> 
>> On Sat, Jul 25, 2009 at 09:06:34PM -0400, Michael Butler wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> Jamie Gritton wrote:
>>>> Michael Butler wrote:
>>>>> imb@aaron:/home/imb> sudo jexec 5 tcsh
>>>>> jexec: Unable to parse jail ID.: No such file or directory
>>>
>>>>
>>>> The symptom in jexec can be fixed by this little patch:
>>>>
>>>> Index: usr.sbin/jexec/jexec.c
>>>> ===================================================================
>>>> --- usr.sbin/jexec/jexec.c    (revision 195879)
>>>> +++ usr.sbin/jexec/jexec.c    (working copy)
>>>> @@ -248,6 +248,7 @@
>>>>      if (argc < 2)
>>>>          usage();
>>>>      if (strlen(argv[0]) > 0) {
>>>> +        errno = 0;
>>>>          jid = (int)strtol(argv[0], NULL, 10);
>>>>          if (errno)
>>>>              err(1, "Unable to parse jail ID.");
>>>
>>> Thanks - this certainly cures the effect.
>>>
>>>> But the broader problem is malloc.  It's leaving errno set to
>>>> ENOENT when /etc/malloc.conf doesn't exist.  This seems like
>>>> wrong behavior to me.
>>>
>>> Seems like a POLA violation to me,
>>
>> No, this is how errno generally work, it is not changed if no error
>> happens.
> 
> I haven't really understood which part, when and why would set the errno in
> first place so that it would still be there?  Is it something in jexec
> that gets the errno in first place or is it something internal to
> malloc that sets it returns successfully and doesn't clear it?

The POLA violation is in malloc - it sets errno even when there was no
error.  The allocation succeeded and a pointer was returned, yet errno
was set to ENOENT (not even an error malloc should be able to return).
The fact that malloc looks for an optional config file and doesn't find
one shouldn't be relayed back to the caller in errno.  If
/etc/malloc.conf doesn't exist, it should either clear errno after that,
or perhaps restore its previous value.  There's also a
getenv("MALLOC_OPTIONS") that can similarly set errno.

Perhaps this has all been gone over before and I missed it (this is from
code that's been stable since 2006), so I wouldn't want to just rush in
and fix malloc.  Maybe this general principle has already been discussed
and my viewpoint lost.  But if not, it's my opinion that malloc is
acting badly and needs a change.

In the meantime, I have no problem with errno not being cleared in
strtol, and the patch to jexec is correct (though strictly speaking it
shouldn't be necessary since we "know" errno has not yet been set).

- Jamie
From attilio at freebsd.org  Sun Jul 26 14:36:46 2009
From: attilio at freebsd.org (Attilio Rao)
Date: Sun Jul 26 14:36:53 2009
Subject: kern/134584: [panic] spin lock held too long
In-Reply-To: <KNDMU8$8EFE8DA350FF14C54F1F3D61C7265B47@libero.it>
References: <KNDMU8$8EFE8DA350FF14C54F1F3D61C7265B47@libero.it>
Message-ID: <3bbf2fe10907260736j3182af26v5346a4d9d2df2a84@mail.gmail.com>

2009/7/26 barbara <barbara.xxx1975@libero.it>:
> It happened again, on shutdown.
> As the previous time, it happened after a high (for a desktop) uptime and, if it could matter, after running net-p2p/transmission-gtk2 for several hours.
> I don't know if it's related, but often quitting transmission, doesn't terminate the process. Sometimes it end after several minutes the gui exited, sometimes it's still running after hours.
> I've noticed it as the destination folder is on a manually mounted device and I can't umount it as fstat reports the device used by a transmission process.
> So I often have to kill it.
> This happened both the time I had this kind of panic.

Can you try to reproduce it with WITNESS and *without*
WITNESS_SKIPSPIN? I would need to look at "show alllocks" and
possibily "ps" because it seems that the lock owner is preempted but
it should not happen while holding a spinlock (unless the acquired
spinlock is the one in the preempting path, in this case thought it
should drop inside sched_switch() and we can try to understand why
that doesn't happen).

Thanks,
Attilio


-- 
Peace can only be achieved by understanding - A. Einstein
From kostikbel at gmail.com  Sun Jul 26 14:42:34 2009
From: kostikbel at gmail.com (Kostik Belousov)
Date: Sun Jul 26 14:42:41 2009
Subject: regression with jexec?
In-Reply-To: <4A6C67F5.8080408@FreeBSD.org>
References: <4A6B0BD3.6040206@protected-networks.net>
	<4A6B9A60.90302@FreeBSD.org>
	<4A6BAC1A.5080303@protected-networks.net>
	<20090726120608.GE55190@deviant.kiev.zoral.com.ua>
	<20090726122230.E245@maildrop.int.zabbadoz.net>
	<4A6C67F5.8080408@FreeBSD.org>
Message-ID: <20090726144227.GK55190@deviant.kiev.zoral.com.ua>

On Sun, Jul 26, 2009 at 08:28:05AM -0600, Jamie Gritton wrote:
> Bjoern A. Zeeb wrote:
> >On Sun, 26 Jul 2009, Kostik Belousov wrote:
> >
> >>On Sat, Jul 25, 2009 at 09:06:34PM -0400, Michael Butler wrote:
> >>>-----BEGIN PGP SIGNED MESSAGE-----
> >>>Hash: SHA1
> >>>
> >>>Jamie Gritton wrote:
> >>>>Michael Butler wrote:
> >>>>>imb@aaron:/home/imb> sudo jexec 5 tcsh
> >>>>>jexec: Unable to parse jail ID.: No such file or directory
> >>>
> >>>>
> >>>>The symptom in jexec can be fixed by this little patch:
> >>>>
> >>>>Index: usr.sbin/jexec/jexec.c
> >>>>===================================================================
> >>>>--- usr.sbin/jexec/jexec.c    (revision 195879)
> >>>>+++ usr.sbin/jexec/jexec.c    (working copy)
> >>>>@@ -248,6 +248,7 @@
> >>>>     if (argc < 2)
> >>>>         usage();
> >>>>     if (strlen(argv[0]) > 0) {
> >>>>+        errno = 0;
> >>>>         jid = (int)strtol(argv[0], NULL, 10);
> >>>>         if (errno)
> >>>>             err(1, "Unable to parse jail ID.");
> >>>
> >>>Thanks - this certainly cures the effect.
> >>>
> >>>>But the broader problem is malloc.  It's leaving errno set to
> >>>>ENOENT when /etc/malloc.conf doesn't exist.  This seems like
> >>>>wrong behavior to me.
> >>>
> >>>Seems like a POLA violation to me,
> >>
> >>No, this is how errno generally work, it is not changed if no error
> >>happens.
> >
> >I haven't really understood which part, when and why would set the errno in
> >first place so that it would still be there?  Is it something in jexec
> >that gets the errno in first place or is it something internal to
> >malloc that sets it returns successfully and doesn't clear it?
> 
> The POLA violation is in malloc - it sets errno even when there was no
> error.  The allocation succeeded and a pointer was returned, yet errno
> was set to ENOENT (not even an error malloc should be able to return).
> The fact that malloc looks for an optional config file and doesn't find
> one shouldn't be relayed back to the caller in errno.  If
> /etc/malloc.conf doesn't exist, it should either clear errno after that,
> or perhaps restore its previous value.  There's also a
> getenv("MALLOC_OPTIONS") that can similarly set errno.
> 
> Perhaps this has all been gone over before and I missed it (this is from
> code that's been stable since 2006), so I wouldn't want to just rush in
> and fix malloc.  Maybe this general principle has already been discussed
> and my viewpoint lost.  But if not, it's my opinion that malloc is
> acting badly and needs a change.
> 
> In the meantime, I have no problem with errno not being cleared in
> strtol, and the patch to jexec is correct (though strictly speaking it
> shouldn't be necessary since we "know" errno has not yet been set).
Let me restate that errno is never cleared when no error occured.
It is only set when error took place.

E.g., for syscalls, you should look into errno only if syscall returned
-1, in most cases.

For non-syscall libc functions, you need to clear errno before the call,
then check for the error return (for strtoul that would be ULONG_MAX
or 0), that seems to be missed from your patch, and only then look for
errno.

See RETURN VALUES section of the strtoul(3).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090726/2e988daf/attachment.pgp
From jamie at FreeBSD.org  Sun Jul 26 14:50:18 2009
From: jamie at FreeBSD.org (Jamie Gritton)
Date: Sun Jul 26 14:50:24 2009
Subject: regression with jexec?
In-Reply-To: <20090726144227.GK55190@deviant.kiev.zoral.com.ua>
References: <4A6B0BD3.6040206@protected-networks.net>
	<4A6B9A60.90302@FreeBSD.org>
	<4A6BAC1A.5080303@protected-networks.net>
	<20090726120608.GE55190@deviant.kiev.zoral.com.ua>
	<20090726122230.E245@maildrop.int.zabbadoz.net>
	<4A6C67F5.8080408@FreeBSD.org>
	<20090726144227.GK55190@deviant.kiev.zoral.com.ua>
Message-ID: <4A6C6D27.2030500@FreeBSD.org>

Kostik Belousov wrote:
> On Sun, Jul 26, 2009 at 08:28:05AM -0600, Jamie Gritton wrote:
>> Bjoern A. Zeeb wrote:
>>> On Sun, 26 Jul 2009, Kostik Belousov wrote:
>>>
>>>> On Sat, Jul 25, 2009 at 09:06:34PM -0400, Michael Butler wrote:
>>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>>> Hash: SHA1
>>>>>
>>>>> Jamie Gritton wrote:
>>>>>> Michael Butler wrote:
>>>>>>> imb@aaron:/home/imb> sudo jexec 5 tcsh
>>>>>>> jexec: Unable to parse jail ID.: No such file or directory
>>>>>> The symptom in jexec can be fixed by this little patch:
>>>>>>
>>>>>> Index: usr.sbin/jexec/jexec.c
>>>>>> ===================================================================
>>>>>> --- usr.sbin/jexec/jexec.c    (revision 195879)
>>>>>> +++ usr.sbin/jexec/jexec.c    (working copy)
>>>>>> @@ -248,6 +248,7 @@
>>>>>>     if (argc < 2)
>>>>>>         usage();
>>>>>>     if (strlen(argv[0]) > 0) {
>>>>>> +        errno = 0;
>>>>>>         jid = (int)strtol(argv[0], NULL, 10);
>>>>>>         if (errno)
>>>>>>             err(1, "Unable to parse jail ID.");
>>>>> Thanks - this certainly cures the effect.
>>>>>
>>>>>> But the broader problem is malloc.  It's leaving errno set to
>>>>>> ENOENT when /etc/malloc.conf doesn't exist.  This seems like
>>>>>> wrong behavior to me.
>>>>> Seems like a POLA violation to me,
>>>> No, this is how errno generally work, it is not changed if no error
>>>> happens.
>>> I haven't really understood which part, when and why would set the errno in
>>> first place so that it would still be there?  Is it something in jexec
>>> that gets the errno in first place or is it something internal to
>>> malloc that sets it returns successfully and doesn't clear it?
>> The POLA violation is in malloc - it sets errno even when there was no
>> error.  The allocation succeeded and a pointer was returned, yet errno
>> was set to ENOENT (not even an error malloc should be able to return).
>> The fact that malloc looks for an optional config file and doesn't find
>> one shouldn't be relayed back to the caller in errno.  If
>> /etc/malloc.conf doesn't exist, it should either clear errno after that,
>> or perhaps restore its previous value.  There's also a
>> getenv("MALLOC_OPTIONS") that can similarly set errno.
>>
>> Perhaps this has all been gone over before and I missed it (this is from
>> code that's been stable since 2006), so I wouldn't want to just rush in
>> and fix malloc.  Maybe this general principle has already been discussed
>> and my viewpoint lost.  But if not, it's my opinion that malloc is
>> acting badly and needs a change.
>>
>> In the meantime, I have no problem with errno not being cleared in
>> strtol, and the patch to jexec is correct (though strictly speaking it
>> shouldn't be necessary since we "know" errno has not yet been set).
> Let me restate that errno is never cleared when no error occured.
> It is only set when error took place.
> 
> E.g., for syscalls, you should look into errno only if syscall returned
> -1, in most cases.
> 
> For non-syscall libc functions, you need to clear errno before the call,
> then check for the error return (for strtoul that would be ULONG_MAX
> or 0), that seems to be missed from your patch, and only then look for
> errno.
> 
> See RETURN VALUES section of the strtoul(3).

All true - and I'll add the check you mention to my patch.

But what about the malloc case?  Is it equally valid to say that errno
should not be set when no error occurred?  Or are non-syscall libc
functions generally given free reign to overwrite errno in non-error
situations?

- Jamie
From kostikbel at gmail.com  Sun Jul 26 15:12:51 2009
From: kostikbel at gmail.com (Kostik Belousov)
Date: Sun Jul 26 15:12:59 2009
Subject: regression with jexec?
In-Reply-To: <4A6C6D27.2030500@FreeBSD.org>
References: <4A6B0BD3.6040206@protected-networks.net>
	<4A6B9A60.90302@FreeBSD.org>
	<4A6BAC1A.5080303@protected-networks.net>
	<20090726120608.GE55190@deviant.kiev.zoral.com.ua>
	<20090726122230.E245@maildrop.int.zabbadoz.net>
	<4A6C67F5.8080408@FreeBSD.org>
	<20090726144227.GK55190@deviant.kiev.zoral.com.ua>
	<4A6C6D27.2030500@FreeBSD.org>
Message-ID: <20090726151245.GM55190@deviant.kiev.zoral.com.ua>

On Sun, Jul 26, 2009 at 08:50:15AM -0600, Jamie Gritton wrote:
> All true - and I'll add the check you mention to my patch.
> 
> But what about the malloc case?  Is it equally valid to say that errno
> should not be set when no error occurred?  Or are non-syscall libc
> functions generally given free reign to overwrite errno in non-error
> situations?

Yes, they have a blanket to override errno when no error is returned to
the caller. Malloc is good example.

Errno is defined only after error.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090726/32372c15/attachment.pgp
From gaijin.k at gmail.com  Sun Jul 26 15:47:09 2009
From: gaijin.k at gmail.com (Alexandre "Sunny" Kovalenko)
Date: Sun Jul 26 15:47:18 2009
Subject: status of flash9/flash10 support in RELENG_7 ?
In-Reply-To: <20090726083246.GA1251@gothic.blackend.org>
References: <KNDLLL$F3FF28F7BB21D7F36CB492E8D4CB6EA3@libero.it>
	<20090726083246.GA1251@gothic.blackend.org>
Message-ID: <1248623169.1473.8.camel@RabbitsDen>

On Sun, 2009-07-26 at 10:32 +0200, Marc Fonvieille wrote:
> On Sun, Jul 26, 2009 at 08:20:09AM +0200, barbara wrote:
> > > 
> > > An example of the URLs that is giving me problems is the following
> > > 
> > > http://tv.repubblica.it/copertina/massa-colpito-da-un-detrito/35446?video
> > > 
> > > (basically all videos from that site cause the same problem). I would be
> > > grateful if you cold check it.
> > > 
> > 
> > 
> > The video looks fine here, even if I'm getting a warning about the flash version.
> > http://img24.imageshack.us/img24/2741/screenshotmassacolpitod.png
> > 
> > I've found that on 7, the better combination for me is
> > linux-flashplugin9, linux_base-fc4 and compat.linux.osrelease=2.4.2.
> 
> Same here: the video plays fine on 7.2-S with linux_base-fc4 and
> linux-flashplugin9
> 
> > On CURRENT, using linux_base-f10, I get much more stuck process, while
> > on 7 it barely happens.
> 
> On 8-BETA2 with linux_base-f10 and linux-f10-flashplugin10 that video
> makes npviewer "coredumping".
> 
This video played on my 8-BETA2 (r195818, SMP, i386) with linux_base-f10
and linux-f10-flashplugin10 without dumping core. Was your BETA2 before
or after library version bump and, if latter, did you rebuild all your
ports?

-- 
Alexandre Kovalenko (????????? ?????????)


From barbara.xxx1975 at libero.it  Sun Jul 26 16:15:24 2009
From: barbara.xxx1975 at libero.it (barbara)
Date: Sun Jul 26 16:15:32 2009
Subject: status of flash9/flash10 support in RELENG_7 ?
Message-ID: <KNED5M$238DCED7A14CD744CF4DF1C5C45119D9@libero.it>

> On Sun, 2009-07-26 at 10:32 +0200, Marc Fonvieille wrote:
> > On Sun, Jul 26, 2009 at 08:20:09AM +0200, barbara wrote:
> > > > 
> > > > An example of the URLs that is giving me problems is the following
> > > > 
> > > > http://tv.repubblica.it/copertina/massa-colpito-da-un-detrito/35446?video
> > > > 
> > > > (basically all videos from that site cause the same problem). I would be
> > > > grateful if you cold check it.
> > > > 
> > > 
> > > 
> > > The video looks fine here, even if I'm getting a warning about the flash version.
> > > http://img24.imageshack.us/img24/2741/screenshotmassacolpitod.png
> > > 
> > > I've found that on 7, the better combination for me is
> > > linux-flashplugin9, linux_base-fc4 and compat.linux.osrelease=2.4.2.
> > 
> > Same here: the video plays fine on 7.2-S with linux_base-fc4 and
> > linux-flashplugin9
> > 
> > > On CURRENT, using linux_base-f10, I get much more stuck process, while
> > > on 7 it barely happens.
> > 
> > On 8-BETA2 with linux_base-f10 and linux-f10-flashplugin10 that video
> > makes npviewer "coredumping".
> > 
> This video played on my 8-BETA2 (r195818, SMP, i386) with linux_base-f10
> and linux-f10-flashplugin10 without dumping core. Was your BETA2 before
> or after library version bump and, if latter, did you rebuild all your
> ports?
> 

I've cvsupped and rebuilt my system on Jul. 23 and rebuilt all my ports.
linux-f10-flashplugin10 is dumping core or not working for me too.
BTW, why nspluginwrapper doesn't find the plugin?

Barbara


From jamie at FreeBSD.org  Sun Jul 26 16:19:49 2009
From: jamie at FreeBSD.org (Jamie Gritton)
Date: Sun Jul 26 16:19:59 2009
Subject: regression with jexec?
In-Reply-To: <20090726151245.GM55190@deviant.kiev.zoral.com.ua>
References: <4A6B0BD3.6040206@protected-networks.net>
	<4A6B9A60.90302@FreeBSD.org>
	<4A6BAC1A.5080303@protected-networks.net>
	<20090726120608.GE55190@deviant.kiev.zoral.com.ua>
	<20090726122230.E245@maildrop.int.zabbadoz.net>
	<4A6C67F5.8080408@FreeBSD.org>
	<20090726144227.GK55190@deviant.kiev.zoral.com.ua>
	<4A6C6D27.2030500@FreeBSD.org>
	<20090726151245.GM55190@deviant.kiev.zoral.com.ua>
Message-ID: <4A6C8221.6000807@FreeBSD.org>

Kostik Belousov wrote:
> On Sun, Jul 26, 2009 at 08:50:15AM -0600, Jamie Gritton wrote:
>> All true - and I'll add the check you mention to my patch.
>>
>> But what about the malloc case?  Is it equally valid to say that errno
>> should not be set when no error occurred?  Or are non-syscall libc
>> functions generally given free reign to overwrite errno in non-error
>> situations?
> 
> Yes, they have a blanket to override errno when no error is returned to
> the caller. Malloc is good example.
> 
> Errno is defined only after error.

OK then, patching jexec is all that needs doing;  I'll get that in.

- Jamie
From gaijin.k at gmail.com  Sun Jul 26 16:46:59 2009
From: gaijin.k at gmail.com (Alexandre "Sunny" Kovalenko)
Date: Sun Jul 26 16:47:07 2009
Subject: status of flash9/flash10 support in RELENG_7 ?
In-Reply-To: <KNED5M$238DCED7A14CD744CF4DF1C5C45119D9@libero.it>
References: <KNED5M$238DCED7A14CD744CF4DF1C5C45119D9@libero.it>
Message-ID: <1248626758.1473.11.camel@RabbitsDen>

On Sun, 2009-07-26 at 18:15 +0200, barbara wrote:
> > On Sun, 2009-07-26 at 10:32 +0200, Marc Fonvieille wrote:
> > > On Sun, Jul 26, 2009 at 08:20:09AM +0200, barbara wrote:
> > > > > 
> > > > > An example of the URLs that is giving me problems is the following
> > > > > 
> > > > > http://tv.repubblica.it/copertina/massa-colpito-da-un-detrito/35446?video
> > > > > 
> > > > > (basically all videos from that site cause the same problem). I would be
> > > > > grateful if you cold check it.
> > > > > 
> > > > 
> > > > 
> > > > The video looks fine here, even if I'm getting a warning about the flash version.
> > > > http://img24.imageshack.us/img24/2741/screenshotmassacolpitod.png
> > > > 
> > > > I've found that on 7, the better combination for me is
> > > > linux-flashplugin9, linux_base-fc4 and compat.linux.osrelease=2.4.2.
> > > 
> > > Same here: the video plays fine on 7.2-S with linux_base-fc4 and
> > > linux-flashplugin9
> > > 
> > > > On CURRENT, using linux_base-f10, I get much more stuck process, while
> > > > on 7 it barely happens.
> > > 
> > > On 8-BETA2 with linux_base-f10 and linux-f10-flashplugin10 that video
> > > makes npviewer "coredumping".
> > > 
> > This video played on my 8-BETA2 (r195818, SMP, i386) with linux_base-f10
> > and linux-f10-flashplugin10 without dumping core. Was your BETA2 before
> > or after library version bump and, if latter, did you rebuild all your
> > ports?
> > 
> 
> I've cvsupped and rebuilt my system on Jul. 23 and rebuilt all my ports.
> linux-f10-flashplugin10 is dumping core or not working for me too.
> BTW, why nspluginwrapper doesn't find the plugin?

sunny:RabbitsDen>nspluginwrapper -l   
/home/sunny/.mozilla/plugins/npwrapper.nppdf.so
  Original
plugin: /usr/local/Adobe/Reader9/ENU/Adobe/Reader9/Browser/intellinux/nppdf.so
  Wrapper version string: 1.2.2
/home/sunny/.mozilla/plugins/npwrapper.libflashplayer.so
  Original
plugin: /usr/local/lib/npapi/linux-f10-flashplugin/libflashplayer.so
  Wrapper version string: 1.2.2
sunny:RabbitsDen>

Given that wrapped plugins are local to your home directory, maybe you
need to re-wrap them?

-- 
Alexandre Kovalenko (????????? ?????????)


From blackend at freebsd.org  Sun Jul 26 18:00:45 2009
From: blackend at freebsd.org (Marc Fonvieille)
Date: Sun Jul 26 18:00:53 2009
Subject: status of flash9/flash10 support in RELENG_7 ?
In-Reply-To: <KNED5M$238DCED7A14CD744CF4DF1C5C45119D9@libero.it>
References: <KNED5M$238DCED7A14CD744CF4DF1C5C45119D9@libero.it>
Message-ID: <20090726180116.GA1223@gothic.blackend.org>

On Sun, Jul 26, 2009 at 06:15:22PM +0200, barbara wrote:
> > On Sun, 2009-07-26 at 10:32 +0200, Marc Fonvieille wrote:
> > > On Sun, Jul 26, 2009 at 08:20:09AM +0200, barbara wrote:
> > > > > 
> > > > > An example of the URLs that is giving me problems is the following
> > > > > 
> > > > > http://tv.repubblica.it/copertina/massa-colpito-da-un-detrito/35446?video
> > > > > 
> > > > > (basically all videos from that site cause the same problem). I would be
> > > > > grateful if you cold check it.
> > > > > 
> > > > 
> > > > 
> > > > The video looks fine here, even if I'm getting a warning about the flash version.
> > > > http://img24.imageshack.us/img24/2741/screenshotmassacolpitod.png
> > > > 
> > > > I've found that on 7, the better combination for me is
> > > > linux-flashplugin9, linux_base-fc4 and compat.linux.osrelease=2.4.2.
> > > 
> > > Same here: the video plays fine on 7.2-S with linux_base-fc4 and
> > > linux-flashplugin9
> > > 
> > > > On CURRENT, using linux_base-f10, I get much more stuck process, while
> > > > on 7 it barely happens.
> > > 
> > > On 8-BETA2 with linux_base-f10 and linux-f10-flashplugin10 that video
> > > makes npviewer "coredumping".
> > > 
> > This video played on my 8-BETA2 (r195818, SMP, i386) with linux_base-f10
> > and linux-f10-flashplugin10 without dumping core. Was your BETA2 before
> > or after library version bump and, if latter, did you rebuild all your
> > ports?
> > 
> 
> I've cvsupped and rebuilt my system on Jul. 23 and rebuilt all my ports.
> linux-f10-flashplugin10 is dumping core or not working for me too.
> BTW, why nspluginwrapper doesn't find the plugin?
>

I assume it's cause nothing is installed under 
/usr/local/lib/browser_plugins/ so you need to do a 

ln -s /usr/local/lib/npapi/linux-f10-flashplugin/libflashplayer.so \
/usr/local/lib/browser_plugins/

just before the nspluginwrapper -v -a -i as I mentioned it in the
Handbook.

Regarding my BETA2, I mostly use the 'current' packages and some may
come from before the bump, but firefox was built on friday.  I should
try to rebuild everything... however this box is really slow...

-- 
Marc
From rick at havokmon.com  Sun Jul 26 19:25:28 2009
From: rick at havokmon.com (Rick Romero)
Date: Sun Jul 26 19:25:34 2009
Subject: 7.2-STABLE ZFS: mv: set flags (was: 00000000): Invalid
	argument  - O_EXCL
In-Reply-To: <Kn6GqG.1I72@citylink.dinoex.sub.org>
References: <Kn6GqG.1I72@citylink.dinoex.sub.org>
Message-ID: <20090722082449.15851e1vdl76udr5@www.vfemail.net>


I believe this issue was supposed to have been resolved with a path a  
couple weeks ago - (O_EXCL) I had thought it was solved for myself as  
well (except for my vi on 4.8 oddity), but it is not.  :(

Quoting "Peter Much" <pmc@citylink.dinoex.sub.org>:

>
> Hi ZFS gurus!
>
> After upgrading my system from 7.2-PRERELEASE to 7.2-STABLE (as
> of last week), and accordingly upgrading my Pools from Version
> 6 to Version 13, I get this error when moving arbitrary files
> between different ZFS filesystems.
>
> While this seems not to do much harm (mv returns with 0), it is
> annoying.
> Does anybody know an explanation or fix, or is there some work in
> progress?
>
> rgds,
> PMc
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>
>



From andrew-freebsd at areilly.bpc-users.org  Sun Jul 26 22:24:05 2009
From: andrew-freebsd at areilly.bpc-users.org (Andrew Reilly)
Date: Sun Jul 26 22:24:13 2009
Subject: Weird portmaster behaviour -- everything fails to install
Message-ID: <20090726222403.GA19875@duncan.reilly.home>

Hi all,

I've spent the weekend doing a ports catch-up: there seems to
have been a lot of activity recently!  It's taking a long time
at least partly because portmaster doesn't seem to be "doing the
right thing" all of a sudden: it will happily trace the
dependencies and build the first superceded port, but fails to
re-install it.   On every occsaion this weekend, it gets to
===> Installing for foo-0.123_2
===> Generating temporary packing list
===> Checking if graphics/foo already installed
===>  foo-0.123_2 is already installed
     You may wish to "make deinstall" and blah, blah, blah...

Of course it's installed, that's why I'm running portmaster!

So I go into the directory, run make deinstall reinstall clean,
and that goes without a hitch.  Restart portmaster -uBd -a and
half an hour later it will fail in the same way, and I'll have
to do the same dance.

It's most likely something dumb that I've got misconfigured: can
anyone suggest to me where I should look?

(I don't normally run with the -B switch.  I put that in
recently to stop it from trying to build backup packages,
because it had previously been failing dismally at that stage,
because most of the installed files didn't match their md5
hashes for some reason.  I'm not too concerned with that:
packing lists often get mixed up, in my experience.)

Cheers,

-- 
Andrew

From kamenka at gmail.com  Mon Jul 27 10:27:23 2009
From: kamenka at gmail.com (Paul P.)
Date: Mon Jul 27 10:27:30 2009
Subject: Turn off rebooting in single-user mode after fail.
Message-ID: <659cf8870907270259m2e23769dxf416a3c86f9e8c50@mail.gmail.com>

Hello.
How to turn off automatic reboot in single user mode after power fails or
sudden reset? Do i need to make passin value in fstab equal to zero just to
turn off automatic FSCK fs check?

The system is remote and it is VERY annoy to up it by hands after any fail.
From cristiano.deana at gmail.com  Mon Jul 27 10:55:36 2009
From: cristiano.deana at gmail.com (Cristiano Deana)
Date: Mon Jul 27 10:55:43 2009
Subject: Turn off rebooting in single-user mode after fail.
In-Reply-To: <659cf8870907270259m2e23769dxf416a3c86f9e8c50@mail.gmail.com>
References: <659cf8870907270259m2e23769dxf416a3c86f9e8c50@mail.gmail.com>
Message-ID: <d8a4930a0907270355o2ef07c88hb93c05c48d1af0b6@mail.gmail.com>

On Mon, Jul 27, 2009 at 11:59 AM, Paul P.<kamenka@gmail.com> wrote:
> Hello.
> How to turn off automatic reboot in single user mode after power fails or
> sudden reset? Do i need to make passin value in fstab equal to zero just to
> turn off automatic FSCK fs check?

if i understood correctly:

rc.conf:
fsck_y_enable="YES"      # Set to YES to do fsck -y if the initial preen fails.

-- 
Cris, member of G.U.F.I
Italian FreeBSD User Group
http://www.gufi.org/
From krassi at bulinfo.net  Mon Jul 27 10:58:16 2009
From: krassi at bulinfo.net (Krassimir Slavchev)
Date: Mon Jul 27 10:58:24 2009
Subject: Turn off rebooting in single-user mode after fail.
In-Reply-To: <659cf8870907270259m2e23769dxf416a3c86f9e8c50@mail.gmail.com>
References: <659cf8870907270259m2e23769dxf416a3c86f9e8c50@mail.gmail.com>
Message-ID: <4A6D83FC.8090208@bulinfo.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Just put fsck_y_enable="YES" in /etc/rc.conf

Disabling file system check is dangerous!

Paul P. wrote:
> Hello.
> How to turn off automatic reboot in single user mode after power fails or
> sudden reset? Do i need to make passin value in fstab equal to zero just to
> turn off automatic FSCK fs check?
> 
> The system is remote and it is VERY annoy to up it by hands after any fail.
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (FreeBSD)

iD8DBQFKbYP8xJBWvpalMpkRAguVAKCjlRL1EW11WUKhSxnx2MKKwQxOvgCcDcz/
MZ4GRZJdMN0sUKrr/zHlgVM=
=97QP
-----END PGP SIGNATURE-----
From avg at freebsd.org  Mon Jul 27 12:16:20 2009
From: avg at freebsd.org (Andriy Gapon)
Date: Mon Jul 27 12:16:26 2009
Subject: smartctl: Unrecognized command 13
In-Reply-To: <4A6AC6CD.9090005@icyb.net.ua>
References: <4A6AC6CD.9090005@icyb.net.ua>
Message-ID: <4A6D9A8F.7060507@freebsd.org>

on 25/07/2009 11:48 Andriy Gapon said the following:
> This is stable/7 i386:
> 
> $ smartctl -t select,568157535-568159000 /dev/ad10
> ...
> Unrecognized command 13 in ata_command_interface()
> Please contact smartmontools-support@lists.sourceforge.net
> Error Write Selective Self-Test Log failed: Function not implemented
> 
> In smartmontools sources this is command WRITE_LOG.
> Is this something that can be patched in smartmontools or does it require
> additional support from ata driver?

I think the patch like the following could do the trick:
--- os_freebsd.cpp.orig	2008-03-05 00:09:47.000000000 +0200
+++ os_freebsd.cpp	2009-07-27 14:02:38.948144118 +0300
@@ -341,6 +340,15 @@
     request.count=512;
     copydata=1;
     break;
+  case WRITE_LOG:
+    memcpy(buff, data, 512);
+    request.u.ata.feature=ATA_SMART_WRITE_LOG_SECTOR;
+    request.u.ata.lba=select|(0xc24f<<8);
+    request.u.ata.count=1;
+    request.flags=ATA_CMD_WRITE;
+    request.data=(char *)buff;
+    request.count=512;
+    break;
   case IDENTIFY:
     request.u.ata.command=ATA_IDENTIFY_DEVICE;
     request.flags=ATA_CMD_READ;

-- 
Andriy Gapon
From attilio at freebsd.org  Mon Jul 27 12:32:00 2009
From: attilio at freebsd.org (Attilio Rao)
Date: Mon Jul 27 12:32:07 2009
Subject: kern/134584: [panic] spin lock held too long
In-Reply-To: <KNDMU8$8EFE8DA350FF14C54F1F3D61C7265B47@libero.it>
References: <KNDMU8$8EFE8DA350FF14C54F1F3D61C7265B47@libero.it>
Message-ID: <3bbf2fe10907270531u121bacb9y17d5bb624b3bc23b@mail.gmail.com>

2009/7/26 barbara <barbara.xxx1975@libero.it>:
> It happened again, on shutdown.
> As the previous time, it happened after a high (for a desktop) uptime and, if it could matter, after running net-p2p/transmission-gtk2 for several hours.
> I don't know if it's related, but often quitting transmission, doesn't terminate the process. Sometimes it end after several minutes the gui exited, sometimes it's still running after hours.
> I've noticed it as the destination folder is on a manually mounted device and I can't umount it as fstat reports the device used by a transmission process.
> So I often have to kill it.
> This happened both the time I had this kind of panic.

What hw is that? How many CPUs does it have?

Attilio


-- 
Peace can only be achieved by understanding - A. Einstein
From bms at incunabulum.net  Mon Jul 27 14:53:40 2009
From: bms at incunabulum.net (Bruce Simpson)
Date: Mon Jul 27 14:53:49 2009
Subject: ataraid's revenge! (Was: Re: A nasty ataraid experience.)
In-Reply-To: <1248424208.50198.2.camel@buffy.york.ac.uk>
References: <200901232244.n0NMiRmM098646@lurza.secnetix.de>	
	<46acbb3e-71bc-4cff-93d7-59b48a1a9302@exchange01.ecp.noc>	
	<4A68B2A0.8050509@incunabulum.net>
	<1248424208.50198.2.camel@buffy.york.ac.uk>
Message-ID: <4A6DBF6F.7050806@incunabulum.net>

Gavin Atkinson wrote:
> On Thu, 2009-07-23 at 19:57 +0100, Bruce Simpson wrote:
>   
>> 6 months on, ataraid(4) did it again.
>>     
>
> Which ataraid(4) controller is this?  Seeing a verbose dmesg would help.
> There are several patches in the PR database for ataraid problems, it
> would be worth having a look.
>   

Not much to report; it is a JMicron PCI-e card. I switched to the 
JMicron because it actually worked. The on-board controller is VIA and I 
don't use it; I've had problems managing the VIA based software RAID.

Occasionally the mirror degrades, usually on boot, if something panics 
the machine. This leads to interesting inconsistencies and panics. All I 
was doing at the time was srm'ing a bunch of sensitive files, and 
running some CPU (not disk) intensive regression tests for Boost. I 
found it's difficult to recover from errors. See my post from 6 months 
ago about how 'atacontrol rebuild' often just plain fails.

As per original post, the process(es) just wedged in getblk, and I had 
to take the system down to get some sense out of it as disk access 
ground to a halt.

From bms at incunabulum.net  Mon Jul 27 15:14:23 2009
From: bms at incunabulum.net (Bruce Simpson)
Date: Mon Jul 27 15:14:51 2009
Subject: status of flash9/flash10 support in RELENG_7 ?
In-Reply-To: <20090725013500.GC62402@onelab2.iet.unipi.it>
References: <20090725013500.GC62402@onelab2.iet.unipi.it>
Message-ID: <4A6DBFCC.9040201@incunabulum.net>

Luigi Rizzo wrote:
> Is there a recipe for a working flas9 or flash10 operation ?
>   

Allegedly PC-BSD ship a working Flash install, I have not tried it.

I have had similar problems and tried similar recipes. The Flash 
player(s) thus embedded are not very stable, and can crash or hang with 
multiple opens, or browser tab embedding the player(s) being closed.
From oberman at es.net  Mon Jul 27 16:39:22 2009
From: oberman at es.net (Kevin Oberman)
Date: Mon Jul 27 16:39:29 2009
Subject: status of flash9/flash10 support in RELENG_7 ? 
In-Reply-To: Your message of "Mon, 27 Jul 2009 15:55:08 BST."
	<4A6DBFCC.9040201@incunabulum.net> 
Message-ID: <20090727163919.A7B721CC0B@ptavv.es.net>

> Date: Mon, 27 Jul 2009 15:55:08 +0100
> From: Bruce Simpson <bms@incunabulum.net>
> Sender: owner-freebsd-stable@freebsd.org
> 
> Luigi Rizzo wrote:
> > Is there a recipe for a working flas9 or flash10 operation ?
> >   
> 
> Allegedly PC-BSD ship a working Flash install, I have not tried it.
> 
> I have had similar problems and tried similar recipes. The Flash 
> player(s) thus embedded are not very stable, and can crash or hang with 
> multiple opens, or browser tab embedding the player(s) being closed.

In all honesty, linux-flash has not been really stable, even on Linux,
since flash7. That said, I have had good results with flash9 and
nspluginwrapper. I also use linux_base-f8 and carefully updated all of
my linux emulation mode ports to the f8 version (when available). I
think that covers all of them EXCEPT linux-nvu and the closed source
third-party apps like linux-realplayer and linux-flashplugin9. Also, be
sure to add the define lines to /etc/make.conf as described in the
installation of linux_base-f8.

# portversion | grep linux-
then, for each item:
portupgrade -o /usr/ports/DIR/linux-f8-PORT/ linux-PORT

Where DIR is the ports directory and PORT is the pat of the port name
following 'linux-'. Note that you really need to do these in dependency
tree order or you will get install errors. Use 'portupgrade -fn linux-\*'
to get the order.

Log into the system under your normal account (not root) and run
nspluginwrapper to install the plugins that need to be wrapped.
nspluginwrapper -i /usr/local/lib/npapi/linux-flashplugin/libflashplayer.so
nspluginwrapper -i /usr/local/lib/linux-mozilla/plugins/nphelix.so

Restart firefox3.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@es.net			Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4  EADA 927D EBB3 987B 3751
From marck at FreeBSD.org  Mon Jul 27 19:10:59 2009
From: marck at FreeBSD.org (Dmitry Morozovsky)
Date: Mon Jul 27 19:11:06 2009
Subject: smartctl: Unrecognized command 13
In-Reply-To: <4A6D9A8F.7060507@freebsd.org>
References: <4A6AC6CD.9090005@icyb.net.ua> <4A6D9A8F.7060507@freebsd.org>
Message-ID: <alpine.BSF.2.00.0907272250050.31659@woozle.rinet.ru>

On Mon, 27 Jul 2009, Andriy Gapon wrote:

AG> > $ smartctl -t select,568157535-568159000 /dev/ad10
AG> > ...
AG> > Unrecognized command 13 in ata_command_interface()
AG> > Please contact smartmontools-support@lists.sourceforge.net
AG> > Error Write Selective Self-Test Log failed: Function not implemented
AG> > 
AG> > In smartmontools sources this is command WRITE_LOG.
AG> > Is this something that can be patched in smartmontools or does it require
AG> > additional support from ata driver?
AG> 
AG> I think the patch like the following could do the trick:
AG> --- os_freebsd.cpp.orig	2008-03-05 00:09:47.000000000 +0200
AG> +++ os_freebsd.cpp	2009-07-27 14:02:38.948144118 +0300
AG> @@ -341,6 +340,15 @@
AG>      request.count=512;
AG>      copydata=1;
AG>      break;
AG> +  case WRITE_LOG:
AG> +    memcpy(buff, data, 512);
AG> +    request.u.ata.feature=ATA_SMART_WRITE_LOG_SECTOR;
AG> +    request.u.ata.lba=select|(0xc24f<<8);
AG> +    request.u.ata.count=1;
AG> +    request.flags=ATA_CMD_WRITE;
AG> +    request.data=(char *)buff;
AG> +    request.count=512;
AG> +    break;
AG>    case IDENTIFY:
AG>      request.u.ata.command=ATA_IDENTIFY_DEVICE;
AG>      request.flags=ATA_CMD_READ;

Thank you, PR 137177 created.

-- 
Sincerely,
D.Marck                                        [DM5020, MCK-RIPE, DM3-RIPN]
---------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@FreeBSD.org ***
---------------------------------------------------------------------------
From barbara.xxx1975 at libero.it  Mon Jul 27 20:16:18 2009
From: barbara.xxx1975 at libero.it (barbara)
Date: Mon Jul 27 20:16:26 2009
Subject: status of flash9/flash10 support in RELENG_7 ?
Message-ID: <KNGIZ4$5A238C103AF54E76EC9FE89751F660A0@libero.it>

> On Sun, Jul 26, 2009 at 06:15:22PM +0200, barbara wrote:
> > > On Sun, 2009-07-26 at 10:32 +0200, Marc Fonvieille wrote:
> > > > On Sun, Jul 26, 2009 at 08:20:09AM +0200, barbara wrote:
> > > > > > 
> > > > > > An example of the URLs that is giving me problems is the following
> > > > > > 
> > > > > > http://tv.repubblica.it/copertina/massa-colpito-da-un-detrito/35446?video
> > > > > > 
> > > > > > (basically all videos from that site cause the same problem). I would be
> > > > > > grateful if you cold check it.
> > > > > > 
> > > > > 
> > > > > 
> > > > > The video looks fine here, even if I'm getting a warning about the flash version.
> > > > > http://img24.imageshack.us/img24/2741/screenshotmassacolpitod.png
> > > > > 
> > > > > I've found that on 7, the better combination for me is
> > > > > linux-flashplugin9, linux_base-fc4 and compat.linux.osrelease=2.4.2.
> > > > 
> > > > Same here: the video plays fine on 7.2-S with linux_base-fc4 and
> > > > linux-flashplugin9
> > > > 
> > > > > On CURRENT, using linux_base-f10, I get much more stuck process, while
> > > > > on 7 it barely happens.
> > > > 
> > > > On 8-BETA2 with linux_base-f10 and linux-f10-flashplugin10 that video
> > > > makes npviewer "coredumping".
> > > > 
> > > This video played on my 8-BETA2 (r195818, SMP, i386) with linux_base-f10
> > > and linux-f10-flashplugin10 without dumping core. Was your BETA2 before
> > > or after library version bump and, if latter, did you rebuild all your
> > > ports?
> > > 
> > 
> > I've cvsupped and rebuilt my system on Jul. 23 and rebuilt all my ports.
> > linux-f10-flashplugin10 is dumping core or not working for me too.
> > BTW, why nspluginwrapper doesn't find the plugin?
> >
> 
> I assume it's cause nothing is installed under 
> /usr/local/lib/browser_plugins/ so you need to do a 
> 
> ln -s /usr/local/lib/npapi/linux-f10-flashplugin/libflashplayer.so \
> /usr/local/lib/browser_plugins/
> 
> just before the nspluginwrapper -v -a -i as I mentioned it in the
> Handbook.
> 

That did the trick, thank you!
It's still lagging when I close the window, anyway it's working now.


Barbara



From barbara.xxx1975 at libero.it  Mon Jul 27 21:56:12 2009
From: barbara.xxx1975 at libero.it (barbara)
Date: Mon Jul 27 21:56:20 2009
Subject: kern/134584: [panic] spin lock held too long
Message-ID: <KNGNLM$A471FC7A32AD755D696D68231532AE93@libero.it>

> 2009/7/26 barbara <barbara.xxx1975@libero.it>:
> > It happened again, on shutdown.
> > As the previous time, it happened after a high (for a desktop) uptime and, if it could matter, after running net-p2p/transmission-gtk2 for several hours.
> > I don't know if it's related, but often quitting transmission, doesn't terminate the process. Sometimes it end after several minutes the gui exited, sometimes it's still running after hours.
> > I've noticed it as the destination folder is on a manually mounted device and I can't umount it as fstat reports the device used by a transmission process.
> > So I often have to kill it.
> > This happened both the time I had this kind of panic.
> 
> What hw is that? How many CPUs does it have?
> 


It's desktop pc, dual Athlon CPU, VIA chipset and...
You can find my dmesg.boot here:
http://pastebin.com/f507125f1
Aks if you need more info!

In the meanwhile I've rebuilt my kernel adding WITNESS, KDB, DDB options. Is this what you need?
I'm not able to work with the debugger. I suppose I have to type the commands you asked (ps, show alllocks) when it's panicking and the debbugger starts and write down the output with pen and paper, am I corrent? Or is there a way to redirect or dump the output somewhere?
Sorry, I'll try reading the chapter in the dev. handbook and I will try to do my best, but please, tell me if you have some suggestions.

I'll try to reproduce the problem, even it's not happening regularly.
If you need more info or to test code, etc. I'll be glad to help you.
BTW, can the output of crashinfo be of any help? Here you can find ps -axl from crashinfo:
http://pastebin.com/f3d54f01b

Thanks
Barbara


From andrew-freebsd at areilly.bpc-users.org  Tue Jul 28 00:12:41 2009
From: andrew-freebsd at areilly.bpc-users.org (Andrew Reilly)
Date: Tue Jul 28 00:12:49 2009
Subject: Weird portmaster behaviour -- everything fails to install
In-Reply-To: <20090726222403.GA19875@duncan.reilly.home>
References: <20090726222403.GA19875@duncan.reilly.home>
Message-ID: <20090728001238.GA97218@duncan.reilly.home>

Problem solved!

In case anyone is interested, or has encountered a similar
problem, I believe that my problem was that somehow my
/var/db/pkg directory had a whole pile of near-duplicate entries
corresponding to port revisions.  Portmaster was checking the
installed version against the MD5 hashes in the "old" version
+CONTENTS file, and they weren't matching.  I assume that I
acquired all of these out-of-date pkg entries through a backup
restore mishap: I've been having gmirror issues lately (not
gmirror's fault, I think -- just a series of dodgy hard drives.)

All is good again.  No duplicate db/pkg entries at last, and
portmaster runs to completion as intended.

Cheers,

-- 
Andrew

On Mon, Jul 27, 2009 at 08:24:03AM +1000, Andrew Reilly wrote:
> I've spent the weekend doing a ports catch-up: there seems to
> have been a lot of activity recently!  It's taking a long time
> at least partly because portmaster doesn't seem to be "doing the
> right thing" all of a sudden: it will happily trace the
> dependencies and build the first superceded port, but fails to
> re-install it.   On every occsaion this weekend, it gets to
> ===> Installing for foo-0.123_2
> ===> Generating temporary packing list
> ===> Checking if graphics/foo already installed
> ===>  foo-0.123_2 is already installed
>      You may wish to "make deinstall" and blah, blah, blah...
> 
> Of course it's installed, that's why I'm running portmaster!
> 
> So I go into the directory, run make deinstall reinstall clean,
> and that goes without a hitch.  Restart portmaster -uBd -a and
> half an hour later it will fail in the same way, and I'll have
> to do the same dance.
> 
> It's most likely something dumb that I've got misconfigured: can
> anyone suggest to me where I should look?

From dougb at FreeBSD.org  Tue Jul 28 01:13:16 2009
From: dougb at FreeBSD.org (Doug Barton)
Date: Tue Jul 28 01:13:23 2009
Subject: Weird portmaster behaviour -- everything fails to install
In-Reply-To: <20090728001238.GA97218@duncan.reilly.home>
References: <20090726222403.GA19875@duncan.reilly.home>
	<20090728001238.GA97218@duncan.reilly.home>
Message-ID: <alpine.BSF.2.00.0907271812020.43191@qbhto.arg>

On Tue, 28 Jul 2009, Andrew Reilly wrote:

> Problem solved!

Well I'm glad to hear that in any case. :)

> In case anyone is interested, or has encountered a similar
> problem, I believe that my problem was that somehow my
> /var/db/pkg directory had a whole pile of near-duplicate entries
> corresponding to port revisions.  Portmaster was checking the
> installed version against the MD5 hashes in the "old" version
> +CONTENTS file, and they weren't matching.

FYI, portmaster doesn't do anything with the md5 hashes in +CONTENTS, but 
duplicate entries will definitely cause "issues."


Doug

-- 

     This .signature sanitized for your protection

From dougb at FreeBSD.org  Tue Jul 28 02:39:27 2009
From: dougb at FreeBSD.org (Doug Barton)
Date: Tue Jul 28 02:39:34 2009
Subject: portmaster -s text (Was: Re: HEADS-UP: Shared Library Versions
 bumped)
In-Reply-To: <20090723011246.GA29465@osiris.mauzo.dyndns.org>
References: <1248027417.14210.110.camel@neo.cse.buffalo.edu>
	<58F0204B-ECE6-479A-AAC2-7868E71ABB43@exscape.org>
	<367b2c980907200729s57eafbbfw83c8ae5a94f41ffc@mail.gmail.com>
	<4A6628F0.6080802@mail.zedat.fu-berlin.de>
	<20090721215201.GA61999@troutmask.apl.washington.edu>
	<1248277420.8644.70.camel@localhost>
	<20090722193033.GA83848@zim.MIT.EDU>
	<20090723011246.GA29465@osiris.mauzo.dyndns.org>
Message-ID: <alpine.BSF.2.00.0907271933580.43191@qbhto.arg>

On Thu, 23 Jul 2009, Ben Morrow wrote:

> The problem with that is if you install pkg A deliberately, but it then
> later becomes a dependancy of pkg B. If you remove pkg B (because it's
> no longer needed) there is then no evidence that pkg A was installed on
> purpose, rather than incidentally. portmaster -s will offer to remove
> it, and if you refuse it will offer to remove the empty +REQUIRED_BY,
> effectively promoting it to a 'manually installed' pkg again, though
> it's perhaps not entirely clear from the question that that is what the
> effect will be.

Thanks for pointing this out. Can you suggest an alternative message? 
Other than the mundane reason the current message says what it does 
because I sometimes prefer to leave the empty file there so that when I go 
back through at a later date I can re-evaluate the choice.

> This would be easy to solve in general by maintaining a 'world' package,
> or some such, that had dependencies on everything installed explicitly;
> but that would require modifying all the pkg and port installation tools
> (probably including bsd.port.mk itself) to support that convention.

This sort of mechanism has been suggested before, but the problem you 
described (ports installed "on purpose" becoming a dependency of something 
else) is not an easy one to solve.

Doug

-- 

     This .signature sanitized for your protection

From v.haisman at sh.cvut.cz  Tue Jul 28 07:23:13 2009
From: v.haisman at sh.cvut.cz (=?ISO-8859-1?Q?V=E1clav_Haisman?=)
Date: Tue Jul 28 07:23:51 2009
Subject: Weird portmaster behaviour -- everything fails to install
In-Reply-To: <20090728001238.GA97218@duncan.reilly.home>
References: <20090726222403.GA19875@duncan.reilly.home>
	<20090728001238.GA97218@duncan.reilly.home>
Message-ID: <4A6EA757.8060600@sh.cvut.cz>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Andrew Reilly wrote:
> Problem solved!
> 
> In case anyone is interested, or has encountered a similar
> problem, I believe that my problem was that somehow my
> /var/db/pkg directory had a whole pile of near-duplicate entries
> corresponding to port revisions.  Portmaster was checking the
> installed version against the MD5 hashes in the "old" version
> +CONTENTS file, and they weren't matching.  I assume that I
> acquired all of these out-of-date pkg entries through a backup
> restore mishap: I've been having gmirror issues lately (not
> gmirror's fault, I think -- just a series of dodgy hard drives.)
> 
> All is good again.  No duplicate db/pkg entries at last, and
> portmaster runs to completion as intended.
How have you managed to fix the duplicate entries? Can pkgdb -Ffu or
such fix that?

- --
VH
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkpup1cACgkQjksRtmO2spePJQCeNiTwzOsDRpPhYpHX0ARHy4+T
wekAnjeNFuaXfQwOqrD6eS3YXLJKO6ma
=zyfE
-----END PGP SIGNATURE-----
From petefrench at ticketswitch.com  Tue Jul 28 09:13:47 2009
From: petefrench at ticketswitch.com (Pete French)
Date: Tue Jul 28 09:13:53 2009
Subject: portmaster -s text (Was: Re: HEADS-UP: Shared Library Versions
	bumped)
In-Reply-To: <alpine.BSF.2.00.0907271933580.43191@qbhto.arg>
Message-ID: <E1MViki-0002Dg-CF@dilbert.ticketswitch.com>

> This sort of mechanism has been suggested before, but the problem you 
> described (ports installed "on purpose" becoming a dependency of something 
> else) is not an easy one to solve.

I don't earlly see why that is a "problem" tha needs solving. cerrtainl
all I want is to be able to list ports installed by hand, regardless of
whether the later became dependencies of other ports. Just a nice
simple way to be able to say "what did I install on this?" before
wiping all ports and upgrading would be nice.

-pete.
From andrew-freebsd at areilly.bpc-users.org  Tue Jul 28 09:43:33 2009
From: andrew-freebsd at areilly.bpc-users.org (Andrew Reilly)
Date: Tue Jul 28 09:43:40 2009
Subject: Weird portmaster behaviour -- everything fails to install
In-Reply-To: <4A6EA757.8060600@sh.cvut.cz>
References: <20090726222403.GA19875@duncan.reilly.home>
	<20090728001238.GA97218@duncan.reilly.home>
	<4A6EA757.8060600@sh.cvut.cz>
Message-ID: <20090728094322.GA3717@duncan.reilly.home>

On Tue, Jul 28, 2009 at 09:23:03AM +0200, V?clav Haisman wrote:
> Andrew Reilly wrote:
> > Problem solved!
> > 
> > In case anyone is interested, or has encountered a similar
> > problem, I believe that my problem was that somehow my
> > /var/db/pkg directory had a whole pile of near-duplicate entries
> > corresponding to port revisions.  Portmaster was checking the
> > installed version against the MD5 hashes in the "old" version
> > +CONTENTS file, and they weren't matching.  I assume that I
> > acquired all of these out-of-date pkg entries through a backup
> > restore mishap: I've been having gmirror issues lately (not
> > gmirror's fault, I think -- just a series of dodgy hard drives.)
> > 
> > All is good again.  No duplicate db/pkg entries at last, and
> > portmaster runs to completion as intended.
> How have you managed to fix the duplicate entries? Can pkgdb -Ffu or
> such fix that?

I think that pkgdb is a portupgrade mechanism, and portmaster
doesn't need it.  By "duplicate entries" I mean multiple
directories in the /var/db/pkg directory that differ only in
version number or port version number.

When I realized that this is what was going on, there were only
four such duplicates left, and I just deleted the older
directory of the pair, as that was the one that didn't match the
installed files.  All of the previous duplicates seemed to have
been tidied up (or removed) by the "make deinstall reinstall"
exercise.

I did a final portmaster --check-depends, and that did a *lot*
of +REQUIRED_BY fixing, so I suspect that some of the previous
dependency notation must have been going into the incorrect
(older) versions (I guess that they sort first).

Cheers,

-- 
Andrew
From andrew-freebsd at areilly.bpc-users.org  Tue Jul 28 09:48:14 2009
From: andrew-freebsd at areilly.bpc-users.org (Andrew Reilly)
Date: Tue Jul 28 09:48:21 2009
Subject: Weird portmaster behaviour -- everything fails to install
In-Reply-To: <alpine.BSF.2.00.0907271812020.43191@qbhto.arg>
References: <20090726222403.GA19875@duncan.reilly.home>
	<20090728001238.GA97218@duncan.reilly.home>
	<alpine.BSF.2.00.0907271812020.43191@qbhto.arg>
Message-ID: <20090728094809.GB3717@duncan.reilly.home>

On Mon, Jul 27, 2009 at 06:13:07PM -0700, Doug Barton wrote:
> On Tue, 28 Jul 2009, Andrew Reilly wrote:
> >corresponding to port revisions.  Portmaster was checking the
> >installed version against the MD5 hashes in the "old" version
> >+CONTENTS file, and they weren't matching.
> 
> FYI, portmaster doesn't do anything with the md5 hashes in +CONTENTS, but 
> duplicate entries will definitely cause "issues."

Hmm.  Well, *something* was whinging about the MD5 hashes not
matching (and indeed they weren't), just before the install
failed.  Could it have been the process that builds a backup
package from the installed files?

Thanks for making portmaster, btw.  It's a great tool, and I
find that I prefer it to portupgrade, although I can't say that
I can put my finger on why, exactly...

Cheers,

-- 
Andrew
From ben at morrow.me.uk  Tue Jul 28 11:42:13 2009
From: ben at morrow.me.uk (Ben Morrow)
Date: Tue Jul 28 11:42:20 2009
Subject: portmaster -s text (Was: Re: HEADS-UP: Shared Library Versions
 bumped)
In-Reply-To: <alpine.BSF.2.00.0907271933580.43191@qbhto.arg>
References: <1248027417.14210.110.camel@neo.cse.buffalo.edu>
	<58F0204B-ECE6-479A-AAC2-7868E71ABB43@exscape.org>
	<367b2c980907200729s57eafbbfw83c8ae5a94f41ffc@mail.gmail.com>
	<4A6628F0.6080802@mail.zedat.fu-berlin.de>
	<20090721215201.GA61999@troutmask.apl.washington.edu>
	<1248277420.8644.70.camel@localhost>
	<20090722193033.GA83848@zim.MIT.EDU>
	<20090723011246.GA29465@osiris.mauzo.dyndns.org>
	<alpine.BSF.2.00.0907271933580.43191@qbhto.arg>
Message-ID: <4A6EDD32.6000800@morrow.me.uk>

Doug Barton wrote:
> On Thu, 23 Jul 2009, Ben Morrow wrote:
> 
>> The problem with that is if you install pkg A deliberately, but it then
>> later becomes a dependancy of pkg B. If you remove pkg B (because it's
>> no longer needed) there is then no evidence that pkg A was installed on
>> purpose, rather than incidentally. portmaster -s will offer to remove
>> it, and if you refuse it will offer to remove the empty +REQUIRED_BY,
>> effectively promoting it to a 'manually installed' pkg again, though
>> it's perhaps not entirely clear from the question that that is what the
>> effect will be.
> 
> Thanks for pointing this out. Can you suggest an alternative message? 
> Other than the mundane reason the current message says what it does 
> because I sometimes prefer to leave the empty file there so that when I 
> go back through at a later date I can re-evaluate the choice.

Yes, I can see it needs to be an option. Presumably 'don't ask me again' 
is too Microsoft :)? Maybe something like 'Mark this package as 
explicitly required?'? That's pretty much the user-visible effect.

I know the first time I saw that message, when I didn't really 
understand what it meant, my reaction was 'Delete something? No!' which 
wasn't the right answer.

>> This would be easy to solve in general by maintaining a 'world' package,
>> or some such, that had dependencies on everything installed explicitly;
>> but that would require modifying all the pkg and port installation tools
>> (probably including bsd.port.mk itself) to support that convention.
> 
> This sort of mechanism has been suggested before, but the problem you 
> described (ports installed "on purpose" becoming a dependency of 
> something else) is not an easy one to solve.

No. I have occasionally wondered if a sensible solution would be to drop 
portmaster/portupgrade altogether and just maintain a local 
sysutils/world port with a list of what I want installed, and 'make 
deinstall reinstall' whenever it changes (with something like 
pkg_cutleaves to clear out the trash). I suspect I would lose something 
I'm currently relying on (certainly, portmaster's -o and -r options 
wouldn't be trivial to emulate) but it does seem to me that both 
portmaster and portupgrade spend an awful lot of time doing things like 
tracking dependancies that bsd.port.mk already does for you.

Ben
From dan at yourbsdreport.com  Tue Jul 28 14:55:00 2009
From: dan at yourbsdreport.com (Dan)
Date: Tue Jul 28 14:55:09 2009
Subject: page fault
Message-ID: <4A6F0C2C.6030205@yourbsdreport.com>

Hi,

One of my servers running 7.2-RELEASE-p2 is crashing about every 2 or 3 
days with the following backtrace.  This particular one is from July 
24.I still have all the vmcores available if any further info is required.


Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x0
fault code              = supervisor read, page not present
instruction pointer     = 0x20:0xc077b9e8
stack pointer           = 0x28:0xe846ab34
frame pointer           = 0x28:0xe846ab58
code segment            = base 0x0, limit 0xfffff, type 0x1b
                         = DPL 0, pres 1, def32 1, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 42384 (perl5.10.0)
trap number             = 12
panic: page fault
cpuid = 1
Uptime: 1d23h35m17s
Physical memory: 2023 MB
Dumping 257 MB: 242 226 210 194 178 162 146 130 114 98 82 66 50 34 18 2

Reading symbols from /boot/kernel/accf_http.ko...Reading symbols from 
/boot/kernel/accf_http.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/accf_http.ko
Reading symbols from /boot/kernel/acpi.ko...Reading symbols from 
/boot/kernel/acpi.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/acpi.ko
#0  doadump () at pcpu.h:196
196             __asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb)

(kgdb) where
#0  doadump () at pcpu.h:196
#1  0xc07ddbe7 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418
#2  0xc07ddeb9 in panic (fmt=Variable "fmt" is not available.
) at /usr/src/sys/kern/kern_shutdown.c:574
#3  0xc0a818ac in trap_fatal (frame=0xe846aaf4, eva=0)
     at /usr/src/sys/i386/i386/trap.c:939
#4  0xc0a81b10 in trap_pfault (frame=0xe846aaf4, usermode=0, eva=0)
     at /usr/src/sys/i386/i386/trap.c:852
#5  0xc0a82492 in trap (frame=0xe846aaf4) at 
/usr/src/sys/i386/i386/trap.c:530
#6  0xc0a675ab in calltrap () at /usr/src/sys/i386/i386/exception.s:159
#7  0xc077b9e8 in pfs_ioctl (va=0xe846ab88)
     at /usr/src/sys/fs/pseudofs/pseudofs_vnops.c:247
#8  0xc0a965e2 in VOP_IOCTL_APV (vop=0xc0be6200, a=0xe846ab88)
     at vnode_if.c:795
#9  0xc086d68d in vn_ioctl (fp=0xc58d45f0, com=1076655123, data=0xc61b0440,
     active_cred=0xcb9d8500, td=0xc5e5e000) at vnode_if.h:437
#10 0xc0816a05 in kern_ioctl (td=0xc5e5e000, fd=3, com=1076655123,
     data=0xc61b0440 "") at file.h:269
#11 0xc0816b64 in ioctl (td=0xc5e5e000, uap=0xe846acfc)
     at /usr/src/sys/kern/sys_generic.c:571
#12 0xc0a81e65 in syscall (frame=0xe846ad38)
     at /usr/src/sys/i386/i386/trap.c:1090
#13 0xc0a67610 in Xint0x80_syscall () at 
/usr/src/sys/i386/i386/exception.s:255
#14 0x00000033 in ?? ()
Previous frame inner to this frame (corrupt stack?)
(kgdb)

(kgdb) l *0xc077b9e8
0xc077b9e8 is in pfs_ioctl (/usr/src/sys/fs/pseudofs/pseudofs_vnops.c:248).
243     static int
244     pfs_ioctl(struct vop_ioctl_args *va)
245     {
246             struct vnode *vn = va->a_vp;
247             struct pfs_vdata *pvd = vn->v_data;
248             struct pfs_node *pn = pvd->pvd_pn;
249             struct proc *proc;
250             int error;
251
252             PFS_TRACE(("%s: %lx", pn->pn_name, va->a_command));
From kostikbel at gmail.com  Tue Jul 28 14:59:45 2009
From: kostikbel at gmail.com (Kostik Belousov)
Date: Tue Jul 28 14:59:52 2009
Subject: page fault
In-Reply-To: <4A6F0C2C.6030205@yourbsdreport.com>
References: <4A6F0C2C.6030205@yourbsdreport.com>
Message-ID: <20090728145939.GD1884@deviant.kiev.zoral.com.ua>

On Tue, Jul 28, 2009 at 10:33:16AM -0400, Dan wrote:
> Hi,
> 
> One of my servers running 7.2-RELEASE-p2 is crashing about every 2 or 3 
> days with the following backtrace.  This particular one is from July 
> 24.I still have all the vmcores available if any further info is required.
> 
> 
> Fatal trap 12: page fault while in kernel mode
> cpuid = 0; apic id = 00
> fault virtual address   = 0x0
> fault code              = supervisor read, page not present
> instruction pointer     = 0x20:0xc077b9e8
> stack pointer           = 0x28:0xe846ab34
> frame pointer           = 0x28:0xe846ab58
> code segment            = base 0x0, limit 0xfffff, type 0x1b
>                         = DPL 0, pres 1, def32 1, gran 1
> processor eflags        = interrupt enabled, resume, IOPL = 0
> current process         = 42384 (perl5.10.0)
> trap number             = 12
> panic: page fault
> cpuid = 1
> Uptime: 1d23h35m17s
> Physical memory: 2023 MB
> Dumping 257 MB: 242 226 210 194 178 162 146 130 114 98 82 66 50 34 18 2
> 
> Reading symbols from /boot/kernel/accf_http.ko...Reading symbols from 
> /boot/kernel/accf_http.ko.symbols...done.
> done.
> Loaded symbols for /boot/kernel/accf_http.ko
> Reading symbols from /boot/kernel/acpi.ko...Reading symbols from 
> /boot/kernel/acpi.ko.symbols...done.
> done.
> Loaded symbols for /boot/kernel/acpi.ko
> #0  doadump () at pcpu.h:196
> 196             __asm __volatile("movl %%fs:0,%0" : "=r" (td));
> (kgdb)
> 
> (kgdb) where
> #0  doadump () at pcpu.h:196
> #1  0xc07ddbe7 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418
> #2  0xc07ddeb9 in panic (fmt=Variable "fmt" is not available.
> ) at /usr/src/sys/kern/kern_shutdown.c:574
> #3  0xc0a818ac in trap_fatal (frame=0xe846aaf4, eva=0)
>     at /usr/src/sys/i386/i386/trap.c:939
> #4  0xc0a81b10 in trap_pfault (frame=0xe846aaf4, usermode=0, eva=0)
>     at /usr/src/sys/i386/i386/trap.c:852
> #5  0xc0a82492 in trap (frame=0xe846aaf4) at 
> /usr/src/sys/i386/i386/trap.c:530
> #6  0xc0a675ab in calltrap () at /usr/src/sys/i386/i386/exception.s:159
> #7  0xc077b9e8 in pfs_ioctl (va=0xe846ab88)
>     at /usr/src/sys/fs/pseudofs/pseudofs_vnops.c:247
> #8  0xc0a965e2 in VOP_IOCTL_APV (vop=0xc0be6200, a=0xe846ab88)
>     at vnode_if.c:795
> #9  0xc086d68d in vn_ioctl (fp=0xc58d45f0, com=1076655123, data=0xc61b0440,
>     active_cred=0xcb9d8500, td=0xc5e5e000) at vnode_if.h:437
> #10 0xc0816a05 in kern_ioctl (td=0xc5e5e000, fd=3, com=1076655123,
>     data=0xc61b0440 "") at file.h:269
> #11 0xc0816b64 in ioctl (td=0xc5e5e000, uap=0xe846acfc)
>     at /usr/src/sys/kern/sys_generic.c:571
> #12 0xc0a81e65 in syscall (frame=0xe846ad38)
>     at /usr/src/sys/i386/i386/trap.c:1090
> #13 0xc0a67610 in Xint0x80_syscall () at 
> /usr/src/sys/i386/i386/exception.s:255
> #14 0x00000033 in ?? ()
> Previous frame inner to this frame (corrupt stack?)
> (kgdb)
> 
> (kgdb) l *0xc077b9e8
> 0xc077b9e8 is in pfs_ioctl (/usr/src/sys/fs/pseudofs/pseudofs_vnops.c:248).
> 243     static int
> 244     pfs_ioctl(struct vop_ioctl_args *va)
> 245     {
> 246             struct vnode *vn = va->a_vp;
> 247             struct pfs_vdata *pvd = vn->v_data;
> 248             struct pfs_node *pn = pvd->pvd_pn;
> 249             struct proc *proc;
> 250             int error;
> 251
> 252             PFS_TRACE(("%s: %lx", pn->pn_name, va->a_command));

I highly suspect that your problem was fixed by r194815.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090728/946cc4a6/attachment.pgp
From dan at yourbsdreport.com  Tue Jul 28 15:07:43 2009
From: dan at yourbsdreport.com (Dan)
Date: Tue Jul 28 15:08:00 2009
Subject: page fault
In-Reply-To: <20090728145939.GD1884@deviant.kiev.zoral.com.ua>
References: <4A6F0C2C.6030205@yourbsdreport.com>
	<20090728145939.GD1884@deviant.kiev.zoral.com.ua>
Message-ID: <4A6F1356.6050707@yourbsdreport.com>

Kostik Belousov wrote:
> On Tue, Jul 28, 2009 at 10:33:16AM -0400, Dan wrote:
>> Hi,
>>
>> One of my servers running 7.2-RELEASE-p2 is crashing about every 2 or 3 
>> days with the following backtrace.  This particular one is from July 
>> 24.I still have all the vmcores available if any further info is required.
>>
>>
>> Fatal trap 12: page fault while in kernel mode
>> cpuid = 0; apic id = 00
>> fault virtual address   = 0x0
>> fault code              = supervisor read, page not present
>> instruction pointer     = 0x20:0xc077b9e8
>> stack pointer           = 0x28:0xe846ab34
>> frame pointer           = 0x28:0xe846ab58
>> code segment            = base 0x0, limit 0xfffff, type 0x1b
>>                         = DPL 0, pres 1, def32 1, gran 1
>> processor eflags        = interrupt enabled, resume, IOPL = 0
>> current process         = 42384 (perl5.10.0)
>> trap number             = 12
>> panic: page fault
>> cpuid = 1
>> Uptime: 1d23h35m17s
>> Physical memory: 2023 MB
>> Dumping 257 MB: 242 226 210 194 178 162 146 130 114 98 82 66 50 34 18 2
>>
>> Reading symbols from /boot/kernel/accf_http.ko...Reading symbols from 
>> /boot/kernel/accf_http.ko.symbols...done.
>> done.
>> Loaded symbols for /boot/kernel/accf_http.ko
>> Reading symbols from /boot/kernel/acpi.ko...Reading symbols from 
>> /boot/kernel/acpi.ko.symbols...done.
>> done.
>> Loaded symbols for /boot/kernel/acpi.ko
>> #0  doadump () at pcpu.h:196
>> 196             __asm __volatile("movl %%fs:0,%0" : "=r" (td));
>> (kgdb)
>>
>> (kgdb) where
>> #0  doadump () at pcpu.h:196
>> #1  0xc07ddbe7 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418
>> #2  0xc07ddeb9 in panic (fmt=Variable "fmt" is not available.
>> ) at /usr/src/sys/kern/kern_shutdown.c:574
>> #3  0xc0a818ac in trap_fatal (frame=0xe846aaf4, eva=0)
>>     at /usr/src/sys/i386/i386/trap.c:939
>> #4  0xc0a81b10 in trap_pfault (frame=0xe846aaf4, usermode=0, eva=0)
>>     at /usr/src/sys/i386/i386/trap.c:852
>> #5  0xc0a82492 in trap (frame=0xe846aaf4) at 
>> /usr/src/sys/i386/i386/trap.c:530
>> #6  0xc0a675ab in calltrap () at /usr/src/sys/i386/i386/exception.s:159
>> #7  0xc077b9e8 in pfs_ioctl (va=0xe846ab88)
>>     at /usr/src/sys/fs/pseudofs/pseudofs_vnops.c:247
>> #8  0xc0a965e2 in VOP_IOCTL_APV (vop=0xc0be6200, a=0xe846ab88)
>>     at vnode_if.c:795
>> #9  0xc086d68d in vn_ioctl (fp=0xc58d45f0, com=1076655123, data=0xc61b0440,
>>     active_cred=0xcb9d8500, td=0xc5e5e000) at vnode_if.h:437
>> #10 0xc0816a05 in kern_ioctl (td=0xc5e5e000, fd=3, com=1076655123,
>>     data=0xc61b0440 "") at file.h:269
>> #11 0xc0816b64 in ioctl (td=0xc5e5e000, uap=0xe846acfc)
>>     at /usr/src/sys/kern/sys_generic.c:571
>> #12 0xc0a81e65 in syscall (frame=0xe846ad38)
>>     at /usr/src/sys/i386/i386/trap.c:1090
>> #13 0xc0a67610 in Xint0x80_syscall () at 
>> /usr/src/sys/i386/i386/exception.s:255
>> #14 0x00000033 in ?? ()
>> Previous frame inner to this frame (corrupt stack?)
>> (kgdb)
>>
>> (kgdb) l *0xc077b9e8
>> 0xc077b9e8 is in pfs_ioctl (/usr/src/sys/fs/pseudofs/pseudofs_vnops.c:248).
>> 243     static int
>> 244     pfs_ioctl(struct vop_ioctl_args *va)
>> 245     {
>> 246             struct vnode *vn = va->a_vp;
>> 247             struct pfs_vdata *pvd = vn->v_data;
>> 248             struct pfs_node *pn = pvd->pvd_pn;
>> 249             struct proc *proc;
>> 250             int error;
>> 251
>> 252             PFS_TRACE(("%s: %lx", pn->pn_name, va->a_command));
> 
> I highly suspect that your problem was fixed by r194815.

Will this fix work on a release, or would it be best to upgrade to the 
stable branch.
From kostikbel at gmail.com  Tue Jul 28 15:12:32 2009
From: kostikbel at gmail.com (Kostik Belousov)
Date: Tue Jul 28 15:12:39 2009
Subject: page fault
In-Reply-To: <4A6F1356.6050707@yourbsdreport.com>
References: <4A6F0C2C.6030205@yourbsdreport.com>
	<20090728145939.GD1884@deviant.kiev.zoral.com.ua>
	<4A6F1356.6050707@yourbsdreport.com>
Message-ID: <20090728151227.GG1884@deviant.kiev.zoral.com.ua>

On Tue, Jul 28, 2009 at 11:03:50AM -0400, Dan wrote:
> Kostik Belousov wrote:
> >I highly suspect that your problem was fixed by r194815.
> 
> Will this fix work on a release, or would it be best to upgrade to the 
> stable branch.

If it is applicable without conflicts, then most likely it will work
on release.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090728/c73e9be1/attachment.pgp
From dougb at FreeBSD.org  Tue Jul 28 17:25:46 2009
From: dougb at FreeBSD.org (Doug Barton)
Date: Tue Jul 28 17:25:53 2009
Subject: portmaster -s text (Was: Re: HEADS-UP: Shared Library Versions
 bumped)
In-Reply-To: <4A6EDD32.6000800@morrow.me.uk>
References: <1248027417.14210.110.camel@neo.cse.buffalo.edu>
	<58F0204B-ECE6-479A-AAC2-7868E71ABB43@exscape.org>
	<367b2c980907200729s57eafbbfw83c8ae5a94f41ffc@mail.gmail.com>
	<4A6628F0.6080802@mail.zedat.fu-berlin.de>
	<20090721215201.GA61999@troutmask.apl.washington.edu>
	<1248277420.8644.70.camel@localhost>
	<20090722193033.GA83848@zim.MIT.EDU>
	<20090723011246.GA29465@osiris.mauzo.dyndns.org>
	<alpine.BSF.2.00.0907271933580.43191@qbhto.arg>
	<4A6EDD32.6000800@morrow.me.uk>
Message-ID: <alpine.BSF.2.00.0907281020480.94256@qbhto.arg>

On Tue, 28 Jul 2009, Ben Morrow wrote:

> Yes, I can see it needs to be an option. Presumably 'don't ask me again' is 
> too Microsoft :)? Maybe something like 'Mark this package as explicitly 
> required?'? That's pretty much the user-visible effect.

Thanks for the suggestions.

> I know the first time I saw that message, when I didn't really understand 
> what it meant, my reaction was 'Delete something? No!' which wasn't the right 
> answer.

Yeah, looking back on this from the user perspective it wasn't the best 
choice of messages.

> No. I have occasionally wondered if a sensible solution would be to drop 
> portmaster/portupgrade altogether and just maintain a local sysutils/world 
> port with a list of what I want ins