Messages in this thread | | | Date | Wed, 14 May 2008 14:00:32 -0700 | From | Andrew Morton <> | Subject | Re: 2.6.26-rc2-mm1 |
| |
On Wed, 14 May 2008 14:49:07 -0600 Zan Lynx <zlynx@acm.org> wrote:
> On Wed, 2008-05-14 at 01:01 -0700, Andrew Morton wrote: > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.26-rc2/2.6.26-rc2-mm1/ > > > > > > - The -mm tree is now based on linux-next. > > > > I will occasionally pick up later versions of trees which are already > > in linux-next, to catch material which was added after Stephen last > > pulled that tree. That happened this time: git-net had a lot of driver > > changes which weren't in linux-next and which I wanted in > > 2.6.26-rc2-mm1. > > > > - A few more git trees were added: git-ubifs.patch, git-regulator.patch, > > git-logfs.patch, git-orion.patch. > > No good on my first attempt. Here is what I ran into: > > The printk timestamps have gone wild. I cannot paste a dmesg but here > is one line I wrote down: > [17180644.495790] Testing tracer ftrace: NMI watchdog ...
I've seen reports like this against mainline, but I'm not sure that much has been done about it yet.
> Which leads into the next problem: The kernel freezes after Testing > tracer ftrace. Then I rebooted with my special testing command line > "kernel /bzImage-2.6.26-rc2-mm1 root=/dev/sda2 rootfstype=reiser4 > rootflags=defaults,noatime i8042.nomux elevator=cfq resume=/dev/sda3 > panic=5 nmi_watchdog=2,panic debug idle=poll nohz=off" > > and I got the same freeze but then the NMI watchdog message. Which is > the third problem. > > Why did the NMI watchdog not panic and reboot the system? It detected > the lock and printed the message. It should have then panicked, waited > 5 seconds, and rebooted. > > System is a 64-bit Gentoo AMD-64 Compaq R3000 laptop. Compiler is GCC > 4.3.
afaict this is all Ingo/Thomas stuff, so I'll add the ccs and run away :(
> Config follows:
Thanks.
| |