public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Olivier Fourdan <fourdan@xfce.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Various issues after rebooting
Date: Mon, 28 Mar 2005 22:10:14 +0200	[thread overview]
Message-ID: <1112040614.6626.24.camel@shuttle> (raw)
In-Reply-To: <20050328193921.GW30052@alpha.home.local>

Hi Willy,

On Mon, 2005-03-28 at 21:39 +0200, Willy Tarreau wrote:
> Sorry, at first I only noticed ACPI in your mail, but after reading it
> again, I also noticed APIC. So now, you can only try not to initialize
> some peripherals (IDE, network, display, etc...) by removing their drivers
> from the kernel. You may end up with a kernel panic, but that does not
> matter is you boot it with "panic=5" so that it automatically reboots
> 5 seconds after the panic. You should then finally identify the subsystem
> which is responsible for your problems. Perhaps you'll even need to remove
> PCI support :-(

Well, actually, the system runs (at least) unless I try to load
"ndiswrapper" which leads to a kernel panic.

I tried to bring the issue to the ndiswrapper ML but I doubt that
ndiswrapper is faulty.

I can reliably predict the crash. If the clock (and all other time based
events) are too fast, then modprobing ndiswrapper will lead to a system
crash, just like mounting a CDROM will fail.

I think the clock speed and other effects are just signs, not the cause
of the problem. What I'd like to determine is what would need to be done
to avoid the root cause, or maybe if there is anything that can be done
in Linux to avoid that?

I just tried "acpi_fake_ecdt" but that leads to a immediate kernel
panic.

Ps: Given the crash (Machine check exception), the sleep option seems to
have no effect.

Thanks,
Olivier.





  reply	other threads:[~2005-03-28 20:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-28 19:56 Various issues after rebooting Olivier Fourdan
2005-03-28 19:20 ` Willy Tarreau
2005-03-28 19:30   ` Olivier Fourdan
2005-03-28 19:39     ` Willy Tarreau
2005-03-28 20:10       ` Olivier Fourdan [this message]
2005-03-29 21:28       ` Clock 3x too fast on AMD64 laptop [WAS Re: Various issues after rebooting] Olivier Fourdan
2005-03-29 22:02         ` Olivier Fourdan
2005-03-29 22:11           ` Dominik Brodowski
2005-03-29 22:11           ` john stultz
2005-03-31 19:12             ` Olivier Fourdan

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=1112040614.6626.24.camel@shuttle \
    --to=fourdan@xfce.org \
    --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