From: Luca Tettamanti <kronos.it@gmail.com>
To: netdev@vger.kernel.org
Subject: [BUG] atl1 causes lockup/reboot on resume from STR
Date: Sat, 11 Sep 2010 15:12:09 +0200 [thread overview]
Message-ID: <20100911131209.GA3756@nb-core2.darkstar.lan> (raw)
Hello,
I'm having troubles with atl1 driver (notebook is an Asus F3Sa): during
the resume from S3 the machine either locks up or reboots.
However I was also able to get a (partial) stack trace involving
atl1_resume (the rest of the trace scrolled off screen) and a message
about a recursive fault, followed by a hard lock up.
If I rmmod atl1 before suspending, the machine comes back fine; I don't
known whether this is a regression or not, until recently the radeon
driver didn't survive S3 so I didn't even try suspending to RAM...
I'm currently running -git current (2.6.36-rc3-00396-gbe6200a), but I've
gone back till 2.6.32 without any succcess.
I've no idea on how to debug this, the machine does not have a serial
port (and netconsole obviously does not help)... help :)
Luca
next reply other threads:[~2010-09-11 13:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-11 13:12 Luca Tettamanti [this message]
2010-09-11 20:47 ` [BUG] atl1 causes lockup/reboot on resume from STR Jarek Poplawski
2010-09-14 13:59 ` Luca Tettamanti
2010-09-14 14:22 ` Luca Tettamanti
2010-09-16 19:29 ` Luca Tettamanti
2010-09-16 19:29 ` [PATCH 1/2] atl1: fix resume Luca Tettamanti
2010-09-16 20:13 ` Chris Snook
2010-09-16 21:13 ` [stable] " Greg KH
2010-09-17 4:47 ` David Miller
2010-09-16 19:29 ` [PATCH 2/2] atl1: zero out CMB and SBM in atl1_free_ring_resources Luca Tettamanti
2010-09-16 20:15 ` Chris Snook
[not found] ` <1284717403-12913-1-git-send-email-kronos.it@gmail.com>
2010-09-22 19:34 ` [PATCH 1/2] atl1: fix resume Luca Tettamanti
2010-09-22 20:23 ` David Miller
2010-09-22 20:41 ` Luca Tettamanti
2010-09-22 20:53 ` David Miller
2010-09-22 20:42 ` [PATCH 2/2] atl1: zero out CMB and SBM in atl1_free_ring_resources Luca Tettamanti
2010-09-22 20:53 ` David Miller
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=20100911131209.GA3756@nb-core2.darkstar.lan \
--to=kronos.it@gmail.com \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.