From: Chris Wright <chrisw@osdl.org>
To: Tomasz Lemiech <szpajder@staszic.waw.pl>
Cc: torvalds@osdl.org, chrisw@osdl.org, len.brown@intel.com,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.12.2 acpi_register_gsi() patch causes problems on Asus A7V333 motherboard
Date: Tue, 12 Jul 2005 11:20:07 -0700 [thread overview]
Message-ID: <20050712182007.GX19052@shell0.pdx.osdl.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0507121940170.11987@boss.staszic.waw.pl>
* Tomasz Lemiech (szpajder@staszic.waw.pl) wrote:
> Today I tried 2.6.12.2 on an Asus A7V333 (socket A) with AMD Duron 1300
> MHz CPU and noticed, that the system clock was running about 60 times
> faster than real time and the keyboard was unresponsive. However, I was
> able to log in remotely and collect some standard debugging info (dmesg,
> lspci, interrupts, config), which is available at
> http://szpajder.w.staszic.waw.pl/a7v333/ . Summary of my quick research
> follows:
>
> - 2.6.12.1 works without problems
>
> - 2.6.12.2 with acpi=off works without problems
>
> - 2.6.12.2 with acpi_register_gsi() one-line fix works without problems
One line fix means the 's/>= 0/> 0/' ? If so, that's currently queued to
the -stable tree and should be present in the forthcoming .3. If not,
could you please clarify what the one line fix is?
thanks,
-chris
next prev parent reply other threads:[~2005-07-12 18:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 18:08 2.6.12.2 acpi_register_gsi() patch causes problems on Asus A7V333 motherboard Tomasz Lemiech
2005-07-12 18:20 ` Chris Wright [this message]
2005-07-12 20:00 ` Tomasz Lemiech
2005-07-12 20:15 ` Chris Wright
2005-07-13 8:00 ` Tomasz Lemiech
2005-07-13 8:02 ` Chris Wright
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=20050712182007.GX19052@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=szpajder@staszic.waw.pl \
--cc=torvalds@osdl.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