Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 17 Apr 2012 15:57:41 +0200
From:      Garrett Anderson <gary@amerlok.com>
To:        Eugene Grosbein <egrosbein@rdtc.ru>
Cc:        Alexey Dokuchaev <danfe@nsu.ru>, stable@freebsd.org, John Baldwin <jhb@freebsd.org>
Subject:   Re: RELENG_8 kernel as of Apr 14 does not boot
Message-ID:  <CAKBX9h0MnU9QQeti1kNEGVS4nusEVLssLoeBr66Dsz_sxHpevA@mail.gmail.com>
In-Reply-To: <CAKBX9h3ZZf0zNv2QXTUCUenKejh_wR3SE5%2B0OFTy3C%2BzyL%2BF4g@mail.gmail.com>
References:  <20120416042645.GA53074@regency.nsu.ru> <20120416070646.GA78414@regency.nsu.ru> <4F8BD14D.8050206@rdtc.ru> <201204170840.37631.jhb@freebsd.org> <4F8D6B58.7010902@rdtc.ru> <CAKBX9h3ZZf0zNv2QXTUCUenKejh_wR3SE5%2B0OFTy3C%2BzyL%2BF4g@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
My bad.  Please accept my apologies.  Working on too many things at one tim=
e.

On Tue, Apr 17, 2012 at 3:48 PM, Garrett Anderson <gary@amerlok.com> wrote:
> I am working on the Jerome's computer. =A0What you want is still on the
> server in Moscow. =A0Yes, there is a copy on the Jerome's computer but
> it is password protected. =A0What is the password? =A0I don't know but it
> is the same one that is used to access the Exchange server in Moscow.
> So, we come back to the same bottleneck: Access to the Exchange Server
> in Moscow.
>
> The best thing to do is to get access to Jerome's "current" email on
> the server in Moscow. =A0The alternative is to get this password and I
> setup TeamViewer on the Jerome's computer and you access his computer
> from London (via TeamViewer). =A0In either case, we need Jerome's
> Outlook Password and that can only be reset in Moscow.
>
> On Tue, Apr 17, 2012 at 3:08 PM, Eugene Grosbein <egrosbein@rdtc.ru> wrot=
e:
>>> On Monday, April 16, 2012 3:59:09 am Eugene Grosbein wrote:
>>>>>>> Just update my 8.x kernel sources last weekend, and newly built ker=
nel did
>>>>>>> not boot for me:
>>>>>>>
>>>>>>> link_elf: symbol mem_range_softc undefined
>>>>>>> KLD file acpi.ko - could not finalize loading
>>>>>>> kernel trap 12 with interrupts disabled
>>>>>>
>>>>>> Try to add 'device mem' to your kernel configuration.
>>>>>
>>>>> :-)
>>>>>
>>>>> I explicitly have "nodevice mem" and "nodevice io" in my config. =A0T=
hey are
>>>>> being loaded from /boot/loader.conf. =A0This worked fine for quite a =
while.
>>>>>
>>>>> I will try to have it compiled-in, but would still prefer it fixed, o=
r in
>>>>> case it cannot be fixed and mem.ko cannot be loaded separately from n=
ow on,
>>>>> appropriate entry in UPDATING.
>>>>
>>>> It seems John Baldwin brought dependency of acpi.ko on device mem
>>>> 4 days ago to RELENG_8 with MFC:
>>>>
>>>> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/acpica/acpi_wakeup.=
c#rev1.50.2.3
>>>
>>> Hmm, this has been broken for a long time on HEAD and 9 it seems. =A0Ho=
wever, there
>>> you get compile breakage (as acpi is no longer supported as a module in=
 9+) if you
>>> try to build a kernel with 'nodevice mem'.
>>>
>>> Hmm, mp_machdep.c also breaks. =A0That is probably true on i386 as well=
, and has
>>> been true even on 7.x. =A0(That is, you can't use 'nodevice mem' and 'S=
MP' in the
>>> same kernel.)
>>>
>>> The simplest fix is to just move mem_range_softc out of mem.ko into the=
 base kernel.
>>>
>>> OTOH, what are you trying to gain by putting mem.ko into a module rathe=
r than part of
>>> the base kernel? =A0Do you just want no /dev/mem file or are you trying=
 to disable all
>>> of the MTRR support as well? =A0It may be that we need to rethink what =
goes into mem.ko
>>> and have it only exclude /dev/mem but always leave MTRR support enabled=
.
>>
>> I guess, Alexey just tries to make smallest possible kernel just for fun=
 :-)
>> Or, for PicoBSD case where kernel should be booted from very small media=
 and modules from another one.
>>
>> Eugene Grosbein
>> _______________________________________________
>> freebsd-stable@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org=
"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKBX9h0MnU9QQeti1kNEGVS4nusEVLssLoeBr66Dsz_sxHpevA>