On 31/05/06, Ingo Molnar <mingo@xxxxxxx> wrote:
* Michal Piotrowski <michal.k.k.piotrowski@xxxxxxxxx> wrote:
> > http://redhat.com/~mingo/lockdep-patches/latency-tracing-lockdep.patch
> >
> >just apply it ontop of your current tree and accept all the new .config
> >options as the kernel suggests them to you.
>
> I can't boot with that patch. I even don't see "Uncompressing
> Linux..." - machine reboots.
> I have 2.6.17-rc5-mm1 +
> genirq-cleanup-remove-irq_descp-fix.patch
> lock-validator-irqtrace-support-non-x86-architectures.patch
> lock-validator-special-locking-sb-s_umount-2-fix.patch
> from hot fixes
> +
> Arjan's net/ipv4/igmp.c patch.
could you try to 1) disable PREEMPT, 2) apply the -V2 rollup of all
fixes so far to 2.6.17-rc5-mm1:
http://redhat.com/~mingo/lockdep-patches/lockdep-combo-2.6.17-rc5-mm1.patch
I'll try to reproduce that bug now... but here is new one :)
BUG: key f7155db0 not in .data!
( modprobe-485 |#0): new 15286092 us user-latency.
stopped custom tracer.
BUG: warning at /usr/src/linux-mm/kernel/lockdep.c:1985/lockdep_init_map()
[<c0104208>] show_trace+0x1b/0x20
[<c01042e6>] dump_stack+0x1f/0x24
[<c0136e26>] lockdep_init_map+0x65/0xb0
[<c0134a62>] __mutex_init+0x46/0x50
[<f98b72a3>] find_driver+0xb7/0x115 [snd_seq_device]
[<f98b776f>] snd_seq_device_register_driver+0x42/0xeb [snd_seq_device]
[<f887012d>] alsa_seq_oss_init+0x12d/0x158 [snd_seq_oss]
[<c013fdad>] sys_init_module+0x96/0x1d4
[<c02eb442>] sysenter_past_esp+0x63/0xa1
---------------------------
| preempt count: 00000000 ]
| 0-level deep critical section nesting:
----------------------------------------
Here is dmesg
http://www.stardust.webpages.pl/files/mm/2.6.17-rc5-mm1/mm-dmesg3
Here is new config (without some debugging options)
http://www.stardust.webpages.pl/files/mm/2.6.17-rc5-mm1/mm-config4
? I'll try your config meanwhile.
Ingo
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)
-
: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
