Re: Boot issue with e1000 netdde driver
On Sun, 2020-11-29 at 20:31 +0100, Samuel Thibault wrote: > Svante Signell, le dim. 29 nov. 2020 18:01:51 +0100, a ecrit: > > On Sun, 2020-11-29 at 14:37 +0100, Samuel Thibault wrote: > > > Richard Braun, le dim. 29 nov. 2020 14:09:56 +0100, a ecrit: > > > > Actually, with the e1000 driver, very often, network is not > > > > functional at boot time and I have to manually kill netdde and > > > > trigger some activity > > > Oh? > > > > > > I'm surprised, I never experience this on my box. > > > > I do see it too. Network is functional after a loong time and/or > > after a reboot. > > Has it always been so? No, since the last 1-2 weeks or so.
Re: Boot issue with e1000 netdde driver
Svante Signell, le dim. 29 nov. 2020 18:01:51 +0100, a ecrit: > On Sun, 2020-11-29 at 14:37 +0100, Samuel Thibault wrote: > > Richard Braun, le dim. 29 nov. 2020 14:09:56 +0100, a ecrit: > > > > > > Actually, with the e1000 driver, very often, network is not > > > functional at boot time and I have to manually kill netdde and > > > trigger some activity > > Oh? > > > > I'm surprised, I never experience this on my box. > > I do see it too. Network is functional after a loong time and/or after > a rebbot. And this: see attached. I rump default already? It's not default, but it is now configured by default on /dev/rumpdisk, for the case when disks are not detected by gnumach. Samuel
Re: Boot issue with e1000 netdde driver
On Sun, 2020-11-29 at 14:37 +0100, Samuel Thibault wrote: > Richard Braun, le dim. 29 nov. 2020 14:09:56 +0100, a ecrit: > > > > Actually, with the e1000 driver, very often, network is not > > functional at boot time and I have to manually kill netdde and > > trigger some activity > Oh? > > I'm surprised, I never experience this on my box. I do see it too. Network is functional after a loong time and/or after a rebbot. And this: see attached. I rump default already? Thanks!
Re: Boot issue with e1000 netdde driver
Richard Braun, le dim. 29 nov. 2020 14:09:56 +0100, a ecrit: > On Tue, Sep 22, 2020 at 01:28:42PM +0200, Richard Braun wrote: > > On Fri, Aug 28, 2020 at 06:39:29PM +0200, Samuel Thibault wrote: > > > One way to avoid the bug is to use the e1000 hardware network type. I > > > guess the rtl8139 driver that we ship in netdde has a bug in its irq > > > handling (we had already seen that kind of bug a long time ago in the > > > IDE driver). Moving to rump-based network drivers will probably help > > > fixing this kind of issue long-term :) > > > > It does seem to help. Thanks. > > > > For information, the virtual machines were using the pcnet device, > > not the rtl8139 one. > > Actually, with the e1000 driver, very often, network is not functional > at boot time and I have to manually kill netdde and trigger some activity > for it to work. Oh? I'm surprised, I never experience this on my box. Samuel
Boot issue with e1000 netdde driver
On Tue, Sep 22, 2020 at 01:28:42PM +0200, Richard Braun wrote: > On Fri, Aug 28, 2020 at 06:39:29PM +0200, Samuel Thibault wrote: > > One way to avoid the bug is to use the e1000 hardware network type. I > > guess the rtl8139 driver that we ship in netdde has a bug in its irq > > handling (we had already seen that kind of bug a long time ago in the > > IDE driver). Moving to rump-based network drivers will probably help > > fixing this kind of issue long-term :) > > It does seem to help. Thanks. > > For information, the virtual machines were using the pcnet device, > not the rtl8139 one. Actually, with the e1000 driver, very often, network is not functional at boot time and I have to manually kill netdde and trigger some activity for it to work. -- Richard Braun
