Further investigation of the issue has brought me to the conclusion that 
changing power source during high network traffic whilst connected to a network 
using ethernet causes a crash. It is my opinion that this problem is probably 
the e1000e ethernet driver.
Below is an extract from syslog which from what I can tell has logged the 
effects of changing power source but not the actual crash. But it may be useful!

Dec  7 15:11:37 JustAComp kernel: [   65.948734] CPU0 attaching NULL 
sched-domain.
Dec  7 15:11:37 JustAComp kernel: [   65.948747] CPU1 attaching NULL 
sched-domain.
Dec  7 15:11:37 JustAComp kernel: [   65.960135] CPU0 attaching sched-domain:
Dec  7 15:11:37 JustAComp kernel: [   65.960143]  domain 0: span 0-1 level MC
Dec  7 15:11:37 JustAComp kernel: [   65.960146]   groups: 0 1
Dec  7 15:11:37 JustAComp kernel: [   65.960152] CPU1 attaching sched-domain:
Dec  7 15:11:37 JustAComp kernel: [   65.960155]  domain 0: span 0-1 level MC
Dec  7 15:11:37 JustAComp kernel: [   65.960157]   groups: 1 0
Dec  7 15:12:28 JustAComp kernel: [  117.542150] CPU0 attaching NULL 
sched-domain.
Dec  7 15:12:28 JustAComp kernel: [  117.542168] CPU1 attaching NULL 
sched-domain.
Dec  7 15:12:29 JustAComp kernel: [  117.569134] CPU0 attaching sched-domain:
Dec  7 15:12:29 JustAComp kernel: [  117.569146]  domain 0: span 0-1 level MC
Dec  7 15:12:29 JustAComp kernel: [  117.569152]   groups: 0 1
Dec  7 15:12:29 JustAComp kernel: [  117.569161]   domain 1: span 0-1 level CPU
Dec  7 15:12:29 JustAComp kernel: [  117.569166]    groups: 0-1
Dec  7 15:12:29 JustAComp kernel: [  117.569175] CPU1 attaching sched-domain:
Dec  7 15:12:29 JustAComp kernel: [  117.569179]  domain 0: span 0-1 level MC
Dec  7 15:12:29 JustAComp kernel: [  117.569184]   groups: 1 0
Dec  7 15:12:29 JustAComp kernel: [  117.569191]   domain 1: span 0-1 level CPU
Dec  7 15:12:29 JustAComp kernel: [  117.569196]    groups: 0-1

-- 
Kernel Panic - High Volume Network Traffic using e1000e Intel Gigabit Ethernet
https://bugs.launchpad.net/bugs/304428
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to