All of lore.kernel.org
 help / color / mirror / Atom feed
From: Danny ter Haar <dth@cistron.nl>
To: Andrew Morton <akpm@osdl.org>
Cc: Danny ter Haar <dth@cistron.nl>,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: 2.6.14-rc2-git7 crashed on amd64 (usenet gateway) after 18 hours
Date: Fri, 30 Sep 2005 09:39:58 +0200	[thread overview]
Message-ID: <20050930073958.GA24985@dth.net> (raw)
In-Reply-To: <20050930001301.08eeab9d.akpm@osdl.org>

Quoting Andrew Morton (akpm@osdl.org):
> So we've probably lost the info which will tell us how the problems
> started.  A serial console would be nice.


This is from serial console.
Unfortunatly it's a portmaster2 which has no buffer.
What i do is start a screen, do a telnet to the portmaster
and attach the serial console. I can't go back anyfurther
than this since the output of the new kernel booting replaced it.
Mayby i can tell screen to have more lines of history ?! 

> Are all the failures due to the aic79xx driver failing in this manner?  If
> not then please report the different failures separately, thanks.

So far, all new kernels indeed barfed with scsi errors.
It somehow seems to miss a scsi event and a chain of events occur
which also sometimes lead to shutdown ethernet interfaces.

This is the difference in IRQ settings i talked about earlier:

Linux 2.6.14-rc2-git7 (root@newsgate) (gcc 4.0.2 ) #1 1CPU
irq  0:   3736032 timer                 irq 12:         3
irq  1:         8 i8042                 irq 16:   4519576 aic79xx
irq  4:       449 serial                irq 17:  34901765 aic79xx, eth3
irq  9:         0 acpi                  irq 18:  89100231 acenic

vs

Linux 2.6.12-mm1 (root@newsgate) (gcc 3.3.6 ) #1 Mon Jun 20 11:13:18 CEST 2005 1CPU [newsgate.(none)]
irq  0:   3822422 timer                 irq 12:         3
irq  1:         8 i8042                 irq 16:  82787217 acenic
irq  4:       353 serial                irq 17:   4194166 aic79xx
irq  9:         0 acpi                  irq 18:  28628408 aic79xx, eth3





-- 
Police aren't effective because of their uniforms, badges, guns, or
nightsticks, they're effective because of their radios [seen on /.]

  reply	other threads:[~2005-09-30  7:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-30  6:54 2.6.14-rc2-git7 crashed on amd64 (usenet gateway) after 18 hours Danny ter Haar
2005-09-30  7:13 ` Andrew Morton
2005-09-30  7:13   ` Andrew Morton
2005-09-30  7:39   ` Danny ter Haar [this message]
2005-09-30 12:44     ` Sander
2005-09-30 16:22       ` Danny ter Haar
2005-09-30 11:33   ` Danny ter Haar
2005-09-30 13:04     ` Jens Laas
2005-10-04 10:47       ` Age Strand

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=20050930073958.GA24985@dth.net \
    --to=dth@cistron.nl \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.