Jeremy Chadwick wrote:
I'm not really sure anyone will know how to fix this. Sometimes a BIOS
upgrade can fix such things, other times motherboard replacements are in
order.
I'll check the BIOS and see if I could do something with it.
If I enable POLLING, could that fix the problem?
--
Jeremy Chadwick wrote:
Simply put: I don't know. Based on the polling(4) man page, it might
improve things for you, but your ATA high interrupt rate problem will
still exist even if you use polling(4).
Okay. Thanks for taking time helping me :)
--
chs
On Tue, Nov 11, 2008 at 09:00:18AM +0100, Christer Solskogen wrote:
Jeremy Chadwick wrote:
I'm not really sure anyone will know how to fix this. Sometimes a BIOS
upgrade can fix such things, other times motherboard replacements are in
order.
I'll check the BIOS and see if I could
Uit een eerder bericht (10-11-2008 13:45):
Do anyone have a tips for how to workaround this or is the server just junk?
Got this problem a while ago as well. I found out with me it was hub
related. If I was downloading, my hub was displaying 100Mbit connection
(I wish it was :-)
Then I
Christer Solskogen wrote:
I have a server with a em interface. Whenever the server has a high load
(compiling world for instance) the network connectivity is lost.
The solution was to disable the onboard network card, and insert a pci-x
card instead.
--
chs
Jos Chrispijn([EMAIL PROTECTED])@2008.11.11 09:37:47 +0100:
Uit een eerder bericht (10-11-2008 13:45):
Do anyone have a tips for how to workaround this or is the server just junk?
Got this problem a while ago as well. I found out with me it was hub
related. If I was downloading, my hub
Christer Solskogen writes:
I have a server with a em interface. Whenever the server has a high load
(compiling world for instance) the network connectivity is lost.
dmesg tells me this:
em0: link state changed to DOWN
em0: link state changed to UP
em0: link state changed to DOWN
Robert Huff wrote:
Have you double-checked the hardware? (Includes the cable
connection.) The em driver has a very good reputation and others
- includong myself - use it under siilar load profiles with no
problems.
Yeah, I have. The error is replicated just by giving the machine
On Monday 10 November 2008 15:18:40 Christer Solskogen wrote:
Robert Huff wrote:
Have you double-checked the hardware? (Includes the cable
connection.) The em driver has a very good reputation and others
- includong myself - use it under siilar load profiles with no
problems.
At 06:45 AM 11/10/2008, Christer Solskogen wrote:
I have a server with a em interface. Whenever the server has a high load
(compiling world for instance) the network connectivity is lost.
dmesg tells me this:
em0: link state changed to DOWN
em0: link state changed to UP
em0: link state changed
Mel wrote:
Any shared interrupts? What does vmstat -i show under the load you describe?
irq1: atkbd0 531 0
irq6: fdc010 0
irq14: ata0 95 0
irq18: em0 atapci1 1198845
On Monday 10 November 2008 15:44:59 Christer Solskogen wrote:
irq18: em0 atapci1 1198845 4
Since disk and network card share the same IRQ, does the problem occur if you
generate a similar load, without using disk IO? Like, put a big file on a
memory disk and bzip it.
On Mon, Nov 10, 2008 at 01:45:44PM +0100, Christer Solskogen wrote:
I have a server with a em interface. Whenever the server has a high load
(compiling world for instance) the network connectivity is lost.
dmesg tells me this:
em0: link state changed to DOWN
em0: link state changed to UP
Christer Solskogen([EMAIL PROTECTED])@2008.11.10 13:45:44 +0100:
I have a server with a em interface. Whenever the server has a high load
(compiling world for instance) the network connectivity is lost.
I have a problem where the whole machine becomes unresponsive on
sustained disk IO every few
Jeremy Chadwick wrote:
Can you provide dmesg | grep em0 output? I'd like to see what version
of NIC this is.
No problem.
em0: Intel(R) PRO/1000 Network Connection Version - 6.7.3 port
0xbc00-0xbc1f mem 0xfc5e-0xfc5f irq 18 at device 1.0 on pci1
em0: Ethernet address:
I have a server with a em interface. Whenever the server has a high load
(compiling world for instance) the network connectivity is lost.
dmesg tells me this:
em0: link state changed to DOWN
em0: link state changed to UP
em0: link state changed to DOWN
em0: link state changed to UP
em0: link
em0: link state changed to DOWN
em0: link state changed to UP
em0: link state changed to DOWN
Have you double-checked the hardware? (Includes the cable
connection.) The em driver has a very good reputation and others
- includong myself - use it under siilar load profiles with no
i don't think it's interrupt sharing problems.
anyway - turn on MSI interrupts if your hardware can.
check if producing high load on atapci1 make problem worse or not.
On Mon, 10 Nov 2008, Christer Solskogen wrote:
Mel wrote:
Any shared interrupts? What does vmstat -i show under the load
On Mon, Nov 10, 2008 at 05:52:59PM +0100, Christer Solskogen wrote:
Jeremy Chadwick wrote:
Can you provide dmesg | grep em0 output? I'd like to see what version
of NIC this is.
No problem.
em0: Intel(R) PRO/1000 Network Connection Version - 6.7.3 port
0xbc00-0xbc1f mem
Jeremy Chadwick wrote:
Well shoot, that didn't tell me what I want. pciconv -lv, and look
for the em0 entry? (I need all the lines shown associated with it)
Here you go:
[EMAIL PROTECTED]:1:1:0: class=0x02 card=0x342f8086 chip=0x10758086 rev=0x00
hdr=0x00
vendor = 'Intel
Wojciech Puchar wrote:
i don't think it's interrupt sharing problems.
anyway - turn on MSI interrupts if your hardware can.
I dont seem so (unless i interpret the output of pciconf wrong:
[EMAIL PROTECTED] ~]# pciconf -lc
[EMAIL PROTECTED]:0:0:0: class=0x06 card=0x342f8086
On Tue, Nov 11, 2008 at 08:13:23AM +0100, Christer Solskogen wrote:
Jeremy Chadwick wrote:
Well shoot, that didn't tell me what I want. pciconv -lv, and look
for the em0 entry? (I need all the lines shown associated with it)
Here you go:
[EMAIL PROTECTED]:1:1:0: class=0x02
On Tuesday 11 November 2008 08:25:10 Christer Solskogen wrote:
During dd if=/dev/random of=bigfile bs=500k count=5 (about 200
seconds) made the network unresponsive again. Same symptom as I got when
running make buildworld.
And same command with of=/dev/null?
--
Mel
Problem with
23 matches
Mail list logo
