Re: hang in tstile with Samsung Galaxy

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Fri, Apr 09, 2010 at 10:46:32AM +0200, Christoph Egger wrote:
> Hi!
> 
> When I plug my Samsung Galaxy mobile phone via USB,
> I get this dmesg output:
> 
> umodem0 at uhub1 port 2 configuration 2 interface 0
> umodem0: Qualcomm Incorporated Samsung Android USB Device, rev
> 2.00/1.00, addr 3, iclass 2/2
> umodem0: data interface 1, has no CM over data, has break
> umodem0: status change notification available
> ucom0 at umodem0
> umodem0: WARNING: power management not supported
> umass0 at uhub1 port 2 configuration 2 interface 3
> umass0: Qualcomm Incorporated Samsung Android USB Device, rev 2.00/1.00,
> addr 3
> umass0: using SCSI over Bulk-Only
> scsibus0 at umass0: 2 targets, 2 luns per target
> sd0 at scsibus0 target 0 lun 0: <Samsung, SAMSUNG Android, Mass> disk
> removable
> sd0(umass0:0:0:0): preposterous sector size: 0x0.  Defaulting to 512 bytes.
> sd0: fabricating a geometry
> sd0: 512, 0 cyl, 64 head, 32 sec, 512 bytes/sect x 1 sectors
> sd0(umass0:0:0:0): preposterous sector size: 0x0.  Defaulting to 512 bytes.
> sd0: fabricating a geometry
> 
> When do 'disklabel sd0' then disklabel hangs in tstile.
> 
> The output from 'ps asx':
> 
>   0 619  539    0   1    1 117  0  7552   796 tstile   D    ttyE0
> 0:00.00 disklabel sd0

I would guess the device returns an error which is not properly
handled. can you get a stack trace of the disklabel process in
the kernel ?

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--