On 8 Mar 2008, at 19:57, Jarek Poplawski wrote:No, eth0 is the one driven by e100 driver. The card itself is probably ten years old. So it's old but it has always been a reliable work horse for me :) eth1 is embedded on the Intel motherboard. It's brand new and it's driven by e1000e driver. I'm not sure which interface's interrupts are giving these oopses. The machine was booted two days ago, and after that, still no oopses, though net traffic has been quite light. Should there be new oopses, I will replace the old card with a newer Intel gigabit card that I have laying around, and put it in a different PCI slot. Ok, thanks for the info. I'll try that if changing the card doesn't help. -- Tuomas Jormola <tj@solitudo.net> -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
| Greg Kroah-Hartman | [PATCH 005/196] Chinese: add translation of SubmittingDrivers |
| Paul Jackson | Re: cpuset-remove-sched-domain-hooks-from-cpusets |
| Oleg Verych | Re: [PATCH] trivial: the memset operation on a automatic array variable should be ... |
git: | |
| Larry McVoy | Re: tcp bw in 2.6 |
| David Miller | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
