Jesper Juhl wrote:
Ok, I've done some more testing and it seems, unfortunately, that I
can't trigger the problem reliably. I guess I was just lucky with my
first few reboots.
It now seems that uptime and/or amount of data that has flowed over
the vlan interface impacts the probability of hitting
On 31/08/06, Jesper Juhl [EMAIL PROTECTED] wrote:
On 31/08/06, Ben Greear [EMAIL PROTECTED] wrote:
Jesper Juhl wrote:
Hi,
I've got a small problem with 2.6.18-rc5-git2.
I've got a vlan setup on eth0.20, eth0 does not have an IP.
When I attempt to reboot or halt the machine I get
Jesper Juhl [EMAIL PROTECTED] wrote:
I've just encountered the problem on a different server with an
identical vlan setup. That server is running 2.6.13.4
Do you have a simple recipe to reproduce this? Ideally it'd be a
script that anyone can execute in a freshly booted system that
exhibits
On 01/09/06, Herbert Xu [EMAIL PROTECTED] wrote:
Jesper Juhl [EMAIL PROTECTED] wrote:
I've just encountered the problem on a different server with an
identical vlan setup. That server is running 2.6.13.4
Do you have a simple recipe to reproduce this? Ideally it'd be a
script that anyone can
On 01/09/06, Jesper Juhl [EMAIL PROTECTED] wrote:
On 01/09/06, Herbert Xu [EMAIL PROTECTED] wrote:
Jesper Juhl [EMAIL PROTECTED] wrote:
I've just encountered the problem on a different server with an
identical vlan setup. That server is running 2.6.13.4
Do you have a simple recipe to
Jesper Juhl wrote:
Hi,
I've got a small problem with 2.6.18-rc5-git2.
I've got a vlan setup on eth0.20, eth0 does not have an IP.
When I attempt to reboot or halt the machine I get the following
message from the loop in net/core/dev.c::netdev_wait_allrefs() where
it waits for the ref-count to
On 31/08/06, Ben Greear [EMAIL PROTECTED] wrote:
Jesper Juhl wrote:
Hi,
I've got a small problem with 2.6.18-rc5-git2.
I've got a vlan setup on eth0.20, eth0 does not have an IP.
When I attempt to reboot or halt the machine I get the following
message from the loop in
