mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: zajec5@gmail.com
Cc: bugme-daemon@bugzilla.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 11313] New: Plugging HDMI causes "unable to handle kernel paging request"
Date: Tue, 12 Aug 2008 14:44:06 -0700	[thread overview]
Message-ID: <20080812144406.0c8aff48.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-11313-10286@http.bugzilla.kernel.org/>


(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Tue, 12 Aug 2008 14:30:01 -0700 (PDT)
bugme-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=11313
> 
>            Summary: Plugging HDMI causes "unable to handle kernel paging
>                     request"
>            Product: Platform Specific/Hardware
>            Version: 2.5
>      KernelVersion: 2.6.27-rcX
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: high
>           Priority: P1
>          Component: x86-64
>         AssignedTo: platform_x86_64@kernel-bugs.osdl.org
>         ReportedBy: zajec5@gmail.com
>
> Latest working kernel version: 2.6.26

ugh.  Random rampant memory corruption caused by unplugging an HDMI
cable?  I'm not even sure which subsystem could be involved here.

Are you able to run a git bisection search please? 
http://www.kernel.org/doc/local/git-quick.html has some help.

Thanks.

       reply	other threads:[~2008-08-12 21:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11313-10286@http.bugzilla.kernel.org/>
2008-08-12 21:44 ` Andrew Morton [this message]
2008-08-12 21:59   ` Rafael J. Wysocki
2008-08-12 22:00     ` Rafał Miłecki

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=20080812144406.0c8aff48.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zajec5@gmail.com \
    /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®