mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Hagood <david.hagood@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: [BUG] Winchip2A + 2.6.25 = klogd 100% CPU, /proc/mtrr busted
Date: Sun, 18 May 2008 19:18:49 -0500	[thread overview]
Message-ID: <1211156329.7192.16.camel@surfer> (raw)

I'm trying to resurrect an old laptop based on the Winchip2A, but I am
unable to get a 2.6.25 kernel built that works.

I've tried various combinations of gcc versions (4.1, 4.2.3, 4.3
snapshots), various build options, and in all cases I get the same
symptoms:

1) klogd will take 100% CPU time once the system is up.
2) attempting to access /proc/mtrr will yield "Input/output error"

strace'ing the klogd process yields:
syslog(0x2, 0x804d6e0, 0xfff)           = -1 EPERM (Operation not
permitted)
write(2, "klogd: Error return from sys_syc"..., 65) = -1 EBADF (Bad file
descriptor)

I've tried building the kernel targeting the WinChip2a, the WinChip2,
generic 586, with no preemption, preemption, no optimize for size,
optimize for size.

The funny thing is that if I run the stock kernels as built by Ubuntu
this does not happen, and if I build a kernel in the same way for my
Athlon machines it works.

Has anybody else seen this?



                 reply	other threads:[~2008-05-19  0:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1211156329.7192.16.camel@surfer \
    --to=david.hagood@gmail.com \
    --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
Powered by JetHome