public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@sw.ru>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org, davej@codemonkey.org.uk, akpm@osdl.org
Subject: Re: Oops after cd /sys/.../cpufreq/; rmmod; cat stats/time_in_state
Date: Tue, 20 Mar 2007 13:06:34 +0300	[thread overview]
Message-ID: <20070320100634.GA6811@localhost.sw.ru> (raw)
In-Reply-To: <20070319204125.GA5598@suse.de>

On Mon, Mar 19, 2007 at 01:41:25PM -0700, Greg KH wrote:
> On Mon, Mar 19, 2007 at 06:30:13PM +0300, Alexey Dobriyan wrote:
> > Steps to reproduce:
> >
> > 	# modprobe p4-clockmod
> > 	$ cd /sys/devices/system/cpu/cpu0/cpufreq/
> > 	# rmmod p4-clockmod
> > 	$ cat stats/time_in_state
> > 	Segmentation fault
>
> Has this always happened?  Or is it new?

I've checked 2.6.17 and up and it happens too.

Some .config peculiarities:

	CONFIG_CPU_FREQ=y
	CONFIG_CPU_FREQ_STAT=y
	CONFIG_X86_P4_CLOCKMOD=m

After modprobe/rmmod cpufreq/stats directory appears but doesn't get
removed. Should it?

/sys/devices/system/cpu/cpu0/cpufreq $ ls -lR
.:
total 0
drwxr-xr-x 2 root root 0 2007-03-20 12:59 stats

./stats:
total 0
-r--r--r-- 1 root root 4096 2007-03-20 12:59 time_in_state
-r--r--r-- 1 root root 4096 2007-03-20 12:59 total_trans


  reply	other threads:[~2007-03-20  9:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-19 15:30 Oops after cd /sys/.../cpufreq/; rmmod; cat stats/time_in_state Alexey Dobriyan
2007-03-19 20:41 ` Greg KH
2007-03-20 10:06   ` Alexey Dobriyan [this message]
2007-03-22  3:07     ` Greg KH
2007-03-22  3:51       ` Dave Jones
2007-03-22  4:00         ` Greg KH
2007-03-22  4:10           ` Andrew Morton
2007-03-22 17:02             ` [PATCH] fix cpufreq_stats attrs removal Mattia Dongili
2007-03-22 17:14               ` Dave Jones
2007-03-22 17:43               ` Mattia Dongili
2007-03-22 17:50                 ` Dave Jones
2007-03-30  8:09               ` Alexey Dobriyan
2007-03-30 18:16                 ` Mattia Dongili

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=20070320100634.GA6811@localhost.sw.ru \
    --to=adobriyan@sw.ru \
    --cc=akpm@osdl.org \
    --cc=davej@codemonkey.org.uk \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.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