Re: BSD sleep

[Chris Rees]

On 29 May 2013 07:13, "Matthew Seaman"  wrote:
>
> On 29/05/2013 05:59, Michael Sierchio wrote:
> > On Tue, May 28, 2013 at 4:45 PM, Joshua Isom  wrote:
> >
> >
> >> You think it's trivial until you read this:
> >>
> >> http://infiniteundo.com/post/**25326999628/falsehoods-**
> >> programmers-believe-about-time<
http://infiniteundo.com/post/25326999628/falsehoods-programmers-believe-about-time
>
> >>
> >>
> > Some days have 86400 seconds, some have 86401.  There is a provision for
> > two leap seconds to be applied at once, but that hasn't ever happened.
> >  Still, a truly correct clock, set to UTC, might someday read
> >
> > 23:59:59
> > 23:59:60
> > 23:59:61
> > 00:00:00
> >
> > How many seconds did that hour have?
>
> Right.  The fact that on very rare occasions a minute may not have 60
> seconds in it plus many other corner cases in calculating the current
> wall-clock time is an amusing irrelevance.
>
> First of all, sleep deals in local elapsed time, which is a well defined
> property even if the displayed wall-clock time would be all over the
> place due to DST changes or relativistic effects or whatever.
>
> In this case, I'd be pretty surprised if GNU sleep's algorithm was
> anything more complicated than to convert the stated time into seconds
> and then sleep that number of seconds.  And to do that conversion, it
> wwould just define one minute as 60 seconds, one hour as 60 minutes, one
> day as 24 hours, one week as 7 days, perhaps one month as 30 days, one
> year as 365 days[*].  Sure, it's simplistic and unsophisticated, but as
> an engineering solution it's good enough for the vast majority of
> purposes.

OK, but is this really something the OS should handle?  I'm sure sleep
`expr 3600 \* 2` will suffice and is perfectly readable, including being
more portable.

Why should we keep putting these weird "extensions" in?  At some point it
just becomes fiddling, and yet another source of error when porting

Chris
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: BSD sleep

[Quark]

>You think it's trivial until you read this:
>
>http://infiniteundo.com/post/25326999628/falsehoods-programmers-believe-about-time
>
>If you sleep one hour, do you sleep one hour from now or one hour from 
>the system clock which may change in the next hour?  If it's the system 
>clock, you may sleep for ten minutes or ten hours.  If you need to sleep 
>for 3600 seconds, that's simple and understandable.


what is stopping from interpreting 1h in similar manner to 3600? i.e. from now

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: BSD sleep

[Alexander Yerenkow]

>what is stopping from interpreting 1h in similar manner to 3600? i.e. from
now

No, this is user-friendly, and thus can't be done :)
But if think a second, sleep is used rarely by average users, mostly by
programmers and other scripts, and they should know better what they are
doing.

Seriously, that explanation about different hours is not enough to prevent
at least useful option.
like
sleep -f 1h
(-f means force convert, without it you can see good explanation why sleep
for 1 hour will be not sleep for 1 hour, and etc, and not get sleep at
all.).

Exact units in which sleeps happens (seconds, ticks, minutes, years) can be
described in manual page, even without accepting m,h - that info would be
useful for one.

P.S. There is already non-portable feature in sleep - non-integer, and I'm
sure that no one thought about some financists from various countries, who
used to specify long numbers with separator, e.g. 3.600, and this means for
them one hour and not 3 point 6 seconds.

-- 
Regards,
Alexander Yerenkow
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: BSD sleep

[Michael Sierchio]

On Tue, May 28, 2013 at 4:45 PM, Joshua Isom  wrote:


> You think it's trivial until you read this:
>
> http://infiniteundo.com/post/**25326999628/falsehoods-**
> programmers-believe-about-time
>
>
Some days have 86400 seconds, some have 86401.  There is a provision for
two leap seconds to be applied at once, but that hasn't ever happened.
 Still, a truly correct clock, set to UTC, might someday read

23:59:59
23:59:60
23:59:61
00:00:00

How many seconds did that hour have?
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: BSD sleep

[Jason Birch]

> Seriously, that explanation about different hours is not enough to prevent
> at least useful option.
> like
> sleep -f 1h
> (-f means force convert, without it you can see good explanation why sleep
> for 1 hour will be not sleep for 1 hour, and etc, and not get sleep at
> all.).
>

Do one thing, and do it well. What you have proposed involves:
 * an additional force flag
 * interpolation of what follows the force flag (does m mean minutes, or
months?)
 * expectations around time, time zones, and what an hours is.

That fails the litmus test on complexity for me personally - it seems like
a lot of complexity for not much gain.



> P.S. There is already non-portable feature in sleep - non-integer, and I'm
> sure that no one thought about some financists from various countries, who
> used to specify long numbers with separator, e.g. 3.600, and this means for
> them one hour and not 3 point 6 seconds.
>

This isn't a good reason for adding another non-portable feature.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: BSD sleep

[Alexander Yerenkow]

I'm just saying that there's pretty space for discussion.
If someone raised this now, why not discuss it now.

> If you sleep one hour, do you sleep one hour from now or one hour from
the system clock which may change in the next hour? If it's the system
clock, you may sleep for ten minutes or ten hours. If you need to sleep for
3600 seconds, that's simple and understandable.

How about rephrase it:

> If you sleep 3600 seconds, do you sleep 3600 seconds from now or 3600
seconds from the system clock which may change in the next hour? If it's
the system clock, you may sleep for ten minutes or ten hours.

How "way of specifying period" changing the fact that "internal minimal
unit of sleep" is not clearly specified in manpage?
Also, there no info on how DST/ ntp time changes affects of running sleeps.


I don't see right now how new flag (which currently if specified makes
`sleep` exit with help), could break something, but I see that this is
could be useful in some cases.
This also raise question what sleep should do if something specified
incorrectly, like sleep 2h30m30m , or 1h1h or else.

And also if any changes would be accepted, this should be specified in
manpage (that one about `m` as month).

About non-portable feature with non-integers, it was just side observation.


-- 
Regards,
Alexander Yerenkow
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Supermicro 6027R-N3RF+head, usb trouble

[Bryan Drewery]

On 5/29/2013 12:33 AM, Sergey V. Dyatko wrote:
> On Tue, 28 May 2013 13:20:53 -0500
> Bryan Drewery  wrote:
> 
>> On 4/21/2013 2:38 PM, Sergey V. Dyatko wrote:
>>> Hi,
>>>
>>> Can anybody explain why USB keyboard (and keyboard from
>>> integrated IPKVM) doesn't work when I boot with   'C606
>>> chipset Dual 4-Port SATA/SAS Storage Control Unit' enabled in bios?
>>> Also I can't boot that box from usb memstick and
>>> FreeBSD-10.0-CURRENT-amd64-20130413-r249439-release.iso They both
>>> loose(?) device and can't find root If I disable controller in bios
>>> system can't see any sata hdd connected to it:(
>>> booting with hw.usb.ehci.no_hs=1, kern.cam.boot_delay="1"
>>> and debug.acpi.disabled="hostres" without success. I setup dhcpd,
>>> tftp, nfs on my laptop and finally I install fbsd on that box, but
>>> question with kbd is open - It doesn't work..
>>> dmesg:
>>> http://svn.freebsd.by/files/dmesg_N3RF.txt
>>> pciconf -lv:
>>> http://svn.freebsd.by/files/pciconf_N3RF.txt
>>>
>>> I would appreciate any hints
>>>
>>
>> I'm having this exact problem on HEAD r250991 as well. 9.1-RELEASE
>> (disc1) seems ok though.
>>
>> Did you get this figured out?
>>
> 
> I added to loader.conf
> kern.maxbcache="128M"
> vfs.maxbufspace=134217728
> also I create /boot.config with '-v'
> I don't know what exactly help, but now usb kbd (ipkvm) works fine
> for me.
> p.s. It is smbios.system.product="X9DRW"
> 

Yes! This fix of limiting the size worked for me. USB worked on boot, kb
works remotely in the IP KVM and locally as well now.

For the record, this is a DELL C1100 with 72GB of ram. The symptoms
match the previous posts though and the delay settings did not help.

This was working on 9.1-R, something must have changed on HEAD.

This is not a production system, I'm willing to try any patches or
settings to help get this fixed by default.

-- 
Regards,
Bryan Drewery



signature.asc
Description: OpenPGP digital signature

Re: Supermicro 6027R-N3RF+head, usb trouble

[Bryan Drewery]

On 5/29/2013 7:16 AM, Bryan Drewery wrote:
> On 5/29/2013 12:33 AM, Sergey V. Dyatko wrote:
>> On Tue, 28 May 2013 13:20:53 -0500
>> Bryan Drewery  wrote:
>>
>>> On 4/21/2013 2:38 PM, Sergey V. Dyatko wrote:
 Hi,

 Can anybody explain why USB keyboard (and keyboard from
 integrated IPKVM) doesn't work when I boot with   'C606
 chipset Dual 4-Port SATA/SAS Storage Control Unit' enabled in bios?
 Also I can't boot that box from usb memstick and
 FreeBSD-10.0-CURRENT-amd64-20130413-r249439-release.iso They both
 loose(?) device and can't find root If I disable controller in bios
 system can't see any sata hdd connected to it:(
 booting with hw.usb.ehci.no_hs=1, kern.cam.boot_delay="1"
 and debug.acpi.disabled="hostres" without success. I setup dhcpd,
 tftp, nfs on my laptop and finally I install fbsd on that box, but
 question with kbd is open - It doesn't work..
 dmesg:
 http://svn.freebsd.by/files/dmesg_N3RF.txt
 pciconf -lv:
 http://svn.freebsd.by/files/pciconf_N3RF.txt

 I would appreciate any hints

>>>
>>> I'm having this exact problem on HEAD r250991 as well. 9.1-RELEASE
>>> (disc1) seems ok though.
>>>
>>> Did you get this figured out?
>>>
>>
>> I added to loader.conf
>> kern.maxbcache="128M"

^ This setting is all that was needed. The VFS change was not needed.


>> vfs.maxbufspace=134217728
>> also I create /boot.config with '-v'
>> I don't know what exactly help, but now usb kbd (ipkvm) works fine
>> for me.
>> p.s. It is smbios.system.product="X9DRW"
>>
> 
> Yes! This fix of limiting the size worked for me. USB worked on boot, kb
> works remotely in the IP KVM and locally as well now.
> 
> For the record, this is a DELL C1100 with 72GB of ram. The symptoms
> match the previous posts though and the delay settings did not help.
> 
> This was working on 9.1-R, something must have changed on HEAD.
> 
> This is not a production system, I'm willing to try any patches or
> settings to help get this fixed by default.
> 


-- 
Regards,
Bryan Drewery



signature.asc
Description: OpenPGP digital signature

Support of Dell M620 broadcom BCM57810

[Herve Boulouis]

Hi,

I just tried to install 9.1-STABLE on a Dell M620 and it seems its network 
cards (Broadcom NetXtreme 10G BCM57810)
are not yet supported by the bxe driver.

I looked into -head but the driver doesn't seem to support it there either.

It looks like there are some efforts ongoing :

http://freebsd.1045724.n5.nabble.com/panic-at-serial-boot-td5799226.html

Is there some test code I could try ? The goal is to run -stable but I can do 
some testing on -head if necessary.

Regards,

--
Herve Boulouis
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

"make buildworld" fails

[Robert Huff]

On a system running:

 FreeBSD 10.0-CURRENT #0 r248938: Sun Mar 31 06:24:42 EDT 2013 amd64

with the source tree updated every night, "make buildworld"
has failed for about the past week with:

cc -O -pipe -g -DNO_PWD_OVERRIDE -I/usr/src/usr.bin/bmake  -DUSE_META 
-DMAKE_NATIVE -DHAVE_CONFIG_H -DHAVE_CONFIG_H  -DUSE_META -DMAKE_NATIVE 
-DHAVE_CONFIG_H -D_PATH_DEFSYSPATH=\".../share/mk:/usr/share/mk\" -I. 
-I/usr/src/contrib/bmake  -DMAKE_NATIVE  -std=gnu99 -Qunused-arguments 
-fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -W 
-Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith 
-Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int 
-Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality 
-Wno-unused-function -Wno-conversion  -c 
/usr/src/contrib/bmake/lst.lib/lstPrev.c
cc -O -pipe -g -DNO_PWD_OVERRIDE -I/usr/src/usr.bin/bmake  -DUSE_META 
-DMAKE_NATIVE -DHAVE_CONFIG_H -DHAVE_CONFIG_H  -DUSE_META -DMAKE_NATIVE 
-DHAVE_CONFIG_H -D_PATH_DEFSYSPATH=\".../share/mk:/usr/share/mk\" -I. 
-I/usr/src/contrib/bmake  -DMAKE_NATIVE  -std=gnu99 -Qunused-arguments 
-fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -W 
-Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith 
-Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int 
-Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality 
-Wno-unused-function -Wno-conversion  -c 
/usr/src/contrib/bmake/lst.lib/lstRemove.c
cc -O -pipe -g -DNO_PWD_OVERRIDE -I/usr/src/usr.bin/bmake  -DUSE_META 
-DMAKE_NATIVE -DHAVE_CONFIG_H -DHAVE_CONFIG_H  -DUSE_META -DMAKE_NATIVE 
-DHAVE_CONFIG_H -D_PATH_DEFSYSPATH=\".../share/mk:/usr/share/mk\" -I. 
-I/usr/src/contrib/bmake  -DMAKE_NATIVE  -std=gnu99 -Qunused-arguments 
-fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -W 
-Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith 
-Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int 
-Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality 
-Wno-unused-function -Wno-conversion  -c 
/usr/src/contrib/bmake/lst.lib/lstReplace.c
cc -O -pipe -g -DNO_PWD_OVERRIDE -I/usr/src/usr.bin/bmake  -DUSE_META 
-DMAKE_NATIVE -DHAVE_CONFIG_H -DHAVE_CONFIG_H  -DUSE_META -DMAKE_NATIVE 
-DHAVE_CONFIG_H -D_PATH_DEFSYSPATH=\".../share/mk:/usr/share/mk\" -I. 
-I/usr/src/contrib/bmake  -DMAKE_NATIVE  -std=gnu99 -Qunused-arguments 
-fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -W 
-Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith 
-Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int 
-Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality 
-Wno-unused-function -Wno-conversion  -c 
/usr/src/contrib/bmake/lst.lib/lstSucc.c
cc -O -pipe -g -DNO_PWD_OVERRIDE -I/usr/src/usr.bin/bmake  -DUSE_META 
-DMAKE_NATIVE -DHAVE_CONFIG_H -DHAVE_CONFIG_H  -DUSE_META -DMAKE_NATIVE 
-DHAVE_CONFIG_H -D_PATH_DEFSYSPATH=\".../share/mk:/usr/share/mk\" -I. 
-I/usr/src/contrib/bmake  -DMAKE_NATIVE  -std=gnu99 -Qunused-arguments 
-fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -W 
-Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith 
-Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int 
-Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality 
-Wno-unused-function -Wno-conversion  -c /usr/src/contrib/bmake/stresep.c
cc -O -pipe -g -DNO_PWD_OVERRIDE -I/usr/src/usr.bin/bmake  -DUSE_META 
-DMAKE_NATIVE -DHAVE_CONFIG_H -DHAVE_CONFIG_H  -DUSE_META -DMAKE_NATIVE 
-DHAVE_CONFIG_H -D_PATH_DEFSYSPATH=\".../share/mk:/usr/share/mk\" -I. 
-I/usr/src/contrib/bmake  -DMAKE_NATIVE  -std=gnu99 -Qunused-arguments 
-fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -W 
-Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith 
-Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int 
-Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality 
-Wno-unused-function -Wno-conversion   -static -o make arch.o buf.o compat.o 
cond.o dir.o for.o hash.o job.o main.o make.o make_malloc.o meta.o parse.o 
str.o strlist.o suff.o targ.o trace.o util.o var.o lstAppend.o lstAtEnd.o 
lstAtFront.o lstClose.o lstConcat.o lstDatum.o lstDeQueue.o lstDestroy.o 
lstDupl.o lstEnQueue.o lstFind.o lstFindFrom.o lstFirst.o lstForEach.o 
lstForEachFrom.o lstInit.o lstInsert.o lstIsAtEnd.o ls
 tIsEmpty.o lstLast.o lstMember.o lstNext.o lstOpen.o lstPrev.o lstRemove.o 
lstReplace.o lstSucc.o stresep.o 
sh /usr/src/tools/install.sh  -o root -g wheel -m 555   make 
/usr/obj/usr/src/make.amd64/make
usage: make [-BeikNnqrstWX] 
[-C directory] [-D variable] [-d flags] [-f makefile]
[-I directory] [-J private] [-j max_jobs] [-m directory] [-T file]
[-V variable] [variable=value] [target ...]
*** [buildworld] Error code 2

Stop in /usr/src.


I don't 

Re: Support of Dell M620 broadcom BCM57810

[mh]

Hi Ho,

sorry for top posting...
I contacted the Broadcom developers mentioned in bxe(4). Very friendly 
guys.
They said that they're about to give the driver to FreeBSD someday in 
May (2013). I guess that didn't happen yet. I'd suspect it has something 
to do with broadcom's internal procedures...


Since they were that open minded and friendly I'll just go and drop 
them another email and ask them how the driver is doing.


Until than... there's not much you can do except waiting, I guess.

I'm also waiting for support of this driver. Preferably in 9-STABLE :)

BeSD regards,
Marian

Am 2013-05-29 15:13, schrieb Herve Boulouis:

Hi,

I just tried to install 9.1-STABLE on a Dell M620 and it seems its
network cards (Broadcom NetXtreme 10G BCM57810)
are not yet supported by the bxe driver.

I looked into -head but the driver doesn't seem to support it there 
either.


It looks like there are some efforts ongoing :


http://freebsd.1045724.n5.nabble.com/panic-at-serial-boot-td5799226.html

Is there some test code I could try ? The goal is to run -stable but
I can do some testing on -head if necessary.

Regards,

--
Herve Boulouis
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to 
"freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: "make buildworld" fails

[Craig Rodrigues]

On Wed, May 29, 2013 at 7:28 AM, Robert Huff  wrote:

> sh /usr/src/tools/install.sh  -o root -g wheel -m 555   make
> /usr/obj/usr/src/make.amd64/make
> usage: make [-BeikNnqrstWX]
> [-C directory] [-D variable] [-d flags] [-f makefile]
> [-I directory] [-J private] [-j max_jobs] [-m directory] [-T
> file]
> [-V variable] [variable=value] [target ...]
> *** [buildworld] Error code 2
>
> Stop in /usr/src.
>


See this post:
http://lists.freebsd.org/pipermail/freebsd-current/2013-May/041976.html

and see if removing /usr/obj/usr/src/make.amd64/make helps.

--
Craig
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: BSD sleep

[Stuart Barkley]

On Tue, 28 May 2013 at 19:01 -, Kenta Suzumoto wrote:

> Hi. Is there no built-in way of making "sleep" sleep in increments
> of minutes, hours, etc? The GNU "sleep" can be invoked like "sleep
> 1h" for an hour. The FreeBSD one's manpage leads me to believe we
> can only use seconds, which is kind of annoying. Is there an
> undocmented or missing feature here? Seems really trivial to
> implement.
>
> ~ $ sleep 1h
> usage: sleep seconds

See also /usr/ports/misc/delay.

Stuart
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

RE: Support of Dell M620 broadcom BCM57810

[David Christensen]

> Is there some test code I could try ? The goal is to run -stable but I can do
> some testing on -head if necessary.

I'll have some test code to share in about a week.  Please email me directly
if you're interested and if you're willing to help us work out some of the bugs.
We're not quite ready for a kernel submission yet.

Dave


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Supermicro 6027R-N3RF+head, usb trouble

[Konstantin Belousov]

On Wed, May 29, 2013 at 07:45:39AM -0500, Bryan Drewery wrote:
> On 5/29/2013 7:16 AM, Bryan Drewery wrote:
> > On 5/29/2013 12:33 AM, Sergey V. Dyatko wrote:
> >> On Tue, 28 May 2013 13:20:53 -0500
> >> Bryan Drewery  wrote:
> >>
> >>> On 4/21/2013 2:38 PM, Sergey V. Dyatko wrote:
>  Hi,
> 
>  Can anybody explain why USB keyboard (and keyboard from
>  integrated IPKVM) doesn't work when I boot with   'C606
>  chipset Dual 4-Port SATA/SAS Storage Control Unit' enabled in bios?
>  Also I can't boot that box from usb memstick and
>  FreeBSD-10.0-CURRENT-amd64-20130413-r249439-release.iso They both
>  loose(?) device and can't find root If I disable controller in bios
>  system can't see any sata hdd connected to it:(
>  booting with hw.usb.ehci.no_hs=1, kern.cam.boot_delay="1"
>  and debug.acpi.disabled="hostres" without success. I setup dhcpd,
>  tftp, nfs on my laptop and finally I install fbsd on that box, but
>  question with kbd is open - It doesn't work..
>  dmesg:
>  http://svn.freebsd.by/files/dmesg_N3RF.txt
>  pciconf -lv:
>  http://svn.freebsd.by/files/pciconf_N3RF.txt
> 
>  I would appreciate any hints
> 
> >>>
> >>> I'm having this exact problem on HEAD r250991 as well. 9.1-RELEASE
> >>> (disc1) seems ok though.
> >>>
> >>> Did you get this figured out?
> >>>
> >>
> >> I added to loader.conf
> >> kern.maxbcache="128M"
> 
> ^ This setting is all that was needed. The VFS change was not needed.
> 
> 
> >> vfs.maxbufspace=134217728
> >> also I create /boot.config with '-v'
> >> I don't know what exactly help, but now usb kbd (ipkvm) works fine
> >> for me.
> >> p.s. It is smbios.system.product="X9DRW"
> >>
> > 
> > Yes! This fix of limiting the size worked for me. USB worked on boot, kb
> > works remotely in the IP KVM and locally as well now.
> > 
> > For the record, this is a DELL C1100 with 72GB of ram. The symptoms
> > match the previous posts though and the delay settings did not help.
> > 
> > This was working on 9.1-R, something must have changed on HEAD.
> > 
> > This is not a production system, I'm willing to try any patches or
> > settings to help get this fixed by default.
> > 

Could you get the values of sysctl kern.nbuf, kern.bio_transient_maxcnt
from the boot without any tuning of the KVA usage ?


pgpmEd9jOda10.pgp
Description: PGP signature