Re: 6.1-RELEASE won't boot on Compaq 1580

2006-07-01 Thread Peter Jeremy
On Sat, 2006-Jul-01 08:02:56 +1000, Peter Jeremy wrote:
I've just acquired a couple of old Compaq Armada laptops.  I can
successfully install 6.1-RELEASE but the system won't boot from
the HDD:  The MBR menu displays but pressing F1 (the FreeBSD
partition) just beeps.  Pressing F3 (the Compaq configuration
partition) works.

For the archives: Rebuilding (and re-installing) boot0 from the
sources on the 6.1-RELEASE CD using the default options (no
/etc/make.conf) fixes the problem.  I have no idea why the boot0 on
the CD doesn't work for me (though the two boot0's are definitely
different).

-- 
Peter Jeremy


pgp7NJlV1QOns.pgp
Description: PGP signature


graid3 configure on 6 stable

2006-07-01 Thread Bradley W. Dutton
Hi,

I just tried 'graid3 configure -a' on a degraded array and received the
following:
panic: lock geom topology not exclusively locked @
/usr/src/sys/geom/raid3/g_raid3_ctl.c:105

Thanks,
Brad

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Bug in ata (ata-all.c) driver

2006-07-01 Thread Anish Mistry
On Friday 30 June 2006 22:01, [EMAIL PROTECTED] wrote:
 I found a little bug (probably) in sys/dev/ata-all.c which somehow
 corrupts device parameters structure. When I first did atacontrol
 list device info about ad0 looked like this:
 Master:  ad0 Maxtor 6Y080P0/YAR41BW0 ATA/ATAPI revision 7
 after I ran atacontrol cap ad0 it printed somewhat messy output
 like having enabled SMART but not supported...
 then I did atacontrol list again and saw that the line about ad0
 have changed to something like this:
 Master:  ad0 W0Maxtor 6Y080P0/YAR41BW0 ATA/ATAPI revision 0
 or similar.

 After some digging and comparing the way IOCATADEVICES and
 IOCATAGPARM work I saw (probably) bogus ata_getparam() call.
 After removing this call to ata_getparam() everything work as
 expected (atleast that's what it looks like for ~30 min run).
 atacontrol cap ad0 shows right results and doesn't screw the
 device parameters. I just hope that this doesn't break something
 else but I doubt it coz it just gets info and doesn't set anything.

 The giant patch is attached. It's agains today's -STABLE.
Don't forget to open a PR for this issue, so it doesn't get lost.

-- 
Anish Mistry


pgpJRSSd52gmv.pgp
Description: PGP signature


6-STABLE on 6 Gb RAM 2 x Xeon 3.0 HTT GDT RAID5 - how?

2006-07-01 Thread ASTESIN
 
Dear FreeBSD gurus,

can anyone point me at a good FM where process of _proper_ setting up
FreeBSD 6-STABLE on 6 Gb RAM machine w/ 2 x Xeon CPU is described? It also
has ICP (former GDT) RAID controller w/RAID-5 configuration (iir0 device).

Purpose: just Apache + mod_perl + MySQL 5.x application server.
Install went fine, system boots, I'm going to try PAE kernel on it. But
somathing makes me doubt that things are going on well...

I.e. I worry about strange messages in dmesg output with regard to ACPI, see
below; will iir0 work with PAE?

Thanks in advanse!
Andrew Stesin

p.s. Personal copy of your reply is greatly appreciated: for some reason a
local mail host hates FreeBSD mailing lists and kills most messages from
them. :(


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-STABLE-200606 #0: Sun Jun  4 11:15:14 UTC 2006
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP
ACPI APIC Table: RCCGCHE
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(TM) CPU 2.66GHz (2665.92-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0xf29  Stepping = 9
 
Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA
,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE
  Features2=0x4400CNTX-ID,b14
  Logical CPUs per core: 2
real memory  = 4077912064 (3889 MB)
avail memory = 3992907776 (3807 MB)
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs  cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
 cpu2 (AP): APIC ID:  6
 cpu3 (AP): APIC ID:  7
ACPI-0698: *** Warning: Type override - [DEB_] had invalid type
(Integer) for Scope operator, changed to (Scope)
ACPI-0698: *** Warning: Type override - [MLIB] had invalid type
(Integer) for Scope operator, changed to (Scope)
ACPI-0698: *** Warning: Type override - [IO__] had invalid type
(Integer) for Scope operator, changed to (Scope)
ACPI-0698: *** Warning: Type override - [DATA] had invalid type (String)
for Scope operator, changed to (Scope)
ACPI-0698: *** Warning: Type override - [SIO_] had invalid type (String)
for Scope operator, changed to (Scope)
ACPI-0698: *** Warning: Type override - [SB__] had invalid type (String)
for Scope operator, changed to (Scope)
ACPI-0698: *** Warning: Type override - [PM__] had invalid type (String)
for Scope operator, changed to (Scope)
ACPI-0698: *** Warning: Type override - [ICNT] had invalid type (String)
for Scope operator, changed to (Scope)
ACPI-0698: *** Warning: Type override - [ACPI] had invalid type (String)
for Scope operator, changed to (Scope)
ACPI-0698: *** Warning: Type override - [IORG] had invalid type (String)
for Scope operator, changed to (Scope)
ACPI-0698: *** Warning: Type override - [SB__] had invalid type (String)
for Scope operator, changed to (Scope)
ACPI-0698: *** Warning: Type override - [PM__] had invalid type (String)
for Scope operator, changed to (Scope)
ACPI-0698: *** Warning: Type override - [SIO_] had invalid type (String)
for Scope operator, changed to (Scope)
ACPI-0698: *** Warning: Type override - [PM__] had invalid type (String)
for Scope operator, changed to (Scope)
ACPI-0698: *** Warning: Type override - [BIOS] had invalid type
(Integer) for Scope operator, changed to (Scope)
ACPI-0698: *** Warning: Type override - [CMOS] had invalid type
(Integer) for Scope operator, changed to (Scope)
ACPI-0698: *** Warning: Type override - [KBC_] had invalid type
(Integer) for Scope operator, changed to (Scope)
ACPI-0698: *** Warning: Type override - [OEM_] had invalid type
(Integer) for Scope operator, changed to (Scope)
MADT: Forcing active-low polarity and level trigger for SCI ioapic0 Version
1.1 irqs 0-15 on motherboard
ioapic1 Version 1.1 irqs 16-31 on motherboard
ioapic2 Version 1.1 irqs 32-47 on motherboard
kbd1 at kbdmux0
acpi0: RCC GCHE on motherboard
acpi0: Power Button (fixed)
Timecounter ACPI-safe frequency 3579545 Hz quality 1000
acpi_timer0: 32-bit timer at 3.579545MHz port 0x508-0x50b on acpi0
cpu0: ACPI CPU on acpi0
acpi_throttle0: ACPI CPU Throttling on cpu0
cpu1: ACPI CPU on acpi0
acpi_throttle1: ACPI CPU Throttling on cpu1
acpi_throttle1: failed to attach P_CNT
device_attach: acpi_throttle1 attach returned 6
cpu2: ACPI CPU on acpi0
acpi_throttle2: ACPI CPU Throttling on cpu2
acpi_throttle2: failed to attach P_CNT
device_attach: acpi_throttle2 attach returned 6
cpu3: ACPI CPU on acpi0
acpi_throttle3: ACPI CPU Throttling on cpu3
acpi_throttle3: failed to attach P_CNT
device_attach: acpi_throttle3 attach returned 6
acpi_button0: Sleep Button on acpi0
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
pci0: display, VGA at device 2.0 (no driver attached)
em0: Intel(R) PRO/1000 Network Connection Version - 3.2.18 port
0x8f00-0x8f3f mem 0xfe5a-0xfe5b irq 30 at device 4.0 on pci0
em0: Ethernet 

High vmstat, filesystem unresponsive then hang 6.1 Stable

2006-07-01 Thread Francisco Reyes
I believe this may be related to the NFS issues mentioned recent, but 
hopefully I may have captured enough info to help others troubleshoot..
I got the header of some ps commands.. and when was about to do full listing 
of the same ps commands to files.. the machine hung up.


The machine is 6.1 Stable around 6-25 ( plus or minus 1 day).


iostat 5 (not much of a load)
 tty da0 cpu
tin tout  KB/t tps  MB/s  us ni sy in id
  0   31 17.71 125  2.17  20  0  5  1 74
  0   26  8.57  23  0.19   0  0  1  0 99
  09 33.73  10  0.34   0  0  0  0 99
  0   21  8.42  18  0.15   0  0  1  1 99
  09 15.92  58  0.90   0  0  0  0 99
  09 15.18   7  0.10   0  0  0  0 99
  0   53 12.93   9  0.11   0  0  1  0 99
  0   31  5.17  58  0.29   0  0  1  1 99

vmstat 5 (very high 'b' column)
procs  memory  page   disk   faults  cpu
r b w avmfre  flt  re  pi  po  fr  sr da0   in   sy  cs us sy id
0 248 2 1410436 110728 1519   2   0   0 1644 264   0 4481 8862 9168 20  6 74
0 248 0 1410436 1107960   0   0   0  13   0   4  700   40 1426  0  1 99
0 248 0 1410436 1107641   0   0   0  39   0  14 1253  722 2615  0  1 99
0 248 0 1410436 1107201   0   0   0  10   0   5  407  396 899  0  1 99
0 248 0 1410436 1107041   0   0   0  60   0  21 2822  360 5695  0  2 98
0 248 0 1410436 1106841   0   0   0  10   0   7  538  434 1166  0  1 99
0 248 0 1410436 1106680   0   0   0  75   0  51  576  163 1026  0  0 99
0 248 0 1410436 1106960   0   0   0  23   0  31 1171  190 2271  0  1 99

vmstat 5
procs  memory  page   disk   faults  cpu
r b w avmfre  flt  re  pi  po  fr  sr da0   in   sy  cs us sy id
0 250 1 1399688 152000 1517   2   0   0 1643 264   0 4479 8853 9163 20  6 74
0 250 0 1399688 1519682   0   0   0  25   0  28 1395  966 2852  0  2 98
0 250 0 1399692 1518921   0   0   0  12   0   6  446  540 986  0  0 99
0 250 2 1399692 1516041   0   0   0  50   0  37  803  675 1611  0  1 99


Don't recall which ps..
411 1   0 ufs ??  Ds 0:04.81 /usr/sbin/mountd -r
37675   650   0 ufs ??  D  0:00.46 /usr/bin/perl 
/data/backaway/mailarchive/client/bin/smtpproxy 127.0.0.1:10026 127.0.0.1:10025 
(perl5.8.7)
37919   650   0 ufs ??  D  0:00.46 /usr/bin/perl 
/data/backaway/mailarchive/client/bin/smtpproxy 127.0.0.1:10026 127.0.0.1:10025 
(perl5.8.7)
39306   650   0 ufs ??  D  0:00.39 /usr/bin/perl 
/data/backaway/mailarchive/client/bin/smtpproxy 127.0.0.1:10026 127.0.0.1:10025 
(perl5.8.7)
40214 386494100 ufs ??  Ds 0:00.00 /usr/local/bin/maildrop -d 
[EMAIL PROTECTED]
40220 329434100 ufs ??  Ds 0:00.00 /usr/local/bin/maildrop -d 
[EMAIL PROTECTED]
40223 332574100 ufs ??  Ds 0:00.00 /usr/local/bin/maildrop -d 
[EMAIL PROTECTED]
40226 329424100 ufs ??  Ds 0:00.00 /usr/local/bin/maildrop -d 
[EMAIL PROTECTED]
40228 331994100 ufs ??  Ds 0:00.00 /usr/local/bin/maildrop -d 
[EMAIL PROTECTED]
40231 385994100 ufs ??  Ds 0:00.00 /usr/local/bin/maildrop -d 
[EMAIL PROTECTED]
40233 328964100 ufs ??  Ds 0:00.00 /usr/local/bin/maildrop -d 
[EMAIL PROTECTED]
40236 332244100 ufs ??  Ds 0:00.00 /usr/local/bin/maildrop -d 
[EMAIL PROTECTED]
40238 328764100 ufs ??  Ds 0:00.00 /usr/local/bin/maildrop -d 
[EMAIL PROTECTED]
40240 329764100 ufs ??  Ds 0:00.00 /usr/local/bin/maildrop -d 
[EMAIL PROTECTED]
40242 355804100 ufs ??  Ds 0:00.00 /usr/local/bin/maildrop -d 
[EMAIL PROTECTED]
40246 355934100 ufs ??  Ds 0:00.00 /usr/local/bin/maildrop -d 
[EMAIL PROTECTED]
40248 329234100 ufs ??  Ds 0:00.00 /usr/local/bin/maildrop -d 
[EMAIL PROTECTED]
40252 355964100 ufs ??  Ds 0:00.01 /usr/local/bin/maildrop -d 
[EMAIL PROTECTED]
40253 298334100 ufs ??  Ds 0:00.01 /usr/local/bin/maildrop -d 
[EMAIL PROTECTED]



ps ax -O ppid,flags,mwchan | awk '$6 ~ /^D/ || $6 == STAT'
 PID  PPID   F MWCHAN  TT  STAT  TIME COMMAND
   2 0 204 -   ??  DL 0:17.68 [g_event]
   3 0 204 -   ??  DL 9:14.85 [g_up]
   4 0 204 -   ??  DL10:50.81 [g_down]
   5 0 204 -   ??  DL 0:02.93 [thread taskq]
   6 0 204 -   ??  DL 0:00.00 [acpi_task0]
   7 0 204 -   ??  DL 0:00.00 [acpi_task1]
   8 0 204 -   ??  DL 0:00.00 [acpi_task2]
   9 0 204 -   ??  DL 0:00.00 [kqueue taskq]
  15 0 204 -   ??  DL 8:47.55 [yarrow]
  27 0 204 -   ??  DL 0:01.72 [fdc0]
  28 0 204 psleep  ??  DL 0:43.74 [pagedaemon]
  29 0 204 psleep  ??  DL 0:00.00 [vmdaemon]
  30 0 20c pgzero  ??  DL 7:35.27 [pagezero]
  31 0 204 psleep  ??  DL 0:57.11 [bufdaemon]
  32 0 204 syncer  ??  DL 8:46.07 [syncer]
  33 0 204 vlruwt  ??  DL 0:28.29 

Re: NFS Locking Issue

2006-07-01 Thread Francisco Reyes

John Hay writes:


I only started to see the lockd problems when upgrading the server side
to FreeBSD 6.x and later. I had various FreeBSD clients, between 4.x
and 7-current and the lockd problem only showed up when upgrading the
server from 5.x to 6.x.


It confirms the same we are experiencing.. constant freezing/locking issues.
I guess no more 6.X for us.. for the foreseable future..
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]