Tom Ivar Helbekkmo t...@hamartun.priv.no writes:
Your new wrapper doesn't grab the sc_intr_lock mutex, so it fails the
KASSERT in uhci_intr1(). I'll add the enter and exit calls to the
wrapper and try again -- after dinner. :)
I have it running, now, and the initial impression is that it
Tom Ivar Helbekkmo t...@hamartun.priv.no writes:
The uhci pins on the ioapics are chalking up a few interrupts, but not
many, and no bursts.
Still nothing bad happening, but I did reboot just now, and saw
something that I've observered a few times lately: when the machine was
just sufficiently
On Thu, Feb 12, 2015 at 09:36:52AM +0100, Joerg Sonnenberger wrote:
Well, let's try the first hack of keep uhci interrupts off and just poll
via timeout.
Let's not forget the second part in the header ;)
Joerg
Index: uhci.c
===
Joerg Sonnenberger jo...@britannica.bec.de writes:
Well, let's try the first hack of keep uhci interrupts off and just poll
via timeout.
Will try this in a few hours, when I'm back with the machine. It'll be
interesting to see what happens, not least because there's another
symptom that I
Hi,
Sorry for my silence on the aprint project. I was busy in the last
while, but I have more time to dedicate to it now.
Anyway, I am currently working on the first task, converting printf to
the appropriate aprint during autoconfiguration. Having read through
many files, I have found that
On Thu, Feb 12, 2015 at 07:52:10PM +0100, Tom Ivar Helbekkmo wrote:
Tom Ivar Helbekkmo t...@hamartun.priv.no writes:
The uhci pins on the ioapics are chalking up a few interrupts, but not
many, and no bursts.
Still nothing bad happening, but I did reboot just now, and saw
something that
Tom Ivar Helbekkmo t...@hamartun.priv.no writes:
Still nothing bad happening, but I did reboot just now, and saw
something that I've observered a few times lately: when the machine
was just sufficiently up that I could log in, 'vmstat -i' told me that
the ioapic pin for uhci2 had already
Tom Ivar Helbekkmo t...@hamartun.priv.no writes:
The machine has now been running for nine hours, doing a -j 2 system
build, and also running backups during the night -- with no incidents.
The interrupt counts, though, are up to 600 thousand on the uhci2 pin,
400 thousand on the uhci0 pin,
Joerg Sonnenberger jo...@britannica.bec.de writes:
Well, let's try the first hack of keep uhci interrupts off and just
poll via timeout.
Your new wrapper doesn't grab the sc_intr_lock mutex, so it fails the
KASSERT in uhci_intr1(). I'll add the enter and exit calls to the
wrapper and try
On Thu, Feb 12, 2015 at 05:02:28AM +0100, Tom Ivar Helbekkmo wrote:
Joerg Sonnenberger jo...@britannica.bec.de writes:
Can you add a counter to uhci.c line 1317? The question for me is
whether the device is creating interrupts without actually setting the
status to anything different or
10 matches
Mail list logo
