All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 13874] kenal panic on addition of xfx nvidia gts250 512mb on 946giz motherboard
Date: Thu, 6 Aug 2009 23:25:37 GMT	[thread overview]
Message-ID: <200908062325.n76NPbAp005496@demeter.kernel.org> (raw)
In-Reply-To: <bug-13874-13602@http.bugzilla.kernel.org/>

http://bugzilla.kernel.org/show_bug.cgi?id=13874


Andrew Morton <akpm@linux-foundation.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|ext3                        |x86-64
         AssignedTo|fs_ext3@kernel-bugs.osdl.or |platform_x86_64@kernel-bugs
                   |g                           |.osdl.org
            Product|File System                 |Platform Specific/Hardware




--- Comment #8 from Andrew Morton <akpm@linux-foundation.org>  2009-08-06 23:25:35 ---
I don't know where to reassign it, really.  Where's the bug?

A can randomly punt it in the x86_64 direction, but I suspect the hardware is
broken.

Does _any_ version of the linux kernel run properly on that particular machine?

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

      parent reply	other threads:[~2009-08-06 23:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-13874-13602@http.bugzilla.kernel.org/>
2009-08-04 17:05 ` [Bug 13874] kenal panic on addition of xfx nvidia gts250 512mb on 946giz motherboard bugzilla-daemon
2009-08-04 17:07 ` bugzilla-daemon
2009-08-04 20:17 ` bugzilla-daemon
2009-08-05 14:34 ` bugzilla-daemon
2009-08-05 17:06 ` bugzilla-daemon
2009-08-06 23:25 ` bugzilla-daemon [this message]

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=200908062325.n76NPbAp005496@demeter.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@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.