mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Gernoth <simigern@stud.uni-erlangen.de>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel@vger.kernel.org,
	Matthias Koerber <simakoer@stud.informatik.uni-erlangen.de>,
	scott.feldman@intel.com, ganesh.venkatesan@intel.com
Subject: Re: 2.4.29, e100 and a WOL packet causes keventd going mad
Date: Sun, 30 Jan 2005 13:15:49 +0100	[thread overview]
Message-ID: <20050130121549.GA23946@cip.informatik.uni-erlangen.de> (raw)
In-Reply-To: <20050129181821.GA2128@logos.cnet>

On Sat, Jan 29, 2005 at 04:18:21PM -0200, Marcelo Tosatti wrote:
> Probably a task event is rescheduling itself repeatedly? e100 does not seem 
> to schedule_task() events directly, so I wonder what is going on.
> 
> Can you boot a machine with profile=2, then send the WOL packet causing
> keventd to go mad and run:
> 
> readprofile | sort -nr +2 | head -20

faui07c:~# readprofile | sort -nr +2 | head -20
  2352 acpi_ns_get_next_valid_node              130.6667
  9577 acpi_os_read_port                        121.2278
  4431 acpi_os_signal_semaphore                 100.7045
  4639 default_idle                              57.9875
  4363 acpi_ns_get_next_node                     57.4079
  5957 acpi_ns_delete_namespace_by_owner         37.7025
  2307 acpi_os_write_port                        34.9545
  4048 acpi_os_wait_semaphore                    18.8279
  1924 acpi_ut_acquire_mutex                     16.8772
   492 __rdtsc_delay                             15.3750
   526 acpi_os_get_thread_id                     15.0286
  1421 acpi_ut_release_mutex                     13.1574
   339 acpi_ns_get_parent_node                   11.6897
  1506 acpi_ut_release_to_cache                  10.9130
  1600 acpi_ut_acquire_from_cache                 9.8160
   909 acpi_ds_method_data_init                   8.4953
   327 acpi_ut_valid_acpi_name                    6.9574
   311 acpi_ns_search_node                        4.7121
   268 acpi_ps_get_opcode_info                    4.0606
    31 acpi_ut_delete_generic_state_cache         3.4444

The machine has an uptime of 10 minutes at that point, and the second
WOL packet was sent directly after the machine came up and I was able
to ssh into it.

Regards,
  Michael

  reply	other threads:[~2005-01-30 12:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-28 16:48 Michael Gernoth
2005-01-28 18:53 ` Bukie Mabayoje
2005-01-28 18:54   ` Michael Gernoth
2005-01-28 20:05     ` Bukie Mabayoje
2005-01-30  0:13     ` Bukie Mabayoje
2005-01-29 18:18 ` Marcelo Tosatti
2005-01-30 12:15   ` Michael Gernoth [this message]
2005-01-30 17:18 David Härdeman
2005-01-31  3:47 ` Scott Feldman
2005-01-31  3:58   ` Nigel Cunningham
2005-01-31  5:00     ` Scott Feldman
2005-01-31  6:14       ` Nigel Cunningham
2005-01-31  9:08         ` Nigel Cunningham
2005-01-31  4:23   ` Bukie Mabayoje
2005-01-31 15:24     ` Marcelo Tosatti
2005-01-31 20:29       ` David Härdeman
2005-01-31 21:13       ` Bukie Mabayoje
2005-01-31 19:26 Brandeburg, Jesse
2005-01-31 20:57 ` Bukie Mabayoje

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=20050130121549.GA23946@cip.informatik.uni-erlangen.de \
    --to=simigern@stud.uni-erlangen.de \
    --cc=ganesh.venkatesan@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=scott.feldman@intel.com \
    --cc=simakoer@stud.informatik.uni-erlangen.de \
    /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

all inboxes | Powered by JetHome®