From: Len Brown <lenb@kernel.org>
To: MoRpHeUz <morpheuz@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>, Stelian Pop <stelian@popies.net>,
Mattia Dongili <malattia@linux.it>,
Ismail Donmez <ismail@pardus.org.tr>,
Andrea Gelmini <gelma@gelma.net>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
Cacy Rodney <cacy-rodney-cacy@tlen.pl>
Subject: Re: Sony Vaio VGN-SZ340 (was Re: sonypc with Sony Vaio VGN-SZ1VP)
Date: Fri, 5 Jan 2007 13:10:40 -0500 [thread overview]
Message-ID: <200701051310.41131.lenb@kernel.org> (raw)
In-Reply-To: <7ce7bf330701050924h47546970w36ed189ed147ddb3@mail.gmail.com>
On Friday 05 January 2007 12:24, MoRpHeUz wrote:
> > What workaround are you using?
>
> This one: http://bugzilla.kernel.org/show_bug.cgi?id=7465
Ah yes, the duplicate MADT issue is clearly a BIOS bug.
It is possible that we can tweak our Linux workaround for it to be more
Microsoft Windows Bug Compatbile(TM).
> > The frequency scaling issue sounds like a BIOS/Linux incompatibility.
It looks like this issue results from that above,
rather than being an additional problem.
> > The nvidia issue sounds like an interrupt issue, so please reproduce
> > it using the open source nvidia driver (not the nvidia binary),
> > and include the lspci -vv output, dmesg, and /proc/interrupts.
>
> Will try that !
If interrupts fail using the open source nvidia driver, (and using the workaround
from the bug above to use the right MADT, please open a new bug report
as I think it would be an independent issue.
thanks,
-Len
next prev parent reply other threads:[~2007-01-05 18:11 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 11:51 sonypc with Sony Vaio VGN-SZ1VP stelian
2006-09-28 16:27 ` Yu Luming
2007-01-04 5:24 ` Len Brown
2007-01-04 10:09 ` Stelian Pop
2007-01-04 19:15 ` Mattia Dongili
2007-01-04 20:51 ` Andrew Morton
2007-01-04 21:18 ` Mattia Dongili
2007-01-04 21:28 ` Andrew Morton
2007-01-04 21:36 ` Timo Hoenig
2007-01-04 21:36 ` Richard Hughes
2007-01-04 21:58 ` Mattia Dongili
2007-01-05 17:02 ` Len Brown
2007-01-05 18:06 ` Mattia Dongili
2007-01-04 23:36 ` Stelian Pop
2007-01-04 23:44 ` Andrew Morton
2007-01-04 23:54 ` Stelian Pop
2007-01-05 4:16 ` Andrew Morton
2007-01-05 9:58 ` Stelian Pop
2007-01-05 2:20 ` MoRpHeUz
2007-01-05 17:11 ` Sony Vaio VGN-SZ340 (was Re: sonypc with Sony Vaio VGN-SZ1VP) Len Brown
2007-01-05 17:24 ` MoRpHeUz
2007-01-05 18:10 ` Len Brown [this message]
2007-01-06 4:09 ` Bjorn Helgaas
2007-01-11 19:52 ` Len Brown
2007-01-11 20:01 ` Alexey Starikovskiy
2007-01-05 0:11 ` sonypc with Sony Vaio VGN-SZ1VP Jan Engelhardt
2007-01-05 9:15 ` Mattia Dongili
2007-01-05 9:59 ` Stelian Pop
2007-01-04 23:34 ` Stelian Pop
2007-01-05 9:23 ` Neil Bird
2007-01-05 16:24 ` Mattia Dongili
2007-01-10 8:32 ` Neil Bird
2007-01-11 12:20 ` sonypc with Sony Vaio VGN-SZ1VP [repost] Neil Bird
2007-01-05 17:19 ` sonypc with Sony Vaio VGN-SZ1VP Len Brown
2007-01-10 8:36 ` Neil Bird
2007-01-11 12:20 ` sonypc with Sony Vaio VGN-SZ1VP [repost] Neil Bird
2007-01-05 10:02 ` sonypc with Sony Vaio VGN-SZ1VP Stelian Pop
2007-01-05 12:13 ` Mattia Dongili
2007-01-05 14:23 ` Jan Engelhardt
2007-01-09 15:19 ` Luming Yu
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=200701051310.41131.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=akpm@osdl.org \
--cc=cacy-rodney-cacy@tlen.pl \
--cc=gelma@gelma.net \
--cc=ismail@pardus.org.tr \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=malattia@linux.it \
--cc=morpheuz@gmail.com \
--cc=stelian@popies.net \
/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).