[Bug 1740316] Re: EDAC sbridge: Failed to register device with error -19

2018-03-10 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740316 T

[Bug 1740316] Re: EDAC sbridge: Failed to register device with error -19

2018-01-09 Thread Fawzi Masri
hi guys, any change on this front?bug is still incomplete even though i provided what you wanted. please let me know if you still need anything... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740316

[Bug 1740316] Re: EDAC sbridge: Failed to register device with error -19

2018-01-04 Thread Fawzi Masri
one more observation with 4.15. it does hang on shutdown. if i do shutdown -h now or shutdown -r now, the system does not reboot. it stops at [ ok ] Reached target shutdown. At which time my server fans kicks in like mad, so i manually cold boot it but i never waited for it more than 5 min.

[Bug 1740316] Re: EDAC sbridge: Failed to register device with error -19

2018-01-04 Thread Fawzi Masri
one question, which version should i be using , -generic or -lowlatency? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740316 Title: EDAC sbridge: Failed to register device with error -19 To manag

[Bug 1740316] Re: EDAC sbridge: Failed to register device with error -19

2018-01-04 Thread Fawzi Masri
'kernel-fixed-upstream' To answer your questions: 1- I noticed this error after i upgraded from Ubuntu 17.04 to 17.10... namely because my server did not boot properly. The reason for it not booting properly was not related to this, as i later found out so i cannot guarantee that this error

[Bug 1740316] Re: EDAC sbridge: Failed to register device with error -19

2018-01-02 Thread Joseph Salisbury
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[