From: "Maykel Moya" <mike@icc-cuba.com>
To: <linux-kernel@vger.kernel.org>
Subject: Asus CUV4X crashed at boot
Date: Sat, 5 Oct 2002 17:23:43 -0400 [thread overview]
Message-ID: <03ee01c26cb5$83dd1620$1401010a@icccuba.com> (raw)
Searching through archives founded problems respect to CUV4X-* mainboards
booting 2.4.x kernels. The messages I did found are about mid 2001, where 2.4.3
was in the throne.
I have an Asus CUV4X board, my linux crash while booting, tested with 2.4.19 and
2.4.20-pre8. Taking the advise from those all messages I booted with 'noapic'
but then my second NIC wheren't not correctly. initialized.
I think although noapic "ensures" booting, probably introduces later problems.
<copy from="ancient_message">
On Tue, Apr 03, 2001 at 10:40:36AM +1200, Simon Garner wrote
> 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*
Patience is likely to be effective. The chipset isn't exactly rare
being on SMP boards from Gigabyte, MSI, Tyan and Asus, and likely
others. I'm betting it will be fixed soon enough. UP and 2.2.x
kernels worked fine here if you're really desperate. OTOH, the
board is stable once you get past the boot problems... What sort
of production system needs frequent unattended boots?
Sorry about this, I just don't remember signing any paychecks for
what I know is likely to be a non-issue probably before the next
time I actually have to do something drastic, like reboo
</copy>
I would like to know if anyone is enduring this problem and if it's currently
addressed on -ac tree.
My system (Asus CUV4X, 2.4.19 or 2.4.20-pre8, UP P3 600MHz)
Regards,
Maykel Moya
next reply other threads:[~2002-10-05 21:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-05 21:23 Maykel Moya [this message]
2002-10-05 23:23 ` Asus CUV4X crashed at boot Alan Cox
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='03ee01c26cb5$83dd1620$1401010a@icccuba.com' \
--to=mike@icc-cuba.com \
--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