Re: linux panic on 4.0.0-rc4
On 03/17/2015 04:16 PM, Pranith Kumar wrote: > On Tue, Mar 17, 2015 at 4:13 PM, Peter Hurley > wrote: >> On 03/17/2015 04:07 PM, Pranith Kumar wrote: >>> On Tue, Mar 17, 2015 at 4:03 PM, Peter Hurley >>> wrote: Can you send me a complete dmesg capture from a boot with this commit reverted? >>> >>> Here it is. Let me know if you want any boot options enabled. I >>> removed both debug and verbose boot options. >> >> Ok, thanks. >> >> This is just like Andreas' problem: with my patch, there is _no_ console. >> >> Note those console command line options in your config aren't actually >> in your kernel command line. That really threw me; I couldn't figure out >> how you didn't have a tty0 console. >> >>> [0.00] Kernel command line: >>> root=UUID=7252209a-6106-41c2-90a3-45b85ac47837 ro video=radeonfb:off >>> video=offb:off radeon.modeset=1 radeon.agpmode=-1 >> > > Hmm, interesting. These arguments are passed from the yaboot.conf > which has a line as follows: > > append="video=radeonfb:off video=offb:off radeon.modeset=1 radeon.agpmode=-1" > > I thought this would append these arguments to the default kernel > command line argument in the config. Apparently it is not. So, the > resolution for this is to add the console argument to yaboot.conf I > guess, right? No, I'm sending a revert anyway, but I thought I'd let you know. Regards, Peter Hurley -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux panic on 4.0.0-rc4
On Tue, Mar 17, 2015 at 4:13 PM, Peter Hurley wrote: > On 03/17/2015 04:07 PM, Pranith Kumar wrote: >> On Tue, Mar 17, 2015 at 4:03 PM, Peter Hurley >> wrote: >>> >>> Can you send me a complete dmesg capture from a boot with >>> this commit reverted? >>> >> >> Here it is. Let me know if you want any boot options enabled. I >> removed both debug and verbose boot options. > > Ok, thanks. > > This is just like Andreas' problem: with my patch, there is _no_ console. > > Note those console command line options in your config aren't actually > in your kernel command line. That really threw me; I couldn't figure out > how you didn't have a tty0 console. > >> [0.00] Kernel command line: >> root=UUID=7252209a-6106-41c2-90a3-45b85ac47837 ro video=radeonfb:off >> video=offb:off radeon.modeset=1 radeon.agpmode=-1 > Hmm, interesting. These arguments are passed from the yaboot.conf which has a line as follows: append="video=radeonfb:off video=offb:off radeon.modeset=1 radeon.agpmode=-1" I thought this would append these arguments to the default kernel command line argument in the config. Apparently it is not. So, the resolution for this is to add the console argument to yaboot.conf I guess, right? -- Pranith -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux panic on 4.0.0-rc4
On 03/17/2015 04:07 PM, Pranith Kumar wrote: > On Tue, Mar 17, 2015 at 4:03 PM, Peter Hurley > wrote: >> >> Can you send me a complete dmesg capture from a boot with >> this commit reverted? >> > > Here it is. Let me know if you want any boot options enabled. I > removed both debug and verbose boot options. Ok, thanks. This is just like Andreas' problem: with my patch, there is _no_ console. Note those console command line options in your config aren't actually in your kernel command line. That really threw me; I couldn't figure out how you didn't have a tty0 console. > [0.00] Kernel command line: > root=UUID=7252209a-6106-41c2-90a3-45b85ac47837 ro video=radeonfb:off > video=offb:off radeon.modeset=1 radeon.agpmode=-1 Regards, Peter Hurley -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux panic on 4.0.0-rc4
On Tue, Mar 17, 2015 at 4:03 PM, Peter Hurley wrote: > > Can you send me a complete dmesg capture from a boot with > this commit reverted? > Here it is. Let me know if you want any boot options enabled. I removed both debug and verbose boot options. [0.00] Using PowerMac machine description [0.00] Total memory = 1024MB; using 2048kB for hash table (at cfe0) [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 4.0.0-rc4+ (pranith@macmini) (gcc version 4.9.2 (Debian 4.9.2-10) ) #67 Tue Mar 17 12:40:16 EDT 2015 [0.00] Found initrd at 0xc130:0xc1692000 [0.00] Found UniNorth memory controller & host bridge @ 0xf800 revision: 0xd2 [0.00] Mapped at 0xff7c [0.00] Found a Intrepid mac-io controller, rev: 0, mapped at 0xff74 [0.00] Processor NAP mode on idle enabled. [0.00] PowerMac motherboard: Mac mini (Late 2005) [0.00] bootconsole [udbg0] enabled [0.00] Found UniNorth PCI host bridge at 0xf000. Firmware bus number: 0->0 [0.00] PCI host bridge /pci@f000 ranges: [0.00] MEM 0xf100..0xf1ff -> 0xf100 [0.00] IO 0xf000..0xf07f -> 0x [0.00] MEM 0x9000..0x9fff -> 0x9000 [0.00] Found UniNorth PCI host bridge at 0xf200. Firmware bus number: 0->0 [0.00] PCI host bridge /pci@f200 (primary) ranges: [0.00] MEM 0xf300..0xf3ff -> 0xf300 [0.00] IO 0xf200..0xf27f -> 0x [0.00] MEM 0x8000..0x8fff -> 0x8000 [0.00] Found UniNorth PCI host bridge at 0xf400. Firmware bus number: 0->0 [0.00] PCI host bridge /pci@f400 ranges: [0.00] MEM 0xf500..0xf5ff -> 0xf500 [0.00] IO 0xf400..0xf47f -> 0x [0.00] via-pmu: Server Mode is disabled [0.00] PMU driver v2 initialized for Core99, firmware: 55 [0.00] Top of RAM: 0x4000, Total RAM: 0x4000 [0.00] Memory hole size: 0MB [0.00] Zone ranges: [0.00] DMA [mem 0x-0x2fff] [0.00] Normal empty [0.00] HighMem [mem 0x3000-0x3fff] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x-0x3fff] [0.00] Initmem setup node 0 [mem 0x-0x3fff] [0.00] On node 0 totalpages: 262144 [0.00] free_area_init_node: node 0, pgdat c05a4a64, node_mem_map ef6e3000 [0.00] DMA zone: 1728 pages used for memmap [0.00] DMA zone: 0 pages reserved [0.00] DMA zone: 196608 pages, LIFO batch:31 [0.00] HighMem zone: 65536 pages, LIFO batch:15 [0.00] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 [0.00] pcpu-alloc: [0] 0 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260416 [0.00] Kernel command line: root=UUID=7252209a-6106-41c2-90a3-45b85ac47837 ro video=radeonfb:off video=offb:off radeon.modeset=1 radeon.agpmode=-1 [0.00] PID hash table entries: 4096 (order: 2, 16384 bytes) [0.00] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [0.00] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [0.00] Sorting __ex_table... [0.00] Memory: 1026292K/1048576K available (3980K kernel code, 212K rwdata, 1384K rodata, 240K init, 294K bss, 22284K reserved, 0K cma-reserved, 262144K highmem) [0.00] Kernel virtual memory layout: [0.00] * 0xfffcf000..0xf000 : fixmap [0.00] * 0xff80..0xffc0 : highmem PTEs [0.00] * 0xfdde4000..0xff80 : early ioremap [0.00] * 0xf100..0xfdde4000 : vmalloc & ioremap [0.00] NR_IRQS:512 nr_irqs:512 16 [0.00] mpic: Resetting [0.00] mpic: Setting up MPIC " MPIC 1 " version 1.2 at 8004, max 1 CPUs [0.00] mpic: ISU size: 64, shift: 6, mask: 3f [0.00] mpic: Initializing for 64 sources [0.00] time_init: decrementer frequency = 41.600571 MHz [0.00] time_init: processor frequency = 1333.28 MHz [0.08] clocksource: timebase mult[1809c2fe] shift[24] registered [0.000394] clockevent: decrementer mult[aa655c4] shift[32] cpu[0] [0.000647] Console: colour dummy device 80x25 [0.000998] console [tty0] enabled [0.001333] bootconsole [udbg0] disabled [0.001859] pid_max: default: 32768 minimum: 301 [0.001902] Mount-cache hash table entries: 2048 (order: 1, 8192
Re: linux panic on 4.0.0-rc4
On 03/17/2015 02:33 AM, Pranith Kumar wrote: > On Mon, Mar 16, 2015 at 11:18 PM, Peter Hurley > wrote: >> On 03/16/2015 11:12 PM, Pranith Kumar wrote: >>> On Mon, Mar 16, 2015 at 10:58 PM, Peter Hurley >>> wrote: >> What is your init? > > I am using systemd from debian unstable. Do you have a stdout-path property defined in your dts to a serial console you're not actually using? >>> >>> I am using tty0 as my console. From the config which I posted, it has: >>> >>> CONFIG_CMDLINE="console=ttyS0,9600 console=tty0" >>> >>> I am not using any device tree file. >> >> Ok; there was some reported breakage on PowerMac wrt to 'stdout-path' >> changes I made, so I thought I'd check if that might have affected >> your setup as well. >> > > And the painful slow bisecting did lead to that commit: > > Bisecting: 0 revisions left to test after this (roughly 0 steps) > [2fa645cb2703d9b3786d850db815414dfeefa51d] of: Fix premature > bootconsole disable with 'stdout-path' > > $ git show 2fa645cb2703d9b3786d850db815414dfeefa51d > commit 2fa645cb2703d9b3786d850db815414dfeefa51d > Author: Peter Hurley > Date: Sun Mar 1 12:21:22 2015 -0500 > > of: Fix premature bootconsole disable with 'stdout-path' Can you send me a complete dmesg capture from a boot with this commit reverted? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux panic on 4.0.0-rc4
On Mon, Mar 16, 2015 at 11:18 PM, Peter Hurley wrote: > On 03/16/2015 11:12 PM, Pranith Kumar wrote: >> On Mon, Mar 16, 2015 at 10:58 PM, Peter Hurley >> wrote: > What is your init? I am using systemd from debian unstable. >>> >>> Do you have a stdout-path property defined in your dts to a serial >>> console you're not actually using? >>> >> >> I am using tty0 as my console. From the config which I posted, it has: >> >> CONFIG_CMDLINE="console=ttyS0,9600 console=tty0" >> >> I am not using any device tree file. > > Ok; there was some reported breakage on PowerMac wrt to 'stdout-path' > changes I made, so I thought I'd check if that might have affected > your setup as well. > And the painful slow bisecting did lead to that commit: Bisecting: 0 revisions left to test after this (roughly 0 steps) [2fa645cb2703d9b3786d850db815414dfeefa51d] of: Fix premature bootconsole disable with 'stdout-path' $ git show 2fa645cb2703d9b3786d850db815414dfeefa51d commit 2fa645cb2703d9b3786d850db815414dfeefa51d Author: Peter Hurley Date: Sun Mar 1 12:21:22 2015 -0500 of: Fix premature bootconsole disable with 'stdout-path' Support for devicetree serial consoles via 'stdout-path' causes bootconsoles to be disabled when the vt dummy console loads, since there is no preferred console (the preferred console is not added until the device is probed). Ensure there is at least a preferred console, even if never matched. More info: $ git bisect log git bisect start # bad: [06e5801b8cb3fc057d88cb4dc03c0b64b2744cda] Linux 4.0-rc4 git bisect bad 06e5801b8cb3fc057d88cb4dc03c0b64b2744cda # good: [bfa76d49576599a4b9f9b7a71f23d73d6dcff735] Linux 3.19 git bisect good bfa76d49576599a4b9f9b7a71f23d73d6dcff735 # good: [1a67e256dbd80f47f339c4a88c34deee12489aa0] ARM: mvebu: ISL12057 rtc chip can now wake up RN102, RN102 and RN2120 git bisect good 1a67e256dbd80f47f339c4a88c34deee12489aa0 # good: [878ba61aa98cbb97a513757800e77613f856a029] Merge tag 'soc-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc git bisect good 878ba61aa98cbb97a513757800e77613f856a029 # good: [18a8d49973667aa016e68826eeb374788b7c63b0] Merge tag 'clk-for-linus-3.20' of git://git.linaro.org/people/mike.turquette/linux git bisect good 18a8d49973667aa016e68826eeb374788b7c63b0 # good: [bfda4031621b048ca634abc5f6bce1aa490ac4e5] MAINTAINERS: Add myself as co-maintainer to the legacy support of the mvebu SoCs git bisect good bfda4031621b048ca634abc5f6bce1aa490ac4e5 # good: [29191c7f71aa55401c83df60482417d3c511edde] Merge tag 'char-misc-4.0-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc git bisect good 29191c7f71aa55401c83df60482417d3c511edde # good: [36bef88380037288d5b575ed2029de694533b1ec] Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net git bisect good 36bef88380037288d5b575ed2029de694533b1ec # bad: [3d52c5bdbe57e2b45d9cc8da930b9ab42b5198c4] Merge tag 'devicetree-fixes-for-4.0' of git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux git bisect bad 3d52c5bdbe57e2b45d9cc8da930b9ab42b5198c4 # good: [91e9134eda82b57952fdbdb0c5990a7a6609ff13] Merge tag 'pci-v4.0-fixes-2' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci git bisect good 91e9134eda82b57952fdbdb0c5990a7a6609ff13 # good: [c202baf017aea0c860e53131bc55bb1af7177e76] Merge branch 'akpm' (patches from Andrew) git bisect good c202baf017aea0c860e53131bc55bb1af7177e76 # bad: [649022e08e4798ffb6e9b11c56ee6b2c62465d11] of/unittest: Fix the wrong expected value in of_selftest_property_string git bisect bad 649022e08e4798ffb6e9b11c56ee6b2c62465d11 # good: [2c192699a7050ef5bdf1e2cc95fdddfbcf524509] Merge tag 'v4.0-rc3' into HEAD git bisect good 2c192699a7050ef5bdf1e2cc95fdddfbcf524509 # bad: [d3a891652adb82e1973348c703a597cb54e41dea] of/overlay: Remove unused variable git bisect bad d3a891652adb82e1973348c703a597cb54e41dea # bad: [20aa4d8ae8d2ada8f959364ebc096b8841245456] Documentation: DT: Renamed of-serial.txt to 8250.txt git bisect bad 20aa4d8ae8d2ada8f959364ebc096b8841245456 Thanks! -- Pranith -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux panic on 4.0.0-rc4
On Mon, Mar 16, 2015 at 11:18 PM, Peter Hurley pe...@hurleysoftware.com wrote: On 03/16/2015 11:12 PM, Pranith Kumar wrote: On Mon, Mar 16, 2015 at 10:58 PM, Peter Hurley pe...@hurleysoftware.com wrote: What is your init? I am using systemd from debian unstable. Do you have a stdout-path property defined in your dts to a serial console you're not actually using? I am using tty0 as my console. From the config which I posted, it has: CONFIG_CMDLINE=console=ttyS0,9600 console=tty0 I am not using any device tree file. Ok; there was some reported breakage on PowerMac wrt to 'stdout-path' changes I made, so I thought I'd check if that might have affected your setup as well. And the painful slow bisecting did lead to that commit: Bisecting: 0 revisions left to test after this (roughly 0 steps) [2fa645cb2703d9b3786d850db815414dfeefa51d] of: Fix premature bootconsole disable with 'stdout-path' $ git show 2fa645cb2703d9b3786d850db815414dfeefa51d commit 2fa645cb2703d9b3786d850db815414dfeefa51d Author: Peter Hurley pe...@hurleysoftware.com Date: Sun Mar 1 12:21:22 2015 -0500 of: Fix premature bootconsole disable with 'stdout-path' Support for devicetree serial consoles via 'stdout-path' causes bootconsoles to be disabled when the vt dummy console loads, since there is no preferred console (the preferred console is not added until the device is probed). Ensure there is at least a preferred console, even if never matched. More info: $ git bisect log git bisect start # bad: [06e5801b8cb3fc057d88cb4dc03c0b64b2744cda] Linux 4.0-rc4 git bisect bad 06e5801b8cb3fc057d88cb4dc03c0b64b2744cda # good: [bfa76d49576599a4b9f9b7a71f23d73d6dcff735] Linux 3.19 git bisect good bfa76d49576599a4b9f9b7a71f23d73d6dcff735 # good: [1a67e256dbd80f47f339c4a88c34deee12489aa0] ARM: mvebu: ISL12057 rtc chip can now wake up RN102, RN102 and RN2120 git bisect good 1a67e256dbd80f47f339c4a88c34deee12489aa0 # good: [878ba61aa98cbb97a513757800e77613f856a029] Merge tag 'soc-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc git bisect good 878ba61aa98cbb97a513757800e77613f856a029 # good: [18a8d49973667aa016e68826eeb374788b7c63b0] Merge tag 'clk-for-linus-3.20' of git://git.linaro.org/people/mike.turquette/linux git bisect good 18a8d49973667aa016e68826eeb374788b7c63b0 # good: [bfda4031621b048ca634abc5f6bce1aa490ac4e5] MAINTAINERS: Add myself as co-maintainer to the legacy support of the mvebu SoCs git bisect good bfda4031621b048ca634abc5f6bce1aa490ac4e5 # good: [29191c7f71aa55401c83df60482417d3c511edde] Merge tag 'char-misc-4.0-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc git bisect good 29191c7f71aa55401c83df60482417d3c511edde # good: [36bef88380037288d5b575ed2029de694533b1ec] Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net git bisect good 36bef88380037288d5b575ed2029de694533b1ec # bad: [3d52c5bdbe57e2b45d9cc8da930b9ab42b5198c4] Merge tag 'devicetree-fixes-for-4.0' of git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux git bisect bad 3d52c5bdbe57e2b45d9cc8da930b9ab42b5198c4 # good: [91e9134eda82b57952fdbdb0c5990a7a6609ff13] Merge tag 'pci-v4.0-fixes-2' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci git bisect good 91e9134eda82b57952fdbdb0c5990a7a6609ff13 # good: [c202baf017aea0c860e53131bc55bb1af7177e76] Merge branch 'akpm' (patches from Andrew) git bisect good c202baf017aea0c860e53131bc55bb1af7177e76 # bad: [649022e08e4798ffb6e9b11c56ee6b2c62465d11] of/unittest: Fix the wrong expected value in of_selftest_property_string git bisect bad 649022e08e4798ffb6e9b11c56ee6b2c62465d11 # good: [2c192699a7050ef5bdf1e2cc95fdddfbcf524509] Merge tag 'v4.0-rc3' into HEAD git bisect good 2c192699a7050ef5bdf1e2cc95fdddfbcf524509 # bad: [d3a891652adb82e1973348c703a597cb54e41dea] of/overlay: Remove unused variable git bisect bad d3a891652adb82e1973348c703a597cb54e41dea # bad: [20aa4d8ae8d2ada8f959364ebc096b8841245456] Documentation: DT: Renamed of-serial.txt to 8250.txt git bisect bad 20aa4d8ae8d2ada8f959364ebc096b8841245456 Thanks! -- Pranith -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux panic on 4.0.0-rc4
On Tue, Mar 17, 2015 at 4:03 PM, Peter Hurley pe...@hurleysoftware.com wrote: Can you send me a complete dmesg capture from a boot with this commit reverted? Here it is. Let me know if you want any boot options enabled. I removed both debug and verbose boot options. [0.00] Using PowerMac machine description [0.00] Total memory = 1024MB; using 2048kB for hash table (at cfe0) [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 4.0.0-rc4+ (pranith@macmini) (gcc version 4.9.2 (Debian 4.9.2-10) ) #67 Tue Mar 17 12:40:16 EDT 2015 [0.00] Found initrd at 0xc130:0xc1692000 [0.00] Found UniNorth memory controller host bridge @ 0xf800 revision: 0xd2 [0.00] Mapped at 0xff7c [0.00] Found a Intrepid mac-io controller, rev: 0, mapped at 0xff74 [0.00] Processor NAP mode on idle enabled. [0.00] PowerMac motherboard: Mac mini (Late 2005) [0.00] bootconsole [udbg0] enabled [0.00] Found UniNorth PCI host bridge at 0xf000. Firmware bus number: 0-0 [0.00] PCI host bridge /pci@f000 ranges: [0.00] MEM 0xf100..0xf1ff - 0xf100 [0.00] IO 0xf000..0xf07f - 0x [0.00] MEM 0x9000..0x9fff - 0x9000 [0.00] Found UniNorth PCI host bridge at 0xf200. Firmware bus number: 0-0 [0.00] PCI host bridge /pci@f200 (primary) ranges: [0.00] MEM 0xf300..0xf3ff - 0xf300 [0.00] IO 0xf200..0xf27f - 0x [0.00] MEM 0x8000..0x8fff - 0x8000 [0.00] Found UniNorth PCI host bridge at 0xf400. Firmware bus number: 0-0 [0.00] PCI host bridge /pci@f400 ranges: [0.00] MEM 0xf500..0xf5ff - 0xf500 [0.00] IO 0xf400..0xf47f - 0x [0.00] via-pmu: Server Mode is disabled [0.00] PMU driver v2 initialized for Core99, firmware: 55 [0.00] Top of RAM: 0x4000, Total RAM: 0x4000 [0.00] Memory hole size: 0MB [0.00] Zone ranges: [0.00] DMA [mem 0x-0x2fff] [0.00] Normal empty [0.00] HighMem [mem 0x3000-0x3fff] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x-0x3fff] [0.00] Initmem setup node 0 [mem 0x-0x3fff] [0.00] On node 0 totalpages: 262144 [0.00] free_area_init_node: node 0, pgdat c05a4a64, node_mem_map ef6e3000 [0.00] DMA zone: 1728 pages used for memmap [0.00] DMA zone: 0 pages reserved [0.00] DMA zone: 196608 pages, LIFO batch:31 [0.00] HighMem zone: 65536 pages, LIFO batch:15 [0.00] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 [0.00] pcpu-alloc: [0] 0 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260416 [0.00] Kernel command line: root=UUID=7252209a-6106-41c2-90a3-45b85ac47837 ro video=radeonfb:off video=offb:off radeon.modeset=1 radeon.agpmode=-1 [0.00] PID hash table entries: 4096 (order: 2, 16384 bytes) [0.00] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [0.00] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [0.00] Sorting __ex_table... [0.00] Memory: 1026292K/1048576K available (3980K kernel code, 212K rwdata, 1384K rodata, 240K init, 294K bss, 22284K reserved, 0K cma-reserved, 262144K highmem) [0.00] Kernel virtual memory layout: [0.00] * 0xfffcf000..0xf000 : fixmap [0.00] * 0xff80..0xffc0 : highmem PTEs [0.00] * 0xfdde4000..0xff80 : early ioremap [0.00] * 0xf100..0xfdde4000 : vmalloc ioremap [0.00] NR_IRQS:512 nr_irqs:512 16 [0.00] mpic: Resetting [0.00] mpic: Setting up MPIC MPIC 1version 1.2 at 8004, max 1 CPUs [0.00] mpic: ISU size: 64, shift: 6, mask: 3f [0.00] mpic: Initializing for 64 sources [0.00] time_init: decrementer frequency = 41.600571 MHz [0.00] time_init: processor frequency = 1333.28 MHz [0.08] clocksource: timebase mult[1809c2fe] shift[24] registered [0.000394] clockevent: decrementer mult[aa655c4] shift[32] cpu[0] [0.000647] Console: colour dummy device 80x25 [0.000998] console [tty0] enabled [0.001333] bootconsole [udbg0] disabled [0.001859] pid_max: default: 32768 minimum: 301 [0.001902] Mount-cache hash table entries: 2048 (order: 1,
Re: linux panic on 4.0.0-rc4
On 03/17/2015 04:16 PM, Pranith Kumar wrote: On Tue, Mar 17, 2015 at 4:13 PM, Peter Hurley pe...@hurleysoftware.com wrote: On 03/17/2015 04:07 PM, Pranith Kumar wrote: On Tue, Mar 17, 2015 at 4:03 PM, Peter Hurley pe...@hurleysoftware.com wrote: Can you send me a complete dmesg capture from a boot with this commit reverted? Here it is. Let me know if you want any boot options enabled. I removed both debug and verbose boot options. Ok, thanks. This is just like Andreas' problem: with my patch, there is _no_ console. Note those console command line options in your config aren't actually in your kernel command line. That really threw me; I couldn't figure out how you didn't have a tty0 console. [0.00] Kernel command line: root=UUID=7252209a-6106-41c2-90a3-45b85ac47837 ro video=radeonfb:off video=offb:off radeon.modeset=1 radeon.agpmode=-1 Hmm, interesting. These arguments are passed from the yaboot.conf which has a line as follows: append=video=radeonfb:off video=offb:off radeon.modeset=1 radeon.agpmode=-1 I thought this would append these arguments to the default kernel command line argument in the config. Apparently it is not. So, the resolution for this is to add the console argument to yaboot.conf I guess, right? No, I'm sending a revert anyway, but I thought I'd let you know. Regards, Peter Hurley -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux panic on 4.0.0-rc4
On 03/17/2015 02:33 AM, Pranith Kumar wrote: On Mon, Mar 16, 2015 at 11:18 PM, Peter Hurley pe...@hurleysoftware.com wrote: On 03/16/2015 11:12 PM, Pranith Kumar wrote: On Mon, Mar 16, 2015 at 10:58 PM, Peter Hurley pe...@hurleysoftware.com wrote: What is your init? I am using systemd from debian unstable. Do you have a stdout-path property defined in your dts to a serial console you're not actually using? I am using tty0 as my console. From the config which I posted, it has: CONFIG_CMDLINE=console=ttyS0,9600 console=tty0 I am not using any device tree file. Ok; there was some reported breakage on PowerMac wrt to 'stdout-path' changes I made, so I thought I'd check if that might have affected your setup as well. And the painful slow bisecting did lead to that commit: Bisecting: 0 revisions left to test after this (roughly 0 steps) [2fa645cb2703d9b3786d850db815414dfeefa51d] of: Fix premature bootconsole disable with 'stdout-path' $ git show 2fa645cb2703d9b3786d850db815414dfeefa51d commit 2fa645cb2703d9b3786d850db815414dfeefa51d Author: Peter Hurley pe...@hurleysoftware.com Date: Sun Mar 1 12:21:22 2015 -0500 of: Fix premature bootconsole disable with 'stdout-path' Can you send me a complete dmesg capture from a boot with this commit reverted? -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux panic on 4.0.0-rc4
On Tue, Mar 17, 2015 at 4:13 PM, Peter Hurley pe...@hurleysoftware.com wrote: On 03/17/2015 04:07 PM, Pranith Kumar wrote: On Tue, Mar 17, 2015 at 4:03 PM, Peter Hurley pe...@hurleysoftware.com wrote: Can you send me a complete dmesg capture from a boot with this commit reverted? Here it is. Let me know if you want any boot options enabled. I removed both debug and verbose boot options. Ok, thanks. This is just like Andreas' problem: with my patch, there is _no_ console. Note those console command line options in your config aren't actually in your kernel command line. That really threw me; I couldn't figure out how you didn't have a tty0 console. [0.00] Kernel command line: root=UUID=7252209a-6106-41c2-90a3-45b85ac47837 ro video=radeonfb:off video=offb:off radeon.modeset=1 radeon.agpmode=-1 Hmm, interesting. These arguments are passed from the yaboot.conf which has a line as follows: append=video=radeonfb:off video=offb:off radeon.modeset=1 radeon.agpmode=-1 I thought this would append these arguments to the default kernel command line argument in the config. Apparently it is not. So, the resolution for this is to add the console argument to yaboot.conf I guess, right? -- Pranith -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux panic on 4.0.0-rc4
On 03/17/2015 04:07 PM, Pranith Kumar wrote: On Tue, Mar 17, 2015 at 4:03 PM, Peter Hurley pe...@hurleysoftware.com wrote: Can you send me a complete dmesg capture from a boot with this commit reverted? Here it is. Let me know if you want any boot options enabled. I removed both debug and verbose boot options. Ok, thanks. This is just like Andreas' problem: with my patch, there is _no_ console. Note those console command line options in your config aren't actually in your kernel command line. That really threw me; I couldn't figure out how you didn't have a tty0 console. [0.00] Kernel command line: root=UUID=7252209a-6106-41c2-90a3-45b85ac47837 ro video=radeonfb:off video=offb:off radeon.modeset=1 radeon.agpmode=-1 Regards, Peter Hurley -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux panic on 4.0.0-rc4
On 03/16/2015 11:12 PM, Pranith Kumar wrote: > On Mon, Mar 16, 2015 at 10:58 PM, Peter Hurley > wrote: What is your init? >>> >>> I am using systemd from debian unstable. >> >> Do you have a stdout-path property defined in your dts to a serial >> console you're not actually using? >> > > I am using tty0 as my console. From the config which I posted, it has: > > CONFIG_CMDLINE="console=ttyS0,9600 console=tty0" > > I am not using any device tree file. Ok; there was some reported breakage on PowerMac wrt to 'stdout-path' changes I made, so I thought I'd check if that might have affected your setup as well. Regards, Peter Hurley -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux panic on 4.0.0-rc4
On Mon, Mar 16, 2015 at 10:58 PM, Peter Hurley wrote: >>> What is your init? >> >> I am using systemd from debian unstable. > > Do you have a stdout-path property defined in your dts to a serial > console you're not actually using? > I am using tty0 as my console. From the config which I posted, it has: CONFIG_CMDLINE="console=ttyS0,9600 console=tty0" I am not using any device tree file. -- Pranith -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux panic on 4.0.0-rc4
On 03/16/2015 10:02 PM, Pranith Kumar wrote: > On Mon, Mar 16, 2015 at 7:22 PM, Michael Ellerman wrote: >> >> The log shows that init is being killed, that's what's causing the panic. >> >> The exitcode of init is 0x200, which due to the vagaries of UNIX is I think >> an >> "exit status" of 2 in the common usage. >> >> But it suggests that your init is just exiting for some reason? >> > > Yeah, seems like that. Not sure why though. git bisect seems to be the > only option. > >> What is your init? > > I am using systemd from debian unstable. Do you have a stdout-path property defined in your dts to a serial console you're not actually using? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux panic on 4.0.0-rc4
On Mon, Mar 16, 2015 at 7:22 PM, Michael Ellerman wrote: > > The log shows that init is being killed, that's what's causing the panic. > > The exitcode of init is 0x200, which due to the vagaries of UNIX is I think an > "exit status" of 2 in the common usage. > > But it suggests that your init is just exiting for some reason? > Yeah, seems like that. Not sure why though. git bisect seems to be the only option. > What is your init? I am using systemd from debian unstable. -- Pranith -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux panic on 4.0.0-rc4
On Mon, 2015-03-16 at 09:30 -0400, Pranith Kumar wrote: > On Mon, Mar 16, 2015 at 4:16 AM, Michael Ellerman wrote: > > On Mon, 2015-03-16 at 01:34 -0400, Pranith Kumar wrote: > >> On Mon, Mar 16, 2015 at 1:11 AM, Pranith Kumar > >> wrote: > >> > Hello, > >> > > >> > I have a power mac mini 32-bit system. > >> > > >> ... > >> > You can see the panic message here: http://imgur.com/s1lH15g. (there > >> > is no log and I have no serial console). > >> > >> There was some debug code in there when it hit. The actual hang seems > >> to be in printk_late_init(). It does not return from this. May be this > >> is a hint? > > > > That is where the boot consoles get disabled and it switches to the "real" > > console. It suggests that the system is not "hung" there but you just lost > > output. > > > > Try booting with "keep_bootcon" ? > > I tried this and got to the same place as in the first mail: > http://imgur.com/s1lH15g > > There is a kernel panic with the message printed. Any more suggestions > to how to debug this? The log shows that init is being killed, that's what's causing the panic. The exitcode of init is 0x200, which due to the vagaries of UNIX is I think an "exit status" of 2 in the common usage. But it suggests that your init is just exiting for some reason? What is your init? cheers -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux panic on 4.0.0-rc4
On 03/16/2015 09:30 AM, Pranith Kumar wrote: > On Mon, Mar 16, 2015 at 4:16 AM, Michael Ellerman wrote: >> On Mon, 2015-03-16 at 01:34 -0400, Pranith Kumar wrote: >>> On Mon, Mar 16, 2015 at 1:11 AM, Pranith Kumar >>> wrote: Hello, I have a power mac mini 32-bit system. >>> ... You can see the panic message here: http://imgur.com/s1lH15g. (there is no log and I have no serial console). >>> >>> There was some debug code in there when it hit. The actual hang seems >>> to be in printk_late_init(). It does not return from this. May be this >>> is a hint? >> >> That is where the boot consoles get disabled and it switches to the "real" >> console. It suggests that the system is not "hung" there but you just lost >> output. >> >> Try booting with "keep_bootcon" ? > > I tried this and got to the same place as in the first mail: > http://imgur.com/s1lH15g > > There is a kernel panic with the message printed. Any more suggestions > to how to debug this? git bisect. Regards, Peter Hurley -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux panic on 4.0.0-rc4
On Mon, Mar 16, 2015 at 4:16 AM, Michael Ellerman wrote: > On Mon, 2015-03-16 at 01:34 -0400, Pranith Kumar wrote: >> On Mon, Mar 16, 2015 at 1:11 AM, Pranith Kumar wrote: >> > Hello, >> > >> > I have a power mac mini 32-bit system. >> > >> ... >> > You can see the panic message here: http://imgur.com/s1lH15g. (there >> > is no log and I have no serial console). >> >> There was some debug code in there when it hit. The actual hang seems >> to be in printk_late_init(). It does not return from this. May be this >> is a hint? > > That is where the boot consoles get disabled and it switches to the "real" > console. It suggests that the system is not "hung" there but you just lost > output. > > Try booting with "keep_bootcon" ? I tried this and got to the same place as in the first mail: http://imgur.com/s1lH15g There is a kernel panic with the message printed. Any more suggestions to how to debug this? -- Pranith -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux panic on 4.0.0-rc4
On Mon, 2015-03-16 at 01:34 -0400, Pranith Kumar wrote: > On Mon, Mar 16, 2015 at 1:11 AM, Pranith Kumar wrote: > > Hello, > > > > I have a power mac mini 32-bit system. > > > ... > > You can see the panic message here: http://imgur.com/s1lH15g. (there > > is no log and I have no serial console). > > There was some debug code in there when it hit. The actual hang seems > to be in printk_late_init(). It does not return from this. May be this > is a hint? That is where the boot consoles get disabled and it switches to the "real" console. It suggests that the system is not "hung" there but you just lost output. Try booting with "keep_bootcon" ? If that doesn't help try booting with "udbg-immortal". cheers -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux panic on 4.0.0-rc4
On Mon, Mar 16, 2015 at 7:22 PM, Michael Ellerman m...@ellerman.id.au wrote: The log shows that init is being killed, that's what's causing the panic. The exitcode of init is 0x200, which due to the vagaries of UNIX is I think an exit status of 2 in the common usage. But it suggests that your init is just exiting for some reason? Yeah, seems like that. Not sure why though. git bisect seems to be the only option. What is your init? I am using systemd from debian unstable. -- Pranith -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux panic on 4.0.0-rc4
On 03/16/2015 10:02 PM, Pranith Kumar wrote: On Mon, Mar 16, 2015 at 7:22 PM, Michael Ellerman m...@ellerman.id.au wrote: The log shows that init is being killed, that's what's causing the panic. The exitcode of init is 0x200, which due to the vagaries of UNIX is I think an exit status of 2 in the common usage. But it suggests that your init is just exiting for some reason? Yeah, seems like that. Not sure why though. git bisect seems to be the only option. What is your init? I am using systemd from debian unstable. Do you have a stdout-path property defined in your dts to a serial console you're not actually using? -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux panic on 4.0.0-rc4
On Mon, Mar 16, 2015 at 10:58 PM, Peter Hurley pe...@hurleysoftware.com wrote: What is your init? I am using systemd from debian unstable. Do you have a stdout-path property defined in your dts to a serial console you're not actually using? I am using tty0 as my console. From the config which I posted, it has: CONFIG_CMDLINE=console=ttyS0,9600 console=tty0 I am not using any device tree file. -- Pranith -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux panic on 4.0.0-rc4
On 03/16/2015 11:12 PM, Pranith Kumar wrote: On Mon, Mar 16, 2015 at 10:58 PM, Peter Hurley pe...@hurleysoftware.com wrote: What is your init? I am using systemd from debian unstable. Do you have a stdout-path property defined in your dts to a serial console you're not actually using? I am using tty0 as my console. From the config which I posted, it has: CONFIG_CMDLINE=console=ttyS0,9600 console=tty0 I am not using any device tree file. Ok; there was some reported breakage on PowerMac wrt to 'stdout-path' changes I made, so I thought I'd check if that might have affected your setup as well. Regards, Peter Hurley -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux panic on 4.0.0-rc4
On Mon, Mar 16, 2015 at 4:16 AM, Michael Ellerman m...@ellerman.id.au wrote: On Mon, 2015-03-16 at 01:34 -0400, Pranith Kumar wrote: On Mon, Mar 16, 2015 at 1:11 AM, Pranith Kumar bobby.pr...@gmail.com wrote: Hello, I have a power mac mini 32-bit system. ... You can see the panic message here: http://imgur.com/s1lH15g. (there is no log and I have no serial console). There was some debug code in there when it hit. The actual hang seems to be in printk_late_init(). It does not return from this. May be this is a hint? That is where the boot consoles get disabled and it switches to the real console. It suggests that the system is not hung there but you just lost output. Try booting with keep_bootcon ? I tried this and got to the same place as in the first mail: http://imgur.com/s1lH15g There is a kernel panic with the message printed. Any more suggestions to how to debug this? -- Pranith -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux panic on 4.0.0-rc4
On 03/16/2015 09:30 AM, Pranith Kumar wrote: On Mon, Mar 16, 2015 at 4:16 AM, Michael Ellerman m...@ellerman.id.au wrote: On Mon, 2015-03-16 at 01:34 -0400, Pranith Kumar wrote: On Mon, Mar 16, 2015 at 1:11 AM, Pranith Kumar bobby.pr...@gmail.com wrote: Hello, I have a power mac mini 32-bit system. ... You can see the panic message here: http://imgur.com/s1lH15g. (there is no log and I have no serial console). There was some debug code in there when it hit. The actual hang seems to be in printk_late_init(). It does not return from this. May be this is a hint? That is where the boot consoles get disabled and it switches to the real console. It suggests that the system is not hung there but you just lost output. Try booting with keep_bootcon ? I tried this and got to the same place as in the first mail: http://imgur.com/s1lH15g There is a kernel panic with the message printed. Any more suggestions to how to debug this? git bisect. Regards, Peter Hurley -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux panic on 4.0.0-rc4
On Mon, 2015-03-16 at 09:30 -0400, Pranith Kumar wrote: On Mon, Mar 16, 2015 at 4:16 AM, Michael Ellerman m...@ellerman.id.au wrote: On Mon, 2015-03-16 at 01:34 -0400, Pranith Kumar wrote: On Mon, Mar 16, 2015 at 1:11 AM, Pranith Kumar bobby.pr...@gmail.com wrote: Hello, I have a power mac mini 32-bit system. ... You can see the panic message here: http://imgur.com/s1lH15g. (there is no log and I have no serial console). There was some debug code in there when it hit. The actual hang seems to be in printk_late_init(). It does not return from this. May be this is a hint? That is where the boot consoles get disabled and it switches to the real console. It suggests that the system is not hung there but you just lost output. Try booting with keep_bootcon ? I tried this and got to the same place as in the first mail: http://imgur.com/s1lH15g There is a kernel panic with the message printed. Any more suggestions to how to debug this? The log shows that init is being killed, that's what's causing the panic. The exitcode of init is 0x200, which due to the vagaries of UNIX is I think an exit status of 2 in the common usage. But it suggests that your init is just exiting for some reason? What is your init? cheers -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux panic on 4.0.0-rc4
On Mon, 2015-03-16 at 01:34 -0400, Pranith Kumar wrote: On Mon, Mar 16, 2015 at 1:11 AM, Pranith Kumar bobby.pr...@gmail.com wrote: Hello, I have a power mac mini 32-bit system. ... You can see the panic message here: http://imgur.com/s1lH15g. (there is no log and I have no serial console). There was some debug code in there when it hit. The actual hang seems to be in printk_late_init(). It does not return from this. May be this is a hint? That is where the boot consoles get disabled and it switches to the real console. It suggests that the system is not hung there but you just lost output. Try booting with keep_bootcon ? If that doesn't help try booting with udbg-immortal. cheers -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux panic on 4.0.0-rc4
On Mon, Mar 16, 2015 at 1:11 AM, Pranith Kumar wrote: > Hello, > > I have a power mac mini 32-bit system. > ... > You can see the panic message here: http://imgur.com/s1lH15g. (there > is no log and I have no serial console). There was some debug code in there when it hit. The actual hang seems to be in printk_late_init(). It does not return from this. May be this is a hint? Please let me know if you need more information to debug this. Thanks! > > Let me know if you need any more information. Config follows: > > # > # Automatically generated file; DO NOT EDIT. > # Linux/powerpc 4.0.0-rc4 Kernel Configuration > # > # CONFIG_PPC64 is not set > > # > # Processor support > # > CONFIG_PPC_BOOK3S_32=y > # CONFIG_PPC_85xx is not set > # CONFIG_PPC_8xx is not set > # CONFIG_40x is not set > # CONFIG_44x is not set > # CONFIG_E200 is not set > CONFIG_PPC_BOOK3S=y > CONFIG_6xx=y > CONFIG_PPC_FPU=y > CONFIG_ALTIVEC=y > CONFIG_PPC_STD_MMU=y > CONFIG_PPC_STD_MMU_32=y > # CONFIG_PPC_MM_SLICES is not set > CONFIG_PPC_HAVE_PMU_SUPPORT=y > CONFIG_PPC_PERF_CTRS=y > # CONFIG_SMP is not set > # CONFIG_PPC_DOORBELL is not set > CONFIG_CPU_BIG_ENDIAN=y > # CONFIG_CPU_LITTLE_ENDIAN is not set > CONFIG_PPC32=y > CONFIG_32BIT=y > CONFIG_WORD_SIZE=32 > # CONFIG_ARCH_PHYS_ADDR_T_64BIT is not set > # CONFIG_ARCH_DMA_ADDR_T_64BIT is not set > CONFIG_MMU=y > # CONFIG_HAVE_SETUP_PER_CPU_AREA is not set > # CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK is not set > CONFIG_NR_IRQS=512 > 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_GENERIC_HWEIGHT=y > CONFIG_PPC=y > # CONFIG_GENERIC_CSUM is not set > CONFIG_EARLY_PRINTK=y > CONFIG_PANIC_TIMEOUT=0 > CONFIG_GENERIC_NVRAM=y > CONFIG_SCHED_OMIT_FRAME_POINTER=y > CONFIG_ARCH_MAY_HAVE_PC_FDC=y > CONFIG_PPC_OF=y > CONFIG_PPC_UDBG_16550=y > # CONFIG_GENERIC_TBSYNC is not set > CONFIG_AUDIT_ARCH=y > CONFIG_GENERIC_BUG=y > # CONFIG_EPAPR_BOOT is not set > # 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_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y > CONFIG_ARCH_SUPPORTS_UPROBES=y > CONFIG_PPC_EMULATE_SSTEP=y > CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" > CONFIG_IRQ_WORK=y > > # > # General setup > # > CONFIG_BROKEN_ON_SMP=y > CONFIG_INIT_ENV_ARG_LIMIT=32 > CONFIG_CROSS_COMPILE="" > # CONFIG_COMPILE_TEST is not set > CONFIG_LOCALVERSION="" > # CONFIG_LOCALVERSION_AUTO is not set > CONFIG_DEFAULT_HOSTNAME="(none)" > CONFIG_SWAP=y > CONFIG_SYSVIPC=y > CONFIG_SYSVIPC_SYSCTL=y > CONFIG_POSIX_MQUEUE=y > CONFIG_POSIX_MQUEUE_SYSCTL=y > CONFIG_CROSS_MEMORY_ATTACH=y > CONFIG_FHANDLE=y > CONFIG_USELIB=y > CONFIG_AUDIT=y > CONFIG_HAVE_ARCH_AUDITSYSCALL=y > CONFIG_AUDITSYSCALL=y > CONFIG_AUDIT_WATCH=y > CONFIG_AUDIT_TREE=y > > # > # IRQ subsystem > # > CONFIG_GENERIC_IRQ_SHOW=y > CONFIG_GENERIC_IRQ_SHOW_LEVEL=y > CONFIG_IRQ_DOMAIN=y > CONFIG_GENERIC_MSI_IRQ=y > CONFIG_IRQ_FORCED_THREADING=y > CONFIG_SPARSE_IRQ=y > CONFIG_GENERIC_TIME_VSYSCALL_OLD=y > CONFIG_GENERIC_CLOCKEVENTS=y > CONFIG_GENERIC_CLOCKEVENTS_BUILD=y > CONFIG_GENERIC_CMOS_UPDATE=y > > # > # Timers subsystem > # > CONFIG_TICK_ONESHOT=y > CONFIG_NO_HZ_COMMON=y > # CONFIG_HZ_PERIODIC is not set > CONFIG_NO_HZ_IDLE=y > # CONFIG_NO_HZ is not set > CONFIG_HIGH_RES_TIMERS=y > > # > # CPU/Task time and stats accounting > # > CONFIG_TICK_CPU_ACCOUNTING=y > CONFIG_BSD_PROCESS_ACCT=y > CONFIG_BSD_PROCESS_ACCT_V3=y > CONFIG_TASKSTATS=y > CONFIG_TASK_DELAY_ACCT=y > CONFIG_TASK_XACCT=y > CONFIG_TASK_IO_ACCOUNTING=y > > # > # RCU Subsystem > # > CONFIG_TINY_RCU=y > CONFIG_SRCU=y > CONFIG_TASKS_RCU=y > # CONFIG_RCU_STALL_COMMON is not set > # CONFIG_TREE_RCU_TRACE is not set > CONFIG_RCU_KTHREAD_PRIO=0 > CONFIG_BUILD_BIN2C=y > CONFIG_IKCONFIG=m > # CONFIG_IKCONFIG_PROC is not set > CONFIG_LOG_BUF_SHIFT=17 > CONFIG_CGROUPS=y > # CONFIG_CGROUP_DEBUG is not set > CONFIG_CGROUP_FREEZER=y > CONFIG_CGROUP_DEVICE=y > CONFIG_CPUSETS=y > CONFIG_PROC_PID_CPUSET=y > CONFIG_CGROUP_CPUACCT=y > CONFIG_PAGE_COUNTER=y > CONFIG_MEMCG=y > CONFIG_MEMCG_SWAP=y > # CONFIG_MEMCG_SWAP_ENABLED is not set > CONFIG_CGROUP_PERF=y > CONFIG_CGROUP_SCHED=y > CONFIG_FAIR_GROUP_SCHED=y > # CONFIG_CFS_BANDWIDTH is not set > # CONFIG_RT_GROUP_SCHED is not set > CONFIG_BLK_CGROUP=y > # CONFIG_DEBUG_BLK_CGROUP is not set > CONFIG_CHECKPOINT_RESTORE=y > CONFIG_NAMESPACES=y > CONFIG_UTS_NS=y > CONFIG_IPC_NS=y > CONFIG_USER_NS=y > CONFIG_PID_NS=y > CONFIG_NET_NS=y > CONFIG_SCHED_AUTOGROUP=y > # CONFIG_SYSFS_DEPRECATED is not set > CONFIG_RELAY=y > CONFIG_BLK_DEV_INITRD=y > CONFIG_INITRAMFS_SOURCE="" > CONFIG_RD_GZIP=y > CONFIG_RD_BZIP2=y > CONFIG_RD_LZMA=y > CONFIG_RD_XZ=y > CONFIG_RD_LZO=y > CONFIG_RD_LZ4=y > # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set > CONFIG_SYSCTL=y > CONFIG_ANON_INODES=y >
linux panic on 4.0.0-rc4
Hello, I have a power mac mini 32-bit system. I am getting a kernel panic with the latest rc kernel. The last kernel which worked on this which I remember booting was 3.19-rc5. You can see the panic message here: http://imgur.com/s1lH15g. (there is no log and I have no serial console). Let me know if you need any more information. Config follows: # # Automatically generated file; DO NOT EDIT. # Linux/powerpc 4.0.0-rc4 Kernel Configuration # # CONFIG_PPC64 is not set # # Processor support # CONFIG_PPC_BOOK3S_32=y # CONFIG_PPC_85xx is not set # CONFIG_PPC_8xx is not set # CONFIG_40x is not set # CONFIG_44x is not set # CONFIG_E200 is not set CONFIG_PPC_BOOK3S=y CONFIG_6xx=y CONFIG_PPC_FPU=y CONFIG_ALTIVEC=y CONFIG_PPC_STD_MMU=y CONFIG_PPC_STD_MMU_32=y # CONFIG_PPC_MM_SLICES is not set CONFIG_PPC_HAVE_PMU_SUPPORT=y CONFIG_PPC_PERF_CTRS=y # CONFIG_SMP is not set # CONFIG_PPC_DOORBELL is not set CONFIG_CPU_BIG_ENDIAN=y # CONFIG_CPU_LITTLE_ENDIAN is not set CONFIG_PPC32=y CONFIG_32BIT=y CONFIG_WORD_SIZE=32 # CONFIG_ARCH_PHYS_ADDR_T_64BIT is not set # CONFIG_ARCH_DMA_ADDR_T_64BIT is not set CONFIG_MMU=y # CONFIG_HAVE_SETUP_PER_CPU_AREA is not set # CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK is not set CONFIG_NR_IRQS=512 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_GENERIC_HWEIGHT=y CONFIG_PPC=y # CONFIG_GENERIC_CSUM is not set CONFIG_EARLY_PRINTK=y CONFIG_PANIC_TIMEOUT=0 CONFIG_GENERIC_NVRAM=y CONFIG_SCHED_OMIT_FRAME_POINTER=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_PPC_OF=y CONFIG_PPC_UDBG_16550=y # CONFIG_GENERIC_TBSYNC is not set CONFIG_AUDIT_ARCH=y CONFIG_GENERIC_BUG=y # CONFIG_EPAPR_BOOT is not set # 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_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y CONFIG_ARCH_SUPPORTS_UPROBES=y CONFIG_PPC_EMULATE_SSTEP=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" CONFIG_IRQ_WORK=y # # General setup # CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_CROSS_COMPILE="" # CONFIG_COMPILE_TEST is not set CONFIG_LOCALVERSION="" # CONFIG_LOCALVERSION_AUTO is not set CONFIG_DEFAULT_HOSTNAME="(none)" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_POSIX_MQUEUE_SYSCTL=y CONFIG_CROSS_MEMORY_ATTACH=y CONFIG_FHANDLE=y CONFIG_USELIB=y CONFIG_AUDIT=y CONFIG_HAVE_ARCH_AUDITSYSCALL=y CONFIG_AUDITSYSCALL=y CONFIG_AUDIT_WATCH=y CONFIG_AUDIT_TREE=y # # IRQ subsystem # CONFIG_GENERIC_IRQ_SHOW=y CONFIG_GENERIC_IRQ_SHOW_LEVEL=y CONFIG_IRQ_DOMAIN=y CONFIG_GENERIC_MSI_IRQ=y CONFIG_IRQ_FORCED_THREADING=y CONFIG_SPARSE_IRQ=y CONFIG_GENERIC_TIME_VSYSCALL_OLD=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BUILD=y CONFIG_GENERIC_CMOS_UPDATE=y # # Timers subsystem # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ_COMMON=y # CONFIG_HZ_PERIODIC is not set CONFIG_NO_HZ_IDLE=y # CONFIG_NO_HZ is not set CONFIG_HIGH_RES_TIMERS=y # # CPU/Task time and stats accounting # CONFIG_TICK_CPU_ACCOUNTING=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_BSD_PROCESS_ACCT_V3=y CONFIG_TASKSTATS=y CONFIG_TASK_DELAY_ACCT=y CONFIG_TASK_XACCT=y CONFIG_TASK_IO_ACCOUNTING=y # # RCU Subsystem # CONFIG_TINY_RCU=y CONFIG_SRCU=y CONFIG_TASKS_RCU=y # CONFIG_RCU_STALL_COMMON is not set # CONFIG_TREE_RCU_TRACE is not set CONFIG_RCU_KTHREAD_PRIO=0 CONFIG_BUILD_BIN2C=y CONFIG_IKCONFIG=m # CONFIG_IKCONFIG_PROC is not set CONFIG_LOG_BUF_SHIFT=17 CONFIG_CGROUPS=y # CONFIG_CGROUP_DEBUG is not set CONFIG_CGROUP_FREEZER=y CONFIG_CGROUP_DEVICE=y CONFIG_CPUSETS=y CONFIG_PROC_PID_CPUSET=y CONFIG_CGROUP_CPUACCT=y CONFIG_PAGE_COUNTER=y CONFIG_MEMCG=y CONFIG_MEMCG_SWAP=y # CONFIG_MEMCG_SWAP_ENABLED is not set CONFIG_CGROUP_PERF=y CONFIG_CGROUP_SCHED=y CONFIG_FAIR_GROUP_SCHED=y # CONFIG_CFS_BANDWIDTH is not set # CONFIG_RT_GROUP_SCHED is not set CONFIG_BLK_CGROUP=y # CONFIG_DEBUG_BLK_CGROUP is not set CONFIG_CHECKPOINT_RESTORE=y CONFIG_NAMESPACES=y CONFIG_UTS_NS=y CONFIG_IPC_NS=y CONFIG_USER_NS=y CONFIG_PID_NS=y CONFIG_NET_NS=y CONFIG_SCHED_AUTOGROUP=y # CONFIG_SYSFS_DEPRECATED is not set CONFIG_RELAY=y CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" CONFIG_RD_GZIP=y CONFIG_RD_BZIP2=y CONFIG_RD_LZMA=y CONFIG_RD_XZ=y CONFIG_RD_LZO=y CONFIG_RD_LZ4=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y CONFIG_ANON_INODES=y CONFIG_SYSCTL_EXCEPTION_TRACE=y CONFIG_HAVE_PCSPKR_PLATFORM=y CONFIG_BPF=y CONFIG_EXPERT=y CONFIG_SGETMASK_SYSCALL=y CONFIG_SYSFS_SYSCALL=y # CONFIG_SYSCTL_SYSCALL is not set CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_PCSPKR_PLATFORM=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_TIMERFD=y CONFIG_EVENTFD=y CONFIG_BPF_SYSCALL=y CONFIG_SHMEM=y CONFIG_AIO=y CONFIG_ADVISE_SYSCALLS=y CONFIG_PCI_QUIRKS=y # CONFIG_EMBEDDED is not set CONFIG_HAVE_PERF_EVENTS=y # #
linux panic on 4.0.0-rc4
Hello, I have a power mac mini 32-bit system. I am getting a kernel panic with the latest rc kernel. The last kernel which worked on this which I remember booting was 3.19-rc5. You can see the panic message here: http://imgur.com/s1lH15g. (there is no log and I have no serial console). Let me know if you need any more information. Config follows: # # Automatically generated file; DO NOT EDIT. # Linux/powerpc 4.0.0-rc4 Kernel Configuration # # CONFIG_PPC64 is not set # # Processor support # CONFIG_PPC_BOOK3S_32=y # CONFIG_PPC_85xx is not set # CONFIG_PPC_8xx is not set # CONFIG_40x is not set # CONFIG_44x is not set # CONFIG_E200 is not set CONFIG_PPC_BOOK3S=y CONFIG_6xx=y CONFIG_PPC_FPU=y CONFIG_ALTIVEC=y CONFIG_PPC_STD_MMU=y CONFIG_PPC_STD_MMU_32=y # CONFIG_PPC_MM_SLICES is not set CONFIG_PPC_HAVE_PMU_SUPPORT=y CONFIG_PPC_PERF_CTRS=y # CONFIG_SMP is not set # CONFIG_PPC_DOORBELL is not set CONFIG_CPU_BIG_ENDIAN=y # CONFIG_CPU_LITTLE_ENDIAN is not set CONFIG_PPC32=y CONFIG_32BIT=y CONFIG_WORD_SIZE=32 # CONFIG_ARCH_PHYS_ADDR_T_64BIT is not set # CONFIG_ARCH_DMA_ADDR_T_64BIT is not set CONFIG_MMU=y # CONFIG_HAVE_SETUP_PER_CPU_AREA is not set # CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK is not set CONFIG_NR_IRQS=512 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_GENERIC_HWEIGHT=y CONFIG_PPC=y # CONFIG_GENERIC_CSUM is not set CONFIG_EARLY_PRINTK=y CONFIG_PANIC_TIMEOUT=0 CONFIG_GENERIC_NVRAM=y CONFIG_SCHED_OMIT_FRAME_POINTER=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_PPC_OF=y CONFIG_PPC_UDBG_16550=y # CONFIG_GENERIC_TBSYNC is not set CONFIG_AUDIT_ARCH=y CONFIG_GENERIC_BUG=y # CONFIG_EPAPR_BOOT is not set # 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_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y CONFIG_ARCH_SUPPORTS_UPROBES=y CONFIG_PPC_EMULATE_SSTEP=y CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config CONFIG_IRQ_WORK=y # # General setup # CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_CROSS_COMPILE= # CONFIG_COMPILE_TEST is not set CONFIG_LOCALVERSION= # CONFIG_LOCALVERSION_AUTO is not set CONFIG_DEFAULT_HOSTNAME=(none) CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_POSIX_MQUEUE_SYSCTL=y CONFIG_CROSS_MEMORY_ATTACH=y CONFIG_FHANDLE=y CONFIG_USELIB=y CONFIG_AUDIT=y CONFIG_HAVE_ARCH_AUDITSYSCALL=y CONFIG_AUDITSYSCALL=y CONFIG_AUDIT_WATCH=y CONFIG_AUDIT_TREE=y # # IRQ subsystem # CONFIG_GENERIC_IRQ_SHOW=y CONFIG_GENERIC_IRQ_SHOW_LEVEL=y CONFIG_IRQ_DOMAIN=y CONFIG_GENERIC_MSI_IRQ=y CONFIG_IRQ_FORCED_THREADING=y CONFIG_SPARSE_IRQ=y CONFIG_GENERIC_TIME_VSYSCALL_OLD=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BUILD=y CONFIG_GENERIC_CMOS_UPDATE=y # # Timers subsystem # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ_COMMON=y # CONFIG_HZ_PERIODIC is not set CONFIG_NO_HZ_IDLE=y # CONFIG_NO_HZ is not set CONFIG_HIGH_RES_TIMERS=y # # CPU/Task time and stats accounting # CONFIG_TICK_CPU_ACCOUNTING=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_BSD_PROCESS_ACCT_V3=y CONFIG_TASKSTATS=y CONFIG_TASK_DELAY_ACCT=y CONFIG_TASK_XACCT=y CONFIG_TASK_IO_ACCOUNTING=y # # RCU Subsystem # CONFIG_TINY_RCU=y CONFIG_SRCU=y CONFIG_TASKS_RCU=y # CONFIG_RCU_STALL_COMMON is not set # CONFIG_TREE_RCU_TRACE is not set CONFIG_RCU_KTHREAD_PRIO=0 CONFIG_BUILD_BIN2C=y CONFIG_IKCONFIG=m # CONFIG_IKCONFIG_PROC is not set CONFIG_LOG_BUF_SHIFT=17 CONFIG_CGROUPS=y # CONFIG_CGROUP_DEBUG is not set CONFIG_CGROUP_FREEZER=y CONFIG_CGROUP_DEVICE=y CONFIG_CPUSETS=y CONFIG_PROC_PID_CPUSET=y CONFIG_CGROUP_CPUACCT=y CONFIG_PAGE_COUNTER=y CONFIG_MEMCG=y CONFIG_MEMCG_SWAP=y # CONFIG_MEMCG_SWAP_ENABLED is not set CONFIG_CGROUP_PERF=y CONFIG_CGROUP_SCHED=y CONFIG_FAIR_GROUP_SCHED=y # CONFIG_CFS_BANDWIDTH is not set # CONFIG_RT_GROUP_SCHED is not set CONFIG_BLK_CGROUP=y # CONFIG_DEBUG_BLK_CGROUP is not set CONFIG_CHECKPOINT_RESTORE=y CONFIG_NAMESPACES=y CONFIG_UTS_NS=y CONFIG_IPC_NS=y CONFIG_USER_NS=y CONFIG_PID_NS=y CONFIG_NET_NS=y CONFIG_SCHED_AUTOGROUP=y # CONFIG_SYSFS_DEPRECATED is not set CONFIG_RELAY=y CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE= CONFIG_RD_GZIP=y CONFIG_RD_BZIP2=y CONFIG_RD_LZMA=y CONFIG_RD_XZ=y CONFIG_RD_LZO=y CONFIG_RD_LZ4=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y CONFIG_ANON_INODES=y CONFIG_SYSCTL_EXCEPTION_TRACE=y CONFIG_HAVE_PCSPKR_PLATFORM=y CONFIG_BPF=y CONFIG_EXPERT=y CONFIG_SGETMASK_SYSCALL=y CONFIG_SYSFS_SYSCALL=y # CONFIG_SYSCTL_SYSCALL is not set CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_PCSPKR_PLATFORM=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_TIMERFD=y CONFIG_EVENTFD=y CONFIG_BPF_SYSCALL=y CONFIG_SHMEM=y CONFIG_AIO=y CONFIG_ADVISE_SYSCALLS=y CONFIG_PCI_QUIRKS=y # CONFIG_EMBEDDED is not set CONFIG_HAVE_PERF_EVENTS=y # # Kernel
Re: linux panic on 4.0.0-rc4
On Mon, Mar 16, 2015 at 1:11 AM, Pranith Kumar bobby.pr...@gmail.com wrote: Hello, I have a power mac mini 32-bit system. ... You can see the panic message here: http://imgur.com/s1lH15g. (there is no log and I have no serial console). There was some debug code in there when it hit. The actual hang seems to be in printk_late_init(). It does not return from this. May be this is a hint? Please let me know if you need more information to debug this. Thanks! Let me know if you need any more information. Config follows: # # Automatically generated file; DO NOT EDIT. # Linux/powerpc 4.0.0-rc4 Kernel Configuration # # CONFIG_PPC64 is not set # # Processor support # CONFIG_PPC_BOOK3S_32=y # CONFIG_PPC_85xx is not set # CONFIG_PPC_8xx is not set # CONFIG_40x is not set # CONFIG_44x is not set # CONFIG_E200 is not set CONFIG_PPC_BOOK3S=y CONFIG_6xx=y CONFIG_PPC_FPU=y CONFIG_ALTIVEC=y CONFIG_PPC_STD_MMU=y CONFIG_PPC_STD_MMU_32=y # CONFIG_PPC_MM_SLICES is not set CONFIG_PPC_HAVE_PMU_SUPPORT=y CONFIG_PPC_PERF_CTRS=y # CONFIG_SMP is not set # CONFIG_PPC_DOORBELL is not set CONFIG_CPU_BIG_ENDIAN=y # CONFIG_CPU_LITTLE_ENDIAN is not set CONFIG_PPC32=y CONFIG_32BIT=y CONFIG_WORD_SIZE=32 # CONFIG_ARCH_PHYS_ADDR_T_64BIT is not set # CONFIG_ARCH_DMA_ADDR_T_64BIT is not set CONFIG_MMU=y # CONFIG_HAVE_SETUP_PER_CPU_AREA is not set # CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK is not set CONFIG_NR_IRQS=512 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_GENERIC_HWEIGHT=y CONFIG_PPC=y # CONFIG_GENERIC_CSUM is not set CONFIG_EARLY_PRINTK=y CONFIG_PANIC_TIMEOUT=0 CONFIG_GENERIC_NVRAM=y CONFIG_SCHED_OMIT_FRAME_POINTER=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_PPC_OF=y CONFIG_PPC_UDBG_16550=y # CONFIG_GENERIC_TBSYNC is not set CONFIG_AUDIT_ARCH=y CONFIG_GENERIC_BUG=y # CONFIG_EPAPR_BOOT is not set # 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_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y CONFIG_ARCH_SUPPORTS_UPROBES=y CONFIG_PPC_EMULATE_SSTEP=y CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config CONFIG_IRQ_WORK=y # # General setup # CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_CROSS_COMPILE= # CONFIG_COMPILE_TEST is not set CONFIG_LOCALVERSION= # CONFIG_LOCALVERSION_AUTO is not set CONFIG_DEFAULT_HOSTNAME=(none) CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_POSIX_MQUEUE_SYSCTL=y CONFIG_CROSS_MEMORY_ATTACH=y CONFIG_FHANDLE=y CONFIG_USELIB=y CONFIG_AUDIT=y CONFIG_HAVE_ARCH_AUDITSYSCALL=y CONFIG_AUDITSYSCALL=y CONFIG_AUDIT_WATCH=y CONFIG_AUDIT_TREE=y # # IRQ subsystem # CONFIG_GENERIC_IRQ_SHOW=y CONFIG_GENERIC_IRQ_SHOW_LEVEL=y CONFIG_IRQ_DOMAIN=y CONFIG_GENERIC_MSI_IRQ=y CONFIG_IRQ_FORCED_THREADING=y CONFIG_SPARSE_IRQ=y CONFIG_GENERIC_TIME_VSYSCALL_OLD=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BUILD=y CONFIG_GENERIC_CMOS_UPDATE=y # # Timers subsystem # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ_COMMON=y # CONFIG_HZ_PERIODIC is not set CONFIG_NO_HZ_IDLE=y # CONFIG_NO_HZ is not set CONFIG_HIGH_RES_TIMERS=y # # CPU/Task time and stats accounting # CONFIG_TICK_CPU_ACCOUNTING=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_BSD_PROCESS_ACCT_V3=y CONFIG_TASKSTATS=y CONFIG_TASK_DELAY_ACCT=y CONFIG_TASK_XACCT=y CONFIG_TASK_IO_ACCOUNTING=y # # RCU Subsystem # CONFIG_TINY_RCU=y CONFIG_SRCU=y CONFIG_TASKS_RCU=y # CONFIG_RCU_STALL_COMMON is not set # CONFIG_TREE_RCU_TRACE is not set CONFIG_RCU_KTHREAD_PRIO=0 CONFIG_BUILD_BIN2C=y CONFIG_IKCONFIG=m # CONFIG_IKCONFIG_PROC is not set CONFIG_LOG_BUF_SHIFT=17 CONFIG_CGROUPS=y # CONFIG_CGROUP_DEBUG is not set CONFIG_CGROUP_FREEZER=y CONFIG_CGROUP_DEVICE=y CONFIG_CPUSETS=y CONFIG_PROC_PID_CPUSET=y CONFIG_CGROUP_CPUACCT=y CONFIG_PAGE_COUNTER=y CONFIG_MEMCG=y CONFIG_MEMCG_SWAP=y # CONFIG_MEMCG_SWAP_ENABLED is not set CONFIG_CGROUP_PERF=y CONFIG_CGROUP_SCHED=y CONFIG_FAIR_GROUP_SCHED=y # CONFIG_CFS_BANDWIDTH is not set # CONFIG_RT_GROUP_SCHED is not set CONFIG_BLK_CGROUP=y # CONFIG_DEBUG_BLK_CGROUP is not set CONFIG_CHECKPOINT_RESTORE=y CONFIG_NAMESPACES=y CONFIG_UTS_NS=y CONFIG_IPC_NS=y CONFIG_USER_NS=y CONFIG_PID_NS=y CONFIG_NET_NS=y CONFIG_SCHED_AUTOGROUP=y # CONFIG_SYSFS_DEPRECATED is not set CONFIG_RELAY=y CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE= CONFIG_RD_GZIP=y CONFIG_RD_BZIP2=y CONFIG_RD_LZMA=y CONFIG_RD_XZ=y CONFIG_RD_LZO=y CONFIG_RD_LZ4=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y CONFIG_ANON_INODES=y CONFIG_SYSCTL_EXCEPTION_TRACE=y CONFIG_HAVE_PCSPKR_PLATFORM=y CONFIG_BPF=y CONFIG_EXPERT=y CONFIG_SGETMASK_SYSCALL=y CONFIG_SYSFS_SYSCALL=y # CONFIG_SYSCTL_SYSCALL is not set CONFIG_KALLSYMS=y
