On Thu, Aug 13, 2009 at 04:29:36PM -0600, Moritz Muehlenhoff wrote: > On Mon, Jan 26, 2009 at 05:02:32PM -0700, Will Aoki wrote: > > So far the bug has not manifested itself on > > linux-image-2.6.24-etchnhalf.1-686 2.6.24-6~etchnhalf7; however, I have > > had one unexplained crash. > > So, the appletalk issue seems fixed? Has the unexplained crash manifested > more often? Do you have reason to believe it's related to the appletalk > stack?
As the unexplained crash wrote nothing to the system log and nothing could be obtained from the console, I have no information to go on. The crash hasn't happend again, but then, I stopped running atalkd after the unexplained crash. The appletalk module is still loaded (although I'm not sure why, as nothing should have loaded it), but nothing is using it. Unfortunately, this doesn't say much either way. I've never been able to reproduce the problem on my test system, despite running AppleTalk on it for nine months now, and I'm not going to try AppleTalk again on the production server because the risk is no longer worth the reward. It's possible that the problem involves load -- if so, I'm not set up for load testing. If it's a hardware fault, it must be very subtle, as there are no other symptoms. If it involves an interaction with a driver not present on my test system, I'll have hardware available for testing in about a month that's identical to the production fileserver except for the storage controller, but it won't be available long before it's needed for another purpose, so I wouldn't hold your breath. AppleTalk was a nice-to-have feature but became less and less important as older Macintoshes were retired, so apart from the brief testing in December and January, I've not been using it on the problem system for two years. -- William Aoki KD7YAF wa...@umnh.utah.edu 5-1924 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
