freebsd-stable Digest, Vol 350, Issue 8
freebsd-sta...@freebsd.org
freebsd...@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-sta...@freebsd.org
You can reach the person managing the list at
freebsd-st...@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: random FreeBSD panics (Masoom Shaikh)
2. Re: 8-STABLE/amd64: kernel panic after a minute of mounting
xfs (Nezmer)
3. Re: Results of BIND RFC (Ruben de Groot)
4. Re: random FreeBSD panics (Gary Jennejohn)
5. install touching mbr (Nenhum_de_Nos)
6. Re: install touching mbr (Jeremy Chadwick)
7. Re: install touching mbr (Warren Block)
8. Re: Results of BIND RFC (per...@pluto.rain.com)
9. Re: install touching mbr (Bruce Cran)
10. CPU problems after 8.0-STABLE update (Akephalos Akephalos)
11. Re: CPU problems after 8.0-STABLE update (Andriy Gapon)
----------------------------------------------------------------------
Message: 1
Date: Sat, 3 Apr 2010 12:51:46 +0000
From: Masoom Shaikh <masoom...@gmail.com>
Subject: Re: random FreeBSD panics
To: Ivan Voras <ivo...@freebsd.org>
Cc: freebsd...@freebsd.org, freebsd...@freebsd.org,
freebsd-...@freebsd.org
Message-ID:
<q2ib10011eb1004030551yf...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On Sun, Mar 28, 2010 at 5:38 PM, Ivan Voras <ivo...@freebsd.org> wrote:
> On 28 March 2010 16:42, Masoom Shaikh <masoom...@gmail.com> wrote:
>
>> lets assume if this is h/w problem, then how can other OSes overcome
>> this ? is there a way to make FreeBSD ignore this as well, let it
>> result in reasonable performance penalty.
>
> Very probably, if only we could detect where the problem is.
> Try adding "options � � PRINTF_BUFR_SIZE=128" to the kernel
> configuration file if you can, to see if you can get a less mangled
> log outout.
>
ok, after few days of silence I am back with more questions
this time system feels little better, it is able to sustain for more
time that what 7.3-RELEASE could
FreeBSD raptor 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #0: Thu Apr 1
01:20:45 UTC 2010 root@:/usr/obj/usr/src/sys/INSPIRON amd64
I am using KDE4, and when OS freezes, well it freezes, means I cannot
change to tty0 and see the panic text, if any it might possibly have
spit. the stuck frozen GUI keeps staring there. So the question is how
to I capture that panic text ? unfortunately I am not getting core
files too, so there is nothing I can pick up hints
is there some option (KDB, DDB), so that on panic system drop to debugger ?
Masoom Shaikh
------------------------------
Message: 2
Date: Sat, 3 Apr 2010 16:54:13 +0300
From: Nezmer <b...@nezmer.info>
Subject: Re: 8-STABLE/amd64: kernel panic after a minute of mounting
xfs
To: freebsd...@freebsd.org
Message-ID: <20100403135413.GA2713@mail>
Content-Type: text/plain; charset=us-ascii
On Fri, Mar 26, 2010 at 06:11:06PM +1100, Peter Jeremy wrote:
> On 2010-Mar-25 21:32:10 +0200, Nezmer <b...@nezmer.info> wrote:
> >This is the 1st time FreeBSD panics on me. It happened after a
> >minute of mounting an XFS partition. I'm not sure It's XFS but It's the
> >only part of the OS I try for the 1st time.
> >
> >kernel: vn_iowait doing nothing on FreeBSD?
>
> This is part of XFS. I'm not sure how important it is.
>
> >kernel: Fatal trap 12: page fault while in kernel mode
> ...
> >kernel: Cannot dump. Device not defined or unavailable.
>
> Unfortunately, there's not much that can be done given this
> information. As a minimum, you need a backtrace. Ideally, you need a
> core-dump to investigate the cause.
>
> See http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html
>
> --
> Peter Jeremy
I got a chance to get a backtrace with revision 206096 today. You can
find it with relevant source files here(1). I hope It's enough.
(1) https://nezmer.info/public/xfs_report.tar.gz
------------------------------
Message: 3
Date: Sat, 3 Apr 2010 15:57:03 +0200
From: Ruben de Groot <mai...@bzerk.org>
Subject: Re: Results of BIND RFC
To: Charles Sprickman <sp...@bway.net>
Cc: Reko Turja <reko....@liukuma.net>,
"freebsd-current+AEA-FreeBSD.ORG" <freebsd...@freebsd.org>,
"freebsd...@FreeBSD.org" <freebsd...@freebsd.org>,
"freebs...@FreeBSD.org" <freebs...@freebsd.org>
Message-ID: <20100403135...@ei.bzerk.org>
Content-Type: text/plain; charset=us-ascii
On Fri, Apr 02, 2010 at 02:08:27PM -0400, Charles Sprickman typed:
> Can we do sendmail next April 1?
Better yet, defer all questions about moving <X> out of the base system by
referring to the Grand Discussion that'll take place *next year* on the
first of april.
------------------------------
Message: 4
Date: Sat, 3 Apr 2010 16:35:23 +0200
From: Gary Jennejohn <gary.je...@freenet.de>
Subject: Re: random FreeBSD panics
To: Masoom Shaikh <masoom...@gmail.com>
Cc: freebsd...@freebsd.org, freebsd...@freebsd.org
Message-ID: <20100403163...@ernst.jennejohn.org>
Content-Type: text/plain; charset=US-ASCII
On Sat, 3 Apr 2010 12:51:46 +0000
Masoom Shaikh <masoom...@gmail.com> wrote:
> On Sun, Mar 28, 2010 at 5:38 PM, Ivan Voras <ivo...@freebsd.org> wrote:
> > On 28 March 2010 16:42, Masoom Shaikh <masoom...@gmail.com> wrote:
> >
> >> lets assume if this is h/w problem, then how can other OSes overcome
> >> this ? is there a way to make FreeBSD ignore this as well, let it
> >> result in reasonable performance penalty.
> >
> > Very probably, if only we could detect where the problem is.
> > Try adding "options __ __ PRINTF_BUFR_SIZE=128" to the kernel
> > configuration file if you can, to see if you can get a less mangled
> > log outout.
> >
>
> ok, after few days of silence I am back with more questions
> this time system feels little better, it is able to sustain for more
> time that what 7.3-RELEASE could
>
> FreeBSD raptor 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #0: Thu Apr 1
> 01:20:45 UTC 2010 root@:/usr/obj/usr/src/sys/INSPIRON amd64
>
> I am using KDE4, and when OS freezes, well it freezes, means I cannot
> change to tty0 and see the panic text, if any it might possibly have
> spit. the stuck frozen GUI keeps staring there. So the question is how
> to I capture that panic text ? unfortunately I am not getting core
> files too, so there is nothing I can pick up hints
>
> is there some option (KDB, DDB), so that on panic system drop to debugger ?
>
[trimmed Cc - no need to send this to 3 MLs]
There's no code in the kernel to switch back out of graphics mode (i.e.
what X uses) when a panic happens.
You probably can switch to v0, but you won't be able to see it.
The only sure-fire way is to hook up a screen (terminal, laptop or
another computer) to a serial port.
--
Gary Jennejohn
------------------------------
Message: 5
Date: Sat, 3 Apr 2010 17:48:12 -0300
From: Nenhum_de_Nos <mat...@eternamente.info>
Subject: install touching mbr
To: freebsd...@freebsd.org
Message-ID: <20100403174812....@eternamente.info>
Content-Type: text/plain; charset=US-ASCII
hail,
I just installed a 8.0R amd64 from memstick. when asked, I said to leave mbr untouched. when I rebooted, it was freebsd bootloader that was on control. this options is not what I think it should, or there is really a issue here ?
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
------------------------------
Message: 6
Date: Sat, 3 Apr 2010 13:58:56 -0700
From: Jeremy Chadwick <fre...@jdc.parodius.com>
Subject: Re: install touching mbr
To: freebsd...@freebsd.org
Message-ID: <20100403205...@icarus.home.lan>
Content-Type: text/plain; charset=us-ascii
On Sat, Apr 03, 2010 at 05:48:12PM -0300, Nenhum_de_Nos wrote:
> I just installed a 8.0R amd64 from memstick. when asked, I said to
> leave mbr untouched. when I rebooted, it was freebsd bootloader that
> was on control. this options is not what I think it should, or there
> is really a issue here ?
I can confirm this behaviour. Someone may have broken something when
tinkering around in that part of sysinstall (since the Standard vs.
BootMgr options were moved around compared to previous releases).
--
| Jeremy Chadwick j...@parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
------------------------------
Message: 7
Date: Sat, 3 Apr 2010 15:44:50 -0600 (MDT)
From: Warren Block <wbl...@wonkity.com>
Subject: Re: install touching mbr
To: Jeremy Chadwick <fre...@jdc.parodius.com>
Cc: freebsd...@freebsd.org
Message-ID: <alpine.BSF.2.00.1...@wonkity.com>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
On Sat, 3 Apr 2010, Jeremy Chadwick wrote:
> On Sat, Apr 03, 2010 at 05:48:12PM -0300, Nenhum_de_Nos wrote:
>> I just installed a 8.0R amd64 from memstick. when asked, I said to
>> leave mbr untouched. when I rebooted, it was freebsd bootloader that
>> was on control. this options is not what I think it should, or there
>> is really a issue here ?
>
> I can confirm this behaviour. Someone may have broken something when
> tinkering around in that part of sysinstall (since the Standard vs.
> BootMgr options were moved around compared to previous releases).
Not sure how to repeat the bug, but it's been there at least a few
months:
http://docs.freebsd.org/cgi/mid.cgi?alpine.BSF.2.00.0909262030060.13303
http://docs.freebsd.org/cgi/mid.cgi?58c737d70909262054k7c7b1402w4f9c902fdca2640c
-Warren Block * Rapid City, South Dakota USA
------------------------------
Message: 8
Date: Sat, 03 Apr 2010 19:01:52 -0700
From: per...@pluto.rain.com
Subject: Re: Results of BIND RFC
To: mai...@bzerk.org
Cc: freebsd...@freebsd.org, freebsd...@freebsd.org,
freebs...@freebsd.org
Message-ID: <4bb7f310.gIt41bTtJElBEKHS%per...@pluto.rain.com>
Content-Type: text/plain; charset=us-ascii
Ruben de Groot <mai...@bzerk.org> wrote:
> defer all questions about moving <X> out of the base system ...
Last I knew, X was not _in_ the base system :)
------------------------------
Message: 9
Date: Sun, 4 Apr 2010 04:05:55 +0100
From: Bruce Cran <br...@cran.org.uk>
Subject: Re: install touching mbr
To: freebsd...@freebsd.org
Cc: Jeremy Chadwick <fre...@jdc.parodius.com>
Message-ID: <201004040405...@cran.org.uk>
Content-Type: Text/Plain; charset="iso-8859-1"
On Saturday 03 April 2010 21:58:56 Jeremy Chadwick wrote:
> On Sat, Apr 03, 2010 at 05:48:12PM -0300, Nenhum_de_Nos wrote:
> > I just installed a 8.0R amd64 from memstick. when asked, I said to
> > leave mbr untouched. when I rebooted, it was freebsd bootloader that
> > was on control. this options is not what I think it should, or there
> > is really a issue here ?
>
> I can confirm this behaviour. Someone may have broken something when
> tinkering around in that part of sysinstall (since the Standard vs.
> BootMgr options were moved around compared to previous releases).
I have a patch at http://reviews.freebsdish.org/r/15/ waiting to be committed.
I believe the "None" option won't change the bootcode itself but will still
mark the FreeBSD partition as active.
--
Bruce Cran
------------------------------
Message: 10
Date: Sun, 4 Apr 2010 09:32:01 +0300
From: Akephalos Akephalos <akephalos...@gmail.com>
Subject: CPU problems after 8.0-STABLE update
To: freebsd...@freebsd.org
Message-ID:
<q2v1468a0871004032332kd...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Hey,
I installed 8.0 release and used it very briefly until updating through
cvsup to the latest stable source. I had no problems with the release (DVD)
version, except that my wireless card wasn't detected, so updating was the
natural thing to do. My hardware is an ASUS dual Turion laptop (K50AB), and
my working setup was like this:
- /boot/loader.conf:
cpufreq_load="YES"
hint.acpi_throttle.0.disabled="1"
- /etc/rc.conf:
powerd_enable="YES"
It was working fine, the CPU frequency was scaling as expected, I checked it
numerous times while working and idle with 'sysctl dev.cpu.0.freq'. Also,
the load was displayed correctly in the taskmanager (I don't remember what
was displayed in 'top', but I suppose it was ok).
Now, after updating through buildworld, powerd doesn't scale the frequency
anymore. My observations pointed out that the problem is that the CPU load
is not detected correctly anymore:
- I got three frequency steps: 575, 1150 and 2300 (correctly detected by
dev.cpu.0.freq_levels while cpufreq module is loaded), but powerd scales
down the frequency to the minimum, 575 then keeps it like that no matter of
the load - dev.cpu.0.freq shows 575 and I got large build times because of
it. To be able to use it fully, I have to kill powerd and set the frequency
manually, or disable it at startup.
- 'top -P' displays only one CPU and its load is 0% everything all the time,
despite any load
- I can't see anything in a taskmanager, the last time I tried with xfce and
CURRENT (CURRENT had the same issue)
- dev.cpu.0.cx_usage shows 100%.
---
I'd like to find out the problem, why the CPU level is not detected
correctly and how to fix this/report.
Thanks,
Mihai
------------------------------
Message: 11
Date: Sun, 04 Apr 2010 13:42:59 +0300
From: Andriy Gapon <a...@icyb.net.ua>
Subject: Re: CPU problems after 8.0-STABLE update
To: Akephalos Akephalos <akephalos...@gmail.com>
Cc: freebsd...@freebsd.org
Message-ID: <4BB86D33...@icyb.net.ua>
Content-Type: text/plain; charset=ISO-8859-1
on 04/04/2010 09:32 Akephalos Akephalos said the following:
> - 'top -P' displays only one CPU and its load is 0% everything all the time,
> despite any load
So this is probably the root cause.
Do you I have any unusual messages in dmesg after the upgrade?
Anything about RTC?
--
Andriy Gapon
------------------------------
End of freebsd-stable Digest, Vol 350, Issue 8
**********************************************