From: "Simon Garner" <sgarner@expio.co.nz>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Asus CUV4X-D, 2.4.3 crashes at boot
Date: Tue, 3 Apr 2001 10:40:36 +1200 [thread overview]
Message-ID: <011f01c0bbc5$ffc92e60$1400a8c0@expio.net.nz> (raw)
In-Reply-To: <E14kCnK-0006pa-00@the-village.bc.nu>
From: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
> > I've seen the exact same behavior with my CUV4X-D (2x1GHz) under
> > 2.4.2 (debian woody). In addition, the kernel would sometimes hang
> > around NMI watchdog enable. At least, I think it's trying to
>
> Known problem. Thats one reason why -ac trees had nmi watchdog turned off.
It still crashes with nmi_watchdog turned off.
Running with noapic fixes it but then the system crashes if you access the
RTC with hwclock (and probably creates a hundred other problems...).
How can I get this chipset/motherboard supported properly under Linux? I'm
happy to test patches etc. on the box. *pleading*
Cheers
Simon Garner
next prev parent reply other threads:[~2001-04-02 22:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-01 4:15 Asus CUV4X-D, 2.4.3 crashes at boot Simon Garner
2001-04-01 5:13 ` Allen Campbell
2001-04-01 9:18 ` Simon Garner
2001-04-01 9:47 ` Allen Campbell
2001-04-02 22:27 ` Alan Cox
2001-04-02 22:40 ` Simon Garner [this message]
2001-04-03 6:47 ` Allen Campbell
2001-04-03 6:53 ` Simon Garner
-- strict thread matches above, loose matches on Subject: below --
2001-04-01 9:55 Mikael Pettersson
2001-04-01 10:04 Simon Garner
2001-04-01 10:09 ` David Weinehall
2001-04-01 12:51 ` Keith Owens
2001-04-01 23:49 ` Simon Garner
[not found] <Pine.LNX.3.96.1010401185932.6155D-100000@mandrakesoft.mandrakesoft.com>
2001-04-02 0:48 ` Simon Garner
2001-04-02 2:57 ` Simon Garner
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='011f01c0bbc5$ffc92e60$1400a8c0@expio.net.nz' \
--to=sgarner@expio.co.nz \
--cc=alan@lxorguk.ukuu.org.uk \
--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 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.