Created attachment 161825 [details]
You can see problem on this output from command line

I can confirm the segfault with kernel  2.6.22.3-61.fc7 as well EXCEPT on
my two core i386 system "Intel(R) Pentium(R) 4 CPU 3.06GHz". All my other
systems are Core 2 or Core 2 Quad x86_64 systems and procinfo segfaults
while examining something with the cpu's (seen from a simple strace output).

The crash seems to be happening at line 470 of proc. I am not a c programmer
but if I blindly make the change
             irq_label[i][0] ---> irq_label[i]
at line 470 than there is no crash. Hope this helps.


Here is the backtrace:
===============================================================================
# gdb procinfo
GNU gdb Red Hat Linux (6.6-15.fc7rh)
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu"...
Using host libthread_db library "/lib64/libthread_db.so.1".
(gdb) run
Starting program: /usr/bin/procinfo

Program received signal SIGSEGV, Segmentation fault.
0x0000000000403c44 in first_page (sl=<value optimized out>) at procinfo.c:470
470                     if (irq_label[i][0] == 0)
(gdb) bt
#0  0x0000000000403c44 in first_page (sl=<value optimized out>) at procinfo.c:470
#1  0x00000000004054d9 in main (ac=1, av=0x7ffffa776ca8) at procinfo.c:907
#2  0x0000003dc841dab4 in __libc_start_main () from /lib64/libc.so.6
#3  0x00000000004018e9 in _start ()
==============================================================================

Hello,

I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the fedora kernel.

http://fedoraproject.org/wiki/KernelBugTriage

I am CC'ing myself to this bug and will try and assist you in resolving it if I can.

There hasn't been much activity on this bug for a while. Could you tell me if
you are still having problems with the latest kernel?

If the problem no longer exists then please close this bug or I'll do so in a
few days if there is no additional information lodged.

I have just upgraded kernel from FC7 updates to 2.6.22.9-91.fc7 and it look like
before upgrade:

[root@node2 ~]# uname -r
2.6.22.9-91.fc7

[root@node2 ~]# procinfo 
Naruszenie ochrony pamięci

[root@node2 ~]# dmesg 
procinfo[1878]: segfault at 00007fffa76f6464 rip 0000000000403c14 rsp
00007fffa76e9f20 error 4

If you boot with:

acpi=noirq

does the error still occur? I take it that this is not just happening with procinfo.

With error still occurs.
[root@node2 ~]# cat /proc/cmdline 
ro root=LABEL=/ acpi=noirq
[root@node2 ~]# procinfo 
Naruszenie ochrony pamięci

Is this just happening with procinfo only? Can you give examples of other
applications giving the same error?

for example: nnrp, expireover

So why do you think this is a kernel bug? You might have a broken glibc which
you are building against. I'm no programmer but I fail to see how this relates
to the kernel.

Hello Lukasz,

As I can't see this being a kernel-related issue, I'm tempted to close NOTABUG
or change the component to procinfo. These applications are segfaulting, not the
kernel.

Changing component...

your forgot to hit the reassignment button :)

Can't reproduce with kernel-2.6.23.12-52.fc7 and procinfo-18-21.fc7.  What
version of procinfo do you use?

Well, I have upgraded my servers to FC8, now I don't see this problem.

Hm...  There was an update of procinfo due to segfaulting so chance is that you
didn't have that installed on your F-7.  Let's close this bug.