All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Ville Herva <vherva@niksula.hut.fi>
Cc: linux-kernel@vger.kernel.org, tejun@aratech.co.kr
Subject: Re: 2.4.22pre8 hangs too (Re: 2.4.21-jam1 solid hangs)
Date: Wed, 27 Aug 2003 12:56:33 +0200	[thread overview]
Message-ID: <20030827125633.45f9a003.skraw@ithnet.com> (raw)
In-Reply-To: <20030827101313.GX83336@niksula.cs.hut.fi>

On Wed, 27 Aug 2003 13:13:13 +0300
Ville Herva <vherva@niksula.hut.fi> wrote:

> On Wed, Aug 27, 2003 at 11:30:27AM +0200, you [Stephan von Krawczynski]
> wrote:
> > 
> > Hm, did you try a serial console? On my side this was a big step forward.
> 
> Do you mean in your case nothing shown on monitor (I've disabled monitor
> blanking, so that is not it), sysrq key didn't work, nmi watchdog didn't
> trigger but you were still able to get output from serial console? An oops?

I often have X setups, so console output gets _somewhere_ in the background.

> Or, did you use kdb/kgdb in addition to serial console?

No.

> > What does your /proc/interrupts look like compared between 2.2 and 2.4 ?
> 
> I don't have 2.2 output at hand, but the 2.4.21-jam1 output doesn't seem too
> suspicious:

You're right, it looks pretty clean and simple. Possibly the only thing I would
try is moving aic away from int 9 to int 10 or so. Int 9 sometimes interferes
with VGA int routing on broken boxes. But that is unlikely (though simple to
test).

Regards,
Stephan


  reply	other threads:[~2003-08-27 10:56 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-29  7:39 2.4.21-jam1, aic7xxx-6.2.36: solid hangs, crashes on boot Ville Herva
2003-07-30  7:13 ` 2.4.22pre8 hangs too (Re: 2.4.21-jam1, aic7xxx-6.2.36: solid hangs) Ville Herva
2003-07-30 14:50   ` Marcelo Tosatti
2003-07-30 18:10     ` Ville Herva
2003-08-08 12:55       ` Ville Herva
2003-08-09 20:19         ` Adrian Bunk
2003-08-09 22:15           ` Ville Herva
2003-08-27  6:43       ` 2.4.22pre8 hangs too (Re: 2.4.21-jam1 " Ville Herva
2003-08-27  7:03         ` Stephan von Krawczynski
2003-08-27  7:12           ` Ville Herva
2003-08-27  7:21             ` Stephan von Krawczynski
2003-08-27  7:37               ` Ville Herva
2003-08-27  9:30                 ` Stephan von Krawczynski
2003-08-27 10:13                   ` Ville Herva
2003-08-27 10:56                     ` Stephan von Krawczynski [this message]
2003-08-27 11:04                       ` Ville Herva
2003-08-27 11:30                         ` Stephan von Krawczynski
2003-08-28  9:26                           ` Ingo Oeser
2003-08-28 19:09                             ` Ville Herva
2003-08-28  1:13                 ` TeJun Huh
2003-08-28  5:40                   ` Ville Herva
2003-08-28  5:57                     ` Tejun Huh
  -- strict thread matches above, loose matches on Subject: below --
2003-08-27 23:22 Marcelo Tosatti
2003-08-28  6:10 ` Ville Herva
2003-08-29 16:35 Marcelo Tosatti
2003-08-29 19:57 ` Ville Herva
2003-09-09  7:05   ` Ville Herva
2003-09-09  8:48     ` Stephan von Krawczynski

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=20030827125633.45f9a003.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tejun@aratech.co.kr \
    --cc=vherva@niksula.hut.fi \
    /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.