On Thu, 7 Aug 2014 07:49-0700, David Wolfskill wrote:
> On Thu, Aug 07, 2014 at 01:32:45PM +0200, Roger Pau Monné wrote:
> > ...
> > I think I've found the issue, but since I'm not able to reproduce it,
> > could someone try the following patch? (without r269510 reverted).
> > ...
>
> That worked
On Thu, Aug 07, 2014 at 01:32:45PM +0200, Roger Pau Monné wrote:
> ...
> I think I've found the issue, but since I'm not able to reproduce it,
> could someone try the following patch? (without r269510 reverted).
> ...
That worked for me; thanks!
Peace,
david
--
David H. Wolfskill
On Thu, 7 Aug 2014 13:32+0200, Roger Pau Monné wrote:
> On 06/08/14 23:07, David Wolfskill wrote:
> > On Wed, Aug 06, 2014 at 10:48:32PM +0200, Trond Endrestøl wrote:
> >> ...
> >> Reverting r269510 did the trick, i.e.:
> >>
> >> cd /usr/src && svn up && svn diff -r 269510:269509 | patch
> >>
> >>
On 06/08/14 23:07, David Wolfskill wrote:
> On Wed, Aug 06, 2014 at 10:48:32PM +0200, Trond Endrestøl wrote:
>> ...
>> Reverting r269510 did the trick, i.e.:
>>
>> cd /usr/src && svn up && svn diff -r 269510:269509 | patch
>>
>> My i386 head VM is running smoothly with r269641M, with M meaning only
On Wed, 6 Aug 2014 22:48+0200, Trond Endrestøl wrote:
> On Wed, 6 Aug 2014 19:21+0200, Trond Endrestøl wrote:
>
> > On Tue, 5 Aug 2014 20:49-0700, John Baldwin wrote:
> >
> > >
> > > On Aug 5, 2014, at 2:29 PM, Michael Butler
> > > wrote:
> > >
> > > > On 08/05/14 16:56, Michael Butler wrote
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/06/14 17:07, David Wolfskill wrote:
> On Wed, Aug 06, 2014 at 10:48:32PM +0200, Trond Endrestøl wrote:
>> ... Reverting r269510 did the trick, i.e.:
>>
>> cd /usr/src && svn up && svn diff -r 269510:269509 | patch
>>
>> My i386 head VM is runni
On Wed, Aug 06, 2014 at 10:48:32PM +0200, Trond Endrestøl wrote:
> ...
> Reverting r269510 did the trick, i.e.:
>
> cd /usr/src && svn up && svn diff -r 269510:269509 | patch
>
> My i386 head VM is running smoothly with r269641M, with M meaning only
> the above reversal.
> ...
Works for me, as
On Wed, 6 Aug 2014 19:21+0200, Trond Endrestøl wrote:
> On Tue, 5 Aug 2014 20:49-0700, John Baldwin wrote:
>
> >
> > On Aug 5, 2014, at 2:29 PM, Michael Butler
> > wrote:
> >
> > > On 08/05/14 16:56, Michael Butler wrote:
> > >> On 08/05/14 16:02, John Baldwin wrote:
> > >>
> > >>> My guess
On Tue, 5 Aug 2014 20:49-0700, John Baldwin wrote:
>
> On Aug 5, 2014, at 2:29 PM, Michael Butler
> wrote:
>
> > On 08/05/14 16:56, Michael Butler wrote:
> >> On 08/05/14 16:02, John Baldwin wrote:
> >>
> >>> My guess is that the recent Xen changes tickled something.
> >>
> >> I can confirm
On Aug 5, 2014, at 2:29 PM, Michael Butler wrote:
> On 08/05/14 16:56, Michael Butler wrote:
>> On 08/05/14 16:02, John Baldwin wrote:
>>
>>> My guess is that the recent Xen changes tickled something.
>>
>> I can confirm this on a kernel which is otherwise up to date ..
>>
>> FreeBSD toshi.au
On 08/05/14 16:56, Michael Butler wrote:
> On 08/05/14 16:02, John Baldwin wrote:
>
>> My guess is that the recent Xen changes tickled something.
>
> I can confirm this on a kernel which is otherwise up to date ..
>
> FreeBSD toshi.auburn.protected-networks.net 11.0-CURRENT FreeBSD
> 11.0-CURREN
On 08/05/14 16:02, John Baldwin wrote:
> My guess is that the recent Xen changes tickled something.
I can confirm this on a kernel which is otherwise up to date ..
FreeBSD toshi.auburn.protected-networks.net 11.0-CURRENT FreeBSD
11.0-CURRENT #2 r269608M: Tue Aug 5 16:48:12 EDT 2014
I backed ou
On 08/05/14 16:02, John Baldwin wrote:
>> Given that my build machine did not exhibit the symptoms, and given the
>> references to atpic, it may be relevant to point out that the machine
>> where I see the panic is a Dell Precision M4400 laptop.
>
> My guess is that the recent Xen changes tickled
On Tue, Aug 05, 2014 at 01:02:25PM -0700, John Baldwin wrote:
...
> My guess is that the recent Xen changes tickled something. However, can you
> capture a verbose dmesg from your working kernel?
That was my current hunch, as well.
I've attached /var/run/dmesg.boot from a verbose boot running:
On Aug 5, 2014, at 7:29 AM, David Wolfskill wrote:
> On Mon, Aug 04, 2014 at 12:47:59PM -0700, David Wolfskill wrote:
>> ...
>> I was unable to get a crash dump, and I only recorded the offsets in the
>> backtrace (no arguments; sorry -- I was expecting the build machine to
>> allow me to invest
On Mon, Aug 04, 2014 at 12:47:59PM -0700, David Wolfskill wrote:
> ...
> I was unable to get a crash dump, and I only recorded the offsets in the
> backtrace (no arguments; sorry -- I was expecting the build machine to
> allow me to investigate on a machine with a serial console):
>
> ...
> SMP: A
16 matches
Mail list logo
