Suse 11 SP1 kernel panic。 I can't debug it without debuginfo. Who can give me a link of sels 2.6.32.12-0.7.default.debug or give some advise. Thanks for any reply! kernel: [3077010.856280] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008 kernel: [3077010.856291] IP: [<ffffffff81046958>] find_busiest_group+0x348/0x8b0 kernel: [3077010.856302] PGD a46ac067 PUD 8c828067 PMD 0 kernel: [3077010.856307] Oops: 0000 [#1] SMP kernel: [3077010.856312] last sysfs file: /sys/devices/system/cpu/cpu23/cache/index2/shared_cpu_map kernel: [3077010.856318] CPU 19 kernel: [3077010.856320] Modules linked in: bluetooth rfkill af_packet drbd iptable_filter ip_tables x_tables nfs lockd fscache nfs_acl auth_rpcgss sunrpc ipv6 cpufreq_conservative cpufreq_userspace cpufreq_powersave pcc_cpufreq fuse loop dm_mod tpm_tis tpm tpm_bios bnx2 e1000e iTCO_wdt rtc_cmos serio_raw rtc_core hpilo pcspkr iTCO_vendor_support rtc_lib hpwdt joydev power_meter button container usbhid hid uhci_hcd ehci_hcd usbcore edd ext3 mbcache jbd fan processor hpsa cciss scsi_mod thermal thermal_sys hwmon kernel: [3077010.856370] Supported: Yes kernel: [3077010.856375] Pid: 5762, comm: program_t Not tainted 2.6.32.12-0.7-default #1 ProLiant DL380 G7 kernel: [3077010.856379] RIP: 0010:[<ffffffff81046958>] [<ffffffff81046958>] find_busiest_group+0x348/0x8b0 kernel: [3077010.856387] RSP: 0018:ffff880112f59ab8 EFLAGS: 00010006 kernel: [3077010.856391] RAX: 00000000009da550 RBX: ffff880123c0ebc0 RCX: 0000000000000000 kernel: [3077010.856395] RDX: 0000000100000000 RSI: 0000000000000020 RDI: 0000000000000000 kernel: [3077010.856399] RBP: ffff880112f59c28 R08: 0000000000000020 R09: ffff880123c0ebd0 kernel: [3077010.856404] R10: 0000000000000000 R11: 0000000100000000 R12: 0000000000000000 kernel: [3077010.856408] R13: 0000000100000000 R14: 0000000000000000 R15: ffff880123c0ebd0 kernel: [3077010.856413] FS: 00007fc35fbac710(0000) GS:ffff880123d20000(0000) knlGS:0000000000000000 kernel: [3077010.856417] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 kernel: [3077010.856421] CR2: 0000000000000008 CR3: 0000000018124000 CR4: 00000000000006e0 kernel: [3077010.856426] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 kernel: [3077010.856430] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 kernel: [3077010.856434] Process program_t (pid: 5762, threadinfo ffff880012f58000, task ffff88000db421c0) kernel: [3077010.856438] Stack: kernel: [3077010.856441] 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel: [3077010.856445] <0> 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel: [3077010.856450] <0> 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel: [3077010.856457] Call Trace: kernel: [3077010.856467] Inexact backtrace: kernel: [3077010.856468] kernel: [3077010.856472] Code: 74 10 48 8b 75 10 44 8b 2e 45 85 ed 0f 84 a3 02 00 00 48 8b 95 00 ff ff ff 44 8b a5 f8 fe ff ff 48 8b 45 a8 48 01 85 20 ff ff ff <8b> 42 08 48 01 85 28 ff ff ff 45 85 e4 74 14 48 8b 45 c0 ba 01
Hi.... On Tue, Jul 24, 2012 at 6:38 AM, tingwei liu <tingw.liu@gmail.com> wrote:
Suse 11 SP1 kernel panic。
I can't debug it without debuginfo. Who can give me a link of sels 2.6.32.12-0.7.default.debug or give some advise.
Better just report it to the SuSE novell team about this bug...so that they are aware of this bug.... But anyway, see below...
kernel: [3077010.856280] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
OK, sounds like nasty pointer bug....it could be anything...even exploit...
kernel: [3077010.856291] IP: [<ffffffff81046958>] find_busiest_group+0x348/0x8b0
hmm, maybe a scheduler bug... just asking, how many core you have?
kernel: [3077010.856375] Pid: 5762, comm: program_t Not tainted 2.6.32.12-0.7-default #1 ProLiant DL380 G7
program_t??? never heard of it...is it your user space application?
kernel: [3077010.856438] Stack: kernel: [3077010.856441] 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel: [3077010.856445] <0> 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel: [3077010.856450] <0> 0000000000000000 0000000000000000 0000000000000000 0000000000000000
seems like your stack is "wiped".... if that's so, it's almost impossible to get valid stack trace in my opinion... -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com
On Tue, Jul 24, 2012 at 12:39 PM, Mulyadi Santosa <mulyadi.santosa@gmail.com> wrote:
Hi....
On Tue, Jul 24, 2012 at 6:38 AM, tingwei liu <tingw.liu@gmail.com> wrote:
Suse 11 SP1 kernel panic。
I can't debug it without debuginfo. Who can give me a link of sels 2.6.32.12-0.7.default.debug or give some advise.
Better just report it to the SuSE novell team about this bug...so that they are aware of this bug....
But anyway, see below...
kernel: [3077010.856280] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
OK, sounds like nasty pointer bug....it could be anything...even exploit...
kernel: [3077010.856291] IP: [<ffffffff81046958>] find_busiest_group+0x348/0x8b0
hmm, maybe a scheduler bug...
just asking, how many core you have? 24 cores
kernel: [3077010.856375] Pid: 5762, comm: program_t Not tainted 2.6.32.12-0.7-default #1 ProLiant DL380 G7
program_t??? never heard of it...is it your user space application? Right, This is my user space application.
kernel: [3077010.856438] Stack: kernel: [3077010.856441] 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel: [3077010.856445] <0> 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel: [3077010.856450] <0> 0000000000000000 0000000000000000 0000000000000000 0000000000000000
seems like your stack is "wiped".... if that's so, it's almost impossible to get valid stack trace in my opinion... User space program can affect kernel stack? I thought this is a kernel bug!
-- regards,
Mulyadi Santosa Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com
Thanks!
Hi... On Tue, Jul 24, 2012 at 3:39 PM, tingwei liu <tingw.liu@gmail.com> wrote:
24 cores
BTW, I saw these lines in the oops message: kernel: [3077010.856312] last sysfs file: /sys/devices/system/cpu/cpu23/cache/index2/shared_cpu_map does your program somehow read or write to this sysfs entry?
Right, This is my user space application.
care to explain briefly what this program_t does?
User space program can affect kernel stack? I thought this is a kernel bug!
IIRC, once there is kernel bug (or maybe more than one) than enable user space to "implant" code in kernel space. In the same sense, it would be no surprise that kernel stack could be wiped out. -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com
BTW, I saw these lines in the oops message: kernel: [3077010.856312] last sysfs file: /sys/devices/system/cpu/cpu23/cache/index2/shared_cpu_map
does your program somehow read or write to this sysfs entry? This program doesn't operate this file. But call some syscall,such as sched_setaffinity.
Right, This is my user space application.
care to explain briefly what this program_t does? This program is like RTSP server!
User space program can affect kernel stack? I thought this is a kernel bug!
IIRC, once there is kernel bug (or maybe more than one) than enable user space to "implant" code in kernel space. In the same sense, it would be no surprise that kernel stack could be wiped out.
Thanks!
-- regards,
Mulyadi Santosa Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com
https://bugzilla.kernel.org/show_bug.cgi?id=16991 this link maybe help？ 2012-07-25 c265n46 发件人：tingwei liu 发送时间：2012-07-24 07:39 主题：suse 11 kernel panic 收件人："kernelnewbies"<kernelnewbies@kernelnewbies.org> 抄送： Suse 11 SP1 kernel panic。 I can't debug it without debuginfo. Who can give me a link of sels 2.6.32.12-0.7.default.debug or give some advise. Thanks for any reply! kernel: [3077010.856280] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008 kernel: [3077010.856291] IP: [<ffffffff81046958>] find_busiest_group+0x348/0x8b0 kernel: [3077010.856302] PGD a46ac067 PUD 8c828067 PMD 0 kernel: [3077010.856307] Oops: 0000 [#1] SMP kernel: [3077010.856312] last sysfs file: /sys/devices/system/cpu/cpu23/cache/index2/shared_cpu_map kernel: [3077010.856318] CPU 19 kernel: [3077010.856320] Modules linked in: bluetooth rfkill af_packet drbd iptable_filter ip_tables x_tables nfs lockd fscache nfs_acl auth_rpcgss sunrpc ipv6 cpufreq_conservative cpufreq_userspace cpufreq_powersave pcc_cpufreq fuse loop dm_mod tpm_tis tpm tpm_bios bnx2 e1000e iTCO_wdt rtc_cmos serio_raw rtc_core hpilo pcspkr iTCO_vendor_support rtc_lib hpwdt joydev power_meter button container usbhid hid uhci_hcd ehci_hcd usbcore edd ext3 mbcache jbd fan processor hpsa cciss scsi_mod thermal thermal_sys hwmon kernel: [3077010.856370] Supported: Yes kernel: [3077010.856375] Pid: 5762, comm: program_t Not tainted 2.6.32.12-0.7-default #1 ProLiant DL380 G7 kernel: [3077010.856379] RIP: 0010:[<ffffffff81046958>] [<ffffffff81046958>] find_busiest_group+0x348/0x8b0 kernel: [3077010.856387] RSP: 0018:ffff880112f59ab8 EFLAGS: 00010006 kernel: [3077010.856391] RAX: 00000000009da550 RBX: ffff880123c0ebc0 RCX: 0000000000000000 kernel: [3077010.856395] RDX: 0000000100000000 RSI: 0000000000000020 RDI: 0000000000000000 kernel: [3077010.856399] RBP: ffff880112f59c28 R08: 0000000000000020 R09: ffff880123c0ebd0 kernel: [3077010.856404] R10: 0000000000000000 R11: 0000000100000000 R12: 0000000000000000 kernel: [3077010.856408] R13: 0000000100000000 R14: 0000000000000000 R15: ffff880123c0ebd0 kernel: [3077010.856413] FS: 00007fc35fbac710(0000) GS:ffff880123d20000(0000) knlGS:0000000000000000 kernel: [3077010.856417] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 kernel: [3077010.856421] CR2: 0000000000000008 CR3: 0000000018124000 CR4: 00000000000006e0 kernel: [3077010.856426] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 kernel: [3077010.856430] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 kernel: [3077010.856434] Process program_t (pid: 5762, threadinfo ffff880012f58000, task ffff88000db421c0) kernel: [3077010.856438] Stack: kernel: [3077010.856441] 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel: [3077010.856445] <0> 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel: [3077010.856450] <0> 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel: [3077010.856457] Call Trace: kernel: [3077010.856467] Inexact backtrace: kernel: [3077010.856468] kernel: [3077010.856472] Code: 74 10 48 8b 75 10 44 8b 2e 45 85 ed 0f 84 a3 02 00 00 48 8b 95 00 ff ff ff 44 8b a5 f8 fe ff ff 48 8b 45 a8 48 01 85 20 ff ff ff <8b> 42 08 48 01 85 28 ff ff ff 45 85 e4 74 14 48 8b 45 c0 ba 01 _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
participants (3)
-
c265n46 -
Mulyadi Santosa -
tingwei liu