On Mon, Feb 25, 2013 at 05:23:44PM +0900, YongHyeon PYUN wrote:
Then have no idea at this moment. Can you try other OS and check
whether it can establish a gigabit link?
I did not have a chance to try other OS, because machine paniced during
tinderbuilding of a large port. Unfortunately I
On Sun, Mar 03, 2013 at 09:53:30AM +, Alexey Dokuchaev wrote:
However, after reboot ale0 come up at 1000baseT full-duplex, with patched
driver (longer delays in ale_phy_reset()). I've reverted this change and
rebooted again, but it again come up as GigE.
Alas, after make kernel, link come
On Sun, 2013-03-03 at 15:20 +1100, Peter Jeremy wrote:
On 2013-Mar-02 18:29:54 +0100, deeptech71 deeptec...@gmail.com wrote:
When one of my flash drives is being heavily written to; typically by
``svn update'' on /usr/src, located on the flash drive; the following
can be said about
TB --- 2013-03-03 12:00:18 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-03-03 12:00:18 - 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 ---
TB --- 2013-03-03 12:00:18 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-03-03 12:00:18 - 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 ---
Content-Type: text/plain; charset=ISO-8859-1
In message 1362317291.1195.216.ca...@revolution.hippie.lan, Ian Lepore writes
:
I run into this behavior all the time too, mostly on arm systems that
have an sd card or usb thumb driver as their main/only drive.
This is really a FAQ and I
On Sun, 2013-03-03 at 13:35 +, Poul-Henning Kamp wrote:
Content-Type: text/plain; charset=ISO-8859-1
In message 1362317291.1195.216.ca...@revolution.hippie.lan, Ian Lepore
writes
:
I run into this behavior all the time too, mostly on arm systems that
have an sd card or usb
In message 1362318887.1195.221.ca...@revolution.hippie.lan, Ian Lepore writes
:
Hmmm, so the problem has been known and unfixed for 10 years.
It's hard to fix, because a lot of stuff has been tangled up
cyclically in the disk-I/O relevant layers. The umapped buf
stuff which is (finally!)
TB --- 2013-03-03 12:00:18 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-03-03 12:00:18 - 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 ---
TB --- 2013-03-03 12:00:18 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-03-03 12:00:18 - 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 ---
TB --- 2013-03-03 13:35:23 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-03-03 13:35:23 - 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 ---
TB --- 2013-03-03 14:28:26 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-03-03 14:28:26 - 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 ---
TB --- 2013-03-03 14:28:35 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-03-03 14:28:35 - 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 ---
TB --- 2013-03-03 13:35:19 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-03-03 13:35:19 - 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 ---
TB --- 2013-03-03 15:16:47 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-03-03 15:16:47 - 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 ---
TB --- 2013-03-03 14:40:20 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-03-03 14:40: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 ---
TB --- 2013-03-03 15:16:46 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-03-03 15:16:46 - 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 ---
Pawel Jakub Dawidek p...@freebsd.org writes:
I just committed pretty large change that affects not only Capsicum, but
also descriptor handling code in the kernel. If you will find some
strange problems after r243611 (like panics, unexpected application
errors, etc.) I may be at fault. I'll be
On Sun, Mar 03, 2013 at 10:18:02PM +0300, Jan Beich wrote:
Pawel Jakub Dawidek p...@freebsd.org writes:
I just committed pretty large change that affects not only Capsicum, but
also descriptor handling code in the kernel. If you will find some
strange problems after r243611 (like panics,
- 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 1:54 PM
Subject: Re: access to hard drives is blocked by
On Sun, Mar 03, 2013 at 10:18:02PM +0300, Jan Beich wrote:
Pawel Jakub Dawidek p...@freebsd.org writes:
I just committed pretty large change that affects not only Capsicum, but
also descriptor handling code in the kernel. If you will find some
strange problems after r243611 (like panics,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
SVN r247736 prompts this ..
cc -c -O2 -pipe -fno-strict-aliasing -march=pentium4 -std=c99 -Wall
- -Wredundant-decls -Wnested-externs -Wstrict-prototypes
- -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef
- -Wno-pointer-sign
On Sun, Mar 03, 2013 at 06:47:00PM -0500, Michael Butler wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
SVN r247736 prompts this ..
cc -c -O2 -pipe -fno-strict-aliasing -march=pentium4 -std=c99 -Wall
- -Wredundant-decls -Wnested-externs -Wstrict-prototypes
- -Wmissing-prototypes
On Sun, Mar 03, 2013 at 12:00:10PM +, Alexey Dokuchaev wrote:
On Sun, Mar 03, 2013 at 09:53:30AM +, Alexey Dokuchaev wrote:
However, after reboot ale0 come up at 1000baseT full-duplex, with patched
driver (longer delays in ale_phy_reset()). I've reverted this change and
rebooted
On Mon, Mar 04, 2013 at 09:50:44AM +0900, YongHyeon PYUN wrote:
On Sun, Mar 03, 2013 at 12:00:10PM +, Alexey Dokuchaev wrote:
Alas, after make kernel, link come up as 100mbps again, playing with
delays and rebooting (several times) did not make it GigE. I'm not sure
what's actually
On Mon, Mar 04, 2013 at 01:53:44AM +, Alexey Dokuchaev wrote:
On Mon, Mar 04, 2013 at 09:50:44AM +0900, YongHyeon PYUN wrote:
On Sun, Mar 03, 2013 at 12:00:10PM +, Alexey Dokuchaev wrote:
Alas, after make kernel, link come up as 100mbps again, playing with
delays and rebooting
On Mon, Mar 04, 2013 at 11:10:59AM +0900, YongHyeon PYUN wrote:
On Mon, Mar 04, 2013 at 01:53:44AM +, Alexey Dokuchaev wrote:
Yes, it did help. With 2000us delays (I didn't revert them [...]
Great! But it seems 2ms delays is too much. Could you revert the change
(2000us delays) and
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 (231952 in stable/9 and 231967 in stable/8) a little
On 03/04/2013 04:01, Don Lewis wrote:
The Lemming-syncer problem should have mostly been fixed by 231160 in
head (231952 in stable/9 and 231967 in stable/8) a little over a year
ago. The exceptions are atime updates, mmaped files with dirty pages,
and quotas. Under certain workloads I still
On Mon, Mar 04, 2013 at 02:46:31AM +, Alexey Dokuchaev wrote:
On Mon, Mar 04, 2013 at 11:10:59AM +0900, YongHyeon PYUN wrote:
On Mon, Mar 04, 2013 at 01:53:44AM +, Alexey Dokuchaev wrote:
Yes, it did help. With 2000us delays (I didn't revert them [...]
Great! But it seems 2ms
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.
The Lemming-syncer problem should have mostly been fixed by
On Mon, Mar 04, 2013 at 02:23:28PM +0900, YongHyeon PYUN wrote:
Ok, here is final diff which combines two things you've tested.
So revert any changes before applying it.
Let me know how it goes on your box.
Hmm, apparently something went wrong, as I'm back to 100baseTX after make
kernel and
On Mon, Mar 04, 2013 at 05:59:48AM +, Alexey Dokuchaev wrote:
On Mon, Mar 04, 2013 at 02:23:28PM +0900, YongHyeon PYUN wrote:
Ok, here is final diff which combines two things you've tested.
So revert any changes before applying it.
Let me know how it goes on your box.
Hmm, apparently
Content-Type: text/plain; charset=ISO-8859-1
In message 201303040301.r2431rjm008...@gw.catspoiler.org, Don Lewis writes:
When using TCQ or NCQ, perhaps we should limit the number of outstanding
writes per device to leave some slots open for reads. We should
probably also prioritize
On Mon, Mar 04, 2013 at 03:29:44PM +0900, YongHyeon PYUN wrote:
On Mon, Mar 04, 2013 at 05:59:48AM +, Alexey Dokuchaev wrote:
On Mon, Mar 04, 2013 at 02:23:28PM +0900, YongHyeon PYUN wrote:
Ok, here is final diff which combines two things you've tested.
So revert any changes before
On 4 Mar, 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.
The Lemming-syncer
On Mon, Mar 04, 2013 at 06:59:40AM +, Alexey Dokuchaev wrote:
On Mon, Mar 04, 2013 at 03:29:44PM +0900, YongHyeon PYUN wrote:
On Mon, Mar 04, 2013 at 05:59:48AM +, Alexey Dokuchaev wrote:
On Mon, Mar 04, 2013 at 02:23:28PM +0900, YongHyeon PYUN wrote:
Ok, here is final diff which
Planning to check the attached patch later this week, please let me
know if there any objections.
In case where there are no static kernel environment entries, the
function init_dynamic_kenv() adds an incorrect entry at position 0 of
the dynamic kernel environment. This entry is usually
38 matches
Mail list logo
