So, In the last 2 years with 4.1 / update1 / update2 i have an always-reproducable issue with ppp-ethernet.device when i use D-Link 2500U modem directly (i.e. via Dialers and co) on my peg2. For any users who will want to answer in that topic, like "use router" - yes, my current workoround its just i use static ips + some route + winxp as main machine for connect to internet (via the same D-Link 2500U), but as bug is still here, i still it worth to report. I also report that on Aw.net few times, and one time directly to Olsen , but i do not know if it was approved, and if it already in the bug-report base, and if Olsen read it at all.
That, how looks like my internet connection script:
It called "inet.conn", and have "inet.conn.info", in which:# PROGDIR:Connections/inet.conn
# File generated by Dialer 53.2 (3.10.2009)
# On Среда, 24-Мар-10 at 14:08:28
Default tool: System:Internet/Dialer
Stack size: 32.768
Tool types: MODE=OPEN
Nextly, i click on that icon, it connects, spawn me information window (how many bytes are transfered, activity and so on). All looks fine at that stage, so, i trying to use internet. Run OWB, go to some site - all is fine. Press on some topic, all is fine. Then go to some other site and have crash in the ppp-ethernet.device. Crash always the same, with the same DSI and crashlog, and happens always after 2-5 minuts of internet usage after connection is happens.
I tryed to save all the possible info from. For first i show you screenshot of how looks dialer-info window, GR and memguard/shashimi output at one time: here is that screenshot.
For second, i show you information about that DSL modem (d-link 2500u) which i grab as screenshot when point browser on DSL and get main statistic about (maybe it will helps too): here is that screenshot.
And the last, and the most important, classic GR log:
Please, take a look at this, and i can help with all possibly testings and so on. You also can send me debug version of ppp-ethernet.device and can grab GR with normal offsets.
Hidden Text - Click to Show :
Maybe its all of course in the internal bug-tracker already, but maybe not. So i think its worth to mention one more time here.