From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Nicolas FR <nicolasfr@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sc3200 cpu + apm module kernel crash
Date: Sun, 05 Nov 2006 23:21:05 +0000 [thread overview]
Message-ID: <1162768865.1566.28.camel@localhost.localdomain> (raw)
In-Reply-To: <b9481e140611051333p7250179ax6ba3629fcf0ad9e3@mail.gmail.com>
Ar Sul, 2006-11-05 am 22:33 +0100, ysgrifennodd Nicolas FR:
> The module was "crashing" on my box because it keeps on receiving
> events=APM_UPDATE_TIME meaning that it would never get out of the
> while() loop in check_events. I need to do some tests but I might
That's a BIOS bug
> simply fix this by ignoring APM_UPDATE_TIME events. I first thought
If that works can you run dmidecode on your box and post me the output,
from that we can add a blacklist entry to automatically handle this.
prev parent reply other threads:[~2006-11-05 23:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-03 23:06 sc3200 cpu + apm module kernel crash Nicolas FR
2006-11-05 18:21 ` Alan Cox
2006-11-05 21:33 ` Nicolas FR
2006-11-05 23:21 ` Alan Cox [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=1162768865.1566.28.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolasfr@gmail.com \
/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