I have the same problem... however, my computer won't actually reboot. Lately, I have noticed that I am getting the following error at boot: 'Spurious 8259A interrupt: IRQ7', which has been labeled as a minor kernel bug as of 2.4.10 (I think?!). General opinion is that it is of no consequence (Alan Cox), but... I have to shut my computer off after I reboot in order to bring my OS back up. A minor inconvenience, but an inconvenience nonetheless... all hardware is very new, my NIC is a RealTek 8139... even if I shut down my network interface manually, my computer still freezes on reboot... any suggestions would be greatly appreciated.
- James On Sat, 2001-11-10 at 23:07, Ron Brown wrote: > Does Debian ever actually deconfigure network interfaces upon halt or > reboot? My Debian testing gives the following: > > $ ls /etc/rc?.d/*networking > /etc/rc0.d/S35networking /etc/rc6.d/S35networking > /etc/rcS.d/S40networking > > Looking at the list output above, there are no symlinks to 'kill' > the network interfaces (/etc/rc0.d/KXXnetworking etc.). That is, > "ifdown -a" never gets executed for my system to bring down the > interfaces. > > I was testing 2.4.13-ac8 kernel and was getting plenty of > "eth0: too much work at interrupt, intrstatus = 0x0001" -messages > when shutting down. My first reaction was to think that the kernel > itself was broken, and that may well be the case. However, running > "ifdown -a" before shutdown solved this, and there were no more > messages like that. > > [EMAIL PROTECTED] > > > --
