Dave Jones - Thu, Jun 02 2005 15:01:20 -0400:
On Thu, Jun 02, 2005 at 08:55:40PM +0200, Christoph Franke wrote:
Dave Jones - Thu, Jun 02 2005 14:25:48 -0400:
Is it repeatable ? Does it behave again if you boot with exec-shield=0 ? or exec-shield-randomize=0 ?
Yes, it is repeatable, teamspeak segfaults on every start. Ntpd segfaults on both build -30 and -31 during boot, but can be restarted afterwards. Will try a boot with exec-shield=0 tomorrow morning and pass through the results.
Ok.
Ok, I did a reboot with parameter exec-shield=0 and teamspeak started right away. Ntpd is unchanged, here is the output
3 Jun 06:29:10 ntpd[4293]: synchronized to 192.53.103.104, stratum 1 3 Jun 06:46:04 ntpd[4293]: synchronized to 192.53.103.103, stratum 1 3 Jun 07:15:59 ntpd[4293]: ntpd exiting on signal 15 3 Jun 07:18:40 ntpd[3066]: signal_no_reset: signal 17 had flags 4000000 3 Jun 07:18:42 ntpd[3066]: signal_no_reset: signal 14 had flags 4000000
A restart though works as already mentioned.
Besides: may I ask if your plans to release a 2.6.12 kernel rpm for FC3 are stil valid?
Sure, but from the looks of things, thats still a way into the future, so I'd expect to see antoher 2.6.11 based errata for FC3 first. Upstream still seems a few weeks off (I've heard a few rumours about a -rc6 being planned). FC4 will get a rebase to 2.6.12, and a week or so later (if all goes well), I'll do a backport of the FC4 kernel (minus bits like Xen) to FC3, and see what breaks.
Ok. Thanks in advance.
Christoph