mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Andy Whitcroft <apw@shadowen.org>
Subject: Re: [BUG] linux-next: Tree for April 10 - kernel panic while loading ata driver on powermac
Date: Thu, 10 Apr 2008 23:55:26 +0530	[thread overview]
Message-ID: <47FE5B96.9090207@linux.vnet.ibm.com> (raw)
In-Reply-To: <200804101914.04254.bzolnier@gmail.com>

Bartlomiej Zolnierkiewicz wrote:
> On Thursday 10 April 2008, Bartlomiej Zolnierkiewicz wrote:
>> Hi,
>>
>> On Thu, Apr 10, 2008 at 12:24 PM, Kamalesh Babulal
>> <kamalesh@linux.vnet.ibm.com> wrote:
>>> Hi Stephen,
>>>
>>>  The next-20080410 kernel panics while bootup over the PowerMac G5 box, while
>>>  loading the ATA driver.
>>>
>>>  [    3.704000] Faulting instruction address: 0xc0000000000222a8
>>>  [    3.704000] Oops: Kernel access of bad area, sig: 11 [#1]
>>>  [    3.704000] SMP NR_CPUS=32 NUMA PowerMac
>>>  [    3.704000] Modules linked in:
>>>  [    3.704000] NIP: c0000000000222a8 LR: c00000000021cd10 CTR: 0000000000000100
>>>  [    3.704000] REGS: c0000002760db070 TRAP: 0300   Not tainted  (2.6.25-rc8-next-20080410-autokern1)
>>>  [    3.704000] MSR: 9000000000009032 <EE,ME,IR,DR>  CR: 44000042  XER: 20000000
>>>  [    3.704000] DAR: a0001000822fa000, DSISR: 0000000040000000
>>>  [    3.704000] TASK = c0000002760d7100[1] 'swapper' THREAD: c0000002760d8000 CPU: 0
>>>  [    3.704000] GPR00: 0000000000000100 c0000002760db2f0 c000000000498310 a0001000822fa000
>>>  [    3.704000] GPR04: c000000274806a00 0000000000000100 0000000000000201 c00000000000fed4
>>>  [    3.704000] GPR08: c0000002760daf20 c0000000003ee0d8 c0000000004f1428 0000000000000000
>>>  [    3.704000] GPR12: 0000000000000000 c0000000003fa700 0000000000000000 0000000000000000
>>>  [    3.704000] GPR16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
>>>  [    3.704000] GPR20: 0000000000000001 0000000000000027 0000000000000027 0000000000000000
>>>  [    3.704000] GPR24: c0000000004f1400 0000000000000000 0000000000000201 c0000000004f1490
>>>  [    3.704000] GPR28: a0001000822fa000 0000000000000200 c00000000044cf50 c000000274806a00
>>>  [    3.704000] NIP [c0000000000222a8] ._insw_ns+0x10/0x30
>>>  [    3.704000] LR [c00000000021cd10] .ata_input_data+0x1f4/0x264
>> Could you please add printk() for 'hwif->host_flags', 'mmio' and 'io_32bit'
>> to ide-iops.c::ata_input_data() so we know more on what is going on?
> 
> No longer needed - please test the hot-fix below instead:
> 
> ---
> thanks to Andrew for noticing me about the gcc warning
> 
>  drivers/ide/ppc/pmac.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> Index: b/drivers/ide/ppc/pmac.c
> ===================================================================
> --- a/drivers/ide/ppc/pmac.c
> +++ b/drivers/ide/ppc/pmac.c
> @@ -941,7 +941,7 @@ static const struct ide_port_info pmac_p
>  	.port_ops		= &pmac_ide_port_ops,
>  	.host_flags		= IDE_HFLAG_SET_PIO_MODE_KEEP_DMA |
>  				  IDE_HFLAG_POST_SET_MODE |
> -				  IDE_HFLAG_UNMASK_IRQS,
> +				  IDE_HFLAG_UNMASK_IRQS |
>  				  IDE_HFLAG_MMIO,
>  	.pio_mask		= ATA_PIO4,
>  	.mwdma_mask		= ATA_MWDMA2,
> 
> --
Thanks, the kernel panic is solved after applying the patch.

Tested-by: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.

  reply	other threads:[~2008-04-10 18:25 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-10  8:14 linux-next: Tree for April 10 Stephen Rothwell
2008-04-10 10:24 ` [BUG] linux-next: Tree for April 10 - kernel panic while loading ata driver on powermac Kamalesh Babulal
2008-04-10 10:45   ` Jeff Garzik
2008-04-10 11:02     ` Kamalesh Babulal
2008-04-10 11:32     ` Alan Cox
2008-04-10 12:14       ` Jeff Garzik
2008-04-10 12:03   ` Bartlomiej Zolnierkiewicz
2008-04-10 17:14     ` Bartlomiej Zolnierkiewicz
2008-04-10 18:25       ` Kamalesh Babulal [this message]
2008-04-10 19:16         ` Bartlomiej Zolnierkiewicz
2008-04-10 17:42 ` linux-next: Tree for April 10 Greg KH
2008-04-10 18:07 ` [BUG] linux-next: April 10 - kernel oops at kmem_cache_alloc () regression from April 9 kernel Kamalesh Babulal
2008-04-11 17:56   ` Suresh Siddha
2008-04-14 13:14     ` Kamalesh Babulal
2008-04-10 19:34 ` linux-next: Tree for April 10: generic pci_enable_resources() strikes again Mariusz Kozlowski
2008-04-14  1:48   ` Stephen Rothwell
2008-04-14  4:28     ` Greg KH
2008-04-14  4:49       ` Stephen Rothwell
2008-04-10 22:07 ` linux-next: Tree for April 10 (ftrace) Randy Dunlap
2008-04-10 22:09 ` linux-next: Tree for April 10 (arch/x86) Randy Dunlap
2008-04-11  7:46   ` Ingo Molnar
2008-04-11 15:19     ` Randy Dunlap
2008-04-11 15:26       ` Al Viro
2008-04-14  8:12         ` Ingo Molnar
2008-04-14  8:22           ` Al Viro
2008-04-14  8:34             ` Ingo Molnar
2008-04-14  8:43               ` Jakub Jelinek
2008-04-14  9:30                 ` Al Viro
2008-04-14  9:37                   ` David Miller
2008-04-14  8:40       ` Jakub Jelinek
2008-04-14 22:28         ` Randy Dunlap

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=47FE5B96.9090207@linux.vnet.ibm.com \
    --to=kamalesh@linux.vnet.ibm.com \
    --cc=apw@shadowen.org \
    --cc=bzolnier@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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

Powered by JetHome