From: "Rúben Fonseca" <krani1@0x82.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Linux Kernel Mailling List <linux-kernel@vger.kernel.org>
Subject: Re: libata [ata_piix] still no resume from S3 ?
Date: Sat, 14 Jul 2007 22:01:17 +0100 [thread overview]
Message-ID: <20070714210117.GA20723@0x82.com> (raw)
In-Reply-To: <469744DB.5070600@gmail.com>
On Fri, 13 Jul 2007, Tejun Heo wrote:
> Rúben Fonseca wrote:
> > Hi to all!
> >
> > I'm on Debian Sid with kernel 2.6.21 and I still can't resume my laptop
> > (Sony Vaio SZ2) from S3. Searched on the archive and it seems that SATA
> > drives are getting problems when used via the "new" libata. When the
> > laptop tries to resume, it can't access the hard drive anymore (the LED
> > never blinks), the filesystem is mounted read-only and of course, the
> > system hangs. I still can see a "Lost interrupt" apearing on my LCD when
> > it is resuming. Sometimes it is IRQ 22, other times it is IRQ 23.
> >
> > Is this still a know problem? Does 2.6.22 solve this already? If you
> > need more information about my environment, please ask :)
>
> Actually, 'lost interrupt' is from the "old" IDE driver. Care to give a
> shot at the new one?
Sorry, it was my mistake. Here's more info about the problem.
I had to copy "by hand" the trace, so I remove the hexadecimal parts
(if you need them, please ask i Will try to copy them too). For now
I just want to know if you can diagnose this problem, or need more info.
So here's the interesting (I think) part of the log after resume:
irq 23: nobody cared (try booting with the "irqpool" option)
__report_bad_irq
note_interrupt
handle_IRQ_event
handle_fasteoi_irq
do_IRQ
do_IRQ
irq_exit
smp_acpi_timer
common_interrupt
acpi_pm_read
getnstimeofday
ktime_get_ts
ktime_egt
tick_nohz_restart_sched_tick
cpu_idle
start_kernel
unkown_bootoption
=====
handlers:
(ata_interrupt [libata])
(tifm_7xx1_isr [tifm_7xx1])
Disabling IRQ #23
(...)
ATA: abnormal status 0x7F on port 0x000118cf
And hard drive never cames up.. have to hard reboot the machine..
Does it help?
Ruben
--
Will work for bandwidth
next prev parent reply other threads:[~2007-07-14 21:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 16:24 libata [ata_piix] still no resume from S3 ? Rúben Fonseca
2007-07-13 9:24 ` Tejun Heo
2007-07-14 21:01 ` Rúben Fonseca [this message]
2007-07-18 8:40 ` Tejun Heo
2007-07-19 9:20 ` Rúben Fonseca
2007-07-19 9:26 ` Tejun Heo
2007-07-19 15:04 ` Rúben Fonseca
2007-07-20 6:24 ` Tejun Heo
2007-07-21 11:36 ` Rúben Fonseca
2007-07-22 12:19 ` Tejun Heo
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=20070714210117.GA20723@0x82.com \
--to=krani1@0x82.com \
--cc=htejun@gmail.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox