> On Sat, Aug 24, 2013 at 08:53:31PM -0700, Thomas Mueller wrote:
> > Some updates:
> > I could see what happens if I try to boot the FreeBSD boot partition on the
> > hard drive using the Super Grub Disk with chainloader.
> > If that works, it would boot FreeBSD 9.0-BETA1, but I would see if it
On Sat, Aug 24, 2013 at 08:53:31PM -0700, Thomas Mueller wrote:
> Some updates:
>
> I could see what happens if I try to boot the FreeBSD boot partition on the
> hard drive using the Super Grub Disk with chainloader.
>
> If that works, it would boot FreeBSD 9.0-BETA1, but I would see if it works
Finally I got some hard data in the "stopping amd causes a freeze" case.
I turned off xdm and reproduced the panic a couple of times by creating
high tmpfs load (building chromium on tmpfs) and sending SIGTERM to amd.
I got a couple of panics that produced many screens of output but
instantly rebo
According to Ollivier Robert:
> You are right, I wanted to say r226837 which is the "code" one.
FYI I've finally merged r226837,r226839 as r254856 in stable/9 as it is a
prerequesite to apply jmg's patch. I've asked re@ whether they would consider
this for 9.2. It is very late in the 9.2 relea
On Sun, Aug 25, 2013 at 7:42 AM, Adrian Chadd wrote:
> Does -HEAD have this same problem?
If I understood kib@ correctly, this is fixed in -HEAD by r253927.
> If so, we should likely just revert the patch entirely from -HEAD and -9
> until it's resolved.
It was not too difficult to prepare a re
Michael Tratz wrote:
>
> On Aug 15, 2013, at 2:39 PM, Rick Macklem
> wrote:
>
> > Michael Tratz wrote:
> >>
> >> On Jul 27, 2013, at 11:25 PM, Konstantin Belousov
> >> wrote:
> >>
> >>> On Sat, Jul 27, 2013 at 03:13:05PM -0700, Michael Tratz wrote:
> Let's assume the pid which started th
Hi,
Does -HEAD have this same problem?
If so, we should likely just revert the patch entirely from -HEAD and -9
until it's resolved.
-adrian
On 24 August 2013 23:51, Michael Tratz wrote:
>
> On Aug 15, 2013, at 2:39 PM, Rick Macklem wrote:
>
> > Michael Tratz wrote:
> >>
> >> On Jul 27,
On Aug 15, 2013, at 2:39 PM, Rick Macklem wrote:
> Michael Tratz wrote:
>>
>> On Jul 27, 2013, at 11:25 PM, Konstantin Belousov
>> wrote:
>>
>>> On Sat, Jul 27, 2013 at 03:13:05PM -0700, Michael Tratz wrote:
Let's assume the pid which started the deadlock is 14001 (it will
be a diff
