From: Josh Rosenau <jrosenau@ku.edu>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: [LPPC] Random crashes on snooze
Date: Wed, 17 Mar 2004 11:19:53 -0600 [thread overview]
Message-ID: <20040317171953.GB3195@ku.edu> (raw)
In-Reply-To: <20040316230925.15bfe069.iweiny@acm.org>
So on Tue, Mar 16, 2004 at 11:09:25PM -0800, Ira Weiny was all like,
>I put some debug messages in the sleep code and I think it might have something
>to do with the awacs sound driver.
>
>>From /var/log/messages on a bad sleep:
>
>Mar 16 17:49:15 batwing2 kernel: IKW sleep 1 calling c03b5ff4 (c020cae0)
>Mar 16 17:49:15 batwing2 kernel: aty128fb: aty128_sleep_notify when 1 board c1ab1800
>Mar 16 17:49:16 batwing2 kernel: IKW sleep 1 accepted by c03b5ff4 (c020cae0)
>Mar 16 17:49:16 batwing2 kernel: IKW Sync disks
>Mar 16 17:49:16 batwing2 kernel: IKW sleep 2 calling c03868ec (c01d1b6c)
>Dec 31 20:53:02 batwing2 syslogd 1.4.1: restart.
>
>>From System.map
>c01d1b6c t awacs_sleep_notify
>
>But I don't know if there is something missing from the file because of course
>nothing can be written to the disk at this time... Does anyone have any other
>clues?
I've avoided crashes on sleep on my Lombard by always unloading the
sound module. It isn't elegant, but it works. One more data point.
--
Joshua Rosenau 1345 Jayhawk Boulevard/Dyche Hall
(785) 864-4159 Lawrence, KS 66045-7561
The struggling for knowledge has a pleasure in it like
that of wrestling with a fine woman. -- Lord Halifax
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-03-17 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-17 7:09 Random crashes on snooze Ira Weiny
2004-03-17 7:23 ` Benjamin Herrenschmidt
2004-03-17 18:00 ` Ira Weiny
2004-03-18 22:41 ` Ira Weiny
2004-03-17 17:19 ` Josh Rosenau [this message]
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=20040317171953.GB3195@ku.edu \
--to=jrosenau@ku.edu \
--cc=linuxppc-dev@lists.linuxppc.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).