mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Roland" <devzero@web.de>
To: <j.dierks@Verizon.net>
Cc: <linux-kernel@vger.kernel.org>, <jj@chaosbits.net>
Subject: Re: kernel bug in openSUSE 11.1 64 bit
Date: Tue, 30 Dec 2008 14:14:17 +0100	[thread overview]
Message-ID: <004501c96a80$85357100$0201a8c0@bui.materna.com> (raw)

Hello John,

do you see any relation to this one ?
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/279186

do you use the latest bios for that board?
if not,maybe you could try if that helps ?

regards
Roland




List:       linux-kernel
Subject:    kernel bug in openSUSE 11.1 64 bit
From:       John Dierks <j.dierks () Verizon ! net>
Date:       2008-12-28 22:14:12
Message-ID: 4957FA34.1050501 () Verizon ! net
[Download message RAW]

Greetings -

I am a newbie and not familiar with the accepted way of posting bugs,
so I am simply sending you a link to the appropriate forum discussion.

I believe we have a kernel bug in the released version of openSUSE 11.1
(64 bit).

I have confirmed what another user (ansbar) found:  Any attempt to
install 64 bit
11.1 from DVD or NET media onto a D945GCLF2 platform results in a
kernel oops soon after the version of kernel supplied with the distribution
loads and runs.

As an aside, the platform I attempted to upgrade currently is running
11.0 (64 bit),
which has been running without any evidence of problems.

I hope the discussion gives you enough info to go on.  If not, feel free to
ask questions.  Here's the link:


http://forums.opensuse.org/install-boot-login/402136-kernel-panic-11-1-64bit.html

Thanks,
John Dierks
--




             reply	other threads:[~2008-12-30 13:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-30 13:14 Roland [this message]
2009-01-01 17:52 ` John Dierks
  -- strict thread matches above, loose matches on Subject: below --
2008-12-28 22:14 John Dierks
2008-12-28 22:57 ` Jesper Juhl

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='004501c96a80$85357100$0201a8c0@bui.materna.com' \
    --to=devzero@web.de \
    --cc=j.dierks@Verizon.net \
    --cc=jj@chaosbits.net \
    --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

all inboxes | Powered by JetHome®