Hi,
This did not happen with 2.6.1-mm4 . The system is still running fine
at the moment but I find several message in the dmesg output
pppd: page allocation failure. order:4, mode:0xd0
Call Trace: [<c01388f0>] [<c013895f>] [<c013b48c>] [<c013b79e>] [<c013bae4>] [<c01fc177>] [<c01f87b4>] [<c01f6bd1>] [<c014e742>] [<c015f299>] [<c02b2f67>]
pppd: page allocation failure. order:4, mode:0xd0
Call Trace: [<c01388f0>] [<c013895f>] [<c013b48c>] [<c013b79e>] [<c013bae4>] [<c01fc177>] [<c01f87b4>] [<c01f6bd1>] [<c014e742>] [<c015f299>] [<c02b2f67>]
pppd: page allocation failure. order:4, mode:0xd0
Call Trace: [<c01388f0>] [<c013895f>] [<c013b48c>] [<c013b79e>] [<c013bae4>] [<c01fc177>] [<c01f87b4>] [<c01f6bd1>] [<c014e742>] [<c015f299>] [<c02b2f67>]
If some one need further testing or information pls cc me.
Steve Kieu
[email protected] wrote:
>
>
> Hi,
>
> This did not happen with 2.6.1-mm4 . The system is still running fine
> at the moment but I find several message in the dmesg output
>
> pppd: page allocation failure. order:4, mode:0xd0
> Call Trace: [<c01388f0>] [<c013895f>] [<c013b48c>] [<c013b79e>] [<c013bae4>] [<c01fc177>] [<c01f87b4>] [<c01f6bd1>] [<c014e742>] [<c015f299>] [<c02b2f67>]
Please enable CONFIG_KALLSYMS to get a symbolic trace and resend that.