Re: ale(4) cannot negotiate as GigE

2013-03-04 Thread Alexey Dokuchaev
On Mon, Mar 04, 2013 at 04:06:32PM +0900, YongHyeon PYUN wrote: On Mon, Mar 04, 2013 at 06:59:40AM +, Alexey Dokuchaev wrote: Better this time, I'm having 1000baseT again! :-) Thanks a lot for testing and patience! Could you reboot multiple times and check whether you reliably get a

Re: access to hard drives is blocked by writes to a flash drive

2013-03-04 Thread Peter Jeremy
On 2013-Mar-03 23:12:40 -0800, Don Lewis truck...@freebsd.org wrote: On 4 Mar, Konstantin Belousov wrote: It could be argued that the current typical value of 16MB for the hirunningbufspace is too low, but experiments with increasing it did not provided any measureable change in the throughput

Re: access to hard drives is blocked by writes to a flash drive

2013-03-04 Thread Poul-Henning Kamp
Content-Type: text/plain; charset=ISO-8859-1 In message 201303040712.r247cejp008...@gw.catspoiler.org, Don Lewis writes: Prior to 231160, the syncer thread would call sync_vnode() for the syncer vnode of each mountpoint every 30 seconds [...] I agree that the lemming syncer is better,

FreeBSD Quarterly Status Report, July-September 2012.

2013-03-04 Thread Isabell Long
FreeBSD Quarterly Status Report, July-September 2012. Introduction This report covers FreeBSD-related projects between July and September 2012. This is the third of the four reports planned for 2012. Highlights from this quarter include successful participation in Google Summer of

FreeBSD Quarterly Status Report, October-December 2012.

2013-03-04 Thread Isabell Long
FreeBSD Quarterly Status Report, October-December 2012. Introduction This report covers FreeBSD-related projects between October and December 2012. This is the last of four reports planned for 2012. Highlights from this status report include a very successful EuroBSDCon 2012

Re: access to hard drives is blocked by writes to a flash drive

2013-03-04 Thread Konstantin Belousov
On Mon, Mar 04, 2013 at 01:44:30PM +, Poul-Henning Kamp wrote: Content-Type: text/plain; charset=ISO-8859-1 In message 201303040712.r247cejp008...@gw.catspoiler.org, Don Lewis writes: Prior to 231160, the syncer thread would call sync_vnode() for the syncer vnode of each

[head tinderbox] failure on armv6/arm

2013-03-04 Thread FreeBSD Tinderbox
TB --- 2013-03-04 13:20:20 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-03-04 13:20:20 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB ---

Re: access to hard drives is blocked by writes to a flash drive

2013-03-04 Thread Ian Lepore
On Sun, 2013-03-03 at 19:01 -0800, Don Lewis wrote: On 3 Mar, Poul-Henning Kamp wrote: For various reasons (see: Lemming-syncer) FreeBSD will block all I/O traffic to other disks too, when these pileups gets too bad. The Lemming-syncer problem should have mostly been fixed by 231160 in

[head tinderbox] failure on arm/arm

2013-03-04 Thread FreeBSD Tinderbox
TB --- 2013-03-04 13:20:20 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-03-04 13:20:20 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB ---

Re: access to hard drives is blocked by writes to a flash drive

2013-03-04 Thread Ian Lepore
On Mon, 2013-03-04 at 07:35 +0200, Konstantin Belousov wrote: On Sun, Mar 03, 2013 at 07:01:27PM -0800, Don Lewis wrote: On 3 Mar, Poul-Henning Kamp wrote: For various reasons (see: Lemming-syncer) FreeBSD will block all I/O traffic to other disks too, when these pileups gets too bad.

Re: access to hard drives is blocked by writes to a flash drive

2013-03-04 Thread Ian Lepore
On Sun, 2013-03-03 at 20:28 +, Steven Hartland wrote: - Original Message - From: Ian Lepore i...@freebsd.org To: Poul-Henning Kamp p...@phk.freebsd.dk Cc: deeptech71 deeptec...@gmail.com; freebsd-current@FreeBSD.org; Peter Jeremy pe...@rulingia.com Sent: Sunday, March 03, 2013

[head tinderbox] failure on i386/i386

2013-03-04 Thread FreeBSD Tinderbox
TB --- 2013-03-04 13:20:20 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-03-04 13:20:20 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB ---

[head tinderbox] failure on amd64/amd64

2013-03-04 Thread FreeBSD Tinderbox
TB --- 2013-03-04 13:20:20 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-03-04 13:20:20 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB ---

[head tinderbox] failure on ia64/ia64

2013-03-04 Thread FreeBSD Tinderbox
TB --- 2013-03-04 15:18:48 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-03-04 15:18:48 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB ---

[head tinderbox] failure on i386/pc98

2013-03-04 Thread FreeBSD Tinderbox
TB --- 2013-03-04 15:10:20 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-03-04 15:10:20 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB ---

[head tinderbox] failure on sparc64/sparc64

2013-03-04 Thread FreeBSD Tinderbox
TB --- 2013-03-04 18:26:28 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-03-04 18:26:28 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB ---

[head tinderbox] failure on powerpc/powerpc

2013-03-04 Thread FreeBSD Tinderbox
TB --- 2013-03-04 17:08:43 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-03-04 17:08:43 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB ---

Re: serial console not accepting input?

2013-03-04 Thread Doug Ambrisko
On Thu, Jan 24, 2013 at 01:23:50PM +, Eggert, Lars wrote: | Hi, | | On Jan 23, 2013, at 17:04, Dimitry Andric d...@freebsd.org wrote: | CTS/RTS hardware flow control, maybe? E.g. add :hw to the default | settings in /etc/gettytab, or make a specific entry with an added :hw | setting. | |

Re: Import libyaml into base

2013-03-04 Thread Simon L. B. Nielsen
On 2 Mar 2013 16:52, Baptiste Daroussin b...@freebsd.org wrote: I want to import libyaml into base as libbsdyml so that no ports will use it like we do for expat. I need it for the pkg bootstrap, so it it can parse pkg.conf. I know that some of the bhyve people will also be glad to use it.

Re: Import libyaml into base

2013-03-04 Thread Baptiste Daroussin
On Mon, Mar 04, 2013 at 09:55:20PM +, Simon L. B. Nielsen wrote: On 2 Mar 2013 16:52, Baptiste Daroussin b...@freebsd.org wrote: I want to import libyaml into base as libbsdyml so that no ports will use it like we do for expat. I need it for the pkg bootstrap, so it it can parse

Re: access to hard drives is blocked by writes to a flash drive

2013-03-04 Thread Don Lewis
On 4 Mar, Peter Jeremy wrote: On 2013-Mar-03 23:12:40 -0800, Don Lewis truck...@freebsd.org wrote: On 4 Mar, Konstantin Belousov wrote: It could be argued that the current typical value of 16MB for the hirunningbufspace is too low, but experiments with increasing it did not provided any

Re: access to hard drives is blocked by writes to a flash drive

2013-03-04 Thread Don Lewis
On 4 Mar, Poul-Henning Kamp wrote: Content-Type: text/plain; charset=ISO-8859-1 In message 201303040712.r247cejp008...@gw.catspoiler.org, Don Lewis writes: Prior to 231160, the syncer thread would call sync_vnode() for the syncer vnode of each mountpoint every 30 seconds [...] I

Re: access to hard drives is blocked by writes to a flash drive

2013-03-04 Thread Don Lewis
On 4 Mar, Ian Lepore wrote: On Sun, 2013-03-03 at 19:01 -0800, Don Lewis wrote: On 3 Mar, Poul-Henning Kamp wrote: For various reasons (see: Lemming-syncer) FreeBSD will block all I/O traffic to other disks too, when these pileups gets too bad. The Lemming-syncer problem should have

Re: access to hard drives is blocked by writes to a flash drive

2013-03-04 Thread Don Lewis
On 4 Mar, Ian Lepore wrote: On Sun, 2013-03-03 at 20:28 +, Steven Hartland wrote: - Original Message - From: Ian Lepore i...@freebsd.org To: Poul-Henning Kamp p...@phk.freebsd.dk Cc: deeptech71 deeptec...@gmail.com; freebsd-current@FreeBSD.org; Peter Jeremy pe...@rulingia.com

Re: ale(4) cannot negotiate as GigE

2013-03-04 Thread YongHyeon PYUN
On Mon, Mar 04, 2013 at 08:18:58AM +, Alexey Dokuchaev wrote: On Mon, Mar 04, 2013 at 04:06:32PM +0900, YongHyeon PYUN wrote: On Mon, Mar 04, 2013 at 06:59:40AM +, Alexey Dokuchaev wrote: Better this time, I'm having 1000baseT again! :-) Thanks a lot for testing and patience!

Re: access to hard drives is blocked by writes to a flash drive

2013-03-04 Thread Poul-Henning Kamp
Content-Type: text/plain; charset=ISO-8859-1 In message 201303050519.r255jbau012...@gw.catspoiler.org, Don Lewis writes: That's been my opinion for a long time as well, though I think it would be better to have one thread per device to avoid syncer threads for multiple partitions on the

Re: ale(4) cannot negotiate as GigE

2013-03-04 Thread Alexey Dokuchaev
On Tue, Mar 05, 2013 at 02:49:20PM +0900, YongHyeon PYUN wrote: On Mon, Mar 04, 2013 at 08:18:58AM +, Alexey Dokuchaev wrote: Yes, multiple reboots was a good idea, it's not very stable: [...] I've tried various combinations of just reboot, shutdown -r +1m and pinging some host while

Re: ale(4) cannot negotiate as GigE

2013-03-04 Thread YongHyeon PYUN
On Tue, Mar 05, 2013 at 06:59:10AM +, Alexey Dokuchaev wrote: On Tue, Mar 05, 2013 at 02:49:20PM +0900, YongHyeon PYUN wrote: On Mon, Mar 04, 2013 at 08:18:58AM +, Alexey Dokuchaev wrote: Yes, multiple reboots was a good idea, it's not very stable: [...] I've tried various