(CC-s added) > > > Tried 4.2.0-rc3-00246-g763e326 on A500 but it crashes on boot. This is > > > still present in todays 4.2.0-rc6+git. 4.1 was fine, I Will bisect but > > > it takes time. > > > > > > PDC Stable Storage facility v0.30 > > > STI GSC/PCI core graphics driver Version 0.9b > > > Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled > > > serial 0000:00:04.0: enabling device (0146 -> 0147) > > > console [ttyS0] disabled > > > 0000:00:04.0: ttyS0 at MMIO 0xfffffffff8000000 (irq = 21, base_baud = 115200) is a 16550A > > > console [ttyS0] enabled > > > console [ttyS0] enabled > > > bootconsole [ttyB0] disabled > > > bootconsole [ttyB0] disabled > > > 0000:00:04.0: ttyS1 at MMIO 0xfffffffff8000008 (irq = 21, base_baud = 115200) is a 16550A > > > 0000:00:04.0: ttyS2 at MMIO 0xfffffffff8000010 (irq = 21, base_baud = 115200) is a 16550A > > > serial 0000:00:05.0: enabling device (0000 -> 0003) > > > serial 0000:00:05.0: enabling SERR and PARITY (0003 -> 0143) > > > 0000:00:05.0: ttyS3 at MMIO 0xfffffffff8003000 (irq = 22, base_baud = 115200) is a 16550A > > > serial 0000:00:05.0: Couldn't register serial port 0, irq 22, type 2, error -28 > > > sym53c8xx 0000:00:01.0: enabling device (0000 -> 0003) > > > sym53c8xx 0000:00:01.0: enabling SERR and PARITY (0003 -> 0143) > > > > I'm seeing the same problem on my rp5470 with Kernel 4.2-rc7. My machine just hangs though and doesn't crash. > > I did a bisect and commit 3a9ad0b4fdcd57f775d3615004c8c64c021a9e7d ("PCI: Add pci_bus_addr_t") seems to be the culprit: > http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3a9ad0b4fdcd57f775d3615004c8c64c021a9e7d > > Since the patch has "CC: stable@xxxxxxxxxxxxxxx # v3.19+", it might be the reason why you see kernel 3.19 failing too... I just found the same commit breaking my A500 parisc machine by bisecting. CC: patch author and linux-pci. -- Meelis Roos (mroos@xxxxxxxx) -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html