On 11/6/06, Adrian Chadd <[EMAIL PROTECTED]> wrote:
Just out of curiousity - why wasn't the offending MPSAFE related
changes to em just reverted after discovering the em instability? The
driver -was- stable a couple of months ago, no?
Actually it was not. Some reports have cited problems back
t
Hi,
In bge driver, we have BGE_JUMBO_FRAMELEN defined to 9018.
if_bgereg.h:#define BGE_JUMBO_FRAMELEN 9018
This macro is used to allocate the memory for jumbo buffer. If I have a
MTU size of 2000, still bge will allocate the jumbo buffer of size
BGE_JUMBO_FRAMELEN. Instead can we make the size
Just out of curiousity - why wasn't the offending MPSAFE related
changes to em just reverted after discovering the em instability? The
driver -was- stable a couple of months ago, no?
Adrian
--
Adrian Chadd - [EMAIL PROTECTED]
___
freebsd-stable@freeb
Olivier Mueller wrote:
Le 7 nov. 06 à 01:15, Scott Long a écrit :
Olivier Mueller wrote:
NFS Server: dell poweredge 1950, with the 1.2.2.6 version of if_bce.c:
bce0: mem
- Start a directory listing on it: immediate (network) crash of the NFS
server. (reproduced 3 times)
Do the followin
Le 7 nov. 06 à 01:15, Scott Long a écrit :
Olivier Mueller wrote:
NFS Server: dell poweredge 1950, with the 1.2.2.6 version of
if_bce.c:
bce0: mem
- Start a directory listing on it: immediate (network) crash of
the NFS
server. (reproduced 3 times)
Do the following, then retry your
I'm experiencing kernel panics , and trying to understand something
(not a real kernel hacker... I'm more near 'Hello World' programmer:)
I think there is something like a null-pointer each time, in nd6_output
(crashes 2 and 3)
I'm not sure crash 4 is the same (look like
http://www.freebsd.or
Olivier Mueller wrote:
NFS Server: dell poweredge 1950, with the 1.2.2.6 version of if_bce.c:
bce0: mem
0xf400-0xf5ff irq 16 at device 0.0 on pci9
bce0: ASIC ID 0x57081010; Revision (B1); PCI-X 64-bit 133MHz
miibus0: on bce0
bce0: Ethernet address: 00:13:72:f8:6f:8c
bce0: link state ch
Well, so run 6.2 BETA3 plus the patch I posted as Patrick
mentioned and then report on that. You've got a lot of
potential problem areas here, I have no experience with
samba on FreeBSD. And that motherboard only has PCI
as I recall, yes? Still, it should get rid of the watchdogs
unless you have r
Hi there
I am having similar issues. Running 6.1-RELEASE.
I'm using the box as a samba server with pure-ftpd on it too with 2.5T of
raid storage in it. the box is running the generic MP kernel on a Tyan
Thunder K7 with the latest bios v2.14 and dual AthlonMP's. ECC Reg ram that
passed all tes
NFS Server: dell poweredge 1950, with the 1.2.2.6 version of if_bce.c:
bce0: mem
0xf400-0xf5ff irq 16 at device 0.0 on pci9
bce0: ASIC ID 0x57081010; Revision (B1); PCI-X 64-bit 133MHz
miibus0: on bce0
bce0: Ethernet address: 00:13:72:f8:6f:8c
bce0: link state changed to UP
NFS Client:
Hello!
On Tue, Nov 07, 2006 at 04:55:50AM +0800, ke han wrote:
> I have a Sun X4100 which uses Intel ethernet. I would like to
> install amd64 6.2beta3 on this server and put it through some tests.
> But I have no idea what tests to run or how to run them.
> Can someone provide some pointers?
On Mon, Nov 06, 2006 at 09:37:26PM +, Matthew Seaman wrote:
> We've had a series of Broadcomm bge(4) network interfaces that would
> arbitrarily stop working if hardwired to 100-full, but that are doing
> just fine when allowed to autoneg. Switches are mostly HP Procurve if
> that makes any di
[EMAIL PROTECTED] wrote:
>> I've never paid much attention to what ifconfig says, or what
>> managed switches say, as far as speed or duplex negotiation go.
>> Most vendors do not play well together. I'll repeat that because
>> it needs repeating: most vendors do not play well together.
>> Example
If memory serves me right, ke han wrote:
> According to the 6.2-beta3 announcemetn, there are improvements to
> the em driver.
>
> "The most important of the things that have been worked on is the
> driver for em(4). "
>
> I have a Sun X4100 which uses Intel ethernet. I would like to
> insta
> I've never paid much attention to what ifconfig says, or what
> managed switches say, as far as speed or duplex negotiation go.
> Most vendors do not play well together. I'll repeat that because
> it needs repeating: most vendors do not play well together.
> Example: anyone familiar with Cisco C
According to the 6.2-beta3 announcemetn, there are improvements to
the em driver.
"The most important of the things that have been worked on is the
driver for em(4). "
I have a Sun X4100 which uses Intel ethernet. I would like to
install amd64 6.2beta3 on this server and put it through some
It doesn't effect nearly enough people to warrent a commit to the eratta
branch. It's also not serious enough; the bar has typically been set at
the level of data corruption bugs.
-- Brooks
On Mon, Nov 06, 2006 at 02:20:42PM +0100, Spil Oss wrote:
> Hi all,
>
> Rebuilt dhclient with the bpf.c f
>>
> Check that the USB speed setting in the BIOS is set to its defaults,
> either HiSpeed or FullSpeed, I don't remember exactly. If I change
> it, it similarly hangs on boot, but I'm using FreeBSD/amd64 on it.
Thanks very much for your hint! FreeBSD boots with
USB 2.0 Controller Mode: Fullspee
On Mon, Nov 06, 2006 at 02:45:14PM +0100, Thomas Krause wrote:
> Hello,
> I got a brand new Supermicro H8SSL-i2
> http://www.supermicro.com/Aplus/motherboard/Opteron1000/HT1000/H8SSL-i2.cfm
> but FreeBSD i386 6.2 Beta3 doesn't boot, whether if acpi is enabled or not.
> The latest BIOS is installed.
On Mon, Nov 06, 2006 at 11:31:57AM +0200, Anton - Valqk wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Well,
> the card is connected to a switch that is manageble and the port is set to
> 10Mbit Full duplex on purpose.
Your ifconfig output below shows halfduplex!
> I'm not setting
Hello,
I got a brand new Supermicro H8SSL-i2
http://www.supermicro.com/Aplus/motherboard/Opteron1000/HT1000/H8SSL-i2.cfm
but FreeBSD i386 6.2 Beta3 doesn't boot, whether if acpi is enabled or not.
The latest BIOS is installed. Here is a picture of the boot process with
verbose logging:
http://molda
Yes, no reply yet. But still I would like to ask: Does anyone have *ANY*
experience with "Mustek BearPaw 2448 TA Pro" on FreeBSD ? This scanner was
released in 2003. It is hard problem to find USB scanner on the market
supported by sane. "Mustek ScanExpress 1248 UB" works well but is too
slow.
Hi all,
Rebuilt dhclient with the bpf.c from RELENG_6 ( line 285 == -> >=)
According to the cvs commit log this fixes my problem.
Still leaves me wondering why this was not applied to RELENG_6_1
Kind regards,
Spil.
On 05/11/06, Brooks Davis <[EMAIL PROTECTED]> wrote:
It should be fixed in S
On Mon, Nov 06, 2006 at 11:31:57AM +0200, Anton - Valqk wrote:
> Well,
> the card is connected to a switch that is manageble and the port is set to
> 10Mbit Full duplex on purpose.
>
> I'm not setting the port speed manual - is that a problem when the port is
> not 100mbit/fd?
> This is the ifcon
Anton - Valqk <[EMAIL PROTECTED]> wrote:
> the card is connected to a switch that is manageble and the port is set
> to 10Mbit Full duplex on purpose.
>
> I'm not setting the port speed manual - is that a problem when the port
> is not 100mbit/fd?
If you select the port parameters manually (
John Marshall wrote:
I don't see this at all on 6.1 unless I use SCHED_ULE. (Although, I
haven't compiled all those additional drivers into a 6.1 system, so that
might not be a fair comparison.)
Wrong! I saw this last night for the first time on a production hp
ProLiant ML110 (6.1-RELEASE-p10)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well,
the card is connected to a switch that is manageble and the port is set to
10Mbit Full duplex on purpose.
I'm not setting the port speed manual - is that a problem when the port is not
100mbit/fd?
This is the ifconfig output:
fxp0: flags=18843
27 matches
Mail list logo
