In case anyone else runs into this problem, here it is for the archives.
FreeBSD 8.3, AMD64 (Actually, RELENG_8 as of March 2012)
I upgraded my home server to an Intel DQ67SW motherboard (hardware
version AAG12527-309). I used a bge PCI-E nic in the 1x slot which
caused an interrupt storm issue
On Sat, 7 Jan 2012 13:17:01 +0100
Bas Smeelen wrote:
> Hi all,
>
> After updating the sources to 9.0-STABLE and building a custom kernel
> I get a interrupt storm on irq10, from messages I get that different
> devices use irq10. It starts after loading ums0 and wlan0 and ath0
&
Hi all,
After updating the sources to 9.0-STABLE and building a custom kernel I
get a interrupt storm on irq10, from messages I get that different devices use
irq10.
It starts after loading ums0 and wlan0 and ath0 times out then.
Rebuilding the GENERIC kernel en booting does not give this
Hello All,
I have a server running FreeBSD 8.2-RC1 with a 3ware 9650 24ports
controller. Every now and then I am seeing the interrupt storm
message. I have increased the following according to the list:
hw.intr_storm_threshold=4000 but it still happens. Any advice?
interrupt storm detected on
I'm having the same issue. It's FreeBSD on a Nokia530 Firewall. The message
that keeps repeating over and over is "interrupt storm detected on "irq12:";
throttling interrupt source".
Here's the vmstat -i
interrupt
On Wed, May 27, 2009 at 09:30:19PM +0200, Wojciech Puchar wrote:
>
> I'm not telling that you are wrong that cable produced this, but i
> can't find any explanation for that.
One two-port controller card, two drives, two cables. Interrupt storms
move from one port to the other with the suspect ca
the other drive on ad6 worked. Thought the card was
bad but decided to try swapping cables which fixed ad4 and broke ad6.
Ergo, bad cable.
anyway very strange controller reaction to that case. i can hardly believe
the way cable have to be broken to produce interrupt storm.
maybe this way
errupt sources that interrupt handlers do
not fully support. So the interrupt is not being serviced and is
repeatedly being invoked.
Probably PCI doesn't behave the same as much simpler embedded hardware
that I am used to, but the above is what an interrupt storm looks like
on simple embedded ha
the cardbus slot, I
see messages regarding "interrupt storm detected throttling interrupt
source". This did not occur prior to adding the wireless adapter. If I
insert the wireless adapter after bootup, I don't see the messages on the
console or as dmesg output. Otherwise, the ada
tely evident how to do that.
For the archives, in case the referenced page goes away in the
future, it suggests adding
options KDB
options KDB_UNATTENDED
options DDB
to the kernel. This is reported to have caused an interrupt
storm, involving an at
PerryH-2 wrote:
>
> There are no USB devices connected. I think those must actually
> be atapci1 interrupts, since irq9 is where dmesg reported it.
>
I think this could be related to previous issues on same topic. I don't
recall the thread titles, but the solution is located here:
http://con
"Paul B. Mahol" wrote:
> On 5/10/09, per...@pluto.rain.com wrote:
...
> >> >> > interrupt storm detected on "irq9:"; throttling interrupt source
> >> >> > interrupt storm detected on "irq9:"; throttling interrupt sourc
On 5/10/09, per...@pluto.rain.com wrote:
> "Paul B. Mahol" wrote:
>> On 5/9/09, per...@pluto.rain.com wrote:
>> > "Paul B. Mahol" wrote:
>> >> On 5/8/09, per...@pluto.rain.com wrote:
>> >> > What, exactly, is an "int
"Paul B. Mahol" wrote:
> On 5/9/09, per...@pluto.rain.com wrote:
> > "Paul B. Mahol" wrote:
> >> On 5/8/09, per...@pluto.rain.com wrote:
> >> > What, exactly, is an "interrupt storm", and how do I fix it?
> > ...
> &g
On 5/9/09, per...@pluto.rain.com wrote:
> "Paul B. Mahol" wrote:
>> On 5/8/09, per...@pluto.rain.com wrote:
>> > What, exactly, is an "interrupt storm", and how do I fix it?
> ...
>> > interrupt storm detected on "irq9:"; throttli
"Paul B. Mahol" wrote:
> On 5/8/09, per...@pluto.rain.com wrote:
> > What, exactly, is an "interrupt storm", and how do I fix it?
...
> > interrupt storm detected on "irq9:"; throttling interrupt source
> > interrupt storm detected on &
On 5/8/09, per...@pluto.rain.com wrote:
> What, exactly, is an "interrupt storm", and how do I fix it?
>
> I have added a 64GB Patriot flash drive to a 7.0 system, but it does
> not seem to be working properly. Pertinent parts of dmesg.boot:
>
> FreeBSD 7.0-RELEASE
What, exactly, is an "interrupt storm", and how do I fix it?
I have added a 64GB Patriot flash drive to a 7.0 system, but it does
not seem to be working properly. Pertinent parts of dmesg.boot:
FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008
r...@logan.cse.buffalo.edu:/u
gt;> > From: nazir <[EMAIL PROTECTED]>
> >> > Subject: Interrupt storm detected on "irq10:"; throttling interrupt
> >> > source
> >> > To: freebsd-questions@freebsd.org
> >> > Date: Wednesday, October 15, 2008, 8:44 PM
> >>
On Thu, Oct 16, 2008 at 12:20 PM, Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
> On Wed, Oct 15, 2008 at 06:17:56PM -0700, mdh wrote:
>> --- On Wed, 10/15/08, nazir <[EMAIL PROTECTED]> wrote:
>> > From: nazir <[EMAIL PROTECTED]>
>> > Subject: Int
On Wed, Oct 15, 2008 at 06:17:56PM -0700, mdh wrote:
> --- On Wed, 10/15/08, nazir <[EMAIL PROTECTED]> wrote:
> > From: nazir <[EMAIL PROTECTED]>
> > Subject: Interrupt storm detected on "irq10:"; throttling interrupt source
> > To: freebsd-questions@
--- On Wed, 10/15/08, nazir <[EMAIL PROTECTED]> wrote:
> From: nazir <[EMAIL PROTECTED]>
> Subject: Interrupt storm detected on "irq10:"; throttling interrupt source
> To: freebsd-questions@freebsd.org
> Date: Wednesday, October 15, 2008, 8:44 PM
> Hi,
>
Hi,
I'm getting these on my HP-DL165 AMD Quad Qore
interrupt storm detected on "irq10:"; throttling interrupt source
interrupt storm detected on "irq10:"; throttling interrupt source
interrupt storm detected on "irq10:"; throttling interrupt source
On Wednesday 17 September 2008 05:17:27 pm John Baldwin wrote:
> On Wednesday 17 September 2008 11:00:24 am Scott Gasch wrote:
> > You're right: atapci1, atapci2, fwohci0 and uhci4 are all sharing the same
> > irq (19) while irqs 20, 21, 22 at least seem completely unused. Here's a
> > dumb questi
On Wednesday 17 September 2008 11:00:24 am Scott Gasch wrote:
> You're right: atapci1, atapci2, fwohci0 and uhci4 are all sharing the same
> irq (19) while irqs 20, 21, 22 at least seem completely unused. Here's a
> dumb question: how do I fix it? I tried setting "plug and play OS" in the
> BIOS
You're right: atapci1, atapci2, fwohci0 and uhci4 are all sharing the same
irq (19) while irqs 20, 21, 22 at least seem completely unused. Here's a
dumb question: how do I fix it? I tried setting "plug and play OS" in the
BIOS and then using device.hints to push different devices to different
irq
I'm getting,
interrupt storm detected on "irq10:"; throttling interrupt source
interrupt storm detected on "irq10:"; throttling interrupt source
interrupt storm detected on "irq10:"; throttling interrupt source
Slowly filling up my console. I've seen p
Dear Daniel,
I have moved two disks to motherboard controller, cvsuped sources to
7.0-STABLE and recompiled kernel and world. gmirrored disks (RAID-1).
Server worked good for about 6 hours, and than again,
interrupt storm detected on "irq22:"; throttling interrupt source
gans#
tional devices attached to the motherboard seem like not
having the problem. However most of my machines have at least
additional NIC device.
Please note that my machines does not crash even when there is an
interrupt storm. On the other hand, they suffer from some performance
problems :/
The
Dear Daniel,
Please tell me you had this storms only with 3ware 8006-2LP?
Because as I remember on MSI motherboard controller, I have no
problems with FreeBSD 6.2, but when I upgraded to FreeBSD 7.0 that
storms appeared, but not so often as with 3ware.
P.S. Maybe I have to ask them to update BIOS
Hello FreeBSD,
Saturday, June 14, 2008, 4:38:10 PM, you wrote:
> Be careful with hetzner.de hosting, here is their answer:
> The controller is compatible with the mainboard. With linux there are no
> problems. FreeBSD is also not officially supported by us (only
> Debian/Ubuntu/Suse).
Yea, I kn
Be careful with hetzner.de hosting, here is their answer:
The controller is compatible with the mainboard. With linux there are no
problems. FreeBSD is also not officially supported by us (only
Debian/Ubuntu/Suse).
Sorry, but it is not possible to buy a new model only for a few customers.
2008/6
Dear Daniel,
Yes, you're right:
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: MICRO-STAR INTERANTIONAL CO.,LTD
Product Name: MS-7368
Version: 1.0
Serial Number: To Be Filled By O.E.M.
UUID: Not Present
Wake-up Type: Power Switc
Hello Stanislav,
Thursday, June 12, 2008, 3:45:36 PM, you wrote:
> Hi, I have problem on FreeBSD 6.2, 7.0 with 3ware 8006-2LP RAID-1 controller:
Is it MSI mobo by any cnance?
I am seeing these interrupt storms on a few boxes (irq21 too, twe(4) or
fxp(4) attached to these) with an
Base Board Inf
kernel: twe0: [ITHREAD]
Jun 11 21:38:00 gans kernel: twe0: 2 ports, Firmware FE8S 1.05.00.068,
BIOS BE7X 1.08.00.048
/var/log/messages
Jun 10 14:51:36 gans kernel: interrupt storm detected on "irq21:";
throttling interrupt source
Jun 10 14:52:07 gans last message repeated 31 times
Jun 10 14
On Monday 14 April 2008 11:36:43 Jan Henrik Sylvester wrote:
> lysergius2001 wrote:
> > Recently installed 7.0-RELEASE on an i386 as upgrade from 6.3-RELEASE and
> > now have a continuous interrupt storm on IRQ17. This is a shared IRQ for
> > ath0 and echi0. Never s
> Subject: Re: Interrupt storm with 7.0
> On Sunday 13 April 2008 14:41:51 lysergius2001 wrote:
>
> > Recently installed 7.0-RELEASE on an i386 as upgrade from 6.3-RELEASE and
> > now have a continuous interrupt storm on IRQ17. This is a shared IRQ for
> > ath0 and ec
lysergius2001 wrote:
Recently installed 7.0-RELEASE on an i386 as upgrade from 6.3-RELEASE and
now have a continuous interrupt storm on IRQ17. This is a shared IRQ for
ath0 and echi0. Never saw this on 6.3??? Any suggestions?
Just another contribution to the collection of interrupt storms
On Sunday 13 April 2008 14:41:51 lysergius2001 wrote:
> Recently installed 7.0-RELEASE on an i386 as upgrade from 6.3-RELEASE and
> now have a continuous interrupt storm on IRQ17. This is a shared IRQ for
> ath0 and echi0. Never saw this on 6.3??? Any suggestions?
I've seen som
Hi
Recently installed 7.0-RELEASE on an i386 as upgrade from 6.3-RELEASE and
now have a continuous interrupt storm on IRQ17. This is a shared IRQ for
ath0 and echi0. Never saw this on 6.3??? Any suggestions?
Cheers
--
Lysergius says "Stay light and trust gr
8K RUN2 10:33 12.74%
idle: cpu2
Notice high load (0.94, often higher) and 45% interrupt.
If turn off ACPI (set hint.apic.0.disabled=1 in loader.conf), the
interrupt 'storm' ceases, but then I'm only running on one CPU.
ot of interrupts from ACPI. Load only settles down
to around 0.4 at complete idle with almost no services running. If I
turn off ACPI, obviously the interrupt 'storm' ceases, but then I
lose the multiple CPUs.
I don't have access to the machine(s) at the moment, but my
recollec
Hi,
I bought recently wireless PCMCIA card with atheros chip. When it`s not
connected to my access point (ap down, or I just brought the card up and
didn`t tell it to which SSID to connect) I often see
kernel: interrupt storm detected on "irq11:"; throttling interrupt source
and
the kernel with the cardbus driver disabled. This caused the
cardbus to disappear from the problem interrupt but the ohci driver was
still using irq19 and was having an interrupt storm. In the
compromised state of my computer it takes 48 hours to compile a kernel,
I don't have access to an
the
cardbus to disappear from the problem process in 'ps' but the ohci
driver was still using irq19 and was having an interrupt storm. In the
compromised state of my computer it takes 48 hours to compile a kernel,
I don't have access to another computer and I want to run with USB
support,
;stray IRQ 7 hack' will be
stepped on and return back to the official FBSD version. You will
have to reapply this hack.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Charles
Howse
Sent: Tuesday, May 23, 2006 10:14 AM
To: FreeBSD Questions
Subject: Best P
Charles Howse <[EMAIL PROTECTED]> wrote:
FreeBSD 6.1-RELEASE, cups-1.1.23.0_1, HP 1100 LaserJet
I've found quite a bit of information about how to deal with:
"Interrupt storm detected in "irq7:"; throttling interrupt source"
Problem is, it's a little con
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Charles
Howse
Sent: Tuesday, May 23, 2006 10:14 AM
To: FreeBSD Questions
Subject: Best Practices - interrupt storm
Hi,
FreeBSD 6.1-RELEASE, cups-1.1.23.0_1, HP 1100 LaserJet
I've found quite a bit of inf
Charles Howse <[EMAIL PROTECTED]> wrote:
> FreeBSD 6.1-RELEASE, cups-1.1.23.0_1, HP 1100 LaserJet
>
> I've found quite a bit of information about how to deal with:
> "Interrupt storm detected in "irq7:"; throttling interrupt source"
>
> Probl
Hi,
FreeBSD 6.1-RELEASE, cups-1.1.23.0_1, HP 1100 LaserJet
I've found quite a bit of information about how to deal with:
"Interrupt storm detected in "irq7:"; throttling interrupt source"
Problem is, it's a little confusing.
From what I've gathered, the o
Mark Busby wrote:
> Checking /var/log/messages after loading snd_emu10k1, I see the following.
> muz kernel: pcm1: port 0xd800-0xd81f irq 4 at device 9.0
> on pci0
> muz kernel: Interrupt storm detected on "irq4: atapci0"; throttling interrupt
> source
> muz
Checking /var/log/messages after loading snd_emu10k1, I see the following.
muz kernel: pcm1: port 0xd800-0xd81f irq 4 at device 9.0
on pci0
muz kernel: Interrupt storm detected on "irq4: atapci0"; throttling interrupt
source
muz kernel: pcm1:
muz kernel: emujoy0: detached
U
Seems like the issue was in part to partially failing hardware
between the drive and the controller card or a bad SCSI cable. Amusing.
-Garrett
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
T
Garrett Cooper wrote:
[ ... ]
> Interrupt storm detected on "irq11: ahc0"; throttling interrupt source
> ahc0: PCI error Interrupt at seqaddr = 0x9
> ach0: Data Parity Error Detected during address or write data phase
>
> Any ideas what this means?
> ahc0 is
This is a new error I've seen from FreeBSD. Was displayed on ttyv0
right after I started playing some music on the a remote machine from
the disk shared via NFS:
Interrupt storm detected on "irq11: ahc0"; throttling interrupt source
ahc0: PCI error Interrupt at seqaddr =
of interrupts; this is aparently caused by the 'snd_ich.ko' somehow
because during unload it says:
# kldunload snd_ich
Interrupt storm detected on "irq11: cbb1 pcm0+++"; throttling interrupt source
pcm0: detached
# kldload snd_ich
pcm0: port 0x1800-0x187f,0x1c00-0x1cff ir
You sir, are a genius. Fixed
John
On Aug 27, 2005, at 6:42 AM, Nicklas B. Westerlund wrote:
John Straiton wrote:
Hello,
I am attempting to install 5.4R on a brand new Dell PowerEdge 1850
machine. The installation goes perfectly however after the reboot, I
am unable to log into the machine
This may be getting a bit Off Topic, but I always find it annoying when
archive thread peter out without any conclusion...
Nicklas B. Westerlund wrote:
Alex Zbyslaw wrote:
What version of FreeBSD? AFAIU, FreeBSD only supports one console
keyboard, so if you plug in ukbd1 and make it the
Alex Zbyslaw wrote:
>
> What version of FreeBSD? AFAIU, FreeBSD only supports one console
> keyboard, so if you plug in ukbd1 and make it the console, the DRAC on
> ukbd0 shouldn't work. I'm sure I tried this and that it didn't work,
> but I'd be happy to be wrong. Are you sure that both your D
Nicklas B. Westerlund wrote:
Alex Zbyslaw wrote:
But if you do that, then I believe you will not be able to use the
DRAC as a remote console because your virtual keyboard won't work.
(not without changing to the ukbd0 from your real keyboard, which
pretty much defeats the point of the virtu
Alex Zbyslaw wrote:
>
>
> But if you do that, then I believe you will not be able to use the
> DRAC as a remote console because your virtual keyboard won't work.
> (not without changing to the ukbd0 from your real keyboard, which
> pretty much defeats the point of the virtual keyboard i.e. using i
Nicklas B. Westerlund wrote:
John Straiton wrote:
Hello,
I am attempting to install 5.4R on a brand new Dell PowerEdge 1850
machine. The installation goes perfectly however after the reboot, I
am unable to log into the machine (or in this case, create the
entropy salt)
John,
Le
John Straiton wrote:
> Hello,
>
> I am attempting to install 5.4R on a brand new Dell PowerEdge 1850
> machine. The installation goes perfectly however after the reboot, I
> am unable to log into the machine (or in this case, create the
> entropy salt)
John,
Let me take a quick guess.. You'v
John Straiton <[EMAIL PROTECTED]> [2005-08-26 15:25:40 -0400]:
>> While not a solution, I got this to go away by disabling the USB
>> ports on the system in the BIOS. I only mention it because it's the
>> only other "new" behaviour I'm seeing on this machine versus the
>> other boxes I maintain
* John Straiton <[EMAIL PROTECTED]> [2005-08-26 15:25:40 -0400]:
> While not a solution, I got this to go away by disabling the USB
> ports on the system in the BIOS. I only mention it because it's the
> only other "new" behaviour I'm seeing on this machine versus the
> other boxes I maintain.
Bad
just about the "local package" time of boot when I start
seeing
Interrupt storm detected on "irq18: uhci"; throttling interrupt source
While not a solution, I got this to go away by disabling the USB
ports on the system in the BIOS. I only mention it because it's the
o
Kostas Blekos wrote:
Hi,
In some cases, when two audio events coincide (usually in gaim),
I get the following message:
Interrupt storm detected on "irq9: pcm0 uhci2"; throttling interrupt source
and then there is a continuous noise that I can not stop in anyway.
Does anybody kn
Hi,
In some cases, when two audio events coincide (usually in gaim),
I get the following message:
Interrupt storm detected on "irq9: pcm0 uhci2"; throttling interrupt source
and then there is a continuous noise that I can not stop in anyway.
Does anybody knows how to resolve this (
Dear fellows,
I have a Compaq presario 1230 laptop here!
FreeBSD 4.11
Installs fine but:
a) USB port doesn't work
b) touchpad doesn't work
c) /dev/psm0 cannot be found in /dev
FreeBSD 5.4 and 5.3
---
Installs fine but:
a) USB port works fine
b) touchpad doesn't work
Daniel
I wonder if you can mount a CD with a GENERIC kernel?
I also wonder if you can avoid the "interrupt storm" with your custom kernel
but by disabling atapi dma? (hw.ata.atapi_dma="0" in /boot/loader.conf)
If this kernel boots, can you mount a CD?
If you get some fre
Hello,
attached you will find a copy of my custom kernel
config which did work without any issue under FreeBSD
5.2.1. As outlined earlier if using this config on
FreeBSD 5.3-RELEASE I am getting an interrupt
storm while booting the system.
The following hardware configuration *won't* cau
t;
>
> --- On Fri 01/28, Daniel S. Haischt < [EMAIL PROTECTED] >
> wrote: From: Daniel S. Haischt [mailto: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Cc: freebsd-questions@freebsd.org
> Date: Fri, 28 Jan 2005 14:37:21 +0100
> Subject: Re: 5.3 interrupt storm (ata
devicefirewire# FireWire bus code
+#devicesbp # SCSI over FireWire (Requires scbus
and da)
+#devicefwe # Ethernet over FireWire (non-standard!)
--
Randall D. DuCharme (Radio AD5GB)
Powered by FreeBSD!
The Power to Serve
On 01/28/05 08:38:14, Daniel S. Haischt wrote:
oops, did forget the tixt file ...
Daniel S. Haischt schrieb:
I don't know whether this is related to your issue,
but on one of my boxes I am also getting an interrupt
storm with atapicam enabled.
On FreeBSD 5.2.1 I did not experience any inte
e:
From: Olivier Certner [mailto: [EMAIL PROTECTED]
To: freebsd-questions@freebsd.org
Date: Fri, 28 Jan 2005 10:05:30 +0100
Subject: Re: 5.3 interrupt storm (atapicam) and I/O error
Hi, Could you give a look at my post dated 04/01/2005 entitled "Freeze
with CAM (using KsCD)"? Maybe we have
s@freebsd.org
Date: Fri, 28 Jan 2005 14:37:21 +0100
Subject: Re: 5.3 interrupt storm (atapicam) and I/O error
I don't know whether this is related to your issue,but on one of my boxes I
am also getting an interruptstorm with atapicam enabled.On FreeBSD
5.2.1 I did not experience any inter
To: freebsd-questions@freebsd.org
Date: Fri, 28 Jan 2005 10:05:30 +0100
Subject: Re: 5.3 interrupt storm (atapicam) and I/O error
Hi, Could you give a look at my post dated 04/01/2005 entitled "Freeze
with CAM (using KsCD)"? Maybe we have fallen on the same kind of bug
concerning atapi
oops, did forget the tixt file ...
Daniel S. Haischt schrieb:
I don't know whether this is related to your issue,
but on one of my boxes I am also getting an interrupt
storm with atapicam enabled.
On FreeBSD 5.2.1 I did not experience any interrupt
storm issues, even if using the same har
I don't know whether this is related to your issue,
but on one of my boxes I am also getting an interrupt
storm with atapicam enabled.
On FreeBSD 5.2.1 I did not experience any interrupt
storm issues, even if using the same hardware configuration.
Have a look at the attached text file
Hi,
Could you give a look at my post dated 04/01/2005 entitled "Freeze with CAM
(using KsCD)"? Maybe we have fallen on the same kind of bug concerning
atapicam.
If you have KDE, maybe you should try to reproduce the problem I had. I've no
time to test your scenario (the one with the EIDE dr
0 0C 00
status: 0x0 (GOOD STATUS)
resid: 24576
So I thought I'd try enabling atapicam and trying to use my EIDE CD drive but
the system hangs on boot with a message about an "interrupt storm" (throttling
input).
I tried to disable the 'atapicd' device but it didn't
bd0: irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
pmtimer0 on isa0
orm0: at iomem 0xd4000-0xd57ff,0xc-0xca7ff on isa0
sc0: at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: at port 0x3c0-0x3df iomem 0xa0000-0xb on
isa0
Timecounters tick every 1
lf powered
...
Interrupt storm detected on "irq11: ohci0"; throttling interrupt
source
What can I do to get rid of ALL USB support on this 5.3 system as I
dont use it and dont want these 'storms' of interrupts!
thanks in advance!
If it is not in the kernel see if the module is bein
l see this:
ohci0: at device 15.2 on pci0
ohci0: [GIANT-LOCKED]
usb0: OHCI version 1.0, legacy support
usb0: on ohci0
usb0: USB revision 1.0
uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
...
Interrupt storm detected on &qu
in the
computer's bios to IRQ 15. I additionally included
the above device hint in the file /boot/device.hints.
Tho - During the boot process I am still getting:
ohci0: mem 0xe400-0xe4000fff irq 11 at
device 1.2 on pci0
Which finally leads to the same interrupt storm on
"irq11:
Hello,
Lowell Gilbert schrieb:
"Daniel S. Haischt" <[EMAIL PROTECTED]> writes:
I am getting the following error message during
the boot process after having compiled a custom
kernel for FreeBSD 5.3-RELEASE-p1.
8<8<8<---8<-8<-
Int
"Daniel S. Haischt" <[EMAIL PROTECTED]> writes:
> I am getting the following error message during
> the boot process after having compiled a custom
> kernel for FreeBSD 5.3-RELEASE-p1.
>
> 8<8<----8<---8<-8<-
> Interrup
Hello,
I am getting the following error message during
the boot process after having compiled a custom
kernel for FreeBSD 5.3-RELEASE-p1.
8<8<8<---8<-8<-
Interrupt storm detected on "irq11: ohci+";
throtteling interrupt source
>8-
Enrique Ayesta Perojo wrote:
Anyone of you has had this problem? and if so, how did you solve?
i had the same problem with my printer, switching to polled mode did
help in my case:
lptcontrol -e lpt0
philipp
___
[EMAIL PROTECTED] mailing list
http://lists
Hello, i'm running FreeBSD 5.3 BETA-7 from October 13, everytime i try to
print something through my LPT printer i get the next message:
Interrupt storm detected on "irq 7: lpt0"; throttling interrupt source
and the printer gets extremely slow. I've googled a bit and ha
Hi,
I keep receiving messages about interrupt storm on irq 7 and my
device being throttled down on my -CURRENT machine.
The result is very slow printout.
Does anybody else see this, or is there a workaround for it?
Regards,
Uli.
P.S.I am using cups - perhaps this causes the problem
Hi!
My last cvsup of -CURRENT on monday seems to have messed up
printing somehow.
When I try to print (I am using cups) I receive this
message:
Interrupt storm detected on "irq7: lpt0"; throttling interrupt
source
Result is: Printing becomes very slow (about one minute for a
s
92 matches
Mail list logo
