On May 13, 1:11pm, ci4...@gmail.com (Chavdar Ivanov) wrote:
-- Subject: Re: Strange boot problems on amd64-current (6.99.40)
| Here is my dmesg.boot with DEBUG and DEBUG_GEOM on - it boots fine.
| Still crashes the same way without them, though.
And what is the crash without DEBUG?
christos
ng ext2fs...
mountroot: trying ffs...
root file system type: ffs
init: copying out path `/sbin/init' 11
bge0: link state DOWN (was UNKNOWN)
rtk0: link state UP (was UNKNOWN)
wsdisplay0: screen 1 added (80x25, vt100 emulation)
wsdisplay0: screen 2 added (80x25, vt100 emulation)
wsdisplay0: screen 3
On May 12, 4:24pm, ci4...@gmail.com (Chavdar Ivanov) wrote:
-- Subject: Re: Strange boot problems on amd64-current (6.99.40)
| Just for the record, the suggested patch did not make any difference
| for my problem, which otherwise appears to be linked to this
| discussion - root on raidframe. In
On May 12, 3:19pm, k...@munnari.oz.au (Robert Elz) wrote:
-- Subject: Re: Strange boot problems on amd64-current (6.99.40)
| One possibility that would be a backwards compatible, and slightly less
| hacky (and more flexible) solution, might be to use
|
| booted_partition
Just for the record, the suggested patch did not make any difference
for my problem, which otherwise appears to be linked to this
discussion - root on raidframe. In my case GENERIC still boots fine if
I enable DEBUG and DIAGNOSTIC.
Chavdar
On 12 May 2014 09:19, Robert Elz wrote:
> Date:
Date:Sun, 11 May 2014 22:53:48 -0400
From:chris...@zoulas.com (Christos Zoulas)
Message-ID: <20140512025348.ab23b17f...@rebar.astron.com>
| This should work... But it is sub-optimal.
It returns the state to as it was before the 1.306 commit. That is,
previously, t
On Sun, 11 May 2014, Christos Zoulas wrote:
On May 11, 7:48pm, p...@whooppee.com (Paul Goyette) wrote:
-- Subject: Re: Strange boot problems on amd64-current (6.99.40)
This should work... But it is sub-optimal.
It does indeed work.
Thanks
On May 11, 7:48pm, p...@whooppee.com (Paul Goyette) wrote:
-- Subject: Re: Strange boot problems on amd64-current (6.99.40)
This should work... But it is sub-optimal.
christos
Index: rf_netbsdkintf.c
===
RCS file: /cvsroot/src/sys
On May 12, 1:53am, c...@cubidou.net (Quentin Garnier) wrote:
-- Subject: Re: Strange boot problems on amd64-current (6.99.40)
| My analysis is that rf_netbsdkintf.c:1.306-8 introduced a call to
| findroot() (via cpu_rootconf() changed later to cpu_bootconf()),
| which sets booted_partition to e
On Sun, 11 May 2014, Christos Zoulas wrote:
Ok,
boot device: raid0
root on raid0e dumps on raid0b
This is what you get for the working kernel too? Everything in the logs
looks fine. Can you boot from a usb stick, let the raids autoconfig, mount
them and see if they are what you expect them to
On May 11, 7:10pm, mhi...@montana.edu ("Michael L. Hitch") wrote:
-- Subject: Re: Strange boot problems on amd64-current (6.99.40)
| On Sun, 11 May 2014, Paul Goyette wrote:
|
| > I might be able to get a serial console set-up, but it will likely take
some
| > time, as I
On May 11, 6:01pm, p...@whooppee.com (Paul Goyette) wrote:
-- Subject: Re: Strange boot problems on amd64-current (6.99.40)
| This message is in MIME format. The first part should be readable text,
| while the remaining parts are likely unreadable without MIME-aware tools.
|
| --0
On Sun, 11 May 2014, Paul Goyette wrote:
I might be able to get a serial console set-up, but it will likely take some
time, as I have never used serial console with netbsd. (I would estimate
that it would take me at least until next weekend, maybe even longer...)
If there are any other sugge
On Sun, May 11, 2014 at 06:31:25PM -0700, Paul Goyette wrote:
> On Sun, 11 May 2014, Michael L. Hitch wrote:
>
> >On Sun, 11 May 2014, Paul Goyette wrote:
> >
> >>I might be able to get a serial console set-up, but it will
> >>likely take some time, as I have never used serial console with
> >>net
On Sun, 11 May 2014, Michael L. Hitch wrote:
On Sun, 11 May 2014, Paul Goyette wrote:
I might be able to get a serial console set-up, but it will likely take
some time, as I have never used serial console with netbsd. (I would
estimate that it would take me at least until next weekend, maybe
On Sun, 11 May 2014, Paul Goyette wrote:
On Sun, 11 May 2014, Christos Zoulas wrote:
I found the rest of the e-mails. Please enable DEBUG_GEOM to see what
happens in x86_autoconf.c. And DEBUG and rf_kdebug_level > 0
for rf_netbsdkintf.c
Unfortunately, there is way too much info created by th
On Sun, 11 May 2014, Christos Zoulas wrote:
I found the rest of the e-mails. Please enable DEBUG_GEOM to see what
happens in x86_autoconf.c. And DEBUG and rf_kdebug_level > 0
for rf_netbsdkintf.c
Unfortunately, there is way too much info created by those two options,
and nothing useful remain
On Sun, 11 May 2014, Christos Zoulas wrote:
On May 11, 3:28pm, p...@whooppee.com (Paul Goyette) wrote:
-- Subject: Re: Strange boot problems on amd64-current (6.99.40)
| Good call - a GENERIC kernel from 2014-04-02 at 02:15 UTC works, and one
| from 02:18 (immediately after commit of revision
In article <20140511223213.99dd917f...@rebar.astron.com>,
Christos Zoulas wrote:
>On May 11, 3:28pm, p...@whooppee.com (Paul Goyette) wrote:
>-- Subject: Re: Strange boot problems on amd64-current (6.99.40)
>
>| Good call - a GENERIC kernel from 2014-04-02 at 02:15 UTC works, a
On May 11, 3:28pm, p...@whooppee.com (Paul Goyette) wrote:
-- Subject: Re: Strange boot problems on amd64-current (6.99.40)
| Good call - a GENERIC kernel from 2014-04-02 at 02:15 UTC works, and one
| from 02:18 (immediately after commit of revision 1.306 of
| sys/dev/raidframe
On Sun, 11 May 2014, Quentin Garnier wrote:
On Sun, May 11, 2014 at 08:26:52AM -0700, Paul Goyette wrote:
On Sun, 11 May 2014, Masao Uebayashi wrote:
Someone have to step up and bisect the whole kernel tree.
Well, I can get started. At least I have two end-points,
Working: 2013-1
Kernel from 08/14/2014 still works fine for me.
Chavdar
On 11 May 2014 17:58, Quentin Garnier wrote:
> On Sun, May 11, 2014 at 08:26:52AM -0700, Paul Goyette wrote:
>> On Sun, 11 May 2014, Masao Uebayashi wrote:
>>
>> >Someone have to step up and bisect the whole kernel tree.
>>
>>
>> Well, I ca
On Sun, May 11, 2014 at 08:26:52AM -0700, Paul Goyette wrote:
> On Sun, 11 May 2014, Masao Uebayashi wrote:
>
> >Someone have to step up and bisect the whole kernel tree.
>
>
> Well, I can get started. At least I have two end-points,
>
> Working: 2013-12-09 01:36:15
>
> Broken: 2
On Sun, 11 May 2014, Masao Uebayashi wrote:
Someone have to step up and bisect the whole kernel tree.
Well, I can get started. At least I have two end-points,
Working: 2013-12-09 01:36:15
Broken: 2014-04-14 15:43:14
I guess I'll get started. :) First stop, 2014-01-10
Someone have to step up and bisect the whole kernel tree.
On Sun, May 11, 2014 at 11:04 PM, Chavdar Ivanov wrote:
> I have sumilar problem - Ive discussed it earlier.
>
>
> C/P from my earlier mail to this list:
> ...
> root file system type: ffs
> fatal protection fauilt in supervisor mode
> tra
I have sumilar problem - Ive discussed it earlier.
C/P from my earlier mail to this list:
...
root file system type: ffs
fatal protection fauilt in supervisor mode
trap type 4 code 0 rip 80511a2a cs 8 rflags 10246 cr2
800036c88000 ilevel 0 rsp fe8006d08a20
curlwp 0xfe8006d4da0
BTW, I just checked a 6.99.41 GENERIC kernel, and it fails in the same
manner. So this is not likely a result of my customized kernel config.
I'm suspecting that this is due to booting from an auto-configured raid
mirror.
On Sat, 10 May 2014, Paul Goyette wrote:
On Sat, 10 May 2014, Jonat
On Sat, 10 May 2014, Jonathan A. Kollasch wrote:
On Sat, May 10, 2014 at 04:17:10PM -0700, Paul Goyette wrote:
15:43:14). With no other changes than the updated kernel (and
modules), it crashes with
kernel: pagefault trap, code=0
uvm_fault(0xfe813aec5e60, 0x0, 2) -> e
fatal page fault in s
On Sat, May 10, 2014 at 04:17:10PM -0700, Paul Goyette wrote:
> 15:43:14). With no other changes than the updated kernel (and
> modules), it crashes with
>
> kernel: pagefault trap, code=0
> uvm_fault(0xfe813aec5e60, 0x0, 2) -> e
> fatal page fault in supervisor mode
> trap type 6 code 2 rip f
(Resending without attachments, as I seem to have exceeded a size limit)
My current working kernel (amd64) is a customized 6.99.28 built from sources
that were current on 2013-12-14 at 23:34:52 UTC. Everything works correctly,
although there have been some strange errors coming from my cd driv
30 matches
Mail list logo
