On Tuesday, 13 June 2000, Alan Cox wrote:
> > anywhere from 4-24 hours after boot) started after we added autofs and
> > NIS client functionality to our system profiles. When we were not
> > using NIS and were mounting filesystems manually at boot, we were not
> > having any such problems.
>
> Amuse me. Turn off autofs for a while and see if that stops it. How
> many boxes are affected and are the oopses basically identical
The oopses are identical across all the boxes, AFAIK. Essentially,
any box that we've tried rolling out this new kickstart profile onto
(which includes the NIS client and autofs client functionality) has
this problem. We're doing a limited rollout right now (about 10 boxes
out of our 100+ set) to protect ourselves.
I will turn off autofs and use manual mounts for 24 hours and report
back with the results.
As I'm certain you can understand, with these constant oopses, we're
being paged all hours of the day and night to manually reboot our
systems, and it's driving us crazy and holding product rollouts back
while we try to debug the problem.
> > keyboard: Too many NACKs -- noisy kbd cable?
> > keyboard: Too many NACKs -- noisy kbd cable?
>
> USB keyboard in bios emulation mode ?
No keyboard plugged in at all.
-- Michael S. Fischer <michael@auctionwatch.com> Operations Team Lead, AuctionWatch.com Phone: +1 650 808 5842 FAX: +1 650 875 0915 "From the bricks of shame is built the hope" --Alan Wilder- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Jun 15 2000 - 21:00:30 EST