Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 1 Jun 2009 15:52:10 +0200
From:      cpghost <cpghost@cordula.ws>
To:        ????????? ????????? <der@btsig.ru>
Cc:        questions@freebsd.org
Subject:   Re: Strange text from kernel then detaching USB drive: "sldoosstf sd/e v irceemo"
Message-ID:  <20090601135210.GA5720@phenom.cordula.ws>
In-Reply-To: <4A239BC2.7050606@rusig.ru>
References:  <4A239BC2.7050606@rusig.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 01, 2009 at 01:13:38PM +0400, ????????? ????????? wrote:
> Hello all !
> 
> I got a very confusing messages from kernel then detaching one of my USB 
> external HD (used only for backups):
> 
> 
> May 29 12:40:08 perforce kernel: GEOM_LABEL: Label ufs/Backup5 removed.
> May 29 12:40:08 perforce kernel: GEOM_LABEL: Label for provider da0s1 is 
> ufs/Backup5.
> May 29 12:40:08 perforce kernel: GEOM_LABEL: Label for provider da0s1 is 
> msdosfs/ .
> May 29 12:40:32 perforce kernel: umass0: at uhub3 port 1 (addr 2) 
> disconnected
> May 29 12:40:32 perforce kernel: (da0:uGmEaOsMs_-LsAiBmE0L::0 :La0b:e0l) 
> :m sldoosstf sd/e v irceemo
> May 29 12:40:32 perforce kernel: v(edda.0:
> May 29 12:40:32 perforce kernel: umGaEsOsM-_sLiAmBE0L::0 :L0a:b0e)l:  
> ruefmso/vBiancgk udpe5v irceem oevnetdr.y
> May 29 12:40:32 perforce kernel:
> May 29 12:40:32 perforce kernel: umass0: detached
> 
> 
> I don't understand messages between  "umass0: at uhub3 port 1 (addr 2) 
> disconnected" and "umass0: detached".

It's a known problem on SMP systems. Citing from:
  http://wiki.freebsd.org/BugBusting/Commonly_reported_issues

Scrambled or garbled kernel output, such as:

      SdMaP0::  AP1 6C0P.U0 0#0M1B /Lsa utnrcahnesdf!e
      da0: <SSMEPA:G AATPE  CSPTU3 3#617 5L3auLnWc hHePdS!3> 

      Sep  5 00:34:38 test kernel: Waiting (max 60
      Sep  5 00:34:38 test kernel: seScyonncdisn)g  fdoirs kssy,s tvenmo dperso
      creesmsa i`nsiynngc.e.r.' to3  stop...0 0 done
      Sep  5 00:34:38 test kernel: All buffers synced. 

      <... snip ...>

      Workaround (partial): Use options PRINTF_BUFR_SIZE=256 in your
      kernel configuration. This will decrease the amount of
      interspersed output, but does not solve issue entirely

> What does it mean?
> 
> Best Regards,
> Alexander Derevyanko.

-cpghost.

-- 
Cordula's Web. http://www.cordula.ws/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090601135210.GA5720>