Discussion concerning the use of FreeBSD-current

headers Michael Butler | 29 Jul 2012 19:40

Is anyone else having troubles getting -current after SVN r238886 to
boot? In my case, I have an unstoppable stream of pager_something
console messages 

	imb

On 29.07.2012 19:40 (UTC+2), Michael Butler wrote:
> Is anyone else having troubles getting -current after SVN r238886 to
> boot? In my case, I have an unstoppable stream of pager_something
> console messages 
>
> 	imb

Yes, it's the same here. I had to revert to old kernel.

Rainer

_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"

On Sun, Jul 29, 2012 at 10:40 AM, Michael Butler
<imb <at> protected-networks.net> wrote:
> Is anyone else having troubles getting -current after SVN r238886 to
> boot? In my case, I have an unstoppable stream of pager_something
> console messages 

    What was the previous version you booted and what's your configuration?
Thanks,
-Garrett
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"

On 07/29/12 14:24, Garrett Cooper wrote:
> On Sun, Jul 29, 2012 at 10:40 AM, Michael Butler
> <imb <at> protected-networks.net> wrote:
>> Is anyone else having troubles getting -current after SVN r238886 to
>> boot? In my case, I have an unstoppable stream of pager_something
>> console messages 
> 
>     What was the previous version you booted and what's your configuration?
> Thanks,
> -Garrett

I'm on an x86 core duo laptop with a single SATA disk split between
Windoze-7 and FreeBSD. Nothing really special in the kernel config (as
attached).

The kernel from r238864 (yesterday) is working just fine,

	imb

# TOSHI

include GENERIC

ident		TOSHI-SMP

nomakeoption	DEBUG
#makeoptions	WITH_CTF=no

On Sun, Jul 29, 2012 at 11:36 AM, Michael Butler
<imb <at> protected-networks.net> wrote:
> On 07/29/12 14:24, Garrett Cooper wrote:
>> On Sun, Jul 29, 2012 at 10:40 AM, Michael Butler
>> <imb <at> protected-networks.net> wrote:
>>> Is anyone else having troubles getting -current after SVN r238886 to
>>> boot? In my case, I have an unstoppable stream of pager_something
>>> console messages 
>>
>>     What was the previous version you booted and what's your configuration?
>> Thanks,
>> -Garrett
>
> I'm on an x86 core duo laptop with a single SATA disk split between
> Windoze-7 and FreeBSD. Nothing really special in the kernel config (as
> attached).
>
> The kernel from r238864 (yesterday) is working just fine,

    And if you go back to r238885...?
Thanks!
-Garrett
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"

On 07/29/12 14:39, Garrett Cooper wrote:
> On Sun, Jul 29, 2012 at 11:36 AM, Michael Butler
> <imb <at> protected-networks.net> wrote:
>> On 07/29/12 14:24, Garrett Cooper wrote:
>>> On Sun, Jul 29, 2012 at 10:40 AM, Michael Butler
>>> <imb <at> protected-networks.net> wrote:
>>>> Is anyone else having troubles getting -current after SVN r238886 to
>>>> boot? In my case, I have an unstoppable stream of pager_something
>>>> console messages 
>>>
>>>     What was the previous version you booted and what's your configuration?
>>> Thanks,
>>> -Garrett
>>
>> I'm on an x86 core duo laptop with a single SATA disk split between
>> Windoze-7 and FreeBSD. Nothing really special in the kernel config (as
>> attached).
>>
>> The kernel from r238864 (yesterday) is working just fine,
> 
>     And if you go back to r238885...?

Building that now,

	imb

On Sun, Jul 29, 2012 at 11:39:14AM -0700, Garrett Cooper wrote:
> ...
> >>     What was the previous version you booted and what's your configuration?
> >> Thanks,
> >> -Garrett
> >
> > I'm on an x86 core duo laptop with a single SATA disk split between
> > Windoze-7 and FreeBSD. Nothing really special in the kernel config (as
> > attached).
> >
> > The kernel from r238864 (yesterday) is working just fine,
> 
>     And if you go back to r238885...?
> Thanks!

FWIW, I built & booted r238885 on both my laptop & my home build
machine (without icident), and I'm in the process of building r238886
on my desktop at work as I type.  (I haven't a serial console
attached to the latter, and I'm remote from it, so this may be ...
interesting for me.... :-})

Peace,
david
--

-- 
David H. Wolfskill				david <at> catwhisker.org
Depriving a girl or boy of an opportunity for education is evil.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.

On 07/29/12 14:39, Garrett Cooper wrote:
> On Sun, Jul 29, 2012 at 11:36 AM, Michael Butler
> <imb <at> protected-networks.net> wrote:
>> On 07/29/12 14:24, Garrett Cooper wrote:
>>> On Sun, Jul 29, 2012 at 10:40 AM, Michael Butler
>>> <imb <at> protected-networks.net> wrote:
>>>> Is anyone else having troubles getting -current after SVN r238886 to
>>>> boot? In my case, I have an unstoppable stream of pager_something
>>>> console messages 
>>>
>>>     What was the previous version you booted and what's your configuration?
>>> Thanks,
>>> -Garrett
>>
>> I'm on an x86 core duo laptop with a single SATA disk split between
>> Windoze-7 and FreeBSD. Nothing really special in the kernel config (as
>> attached).
>>
>> The kernel from r238864 (yesterday) is working just fine,
> 
>     And if you go back to r238885...?
> Thanks!

Boots just fine ..

imb <at> toshi:/home/imb> uname -a
FreeBSD toshi.auburn.protected-networks.net 10.0-CURRENT FreeBSD
10.0-CURRENT #1 r238885: Sun Jul 29 14:44:58 EDT 2012
imb <at> toshi.auburn.protected-networks.net:/usr/obj/usr/home/imb/svn/head/sys/TOSHI
 i386

On Sun, Jul 29, 2012 at 12:02 PM, Michael Butler
<imb <at> protected-networks.net> wrote:
> On 07/29/12 14:39, Garrett Cooper wrote:
>> On Sun, Jul 29, 2012 at 11:36 AM, Michael Butler
>> <imb <at> protected-networks.net> wrote:
>>> On 07/29/12 14:24, Garrett Cooper wrote:
>>>> On Sun, Jul 29, 2012 at 10:40 AM, Michael Butler
>>>> <imb <at> protected-networks.net> wrote:
>>>>> Is anyone else having troubles getting -current after SVN r238886 to
>>>>> boot? In my case, I have an unstoppable stream of pager_something
>>>>> console messages 
>>>>
>>>>     What was the previous version you booted and what's your configuration?
>>>> Thanks,
>>>> -Garrett
>>>
>>> I'm on an x86 core duo laptop with a single SATA disk split between
>>> Windoze-7 and FreeBSD. Nothing really special in the kernel config (as
>>> attached).
>>>
>>> The kernel from r238864 (yesterday) is working just fine,
>>
>>     And if you go back to r238885...?
>> Thanks!
>
> Boots just fine ..
>
> imb <at> toshi:/home/imb> uname -a
> FreeBSD toshi.auburn.protected-networks.net 10.0-CURRENT FreeBSD
> 10.0-CURRENT #1 r238885: Sun Jul 29 14:44:58 EDT 2012

On 29.07.2012 22:04, Garrett Cooper wrote:
> On Sun, Jul 29, 2012 at 12:02 PM, Michael Butler
> <imb <at> protected-networks.net> wrote:
>> On 07/29/12 14:39, Garrett Cooper wrote:
>>> On Sun, Jul 29, 2012 at 11:36 AM, Michael Butler
>>> <imb <at> protected-networks.net> wrote:
>>>> On 07/29/12 14:24, Garrett Cooper wrote:
>>>>> On Sun, Jul 29, 2012 at 10:40 AM, Michael Butler
>>>>> <imb <at> protected-networks.net> wrote:
>>>>>> Is anyone else having troubles getting -current after SVN r238886 to
>>>>>> boot? In my case, I have an unstoppable stream of pager_something
>>>>>> console messages 
>>>>>
>>>>>      What was the previous version you booted and what's your configuration?
>>>>> Thanks,
>>>>> -Garrett
>>>>
>>>> I'm on an x86 core duo laptop with a single SATA disk split between
>>>> Windoze-7 and FreeBSD. Nothing really special in the kernel config (as
>>>> attached).
>>>>
>>>> The kernel from r238864 (yesterday) is working just fine,
>>>
>>>      And if you go back to r238885...?
>>> Thanks!
>>
>> Boots just fine ..
>>
>> imb <at> toshi:/home/imb> uname -a
>> FreeBSD toshi.auburn.protected-networks.net 10.0-CURRENT FreeBSD

Hello, Alexander.
You wrote 29 июля 2012 г., 23:15:06:

AM> Do you have any devices other then SATA disk? CD or some USB drive?
  ``Me too''

I have same problem on my net5501. IT is i386 (AMD GEODE) with CF card
attached as IDE (not SATA) disk. I have no swap configured.

AM> Can you make at least any screenshot or tell something diagnostic about
AM> the problem? If there is chance to grab some output, could you set via
AM> the loader prompt variable kern.cam.dflags=0x41 and grab output after that?
  Attached  log  of  booting  without  kern.cam.dflags=0x41  and  with
kern.cam.dflags=0x41 (two files), as I have serial console.

  To be honest, I can not spot the difference.

--

-- 
// Black Lion AKA Lev Serebryakov <lev <at> FreeBSD.org>
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
On 29.07.2012 22:52, Lev Serebryakov wrote:
> Hello, Alexander.
> You wrote 29 июля 2012 г., 23:15:06:
>
> AM> Do you have any devices other then SATA disk? CD or some USB drive?
>    ``Me too''
>
> I have same problem on my net5501. IT is i386 (AMD GEODE) with CF card
> attached as IDE (not SATA) disk. I have no swap configured.

I was able to diagnose problem and it is not related to CAM as I've 
thought initially. It is related to GEOM spoiling mechanism.

During boot process fsck opens checked disks for writing, while root at 
that time mounted as read-only. Disks close by fsck causes spoiling of 
the root partition's GEOM VFS, that with r238886 change made it 
inaccessible.

I've reverted that GEOM VFS change at r238892, that should fix the 
problem until better solution will be found.

I'm sorry.

--

-- 
Alexander Motin
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"

On 07/29/12 16:13, Alexander Motin wrote:
> I was able to diagnose problem and it is not related to CAM as I've
> thought initially. It is related to GEOM spoiling mechanism.
> 
> During boot process fsck opens checked disks for writing, while root at
> that time mounted as read-only. Disks close by fsck causes spoiling of
> the root partition's GEOM VFS, that with r238886 change made it
> inaccessible.
> 
> I've reverted that GEOM VFS change at r238892, that should fix the
> problem until better solution will be found.

I can confirm that this change avoids/fixes the issue - thanks 

> I'm sorry.

No apology required - if I'm running -current, I should and do expect
the occasional breakage. It's better found now than when it hits a wider
release, i.e. I don't put -current on a production box ..

	imb

On 7/29/2012 10:40 AM, Michael Butler wrote:
> Is anyone else having troubles getting -current after SVN r238886 to
> boot? In my case, I have an unstoppable stream of pager_something
> console messages 
>
> 	imb
>
me2

If I stop at single user and then continue, then all seems okay.

I'm guessing (just a SWAG) that it might be related to the disk resize 
CAM stuff just added.

_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"

post SVN r238886 no boot?

Re: post SVN r238886 no boot?

Re: post SVN r238886 no boot?

Re: post SVN r238886 no boot?

Re: post SVN r238886 no boot?

Re: post SVN r238886 no boot?

Re: post SVN r238886 no boot?

Re: post SVN r238886 no boot?

Re: post SVN r238886 no boot?

Re: post SVN r238886 no boot?

Re: post SVN r238886 no boot?

Re: post SVN r238886 no boot?

Re: post SVN r238886 no boot?

Re: post SVN r238886 no boot?