OK, thanks.
>
> I'm still seeing the buffer layer error at fs/buffer.c:1623,
> though. Happens when a blockdev is close()d. Is a fix for
> this in -mm2? Does -mm2 include -bk5 ? If so I'll put that
> on it and keep an eye on it tomorrow, see what happens.
This is a blockdev which was under mmap(), yes? No, I haven't looked at
that yet. It'll be a matter of just killing the warning.
mmapping a blockdev is a pretty dopey thing to do, btw. It doesn't
allow the use of highmem, the IO uses tiny BIOs (in fact I think
it uses 512-byte or 1k blocksize too) and there are buffer_heads
all over the place. You'll get better results from mmapping a
regular file.
> Debug messages I'm still seeing:
> (note that I compiled IPv6 into the kernel since we're slowly moving
> our network to IPv6 but that it is otherwise unused right now, and
> that the previous kernels that crashed on me didn't have IPv6 in it)
>
> Uninitialised timer!
> This is just a warning. Your computer is OK
> function=0xc0285748, data=0xf78a6680
> Call Trace:
> [<c0122610>] check_timer_failed+0x40/0x54
> [<c0285748>] igmp6_timer_handler+0x0/0x58
> [<c0122b12>] del_timer+0x16/0x84
> [<c02855d8>] igmp6_join_group+0x94/0x124
I missed one there.
--- 25/net/ipv6/mcast.c~ip6-mcast-timer Sun Nov 10 09:12:28 2002
+++ 25-akpm/net/ipv6/mcast.c Sun Nov 10 09:12:44 2002
@@ -296,6 +296,7 @@ int ipv6_dev_mc_inc(struct net_device *d
}
memset(mc, 0, sizeof(struct ifmcaddr6));
+ init_timer(&mc->mca_timer);
mc->mca_timer.function = igmp6_timer_handler;
mc->mca_timer.data = (unsigned long) mc;
_
-
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/