* PSI, Mike Smith <[EMAIL PROTECTED]> [011205 12:12] wrote:
> Hi all.
>
> Does anyone have ANY suggestions on how to determine where the
> kernel/program is when the system freezes??? Even hardware solutions,
> such as the infamous paperclip across two pins will do.
Ohh... the infamous paperclip trick...
That's what I used to debug the wi wireless driver.
* THIS DIAGRAM IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
* OUT OF THE USE OF THIS DIAGRAM, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
Ok, now..
What you do is fold a paperclip then use it to make the last
two pins of the ISA bus short:
here
vv
________________________________
| || || || || :: :: :: | [-] <- blow up diagram
| || || || || :: :: :: | [ ] make paperclip short
| || || || || :: :: :: | [ ] the last two terminals
| || || || || :: :: :: | [ ] that face each other
| || || || || :: :: :: | [ ]
| || || || || :: :: :: | [ ]
| || || || || | [ ]
| || || || || \_____/ | [ ]
| PCI slots |
| \________/ |
| ISA slots |
| |
| |
|________________________________|
Be warned, this doesn't work on all motherboards!
The one that I had that it didn't work on didn't have any damage
though.
--
-Alfred Perlstein [[EMAIL PROTECTED]]
'Instead of asking why a piece of software is using "1970s technology,"
start asking why software is ignoring 30 years of accumulated wisdom.'
http://www.morons.org/rants/gpl-harmful.php3
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
