hello everyone, thanks for your suggestions from before, here are my responses:
baud wrote: > > /usr/include/asm/bitops.h:327:2: warning: #warning > > This includefile is not available on all > > architectures. > > /usr/include/asm/bitops.h:328:2: warning: #warning > > Using kernel headers in userspace: atomicity not > > guaranteed > we'll have to investigate, this does not happen on > my Mandrake 10 / > cooker ok. let me know if i can help in anyway. i think the above headers are recommending that the kernel's bitops not be used. not sure if that is viable. > what is your ISP ? (any link would be appreciated) i'm currently using streamyx in malaysia. their url is http://isp.tm.net.my/ --- Patrice Dumas wrote: > > Stack pointer is garbage, not printing trace > I see also that and I reported it, sleeper is working on that. It > shouldn't be problematic. Ok. Let me know if there is anything I can help do to debug that problem. Maybe I should rebuild the kernel with frame pointer support so that I can give you a stack trace. But it seems very odd that the failure is associated with wait_ms. ----- Ok. So I've been testing a little bit more and have made some progress. As you pointed out, after the Badness in wait_ms, the modem does eventually become operational. I agree that this is now also true for me. ===== Jun 21 21:03:45 j kernel: [eagle-usb] ioctl EU_IO_DSP received Jun 21 21:03:45 j kernel: [eagle-usb] Loading DSP code to device... Jun 21 21:03:45 j kernel: [eagle-usb] DSP code successfully loaded to device Jun 21 21:03:52 j kernel: longhaul: FSB:133 Mult:4.0x Jun 21 21:04:08 j kernel: [eagle-usb] Modem operational !! Jun 21 21:04:08 j kernel: [eagle-usb] Ethernet device eth1 created. ===== So this part looked good. The next part had to do with the fctStartAdsl script, it references /usr/local/sbin/pppoe which on fc2 doesn't exist. rather it is /sbin/pppoe. i see that the configure.in supplied does check for /sbin/pppoe but fctStartAdsl makes the assumption it is in /usr/local/sbin. So I symlinked to /sbin/pppoe. btw, I'm using ppp-2.4.2 and rp-pppoe-3.5-14 as comes with fc2. After setting up my ppp configs using eagleconfig, I attempted to establish a session. But I wasn't able to get the pppoe session established. Specifically, I see that pppd repeatedly complains about timeouts sending the config request. [log below] i noticed that the pppoe and pppox kernel modules weren't loaded in lsmod. so i manually modprobed them to make sure that wasn't the cause. i'm not familiar with how rp-pppoe and the pppoe kernel module interact. so i also tested with the modules never loaded. the results were the same. Based on eaglestat, I presume that the modem's training and signaling works since eaglestat reports the expected 384/128 speed. if i understand correctly, pppd forms the LCP config request and passes it to pppoe which then encapsulates it and sends it on the line right? so a timeout wating for the LCP config request response would indicate that either we are failing to send out the LCP config request to pppoe or that the isp is not responding. i confirmed that it's not the isp not responding because i was able to test right after using the same modem and windows xp to establish a valid session. i also see pppoe reporting timeout waiting for PADO, and tcpdump on the eth1 interface show that we are forming and sending broadcast PADI frames. logs and diags output follow: Jun 21 21:07:15 j pppd[4131]: pppd 2.4.2 started by root, uid 0 Jun 21 21:07:15 j pppd[4131]: Serial connection established. Jun 21 21:07:15 j pppd[4131]: Using interface ppp0 Jun 21 21:07:15 j pppd[4131]: Connect: ppp0 <--> /dev/pts/0 Jun 21 21:07:46 j pppd[4131]: LCP: timeout sending Config-Requests Jun 21 21:07:46 j pppd[4131]: Connection terminated. Jun 21 21:07:50 j pppoe[4132]: Timeout waiting for PADO packets Jun 21 21:07:51 j pppd[4131]: Serial connection established. Jun 21 21:07:52 j pppd[4131]: Using interface ppp0 Jun 21 21:07:52 j pppd[4131]: Connect: ppp0 <--> /dev/pts/1 Jun 21 21:08:23 j pppd[4131]: LCP: timeout sending Config-Requests Jun 21 21:08:23 j pppd[4131]: Connection terminated. Jun 21 21:08:27 j pppoe[4178]: Timeout waiting for PADO packets Jun 21 21:08:28 j pppd[4131]: Serial connection established. ========== eagle-usb status display ------------------------------------------------------------- Driver version 2 USB Bus : 002 USB Device : 003 Dbg mask: 0x0 Ethernet Interface : eth1 MAC: 00:05:5d:99:5b:15 Tx Rate 0000000128 Rx Rate 0000000384 Crc 0000000000 FEC 0000000000 Margin 0000000018 Atten 0000000038 dB VID-CPE 0000000000 VID-CO 0000000028 HEC 0000000000 VPI 0000000000 VCI 0000000053 Delin GOOD Cells Rx 0000000000 Cells Tx 0000000028 Pkts Rx 0000000000 Pkts Tx 0000000022 OAM 0000000000 Bad VPI 0000000000 Bad CRC 0000000000 Oversiz. 0000000000 Modem is operational ====================== Diagnostic (v1.6 20040504) driver eagle-usb 20040621211048 # System Information Linux j 2.6.6-1.383custom #2 Fri Jun 18 22:55:10 MYT 2004 i686 i686 i386 GNU/ Linux Fedora Core release 2 (Tettnang) Linux version 2.6.6-1.383custom ([EMAIL PROTECTED]) (gcc version 3.3.3 20040412 (Red Hat Linux 3.3.3-7)) #2 Fri Jun 18 22:55:10 MYT 2004 gcc version 3.3.3 20040412 (Red Hat Linux 3.3.3-7) # module loaded ? [ OK ] # modem operational ? [ OK ] # Config eagle-usb : vpi/vci/encapsulation 0 35 1 # pppd launched ? [ OK ] # Service for connection [ OK ] # ping IP ? [ KO ] # test DNS resolution ? [ KO ] Complete diagnostic has been saved on /var/log/eagle-usb/eagle_diag_200406212110 48.txt Please keep only relevant data and remove personal informations. __________________________________ Do you Yahoo!? Yahoo! Mail - Helps protect you from nasty viruses. http://promotions.yahoo.com/new_mail
