[apport] depmod crashed with SIGSEGV in strcmp()

[Johnny]

Binary package hint: module-init-tools

make initrd iamge with mkinitramfs

ProblemType: Crash
Architecture: i386
Date: Sat Mar 31 22:10:18 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /sbin/depmod
Package: module-init-tools 3.3-pre3-1ubuntu4
PackageArchitecture: i386
ProcCmdline: depmod 2.6.20-ubuntu1johnny
ProcCwd: /usr/src/linux-source-2.6.20
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
 LANG=hu_HU.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: module-init-tools
StacktraceTop:
 strcmp () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Uname: Linux johnny-desktop 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:?? ()

[Apport retracing service (apport)]

StacktraceTop:strcmp () from /lib/tls/i686/cmov/libc.so.6
load_section32 (hdr=0xb7f0d000, secname=0x80504fb "__ksymtab_strings", size=0xbfdb3368, conv=0) at ../moduleops_core.c:18
load_symbols32 (module=0x805a210) at ../moduleops_core.c:34
main (argc=2, argv=0xbfdb5e24) at ../depmod.c:679
__libc_start_main () from /lib/tls/i686/cmov/libc.so.6

[Jean-Baptiste Lallement (jibel)]

marking as confirmed due to recent duplicate.

[Zdenek (zdenek-redhat-bugs)]

Description of problem:

during some installation of linux 2.6.28-rcx kernel I've got this coredump:

#0 0x00007f5012df3880 in strcmp () from /lib64/libc.so.6
#1 0x0000000000405da2 in load_section64 (hdr=0x67a420, secname=0x415ab9 "__ksymtab_strings", size=0x7fff1b303438, conv=0)
    at moduleops_core.c:18
#2 0x00000000004070bd in load_symbols64 (module=0x651940) at moduleops_core.c:34
#3 0x00000000004039c9 in parse_modules (list=0x652290) at depmod.c:714

Version-Release number of selected component (if applicable):
module-init-tools-3.5-3.fc10.x86_64

How reproducible:
no idea

Steps to Reproduce:
1.
2.
3.

Actual results:

Expected results:

Additional info:

[Launchpad Janitor (janitor)]

This bug was fixed in the package module-init-tools - 3.7~pre7-1

---------------
module-init-tools (3.7~pre7-1) jaunty; urgency=low

  * Repackage afresh for Ubuntu based off an upstream GIT import into bzr,
    rather than the Debian package.
  * New upstream pre-release:
    - many bug fixes. LP: #99547, #292887, #303613, #284001.
    - much profiling and optimisation work.
    - depmod generates and modprobe uses binary indexes for module lists,
      giving a significant performance benefit.
    - legacy support for pre-2.6 kernels dropped.
    - module ordering support. LP: #118040, #317724.
    - updated documentation. LP: #203828, #259791.

  * /etc/modprobe.d/aliases: Dropped this file, the kernel has been able to
    export the {char,block}-major-* aliases for a while and adding them to the
    appropriate modules is a one line patch. All aliases present here have
    been added to the Ubuntu kernel if not already present. LP: #332357.
  * /etc/modprobe.d/isapnp: Dropped this file, the modalias strings in it were
    not current with the strings produced by pnpacpi in the kernel (pnpbios
    does not produce any modalias strings), and this kind of thing is better
    off done with kernel patches.
  * /etc/modprobe.d/options: Dropped this file, changes to default kernel
    options should be changed in the kernel so that they also take effect if
    the module is built-in; and also to make sure they're kept in sync with
    any changes to option names or defaults (or even module names) in the
    kernel.
  * /etc/modprobe.d/arch/*, /etc/modprobe.d/arch-aliases: Dropped the arch
    directory and the symlink into it, these aliases and/or options are
    handled by kernel patches now.

  * /etc/modprobe.d/blacklist-amd76-edac: Merged with the ordinary blacklist
    file, since it only contains one line.
  * /etc/modprobe.d/blacklist{,-*}: Files renamed to end in ".conf" as
    required by new upstream version.a

  * /sbin/update-modules: This deprecated command has been removed.
  * Completely non-parallel-installable with modutils. LP: #208874.

  * All patches either merged upstream or dropped:
    - always_apply_blacklist: merged
    - blacklist-warn.diff: dropped. LP: #66423.
    - fix_8bit: merged
    - fix_sgml: merged
    - ignore_arch_directory: dropped
    - insmod-segv: merged
    - last_good_boot: dropped
    - modprobe_conf_and_directory: dropped
    - runparts_like_names: merged
    - silence_modprobe: dropped
    - use_blacklist_doc: merged

  * Note that from this version of module-init-tools, all configuration files
    in /etc/modprobe.d should end with ".conf", support for other names is
    retained with a warning but will be dropped.
  * Note that the Ubuntu -Q option to modprobe has been dropped, to silence
    modprobe use -q.

 -- Scott James Remnant <email address hidden> Mon, 09 Mar 2009 17:13:55 +0000

[Bug (bug-redhat-bugs)]

This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

[Mark Mentovai (mark-moxienet)]

This bug is not fixed in Jaunty. module-init-tools 3.7 (or 3.7preANYTHING) doesn't contain a complete fix for the problem. depmod module-init-tools 3.7-pre9 still crashes in strcmp with SIGSEGV for me on Januty when I have a broken module present. (The module is a truncated DKMS module, I don't know how it happened and it doesn't really matter either, it's just a good testcase for this bug.)

mark@ebony bash$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 9.04
Release: 9.04
Codename: jaunty
mark@ebony bash$ /sbin/depmod --version
module-init-tools 3.7-pre9
mark@ebony bash$ /sbin/depmod
Segmentation fault

Great.

For this demonstration, I pulled the current source from |bzr checkout http://bazaar.launchpad.net/~ubuntu-core-dev/module-init-tools/ubuntu| (which is actually based on 3.8) and confirmed that the bug is present.

mark@ebony bash$ gdb depmod
GNU gdb 6.8-debian
[...]
(gdb) run
Starting program: .../obj/depmod

Program received signal SIGSEGV, Segmentation fault.
0x00007f37de8676a0 in strcmp () from /lib/libc.so.6
(gdb) bt
#0 0x00007f37de8676a0 in strcmp () from /lib/libc.so.6
#1 0x000000000040a7ec in get_section64 (file=0x7f37de1ab000, fsize=0,
    secname=0x40d610 "__ksymtab_strings", secsize=0x7fffe6d77458, conv=0)
    at ../src/elf_core.c:35
#2 0x0000000000405bf3 in load_section64 (hdr=0x7f37de1ab000,
    secname=0x40d610 "__ksymtab_strings", secsize=0x7fffe6d77458, conv=0)
    at ../src/moduleops_core.c:7
#3 0x0000000000405c24 in load_symbols64 (module=0xe31320)
    at ../src/moduleops_core.c:17
#4 0x0000000000403132 in parse_modules (list=0xe43020)
    at ../src/depmod.c:675
#5 0x0000000000404b4a in main (argc=1, argv=0x7fffe6d777f8)
    at ../src/depmod.c:1288

Therefore, this problem would still be present in Karmic as it stands now.

The real problem here is that upstream module-init-tools does not do proper bounds checking prior to 3.9. Look at load_section in 3.7/moduleops_core.c. It assumes that the ELF file is as big as it needs to be, which is not a safe assumption. In 3.8/moduleops_core.c, load_section calls to elf_core.c's get_section, which introduces the possibility for bounds checking, but it is bypassed because load_section always passes 0 for |fsize|. Finally, in 3.9/elfops_core.c, load_section passes the entire module struct to get_section, which now always enforces bounds checking to ensure that it doesn't attempt to read unmapped memory beyond the end of the file.

mark@ebony bash$ 3.7.obj/depmod -n > modules.dep && ls -l modules.dep
Segmentation fault
mark@ebony bash$ 3.8.obj/depmod -n > modules.dep && ls -l modules.dep
Segmentation fault
mark@ebony bash$ 3.9.obj/depmod -n > modules.dep && ls -l modules.dep
WARNING: Couldn't find symtab and strtab in module /lib/modules/2.6.28-13-generic/updates/dkms/nvidia.ko
-rw-r--r-- 1 mark mark 1822960 2009-07-07 23:18 modules.dep

That warning (non-fatal) is far more useful than crashing without producing a modules.dep file. With the "broken" (3.7 or 3.8) depmod, I was suffering through this on every apt-get invocation:

Setting up linux-image-2.6.28-13-generic (2.6.28-13.45) ...
Running depmod.
Failed to run depm...

[Scott James Remnant (Canonical) (canonical-scott)]

I've replicated this by doing the following:

# dd if=/lib/modules/2.6.28-14-generic/updates/dkms/nvidia.ko of=/lib/modules/2.6.28-14-generic/updates/broken.ko bs=1 count=761
# depmod
zsh: segmentation fault (core dumped) depmod

The good news is that the ELF rewrite in 3.10 seems to fix this:

# ./build/depmod
WARNING: Couldn't find symtab and strtab in module /lib/modules/2.6.28-14-generic/updates/broken.ko

[Launchpad Janitor (janitor)]

This bug was fixed in the package module-init-tools - 3.10-1

---------------
module-init-tools (3.10-1) karmic; urgency=low

  * New upstream release:
    - Pretty comprehensive ELF handling rewrite.
      LP: #99547, #342255, #370968, #382676, #387081, #399955.
    - depmod can now check module symbol versions.
    - Comprehensive code cleanup.
    - Documentation cleanups.

  * debian/modprobe.d/blacklist-watchdog.conf: Add iTCO_wdt, it8712_wdt,
    it87_wdt, pc87413_wdt, sbc7240_wdt, sch311_wdt, smsc37b787_wdt,
    twl4030_wdt, w83697hf_wdt, w83697ug_wdt & wm8350_wdt. LP: #378328.

 -- Scott James Remnant <email address hidden> Thu, 16 Jul 2009 17:10:34 +0100

[Ivan Baldo (ibaldo)]

I had this problem in a customer machine today, running Ubuntu 9.04 updated as of today, it made the -15 kernel unbootable.
Can this fix be backported to 9.04?
Thanks!!!

[BrettMckee (brett-mckee)]

Agree with the last update. I am on Jaunty and my bug:417019 has been set as a
duplicate of 417020, which is a duplicate now of this one.

However I am still unable to upgrade my kernel 2.6.28-15.
Still getting the following errors.

Errors were encountered while processing:
 linux-image-2.6.28-15-generic
 linux-restricted-modules-2.6.28-15-generic
 linux-image-generic
 linux-restricted-modules-generic
 linux-generic

If this is fixed, how do we overcome these problems?

[Alex Ng'ang'a (lxnganga)]

Having the same problem too. I tried to upgrade my kernel to 2.6.28-15, but couldn't. Got the following,

Setting up linux-image-2.6.28-15-generic (2.6.28-15.49) ...
Running depmod.
Failed to run depmod
dpkg: error processing linux-image-2.6.28-15-generic (--configure):
 subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of linux-restricted-modules-2.6.28-15-generic:
 linux-restricted-modules-2.6.28-15-generic depends on linux-image-2.6.28-15-generic; however:
  Package linux-image-2.6.28-15-generic is not configured yet.
dpkg: error processing linux-restricted-modules-2.6.28-15-generic (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-image-generic:
 linux-image-generic depends on linux-image-2.6.28-15-generic; however:
  Package linux-image-2.6.28-15-generic is not configured yet.
dpkg: error processing linux-image-generic (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-restricted-modules-generic:
 linux-restricted-modules-generic depends on linux-restricted-modules-2.6.28-15-generic; however:
  Package linux-restricted-modules-2.6.28-15-generic is not configured yet.
dpkg: error processing linux-restricted-modules-generic (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic:
 linux-generic depends on linux-image-generic (= 2.6.28.15.20); however:
  Package linux-image-generic is not configured yet.
 linux-generic depends on linux-restricted-modules-generic (= 2.6.28.15.20); however:
  Package linux-restricted-modules-generic is not configured yet.
dpkg: error processing linux-generic (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-image-2.6.28-15-generic
 linux-restricted-modules-2.6.28-15-generic
 linux-image-generic
 linux-restricted-modules-generic
 linux-generic

I tried doing it in recovery mode. This looped for ever giving errors. Now grub shows two kernels, 13 and 15.
15 won't boot so I am using 13.

I am running ubuntu 9.04.

Need help on how to deal with this.

[Zuzkins (zuzkins-gmail)]

Got this problem on 8.10 and couldn't solve it, so i installed ubuntu 9.04 alpha from cd didn't use dist-upgrade, and the problem disappeared.
I think this is not gonna help you much, guys, but anyways, I think reinstalling can help (which is not optimal).

Good luck

[BrettMckee (brett-mckee)]

I don't think reinstall is going to help, and it shouldn't be necessary. I just installed Jaunty on my
machine from live CD, then ran Update Manager and ran into the issue. So, mine is a brand new
install, about a week old.

Of course I am not sure what alpha is, so it may be a different release than what I used, but I don't
think reinstall should be necessary.

[Matt Zimmerman (mdz)]

To those asking for a workaround:

The situation which triggers this crash is a corrupt or invalid module in
/lib/modules. Naturally, depmod should not crash, even in this case, and
that is the bug which is now believed to be fixed in Karmic.

In order to work around the problem, it's necessary to remove or replace the
invalid module. I don't have a step-by-step recipe to hand for this at the
moment, so if you don't know how to do this, just sit tight until someone
posts one. If a workaround is available, it should be added to the bug
description at the top so that it's immediately visible to everyone.

--
 - mdz

[Ivan Baldo (ibaldo)]

    Hello.
    You can fix it by removing the kernel that is giving problems, then
removing the directory /lib/modules/VERSION_OF_THE_KERNEL_REMOVED, then
reinstalling the kernel.
    DKMS has a caching system for modules also, so if the problematic
module is one generated by DKMS and it has a corrupt cached version, you
must tell DKMS to rebuild all its modules or clear its cache, I don't
remember how I did that though and I don't have access to an Ubuntu
machine right now, but if someone asks then I will try to give the
proper instructions.
    Hope this helps anyway.
    Bye.

El 02/09/09 12:32, Matt Zimmerman escribió:
> To those asking for a workaround:
>
> The situation which triggers this crash is a corrupt or invalid module in
> /lib/modules. Naturally, depmod should not crash, even in this case, and
> that is the bug which is now believed to be fixed in Karmic.
>
> In order to work around the problem, it's necessary to remove or replace the
> invalid module. I don't have a step-by-step recipe to hand for this at the
> moment, so if you don't know how to do this, just sit tight until someone
> posts one. If a workaround is available, it should be added to the bug
> description at the top so that it's immediately visible to everyone.
>
>

--
Ivan Baldo - <email address hidden> - http://ibaldo.codigolibre.net/
From Montevideo, Uruguay, at the south of South America.
Freelance programmer and GNU/Linux system administrator, hire me!
Alternatives: <email address hidden> - http://go.to/ibaldo

[Alex Ng'ang'a (lxnganga)]

Hello Ivan,

Someone is asking. So please post a step by step guide on how to fix this.
I am new to Ubuntu (Linux actually), and just learning. This issue is a bit frustrating.

Regards.

[Leann Ogasawara (leannogasawara)]

Alex,

The simplest set of directions for you will be to run the following commands from a Terminal (Applications->Accessories->Terminal):

1) sudo apt-get remove linux-image-2.6.28-15-generic
2) sudo rm -rf /lib/modules/2.6.28-15-generic
3) sudo apt-get install linux-image-2.6.28-15-generic

[Ivan Baldo (ibaldo)]

    Yes, I agree with Leann.
    Let me know if that doesn't fix your problem, then I will try to get
instructions for the DKMS.
    Good luck!

El 04/09/09 14:07, Leann Ogasawara escribió:
> Alex,
>
> The simplest set of directions for you will be to run the following
> commands from a Terminal (Applications->Accessories->Terminal):
>
> 1) sudo apt-get remove linux-image-2.6.28-15-generic
> 2) sudo rm -rf /lib/modules/2.6.28-15-generic
> 3) sudo apt-get install linux-image-2.6.28-15-generic
>
>

--
Ivan Baldo - <email address hidden> - http://ibaldo.codigolibre.net/
From Montevideo, Uruguay, at the south of South America.
Freelance programmer and GNU/Linux system administrator, hire me!
Alternatives: <email address hidden> - http://go.to/ibaldo

[Apual (huanghuaiyue)]

在2009-09-05，"Ivan Baldo" <email address hidden> 写道：
> Yes, I agree with Leann.
> Let me know if that doesn't fix your problem, then I will try to get
>instructions for the DKMS.
> Good luck!
>
>
>El 04/09/09 14:07, Leann Ogasawara escribió:
>> Alex,
>>
>> The simplest set of directions for you will be to run the following
>> commands from a Terminal (Applications->Accessories->Terminal):
>>
>> 1) sudo apt-get remove linux-image-2.6.28-15-generic
>> 2) sudo rm -rf /lib/modules/2.6.28-15-generic
>> 3) sudo apt-get install linux-image-2.6.28-15-generic
>>
>>
>
>--
>Ivan Baldo - <email address hidden> - http://ibaldo.codigolibre.net/
>>From Montevideo, Uruguay, at the south of South America.
>Freelance programmer and GNU/Linux system administrator, hire me!
>Alternatives: <email address hidden> - http://go.to/ibaldo
>
>--
>[apport] depmod crashed with SIGSEGV in strcmp()
>https://bugs.launchpad.net/bugs/99547
>You received this bug notification because you are a direct subscriber
>of a duplicate bug.
>
>Status in “module-init-tools” package in Ubuntu: Fix Released
>Status in “module-init-tools” package in Fedora: Confirmed
>
>Bug description:
>Binary package hint: module-init-tools
>
>make initrd iamge with mkinitramfs
>
>ProblemType: Crash
>Architecture: i386
>Date: Sat Mar 31 22:10:18 2007
>DistroRelease: Ubuntu 7.04
>ExecutablePath: /sbin/depmod
>Package: module-init-tools 3.3-pre3-1ubuntu4
>PackageArchitecture: i386
>ProcCmdline: depmod 2.6.20-ubuntu1johnny
>ProcCwd: /usr/src/linux-source-2.6.20
>ProcEnviron:
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
> LANG=hu_HU.UTF-8
> SHELL=/bin/bash
>Signal: 11
>SourcePackage: module-init-tools
>StacktraceTop:
> strcmp () from /lib/tls/i686/cmov/libc.so.6
> ?? ()
> ?? ()
> ?? ()
> ?? ()
>Uname: Linux johnny-desktop 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux
>UserGroups:

[Alex Ng'ang'a (lxnganga)]

Removing then reinstalling worked as suggested by leann.

Thanks so much for your help guys!

[BrettMckee (brett-mckee)]

The steps that Leann posted did not work for me.
Well, the remove and rm -rf did, but the install failed
again with the following.

sudo apt-get install linux-image-2.6.28-15-generic
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-headers-2.6.28-11 linux-headers-2.6.28-11-generic
Use 'apt-get autoremove' to remove them.
Suggested packages:
  fdutils linux-doc-2.6.28 linux-source-2.6.28
The following packages will be REMOVED:
  linux-restricted-modules-2.6.28-15-generic
The following NEW packages will be installed:
  linux-image-2.6.28-15-generic
0 upgraded, 1 newly installed, 1 to remove and 2 not upgraded.
1 not fully installed or removed.
Need to get 0B/24.6MB of archives.
After this operation, 93.4MB of additional disk space will be used.
Do you want to continue [Y/n]? Y
(Reading database ... 120640 files and directories currently installed.)
Removing linux-restricted-modules-2.6.28-15-generic ...
dpkg (subprocess): unable to execute post-removal script: Exec format error
dpkg: error processing linux-restricted-modules-2.6.28-15-generic (--remove):
 subprocess post-removal script returned error exit status 2
Errors were encountered while processing:
 linux-restricted-modules-2.6.28-15-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)

Any ideas?

/Brett

[Ivan Baldo (ibaldo)]

    This doesn't seem related to the depmod problem.
    First try removing the package
linux-restricted-modules-2.6.28-15-generic.
    If the error persist when trying to remove that package and if you
know posix shell scripting, then edit the
/var/lib/dpkg/info/linux-restricted-modules-2.6.28-15-generic.postrm ,
put debug statements to see where it fails and try to avoid the error or
ignore it.
    If the error persist when trying to remove that package and if you
don't know posix shell scripting, then delete the file
/var/lib/dpkg/info/linux-restricted-modules-2.6.28-15-generic.postrm.
    Then try to remove the package again, it should work now.
    After that, install both packages again: "sudo apt-get install
linux-image-2.6.28-15-generic linux-restricted-modules-2.6.28-15-generic".
    Hope this helps! Good luck!

El 08/09/09 14:46, BrettMckee escribió:
> The steps that Leann posted did not work for me.
> Well, the remove and rm -rf did, but the install failed
> again with the following.
>
> sudo apt-get install linux-image-2.6.28-15-generic
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following packages were automatically installed and are no longer required:
> linux-headers-2.6.28-11 linux-headers-2.6.28-11-generic
> Use 'apt-get autoremove' to remove them.
> Suggested packages:
> fdutils linux-doc-2.6.28 linux-source-2.6.28
> The following packages will be REMOVED:
> linux-restricted-modules-2.6.28-15-generic
> The following NEW packages will be installed:
> linux-image-2.6.28-15-generic
> 0 upgraded, 1 newly installed, 1 to remove and 2 not upgraded.
> 1 not fully installed or removed.
> Need to get 0B/24.6MB of archives.
> After this operation, 93.4MB of additional disk space will be used.
> Do you want to continue [Y/n]? Y
> (Reading database ... 120640 files and directories currently installed.)
> Removing linux-restricted-modules-2.6.28-15-generic ...
> dpkg (subprocess): unable to execute post-removal script: Exec format error
> dpkg: error processing linux-restricted-modules-2.6.28-15-generic (--remove):
> subprocess post-removal script returned error exit status 2
> Errors were encountered while processing:
> linux-restricted-modules-2.6.28-15-generic
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
>
> Any ideas?
>
> /Brett
>
>

--
Ivan Baldo - <email address hidden> - http://ibaldo.codigolibre.net/
From Montevideo, Uruguay, at the south of South America.
Freelance programmer and GNU/Linux system administrator, hire me!
Alternatives: <email address hidden> - http://go.to/ibaldo

[BrettMckee (brett-mckee)]

Thanks Ivan.

I did the latter, as I didn't feel like spending the time debugging and
removed the /var/lib/dpkg/info/linux-restricted-modules-2.6.28-15-generic.postrm
and then did the sudo apt-get install linux-image-2.6.28-15-generic linux-restricted-modules-2.6.28-15-generic

That worked and it is all working now.

Thanks again!
/Brett

[Jon (jon-redhat-bugs)]

Was this ever reproduced?

[Zdenek (zdenek-redhat-bugs)]

Hmm, 2 years old bug - I'm running rawhide - thus I cannot try to reproduce this bug anyway. It's been most probably fixed with some package update.

As I said originally, I had no idea, how I did manage to produce such crash.

[David Gordon (david-gordon-hughes)]

Just to verify this has also solved my issue with linux-image-2.6.28-18
Thank you

[Bug (bug-redhat-bugs)]

This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

[Bug (bug-redhat-bugs)]

Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.