Re: How to debug complete kernel lock-ups

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Ray Lee
Date: Wednesday, October 31, 2007 - 2:28 pm

On 10/31/07, John Sigler <linux.kernel@free.fr> wrote:

Yes, if the voltage is applied (or lacking) at the right place.


This doesn't appear to be a case of the *board* crashing, but rather
the board taking the pci bus and related hardware on-motherboard down
with it. Once that's down, anything that you need that goes through
the bus (on a PC, that's pretty much everything), is inaccessible.


No, given the hardware guy's description, it's a power issue. Perhaps
when you're writing to a port, you're using more power on the card?
Four ports = 4 * the power draw. When the current load increases,
voltage drops, and if you underpower a chip, it's going to lose its
little head.


Yes, all signs point to it being a pure hardware issue. You may be
able to work around it in software by initializing a 'counting
semaphore' to 2 to manage the maximum concurrency, so that you'll
never write more than 2 ports at a time until the hardware guys figure
it out.

Ray
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
How to debug complete kernel lock-ups, John Sigler, (Tue Oct 23, 9:11 am)
Re: How to debug complete kernel lock-ups, John Sigler, (Wed Oct 24, 2:17 am)
Re: How to debug complete kernel lock-ups, Greg KH, (Wed Oct 24, 8:56 am)
Re: How to debug complete kernel lock-ups, Ray Lee, (Wed Oct 24, 9:19 am)
Re: How to debug complete kernel lock-ups, Grant Grundler, (Wed Oct 24, 9:06 pm)
Re: How to debug complete kernel lock-ups, John Sigler, (Wed Oct 31, 2:25 am)
Re: How to debug complete kernel lock-ups, Ray Lee, (Wed Oct 31, 2:28 pm)