Bug 24262 - kernel: firmware[13353]: segfault in libc-2.11.2.so
Summary: kernel: firmware[13353]: segfault in libc-2.11.2.so
Status: CLOSED UNREPRODUCIBLE
Alias: None
Product: Power Management
Classification: Unclassified
Component: Hibernation/Suspend (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: power-management_other
URL:
Keywords:
Depends on:
Blocks: 7216
  Show dependency tree
 
Reported: 2010-12-03 09:35 UTC by Toralf Förster
Modified: 2011-01-17 08:53 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.36.1
Subsystem:
Regression: No
Bisected commit-id:

Attachments
/var/log/messages.log (110.21 KB, text/plain)
2010-12-03 09:35 UTC, Toralf Förster 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Toralf Förster 2010-12-03 09:35:14 UTC 
Created attachment 38922 [details]
/var/log/messages.log

As requested from  linux-pci@vger.kernel.org I attached the appropriate /var/log/messages.log part onto this bug report related to :

  dvb-usb: did not find the firmware file. (dvb-usb-dib0700-1.20.fw) Please see linux/Documentation/dvb/ for more details on firmware-problems. (-2)
  usblp0: USB Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x043D pid 0x0078
  PM: Finishing wakeup.
  Restarting tasks ... done.
  video LNXVIDEO:00: Restoring backlight state
  firmware[13353]: segfault at 46 ip b7769597 sp bf9158a0 error 4 in libc-2.11.2.so[b770e000+13f000]
  udevd-work[13350]: 'firmware --firmware=dvb-usb-dib0700-1.20.fw --devpath=/devices/pci0000:00/0000:00:1a.7/usb1/1-1/firmware/1-1' unexpected exit with status 0x000b

I observed this only once. However sometimes my computer doesn't s2ram properly even when it does it well immediately before. This happens if the adapter is plugged in into the ThinkPad.
Comment 1 Rafael J. Wysocki 2010-12-03 21:34:26 UTC 
Does it happen in previous kernels, especially in 2.6.35.y, or is it just
the first kernel you ran on that box?
Comment 2 Toralf Förster 2010-12-04 09:46:56 UTC 
I never observed it before - btw however only once until today.
Comment 3 Rafael J. Wysocki 2011-01-16 22:45:11 UTC 
Is this still an issue with 2.6.37?
Comment 4 Toralf Förster 2011-01-17 08:53:31 UTC 
(In reply to comment #3)
> Is this still an issue with 2.6.37?
Not till now - I'll close it
Note You need to log in before you can comment on or make changes to this bug.