Re: kacpid problems

dev_zero
2004-11-11T15:26:10Z

When I applied this patch.. I could play even longer
than last time, before kacpid started running at 99%
cpu usage. First I played longer than usual, then
kacpid started running but not with 99% cpu usage,
then it stopped. It went like this a couple of times
then kacpid started with 99% cpu usage again.
Don't know if the patch worked correctly, but I
thought the kacpid should go S5, shutdown, shouldn't
it?

--- "Wang, Zhenyu" <zhenyu.z.wang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> wrote:
> copy these from acpi_thermal_remove, does this
> workaround your issue?
>
> ---
> acpi-2.6/drivers/acpi/thermal.c~remove_queue_work
> 2004-11-10 23:38:51.000000000 +0800
> +++ acpi-2.6/drivers/acpi/thermal.c 2004-11-11
> 09:19:57.365634568 +0800
> @@ -472,6 +472,13 @@ acpi_thermal_critical (
> printk(KERN_EMERG "Critical temperature reached
> (%ld C), shutting down.\n",
> KELVIN_TO_CELSIUS(tz->temperature));
> acpi_bus_generate_event(device,
> ACPI_THERMAL_NOTIFY_CRITICAL,
> tz->trips.critical.flags.enabled);
>
> + tz->zombie = 1;
> + /* wait for running timer (on other CPUs) finish
> */
> + del_timer_sync(&(tz->timer));
> + /* synchronize deferred task */
> + acpi_os_wait_events_complete(NULL);
> + /* deferred task may reinsert timer */
> + del_timer_sync(&(tz->timer));
>
>
acpi_thermal_call_usermode(ACPI_THERMAL_PATH_POWEROFF);
>
> return_VALUE(0);
>
>
> On 2004.11.10 18:09:45 +0000, dev_zero wrote:
> > This patch actually made some difference. I could
> play
> > much longer now. First it started lagging, then it
> > stopped, then it started lagging again, then it
> > stopped. It went like this for a while, but after
> I
> > had played som more, it started lagging again but
> now
> > it didn't stop.
> >
> > --- "Wang, Zhenyu" <zhenyu.z.wang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> wrote:
> > > oops,
> > >
> > > ---
> > >
> acpi-2.6/drivers/acpi/thermal.c~remove_queue_work
> > > 2004-11-10 23:38:51.693022464 +0800
> > > +++ acpi-2.6/drivers/acpi/thermal.c 2004-11-10
> > > 23:52:40.820975856 +0800
> > > @@ -472,6 +472,8 @@ acpi_thermal_critical (
> > > printk(KERN_EMERG "Critical temperature
> reached
> > > (%ld C), shutting down.\n",
> > > KELVIN_TO_CELSIUS(tz->temperature));
> > > acpi_bus_generate_event(device,
> > > ACPI_THERMAL_NOTIFY_CRITICAL,
> > > tz->trips.critical.flags.enabled);
> > >
> > > + tz->zombie = 1;
> > > + acpi_os_wait_events_complete(NULL);
> > >
> > >
> >
>
acpi_thermal_call_usermode(ACPI_THERMAL_PATH_POWEROFF);
> > >
> > > return_VALUE(0);
> > >
> > > If this has no help, maybe others eat up
> kacpid..
> > >
> > > On 2004.11.10 23:44:33 +0000, Wang, Zhenyu
> wrote:
> > > > Pls try this patch,
> > > >
> > > > ---
> > >
> acpi-2.6/drivers/acpi/thermal.c~remove_queue_work
> > > 2004-11-10 23:38:51.693022464 +0800
> > > > +++ acpi-2.6/drivers/acpi/thermal.c
> 2004-11-10
> > > 23:39:50.195128792 +0800
> > > > @@ -472,6 +472,7 @@ acpi_thermal_critical (
> > > > printk(KERN_EMERG "Critical
> temperature
> > > reached (%ld C), shutting down.\n",
> > > KELVIN_TO_CELSIUS(tz->temperature));
> > > > acpi_bus_generate_event(device,
> > > ACPI_THERMAL_NOTIFY_CRITICAL,
> > > tz->trips.critical.flags.enabled);
> > > >
> > > > + tz->zombie = 1;
> > > >
> > >
> >
>
acpi_thermal_call_usermode(ACPI_THERMAL_PATH_POWEROFF);
> > > >
> > > > return_VALUE(0);
> > > >
> > > > Is this work?
> > > >
> > > > -zhen
> > > >
> > > > On 2004.11.10 14:33:35 +0000, dev_zero wrote:
> > > > > kacpid still runns with 99%cpu usage when
> the
> > > cpu gets
> > > > > too hot. I tried the game quake 2. You can
> play
> > > around
> > > > > 10 -15 minutes before the kacpid starts
> running
> > > on 99%
> > > > > cpu usage. I also used quake 2 too test the
> > > kernel
> > > > > before I applied your patch.
> > > > >
> > > > > --- "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> wrote:
> > > > > > It means there was NO event generated at
> that
> > > time.
> > > > > > Do you think the symptom is gone with my
> debug
> > > > > > patch?
> > > > > > If so, I think your box need a more sane
> > > schedule
> > > > > > for acpi_thermal_check
> > > > > > And, I can come up with a patch.
> > > > > >
> > > > > > Thanks
> > > > > > Luming
> > > > > >
> > > > > > >-----Original Message-----
> > > > > > >From: dev_zero [mailto:dev_xor-eZNTXLQAfP4@public.gmane.org]
> > > > > > >Sent: 2004å¹´11æœˆ10æ—¥ 1:06
> > > > > > >To: Yu, Luming
> > > > > > >Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> > > > > > >Subject: RE: [ACPI] kacpid problems
> > > > > > >
> > > > > > >When I try to output the event file I do
> > > this:
> > > > > > >[root@balder: /proc/acpi]# cat event >
> > > > > > /home/event.log
> > > > > > >
> > > > > > >But then It just stands there without
> doing
> > > > > > anything.
> > > > > > >So i tried to check what was wrong (ps
> ax)
> > > command:
> > > > > > >2922 pts/0 S+ 0:00 cat event
> > > > > > >
> > > > > > >I don't know if it is supposed to be
> > > suspended?
> > > > > > >> I want to know what kind of events
> could be
> > > > > > >> generated heavily, which could have
> > > corresponding
> > > > > > >> pending execution of AML method issued
> to
> > > work
> > > > > > queue
> > > > > > >> handled by kacpid. So just cat
> > > /proc/acpi/event
> > > > > > >
> > > > > > >> event.log
> > > > > > >> to me when you were observing abnormal
> cpu
> > > > > > >> consumption by kacpid.
> > > > > > >>
> > > > > > >> Thanks
> > > > > > >> Luming
> > > > > > >>
> > > > > > >> >-----Original Message-----
> > > > > > >> >From: dev_zero
> [mailto:dev_xor-eZNTXLQAfP4@public.gmane.org]
> > > > > > >> >Sent: 2004Ã„Ãª11Ã”Ã‚10ÃˆÃ• 0:00
> > > > > > >> >To: Yu, Luming
> > > > > > >> >Subject: RE: [ACPI] kacpid problems
> > > > > > >> >
> > > > > > >> >Of course.. But which log files do you
> > > want to
> > > > > > take
> > > > > > >> a
> > > > > > >> >look at?
> > > > > > >> >> >How am i supppose to get an output
> from
> > > > > > >> >> >/proc/acpi/event ??? I can't access
> the
> > > file,
> > > > > > >> >> because
> > > > > > >> >> >it's in use.
> > > > > > >> >>
> > > > > > >> >> Just kill acpid or the similar.
> > > > > > >> >>
> > > > > > >> >>
> > > > > > >> >>
> > > > > > >>
> > > > > >
>
=== message truncated ===