LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Matthew <jackdachef@gmail.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Fwd: Fwd: laptop / computer hardlocks during execution of 32bit applications(binaries) on 64bit system (Gentoo)
Date: Thu, 10 Jan 2008 10:42:19 +0100 [thread overview]
Message-ID: <20080110094219.GC17808@elte.hu> (raw)
In-Reply-To: <e85b9d30801100105s60ad675ey1ba939491d01a649@mail.gmail.com>
* Matthew <jackdachef@gmail.com> wrote:
> > I have been unable to reproduce your problem here, and I notice you have
> > the proprietary, highly invasive and closed-source Nvidia driver
> > installed in your kernel.
> >
> > Can you try using the "nv" or "vesa" (unaccelerated) Xorg drivers and
> > reproduce the problem that way?
> >
> > If you *do* reproduce the problem that way, it would be extremely
> > helpful if you could enable CONFIG_DEBUG_INFO and provide the vmlinux
> > (not vmlinuz/bzImage) file that goes with the crash dump screenshot.
> >
> > Thanks!
>
> I was able to reproduce it with removed nvidia module (rmmod nvidia) &
> nv driver, and will post the pictures later if I find some time (it
> was the same function if I recall right) do you also need:
> CONFIG_DEBUG_BUGVERBOSE enabled ?
really, that module does all sorts of nasty stuff when inserted (and
then removed), so just to make sure (because you are about to crash your
box again to take a picture), could you try to boot up without never
even once loading the nvidia module?
Ingo
next prev parent reply other threads:[~2008-01-10 9:42 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-29 19:57 Matthew
2007-12-29 23:04 ` Fwd: " Matthew
2007-12-30 0:28 ` Miguel Botón
2008-01-02 8:40 ` Ingo Molnar
[not found] ` <e85b9d30801080333y3d6668ccgf20f9666d0326884@mail.gmail.com>
2008-01-08 11:40 ` Fwd: " Matthew
2008-01-09 0:58 ` H. Peter Anvin
2008-01-10 9:05 ` Matthew
2008-01-10 9:42 ` Ingo Molnar [this message]
2008-01-10 12:43 ` Matthew
2008-01-10 12:48 ` Ingo Molnar
2008-01-10 12:59 ` Matthew
2008-01-10 13:24 ` Ingo Molnar
2008-01-10 13:08 ` Ed Tomlinson
2008-01-10 13:32 ` Ingo Molnar
2008-01-10 15:56 ` Matthew
2008-01-10 16:38 ` Ed Tomlinson
2008-01-10 23:35 ` Zan Lynx
2008-01-10 21:10 ` Matthew
2008-01-10 21:17 ` H. Peter Anvin
2008-01-10 21:52 ` Matthew
2008-01-10 21:57 ` H. Peter Anvin
2008-01-10 22:28 ` Matthew
2008-01-10 22:30 ` H. Peter Anvin
2008-01-10 22:53 ` Matthew
2008-01-14 16:13 ` Ingo Molnar
2008-01-14 16:47 ` Matthew
2008-01-14 17:00 ` Ingo Molnar
2008-01-14 22:16 ` Ed Tomlinson
2008-01-15 17:11 ` Matthew
2008-01-15 22:09 ` Ingo Molnar
2008-01-15 23:41 ` Ed Tomlinson
[not found] ` <20080108113820.GA16380@elte.hu>
2008-01-08 11:52 ` Matthew
2008-01-11 2:22 Fwd: " Ed Tomlinson
2008-01-14 16:16 ` Ingo Molnar
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=20080110094219.GC17808@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=jackdachef@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--subject='Re: Fwd: Fwd: laptop / computer hardlocks during execution of 32bit applications(binaries) on 64bit system (Gentoo)' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).