mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zwane Mwaikambo <zwane@arm.linux.org.uk>
To: Mike <Mike@kordik.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.1-mm5, kernel panic "Interrupt not syncing"
Date: Sun, 25 Jan 2004 20:58:57 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0401252057080.1741@montezuma.fsmlabs.com> (raw)
In-Reply-To: <pan.2004.01.26.01.32.38.822806@kordik.net>

On Sun, 25 Jan 2004, Mike wrote:

> >> > I have run 2.6.0-test.* kernels, 2.6.1-mm1 and 4 and they all boot
> >> > fine. When I go to 2.6.1-mm5 I get a kernel panic and the boot
> >> > freezes. The messages go by so quick I can't tell at what point it is
> >> > doing this but the last line is interrupt not syncing. Any ideas? I
> >> > have gone back to 2.6.1-mm4 so I can boot but I was interested in mm5
> >> > because it has ALSA 1.01 and I was hoping that would solve my lockup
> >> > when I got to a web page with a lot of flash problem but not being
> >> > able to boot is even worse. :-)
> >> >
> >> > Any ideas on the problem or advice on how to debug this would be most
> >> > appreciated.
> >> >
> >> > Mike
> >> No ideas? I can wait to try a newer kernel but I am concerned that the
> >> 20 or so kernels I used before booted without problems then all of a
> >> sudden 2.6.1-mm5 does not. Should I just ignore the problem and try a
> >> newer kernel? Is anyone else using 2.6.1-mm5 successfully?

Ok i've got a few things for you to try, first try 2.6.1-mm5 without
CONFIG_PREEMPT and then if that still fails, could you please try
2.6.2-rc1 and if that works, 2.6.2-rc1-mm3

Good luck
	Zwane


  reply	other threads:[~2004-01-26  1:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-23 14:58 Mike
2004-01-25 13:51 ` Mike
2004-01-25 15:24   ` Zwane Mwaikambo
2004-01-26  1:32     ` Mike
2004-01-26  1:58       ` Zwane Mwaikambo [this message]
2004-01-26  2:56         ` Mike

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=Pine.LNX.4.58.0401252057080.1741@montezuma.fsmlabs.com \
    --to=zwane@arm.linux.org.uk \
    --cc=Mike@kordik.net \
    --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

all inboxes | Powered by JetHome®