Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 29 Oct 2010 16:20:24 -0400
From:      Stephen Clark <sclark46@earthlink.net>
To:        sclark46@earthlink.net
Cc:        FreeBSD Stable <freebsd-stable@freebsd.org>, Jeremy Chadwick <freebsd@jdc.parodius.com>
Subject:   Re: safe mode
Message-ID:  <4CCB2C88.9050208@earthlink.net>
In-Reply-To: <4CCB25CC.9050405@earthlink.net>
References:  <4CCAE59E.5020006@earthlink.net>	<20101029165405.GA82279@icarus.home.lan>	<4CCB007D.8080204@earthlink.net>	<20101029174014.GA82936@icarus.home.lan> <4CCB25CC.9050405@earthlink.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On 10/29/2010 03:51 PM, 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:
>>> On 10/29/2010 12:54 PM, Jeremy Chadwick wrote:
>>>> On Fri, Oct 29, 2010 at 11:17:50AM -0400, Stephen Clark wrote:
>>>>> 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.
>>>> Can you try 8.1-RELEASE or an 8.1-STABLE snapshot 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 identifies the drive but 
>>>>> then
>>>>> starts spewing the following errors:
>>>>> ipfw2 initialized, divert enabled, rule-based forwarding disabled,
>>>>> default to ad
>>>>> interrupt storm detected on "irq15:"; throttling interrupt source
>>>>> ad4: 152627MB<WDC WD1600BEKT-00A25T0 01.01A01>   at ata2-master PIO4
>>>>> interrupt storm detected on "irq15:"; throttling interrupt source
>>>>> interrupt storm detected on "irq15:"; throttling interrupt source
>>>>> interrupt storm detected on "irq15:"; throttling interrupt source
>>>>>
>>>>> FreeBSD runs but I continue to get these errors:
>>>>>
>>>>> What exactly does safe mode do - I am afraid my forth skills are not
>>>>> what they should be.
>>>> "Safe mode" does the following before doing "boot":
>>>>
>>>> set hw.ata.ata_dma=0
>>>> set hw.ata.atapi_dma=0
>>>> set hw.ata.wc=0
>>>> set hw.eisa_slots=0
>>>> set hint.kbdmux.0.disabled=1
>>>>
>>>> It also does the following if you're booting/running i386:
>>>>
>>>> unset acpi_load
>>>> set hint.acpi.0.disabled=1
>>>> set loader.acpi_disabled_by_user=1
>>>> set hint.apic.0.disabled=1
>>>>
>>>> The code is in /boot/beastie.4th.
>>>>
>>>> IMHO, you shouldn't be disabling ACPI, or using "safe mode" to try and
>>>> get your system working.  Can you please boot Verbose mode instead and
>>>> provide all of the output somewhere?  You'll probably need serial
>>>> console for this, since the system hangs.
>>>>
>>>>
>>>>> atapci0@pci0:0:31:1:    class=0x01018a card=0x28508086
>>>>> chip=0x28508086 rev=0x03 hdr=0x00
>>>>>      vendor     = 'Intel Corporation'
>>>>>      device     = '82801H (ICH8 Family) Ultra ATA Storage 
>>>>> Controllers'
>>>>>      class      = mass storage
>>>>>      subclass   = ATA
>>>>> atapci1@pci0:0:31:2:    class=0x01018f card=0x28288086
>>>>> chip=0x28288086 rev=0x03 hdr=0x00
>>>>>      vendor     = 'Intel Corporation'
>>>>>      device     = 'ICH8M (ICH8 Family) 3 port SATA Controller'
>>>>>      class      = mass storage
>>>>>      subclass   = ATA
>>>> Your storage controller is an Intel ICH8, which is supported by 
>>>> FreeBSD,
>>>> but the ATA layer differs greatly between 6.x and 8.x (read: better on
>>>> 8.x).  AHCI is also well-supported on 8.x if your system/BIOS supports
>>>> it.
>>>>
>>>>> I am stuck for now on 6.3 so moving to a later release 7+ is not 
>>>>> feasible.
>>>> Can you explain why?  (If I don't ask it, someone else will.)  This 
>>>> will
>>>> almost certainly be the key to this discussion, especially since you
>>>> say:
>>>>
>>> I am supporting over 700 units in the field that are acting as
>>> firewall/router/vpn devices,
>>> that are running 6.3. It would not be feasible to upgrade them to a
>>> new version of FreeBSD
>>> remotely. Also if I was going to move to a  later release of FreeBSD
>>> for the new hardware
>>> it would involve months  of new testing and validation of the new
>>> release, where putting a patched
>>> 6.3 kernel is relatively straightforward.
>> I'm a little confused.  Did you deploy over 700 field units running
>> FreeBSD 6.3 without testing it first on this particular piece of
>> hardware/setup?  Or did you recently upgrade from FreeBSD X.Y to 6.3 and
>> found that things broke?  What I'm trying to find out is whether or not
>> these systems ever worked for you, and if so, at what point did they
>> stop working.
> Sorry for the confusion. We have a mix of hardware in the field. The 
> current
> hardware platform we are shipping is going EOL from the vendor. I am 
> testing
> the vendors next generation of hardware.
>
> I included at the end a verbose startup using the 6.3 install disc.
>
>>   Possibly we can work backwards to figure out what code
>> change/commit broke things for you.  Keep reading for some ideas.
>>
>> First question: are you using any parameters in /boot/loader.conf or
>> /boot.config?  If so, what are they?
>>    Second question: can you provide your kernel configuration file?
>>
>> As for the verbose boot -- thanks much.  Appropriate folks should be
>> here on the list, so if they have ideas they'll probably reply.  A quick
>> analysis indicates the following:
>>
>> ata0 -->  atapci0 -->  Intel ATA controller master, IDE/PATA, IRQ 14
>> ata1 -->  atapci0 -->  Intel ATA controller slave,  IDE/PATA, IRQ 14
>> ata2 -->  atapci1 -->  Intel ATA controller master, IDE/PATA, IRQ 15
>> ata3 -->  atapci1 -->  Intel ATA controller slave,  IDE/PATA, IRQ 15
>>
>> A single device is found on ata2, but no other devices are found on the
>> other ATA busses:
>>
>>> ata2: reset tp2 stat0=50 stat1=00 devices=0x1<ATA_MASTER>
>> That probably correlates with what you see when you boot "safe mode",
>> since there we see this message:
>>
>>    ad4: 152627MB<WDC WD1600BEKT-00A25T0 01.01A01>  at ata2-master PIO4
>>
>> However, there's other messages which are a serious concern, given their
>> association with the ATA controller in question:
>>
>>    interrupt storm detected on "irq15:"; throttling interrupt source
>>    interrupt storm detected on "irq15:"; throttling interrupt source
>>    interrupt storm detected on "irq15:"; throttling interrupt source
>>    interrupt storm detected on "irq15:"; throttling interrupt source
>>
>> You might try escaping to the loader prompt (I forget what menu item it
>> is on 6.x, might be item 6) and entering the following commands.  These
>> are the 3 things I'd try first, and in this order:
>>
>> 1) set hint.apic.0.disabled=1
>>     boot
>>
>> 2) set hw.ata.ata_dma=0
>>     boot
>>
>> 3) set hint.apic.0.disabled=1
>>     set hw.ata.ata_dma=0
>>     set hint.kbdmux.0.disabled=1
>>     boot
>>
>> If any of these work (I'm hoping #1 or #2 suffices), you can add the
>> appropriate lines to your /boot/loader.conf without the "set" portion
>> and they should be retained going forward.
>>
> Unfortunately none of the above worked. Here is a verbose startup from 
> the
> generic kernel on the 6.3 install disk. Note: when I used the safe for 
> the install
> it actually went into the install program and didn't hang - though I 
> did see the
> interrupt storm message right before sysinstall ran.
>
>
> m��^:FZ�2+/#";wJ/+*+"�:*;+&o""""B"B""""B"~"""B"B"""B"�"B"B""6"B"B"*""B"B"      
> 0
> SMAP type=02 base=000000000009fc00 len=0000000000000400
> SMAP type=02 base=00000000000e0000 len=0000000000020000
> SMAP type=01 base=0000000000100000 len=000000003f9a0000
> SMAP type=03 base=000000003faa0000 len=000000000000e000
> SMAP type=04 base=000000003faae000 len=0000000000032000
> SMAP type=02 base=000000003fae0000 len=0000000000010000
> SMAP type=02 base=000000003faf0000 len=0000000000010000
> SMAP type=02 base=00000000fee00000 len=0000000000001000
> SMAP type=02 base=00000000ffb00000 len=0000000000500000
> Copyright (c) 1992-2008 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
>         The Regents of the University of California. All rights reserved.
> FreeBSD is a registered trademark of The FreeBSD Foundation.
> FreeBSD 6.3-RELEASE #0: Wed Jan 16 04:18:52 UTC 2008
>     root@dessler.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
> Preloaded elf kernel "/boot/kernel/kernel" at 0xc1037000.
> Preloaded mfs_root "/boot/mfsroot" at 0xc10371ac.
> Preloaded elf module "/boot/kernel/acpi.ko" at 0xc10371f0.
> MP Configuration Table version 1.4 found at 0xc00fdc90
> Table 'FACP' at 0x3faa0290
> Table 'APIC' at 0x3faa0390
> MADT: Found table at 0x3faa0390
> APIC: Using the MADT enumerator.
> MADT: Found CPU APIC ID 0 ACPI ID 1: enabled
> MADT: Found CPU APIC ID 2 ACPI ID 2: enabled
> MADT: Found CPU APIC ID 1 ACPI ID 3: enabled
> MADT: Found CPU APIC ID 3 ACPI ID 4: enabled
> ACPI APIC Table: <080610 APIC1657>
> Calibrating clock(s) ... i8254 clock: 1188490 Hz
> CLK_USE_I8254_CALIBRATION not specified - using default frequency
> Timecounter "i8254" frequency 1193182 Hz quality 0
> Calibrating TSC clock ... TSC clock: 1673327070 Hz
> CPU: Intel(R) Atom(TM) CPU D510   @ 1.66GHz (1673.33-MHz 686-class CPU)
>   Origin = "GenuineIntel"  Id = 0x106ca  Stepping = 10
>   
> Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,> 
>
>   
> Features2=0x40e31d<SSE3,RSVD2,MON,DS_CPL,TM2,SSSE3,CX16,xTPR,PDCM,<b22>>
>   AMD Features=0x20100000<NX,LM>
>   AMD Features2=0x1<LAHF>
>   Cores per package: 2
>   Logical CPUs per core: 2
> real memory  = 1068105728 (1018 MB)
> Physical memory chunk(s):
> 0x0000000000001000 - 0x000000000009efff, 647168 bytes (158 pages)
> 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages)
> 0x0000000001425000 - 0x000000003e86ffff, 1027911680 bytes (250955 pages)
> avail memory = 1027821568 (980 MB)
> bios32: Found BIOS32 Service Directory header at 0xc00f0000
> bios32: Entry = 0xf0010 (c00f0010)  Rev = 0  Len = 1
> pcibios: PCI BIOS entry at 0xf0000+0x31
> pnpbios: Found PnP BIOS data at 0xc00f6100
> pnpbios: Entry = f0000:78ba  Rev = 1.0
> Other BIOS signatures found:
> APIC: CPU 0 has ACPI ID 1
> MADT: Found IO APIC ID 4, Interrupt 0 at 0xfec00000
> ioapic0: Changing APIC ID to 4
> ioapic0: Routing external 8259A's -> intpin 0
> MADT: Interrupt override: source 0, irq 2
> ioapic0: Routing IRQ 0 -> intpin 2
> MADT: Interrupt override: source 9, irq 9
> ioapic0: intpin 9 trigger: level
> ioapic0 <Version 2.0> irqs 0-23 on motherboard
> cpu0 BSP:
>      ID: 0x00000000   VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff
>   lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff
>   timer: 0x000100ef therm: 0x00010000 err: 0x0001000f pcm: 0x00010000
> wlan: <802.11 Link Layer>
> ath_rate: version 1.2 <SampleRate bit-rate selection algorithm>
> null: <null device, zero device>
> random: <entropy source, Software, Yarrow>
> nfslock: pseudo-device
> io: <I/O>
> kbd: new array size 4
> kbd1 at kbdmux0
> mem: <memory>
> Pentium Pro MTRR support enabled
> ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, 
> RF5413)
> 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 controller detected.
> m
>
Why does FreeBSD think I have a rocket raid controller? This the generic 
kernel.
Is there some way disable this from loading?

When I boot the 7.2 install disk it doesn't say anything about finding 
hptrr:

-- 

"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety."  (Ben Franklin)

"The course of history shows that as a government grows, liberty
decreases."  (Thomas Jefferson)






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