From: Mark Lord <liml@rtr.ca>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-ide@vger.kernel.org, torvalds@osdl.org
Subject: Re: [PATCH alt4 v2] libata resume fixes
Date: Sat, 27 May 2006 16:30:48 -0400 [thread overview]
Message-ID: <4478B6F8.1090608@rtr.ca> (raw)
In-Reply-To: <4478B312.5040901@garzik.org>
Jeff Garzik wrote:
> Jeff Garzik wrote:
>> This fixes a bug in alt4 v1, by eliminating the second ata_set_mode()
>> call, found in ata_device_resume().
>
> This seems to make my x86-64 box happier...
>
> Jeff
((second attempt at sending this -- first one seems
to have been blocked by something, probably due to
an attached .jpg screenshot))
With alt4_v2 applied, resume still fails,
but slightly differently from before.
This time, there's the initial blank-screen for 31 seconds,
then the backlight turns on and I can see the syslog scrolling
in the window where I left it, as before.
New, is that the disk activity LED is stuck-on,
and the error-recovery code is doing something
every 30 seconds or so.
Screenshot here temporarily: http://rtr.ca/libata1.jpg
Other than that, it's still dead -- disk I/O not working.
Can this patch be combined with Linus's one-liner
and still work on your machine?
Cheers
next prev parent reply other threads:[~2006-05-27 20:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-27 19:58 [PATCH alt4] libata resume fixes Jeff Garzik
2006-05-27 20:10 ` [PATCH alt4 v2] " Jeff Garzik
2006-05-27 20:14 ` Jeff Garzik
2006-05-27 20:30 ` Mark Lord [this message]
[not found] ` <4478B611.2030201@rtr.ca>
2006-05-27 20:32 ` Jeff Garzik
2006-05-27 20:41 ` Mark Lord
2006-05-27 20:56 ` Jeff Garzik
2006-05-27 21:00 ` Mark Lord
2006-05-27 21:06 ` Jeff Garzik
2006-05-27 21:09 ` Mark Lord
2006-05-27 21:14 ` Jeff Garzik
2006-05-27 20:13 ` [PATCH alt4] " Mark Lord
2006-05-27 20:52 ` [PATCH alt4 v3] " Jeff Garzik
2006-05-27 20:56 ` Mark Lord
2006-05-27 21:11 ` Jeff Garzik
2006-05-27 21:15 ` Mark Lord
2006-05-27 21:25 ` Jeff Garzik
2006-05-27 21:12 ` Mark Lord
2006-05-27 21:21 ` Jeff Garzik
2006-05-29 3:53 ` zhao, forrest
2006-05-29 5:25 ` Jeff Garzik
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=4478B6F8.1090608@rtr.ca \
--to=liml@rtr.ca \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=torvalds@osdl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.