All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 24702] Possible bug - crash during IDE interface probing.
Date: Sun, 12 Dec 2010 12:24:57 GMT	[thread overview]
Message-ID: <201012121224.oBCCOv1e012149@demeter2.kernel.org> (raw)
In-Reply-To: <bug-24702-11633@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=24702


Borislav Petkov <bp@alien8.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bp@alien8.de




--- Comment #1 from Borislav Petkov <bp@alien8.de>  2010-12-12 12:24:50 ---
Hi,

first of all, how did you update from .1 to .2? I'd like to rule out
the use of some stale .o objects from the 36.1 build. Can you copy
your .config to a safe place, do "make mrproper" and then copy it back
(mrproper removes the .config too) and then build 36.2 and try booting.

Then, if it crashes again, can you catch the oops somehow, provided
there is one? Either serial console, netconsole or if those are not an
option, make a readable photo of the oops and upload it to bugzilla.

Thanks.

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

  reply	other threads:[~2010-12-12 12:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-12  7:41 [Bug 24702] New: Possible bug - crash during IDE interface probing bugzilla-daemon
2010-12-12 12:24 ` bugzilla-daemon [this message]
2010-12-12 21:55 ` [Bug 24702] " bugzilla-daemon
2010-12-13 14:13 ` bugzilla-daemon
2010-12-17  8:47 ` bugzilla-daemon
2010-12-17  9:19 ` bugzilla-daemon
2010-12-20 21:11 ` bugzilla-daemon
2010-12-23  2:39 ` bugzilla-daemon

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=201012121224.oBCCOv1e012149@demeter2.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ide@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.