On Fri, 2007-03-30 at 00:51 -0700, Greg KH wrote:
> On Fri, Mar 30, 2007 at 03:08:03PM +0800, Shaohua Li wrote:
> > On Fri, 2007-03-30 at 00:05 -0700, Greg KH wrote:
> > >
> > > I'm still confused as to why you are creating these "extra" kobjects.
> > > What are they used for?
> > It's for each id
On Fri, Mar 30, 2007 at 03:08:03PM +0800, Shaohua Li wrote:
> On Fri, 2007-03-30 at 00:05 -0700, Greg KH wrote:
> >
> > I'm still confused as to why you are creating these "extra" kobjects.
> > What are they used for?
> It's for each idle state.
Where are these states in sysfs? Is this the
/sys/
On Fri, 2007-03-30 at 00:05 -0700, Greg KH wrote:
> On Fri, Mar 30, 2007 at 02:33:44PM +0800, Shaohua Li wrote:
> > On Thu, 2007-03-29 at 22:18 -0700, Greg KH wrote:
> > > On Wed, Mar 28, 2007 at 02:49:12PM +0800, Shaohua Li wrote:
> > > > On Tue, 2007-03-27 at 22:58 -0700, Greg KH wrote:
> > > > >
On Fri, Mar 30, 2007 at 02:33:44PM +0800, Shaohua Li wrote:
> On Thu, 2007-03-29 at 22:18 -0700, Greg KH wrote:
> > On Wed, Mar 28, 2007 at 02:49:12PM +0800, Shaohua Li wrote:
> > > On Tue, 2007-03-27 at 22:58 -0700, Greg KH wrote:
> > > > On Wed, Mar 28, 2007 at 01:39:26PM +0800, Shaohua Li wrote:
On Thu, 2007-03-29 at 22:18 -0700, Greg KH wrote:
> On Wed, Mar 28, 2007 at 02:49:12PM +0800, Shaohua Li wrote:
> > On Tue, 2007-03-27 at 22:58 -0700, Greg KH wrote:
> > > On Wed, Mar 28, 2007 at 01:39:26PM +0800, Shaohua Li wrote:
> > > > On Tue, 2007-03-27 at 22:27 -0700, Greg KH wrote:
> > > > >
On Wed, Mar 28, 2007 at 02:49:12PM +0800, Shaohua Li wrote:
> On Tue, 2007-03-27 at 22:58 -0700, Greg KH wrote:
> > On Wed, Mar 28, 2007 at 01:39:26PM +0800, Shaohua Li wrote:
> > > On Tue, 2007-03-27 at 22:27 -0700, Greg KH wrote:
> > > >
> > > > Putting more than one kobject in the same structur
On 3/29/07, Ed Sweetman <[EMAIL PROTECTED]> wrote:
NVRM: loading NVIDIA UNIX x86_64 Kernel Module 1.0-9746 Fri Dec 15 10:19:35
PST 2006
PCI: Setting latency timer of device :01:00.0 to 64
NVRM: loading NVIDIA UNIX x86_64 Kernel Module 1.0-9746 Fri Dec 15 10:19:35
PST 2006
**WARNING** I2
On Friday 30 March 2007 03:09:14 David Brownell wrote:
> On Thursday 29 March 2007 4:29 pm, Maxim Levitsky wrote:
> > On Friday 30 March 2007 00:33:35 David Brownell wrote:
> > > On Wednesday 28 March 2007 2:27 pm, Maxim wrote:
>
> > > > So the only way out is to emulate RTC using HPET,
>
On Thursday 29 March 2007 4:29 pm, Maxim Levitsky wrote:
> On Friday 30 March 2007 00:33:35 David Brownell wrote:
> > On Wednesday 28 March 2007 2:27 pm, Maxim wrote:
> > > So the only way out is to emulate RTC using HPET,
> > > It is done this way in old rtc driver, rtc-cmos should do the sam
On Friday 30 March 2007 00:33:35 David Brownell wrote:
> On Wednesday 28 March 2007 2:27 pm, Maxim wrote:
> > On Wednesday 28 March 2007 22:59:26 David Brownell wrote:
>
> > When HPET is active it eats RTC IRQ,
>
> Only when HPET timers 0 and 1 are set up for "Legacy Replacement Mode".
> In t
On Wednesday 28 March 2007 2:27 pm, Maxim wrote:
> On Wednesday 28 March 2007 22:59:26 David Brownell wrote:
> When HPET is active it eats RTC IRQ,
Only when HPET timers 0 and 1 are set up for "Legacy Replacement Mode".
In the more sensible "Standard Mode", they have their own IRQs.
>
Hmm. I've reproduced these problems with vanilla 2.6.21-rc5, so the
latest acpi-git changes are off the hook. I am currently trying to
reproduce the problems with 2.6.21-rc4. I'll let you know how it
turns out.
Miles
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi
Added:
http://bugzilla.kernel.org/show_bug.cgi?id=8283
I am going to double-check with vanilla 2.6.21-rc5 and make sure none
of the problems are happening there.
Miles
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to [EMAIL PROTECTED]
More m
Ingo Molnar <[EMAIL PROTECTED]> writes:
>
> there's no fundamental reason. x86_64 COW-ed hpet_timer.c and
> time_hpet.c years ago and drifted off into different areas.
Not quite -- x86-64 did HPET long before i386; the only stuff cowed
was the character driver support code. But the core HPET cod
On 3/29/07, Maxim Levitsky <[EMAIL PROTECTED]> wrote:
Subject: Add suspend/resume for HPET
This adds support of suspend/resume on i386 for HPET
Signed-off-by: Maxim Levitsky <[EMAIL PROTECTED]>
Confirmed that suspend/resume disk/ram works on X60s with
CONFIG_HPET_TIMER=y and CONFIG_NO_HZ unset.
* Linus Torvalds <[EMAIL PROTECTED]> wrote:
> Btw, what about arch/x86_64/kernel/hpet.c?
at least wrt. suspend/resume it should be fine, because in
arch/x86_64/kernel/time.c it does this upon resume:
static int timer_resume(struct sys_device *dev)
{
if (hpet_address)
update: i've tested Maxim's v2 patch on both a hpet-capable and a
hpet-less system, and it works fine here.
on a dual-core hpet-capable system, running a NO_HZ+!HIGH_RES_TIMERS
kernel:
europe:~> grep Clock /proc/timer_list
Clock Event Device: hpet
Clock Event Device: lapic
Clock Event
On Thursday 29 March 2007 18:53:37 Linus Torvalds wrote:
>
> On Thu, 29 Mar 2007, Maxim Levitsky wrote:
> >
> > Subject: Add suspend/resume for HPET
> >
> > This adds support of suspend/resume on i386 for HPET
> >
> > Signed-off-by: Maxim Levitsky <[EMAIL PROTECTED]>
> >
> > ---
> > arch/i386/ke
On Thu, 29 Mar 2007, Maxim Levitsky wrote:
>
> I agree, and as you said I did exactly that:
Gaah. I'm blind. Sorry. Your patch did indeed do exactly that, I somehow
overlooked it.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of
On Thursday 29 March 2007 04:15, Andrew Morton wrote:
> On Thu, 29 Mar 2007 01:00:45 -0700 "Miles Lane" <[EMAIL PROTECTED]> wrote:
>
> > On 3/28/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
> > > On Wed, 28 Mar 2007 13:55:54 -0700
> > > "Miles Lane" <[EMAIL PROTECTED]> wrote:
> > >
> > > > My lapt
On Thu, 29 Mar 2007, Maxim Levitsky wrote:
>
> Subject: Add suspend/resume for HPET
>
> This adds support of suspend/resume on i386 for HPET
>
> Signed-off-by: Maxim Levitsky <[EMAIL PROTECTED]>
>
> ---
> arch/i386/kernel/hpet.c | 68
> +++
Btw, wh
On Thursday 29 March 2007 18:35:21 Linus Torvalds wrote:
>
> On Thu, 29 Mar 2007, Maxim wrote:
>
> > On Thursday 29 March 2007 07:08:58 Linus Torvalds wrote:
> > >
> > > (Or, better yet, shouldn't we set "boot_hpet_disable" when we decide not
> > > to use the HPET, and set hpet_virt_address to
On Thu, 29 Mar 2007, Maxim wrote:
> On Thursday 29 March 2007 07:08:58 Linus Torvalds wrote:
> >
> > (Or, better yet, shouldn't we set "boot_hpet_disable" when we decide not
> > to use the HPET, and set hpet_virt_address to NULL?)
>
> This is done here
>
> out_nohpet:
> iounmap(hpet_vi
Dave,
[EMAIL PROTECTED] wrote:
http://bugzilla.kernel.org/show_bug.cgi?id=8255
Okay. I tracked down the problem with git. Here is what is the submission that
causes the problem:
solaris linux-git # git bisect good
0916bd3ebb7cefdd0f432e8491abe24f4b5a101e is first bad commit
commit 0916bd3ebb
On 3/29/07, Michael S. Tsirkin <[EMAIL PROTECTED]> wrote:
> Quoting Maxim <[EMAIL PROTECTED]>:
> The patch below is a temporally fix, until
> clock-events and clocksources will get proper suspend/resume
> hooks:
Bingo!
I confirmed that it suspend/resume disk/ra
Subject: Add suspend/resume for HPET
This adds support of suspend/resume on i386 for HPET
Signed-off-by: Maxim Levitsky <[EMAIL PROTECTED]>
---
arch/i386/kernel/hpet.c | 68 +++
1 files changed, 68 insertions(+), 0 deletions(-)
diff --git a/arch/i386
On Thursday 29 March 2007 15:20:27 Sergei Shtylyov wrote:
> Hello.
>
> Maxim wrote:
>
> > ---
> > This adds support of suspend/resume on i386 for HPET
>
>The part after usually "---" gets cut off, the patch description and
> signoff should actially *precede* it.
>
> > Signed-off-by: Maxim
Hello.
Maxim wrote:
---
This adds support of suspend/resume on i386 for HPET
The part after usually "---" gets cut off, the patch description and
signoff should actially *precede* it.
Signed-off-by: Maxim Levitsky <[EMAIL PROTECTED]>
diff --git a/arch/i386/kernel/hpet.c b/arch/i386/k
On Thu, 2007-03-29 at 17:19 +0800, Zhang, Rui wrote:
> Does the problem still exists in the latest kernel? Say 2.6.21-rc5.
Yes, the attached dmesg file is got from 2.6.21-rc5-git1
> It will be helpful if you can attach your acpidump file.
>
(snip)
-
To unsubscribe from this list: send the line
On Thu, 2007-03-29 at 17:19 +0800, Zhang, Rui wrote:
> Does the problem still exists in the latest kernel? Say 2.6.21-rc5.
> It will be helpful if you can attach your acpidump file.
where is, or how to get, the acpidump file?
-
To unsubscribe from this list: send the line "unsubscribe linux-acp
Does the problem still exists in the latest kernel? Say 2.6.21-rc5.
It will be helpful if you can attach your acpidump file.
Best regards,
Zhang.Rui(Ray)
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Conke Hu
Sent: 2007年3月29日 17:05
To: linux-acpi@vge
On Thu, 2007-03-29 at 14:56 +0800, Luming Yu wrote:
> why do you think so?
>
> On 3/29/07, Conke Hu <[EMAIL PROTECTED]> wrote:
> > my mail does not work ?
> >
It seems OK:)
Pls just ignore or delete the message.
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body
Hi all,
I am idiot on ACPI knowing nothing about it :)
When I boot linux on AMD Athlon64x2 + A690G + SB600 platform, I get
2 lines of error message saying "Error attaching device data". I've
tested on kernels 2.6.18 ~ 2.6.20, and each of them has the same error.
I debug the drivers/acpi
Hi all,
I am idiot on ACPI knowing nothing about it :)
When I boot linux on AMD Athlon64x2 + A690G + SB600 platform, I get
2 lines of error message saying "Error attaching device data", pls see
the attachment. I've tested on kernels 2.6.18 ~ 2.6.20, and each of them
has the same error.
On Wed, 2007-03-28 at 14:49 +0800, Shaohua Li wrote:
> On Tue, 2007-03-27 at 22:58 -0700, Greg KH wrote:
> > On Wed, Mar 28, 2007 at 01:39:26PM +0800, Shaohua Li wrote:
> > > On Tue, 2007-03-27 at 22:27 -0700, Greg KH wrote:
> > > >
> > > > Putting more than one kobject in the same structure is a
On Thu, 29 Mar 2007 01:00:45 -0700 "Miles Lane" <[EMAIL PROTECTED]> wrote:
> On 3/28/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
> > On Wed, 28 Mar 2007 13:55:54 -0700
> > "Miles Lane" <[EMAIL PROTECTED]> wrote:
> >
> > > My laptop (HP dv1240us) is always showing that my laptop is plugged
> > > i
On 3/28/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
On Wed, 28 Mar 2007 13:55:54 -0700
"Miles Lane" <[EMAIL PROTECTED]> wrote:
> My laptop (HP dv1240us) is always showing that my laptop is plugged
> into AC power, even when it is running off of the battery. When I
> plug into the AC after runn
37 matches
Mail list logo
