linux-kernel - RE: [BISECTION RESULT] sched: revert cpu_clock to pre-27ec4407790d075c325e1f4da0a19c56953cce23 state

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>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 19 Aug 2008 15:34:18 -0700
From:	"Luck, Tony" <tony.luck@...el.com>
To:	Nishanth Aravamudan <nacc@...ibm.com>
CC:	Ingo Molnar <mingo@...e.hu>,
	"linux-ia64@...r.kernel.org" <linux-ia64@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: RE: [BISECTION RESULT] sched: revert cpu_clock to
	pre-27ec4407790d075c325e1f4da0a19c56953cce23 state

> Yes, your patch in isolation (having reverted Peter's
> c1955a3d4762e7a9bf84035eb3c4886a900f0d15) allows this box to boot
> 2.6.27-rc3 with CONFIG_PRINTK_TIME=y. As you noted, I did see some
> oddities in the printk timings, where the values would go up then back
> down, but nothing further out of the ordinary.

Good.  Thanks a lot for testing.

> P.S. Should I start a separate thread on the messages I mentioned
> earlier (but only in passing)?
>
> [   32.593534] kernel unaligned access to 0xe000000644220466, ip=0xa000000100516fa1

Separate thread sounds like a good idea.  You should decode the
ip=value to which routine was running. Look at System.map to get
the routine name, or use "objdump -d" to disassamble your vmlinux
to find the exact instruction (but note that the kernel indicates
the instruction in the bundle with a low order digit of 0, 1, 2
whereas the objdump disassembly uses 0, 6, c).

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