Re: FreeBSD 7.2-STABLE boot freeze

2009-09-28 Thread kama


On Fri, 25 Sep 2009, Andriy Gapon wrote:

 on 25/09/2009 12:04 kama said the following:
  On Thu, 24 Sep 2009, kama wrote:
 
  I am currently building the source on another machine. Lets see if it will
  build it any better.
 
  Building the the world on another machine and install it on the DL385
  machine made it also to freeze.

 Did you still get the message about unresolved symbol?

I did not try with ACPI_DEBUG enabled.

Another week, so I can start testing again...

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


Re: FreeBSD 7.2-STABLE boot freeze

2009-09-28 Thread Andriy Gapon
on 28/09/2009 10:21 kama said the following:
 
 On Fri, 25 Sep 2009, Andriy Gapon wrote:
 
 on 25/09/2009 12:04 kama said the following:
 On Thu, 24 Sep 2009, kama wrote:

 I am currently building the source on another machine. Lets see if it will
 build it any better.
 Building the the world on another machine and install it on the DL385
 machine made it also to freeze.
 Did you still get the message about unresolved symbol?
 
 I did not try with ACPI_DEBUG enabled.
 
 Another week, so I can start testing again...

I did not ask that :-)
I asked -  when you got your latest freeze, did you see that 'unresolved'
message or not?


-- 
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: 7.2-release/amd64: panic, spin lock held too long

2009-09-28 Thread Attilio Rao
2009/9/28 C. C. Tang hiyo...@gmail.com:
 C. C. Tang wrote:

 Attilio Rao wrote:

 2009/9/22 C. C. Tang hiyo...@gmail.com:

 I have patched the sched_ule.c and did a make buildkernel  make
 installkernel (is buildworld and installworld necessary?), rebooted
 and
 the
 machine is running now.
 I will post here again if there is any update.

 My server is up for 3.5 days now with HyperThreading  powerd enabled.
 No panic occured yet.

 Usually how long did it take to panic?

 Attilio


 It is rather random, but will usually panic within one week.
 Anyway my server will keep running and I will report if it has any
 problem.

 Thanks,
 C.C.

 My server is up for 9.5 days now. Seems working fine.

The patch has been committed to STABLE_7 as well.

Attilio


-- 
Peace can only be achieved by understanding - A. Einstein
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: glabel+gmirror (8.0-RC1 problem)

2009-09-28 Thread Pawel Jakub Dawidek
On Sun, Sep 27, 2009 at 10:37:25PM +0200, Oliver Lehmann wrote:
 Hi,
 
 that gmirror together with glabel cannot be used looks like a problem
 introduced with 8.0-RC1 to me.
[...]

Does anything change between you upgrade from BETA3 and RC1? For example
gmirror was compiled into the kernel before and now is loaded as module
or something similar?

Could you test this patch:

http://people.freebsd.org/~pjd/patches/improved_taste.patch

-- 
Pawel Jakub Dawidek   http://www.wheel.pl
p...@freebsd.org   http://www.FreeBSD.org
FreeBSD committer Am I Evil? Yes, I Am!


pgpSxWihIdQz0.pgp
Description: PGP signature


Re: locate(1) ZFS addition

2009-09-28 Thread Gavin Atkinson
On Sun, 2009-09-27 at 23:37 -0400, CmdLnKid wrote:
 I just came across what I believe to be just a oversight on locate(1). By 
 default as stated in its locate.rc file in /etc it states that the default 
 file systems that will be searched is ufs ext2fs. Would it be wise to have 
 the 
 default be ufs zfs xfs ext2fs ? or some other combination.

It appears to be a little more confused than that.  In 8.x and 7.2, the
list of filesystems that are actually searched are ufs ext2fs zfs.
The comment in the default /etc/locate.rc lists those, and also xfs.

The real problem seems to be that /etc/locate.rc seems to be missed by
mergemaster, and so updates to it aren't being picked up.  However, from
a quick inspection, I can't see why.

I think it would be a good idea to file a PR so that this doesn't get
lost.

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


Re: glabel+gmirror (8.0-RC1 problem)

2009-09-28 Thread Dag-Erling Smørgrav
Pawel Jakub Dawidek p...@freebsd.org writes:
 Oliver Lehmann lehm...@ans-netz.de writes:
  that gmirror together with glabel cannot be used looks like a
  problem introduced with 8.0-RC1 to me.
 Does anything change between you upgrade from BETA3 and RC1?  For
 example gmirror was compiled into the kernel before and now is loaded
 as module or something similar?

Looks like the same issue I mentioned to you (pjd) last night.  In my
case, it was an upgrade from a week-old head to last night's head, and
the only change was that the new kernel had NFS compiled in.  Both the
old and the new kernel loaded geom_label and geom_mirror as modules.

 Could you test this patch:

   http://people.freebsd.org/~pjd/patches/improved_taste.patch

Works for me.

DES
-- 
Dag-Erling Smørgrav - d...@des.no
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: locate(1) ZFS addition

2009-09-28 Thread Ruslan Ermilov
On Sun, Sep 27, 2009 at 11:37:14PM -0400, CmdLnKid wrote:
 I just came across what I believe to be just a oversight on locate(1). By 
 default as stated in its locate.rc file in /etc it states that the default 
 file systems that will be searched is ufs ext2fs.
 
 Would it be wise to have the 
 default be ufs zfs xfs ext2fs ? or some other combination.
 
 PS: Should a PR be filed for this ?

The default list is actually ufs ext2fs zfs for RELENG_7 now,
it's just that the comment hasn't been updated.  For HEAD and
RELENG_8, the default list contains all local file systems that
are not synthetic, loopback mounts, or read-only, according to
lsvfs.


Cheers,
-- 
Ruslan Ermilov
r...@freebsd.org
FreeBSD committer
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: PATA disks/DVD not detected on ATI IXP 700 - cannot boot (dmesg attached)

2009-09-28 Thread Dennis Chikin
 Is it means that all works with this patch?

No visible ata-specific faults encountered after loading the kernel.

 Can you show dmesg from patched system?


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.2-RELEASE-p3 #0: Sun Sep 27 23:57:27 YEKST 2009
r...@hq.sps.org:/work/usr/obj/work/usr/src/sys/GENERIC
Preloaded elf kernel /boot/kernel/kernel at 0xc0882000.
Preloaded elf module /boot/kernel/acpi.ko at 0xc0882188.
Calibrating clock(s) ... i8254 clock: 1193131 Hz
CLK_USE_I8254_CALIBRATION not specified - using default frequency
Timecounter i8254 frequency 1193182 Hz quality 0
Calibrating TSC clock ... TSC clock: 3100300862 Hz
CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ (3100.30-MHz 686-class CPU)
  Origin = AuthenticAMD  Id = 0x60fb2  Stepping = 2
  
Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT
  Features2=0x2001SSE3,CX16
  AMD Features=0xea500800SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow!
  AMD Features2=0x11fLAHF,CMP,SVM,ExtAPIC,CR8,Prefetch
  TSC: P-state invariant
  Cores per package: 2
Data TLB: 32 entries, fully associative
Instruction TLB: 32 entries, fully associative
L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative
L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative
L2 internal cache: 512 kbytes, 64 bytes/line, 1 lines/tag, 8-way associative
real memory  = 1610285056 (1535 MB)
Physical memory chunk(s):
0x1000 - 0x0009efff, 647168 bytes (158 pages)
0x0010 - 0x003f, 3145728 bytes (768 pages)
0x00c25000 - 0x5e460fff, 1568915456 bytes (383036 pages)
avail memory = 1568407552 (1495 MB)
Table 'FACP' at 0x5ffb0290
Table 'APIC' at 0x5ffb0390
MADT: Found table at 0x5ffb0390
MP Configuration Table version 1.4 found at 0xc00fcd20
APIC: Using the MADT enumerator.
MADT: Found CPU APIC ID 0 ACPI ID 1: enabled
SMP: Added CPU 0 (AP)
MADT: Found CPU APIC ID 1 ACPI ID 2: enabled
SMP: Added CPU 1 (AP)
MADT: Found CPU APIC ID 130 ACPI ID 3: disabled
MADT: Found CPU APIC ID 131 ACPI ID 4: disabled
ACPI APIC Table: 092208 APIC1629
INTR: Adding local APIC 1 as a target
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
bios32: Found BIOS32 Service Directory header at 0xc00f
bios32: Entry = 0xf0010 (c00f0010)  Rev = 0  Len = 1
pcibios: PCI BIOS entry at 0xf+0x31
pnpbios: Found PnP BIOS data at 0xc00f4ea0
pnpbios: Entry = f:660a  Rev = 1.0
Other BIOS signatures found:
APIC: CPU 0 has ACPI ID 1
APIC: CPU 1 has ACPI ID 2
ULE: setup cpu group 0
ULE: setup cpu 0
ULE: adding cpu 0 to group 0: cpus 1 mask 0x1
ULE: setup cpu group 1
ULE: setup cpu 1
ULE: adding cpu 1 to group 1: cpus 1 mask 0x2
ACPI: RSDP @ 0x0xf9d90/0x0024 (v  2 ACPIAM)
ACPI: XSDT @ 0x0x5ffb0100/0x0054 (v  1 092208 XSDT1629 0x20080922 MSFT
0x0097)
ACPI: FACP @ 0x0x5ffb0290/0x00F4 (v  3 092208 FACP1629 0x20080922 MSFT
0x0097)
ACPI: DSDT @ 0x0x5ffb0440/0x7214 (v  1  A78GM A78GM922 0x0004 INTL
0x20051117)
ACPI: FACS @ 0x0x5ffbe000/0x0040
ACPI: APIC @ 0x0x5ffb0390/0x006C (v  1 092208 APIC1629 0x20080922 MSFT
0x0097)
ACPI: MCFG @ 0x0x5ffb0400/0x003C (v  1 092208 OEMMCFG  0x20080922 MSFT
0x0097)
ACPI: OEMB @ 0x0x5ffbe040/0x0071 (v  1 092208 OEMB1629 0x20080922 MSFT
0x0097)
ACPI: HPET @ 0x0x5ffb7660/0x0038 (v  1 092208 OEMHPET  0x20080922 MSFT
0x0097)
ACPI: SSDT @ 0x0x5ffb76a0/0x0350 (v  1 A M I  POWERNOW 0x0001 AMD
0x0001)
MADT: Found IO APIC ID 2, Interrupt 0 at 0xfec0
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: intpin 9 polarity: low
ioapic0 Version 2.1 irqs 0-23 on motherboard
cpu0 BSP:
 ID: 0x   VER: 0x80050010 LDR: 0x DFR: 0x
  lint0: 0x00010700 lint1: 0x0400 TPR: 0x SVR: 0x01ff
  timer: 0x000100ef therm: 0x0001 err: 0x0001000f pcm: 0x0001
io: I/O
null: null device, zero device
kbd: new array size 4
kbd1 at kbdmux0
random: entropy source, Software, Yarrow
mem: memory
Pentium Pro MTRR support enabled
npx0: INT 16 interface
acpi0: 092208 XSDT1629 on motherboard
ioapic0: routing intpin 9 (ISA IRQ 9) to vector 48
acpi0: [MPSAFE]
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: wakeup code va 0xc439b000 pa 0x1000
pci_open(1):mode 1 addr port (0x0cf8) is 0x8000a078
pci_open(1a):   mode1res=0x8000 (0x8000)
pci_cfgcheck:   device 0 [class=06] [hdr=00] is there (id=96001022)
pcibios: BIOS version 3.00
AcpiOsDerivePciId: \\_SB_.PCI0.RS78.NB2_ - bus 0 dev 0 func 0
acpi: bad write to port 0x000 (8), val 0x5a
acpi: bad write to port 

[LOR] unmounting a filesystem

2009-09-28 Thread Borja Marcos

Sep 28 19:47:46  kernel: lock order reversal:
Sep 28 19:47:46  kernel: 1st 0xff0002a9a308 ufs (ufs) @ /usr/src/ 
sys/kern/vfs_mount.c:1200
Sep 28 19:47:46  kernel: 2nd 0xff0002a63a58 devfs (devfs) @ /usr/ 
src/sys/ufs/ffs/ffs_vfsops.c:1194

Sep 28 19:47:46  kernel: KDB: stack backtrace:
Sep 28 19:47:46  kernel: db_trace_self_wrapper() at  
db_trace_self_wrapper+0x2a

Sep 28 19:47:46  kernel: _witness_debugger() at _witness_debugger+0x2e
Sep 28 19:47:46  kernel: witness_checkorder() at witness_checkorder 
+0x81e

Sep 28 19:47:46  kernel: __lockmgr_args() at __lockmgr_args+0xd03
Sep 28 19:47:46  kernel: vop_stdlock() at vop_stdlock+0x39
Sep 28 19:47:46  kernel: VOP_LOCK1_APV() at VOP_LOCK1_APV+0x9b
Sep 28 19:47:46  kernel: _vn_lock() at _vn_lock+0x57
Sep 28 19:47:46  kernel: ffs_flushfiles() at ffs_flushfiles+0xc5
Sep 28 19:47:46  kernel: softdep_flushfiles() at softdep_flushfiles+0x63
Sep 28 19:47:46  kernel: ffs_unmount() at ffs_unmount+0x2e1
Sep 28 19:47:46  kernel: dounmount() at dounmount+0x2e6
Sep 28 19:47:46  kernel: unmount() at unmount+0x27e
Sep 28 19:47:46  kernel: syscall() at syscall+0x1d0
Sep 28 19:47:46  kernel: Xfast_syscall() at Xfast_syscall+0xe1
Sep 28 19:47:46  kernel: --- syscall (22, FreeBSD ELF64, unmount), rip  
= 0x8006a09bc, rsp = 0x7fffe3b8, rbp = 0 ---


FreeBSD  8.0-RC1 FreeBSD 8.0-RC1 #0: Fri Sep 25 16:55:06 CEST 2009  
root@:/usr/obj/usr/src/sys/DEBUG  amd64


I'm running it on VMWare Fussion, but it shouldn't matter.

The system has two disks, one of them just a root partition and the  
other one has two filesystems, one for /usr/src and the other for /usr/ 
obj


How to reproduce?

Right after boot, I have mounted /usr/src and /usr/obj.

Unmounting /usr/obj has given this LOR.

I can reproduce it easily, please let me know if I can do anything else.





Borja.

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


Re: 8.0-RC1 panic attaching ppc

2009-09-28 Thread Alan Cox

Daniel O'Connor wrote:

On Sun, 27 Sep 2009, Alan Cox wrote:
  

Ok, now I can explain what is happening.  The kernel is using 1GB
pages to implement the direct map.  Unfortunately, pmap_extract()
doesn't know how to handle a 1GB page mapping.  pmap_kextract() only
works by an accident of its different implementation.  In other
words, it should not be relied upon to work either.

Please revert whatever patch John gave you and try the attached
patch. It simply disables the use of 1GB page mapping by the direct
map.



Your patch fixes (works around?) the problem.
  


Thanks.  I've committed the patch.

Yes, it's a work around.  Fortunately(?), on my test machine, I don't 
see any measurable effect from disabling the use of 1GB pages by the 
direct map.


Alan

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


Re: glabel+gmirror (8.0-RC1 problem)

2009-09-28 Thread Oliver Lehmann
Hi Pawel,

Pawel Jakub Dawidek wrote:

 Does anything change between you upgrade from BETA3 and RC1? For example
 gmirror was compiled into the kernel before and now is loaded as module
 or something similar?

Nope, it was a clean BETA3 installation with the default GENERIC kernel
which has afaik geom_label in kernel, but not geom_mirror (nevertheless I
loaded geom_label.ko at boottime as well as geom_mirror)
The same with RC1 - clean and fresh installation with the default GENERIC
kernel and geom_label in kernel (default), but still loaded as module at
boottime as well as geom_mirror.

 Could you test this patch:
 
   http://people.freebsd.org/~pjd/patches/improved_taste.patch

This makes gmirror+glabel work again on RC1

One thing which I noticed. I labeled in single user mode, my root
partition with tunefs - as well as all my other partitions. After this
was done, I remounted my root partition (mount -rw /) and changed my
fstab to use the new geom labels instead. But somehow this killed the
new root-label of my mirror/gm0s1a partition. After I rebooted, the label
was gone and I had to manually specify the root partition
ufs:mirror/gm0s1a to mount. All the labels of my other mirrored
partitions where there (usr, tmp, var). I then rebooted once more into
single user mode (specified once more the root partition manually) and
did a tunefs -L once more. Then I rebooted directly and the label is now
there.

Is it possible that mount -rw / (which remounts /dev/mirror/gm0s1a) could
have been killed the freshly given label?

-- 
 Oliver Lehmann
  http://www.pofo.de/
  http://wishlist.ans-netz.de/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: glabel+gmirror (8.0-RC1 problem)

2009-09-28 Thread Pawel Jakub Dawidek
On Mon, Sep 28, 2009 at 08:37:56PM +0200, Oliver Lehmann wrote:
 Hi Pawel,
 
 Pawel Jakub Dawidek wrote:
 
  Does anything change between you upgrade from BETA3 and RC1? For example
  gmirror was compiled into the kernel before and now is loaded as module
  or something similar?
 
 Nope, it was a clean BETA3 installation with the default GENERIC kernel
 which has afaik geom_label in kernel, but not geom_mirror (nevertheless I
 loaded geom_label.ko at boottime as well as geom_mirror)
 The same with RC1 - clean and fresh installation with the default GENERIC
 kernel and geom_label in kernel (default), but still loaded as module at
 boottime as well as geom_mirror.
 
  Could you test this patch:
  
  http://people.freebsd.org/~pjd/patches/improved_taste.patch
 
 This makes gmirror+glabel work again on RC1

Thanks for confirmation.

 One thing which I noticed. I labeled in single user mode, my root
 partition with tunefs - as well as all my other partitions. After this
 was done, I remounted my root partition (mount -rw /) and changed my
 fstab to use the new geom labels instead. But somehow this killed the
 new root-label of my mirror/gm0s1a partition. After I rebooted, the label
 was gone and I had to manually specify the root partition
 ufs:mirror/gm0s1a to mount. All the labels of my other mirrored
 partitions where there (usr, tmp, var). I then rebooted once more into
 single user mode (specified once more the root partition manually) and
 did a tunefs -L once more. Then I rebooted directly and the label is now
 there.
 
 Is it possible that mount -rw / (which remounts /dev/mirror/gm0s1a) could
 have been killed the freshly given label?

Yes. tunefs(8) updates only on-disk super-block, but the kernel holds
super-block that was read before. Now when you do 'mount -rw /' the
in-kernel super-block is stored to the disk, and there is nothing about
your label in there, so it gets overwritten.

-- 
Pawel Jakub Dawidek   http://www.wheel.pl
p...@freebsd.org   http://www.FreeBSD.org
FreeBSD committer Am I Evil? Yes, I Am!


pgpxYBiQfwXn2.pgp
Description: PGP signature


Re: PATA disks/DVD not detected on ATI IXP 700 - cannot boot (dmesg attached)

2009-09-28 Thread Alexander Motin
Dennis Chikin wrote:
 Is it means that all works with this patch?
 
 No visible ata-specific faults encountered after loading the kernel.
 
 Can you show dmesg from patched system?

 atapci0: ATI (ID=43901002) AHCI controller port
 0xc000-0xc007,0xb000-0xb003,0xa000-0xa007,0x9000-0x9003,0x8000-0x800f
 mem 0xfe8ff800-0xfe8ffbff irq 22 at device 17.0 on pci0
 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0x8000
 atapci0: Reserved 0x400 bytes for rid 0x24 type 3 at 0xfe8ff800
 ioapic0: routing intpin 22 (PCI IRQ 22) to vector 50
 atapci0: [MPSAFE]
 atapci0: [ITHREAD]
 atapci0: AHCI Version 01.10 controller with 4 ports detected
 ata2: ATA channel 0 on atapci0
 ata2: SATA connect time=0ms
 ata2: SIGNATURE: 0101
 ata2: ahci_reset devices=0x1ATA_MASTER
 ata2: [MPSAFE]
 ata2: [ITHREAD]
 ata3: ATA channel 1 on atapci0
 ata3: SATA connect status=
 ata3: ahci_reset devices=0x0
 ata3: [MPSAFE]
 ata3: [ITHREAD]
 ata4: ATA channel 2 on atapci0
 ata4: SATA connect status=
 ata4: ahci_reset devices=0x0
 ata4: [MPSAFE]
 ata4: [ITHREAD]
 ata5: ATA channel 3 on atapci0
 ata5: SATA connect status=
 ata5: ahci_reset devices=0x0
 ata5: [MPSAFE]
 ata5: [ITHREAD]
 atapci1: ATI IXP700 UDMA133 controller port
 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 20.1 on
 pci0
 atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0xff00
 ata0: ATA channel 0 on atapci1
 atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0
 atapci1: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6
 ata0: reset tp1 mask=03 ostat0=7f ostat1=7f
 ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff
 ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff
 ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff
 ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff
 ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff
 ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff
 ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff
 ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff
 ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff
 ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff
 ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff
 ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff
 ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff
 ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff
 ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff
 ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff
 ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff
 ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff
 ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff
 ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff
 ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff
 ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff
 ata0: stat1=0x7f err=0xff lsb=0xff msb=0xff
 ata0: reset tp2 stat0=ff stat1=ff devices=0x0
 ioapic0: routing intpin 14 (ISA IRQ 14) to vector 55
 ata0: [MPSAFE]
 ata0: [ITHREAD]
 ata1: ATA channel 1 on atapci1
 atapci1: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170
 atapci1: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376
 ata1: reset tp1 mask=03 ostat0=50 ostat1=50
 ata1: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
 ata1: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb
 ata1: reset tp2 stat0=50 stat1=00 devices=0x9ATAPI_SLAVE,ATA_MASTER

Here we can see detected: 4 (not 6!) SATA channels on AHCI controller,
one PATA channel and 2 SATA channels in legacy emulation (why?).
Actually, the same happens if I comment out all that device class magic.
Looks like the only thing really required to fix problem with two lost
channels is this part of patch:

-/* IXP600  IXP700 only have 1 PATA channel */
-if ((ctlr-chip-chipid == ATA_ATI_IXP600) ||
-   (ctlr-chip-chipid == ATA_ATI_IXP700))
+/* IXP600 only have 1 PATA channel */
+if (ctlr-chip-chipid == ATA_ATI_IXP600)

Looks like part of changing device class just not working. Today I have
bought IXP700 based board and can acknowledge that the same situation I
can see with recent HEAD. `pciconf -l` reports to me original PATA
device class and only 4 channels reported by AHCI.

So jkim@, could you please comment, how should it really work and why it
doesn't?

PS: I have tried to disable all that ATI-specific code and found that
both legacy PCI ATA and AHCI drivers looks like working fine with
IXP700. Do we really need AHCI forcing for IXP700?

-- 
Alexander Motin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: glabel+gmirror (8.0-RC1 problem)

2009-09-28 Thread Oliver Lehmann
Pawel Jakub Dawidek wrote:

 Yes. tunefs(8) updates only on-disk super-block, but the kernel holds
 super-block that was read before. Now when you do 'mount -rw /' the
 in-kernel super-block is stored to the disk, and there is nothing about
 your label in there, so it gets overwritten.

Ok this sounds familar to me - maybe I have read about this before ;)
What would be the prefered way to label the root partition and changing
fstab without entering the root partition at bootup manually at least
once? Is there a way to do so?

I noticed that even when I boot in multiuser, change fstab, then return
into single user mode and remount / read-only, the label cannot be set.
I need to boot directly into single user mode. Looks like writing the
label is denied when the partition was once mounted rw before - even if
it is actually mounted ro.

-- 
 Oliver Lehmann
  http://www.pofo.de/
  http://wishlist.ans-netz.de/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: FreeBSD 7.2-STABLE boot freeze

2009-09-28 Thread kama


On Mon, 28 Sep 2009, Andriy Gapon wrote:

 on 28/09/2009 10:21 kama said the following:
 
  On Fri, 25 Sep 2009, Andriy Gapon wrote:
 
  on 25/09/2009 12:04 kama said the following:
  On Thu, 24 Sep 2009, kama wrote:
 
  I am currently building the source on another machine. Lets see if it 
  will
  build it any better.
  Building the the world on another machine and install it on the DL385
  machine made it also to freeze.
  Did you still get the message about unresolved symbol?
 
  I did not try with ACPI_DEBUG enabled.
 
  Another week, so I can start testing again...

 I did not ask that :-)
 I asked -  when you got your latest freeze, did you see that 'unresolved'
 message or not?

But that only appears when I enable ACPI_DEBUG.

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


Laggy X11 after updating to 8.0-RC1

2009-09-28 Thread Rohit Grover
I have upgraded to 8.0-RC1 (from 7.2-STABLE) on my MacBook 4,1. I did
so by checking out stable/8 under /usr/src, rebuilding kernel/world,
and using portupgrade to update all installed ports from packages
available on the 8.0RC1 DVD-iso.

Since the update, my X11 is laggy. Now, I often have to move the mouse
before keystrokes/button presses take effect.

wiki.freebsd.org/USB mentions about a similar situation under the
question: Screen updates in X111 are slow/broken/laggy, and their
recommended solution is to update kernel/world, remove old libs, and
rebuild the port libpciaccess.

As I've mentioned, I've updated the kernel/world, and updated
libpciaccess. Perhaps I'm having issues because I need to remove old
libs. How do I remove old libs?

Could there be another cause for the symptoms I'm experiencing?

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


Re: Laggy X11 after updating to 8.0-RC1

2009-09-28 Thread Warren Block

On Tue, 29 Sep 2009, Rohit Grover wrote:


I have upgraded to 8.0-RC1 (from 7.2-STABLE) on my MacBook 4,1. I did
so by checking out stable/8 under /usr/src, rebuilding kernel/world,
and using portupgrade to update all installed ports from packages
available on the 8.0RC1 DVD-iso.

Since the update, my X11 is laggy. Now, I often have to move the mouse
before keystrokes/button presses take effect.


Make sure hal and dbus are enabled in rc.conf and running.  In 
xorg.conf, remove Option AllowEmptyInput off.


A bonus of using hal is that you can remove the keyboard and mouse 
sections from xorg.conf.



As I've mentioned, I've updated the kernel/world, and updated
libpciaccess. Perhaps I'm having issues because I need to remove old
libs. How do I remove old libs?


cd /usr/src
make check-old-libs
make delete-old-libs

/usr/src/Makefile lists all the options.

-Warren Block * Rapid City, South Dakota USA
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Laggy X11 after updating to 8.0-RC1

2009-09-28 Thread Rohit Grover
On Tue, Sep 29, 2009 at 7:30 AM, Warren Block wbl...@wonkity.com wrote:
 On Tue, 29 Sep 2009, Rohit Grover wrote:

 I have upgraded to 8.0-RC1 (from 7.2-STABLE) on my MacBook 4,1. I did
 so by checking out stable/8 under /usr/src, rebuilding kernel/world,
 and using portupgrade to update all installed ports from packages
 available on the 8.0RC1 DVD-iso.

 Since the update, my X11 is laggy. Now, I often have to move the mouse
 before keystrokes/button presses take effect.

 Make sure hal and dbus are enabled in rc.conf and running.  In xorg.conf,
 remove Option AllowEmptyInput off.

 A bonus of using hal is that you can remove the keyboard and mouse sections
 from xorg.conf.

 As I've mentioned, I've updated the kernel/world, and updated
 libpciaccess. Perhaps I'm having issues because I need to remove old
 libs. How do I remove old libs?

 cd /usr/src
 make check-old-libs
 make delete-old-libs


I deleted old libs using 'make delete-old-libs' from /usr/src, but
that has led to many other problems.
It seems many libraries currently in use were deleted in the process.
I'm having to rebuild/reinstall many of my applications to get them
working again.
And gdm doesn't work anymore. Initially X was complaining about
missing libraries, but after reinstalling a few packages, I now have
gdm going into an endless loop in which it X tries to startup,
displays the mouse pointer, and then re-initializes itself.
Starting X by itself gets me similar behaviour: the screen blanks out,
and then nothing happens.

There is nothing in /var/log/messages or on the console to help debug
the problem. No man page for gdm. Any ideas on what should be done?

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


Re: Laggy X11 after updating to 8.0-RC1

2009-09-28 Thread Warren Block

On Tue, 29 Sep 2009, Rohit Grover wrote:


On Tue, Sep 29, 2009 at 7:30 AM, Warren Block wbl...@wonkity.com wrote:

On Tue, 29 Sep 2009, Rohit Grover wrote:


I have upgraded to 8.0-RC1 (from 7.2-STABLE) on my MacBook 4,1. I did
so by checking out stable/8 under /usr/src, rebuilding kernel/world,
and using portupgrade to update all installed ports from packages
available on the 8.0RC1 DVD-iso.

Since the update, my X11 is laggy. Now, I often have to move the mouse
before keystrokes/button presses take effect.


Make sure hal and dbus are enabled in rc.conf and running.  In xorg.conf,
remove Option AllowEmptyInput off.

A bonus of using hal is that you can remove the keyboard and mouse sections
from xorg.conf.


As I've mentioned, I've updated the kernel/world, and updated
libpciaccess. Perhaps I'm having issues because I need to remove old
libs. How do I remove old libs?


cd /usr/src
make check-old-libs
make delete-old-libs



I deleted old libs using 'make delete-old-libs' from /usr/src, but
that has led to many other problems.
It seems many libraries currently in use were deleted in the process.
I'm having to rebuild/reinstall many of my applications to get them
working again.


When upgrading from one major release of FreeBSD to another, the 
standard recommendation is to delete all installed applications 
(pkg_delete -a) and then reinstall everything.  There may be some 
incantation of portupgrade or portmaster that will do it.  pkg_libchk 
from sysutils/bsdadminscripts may help.  But that is likely to take 
longer than just pkg_delete -a and reinstalling applications.


-Warren Block * Rapid City, South Dakota USA___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Laggy X11 after updating to 8.0-RC1

2009-09-28 Thread Scott Lambert
On Mon, Sep 28, 2009 at 07:29:46PM -0600, Warren Block wrote:
 On Tue, 29 Sep 2009, Rohit Grover wrote:
 
 On Tue, Sep 29, 2009 at 7:30 AM, Warren Block wbl...@wonkity.com wrote:
 On Tue, 29 Sep 2009, Rohit Grover wrote:
 
 I have upgraded to 8.0-RC1 (from 7.2-STABLE) on my MacBook 4,1. I
 did so by checking out stable/8 under /usr/src, rebuilding
 kernel/world, and using portupgrade to update all installed ports
 from packages available on the 8.0RC1 DVD-iso.
 
 Since the update, my X11 is laggy. Now, I often have to move the
 mouse before keystrokes/button presses take effect.
 
 Make sure hal and dbus are enabled in rc.conf and running.  In
 xorg.conf, remove Option AllowEmptyInput off.
 
 A bonus of using hal is that you can remove the keyboard and mouse
 sections from xorg.conf.
 
 As I've mentioned, I've updated the kernel/world, and updated
 libpciaccess. Perhaps I'm having issues because I need to remove
 old libs. How do I remove old libs?
 
 cd /usr/src make check-old-libs make delete-old-libs
 
 
 I deleted old libs using 'make delete-old-libs' from /usr/src,
 but that has led to many other problems.  It seems many libraries
 currently in use were deleted in the process.  I'm having to
 rebuild/reinstall many of my applications to get them working again.

I'm seeing something similar to OP, apparent keyboard buffer delays, but
maybe not exactly.  When I click from one xterm to another, it may be
1 - 30 seconds before my key entries show.  Firefox seems to have less
delay after clicks into text fields, but sometimes it is noticeable maybe
0.25 to 1 second.  Just two xterms, the fluxbox toolbar, and firefox
running.  No frufru stuff.  

I haven't had time to systematically try to narrow down the actual
problem.

Wiggling the mouse, hitting various keys all seemed like they helped
at one time or another, but I think I was just trying things until the
buffer released.  If I leave it alone, the delays seem to be of about
the same length as when I'm trying random things to break it loose.

Only clicking in a window (particularly an xterm) seems to stall the
keyboard buffer.  Just wiggling the mouse above or around the focused
window is no problem.  Clicks take effect immediately.  I can drag
the window by the title bar or resize the window without stalling the
keyboard buffer.

I haven't lost a key press that I've noticed.  Now I just type blind
until it catches up or I actually need to see the results of my typing.

Oh, it seems like if there is something in the xterm which can use the
mouse input, it may not be stalling the keyboard buffer.  I need to
watch that more closely.

I've tried with and without an explicit xorg.conf.  Switching
back to the console works better without.  With doesn't leave me a
usable display outside of X.  

It seems like the delays get longer and longer the longer the X session
has been up.  But sometimes there will be no delay.  If I switch
windows/desktops with alt-tab, ctrl-f#, there is no delay.  I've been
wondering if it could be due to the synaptics touchpad.  I enabled the
synaptics features about the same time to try to get rid of tap events
from the touchpad.  I hate touchpads and still haven't figured out how
to kill tapping.

agp0: Intel GM965 SVGA controller on vgapci0

I've done the delete-old stuff and got mad at KDE4 and did a pkg_delete
-a in a fit of rage.  I went back with fluxbox, took about 2 to 3 hours
to compile everything from source to have my multiple xterms back.
Firefox took another 2 hours.  But I was able to *work* while that
built.

I was running FreeBSD 8-CURRENT pre-beta cycle.  KDE4 was giving me so
many fits that I would just run Windows instead so I could get work
done, sad.  I don't know if I would have noticed an input buffer delay
before I upgraded to BETA2 and replaced KDE with fluxbox.  I just
couldn't stand to spend that much time in X.  Windows finally annoyed me
enough to try something different (fluxbox).  This problem has been with
me through the BETAs and now into RC1, as far as I can remember.  I've
been busy and trying really hard to ignore workstation issues to get
work done ever since my PowerBook died.

 When upgrading from one major release of FreeBSD to another, the 
 standard recommendation is to delete all installed applications 
 (pkg_delete -a) and then reinstall everything.  There may be some 
 incantation of portupgrade or portmaster that will do it.  pkg_libchk 
 from sysutils/bsdadminscripts may help.  But that is likely to take 
 longer than just pkg_delete -a and reinstalling applications.

portmaster's man page suggests pkg_delete -a.  It has explicit
instructions so you don't miss anything putting them back on.  Not
that I've used the instructions yet.  Rage is not condusive to reading
manuals.
 
-- 
Scott LambertKC5MLE   Unix SysAdmin
lamb...@lambertfam.org

___
freebsd-stable@freebsd.org mailing list

Re: Excessivly cheap USB device issue

2009-09-28 Thread Daniel O'Connor
On Mon, 28 Sep 2009, Mike Tancsa wrote:
 I also have a similar device, which I've been messing with a bit the
 last couple of days.  In your case, it isn't seeing the media, just
  the drive.  I've had to try various combinations of unplugging
  the adapter from usb, inserting the media then plugging it back in.
   It does seem to work fairly reliably if you boot with the media
  already inserted, but it doesn't seem to detect media change at
  all.

 I get around it (on my cheap reader) by  always doing a
 cat /dev/null  /dev/da1
 whever I change or insert new media into the reader

 That seems to work with the gear I have 99% of the time.

Hmm OK, I sort of expected fdisk da1 to fail straightaway though (it 
takes ~30 seconds to fail for me).

I have unplugged it for now, it interacts annoyingly with SANE because 
that scans the SCSI bus(es) looking for scanner and each umass takes 
30+ seconds to fail.

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
The nice thing about standards is that there
are so many of them to choose from.
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C


signature.asc
Description: This is a digitally signed message part.