[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Ethernet fails after package upgrades (was:Kernels does not assign irq to eth0)



Sorry for the noise. The problem was found in the ifupdown package,
version 0.7~alpha2 from experimental is buggy. Replacing it with 0.6.8
from unstable/testing/stable solves my problem. I will file a bug report
on this package with hight severity. Using packages from experimental is
sometimes risky! Now I have two ethernet cards for this box, the old one
works perfectly :)
 
On Fri, 2007-06-29 at 11:23 +0200, Svante Signell wrote:
> New input again: Suddenly both cards are allocated interrupts and
> recognized as eth0, and eth1. Trying to bring up either interfaces give
> the same output:
> RTNETLINK anwers: File exists
> Failed to bring up "eth0" or
> Failed to bring up "eth01"
> What's going on here??
> Do I have a hardware problem somewhere on the motherboard??
> 
> Googling a little seems to indicate that the RTNETLINK message comes
> from the kernel, right?
> 
> On Fri, 2007-06-29 at 10:55 +0200, Svante Signell wrote:
> > I think the problem might be related to IRQ and ACPI. 
> > Attached is a boot log from a succesful boot, _before_ the upgrade.
> > If you need the boot log from the broken box, I have to copy it via a
> > floppy or something. Please let me know.
> > 
> > I have now tried with bot network cards: The old one, 3c59x-based, gets
> > an IRQ assigned, but does not work as written before:
> > RTNETLINK anwers: File exists
> > Failed to bring up "eth0"
> > while the other one, 8139too-based, is not assigned an IRQ and gives the
> > following eoutput:
> > Cannot find device "eth0"
> > Failed to bring up "eth0"
> >  
> > On Fri, 2007-06-29 at 10:21 +0200, Svante Signell wrote:
> > > Hi,
> > > 
> > > Sorry to disturb you on this list, but I need some help and will not
> > > file a bug report yet and don't know where to get help. After recent
> > > upgrades on unstable+experimental ethernet does not work any longer. I
> > > have been using a 3com card for a long time and after the upgrade it
> > > suddenly doesn't work any longer. Module loaded is 3c59x.ko. Kernels
> > > 2.6.18-3-686, 2.6.18-4-686, 2.6-20-1-686, 2.6.21-686. Whem tring to
> > > bring up the interface I get the following output:
> > > RTNETLINK anwers: File exists/No such process/Network is unreachable.
> > > 
> > > Buying a new network card and loading the 8138too.ko module this card is
> > > detected as eth0 according to the kernel logs and assigned, e.g IRQ 17.
> > > However, when looking at /proc/interrupts the assigned interupt does not
> > > show :( When tring to bring up the interface the output is:
> > > Cannot find device "eth0"
> > > Failed to bring up "eth0"
> > > 
> > > I have tried to move the crd to another PCI slot, but no avail.
> > > According to dmesg there are problems with IRQ assignments, and one of
> > > the IRQs are disabled for some reasons. Have tried booting with
> > > pci=routeirq without any difference and usnig irqpoll oprion hangs the
> > > boot! The computer is a  Dual CPU Celeron box, having been running for a
> > > long time now. I had recent problems installing the latest
> > > module-init-tools-3.3-pre-3, and backed to 3.3pere-1 and reinstalled
> > > modutils. Does this have abything to do with the problems seen?
> > > Which upgrades does affect the ethernet functionality, the kernels were
> > > _not_ upgraded with the latest upgrade!
> > > 
> > > Please Cc: me since I'm not subscribed.
> > > 
> > > Thanks,
> > > Svante



Reply to: