Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 10 Feb 2006 06:09:18 +0000
From:      Chris <chrcoluk@gmail.com>
To:        "Mars G. Miro" <marsgmiro@gmail.com>
Cc:        Geoffroy Desvernay <dgeo@dgeos.net>, freebsd-stable@freebsd.org, bug-followup@freebsd.org
Subject:   Re: i386/86880: [hang] 6.0 hangs or reboots whilst 5.4 is stable (ASUS-A7NX motherboard with nforce2 chipset)
Message-ID:  <3aaaa3a0602092209t53d228b4h@mail.gmail.com>
In-Reply-To: <28edec3c0602090517t6967bd88l16eb63207bd16ffd@mail.gmail.com>
References:  <28edec3c0602032049l3d258a5cx72efe2c2ba4b23aa@mail.gmail.com> <43E8E353.1090900@dgeos.net> <28edec3c0602071826t5b619al24f0a93c713b5d30@mail.gmail.com> <20060209131840.0pgsy7fs1s0ocos0@mail.dgeos.net> <28edec3c0602090517t6967bd88l16eb63207bd16ffd@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 09/02/06, Mars G. Miro <marsgmiro@gmail.com> wrote:
>
> On 2/9/06, Geoffroy Desvernay <dgeo@dgeos.net> wrote:
> > Quoting "Mars G. Miro" <marsgmiro@gmail.com>:
> >
> > > On 2/8/06, Geoffroy Desvernay <dgeo@dgeos.net> wrote:
> > >>
> > >> >>>I've got the same problem with an A7N8X-X (athlon 2000+)
> motherboard
> > and
> > >> >>>6-STABLE (Build Feb, 2 2006).
> > >> >>>booting with kernel.debug says nothing, seems to be hardware hang
> but
> > >> >>>doesn't happend with linux nor OpenBSD. Didn't tried 5.3 yet.
> > >> >>>Hang after detection of ATA devices (floppy's light turns on, the=
n
> > hang)
> > >> >
> > >> > I've experienced this myself. Happens w/ nForce-based mobos and
> > >> > certain shuttles. My fix has to always set the BIOS setting of the
> HD
> > >> > to LBA instead of Auto or CHS.
> > >> >
> > >> > Try this and report back ;-)
> > >> >
> > >> Tried this unsuccessfully, but fixing cpu freq to 100Mhz (instead of
> > >> 133Mhz) seems to work...
> > >>
> > >> I've read something about disabling firewire in the bios, but I have
> it
> > >> on a separate card (not in the MB), and I can't remove it for the
> > moment...
> > >>
> > >
> > > Also try disabling APIC (not ACPI) as I've encountered several mobos
> > > that have this implemented poorly w/c results in weird behaviors of
> > > the OS.
> > >
> > >> I'm not kernel developper, but I may try patches or ?
> > >>
> > >
> > > I'm not aware of any patches but I think this is just a hardware
> > > config problem tho YMMV.
> > >
> > Working at 133Mhz with hint.apic.0.disabled=3D"1" in looader.conf.
> >
> > Thanks for that :)
> >
>
> Actually, I was referring to disabling APIC in the BIOS, not in
> FreeBSD. But I'm glad that it works ;-)
>
> > I saw at http://acpi.sf.net/dsdt/view.php?id=3D233 that a dsdt specific
> > for this board is available... (not fixing all), could this fix
> > anything in my case ? I think I'll give a try on of these days...
> >
>
> That I have no clue ;-)
>
>
> > Geoffroy
> >
> > ----------------------------------------------------------------
> > This message was sent using IMP, the Internet Messaging Program.
> >
> >
> >
>
>
> cheers
> mars
> _______________________________________________


I noticed a few times now disabling acpi in 6.0 fixes some problems, but on
the same hardware acpi will work on 5.4 is this to do with i386 support bee=
n
removed or are there other acpi changes under the hood?

Chris



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3aaaa3a0602092209t53d228b4h>