OK will try fedora if I get a chance over the weekend. Sorry I dont have an answer on your wifi side. My machine is a server class running multiple VMs. Connection is via GB LAN and I've overridden all the network autoconfig stuff to force a static IP - its the DHCP server for my internal network too.
Completely agree that we need to get this escalated.
IMO all the panics we are seeing in related threads could be the same cause. Depending on which kernel version I'm using it either panics during boot or shortly afterwards. I think there is a thermal / ACPI component to the behavior though this is only a gut feel. Have poured over log files and there is nothing deterministric about the panics on my system other than perhaps general CPU load.
38-8 gives me various [Hardware Error] during early kernel load. 38-10 doesnt but still panics.
Agree with you that this seems like a kernel error (or at least closely releated eg module). I think many people are chasing their tails based on some sort of threshold load pattern that has theirs panicing at a repeatable point thereby giving a false indication that the driver/code etc at that point is the problem. Whereas it is likley to be some ACPI / timing issue that happens to trigger at that load level. (does this make sense?)
If there are some of those dedicated developers reading this: I'm happy to take instruction in providing more information.
OK will try fedora if I get a chance over the weekend. Sorry I dont have an answer on your wifi side. My machine is a server class running multiple VMs. Connection is via GB LAN and I've overridden all the network autoconfig stuff to force a static IP - its the DHCP server for my internal network too.
Completely agree that we need to get this escalated.
IMO all the panics we are seeing in related threads could be the same cause. Depending on which kernel version I'm using it either panics during boot or shortly afterwards. I think there is a thermal / ACPI component to the behavior though this is only a gut feel. Have poured over log files and there is nothing deterministric about the panics on my system other than perhaps general CPU load.
38-8 gives me various [Hardware Error] during early kernel load. 38-10 doesnt but still panics.
Agree with you that this seems like a kernel error (or at least closely releated eg module). I think many people are chasing their tails based on some sort of threshold load pattern that has theirs panicing at a repeatable point thereby giving a false indication that the driver/code etc at that point is the problem. Whereas it is likley to be some ACPI / timing issue that happens to trigger at that load level. (does this make sense?)
If there are some of those dedicated developers reading this: I'm happy to take instruction in providing more information.
Cheers
Brendan