Bug 859468 - OOPS: 3.5.4-1.fc17 && xfs == crash at randomly when unmounting an USB device using truecrypt
Summary: OOPS: 3.5.4-1.fc17 && xfs == crash at randomly when unmounting an USB device ...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-21 15:53 UTC by Ali Akcaagac
Modified: 2013-01-02 12:51 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-01-02 12:51:22 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
The promised picture (669.16 KB, image/jpeg)
2012-11-02 12:05 UTC, Ali Akcaagac
no flags Details

Description Ali Akcaagac 2012-09-21 15:53:03 UTC
Hello

I've been running F17 here with latest updates and realized (over a period of some weeks now) that the kernel tend to crash entirely when trying to unmount an USB partition using truecrypt 7.1a

Unfortunately I can not provide any backtrace or logfile but I wanted to mention it here so in case this happens again that I get the chance to take a picture of the crash and put it online here.

More detail:

I have a crypted USB partition using truecrypt 7.1a (from their site) and the partition self has XFS as filesystem on it. Every now and then when I enter "truecrypt -d" in the terminal to unmount this device the entire Kernel says good bye.

The crash itself told me something about timing issues or so - not sure. Maybe this has been a known issue (if not then this problem is known now).

Comment 1 Ali Akcaagac 2012-11-02 12:05:09 UTC
Created attachment 637052 [details]
The promised picture

Comment 2 Ali Akcaagac 2012-12-31 20:16:55 UTC
The problem can be closed. It has not shown up with more recent kernel versions. Maybe it was a temporary issue which got solved during further kernel development.


Note You need to log in before you can comment on or make changes to this bug.