On Wed, 2005-11-23 at 21:52 -0700, Scott Long wrote:
[..]
> and if we don't EOI then we can't get any other interrupts. This scheme
> works fairly well for typical PC hardware, and these Intel chipsets seem
> to be the exception, albeit a popular one. One solution that is being
[..]
Yep, the wi
:You're seeing the same aliasing. Here's exactly what happens:
:irq64 generates an interrupt and the APIC routes it to the CPU.
:FreeBSD services the interrupt, masks irq64 in the APIC, and schedules
:the interrupt thread for em2. When that ithread runs, the driver
:will take action to turn off
Michael Vince wrote:
Kris Kennaway wrote:
This is Intels latest server chipset designs and Dell are putting that
chipset in all their servers.
Luckily I haven't not seen the problem on any of my Dell servers (as
long as I am looking at this right).
I just tried intel's latest em driver
Michael Vince wrote:
Scott Long wrote:
Michael Vince wrote:
Kris Kennaway wrote:
On Tue, Nov 22, 2005 at 08:54:49PM -0800, John Polstra wrote:
On 23-Nov-2005 Kris Kennaway wrote:
I am seeing the em driver undergoing an interrupt storm whenever the
amr driver receives interrupts. I
Scott Long wrote:
Michael Vince wrote:
Kris Kennaway wrote:
On Tue, Nov 22, 2005 at 08:54:49PM -0800, John Polstra wrote:
On 23-Nov-2005 Kris Kennaway wrote:
I am seeing the em driver undergoing an interrupt storm whenever the
amr driver receives interrupts. In this case I was runni
Mihail Balikov wrote:
try to enable kern.polling
sysctl -w kern.polling.enable=1
Polling solves specific problems, but isn't a good choice for
every situation.
Scott
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listin
On Thu, Nov 24, 2005 at 12:40:24PM +1100, Michael Vince wrote:
> chipset in all their servers.
> Luckily I haven't not seen the problem on any of my Dell servers (as
> long as I am looking at this right).
>
> This server has been running for a long time.
> vmstat -i
> interrupt
Michael Vince wrote:
Kris Kennaway wrote:
On Tue, Nov 22, 2005 at 08:54:49PM -0800, John Polstra wrote:
On 23-Nov-2005 Kris Kennaway wrote:
I am seeing the em driver undergoing an interrupt storm whenever the
amr driver receives interrupts. In this case I was running newfs on
the amr
Kris Kennaway wrote:
On Tue, Nov 22, 2005 at 08:54:49PM -0800, John Polstra wrote:
On 23-Nov-2005 Kris Kennaway wrote:
I am seeing the em driver undergoing an interrupt storm whenever the
amr driver receives interrupts. In this case I was running newfs on
the amr array and em0 was not
L PROTECTED]>
Sent: Wednesday, November 23, 2005 10:46 AM
Subject: Re: em interrupt storm
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Tue, Nov 22, 2005 at 08:54:49PM -0800, John Polstra wrote:
>
> On 23-Nov-2005 Kris Kennaway wrote:
> > I am seeing the em driver undergoing an interrupt storm whenever the
> > amr driver receives interrupts. In this case I was running newfs on
> > the amr array and em0 was not in use:
> >
> >
On 23-Nov-2005 Kris Kennaway wrote:
> I am seeing the em driver undergoing an interrupt storm whenever the
> amr driver receives interrupts. In this case I was running newfs on
> the amr array and em0 was not in use:
>
>28 root1 -68 -187 0K 8K CPU1 1 0:32 53.98% irq16: em
12 matches
Mail list logo
