![]() | |||||||||||||
Messages in this thread |
On Wednesday 14 May 2008 05:00:32 pm Andrew Morton wrote: > 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-rc > > >2/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. I've reported problems with -next and ftrace. The timestamps look very similar to what I've seen as well. I don't have those kernels available anymore - I decided to wipe my system and move to a distro where it's easier to test new kernels. However, it stands to reason that it isn't ftrace actually causing the problem. > > 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. That is quite similar... I'm on a Core2Duo (Dell Inspiron 1420 laptop) and was seeing the problems with GCC4.3 and a pure 64bit userland. DRH > afaict this is all Ingo/Thomas stuff, so I'll add the ccs and run away :( > > > Config follows: > > Thanks. > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ -- Dialup is like pissing through a pipette. Slow and excruciatingly painful. | ||||||||||||
| Last update: 2008-05-14 23:37 [W:1.157 / U:0.210 seconds] ©2003-2008 Jasper Spaans | |||||||||||||