On Sat, Oct 20, 2012 at 07:10:19AM -0700, David Wolfskill wrote:
This seems ... fairly weird to me.
Yesterday, I built booted:
FreeBSD g1-227.catwhisker.org 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #274
241726M: Fri Oct 19 05:40:05 PDT 2012
On Sun, Oct 21, 2012 at 03:13:56PM +0300, Konstantin Belousov wrote:
...
Anyone else seeing this? Any ideas how to diagnose it?
devread is the method of devctl(4) which passes devd notifications from
the kernel to userland (to devd, specifically). There were no changes to
devctl(4) for
On Sun, Oct 21, 2012 at 03:13:56PM +0300, Konstantin Belousov wrote:
On Sat, Oct 20, 2012 at 07:10:19AM -0700, David Wolfskill wrote:
This seems ... fairly weird to me.
Yesterday, I built booted:
FreeBSD g1-227.catwhisker.org 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #274
241726M: Fri
On Sun, Oct 21, 2012 at 09:33:22AM -0700, David Wolfskill wrote:
...
So I tried reverting 241749 ... and I failed to reproduce the problem.
Well, one boot out of one, at least. I'll try a few more reality
checks, and report back if a correction is in order. But (for now, at
least), it
On Sun, Oct 21, 2012 at 09:46:34AM -0700, David Wolfskill wrote:
On Sun, Oct 21, 2012 at 09:33:22AM -0700, David Wolfskill wrote:
...
So I tried reverting 241749 ... and I failed to reproduce the problem.
Well, one boot out of one, at least. I'll try a few more reality
checks, and
On 21.10.2012 20:40, Konstantin Belousov wrote:
On Sun, Oct 21, 2012 at 09:46:34AM -0700, David Wolfskill wrote:
On Sun, Oct 21, 2012 at 09:33:22AM -0700, David Wolfskill wrote:
...
So I tried reverting 241749 ... and I failed to reproduce the problem.
Well, one boot out of one, at least.
On Sun, Oct 21, 2012 at 09:28:06PM +0300, Alexander Motin wrote:
...
I am curious, how to interpret phrase 42=94966796 bytes allocated in
log. May be it is just corrupted output, but the number still seems
quite big, especially for i386 system, making me think about some
integer overflow.
On Sun, Oct 21, 2012 at 09:28:06PM +0300, Alexander Motin wrote:
...
I am curious, how to interpret phrase 42=94966796 bytes allocated in
log. May be it is just corrupted output, but the number still seems
quite big, especially for i386 system, making me think about some
integer overflow.
On 21.10.2012 23:23, David Wolfskill wrote:
On Sun, Oct 21, 2012 at 09:28:06PM +0300, Alexander Motin wrote:
...
I am curious, how to interpret phrase 42=94966796 bytes allocated in
log. May be it is just corrupted output, but the number still seems
quite big, especially for i386 system, making
On Sat, Oct 20, 2012 at 07:10:19AM -0700, David Wolfskill wrote:
This seems ... fairly weird to me.
Yesterday, I built booted:
FreeBSD g1-227.catwhisker.org 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #274
241726M: Fri Oct 19 05:40:05 PDT 2012
On 22.10.2012 01:03, Alexander Motin wrote:
On 21.10.2012 23:23, David Wolfskill wrote:
On Sun, Oct 21, 2012 at 09:28:06PM +0300, Alexander Motin wrote:
...
I am curious, how to interpret phrase 42=94966796 bytes allocated in
log. May be it is just corrupted output, but the number still seems
On Mon, Oct 22, 2012 at 12:09:08AM +0200, Mateusz Guzik wrote:
...
This looks a lot like issue you reported a couple of months earlier,
even affected buffer address matches.
It's a tad scary that someone else notices that sort of thing before I
do. :-}
At least part of REDZONE metadata
On Mon, Oct 22, 2012 at 01:31:04AM +0300, Alexander Motin wrote:
...
I've used your kernel config and my test system was unable to boot from
NFS, while GENERIC kernel boots fine. I haven't got panic, but boot just
stopped on root mounting. You have so many options specified there so I
On Sun, Oct 21, 2012 at 3:46 PM, David Wolfskill da...@catwhisker.org wrote:
On Mon, Oct 22, 2012 at 01:31:04AM +0300, Alexander Motin wrote:
...
I've used your kernel config and my test system was unable to boot from
NFS, while GENERIC kernel boots fine. I haven't got panic, but boot just
On Sun, Oct 21, 2012 at 05:28:49PM -0700, Kevin Oberman wrote:
...
This is starting to smell a bit like it may be tied to hardware. If
you have two memory cards, you might want to try swapping them. If
not, maybe let memtest86 run overnight.
There are 2 SODIMMS, yes.
So I reverted mjg@'s
This seems ... fairly weird to me.
Yesterday, I built booted:
FreeBSD g1-227.catwhisker.org 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #274
241726M: Fri Oct 19 05:40:05 PDT 2012
r...@g1-227.catwhisker.org:/usr/obj/usr/src/sys/CANARY i386
and used the machine all day; nothing unusual
16 matches
Mail list logo
