[coreboot] coreboot Digest, Vol 106, Issue 12

Christopher Lang christopherlang1 at gmail.com
Mon Dec 9 14:54:40 CET 2013


Hi Peter, I will try a debug kernel set to panic on an oops. Hopefully I
can get some better diagnostics.

Thanks,

Chris


On Mon, Dec 9, 2013 at 5:00 AM, <coreboot-request at coreboot.org> wrote:

> Send coreboot mailing list submissions to
>         coreboot at coreboot.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://www.coreboot.org/mailman/listinfo/coreboot
> or, via email, send a message with subject or body 'help' to
>         coreboot-request at coreboot.org
>
> You can reach the person managing the list at
>         coreboot-owner at coreboot.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of coreboot digest..."
>
>
> Today's Topics:
>
>    1. Re: [Bug 66261] Kernel oops upon reboot from suspend      -
>       Flashed Acer C7 using coreboot (Peter Stuge)
>    2. Re: Request to see if Coreboot will work for a Gigabyte BRIX
>       GB-XM14-1037 (Gerd Hoffmann)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 8 Dec 2013 18:15:53 +0100
> From: Peter Stuge <peter at stuge.se>
> To: coreboot at coreboot.org
> Subject: Re: [coreboot] [Bug 66261] Kernel oops upon reboot from
>         suspend -       Flashed Acer C7 using coreboot
> Message-ID: <20131208171553.23607.qmail at stuge.se>
> Content-Type: text/plain; charset=us-ascii
>
> Christopher Lang wrote:
> > upon resume the kernel oops. The hardware is an Acer C7 Parrot
> > board. I have attached the kernel config, coreboot config and
> > the kernel oops message log.
>
> There's no actual kernel log. That log is unfortunately some
> uninformative ubuntu thing.
>
> You'll need a way to capture the kernel log when resuming.
>
> That may involve a USB debug device or otherwise some hardware
> development and soldering.
>
>
> //Peter
>
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 09 Dec 2013 08:36:23 +0100
> From: Gerd Hoffmann <kraxel at redhat.com>
> To: Patrick Georgi <patrick at georgi-clan.de>
> Cc: Jeremy White <jwhite at codeweavers.com>, coreboot at coreboot.org
> Subject: Re: [coreboot] Request to see if Coreboot will work for a
>         Gigabyte BRIX GB-XM14-1037
> Message-ID: <1386574583.8684.14.camel at nilsson.home.kraxel.org>
> Content-Type: text/plain; charset="UTF-8"
>
> On Sa, 2013-12-07 at 09:54 +0100, Patrick Georgi wrote:
> > Am Freitag, den 06.12.2013, 20:05 -0600 schrieb Jeremy White:
> > > If I were to change the second paragraph as follows:
> > >
> > >   If your board is not already supported, it will likely take
> > >   you years of work to port coreboot to operate correctly on it.
> >    "unless you have experience with firmware level C development and
> >     good knowledge of the x86 architecture."
>
> "But then you probably wouldn't read this FAQ but the code to figure
> what the support status is ;)"
>
> cheers,
>   Gerd
>
>
>
>
>
> ------------------------------
>
> _______________________________________________
> coreboot mailing list
> coreboot at coreboot.org
> http://www.coreboot.org/mailman/listinfo/coreboot
>
> End of coreboot Digest, Vol 106, Issue 12
> *****************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20131209/ab40b4ff/attachment.html>


More information about the coreboot mailing list