linux-kernel - [BUG] Winchip2A + 2.6.25 = klogd 100% CPU, /proc/mtrr busted

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]

Date:	Sun, 18 May 2008 19:18:49 -0500
From:	David Hagood <david.hagood@...il.com>
To:	LKML <linux-kernel@...r.kernel.org>
Subject: [BUG] Winchip2A + 2.6.25 = klogd 100% CPU, /proc/mtrr busted

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?

--
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/