Linux PARISC architecture development
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: John David Anglin <dave.anglin@nrc-cnrc.gc.ca>
Cc: linux-parisc@vger.kernel.org, 622997@bugs.debian.org
Subject: Re: Debian bug 622997
Date: Sun, 17 Apr 2011 22:22:36 -0500	[thread overview]
Message-ID: <1303096956.2583.25.camel@mulgrave.site> (raw)
In-Reply-To: <20110418012519.GA25505@hiauly1.hia.nrc.ca>

On Sun, 2011-04-17 at 21:25 -0400, John David Anglin wrote:
> This is excellent detective work.  If I might ask, how did you trace
> the module loads and successful inits?

Heh, you're expecting me to name magic tracing tools?  Well (shuffles
feet) I just put printks in kernel/modules.c to do it.  It's basically
impossible to trace a boot problem like this any other way, because we
don't have enough of the system up to use any tools.

James



  reply	other threads:[~2011-04-18  3:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-16 18:07 Debian bug 622997 John David Anglin
2011-04-16 18:57 ` James Bottomley
2011-04-16 19:22   ` Bug#622997: " Ben Hutchings
2011-04-17  2:50     ` John David Anglin
2011-04-16 19:29   ` John David Anglin
2011-04-16 20:48     ` James Bottomley
2011-04-16 21:14       ` James Bottomley
2011-04-16 23:35         ` John David Anglin
2011-04-17  4:57           ` James Bottomley
2011-04-17 15:11             ` John David Anglin
2011-04-17 15:23               ` James Bottomley
2011-04-17 17:06                 ` John David Anglin
2011-04-17 19:28                 ` James Bottomley
2011-04-17 19:37                   ` Bug#622997: " Ben Hutchings
2011-04-17 23:33                     ` James Bottomley
2011-04-18  1:25                   ` John David Anglin
2011-04-18  3:22                     ` James Bottomley [this message]
2011-04-18  3:51                     ` Grant Grundler

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=1303096956.2583.25.camel@mulgrave.site \
    --to=james.bottomley@hansenpartnership.com \
    --cc=622997@bugs.debian.org \
    --cc=dave.anglin@nrc-cnrc.gc.ca \
    --cc=linux-parisc@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