On Mon, Jul 27, 2009 at 6:46 PM, Richard Cahilig<r.cahilig@xxxxxxxxx> wrote: > That's not the only problem I have, I also have this kernel error. > >> WARNING: at arch/x86/kernel/cpu/mtrr/generic.c:407 >> generic_get_mtrr+0xc8/0x105() (Not tainted) >> Hardware name: ProLiant ML115 G1 >> mtrr: your BIOS has set up an incorrect mask, fixing it up. >> Modules linked in: >> Pid: 0, comm: swapper Not tainted 2.6.29.6-213.fc11.x86_64 #1 >> Call Trace: >> [<ffffffff8104883f>] warn_slowpath+0xbc/0xf0 >> [<ffffffff810493ad>] ? vprintk+0x308/0x335 >> [<ffffffff813abf2c>] ? _spin_unlock_irqrestore+0x2c/0x42 >> [<ffffffff813abf2c>] ? _spin_unlock_irqrestore+0x2c/0x42 >> [<ffffffff8101e8b3>] generic_get_mtrr+0xc8/0x105 >> [<ffffffff81649aca>] mtrr_bp_init+0x222/0x59f >> [<ffffffff816533fb>] ? early_gart_iommu_check+0x8a/0x25b >> [<ffffffff8164540f>] setup_arch+0x41a/0x929 >> [<ffffffff813a9916>] ? printk+0x41/0x43 >> [<ffffffff810603a9>] ? raw_notifier_chain_register+0x9/0x2e >> [<ffffffff8163da83>] start_kernel+0x99/0x3cc >> [<ffffffff8163d2c1>] x86_64_start_reservations+0xac/0xb0 >> [<ffffffff8163d3ce>] x86_64_start_kernel+0xe6/0xf5 >> > > I don't know if this ssh error is related to this one. > > > On Mon, Jul 27, 2009 at 8:57 AM, Richard Cahilig <r.cahilig@xxxxxxxxx> > wrote: >> >> Yes, I can ping the destination server. I already disabled firewall and >> selinux on both servers. >> >> On Mon, Jul 27, 2009 at 1:52 AM, Sam Varshavchik <mrsam@xxxxxxxxxxxxxxx> >> wrote: >>> >>> Richard R. Cahilig writes: >>> >>>> Hello, >>>> >>>> >>>> I just installed fedora 11 64bit on our server, the problem is I cannot >>>> connect to other Linux server using "ssh" the error says "ssh: connect to >>>> host 83.229.64.51 port 22: No route to host". Its strange because I already >>>> disabled the firewall and the selinux on this server and I can connect to >>>> that other Linux server using different computer and the firewall and >>>> selinux on that server is also disabled. Please help me. >>> >>> Can you ping the destination server. If you can, it's a firewall issue. >>> If you cannot, you have a networking issue. >>> >>>83.229.64.51 you can use nmap to check if port 22 is accessable nmap -P0 83.229.64.51 -p22 >>> -- >>> fedora-list mailing list >>> fedora-list@xxxxxxxxxx >>> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list >>> Guidelines: >>> http://fedoraproject.org/wiki/Communicate/MailingListGuidelines >> >> >> >> -- >> Richard R. Cahilig >> http://www.cahilig.org >> http://www.aklan-linux.org >> > > > > -- > Richard R. Cahilig > http://www.cahilig.org > http://www.aklan-linux.org > > > -- > fedora-list mailing list > fedora-list@xxxxxxxxxx > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list > Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines > -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
