From: Dragan Stancevic <visitor@valinux.com>
To: Andrey Savochkin <saw@saw.sw.com.sg>
Cc: Tom Murphy <freyason@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.0-test12-pre7 shutdowns and eepro100 woes
Date: Wed, 20 Dec 2000 14:28:28 -0800 [thread overview]
Message-ID: <20001220142828.B32335@valinux.com> (raw)
In-Reply-To: <20001211185219.28022.qmail@web2006.mail.yahoo.com> <20001212142846.A14979@saw.sw.com.sg>
In-Reply-To: <20001212142846.A14979@saw.sw.com.sg>; from Andrey Savochkin on Tue, Dec 12, 2000 at 02:28:46PM +0800
On Tue, Dec 12, 2000, Andrey Savochkin <saw@saw.sw.com.sg> wrote:
; To answer your question in short, yet, we hope to fix the problem sooner or
; later.
I added the print out of the message to see in what state was the card
being left after it was wedged.
The card seems to be locking up with undefined opcodes, atleast according to
my specs.
The command doesn't necessarly come from the driver, I'we done some
experimenting and it seems that sending the card an undefined opcode
will lock up the card with a different value in the command register.
I am still waiting for latest specs from intel, I wonder if the new
specs will define those values.
--
I knew I was alone, I was scared, it was getting dark and
it was a hardware problem.
-Dragan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-12-20 21:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-11 18:52 2.4.0-test12-pre7 shutdowns and eepro100 woes Tom Murphy
2000-12-12 6:28 ` Andrey Savochkin
2000-12-20 22:28 ` Dragan Stancevic [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20001220142828.B32335@valinux.com \
--to=visitor@valinux.com \
--cc=freyason@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=saw@saw.sw.com.sg \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox