linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rúben Fonseca" <krani1@0x82.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Linux Kernel Mailling List <linux-kernel@vger.kernel.org>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: libata [ata_piix] still no resume from S3 ?
Date: Thu, 19 Jul 2007 16:04:36 +0100	[thread overview]
Message-ID: <20070719150436.GA9006@0x82.com> (raw)
In-Reply-To: <469F2E4A.1020502@gmail.com>

On Thu, 19 Jul 2007, Tejun Heo wrote:

> Rúben Fonseca wrote:
> > On Wed, 18 Jul 2007, Tejun Heo wrote:
> > 
> >>> 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?
> >> Hmmm... That's 'nobody cared' during resume.  Please post the result of
> >> 'lspci -nnvvv'.
> > 
> > 09:04.2 Mass storage controller [0180]: Texas Instruments 5-in-1 Multimedia Card Reader (SD/MMC/MS/MS PRO/xD) [104c:803b]
> > 	Subsystem: Sony Corporation Unknown device [104d:81e6]
> > 	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> > 	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> > 	Latency: 57 (1750ns min, 1000ns max), Cache Line Size: 64 bytes
> > 	Interrupt: pin C routed to IRQ 23
> > 	Region 0: Memory at dc004000 (32-bit, non-prefetchable) [size=4K]
> > 	Capabilities: [44] Power Management version 2
> > 		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
> > 		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> 
> Does the problem still occur if you disable the card reader?

I wish I could disable this card reader. It is built in on the hardware,
and there are no drivers for Linux. There is no option on the BIOS to
disable the device. Is there any way (kernel parameters, magic program,
etc) to disable this device without opening my laptop to cut the wires?
:D

Ruben

-- 
Will work for bandwidth

  reply	other threads:[~2007-07-19 15:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070712162450.GA7132@0x82.com>
     [not found] ` <469744DB.5070600@gmail.com>
     [not found]   ` <20070714210117.GA20723@0x82.com>
2007-07-18  8:40     ` libata [ata_piix] still no resume from S3 ? 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 [this message]
2007-07-20  6:24             ` Tejun Heo
2007-07-21 11:36               ` Rúben Fonseca
2007-07-22 12:19                 ` Tejun Heo
2007-07-17 16:49 Rúben Fonseca

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=20070719150436.GA9006@0x82.com \
    --to=krani1@0x82.com \
    --cc=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).