public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Hagood <david.hagood@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Strange problems building 2.6.2[45] for Winchip2A under Ubuntu
Date: Wed, 30 Apr 2008 19:58:45 -0500	[thread overview]
Message-ID: <1209603525.8100.43.camel@surfer> (raw)

I have an old laptop I'm trying to resurrect, and am having a strange
problem:

If I run the kernels supplied by Xubuntu, all is well - no strange
behavior (as in, none of the stuff I am about to describe happens).

If I build my own kernel (as I am trying to strip out unneeded stuff
this machine does not and never will have like AGP and Bluetooth), weird
things happen:
  For 2.6.25, I cannot read or write to /proc/mtrr - I get an I/O error
(the file exists within proc)
  Starting klogd hangs for about 2 minutes - looking at the system
during this time shows a "dd if=/proc/kmsg of=/var/log/kmsg" process
hanging. Attempting this by hand shows dd hangs (as does a
"cat /proc/kmsg").

Other than this, the system runs (networking comes up, X comes up
(eventually).

I've tried just building with the kernel configuration Xubuntu uses to
the same results.

I would think that the fact that the Xubuntu supplies kernels work would
tend to exonerate the hardware, that building with the Xubuntu supplied
configuration would tend to exonerate the configuration, but that leaves
me stumped - either my version of GCC is screwy, or my build process is
bad, or ???

(builds are done on my Athlon Ubuntu machine ( GCC version 4.2.3 (Ubuntu
4.2.3-2ubuntu7)) via the standard "make gconfig; make" process on a
tarball pulled fresh from kernel.org, which is then NFS mounted by the
target, a final "make modules_install install" executed, and the initrd
created on the target).



                 reply	other threads:[~2008-05-01  0:59 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=1209603525.8100.43.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