Hi,
On this subject, does somebody know why there is no pending issues listed
at http://www.freebsd.org/releases/6.2R/todo.html ?
--
Philippe Pegon
Jeremy Chadwick wrote:
On Wed, Oct 04, 2006 at 02:34:16PM +1000, John Marshall wrote:
$ dmesg | grep bge
bge0: mem
0xe820-0xe820 irq 17
Jeremy Chadwick skrev:
An alternate idea: remove SCHED_ULE from the GENERIC kernel config
and instead make a ULE config which can be included (similar to
SMP and PAE).
The problem with ULE is that it works so well that you enable it and
forget it. Then a couple of months later you find somethi
Hi all,
I have few servers that have Intel and Broadcom (em&bge) giga NICs
running FreeBSD RELENG_6 (from 6.1-R to 6.2-PRERELEASE).
And (luckily) there are no such problems like watchdog timeouts.
So may be something is different in our configurations, do you want my
kernel confs
or something e
On Wed, Oct 04, 2006 at 08:59:09AM +0200, Martin Nilsson wrote:
> Can we have a commit (at least to STABLE) that adds a big fat message
> during boot that goes something like:
>
> ### You are using SCHED_ULE scheduler ###
> ### SCHED_ULE is still considered to be highly
Scott Long skrev:
In any case, SCHED_ULE is still considered to be highly experimental.
> Hopefully it will get some more attention in the near future to
> bring it closer to production quality.
Can we have a commit (at least to STABLE) that adds a big fat message
during boot that goes somethi
Jeremy Chadwick wrote:
>
> As far as SCHED_ULE goes, if you have issues with it, use SCHED_4BSD.
>
> Now, about watchdog timeouts in general -- there's a pending issue
> which is still under investigation. Please see this thread:
>
That was the "em" thread to which I referred in my original pos
David G Lawrence wrote:
Very interesting data point. I wonder if this accounts for some of the
inconsistency in the reporting from others. In any case, SCHED_ULE is
still considered to be highly experimental. Hopefully it will get some
more attention in the near future to bring it closer to pr
> Very interesting data point. I wonder if this accounts for some of the
> inconsistency in the reporting from others. In any case, SCHED_ULE is
> still considered to be highly experimental. Hopefully it will get some
> more attention in the near future to bring it closer to production
> quality
On Wed, Oct 04, 2006 at 02:34:16PM +1000, John Marshall wrote:
> $ dmesg | grep bge
> bge0: mem
> 0xe820-0xe820 irq 17 at device 4.0 on pci4
> miibus1: on bge0
> bge0: Ethernet address: 00:0b:cd:e7:51:ba
> bge0: watchdog timeout -- resetting
> bge0: link state changed to DOWN
> bge0: link
John Marshall wrote:
$ dmesg | grep bge
bge0: mem
0xe820-0xe820 irq 17 at device 4.0 on pci4
miibus1: on bge0
bge0: Ethernet address: 00:0b:cd:e7:51:ba
bge0: watchdog timeout -- resetting
bge0: link state changed to DOWN
bge0: link state changed to UP
I initially pronounced the network
$ dmesg | grep bge
bge0: mem
0xe820-0xe820 irq 17 at device 4.0 on pci4
miibus1: on bge0
bge0: Ethernet address: 00:0b:cd:e7:51:ba
bge0: watchdog timeout -- resetting
bge0: link state changed to DOWN
bge0: link state changed to UP
I initially pronounced the network cable dead and replace
11 matches
Mail list logo
