Samsung A900 MSD mode no longer mounts w/ kernel 2.6.27-7

Bug #292522 reported by Lucas Henderson
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
Nominated for Jaunty by Corey Kearney

Bug Description

Binary package hint: linux-image-2.6.27-7-generic

After upgrading to 2.6.27-7, with the upgrade to Intrepid, I can no longer get the USB Mass Storage mode of my Samsung A900 cell phone to mount. When I boot into 2.6.24-21, it works flawlessly.

Here's the log:

Nov 2 02:51:13 LTHlaptop kernel: [ 5924.384164] usb 3-2: new full speed USB device using uhci_hcd and address 6
Nov 2 02:51:13 LTHlaptop kernel: [ 5924.582999] usb 3-2: configuration #1 chosen from 1 choice
Nov 2 02:51:13 LTHlaptop kernel: [ 5924.601966] scsi3 : SCSI emulation for USB Mass Storage devices
Nov 2 02:51:13 LTHlaptop kernel: [ 5924.607529] usb-storage: device found at 6
Nov 2 02:51:13 LTHlaptop kernel: [ 5924.607543] usb-storage: waiting for device to settle before scanning
Nov 2 02:51:18 LTHlaptop kernel: [ 5929.605612] usb-storage: device scan complete
Nov 2 02:51:18 LTHlaptop kernel: [ 5929.609589] scsi 3:0:0:0: Direct-Access Samsung Mass Storage 2.31 PQ: 0 ANSI: 2
Nov 2 02:51:18 LTHlaptop kernel: [ 5929.637486] sd 3:0:0:0: [sdb] 97210 512-byte hardware sectors (50 MB)
Nov 2 02:51:18 LTHlaptop kernel: [ 5929.640462] sd 3:0:0:0: [sdb] Write Protect is off
Nov 2 02:51:18 LTHlaptop kernel: [ 5929.640480] sd 3:0:0:0: [sdb] Mode Sense: 0b 00 00 08
Nov 2 02:51:18 LTHlaptop kernel: [ 5929.640488] sd 3:0:0:0: [sdb] Assuming drive cache: write through
Nov 2 02:51:18 LTHlaptop kernel: [ 5929.651471] sd 3:0:0:0: [sdb] 97210 512-byte hardware sectors (50 MB)
Nov 2 02:51:18 LTHlaptop kernel: [ 5929.657481] sd 3:0:0:0: [sdb] Write Protect is off
Nov 2 02:51:18 LTHlaptop kernel: [ 5929.657504] sd 3:0:0:0: [sdb] Mode Sense: 0b 00 00 08
Nov 2 02:51:18 LTHlaptop kernel: [ 5929.657513] sd 3:0:0:0: [sdb] Assuming drive cache: write through
Nov 2 02:51:18 LTHlaptop kernel: [ 5929.665105] sdb: sdb1
Nov 2 02:51:18 LTHlaptop kernel: [ 5929.678737] sd 3:0:0:0: [sdb] Attached SCSI removable disk
Nov 2 02:51:18 LTHlaptop kernel: [ 5929.683062] sd 3:0:0:0: Attached scsi generic sg1 type 0
Nov 2 02:51:19 LTHlaptop kernel: [ 5930.372407] sd 3:0:0:0: [sdb] Device not ready: Sense Key : Not Ready [current]
Nov 2 02:51:19 LTHlaptop kernel: [ 5930.372431] sd 3:0:0:0: [sdb] Device not ready: Add. Sense: Medium not present
Nov 2 02:51:19 LTHlaptop kernel: [ 5930.372446] end_request: I/O error, dev sdb, sector 97209
Nov 2 02:51:19 LTHlaptop kernel: [ 5930.372464] Buffer I/O error on device sdb, logical block 48604
The last 3 lines are repeated numerous times(with differing sectors) every second, until I disconnect my phone.

After comparing this to the logs produced when running 2.6.24-21, I noticed that the messages were mostly(I think entirely) the same, the only difference was that on 2.6.27-7, the messages never stop, and the device does not auto-mount(Manual mounting was unsuccessful too).

I compiled my kernel with the patch from Bug #287701, since the problem looked similar, but it did not solve the problem.

Here is the output of lsusb -v
Bus 003 Device 004: ID 05c6:1000 Qualcomm, Inc.
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 1.10
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 64
  idVendor 0x05c6 Qualcomm, Inc.
  idProduct 0x1000
  bcdDevice 0.00
  iManufacturer 1
  iProduct 2
  iSerial 3
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 32
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xe0
      Self Powered
      Remote Wakeup
    MaxPower 100mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 2
      bInterfaceClass 8 Mass Storage
      bInterfaceSubClass 6 SCSI
      bInterfaceProtocol 80 Bulk (Zip)
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x84 EP 4 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x05 EP 5 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0

description: updated
description: updated
Revision history for this message
Corey Kearney (snkiz-deactivatedaccount) wrote :

Also having the same problem with a Samsung SPH-m510. mount ok for 8.04, and windows

Revision history for this message
Corey Kearney (snkiz-deactivatedaccount) wrote :

Lucas I've been unable to update for awhile my dsl is down, my kernel version is 2.6.27-11-generic still no love for my phone. Are you up-to-date? has the problem been fixed?

Revision history for this message
kernel-janitor (kernel-janitor) wrote :

Hi Lucas,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/karmic .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 292522

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.