2008-01-26 15:58:06     dropbear problems in svn?

Document created by Aaronwu Employee on Aug 6, 2013
Version 1Show Document
  • View in full screen mode

2008-01-26 15:58:06     dropbear problems in svn?

Jason Holden (UNITED STATES)

Message: 50187    The last feature I am trying to enable is dropbear from an SVN kernel.  It looks like dropbear hasn't been modified in over 4 months, and there has been forum traffic indicating that the trunk was good.  However, I get the following error when SSHing into the board using a straight svn build.  I answer No to all the new kernel config options., and the only change I make to uclinux configs is to enable dropbear.  Does anyone else see this when they try and SSH into the blackfin?  Is there some new dependency that I am missing?  The wiki looks a bit out of date (dropbearstatic instead of dropbearmulti).  Thanks again!

 

-Jason

 

root:~> PHY: 0:01 - Link is Up - 100/Full

Data access CPLB miss

- Used by the MMU to signal a CPLB miss on a data access.

Defered Exception context

CURRENT PROCESS:

COMM=dropbear PID=99

TEXT = 0x00600040-0x0062d100  DATA = 0x0062d104-0x0063aa34

BSS = 0x0063aa34-0x0064cfd4   USER-STACK = 0x0064ef0c

 

return address: [0x006270e8]; contents of:

0x006270c0:  1fe3  0803  51fa  181d  0000  0000  ac51  0c41

0x006270d0:  1809  0000  0000  9109  3071  520e  6460  0803

0x006270e0:  1820  3222  0c40  5a94 [bc51] bc90  1818  bc42

0x006270f0:  0c41  1802  bc8a  324a  9317  2fd3  6800  2fc4

 

SEQUENCER STATUS:               Not tainted

SEQSTAT: 00000026  IPEND: 0030  SYSCFG: 0006

  HWERRCAUSE: 0x0

  EXCAUSE   : 0x26

RETE: <0x00000000> /* Maybe null pointer? */

RETN: <0x008b2000> /* unknown address */

RETX: <0x006270e8> [ dropbear + 0x270a8 ]

RETS: <0x00626df8> [ dropbear + 0x26db8 ]

PC  : <0x006270e8> [ dropbear + 0x270a8 ]

DCPLB_FAULT_ADDR: <0x204e300c> /* unknown address */

ICPLB_FAULT_ADDR: <0x006270e8> [ dropbear + 0x270a8 ]

 

PROCESSOR STATE:

R0 : 00786f50    R1 : 000000b0    R2 : 1fea87b0    R3 : 20000000

R4 : 0063a810    R5 : 00157850    R6 : 00786ff4    R7 : 1fea87c4

P0 : 001575a4    P1 : 00786ff4    P2 : 204e3008    P3 : 0063a80c

P4 : 1fea87b0    P5 : 0063a80c    FP : 0064cffc    SP : 008b1f24

LB0: 00625073    LT0: 00625072    LC0: 00000000

LB1: 006179e7    LT1: 006179e0    LC1: 00000000

B0 : 00000000    L0 : 00000000    M0 : 00000000    I0 : 00157958

B1 : 00000000    L1 : 00000000    M1 : 00000000    I1 : 00000000

B2 : 00000000    L2 : 00000000    M2 : 00000000    I2 : 00000036

B3 : 00000000    L3 : 00000000    M3 : 00000000    I3 : 00000000

A0.w: fffffe49   A0.x: ffffffff   A1.w: fffffe49   A1.x: ffffffff

USP : 0064cffc  ASTAT: 02003004

 

Hardware Trace:

   0 Target : <0x000047e0> { _trap_c + 0x0 }

     Source : <0xffa007ac> { _exception_to_level5 + 0xb4 }

   1 Target : <0xffa006f8> { _exception_to_level5 + 0x0 }

     Source : <0xffa00650> { _ex_trap_c + 0x68 }

   2 Target : <0xffa00824> { _trap + 0x0 }

     Source : <0xffa0057e> { _bfin_return_from_exception + 0x1a }

   3 Target : <0xffa00824> { _trap + 0x0 }

     Source : <0x006270e6> [ dropbear + 0x270a6 ]

   4 Target : <0x006270ae> [ dropbear + 0x2706e ]

     Source : <0x00627074> [ dropbear + 0x27034 ]

   5 Target : <0x0062706c> [ dropbear + 0x2702c ]

     Source : <0x00627080> [ dropbear + 0x27040 ]

   6 Target : <0x0062706e> [ dropbear + 0x2702e ]

     Source : <0x0062706a> [ dropbear + 0x2702a ]

   7 Target : <0x00627058> [ dropbear + 0x27018 ]

     Source : <0x00626df4> [ dropbear + 0x26db4 ]

   8 Target : <0x00626de2> [ dropbear + 0x26da2 ]

     Source : <0x00626d9a> [ dropbear + 0x26d5a ]

   9 Target : <0x00626d4c> [ dropbear + 0x26d0c ]

     Source : <0x006270a8> [ dropbear + 0x27068 ]

  10 Target : <0x006270a0> [ dropbear + 0x27060 ]

     Source : <0x006270fa> [ dropbear + 0x270ba ]

  11 Target : <0x006270ae> [ dropbear + 0x2706e ]

     Source : <0x00627074> [ dropbear + 0x27034 ]

  12 Target : <0x0062706c> [ dropbear + 0x2702c ]

     Source : <0x00627080> [ dropbear + 0x27040 ]

  13 Target : <0x0062706e> [ dropbear + 0x2702e ]

     Source : <0x0062706a> [ dropbear + 0x2702a ]

  14 Target : <0x00627058> [ dropbear + 0x27018 ]

     Source : <0x00626d48> [ dropbear + 0x26d08 ]

  15 Target : <0x00626d42> [ dropbear + 0x26d02 ]

     Source : <0x006288bc> [ dropbear + 0x2887c ]

Stack from 008b1f04:

        ffa00b6e ffa007b0 00144568 00144568 00144564 00157500 00000000 000084f8

        006270e8 00000030 00000026 00000000 008b2000 006270e8 006270e8 00626df8

        00786f50 02003004 006179e7 00625073 006179e0 00625072 00000000 00000000

        fffffe49 ffffffff fffffe49 ffffffff 00000000 00000000 00000000 00000000

        00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

        00000000 00000036 00000000 00157958 0064cffc 0064cffc 0063a80c 1fea87b0

 

Call Trace:

[<001575a4>] _bfin_init_mmr_debugfs+0xff0/0x7074

[<00157850>] _bfin_init_mmr_debugfs+0x129c/0x7074

[<001575a4>] _bfin_init_mmr_debugfs+0xff0/0x7074

QuoteReplyEditDelete

 

 

2008-01-27 13:46:05     Re: dropbear problems in svn?

Mike Frysinger (UNITED STATES)

Message: 50195    looks like a stack overflow

 

it doesnt crash as FDPIC ELF (prob because the stack mapping happens to not overlap anything else) and if you bump the stack up using flthdr, it seems to work ok

 

can you confirm ?

QuoteReplyEditDelete

 

 

2008-01-27 14:50:13     Re: dropbear problems in svn?

Robin Getz (UNITED STATES)

Message: 50196    The default stack size for fdpic is larger than the current setting for dropbear (as flat) - aren't they? (so it is not just a location issue?)

 

-Robin

QuoteReplyEditDelete

 

 

2008-01-28 00:56:51     Re: dropbear problems in svn?

Mike Frysinger (UNITED STATES)

Message: 50198    you're right ... FDPIC ELF has a default stack 20x that of FLAT

QuoteReplyEditDelete

 

 

2008-01-28 11:48:33     Re: dropbear problems in svn?

Jason Holden (UNITED STATES)

Message: 50240    Setting the stack size to 16384 gave very good results.  A stack size of 8192 didn't crash the board, but scp also doesn't copy files properly.

QuoteReplyEditDelete

 

 

2008-01-28 12:19:35     Re: dropbear problems in svn?

Mike Frysinger (UNITED STATES)

Message: 50242    ive bumped the default to 0x4000 in the dist ... thanks for testing

QuoteReplyEditDelete

 

 

2008-04-09 11:10:56     Re: dropbear problems in svn?

Manolo van Ee (NETHERLANDS)

Message: 53929    I still see this problem in 2008R1-RC8.

Was this only fixed on trunk?

 

Regards,

Manolo

QuoteReplyEditDelete

 

 

2008-04-09 11:55:39     Re: dropbear problems in svn?

Mike Frysinger (UNITED STATES)

Message: 53934    well it's fairly easy for you to check: do you see FLTFLAGS in the branch like in trunk ?  if not, then it was only added to trunk and i'll have to add it to the branch as well.

QuoteReplyEditDelete

 

 

2008-04-10 03:22:31     Re: dropbear problems in svn?

Manolo van Ee (NETHERLANDS)

Message: 53982    Ok, now I understand what's happening.

And I see that vapier fixed it.

Thanks,

Manolo

QuoteReplyEditDelete

 

 

2008-05-06 14:16:11     Re: dropbear problems in svn?

Keith Morgan (UNITED STATES)

Message: 55576   

 

Sorry, I'm a newbie here and don't quite understand all of the lingo used in this thread.  I'm having the same problem and it isn't clear to me what I should do to fix it.  Do I need to change the stack size?  If so, exactly how do I do that?  Or do I need to use the latest bleeding edge code from SVN and rebuild the kernel that way?

 

Thanks!

 

-keith

 

 

QuoteReplyEditDelete

 

 

2008-05-06 14:32:43     Re: dropbear problems in svn?

Mike Frysinger (UNITED STATES)

Message: 55577   

 

just use the fix here:

http://blackfin.uclinux.org/gf/project/uclinux-dist/scmsvn/?action=browse&path=%2F&view=rev&revision=6540

Attachments

    Outcomes