Hello,
last month i reported a problem with interrupt storms in re(4). You
can find that report here:
http://lists.freebsd.org/pipermail/freebsd-stable/2008-October/046075.html
After that, i filled a bug report:
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/128287
Remko Lodder (CC'ed) sugges
I've communicated with a few people about this off-list, and it was sug-
gested I give the issue some wider exposure on this list in the hope of
having it addressed for 5.4-RELEASE. It may or not be related to the other
interrupt storm problems some people are seeing.
I have a number of system
Thanks to all who tried to help. I decided to move the discussion to acpi@
> >>> Ah, so they are all on the same bus. Yuck, performance is going to be
> >>> sucky. Bad Tyan, no cookie. That'll also explain the limited number of
> >>> interrupts available. I don't think there's anything we can d
>>> Ah, so they are all on the same bus. Yuck, performance is going to be
>>> sucky. Bad Tyan, no cookie. That'll also explain the limited number of
>>> interrupts available. I don't think there's anything we can do to help
>>> the situation, sadly.
>> I cannot affect the company equipment purch
>> Ah, so they are all on the same bus. Yuck, performance is going to be
>> sucky. Bad Tyan, no cookie. That'll also explain the limited number
>> of interrupts available. I don't think there's anything we can do to
>> help the situation, sadly.
>
> Buy a PCI-X SCSI/GigE card, and use that inst
On Wed, 9 Feb 2005, dima wrote:
> > Ah, so they are all on the same bus. Yuck, performance is going to be
> > sucky. Bad Tyan, no cookie. That'll also explain the limited number of
> > interrupts available. I don't think there's anything we can do to help
> > the situation, sadly.
> I cannot af
* Doug White ([EMAIL PROTECTED]) wrote:
> Ah, so they are all on the same bus. Yuck, performance is going to be
> sucky. Bad Tyan, no cookie. That'll also explain the limited number
> of interrupts available. I don't think there's anything we can do to
> help the situation, sadly.
Buy a PCI-X
I am preparing a new server for production use.
It contains 2 1000BaseTX NICs and 2 SCSI controllers.
The interrupt assignment performed by ACPI looks kinda strange:
irq24: bge0 ahd0
irq25: bge1 ahd1
How can I affect it? I mean I want all the devices use different IRQ
On Tue, 8 Feb 2005, dima wrote:
> > > I am preparing a new server for production use.
> > > It contains 2 1000BaseTX NICs and 2 SCSI controllers.
> > > The interrupt assignment performed by ACPI looks kinda strange:
> > > irq24: bge0 ahd0
> > > irq25: bge1 ahd1
> > > How can I affect it? I mean I
On Feb 8, 2005, at 8:20 AM, dima wrote:
The BIOS assigned all those devices IRQ10 and there is no way to
change the settings...
I have similar issues with a Tyan S2881. Very annoying, since many
interrupts are assigned to devices I don't need. I turned off
everything I could in the BIOS, too.
> > I am preparing a new server for production use.
> > It contains 2 1000BaseTX NICs and 2 SCSI controllers.
> > The interrupt assignment performed by ACPI looks kinda strange:
> > irq24: bge0 ahd0
> > irq25: bge1 ahd1
> > How can I affect it? I mean I want all the devices use different IRQ lines.
On Mon, 7 Feb 2005, dima wrote:
> I am preparing a new server for production use.
> It contains 2 1000BaseTX NICs and 2 SCSI controllers.
> The interrupt assignment performed by ACPI looks kinda strange:
> irq24: bge0 ahd0
> irq25: bge1 ahd1
> How can I affect it? I mean I want all the devices use
I am preparing a new server for production use.
It contains 2 1000BaseTX NICs and 2 SCSI controllers.
The interrupt assignment performed by ACPI looks kinda strange:
irq24: bge0 ahd0
irq25: bge1 ahd1
How can I affect it? I mean I want all the devices use different IRQ lines.
_
In message <[EMAIL PROTECTED]> John Hay writes:
: For those who care, the net4501 only maps the "video" area (0xa -
: 0xb) to the pci bus and not the rest of the hole below 1M. So
: 0xc to 0xe is not usable.
Yuck. If I had more energy for OLDCARD, I'd see how hard it would be
to
> In message <[EMAIL PROTECTED]> John
> Hay writes:
> : pci_cfgintr: BIOS 2.00 doesn't support interrupt routing
>
> I think this is an issue for sopris. However, if you comment out the
> version check in pci_cfgintr, it might work none the less.
I received a n
In message <[EMAIL PROTECTED]> John
Hay writes:
: pci_cfgintr: BIOS 2.00 doesn't support interrupt routing
I think this is an issue for sopris. However, if you comment out the
version check in pci_cfgintr, it might work none the less.
Warner
To Unsubscribe: send mail to [EMAI
16 matches
Mail list logo
