From: David Tolpin <dvd@davidashen.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] i/o error: wrenwrite
Date: Wed, 3 Mar 2004 16:19:55 +0400 [thread overview]
Message-ID: <200403031219.i23CJtpW099327@adat.davidashen.net> (raw)
In-Reply-To: <9bd008d2b84df83f80ad7c7c35867818@terzarima.net>
>
> round about here, say:
> if(status & Err)
> drive->error = inb(cmdport+Error);
>
> i suspect the error might happen much earlier, before it gets to
> generate an interrupt, but that should become apparent if you
> see no error output from that point. just a print() of the status
> might do. i suspect the controller ends up in a state where its
> registers don't look right to the driver, or indeed where the
> controller needs a bit of a whack from the driver after the power cycling,
> in which case it probably can't generate IO at all and it's (perhaps)
1) I have added print("status=%d\n",status)
which during normal boot displays status=81 occasionally.
During wrenwrite loop the point is not reached.
2) I then added a call to print("atainterrupt\n") at the top
of atainterrupt(). The result has been that the computer boots
with this kernel (after a few minutes of course) and does not
with kernel without that 'brake'.
Does it mean it is something about timeouts?
I'll continute investigating.
next prev parent reply other threads:[~2004-03-03 12:19 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 7:57 David Tolpin
2004-03-03 8:06 ` Fco.J.Ballesteros
2004-03-03 8:10 ` David Tolpin
2004-03-03 8:15 ` Fco.J.Ballesteros
2004-03-03 8:22 ` David Tolpin
2004-03-03 8:34 ` Fco.J.Ballesteros
2004-03-03 8:59 ` David Tolpin
2004-03-03 9:51 ` Geoff Collyer
2004-03-03 9:54 ` David Tolpin
2004-03-03 10:39 ` matt
2004-03-03 10:43 ` David Tolpin
2004-03-03 11:37 ` Charles Forsyth
2004-03-03 12:19 ` David Tolpin [this message]
2004-03-03 12:46 ` boyd, rounin
2004-03-03 12:44 ` boyd, rounin
2004-03-03 20:35 ` splite
2004-03-03 21:25 ` Geoff Collyer
2004-03-03 21:42 ` splite
2004-03-03 22:48 ` boyd, rounin
2004-03-03 9:55 ` Bruce Ellis
2004-03-03 10:00 ` David Tolpin
2004-03-03 10:47 ` Richard Miller
2004-03-03 11:19 ` David Tolpin
2004-03-03 11:25 ` lucio
2004-03-03 11:34 ` David Tolpin
2004-03-03 20:11 ` splite
2004-03-03 20:25 ` David Tolpin
2004-03-03 13:41 ` jmk
2004-03-03 13:45 ` David Tolpin
2004-03-03 13:58 ` C H Forsyth
2004-03-03 13:58 ` lucio
2004-03-03 14:07 ` C H Forsyth
2004-03-03 14:04 ` David Tolpin
2004-03-03 14:14 ` lucio
2004-03-03 14:23 ` jmk
2004-03-03 14:24 ` David Tolpin
2004-03-03 21:34 ` Exact Eios " David Tolpin
2004-03-03 14:41 ` Derek Fawcus
2004-03-03 9:15 ` Richard Miller
2004-03-03 9:18 ` David Tolpin
2004-03-03 12:31 ` boyd, rounin
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=200403031219.i23CJtpW099327@adat.davidashen.net \
--to=dvd@davidashen.net \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).