linux-kernel - Strange problems building 2.6.2[45] for Winchip2A under Ubuntu

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <1209603525.8100.43.camel@surfer>
Date:	Wed, 30 Apr 2008 19:58:45 -0500
From:	David Hagood <david.hagood@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Strange problems building 2.6.2[45] for Winchip2A under Ubuntu

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).

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/