On Fri, 2015-12-18 at 09:52 -0400, Julian Margetson wrote:
> On 12/18/2015 8:45 AM, Måns Rullgård wrote:
> > Julian Margetson <runaway@xxxxxxxx> writes:
> > > > > [ 4.784199] sata-dwc 4bffd1000.sata: id 0, controller
> > > > > version 1.82
> > > > > [ 4.791186] scsi host0: sata-dwc
> > > > > [ 4.794830] ata1: SATA max UDMA/133 irq 36
> > > > > [ 4.799463] sata_sil 0001:00:04.0: Applying R_ERR on DMA
> > > > > activate FIS errata fix
> > > > > [ 4.807959] scsi host1: sata_sil
> > > > > [ 4.811662] scsi host2: sata_sil
> > > > > [ 4.815242] ata2: SATA max UDMA/100 mmio m512@0xd84280000
> > > > > tf 0xd84280080 irq 21
> > > > > [ 4.822990] ata3: SATA max UDMA/100 mmio m512@0xd84280000
> > > > > tf 0xd842800c0 irq 21
> > > > >
> > > > > [ 5.143502] ata1: SATA link up 3.0 Gbps (SStatus 123
> > > > > SControl 300)
> > > > > [ 5.164367] ata2: SATA link up 1.5 Gbps (SStatus 113
> > > > > SControl 310)
> > > > > [ 5.185174] ppc-of-ohci 4bffd0000.usb: irq 32, io mem
> > > > > 0x4bffd0000
> > > > > [ 5.206125] Unable to handle kernel paging request for
> > > > > data at address 0x00000000
> > > > > [ 5.228546] Faulting instruction address: 0xc043a2c8
> > > > > [ 5.248577] Vector: 300 (Data Access) at [eddafae0]
> > > > > [ 5.268658] pc: c043a2c8: sata_dwc_qc_issue+0xb8/0x204
> > > > Well, that's not good. Can you translate that address to a
> > > > line of code?
> > > >
> > > need some guidance on method .
> > Enable CONFIG_DEBUG_INFO, then use this command:
> >
> > $ addr2line -e vmlinux 0xc043a2c8
> >
> > Obviously substitute the actual crashing address if it changes.
> >
> addr2line -e vmlinux 0xc044b41c
> arch/powerpc/lib/copy_32.S:?
memcpy I suppose. Might be copy to unmapped memory.
Anyway, can you enable debug options as I suggested including debug for
sata driver ('dw_dmac_core.dyndbg dw_dmac.dyndbg sata_dwc_460ex.dydbg'
to the cmdline and CONFIG_DYNAMIC_DEBUG=y)?
--
Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
Intel Finland Oy
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
