Re: 2.6.11-rc5 and 2.6.12: cannot transmit anything - more info

2005-08-07 Thread Denis Vlasenko
On Thursday 04 August 2005 23:45, Tommy Christensen wrote: > Denis Vlasenko wrote: > > Hi, > > > > As reported earlier, sometimes my home box don't want > > to send anything. > > > > # ip r > > 1.1.5.5 dev tun0 proto kernel scope link src 1.1.5.6 > > 1.1.4.0/24 dev if proto kernel scope link

Re: 2.6.11-rc5 and 2.6.12: cannot transmit anything - more info

2005-08-04 Thread Tommy Christensen
Denis Vlasenko wrote: Hi, As reported earlier, sometimes my home box don't want to send anything. # ip r 1.1.5.5 dev tun0 proto kernel scope link src 1.1.5.6 1.1.4.0/24 dev if proto kernel scope link src 1.1.4.6 default via 1.1.5.5 dev tun0 # ping 1.1.4.1 -i 0.01 2005-08-02_19:12:18.19

2.6.11-rc5 and 2.6.12: cannot transmit anything - more info

2005-08-02 Thread Denis Vlasenko
Hi, As reported earlier, sometimes my home box don't want to send anything. # ip r 1.1.5.5 dev tun0 proto kernel scope link src 1.1.5.6 1.1.4.0/24 dev if proto kernel scope link src 1.1.4.6 default via 1.1.5.5 dev tun0 # ping 1.1.4.1 -i 0.01 kernel log: 2005-07-30_21:28:25.15338 kern.info:

Re: 2.6.11-rc5 and 2.6.12: cannot transmit anything

2005-07-31 Thread Denis Vlasenko
On Monday 25 July 2005 08:17, Denis Vlasenko wrote: > I reported earlied that around linux-2.6.11-rc5 my home box sometimes > does not want to send anything over ethernet. That report is repeated below > sig. > > I finally managed to nail down where this happens. > I instrumented sch_generic.c to

Re: 2.6.11-rc5 and 2.6.12: cannot transmit anything

2005-07-25 Thread Denis Vlasenko
On Monday 25 July 2005 08:28, David S. Miller wrote: > > Probably your link is never coming up. We won't send packets > over the wire unless the device is in the link-up state. > > However, if ->dequeue() is returning NULL, there really aren't > any packets in the device queue to be sent. > > If y

Re: 2.6.11-rc5 and 2.6.12: cannot transmit anything

2005-07-24 Thread David S. Miller
Probably your link is never coming up. We won't send packets over the wire unless the device is in the link-up state. However, if ->dequeue() is returning NULL, there really aren't any packets in the device queue to be sent. If you want, add more tracing to pfifo_fast_dequeue() since that's alm

2.6.11-rc5 and 2.6.12: cannot transmit anything

2005-07-24 Thread Denis Vlasenko
[resend. Did not reach mailing lists, most probably due to KMail's unstoppable desire to use base64 encoding :)] Hi folks, I reported earlied that around linux-2.6.11-rc5 my home box sometimes does not want to send anything over ethetnet. That report is repeated below sig. I finally managed to n