Re: 7.0 - 7.1 crash every two day

2009-05-13 Thread Gabri Mate
On 19:57 Tue 12 May , Mel Flynn wrote:
 On Sunday 10 May 2009 20:51:48 mailingl...@modernbiztonsag.org wrote:
  Dear List,
 
  I've upgraded from source my 7.0-RELEASE to 7.1-RELEASE. It's a general
  purpose server for a small company and it's clients, running web, sql, mail
  and recursive dns. The machine is a Compaq ML350 G2. Version 7.0 was
  running on it for a year now without any problem. After 30 of April I've
  upgraded to 7.1 (I've followed the handbook) and since then nearly every
  two day the machine becomes unreachable except for echorequest. If i try to
  log in in the terminal it just hangs after i give my password.
 
  I'm out of any ideas. Please feel free to ask any more info that I've
  forgotten to provide. Thank You for your help in advance.
 
 If this is a not a GENERIC kernel, did you change scheduler or stuck with 
 SCHED_4BSD in your kernel?
I've just added PF related stuff, so the scheduler is remained the
default.

 -- 
 Mel
 
 !DSPAM:117,4a09ba6e83011202221441!
 

-- 
Gabri Mate
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: 7.0 - 7.1 crash every two day

2009-05-13 Thread Gabri Mate
On 20:51 Sun 10 May , mailingl...@modernbiztonsag.org wrote:
 Dear List,
 
 I've upgraded from source my 7.0-RELEASE to 7.1-RELEASE. It's a general
 purpose server for a small company and it's clients, running web, sql, mail
 and recursive dns. The machine is a Compaq ML350 G2. Version 7.0 was
 running on it for a year now without any problem. After 30 of April I've
 upgraded to 7.1 (I've followed the handbook) and since then nearly every
 two day the machine becomes unreachable except for echorequest. If i try to
 log in in the terminal it just hangs after i give my password.
 
 I'm out of any ideas. Please feel free to ask any more info that I've
 forgotten to provide. Thank You for your help in advance.

It seems that the problem is related to Squirrelmail, particularly to
the file attaching process. Every time a certain account tries to upload
an attachement the above described happens. I'm absolutely sure that the
problem is not FreeBSD related. Something with Squirrelmail or with the
account is wrong. I'm trying to figure this out.

 
 Here's the dmesg:
 
 Copyright (c) 1992-2009 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 7.1-RELEASE-p5 #2: Fri Apr 24 18:44:13 CEST 2009
 r...@lildevil.datawlan:/usr/obj/usr/src/sys/FIREWALL
 Timecounter i8254 frequency 1193182 Hz quality 0
 CPU: Intel Pentium III (996.85-MHz 686-class CPU)
   Origin = GenuineIntel  Id = 0x686  Stepping = 6
  
 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
 real memory  = 536854528 (511 MB)
 avail memory = 511340544 (487 MB)
 kbd1 at kbdmux0
 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
 ACPI Warning (tbfadt-0505): Optional field Gpe1Block has zero address or
 length:0   0/2 [20070320]
 acpi0: COMPAQ RACEBAIT on motherboard
 acpi0: [ITHREAD]
 acpi0: Power Button (fixed)
 unknown: I/O range not supported
 Timecounter ACPI-safe frequency 3579545 Hz quality 850
 acpi_timer0: 24-bit timer at 3.579545MHz port 0x240-0x243 on acpi0
 pcib0: ACPI Host-PCI bridge on acpi0
 pci_link0: apparently invalid index 0
 pci0: ACPI PCI bus on pcib0
 sym0: 1510d port 0x2000-0x20ff mem
 0xc6effc00-0xc6ef,0xc6efe000-0xc6efefff irq 10 at device 1.0 on pci0
 sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking
 sym0: [ITHREAD]
 sym1: 1510d port 0x2400-0x24ff mem
 0xc6efdc00-0xc6efdfff,0xc6efc000-0xc6efcfff irq 11 at device 1.1 on pci0
 sym1: No NVRAM, ID 7, Fast-40, LVD, parity checking
 sym1: [ITHREAD]
 fxp0: Intel 82559 Pro/100 Ethernet port 0x2800-0x283f mem
 0xc6efb000-0xc6efbfff,0xc6d0-0xc6df irq 15 at device 2.0 on pci0
 miibus0: MII bus on fxp0
 inphy0: i82555 10/100 media interface PHY 1 on miibus0
 inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 fxp0: Ethernet address: 00:50:8b:ee:d2:d6
 fxp0: [ITHREAD]
 vgapci0: VGA-compatible display port 0x2c00-0x2cff mem
 0xc500-0xc5ff,0xc6cff000-0xc6cf at device 3.0 on pci0
 pci0: base peripheral at device 4.0 (no driver attached)
 isab0: PCI-ISA bridge at device 15.0 on pci0
 isa0: ISA bus on isab0
 atapci0: ServerWorks ROSB4 UDMA33 controller port
 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x3000-0x300f at device 15.1 on pci0
 ata0: ATA channel 0 on atapci0
 ata0: [ITHREAD]
 ata1: ATA channel 1 on atapci0
 ata1: [ITHREAD]
 pcib1: ACPI Host-PCI bridge on acpi0
 pci3: ACPI PCI bus on pcib1
 ida0: Compaq Smart Array 431 controller port 0x4000-0x40ff mem
 0xc6fff000-0xc6ff irq 5 at device 3.0 on pci3
 ida0: [GIANT-LOCKED]
 ida0: [ITHREAD]
 ida0: drives=1 firm_rev=1.22
 idad0: Compaq Logical Drive on ida0
 idad0: 34727MB (71122560 sectors), blocksize=512
 acpi_tz0: Thermal Zone on acpi0
 atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0
 atkbd0: AT Keyboard irq 1 on atkbdc0
 kbd0 at atkbd0
 atkbd0: [GIANT-LOCKED]
 atkbd0: [ITHREAD]
 fdc0: floppy drive controller port 0x3f2-0x3f5 irq 6 drq 2 on acpi0
 fdc0: [FILTER]
 fd0: 1440-KB 3.5 drive on fdc0 drive 0
 sio0: Standard PC COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
 sio0: type 16550A
 sio0: [FILTER]
 sio1: Standard PC COM port port 0x2f8-0x2ff irq 3 on acpi0
 sio1: type 16550A
 sio1: [FILTER]
 cpu0: ACPI CPU on acpi0
 pmtimer0 on isa0
 orm0: ISA Option ROMs at iomem
 0xc-0xc7fff,0xc8000-0xcbfff,0xe8000-0xedfff,0xee000-0xe pnpid
 ORM on isa0
 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0
 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
 ppbus0: Parallel port bus on ppc0
 ppbus0: [ITHREAD]
 plip0: PLIP network interface on ppbus0
 plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag
 lpt0: Printer on ppbus0
 lpt0: Interrupt-driven port
 ppi0: Parallel I/O on ppbus0
 ppc0: [GIANT-LOCKED]
 ppc0: [ITHREAD]
 sc0: System console at flags 0x100 on isa0
 sc0: VGA 16 virtual consoles, flags=0x300

Re: 7.0 - 7.1 crash every two day

2009-05-13 Thread Maciej Milewski
Wednesday 13 May 2009 19:50:51 Gabri Mate napisał(a):
 It seems that the problem is related to Squirrelmail, particularly to
 the file attaching process. Every time a certain account tries to upload
 an attachement the above described happens. I'm absolutely sure that the
 problem is not FreeBSD related. Something with Squirrelmail or with the
 account is wrong. I'm trying to figure this out.
Is there any chance that you are using lighttpd as your web server?
 
-- 
Regards,
Maciej Milewski
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: 7.0 - 7.1 crash every two day

2009-05-13 Thread Mel Flynn
On Wednesday 13 May 2009 19:46:26 Gabri Mate wrote:
 On 19:57 Tue 12 May , Mel Flynn wrote:
  On Sunday 10 May 2009 20:51:48 mailingl...@modernbiztonsag.org wrote:
   Dear List,
  
   I've upgraded from source my 7.0-RELEASE to 7.1-RELEASE. It's a general
   purpose server for a small company and it's clients, running web, sql,
   mail and recursive dns. The machine is a Compaq ML350 G2. Version 7.0
   was running on it for a year now without any problem. After 30 of April
   I've upgraded to 7.1 (I've followed the handbook) and since then nearly
   every two day the machine becomes unreachable except for echorequest.
   If i try to log in in the terminal it just hangs after i give my
   password.
  
   I'm out of any ideas. Please feel free to ask any more info that I've
   forgotten to provide. Thank You for your help in advance.
 
  If this is a not a GENERIC kernel, did you change scheduler or stuck with
  SCHED_4BSD in your kernel?

 I've just added PF related stuff, so the scheduler is remained the
 default.

Just FYI: unless you use include GENERIC and added pf, rather then copy 
GENERIC to MYKERNEL, you're running with SCHED_4BSD, the default has changed 
in 7.1.
-- 
Mel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: 7.0 - 7.1 crash every two day

2009-05-13 Thread Gabri Mate
On 22:29 Wed 13 May , Mel Flynn wrote:
 On Wednesday 13 May 2009 19:46:26 Gabri Mate wrote:
  On 19:57 Tue 12 May , Mel Flynn wrote:
   On Sunday 10 May 2009 20:51:48 mailingl...@modernbiztonsag.org wrote:
Dear List,
   
I've upgraded from source my 7.0-RELEASE to 7.1-RELEASE. It's a general
purpose server for a small company and it's clients, running web, sql,
mail and recursive dns. The machine is a Compaq ML350 G2. Version 7.0
was running on it for a year now without any problem. After 30 of April
I've upgraded to 7.1 (I've followed the handbook) and since then nearly
every two day the machine becomes unreachable except for echorequest.
If i try to log in in the terminal it just hangs after i give my
password.
   
I'm out of any ideas. Please feel free to ask any more info that I've
forgotten to provide. Thank You for your help in advance.
  
   If this is a not a GENERIC kernel, did you change scheduler or stuck with
   SCHED_4BSD in your kernel?
 
  I've just added PF related stuff, so the scheduler is remained the
  default.
 
 Just FYI: unless you use include GENERIC and added pf, rather then copy 
 GENERIC to MYKERNEL, you're running with SCHED_4BSD, the default has changed 
 in 7.1.
Hm, You've got the point. I've just copied over the kernel config from
7.0 to 7.1, made a diff with GENERIC but somehow I've missed the
scheduler change. I'm building a new kernel now.

Could this be related with the Squirrelmail problem I've posted earlier?

 -- 
 Mel
 
 !DSPAM:117,4a0b2dc183011557416561!
 

-- 
Gabri Mate
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: 7.0 - 7.1 crash every two day

2009-05-13 Thread Gabri Mate
On 23:59 Wed 13 May , Maciej Milewski wrote:
 Wednesday 13 May 2009 23:15:46 napisałeś(-łaś):
  On 22:04 Wed 13 May , Maciej Milewski wrote:
   Wednesday 13 May 2009 19:50:51 Gabri Mate napisał(a):
It seems that the problem is related to Squirrelmail, particularly to
the file attaching process. Every time a certain account tries to
upload an attachement the above described happens. I'm absolutely sure
that the problem is not FreeBSD related. Something with Squirrelmail or
with the account is wrong. I'm trying to figure this out.
  
   Is there any chance that you are using lighttpd as your web server?
 
  You bet! I'm using the latest one from ports. I've turned off file
  uploading in php to see what happens in the coming days. Is there
  something with lighttpd regarding this problem?
 
  Thank You!
 :)
 You should set this in lighttpd.conf: 
 server.network-backend = write
 I don't have right now link for info why this should be set this way but if 
 memory serves me right it is specific for FreeBSD because of problem with 
 sendfile working differently or not working at all. You should find some info 
 on lighttpd bugs page.

I'll search for it.
It was set to freebsd-sendfile, and I've changed it as You've
suggested.

Thank You for the information!

 
 -- 
 Pozdrawiam,
 Maciej Milewski
 
 
 !DSPAM:117,4a0b42ba83011575916308!

-- 
Gabri Mate
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: 7.0 - 7.1 crash every two day

2009-05-13 Thread Gabri Mate
On 23:59 Wed 13 May , Maciej Milewski wrote:
 Wednesday 13 May 2009 23:15:46 napisałeś(-łaś):
  On 22:04 Wed 13 May , Maciej Milewski wrote:
   Wednesday 13 May 2009 19:50:51 Gabri Mate napisał(a):
It seems that the problem is related to Squirrelmail, particularly to
the file attaching process. Every time a certain account tries to
upload an attachement the above described happens. I'm absolutely sure
that the problem is not FreeBSD related. Something with Squirrelmail or
with the account is wrong. I'm trying to figure this out.
  
   Is there any chance that you are using lighttpd as your web server?
 
  You bet! I'm using the latest one from ports. I've turned off file
  uploading in php to see what happens in the coming days. Is there
  something with lighttpd regarding this problem?
 
  Thank You!
 :)
 You should set this in lighttpd.conf: 
 server.network-backend = write
 I don't have right now link for info why this should be set this way but if 
 memory serves me right it is specific for FreeBSD because of problem with 
 sendfile working differently or not working at all. You should find some info 
 on lighttpd bugs page.
I've found this link describing exactly what i was experiencing. 

http://lists.freebsd.org/pipermail/freebsd-questions/2008-September/182872.html

I hope that the problem will go away. :)

 
 -- 
 Pozdrawiam,
 Maciej Milewski
 
 
 !DSPAM:117,4a0b42ba83011575916308!

-- 
Gabri Mate
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: 7.0 - 7.1 crash every two day

2009-05-12 Thread Mel Flynn
On Sunday 10 May 2009 20:51:48 mailingl...@modernbiztonsag.org wrote:
 Dear List,

 I've upgraded from source my 7.0-RELEASE to 7.1-RELEASE. It's a general
 purpose server for a small company and it's clients, running web, sql, mail
 and recursive dns. The machine is a Compaq ML350 G2. Version 7.0 was
 running on it for a year now without any problem. After 30 of April I've
 upgraded to 7.1 (I've followed the handbook) and since then nearly every
 two day the machine becomes unreachable except for echorequest. If i try to
 log in in the terminal it just hangs after i give my password.

 I'm out of any ideas. Please feel free to ask any more info that I've
 forgotten to provide. Thank You for your help in advance.

If this is a not a GENERIC kernel, did you change scheduler or stuck with 
SCHED_4BSD in your kernel?
-- 
Mel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: 7.0 - 7.1 crash every two day

2009-05-11 Thread mojo fms
Have you tried: freebsd-update IDS ?  I am assuming you did the
freebsd-update to update the machine but if not maybe run through
mergemaster and another rebuild of the world and kernel to make sure that
none of the files got an error from the build.

On Sun, May 10, 2009 at 11:51 AM, mailingl...@modernbiztonsag.org wrote:

 Dear List,

 I've upgraded from source my 7.0-RELEASE to 7.1-RELEASE. It's a general
 purpose server for a small company and it's clients, running web, sql, mail
 and recursive dns. The machine is a Compaq ML350 G2. Version 7.0 was
 running on it for a year now without any problem. After 30 of April I've
 upgraded to 7.1 (I've followed the handbook) and since then nearly every
 two day the machine becomes unreachable except for echorequest. If i try to
 log in in the terminal it just hangs after i give my password.

 I'm out of any ideas. Please feel free to ask any more info that I've
 forgotten to provide. Thank You for your help in advance.

 Here's the dmesg:

 Copyright (c) 1992-2009 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 7.1-RELEASE-p5 #2: Fri Apr 24 18:44:13 CEST 2009
r...@lildevil.datawlan:/usr/obj/usr/src/sys/FIREWALL
 Timecounter i8254 frequency 1193182 Hz quality 0
 CPU: Intel Pentium III (996.85-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0x686  Stepping = 6


 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
 real memory  = 536854528 (511 MB)
 avail memory = 511340544 (487 MB)
 kbd1 at kbdmux0
 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
 ACPI Warning (tbfadt-0505): Optional field Gpe1Block has zero address or
 length:0   0/2 [20070320]
 acpi0: COMPAQ RACEBAIT on motherboard
 acpi0: [ITHREAD]
 acpi0: Power Button (fixed)
 unknown: I/O range not supported
 Timecounter ACPI-safe frequency 3579545 Hz quality 850
 acpi_timer0: 24-bit timer at 3.579545MHz port 0x240-0x243 on acpi0
 pcib0: ACPI Host-PCI bridge on acpi0
 pci_link0: apparently invalid index 0
 pci0: ACPI PCI bus on pcib0
 sym0: 1510d port 0x2000-0x20ff mem
 0xc6effc00-0xc6ef,0xc6efe000-0xc6efefff irq 10 at device 1.0 on pci0
 sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking
 sym0: [ITHREAD]
 sym1: 1510d port 0x2400-0x24ff mem
 0xc6efdc00-0xc6efdfff,0xc6efc000-0xc6efcfff irq 11 at device 1.1 on pci0
 sym1: No NVRAM, ID 7, Fast-40, LVD, parity checking
 sym1: [ITHREAD]
 fxp0: Intel 82559 Pro/100 Ethernet port 0x2800-0x283f mem
 0xc6efb000-0xc6efbfff,0xc6d0-0xc6df irq 15 at device 2.0 on pci0
 miibus0: MII bus on fxp0
 inphy0: i82555 10/100 media interface PHY 1 on miibus0
 inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 fxp0: Ethernet address: 00:50:8b:ee:d2:d6
 fxp0: [ITHREAD]
 vgapci0: VGA-compatible display port 0x2c00-0x2cff mem
 0xc500-0xc5ff,0xc6cff000-0xc6cf at device 3.0 on pci0
 pci0: base peripheral at device 4.0 (no driver attached)
 isab0: PCI-ISA bridge at device 15.0 on pci0
 isa0: ISA bus on isab0
 atapci0: ServerWorks ROSB4 UDMA33 controller port
 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x3000-0x300f at device 15.1 on pci0
 ata0: ATA channel 0 on atapci0
 ata0: [ITHREAD]
 ata1: ATA channel 1 on atapci0
 ata1: [ITHREAD]
 pcib1: ACPI Host-PCI bridge on acpi0
 pci3: ACPI PCI bus on pcib1
 ida0: Compaq Smart Array 431 controller port 0x4000-0x40ff mem
 0xc6fff000-0xc6ff irq 5 at device 3.0 on pci3
 ida0: [GIANT-LOCKED]
 ida0: [ITHREAD]
 ida0: drives=1 firm_rev=1.22
 idad0: Compaq Logical Drive on ida0
 idad0: 34727MB (71122560 sectors), blocksize=512
 acpi_tz0: Thermal Zone on acpi0
 atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0
 atkbd0: AT Keyboard irq 1 on atkbdc0
 kbd0 at atkbd0
 atkbd0: [GIANT-LOCKED]
 atkbd0: [ITHREAD]
 fdc0: floppy drive controller port 0x3f2-0x3f5 irq 6 drq 2 on acpi0
 fdc0: [FILTER]
 fd0: 1440-KB 3.5 drive on fdc0 drive 0
 sio0: Standard PC COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
 sio0: type 16550A
 sio0: [FILTER]
 sio1: Standard PC COM port port 0x2f8-0x2ff irq 3 on acpi0
 sio1: type 16550A
 sio1: [FILTER]
 cpu0: ACPI CPU on acpi0
 pmtimer0 on isa0
 orm0: ISA Option ROMs at iomem
 0xc-0xc7fff,0xc8000-0xcbfff,0xe8000-0xedfff,0xee000-0xe pnpid
 ORM on isa0
 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0
 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
 ppbus0: Parallel port bus on ppc0
 ppbus0: [ITHREAD]
 plip0: PLIP network interface on ppbus0
 plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag
 lpt0: Printer on ppbus0
 lpt0: Interrupt-driven port
 ppi0: Parallel I/O on ppbus0
 ppc0: [GIANT-LOCKED]
 ppc0: [ITHREAD]
 sc0: System console at flags 0x100 on isa0
 sc0: VGA 16 virtual consoles, flags=0x300
 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
 

7.0 - 7.1 crash every two day

2009-05-10 Thread mailinglist
Dear List,

I've upgraded from source my 7.0-RELEASE to 7.1-RELEASE. It's a general
purpose server for a small company and it's clients, running web, sql, mail
and recursive dns. The machine is a Compaq ML350 G2. Version 7.0 was
running on it for a year now without any problem. After 30 of April I've
upgraded to 7.1 (I've followed the handbook) and since then nearly every
two day the machine becomes unreachable except for echorequest. If i try to
log in in the terminal it just hangs after i give my password.

I'm out of any ideas. Please feel free to ask any more info that I've
forgotten to provide. Thank You for your help in advance.

Here's the dmesg:

Copyright (c) 1992-2009 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 7.1-RELEASE-p5 #2: Fri Apr 24 18:44:13 CEST 2009
r...@lildevil.datawlan:/usr/obj/usr/src/sys/FIREWALL
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: Intel Pentium III (996.85-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0x686  Stepping = 6
 
Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
real memory  = 536854528 (511 MB)
avail memory = 511340544 (487 MB)
kbd1 at kbdmux0
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
ACPI Warning (tbfadt-0505): Optional field Gpe1Block has zero address or
length:0   0/2 [20070320]
acpi0: COMPAQ RACEBAIT on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
unknown: I/O range not supported
Timecounter ACPI-safe frequency 3579545 Hz quality 850
acpi_timer0: 24-bit timer at 3.579545MHz port 0x240-0x243 on acpi0
pcib0: ACPI Host-PCI bridge on acpi0
pci_link0: apparently invalid index 0
pci0: ACPI PCI bus on pcib0
sym0: 1510d port 0x2000-0x20ff mem
0xc6effc00-0xc6ef,0xc6efe000-0xc6efefff irq 10 at device 1.0 on pci0
sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking
sym0: [ITHREAD]
sym1: 1510d port 0x2400-0x24ff mem
0xc6efdc00-0xc6efdfff,0xc6efc000-0xc6efcfff irq 11 at device 1.1 on pci0
sym1: No NVRAM, ID 7, Fast-40, LVD, parity checking
sym1: [ITHREAD]
fxp0: Intel 82559 Pro/100 Ethernet port 0x2800-0x283f mem
0xc6efb000-0xc6efbfff,0xc6d0-0xc6df irq 15 at device 2.0 on pci0
miibus0: MII bus on fxp0
inphy0: i82555 10/100 media interface PHY 1 on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp0: Ethernet address: 00:50:8b:ee:d2:d6
fxp0: [ITHREAD]
vgapci0: VGA-compatible display port 0x2c00-0x2cff mem
0xc500-0xc5ff,0xc6cff000-0xc6cf at device 3.0 on pci0
pci0: base peripheral at device 4.0 (no driver attached)
isab0: PCI-ISA bridge at device 15.0 on pci0
isa0: ISA bus on isab0
atapci0: ServerWorks ROSB4 UDMA33 controller port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x3000-0x300f at device 15.1 on pci0
ata0: ATA channel 0 on atapci0
ata0: [ITHREAD]
ata1: ATA channel 1 on atapci0
ata1: [ITHREAD]
pcib1: ACPI Host-PCI bridge on acpi0
pci3: ACPI PCI bus on pcib1
ida0: Compaq Smart Array 431 controller port 0x4000-0x40ff mem
0xc6fff000-0xc6ff irq 5 at device 3.0 on pci3
ida0: [GIANT-LOCKED]
ida0: [ITHREAD]
ida0: drives=1 firm_rev=1.22
idad0: Compaq Logical Drive on ida0
idad0: 34727MB (71122560 sectors), blocksize=512
acpi_tz0: Thermal Zone on acpi0
atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0
atkbd0: AT Keyboard irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
fdc0: floppy drive controller port 0x3f2-0x3f5 irq 6 drq 2 on acpi0
fdc0: [FILTER]
fd0: 1440-KB 3.5 drive on fdc0 drive 0
sio0: Standard PC COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A
sio0: [FILTER]
sio1: Standard PC COM port port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
sio1: [FILTER]
cpu0: ACPI CPU on acpi0
pmtimer0 on isa0
orm0: ISA Option ROMs at iomem
0xc-0xc7fff,0xc8000-0xcbfff,0xe8000-0xedfff,0xee000-0xe pnpid
ORM on isa0
ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
ppbus0: Parallel port bus on ppc0
ppbus0: [ITHREAD]
plip0: PLIP network interface on ppbus0
plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag
lpt0: Printer on ppbus0
lpt0: Interrupt-driven port
ppi0: Parallel I/O on ppbus0
ppc0: [GIANT-LOCKED]
ppc0: [ITHREAD]
sc0: System console at flags 0x100 on isa0
sc0: VGA 16 virtual consoles, flags=0x300
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
Timecounter TSC frequency 996851056 Hz quality 800
Timecounters tick every 1.000 msec
acd0: CDROM GCR-8523B/1.03 at ata0-master PIO4
Waiting 5 seconds for SCSI devices to settle
GEOM_LABEL: Label for provider idad0s3 is msdosfs/SYSTEMCFG.
Trying to mount root from ufs:/dev/idad0s1a
WARNING: / was not properly dismounted
WARNING: /tmp was not properly dismounted
WARNING: /usr was not properly dismounted
WARNING: /usr/home was not