On Mon, Dec 01, 2008 at 10:16:27AM -0700, waoki wrote: > I've turned off AppleTalk on the problem system because of this bug, so > I'm not sure if it will still happen with 2.6.18-6-686, and even though > the oops didn't affect other aspects of the system's operation, I'd > rather not try it on my production file server. I'll try it on a test > system now and get back to you in a few weeks (it may take a while > before it oopses). > > I can't guarantee that failure to reproduce it on 2.6.18-6-686 on my > test system means it won't happen on 2.6.18-6-686 on the machine that > was having problems, but if it runs cleanly on the test system, I may > risk it on the production system over the holiday break.
I've not been able to reproduce the problem on a test system, but it took less than sixteen hours for an oops to occur on linux-image-2.6.18-6-686 2.6.18.dfsg.1-23etch1 on my production system. The oops takes down AppleTalk but does not break other parts of the system. I'll prepare to put the 2.6.24 kernel into production and try with it. -- William Aoki KD7YAF wa...@umnh.utah.edu 5-1924 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
