On Wed, 2005-08-31 at 14:09 +0200, Antonio Montagnani wrote:
Bob Chiodini said the following on 31/08/2005 12:53:
On Wed, 2005-08-31 at 11:47 +0200, Antonio Montagnani wrote:
Bob Chiodini said the following on 31/08/2005 11:33:
On Wed, 2005-08-31 at 07:52 +0200, Antonio Montagnani wrote:
Edward Dekkers said the following on 31/08/2005 06:26:
Antonio Montagnani wrote:
>Antonio Montagnani said the following on 30/08/2005 09:16: > > > >>Edward Dekkers said the following on 30/08/2005 09:06: >> >> >> >>>Antonio Montagnani wrote: >>> >>> >>> >>>>I cannot connect to my ADSL Internet if I use SMP kernel, while >>>>with standard 2.6.12-1.1376 kernel on same machine, it works >>>>flawlessly. >>>>The modem works, Ethernet network is on but connection is refused >>>>Shall I file a bug?? >>> >>> >>> >>> >>> >>>No, >>> >>>There is no real difference between running a standard kernel or an >>>SMP one. Bar the fact that SMP will actually use the two processors >>>in your machine that is. I run SMP myself, and it makes no >>>difference to my connection running standard or SMP kernel. >>> >>>I'd look at doing some other diagnostic work before filing a report. >>> >>>We can't help you for the rest because you don't explain your set up. >>> >>>Regards, >>>Ed. >>> >> >>My setup is very standard, a Pentium 4 Asus motherboard P5P800, 1 GB, >>two network cards (the integrated is connected to my network, the >>Realtek 8029 to my ethernet modem). >>Which diagnostic shall I check?? >> > >upgraded to FC4, same behaviour also with 2.6.12-1.447smp > >where to look??? >
Number one would be to see if the Realtek interface actually comes up - then there's a whole slew of tools like ifconfig, ping, iptraf, dhclient etc. to be used one by one to see where the problem lies.
When I asked you to provide more details, I wasn't really after motherboard and stuff like that, I was after your internet connection details of course. This is how I would describe one for example:
Maestro Woomera Serial modem connected to /dev/ttyS0 Using pppd on demand/wvdial to make a connection The IP address on that interface (ppp0) is assigned dynamically by my isp. The log shows dialling to be ok, and pppd taking over the connection once wvdial has established it. ifconfig shows an IP allocated to me ip address: 203.0.178.191 with netmask 255.255.255.0. I can ping internal addresses and external ones by name (www.microsoft.com) and number (207.46.199.60).
This is in the case of dial-up. Your trace will be different.
Really, you have provided nothing of use in diagnosing this problem. I'm assuming your modem takes care of the connection and just gives you an internal IP address which you set to the gateway? or do you need to run PPPoE or some other protocol manually?
You must assume we know nothing about your set-up when posting to this list.
Regards, Ed.
Ed,
it seems that I can't ping the Ethernet modem when using SMP kernel(destination unreachable), if I connet to ist internal webpage I get a message of no routing. I have iptables running: and everything is o.k on standard kernel!!! What is happening???
-- Antonio
Anything relevant in /var/log/messages? What is the output of route -n?
Bob...
I had a look at /var/log/messages (that I attach, only as e-mail to you...), but I am not very expert. I see a timeout transmit on eth0 repeated many times when using SMP kernel at about 6.35 at the end. I see also many errors conencted to ACPI (on both kernels) that I am not able to decode
Tnx
Antonio,
I culled the messages down into a SMP boot and a UP boot. A quick look indicates one message is missing in the SMP boot log. It's marked with an arrow and indicates that the eth0 device interrupt was detected as IRQ 11 (UP only). Hopefully someone can shed some light on this. Some other information that might help:
cat /proc/interrupts for both the UP and SMP.
Also, do you have the latest BIOS installed for your motherboard? What kind of motherboard is this?
An Asus P5P800, Bios updated in July
Check the IO-APIC options in the BIOS
setup.
You might try moving the realtek NIC to another slot. That's a shot in the dark, but it's pretty early and I'm only into my first cup of coffee!
Bob...
Standard CPU00: 20180445 XT-PIC timer 1: 5563 XT-PIC i8042 2: 0 XT-PIC cascade 5: 701131 XT-PIC SysKonnect SK-98xx, Intel ICH5, ehci_hcd:usb1, uhci_hcd:usb3 8: 1 XT-PIC rtc 11: 380784 XT-PIC uhci_hcd:usb2, uhci_hcd:usb4, uhci_hcd:usb5, eth0 12: 801086 XT-PIC i8042 14: 112972 XT-PIC ide0 15: 358109 XT-PIC ide1 NMI: 0 ERR: 0
SMP CPU0 CPU1 0: 137004 48896 IO-APIC-edge timer 1: 29 27 IO-APIC-edge i8042 5: 0 0 IO-APIC-edge SysKonnect SK-98xx, Intel ICH5, ehci _hcd:usb1, uhci_hcd:usb3 8: 1 0 IO-APIC-edge rtc 11: 0 0 IO-APIC-edge uhci_hcd:usb2, uhci_hcd:usb4, uhci_h cd:usb5, eth0 12: 1146 836 IO-APIC-edge i8042 14: 9294 5957 IO-APIC-edge ide0 15: 440 568 IO-APIC-edge ide1 NMI: 0 0 LOC: 181971 182055 ERR: 0 MIS: 0
I am wondering if the two kernels have different management of iptables, in particular IPv4 or IPv6, another shot in the dark, even if is afternoon here
tnx
Antonio,
service iptables stop. I suspect that the IRQ for eth0 is not getting properly registered and thus the timeouts.
Does specifying acpi=ht on the SMP kernel command line make any difference? It probably defeats the purpose of SMP.
Bob...