I occasionally run into issues that newer PCI device IDs are
not yet supported, these in particular are on a new box
I am working on. Can someone see that these changes
get integrated please :)
Cheers,
Jack
--- dev/ata/ata-chipset.orig.c Fri Jun 2 05:39:18 2006
+++ dev/ata/ata-chipset.c
Both on my own machine, and on systems in our test group's lab, we
notice these long (like 2min maybe?) delays near the end of boot. It
seems to be ATA/SATA related. It has just announced the one disk
it discovered, then shows the CPUs launched, and then it just sits
printing nothing for, like I
On 6/2/06, Gavin Atkinson [EMAIL PROTECTED] wrote:
On Thu, 2006-06-01 at 15:30 -0700, Jack Vogel wrote:
Both on my own machine, and on systems in our test group's lab, we
notice these long (like 2min maybe?) delays near the end of boot. It
seems to be ATA/SATA related. It has just announced
On 6/5/06, Pete French [EMAIL PROTECTED] wrote:
Not that 6.1 is out the dor I monder if anyone wuld like to give me
a hand with an SMP problem I have. I am running a system with two
Opterorn 242 processors in a K8D Master-F motherboard, each with 512M
of RAM attached. The processors both work
On 6/5/06, Pete French [EMAIL PROTECTED] wrote:
You say you can boot 'safe', can you boot with just ACPI disabled?
Not using an SMP kernel, no. I did another experiment though, I
installed amd64 onto an IDe drive, and that will boot SMP with
APCI disabled, but still only recognises a single
On 6/7/06, Pete French [EMAIL PROTECTED] wrote:
If just non-ACPI isnt sufficient, the other thing SAFE does is turn
off disk DMA. I have an as-yet unreleased system that has this
same type of issue, and the problem is that two PCI device ID's
are not recognized, so maybe that will be your
On 6/26/06, Jorn Argelo [EMAIL PROTECTED] wrote:
[sni[
Yahoo . yscrappy Skype: hub.orgICQ . 7615664
Copyright (c) 1992-2006 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989,
On 8/13/06, Arjan van Leeuwen [EMAIL PROTECTED] wrote:
I'm trying to boot FreeBSD 6.1-RELEASE/amd64 on an IBM xSeries 336 machine
with dual Xeons 3.2GHz installed.
The installation was successful, but
if I try to boot the SMP kernel, it hangs after detection of SCSI and ATA
devices (possibly
On 8/20/06, Nikolas Britton [EMAIL PROTECTED] wrote:
On 6/1/06, Jack Vogel [EMAIL PROTECTED] wrote:
I occasionally run into issues that newer PCI device IDs are
not yet supported, these in particular are on a new box
I am working on. Can someone see that these changes
get integrated please
On 8/21/06, Christian Brueffer [EMAIL PROTECTED] wrote:
Not exactly the above patch, but a similar one:
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/ata/ata-chipset.c?rev=1.169content-type=text/x-cvsweb-markup
This is likely to be MFCed before 6.2 gets released.
Oh, this is great news,
On 8/20/06, Darren Pilgrim [EMAIL PROTECTED] wrote:
Johnie Wong wrote:
Dear All,
I am the user of FreeBSD 6.1. Recently, i buy a new server for my
company which is a Intel Core 2 Duo E6300 (1.86GHz) with Intel
D946GZIS mainboard, 2GB Consair DDR2 Ram, 3Ware 9500S-4LP, and 4X
Seagate 250GB
On 8/30/06, Danny Braniss [EMAIL PROTECTED] wrote:
ever since 6.1 I've seen fluctuations in the performance of
the em (Intel(R) PRO/1000 Gigabit Ethernet).
motherboard OBN (On Board NIC)
--
1- Intel
On 9/13/06, Ronald Klop [EMAIL PROTECTED] wrote:
...
Them manual page em(4) mentions trying another cable when the watchdog
timeout happens, so I tried that. But it didn't help.
Is there anything I can test to (help) debug this?
It happens a lot when my machine is under load. (100% CPU)
Is it
On 9/14/06, David C. Myers [EMAIL PROTECTED] wrote:
watchdogs mean that the transmit ring is not being cleaned, so the
question is what is your machine doing at 100% cpu, if its that busy
the network watchdogs may just be a side effect and not the real
problem?
I get them with a
On 9/15/06, Martin Nilsson [EMAIL PROTECTED] wrote:
I'm also seeing these on a Supermicro PDSMi board with a recent stable.
Please tell me what debugging info that is needed to fix this.
/Martin
FreeBSD mailbox 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #1: Sun Sep 10
17:43:15 CEST 2006 [EMAIL
As an optional data point you might wish to consider the Intel
driver I am about to release, it has everything that 6.2 does
EXCEPT the interrupt changes. I kept those out because I
didn't want to break backward compatibility. If someone that
has repro'd this problem wants to check this speak up
Absolutely, its an architecture not a brand name, should call it x86_64
as often done in Linux. If you run only a 32bit kernel on that system of
yours you're cheating yourself out of performance anyway.
slurp down an iso and boot that before you go pulling dimms and such :)
Jack
On 9/27/06,
On 9/27/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Absolutely, its an architecture not a brand name, should call it x86_64
as often done in Linux. If you run only a 32bit kernel on that system of
yours you're cheating yourself out of performance anyway.
slurp down an iso and boot that
On 9/27/06, Bill Moran [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
I have no idea if the problem is related to PAE, but have you tried
booting an amd64 kernel on the system?
This is an Intel Pentium 4 (D) system. Would the AMD64 kernel even work?
I'm not an Intel sales rep, but I
One can't do anything with this kind of information, think about
it as one that has to fix the issue, we need:
- exact model numbers on the system or mb
- pciconf -l so we can see the real version of the adapter
- What exactly was the driver version that last worked, and
what is the
I think there may be a few different problems going on with the em driver
on 6.2 that are being lumped under the general description of network
hangs. In order to solve these I need a reproducible failure, either on a
system here at Intel, or someone who is willing to be a remote guinea
pig :)
I
On 10/18/06, Kip Macy [EMAIL PROTECTED] wrote:
I have a Sun T2000 that I generally run with the em driver from as of
July in order to avoid watchdog timeouts. One trivial scenario that
reproduces the problem with 100% consistency is running the ghc
configure script (a 20kloc shell script) over
On 10/18/06, Albert Shih [EMAIL PROTECTED] wrote:
There is also a hardware eeprom issue on systems with an 82573
type NIC on SOME systems. There is a utility to fix that, if you
and on HP ?
your system does not have 573 NICs, (what you show are 546) do you
have others that are?
Jack
Awesome, this is the kind of data that will help.
I'll see what I can do to get something repro'd.
Jack
On 10/18/06, Albert Shih [EMAIL PROTECTED] wrote:
Le 19/10/2006 01:03:40+0200, Albert Shih a écrit
Le 18/10/2006 10:46:30-0700, Jack Vogel a écrit
I think there may be a few
On 10/19/06, Remko Lodder [EMAIL PROTECTED] wrote:
Kip Macy wrote:
On Wed, 18 Oct 2006, Jack Vogel wrote:
I'm a bit confused from the way you worded this, do you have watchdogs
with em, or you use em to avoid them?
I have watchdogs with the current (post vendor update) em driver
On 10/19/06, Erwin Lansing [EMAIL PROTECTED] wrote:
On Thu, Oct 19, 2006 at 11:40:16AM -0700, Jack Vogel wrote:
On 10/19/06, Remko Lodder [EMAIL PROTECTED] wrote:
Kip Macy wrote:
On Wed, 18 Oct 2006, Jack Vogel wrote:
I'm a bit confused from the way you worded this, do you have watchdogs
The engineer in our test group has installed 6.2 BETA2 and attempted via a
number of tests to reproduce this problem, the machine even shares the em
interrupt with usb, and yet so far he has been unsuccessful.
I have an Intel driver about to be released, it is close, but not identical to
the 6.2
On 10/19/06, Kris Kennaway [EMAIL PROTECTED] wrote:
On Thu, Oct 19, 2006 at 02:18:13PM -0700, Jack Vogel wrote:
The engineer in our test group has installed 6.2 BETA2 and attempted via a
number of tests to reproduce this problem, the machine even shares the em
interrupt with usb, and yet so
On 10/20/06, Bill Paul [EMAIL PROTECTED] wrote:
[Charset ISO-8859-1 unsupported, filtering to ASCII...]
On 10/19/06, Kris Kennaway [EMAIL PROTECTED] wrote:
On Thu, Oct 19, 2006 at 02:18:13PM -0700, Jack Vogel wrote:
The engineer in our test group has installed 6.2 BETA2 and attempted via
On 10/20/06, Scott Long [EMAIL PROTECTED] wrote:
Bill Paul wrote:
[Charset ISO-8859-1 unsupported, filtering to ASCII...]
On 10/19/06, Kris Kennaway [EMAIL PROTECTED] wrote:
On Thu, Oct 19, 2006 at 02:18:13PM -0700, Jack Vogel wrote:
The engineer in our test group has installed 6.2 BETA2
On 10/20/06, Bill Paul [EMAIL PROTECTED] wrote:
This is exactly the test that Andre and I were running, though only in
one direction (I think due to lack of hardware for a full test).
Yes, but did you do it with a Smartbits though, or just with a couple of
other FreeBSD machines?
On 10/20/06, Bill Paul [EMAIL PROTECTED] wrote:
[...]
Another thing that might be handy is improving the watchdog timeout
message so that it dumps the state of the ICR and ICM registers (and
maybe some other interesting driver and/or device state). The timeout
implies no interrupts
On 11/29/05, Mike Tancsa [EMAIL PROTECTED] wrote:
At 09:29 AM 29/11/2005, Lowell Gilbert wrote:
Forrest Aldrich [EMAIL PROTECTED] writes:
I have an older PC (Compaq AP200) that I'm running FreeBSD-6.0 on.
I have an Intel Gigabit interface installed in one of the PCI slots,
along
On 11/29/05, Forrest Aldrich [EMAIL PROTECTED] wrote:
Hi Jack, Mike,
Thank you for your responses. Sorry it took me a day to get to this.
Here is the output per the above command.
Thanks again,
Forrest
...
[EMAIL PROTECTED]:13:0: class=0x02 card=0x11768086 chip=0x10768086
On 10/27/06, Kurt Jaeger [EMAIL PROTECTED] wrote:
Hi!
Can someone report success with the onboard GigE ports of an
Intel S5000PAL board ?
Thanks for any report 8-}
This is one of our new systems, the onboard NICs require either
the latest driver you can download from Intel, or the community
/2006, Jack Vogel wrote:
On 10/27/06, Kurt Jaeger [EMAIL PROTECTED] wrote:
Hi!
Can someone report success with the onboard GigE ports of an
Intel S5000PAL board ?
Thanks for any report 8-}
This is one of our new systems, the onboard NICs require either
the latest driver you can download from Intel
On 10/27/06, Mike Tancsa [EMAIL PROTECTED] wrote:
At 05:28 PM 10/27/2006, Jack Vogel wrote:
Sorry, but you dont want to do this. This is a hybrid
sorta NIC, the PHY is only 10/100, but the MAC is
a Gig part.
Get the latest em driver and load that, guess what, it
will work.
Hi,
I
On 10/27/06, Mike Tancsa [EMAIL PROTECTED] wrote:
At 05:52 PM 10/27/2006, Jack Vogel wrote:
HMMM, ok, maybe I jumped the gun, if this thing says ICH7 then its not
the NIC I was talking about, thats ICH8. I just didnt think there were any
10/100 parts that werent already in the fxp driver.
I
After a conference call today, it was decided that a merge of
my Intel driver base and the STABLE code would take place.
This code undoes the INTR_FAST/taskqueue approach for right
now. Work will continue to get that to work, but the hope is that
this driver will be more stable for the 6.2
On 10/28/06, Nikolay Pavlov [EMAIL PROTECTED] wrote:
On Friday, 27 October 2006 at 18:44:37 -0700, Jack Vogel wrote:
After a conference call today, it was decided that a merge of
my Intel driver base and the STABLE code would take place.
This code undoes the INTR_FAST/taskqueue approach
Contrary to what I was told there are still users with 82542
hardware. I promised that if anyone spoke up I'd replace it,
so its back.
So Intel test and validation isnt always right, who knew :)
Enjoy,
Jack
___
freebsd-stable@freebsd.org mailing list
On 10/31/06, Mikhail Teterin [EMAIL PROTECTED] wrote:
понеділок 30 жовтень 2006 23:23, Mikhail Teterin написав:
Ok. I rebooted and restarted the heavy traffic dump (DEVICE_POLLING in
kernel, but without polling actialy enabled). The dump got underway,
although the amount of sys load was
On 10/31/06, Mikhail Teterin [EMAIL PROTECTED] wrote:
Actually, it stalls even with polling disabled. It just takes A LOT longer, as
I just found out.
Instead of minutes, it takes hours of heavey traffict to stall, but it still
happens. Pressing a key still wakes it up...
-mi
This
On 10/31/06, Jack Vogel [EMAIL PROTECTED] wrote:
On 10/31/06, Mikhail Teterin [EMAIL PROTECTED] wrote:
Actually, it stalls even with polling disabled. It just takes A LOT longer, as
I just found out.
Instead of minutes, it takes hours of heavey traffict to stall, but it still
happens
On 10/31/06, Joerg Pernfuss [EMAIL PROTECTED] wrote:
On Tue, 31 Oct 2006 16:46:10 -0800
Jack Vogel [EMAIL PROTECTED] wrote:
So like :
options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time
extensions
Looks like a special option that most probably dont have
Yes, I know this is still happening. I also have pretty good data now
that its a bogus problem, meaning due to scheduling issues the
watchdog does not get reset even though the system is just fine
as far as transmit descriptors is concerned. I have a patch that
detects this and keeps the watchdog
On 11/2/06, Jeremy Chadwick [EMAIL PROTECTED] wrote:
On Thu, Nov 02, 2006 at 09:43:34AM -0800, Jack Vogel wrote:
Yes, I know this is still happening. I also have pretty good data now
that its a bogus problem, meaning due to scheduling issues the
watchdog does not get reset even though
Yes, this is the second report I've had, other came to me personally.
I'm looking into it.
Jack
On 11/2/06, Craig Boston [EMAIL PROTECTED] wrote:
Don't have much time right now, but wanted to report that the new em
driver in -STABLE breaks jumbo frame support for me. With it in the
kernel
On 11/3/06, M. Warner Losh [EMAIL PROTECTED] wrote:
In message: [EMAIL PROTECTED]
Rink Springer [EMAIL PROTECTED] writes:
: Hi people,
:
: Recently, I installed FreeBSD on a Tyan GS14 barebone, which houses an
: bge(4) and a fxp(4). However, FreeBSD does not recognize the on-board
:
I have been hard at work trying to understand and fix the
remaining issues with the em driver. What I have here is
a patch that has gotten rid of any issues that I can reproduce.
It solves the intermittent watchdogs that have been happening.
It also fixes the problem noted with jumbo frame tx
On 11/3/06, Kip Macy [EMAIL PROTECTED] wrote:
If you create a patch against -CURRENT I can test on sun4v. The timeouts
with em on sun4v are so severe that I have to use the driver from June for
any kind of workload.
-Kip
I believe Gleb was going to merge code to current so you should
have
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
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
to
On 11/7/06, Clayton Milos [EMAIL PROTECTED] wrote:
Hi Jack
I patched the driver and re-compiled the kernel and userland.
All appears well with the em driver now. No more errors on it.
I am getting watchdog timeouts on the xl driver now though. It was
happenning before at the same time as the
On 11/7/06, Mike Jakubik [EMAIL PROTECTED] wrote:
Clayton Milos wrote:
Hi Jack
I patched the driver and re-compiled the kernel and userland.
All appears well with the em driver now. No more errors on it.
I am getting watchdog timeouts on the xl driver now though. It was
happenning before
This patch is an evolution of the last one I sent out. It has
a couple of minor corrections, like a bad forward decl in
the header.
The last patch has had quite a bit of testing and all reports
have been positive. The only complaint was from Gleb who
says he needs to keep his beloved infinite
wanted
to get this code back into the driver conditionally before
RELEASE.
Does that answer your question Sam?
Regards,
Jack
On 11/9/06, Jack Vogel [EMAIL PROTECTED] wrote:
This patch is an evolution of the last one I sent out. It has
a couple of minor corrections, like a bad forward decl
Yes, they are incompatible, I suppose there should be something
that makes it impossible to do, but not building should be a clue :)
Jack
On 11/9/06, Mike Tancsa [EMAIL PROTECTED] wrote:
At 08:19 PM 11/8/2006, Jack Vogel wrote:
BUT, I've added the FAST_INTR changes back into the code, so
On 11/10/06, Mike Tancsa [EMAIL PROTECTED] wrote:
Some more tests. I tried again with what was committed to today's
RELENG_6. I am guessing its pretty well the same patch. Polling is
the only way to avoid livelock at a high pps rate. Does anyone know
of any simple tools to measure end to end
On 11/10/06, Barry Boes [EMAIL PROTECTED] wrote:
Luck ran out. Hard must press the reset button hang. No console
messages. The system was idle at the time.
Is there anything you'd like me to do to attempt to narrow down the
problem or get debugging output? I do not know if the freeze
On 11/13/06, Bill Moran [EMAIL PROTECTED] wrote:
Just experienced an interrupt storm on an em device that disabled a
server until I could reboot it.
My initial research turned up this thread:
http://lists.freebsd.org/pipermail/freebsd-current/2005-November/058336.html
Which seems related,
On 12/12/06, Chris Buechler [EMAIL PROTECTED] wrote:
I'm attempting to install 6.2-RC1 on a box that ran 5.3, 5.4, 6.0, and
6.1 for the past few years, but the 6.2-RC1 CD won't boot. After it
detects the em0 NIC, before it gets into sysinstall, it freezes solid.
I've let it sit there for over
On 12/12/06, Jack Vogel [EMAIL PROTECTED] wrote:
On 12/12/06, Chris Buechler [EMAIL PROTECTED] wrote:
I'm attempting to install 6.2-RC1 on a box that ran 5.3, 5.4, 6.0, and
6.1 for the past few years, but the 6.2-RC1 CD won't boot. After it
detects the em0 NIC, before it gets into sysinstall
On 12/12/06, Chris Buechler [EMAIL PROTECTED] wrote:
Jack Vogel wrote:
UH, can't do anything if you don't give any information, saying its a
'box'
and it has an 'em' is useless. We have installed RC1 on a number of
systems without problem.
Yes, I understand that. I was after what info
On 12/13/06, Chris Buechler [EMAIL PROTECTED] wrote:
Jack Vogel wrote:
I need the PCI ID of that NIC, just to be sure that I can't reproduce
this, but
I doubt it, pciconf -l
Here's the pciconf -l from 6.2-RC1, custom kernel (copy of GENERIC,
minus 'device em')
[EMAIL PROTECTED]:0:0: class
On 1/7/07, Erik Trulsson [EMAIL PROTECTED] wrote:
On Sun, Jan 07, 2007 at 04:56:26PM +0100, O. Hartmann wrote:
Hello,
the company I'm working is about to purchae some additional NICs for
some replacement built-in NICs of nForce 405-based desktop PCs. I would
like to purchase the above
On 1/10/07, Colin Percival [EMAIL PROTECTED] wrote:
Scott T. Hildreth wrote:
Does anyone know if the Release is still going to happen today?
The release is not going to happen today, but will be very soon. My
guess is that builds and mirroring will happen over the weekend and
the release
On 1/11/07, Bruce A. Mah [EMAIL PROTECTED] wrote:
If memory serves me right, Jack Vogel wrote:
On 1/10/07, Colin Percival [EMAIL PROTECTED] wrote:
Scott T. Hildreth wrote:
Does anyone know if the Release is still going to happen today?
The release is not going to happen today
On 1/16/07, Jeremy Chadwick [EMAIL PROTECTED] wrote:
On Tue, Jan 16, 2007 at 10:53:04AM -0800, Jack Vogel wrote:
There are some management related issues with this NIC, first if you
have not done so make a DOS bootable device, and run this app I
am enclosing, it fixes the prom setting
Since this was just seen, and the patch below validated as working I wanted
to send general email to capture this:
The Lenovo X60 can have issues with long ping times, this is a KNOWN
hardware problem, and Intel is working with IBM/Lenovo, a final 'fix' has
not been decided on yet. Nevertheless,
On 1/19/07, Bill Paul [EMAIL PROTECTED] wrote:
Since this was just seen, and the patch below validated as working I wanted
to send general email to capture this:
The Lenovo X60 can have issues with long ping times, this is a KNOWN
hardware problem, and Intel is working with IBM/Lenovo, a
On 1/22/07, Gleb Smirnoff [EMAIL PROTECTED] wrote:
Jack,
On Sat, Jan 20, 2007 at 02:35:17PM -0800, Jack Vogel wrote:
J Since this was just seen, and the patch below validated as working I
J wanted
J to send general email to capture this:
J
J The Lenovo X60 can have issues with long ping
On 1/22/07, Jack Vogel [EMAIL PROTECTED] wrote:
On 1/22/07, Gleb Smirnoff [EMAIL PROTECTED] wrote:
Jack,
On Sat, Jan 20, 2007 at 02:35:17PM -0800, Jack Vogel wrote:
J Since this was just seen, and the patch below validated as working I
J wanted
J to send general email to capture
On 1/23/07, Guy Helmer [EMAIL PROTECTED] wrote:
Using FreeBSD 6.2, I'm having trouble with the Supermicro X7DBR-8+
motherboard (dual Xeon 5130 CPUs on the Blackford chipset -
http://www.supermicro.com/products/motherboard/Xeon1333/5000P/X7DBR-8+.cfm)
hanging after printing the Waiting 5 seconds
On 1/23/07, Louis Kowolowski [EMAIL PROTECTED] wrote:
On Mon, Jan 22, 2007 at 10:34:48AM -0800, Jack Vogel wrote:
On 1/22/07, Jack Vogel [EMAIL PROTECTED] wrote:
On 1/22/07, Gleb Smirnoff [EMAIL PROTECTED] wrote:
Jack,
On Sat, Jan 20, 2007 at 02:35:17PM -0800, Jack Vogel wrote:
J
On 1/24/07, Gavin Atkinson [EMAIL PROTECTED] wrote:
On Mon, 2007-01-22 at 10:30 -0800, Jack Vogel wrote:
On 1/22/07, Gleb Smirnoff [EMAIL PROTECTED] wrote:
Jack,
On Sat, Jan 20, 2007 at 02:35:17PM -0800, Jack Vogel wrote:
J Since this was just seen, and the patch below validated
On 1/30/07, Mike Tancsa [EMAIL PROTECTED] wrote:
On one of my servers (RELENG_6 as of yesterday), I am seeing what
appears to be RX overruns. Load avg does not seem to be high, and the
only odd thing I have done to the kernel is defined
#define EM_FAST_INTR 1
The man page talks about setting
On 3/4/07, Mark Costlow [EMAIL PROTECTED] wrote:
The Machine:
I have a dual Xeon 5130 machine, Supermicro motherboard, with
the 82563EB NIC. From dmesg:
CPU: Intel(R) Xeon(R) CPU5130 @ 2.00GHz (2000.08-MHz 686-class CPU)
cpu0: ACPI CPU on acpi0
em0: Intel(R) PRO/1000 Network
On 3/4/07, Duane Whitty [EMAIL PROTECTED] wrote:
On Sun, Mar 04, 2007 at 11:30:07PM -0700, Mark Costlow wrote:
The Machine:
I have a dual Xeon 5130 machine, Supermicro motherboard, with
the 82563EB NIC. From dmesg:
CPU: Intel(R) Xeon(R) CPU5130 @ 2.00GHz (2000.08-MHz
On 3/5/07, Mark Costlow [EMAIL PROTECTED] wrote:
On Mon, Mar 05, 2007 at 08:41:01AM -0800, Jack Vogel wrote:
Maybe more of your dmesg might help as it could show interrrupt issues
that perhaps others could help diagnose
Yes, agreed, this might be revealing.
Here's the full dmesg. Thanks
On 3/5/07, Jack Vogel [EMAIL PROTECTED] wrote:
On 3/5/07, Mark Costlow [EMAIL PROTECTED] wrote:
On Mon, Mar 05, 2007 at 08:41:01AM -0800, Jack Vogel wrote:
Maybe more of your dmesg might help as it could show interrrupt issues
that perhaps others could help diagnose
Yes, agreed
On 3/5/07, Mark Costlow [EMAIL PROTECTED] wrote:
On Mon, Mar 05, 2007 at 10:02:26AM -0800, Jack Vogel wrote:
On 3/5/07, Jack Vogel [EMAIL PROTECTED] wrote:
On 3/5/07, Mark Costlow [EMAIL PROTECTED] wrote:
On Mon, Mar 05, 2007 at 08:41:01AM -0800, Jack Vogel wrote:
Maybe more of your
On 3/5/07, Artem Kuchin [EMAIL PROTECTED] wrote:
Hello!
I hope some people will understand what i am talking about, because
the technology, i think, is not very popular, but can come VERY handy.
Intel AMT Serial over LAN (SOL, why is it called 'over LAN' if it is really
'OVER IP'?) allows to
On 3/6/07, Artem Kuchin [EMAIL PROTECTED] wrote:
I hope some people will understand what i am talking about, because
the technology, i think, is not very popular, but can come VERY handy.
Intel AMT Serial over LAN (SOL, why is it called 'over LAN' if it is really
'OVER IP'?) allows to boot
On 3/6/07, Vivek Khera [EMAIL PROTECTED] wrote:
On Mar 6, 2007, at 1:04 PM, Jack Vogel wrote:
Yes, my bad, I spoke too quickly, it does use IP, sorry,
I still find SOL much more descriptive of what I think about
the whole apparatus however :)
:-)
Personally, I really like the Sun ILOM
On 3/13/07, Jeremy Chadwick [EMAIL PROTECTED] wrote:
On Tue, Mar 13, 2007 at 02:58:34PM -0500, Nikolas Britton wrote:
We need to start hounding on AMD to publish the developer
documentation for all radeon chipsets. I for one will not buy any AMD
or ATI components until they decide to fix the
On 4/5/07, Jasper Berlijn [EMAIL PROTECTED] wrote:
Hi,
At this moment I'm running FreeBSD 4.11 without any problems. A couple
of times I've tried to upgrade to 6.x but without any luck because of
the watchdog timeout errors on em0 when using nfs.
Mar 30 11:30:48 large kernel: em0: watchdog
Our test group uses a script that does 100 iterations of
a module load, then bring up all interfaces, and then
unload driver.
Depending on the system in anything from just a few
iterations to 20 or more, the system will panic.
Its doing an em_detach() which calls ether_ifdetach()
which goes to
On 4/6/07, Tai-hwa Liang [EMAIL PROTECTED] wrote:
On Thu, 5 Apr 2007, Jack Vogel wrote:
Our test group uses a script that does 100 iterations of
a module load, then bring up all interfaces, and then
unload driver.
Depending on the system in anything from just a few
iterations to 20 or more
I am hoping someone here who has more familiarity with the ACPI
code can enlighten me
I have an internal bug filed complaining that FreeBSD disables
wake-on-lan on the hardware. This means that if you boot, say,
Linux, even Knoppix as a quickie, and then shutdown, if the
hardware supports
On 4/11/07, Anne Marcel Roorda [EMAIL PROTECTED] wrote:
In message [EMAIL PROTECTED], Kimi
Ostro writes:
On 10/04/07, Jack Vogel [EMAIL PROTECTED] wrote:
I am hoping someone here who has more familiarity with the ACPI
code can enlighten me
I have an internal bug filed complaining
On 4/17/07, Henrik Brix Andersen [EMAIL PROTECTED] wrote:
Hi,
On Mon, Jan 22, 2007 at 10:30:48AM -0800, Jack Vogel wrote:
Acknowledge... I can do better than that, I have a fix for this problem, and
its not temporary. Here is the code change (not a patch, I'm very busy),
its
fast processor and on a gigE network
you'll probably see 8-9MByte/sec via SSH while 60-70MByte/sec via FTP.
That's the only difference I can think of.
The watchdog resets I can't explain; Jack Vogel should be able to assist
with that. But it sounds like the resets only happen under very high
On 4/20/07, Sven Willenberger [EMAIL PROTECTED] wrote:
On Fri, 2007-04-20 at 10:17 -0700, Jack Vogel wrote:
On 4/20/07, Jeremy Chadwick [EMAIL PROTECTED] wrote:
On Fri, Apr 20, 2007 at 11:51:56AM -0400, Sven Willenberger wrote:
Having done more diagnostics I have found out it is not CARP
On 4/20/07, Brian McCann [EMAIL PROTECTED] wrote:
On 4/20/07, Jack Vogel [EMAIL PROTECTED] wrote:
On 4/20/07, Sven Willenberger [EMAIL PROTECTED] wrote:
On Fri, 2007-04-20 at 10:17 -0700, Jack Vogel wrote:
On 4/20/07, Jeremy Chadwick [EMAIL PROTECTED] wrote:
On Fri, Apr 20, 2007 at 11
On 12/22/05, Gleb Smirnoff [EMAIL PROTECTED] wrote:
On Thu, Dec 22, 2005 at 12:37:53PM +0200, Danny Braniss wrote:
D On Thu, Dec 22, 2005 at 12:24:42PM +0200, Danny Braniss wrote:
D D
D D Server listening on TCP port 5001
D D
On 12/22/05, Danny Braniss [EMAIL PROTECTED] wrote:
iperf -c host
i'm begining to believe that the problem is elsewhere, i just put in
an ethernet nic in a PCI-X/Express slot, and the performance is similar, bad.
danny
Hmm, not some silly like getting set to half duplex? :)
Jack
On 2/6/06, Stephen Montgomery-Smith [EMAIL PROTECTED] wrote:
Jon Holstrom wrote:
any one know the date to get 5.4 stable ?
i am not able to find the date to CVsup 5.4 stable
as 5.5 is vary slow is to buggy
You might try stable-6.x, which in my opinion is really fine. My sense
is that
On 2/8/06, Christopher Arnold [EMAIL PROTECTED] wrote:
Hi,
does anyone have any info on how to disable the watchdog timer on an intel
serverboard model SE7501WV2?
I have found the userland application to disable the watchdog in the ICH
but that dosnt help much when i cant even get 6.0
On 3/16/06, Yuriy N. Shkandybin [EMAIL PROTECTED] wrote:
Hello
I have 2 freebsd servers connected by dedicated wire via em interfaces.
systems = 6.1-PRERELEASE #0: Tue Mar 14 11:58:23 MSK 2006
1st)
man em says
MTU size for Jumbo Frames is 16114 and i'm sure i've setup this on freebsd-5
1 - 100 of 339 matches
Mail list logo
