[Bug 582222] New: kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!)

newer
[Bug 584334] New: Cannot select...

older
[Bug 583816] New: "Root Terminal"...

bugzilla_noreply＠novell.com

23 Feb 2010 23 Feb '10

15:35

http://bugzilla.novell.com/show_bug.cgi?id=582222 http://bugzilla.novell.com/show_bug.cgi?id=582222#c0 Summary: kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!) Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: i586 OS/Version: openSUSE 11.3 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: kairo@kairo.at QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9pre) Gecko/20100222 Lightning/1.0b2pre SeaMonkey/2.0.3pre When installing any kernel on my desktop machine that was compiled after we introduced gcc 4.5 (around February 18-20), I run into a kernel panic right when the system tries to boot the kernel. I currently have this system running with an older kernel and missed to take a pic of the panic screen, but it says "kernel panic - not syncing: Attempted ti kill init!" and something with "comm: swapper" in the line before, as well as a Tainted info with G and D flags, which I guess are standard with every openSUSE kernel. My machine is a Core2 (Conroe) system with an ASUS P5B main board, an NVidia card and a root partition that is still on reiserfs for hysteric reasons. I tested with kernel-desktop-2.6.33-3.3.i586.rpm, kernel-default with the same version (bot from plain Factory repo), and with kernel-pae (some 2.6.33-rc8 version) from Kernel:HEAD, all running into that issue, no matter if the related drm-all-kmp-* package from home:jobermayer is installed or not (I'm trying those to get nouveau graphics). Reproducible: Always Steps to Reproduce: 1. Install kernel from after the switch to gcc 4.5 2. Reboot Actual Results: kernel panic right on boot Expected Results: start up the system Thankfully I found kernel-default-2.6.33-3.1.i586.rpm compiled on Feb 13 still in the Factory repo, this one runs well with or without the DRM module for nouveau installed. With the bad kernels, I need to remove the vga= parameter from the boot line to even be able to see the panic output, if I leave it in there, I just get a black screen. As the 2.6.33-3.1 and 2.6.33-3.3 are both -rc7 kernels that are not much apart, but the switch from gcc 4.4 to 4.5 was probably in between, I feel like that could be the actual dealbreaker here - possibly with reiserfs, but maybe some other driver. With the slightly older kernel, the whole system runs completely fine, it's only that one package I changed to get it up and running. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Show replies by date

bugzilla_noreply＠novell.com

23 Feb 23 Feb

16:09

New subject: [Bug 582222] kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!)

http://bugzilla.novell.com/show_bug.cgi?id=582222 http://bugzilla.novell.com/show_bug.cgi?id=582222#c1 Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffm@novell.com --- Comment #1 from Jeff Mahoney 2010-02-23 16:09:10 UTC --- [ 0.299276] BUG: unable to handle kernel NULL pointer dereference at 0000000000000001 [ 0.300112] IP: [<ffffffff81a0f6ca>] ftrace_event_type_sys_enter+0x2a/0x60 [ 0.300112] PGD 0 [ 0.300112] Oops: 0002 [#1] PREEMPT SMP [ 0.300112] last sysfs file: [ 0.300112] CPU 2 [ 0.300112] Pid: 1, comm: swapper Not tainted 2.6.33-rc7-3-desktop #1 S2881 Thunder K8SR Mainboard/To Be Filled By O.E.M. [ 0.300112] RIP: 0010:[<ffffffff81a0f6ca>] [<ffffffff81a0f6ca>] ftrace_event_type_sys_enter+0x2a/0x60 [ 0.300112] RSP: 0000:ffff8801ffabbec8 EFLAGS: 00010282 [ 0.300112] RAX: ffffffff81a0f6a0 RBX: ffffffff81b14b98 RCX: 0000000000000002 [ 0.300112] RDX: 0000000000009802 RSI: ffffffff81a03ac0 RDI: ffffffff81b14b98 [ 0.300112] RBP: ffff8800f70405c0 R08: ffff8800f70408a0 R09: 0000000000000000 [ 0.300112] R10: 0000000000000000 R11: ffff8801ffc219e0 R12: 0000000000000200 [ 0.300112] R13: 0000000000000200 R14: 0000000000000000 R15: 0000000000000000 [ 0.300112] FS: 0000000000000000(0000) GS:ffff880103c00000(0000) knlGS:0000000000000000 [ 0.300112] CS: 0010 DS: 0000 ES: 0000 CR0: 0 00000008005003b [ 0.300112] CR2: 0000000000000001 CR3: 0000000001a04000 CR4: 00000000000006e0 [ 0.300112] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 0.300112] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [ 0.300112] Process swapper (pid: 1, threadinfo ffff8801ffaba000, task ffff8800f76cc040) [ 0.300112] Stack: [ 0.300112] ffffffff81b52be8 0000000000000000 ffffffff81bc1b60 ffffffff81b529e5 [ 0.300112] <0> 0000000000000001 ffffffff81b52acf ffffffff81000324 ffffffff81c050f0 [ 0.300112] <0> ffffffff81b1c0c0 0000000000000200 ffffffff81b37db9 0000000000000000 [ 0.300112] Call Trace: [ 0.300112] BUG: unable to handle kernel NULL pointer dereference at (null) [ 0.300112] IP: [<ffffffff810902c8>] processCFI+0x88/0x690 [ 0.300112] PGD 0 [ 0.300112] Oops: 0000 [#2] PREEMPT SMP [ 0.300112] last sysfs file: [ 0.300112] CPU 2 [ 0.300112] Pid: 1, comm: swapper Not tainted 2.6.33-rc7-3-desktop #1 S2881 Thunder K8SR Mainboard/To Be Filled By O.E.M. [ 0.300112] RIP: 0010:[<ffffffff810902c8>] [<ffffffff810902c8>] processCFI+0x88/0x690 [ 0.300112] RSP: 0000:ffff8801ffabb7b8 EFLAGS: 00010013 [ 0.300112] RAX: 0000000000000000 RBX: ffffffff81757fa5 RCX: ffffffff81757fa9 [ 0.300112] RDX: ffffffff81757fa7 RSI: ffffffff81757fa5 RDI: 0000000000000000 [ 0.300112] RBP: ffff8801ffabb948 R08: ffff8801ffabb948 R09: 0000000000000000 [ 0.300112] R10: 0000000000000007 R11: 0000000000000039 R12: 0000000000000000 [ 0.300112] R13: ffff8801ffabb7f8 R14: 0000000000000001 R15: 0000000000000000 [ 0.300112] FS: 0000000000000000(0000) GS:ffff880103c00000(0000) knlGS:0000000000000000 [ 0.300112] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b [ 0.300112] CR2: 0000000000000000 CR3: 0000000001a04000 CR4: 00000000000006e0 [ 0.300112] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 0.300112] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [ 0.300112] Process swapper (pid: 1, threadinfo ffff8801ffaba000, task ffff8800f76cc040) [ 0.300112] Stack: [ 0.300112] ffff8800f76b9e88 ffff88027fabb9e2 0000000000000057 0000000000000000 [ 0.300112] <0> 0000000b00000001 ffff8801ffabb988 ffffffff81757fa9 ffffffff81757fa7 [ 0.300112] <0> 0000000000000000 ffffffff00000001 ffffffff00000057 ffffffff8185b2f4 [ 0.300112] Call Trace: [ 0.300112] [<ffffffff8109027d>] processCFI+0x3d/0x690 [ 0.300112] [<ffffffff81090ae4>] unwind+0xf4/0x12a0 [ 0.300112] [<ffffffff81007385>] dump_trace_unwind+0x65/0xf0 [ 0.300112] [<ffffffff81007574>] try_stack_unwind+0xe4/0x1f0 [ 0.300112] [<ffffffff81005cb9>] dump_trace+0x79/0x340 [ 0.300112] [<ffffffff81006071>] show_stack_log_lvl+0xd1/0x1f0 [ 0.300112] [<ffffffff81006274>] show_registers+0xe4/0x2e0 [ 0.300112] [<ffffffff814a0650>] __die+0xc0/0x100 [ 0.300112] [<ffffffff810306e4>] no_context+0xd4/0x1b0 [ 0.300112] [<ffffffff8149f8cf>] page_fault+0x1f/0x30 [ 0.300112] [<ffffffff81a0f6ca>] ftrace_event_type_sys_enter+0x2a/0x60 [ 0.300112] DWARF2 unwinder stuck at ftrace_event_type_sys_enter+0x2a/0x60 [ 0.300112] [ 0.300112] Leftover inexact backtrace: [ 0.300112] [ 0.300112] [<ffffffff81b52be8>] ? event_trace_init+0x119/0x1fe [ 0.300112] [<ffffffff81b529e5>] ? init_trace_printk_function_export+0x0/0x32 [ 0.300112] [<ffffffff81b52acf>] ? event_trace_init+0x0/0x1fe [ 0.300112] [<ffffffff81000324>] ? do_one_initcall+0x34/0x1a0 [ 0.300112] [<ffffffff81b37db9>] ? kernel_init+0x14d/0x1a5 [ 0.300112] [<ffffffff81003df4>] ? kernel_thread_helper+0x4/0x10 [ 0.300112] [<ffffffff81b37c6c>] ? kernel_init+0x0/0x1a5 [ 0.300112] [<ffffffff81003df0>] ? kernel_thread_helper+0x0/0x10 [ 0.300112] Code: 05 00 00 48 8d 55 40 48 8d 4b 04 4c 8d 6c 24 40 4c 89 f8 48 89 54 24 28 48 8d 53 02 48 89 4c 24 30 48 89 54 24 38 0f 1f 44 00 00 <0f> b6 10 89 d1 c0 e9 06 80 f9 01 0f 84 37 01 00 00 73 75 48 8d [ 0.300112] RIP [<ffffffff810902c8>] processCFI+0x88/0x690 [ 0.300112] RSP <ffff8801ffabb7b8> [ 0.300112] CR2: 0000000000000000 [ 0.300112] ---[ end trace 4eaa2a86a8e2da22 ]--- -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

16:19

New subject: [Bug 582222] kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!)

http://bugzilla.novell.com/show_bug.cgi?id=582222 http://bugzilla.novell.com/show_bug.cgi?id=582222#c2 Felix Miata changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrmazda@earthlink.net --- Comment #2 from Felix Miata 2010-02-23 16:19:33 UTC --- With vga=0x305 and whatever kernel-default that was on mirrors late Sunday, I got black screen and panic on ext3 and 32 bit. I didn't try excluding vga= when I tried old 2.6.31.5 kernel and initrd, but that got halt on black screen with it too. I reinstalled M2 on that system after selectively deleting most files and dirs, leaving behind the 2.6.31 kernel-desktop, initrd & modules, which along with the M2 kernel-default boot normally using vga=0x305. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

16:37

New subject: [Bug 582222] kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!)

http://bugzilla.novell.com/show_bug.cgi?id=582222 http://bugzilla.novell.com/show_bug.cgi?id=582222#c3 --- Comment #3 from Leonardo Chiquitto 2010-02-23 16:37:58 UTC --- I had the same problem after I updated to the latest Factory kernel. Updating again to a recent KOTD (2.6.33-rc8-2.99.24.854e988-default here) fixed it. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

20:32

New subject: [Bug 582222] kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!)

http://bugzilla.novell.com/show_bug.cgi?id=582222 http://bugzilla.novell.com/show_bug.cgi?id=582222#c4 --- Comment #4 from Jeff Mahoney 2010-02-23 20:32:08 UTC --- I am able to boot the current master repo as expected with gcc 4.4 but it fails when built with gcc 4.5. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

22:27

New subject: [Bug 582222] kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!)

http://bugzilla.novell.com/show_bug.cgi?id=582222 http://bugzilla.novell.com/show_bug.cgi?id=582222#c5 --- Comment #5 from Jeff Mahoney 2010-02-23 22:27:50 UTC --- Ok, I've tracked it down. It's failing because instead of calling the ->raw_init callback for the second event, it's calling the ->unregfunc. It's failing in event_trace_init(), where it goes through each of the ftrace events and runs the ->raw_init() callback. ftrace events are defined in the _ftrace_events section as an array of struct ftrace_event_call, aligned to 4 byte boundaries. An event is defined like this: struct ftrace_event_call { struct list_head list; char *name; char *system; struct dentry *dir; struct trace_event *event; int enabled; int (*regfunc)(struct ftrace_event_call *); void (*unregfunc)(struct ftrace_event_call *); int id; int (*raw_init)(struct ftrace_event_call *); int (*show_format)(struct ftrace_event_call *, struct trace_seq *); int (*define_fields)(struct ftrace_event_call *); struct list_head fields; int filter_active; struct event_filter *filter; void *mod; void *data; int profile_count; int (*profile_enable)(struct ftrace_event_call *); void (*profile_disable)(struct ftrace_event_call *); }; [...] #define DEFINE_EVENT(template, call, proto, args) \ \ static struct ftrace_event_call __used \ __attribute__((__aligned__(4))) \ __attribute__((section("_ftrace_events"))) event_##call = { \ .name = #call, \ .system = __stringify(TRACE_SYSTEM), \ .event = &ftrace_event_type_##call, \ .raw_init = trace_event_raw_init, \ .regfunc = ftrace_raw_reg_event_##call, \ .unregfunc = ftrace_raw_unreg_event_##call, \ .show_format = ftrace_format_##template, \ .define_fields = ftrace_define_fields_##template, \ _TRACE_PROFILE_INIT(call) \ } This is the objdump of arch/x86/kernel/ptrace.o, where the sys_enter ftrace vent is defined. With gcc 4.5: Disassembly of section _ftrace_events: 0000000000000000 : ... 10: R_X86_64_64 .rodata.str1.1+0x3f 18: R_X86_64_64 .rodata.str1.1+0x81 28: R_X86_64_64 .data 38: R_X86_64_64 .text+0x380 40: R_X86_64_64 .text+0x300 50: R_X86_64_64 trace_event_raw_init 58: R_X86_64_64 .text+0x1e0 60: R_X86_64_64 .text+0x410 a0: R_X86_64_64 .text+0x360 a8: R_X86_64_64 .text+0x2e0 00000000000000c0 : ... d0: R_X86_64_64 .rodata.str1.1+0x35 d8: R_X86_64_64 .rodata.str1.1+0x81 e8: R_X86_64_64 .data+0x60 f8: R_X86_64_64 .text+0x340 100: R_X86_64_64 .text+0x2c0 110: R_X86_64_64 trace_event_raw_init 118: R_X86_64_64 .text+0x150 120: R_X86_64_64 .text+0x3a0 160: R_X86_64_64 .text+0x320 168: R_X86_64_64 .text+0x2a0 With gcc 4.4: Disassembly of section _ftrace_events: 0000000000000000 : ... 10: R_X86_64_64 .rodata.str1.1+0x3f 18: R_X86_64_64 .rodata.str1.1+0x7d 28: R_X86_64_64 .data 38: R_X86_64_64 .text+0x3c0 40: R_X86_64_64 .text+0x340 50: R_X86_64_64 trace_event_raw_init 58: R_X86_64_64 .text+0x250 60: R_X86_64_64 .text+0x450 a0: R_X86_64_64 .text+0x3a0 a8: R_X86_64_64 .text+0x320 00000000000000b0 : ... c0: R_X86_64_64 .rodata.str1.1+0x35 c8: R_X86_64_64 .rodata.str1.1+0x7d d8: R_X86_64_64 .data+0x60 e8: R_X86_64_64 .text+0x380 f0: R_X86_64_64 .text+0x300 100: R_X86_64_64 trace_event_raw_init 108: R_X86_64_64 .text+0x1e0 110: R_X86_64_64 .text+0x3e0 150: R_X86_64_64 .text+0x360 158: R_X86_64_64 .text+0x2e0 For both versions, I see: (gdb) print sizeof(struct ftrace_event_call) $1 = 176 So the second event is at 0xc0 in the gcc 4.5-built version and at 0xb0 in the gcc 4.4-build version. Here's the disass of the relevant portion of the loop that iterates these event structures in event_trace_init -- on the gcc 4.5 version. e8: 48 c7 c3 00 00 00 00 mov $0x0,%rbx eb: R_X86_64_32S __start_ftrace_events .. 138: 48 83 7b 10 00 cmpq $0x0,0x10(%rbx) 13d: 74 73 je 1b2 13f: 48 8b 43 50 mov 0x50(%rbx),%rax 143: 48 85 c0 test %rax,%rax 146: 74 22 je 16a 148: 48 89 df mov %rbx,%rdi 14b: ff d0 callq *%rax .. 1b2: 48 81 c3 b0 00 00 00 add $0xb0,%rbx 1b9: 48 81 fb 00 00 00 00 cmp $0x0,%rbx 1bc: R_X86_64_32S __stop_ftrace_events 1c0: 0f 82 72 ff ff ff jb 138 So at first, we're at the beginning of __start_ftrace_events, which starts with the sys_exit ftrace event, followed by the sys_enter ftrace event. Using local addresses, that means: event 0: 0x000 event 1: 0x0b0 event 2: 0x160 . but instead of finding event 1 at b0, we're in between array members. When we go back up and look up the raw_init callback, which should be at 0x100 and set to trace_event_raw_init, we get .text+0x2c0 (ftrace_raw_unreg_event_sys_enter) instead. Naturally, nothing is set up yet since we haven't registered anything yet, so we blow up. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

22:31

New subject: [Bug 582222] kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!)

http://bugzilla.novell.com/show_bug.cgi?id=582222 http://bugzilla.novell.com/show_bug.cgi?id=582222#c6 Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matz@novell.com --- Comment #6 from Jeff Mahoney 2010-02-23 22:31:40 UTC --- So the question is, why are the array members aligned differently with gcc 4.5? The traversal code still thinks that they should be one-after-another and doesn't do anything fancy: #define for_each_event(event, start, end) \ for (event = start; \ (unsigned long)event < (unsigned long)end; \ event++) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

24 Feb 24 Feb

08:27

New subject: [Bug 582222] kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!)

http://bugzilla.novell.com/show_bug.cgi?id=582222 http://bugzilla.novell.com/show_bug.cgi?id=582222#c7 Andreas Jaeger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aj@novell.com, | |rguenther@novell.com --- Comment #7 from Andreas Jaeger 2010-02-24 08:27:00 UTC --- Jeff, do you have a source file for compilation? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10:32

New subject: [Bug 582222] kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!)

http://bugzilla.novell.com/show_bug.cgi?id=582222 http://bugzilla.novell.com/show_bug.cgi?id=582222#c8 --- Comment #8 from Michael Matz 2010-02-24 10:32:45 UTC --- Created an attachment (id=344397) --> (http://bugzilla.novell.com/attachment.cgi?id=344397) Testcase that doesn't have a problem We indeed need a preprocessed file (of ptrace.o) and compilation options, because I can't reproduce the problem with this testcase in which I tried to fill in the missing details. With -O0 and -O2 the second symbol is always at offset 0xb0, as expected. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

14:31

New subject: [Bug 582222] kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!)

http://bugzilla.novell.com/show_bug.cgi?id=582222 http://bugzilla.novell.com/show_bug.cgi?id=582222#c9 --- Comment #9 from Jeff Mahoney 2010-02-24 14:31:23 UTC --- Created an attachment (id=344466) --> (http://bugzilla.novell.com/attachment.cgi?id=344466) arch/x86/kernel/ptrace.i - gcc 4.4 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

14:31

New subject: [Bug 582222] kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!)

http://bugzilla.novell.com/show_bug.cgi?id=582222 http://bugzilla.novell.com/show_bug.cgi?id=582222#c10 --- Comment #10 from Jeff Mahoney 2010-02-24 14:31:58 UTC --- Created an attachment (id=344467) --> (http://bugzilla.novell.com/attachment.cgi?id=344467) arch/x86/kernel/ptrace.i - gcc 4.5 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

14:35

New subject: [Bug 582222] kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!)

http://bugzilla.novell.com/show_bug.cgi?id=582222 http://bugzilla.novell.com/show_bug.cgi?id=582222#c11 --- Comment #11 from Jeff Mahoney 2010-02-24 14:35:07 UTC --- Compilation options: gcc -Wp,-MD,arch/x86/kernel/.ptrace.o.d -nostdinc -isystem /usr/lib64/gcc/x86_64-suse-linux/4.5/include -I/home/jeffm/src/scratch/trees/linux-2.6.32-master/arch/x86/include -Iinclude -include include/generated/autoconf.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -O2 -m64 -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -pipe -Wno-sign-compare -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -Wframe-larger-than=2048 -fno-stack-protector -fomit-frame-pointer -fasynchronous-unwind-tables -g -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-dwarf2-cfi-asm -fconserve-stack -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(ptrace)" -D"KBUILD_MODNAME=KBUILD_STR(ptrace)" -D"DEBUG_HASH=39" -D"DEBUG_HASH2=54" -c -o arch/x86/kernel/.tmp_ptrace.o arch/x86/kernel/ptrace.c The only difference between the two is with gcc 4.4 there is "-isystem /usr/lib64/gcc/x86_64-suse-linux/4.4/include" instead. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

15:23

New subject: [Bug 582222] kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!)

http://bugzilla.novell.com/show_bug.cgi?id=582222 http://bugzilla.novell.com/show_bug.cgi?id=582222#c12 --- Comment #12 from Michael Matz 2010-02-24 15:23:21 UTC --- Thanks, I can reproduce it now, it's a latent kernel problem that is now exposed with GCC 4.5. It can be demonstrated with such testcase: struct X { char c[176]; }; #define __used __attribute__((__used__)) #define __al4 __attribute__((__aligned__(4))) static struct X x; static struct X __used __al4 __attribute__((section("x"))) x = { .c[0] = 1 }; Here the object 'x' will have alignment of 8 (in gcc44 or less) or 32 (since gcc45), despite the aligned(4) attribute. This is because the first seen declaration doesn't have such attribute. The attributes of all decls of the same object are merged, and for alignment this means choosing the larger one (this is correct because there might have been code emitted that only saw the first decl relying on the larger default alignment). You either need to remove the first decl, or annotate it with the same attributes (at least with the aligned attribute). This wasn't exposed with former GCCs because there the default alignment was 8 (and as the struct size is 176, which is divisible by 8, align to 8 or 4 doesn't make a difference, but you can see the wrong .align 8 directives also with gcc44 in the .s file). More recent GCCs align large structs to 32byte by default. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

16:27

New subject: [Bug 582222] kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!)

http://bugzilla.novell.com/show_bug.cgi?id=582222 http://bugzilla.novell.com/show_bug.cgi?id=582222#c13 --- Comment #13 from Jeff Mahoney 2010-02-24 16:27:46 UTC --- Your explanation makes sense and I've been able to duplicate it. It looks like this is the cause: #define DEFINE_EVENT(template, name, proto, args) \ static struct ftrace_event_call event_##name Changing it to: #define DEFINE_EVENT(template, name, proto, args) \ static struct ftrace_event_call \ __attribute__((__aligned__(4))) event_##name Produces the right alignment in ptrace.o. I'm building a test kernel now. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

17:00

New subject: [Bug 582222] kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!)

http://bugzilla.novell.com/show_bug.cgi?id=582222 http://bugzilla.novell.com/show_bug.cgi?id=582222#c14 --- Comment #14 from Jeff Mahoney 2010-02-24 16:59:59 UTC --- Ok, we made it past that problem. On to another! BUG: unable to handle kernel NULL pointer dereference at 000000000000000f IP: [<ffffffff812426c2>] strlen+0x2/0x20 PGD 0 Oops: 0000 [#1] PREEMPT SMP last sysfs file: CPU 2 Pid: 1, comm: swapper Not tainted 2.6.33-rc8-desktop #3 S2881 Thunder K8SR Mainboard/To Be Filled By O.E.M. RIP: 0010:[<ffffffff812426c2>] [<ffffffff812426c2>] strlen+0x2/0x20 RSP: 0000:ffff8801ffabbe08 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000000067 RSI: ffffffff81d203b8 RDI: 000000000000000f RBP: ffff8800f7042300 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000001 R11: 0000000000000000 R12: 000000000000000f R13: 00000000000041ed R14: 0000000000000000 R15: ffffffff8161c4e0 FS: 0000000000000000(0000) GS:ffff880103c00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 000000000000000f CR3: 0000000001a04000 CR4: 00000000000006e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Process swapper (pid: 1, threadinfo ffff8801ffaba000, task ffff8800f76ce040) Stack: ffffffff811c44d1 ffffffff810c4af0 0000000000000000 ffff8800f7757320 <0> ffffffff81b170b8 ffffffff810c4af0 ffff8801ffb0f9c0 ffff8800f7042300 <0> ffffffff8161c6a0 ffffffff8161c4e0 ffffffff810c358b ffff880000000000 Call Trace: [<ffffffff811c44d1>] debugfs_create_file+0xb1/0x2d0 [<ffffffff810c358b>] event_create_dir+0x4b/0x580 [<ffffffff81b52fb2>] event_trace_init+0x15d/0x1fe [<ffffffff81000324>] do_one_initcall+0x34/0x1a0 [<ffffffff81b37db9>] kernel_init+0x14d/0x1a5 [<ffffffff81003d34>] kernel_thread_helper+0x4/0x10 Code: 00 48 83 ea 01 48 39 d0 77 0c 0f b6 0a f6 81 40 64 63 81 20 75 eb c6 42 01 00 f3 c3 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 31 c0 <80> 3f 00 74 15 48 89 f8 66 0f 1f 44 00 00 48 83 c0 01 80 38 00 RIP [<ffffffff812426c2>] strlen+0x2/0x20 RSP <ffff8801ffabbe08> CR2: 000000000000000f -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

17:08

New subject: [Bug 582222] kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!)

http://bugzilla.novell.com/show_bug.cgi?id=582222 http://bugzilla.novell.com/show_bug.cgi?id=582222#c15 --- Comment #15 from Jeff Mahoney 2010-02-24 17:08:50 UTC --- Same problem, different place. Still hunting. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

18:33

New subject: [Bug 582222] kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!)

http://bugzilla.novell.com/show_bug.cgi?id=582222 http://bugzilla.novell.com/show_bug.cgi?id=582222#c16 --- Comment #16 from Jeff Mahoney 2010-02-24 18:33:21 UTC --- event_mce_record - event_sched_stat_runtime is misaligned (210,220) event_function - event_funcgraph_entry is misaligned (2110,2120) event_funcgraph_entry - event_funcgraph_exit is misaligned (21d0,21e0) event_funcgraph_exit - event_context_switch is misaligned (2290,22a0) event_context_switch - event_wakeup is misaligned (2350,2360) event_wakeup - event_special is misaligned (2410,2420) event_special - event_kernel_stack is misaligned (24d0,24e0) event_kernel_stack - event_user_stack is misaligned (2590,25a0) event_user_stack - event_bprint is misaligned (2650,2660) event_bprint - event_print is misaligned (2710,2720) event_print - event_mmiotrace_rw is misaligned (27d0,27e0) event_mmiotrace_rw - event_mmiotrace_map is misaligned (2890,28a0) event_mmiotrace_map - event_boot_call is misaligned (2950,2960) event_boot_call - event_boot_ret is misaligned (2a10,2a20) event_boot_ret - event_branch is misaligned (2ad0,2ae0) event_branch - event_hw_branch is misaligned (2b90,2ba0) event_hw_branch - event_kmem_alloc is misaligned (2c50,2c60) event_kmem_alloc - event_kmem_free is misaligned (2d10,2d20) event_kmem_free - event_ksym_trace is misaligned (2dd0,2de0) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

18:52

New subject: [Bug 582222] kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!)

http://bugzilla.novell.com/show_bug.cgi?id=582222 http://bugzilla.novell.com/show_bug.cgi?id=582222#c17 --- Comment #17 from Jeff Mahoney 2010-02-24 18:52:35 UTC --- Created an attachment (id=344563) --> (http://bugzilla.novell.com/attachment.cgi?id=344563) ftrace: fix ftrace_event_call alignment for use with gcc 4.5 GCC 4.5 introduced behavior that forces the alignment of structures to use the largest possible value. The default value is 32 bytes, so if some structures are defined with a 4-byte alignment and others aren't declared with an alignment constraint at all - it will align at 32-bytes. For things like the ftrace events, this results in a non-standard array. When initializing the ftrace subsystem, we traverse the _ftrace_events section and call the initialization callback for each event. When the structures are misaligned, we could be treating another part of the structure (or the zeroed out space between them) as a function pointer. This patch forces the alignment for all the ftrace_event_call structures to 4 bytes. Without this patch, the kernel fails to boot very early when built with gcc 4.5. It's trivial to check the alignment of the members of the array, so it might be worthwhile to add something to the build system to do that automatically. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

28 Feb 28 Feb

01:44

New subject: [Bug 582222] kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!)

http://bugzilla.novell.com/show_bug.cgi?id=582222 http://bugzilla.novell.com/show_bug.cgi?id=582222#c18 Jon Masters changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jcm@jonmasters.org --- Comment #18 from Jon Masters 2010-02-28 01:44:17 UTC --- I was able to reproduce this on my test Factory system, forwarding the link over to the Fedora kernel team for their information. Is there a new kernel being pushed somewhere? Do you guys still do kernel or the day/week with the latest bits in? Jon. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

03:32

New subject: [Bug 582222] kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!)

http://bugzilla.novell.com/show_bug.cgi?id=582222 http://bugzilla.novell.com/show_bug.cgi?id=582222#c19 Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.pr |jeffm@novell.com |ovo.novell.com | --- Comment #19 from Jeff Mahoney 2010-02-28 03:32:03 UTC --- Yep, we do, but only the builds built with the Factory gcc would have exhibited the problem. The normal KOTD builds are still using gcc 4.4 and were unaffected. I've submitted a new kernel package to Factory but it looks like it hasn't been rebuilt yet. In the interim, an up-to-date kernel can be found here: http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_Factory/ -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

03:32

New subject: [Bug 582222] kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!)

http://bugzilla.novell.com/show_bug.cgi?id=582222 http://bugzilla.novell.com/show_bug.cgi?id=582222#c20 --- Comment #20 from Jeff Mahoney 2010-02-28 03:32:48 UTC --- The patch was accepted by the maintainer and is queued for Linus's tree and sent to stable. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

04:39

New subject: [Bug 582222] kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!)

http://bugzilla.novell.com/show_bug.cgi?id=582222 http://bugzilla.novell.com/show_bug.cgi?id=582222#c21 --- Comment #21 from Clark Tompsett 2010-02-28 04:39:04 UTC --- Tried the KOTD i586 desktop kernel build on the 23rd and it still crashes on my system. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

19:01

New subject: [Bug 582222] kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!)

http://bugzilla.novell.com/show_bug.cgi?id=582222 http://bugzilla.novell.com/show_bug.cgi?id=582222#c22 --- Comment #22 from Jon Masters 2010-02-28 19:01:15 UTC --- Indeed, the latest KOTD's are falling over - thanks Jeff, but I dug up the information I needed after making that comment and agree with Clark Tompsett. Can you reply when there's a build I can throw on my Factory system? Also, does OpenSUSE have an installonlyn type option for zypper to retain older kernels? I did a Factory install the other day to keep up with what you guys are doing and it just sits there doing a zypper -n dup (with some extra bits to ensure that rpm and zypper are up to date). Jon. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

19:08

New subject: [Bug 582222] kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!)

http://bugzilla.novell.com/show_bug.cgi?id=582222 http://bugzilla.novell.com/show_bug.cgi?id=582222#c23 --- Comment #23 from Felix Miata 2010-02-28 19:08:14 UTC --- (In reply to comment #22)

...

Also, does OpenSUSE have an installonlyn type option for zypper to retain > older kernels?

/etc/zypp/zypp.conf -> multiversion -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

19:52

New subject: [Bug 582222] kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!)

http://bugzilla.novell.com/show_bug.cgi?id=582222 http://bugzilla.novell.com/show_bug.cgi?id=582222#c24 --- Comment #24 from Jon Masters 2010-02-28 19:52:01 UTC --- I pulled down kernel-desktop-2.6.33-25.1.x86_64.rpm from 11.2 and yeah, with the older GCC from 11.2 it is booting again. I've passed on the ftrace issue so everyone is aware of this coming up in GCC 4.5. I may add a reference in this week's kernel podcast for good measure. btw, I'm not sure of the "official" way of rescuing and upgrading but I did a rescue boot with a Factory CD, bind mounted various bits into the target and chrooted in to ensure the OpenSUSE mkinird would pick up the right device nodes. That more or less seemed to work out. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

21:56

New subject: [Bug 582222] kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!)

http://bugzilla.novell.com/show_bug.cgi?id=582222 http://bugzilla.novell.com/show_bug.cgi?id=582222#c25 Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |jcm@jonmasters.org --- Comment #25 from Jeff Mahoney 2010-02-28 21:56:41 UTC --- Strange. I just installed the Factory-built version of kernel-desktop-2.6.33-22.1.x86_64.rpm and it booted fine. Are you running into a different problem? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

23:56

New subject: [Bug 582222] kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!)

http://bugzilla.novell.com/show_bug.cgi?id=582222 http://bugzilla.novell.com/show_bug.cgi?id=582222#c26 --- Comment #26 from Jon Masters 2010-02-28 23:56:42 UTC --- Actually after re-installing 2.6.33-22.1 it does work. There was an issue with the way I was installing kernels within the rescue mounted environment. Thanks. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

1 Mar 1 Mar

16:19

New subject: [Bug 582222] kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!)

http://bugzilla.novell.com/show_bug.cgi?id=582222 http://bugzilla.novell.com/show_bug.cgi?id=582222#c27 Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #27 from Jeff Mahoney 2010-03-01 16:19:19 UTC --- Closing as FIXED. SR 33504 has been accepted. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

5172

Age (days ago)

5178

Last active (days ago)

List overview

Download

27 comments

1 participants

participants (1)

bugzilla_noreply＠novell.com

[Bug 582222] New: kernel panic on boot with gcc-4.5-compiled kernel (Attempted to kill init!)

tags

participants (1)