NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: kern/45361



The following reply was made to PR kern/45361; it has been noted by GNATS.

From: Julio Merino <jmmv%NetBSD.org@localhost>
To: matthew green <mrg%eterna.com.au@localhost>
Cc: David Holland <dholland-bugs%netbsd.org@localhost>, 
kern-bug-people%netbsd.org@localhost, 
 gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost, 
gnats-bugs%NetBSD.org@localhost
Subject: Re: kern/45361
Date: Tue, 15 Nov 2011 09:24:00 -0500

 On 11/15/11 4:49 AM, matthew green wrote:
 >> On 11/13/11 2:58 PM, Julio Merino wrote:
 >>> On 11/13/11 1:30 PM, David Holland wrote:
 >>>>    On Sun, Nov 13, 2011 at 06:25:06PM +0000, Jukka Ruohonen wrote:
 >>>>     >    Yes. Kernel from November 8 just crashed while compiling 
 >>>> Postgres. So still
 >>>>     >    can't upgrade from amd64/5.99.55 and all NetBSD-work is stalled.
 >>>>     >    However, I am too busy right now to check whether it is the same 
 >>>> problem.
 >>>>
 >>>>    Blah, I was hoping...
 >>>>
 >>>>     >    But better to keep this open so that there is at least one 
 >>>> tracker PR.
 >>>>
 >>>>    Indeed. I've also marked it 6-CRITICAL.
 >>>
 >>> Thanks.  I will also try tomorrow if I still see the same issue with
 >>> qemu, just in case the problem has "shifted" in some way.
 >>>
 >>
 >> I can't actually reproduce the problem any more on my amd64 VM.  qemu
 >> builds just fine under intensive swapping.
 >>
 >> I'm wondering if the problems that jruohonen is still experiencing are
 >> the same I was hitting, or just have similar symptoms.
 >
 > the problem with swapping under load was fixed by myself/matt a
 > while ago.
 
 Do you remember exactly when that happened?  I'm pretty sure I tried to 
 build qemu right after the fix was committed, and my machine still 
 crashed.  So, if you have the date, I'll roll back the kernel to that 
 point and try again just to make sure I did the correct thing back then.
 
  > that's the subject of this PR.  i'm pretty sure this
 > PR should be closed.
 
 Probably.  I just would like to revalidate according to when the fixes 
 happened.
 
 > if there are other problems without PRs occuring, they should be
 > given new PRs.  ie, don't confuse multiple issues in the same PR.
 
 Agreed.
 


Home | Main Index | Thread Index | Old Index