Re: [regression] 2.6.39-rc[1-3] fail to boot on G5 PowerMac
On Sun, Apr 17, 2011 at 12:00 AM, Jens Axboe wrote: > On 2011-04-17 05:16, Hugh Dickins wrote: >> On Thu, Apr 14, 2011 at 2:54 PM, Benjamin Herrenschmidt >> wrote: >>> On Thu, 2011-04-14 at 14:25 -0700, Hugh Dickins wrote: Something worth trying: turn off CONFIG_IDE. That's what I need to boot 2.6.39-rc[1-3] on PowerPC G5. I know Jens has been fixing problems with IDE versus his plug/unplug changes, but it's still not fixed for me in rc3. In other mail http://lkml.org/lkml/2011/4/14/614 I see Linus recommending his post-rc3 commit 6631e635c65d but I've not tried that myself yet. >>> >>> Well, the disk is SATA so it's CONFIG_ATA/libata, which works fine here, >>> unless you somewhat replaced your CD-ROM with a legacy IDE disk :-) Or >>> maybe the problem is related to the CD-ROM drive. There's a libata >>> driver for it nowadays, so you can use PATA_MACIO instead of IDE_PMAC >> >> Thanks for that, Ben: I remember you were brewing up such a driver, >> but I missed when it actually went in. I can confirm that switching >> off CONFIG_IDE and switching on CONFIG_PATA_MACIO and >> CONFIG_BLK_DEV_SR now gives me a booting system with a working CD-ROM >> (though I've not yet tried burning). >> >> Whereas CONFIG_IDE=y with current git still does not boot: hangs for a >> minute or three around the windfarm announcements, then an endless >> splurge of hda error messages - sorry, I'm not being helpful, other >> worries... > > It's the media event notification that goes crazy. Try and comment out > this line: > > drive->dev_flags |= IDE_DFLAG_MEDIA_CHANGED; > > in drivers/ide/ide-cd.c:cdrom_saw_media_change() and see if it boots. Yes, that also boots, with a working CD-ROM: thanks. Hugh ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [regression] 2.6.39-rc[1-3] fail to boot on G5 PowerMac
On 2011-04-17 05:16, Hugh Dickins wrote: > On Thu, Apr 14, 2011 at 2:54 PM, Benjamin Herrenschmidt > wrote: >> On Thu, 2011-04-14 at 14:25 -0700, Hugh Dickins wrote: >>> >>> Something worth trying: turn off CONFIG_IDE. That's what I need to >>> boot 2.6.39-rc[1-3] on PowerPC G5. >>> >>> I know Jens has been fixing problems with IDE versus his plug/unplug >>> changes, but it's still not fixed for me in rc3. >>> >>> In other mail http://lkml.org/lkml/2011/4/14/614 >>> I see Linus recommending his post-rc3 commit 6631e635c65d >>> but I've not tried that myself yet. >> >> Well, the disk is SATA so it's CONFIG_ATA/libata, which works fine here, >> unless you somewhat replaced your CD-ROM with a legacy IDE disk :-) Or >> maybe the problem is related to the CD-ROM drive. There's a libata >> driver for it nowadays, so you can use PATA_MACIO instead of IDE_PMAC > > Thanks for that, Ben: I remember you were brewing up such a driver, > but I missed when it actually went in. I can confirm that switching > off CONFIG_IDE and switching on CONFIG_PATA_MACIO and > CONFIG_BLK_DEV_SR now gives me a booting system with a working CD-ROM > (though I've not yet tried burning). > > Whereas CONFIG_IDE=y with current git still does not boot: hangs for a > minute or three around the windfarm announcements, then an endless > splurge of hda error messages - sorry, I'm not being helpful, other > worries... It's the media event notification that goes crazy. Try and comment out this line: drive->dev_flags |= IDE_DFLAG_MEDIA_CHANGED; in drivers/ide/ide-cd.c:cdrom_saw_media_change() and see if it boots. -- Jens Axboe ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [regression] 2.6.39-rc[1-3] fail to boot on G5 PowerMac
On Thu, Apr 14, 2011 at 2:54 PM, Benjamin Herrenschmidt wrote: > On Thu, 2011-04-14 at 14:25 -0700, Hugh Dickins wrote: >> >> Something worth trying: turn off CONFIG_IDE. That's what I need to >> boot 2.6.39-rc[1-3] on PowerPC G5. >> >> I know Jens has been fixing problems with IDE versus his plug/unplug >> changes, but it's still not fixed for me in rc3. >> >> In other mail http://lkml.org/lkml/2011/4/14/614 >> I see Linus recommending his post-rc3 commit 6631e635c65d >> but I've not tried that myself yet. > > Well, the disk is SATA so it's CONFIG_ATA/libata, which works fine here, > unless you somewhat replaced your CD-ROM with a legacy IDE disk :-) Or > maybe the problem is related to the CD-ROM drive. There's a libata > driver for it nowadays, so you can use PATA_MACIO instead of IDE_PMAC Thanks for that, Ben: I remember you were brewing up such a driver, but I missed when it actually went in. I can confirm that switching off CONFIG_IDE and switching on CONFIG_PATA_MACIO and CONFIG_BLK_DEV_SR now gives me a booting system with a working CD-ROM (though I've not yet tried burning). Whereas CONFIG_IDE=y with current git still does not boot: hangs for a minute or three around the windfarm announcements, then an endless splurge of hda error messages - sorry, I'm not being helpful, other worries... Hugh ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [regression] 2.6.39-rc[1-3] fail to boot on G5 PowerMac
On Thu, 14 Apr 2011 14:25:31 -0700, Hugh Dickins wrote: > Mikael, > > Something worth trying: turn off CONFIG_IDE. That's what I need to > boot 2.6.39-rc[1-3] on PowerPC G5. > > I know Jens has been fixing problems with IDE versus his plug/unplug > changes, but it's still not fixed for me in rc3. > > In other mail http://lkml.org/lkml/2011/4/14/614 > I see Linus recommending his post-rc3 commit 6631e635c65d > but I've not tried that myself yet. > > Hugh Hugh, With CONFIG_IDE disabled I could finally boot 2.6.39-rc3 on my G5. I lost the DVD drive, but that's fine for now. Thanks! /Mikael ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [regression] 2.6.39-rc[1-3] fail to boot on G5 PowerMac
On Thu, 2011-04-14 at 14:25 -0700, Hugh Dickins wrote: > > Something worth trying: turn off CONFIG_IDE. That's what I need to > boot 2.6.39-rc[1-3] on PowerPC G5. > > I know Jens has been fixing problems with IDE versus his plug/unplug > changes, but it's still not fixed for me in rc3. > > In other mail http://lkml.org/lkml/2011/4/14/614 > I see Linus recommending his post-rc3 commit 6631e635c65d > but I've not tried that myself yet. Well, the disk is SATA so it's CONFIG_ATA/libata, which works fine here, unless you somewhat replaced your CD-ROM with a legacy IDE disk :-) Or maybe the problem is related to the CD-ROM drive. There's a libata driver for it nowadays, so you can use PATA_MACIO instead of IDE_PMAC Cheers, Ben. ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [regression] 2.6.39-rc[1-3] fail to boot on G5 PowerMac
On Thu, Apr 14, 2011 at 2:02 AM, Michel Dänzer wrote: > On Mit, 2011-04-13 at 18:43 -0500, kevin diggs wrote: >> >> On Wed, Apr 13, 2011 at 6:21 PM, Benjamin Herrenschmidt >> wrote: >> > On Wed, 2011-04-13 at 12:52 -0500, kevin diggs wrote: >> >> > Actually I do get a crash in X later on... something in the radeon >> >> DRM >> >> > interrupt code is getting what looks like a NULL dereference. I'll >> >> try >> >> > to dig that one later on. I don't know if it's related to your >> >> problem >> >> > at all though. >> >> > >> >> In this context, what does 'crash' mean? The X thingy goes down? Or >> >> the whole OS? >> > >> > Depends, with xmon enabled you get into xmon :-) Dunno if the oops is >> > fatal but it could be. >> > >> > Cheers, >> > Ben. >> > >> > >> >> As I think I have the same hardware as you (7,3, radeon 9600) If you >> can tell me how to reproduce it maybe I can poke around a little. >> Thus, at least temporarily, freeing you up for other stuff. >> >> I kinda need a break from fighting with GCC. > > FWIW, the problem Ben refers to might be fixed in current mainline by > commit d87dfdbfc91c5e37288e7e8f7afdd992ba61a60d which reverts > 69a07f0b117a40fcc1a479358d8e1f41793617f2 . Mikael, Something worth trying: turn off CONFIG_IDE. That's what I need to boot 2.6.39-rc[1-3] on PowerPC G5. I know Jens has been fixing problems with IDE versus his plug/unplug changes, but it's still not fixed for me in rc3. In other mail http://lkml.org/lkml/2011/4/14/614 I see Linus recommending his post-rc3 commit 6631e635c65d but I've not tried that myself yet. Hugh ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [regression] 2.6.39-rc[1-3] fail to boot on G5 PowerMac
On Mit, 2011-04-13 at 18:43 -0500, kevin diggs wrote: > > On Wed, Apr 13, 2011 at 6:21 PM, Benjamin Herrenschmidt > wrote: > > On Wed, 2011-04-13 at 12:52 -0500, kevin diggs wrote: > >> > Actually I do get a crash in X later on... something in the radeon > >> DRM > >> > interrupt code is getting what looks like a NULL dereference. I'll > >> try > >> > to dig that one later on. I don't know if it's related to your > >> problem > >> > at all though. > >> > > >> In this context, what does 'crash' mean? The X thingy goes down? Or > >> the whole OS? > > > > Depends, with xmon enabled you get into xmon :-) Dunno if the oops is > > fatal but it could be. > > > > Cheers, > > Ben. > > > > > > As I think I have the same hardware as you (7,3, radeon 9600) If you > can tell me how to reproduce it maybe I can poke around a little. > Thus, at least temporarily, freeing you up for other stuff. > > I kinda need a break from fighting with GCC. FWIW, the problem Ben refers to might be fixed in current mainline by commit d87dfdbfc91c5e37288e7e8f7afdd992ba61a60d which reverts 69a07f0b117a40fcc1a479358d8e1f41793617f2 . -- Earthling Michel Dänzer |http://www.vmware.com Libre software enthusiast | Debian, X and DRI developer ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [regression] 2.6.39-rc[1-3] fail to boot on G5 PowerMac
Hi, On Wed, Apr 13, 2011 at 6:21 PM, Benjamin Herrenschmidt wrote: > On Wed, 2011-04-13 at 12:52 -0500, kevin diggs wrote: >> > Actually I do get a crash in X later on... something in the radeon >> DRM >> > interrupt code is getting what looks like a NULL dereference. I'll >> try >> > to dig that one later on. I don't know if it's related to your >> problem >> > at all though. >> > >> In this context, what does 'crash' mean? The X thingy goes down? Or >> the whole OS? > > Depends, with xmon enabled you get into xmon :-) Dunno if the oops is > fatal but it could be. > > Cheers, > Ben. > > As I think I have the same hardware as you (7,3, radeon 9600) If you can tell me how to reproduce it maybe I can poke around a little. Thus, at least temporarily, freeing you up for other stuff. I kinda need a break from fighting with GCC. kevin ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [regression] 2.6.39-rc[1-3] fail to boot on G5 PowerMac
On Wed, 2011-04-13 at 12:52 -0500, kevin diggs wrote: > > Actually I do get a crash in X later on... something in the radeon > DRM > > interrupt code is getting what looks like a NULL dereference. I'll > try > > to dig that one later on. I don't know if it's related to your > problem > > at all though. > > > In this context, what does 'crash' mean? The X thingy goes down? Or > the whole OS? Depends, with xmon enabled you get into xmon :-) Dunno if the oops is fatal but it could be. Cheers, Ben. ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [regression] 2.6.39-rc[1-3] fail to boot on G5 PowerMac
HI, On Wed, Apr 13, 2011 at 3:58 AM, Benjamin Herrenschmidt wrote: > > Actually I do get a crash in X later on... something in the radeon DRM > interrupt code is getting what looks like a NULL dereference. I'll try > to dig that one later on. I don't know if it's related to your problem > at all though. > In this context, what does 'crash' mean? The X thingy goes down? Or the whole OS? Cheers, kevin. > Cheers, > Ben. ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [regression] 2.6.39-rc[1-3] fail to boot on G5 PowerMac
On Wed, 2011-04-13 at 10:16 +0200, Mikael Pettersson wrote: > > Ok so on a PowerMac7,3 here (dual 2.5Ghz and mostly same HW or at least > > very similar) I can't reproduce your problem with a g5_defconfig. > > > > Your config doesn't work well for me (I don't do modules, I netboot), > > but after adding a few things to it, it seems to work fine as well. I > > added radeonfb and the radeon DRM (not KMS) and I added eventfd, timerfd > > and input events. > > > > So I'm afraid I'm going to need you to bisect that one to find out what > > exact change caused the breakage for you. > > Thanks for checking. I'll try a bisect later today. Actually I do get a crash in X later on... something in the radeon DRM interrupt code is getting what looks like a NULL dereference. I'll try to dig that one later on. I don't know if it's related to your problem at all though. Cheers, Ben. ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [regression] 2.6.39-rc[1-3] fail to boot on G5 PowerMac
Benjamin Herrenschmidt writes: > > > > Finally I tried using g5_defconfig with 2.6.39-rc3. First boot > > > it did get to /sbin/init, but udev init took much longer than > > > normal and threw errors. After a warm reboot the same kernel > > > hung as usual, this time before framebuffer init. > > > > > > 2.6.38 works just fine. > > > > Hrm, that must be new, I remember testing something around -rc1 on a > > similar machine and it worked fine. I'll see if I can find something > > out. > > Ok so on a PowerMac7,3 here (dual 2.5Ghz and mostly same HW or at least > very similar) I can't reproduce your problem with a g5_defconfig. > > Your config doesn't work well for me (I don't do modules, I netboot), > but after adding a few things to it, it seems to work fine as well. I > added radeonfb and the radeon DRM (not KMS) and I added eventfd, timerfd > and input events. > > So I'm afraid I'm going to need you to bisect that one to find out what > exact change caused the breakage for you. Thanks for checking. I'll try a bisect later today. /Mikael ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [regression] 2.6.39-rc[1-3] fail to boot on G5 PowerMac
> > Finally I tried using g5_defconfig with 2.6.39-rc3. First boot > > it did get to /sbin/init, but udev init took much longer than > > normal and threw errors. After a warm reboot the same kernel > > hung as usual, this time before framebuffer init. > > > > 2.6.38 works just fine. > > Hrm, that must be new, I remember testing something around -rc1 on a > similar machine and it worked fine. I'll see if I can find something > out. Ok so on a PowerMac7,3 here (dual 2.5Ghz and mostly same HW or at least very similar) I can't reproduce your problem with a g5_defconfig. Your config doesn't work well for me (I don't do modules, I netboot), but after adding a few things to it, it seems to work fine as well. I added radeonfb and the radeon DRM (not KMS) and I added eventfd, timerfd and input events. So I'm afraid I'm going to need you to bisect that one to find out what exact change caused the breakage for you. Cheers, Ben. ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [regression] 2.6.39-rc[1-3] fail to boot on G5 PowerMac
On Tue, 2011-04-12 at 19:30 +0200, Mikael Pettersson wrote: > I'm unable to boot any post-2.6.38 kernel on my G5 (PowerMac7,2 > with dual 1.8GHz processors). Basically the kernel hangs at varying > points before /sbin/init is started, sometimes before and sometimes > after the framebuffer has taken over the console. There are no visible > errors on the console, only a hang. Sorry, got no serial console > set up yet. My 2.6.39-rc3 .config is attached below. > > Finally I tried using g5_defconfig with 2.6.39-rc3. First boot > it did get to /sbin/init, but udev init took much longer than > normal and threw errors. After a warm reboot the same kernel > hung as usual, this time before framebuffer init. > > 2.6.38 works just fine. Hrm, that must be new, I remember testing something around -rc1 on a similar machine and it worked fine. I'll see if I can find something out. Thanks ! Cheers, Ben. > /Mikael > > # > # Automatically generated make config: don't edit > # > CONFIG_PPC64=y > > # > # Processor support > # > CONFIG_PPC_BOOK3S_64=y > # CONFIG_PPC_BOOK3E_64 is not set > CONFIG_PPC_BOOK3S=y > CONFIG_POWER4_ONLY=y > CONFIG_POWER4=y > # CONFIG_TUNE_CELL is not set > CONFIG_PPC_FPU=y > CONFIG_ALTIVEC=y > # CONFIG_VSX is not set > CONFIG_PPC_STD_MMU=y > CONFIG_PPC_STD_MMU_64=y > CONFIG_PPC_MM_SLICES=y > CONFIG_VIRT_CPU_ACCOUNTING=y > CONFIG_PPC_HAVE_PMU_SUPPORT=y > CONFIG_SMP=y > CONFIG_NR_CPUS=2 > CONFIG_64BIT=y > CONFIG_WORD_SIZE=64 > CONFIG_ARCH_PHYS_ADDR_T_64BIT=y > CONFIG_ARCH_DMA_ADDR_T_64BIT=y > CONFIG_MMU=y > CONFIG_GENERIC_CMOS_UPDATE=y > CONFIG_GENERIC_TIME_VSYSCALL=y > CONFIG_GENERIC_CLOCKEVENTS=y > CONFIG_HAVE_SETUP_PER_CPU_AREA=y > CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y > CONFIG_NR_IRQS=256 > CONFIG_STACKTRACE_SUPPORT=y > CONFIG_HAVE_LATENCYTOP_SUPPORT=y > CONFIG_TRACE_IRQFLAGS_SUPPORT=y > CONFIG_LOCKDEP_SUPPORT=y > CONFIG_RWSEM_XCHGADD_ALGORITHM=y > CONFIG_ARCH_HAS_ILOG2_U32=y > CONFIG_ARCH_HAS_ILOG2_U64=y > CONFIG_GENERIC_HWEIGHT=y > CONFIG_GENERIC_FIND_NEXT_BIT=y > CONFIG_GENERIC_FIND_BIT_LE=y > CONFIG_ARCH_NO_VIRT_TO_BUS=y > CONFIG_PPC=y > CONFIG_EARLY_PRINTK=y > CONFIG_COMPAT=y > CONFIG_SYSVIPC_COMPAT=y > CONFIG_SCHED_OMIT_FRAME_POINTER=y > CONFIG_ARCH_MAY_HAVE_PC_FDC=y > CONFIG_PPC_OF=y > # CONFIG_PPC_UDBG_16550 is not set > CONFIG_GENERIC_TBSYNC=y > CONFIG_AUDIT_ARCH=y > CONFIG_GENERIC_BUG=y > # CONFIG_DEFAULT_UIMAGE is not set > CONFIG_ARCH_HIBERNATION_POSSIBLE=y > CONFIG_ARCH_SUSPEND_POSSIBLE=y > # CONFIG_PPC_DCR_NATIVE is not set > # CONFIG_PPC_DCR_MMIO is not set > # CONFIG_PPC_OF_PLATFORM_PCI is not set > CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y > CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" > CONFIG_CONSTRUCTORS=y > CONFIG_HAVE_IRQ_WORK=y > > # > # General setup > # > CONFIG_EXPERIMENTAL=y > CONFIG_INIT_ENV_ARG_LIMIT=32 > CONFIG_CROSS_COMPILE="" > CONFIG_LOCALVERSION="" > # CONFIG_LOCALVERSION_AUTO is not set > CONFIG_SWAP=y > CONFIG_SYSVIPC=y > CONFIG_SYSVIPC_SYSCTL=y > # CONFIG_POSIX_MQUEUE is not set > # CONFIG_BSD_PROCESS_ACCT is not set > # CONFIG_FHANDLE is not set > # CONFIG_TASKSTATS is not set > # CONFIG_AUDIT is not set > CONFIG_HAVE_GENERIC_HARDIRQS=y > > # > # IRQ subsystem > # > CONFIG_GENERIC_HARDIRQS=y > CONFIG_HAVE_SPARSE_IRQ=y > CONFIG_GENERIC_IRQ_SHOW=y > CONFIG_GENERIC_IRQ_SHOW_LEVEL=y > # CONFIG_SPARSE_IRQ is not set > > # > # RCU Subsystem > # > CONFIG_TREE_RCU=y > # CONFIG_PREEMPT_RCU is not set > # CONFIG_RCU_TRACE is not set > CONFIG_RCU_FANOUT=64 > # CONFIG_RCU_FANOUT_EXACT is not set > # CONFIG_RCU_FAST_NO_HZ is not set > # CONFIG_TREE_RCU_TRACE is not set > # CONFIG_IKCONFIG is not set > CONFIG_LOG_BUF_SHIFT=17 > # CONFIG_NAMESPACES is not set > # CONFIG_SCHED_AUTOGROUP is not set > # CONFIG_SYSFS_DEPRECATED is not set > # CONFIG_RELAY is not set > CONFIG_BLK_DEV_INITRD=y > CONFIG_INITRAMFS_SOURCE="" > CONFIG_RD_GZIP=y > # CONFIG_RD_BZIP2 is not set > # CONFIG_RD_LZMA is not set > # CONFIG_RD_XZ is not set > # CONFIG_RD_LZO is not set > CONFIG_CC_OPTIMIZE_FOR_SIZE=y > CONFIG_SYSCTL=y > CONFIG_ANON_INODES=y > CONFIG_EXPERT=y > CONFIG_EMBEDDED=y > CONFIG_SYSCTL_SYSCALL=y > CONFIG_KALLSYMS=y > # CONFIG_KALLSYMS_ALL is not set > # CONFIG_KALLSYMS_EXTRA_PASS is not set > CONFIG_HOTPLUG=y > CONFIG_PRINTK=y > CONFIG_BUG=y > CONFIG_ELF_CORE=y > CONFIG_BASE_FULL=y > CONFIG_FUTEX=y > CONFIG_EPOLL=y > CONFIG_SIGNALFD=y > # CONFIG_TIMERFD is not set > # CONFIG_EVENTFD is not set > CONFIG_SHMEM=y > # CONFIG_AIO is not set > CONFIG_HAVE_PERF_EVENTS=y > > # > # Kernel Performance Events And Counters > # > # CONFIG_PERF_EVENTS is not set > # CONFIG_PERF_COUNTERS is not set > # CONFIG_VM_EVENT_COUNTERS is not set > CONFIG_PCI_QUIRKS=y > CONFIG_SLUB_DEBUG=y > # CONFIG_COMPAT_BRK is not set > # CONFIG_SLAB is not set > CONFIG_SLUB=y > # CONFIG_SLOB is not set > # CONFIG_PROFILING is not set > CONFIG_HAVE_OPROFILE=y > # CONFIG_KPROBES is not set > CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y > CONFIG_HAVE_SYSCALL_WRAPPERS=y > CONFIG_HAVE_IOREMAP_PROT=y >
Re: [regression] 2.6.39-rc[1-3] fail to boot on G5 PowerMac
Hi, Uh Oh. Are we gettin' booted (no pun intended)? kevin ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
[regression] 2.6.39-rc[1-3] fail to boot on G5 PowerMac
I'm unable to boot any post-2.6.38 kernel on my G5 (PowerMac7,2 with dual 1.8GHz processors). Basically the kernel hangs at varying points before /sbin/init is started, sometimes before and sometimes after the framebuffer has taken over the console. There are no visible errors on the console, only a hang. Sorry, got no serial console set up yet. My 2.6.39-rc3 .config is attached below. Finally I tried using g5_defconfig with 2.6.39-rc3. First boot it did get to /sbin/init, but udev init took much longer than normal and threw errors. After a warm reboot the same kernel hung as usual, this time before framebuffer init. 2.6.38 works just fine. /Mikael # # Automatically generated make config: don't edit # CONFIG_PPC64=y # # Processor support # CONFIG_PPC_BOOK3S_64=y # CONFIG_PPC_BOOK3E_64 is not set CONFIG_PPC_BOOK3S=y CONFIG_POWER4_ONLY=y CONFIG_POWER4=y # CONFIG_TUNE_CELL is not set CONFIG_PPC_FPU=y CONFIG_ALTIVEC=y # CONFIG_VSX is not set CONFIG_PPC_STD_MMU=y CONFIG_PPC_STD_MMU_64=y CONFIG_PPC_MM_SLICES=y CONFIG_VIRT_CPU_ACCOUNTING=y CONFIG_PPC_HAVE_PMU_SUPPORT=y CONFIG_SMP=y CONFIG_NR_CPUS=2 CONFIG_64BIT=y CONFIG_WORD_SIZE=64 CONFIG_ARCH_PHYS_ADDR_T_64BIT=y CONFIG_ARCH_DMA_ADDR_T_64BIT=y CONFIG_MMU=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_HAVE_SETUP_PER_CPU_AREA=y CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y CONFIG_NR_IRQS=256 CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_TRACE_IRQFLAGS_SUPPORT=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_ARCH_HAS_ILOG2_U32=y CONFIG_ARCH_HAS_ILOG2_U64=y CONFIG_GENERIC_HWEIGHT=y CONFIG_GENERIC_FIND_NEXT_BIT=y CONFIG_GENERIC_FIND_BIT_LE=y CONFIG_ARCH_NO_VIRT_TO_BUS=y CONFIG_PPC=y CONFIG_EARLY_PRINTK=y CONFIG_COMPAT=y CONFIG_SYSVIPC_COMPAT=y CONFIG_SCHED_OMIT_FRAME_POINTER=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_PPC_OF=y # CONFIG_PPC_UDBG_16550 is not set CONFIG_GENERIC_TBSYNC=y CONFIG_AUDIT_ARCH=y CONFIG_GENERIC_BUG=y # CONFIG_DEFAULT_UIMAGE is not set CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y # CONFIG_PPC_DCR_NATIVE is not set # CONFIG_PPC_DCR_MMIO is not set # CONFIG_PPC_OF_PLATFORM_PCI is not set CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" CONFIG_CONSTRUCTORS=y CONFIG_HAVE_IRQ_WORK=y # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_CROSS_COMPILE="" CONFIG_LOCALVERSION="" # CONFIG_LOCALVERSION_AUTO is not set CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y # CONFIG_POSIX_MQUEUE is not set # CONFIG_BSD_PROCESS_ACCT is not set # CONFIG_FHANDLE is not set # CONFIG_TASKSTATS is not set # CONFIG_AUDIT is not set CONFIG_HAVE_GENERIC_HARDIRQS=y # # IRQ subsystem # CONFIG_GENERIC_HARDIRQS=y CONFIG_HAVE_SPARSE_IRQ=y CONFIG_GENERIC_IRQ_SHOW=y CONFIG_GENERIC_IRQ_SHOW_LEVEL=y # CONFIG_SPARSE_IRQ is not set # # RCU Subsystem # CONFIG_TREE_RCU=y # CONFIG_PREEMPT_RCU is not set # CONFIG_RCU_TRACE is not set CONFIG_RCU_FANOUT=64 # CONFIG_RCU_FANOUT_EXACT is not set # CONFIG_RCU_FAST_NO_HZ is not set # CONFIG_TREE_RCU_TRACE is not set # CONFIG_IKCONFIG is not set CONFIG_LOG_BUF_SHIFT=17 # CONFIG_NAMESPACES is not set # CONFIG_SCHED_AUTOGROUP is not set # CONFIG_SYSFS_DEPRECATED is not set # CONFIG_RELAY is not set CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" CONFIG_RD_GZIP=y # CONFIG_RD_BZIP2 is not set # CONFIG_RD_LZMA is not set # CONFIG_RD_XZ is not set # CONFIG_RD_LZO is not set CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_SYSCTL=y CONFIG_ANON_INODES=y CONFIG_EXPERT=y CONFIG_EMBEDDED=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y # CONFIG_TIMERFD is not set # CONFIG_EVENTFD is not set CONFIG_SHMEM=y # CONFIG_AIO is not set CONFIG_HAVE_PERF_EVENTS=y # # Kernel Performance Events And Counters # # CONFIG_PERF_EVENTS is not set # CONFIG_PERF_COUNTERS is not set # CONFIG_VM_EVENT_COUNTERS is not set CONFIG_PCI_QUIRKS=y CONFIG_SLUB_DEBUG=y # CONFIG_COMPAT_BRK is not set # CONFIG_SLAB is not set CONFIG_SLUB=y # CONFIG_SLOB is not set # CONFIG_PROFILING is not set CONFIG_HAVE_OPROFILE=y # CONFIG_KPROBES is not set CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y CONFIG_HAVE_SYSCALL_WRAPPERS=y CONFIG_HAVE_IOREMAP_PROT=y CONFIG_HAVE_KPROBES=y CONFIG_HAVE_KRETPROBES=y CONFIG_HAVE_ARCH_TRACEHOOK=y CONFIG_HAVE_DMA_ATTRS=y CONFIG_USE_GENERIC_SMP_HELPERS=y CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y CONFIG_HAVE_DMA_API_DEBUG=y # # GCOV-based kernel profiling # # CONFIG_HAVE_GENERIC_DMA_COHERENT is not set CONFIG_SLABINFO=y CONFIG_RT_MUTEXES=y CONFIG_BASE_SMALL=0 CONFIG_MODULES=y # CONFIG_MODULE_FORCE_LOAD is not set CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set CONFIG_MODVERSIONS=y # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_STOP_MACHINE=y CONFIG_BLOCK=y # CONFIG_BLK_DEV_BS