linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: Dominik Brodowski <linux@dominikbrodowski.net>,
	linux-ide@vger.kernel.org, linux-pcmcia@lists.infradead.org
Subject: Re: 2.6.27-rc3: IP: [<ffffffffa0038b77>] init_irq+0x18d/0x31c	[ide_core]
Date: Thu, 21 Aug 2008 12:34:59 -0500	[thread overview]
Message-ID: <48ADA743.1070000@lwfinger.net> (raw)
In-Reply-To: <20080821161610.GA2640@deprecation.cyrius.com>

Martin Michlmayr wrote:
> * Larry Finger <Larry.Finger@lwfinger.net> [2008-08-20 14:34]:
>> Please do the following, which will require the package containing  
>> objdump. First of all, do the command
>>
>> objdump -d -l drivers/ide/ide-core.o > ide_core.dump
>>
>> Next, open ide_core.dump with less or your favorite editor and search for 
>> the start of init_irq. Note that address. Add your offset of 0x18D to that 
>> value and find the instruction at that address. Move up in the file until 
>> you find a line that looks like
>> /home/finger/linux-2.6/drivers/ide/ide-probe.c:1054
> 
> Hey Larry,
> 
> The dump file doesn't contain any line numbers.  See the attached
> file.

I think the error is in hwif_to_node with dev set to NULL in the 
dereference of dev->bus. This inline routine is called from the 
following code fragment from ide-probe.c:

         if (match) {
                 hwgroup = match->hwgroup;
                 hwif->hwgroup = hwgroup;
                 /*
                  * Link us into the hwgroup.
                  * This must be done early, do ensure that 
unexpected_intr
                  * can find the hwif and prevent irq storms.
                  * No drives are attached to the new hwif, choose_drive
                  * can't do anything stupid (yet).
                  * Add ourself as the 2nd entry to the hwgroup->hwif
                  * linked list, the first entry is the hwif that owns
                  * hwgroup->handler - do not change that.
                  */
                 spin_lock_irq(&ide_lock);
                 hwif->next = hwgroup->hwif->next;
                 hwgroup->hwif->next = hwif;
                 BUG_ON(hwif->next == hwif);
                 spin_unlock_irq(&ide_lock);
         } else {
                 hwgroup = kmalloc_node(sizeof(*hwgroup), 
GFP_KERNEL|__GFP_ZERO,
                                        hwif_to_node(hwif));

The line above triggers the fault.

I don't know enough about the code to figure the rest out, but I 
expect that the experts will.

Did this work with precious versions? If so, it should be posted as a 
regression.

Larry


  parent reply	other threads:[~2008-08-21 17:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-20 17:31 2.6.27-rc3: IP: [<ffffffffa0038b77>] init_irq+0x18d/0x31c [ide_core] Martin Michlmayr
2008-08-20 19:34 ` Larry Finger
     [not found]   ` <20080821161610.GA2640@deprecation.cyrius.com>
2008-08-21 17:34     ` Larry Finger [this message]
2008-08-21 17:52       ` Martin Michlmayr
2008-08-21 17:57         ` Larry Finger
2008-08-25 11:02           ` Martin Michlmayr
2008-08-25 19:11             ` Bartlomiej Zolnierkiewicz
2008-08-26  5:17               ` Martin Michlmayr

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=48ADA743.1070000@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-pcmcia@lists.infradead.org \
    --cc=linux@dominikbrodowski.net \
    --cc=tbm@cyrius.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;
as well as URLs for NNTP newsgroup(s).