Red Hat Bugzilla – Bug 720054
dmesg shows usb disconnect and traceback on a Toshiba NB555D
Last modified: 2011-08-22 10:50:59 EDT
Created attachment 511996 [details]
output of dmesg command
Call trace in dmesg during boot.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Might this be a duplicate of:
(In reply to comment #1)
> Might this be a duplicate of:
> Bug 663186?
I don't think so, no. The backtraces are entirely different. This looks more like a bug in the ums-realtek driver. It's using stack variables to pass as DMA buffers, which is a no-no.
Could you please test this kernel and let me know if it solves the stack trace?
Created attachment 517000 [details]
Output of dmesg command with test kernel
Call trace is gone. However, I am observing the collision problem mentioned in bug 710715 , around line 237, since kernel version 3.
kernel-3.0.1-3.fc16 has been submitted as an update for Fedora 16.
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kernel-3.0.1-3.fc16'
as soon as you are able to, then reboot.
Please go to the following url:
then log in and leave karma (feedback).
Created attachment 517435 [details]
dmesg output of kernel 3.0.1-3.fc16.x86_64
Still shows address space collision. Display locks after restarting from Hibernate.
Created attachment 517436 [details]
dmesg output of kernel 3.0.1-3.fc16.x86_64 with nomodest, pci=nocrs
Added pci=nocrs to get rid of address space collision, and pci=nocrs to avoid display lockup on return from Hibernate.
kernel-220.127.116.11-0.fc15 has been submitted as an update for Fedora 15.
kernel-18.104.22.168-0.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
kernel-3.0.1-3.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.