Re: iwn failure on -current (XEN3_DOM0)

I just upgraded my EliteBook laptop with -current from 18th of November. XEN3_DOM0 again timeouts on ehci in a loop taking about two minutes, after which it panics with a message about a recursive panic; no crash dump is generated. On the other hand my older XEN3_DOM0 from 8.99.5 continues to

Re: iwn failure on -current (XEN3_DOM0)

Thanks for the tip! On Sun, 19 Nov 2017 at 18:31, wrote: > On Sun, Nov 19, 2017 at 11:11:44AM +, Chavdar Ivanov wrote: > > Here my point was that iwn used to work under XEN3_DOM0 a few months > > ago and is not working now, which may indicate some problem or > > regression

Re: iwn failure on -current (XEN3_DOM0)

To be honest, I have always used it without many troubles on many machines and never checked that. By the way, on the same T61p I was doing the same test there is also a W10 partition, it runs as fast as it can on that hardware, but the driver is ancient and from time to time I am getting BSODs,

Re: iwn failure on -current (XEN3_DOM0)

ci4...@gmail.com (Chavdar Ivanov) writes: >Here my point was that iwn used to work under XEN3_DOM0 a few months >ago and is not working now, Hmm. iwn is working on bare metal for me. It should work on XEN3_DOM0. >which may indicate some problem or >regression elsewhere, which was the main

Re: iwn failure on -current (XEN3_DOM0)

On Sun, Nov 19, 2017 at 11:11:44AM +, Chavdar Ivanov wrote: > Here my point was that iwn used to work under XEN3_DOM0 a few months > ago and is not working now, which may indicate some problem or > regression elsewhere, which was the main reason for my question. 'Git bisect' is a good way to

Re: iwn failure on -current (XEN3_DOM0)

On 19 November 2017 at 08:01, Michael van Elst wrote: > ci4...@gmail.com (Chavdar Ivanov) writes: > >>I used to run DOM0 on xen4.8, the wireless interface worked for the >>DOM0, although I could never make the bridge work (it worked with the >>wired wm0, though). > > You

Re: iwn failure on -current (XEN3_DOM0)

ci4...@gmail.com (Chavdar Ivanov) writes: >I used to run DOM0 on xen4.8, the wireless interface worked for the >DOM0, although I could never make the bridge work (it worked with the >wired wm0, though). You cannot bridge via WiFi because this requires support to not only receive for arbitrary

iwn failure on -current (XEN3_DOM0)

Hi, This may belong to port-xen@ or elsewhere, but as it is ran on -current from today and the behaviour was different than a month or so ago, I am here. I used to run DOM0 on xen4.8, the wireless interface worked for the DOM0, although I could never make the bridge work (it worked with the