Alexey Dobriyan <[EMAIL PROTECTED]> wrote: >> Is the machine running X? We need some output from it so we can debug >> what's going on, the info should be printed to the console. It would >> be great if you could run the latest kernel and see if you get any >> output. Also add nmi_watchdog=2 to the boot command line.
No, it's not running X. It's running debian (amd64) I allready posted more details http://newsgate.newsserver.nl/kernel/ including problems with SCSI. _my_ guess it's an IRQ problem (acpi related) ? >> You can also set up a serial console or netconsole to capture the output >> from the server with the help of another machine, described in >> Documentation/serial-console.txt >> Documentation/networking/netconsole.txt As stated before, it's connected to a sercon, but not with capture capabilities. I've a program that captured a few panics/resets >Danny, could you please go to http://bugme.osdl.org/show_bug.cgi?id=4982 >and fill new info there. I certainly will! >Alexander, could you please forward this email to Danny if you don't get >bounces from him. I got this when tried to reply that his bug was sucked >into bugzilla. > [EMAIL PROTECTED] >Technical details of permanent failure: >TEMP_FAILURE: Could not initiate SMTP conversation with any hosts: >[bitbucket.cistron.nl (100): Connection timed out] Ouch, wil look into this ... Danny [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/