Same here. EARLY_AP_STARTUP no longer needs to be disabled on my boxes too.
> On 24 May 2018, at 19:12, Mark Martinec wrote:
>
> Just a short report to a thread I started when 11.1 came out.
>
> This machine would stall in a busy loop while attaching disks
> during boot. Rebuilding a kernel wi
Just a short report to a thread I started when 11.1 came out.
This machine would stall in a busy loop while attaching disks
during boot. Rebuilding a kernel with EARLY_AP_STARTUP disabled
avoided the problem. This was a situation through the whole
11.1 life cycle (i.e. patch releases did not help
the sources of
those panics anyway.
Took r321415 from stable/11 and applied it to 11.1-RC3 - and it makes
no difference to booting: still hangs attempting to attach da0,
with a spinning CPU (according to fan speed).
Booting in safe mode, or with EARLY_AP_STARTUP disabled avoids the
problem
t;> during a boot of a generic (patched) kernel, at least not in
>>> the last 40-lines screen before the hang occurs.
>>> (It also does not show during a "Safe mode" successful boot.)
>>
>> Btw (may or may not be relevant): after the above experiment
>
07/2017 15:55, Mark Martinec wrote:
Thanks! Tried it, and the message (or a backtrace) does not show
during a boot of a generic (patched) kernel, at least not in
the last 40-lines screen before the hang occurs.
(It also does not show during a "Safe mode" successful boot.)
Btw (may or
Thanks! Tried it, and the message (or a backtrace) does not show
during a boot of a generic (patched) kernel, at least not in
the last 40-lines screen before the hang occurs.
(It also does not show during a "Safe mode" successful boot.)
Btw (may or may not be relevant): after
r tracking down the hang. It might
produce false positives, but we'll see.
Thanks! Tried it, and the message (or a backtrace) does not show
during a boot of a generic (patched) kernel, at least not in
the last 40-lines screen before the hang occurs.
(It also does not show during a "S
On Thu, Jul 20, 2017 at 03:45:39PM +0200, Mark Martinec wrote:
> 2017-07-20 02:03, Mark Johnston wrote:
> > One thing to try at this point would be to disable EARLY_AP_STARTUP in
> > the kernel config. That is, take a configuration with which you're able
> > to reproduce the hang during boot, and r
2017-07-20 02:03, Mark Johnston wrote:
One thing to try at this point would be to disable EARLY_AP_STARTUP in
the kernel config. That is, take a configuration with which you're able
to reproduce the hang during boot, and remove "options
EARLY_AP_STARTUP".
Done. And it avoids the problem altoget
(possibly due to an unresponsive USB keyboard at that time),
> even though the debug.kdb.break_to_debugger was set to 1 at a
> loader prompt. It needs loader "Safe mode" to be able to boot.
>
> Next, a locally built kernel with DDB and INVARIANTS works well
> (the remain
. It needs loader "Safe mode" to be able to boot.
Next, a locally built kernel with DDB and INVARIANTS works well
(the remaining options come from an included GENERIC).
Now the funny part: a locally built kernel with just the DDB
option (and the rest included from GENERIC) *also* works wel
much. Unfortunately this machine does not have a serial
interface.
So in my last attempt I rebuilt a kernel with INVARIANTS but
without WITNESS - and now I cannot reproduce the problem, with
or without a "safe mode". What is interesting here that now
the da0..da3 disks are attached firs
On Tue, Jul 18, 2017 at 01:01:16AM +0200, Mark Martinec wrote:
> Upgrading 11.0-RELEASE-p11 to 11.1-RC3 using the usual freebsd-update
> upgrade
> method I ended up with a system which gets stuck while trying to attach
> the second set of disks. This happened already after the first phase of
> the
e
if a boot loader option "Safe mode" is set. This way I successfully
finished the upgrade procedure (installing world).
Playing with loader options that the "Safe mode" turns on
( /boot/menu-commands.4th ) it seems that kern.smp.disabled=1
is the crucial option, although
On 11/01/2010 01:42 PM, John Baldwin wrote:
On Monday, November 01, 2010 1:30:35 pm Stephen Clark wrote:
On 11/01/2010 09:54 AM, John Baldwin wrote:
On Monday, November 01, 2010 8:38:15 am Stephen Clark wrote:
On 10/29/2010 05:20 PM, John Baldwin wrote:
On Friday
On 2010-Oct-29 15:51:40 -0400, Stephen Clark wrote:
>On 10/29/2010 01:40 PM, Jeremy Chadwick wrote:
>> On Fri, Oct 29, 2010 at 01:12:29PM -0400, Stephen Clark wrote:
>>> I am supporting over 700 units in the field that are acting as
>>> firewall/router/vpn devices,
>>> that are running 6.3. It wou
On Monday, November 01, 2010 2:05:49 pm Stephen Clark wrote:
> atapci0: port
> 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa00
> atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xffa0
> ata0: on atapci0
> atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0
> atapci0: Reserved 0x1 bytes for
On 11/01/2010 01:42 PM, John Baldwin wrote:
On Monday, November 01, 2010 1:30:35 pm Stephen Clark wrote:
On 11/01/2010 09:54 AM, John Baldwin wrote:
On Monday, November 01, 2010 8:38:15 am Stephen Clark wrote:
On 10/29/2010 05:20 PM, John Baldwin wrote:
On Friday
On Monday, November 01, 2010 1:30:35 pm Stephen Clark wrote:
> On 11/01/2010 09:54 AM, John Baldwin wrote:
> > On Monday, November 01, 2010 8:38:15 am Stephen Clark wrote:
> >
> >> On 10/29/2010 05:20 PM, John Baldwin wrote:
> >>
> >>> On Friday, October 29, 2010 4:20:24 pm Stephen Clark
On 11/01/2010 09:54 AM, John Baldwin wrote:
On Monday, November 01, 2010 8:38:15 am Stephen Clark wrote:
On 10/29/2010 05:20 PM, John Baldwin wrote:
On Friday, October 29, 2010 4:20:24 pm Stephen Clark wrote:
rr232x: RocketRAID 232x controller driver v1.02 (Jan 16 2008 04:16
On Monday, November 01, 2010 8:38:15 am Stephen Clark wrote:
> On 10/29/2010 05:20 PM, John Baldwin wrote:
> > On Friday, October 29, 2010 4:20:24 pm Stephen Clark wrote:
> >
> >>> rr232x: RocketRAID 232x controller driver v1.02 (Jan 16 2008 04:16:21)
> >>> hptrr: HPT RocketRAID controller driv
On 10/29/2010 05:20 PM, John Baldwin wrote:
On Friday, October 29, 2010 4:20:24 pm Stephen Clark wrote:
rr232x: RocketRAID 232x controller driver v1.02 (Jan 16 2008 04:16:21)
hptrr: HPT RocketRAID controller driver v1.1 (Jan 16 2008 04:16:19)
big snip
lo0: bpf attached
rr232
On Friday, October 29, 2010 11:17:50 am Stephen Clark wrote:
> Hello,
>
> I am having a problem getting 6.3 to boot on an intel atom mb. When it
> gets to
> where it should identify the drive it hangs.
>
> If I boot with no acpi it does the same thing.
>
> If I boot
On Friday, October 29, 2010 4:20:24 pm Stephen Clark wrote:
> > rr232x: RocketRAID 232x controller driver v1.02 (Jan 16 2008 04:16:21)
> > hptrr: HPT RocketRAID controller driver v1.1 (Jan 16 2008 04:16:19)
> >
> big snip
> > lo0: bpf attached
> > rr232x: no controller detected.
> > hptrr: no contr
.
Oh, I think you answer this further down...
If I boot with no acpi it does the same thing.
If I boot with safe mode it comes up and identifies the drive but
then
starts spewing the following errors:
ipfw2 initialized, divert enabled, rule-based forwarding disabled,
default to ad
interrupt
answer this further down...
If I boot with no acpi it does the same thing.
If I boot with safe mode it comes up and identifies the drive but then
starts spewing the following errors:
ipfw2 initialized, divert enabled, rule-based forwarding disabled,
default to ad
interrupt storm detected
you answer this further down...
> >
> >>If I boot with no acpi it does the same thing.
> >>
> >>If I boot with safe mode it comes up and identifies the drive but then
> >>starts spewing the following errors:
> >>ipfw2 initialized, divert ena
instead? I mean, you
*are* using an Intel Atom system, which contains significantly more
advanced hardware than was available during the RELENG_6 days.
Oh, I think you answer this further down...
If I boot with no acpi it does the same thing.
If I boot with safe mode it comes up and
system, which contains significantly more
advanced hardware than was available during the RELENG_6 days.
Oh, I think you answer this further down...
> If I boot with no acpi it does the same thing.
>
> If I boot with safe mode it comes up and identifies the drive but then
> starts spe
Hello,
I am having a problem getting 6.3 to boot on an intel atom mb. When it
gets to
where it should identify the drive it hangs.
If I boot with no acpi it does the same thing.
If I boot with safe mode it comes up and identifies the drive but then
starts spewing the following errors:
ipfw2
Ivailo Bonev wrote:
What is the difference between installing 5.4 Release in Safe mode and
Normal installation?
Tried installing Normal installation on laptop paniced, but with Safe
mode is ok?
Safe mode disables ACPI/APM, it disables APIC and SMP, it slows down the hard
drives and so
What is the difference between installing 5.4 Release in Safe mode and
Normal installation?
Tried installing Normal installation on laptop paniced, but with Safe mode
is ok?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org
On Thu, 2004-11-25 at 00:22, Scott Long wrote:
> secmgr wrote:
> > Can someone point me to what "safe mode" sets so I can debug whats
> > broke?
> >
> > thanks
> > jim
> >
>
> It disables ACPI, APIC, ATA DMA, ATAPI DMA, ATA Write Cache, an
secmgr wrote:
Can someone point me to what "safe mode" sets so I can debug whats
broke?
thanks
jim
It disables ACPI, APIC, ATA DMA, ATAPI DMA, ATA Write Cache, and EISA.
Scott
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailma
Can someone point me to what "safe mode" sets so I can debug whats
broke?
thanks
jim
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
35 matches
Mail list logo
