linux-kernel - Re: Suspend and resume on ASUS Laptops

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20111203024317.GA5370@ellpspace.math.ualberta.ca>
Date:	Fri, 2 Dec 2011 19:43:17 -0700
From:	Michal Jaegermann <michal@...pspace.math.ualberta.ca>
To:	Alan Stern <stern@...land.harvard.edu>
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>,
	Oliver Neukum <oneukum@...e.de>,
	"Rafael J. Wysocki" <rjw@...k.pl>, linux-pm@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>,
	Len Brown <len.brown@...el.com>, Pavel Machek <pavel@....cz>,
	Greg Kroah-Hartman <gregkh@...e.de>
Subject: Re: Suspend and resume on ASUS Laptops

On Fri, Dec 02, 2011 at 10:43:30AM -0500, Alan Stern wrote:
> 
> It's possible that this problem is related to wakeup settings.  Have 
> you tried disabling wakeup for the EHCI controllers?

On my ASUS K52Jc these controllers are also reported "disabled".  This
is after switching to Fedora 16 with its 3.1.2-1 kernel.

After doing these updates I had also to add "ath ath9k" to my list of
SUSPEND_MODULES (which are removed and reinserted in these operations)
or otherwise I will loose my wireless connection on a resume and a
reboot after hibernate will silently die.  In logs I can find

 irq 17: nobody cared (try booting with the "irqpoll" option)
 Pid: 0, comm: swapper Not tainted 3.1.2-1.fc16.x86_64 #1
 Call Trace:
  <IRQ>  [<ffffffff810b2222>] __report_bad_irq+0x38/0xc3
  [<ffffffff810b24bc>] note_interrupt+0x176/0x1fa
  [<ffffffff810b0a0f>] handle_irq_event_percpu+0x15d/0x1a5
  [<ffffffff810b0a92>] handle_irq_event+0x3b/0x59
  [<ffffffff81078268>] ? sched_clock_cpu+0x42/0xc6
  [<ffffffff810b2c7c>] handle_fasteoi_irq+0x80/0xa4
  [<ffffffff81010af9>] handle_irq+0x88/0x8e
  [<ffffffff814c040d>] do_IRQ+0x4d/0xa5
  [<ffffffff814b756e>] common_interrupt+0x6e/0x6e
  <EOI>  [<ffffffff814b71ac>] ? _raw_spin_unlock_irqrestore+0x17/0x19
  [<ffffffff813a5cc3>] ? poll_idle+0x28/0x65
  [<ffffffff813a5cb6>] ? poll_idle+0x1b/0x65
  [<ffffffff813a5fe6>] cpuidle_idle_call+0xe8/0x182
  [<ffffffff8100e2e3>] cpu_idle+0xa4/0xe8
  [<ffffffff81494a8e>] rest_init+0x72/0x74
  [<ffffffff81b76b7d>] start_kernel+0x3ab/0x3b6
  [<ffffffff81b762c4>] x86_64_start_reservations+0xaf/0xb3
  [<ffffffff81b76140>] ? early_idt_handlers+0x140/0x140
  [<ffffffff81b763ca>] x86_64_start_kernel+0x102/0x111
 handlers:
 [<ffffffffa02c0d80>] ath_isr
 Disabling IRQ #17

These "irq 17: nobody cared" were happening before but I could get away
without touching ath and aht9k modules.

   Michal
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/