On Wed, 2006-02-01 at 16:47 -0500, Steven Rostedt wrote: > On Wed, 2006-02-01 at 12:39 -0600, Clark Williams wrote: > > On Wed, 2006-02-01 at 13:32 -0500, Steven Rostedt wrote: > > > > > > I'm still curious to what's happening with your kernel. I'm currently > > > running my x86_64 (typing right now on it) with CONFIG_SMP=n and > > > CONFIG_LATENCY=y. I know you probably sent a config before, but could > > > you send it to me again. (probably best to send it to me off list) > > > > yeah, it's been gnawing at me too. Not really stopping me, but I've seen > > it happen on two Athlon64's (3000+ and 3400+). > > > > I'll send the .config offlist. > > Clark, > > Could you make sure that your modules in the initrd that you use are the > ones created with the LATENCY_TRACE option. After converting all the > modules into compiled in options, I successfully booted the kernel. So > you might have an incompatibility with the modules in initrd, when you > turn on LATENCY_TRACE. Did you ever duplicated the failure? I'm fairly certain that the initrd contains the appropriate modules, since I regenerate the initrd each time I generate a new kernel, but I'll go back and verify. I'll also convert modules to compiled in and see if that makes a difference. Clark -- Clark Williams <[email protected]>
Attachment:
signature.asc
Description: This is a digitally signed message part
- Follow-Ups:
- Re: 2.6.15-rt16
- From: Steven Rostedt <[email protected]>
- Re: 2.6.15-rt16
- References:
- 2.6.15-rt16
- From: chris <[email protected]>
- Re: 2.6.15-rt16
- From: Thomas Gleixner <[email protected]>
- Re: 2.6.15-rt16
- From: chris perkins <[email protected]>
- Re: 2.6.15-rt16
- From: Clark Williams <[email protected]>
- Re: 2.6.15-rt16
- From: chris perkins <[email protected]>
- Re: 2.6.15-rt16
- From: Clark Williams <[email protected]>
- Re: 2.6.15-rt16
- From: Steven Rostedt <[email protected]>
- Re: 2.6.15-rt16
- From: Clark Williams <[email protected]>
- Re: 2.6.15-rt16
- From: Steven Rostedt <[email protected]>
- 2.6.15-rt16
- Prev by Date: Re: CD writing in future Linux (stirring up a hornets' nest)
- Next by Date: Re: 100% cpu usage (kjournald, pdflush) with encrypted disks (dm-crypt)
- Previous by thread: Re: 2.6.15-rt16
- Next by thread: Re: 2.6.15-rt16
- Index(es):