Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 27 Jun 2013 13:43:14 -0400
From:      Super Bisquit <superbisquit@gmail.com>
To:        Justin Hibbits <jhibbits@freebsd.org>
Cc:        FreeBSD PowerPC ML <freebsd-ppc@freebsd.org>
Subject:   Re: Strange panic on ppc64
Message-ID:  <CA%2BWntOvN1iG-WJS0JEepmsL5jk0iV5EuDCeeMrdfRUA7AKZauQ@mail.gmail.com>
In-Reply-To: <CAHSQbTAnzfq_AQ8yRdTbztCpnYjeKtWp3zayE7o1evzBasULbQ@mail.gmail.com>
References:  <CAHSQbTAZTc9puGaH0rbhyY11s0%2BL0xGjSabK1kj65UMm1t7j3w@mail.gmail.com> <51AF6661.3060007@freebsd.org> <CAHSQbTBjza0u7nZf4z%2BxpTCcWj-TW-ZigV2-CZexuBOYQX5=3A@mail.gmail.com> <CAHSQbTCvFXDZPsOnmogc0FkZeMXwOP6h40F2kFUu2s6UmffyPw@mail.gmail.com> <51B345BE.5030905@freebsd.org> <CAHSQbTDnwne3KJWN7xjcUw4PhF-uiD4B-4y1Lf90Bfou-2Ppvw@mail.gmail.com> <51B4A389.4020607@freebsd.org> <CAHSQbTACtejaRKiG4qScSV_EdTC8y_k5Qghx_FYebWzstBP61g@mail.gmail.com> <51B5D28C.505@freebsd.org> <51B5D539.8050102@freebsd.org> <CAHSQbTCposTE1AwHS0Ov=FT4w8gNkgpE4x_7-cHhyzMDfZr5UA@mail.gmail.com> <CAHSQbTB6bXpqFM5n8FMmpbbfKik0szDvp9M6KfCWreXKHTaR1g@mail.gmail.com> <CAJTQnqYaeBt690G0Nxv8gO1PpmTan3rXbARgTb-s63EEo_LiQQ@mail.gmail.com> <CAHSQbTAV19xUasD7v_gw5wcLGoVvefyP5F%2BUbiGeX1=raiVrig@mail.gmail.com> <CAHSQbTAnzfq_AQ8yRdTbztCpnYjeKtWp3zayE7o1evzBasULbQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Wouldn't the error be correctable in ofwcall64.S ?
Just asking.


On Thu, Jun 27, 2013 at 1:03 AM, Justin Hibbits <jhibbits@freebsd.org>wrote:

> >
> > On Jun 12, 2013 11:31 PM, "Justin Hibbits" <jhibbits@freebsd.org> wrote:
> >>
> >>> On Mon, Jun 10, 2013 at 9:20 PM, Justin Hibbits <jhibbits@freebsd.org
> >>> >wrote:
> >>>
> >>> > On Mon, Jun 10, 2013 at 6:31 AM, Nathan Whitehorn <
> >>> nwhitehorn@freebsd.org>wrote:
> >>> >
> >>> >> On 06/10/13 08:20, Nathan Whitehorn wrote:
> >>> >> > This is now getting interesting. Reading the tea leaves, what has
> >>> >> > happened is that the kernel has called into Open Firmware. Open
> >>> Firmware
> >>> >> > has then crashed early on, before setting up its own trap
> handlers,
> >>> >> > which has then flung you back into FreeBSD's handlers with a
> totally
> >>> >> > bogus environment, causing a second panic, which then causes a
> >>> *third*
> >>> >> > panic when trying to acquire a lock. It would be interesting to
> know
> >>> >> > what the OF environment looked like and what commands it was
> trying
> >>> to
> >>> >> > execute (in r3), but that may be tricky to get...
> >>> >> > -Nathan
> >>> >> > _______________________________________________
> >>> >>
> >>> >> One other point: you can trace this pretty easily by just putting
> >>> >> something like:
> >>> >>
> >>> >> if (pmap_bootstrapped) printf("Open Firmware call %p\n", args);
> >>> >>
> >>> >> in the top of openfirmware(). If I understood the debugger output
> >>> >> correctly, something should be making a firmware call immediately
> >>> before
> >>> >> the crash.
> >>> >>
> >>> >> As a random guess about what is happening, it is possible OF is
> trying
> >>> >> to allocate memory for itself. We just ignore the possibility that
> it
> >>> >> might want to do that at present, but that is not necessarily a good
> >>> >> assumption.
> >>> >> -Nathan
> >>>
> >>
>
> Here's where I stand on the panic:  The panic was actually caused within a
> bad return from Open Firmware, or something like that.  I eliminated the
> runtime panic by removing the necessity of Open Firmware to retrieve CPU
> ivars and instead caching them.  Now, after discussing with Nathan a bit, I
> added a trace and register dump to the db_main() function, so that every
> entry into DDB, even at the very beginning which is one place I see this
> problem, it would dump the needed information.
>
> I ran this twice, and go the exact same register dump, which is attached.
>  Any further insights are welcome.
>
> Oh, the actual entry is on an illegal instruction 0 at address 0, or so it
> claims.
>
> - Justin
>
> _______________________________________________
> freebsd-ppc@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ppc
> To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org"
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BWntOvN1iG-WJS0JEepmsL5jk0iV5EuDCeeMrdfRUA7AKZauQ>