public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux ACPI <linux-acpi@vger.kernel.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Problem with resuming ATI SATA on HPC nx6325
Date: Tue, 5 Sep 2006 08:24:50 +0200	[thread overview]
Message-ID: <20060905062438.GD1958@elf.ucw.cz> (raw)
In-Reply-To: <200609041332.19780.rjw@sisk.pl>

Hi!

> I've just installed SUSE 10.1 on a HPC 6325 notebook (x86_64, dual_core) with
> an ATI chipset.  It generally works just fine (well, except for some minor
> glitches), but I'm having problems with suspending it which seem to be ACPI
> related.
> 
> Namely, on the 2.6.18-rc5-mm1 kernel the hard drive is not accessible after
> a resume of device drivers (eg. in the resume-during-suspend phase of swsusp).
> On 2.6.18-rc5 swsusp works with the following drivers loaded:
> 
> cpufreq_ondemand
> powernow_k8
> freq_table
> af_packet
> ip6t_REJECT
> xt_tcpudp
> ipt_REJECT
> xt_state
> iptable_filter
> ip_conntrack
> nfnetlink
> ip_tables
> ip6table_filter
> ip6_tables
> x_tables
> ipv6
> ext3
> jbd
> fan
> thermal
> processor
> sg
> atiixp
> sata_sil
> libata
> ide_disk
> ide_core
> 
> but if ohci_hcd and ehci_hcd are loaded additionally, the SATA thing doesn't
> resume properly (if only one of ehci_hcd or ohci_hcd is loaded, it works).

So situation is:

2.6.18-rc5: works in any config

2.6.18-rc5-mm1: if ohci+ehci+sata are loaded, SATA breaks during
resume

, right? How does it breaks? Are interrupts shared between the two?

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2006-09-05  6:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-04 11:32 Problem with resuming ATI SATA on HPC nx6325 Rafael J. Wysocki
2006-09-05  6:24 ` Pavel Machek [this message]
2006-09-05 11:38   ` Rafael J. Wysocki
2006-09-06 10:42     ` Pavel Machek
2006-09-06 20:47       ` Rafael J. Wysocki
2006-09-06 21:12         ` Pavel Machek
2006-09-07  7:03           ` Rafael J. Wysocki
2006-09-07 10:34             ` Rafael J. Wysocki
2006-09-07 22:08               ` Pavel Machek
2006-09-07 22:22                 ` Rafael J. Wysocki
2006-09-08 14:14                   ` Rafael J. Wysocki
2006-09-08 15:49                   ` Pavel Machek
2006-09-08 23:27                     ` Rafael J. Wysocki
2006-09-10 16:01                   ` Martin Zuther
2006-09-10 18:31                   ` Yet another DSDL problem Martin Zuther
2006-09-11  8:05                     ` Sorry Martin Zuther
2006-09-10 18:55                   ` Yet another DSDL problem Martin Zuther
2006-09-10 19:37                   ` Yet another DSDT problem Martin Zuther
2006-09-10 20:16                   ` Martin Zuther
2006-09-10 20:19                   ` Martin Zuther
2006-09-10 20:43                   ` Martin Zuther

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=20060905062438.GD1958@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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