Port-xen archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: NetBSD/xen network problems (need help)
On Fri, 27 Jan 2006 10:01:44 +0200
"Mike M. Volokhov" <mishka%intostroy.com@localhost> wrote:
> On Thu, 26 Jan 2006 20:00:11 +0100
> Manuel Bouyer <bouyer%antioche.eu.org@localhost> wrote:
>
> > On Thu, Jan 26, 2006 at 05:24:54PM +0200, Mike M. Volokhov wrote:
> > > > Here's a new patch which adds more debug printf.
> > >
> > > Kernel panic message:
> > >
> > > pa 0x5fd5f38 len 200 m_flags 0x2
> > > new_m 0xc06bbf00 m_paddr 5fd5f00 M_BUFOFFSET 56
> >
> > Hey, of course ! 200 + 56 = 256 = 0x100. The KASSERT is wrong, it should
> > use m_pkthdr.len - 1.
> >
> > Attached is a new patch for if_xennet.c, with this fixed (but still the
> > additionnal debug printfs, just in case).
> >
>
> Rebuilt, installed, testing now. If there are will be no hangs nor
> panics during nearest few hours, I'll report my results in Monday.
Ok, seems that so far all works like a charm! After 3.5 days uptime:
Name Ipkts Ierrs Opkts Oerrs Colls
bge0 859769 0 507937 0 0
bge1 165085 0 182095 0 0
lo0 272 0 272 0 0
bridge0 1369041 0 2633409 0 0
bridge1 347173 0 347175 0 0
xvif1.0 135838 0 548652 0 0
xvif2.0 167261 0 556786 0 0
xvif2.1 182088 0 165083 0 0
xvif3.0 200724 0 593828 0 0
xvif4.0 6043 0 426210 0 0
BTW, it would be nice to see that patches commited into the -current
and to the 3.x branches...
--
Sincerely yours,
Mishka.
Home |
Main Index |
Thread Index |
Old Index