Skip to content

Increase default PPP stack size from 512 bytes to 768 bytes. #4677

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 13, 2017

Conversation

RobMeades
Copy link
Contributor

Description

PPP is running close to the edge of its default thread stack size of 512 bytes. When it experiences an FCS error on the incoming data (caused by character loss when the incoming serial rate is too high for it to process in time) it performs some additional work which overruns the thread's stack, hitting the OS "stack underflow" check.

Increasing the PPP stack size to 768 bytes resolves this problem.

Note: this change already discussed at some length with @kjbracey-arm.

Steps to reproduce

Run PPPCellularInterface with the UART serial port running at 460800 or higher and wait for the OS stack check to be hit.

@bulislaw
Copy link
Member

Not really related to this PR, but we should have documentation somewhere stating how different features will impact memory usage/requirements.

@0xc0170
Copy link
Contributor

0xc0170 commented Jul 3, 2017

@RobMeades Can you please amend your commit to provide more details (what you already did in the description here) - why are we changing from x to y stack value.

PPP is running close to the edge of its default thread stack size of 512 bytes. When it experiences an FCS error on the incoming data (for example. caused by character loss when the incoming serial rate is too high for it to process in time) it performs some additional work which overruns the thread's stack, hitting the OS "stack underflow" check. Increasing the PPP stack size to 768 bytes resolves this problem.
@RobMeades RobMeades force-pushed the ppp_stack_increase branch from 484ad32 to 921d1fa Compare July 3, 2017 08:49
@RobMeades
Copy link
Contributor Author

Certainly, done.

@0xc0170
Copy link
Contributor

0xc0170 commented Jul 3, 2017

retest uvisor

@theotherjimmy
Copy link
Contributor

/morph test

@mbed-bot
Copy link

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 771

All builds and test passed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants