Bug 478679

Summary: Nokia 6288 usb storage problem
Product: [Fedora] Fedora Reporter: Sergei LITVINENKO <sergei.litvinenko>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 10CC: kernel-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-12-18 07:28:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Sergei LITVINENKO 2009-01-03 11:51:07 UTC
Description of problem:

Nokia 6288 can not be connected by usb cable as USB storage device on Fedora-10.
Nokia 7610 Supernova can not be connected by usb cable as USB storage device on Fedora-10.

How reproducible:
Connect Nokia 6288 by cable to USB and choice "save data" mode in mobile phone.

Steps to Reproduce:
1. Connect phone by standard nokia cable to USB
2. Choice mode "save data" on mobile phone
3. look into /var/log/message or run dmesg 
  
Actual results:

A log of
...
[sdd] Sense Key : No Sense [current]
[sdd] Add. Sense: No additional sense information
...
After some time "Nokia 6288" is self-switched off (unexpected).

Expected results:
New usb storage device is attached and accessible by /dev/sd? device.

Additional info:

1. Log message from my PC:
---
Jan  3 12:34:42 homedesk kernel: scsi 9:0:0:0: Direct-Access     Nokia    Nokia 6288       0000 PQ: 0 ANSI: 4
Jan  3 12:34:42 homedesk kernel: sd 9:0:0:0: [sdd] 3970049 512-byte hardware sectors (2033 MB)
Jan  3 12:34:42 homedesk kernel: sd 9:0:0:0: [sdd] Test WP failed, assume Write Enabled
Jan  3 12:34:42 homedesk kernel: sd 9:0:0:0: [sdd] Assuming drive cache: write through
Jan  3 12:34:42 homedesk kernel: sd 9:0:0:0: [sdd] 3970049 512-byte hardware sectors (2033 MB)
Jan  3 12:34:42 homedesk kernel: sd 9:0:0:0: [sdd] Test WP failed, assume Write Enabled
Jan  3 12:34:42 homedesk kernel: sd 9:0:0:0: [sdd] Assuming drive cache: write through
Jan  3 12:34:42 homedesk kernel: sdd: sdd1
Jan  3 12:34:42 homedesk kernel: sd 9:0:0:0: [sdd] Attached SCSI removable disk
Jan  3 12:34:42 homedesk kernel: sd 9:0:0:0: Attached scsi generic sg5 type 0
Jan  3 12:34:42 homedesk kernel: sd 9:0:0:0: [sdd] Sense Key : No Sense [current]
Jan  3 12:34:42 homedesk kernel: sd 9:0:0:0: [sdd] Add. Sense: No additional sense information
Jan  3 12:34:42 homedesk kernel: sd 9:0:0:0: [sdd] Sense Key : No Sense [current]
Jan  3 12:34:42 homedesk kernel: sd 9:0:0:0: [sdd] Add. Sense: No additional sense information
Jan  3 12:34:42 homedesk kernel: sd 9:0:0:0: [sdd] Sense Key : No Sense [current]
...
... [skip a lot of lines ]
...
Jan  3 12:40:19 homedesk kernel: usb 3-1: reset full speed USB device using uhci_hcd and address 9
Jan  3 12:40:19 homedesk kernel: usb 3-1: device descriptor read/64, error -71
Jan  3 12:40:19 homedesk kernel: usb 3-1: device descriptor read/64, error -71

2. Problem is reproduced on my PC with fedora-10 and distributive kernel
3. Problem is reproduced on my PC with fedora-10 and kernel-2.6.28 from www.kernel.org
4. Problem is reproduced on "ASUS Eee901" with fedora-10 and distributive kernel
5. No problem on Fedora-8 with kernel 2.6.26.6-49.fc8

Version-Release number of selected component (if applicable):
kernel 2.6.27.9-159.fc10.i686.PAE

Comment 1 Sergei LITVINENKO 2009-01-03 21:52:46 UTC
I'm used this hint http://blog.fedoramd.org/2008/11/26/sense-key-no-sense-current/

Because Fedora-10 do not have /etc/udev/rules.d/60-persistent-storage.rules, I'm used 60-persistent-storage.rules from Fedora-8 (without any modification).

It work, now I can mount my mobile phone and read/write files from/to. 

PS: Maybe, it is only work-around, but it is solution for right now.

Comment 2 Sergei LITVINENKO 2009-01-03 23:07:52 UTC
I have changed standard /lib/udev/rules.d/60-persistent-storage.rules from Fedora-10:


# probe filesystem metadata of disks
-KERNEL!="sr*", IMPORT{program}="vol_id --export $tempnode"
+KERNEL!="sr*", ENV{DEVTYPE}=="partition", IMPORT{program}="vol_id --export $tempnode"


and put it into /etc/udev/rules.d/. Now it is in testing, but, as I see, it work OK...

Comment 3 Pete Zaitcev 2009-01-17 00:44:25 UTC
The repeating No Sense seems like bug 470491.

Comment 4 Bug Zapper 2009-11-18 09:43:53 UTC
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  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 '10'.

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 10'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 10 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

Comment 5 Bug Zapper 2009-12-18 07:28:23 UTC
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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.