It’s very possible the kernel upgrade used some feature of the chipset that was buggy and resolved in a later release.
On Wed, 18 May 2022 at 14:58, Ken Smith via GLLUG <[email protected]> wrote: > > Chris Bell wrote: > > On Sunday, 15 May 2022 17:32:50 BST you wrote: > >> Chris Bell via GLLUG wrote: > >>> On Sunday, 15 May 2022 13:37:10 BST Ken Smith via GLLUG wrote: > >>>> Any pearls of wisdom either about my question or about recovering a > >>>> miscreant ML350 motherboard that won't boot anything or go into the > >>>> setup pages. > >>>> > >>>> Thanks > >>>> > >>>> Ken > >>> Hello Ken, > >>> I had a very lightly loaded ML150 running last year when suddenly it > >>> totally stopped > >> Did yours recover? > > No permanent damage, it was just the same as an ordinary re-start > After finding how to engage the secondary BIOS, I reflashed the primary > BIOS and the machine has been running the 5.4 Kernel for over 24 hours > now. I don't think the mysterious crash was to do with the 5.4 Kernel > after all. > > Motherboard saved from the recyclers! > > Ken > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > > -- > GLLUG mailing list > [email protected] > https://mailman.lug.org.uk/mailman/listinfo/gllug >
-- GLLUG mailing list [email protected] https://mailman.lug.org.uk/mailman/listinfo/gllug
