LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: Pavel Machek <pavel@ucw.cz>,
	kernel list <linux-kernel@vger.kernel.org>,
	linux-ide@vger.kernel.org
Subject: Re: 2.6.26-git0: IDE oops during boot
Date: Thu, 7 Feb 2008 15:01:09 +0100	[thread overview]
Message-ID: <200802071501.09318.bzolnier@gmail.com> (raw)
In-Reply-To: <47AAD0CB.3090305@linux.vnet.ibm.com>


On Thursday 07 February 2008, Kamalesh Babulal wrote:
> Bartlomiej Zolnierkiewicz wrote:
> > Hi,
> > 
> > On Wednesday 06 February 2008, Pavel Machek wrote:
> >> On Wed 2008-02-06 11:53:34, Pavel Machek wrote:
> >>> Hi!
> >>>
> >>> Trying to boot 2.6.25-git0 (few days old), I get
> >>>
> >>> BUG: unable to handle kernel paging request at ffff..ffb0
> >>> IP at init_irq+0x42e
> > 
> > init_irq? hmm...
> > 
> >>> Call trace:
> >>> ide_device_add_all
> > 
> > this comes from ide-generic
> > (Generic IDE host driver)
> > 
> >>> ide_generic_init
> >>> kernel_init
> >>> child_rip
> >>> vgacon_cursor
> >>> kernel_init
> >>> child_rip
> >>>
> >>> Excerpt from config:
> >>>
> >>> CONFIG_IDE=y
> >>> CONFIG_BLK_DEV_IDE=y
> >> Disabling CONFIG_IDE made my machine boot, as it was using libata
> >> anyway.
> > 
> > Kamalesh/Pavel:
> > 
> > Could you try latest git and see if the OOPS is still there?
> > 
> > [ Yeah, I'm unable to reproduce it. :( ]
> > 
> > Thanks,
> > Bart
> Hi Bart,
> 
> The panic is reproducible with the 2.6.24-git16 kernel, the call trace is
> similar to the previous one

Thanks, I again reviewed ide-probe.c changes but nothing seems wrong...

Could you please bisect it down to the guilty commit?

> BUG: unable to handle kernel paging request at ffffffffffffffa0
> IP: [<ffffffff80415673>] init_irq+0x188/0x444

Please also try disassembling init_irq using gdb so we see where it fails.

Bart

> PGD 203067 PUD 204067 PMD 0 
> Oops: 0000 [1] SMP 
> CPU 3 
> Modules linked in:
> Pid: 1, comm: swapper Not tainted 2.6.24-git16 #1
> RIP: 0010:[<ffffffff80415673>]  [<ffffffff80415673>] init_irq+0x188/0x444
> RSP: 0000:ffff81022f093e00  EFLAGS: 00010282
> RAX: ffffffffffffff80 RBX: ffffffff808ad200 RCX: 0000000000000000
> RDX: 00000000ffffffff RSI: ffff81022fc039c0 RDI: ffffffff807512c0
> RBP: ffff81022f093e30 R08: ffff81022f093d70 R09: 0000000000000002
> R10: 0000000000000001 R11: ffff81022f093c00 R12: ffffffff808b4500
> R13: ffffffff808b4510 R14: 0000000000000000 R15: ffffffffffffffff
> FS:  0000000000000000(0000) GS:ffff81022f0e7ac0(0000) knlGS:0000000000000000
> CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
> CR2: ffffffffffffffa0 CR3: 0000000000201000 CR4: 00000000000006e0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Process swapper (pid: 1, threadinfo ffff81022f092000, task ffff81022f0797e0)
> Stack:  ffff81022f093e30 0000000000000000 ffffffff808ad200 ffffffff808ad220
>  ffffffff808add80 0000000000000000 ffff81022f093eb0 ffffffff8041648f
>  ffff81022f093ec0 0000000000000000 0000000080751ee0 0000000000000246
> Call Trace:
>  [<ffffffff8041648f>] ide_device_add_all+0xb60/0xe54
>  [<ffffffff807d6d48>] ide_generic_init+0x46/0x4a
>  [<ffffffff807b873b>] kernel_init+0x175/0x2e7
>  [<ffffffff8020bff8>] child_rip+0xa/0x12
>  [<ffffffff8037476c>] acpi_ds_init_one_object+0x0/0x88
>  [<ffffffff807b85c6>] kernel_init+0x0/0x2e7
>  [<ffffffff8020bfee>] child_rip+0x0/0x12
> 
> 
> Code: 89 03 49 8b 45 18 48 89 18 48 39 1b 75 04 0f 0b eb fe fe 05 20 71 38 00 fb eb 5b 48 8b 83 20 07 00 00 83 ca ff 48 83 c0 80 74 0e <48> 8b 40 20 48 8b 80 88 00 00 00 8b 50 04 48 8b 3d 48 11 30 00 
> RIP  [<ffffffff80415673>] init_irq+0x188/0x444
>  RSP <ffff81022f093e00>
> CR2: ffffffffffffffa0
> ---[ end trace 165798c72d52c3e3 ]---
> 
> 
> -- 
> Thanks & Regards,
> Kamalesh Babulal,
> Linux Technology Center,
> IBM, ISTL.

  reply	other threads:[~2008-02-07 13:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080206105334.GA3664@elf.ucw.cz>
2008-02-06 11:08 ` Pavel Machek
2008-02-06 20:05   ` Bartlomiej Zolnierkiewicz
2008-02-07  9:35     ` Kamalesh Babulal
2008-02-07 14:01       ` Bartlomiej Zolnierkiewicz [this message]
2008-02-10 21:32         ` Nish Aravamudan
2008-02-11  7:54           ` Kamalesh Babulal
2008-02-11 19:35             ` Bartlomiej Zolnierkiewicz
2008-02-12  9:04               ` Kamalesh Babulal
2008-02-13 23:00                 ` Bartlomiej Zolnierkiewicz
2008-02-14  9:46                   ` Kamalesh Babulal
2008-02-14 10:28                     ` Yinghai Lu
2008-02-15 11:15                       ` Kamalesh Babulal
2008-02-25  7:05                         ` Yinghai Lu
2008-02-25  7:23                           ` Yinghai Lu
2008-02-14 12:01                     ` "mount: could not find filesystem" - aacraid? (was: Re: 2.6.26-git0: IDE oops during boot) Bartlomiej Zolnierkiewicz
2008-02-14 12:07                       ` Bartlomiej Zolnierkiewicz
2008-02-14 15:47                         ` James Bottomley

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=200802071501.09318.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=kamalesh@linux.vnet.ibm.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --subject='Re: 2.6.26-git0: IDE oops during boot' \
    /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

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).