From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
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: Wed, 6 Sep 2006 22:47:37 +0200 [thread overview]
Message-ID: <200609062247.38169.rjw@sisk.pl> (raw)
In-Reply-To: <20060906104205.GE4987@atrey.karlin.mff.cuni.cz>
Hi,
On Wednesday, 6 September 2006 12:42, Pavel Machek wrote:
> Hi!
>
> > Now, the output of /proc/interrupts with everything loaded is
> >
> > CPU0 CPU1
> > 0: 511683 0 local-APIC-edge timer
> > 1: 6164 0 IO-APIC-edge i8042
> > 8: 0 0 IO-APIC-edge rtc
> > 12: 148 0 IO-APIC-edge i8042
> > 14: 18053 0 IO-APIC-edge ide0
> > 169: 140 0 IO-APIC-level acpi
> > 177: 4 0 IO-APIC-level yenta, ohci1394, sdhci:slot0
> > 217: 48306 0 IO-APIC-level libata, HDA Intel
> > 225: 22528 0 IO-APIC-level ehci_hcd:usb1, ohci_hcd:usb2, ohci_hcd:usb3
> > 233: 30024 0 IO-APIC-level eth0
> > NMI: 682 1125
> > LOC: 511687 511654
> > ERR: 0
> > MIS: 0
> >
> > so it looks like the problems are related to the drivers of interrupt vectors
> > above 14. However, powernow_k8 doesn't seem to fit.
>
> Its possible that pn_k8 has some separate problem...
>
> > 3) when it breaks, the kernel reports:
> >
> > sd 0:0:0:0 SCSI error, return code = 0x00070000
> > end_request: I/O error, dev sda, sector <sector_number>
> > lost page write due to I/O error on sda
> >
> > for each sector that is attempted to be read from/written to. Interestingly
> > enough, when this happens, the other devices seem to work (eg. the tg3 driver
> > evidently works).
>
> That actually points to interrupt problems.
>
> > I'm attaching the output of dmesg after a fresh boot (I think I'll create a
> > bugzilla entry and put all of the information in there).
>
> Yes please. Big question is who to assign it to...
Actually, I won't for now, because there's some progress. :-)
Namely, on a non-preemptible 2.6.18-rc5-mm1 the only module that causes
problems is snd_hda_intel. Unfortunately I can't unload it before suspend,
because the kernel oopses on every attempt to do so, but I'll report this
in a separate thread.
I'll experiment with the preemptible kernel when the snd_hda_intel issue gets
resolved.
Greetings,
Rafael
--
You never change things by fighting the existing reality.
R. Buckminster Fuller
next prev parent reply other threads:[~2006-09-06 20:44 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
2006-09-05 11:38 ` Rafael J. Wysocki
2006-09-06 10:42 ` Pavel Machek
2006-09-06 20:47 ` Rafael J. Wysocki [this message]
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=200609062247.38169.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-acpi@vger.kernel.org \
--cc=pavel@ucw.cz \
/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