FreeBSD Apache Mysql Php Squid: freebsd-stable Digest, Vol 264, Issue 8

Send freebsd-stable mailing list submissions to
freebsd-stable@freebsd.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
or, via email, send a message with subject or body 'help' to
freebsd-stable-request@freebsd.org

You can reach the person managing the list at
freebsd-stable-owner@freebsd.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-stable digest..."

Today's Topics:

1. Re: Regression 7.0R -> 7-stable? (Jeremy Chadwick)
2. Re: Regression 7.0R -> 7-stable? (Gerrit K?hn)
3. Re: Regression 7.0R -> 7-stable? (Edwin Groothuis)
4. Re: i386 vs amd64? (Eugene Kazarinov)
5. Re: PPP doesn't set the correct interface in 7-STABLE (Andy Dills)
6. Re: Swapping boot disks and getting mountroot> (Lisa Besko)
7. should looking at an interface with 'ifconfig' trigger a
change ? (Pete French)
8. Re: should looking at an interface with 'ifconfig' trigger a
change ? (Pete French)
9. Re: should looking at an interface with 'ifconfig' trigger a
change ? (Andrew Thompson)
10. Re: should looking at an interface with 'ifconfig' trigger a
change ? (Andrew Thompson)
11. Re: i386 vs amd64? (Chuck Swiger)
12. Re: Swapping boot disks and getting mountroot>===SOLVED
(Lisa Besko)
13. Re: cpufreq(4) panic on RELENG_7 (was: Re: Call for bfe(4)
testers.) (pluknet)
14. Re: ng_ipacct.c:905: error: too few arguments to function
'in_pcblookup_local' (Xin LI)
15. Re: Regression 7.0R -> 7-stable? (Xin LI)
16. Re: Query timeouts on FreeBSD 7 over network ( Sebastian Tymk?w )
17. sysinstall compilation issue (Unga)
18. Re: Upgrading from 6.x to 7.x (Vincent Hoffman)
19. Re: Upgrading from 6.x to 7.x (Vincent Hoffman)
20. Re: Upgrading from 6.x to 7.x (Warren Liddell)
21. Re: Upgrading from 6.x to 7.x (Warren Liddell)
22. Re: Upgrading from 6.x to 7.x (Vincent Hoffman)
23. Re: Upgrading from 6.x to 7.x (Warren Liddell)
24. Re: should looking at an interface with 'ifconfig' trigger a
change ? (Pyun YongHyeon)

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

Message: 1
Date: Thu, 7 Aug 2008 05:19:40 -0700
From: Jeremy Chadwick <koitsu@FreeBSD.org>
Subject: Re: Regression 7.0R -> 7-stable?
To: Edwin Groothuis <edwin@mavetju.org>, Gerrit K?hn
<gerrit@pmp.uni-hannover.de>, freebsd-stable@freebsd.org
Message-ID: <20080807121940.GA28212@eos.sc1.parodius.com>
Content-Type: text/plain; charset=us-ascii

On Thu, Aug 07, 2008 at 09:47:06PM +1000, Edwin Groothuis wrote:
> On Thu, Aug 07, 2008 at 01:29:47PM +0200, Gerrit K?hn wrote:
> > Hi folks,
> >
> > I have a rather new FujitsuSiemens Esprimo here with an AMD Phenom X3
> > processor (triple core is somehow strange :-) and a lot of NVidia stuff
> > onboard. I installed 7.0-R, which ran quite well except for the bge driver
> > and snd_hda which both complained.
> > After putting in an extra networking card I was able to install some more
> > software and all appeared to be nice. Then I cvsupped to the recent
> > 7-stable as of today. My hope was that maybe the bge or the sound card
> > would improve from this. However, the new kernel I compiled does not run
> > at all. It boots up to CPU#1 and CPU#2 lauchned messages and then sits
> > there and does nothing anymore. I have verified this behaviour with amd64
> > snapshot images from July and August to make sure I did not compile a bad
> > kernel. Both show the same behaviour.
> > Are there any ideas what has changed from 7.0-R to recent 7.0-stable that
> > could cause this? What can I do to debug/fix this?
>
> Make sure you have this in your /etc/sysctl.conf:
>
> [~] edwin@k7>grep hyper /etc/sysctl.conf
> machdep.hyperthreading_allowed=1
>
> Then with top you can see the CPUs in use ----------v
>
> PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND
> 69200 edwin 9 44 0 236M 130M ucond 0 33:37 5.76% seamonkey-b
> 3317 edwin 1 71 0 38404K 33572K select 1 3:51 0.10% mutt
> 3015 edwin 1 45 0 403M 81672K select 0 101:52 0.00% Xorg

I think you misread what he was saying. :-) He's saying that his
system locks up hard after the kernel prints the "SMP: AP CPU #x
Launched!" messages.

I believe this is the 2nd or 3rd report we've had of this behaviour, re:
system locking up hard after those messages. I'll see if I can find the
past reports; I'm going off of memory, but they were in recent days.

Also (for you Edwin), be aware of the security issues when enabling HTT,
as well as the possible decrease in system performance (while increase
in power draw) it can cause:

http://en.wikipedia.org/wiki/Hyper-threading#Security
http://en.wikipedia.org/wiki/Hyper-threading#Future

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

Message: 2
Date: Thu, 7 Aug 2008 14:35:35 +0200
From: Gerrit K?hn <gerrit@pmp.uni-hannover.de>
Subject: Re: Regression 7.0R -> 7-stable?
To: Jeremy Chadwick <koitsu@freebsd.org>
Cc: Edwin Groothuis <edwin@mavetju.org>, freebsd-stable@freebsd.org
Message-ID: <20080807143535.86c25613.gerrit@pmp.uni-hannover.de>
Content-Type: text/plain; charset=US-ASCII

On Thu, 7 Aug 2008 05:19:40 -0700 Jeremy Chadwick <koitsu@FreeBSD.org>
wrote about Re: Regression 7.0R -> 7-stable?:

JC> I think you misread what he was saying. :-) He's saying that his
JC> system locks up hard after the kernel prints the "SMP: AP CPU #x
JC> Launched!" messages.

Exactly. ;-)

JC> I believe this is the 2nd or 3rd report we've had of this behaviour,
JC> re: system locking up hard after those messages. I'll see if I can
JC> find the past reports; I'm going off of memory, but they were in
JC> recent days.

Please let me know if I can provide any further information. However, I
will probably not be on the net from tomorrow (Friday) until Monday.

cu
Gerrit

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

Message: 3
Date: Thu, 7 Aug 2008 22:36:06 +1000
From: Edwin Groothuis <edwin@mavetju.org>
Subject: Re: Regression 7.0R -> 7-stable?
To: Jeremy Chadwick <koitsu@FreeBSD.org>
Cc: Gerrit K?hn <gerrit@pmp.uni-hannover.de>,
freebsd-stable@freebsd.org
Message-ID: <20080807123606.GT3285@k7.mavetju>
Content-Type: text/plain; charset=us-ascii

On Thu, Aug 07, 2008 at 05:19:40AM -0700, Jeremy Chadwick wrote:
> On Thu, Aug 07, 2008 at 09:47:06PM +1000, Edwin Groothuis wrote:
> > On Thu, Aug 07, 2008 at 01:29:47PM +0200, Gerrit K?hn wrote:
> > > Hi folks,
> > >
> > > I have a rather new FujitsuSiemens Esprimo here with an AMD Phenom X3
> > > processor (triple core is somehow strange :-) and a lot of NVidia stuff
> > > onboard. I installed 7.0-R, which ran quite well except for the bge driver
> > > and snd_hda which both complained.
> > > After putting in an extra networking card I was able to install some more
> > > software and all appeared to be nice. Then I cvsupped to the recent
> > > 7-stable as of today. My hope was that maybe the bge or the sound card
> > > would improve from this. However, the new kernel I compiled does not run
> > > at all. It boots up to CPU#1 and CPU#2 lauchned messages and then sits
> > > there and does nothing anymore. I have verified this behaviour with amd64
> > > snapshot images from July and August to make sure I did not compile a bad
> > > kernel. Both show the same behaviour.
> > > Are there any ideas what has changed from 7.0-R to recent 7.0-stable that
> > > could cause this? What can I do to debug/fix this?
> >
> > Make sure you have this in your /etc/sysctl.conf:
> >
> > [~] edwin@k7>grep hyper /etc/sysctl.conf
> > machdep.hyperthreading_allowed=1
> >
> > Then with top you can see the CPUs in use ----------v
> >
> > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND
> > 69200 edwin 9 44 0 236M 130M ucond 0 33:37 5.76% seamonkey-b
> > 3317 edwin 1 71 0 38404K 33572K select 1 3:51 0.10% mutt
> > 3015 edwin 1 45 0 403M 81672K select 0 101:52 0.00% Xorg
>
> I think you misread what he was saying. :-) He's saying that his
> system locks up hard after the kernel prints the "SMP: AP CPU #x
> Launched!" messages.

It's indeed a different interpretation of what I originally read.
Sorry for the noise!

Edwin

--
Edwin Groothuis | Personal website: http://www.mavetju.org
edwin@mavetju.org | Weblog: http://www.mavetju.org/weblog/

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

Message: 4
Date: Thu, 7 Aug 2008 16:48:10 +0400
From: "Eugene Kazarinov" <kamuzon@milshop.ru>
Subject: Re: i386 vs amd64?
To: "FreeBSD Stable" <freebsd-stable@freebsd.org>
Message-ID:
<519867a90808070548n5eee13adwb79b62bd2fecb67a@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

Hello everybody.
(sorry for my english)

>
> # For individuals wanting to upgrade their sources (even if only a
> # delta of a few days):
> #
> # 1. `cd /usr/src' (or to the directory containing your source
> tree).
> # 2. `make buildworld'
> # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is
> GENERIC).
> # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is
> GENERIC).
> # 5. `reboot' (in single user mode: boot -s from the loader
> prompt).
> # 6. `mergemaster -p'
> # 7. `make installworld'
> # 8. `make delete-old'
> # 9. `mergemaster'
> # 10. `reboot'
> # 11. `make delete-old-libs' (in case no 3rd party program uses them
> anymore)
>

Pls tell me what for I need 5 step?
I have about 15 remote servers (10 on 6.X-stable and others on 7.0-stable).
These servers are far far away from me and I really cant connect serial or
keyboard to it.
So I upgrade remotely without "# 5 reboot" very long time, starting from at
least 5.4 (maybe 4.x I dont remember), 5.4-stable -> 6.0-stable, 6.0-stable
-> 6.2-stable, 6.0/6.2-stable -> 6.3-stable and of couse 6.2/6.3-stable ->
7.0-stable.
Only once I got a problem with /libexec/ld-elf.so.X then I try upgrade from
6.2-RELEASE-pX to 7.0-stable. Of couse I got phisical access to this server
to repair it. I got this file from another server and then succesfully
rebuild all the world with my "reception". This was really hard situation.
(I use /rescue and have shamanian danced with tambourine around this server
;) lol ;) )
I dont remember why I had on that server this strange (for me) version
(6.2-RELEASE).

So have I a chance to upgrade remote servers without single mode?
Now my practice is (a few last years):
#cd /usr/src
#mergemaster -p && make -j8 buildworld && make -j8 buildkernel KERNCONF=KMD
&& make installkernel KERNCONF=KMD && make installworld && mergemaster -iU
&& reboot
*) -j8 on 2x- or 4x-kernels cpu and -j4 on 1x-kernel cpu
*) some time I did "make -j4 installkernel KERNCONF=KMD" and "make -j4
installworld" but it's worked not stable. Sometimes it returns an error.
Maybe hdd was not speedy - dont know why it was so and dont know how to say
it all in english. :\
*) on Phenom 9750 with 2GB DDR2 800MHz memory "-j8 buildworld" makes in
about 16 minutes and "-j8 buildkernel KERN..." in about 5 minutes. As a
result all upgrade takes about 30 minutes or less. On x2 CPUs I put this
long command in ssh-term and go away. When I come back "mergemaster -iU" is
waiting me.

And if I make major update (6.x to 7.x) I'll portupgrade all ports as in
manual "portupgrade -faP"
and then reboot
after that "make delete-old" and "make delete-old-libs" and reboot

All of this I do remotely. Is this way very wrong? I understand that it's
not a "canonical" way but how I can do it right and remotely?

Thanks in advance.

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

Message: 5
Date: Thu, 7 Aug 2008 10:05:38 -0400 (EDT)
From: Andy Dills <andy@xecu.net>
Subject: Re: PPP doesn't set the correct interface in 7-STABLE
To: Mike Tancsa <mike@sentex.net>
Cc: freebsd-stable@freebsd.org
Message-ID: <20080807095944.R46224@shell.xecu.net>
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 6 Aug 2008, Mike Tancsa wrote:

> At 10:16 AM 8/6/2008, Andy Dills wrote:
>
> > I'm trying to setup pptpd to enable VPN connections. This worked well in
> > all versions of FreeBSD prior to 7.
>
> I would turf pptpd and look at mpd51 from the ports. It is far, far better
> maintained and is quite solid as an LNS as well as PPTP termination server.

Yep, it looks like this is definitely the best solution, for a number of
reasons.

Thanks for the pointer.

Andy

---
Andy Dills
Xecunet, Inc.
www.xecu.net
301-682-9972
---

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

Message: 6
Date: Thu, 07 Aug 2008 10:25:29 -0400
From: Lisa Besko <besko@msu.edu>
Subject: Re: Swapping boot disks and getting mountroot>
To: Joseph Koshy <joseph.koshy@gmail.com>
Cc: freebsd-stable@freebsd.org
Message-ID: <489B05D9.7030407@msu.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Joseph Koshy wrote:
>> I notice that it finds the device ad4 but then it tries to mount root from
>> /dev/ad6s1a. I've edited the fstab to have it look for ad4s1a but it still
>> won't boot. Anyone have any pointers or ideas?
>
> Have you tried interrupting the boot sequence and setting new
> values for the `rootdev' and `root_disk_unit' loader variables?
> The loader(8) manual page has more information.

No I haven't tried that yet. Will that get me to a point where I can
trust it to boot on it's own to the correct disk all the time?

LB
--
Lisa Besko

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

Message: 7
Date: Thu, 07 Aug 2008 17:27:53 +0100
From: Pete French <petefrench@ticketswitch.com>
Subject: should looking at an interface with 'ifconfig' trigger a
change ?
To: stable@freebsd.org
Message-ID: <E1KR8LB-000KtI-02@dilbert.ticketswitch.com>

I have a very odd problem here - two interfaces bundled using lagg
in 'failover' mode, so one interface is active and the other not being
used. if the carrier drops on the active one I expect it to
failover, but it doesnt.

...until I type 'ifconfig bce0' to look at the status of the interface
which has gone down. At which point it fails over properly!

This is most odd - how can simply looking at the config of an
interface trigger the failover ? It wont fail over otherwise either - you
can leave it as long as you like and lagg wont realise that the active
has gone down.

The interfaces here are 'bce' by the way, if that make a difference....

-pete.

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

Message: 8
Date: Thu, 07 Aug 2008 18:11:58 +0100
From: Pete French <petefrench@ticketswitch.com>
Subject: Re: should looking at an interface with 'ifconfig' trigger a
change ?
To: thompsa@FreeBSD.org
Cc: stable@freebsd.org
Message-ID: <E1KR91q-000LRz-HQ@dilbert.ticketswitch.com>

> The bce driver is not properly generating link state events.

OK, that explains why it doesnt failover - but why does looking at it
with ifconfig make a difference ? surely that should be 'read only ?

-pete.

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

Message: 9
Date: Thu, 7 Aug 2008 09:57:12 -0700
From: Andrew Thompson <thompsa@FreeBSD.org>
Subject: Re: should looking at an interface with 'ifconfig' trigger a
change ?
To: Pete French <petefrench@ticketswitch.com>
Cc: stable@freebsd.org
Message-ID: <20080807165712.GA37969@citylink.fud.org.nz>
Content-Type: text/plain; charset=us-ascii

On Thu, Aug 07, 2008 at 05:27:53PM +0100, Pete French wrote:
> I have a very odd problem here - two interfaces bundled using lagg
> in 'failover' mode, so one interface is active and the other not being
> used. if the carrier drops on the active one I expect it to
> failover, but it doesnt.
>
> ...until I type 'ifconfig bce0' to look at the status of the interface
> which has gone down. At which point it fails over properly!
>
> This is most odd - how can simply looking at the config of an
> interface trigger the failover ? It wont fail over otherwise either - you
> can leave it as long as you like and lagg wont realise that the active
> has gone down.
>
> The interfaces here are 'bce' by the way, if that make a difference....

The bce driver is not properly generating link state events.

Andrew

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

Message: 10
Date: Thu, 7 Aug 2008 10:35:25 -0700
From: Andrew Thompson <thompsa@FreeBSD.org>
Subject: Re: should looking at an interface with 'ifconfig' trigger a
change ?
To: Pete French <petefrench@ticketswitch.com>
Cc: stable@freebsd.org
Message-ID: <20080807173525.GB37969@citylink.fud.org.nz>
Content-Type: text/plain; charset=us-ascii

On Thu, Aug 07, 2008 at 06:11:58PM +0100, Pete French wrote:
> > The bce driver is not properly generating link state events.
>
> OK, that explains why it doesnt failover - but why does looking at it
> with ifconfig make a difference ? surely that should be 'read only ?

ifconfig will cause the media status to be read from the hardware at
which time the link change is generated as it is different to the stored
value.

cheers,
Andrew

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

Message: 11
Date: Thu, 7 Aug 2008 11:31:49 -0700
From: Chuck Swiger <cswiger@mac.com>
Subject: Re: i386 vs amd64?
To: Milan Obuch <freebsd-stable@dino.sk>
Cc: Jeremy Chadwick <koitsu@freebsd.org>, Ask Bj?rn Hansen
<ask@develooper.com>, freebsd-stable@freebsd.org
Message-ID: <DA2BA81A-AC17-4818-916E-30E8AD134FCE@mac.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes

On Aug 7, 2008, at 2:34 AM, Milan Obuch wrote:
>> 5) Get familiar with mergemaster, specifically the side-by-side
>> interactive diff feature. It looks scary the first time around,
>> but once you learn that "r" applies the stuff you see on the right,
>> and "l" applies the stuff you see on the left, you should be fine.
>
> Funny observation: "r" is on LEFT keyboard side, "l" is on RIGHT
> keyboard
> side. I for one have problem at times precisely for this reason, but
> I know
> this is an important step and one need to act with great care.

Fortunately, the diffutils maintainer has accepted a patch to allow
"1" and "2" (similar to http://www.pkix.net/~chuck/sdiff2.diff);
hopefully your system is recent enough to include that change:

Regards,
--
-Chuck

Begin forwarded message:
> From: Chuck Swiger <cswiger@mac.com>
> Date: June 13, 2007 11:57:34 AM PDT
> To: LI Xin <delphij@delphij.net>
> Cc: FreeBSD Current <freebsd-current@freebsd.org>
> Subject: Re: RFC: diff(1) update
>
> On Jun 13, 2007, at 2:10 AM, LI Xin wrote:
>> I have done a first cut of bringing latest GNU diffutils (2.8.1) to
>> the
>> FreeBSD base system. This consists two parts of changes:
>> [ ... ]
>> Some notes:
>> - I have tried to keep as most our local features (DIFF_OPTIONS,
>> etc),
>> but we still need to have some test cases to figure out whether
>> there is
>> regression.
>> - Local changes are now maintained as patchsets.
>> - Still need to find a better way to handle local manpage changes...
>>
>> Comments?
>
> Thanks for looking into updating diffutils, Xin.
>
> Paul Eggert, the diffutils maintainer, has recently adopted a patch
> for sdiff which allows using "1" and "2" in addition to "l" and "r",
> which is exceptionally useful when people are running mergemaster.
> Also, v2.8.6 also includes a fix for invoking an editor in sdiff mode:
>
> Paul Eggert <eggert@cs.ucla.edu> wrote:
>> Chuck Swiger <chuck@pkix.net> writes:
>>> At least with diff-2.7 or thereabouts, invoking the
>>> external editor via "e l" or "e r" would always fail and return the
>>> warning from this line of diff code:
>>>
>>> fatal ("Subsidiary editor failed");
>>
>> You can double-check, but I think that bug was fixed here:
>>
>> 2004-04-12 Paul Eggert <eggert@twinsun.com>
>>
>> * NEWS, configure.ac (AC_INIT): Version 2.8.6.
>> ...
>> * src/sdiff.c (check_child_status): Renamed from ck_editor_status,
>> and
>> accept a new arg MAX_OK_STATUS. All callers changed.
>> Handle status 126/127 as per POSIX.
>>
>
> ------
>
>> Good point, thanks. I installed this:
>>
>> 2007-06-06 Paul Eggert <eggert@cs.ucla.edu>
>>
>> * NEWS: Mention new sdiff aliases 1 and 2 for l and r.
>> * doc/diff.texi (Merge Commands): Likewise.
>> * src/sdiff.c (give_help): Give help for them.
>> (edit): Support them.
>>
>> Index: NEWS
>> ===================================================================
>> RCS file: /cvsroot/diffutils/diffutils/NEWS,v
>> retrieving revision 1.25
>> diff -u -p -r1.25 NEWS
>> --- NEWS 5 Sep 2006 23:02:32 -0000 1.25
>> +++ NEWS 6 Jun 2007 23:40:12 -0000
>> @@ -14,6 +14,8 @@ User-visible changes since 2.8.7 (in "ve
>> "Utility Syntax Guidelines" in the Minutes of the January 2005
>> Meeting <http://www.opengroup.org/austin/docs/austin_239.html>.
>>
>> +* sdiff now understands '1' and '2' as synonyms for 'l' and 'r'.
>> +
>> Version 2.8.7 contains no user-visible changes.
>
> --
> -Chuck
>
>

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

Message: 12
Date: Thu, 07 Aug 2008 14:43:11 -0400
From: Lisa Besko <besko@msu.edu>
Subject: Re: Swapping boot disks and getting mountroot>===SOLVED
To: freebsd-stable@freebsd.org
Cc: Joseph Koshy <joseph.koshy@gmail.com>
Message-ID: <489B423F.3050102@msu.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

I got thinks working by commenting out
options ATA_STATIC_ID # Static device numbering
in the kernel.

I had to build a test kernel as described in /usr/src/UPDATING.

I still got my mountroot> prompt but for a change is showed me some
possible devices. I was able to ad0s1a to boot from. I rebooted to my
working kernel and edited /etc/fstab to use ad0. Then booted my test
kernel again.

The system booted. I installed the kernel w/o ATA_STATIC_ID and was
able to boot in my Sunfire X2100 and my X2200.

Lisa Besko wrote:
>
>
> Joseph Koshy wrote:
>>> I notice that it finds the device ad4 but then it tries to mount root
>>> from
>>> /dev/ad6s1a. I've edited the fstab to have it look for ad4s1a but it
>>> still
>>> won't boot. Anyone have any pointers or ideas?
>>
>> Have you tried interrupting the boot sequence and setting new
>> values for the `rootdev' and `root_disk_unit' loader variables?
>> The loader(8) manual page has more information.
>
> No I haven't tried that yet. Will that get me to a point where I can
> trust it to boot on it's own to the correct disk all the time?
>
> LB

--
Lisa Besko

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

Message: 13
Date: Fri, 8 Aug 2008 00:59:00 +0400
From: pluknet <pluknet@gmail.com>
Subject: Re: cpufreq(4) panic on RELENG_7 (was: Re: Call for bfe(4)
testers.)
To: "John Baldwin" <jhb@freebsd.org>, freebsd-stable@freebsd.org,
"Ulrich Spoerlein" <uspoerlein@gmail.com>
Message-ID:
<a31046fc0808071359i4d070f7ak3f098d59575cdf9@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

Hi, John.

>> > Fatal trap 12: page fault while in kernel mode
>> > cpuid = 0; apic id = 00
>> > fault virtual address = 0x38
>> > fault code = supervisor read, page not present
>> > instruction pointer = 0x20:0xc058ec16
>> > stack pointer = 0x28:0xfb8b8ac8
>> > frame pointer = 0x28:0xfb8b8ac8
>> > 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 = 1176 (powerd)
>> > db:0:kdb.enter.default> show pcpu
>> > cpuid = 0
>> > curthread = 0xc4ec0aa0: pid 1176 "powerd"
>> > curpcb = 0xfb8b8d90
>> > fpcurthread = none
>> > idlethread = 0xc3f80cc0: pid 10 "idle: cpu0"
>> > APIC ID = 0
>> > currentldt = 0x50
>> > db:0:kdb.enter.default> bt
>> > Tracing pid 1176 tid 100103 td 0xc4ec0aa0
>> > device_is_attached(0,c87e6b40,fb8b8afc,0,101,...) at device_is_attached+0x6
>> > cf_set_method(c420b600,c87e6b40,64,fb8b8ba4,c87e33b4,...) at
>> cf_set_method+0x6a3
>> > cpufreq_curr_sysctl(c420d840,c4207000,0,fb8b8ba4,fb8b8ba4,...) at
>> cpufreq_curr_sysctl+0x232
>> > sysctl_root(fb8b8ba4,4,1,c4ec0aa0,c4501d38,...) at sysctl_root+0x137
>> > userland_sysctl(c4ec0aa0,fb8b8c14,4,0,0,...) at userland_sysctl+0x151
>> > __sysctl(c4ec0aa0,fb8b8cfc,18,fb8b8ca0,46,...) at __sysctl+0xec
>> > syscall(fb8b8d38) at syscall+0x345
>> > Xint0x80_syscall() at Xint0x80_syscall+0x20
>> > --- syscall (202, FreeBSD ELF32, __sysctl), eip = 0x28161bd3, esp =
>> 0xbfbfe8cc, ebp = 0xbfbfe8f8 ---
>> > db:0:kdb.enter.default> capture off
>> >

Is it intentional?

(kgdb) p level.rel_count
$44 = 1986356271

First level.rel_set+5 are NULL in my case.
(kgdb) p i
$46 = 0

P.S. Same problem/hardware/bt/sysctl/dmesg on Banias 1.6GHz, worked ok
on previous stable7 from Jun 16.

hth,
pluknet

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

Message: 14
Date: Thu, 07 Aug 2008 15:36:15 -0700
From: Xin LI <delphij@delphij.net>
Subject: Re: ng_ipacct.c:905: error: too few arguments to function
'in_pcblookup_local'
To: KES <kes-kes@yandex.ru>
Cc: freebsd-stable@freebsd.org
Message-ID: <489B78DF.4000901@delphij.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

KES wrote:
[...]
| kes# make deinstall reinstall clean
| ===> Deinstalling for net-mgmt/ng_ipacct
| ===> ng_ipacct not installed, skipping
| ===> Building for ng_ipacct-20061223
| ===> ng_ipacct (all)
| Warning: Object directory not changed from original
/usr/ports/net-mgmt/ng_ipacct/work/ng_ipacct/ng_ipacct
| cc -O -pipe -g -D_KERNEL -DKLD_MODULE -std=c99 -nostdinc
- -I/usr/ports/net-mgmt/ng_ipacct/work/ng_ipacct/ng_ipacct -I. -I@
- -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100
- --param large-function-growth=1000 -fno-common -mno-align-long-strings
- -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2
- -mno-sse3 -ffreestanding -Wall -Wredundant-decls -Wnested-externs
- -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
- -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c ng_ipacct.c
| ng_ipacct.c: In function 'pcb_get_cred':
| ng_ipacct.c:905: error: too few arguments to function 'in_pcblookup_local'
| *** Error code 1

Newer FreeBSD versions requires a 'ucred' parameter, from my
understanding it looks that one has to pass the current thread's ucred?

Cheers,
- --
Xin LI <delphij@delphij.net> http://www.delphij.net/
FreeBSD - The Power to Serve!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAkibeN4ACgkQi+vbBBjt66DO6wCfeG4bbzuFs40CNR28aNFoR/ld
P0UAniG1zwrzmQurBOg3yRSDejM4mEaN
=mN+B
-----END PGP SIGNATURE-----

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

Message: 15
Date: Thu, 07 Aug 2008 15:55:30 -0700
From: Xin LI <delphij@delphij.net>
Subject: Re: Regression 7.0R -> 7-stable?
To: Gerrit K?hn <gerrit@pmp.uni-hannover.de>
Cc: freebsd-stable@freebsd.org
Message-ID: <489B7D62.4080606@delphij.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gerrit K�hn wrote:
| Hi folks,
|
| I have a rather new FujitsuSiemens Esprimo here with an AMD Phenom X3
| processor (triple core is somehow strange :-) and a lot of NVidia stuff
| onboard. I installed 7.0-R, which ran quite well except for the bge driver
| and snd_hda which both complained.
| After putting in an extra networking card I was able to install some more
| software and all appeared to be nice. Then I cvsupped to the recent
| 7-stable as of today. My hope was that maybe the bge or the sound card
| would improve from this. However, the new kernel I compiled does not run
| at all. It boots up to CPU#1 and CPU#2 lauchned messages and then sits
| there and does nothing anymore. I have verified this behaviour with amd64
| snapshot images from July and August to make sure I did not compile a bad
| kernel. Both show the same behaviour.
| Are there any ideas what has changed from 7.0-R to recent 7.0-stable that
| could cause this? What can I do to debug/fix this?

Could you please try disabling ACPI and boot? Additionally a 'boot -v'
may reveal some useful information as well. Just some random thoughts.

Cheers,
- --
Xin LI <delphij@delphij.net> http://www.delphij.net/
FreeBSD - The Power to Serve!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAkibfWEACgkQi+vbBBjt66CMKwCfcwhp75YfAKOsmPPmmXmzBGSp
3NEAn388u/YD77vpMTRS/QK6moSu3iu1
=1s3u
-----END PGP SIGNATURE-----

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

Message: 16
Date: Fri, 8 Aug 2008 07:58:10 +0200
From: " Sebastian Tymk?w " <sebastian.tymkow@gmail.com>
Subject: Re: Query timeouts on FreeBSD 7 over network
To: "Vinny Abello" <vinny@tellurian.com>
Cc: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org>,
"bind-users@isc.org" <bind-users@isc.org>
Message-ID:
<692660060808072258u24f5a701p67c81d9a7f8f34de@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I gave up and installed Debian (etch ) on other machine.
I've tried FreeBSD 7.0 amd64 on blade machine also and it didn't work
perfectly.
On the same machine with Debian on board problems stopped.
The most strange thing is that on other servers with FreeBSD 4.8 Stable
everything works perfectly
without problems even after bind upgrade.
It looks like Bind and FreeBSD > 6.x have problems or maybe something is
wrong with my machines.
But how to explain that other system on the same machine works fie ?

Best regards,

Sebastian Tymk�w

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

Message: 17
Date: Thu, 7 Aug 2008 23:07:03 -0700 (PDT)
From: Unga <unga888@yahoo.com>
Subject: sysinstall compilation issue
To: freebsd-stable@freebsd.org
Message-ID: <255533.64647.qm@web57001.mail.re3.yahoo.com>
Content-Type: text/plain; charset=us-ascii

This is i386 RELENG_7.

Following section of the /usr/src/usr.sbin/sysinstall/Makefile does not generate C code properly:

makedevs.c: Makefile rtermcap
echo '#include <sys/types.h>' > makedevs.c
${RTERMCAP} ansi | \
file2c 'const char termcap_ansi[] = {' ',0};' \
>> makedevs.c

At compile time, above expands to:
TERMCAP=/usr/src/usr.sbin/sysinstall/../../share/termcap/termcap.src ./rtermcap ansi | file2c 'const char termcap_ansi[] = {' ',0};' >> makedevs.c

Which generates C code as follows:
const char termcap_ansi[] = {

,0};

That is, it generates 3 lines, which results a compilation error.

I presume, intended generated code should be:
const char termcap_ansi[] = {' ',0};

Am I right?

That intended code can be generated by a modified statement as:
TERMCAP=/usr/src/usr.sbin/sysinstall/../../share/termcap/termcap.src ./rtermcap ansi | file2c "const char termcap_ansi[] = {""' ',0};"

What is wrong at my end?

Note, I linked the rtermcap with ncursesw libraries, can that be the cause? Any ideas?

Many thanks in advance.

Kind regards
Unga

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

Message: 18
Date: Fri, 08 Aug 2008 10:10:30 +0100
From: Vincent Hoffman <vince@unsane.co.uk>
Subject: Re: Upgrading from 6.x to 7.x
To: Warren Liddell <shinjii@maydias.com>
Cc: mcoyles@horbury.wakefield.sch.uk, FreeBSD Stable Mailing List
<freebsd-stable@freebsd.org>, freebsd-questions@freebsd.org
Message-ID: <489C0D86.3080702@unsane.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Warren Liddell wrote:
> On Thursday 07 August 2008 23:18:34 Marc Coyles wrote:
>
>>> If i have read the man pages correct the command im using being ...
>>>
>>> # freebsd-update upgrade -r 7.0-CURRENT
>>>
>> # sh freebsd-update.sh -f freebsd-update.conf -r 7.0-RELEASE upgrade
>>
>> followed eventually by...
>>
>> # sh freebsd-update.sh -f freebsd-update.conf install
>>
>> I have just upgraded a 6.2 box to 7.0 Release following the instructions
>> at
>> http://www.daemonology.net/blog/2007-11-11-freebsd-major-version-upgrade
>> .html to the letter without issue (other than bind needing to be
>> reinstalled from ports afterwards)
>>
>> L8rs!
>> Marci
>>
>
>
> # freebsd-update -r 7.0-RELEASE upgrade
> Looking up update.FreeBSD.org mirrors... 1 mirrors found.
> Fetching public key from update1.FreeBSD.org... failed.
> No mirrors remaining, giving up.
>
> # sh freebsd-update.sh -f freebsd-update.conf -r 7.0-RELEASE upgrade
> freebsd-update.sh: Can't open freebsd-update.sh: No such file or directory
>
> I then did a search for the sh file ....
>
> # sh freebsd-update.sh -f freebsd-update.conf -r 7.0-RELEASE upgrade
> File does not exist or is not readable: freebsd-update.conf
>
> freebsd-update is part of base system so there was no need to install it via
> the port etc .. or is there ?
>
>
no for versions of FreeBSD beyond 6.3 its in base and you dont need to
install it seperately to upgrade between versions.
freebsd-update -r 7.1-RELEASE upgrade
seems to have an effect where 7.0-RELEASE no longer does. I have CCed
freebsd-stable@ on this to see if anyone knows if this is intended or a
mistake.

Vince

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

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

Message: 19
Date: Fri, 08 Aug 2008 10:46:30 +0100
From: Vincent Hoffman <vince@unsane.co.uk>
Subject: Re: Upgrading from 6.x to 7.x
To: Warren Liddell <shinjii@maydias.com>
Cc: mcoyles@horbury.wakefield.sch.uk, FreeBSD Stable Mailing List
<freebsd-stable@freebsd.org>, freebsd-questions@freebsd.org
Message-ID: <489C15F6.4080507@unsane.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Warren Liddell wrote:
>> no for versions of FreeBSD beyond 6.3 its in base and you dont need to
>> install it seperately to upgrade between versions.
>> freebsd-update -r 7.1-RELEASE upgrade
>> seems to have an effect where 7.0-RELEASE no longer does. I have CCed
>> freebsd-stable@ on this to see if anyone knows if this is intended or a
>> mistake.
>>
>>
>> Vince
>>
>
> # freebsd-update -r 7.1-RELEASE upgrade
> Looking up update.FreeBSD.org mirrors... 1 mirrors found.
> Fetching public key from update1.FreeBSD.org... failed.
> No mirrors remaining, giving up.
>
> The getting of the public key seems to be the issue no matter how i go about
> trying to upgrade .. so my question now is, why is this and are there other
> mirror sites that can be used ?
>
> Below is my Uname -a output if it has any relevance..
>
> FreeBSD 6.3-STABLE FreeBSD 6.3-STABLE #11: Thu Aug 7 17:32:22 EST 2008
> shinjii@:/usr/obj/usr/src/sys/GENERIC amd64
>
No idea if the fact you are on a -STABLE branch will matter (it could
well, the box I tried to use the 7.0-RELEASE tag on was a -STABLE box
too,) but my test seems to get different results to yours.
Possibly an issue with the freebsd-update servers/mirrors? more likely
that it doesnt support upgrading from an arbitrary point in the -STABLE
tree.

10:05:58 </usr/src/sys/i386/compile/LOBSTER>) 0 # freebsd-update -r
7.1-RELEASE upgrade
Looking up update.FreeBSD.org mirrors... 1 mirrors found.
Fetching metadata signature for 7.0-RELEASE from update1.FreeBSD.org...
done.
Fetching metadata index... done.
Inspecting system... done.

The following components of FreeBSD seem to be installed:
kernel/generic src/base src/bin src/contrib src/crypto src/etc src/games
src/gnu src/include src/krb5 src/lib src/libexec src/release src/rescue
src/sbin src/secure src/share src/sys src/tools src/ubin src/usbin
world/base world/catpages world/dict world/games world/info
world/manpages world/proflibs

The following components of FreeBSD do not seem to be installed:
src/cddl src/compat world/doc

Does this look reasonable (y/n)? n
(10:06:53 </usr/src/sys/i386/compile/LOBSTER>) 0 # uname -a
FreeBSD lobster.unsane.co.uk 7.0-RELEASE-p2 FreeBSD 7.0-RELEASE-p2 #0:
Wed Jun 18 07:33:20 UTC 2008
root@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386

I would upgrade to a -RELEASE branch from source then try again.

Vince

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

Message: 20
Date: Fri, 8 Aug 2008 19:32:36 +1000
From: Warren Liddell <shinjii@maydias.com>
Subject: Re: Upgrading from 6.x to 7.x
To: freebsd-questions@freebsd.org
Cc: mcoyles@horbury.wakefield.sch.uk, FreeBSD Stable Mailing List
<freebsd-stable@freebsd.org>, Vincent Hoffman <vince@unsane.co.uk>
Message-ID: <200808081932.36648.shinjii@maydias.com>
Content-Type: text/plain; charset="iso-8859-1"

> no for versions of FreeBSD beyond 6.3 its in base and you dont need to
> install it seperately to upgrade between versions.
> freebsd-update -r 7.1-RELEASE upgrade
> seems to have an effect where 7.0-RELEASE no longer does. I have CCed
> freebsd-stable@ on this to see if anyone knows if this is intended or a
> mistake.
>
>
> Vince

# freebsd-update -r 7.1-RELEASE upgrade
Looking up update.FreeBSD.org mirrors... 1 mirrors found.
Fetching public key from update1.FreeBSD.org... failed.
No mirrors remaining, giving up.

The getting of the public key seems to be the issue no matter how i go about
trying to upgrade .. so my question now is, why is this and are there other
mirror sites that can be used ?

Below is my Uname -a output if it has any relevance..

FreeBSD 6.3-STABLE FreeBSD 6.3-STABLE #11: Thu Aug 7 17:32:22 EST 2008
shinjii@:/usr/obj/usr/src/sys/GENERIC amd64

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

Message: 21
Date: Fri, 8 Aug 2008 19:50:07 +1000
From: Warren Liddell <shinjii@maydias.com>
Subject: Re: Upgrading from 6.x to 7.x
To: Vincent Hoffman <vince@unsane.co.uk>
Cc: mcoyles@horbury.wakefield.sch.uk, FreeBSD Stable Mailing List
<freebsd-stable@freebsd.org>, freebsd-questions@freebsd.org
Message-ID: <200808081950.08029.shinjii@maydias.com>
Content-Type: text/plain; charset="iso-8859-1"

> I would upgrade to a -RELEASE branch from source then try again.
>
> Vince

change my releng to 7 in the supfile and do a csup then do world & kernel and
go from there ?

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

Message: 22
Date: Fri, 08 Aug 2008 11:09:03 +0100
From: Vincent Hoffman <vince@unsane.co.uk>
Subject: Re: Upgrading from 6.x to 7.x
To: Warren Liddell <shinjii@maydias.com>
Cc: mcoyles@horbury.wakefield.sch.uk, FreeBSD Stable Mailing List
<freebsd-stable@freebsd.org>, freebsd-questions@freebsd.org
Message-ID: <489C1B3F.8040809@unsane.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Warren Liddell wrote:
>> I would upgrade to a -RELEASE branch from source then try again.
>>
>> Vince
>>
>
>
> change my releng to 7 in the supfile and do a csup then do world & kernel and
> go from there ?
>
RELENG_7_0 for the -RELEASE
7 is -STABLE

Vince
> _______________________________________________
> 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"
>

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

Message: 23
Date: Fri, 8 Aug 2008 20:24:12 +1000
From: Warren Liddell <shinjii@maydias.com>
Subject: Re: Upgrading from 6.x to 7.x
To: Vincent Hoffman <vince@unsane.co.uk>
Cc: mcoyles@horbury.wakefield.sch.uk, FreeBSD Stable Mailing List
<freebsd-stable@freebsd.org>, freebsd-questions@freebsd.org
Message-ID: <200808082024.13166.shinjii@maydias.com>
Content-Type: text/plain; charset="iso-8859-1"

On Friday 08 August 2008 20:09:03 Vincent Hoffman wrote:
> Warren Liddell wrote:
> >> I would upgrade to a -RELEASE branch from source then try again.
> >>
> >> Vince
> >
> > change my releng to 7 in the supfile and do a csup then do world & kernel
> > and go from there ?
>
> RELENG_7_0 for the -RELEASE
> 7 is -STABLE
>
> Vince

csup running on 7_0 system all ready backed up so lets see how well this all
goes.

Much tnxs to all who have supplied info on this, greatly appreciated.

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

Message: 24
Date: Fri, 8 Aug 2008 19:18:31 +0900
From: Pyun YongHyeon <pyunyh@gmail.com>
Subject: Re: should looking at an interface with 'ifconfig' trigger a
change ?
To: Pete French <petefrench@ticketswitch.com>
Cc: stable@freebsd.org
Message-ID: <20080808101831.GD38118@cdnetworks.co.kr>
Content-Type: text/plain; charset="us-ascii"

Try attached patch and check whether bce(4) correctly reports link
state changes.

After seeing 'link state changed to UP' message, unplug the cable
and see whether it reports link DOWN. The message should be printed
in a second. Also try replugging cable and you should see link UP
message within several seconds. Since auto-negotation takes more
time you may have to wait for a while.

--
Regards,
Pyun YongHyeon
-------------- next part --------------
--- sys/dev/mii/brgphy.c.orig 2008-01-22 10:23:10.000000000 +0900
+++ sys/dev/mii/brgphy.c 2008-01-22 12:32:41.000000000 +0900
@@ -364,16 +364,13 @@
break;
}

-#if 0
- /* Todo: Is this correct? */
/* Announce link loss right after it happens. */
if (sc->mii_ticks++ == 0)
break;
-

FreeBSD Apache Mysql Php Squid

2008年8月8日

freebsd-stable Digest, Vol 264, Issue 8

0 条评论: