freebsd-hackers Digest, Vol 366, Issue 3
freebsd-hac...@freebsd.org
freebsd...@freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
or, via email, send a message with subject or body 'help' to
freebsd-hac...@freebsd.org
You can reach the person managing the list at
freebsd-ha...@freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-hackers digest..."
Today's Topics:
1. Dynamic ticks in FreeBSD (Tsuyoshi Ozawa)
2. Re: Dynamic ticks in FreeBSD (Dag-Erling Sm?rgrav)
3. grep (Mark nesterovych)
4. Re: grep (Dag-Erling Sm?rgrav)
5. Re: grep (James P. Howard, II)
6. Re: grep (James P. Howard, II)
7. Re: grep (Gabor Kovesdan)
8. Re: grep (Dominic Fandrey)
9. Re: periodically save current time to time-of-day hardware
(Andriy Gapon)
10. Re: building world with debugging symbols (Giorgos Keramidas)
11. Re: Dynamic ticks in FreeBSD (Julian Elischer)
12. Re: Dynamic ticks in FreeBSD (Roman Divacky)
13. Re: building world with debugging symbols (John Baldwin)
14. kern/104406 on 8.0-RELEASE-p2 ? (Victor Sudakov)
15. Re: grep (Mark nesterovych)
16. Re: kern/104406 on 8.0-RELEASE-p2 ? (Cleber Alves Nascimento)
17. Re: kern/104406 on 8.0-RELEASE-p2 ? (Victor Sudakov)
18. Re: kern/104406 on 8.0-RELEASE-p2 ? (Rink Springer)
----------------------------------------------------------------------
Message: 1
Date: Tue, 30 Mar 2010 05:39:04 -0800
From: Tsuyoshi Ozawa <ozaw...@t-oza.net>
Subject: Dynamic ticks in FreeBSD
To: freebsd-hackers <freebsd...@freebsd.org>
Message-ID:
<411a180c1003300639l13d...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Hello,
I started to work dynamic ticks in FreeBSD, and now experimental
code start to work roughly.
The code is here : http://github.com/oza/FreeBSD-8.0-dyntick
The timer interrupt handler works as follows :
1. Scan callout queue and get when the timer fire. This is the value
we can skip.
2. Run hardware timer in "oneshot mode" instead of periodic mode.
My experimental code only work for local apic timer.
After translating the value which is gotten at 1 to local apic timer
count, pass the value to local apic timer.
3. Exit timer interrupt handler.
My experimental code needs a kernel module to switch to dynamic
tick mode. The kernel module is here : http://gist.github.com/345917
The benchmark is here :
http://tsuyoshiozawa.blogspot.com/2010/03/started-to-implement-dynticks-in.html
The result says that dynticks can save CPU power significantly,
so this worth to work. But this is incomplete to work kernel components
correctly. There are a lot of problems:
1. The global variable "ticks" isn't incremented by 2 and above.
This gets worse the response.
2. To fix problem 1, I have to hack scheduler and profiler.
If I do 1, these kernel component doesn't work correctly.
But 2. is very expensive to implement. I think that it's good to
switch between periodic ticks mode and dynamic ticks mode
when isched_idletd is scheduled. So I'm planning to do this as
a next step.
If you have some idea or question about this work,
please let me know. Thank you!
Very truly yours
Tsuyoshi Ozawa
<oz...@t-oza.net>
------------------------------
Message: 2
Date: Tue, 30 Mar 2010 15:45:49 +0200
From: Dag-Erling Sm?rgrav <d...@des.no>
Subject: Re: Dynamic ticks in FreeBSD
To: Tsuyoshi Ozawa <ozaw...@t-oza.net>
Cc: freebsd-hackers <freebsd...@freebsd.org>
Message-ID: <86fx3hr...@ds4.des.no>
Content-Type: text/plain; charset=utf-8
Tsuyoshi Ozawa <ozaw...@t-oza.net> writes:
> I started to work dynamic ticks in FreeBSD, and now experimental
> code start to work roughly.
This is great! I haven't looked at the patch, but I'm very happy that
someone actually implemented this. We've been talking about it for
years, and there was actually a GSoC project last year, but nothing came
out of it. I really hope we can commit this soon!
BTW, at one point, in your blog, you write "periodic tick mode" instead
of "dynamic tick mode", which had me confused for a moment.
DES
--
Dag-Erling Smørgrav - d...@des.no
------------------------------
Message: 3
Date: Tue, 30 Mar 2010 17:15:46 +0300
From: Mark nesterovych <m.nest...@gmail.com>
Subject: grep
To: hac...@freebsd.org
Message-ID: <1269958546.3456.14.camel@mark-desktop>
Content-Type: text/plain; charset="UTF-8"
Hi all.
Decided to write BSD licensed grep and provide it to FreeBSD project if
success.
But encountered with a problem, which I can resolve.
I looked through the gnu, OpenBSD sources and posix requirements to this
utility, and can't find a solution.
Problem is next. System have few utilities [e|f]grep. And have a keys -E
-F and -G which force the certain regexp processing mode.
But I can't find what to do if mode caused by the utility name is
another than mode of a key provided to it.
If an error should be printed and utility should exit. Or may be a key
must be more preferable.
OpenBSD use the latest key provided in alphabetical order.
Gnu's looks for a single key, error if 2 ore more provided.
Posix requirements aks only for one key to be provided.
How to deal with this in right way ?
--
Mark Nesterovych
------------------------------
Message: 4
Date: Tue, 30 Mar 2010 16:58:19 +0200
From: Dag-Erling Sm?rgrav <d...@des.no>
Subject: Re: grep
To: m.nest...@gmail.com
Cc: hac...@freebsd.org
Message-ID: <86zl1pq...@ds4.des.no>
Content-Type: text/plain; charset=utf-8
Mark nesterovych <m.nest...@gmail.com> writes:
> Decided to write BSD licensed grep and provide it to FreeBSD project if
> success.
There is one already: textproc/bsdgrep.
DES
--
Dag-Erling Smørgrav - d...@des.no
------------------------------
Message: 5
Date: Tue, 30 Mar 2010 11:01:01 -0400
From: "James P. Howard, II" <j...@jameshoward.us>
Subject: Re: grep
To: Dag-Erling Sm?rgrav <d...@des.no>
Cc: hac...@freebsd.org, m.nest...@gmail.com
Message-ID:
<88a2333a1003300801n338...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
2010/3/30 Dag-Erling Smørgrav <d...@des.no>:
> Mark nesterovych <m.nest...@gmail.com> writes:
>> Decided to write BSD licensed grep and provide it to FreeBSD project if
>> success.
>
> There is one already: textproc/bsdgrep.
Which is the basis for both NetBSD's and OpenBSD's implementations.
Also, you can get slightly revised source from here:
http://github.com/howardjp/freegrep
It compiles and runs on both FreeBSD 8 and MacOS X.
James
--
James P. Howard, II, MPA MBCS
j...@jameshoward.us
------------------------------
Message: 6
Date: Tue, 30 Mar 2010 10:47:42 -0400
From: "James P. Howard, II" <j...@jameshoward.us>
Subject: Re: grep
To: m.nest...@gmail.com
Cc: hac...@freebsd.org
Message-ID:
<88a2333a1003300747w3c6...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
On Tue, Mar 30, 2010 at 10:15, Mark nesterovych <m.nest...@gmail.com> wrote:
> Decided to write BSD licensed grep and provide it to FreeBSD project if
> success.
How far along are you in this project?
--
James P. Howard, II, MPA MBCS
j...@jameshoward.us
------------------------------
Message: 7
Date: Tue, 30 Mar 2010 21:34:25 +0545
From: Gabor Kovesdan <ga...@kovesdan.org>
Subject: Re: grep
To: m.nest...@gmail.com
Cc: hac...@freebsd.org
Message-ID: <4BB21D85...@kovesdan.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
On 30/03/2010 20:00, Mark nesterovych wrote:
> Hi all.
>
> Decided to write BSD licensed grep and provide it to FreeBSD project if
> success.
>
Dear Mark,
this project is already completed and is going to be integrated to the
base system once portmgr can run an experimental build to make sure it
introduces no regressions. I suggest that you consider working on either
diff/sdiff or you can contribute to my sort implementation, which is not
totally completed yet.
Gabor
------------------------------
Message: 8
Date: Tue, 30 Mar 2010 17:56:00 +0200
From: Dominic Fandrey <kami...@bsdforen.de>
Subject: Re: grep
To: freebsd...@freebsd.org
Message-ID: <4BB21F10...@bsdforen.de>
Content-Type: text/plain; charset=UTF-8
On 30/03/2010 16:15, Mark nesterovych wrote:
> Decided to write BSD licensed grep and provide it to FreeBSD project if
> success.
> But encountered with a problem, which I can resolve.
> I looked through the gnu, OpenBSD sources and posix requirements to this
> utility, and can't find a solution.
> ...
If FreeBSD is your primary target platform, I'd suggest to do whatever
the currently present implementation of grep does.
Regards
--
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
------------------------------
Message: 9
Date: Tue, 30 Mar 2010 19:43:46 +0300
From: Andriy Gapon <a...@icyb.net.ua>
Subject: Re: periodically save current time to time-of-day hardware
To: John Baldwin <j...@freebsd.org>
Cc: freebsd...@freebsd.org, Dag-Erling Sm?rgrav <d...@des.no>
Message-ID: <4BB22A42...@icyb.net.ua>
Content-Type: text/plain; charset=UTF-8
on 29/03/2010 17:44 John Baldwin said the following:
> On Sunday 28 March 2010 7:45:25 am Dag-Erling Smørgrav wrote:
>> Peter Jeremy <peter...@acm.org> writes:
>>> A new kthread which sleeps on channel "update_rtc". When woken, it
>>> checks to see if it's within (say) 50msec of a second boundary and so,
>>> it does a trylock on the (new) RTC mutex. If it grabs the mutex then
>>> it performs the update. If it was too far from the second boundary or
>>> it fails to grab the mutex then it sleeps until the next second
>>> boundary and tries again.
>>>
>>> The existing resettodr() would then turn into a wakeup(update_rtc).
>> Sounds good to me, but if only that thread has access to the RTC, why
>> bother with a mutex?
>
> I would dispense with the kthread and just use a callout (or have a callout
> schedule a task for taskqueue_thread).
Guys,
do you think that periodic saving of system clock to hardware and making resettodr
asynchronous are dependent issues? Or are they orthogonal and can be implemented
independently?
--
Andriy Gapon
------------------------------
Message: 10
Date: Tue, 30 Mar 2010 18:48:58 +0300
From: Giorgos Keramidas <kera...@ceid.upatras.gr>
Subject: Re: building world with debugging symbols
To: Alexander Best <alexb...@wwu.de>
Cc: Bruce Cran <br...@cran.org.uk>, freebsd...@freebsd.org
Message-ID: <874ojx4...@kobe.laptop>
Content-Type: text/plain; charset="us-ascii"
On Fri, 05 Mar 2010 18:15:33 +0100 (CET), Alexander Best <alexb...@wwu.de> wrote:
>> DEBUG_FLAGS=-g
>
> ahh. thanks for the hint. with DEBUG_FLAGS i was able to build world with
> debugging symbols but also managed to keep the bootloader small enough.
>
> i don't think this option is documented anywhere or is it?
It's not documented in the obvious place I'd look for it: the build(7)
manpage. Does the following look ok?
%%%
diff -r 236fcd32a358 share/man/man7/build.7
--- a/share/man/man7/build.7 Sun Mar 28 00:46:10 2010 +0200
+++ b/share/man/man7/build.7 Tue Mar 30 18:48:16 2010 +0300
@@ -24,7 +24,7 @@
.\"
.\" $FreeBSD$
.\"
-.Dd December 15, 2009
+.Dd March 30, 2010
.Dt BUILD 7
.Os
.Sh NAME
@@ -311,6 +311,20 @@ should be set as with
.Sh ENVIRONMENT
Variables that influence all builds include:
.Bl -tag -width ".Va MAKEOBJDIRPREFIX"
+.It Va DEBUG_FLAGS
+Defines a set of debugging flags that will be used to build all userland
+binaries under
+.Pa /usr/src .
+When
+.Va DEBUG_FLAGS
+is defined, the
+.Cm install
+and
+.Cm installworld
+targets install binaries from the current
+.Va MAKEOBJDIRPREFIX
+without stripping too, so that debugging information is retained in the
+installed binaries.
.It Va DESTDIR
The directory hierarchy prefix where built objects will be installed.
If not set,
%%%
-------------- 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-hackers/attachments/20100330/3cf0a351/attachment-0001.pgp
------------------------------
Message: 11
Date: Tue, 30 Mar 2010 09:56:18 -0700
From: Julian Elischer <jul...@elischer.org>
Subject: Re: Dynamic ticks in FreeBSD
To: Dag-Erling Sm?rgrav <d...@des.no>
Cc: Tsuyoshi Ozawa <ozaw...@t-oza.net>, freebsd-hackers
<freebsd...@freebsd.org>
Message-ID: <4BB22D32...@elischer.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
On 3/30/10 6:45 AM, Dag-Erling Smørgrav wrote:
> Tsuyoshi Ozawa<ozaw...@t-oza.net> writes:
>> I started to work dynamic ticks in FreeBSD, and now experimental
>> code start to work roughly.
>
> This is great! I haven't looked at the patch, but I'm very happy that
> someone actually implemented this. We've been talking about it for
> years, and there was actually a GSoC project last year, but nothing came
> out of it. I really hope we can commit this soon!
>
> BTW, at one point, in your blog, you write "periodic tick mode" instead
> of "dynamic tick mode", which had me confused for a moment.
>
> DES
Who are you? and what have you done with DES?
------------------------------
Message: 12
Date: Tue, 30 Mar 2010 19:35:04 +0200
From: Roman Divacky <rdiv...@freebsd.org>
Subject: Re: Dynamic ticks in FreeBSD
To: Tsuyoshi Ozawa <ozaw...@t-oza.net>
Cc: freebsd-hackers <freebsd...@freebsd.org>
Message-ID: <20100330173...@freebsd.org>
Content-Type: text/plain; charset=us-ascii
On Tue, Mar 30, 2010 at 05:39:04AM -0800, Tsuyoshi Ozawa wrote:
> Hello,
>
> I started to work dynamic ticks in FreeBSD, and now experimental
> code start to work roughly.
> The code is here : http://github.com/oza/FreeBSD-8.0-dyntick
this is great! would it be possible for you to provide a patch?
thnx! roman
------------------------------
Message: 13
Date: Tue, 30 Mar 2010 15:10:58 -0400
From: John Baldwin <j...@freebsd.org>
Subject: Re: building world with debugging symbols
To: freebsd...@freebsd.org
Cc: Giorgos Keramidas <kera...@ceid.upatras.gr>, Alexander Best
<alexb...@wwu.de>, Bruce Cran <br...@cran.org.uk>
Message-ID: <20100330151...@freebsd.org>
Content-Type: Text/Plain; charset="iso-8859-15"
On Tuesday 30 March 2010 11:48:58 am Giorgos Keramidas wrote:
> On Fri, 05 Mar 2010 18:15:33 +0100 (CET), Alexander Best <alexb...@wwu.de>
wrote:
> >> DEBUG_FLAGS=-g
> >
> > ahh. thanks for the hint. with DEBUG_FLAGS i was able to build world with
> > debugging symbols but also managed to keep the bootloader small enough.
> >
> > i don't think this option is documented anywhere or is it?
>
> It's not documented in the obvious place I'd look for it: the build(7)
> manpage. Does the following look ok?
>
> %%%
> diff -r 236fcd32a358 share/man/man7/build.7
> --- a/share/man/man7/build.7 Sun Mar 28 00:46:10 2010 +0200
> +++ b/share/man/man7/build.7 Tue Mar 30 18:48:16 2010 +0300
> @@ -24,7 +24,7 @@
> .\"
> .\" $FreeBSD$
> .\"
> -.Dd December 15, 2009
> +.Dd March 30, 2010
> .Dt BUILD 7
> .Os
> .Sh NAME
> @@ -311,6 +311,20 @@ should be set as with
> .Sh ENVIRONMENT
> Variables that influence all builds include:
> .Bl -tag -width ".Va MAKEOBJDIRPREFIX"
> +.It Va DEBUG_FLAGS
> +Defines a set of debugging flags that will be used to build all userland
> +binaries under
> +.Pa /usr/src .
> +When
> +.Va DEBUG_FLAGS
> +is defined, the
> +.Cm install
> +and
> +.Cm installworld
> +targets install binaries from the current
> +.Va MAKEOBJDIRPREFIX
> +without stripping too, so that debugging information is retained in the
> +installed binaries.
I would drop the "too" and start 'so' on a new line (at least that is my
interpretation of the line-break rules we use for mdoc). Other than that I
think this looks fine.
--
John Baldwin
------------------------------
Message: 14
Date: Wed, 31 Mar 2010 11:40:31 +0700
From: Victor Sudakov <sudakov...@sibptus.tomsk.ru>
Subject: kern/104406 on 8.0-RELEASE-p2 ?
To: freebsd-hackers <freebsd...@freebsd.org>
Message-ID: <20100331044...@admin.sibptus.tomsk.ru>
Content-Type: text/plain; charset=us-ascii
Colleagues,
I seem to have symptoms of kern/104406 on a 8.0-RELEASE-p2 system.
After an uptime of several days, many processes get stuck in the "ufs"
state. The processes which had already opened some files before the
deadlock continue working all right, e.g. my old login sessions are
functional but I cannot start a new ssh session to the box.
Can you advise me a workaround?
The box is being used as a BGP (quagga) router with two full views.
Hardware configuration is below:
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-RELEASE-p2 #0: Tue Jan 5 16:02:27 UTC 2010
ro...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) III CPU family 1133MHz (1129.43-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x6b1 Stepping = 1
Features=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE>
real memory = 1073741824 (1024 MB)
avail memory = 1036312576 (988 MB)
ACPI APIC Table: <AMIINT >
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 2 package(s) x 1 core(s)
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 1
ioapic0 <Version 1.1> irqs 0-23 on motherboard
kbd1 at kbdmux0
acpi0: <AMIINT > on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
Timecounter "ACPI-safe" frequency 3579545 Hz quality 850
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
acpi_button0: <Power Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
agp0: <VIA 82C691 (Apollo Pro) host to PCI bridge> on hostb0
agp0: aperture size is 256M
pcib1: <PCI-PCI bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
vgapci0: <VGA-compatible display> port 0xa800-0xa8ff mem 0xde000000-0xdeffffff,0xdf8ff000-0xdf8fffff irq 17 at device 0.0 on pci1
isab0: <PCI-ISA bridge> at device 7.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <VIA 82C686B UDMA100 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 7.1 on pci0
ata0: <ATA channel 0> on atapci0
ata0: [ITHREAD]
ata1: <ATA channel 1> on atapci0
ata1: [ITHREAD]
uhci0: <VIA 83C572 USB controller> port 0xcc00-0xcc1f irq 11 at device 7.2 on pci0
uhci0: [ITHREAD]
uhci0: LegSup = 0x0030
usbus0: <VIA 83C572 USB controller> on uhci0
uhci1: <VIA 83C572 USB controller> port 0xd000-0xd01f irq 11 at device 7.3 on pci0
uhci1: [ITHREAD]
uhci1: LegSup = 0x0030
usbus1: <VIA 83C572 USB controller> on uhci1
pci0: <serial bus, SMBus> at device 7.4 (no driver attached)
fxp0: <Intel 82559ER Pro/100 Ethernet> port 0xd400-0xd43f mem 0xdfffb000-0xdfffbfff,0xdffc0000-0xdffdffff irq 18 at device 10.0 on pci0
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:02:55:90:64:b6
fxp0: [ITHREAD]
skc0: <Marvell Gigabit Ethernet> port 0xd800-0xd8ff mem 0xdfffc000-0xdfffffff irq 16 at device 12.0 on pci0
skc0: Marvell Yukon Gigabit Ethernet rev. (0x1)
sk0: <Marvell Semiconductor, Inc. Yukon> on skc0
sk0: Ethernet address: 00:80:48:27:18:be
miibus1: <MII bus> on sk0
e1000phy0: <Marvell 88E1011 Gigabit PHY> PHY 0 on miibus1
e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
skc0: [ITHREAD]
fxp1: <Intel 82559 Pro/100 Ethernet> port 0xdc00-0xdc3f mem 0xdffbf000-0xdffbffff,0xdfe00000-0xdfefffff irq 18 at device 14.0 on pci0
miibus2: <MII bus> on fxp1
inphy1: <i82555 10/100 media interface> PHY 1 on miibus2
inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp1: Ethernet address: 00:20:ed:20:72:be
fxp1: [ITHREAD]
acpi_tz0: <Thermal Zone> on acpi0
atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0
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]
fdc0: <floppy drive controller> port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on acpi0
fdc0: [FILTER]
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 (EPP/NIBBLE) 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
cpu1: <ACPI CPU> on acpi0
pmtimer0 on isa0
orm0: <ISA Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xd2fff,0xd3000-0xd6fff 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
Timecounters tick every 1.000 msec
usbus0: 12Mbps Full Speed USB v1.0
usbus1: 12Mbps Full Speed USB v1.0
ad0: 8063MB <FUJITSU MPC3084AT 6018> at ata0-master UDMA33
ugen0.1: <VIA> at usbus0
uhub0: <VIA UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
ugen1.1: <VIA> at usbus1
uhub1: <VIA UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1
SMP: AP CPU #1 Launched!
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
Trying to mount root from ufs:/dev/ad0s2a
WARNING: / was not properly dismounted
sk0: link state changed to UP
--
Victor Sudakov, VAS4-RIPE, VAS47-RIPN
sip:sud...@sibptus.tomsk.ru
------------------------------
Message: 15
Date: Wed, 31 Mar 2010 08:21:48 +0300
From: Mark nesterovych <m.nest...@gmail.com>
Subject: Re: grep
To: j...@jameshoward.us
Cc: hac...@freebsd.org
Message-ID: <1270012908.3456.16.camel@mark-desktop>
Content-Type: text/plain; charset="UTF-8"
On Tue, 2010-03-30 at 11:01 -0400, James P. Howard, II wrote:
> 2010/3/30 Dag-Erling Smørgrav <d...@des.no>:
> > Mark nesterovych <m.nest...@gmail.com> writes:
> >> Decided to write BSD licensed grep and provide it to FreeBSD project if
> >> success.
> >
> > There is one already: textproc/bsdgrep.
>
> Which is the basis for both NetBSD's and OpenBSD's implementations.
> Also, you can get slightly revised source from here:
>
> http://github.com/howardjp/freegrep
>
> It compiles and runs on both FreeBSD 8 and MacOS X.
Looks like project ideas page should be updated.
Will look for new free idea to do.
--
Mark Nesterovych
------------------------------
Message: 16
Date: Wed, 31 Mar 2010 07:02:06 -0300
From: Cleber Alves Nascimento <cle...@bsd.com.br>
Subject: Re: kern/104406 on 8.0-RELEASE-p2 ?
To: Victor Sudakov <sudakov...@sibptus.tomsk.ru>,
freebsd-hackers <freebsd...@freebsd.org>
Message-ID:
<z2ke91a08651003310302k9...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
2010/3/31 Victor Sudakov
<sudakov...@sibptus.tomsk.ru<sudakov%2Bfr...@sibptus.tomsk.ru>
>
> Colleagues,
>
> I seem to have symptoms of kern/104406 on a 8.0-RELEASE-p2 system.
> After an uptime of several days, many processes get stuck in the "ufs"
> state. The processes which had already opened some files before the
> deadlock continue working all right, e.g. my old login sessions are
> functional but I cannot start a new ssh session to the box.
>
> Can you advise me a workaround?
>
> The box is being used as a BGP (quagga) router with two full views.
> Hardware configuration is below:
>
>
> 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-RELEASE-p2 #0: Tue Jan 5 16:02:27 UTC 2010
> ro...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
> Timecounter "i8254" frequency 1193182 Hz quality 0
> CPU: Intel(R) Pentium(R) III CPU family 1133MHz (1129.43-MHz 686-class
> CPU)
> Origin = "GenuineIntel" Id = 0x6b1 Stepping = 1
>
> Features=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE>
> real memory = 1073741824 (1024 MB)
> avail memory = 1036312576 (988 MB)
> ACPI APIC Table: <AMIINT >
> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
> FreeBSD/SMP: 2 package(s) x 1 core(s)
> cpu0 (BSP): APIC ID: 0
> cpu1 (AP): APIC ID: 1
> ioapic0 <Version 1.1> irqs 0-23 on motherboard
> kbd1 at kbdmux0
> acpi0: <AMIINT > on motherboard
> acpi0: [ITHREAD]
> acpi0: Power Button (fixed)
> Timecounter "ACPI-safe" frequency 3579545 Hz quality 850
> acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
> acpi_button0: <Power Button> on acpi0
> pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
> pci0: <ACPI PCI bus> on pcib0
> agp0: <VIA 82C691 (Apollo Pro) host to PCI bridge> on hostb0
> agp0: aperture size is 256M
> pcib1: <PCI-PCI bridge> at device 1.0 on pci0
> pci1: <PCI bus> on pcib1
> vgapci0: <VGA-compatible display> port 0xa800-0xa8ff mem
> 0xde000000-0xdeffffff,0xdf8ff000-0xdf8fffff irq 17 at device 0.0 on pci1
> isab0: <PCI-ISA bridge> at device 7.0 on pci0
> isa0: <ISA bus> on isab0
> atapci0: <VIA 82C686B UDMA100 controller> port
> 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 7.1 on pci0
> ata0: <ATA channel 0> on atapci0
> ata0: [ITHREAD]
> ata1: <ATA channel 1> on atapci0
> ata1: [ITHREAD]
> uhci0: <VIA 83C572 USB controller> port 0xcc00-0xcc1f irq 11 at device 7.2
> on pci0
> uhci0: [ITHREAD]
> uhci0: LegSup = 0x0030
> usbus0: <VIA 83C572 USB controller> on uhci0
> uhci1: <VIA 83C572 USB controller> port 0xd000-0xd01f irq 11 at device 7.3
> on pci0
> uhci1: [ITHREAD]
> uhci1: LegSup = 0x0030
> usbus1: <VIA 83C572 USB controller> on uhci1
> pci0: <serial bus, SMBus> at device 7.4 (no driver attached)
> fxp0: <Intel 82559ER Pro/100 Ethernet> port 0xd400-0xd43f mem
> 0xdfffb000-0xdfffbfff,0xdffc0000-0xdffdffff irq 18 at device 10.0 on pci0
> 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:02:55:90:64:b6
> fxp0: [ITHREAD]
> skc0: <Marvell Gigabit Ethernet> port 0xd800-0xd8ff mem
> 0xdfffc000-0xdfffffff irq 16 at device 12.0 on pci0
> skc0: Marvell Yukon Gigabit Ethernet rev. (0x1)
> sk0: <Marvell Semiconductor, Inc. Yukon> on skc0
> sk0: Ethernet address: 00:80:48:27:18:be
> miibus1: <MII bus> on sk0
> e1000phy0: <Marvell 88E1011 Gigabit PHY> PHY 0 on miibus1
> e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
> 1000baseT-FDX, auto
> skc0: [ITHREAD]
> fxp1: <Intel 82559 Pro/100 Ethernet> port 0xdc00-0xdc3f mem
> 0xdffbf000-0xdffbffff,0xdfe00000-0xdfefffff irq 18 at device 14.0 on pci0
> miibus2: <MII bus> on fxp1
> inphy1: <i82555 10/100 media interface> PHY 1 on miibus2
> inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> fxp1: Ethernet address: 00:20:ed:20:72:be
> fxp1: [ITHREAD]
> acpi_tz0: <Thermal Zone> on acpi0
> atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0
> 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]
> fdc0: <floppy drive controller> port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on acpi0
> fdc0: [FILTER]
> 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 (EPP/NIBBLE) 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
> cpu1: <ACPI CPU> on acpi0
> pmtimer0 on isa0
> orm0: <ISA Option ROMs> at iomem
> 0xc0000-0xc7fff,0xc8000-0xd2fff,0xd3000-0xd6fff 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
> Timecounters tick every 1.000 msec
> usbus0: 12Mbps Full Speed USB v1.0
> usbus1: 12Mbps Full Speed USB v1.0
> ad0: 8063MB <FUJITSU MPC3084AT 6018> at ata0-master UDMA33
> ugen0.1: <VIA> at usbus0
> uhub0: <VIA UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
> ugen1.1: <VIA> at usbus1
> uhub1: <VIA UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1
> SMP: AP CPU #1 Launched!
> uhub0: 2 ports with 2 removable, self powered
> uhub1: 2 ports with 2 removable, self powered
> Trying to mount root from ufs:/dev/ad0s2a
> WARNING: / was not properly dismounted
> sk0: link state changed to UP
>
> --
> Victor Sudakov, VAS4-RIPE, VAS47-RIPN
> sip:sud...@sibptus.tomsk.ru <sip%3Asu...@sibptus.tomsk.ru>
> _______________________________________________
> freebsd...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hacke...@freebsd.org"
>
Do you have disable the flowtable options?
# sysctl net.inet.flowtable.enable=0
net.inet.flowtable.enable: 1 -> 0
This feature is default since 8 release, but is not good for bgp full
routing.
Cleber Alves
--
.ılı..ılı.
"Observe as estrelas e aprenda com elas." Albert Einstein
------------------------------
Message: 17
Date: Wed, 31 Mar 2010 17:58:31 +0700
From: Victor Sudakov <sudakov...@sibptus.tomsk.ru>
Subject: Re: kern/104406 on 8.0-RELEASE-p2 ?
To: freebsd-hackers <freebsd...@freebsd.org>
Message-ID: <20100331105...@admin.sibptus.tomsk.ru>
Content-Type: text/plain; charset=us-ascii
Cleber Alves Nascimento wrote:
> >
> > I seem to have symptoms of kern/104406 on a 8.0-RELEASE-p2 system.
> > After an uptime of several days, many processes get stuck in the "ufs"
> > state. The processes which had already opened some files before the
> > deadlock continue working all right, e.g. my old login sessions are
> > functional but I cannot start a new ssh session to the box.
> >
> > Can you advise me a workaround?
> >
> > The box is being used as a BGP (quagga) router with two full views.
> > Hardware configuration is below:
> >
[dd]
>
> Do you have disable the flowtable options?
>
> # sysctl net.inet.flowtable.enable=0
> net.inet.flowtable.enable: 1 -> 0
>
> This feature is default since 8 release, but is not good for bgp full
> routing.
It seems to be a different issue, kern/144917 related, but a good idea
anyway to set net.inet.flowtable.enable=0. Thank you for the reminder.
However, my box does not crash or lock up hard, just some processes
lock up in the "ufs" state and other processes cannot access files.
--
Victor Sudakov, VAS4-RIPE, VAS47-RIPN
sip:sud...@sibptus.tomsk.ru
------------------------------
Message: 18
Date: Wed, 31 Mar 2010 13:11:42 +0200
From: Rink Springer <ri...@FreeBSD.org>
Subject: Re: kern/104406 on 8.0-RELEASE-p2 ?
To: Victor Sudakov <sudakov...@sibptus.tomsk.ru>, freebsd-hackers
<freebsd...@freebsd.org>
Message-ID: <20100331111...@rink.nu>
Content-Type: text/plain; charset=us-ascii
Hi Victor,
On Wed, Mar 31, 2010 at 05:58:31PM +0700, Victor Sudakov wrote:
> However, my box does not crash or lock up hard, just some processes
> lock up in the "ufs" state and other processes cannot access files.
Have you tried fsck(8)-ing all filesystems to ensure they are OK ?
Regards,
--
Rink P.W. Springer - http://rink.nu
"Beauty often seduces us on the road to truth."
- Dr. Wilson
------------------------------
End of freebsd-hackers Digest, Vol 366, Issue 3
***********************************************