Re: FreeBSD 6.1 shutting down.

[Kris Kennaway]

On Thu, Sep 14, 2006 at 07:29:13PM +, Marwan Sultan wrote:
> hello Lowell,
> 
>   thank you for your reply, i wish you could find some solution for me
>   i tried to google the net, and found many results for atapci1: failed to 
> enable memory mapping!
>   but most with no solutions.

I doubt it's the cause of the problems; most likely you have some
other failing hardware component (bad memory, power supply, etc).
Check the archives for extensive discussion.

Kris

P.S. Don't top-post, it spoils the logical flow of the thread.


pgpvoBONOcdau.pgp
Description: PGP signature

Re: FreeBSD 6.1 shutting down.

[Marwan Sultan]

hello Lowell,

  thank you for your reply, i wish you could find some solution for me
  i tried to google the net, and found many results for atapci1: failed to 
enable memory mapping!

  but most with no solutions.

  here is the dmesg,



Copyright (c) 1992-2006 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 6.1-RELEASE #0: Thu Aug 17 07:53:54 AST 2006
   [EMAIL PROTECTED]:/usr/src/sys/i386/compile/MYKERNEL
ACPI APIC Table: 
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) 4 CPU 3.40GHz (3406.70-MHz 686-class CPU)
 Origin = "GenuineIntel"  Id = 0xf41  Stepping = 1
 
Features=0xbfebfbff

 Features2=0x641d>
 AMD Features=0x2010
 Logical CPUs per core: 2
real memory  = 1063669760 (1014 MB)
avail memory = 1031925760 (984 MB)
ioapic0: Changing APIC ID to 2
ioapic0  irqs 0-23 on motherboard
kbd1 at kbdmux0
acpi0:  on motherboard
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
cpu0:  on acpi0
acpi_button0:  on acpi0
pcib0:  port 0xcf8-0xcff on acpi0
pci0:  on pcib0
pci0:  at device 2.0 (no driver attached)
pci0:  at device 27.0 (no driver attached)
pcib1:  at device 28.0 on pci0
pci1:  on pcib1
pcib2:  at device 28.2 on pci0
pci2:  on pcib2
pcib3:  at device 28.3 on pci0
pci3:  on pcib3
uhci0:  port 0x2080-0x209f irq 23 at device 
29.0 on pci0

uhci0: [GIANT-LOCKED]
usb0:  on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1:  port 0x2060-0x207f irq 19 at device 
29.1 on pci0

uhci1: [GIANT-LOCKED]
usb1:  on uhci1
usb1: USB revision 1.0
uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2:  port 0x2040-0x205f irq 18 at device 
29.2 on pci0

uhci2: [GIANT-LOCKED]
usb2:  on uhci2
usb2: USB revision 1.0
uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhci3:  port 0x2020-0x203f irq 16 at device 
29.3 on pci0

uhci3: [GIANT-LOCKED]
usb3:  on uhci3
usb3: USB revision 1.0
uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
ehci0:  mem 0x501c4000-0x501c43ff 
irq 23 at device 29.7 on pci0

ehci0: [GIANT-LOCKED]
usb4: EHCI version 1.0
usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3
usb4:  on ehci0
usb4: USB revision 2.0
uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub4: 8 ports with 8 removable, self powered
pcib4:  at device 30.0 on pci0
pci4:  on pcib4
vr0:  port 0x1000-0x10ff mem 
0x50001000-0x500010ff irq 22 at device 1.0 on pci4

miibus0:  on vr0
ukphy0:  on miibus0
ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
vr0: Ethernet address: 00:15:e9:a5:ad:17
fxp0:  port 0x1100-0x113f mem 
0x5000-0x5fff irq 20 at device 8.0 on pci4

miibus1:  on fxp0
inphy0:  on miibus1
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp0: Ethernet address: 00:16:76:68:fa:53
isab0:  at device 31.0 on pci0
isa0:  on isab0
atapci0:  port 
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x20b0-0x20bf irq 18 at device 31.1 on 
pci0

ata0:  on atapci0
ata1:  on atapci0
atapci1:  port 
0x20c8-0x20cf,0x20ec-0x20ef,0x20c0-0x20c7,0x20e8-0x20eb,0x20a0-0x20af irq 19 
at device 31.2 on pci0

atapci1: failed to enable memory mapping!
ata2:  on atapci1
ata3:  on atapci1
pci0:  at device 31.3 (no driver attached)
ppc0:  port 0x378-0x37f,0x778-0x77f irq 7 on 
acpi0

ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/8 bytes threshold
ppbus0:  on ppc0
plip0:  on ppbus0
lpt0:  on ppbus0
lpt0: Interrupt-driven port
ppi0:  on ppbus0
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on 
acpi0

sio0: type 16550A
pmtimer0 on isa0
orm0:  at iomem 0xcb000-0xcc7ff,0xcc800-0xcd7ff on isa0
atkbdc0:  at port 0x60,0x64 on isa0
atkbd0:  irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
sc0:  at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0:  at port 0x3c0-0x3df iomem 0xa-0xb on isa0
Timecounter "TSC" frequency 3406697941 Hz quality 800
Timecounters tick every 1.000 msec
ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, 
default to accept, logging unlimited

ad6: 152627MB  at ata3-master SATA150
Trying to mount root from ufs:/dev/ad6s1a
ukbd0: CHESEN USB Keyboard, rev 1.10/1.10, addr 2, iclass 3/1
kbd2 at ukbd0
uhid0: CHESEN USB Keyboard, rev 1.10/1.10, addr 2, iclass 3/1


> Hello everyone,
>
>  I'm On FreeBSD 6.1R, the box is intel945 extra Dlink NIC
>  P4.3 1G DDR2, 160GB sata.
>
>  running Freeradius, chillispot, MySql 4.1, apache2.
>  acting as NAT and hotspot login.
>
>  there is two diffren

Re: FreeBSD 6.1 shutting down.

[Lowell Gilbert]

"Marwan Sultan" <[EMAIL PROTECTED]> writes:

> Hello everyone,
>
>  I'm On FreeBSD 6.1R, the box is intel945 extra Dlink NIC
>  P4.3 1G DDR2, 160GB sata.
>
>  running Freeradius, chillispot, MySql 4.1, apache2.
>  acting as NAT and hotspot login.
>
>  there is two diffrent servers with the same specifications.
>
>  Its was working fine starting from day 1 to day 5 uptime.
>  and the other box from day 1 to 3,
>  with almost 30 users as hotspot login.
>
>  On day 5, it had a sudden shutdown, some users called me reported
> there is no internet
>  when i checked the server i discovered the box is off power.
>
>  The second box after 3 days had the same problem.
>
>  when i started the power, for both...again it start to work in a goodway.
>
>  I was shocked.. checked messages, dmesg, and almost everything I
> couldnot find any clue
>  in logs.. so
>  question 1, How would i check what happened for this power shutting down?

Did the filesystems come up clean?  That would be a hint that the
kernel shut down on purpose.  [I wouldn't expect it, since you said
there were no hints in the logs, but it's worth checking.

Next step is probably to set up a serial console and see if anything
useful is showing up there when the shutdown occurs.  Also try to get
and track any information about system temperature, voltage, and so
on; these kinds of phantom powerdowns are usually power trouble in my
experience.  

>  2)
>  in my dmesg and since i was settingup the box, the following error
> was always coming and on
>  single line
>
>  atapci1: failed to enable memory mapping!

I can't find that message in the -STABLE sources.  Admittedly, it was
a very quick search, but are you sure you copied it exactly?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"