After upgrading to F8 I still had a dom0 crash last night, but didn't catch any output. I think it's still the null pointer dereference in tcp_tso_segment, possibly brought to prominence by traffic shaping in a busy domU. I'd like to catch a crash dump the next time it happens so I can (hopefully) intelligently report this bug somewhere. I'm looking at http://fedoraproject.org/wiki/FC6KdumpKexecHowTo http://www.redhatmagazine.com/2007/08/15/a-quick-overview-of-linux-kernel-crash-dump-analysis/ There is no mention of Xen. I don't see a kernel-xen-debuginfo rpm for f8 or even f7, but there is one for f9 in rawhide it appears. Is kernel-debuginfo sufficient even if running xen? The versions differ, so I would imagine not. # yum --enablerepo=fedora-debuginfo list kernel-xen-debuginfo kernel-debuginfo Available Packages kernel-debuginfo.x86_64 2.6.23.1-49.fc8 updates-debuginf # rpm -q kernel kernel-xen kernel-2.6.23.1-49.fc8 kernel-xen-2.6.21-2950.fc8 Any advice on how capture some useful info from a crashing dom0 kernel? -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 -- Fedora-xen mailing list Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen
