Re: console hangs after setting hostname

On Sat, 11 Aug 2007 21:34:52 +0100
Bruce Cran <bruce_at_cran.org.uk> wrote:

> KOT MATPOCKuH wrote:
> > I got a problem. After messages on console:
> > ...
> > Mounting local files systems:.
> > Setting hostname: green.
> > fxp: link state changed to UP
> > nfe0: link state changed to DOWN
> >
> > console hangs.
> > No any new messages, I can't input anything from keyboard, changing virtual
> > consoles is not working. After X is started, console is not switched to xdm
> > display.
> > But system is works - I can login to system via ssh, ...
> >
> > dmesg.boot is attached.
> >
> > Where is a problem and what I need to do? :)
> >   
> 
> I'm also seeing the console hang, but in a different situation.  If I 
> attach and remove my iPod the console hangs - the only key press that's 
> accepted is ctrl-alt-esc to break into the debugger.
> 
> umass0: <Apple iPod, class 0/0, rev 2.00/0.01, addr 2> on uhub5
> da0 at umass-sim0 bus 0 target 0 lun 0
> da0: <Apple iPod 1.62> Removable Direct Access SCSI-0 device
> da0: 40.000MB/s transfers
> da0: 19073MB (39063024 512 byte sectors: 255H 63S/T 2431C)
> (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 2 54 d ef 0 0 1 0
> (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
> (da0:umass-sim0:0:0:0): SCSI Status: Check Condition
> (da0:umass-sim0:0:0:0): ILLEGAL REQUEST asc:21,0
> (da0:umass-sim0:0:0:0): Logical block address out of range
> (da0:umass-sim0:0:0:0): Unretryable error
> (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 2 54 d ef 0 0 1 0
> (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
> (da0:umass-sim0:0:0:0): SCSI Status: Check Condition
> (da0:umass-sim0:0:0:0): ILLEGAL REQUEST asc:21,0
> (da0:umass-sim0:0:0:0): Logical block address out of range
> (da0:umass-sim0:0:0:0): Unretryable error
> GEOM_LABEL: Label for provider da0s2 is msdosfs/IPOD.
> 
> When I remove the iPod I get the following messages:
> 
> umass0: at uhub5 port 1 (addr 2) disconnected
> da0:umass-sim0:0:0G:0EO :M _LlAoBst L d  ev aibceel <-- garbled
> )m(sd ao0s:fs m/aIsPsO-Ds irme0m:o0v:ed :.0         <-- output
>  : removing device entry
> umass0: detached
> 

I reported this problem at least a month ago. The garbled ouput to the
console somehow completely screws things up so that only output from
the kernel appears thereafter.

I have no idea why this happens, but the pattern is very clear.

--- 
Gary Jennejohn