--------------------------------------------------------------------- Fedora Test Update Notification FEDORA-2005-1038 2005-10-31 ---------------------------------------------------------------------
Product : Fedora Core 4 Name : kernel Version : 2.6.14 Release : 1.1633_FC4 Summary : The Linux kernel (the core of the Linux operating system) Description : The kernel package contains the Linux kernel (vmlinuz), the core of any Linux operating system. The kernel handles the basic functions of the operating system: memory allocation, process allocation, device input and output, etc.
--------------------------------------------------------------------- Update Information:
A rebase to the latest upstream kernel.
--------------------------------------------------------------------- * Thu Oct 27 2005 Dave Jones davej@redhat.com - Rebase to 2.6.14
--------------------------------------------------------------------- This update can be downloaded from: http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/4/
08befd04c59333b3d50d59f41d25b7ad SRPMS/kernel-2.6.14-1.1633_FC4.src.rpm d6c778d9443365ee83ca0c9e63284391 ppc/kernel-2.6.14-1.1633_FC4.ppc.rpm d24e7df3cadac1f9e46e5a4983b69a1c ppc/kernel-devel-2.6.14-1.1633_FC4.ppc.rpm 74ec2fa0e1f6480e0648d59d8e1c4dd9 ppc/kernel-smp-2.6.14-1.1633_FC4.ppc.rpm 1ea2b1ff6cc4e26b54601b161a06d5a3 ppc/kernel-smp-devel-2.6.14-1.1633_FC4.ppc.rpm d29ede1616932222f3e4d8dc91cce791 ppc/debug/kernel-debuginfo-2.6.14-1.1633_FC4.ppc.rpm c3af0c7c3fdc9170f672ea57f451d5f1 ppc/kernel-2.6.14-1.1633_FC4.ppc64.rpm b55ec355426dc658ad1e804808b2c9c8 ppc/kernel-devel-2.6.14-1.1633_FC4.ppc64.rpm 1216190402df45c92c8746608add1750 x86_64/kernel-2.6.14-1.1633_FC4.x86_64.rpm 0be0b1fef12eb30aa8ee55a85671b338 x86_64/kernel-devel-2.6.14-1.1633_FC4.x86_64.rpm 80a3a67314cf0aa870d13e89325b1313 x86_64/kernel-smp-2.6.14-1.1633_FC4.x86_64.rpm bd3faa2f037f9ff1589367138f0eebbb x86_64/kernel-smp-devel-2.6.14-1.1633_FC4.x86_64.rpm bf456239aae9a2dcbec1fb573eb420ed x86_64/debug/kernel-debuginfo-2.6.14-1.1633_FC4.x86_64.rpm e64f7e8ec275aa3af8ca364377f90a07 x86_64/kernel-doc-2.6.14-1.1633_FC4.noarch.rpm b48841027641791e4dd43fdf20273d61 i386/kernel-2.6.14-1.1633_FC4.i586.rpm 391ff6a48e7df1bbaf6ebf108ab0a0f5 i386/kernel-devel-2.6.14-1.1633_FC4.i586.rpm 77b70008809f446426f22cb7af8e69c3 i386/debug/kernel-debuginfo-2.6.14-1.1633_FC4.i586.rpm 3e6ff9d42727f82232e9970a831ccbb7 i386/kernel-2.6.14-1.1633_FC4.i686.rpm 5738793a35d3fbf43684e02c9a1d5a75 i386/kernel-devel-2.6.14-1.1633_FC4.i686.rpm 855089e7669b2cbe20e77b70f7bdeabf i386/kernel-smp-2.6.14-1.1633_FC4.i686.rpm d399d760f1c77b523d224af5b73c211a i386/kernel-smp-devel-2.6.14-1.1633_FC4.i686.rpm e019219e36dd321d9c1e7d6d2f371af5 i386/debug/kernel-debuginfo-2.6.14-1.1633_FC4.i686.rpm e64f7e8ec275aa3af8ca364377f90a07 i386/kernel-doc-2.6.14-1.1633_FC4.noarch.rpm
This update can also be installed with the Update Agent; you can launch the Update Agent with the 'up2date' command. You may need to edit your up2date channels configuration. Within /etc/sysconfig/rhn/sources enable the following line: yum updates-testing http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/4/$A... ---------------------------------------------------------------------
On Mon, 2005-10-31 at 12:18 -0500, Dave Jones wrote:
Fedora Test Update Notification FEDORA-2005-1038 2005-10-31
Product : Fedora Core 4 Name : kernel Version : 2.6.14 Release : 1.1633_FC4 Summary : The Linux kernel (the core of the Linux operating system) Description : The kernel package contains the Linux kernel (vmlinuz), the core of any Linux operating system. The kernel handles the basic functions of the operating system: memory allocation, process allocation, device input and output, etc.
Update Information:
A rebase to the latest upstream kernel.
Are we also going to shortly see an update to iptables 1.3.3 to take advantage of some of the newer features that are compiled into the netfilter modules of this kernel such as IPv4 NFQUEUE and IPv6 REJECT and NFQUEUE targets (amongst others)?
- Thu Oct 27 2005 Dave Jones davej@redhat.com
- Rebase to 2.6.14
This update can be downloaded from: http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/4/
08befd04c59333b3d50d59f41d25b7ad SRPMS/kernel-2.6.14-1.1633_FC4.src.rpm d6c778d9443365ee83ca0c9e63284391 ppc/kernel-2.6.14-1.1633_FC4.ppc.rpm d24e7df3cadac1f9e46e5a4983b69a1c ppc/kernel-devel-2.6.14-1.1633_FC4.ppc.rpm 74ec2fa0e1f6480e0648d59d8e1c4dd9 ppc/kernel-smp-2.6.14-1.1633_FC4.ppc.rpm 1ea2b1ff6cc4e26b54601b161a06d5a3 ppc/kernel-smp-devel-2.6.14-1.1633_FC4.ppc.rpm d29ede1616932222f3e4d8dc91cce791 ppc/debug/kernel-debuginfo-2.6.14-1.1633_FC4.ppc.rpm c3af0c7c3fdc9170f672ea57f451d5f1 ppc/kernel-2.6.14-1.1633_FC4.ppc64.rpm b55ec355426dc658ad1e804808b2c9c8 ppc/kernel-devel-2.6.14-1.1633_FC4.ppc64.rpm 1216190402df45c92c8746608add1750 x86_64/kernel-2.6.14-1.1633_FC4.x86_64.rpm 0be0b1fef12eb30aa8ee55a85671b338 x86_64/kernel-devel-2.6.14-1.1633_FC4.x86_64.rpm 80a3a67314cf0aa870d13e89325b1313 x86_64/kernel-smp-2.6.14-1.1633_FC4.x86_64.rpm bd3faa2f037f9ff1589367138f0eebbb x86_64/kernel-smp-devel-2.6.14-1.1633_FC4.x86_64.rpm bf456239aae9a2dcbec1fb573eb420ed x86_64/debug/kernel-debuginfo-2.6.14-1.1633_FC4.x86_64.rpm e64f7e8ec275aa3af8ca364377f90a07 x86_64/kernel-doc-2.6.14-1.1633_FC4.noarch.rpm b48841027641791e4dd43fdf20273d61 i386/kernel-2.6.14-1.1633_FC4.i586.rpm 391ff6a48e7df1bbaf6ebf108ab0a0f5 i386/kernel-devel-2.6.14-1.1633_FC4.i586.rpm 77b70008809f446426f22cb7af8e69c3 i386/debug/kernel-debuginfo-2.6.14-1.1633_FC4.i586.rpm 3e6ff9d42727f82232e9970a831ccbb7 i386/kernel-2.6.14-1.1633_FC4.i686.rpm 5738793a35d3fbf43684e02c9a1d5a75 i386/kernel-devel-2.6.14-1.1633_FC4.i686.rpm 855089e7669b2cbe20e77b70f7bdeabf i386/kernel-smp-2.6.14-1.1633_FC4.i686.rpm d399d760f1c77b523d224af5b73c211a i386/kernel-smp-devel-2.6.14-1.1633_FC4.i686.rpm e019219e36dd321d9c1e7d6d2f371af5 i386/debug/kernel-debuginfo-2.6.14-1.1633_FC4.i686.rpm e64f7e8ec275aa3af8ca364377f90a07 i386/kernel-doc-2.6.14-1.1633_FC4.noarch.rpm
This update can also be installed with the Update Agent; you can launch the Update Agent with the 'up2date' command. You may need to edit your up2date channels configuration. Within /etc/sysconfig/rhn/sources enable the following line: yum updates-testing http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/4/$A...
On Mon, Oct 31, 2005 at 03:22:53PM -0500, Michael H. Warfield wrote:
On Mon, 2005-10-31 at 12:18 -0500, Dave Jones wrote:
Product : Fedora Core 4 Name : kernel Version : 2.6.14 Release : 1.1633_FC4
A rebase to the latest upstream kernel.
- Thu Oct 27 2005 Dave Jones davej@redhat.com
- Rebase to 2.6.14
Are we also going to shortly see an update to iptables 1.3.3 to take advantage of some of the newer features that are compiled into the netfilter modules of this kernel such as IPv4 NFQUEUE and IPv6 REJECT and NFQUEUE targets (amongst others)?
I'm keen to try FUSE with LTSP and the ltspFS
http://wiki.ltsp.org/twiki/bin/view/Ltsp/LtspFS
Am Dienstag, den 01.11.2005, 09:07 +1100 schrieb Norman Gaywood:
On Mon, Oct 31, 2005 at 03:22:53PM -0500, Michael H. Warfield wrote:
On Mon, 2005-10-31 at 12:18 -0500, Dave Jones wrote:
Product : Fedora Core 4 Name : kernel Version : 2.6.14 Release : 1.1633_FC4
A rebase to the latest upstream kernel.
- Thu Oct 27 2005 Dave Jones davej@redhat.com
- Rebase to 2.6.14
I'm keen to try FUSE with LTSP and the ltspFS http://wiki.ltsp.org/twiki/bin/view/Ltsp/LtspFS
Fuse is enabled in cvs for the FC4 kernel -- the next build will ship with a fuse module (this version has fuse disabled).
I'm in the process of preparing Fuse-Packages for Fedora-Extras -- see the archive of fedora-extras-list.
HTH
CU thl
On Tue, Nov 01, 2005 at 09:07:03AM +1100, Norman Gaywood wrote:
On Mon, Oct 31, 2005 at 03:22:53PM -0500, Michael H. Warfield wrote:
On Mon, 2005-10-31 at 12:18 -0500, Dave Jones wrote:
Product : Fedora Core 4 Name : kernel Version : 2.6.14 Release : 1.1633_FC4
A rebase to the latest upstream kernel.
- Thu Oct 27 2005 Dave Jones davej@redhat.com
- Rebase to 2.6.14
Are we also going to shortly see an update to iptables 1.3.3 to take advantage of some of the newer features that are compiled into the netfilter modules of this kernel such as IPv4 NFQUEUE and IPv6 REJECT and NFQUEUE targets (amongst others)?
I'm keen to try FUSE with LTSP and the ltspFS
There's packages for this in extras I believe (or at least there's ones being worked on).
Dave
On Mon, Oct 31, 2005 at 03:22:53PM -0500, Michael H. Warfield wrote:
A rebase to the latest upstream kernel.
Are we also going to shortly see an update to iptables 1.3.3 to take advantage of some of the newer features that are compiled into the netfilter modules of this kernel such as IPv4 NFQUEUE and IPv6 REJECT and NFQUEUE targets (amongst others)?
--end quoted text---
That's a decision I'll leave to teh maintainer of the iptables package. As a rule, for older releases, I try to minimise the "oh, you need to upgrade package x and y" effect as much as possible, and as this is just a new feature, I'd not say it's an "urgent must fix" item, but at the same time, any update to iptables may as well move to the latest rev and take advantage of this.
Dave
Dave Jones wrote:
Fedora Test Update Notification FEDORA-2005-1038 2005-10-31
Product : Fedora Core 4 Name : kernel Version : 2.6.14 Release : 1.1633_FC4 Summary : The Linux kernel (the core of the Linux operating system) Description : The kernel package contains the Linux kernel (vmlinuz), the core of any Linux operating system. The kernel handles the basic functions of the operating system: memory allocation, process allocation, device input and output, etc.
Update Information:
A rebase to the latest upstream kernel.
- Thu Oct 27 2005 Dave Jones davej@redhat.com
- Rebase to 2.6.14
This update can be downloaded from: http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/4/
08befd04c59333b3d50d59f41d25b7ad SRPMS/kernel-2.6.14-1.1633_FC4.src.rpm d6c778d9443365ee83ca0c9e63284391 ppc/kernel-2.6.14-1.1633_FC4.ppc.rpm d24e7df3cadac1f9e46e5a4983b69a1c ppc/kernel-devel-2.6.14-1.1633_FC4.ppc.rpm 74ec2fa0e1f6480e0648d59d8e1c4dd9 ppc/kernel-smp-2.6.14-1.1633_FC4.ppc.rpm 1ea2b1ff6cc4e26b54601b161a06d5a3 ppc/kernel-smp-devel-2.6.14-1.1633_FC4.ppc.rpm d29ede1616932222f3e4d8dc91cce791 ppc/debug/kernel-debuginfo-2.6.14-1.1633_FC4.ppc.rpm c3af0c7c3fdc9170f672ea57f451d5f1 ppc/kernel-2.6.14-1.1633_FC4.ppc64.rpm b55ec355426dc658ad1e804808b2c9c8 ppc/kernel-devel-2.6.14-1.1633_FC4.ppc64.rpm 1216190402df45c92c8746608add1750 x86_64/kernel-2.6.14-1.1633_FC4.x86_64.rpm 0be0b1fef12eb30aa8ee55a85671b338 x86_64/kernel-devel-2.6.14-1.1633_FC4.x86_64.rpm 80a3a67314cf0aa870d13e89325b1313 x86_64/kernel-smp-2.6.14-1.1633_FC4.x86_64.rpm bd3faa2f037f9ff1589367138f0eebbb x86_64/kernel-smp-devel-2.6.14-1.1633_FC4.x86_64.rpm bf456239aae9a2dcbec1fb573eb420ed x86_64/debug/kernel-debuginfo-2.6.14-1.1633_FC4.x86_64.rpm e64f7e8ec275aa3af8ca364377f90a07 x86_64/kernel-doc-2.6.14-1.1633_FC4.noarch.rpm b48841027641791e4dd43fdf20273d61 i386/kernel-2.6.14-1.1633_FC4.i586.rpm 391ff6a48e7df1bbaf6ebf108ab0a0f5 i386/kernel-devel-2.6.14-1.1633_FC4.i586.rpm 77b70008809f446426f22cb7af8e69c3 i386/debug/kernel-debuginfo-2.6.14-1.1633_FC4.i586.rpm 3e6ff9d42727f82232e9970a831ccbb7 i386/kernel-2.6.14-1.1633_FC4.i686.rpm 5738793a35d3fbf43684e02c9a1d5a75 i386/kernel-devel-2.6.14-1.1633_FC4.i686.rpm 855089e7669b2cbe20e77b70f7bdeabf i386/kernel-smp-2.6.14-1.1633_FC4.i686.rpm d399d760f1c77b523d224af5b73c211a i386/kernel-smp-devel-2.6.14-1.1633_FC4.i686.rpm e019219e36dd321d9c1e7d6d2f371af5 i386/debug/kernel-debuginfo-2.6.14-1.1633_FC4.i686.rpm e64f7e8ec275aa3af8ca364377f90a07 i386/kernel-doc-2.6.14-1.1633_FC4.noarch.rpm
This update can also be installed with the Update Agent; you can launch the Update Agent with the 'up2date' command. You may need to edit your up2date channels configuration. Within /etc/sysconfig/rhn/sources enable the following line: yum updates-testing http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/4/$A...
Suspend for IBM Thinkpads seems to have stopped working. See: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172180
On Mon, 2005-10-31 at 12:18 -0500, Dave Jones wrote:
Fedora Test Update Notification FEDORA-2005-1038 2005-10-31
Product : Fedora Core 4 Name : kernel Version : 2.6.14 Release : 1.1633_FC4 Summary : The Linux kernel (the core of the Linux operating system) Description : The kernel package contains the Linux kernel (vmlinuz), the core of any Linux operating system. The kernel handles the basic functions of the operating system: memory allocation, process allocation, device input and output, etc.
Fixed kernel oops problems at boot I was seeing on a Dell Inspiron 5160 with both release kernels in 2.6.13-1.xxxx. See:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=171357
Nice job Dave.
Brian Gaynor wrote:
On Mon, 2005-10-31 at 12:18 -0500, Dave Jones wrote:
Fedora Test Update Notification FEDORA-2005-1038 2005-10-31
Product : Fedora Core 4 Name : kernel Version : 2.6.14 Release : 1.1633_FC4 Summary : The Linux kernel (the core of the Linux operating system) Description : The kernel package contains the Linux kernel (vmlinuz), the core of any Linux operating system. The kernel handles the basic functions of the operating system: memory allocation, process allocation, device input and output, etc.
Fixed kernel oops problems at boot I was seeing on a Dell Inspiron 5160 with both release kernels in 2.6.13-1.xxxx. See:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=171357
Nice job Dave.
Ditto!
One quick note:
After getting up and running with the new kernel, I have a SEGFAULT with gkrellm when trying to load the i8k monitor for CPU temp and fans:
gkrellm segmentation fault: Dell I8K Plugin (create_monitor)
This ran fine under the .12 kernels.
For the time being, I disabled this and grkrellm works fine otherwise.
lsmod shows the i8k module loaded and I have the latest version of i8kutils installed:
i8kutils-1.25-4.fc4
Will i8kutils need to be recompiled for the .14 series kernels or is this a transient thing with a testing kernel?
HTH,
Marc Schwartz
On Tue, Nov 01, 2005 at 12:31:16PM -0600, Marc Schwartz wrote:
After getting up and running with the new kernel, I have a SEGFAULT with gkrellm when trying to load the i8k monitor for CPU temp and fans:
gkrellm segmentation fault: Dell I8K Plugin (create_monitor)
This ran fine under the .12 kernels.
if you run 'dmesg' after the segfault, do you get a kernel oops message? If you do, dump it into bugzilla.redhat.com please.
Dave
Dave Jones wrote:
On Tue, Nov 01, 2005 at 12:31:16PM -0600, Marc Schwartz wrote:
After getting up and running with the new kernel, I have a SEGFAULT with gkrellm when trying to load the i8k monitor for CPU temp and fans:
gkrellm segmentation fault: Dell I8K Plugin (create_monitor)
This ran fine under the .12 kernels.
if you run 'dmesg' after the segfault, do you get a kernel oops message? If you do, dump it into bugzilla.redhat.com please.
Dave
Dave,
Thanks for your follow up here.
There was nothing in dmesg, however, I tried running gkrellm under gdb.
When selecting the Dell I8K Plugin from the configuration menu in grkellm, I get the following:
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1208768832 (LWP 30729)] 0x00901c7d in strcpy () from /lib/libc.so.6
(gdb) bt #0 0x00901c7d in strcpy () from /lib/libc.so.6 #1 0x003eec4f in ?? () from /usr/lib/gkrellm2/plugins/i8krellm.so #2 0x003f49b8 in ?? () from /usr/lib/gkrellm2/plugins/i8krellm.so #3 0x00000000 in ?? ()
It looks like the debugging symbols are not available in the installed version of gkrellm. Is there something else that I can do or provide to assist?
Thanks,
Marc Schwartz
Marc Schwartz wrote:
Dave Jones wrote:
On Tue, Nov 01, 2005 at 12:31:16PM -0600, Marc Schwartz wrote:
After getting up and running with the new kernel, I have a SEGFAULT with gkrellm when trying to load the i8k monitor for CPU temp and fans:
gkrellm segmentation fault: Dell I8K Plugin (create_monitor)
This ran fine under the .12 kernels.
if you run 'dmesg' after the segfault, do you get a kernel oops message? If you do, dump it into bugzilla.redhat.com please.
Dave
Dave,
Thanks for your follow up here.
There was nothing in dmesg, however, I tried running gkrellm under gdb.
When selecting the Dell I8K Plugin from the configuration menu in grkellm, I get the following:
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1208768832 (LWP 30729)] 0x00901c7d in strcpy () from /lib/libc.so.6
(gdb) bt #0 0x00901c7d in strcpy () from /lib/libc.so.6 #1 0x003eec4f in ?? () from /usr/lib/gkrellm2/plugins/i8krellm.so #2 0x003f49b8 in ?? () from /usr/lib/gkrellm2/plugins/i8krellm.so #3 0x00000000 in ?? ()
It looks like the debugging symbols are not available in the installed version of gkrellm. Is there something else that I can do or provide to assist?
Thanks,
Marc Schwartz
OK. Now that I had some more coffee, I located the debug RPMS for both gkrellm and i8kutils from the FC and FCE repos and have installed them.
Here is the output from gdb now:
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1208248640 (LWP 4802)] 0x00901c7d in strcpy () from /lib/libc.so.6
(gdb) bt #0 0x00901c7d in strcpy () from /lib/libc.so.6 #1 0x00bc2c4f in __i8k_get_proc_info () from /usr/lib/gkrellm2/plugins/i8krellm.so #2 0x00bc47e3 in i8krellm_create_plugin () from /usr/lib/gkrellm2/plugins/i8krellm.so #3 0x0805b13e in gkrellm_build () #4 0x080a7cd2 in gkrellm_disable_plugin_connect () #5 0x00d28efa in g_cclosure_marshal_VOID__STRING () from /usr/lib/libgobject-2.0.so.0 #6 0x00d1d285 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #7 0x00d2b75b in g_signal_stop_emission () from /usr/lib/libgobject-2.0.so.0 #8 0x00d2ceb0 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #9 0x00d2d223 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #10 0x07a781d4 in gtk_cell_renderer_toggle_new () from /usr/lib/libgtk-x11-2.0.so.0 #11 0x07a71e2d in gtk_cell_renderer_activate () from /usr/lib/libgtk-x11-2.0.so.0 #12 0x07bf2218 in gtk_tree_view_column_focus_cell () from /usr/lib/libgtk-x11-2.0.so.0 #13 0x07bf2403 in gtk_tree_view_column_focus_cell () from /usr/lib/libgtk-x11-2.0.so.0 #14 0x07bed528 in gtk_tree_view_set_model () from /usr/lib/libgtk-x11-2.0.so.0 #15 0x07b22be2 in gtk_marshal_VOID__UINT_STRING () from /usr/lib/libgtk-x11-2.0.so.0 #16 0x00d1cd9b in g_cclosure_new_swap () from /usr/lib/libgobject-2.0.so.0 #17 0x00d1d285 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #18 0x00d2b8e7 in g_signal_stop_emission () from /usr/lib/libgobject-2.0.so.0 #19 0x00d2cc23 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #20 0x00d2d223 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #21 0x07bfe743 in gtk_widget_activate () from /usr/lib/libgtk-x11-2.0.so.0 #22 0x07b21348 in gtk_propagate_event () from /usr/lib/libgtk-x11-2.0.so.0 #23 0x07b217ac in gtk_main_do_event () from /usr/lib/libgtk-x11-2.0.so.0 #24 0x079ccdf6 in gdk_screen_get_setting () from /usr/lib/libgdk-x11-2.0.so.0 #25 0x00c8c4ce in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #26 0x00c8f4d6 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #27 0x00c8f7c3 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #28 0x07b20a46 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 #29 0x0805c7e7 in main ()
I am at the limits of my low level knowledge here, so any guidance to me that can help you further diagnose the issue would be appreciated.
HTH,
Marc Schwartz
On Wed, 2005-11-02 at 09:45 -0600, Marc Schwartz wrote:
Marc Schwartz wrote:
Dave Jones wrote:
On Tue, Nov 01, 2005 at 12:31:16PM -0600, Marc Schwartz wrote:
After getting up and running with the new kernel, I have a SEGFAULT with gkrellm when trying to load the i8k monitor for CPU temp and fans:
gkrellm segmentation fault: Dell I8K Plugin (create_monitor)
This ran fine under the .12 kernels.
if you run 'dmesg' after the segfault, do you get a kernel oops message? If you do, dump it into bugzilla.redhat.com please.
Dave
Dave,
Thanks for your follow up here.
There was nothing in dmesg, however, I tried running gkrellm under gdb.
When selecting the Dell I8K Plugin from the configuration menu in grkellm, I get the following:
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1208768832 (LWP 30729)] 0x00901c7d in strcpy () from /lib/libc.so.6
(gdb) bt #0 0x00901c7d in strcpy () from /lib/libc.so.6 #1 0x003eec4f in ?? () from /usr/lib/gkrellm2/plugins/i8krellm.so #2 0x003f49b8 in ?? () from /usr/lib/gkrellm2/plugins/i8krellm.so #3 0x00000000 in ?? ()
It looks like the debugging symbols are not available in the installed version of gkrellm. Is there something else that I can do or provide to assist?
Thanks,
Marc Schwartz
OK. Now that I had some more coffee, I located the debug RPMS for both gkrellm and i8kutils from the FC and FCE repos and have installed them.
Here is the output from gdb now:
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1208248640 (LWP 4802)] 0x00901c7d in strcpy () from /lib/libc.so.6
(gdb) bt #0 0x00901c7d in strcpy () from /lib/libc.so.6 #1 0x00bc2c4f in __i8k_get_proc_info () from /usr/lib/gkrellm2/plugins/i8krellm.so #2 0x00bc47e3 in i8krellm_create_plugin () from /usr/lib/gkrellm2/plugins/i8krellm.so #3 0x0805b13e in gkrellm_build () #4 0x080a7cd2 in gkrellm_disable_plugin_connect () #5 0x00d28efa in g_cclosure_marshal_VOID__STRING () from /usr/lib/libgobject-2.0.so.0 #6 0x00d1d285 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #7 0x00d2b75b in g_signal_stop_emission () from /usr/lib/libgobject-2.0.so.0 #8 0x00d2ceb0 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #9 0x00d2d223 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #10 0x07a781d4 in gtk_cell_renderer_toggle_new () from /usr/lib/libgtk-x11-2.0.so.0 #11 0x07a71e2d in gtk_cell_renderer_activate () from /usr/lib/libgtk-x11-2.0.so.0 #12 0x07bf2218 in gtk_tree_view_column_focus_cell () from /usr/lib/libgtk-x11-2.0.so.0 #13 0x07bf2403 in gtk_tree_view_column_focus_cell () from /usr/lib/libgtk-x11-2.0.so.0 #14 0x07bed528 in gtk_tree_view_set_model () from /usr/lib/libgtk-x11-2.0.so.0 #15 0x07b22be2 in gtk_marshal_VOID__UINT_STRING () from /usr/lib/libgtk-x11-2.0.so.0 #16 0x00d1cd9b in g_cclosure_new_swap () from /usr/lib/libgobject-2.0.so.0 #17 0x00d1d285 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #18 0x00d2b8e7 in g_signal_stop_emission () from /usr/lib/libgobject-2.0.so.0 #19 0x00d2cc23 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #20 0x00d2d223 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #21 0x07bfe743 in gtk_widget_activate () from /usr/lib/libgtk-x11-2.0.so.0 #22 0x07b21348 in gtk_propagate_event () from /usr/lib/libgtk-x11-2.0.so.0 #23 0x07b217ac in gtk_main_do_event () from /usr/lib/libgtk-x11-2.0.so.0 #24 0x079ccdf6 in gdk_screen_get_setting () from /usr/lib/libgdk-x11-2.0.so.0 #25 0x00c8c4ce in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #26 0x00c8f4d6 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #27 0x00c8f7c3 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #28 0x07b20a46 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 #29 0x0805c7e7 in main ()
I am at the limits of my low level knowledge here, so any guidance to me that can help you further diagnose the issue would be appreciated.
I would suggest getting the SRPMS as well; since gdb can you take to lines in the source code. :)
HTH,
Marc Schwartz
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
On Wed, Nov 02, 2005 at 09:45:09AM -0600, Marc Schwartz wrote:
(gdb) bt #0 0x00901c7d in strcpy () from /lib/libc.so.6 #1 0x00bc2c4f in __i8k_get_proc_info () from /usr/lib/gkrellm2/plugins/i8krellm.so
Can you paste the contents of /proc/i8k from both kernels? I'm curious whether that format changed somehow.
Also, what was the last kernel that worked ? The only major change to this recently seems to have happened in 2.6.13. So I suspect you're upgrading from 2.6.12 ?
Dave
On Thu, 2005-11-03 at 17:52 -0500, Dave Jones wrote:
On Wed, Nov 02, 2005 at 09:45:09AM -0600, Marc Schwartz wrote:
(gdb) bt #0 0x00901c7d in strcpy () from /lib/libc.so.6 #1 0x00bc2c4f in __i8k_get_proc_info () from /usr/lib/gkrellm2/plugins/i8krellm.so
Can you paste the contents of /proc/i8k from both kernels? I'm curious whether that format changed somehow.
Also, what was the last kernel that worked ? The only major change to this recently seems to have happened in 2.6.13. So I suspect you're upgrading from 2.6.12 ?
Dave
Dave,
Thanks for your reply.
Yes, I went from .12 to .14, since .13 resulted in a boot time panic, which I had posted to Bugzilla and was noted earlier in this thread:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=171357
From kernel-2.6.12-1.1456_FC4:
$ cat /proc/i8k 1.0 A38 ? 54 -22 1 -22 79260 -1 2
From kernel-2.6.14-1.1633_FC4:
$ cat /proc/i8k 1.0 A38 52 -22 1 -22 77340 -1 2
What is different is the field that should show the service tag ID for the laptop. This is the '?' in the first instance (3rd field) and appears to be missing in the second.
This would perhaps explain the SEGFAULT, since in reviewing the code in i8krellm.c for the __i8k_get_proc_info() function, there are a series of strcpy's, parsing the fields from the result of getting the /proc/i8k info.
The gkrellm plugin is supposed to display the service tag ID as a "tooltip" when one puts the mouse over the fan speed indicator. I had not noticed this previously since I do not routinely need the service tag, but with the 12 series kernel, I do get the question mark. In all honesty, while I can recall seeing the proper service tag in the past, I do not recall when this changed.
I do know that at some point in the past, pre-FC4, I need to change the entry for i8k in /etc/modprobe.conf to:
alias /proc/i8k i8k options i8k force=1
where the 'force=1' is noted in the i8kutils README file as possibly being required on some systems.
The BIOS version, A38, is the latest for this particular laptop (Dell 5150 with the 3.2 Ghz P4).
Let me know if you require further information.
Thanks,
Marc Schwartz
On Thu, Nov 03, 2005 at 05:31:53PM -0600, Marc Schwartz (via MN) wrote:
From kernel-2.6.12-1.1456_FC4:
$ cat /proc/i8k 1.0 A38 ? 54 -22 1 -22 79260 -1 2
From kernel-2.6.14-1.1633_FC4:
$ cat /proc/i8k 1.0 A38 52 -22 1 -22 77340 -1 2
Ok, that looks like unintentional breakage. I've brought this up upstream. Will try and get any resulting fix backported to FC4 when that appears.
What is different is the field that should show the service tag ID for the laptop. This is the '?' in the first instance (3rd field) and appears to be missing in the second.
This would perhaps explain the SEGFAULT, since in reviewing the code in i8krellm.c for the __i8k_get_proc_info() function, there are a series of strcpy's, parsing the fields from the result of getting the /proc/i8k info.
That code is really quite icky, and screams "scanf" to me. Whilst that kernel interface *shouldnt* change, things like this do happen, and it could have taken defensive action instead of being as fragile as it is.
Dave
On Thu, 2005-11-03 at 23:21 -0500, Dave Jones wrote:
On Thu, Nov 03, 2005 at 05:31:53PM -0600, Marc Schwartz (via MN) wrote:
From kernel-2.6.12-1.1456_FC4:
$ cat /proc/i8k 1.0 A38 ? 54 -22 1 -22 79260 -1 2
From kernel-2.6.14-1.1633_FC4:
$ cat /proc/i8k 1.0 A38 52 -22 1 -22 77340 -1 2
Ok, that looks like unintentional breakage. I've brought this up upstream. Will try and get any resulting fix backported to FC4 when that appears.
What is different is the field that should show the service tag ID for the laptop. This is the '?' in the first instance (3rd field) and appears to be missing in the second.
This would perhaps explain the SEGFAULT, since in reviewing the code in i8krellm.c for the __i8k_get_proc_info() function, there are a series of strcpy's, parsing the fields from the result of getting the /proc/i8k info.
That code is really quite icky, and screams "scanf" to me. Whilst that kernel interface *shouldnt* change, things like this do happen, and it could have taken defensive action instead of being as fragile as it is.
Great! Thanks for your assistance here Dave.
Thanks also to Ernest for his offlist guidance.
Best regards,
Marc
On 10/31/05, Dave Jones davej@redhat.com wrote:
Product : Fedora Core 4 Name : kernel Version : 2.6.14 Release : 1.1633_FC4 Summary : The Linux kernel (the core of the Linux operating system)
My hyperthreading issues continue -- the symptoms are different, but I still can't boot the SMP kernel if I enable hyperthreading in my BIOS.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169675
MEF
-- __ Mary Ellen Foster __ http://homepages.inf.ed.ac.uk/mef/ __ "One of the main causes of the fall of the Roman Empire was that, lacking zero, they had no way to indicate successful termination of their C programs." (Robert Firth)
Mary Ellen Foster wrote:
On 10/31/05, Dave Jones davej@redhat.com wrote:
Product : Fedora Core 4 Name : kernel Version : 2.6.14 Release : 1.1633_FC4 Summary : The Linux kernel (the core of the Linux operating system)
My hyperthreading issues continue -- the symptoms are different, but I still can't boot the SMP kernel if I enable hyperthreading in my BIOS.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169675
MEF
My hyperthreading works fine with this kernel. Actually, I can not remember the last time I have ever had a problem with the kernel.
Dave Jones wrote:
Fedora Test Update Notification FEDORA-2005-1038 2005-10-31
Product : Fedora Core 4 Name : kernel Version : 2.6.14 Release : 1.1633_FC4 Summary : The Linux kernel (the core of the Linux operating system) Description : The kernel package contains the Linux kernel (vmlinuz), the core of any Linux operating system. The kernel handles the basic functions of the operating system: memory allocation, process allocation, device input and output, etc.
Update Information:
A rebase to the latest upstream kernel.
- Thu Oct 27 2005 Dave Jones davej@redhat.com
- Rebase to 2.6.14
It fixed a problem with my desktop's network driver which is nice. Been running the rawhide kernels for a while to workaround that issue.
It does cause a problem with my main server's named. It will regularly stop responding to dns traffic.
http://marc.theaimsgroup.com/?l=linux-kernel&m=113075404512827&w=2
Nov 1 12:16:48 server named[1713]: errno2result.c:109: unexpected error: Nov 1 12:16:48 server named[1713]: unable to convert errno to isc_result: 14: Bad address Nov 1 12:16:48 server named[1713]: UDP client handler shutting down due to fatal receive error: unexpected error
On Thu, Nov 03, 2005 at 08:28:15AM -0800, Nathan Grennan wrote:
Dave Jones wrote:
Fedora Test Update Notification FEDORA-2005-1038 2005-10-31
Product : Fedora Core 4 Name : kernel Version : 2.6.14 Release : 1.1633_FC4 Summary : The Linux kernel (the core of the Linux operating system) Description : The kernel package contains the Linux kernel (vmlinuz), the core of any Linux operating system. The kernel handles the basic functions of the operating system: memory allocation, process allocation, device input and output, etc.
Update Information:
A rebase to the latest upstream kernel.
- Thu Oct 27 2005 Dave Jones davej@redhat.com
- Rebase to 2.6.14
It fixed a problem with my desktop's network driver which is nice. Been running the rawhide kernels for a while to workaround that issue.
It does cause a problem with my main server's named. It will regularly stop responding to dns traffic.
http://marc.theaimsgroup.com/?l=linux-kernel&m=113075404512827&w=2
Nov 1 12:16:48 server named[1713]: errno2result.c:109: unexpected error: Nov 1 12:16:48 server named[1713]: unable to convert errno to isc_result: 14: Bad address Nov 1 12:16:48 server named[1713]: UDP client handler shutting down due to fatal receive error: unexpected error
Ok, I just checked in the fix for this from the kernel.org bugzilla - http://bugzilla.kernel.org/show_bug.cgi?id=5505
I'll do another build in a few hours that'll show up at people.redhat.com/davej/kernels/Fedora/FC4/
(I usually do a few test builds that appear there before I push one out to updates-testing, as its lower overhead for me to do this).
Dave
Dave Jones wrote:
Ok, I just checked in the fix for this from the kernel.org bugzilla - http://bugzilla.kernel.org/show_bug.cgi?id=5505
I'll do another build in a few hours that'll show up at people.redhat.com/davej/kernels/Fedora/FC4/
(I usually do a few test builds that appear there before I push one out to updates-testing, as its lower overhead for me to do this).
My server has been running 1.1634 for a day with no problems. The patch does resolve the issue. Thank you.