From: Sergey Senozhatsky <sergey.senozhatsky at gmail.com>
To: powertop@lists.01.org
Subject: Re: [Powertop] segfault on Sheevaplug (ARM Kirkwood)
Date: Sun, 20 May 2012 12:05:01 +0300 [thread overview]
Message-ID: <20120520090501.GA3515@swordfish> (raw)
In-Reply-To: 1337503302.67870.YahooMailNeo@web160301.mail.bf1.yahoo.com
[-- Attachment #1: Type: text/plain, Size: 878 bytes --]
On (05/20/12 01:41), Rui DaCosta wrote:
> I get the following segfault running 2.0 from unmodified source and
> default build options in Arch Linux ARM:
> Linux alarm 3.1.10-10-ARCH #1 PREEMPT Thu May 10 02:00:37 UTC 2012
> armv5tel GNU/Linux
> Cannot load from file /var/cache/powertop/saved_results.powertop
> Cannot load from file /var/cache/powertop/saved_parameters.powertop
> Segmentation fault
> trace is:
> #0 handle_one_cpu (model=0, family=0, vendor=0xbeffcf8c "",
> number=4294967295)
weird and overflowed input.
could you please provide your /proc/cpuinfo output?
-ss
> at cpu/cpu.cpp:210
> #1 enumerate_cpus () at cpu/cpu.cpp:276
> #2 0x000495d8 in main (argc=1, argv=0xbefffcc4) at main.cpp:382
> please let me know if there's anything else I can provide to assist.
> Regards,
> RuiDC
next reply other threads:[~2012-05-20 9:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-20 9:05 Sergey Senozhatsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-05-22 22:08 [Powertop] segfault on Sheevaplug (ARM Kirkwood) Rui DaCosta
2012-05-22 21:58 Rui DaCosta
2012-05-22 21:23 Sergey Senozhatsky
2012-05-22 20:50 Thomas Spura
2012-05-22 19:35 Rui DaCosta
2012-05-22 19:19 Rui DaCosta
2012-05-21 23:09 Chris Ferron
2012-05-20 22:17 Sergey Senozhatsky
2012-05-20 22:05 Sergey Senozhatsky
2012-05-20 21:57 Sergey Senozhatsky
2012-05-20 19:32 Rui DaCosta
2012-05-20 11:01 Rui DaCosta
2012-05-20 9:34 Sergey Senozhatsky
2012-05-20 9:19 Rui DaCosta
2012-05-20 8:41 Rui DaCosta
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=20120520090501.GA3515@swordfish \
--to=powertop@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.