Re: ether_ifattach() issue

2000-08-06 Thread Neil Blakey-Milner
On Sun 2000-08-06 (13:28), Archie Cobbs wrote: > > > No interface should be attached twice, Ethernet or other, right? > > > So try this patch and find out which driver is broken. > > > > I think the concern was because the semantics to attach devices changed, > > meaning that drivers from before

Re: ether_ifattach() issue

2000-08-06 Thread Archie Cobbs
Neil Blakey-Milner writes: > > No interface should be attached twice, Ethernet or other, right? > > So try this patch and find out which driver is broken. > > I think the concern was because the semantics to attach devices changed, > meaning that drivers from before no longer work. Hmm.. my unde

Re: ether_ifattach() issue

2000-08-06 Thread Neil Blakey-Milner
On Sun 2000-08-06 (12:44), Archie Cobbs wrote: > No interface should be attached twice, Ethernet or other, right? > So try this patch and find out which driver is broken. I think the concern was because the semantics to attach devices changed, meaning that drivers from before no longer work. Nei

Re: ether_ifattach() issue

2000-08-06 Thread Archie Cobbs
Dennis writes: > The change in 4.1 to ether_ifattach() needs a check to see if the device is > already attached. > > calling ether_ifattch() with a device already attached will lock up the > system consistently. No interface should be attached twice, Ethernet or other, right? So try this patch a

ether_ifattach() issue

2000-08-05 Thread Dennis
The change in 4.1 to ether_ifattach() needs a check to see if the device is already attached. calling ether_ifattch() with a device already attached will lock up the system consistently. Dennis To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of th