From: Sam Krasnik <genlogic@mediaone.net>
To: linux-kernel@vger.kernel.org
Subject: kernel lockup?
Date: Mon, 31 Dec 2001 12:24:33 -0500 [thread overview]
Message-ID: <3C309F51.9050908@mediaone.net> (raw)
*please cc the replies to me*
hello
i have been getting some (i thought) kernel lockups. only a hard reset would
help. originally i thought it was the emu10k1 sb live driver, and i read
that 2.4.7 didn't have the problem (i was using 2.4.8). i also tried using
alsa, which didn't work either.
however, after seeing it still happening, i am led to believe that it may
be some power management problem or not a kernel problem at all...
(in which case this mailing list is NOT where i should be posting,
sorry for the distraction if i am wrong). the lockup only happens after
extended periods of idle time (specifically in the morning after a night
of not using the computer). the sysrq works, so i guess it isn't a hard
lockup? if it is kernel...what then? if not...what could be the problem?
thx
--sam
next reply other threads:[~2001-12-31 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-31 17:24 Sam Krasnik [this message]
2002-01-01 10:37 ` kernel lockup? Alan Cox
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=3C309F51.9050908@mediaone.net \
--to=genlogic@mediaone.net \
--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