From: dth@picard.cistron.nl (Danny ter Haar)
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rcX really this bad ?
Date: Sun, 14 Aug 2005 17:02:49 +0000 (UTC) [thread overview]
Message-ID: <ddntfp$a6p$1@news.cistron.nl> (raw)
In-Reply-To: <20050814123007.GA647@mipter.zuzino.mipt.ru>
Alexey Dobriyan <adobriyan@gmail.com> 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.
> dth@picard.cistron.nl
>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
dth@cistron.nl
prev parent reply other threads:[~2005-08-14 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-14 10:10 Danny ter Haar
2005-08-14 11:43 ` Alexander Nyberg
2005-08-14 12:30 ` Alexey Dobriyan
2005-08-14 17:02 ` Danny ter Haar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ddntfp$a6p$1@news.cistron.nl' \
--to=dth@picard.cistron.nl \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome