Re: No ATA disks on 9.1
03.05.2013 22:33, John Baldwin пишет: On Friday, May 03, 2013 1:53:35 pm Alex Keda wrote: 03.05.2013 20:41, John Baldwin пишет: On Thursday, May 02, 2013 4:18:45 pm Alex Keda wrote: see begin in: http://lists.freebsd.org/pipermail/freebsd-current/2012- November/038000.html Hmm, what I see is that hdac0 is affected by this, but it's a bit odd. Can you try the patch below, but can you also get the output of 'devinfo -u' and 'devinfo -rv' from the 9.0 kernel? see attached files Ok, your BIOS assigns conflicting resources to ahci0 and hdac0. HPS' patch means that hdac0 claims register reads of ahci0 which breaks things. The patch I posted should help. I was able to apply the patch to 9 without any difficulties: OK, it's work please, commit this to tree ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: No ATA disks on 9.1
03.05.2013 20:41, John Baldwin пишет: On Thursday, May 02, 2013 4:18:45 pm Alex Keda wrote: see begin in: http://lists.freebsd.org/pipermail/freebsd-current/2012-November/038000.html Hmm, what I see is that hdac0 is affected by this, but it's a bit odd. Can you try the patch below, but can you also get the output of 'devinfo -u' and 'devinfo -rv' from the 9.0 kernel? see attached files = about patch, I cannot apply it for 9.1 source, too many differents... nexus0 apic0 I/O memory addresses: 0xfec0-0xfec0001f 0xfee0-0xfee003ff ram0 I/O memory addresses: 0x0-0x9fbff 0x10-0xb7fa 0x1-0x13fff acpi0 Interrupt request lines: 9 I/O ports: 0x10-0x1f 0x22-0x23 0x2e-0x2f 0x4e-0x4f 0x92 0x40b 0x4d0-0x4d1 0x4d6 0x500-0x53f 0xc00-0xc01 0xc14 0xc50-0xc51 0xc52 0xc6c 0xc6f 0xcd0-0xcdf 0x8000-0x802f 0x8100-0x811f I/O memory addresses: 0xcd400-0xc 0xd2a00-0xd2fff 0xe-0xf cpu0 pnpinfo _HID=none _UID=0 at handle=\_PR_.C000 acpi_throttle0 ACPI I/O ports: 0x8010-0x8013 acpi_perf0 powernow0 cpufreq0 cpu1 pnpinfo _HID=none _UID=0 at handle=\_PR_.C001 acpi_throttle1 acpi_perf1 powernow1 cpufreq1 acpi_sysresource0 pnpinfo _HID=PNP0C01 _UID=0 at handle=\_SB_.C011 pcib0 pnpinfo _HID=PNP0A03 _UID=0 at handle=\_SB_.C08B I/O ports: 0xcf8-0xcff pci0 hostb0 pnpinfo vendor=0x1002 device=0x7910 subvendor=0x103c subdevice=0x30c2 class=0x06 at slot=0 function=0 pcib1 pnpinfo vendor=0x1002 device=0x7912 subvendor=0x103c subdevice=0x30c2 class=0x060400 at slot=1 function=0 handle=\_SB_.C08B.C08C I/O ports: 0x4000-0x4fff I/O memory addresses: 0xc000-0xc7ff 0xd020-0xd03f pci1 vgapci0 pnpinfo vendor=0x1002 device=0x791f subvendor=0x103c subdevice=0x30c2 class=0x03 at slot=5 function=0 handle=\_SB_.C08B.C08C.C08D Interrupt request lines: 258 pcib1 I/O port window: 0x4000-0x40ff pcib1 memory window: 0xd020-0xd020 0xd030-0xd03f pcib1 prefetch window: 0xc000-0xc7ff vgapm0 drm0 pcib2 pnpinfo vendor=0x1002 device=0x7914 subvendor=0x103c subdevice=0x30c2 class=0x060400 at slot=4 function=0 handle=\_SB_.C08B.C250 I/O memory addresses: 0xd000-0xd00f pci16 bge0 pnpinfo vendor=0x14e4 device=0x1713 subvendor=0x103c subdevice=0x30c2 class=0x02 at slot=0 function=0 handle=\_SB_.C08B.C250.C251 Interrupt request lines: 256 pcib2 memory window: 0xd000-0xd000 miibus0 brgphy0 pnpinfo oui=0x50ef model=0x4 rev=0x0 at phyno=1 pcib3 pnpinfo vendor=0x1002 device=0x7915 subvendor=0x103c subdevice=0x30c2 class=0x060400 at slot=5 function=0 handle=\_SB_.C08B.C255 I/O ports: 0x2000-0x3fff I/O memory addresses: 0xcc00-0xcfff pci32 pcib4 pnpinfo vendor=0x1002 device=0x7916 subvendor=0x103c subdevice=0x30c2 class=0x060400 at slot=6 function=0 handle=\_SB_.C08B.C25F I/O memory addresses: 0xc800-0xc80f pci48 siba_bwn0 pnpinfo vendor=0x14e4 device=0x4312 subvendor=0x103c subdevice=0x1371 class=0x028000 at slot=0 function=0 handle=\_SB_.C08B.C25F.C260 Interrupt request lines: 257 pcib4 memory window: 0xc800-0xc8003fff unknown bwn0 unknown unknown ahci0 pnpinfo vendor=0x1002 device=0x4380 subvendor=0x1002 subdevice=0x4380 class=0x01018f at slot=18 function=0 handle=\_SB_.C08B.C275 Interrupt request lines: 16 I/O ports: 0x5018-0x501b 0x5020-0x502f 0x9000-0x9007 0x9008-0x900b 0x9010-0x9017 I/O memory addresses: 0xd0409000-0xd04093ff ahcich0 at channel=0 I/O memory addresses: 0xd0409100-0xd040917f ohci0 pnpinfo vendor=0x1002 device=0x4387 subvendor=0x103c subdevice=0x30c2 class=0x0c0310 at slot=19 function=0 handle=\_SB_.C08B.C12D Interrupt request lines: 23 I/O memory
Re: No ATA disks on 9.1
03.05.2013 20:41, John Baldwin пишет:
On Thursday, May 02, 2013 4:18:45 pm Alex Keda wrote:
see begin in:
http://lists.freebsd.org/pipermail/freebsd-current/2012-November/038000.html
Hmm, what I see is that hdac0 is affected by this, but it's a bit odd. Can
you try the patch below, but can you also get the output of 'devinfo -u' and
'devinfo -rv' from the 9.0 kernel?
I use this patch:
srv0# diff -Nru sys/dev/pci/pci.c.orig sys/dev/pci/pci.c
--- sys/dev/pci/pci.c.orig 2012-11-17 12:47:51.0 +0400
+++ sys/dev/pci/pci.c 2013-05-03 21:49:18.0 +0400
@@ -2751,6 +2751,11 @@
* from the parent.
*/
resource_list_delete(rl, type, reg);
+ pci_disable_io(dev, type);
+ device_printf(bus,
+ pci%d:%d:%d:%d bar %#x failed to allocate\n,
+ pci_get_domain(dev), pci_get_bus(dev),
pci_get_slot(dev),
+ pci_get_function(dev), reg);
} else {
start = rman_get_start(res);
pci_write_bar(dev, pm, start);
srv0#
all OK:
HP# uname -a
FreeBSD HP.lissyara.su 9.1-RELEASE-p3 FreeBSD 9.1-RELEASE-p3 #0: Fri May
3 22:03:50 MSK 2013
lissy...@srv0.host-food.ru:/usr/obj/usr/src/sys/GENERIC amd64
HP#
Thanks!
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
No ATA disks on 9.1
see begin in:
http://lists.freebsd.org/pipermail/freebsd-current/2012-November/038000.html
today, I have time and try find problem commit for 9-stable
2012.05.04.15.20.00 - all work OK
2012.05.05.00.00.00 - cannot boot
it's only two kernel-related file for this period:
Edit src/lib/libc/gen/sem_new.c
Add delta 1.8.2.2 2012.05.04.20.45.53 jilles
Edit src/sys/dev/pci/pci.c
Add delta 1.425.2.8 2012.05.04.15.38.47 hselasky
Edit src/sys/ufs/ufs/ufs_vnops.c
Add delta 1.328.2.7 2012.05.04.15.51.23 jh
diff -Nru /usr/src/sys/dev/pci/pci.c /tmp/src/sys/dev/pci/pci.c
--- /usr/src/sys/dev/pci/pci.c 2013-05-03 00:05:19.0 +0400
+++ /tmp/src/sys/dev/pci/pci.c 2013-05-02 23:56:38.0 +0400
@@ -27,7 +27,7 @@
*/
#include sys/cdefs.h
-__FBSDID($FreeBSD: src/sys/dev/pci/pci.c,v 1.425.2.7 2012/04/11
20:50:17 jhb Exp $);
+__FBSDID($FreeBSD: src/sys/dev/pci/pci.c,v 1.425.2.8 2012/05/04
15:38:47 hselasky Exp $);
#include opt_bus.h
@@ -2746,16 +2746,15 @@
prefetch ? RF_PREFETCHABLE : 0);
if (res == NULL) {
/*
-* If the allocation fails, clear the BAR and delete
-* the resource list entry to force
-* pci_alloc_resource() to allocate resources from the
-* parent.
+* If the allocation fails, delete the resource list entry
+* to force pci_alloc_resource() to allocate resources
+* from the parent.
*/
resource_list_delete(rl, type, reg);
- start = 0;
- } else
+ } else {
start = rman_get_start(res);
- pci_write_bar(dev, pm, start);
+ pci_write_bar(dev, pm, start);
+ }
return (barlen);
}
@@ -3824,7 +3823,7 @@
if ((desc = malloc(strlen(vp) + strlen(dp) + 3, M_DEVBUF,
M_NOWAIT)) !=
NULL)
sprintf(desc, %s, %s, vp, dp);
- out:
+out:
if (vp != NULL)
free(vp, M_DEVBUF);
if (dp != NULL)
@@ -4100,7 +4099,7 @@
count, *rid, type, rman_get_start(res));
map = rman_get_start(res);
pci_write_bar(child, pm, map);
-out:;
+out:
return (res);
}
@@ -4289,19 +4288,6 @@
type, rid, rman_get_start(rle-res));
return;
}
-
-#ifndef __PCI_BAR_ZERO_VALID
- /*
-* If this is a BAR, clear the BAR so it stops
-* decoding before releasing the resource.
-*/
- switch (type) {
- case SYS_RES_IOPORT:
- case SYS_RES_MEMORY:
- pci_write_bar(child, pci_find_bar(child, rid), 0);
- break;
- }
-#endif
resource_list_unreserve(rl, dev, child, type, rid);
}
resource_list_delete(rl, type, rid);
diff -Nru /usr/src/sys/ufs/ufs/ufs_vnops.c /tmp/src/sys/ufs/ufs/ufs_vnops.c
--- /usr/src/sys/ufs/ufs/ufs_vnops.c2013-05-03 00:05:30.0 +0400
+++ /tmp/src/sys/ufs/ufs/ufs_vnops.c2013-05-02 23:56:49.0 +0400
@@ -35,7 +35,7 @@
*/
#include sys/cdefs.h
-__FBSDID($FreeBSD: src/sys/ufs/ufs/ufs_vnops.c,v 1.328.2.6 2012/05/02
15:15:28 jh Exp $);
+__FBSDID($FreeBSD: src/sys/ufs/ufs/ufs_vnops.c,v 1.328.2.7 2012/05/04
15:51:23 jh Exp $);
#include opt_quota.h
#include opt_suiddir.h
@@ -528,6 +528,10 @@
return (EINVAL);
}
if (vap-va_flags != VNOVAL) {
+ if ((vap-va_flags ~(UF_NODUMP | UF_IMMUTABLE |
UF_APPEND |
+ UF_OPAQUE | UF_NOUNLINK | SF_ARCHIVED | SF_IMMUTABLE |
+ SF_APPEND | SF_NOUNLINK | SF_SNAPSHOT)) != 0)
+ return (EOPNOTSUPP);
if (vp-v_mount-mnt_flag MNT_RDONLY)
return (EROFS);
/*
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: No ATA disks on 9.1
03.05.2013 00:18, Alex Keda пишет: see begin in: http://lists.freebsd.org/pipermail/freebsd-current/2012-November/038000.html today, I have time and try find problem commit for 9-stable 2012.05.04.15.20.00 - all work OK 2012.05.05.00.00.00 - cannot boot I try build after Edit src/sys/dev/pci/pci.c Add delta 1.425.2.8 2012.05.04.15.38.47 hselasky it's cannot boot ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
FreeBSD 9.1 - not work IPMI
srv3# dmesg -a | grep -i ipmi ipmi0: IPMI System Interface on isa0 ipmi0: KCS mode found at io 0xca2 alignment 0x1 on isa ipmi0: Timed out waiting for GET_DEVICE_ID srv3# ll /dev/ipmi* ls: No match. srv3# srv3# uname -a FreeBSD srv3.host-food.ru 9.1-RELEASE FreeBSD 9.1-RELEASE #0: Wed Dec 5 04:53:34 MSK 2012 t...@srv3.host-food.ru:/usr/obj/usr/src/sys/HOST-FOOD amd64 srv3# not work on HP Proliant DL165 G7, SuperMicro AS-1022G-URF work on Tyan B8236G24W4HR-IL before update, on 8.3, it work on all ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: fsck problem
07.01.2013 03:15, Kirk McKusick пишет: Date: Wed, 02 Jan 2013 00:46:53 +0400 From: Alex Keda ad...@lissyara.su To: curr...@freebsd.org Subject: fsck problem so, whats reason for use SUJ? SUJ is used to speed up the fsck process. If you have had hard disk errors then it is not able to recover and you need to run fsck in the old full-fsck way. It is not necessary to disable the journal. If fsck runs and fails it marks the journal as failed so when you rerun fsck it will run in the old full-fsck mode. Note that running `fsck -y' is not recommended as that says make this filesystem clean no matter what. So while you will end up with a clean filesystem, it may be empty if you had a bad block in the root directory. Instead you should run fsck and read and think about the questions rather than just blindly answering them all yes. it's HDD not have bad blocks - it's hardware RAID10 I run fsck -y more than 3 time, before disable journal. it's can't fix error, with enabled journal and, I see it's error not first time. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
fsck problem
Starting file system checks: /dev/label/rootFS: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/label/rootFS: clean, 11916812 free (74068 frags, 1480343 blocks, 0.5% fragmentation) ** SU+J Recovering /dev/label/homeFS ** Reading 33554432 byte journal from inode 12. ** Building recovery table. ** Resolving unreferenced inode list. ** Processing journal entries. fsck_ufs: Directory 1136967 name not found THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY: ufs: /dev/label/homeFS (/home) Unknown error; help! ERROR: ABORTING BOOT (sending SIGTERM to parent)! Jan 2 04:35:11 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode Enter full pathname of shell or RETURN for /bin/sh: # g\^H\^[[Kfsck -y .home fsck: cannot open `/dev/.home': No such file or directory # fsck -y .home\^H\^H\^H\^H\^Hhome\^[[K\^H\^H\^H\^H/home\^H\^H\^H\^H twa0: INFO: (0x04: 0x0029): Verify started: unit=0, subunit=1 twa0: INFO: (0x04: 0x0029): Verify started: unit=0, subunit=0 ** /dev/label/homeFS USE JOURNAL? yes ** SU+J Recovering /dev/label/homeFS ** Reading 33554432 byte journal from inode 12. RECOVER? yes ** Building recovery table. ** Resolving unreferenced inode list. ** Processing journal entries. fsck_ufs: Directory 1136967 name not found # tunefs -j disable .\^H\^[[K/home Clearing journal flags from inode 12 tunefs: soft updates journaling cleared but soft updates still set. tunefs: remove .sujournal to reclaim space # tunefs -j disable /home\^[[23D\^[[10Pfsck -y\^[[6C ** /dev/label/homeFS ** Last Mounted on /home ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts UNREF FILE I=48071192 OWNER=www MODE=100600 SIZE=5472256 MTIME=Jan 1 23:59 2013 CLEAR? yes UNREF FILE I=48071193 OWNER=www MODE=100600 SIZE=3538944 MTIME=Jan 2 00:01 2013 CLEAR? yes UNREF FILE I=53478932 OWNER=h40708 MODE=100644 SIZE=81 MTIME=Dec 29 00:24 2012 CLEAR? yes UNREF FILE I=53478934 OWNER=h40708 MODE=100644 SIZE=67 MTIME=Dec 27 17:24 2012 CLEAR? yes UNREF FILE I=53478935 OWNER=h40708 MODE=100644 SIZE=71 MTIME=Dec 28 12:34 2012 CLEAR? yes UNREF FILE I=53478947 OWNER=h40708 MODE=100644 SIZE=88 MTIME=Jan 1 18:10 2013 CLEAR? yes UNREF FILE I=53478953 OWNER=h40708 MODE=100644 SIZE=70 MTIME=Dec 28 00:42 2012 CLEAR? yes UNREF FILE I=53478954 OWNER=h40708 MODE=100644 SIZE=66 MTIME=Dec 31 08:20 2012 CLEAR? yes UNREF FILE I=53478956 OWNER=h40708 MODE=100644 SIZE=72 MTIME=Dec 28 00:48 2012 CLEAR? yes ** Phase 5 - Check Cyl groups FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? yes SUMMARY INFORMATION BAD SALVAGE? yes BLK(S) MISSING IN BIT MAPS SALVAGE? yes 2587656 files, 12137676 used, 212163011 free (637755 frags, 26440657 blocks, 0.3% fragmentation) * FILE SYSTEM MARKED CLEAN * * FILE SYSTEM WAS MODIFIED * # # # # # ^DSetting hostuuid: 564d258e-1ef7-b7a3-bde0-b6bca10c3382. Setting hostid: 0x88403a99. Entropy harvesting: interrupts ethernet point_to_point kickstart. Fast boot: skipping disk checks. Mounting local file systems:. === so, whats rason for use SUJ? about system: srv0$ uname -a FreeBSD srv0.host-food.ru 9.1-RELEASE FreeBSD 9.1-RELEASE #0: Wed Dec 5 04:05:50 MSK 2012 t...@srv0.host-food.ru:/usr/obj/usr/src/sys/HOST-FOOD amd64 srv0$ mount /dev/label/rootFS on / (ufs, local) devfs on /dev (devfs, local, multilabel) /dev/label/homeFS on /home (ufs, local, noatime, nosuid, with quotas, soft-updates) linprocfs on /proc (linprocfs, local) tmpfs on /tmp (tmpfs, local, noexec, nosuid) devfs on /var/named/dev (devfs, local, multilabel) srv0$ df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/label/rootFS 59G 13G 40G25%/ devfs1.0k1.0k 0B 100%/dev /dev/label/homeFS855G 46G740G 6%/home linprocfs4.0k4.0k 0B 100%/proc tmpfs 14G4.0k 14G 0%/tmp devfs1.0k1.0k 0B 100%/var/named/dev srv0$ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: No ATA disks on 9.1-RC3
19.11.2012 13:19, Volodymyr Kostyrko пишет: 19.11.2012 10:59, Volodymyr Kostyrko wrote: 19.11.2012 10:24, Alex Keda wrote: ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: WDC WD1600BEVT-00A0RT0 01.01A01 ATA-8 SATA 2.x device ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 152627MB (312581809 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad4 Looking for this one? ATA_CAM was made default for now. Damn I'm sorry. Looks like I need my coffee back... The change actually is at: ahci0: ATI IXP600 AHCI SATA controller port 0x9000-0x9007,0x9008-0x900b,0x9010-0x9017,0x5018-0x501b,0x5020-0x502f mem 0xd0409000-0xd04093ff irq 16 at device 18.0 on pci0 ahci0: AHCI v1.10 with 4 3Gbps ports, Port Multiplier not supported and ahci0: ATI IXP600 AHCI SATA controller port 0x9000-0x9007,0x9008-0x900b,0x9010-0x9017,0x5018-0x501b,0x5020-0x502f mem 0xd0409000-0xd04093ff irq 16 at device 18.0 on pci0 ioapic0: routing intpin 16 (PCI IRQ 16) to lapic 0 vector 52 ahci0: AHCI v0.00 with 1 ?Gbps ports, Port Multiplier not supported with FBS ahci0: Caps: ?Gbps FBS 2cmd 1ports The bad thing about that is that there was no major rewrite of ahci code in this timeframe. There are some point that can be checked though: 1. What is your BIOS settings for controller? Can you try switching it between Legacy/Compatible mode? There was a change that fixed behavior for detecting different BIOS settings. BIOS does not have SATA controller settings ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: No ATA disks on 9.1-RC3
19.11.2012 13:19, Volodymyr Kostyrko пишет: 19.11.2012 10:59, Volodymyr Kostyrko wrote: 19.11.2012 10:24, Alex Keda wrote: ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: WDC WD1600BEVT-00A0RT0 01.01A01 ATA-8 SATA 2.x device ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 152627MB (312581809 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad4 Looking for this one? ATA_CAM was made default for now. Damn I'm sorry. Looks like I need my coffee back... The change actually is at: ahci0: ATI IXP600 AHCI SATA controller port 0x9000-0x9007,0x9008-0x900b,0x9010-0x9017,0x5018-0x501b,0x5020-0x502f mem 0xd0409000-0xd04093ff irq 16 at device 18.0 on pci0 ahci0: AHCI v1.10 with 4 3Gbps ports, Port Multiplier not supported and ahci0: ATI IXP600 AHCI SATA controller port 0x9000-0x9007,0x9008-0x900b,0x9010-0x9017,0x5018-0x501b,0x5020-0x502f mem 0xd0409000-0xd04093ff irq 16 at device 18.0 on pci0 ioapic0: routing intpin 16 (PCI IRQ 16) to lapic 0 vector 52 ahci0: AHCI v0.00 with 1 ?Gbps ports, Port Multiplier not supported with FBS ahci0: Caps: ?Gbps FBS 2cmd 1ports The bad thing about that is that there was no major rewrite of ahci code in this timeframe. There are some point that can be checked though: 1. What is your BIOS settings for controller? Can you try switching it between Legacy/Compatible mode? There was a change that fixed behavior for detecting different BIOS settings. 2. You can try using modular driver for this one, this means adding this to kernel: nodevice ata device atacore device ataati device ataahci It's not build config: === root@HP:/usr/src # vim /usr/src/sys/amd64/conf/HP # include GENERIC ident HPKERNEL nodevice ata nodevice siis device atacore device ataati device ataahci = error: = MAKE=make sh /usr/src/sys/conf/newvers.sh HPKERNEL /usr/local/bin/svnversion cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector vers.c linking kernel.debug ata-ahci.o: In function `ata_ahci_ata_attach': /usr/src/sys/dev/ata/chipsets/ata-ahci.c:128: undefined reference to `ata_pci_ch_attach' /usr/src/sys/dev/ata/chipsets/ata-ahci.c:129: undefined reference to `ata_pci_ch_detach' ata-ahci.o: In function `ata_ahci_probe': /usr/src/sys/dev/ata/chipsets/ata-ahci.c:97: undefined reference to `ata_pcivendor2str' /usr/src/sys/dev/ata/chipsets/ata-ahci.c:100: undefined reference to `ata_pcivendor2str' ata-ahci.o: In function `ata_ahci_chipinit': /usr/src/sys/dev/ata/chipsets/ata-ahci.c:165: undefined reference to `ata_generic_intr' /usr/src/sys/dev/ata/chipsets/ata-ahci.c:165: undefined reference to `ata_setup_interrupt' ata-ahci.o:(.data+0x1c0): undefined reference to `ata_pci_devclass' ata-ahci.o:(.data+0x200): undefined reference to `ata_pci_devclass' ata-ahci.o:(.data+0x2c8): undefined reference to `ata_pci_detach' ata-ahci.o:(.data+0x2d8): undefined reference to `ata_pci_suspend' ata-ahci.o:(.data+0x2e8): undefined reference to `ata_pci_resume' ata-ahci.o:(.data+0x308): undefined reference to `ata_pci_read_ivar' ata-ahci.o:(.data+0x318): undefined reference to `ata_pci_write_ivar' ata-ahci.o:(.data+0x328): undefined reference to `ata_pci_alloc_resource' ata-ahci.o:(.data+0x338): undefined reference to `ata_pci_release_resource' ata-ahci.o:(.data+0x368): undefined reference to `ata_pci_setup_intr' ata-ahci.o:(.data+0x378): undefined reference to `ata_pci_teardown_intr' ata-ahci.o:(.data+0x3b8): undefined reference to `ata_pci_attach' ata-ahci.o:(.data+0x3c8): undefined reference to `ata_pci_detach' ata-ahci.o:(.data+0x3d8): undefined reference to `ata_pci_suspend' ata-ahci.o:(.data+0x3e8): undefined reference to `ata_pci_resume' ata-ahci.o:(.data+0x408): undefined reference to `ata_pci_read_ivar' ata-ahci.o:(.data+0x418): undefined reference to `ata_pci_write_ivar' ata-ahci.o:(.data+0x428): undefined reference to `ata_pci_alloc_resource' ata-ahci.o:(.data+0x438): undefined reference to `ata_pci_release_resource' ata-ahci.o:(.data+0x468): undefined reference to `ata_pci_setup_intr' ata-ahci.o:(.data+0x478): undefined reference to `ata_pci_teardown_intr' ata-ahci.o:(.data+0x488): undefined reference to `ata_pci_read_config' ata-ahci.o:(.data+0x498): undefined reference to `ata_pci_write_config' ata-ahci.o:(.data+0x4a8): undefined reference to `ata_pci_print_child' ata-ahci.o:(.data+0x4b8
Re: No ATA disks on 9.1-RC3
19.11.2012 17:18, Volodymyr Kostyrko пишет: 19.11.2012 15:01, Alex Keda wrote: It's not build config: === root@HP:/usr/src # vim /usr/src/sys/amd64/conf/HP # include GENERIC ident HPKERNEL nodevice ata nodevice siis device atacore device ataati device ataahci Looks like I have missed `device atapci` here. OK, I rebuild kernel - no happy - error remains ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: No ATA disks on 9.1-RC3
On 19.11.2012 18:50, Warren Block wrote: On Mon, 19 Nov 2012, Alex Keda wrote: I try update my laptop - Compaq 6715s from 9.0 to 9.1-rc3 it cannot boot, because no HDD found dmesg from 9.0/9.1 and pciconf in attached files If there is an IDE/AHCI mode setting in the BIOS, switch it to the other setting. It's HP. No BIOS settings for hard drive/SATA controller ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [HEADSUP] current switched by default to pkgng
On 10.10.2012 17:44, Baptiste Daroussin wrote: Hi all, If you are using the ports tree on a FreeBSD current setup, then you are concerned by the announce. As nvidia-drivers has been fixed and is now properly working with pkgng, the ports tree as been switch by default to use pkgng on FreeBSD Current based on version = 117 which was the version when we tested the switch code. Make sure to read UPDATING (from ports) to correctly migrate your system or find instruction to make your system still running with legacy pkg_install tools. I try use it on my home server. In make conf, I have WITHOUT_X11=yes NO_GUI=yes I run pkg2ng, set mirror in pkg.conf and, run pkg upgrade -y It update some packages, and install ~20 new packages, named x* How I can say It's server, I do not need X on them? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [HEADSUP] current switched by default to pkgng
On 21.10.2012 13:39, Edho Arief wrote: On Sun, Oct 21, 2012 at 4:33 PM, Alex Keda ad...@lissyara.su wrote: It update some packages, and install ~20 new packages, named x* How I can say It's server, I do not need X on them? Install the -nox11 variant of the package. for example, /usr/ports/editors/vim/Makefile have . if defined(NO_GUI) || defined(WITHOUT_GUI) WITHOUT_X11=yes . endif but, it not have -nox11 port Athlon5000# pkg search vim vim-7.3.669Vi workalike, with many additional xpi-vimperator-3.5 Vim look and feel for Firefox ja-jvim-3.0.j2.1a_4Japanized Vim-3.0 vim-lite-7.3.669 Vi workalike, with many additional vimpager-1.7.5 Use ViM as a pager Athlon5000# ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [HEADSUP] current switched by default to pkgng
On 20.10.2012 11:23, Sergey V. Dyatko wrote:
On Fri, 19 Oct 2012 20:32:31 +0400
Alex Keda ad...@lissyara.su wrote:
On 19.10.2012 20:21, Alex Keda wrote:
On 19.10.2012 19:59, Chris Rees wrote:
On 19 October 2012 16:16, Alex Keda ad...@lissyara.su wrote:
On 19.10.2012 19:10, Vincent Hoffman wrote:
On 19/10/2012 15:39, Alex Keda wrote:
pkg command does not have key for list options - no
autocompletions
for example, for service command, I use
complete service'n/*/`service -l`/'
in .cshrc
what I can use for pkg command?
horrible but working example
pkg help 21 | sed -e '1,/Commands supported:/d ; /For more
information on the different commands/,$d; s/^ *// ;
s/ .*.*$// ;/^$/d'
There's bound to be better ways, I was just bored enough to
knock this up. note s/^*// is a tab, while s/ .*.*$// is
2 spaces dont think our sed has any other way to express tab
other than an actual tab (ctrl-v then tab on the command line)
it's crazy =)
may be add -l options?
For Bourne-style shell:
`pkg help 21 | sed -nE 's,^ +(.*),\1,p'`
For csh-style shell:
`pkg help | sed -nE 's,^ +(.*),\1,p'`
where the bit between ^ and + is a tab character. You can type the
tab character on a command prompt by using Ctrl+V then tab, or just
type it normally in the script.
Hope that helps in the meantime.
Chris
dc7700p# pkg
-cDisplays Performs a and
check debug from insidelocal
package packages remotesearchsystem
updating
-dDisplays Performs a and
. skipped
Displays Opens a against catalogues
debug from insidelink package
packages register searchsystemupdate
dc7700p#
dc7700p# grep pkg /root/.cshrc
complete pkg'n/*/`pkg help | sed -nE s,^
+(.*),\1,p`/'
some not work... I try my own string:
complete pkg 'n/*/`pkg help | grep Commands supported:
--after-context=100 | grep ^\s | awk {print $1}`/'
output identical. maybe pipe not work in this place?
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
freebsd-current-unsubscr...@freebsd.org
it's a good crutch =)
dc7700p# pkg
addautoremove check create fetch info
query remove rquery setshlib update upgrade
which
audit backup clean delete help install
register repo search shell stats updating
version
dc7700p# pkg
dc7700p# grep pkg /root/.cshrc
complete pkg 'n/*/`pkg help | grep Commands supported:
--after-context=100 | grep ^\s | cut -d -f 1`/'
dc7700p#
https://github.com/yoursbofh/pkgng-tcsh/blob/master/dot.cshrc_pkg
Unfortunately, I do not know how to do something like `pkg command
-keys pkgname`
i.e.
'n/audit/' 'c/-/(F q)/' '`pkg query %n-%v`/'
doesn't work :(
[tiger@laptop]:~%pkg audit [tab]
Missing separator '/' after completion .
need escape '
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [HEADSUP] current switched by default to pkgng
On 10.10.2012 17:44, Baptiste Daroussin wrote: Hi all, If you are using the ports tree on a FreeBSD current setup, then you are concerned by the announce. As nvidia-drivers has been fixed and is now properly working with pkgng, the ports tree as been switch by default to use pkgng on FreeBSD Current based on version = 117 which was the version when we tested the switch code. Make sure to read UPDATING (from ports) to correctly migrate your system or find instruction to make your system still running with legacy pkg_install tools. regards, Bapt pkg command does not have key for list options - no autocompletions for example, for service command, I use complete service'n/*/`service -l`/' in .cshrc what I can use for pkg command? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [HEADSUP] current switched by default to pkgng
On 19.10.2012 19:10, Vincent Hoffman wrote: On 19/10/2012 15:39, Alex Keda wrote: On 10.10.2012 17:44, Baptiste Daroussin wrote: Hi all, If you are using the ports tree on a FreeBSD current setup, then you are concerned by the announce. As nvidia-drivers has been fixed and is now properly working with pkgng, the ports tree as been switch by default to use pkgng on FreeBSD Current based on version = 117 which was the version when we tested the switch code. Make sure to read UPDATING (from ports) to correctly migrate your system or find instruction to make your system still running with legacy pkg_install tools. regards, Bapt pkg command does not have key for list options - no autocompletions for example, for service command, I use complete service'n/*/`service -l`/' in .cshrc what I can use for pkg command? horrible but working example pkg help 21 | sed -e '1,/Commands supported:/d ; /For more information on the different commands/,$d; s/^ *// ; s/ .*.*$// ;/^$/d' There's bound to be better ways, I was just bored enough to knock this up. note s/^*// is a tab, while s/ .*.*$// is 2 spaces dont think our sed has any other way to express tab other than an actual tab (ctrl-v then tab on the command line) it's crazy =) may be add -l options? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [HEADSUP] current switched by default to pkgng
On 19.10.2012 19:59, Chris Rees wrote:
On 19 October 2012 16:16, Alex Keda ad...@lissyara.su wrote:
On 19.10.2012 19:10, Vincent Hoffman wrote:
On 19/10/2012 15:39, Alex Keda wrote:
pkg command does not have key for list options - no autocompletions
for example, for service command, I use
complete service'n/*/`service -l`/'
in .cshrc
what I can use for pkg command?
horrible but working example
pkg help 21 | sed -e '1,/Commands supported:/d ; /For more information
on the different commands/,$d; s/^ *// ; s/ .*.*$// ;/^$/d'
There's bound to be better ways, I was just bored enough to knock this up.
note s/^*// is a tab, while s/ .*.*$// is 2 spaces
dont think our sed has any other way to express tab other than an actual
tab (ctrl-v then tab on the command line)
it's crazy =)
may be add -l options?
For Bourne-style shell:
`pkg help 21 | sed -nE 's,^ +(.*),\1,p'`
For csh-style shell:
`pkg help | sed -nE 's,^ +(.*),\1,p'`
where the bit between ^ and + is a tab character. You can type the
tab character on a command prompt by using Ctrl+V then tab, or just
type it normally in the script.
Hope that helps in the meantime.
Chris
dc7700p# pkg
-cDisplays Performs a and
check debug from insidelocal
package packages remotesearchsystem
updating
-dDisplays Performs a and
. skipped
Displays Opens a against catalogues
debug from insidelink package
packages register searchsystemupdate
dc7700p#
dc7700p# grep pkg /root/.cshrc
complete pkg'n/*/`pkg help | sed -nE s,^ +(.*),\1,p`/'
some not work... I try my own string:
complete pkg 'n/*/`pkg help | grep Commands supported:
--after-context=100 | grep ^\s | awk {print $1}`/'
output identical. maybe pipe not work in this place?
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [HEADSUP] current switched by default to pkgng
On 19.10.2012 20:21, Alex Keda wrote:
On 19.10.2012 19:59, Chris Rees wrote:
On 19 October 2012 16:16, Alex Keda ad...@lissyara.su wrote:
On 19.10.2012 19:10, Vincent Hoffman wrote:
On 19/10/2012 15:39, Alex Keda wrote:
pkg command does not have key for list options - no autocompletions
for example, for service command, I use
complete service'n/*/`service -l`/'
in .cshrc
what I can use for pkg command?
horrible but working example
pkg help 21 | sed -e '1,/Commands supported:/d ; /For more information
on the different commands/,$d; s/^ *// ; s/ .*.*$// ;/^$/d'
There's bound to be better ways, I was just bored enough to knock this up.
note s/^*// is a tab, while s/ .*.*$// is 2 spaces
dont think our sed has any other way to express tab other than an actual
tab (ctrl-v then tab on the command line)
it's crazy =)
may be add -l options?
For Bourne-style shell:
`pkg help 21 | sed -nE 's,^ +(.*),\1,p'`
For csh-style shell:
`pkg help | sed -nE 's,^ +(.*),\1,p'`
where the bit between ^ and + is a tab character. You can type the
tab character on a command prompt by using Ctrl+V then tab, or just
type it normally in the script.
Hope that helps in the meantime.
Chris
dc7700p# pkg
-cDisplays Performs a and
check debug from insidelocal
package packages remotesearchsystem
updating
-dDisplays Performs a and
. skipped
Displays Opens a against catalogues
debug from insidelink package
packages register searchsystemupdate
dc7700p#
dc7700p# grep pkg /root/.cshrc
complete pkg'n/*/`pkg help | sed -nE s,^ +(.*),\1,p`/'
some not work... I try my own string:
complete pkg 'n/*/`pkg help | grep Commands supported:
--after-context=100 | grep ^\s | awk {print $1}`/'
output identical. maybe pipe not work in this place?
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
it's a good crutch =)
dc7700p# pkg
addautoremove check create fetch info query
remove rquery setshlib update upgrade
which
audit backup clean delete help install
register repo search shell stats updating
version
dc7700p# pkg
dc7700p# grep pkg /root/.cshrc
complete pkg 'n/*/`pkg help | grep Commands supported:
--after-context=100 | grep ^\s | cut -d -f 1`/'
dc7700p#
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: pkg (aka pkgng) 1.0 released
15.10.2012 01:55, Bryan Drewery пишет: On 8/30/2012 10:56 AM, John Nielsen wrote: Running ps in another terminal shows pkg query %n-%v. Since the actual pkg is now gone, I suspect this is really /usr/sbin/pkg. I further suspect that it's waiting for y/n input (whether to install the binary pkg) on its nonexistent stdin somewhere. I killed it (pkg) and portupgrade seemed to finish normally. This waiting is the bootstrapper. Can you see if this is still an issue? It should be fixed by r239663 and r239664, which were fulled MFC'd to 9-STABLE, 9.1, and 8-STABLE now. http://svn.freebsd.org/changeset/base/239663 http://svn.freebsd.org/changeset/base/239664 root# pkg check -a usage: pkg check [-dsr] [-vy] [-a | -gxX pattern] For more information see 'pkg help check'. root# what wrong? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: r234000: i386 freeze when HT enabled
09.04.2012 19:37, Gavin Atkinson пишет: On Mon, 9 Apr 2012, Alex Keda wrote: FreeBSD bsd-test.moskb.local 9.9-CURRENT FreeBSD 10.0-CURRENT #0 r234000: Sun Apr 8 03:02:51 MSK 2012 root@bsd-test.moskb.local:/usr/obj/usr/src/sys/GENERIC i386 Proliant 320 G4 freeze with Hyper-Threading enabled with last Line some about CPU1 AP Launched with disabled - boot OK Can you try reverting r233961 and seeing if this fixes boot for you? No. Yesterday, I reinstall all my desktops and laptops to 9.0 last 4-5 month too many not fixed problems with CURRENT- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
r234000: i386 freeze when HT enabled
FreeBSD bsd-test.moskb.local 9.9-CURRENT FreeBSD 10.0-CURRENT #0 r234000: Sun Apr 8 03:02:51 MSK 2012 root@bsd-test.moskb.local:/usr/obj/usr/src/sys/GENERIC i386 Proliant 320 G4 freeze with Hyper-Threading enabled with last Line some about CPU1 AP Launched with disabled - boot OK ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD 10.0-CURRENT/amd64: clientsoftware crashes since make world of today at revision r233779
02.04.2012 16:32, O. Hartmann пишет: Hello out there. My FreeBSD 10 box is at revision r233779. I updated the sources this morning and made a buildworld successfully. After a reboot of the box, I witness several bad issues. Firefox, for instance, is droppimng a core now when starting. Using portmaster for updates produces a lot of Segmentation faults on the screen. Othe minor clients which were working prior to the update today (last makeworl on Friday last week) aren't any more and dropping cores. Does anyone also realize this on FreeBSD 10 boxes? I use CLANG as the base compiler and also for the ports (for those which are compiling with CLANG). Regards, Oliver confirm, for amd64 using gcc ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: projects/mfi_head to -current next week
On 16.03.2012 19:39, Doug Ambrisko wrote: Hi folks, I'd like to start merging mfi(4) from projects/head_mfi into -current next week. The mfi(4) driver is stable and I don't know of any issues with it now. I fixed a few issues that I knew of this past week. Several people have contributed to this. LSI did the base HW support. This update supports all current mfi based cards. It supports JBOD via creating /sys/mfisyspd* entries for each disk. When a disk is pulled from the controller the node goes away and when a disk is inserted it creates an entry. Using a fairly new MegaCli, it can also control how JBOD support works. We may need to update our port. This JBOD support is not the same as CAM pass through that some have hacked to make disks appear as da*. Several people are using this driver now so I feel it is stable enough to hit the tree. More eyes and people using this will make it better. This new HW is showing up more and more in new systems so it will make it easier for people to use FreeBSD on these machines and have it just work. Thanks to LSI for the initial HW support and all of the people that have been testing and getting it in shape to commit. Good news! How about new hardware? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: SU+J and fsck problem ?
On 10.03.2012 14:01, jb wrote: Hi, FB9.0-RELEASE; no updates or recompilation. In multi-user mode: $ mount /dev/ada0s2a on / (ufs, local, journaled soft-updates) The fs was in normal state (no known problem, clean shutdown), Booted by choice in single-user mode. # mount /dev/ada0s2a on / (ufs, local, read-only) # fsck -F ** /dev/ada0s2a USE JOURNAL? [yn] y ** SU+J recovering /dev/ada0s2a ** Reading 33554432 byte journal from inode 4. RECOVER? [yn] y ** ... ** Processing journal entries. WRITE CHANGES? [yn] y ** 208 journal records in 13312 bytes for 50% utilization ** Freed 0 inodes (0 dirs) 6 blocks, and 0 frags. * FILE SYSTEM MARKED CLEAN # fsck -F ** /dev/ada0s2a USE JOURNAL? [yn] n ** Skipping journal, falling through to full fsck ** Last Mounted on / ** Root file system ** Phase 1 - Check Blocks and Sizes INCORRECT BLOCK COUNT I=114700 (8 should be 0) CORRECT? [yn] n INCORRECT BLOCK COUNT I=196081 (32 should be 8) CORRECT? [yn] n INCORRECT BLOCK COUNT I=474381 (32 should be 8) CORRECT? [yn] n ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups FREE BLOCK COUNTS(S) WRONG IN SUPERBLK SALVAGE? [yn] n SUMMARY INFORMATION BAD SALVAGE? [yn] n BLK(S) MISSING IN BIT MAPS SALVAGE? [yn] n 266075 files, 939314 used, 1896628 free (2724 frags, 236738 blocks, 0.1% fragmentation) * FILE SYSTEM MARKED DIRTY * * FILE SYSTEM WAS MODIFIED * * PLEASE RERUN FSCK * # fsck -F ** /dev/ada0s2a USE JOURNAL? [yn] y ** SU+J recovering /dev/ada0s2a Journal timestamp does not match fs mount time ** Skipping journal, falling through to full fsck ** Last Mounted on / ** Root file system ** Phase 1 - Check Blocks and Sizes INCORRECT BLOCK COUNT I=114700 (8 should be 0) CORRECT? [yn] y INCORRECT BLOCK COUNT I=196081 (32 should be 8) CORRECT? [yn] y INCORRECT BLOCK COUNT I=474381 (32 should be 8) CORRECT? [yn] y ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups FREE BLOCK COUNTS(S) WRONG IN SUPERBLK SALVAGE? [yn] y SUMMARY INFORMATION BAD SALVAGE? [yn] y BLK(S) MISSING IN BIT MAPS SALVAGE? [yn] y 266075 files, 939314 used, 1896629 free (2725 frags, 236738 blocks, 0.1% fragmentation) * FILE SYSTEM MARKED CLEAN * * FILE SYSTEM WAS MODIFIED * # Summary: 1. # fsck -F ## recovery done with J 2. # fsck -F ## no recovery; fs marked dirty; time stamp modified Why during this step there were incorrect block counts reported if the fs was recovered and marked clean in step 1 ? Despite the fact that choice of no recovery was made, the fs was marked dirty (based on false assumption above ?, and time stamp ?) 3. # fsck -F ## forced skipped Journal Same question as in step 2, based on which it accepted the choice of recovery ... Note: after step 2: 1896628 free and 2724 frags in 266075 files, 939314 used, 1896620 free (2724 frags, 236738 blocks, ... after step 3: 1896629 free and 2725 frags in 266075 files, 939314 used, 1896629 free (2725 frags, 236738 blocks, ... Questions: - is the fsck working properly with SU+J fs ? Note: fsck(8) -F ... -B ... It is recommended that you perform foreground fsck on your systems periodically and whenever you encounter file-system-related panics. - would the fs as after step 1, and steps 1-3 or 1,3 be considered recovered: - structurally ? - identical ?, does it matter ? - integrally ? Any comments before I file a PR# ? jb SUJ very strange work. it's can say - filesystem OK, but, after full boot system crash - file system have errors... I disable it on all production hosts, use only on desktop. If I manually run fsck after crash and unexpected reboot - fsck _always_ find errors, unhandled by SUJ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
-CURRENT is broken?
I have 2 machine, i386 and amd64 world rebuild tonight all work. all applications crash with core dump... I reinstall 9.0 using iso images on my hard drive (mdconfig, mount, tar, unxz, and chflags from /rescue - work perfectly), rebuild world, to yesterday - all OK. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: -CURRENT is broken?
On 05.03.2012 19:39, Alex Keda wrote: I have 2 machine, i386 and amd64 world rebuild tonight all work. all applications crash with core dump... read as world rebuild tonight not work =)) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Xorg - monitor off after start
On 24.02.2012 12:37, Alex Keda wrote: problem, first described: http://lists.freebsd.org/pipermail/freebsd-current/2011-December/030528.html on last days 2011 year, all work OK, without some custom kernel new year - old problems =) if I rename drm.ko - all OK. with drm.ko - I have monitor off =( yesterday, all work OK FreeBSD lissyara.moskb.local 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r232326: Thu Mar 1 08:33:24 MSK 2012 root@lissyara.moskb.local:/usr/obj/usr/src/sys/GENERIC amd64 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Xorg - monitor off after start
problem, first described: http://lists.freebsd.org/pipermail/freebsd-current/2011-December/030528.html on last days 2011 year, all work OK, without some custom kernel new year - old problems =) if I rename drm.ko - all OK. with drm.ko - I have monitor off =( X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 9.9-CURRENT amd64 Current Operating System: FreeBSD lissyara.moskb.local 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r232094: Fri Feb 24 08:30:45 MSK 2012 root@lissyara.moskb.local:/usr/obj/usr/src/sys/GENERIC amd64 Build Date: 12 December 2011 12:24:07PM Current version of pixman: 0.24.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Fri Feb 24 12:18:26 2012 (II) Loader magic: 0x7ba500 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (--) PCI:*(0:1:5:0) 1002:791e:103c:12ff Advanced Micro Devices [AMD] nee ATI RS690 [Radeon X1200 Series] rev 0, Mem @ 0xd000/134217728, 0xd850/65536, 0xd840/1048576, I/O @ 0x1100/256, BIOS @ 0x/65536 (==) Using default built-in configuration (30 lines) (==) --- Start of built-in configuration --- Section Device Identifier Builtin Default ati Device 0 Driver ati EndSection Section Screen Identifier Builtin Default ati Screen 0 Device Builtin Default ati Device 0 EndSection Section Device Identifier Builtin Default vesa Device 0 Driver vesa EndSection Section Screen Identifier Builtin Default vesa Screen 0 Device Builtin Default vesa Device 0 EndSection Section Device Identifier Builtin Default fbdev Device 0 Driver fbdev EndSection Section Screen Identifier Builtin Default fbdev Screen 0 Device Builtin Default fbdev Device 0 EndSection Section ServerLayout Identifier Builtin Default Layout Screen Builtin Default ati Screen 0 Screen Builtin Default vesa Screen 0 Screen Builtin Default fbdev Screen 0 EndSection (==) --- End of built-in configuration --- (==) ServerLayout Builtin Default Layout (**) |--Screen Builtin Default ati Screen 0 (0) (**) | |--Monitor default monitor (**) | |--Device Builtin Default ati Device 0 (==) No monitor specified for screen Builtin Default ati Screen 0. Using a default monitor configuration. (**) |--Screen Builtin Default vesa Screen 0 (1) (**) | |--Monitor default monitor (**) | |--Device Builtin Default vesa Device 0 (==) No monitor specified for screen Builtin Default vesa Screen 0. Using a default monitor configuration. (**) |--Screen Builtin Default fbdev Screen 0 (2) (**) | |--Monitor default monitor (**) | |--Device Builtin Default fbdev Device 0 (==) No monitor specified for screen Builtin Default fbdev Screen 0. Using a default monitor configuration. (==) Automatically adding devices (==) Automatically enabling devices (==) FontPath set to: /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/ (==) ModulePath set to /usr/local/lib/xorg/modules (II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on HAL to provide the list of input devices. If no devices become available, reconfigure HAL or disable AutoAddDevices. (II) LoadModule: extmod (II) Loading /usr/local/lib/xorg/modules/extensions/libextmod.so (II) Module extmod: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: dbe (II) Loading /usr/local/lib/xorg/modules/extensions/libdbe.so (II) Module dbe: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server
Re: Enhancing the user experience with tcsh
On 10.02.2012 21:07, Chuck Burns wrote: set prompt = [%n@%m]%c04%# it's not needed need some as alias ll ls -lAhG alias ls ls -G set autolist = TAB bindkey \e[3~ delete-char and other _really_ necessary settings complete chown 'p/1/u/' complete man'C/*/c/' complete service'n/*/`service -l`/' need as example. may be in include file, may be in .cshrc ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
9.0-BETA3 - network scripts problem
I install 9.0-BETA3 i386, set next rc.conf configurations: mail# grep -E hostname|ifconfig /etc/rc.conf ifconfig_em0=inet 91.227.17.15 netmask 255.255.255.0 hostname=mail.AeroStarContract.ru mail# after reboot with plugged LAN cable, I have this strange network configuration: lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=3RXCSUM,TXCSUM inet 127.0.0.1 netmask 0xff00 em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=209bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC ether 00:30:48:71:11:a4 inet 91.227.16.17 netmask 0xff00 broadcast 91.227.16.17 media: Ethernet autoselect (1000baseT full-duplex) status: active em1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=209bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC ether 00:30:48:71:11:a5 inet 91.227.16.17 netmask 0xff00 broadcast 91.227.16.17 media: Ethernet autoselect status: no carrier ipfw0: flags=8801UP,SIMPLEX,MULTICAST metric 0 mtu 65536 if I unplug network cable and reboot - network configurations is correct: em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=209bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC ether 00:30:48:71:11:a4 inet 91.227.17.15 netmask 0xff00 broadcast 91.227.17.255 media: Ethernet autoselect (1000baseT full-duplex) status: active em1: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 options=209bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC ether 00:30:48:71:11:a5 media: Ethernet autoselect status: no carrier ipfw0: flags=8801UP,SIMPLEX,MULTICAST metric 0 mtu 65536 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=3RXCSUM,TXCSUM inet 127.0.0.1 netmask 0xff00 91.227.16.17 - is IP for DNS A record for mail.AeroStarContract.ru if I run /etc/rc.d/netif start with plugged cable - network configurations reset to first listing. If cable unplugged - to second. if I change hostname to non-existent: mail# grep -E hostname|ifconfig /etc/rc.conf ifconfig_em0=inet 91.227.17.15 netmask 255.255.255.0 hostname=mail.AeroStarContract-bad.ru mail# reboot with/without LAN cable get good network configurations. change A DNS record for mail.AeroStarContract.ru from 91.227.16.17 to 91.227.16.27 get this configurations, with plugged cable: lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=3RXCSUM,TXCSUM inet 127.0.0.1 netmask 0xff00 em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=209bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC ether 00:30:48:71:11:a4 inet 91.227.16.27 netmask 0xff00 broadcast 91.227.16.27 media: Ethernet autoselect (1000baseT full-duplex) status: active em1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=209bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC ether 00:30:48:71:11:a5 inet 91.227.16.27 netmask 0xff00 broadcast 91.227.16.27 media: Ethernet autoselect status: no carrier ipfw0: flags=8801UP,SIMPLEX,MULTICAST metric 0 mtu 65536 with unplugged - all correct. setting A record to 91.227.17.15 (as in rc.conf) get this, with plugged cable: lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=3RXCSUM,TXCSUM inet 127.0.0.1 netmask 0xff00 em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=209bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC ether 00:30:48:71:11:a4 inet 91.227.17.15 netmask 0xff00 broadcast 91.227.17.15 media: Ethernet autoselect (1000baseT full-duplex) status: active em1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=209bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC ether 00:30:48:71:11:a5 inet 91.227.17.15 netmask 0xff00 broadcast 91.227.17.15 media: Ethernet autoselect status: no carrier ipfw0: flags=8801UP,SIMPLEX,MULTICAST metric 0 mtu 65536 with unplugged - all correct. = DNS zone AeroStarContract.ru use our DNS servers, used in resolv.conf: mail# more /etc/resolv.conf nameserver 91.227.16.10 nameserver 91.227.17.11 mail# I think, it try find hostname in DNS (DNS server in some network with server) and use finded IP to set all interfaces. It's serious mistake, because I find it when server first booting and set to interface IP used in another server =)) All names, IP addresses and another information - is real. ___ freebsd-current@freebsd.org mailing list
Re: svn commit: r220430 - head/sys/amd64/amd64
08.04.2011 14:23, Andriy Gapon пишет: on 08/04/2011 00:32 John Baldwin said the following: Author: jhb Date: Thu Apr 7 21:32:25 2011 New Revision: 220430 URL: http://svn.freebsd.org/changeset/base/220430 Log: If a system call does not request a full interrupt return, use a fast path via the sysretq instruction to return from the system call. This was removed in 190620 and not quite fully restored in 195486. This resolves most of the performance regression in system call microbenchmarks between 7 and 8 on amd64. Reviewed by: kib MFC after: 1 week I think that this commit (plus r220431) has broken something in my environment. After updating to the most recent head I started to get semi-random problems in various areas: - named would consistently fail to start, but with different errors (assertions) - ^Z and fg result in a process getting SIGSEGV - X sometimes fails to start complaining about failed VT switch Reverting just these two commits restores sanity. Just in case, my processor is AMD (arch is obviously amd64). confirm Modified: head/sys/amd64/amd64/exception.S Modified: head/sys/amd64/amd64/exception.S == --- head/sys/amd64/amd64/exception.SThu Apr 7 21:29:34 2011 (r220429) +++ head/sys/amd64/amd64/exception.SThu Apr 7 21:32:25 2011 (r220430) @@ -339,6 +339,9 @@ IDTVEC(prot) * and the new privilige level. We are still running on the old user stack * pointer. We have to juggle a few things around to find our stack etc. * swapgs gives us access to our PCPU space only. + * + * We do not support invoking this from a custom %cs or %ss (e.g. using + * entries from an LDT). */ IDTVEC(fast_syscall) swapgs @@ -380,6 +383,36 @@ IDTVEC(fast_syscall) movq%rsp,%rdi callsyscall movqPCPU(CURPCB),%rax + testq $PCB_FULL_IRET,PCB_FLAGS(%rax) + jne 3f +1: /* Check for and handle AST's on return to userland. */ + cli + movqPCPU(CURTHREAD),%rax + testl $TDF_ASTPENDING | TDF_NEEDRESCHED,TD_FLAGS(%rax) + je 2f + sti + movq%rsp, %rdi + callast + jmp 1b +2: /* Restore preserved registers. */ + MEXITCOUNT + movqTF_RDI(%rsp),%rdi /* bonus; preserve arg 1 */ + movqTF_RSI(%rsp),%rsi /* bonus: preserve arg 2 */ + movqTF_RDX(%rsp),%rdx /* return value 2 */ + movqTF_RAX(%rsp),%rax /* return value 1 */ + movqTF_RBX(%rsp),%rbx /* C preserved */ + movqTF_RBP(%rsp),%rbp /* C preserved */ + movqTF_R12(%rsp),%r12 /* C preserved */ + movqTF_R13(%rsp),%r13 /* C preserved */ + movqTF_R14(%rsp),%r14 /* C preserved */ + movqTF_R15(%rsp),%r15 /* C preserved */ + movqTF_RFLAGS(%rsp),%r11/* original %rflags */ + movqTF_RIP(%rsp),%rcx /* original %rip */ + movqTF_RSP(%rsp),%r9/* user stack pointer */ + movq%r9,%rsp/* original %rsp */ + swapgs + sysretq +3: /* Requested full context restore, use doreti for that. */ MEXITCOUNT jmp doreti ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
login.conf: maxproc does not work when command running from cron?
I create login class: lissyara# grep id100 --after-context=7 /etc/login.conf id100:\ :coredumpsize=1:\ :cputime=60s:\ :maxproc=12:\ :openfiles=32:\ :priority=20:\ :tc=default: lissyara# then, run command: lissyara# cap_mkdb -v /etc/login.conf cap_mkdb: 10 capability records lissyara# add user: lissyara# grep ^test1234 /etc/master.passwd test1234:$1$kj/WOTuN$vLGcOBPv9ro8eljOe.ChA1:1002:1004:id100:0:0:User :/home/test1234:/bin/sh lissyara# add cron job for user: lissyara# crontab -l -u test1234 * * * * * /bin/sleep 72000 * * * * * /bin/sleep 72000 * * * * * /bin/sleep 72000 * * * * * /bin/sleep 72000 * * * * * /bin/sleep 72000 * * * * * /bin/sleep 72000 * * * * * /bin/sleep 72000 * * * * * /bin/sleep 72000 * * * * * /bin/sleep 72000 * * * * * /bin/sleep 72000 * * * * * /bin/sleep 72000 * * * * * /bin/sleep 72000 * * * * * /bin/sleep 72000 lissyara# after some time I see lot sleep processes in ps output lissyara# ps -auxww | grep ^test1234 | grep sleep | wc -l 130 lissyara# 130 12 If I running commands from ssh session - all OK, I cannot run more than maxproc processes... tested on 8.1 (i386), 8.2 (i386), -CURRENT (amd64) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: login.conf: maxproc does not work when command running from cron?
03.03.2011 11:52, Alex Keda пишет: I create login class: lissyara# grep id100 --after-context=7 /etc/login.conf id100:\ :coredumpsize=1:\ :cputime=60s:\ :maxproc=12:\ :openfiles=32:\ :priority=20:\ :tc=default: lissyara# another parameters (I test cputime, priority) work correct ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: login.conf: maxproc does not work when command running from cron?
03.03.2011 15:11, Sergey Kandaurov пишет: 2011/3/3 Alex Kedaad...@lissyara.su: 03.03.2011 11:52, Alex Keda пишет: I create login class: lissyara# grep id100 --after-context=7 /etc/login.conf id100:\ :coredumpsize=1:\ :cputime=60s:\ :maxproc=12:\ :openfiles=32:\ :priority=20:\ :tc=default: lissyara# another parameters (I test cputime, priority) work correct Indeed. and I was able to reproduce it too, fyi. That doesn't really work because cron doesn't perform further fork()s after RLIMIT_NPROC limit is set, but it only exec() a task. it's not good. it's problem for some situations - hosting servers, etc... E.g. my cron implementation used at work does an additional fork necessary for some teardown work thus it doesn't suffer from this problem. what's your cron implementation? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: WARNING: Non-uniform processors.
09.07.2010 14:41, Ivan Voras пишет: On 07/08/10 18:42, Alex Keda wrote: When booting, I have strange message. All work OK (processor with hyperthreading, but system seems it as 1 CPU ). lissyara-gp# dmesg Copyright (c) 1992-2010 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 9.0-CURRENT #0 r209745: Wed Jul 7 06:08:36 MSD 2010 r...@lissyara-gp.grand-prix:/usr/obj/usr/src/sys/GENERIC i386 WARNING: WITNESS option enabled, expect reduced performance. CPU: Intel(R) Pentium(R) 4 CPU 3.06GHz (3056.87-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf29 Family = f Model = 2 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=0x4400CNXT-ID,xTPR real memory = 1611137024 (1536 MB) avail memory = 1559203840 (1486 MB) Event timer LAPIC frequency 0 Hz quality 500 ACPI APIC Table:COMPAQ BROOKDG WARNING: Non-uniform processors. WARNING: Using suboptimal topology. ioapic0: Changing APIC ID to 8 ioapic0Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0:COMPAQ CPQ0050 on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 5ff0 (3) failed Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0:24-bit timer at 3.579545MHz port 0xf808-0xf80b on acpi0 cpu0:ACPI CPU on acpi0 Yes, your situation looks a bit strange, but maybe it's because of the Compaq (or early HPaq) brand, they did strange things with BIOSes in those days. Apparently, the OS detects only one logical CPU (no hyperthreading) on your system, but it looks like HTT is enabled, so this might be the cause of your message. In any case, you will probably not have any problems with this configuration. HTT in those days sucked anyway. On the other hand, you are running a CURRENT kernel with WITNESS and other debugging enabled, so as the boot message says, expect your system to run very slow. OK. Thanks for explanation! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
WARNING: Non-uniform processors.
When booting, I have strange message. All work OK (processor with hyperthreading, but system seems it as 1 CPU ). lissyara-gp# dmesg Copyright (c) 1992-2010 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 9.0-CURRENT #0 r209745: Wed Jul 7 06:08:36 MSD 2010 r...@lissyara-gp.grand-prix:/usr/obj/usr/src/sys/GENERIC i386 WARNING: WITNESS option enabled, expect reduced performance. CPU: Intel(R) Pentium(R) 4 CPU 3.06GHz (3056.87-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf29 Family = f Model = 2 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=0x4400CNXT-ID,xTPR real memory = 1611137024 (1536 MB) avail memory = 1559203840 (1486 MB) Event timer LAPIC frequency 0 Hz quality 500 ACPI APIC Table: COMPAQ BROOKDG WARNING: Non-uniform processors. WARNING: Using suboptimal topology. ioapic0: Changing APIC ID to 8 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: COMPAQ CPQ0050 on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 5ff0 (3) failed Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0xf808-0xf80b on acpi0 cpu0: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82845G host to AGP bridge on hostb0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 vgapci0: VGA-compatible display port 0x2000-0x20ff mem 0xf400-0xf7ff,0xfc40-0xfc40 irq 18 at device 0.0 on pci1 vgapci1: VGA-compatible display mem 0xf800-0xfbff,0xfc41-0xfc41 at device 0.1 on pci1 uhci0: Intel 82801DB (ICH4) USB controller USB-A port 0x3440-0x345f irq 16 at device 29.0 on pci0 uhci0: [ITHREAD] usbus0: Intel 82801DB (ICH4) USB controller USB-A on uhci0 uhci1: Intel 82801DB (ICH4) USB controller USB-B port 0x3460-0x347f irq 19 at device 29.1 on pci0 uhci1: [ITHREAD] usbus1: Intel 82801DB (ICH4) USB controller USB-B on uhci1 ehci0: Intel 82801DB/L/M (ICH4) USB 2.0 controller mem 0xfca0-0xfca003ff irq 23 at device 29.7 on pci0 ehci0: [ITHREAD] usbus2: EHCI version 1.0 usbus2: Intel 82801DB/L/M (ICH4) USB 2.0 controller on ehci0 pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0 pci5: ACPI PCI bus on pcib2 fxp0: Intel 82801DB (ICH4) Pro/100 VM Ethernet port 0x1000-0x103f mem 0xfc50-0xfc500fff irq 20 at device 8.0 on pci5 miibus0: MII bus on fxp0 inphy0: i82562EM 10/100 media interface PHY 1 on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:0b:cd:c0:b2:5e fxp0: [ITHREAD] isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH4 UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x34a0-0x34af irq 18 at device 31.1 on pci0 ata0: ATA channel 0 on atapci0 ata0: [ITHREAD] ata1: ATA channel 1 on atapci0 ata1: [ITHREAD] pcm0: Intel ICH4 (82801DB) port 0x3000-0x30ff,0x3400-0x343f mem 0xfca00400-0xfca005ff,0xfca00600-0xfca006ff irq 17 at device 31.5 on pci0 pcm0: [ITHREAD] pcm0: Analog Devices AD1981A AC97 Codec acpi_button0: Power Button on acpi0 attimer0: AT timer port 0x40-0x43 irq 0 on acpi0 Timecounter i8254 frequency 1193182 Hz quality 0 attimer0: [FILTER] Event timer i8254 frequency 1193182 Hz quality 100 atrtc0: AT realtime clock port 0x70-0x71 irq 8 on acpi0 atrtc0: [FILTER] Event timer RTC frequency 32768 Hz quality 0 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] psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model IntelliMouse, device ID 3 ppc0: Parallel port port 0x378-0x37f,0x778-0x77d irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/13 bytes threshold ppc0: [ITHREAD] ppbus0: Parallel port bus on ppc0 plip0: PLIP network interface on ppbus0 plip0: [ITHREAD] lpt0: Printer on ppbus0 lpt0: [ITHREAD] lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 uart0: 16550 or compatible port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: [FILTER] uart1: 16550 or compatible port 0x2f8-0x2ff irq 3 on acpi0 uart1: [FILTER] fdc0: floppy drive controller port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FILTER] fd0: 1440-KB 3.5 drive on fdc0 drive 0 pmtimer0 on isa0 orm0: ISA Option ROMs at iomem 0xc-0xcbfff,0xcc000-0xcd7ff pnpid ORM on isa0 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 p4tcc0: CPU Frequency Thermal Control on cpu0 Timecounter TSC frequency
Re: WARNING: Non-uniform processors.
08.07.2010 22:13, Super Biscuit ?: --- On *Thu, 7/8/10, Alex Keda /ad...@lissyara.su/* wrote: From: Alex Keda ad...@lissyara.su Subject: WARNING: Non-uniform processors. To: freebsd-current@freebsd.org Date: Thursday, July 8, 2010, 4:42 PM When booting, I have strange message. All work OK (processor with hyperthreading, but system seems it as 1 CPU ). Compatible mode usually gives slower response. Unless you need it, don't run it. I have a P4 2.8GHz. Same thing happens. you about it: WARNING: Non-uniform processors. WARNING: Using suboptimal topology. ? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: SUJ problem
On 22.06.2010 03:26, Alexander Best wrote: i experienced the same problem running r209391. this might have to do something with a fs being full. i saw these warnings during buildworld when eventuall / ran out of space: Jun 21 21:32:55 otaku kernel: pid 1398 (sakura), uid 1001 inumber 2661904 on /: filesystem full I have 160Gb disk used as one pat for / Only 16% space used... Jun 21 21:32:59 otaku kernel: pid 1398 (sakura), uid 1001 inumber 2661904 on /: filesystem full Jun 21 21:33:00 otaku kernel: pid 76033 (dd), uid 2 inumber 2591139 on /: filesystem full Jun 21 21:33:02 otaku kernel: pid 1398 (sakura), uid 1001 inumber 2661904 on /: filesystem full Jun 21 21:33:07 otaku kernel: pid 75215 (chrome), uid 1001 inumber 18205737 on /: filesystem full Jun 21 21:33:08 otaku kernel: pid 1467 (script), uid 1001 inumber 14226185 on /: filesystem full Jun 21 21:33:08 otaku kernel: pid 1398 (sakura), uid 1001 inumber 2661904 on /: filesystem full Jun 21 21:33:11 otaku kernel: pid 1398 (sakura), uid 1001 inumber 2661904 on /: filesystem full Jun 21 21:33:18 otaku kernel: pid 75215 (chrome), uid 1001 inumber 18205702 on /: filesystem full Jun 21 21:33:28 otaku kernel: pid 1398 (sakura), uid 1001 inumber 2661461 on /: filesystem full Jun 21 21:33:39 otaku kernel: pid 1398 (sakura), uid 1001 inumber 2661461 on /: filesystem full Jun 21 21:33:47 otaku kernel: pid 1398 (sakura), uid 1001 inumber 2661904 on /: filesystem full Jun 21 21:33:48 otaku kernel: pid 75215 (chrome), uid 1001 inumber 16086093 on /: filesystem full Jun 21 21:33:50 otaku kernel: pid 1398 (sakura), uid 1001 inumber 2661461 on /: filesystem full followed by lots of Jun 21 21:35:25 otaku kernel: bad block 7020785329444114652, ino 7468267 Jun 21 21:35:25 otaku kernel: pid 16 (softdepflush), uid 0 inumber 7468267 on /: bad block Jun 21 21:35:25 otaku kernel: bad block -315669439672768816, ino 7468267 Jun 21 21:35:25 otaku kernel: pid 16 (softdepflush), uid 0 inumber 7468267 on /: bad block Jun 21 21:35:25 otaku kernel: bad block -3220207053503867546, ino 7468267 Jun 21 21:35:25 otaku kernel: pid 16 (softdepflush), uid 0 inumber 7468267 on /: bad block Jun 21 21:35:25 otaku kernel: bad block -6419917778393221405, ino 7468267 Jun 21 21:35:25 otaku kernel: pid 16 (softdepflush), uid 0 inumber 7468267 on /: bad block Jun 21 21:35:25 otaku kernel: bad block 3919397040058727880, ino 7468267 Jun 21 21:35:25 otaku kernel: pid 16 (softdepflush), uid 0 inumber 7468267 on /: bad block Jun 21 21:35:25 otaku kernel: bad block -6888424595660707789, ino 7468267 Jun 21 21:35:25 otaku kernel: pid 16 (softdepflush), uid 0 inumber 7468267 on /: bad block Jun 21 21:35:25 otaku kernel: g_vfs_done():ufs/rootfs[READ(offset=100240429127958528, length=16384)]error = 5 Jun 21 21:35:25 otaku kernel: bad block -1173790944229704887, ino 7468267 Jun 21 21:35:25 otaku kernel: pid 16 (softdepflush), uid 0 inumber 7468267 on /: bad block Jun 21 21:35:25 otaku kernel: bad block 5537349803492323867, ino 7468267 Jun 21 21:35:25 otaku kernel: pid 16 (softdepflush), uid 0 inumber 7468267 on /: bad block Jun 21 21:35:25 otaku kernel: bad block 882554538064816358, ino 7468267 Jun 21 21:35:25 otaku kernel: pid 16 (softdepflush), uid 0 inumber 7468267 on /: bad block Jun 21 21:35:25 otaku kernel: bad block -2565060229441336925, ino 7468267 ~ 2 minutes later (see timestamp). i then did a `find / -inum 7468267` but couldn't find the file. i then did a clean reboot using `shutdown -r now`. the buffers got synched down to 0 however it said something like / cannot be unmounted filesystem busy. i then was thrown into single user mode due to the same problem alex kada reported. at some point i did a `mount -f /` and did `dmesg -a /FEHLER`. strange thing is that everything seems to have been piped to that file twice. after that i did `fastboot` and freebsd came up with / being clean (although the last fsck report said / was marked dirty). i've attached the file. cheers. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
SUJ problem
after unexpected reboot I have problem Mounting root filesystem rw failed, startup aborted ERROR: ABORTING BOOT (sending SIGTERM to parent)! Jun 17 12:35:49 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode Enter full pathname of shell or RETURN for /bin/sh : # f s c k - y ** /dev/label/rootFS USE JOURNAL?? yes ** SU+J Recovering /dev/label/rootFS ** Reading 33554432 byte journal from inode 10. RECOVER? yes ** Building recovery table. ** Resolving unreferenced inode list. ** Processing journal entries. fsck: /dev/label/rootFS: Abort trap: 6 # fsck -y ** /dev/label/rootFS USE JOURNAL?? yes ** SU+J Recovering /dev/label/rootFS ** Reading 33554432 byte journal from inode 10. RECOVER? yes ** Building recovery table. ** Resolving unreferenced inode list. ** Processing journal entries. fsck: /dev/label/rootFS: Abort trap: 6 # fsck -y \^H\^[[K \^H\^[[K / ** /dev/label/rootFS USE JOURNAL?? [yn] ** Skipping journal, falling through to full fsck ** Last Mounted on / ** Root file system ** Phase 1 - Check Blocks and Sizes 73183545484378114 BAD I=29393063 UNEXPECTED SOFT UPDATE INCONSISTENCY 8589934638 BAD I=29393063 UNEXPECTED SOFT UPDATE INCONSISTENCY 50775137189900 BAD I=29393063 UNEXPECTED SOFT UPDATE INCONSISTENCY 361413938815959043 BAD I=29393063 UNEXPECTED SOFT UPDATE INCONSISTENCY 482670965550 BAD I=29393063 UNEXPECTED SOFT UPDATE INCONSISTENCY 289356344794376192 BAD I=29393063 UNEXPECTED SOFT UPDATE INCONSISTENCY -1097558167694 BAD I=29393063 UNEXPECTED SOFT UPDATE INCONSISTENCY 289356344784931840 BAD I=29393063 UNEXPECTED SOFT UPDATE INCONSISTENCY -1097843379600 BAD I=29393063 UNEXPECTED SOFT UPDATE INCONSISTENCY 361413938827687936 BAD I=29393063 UNEXPECTED SOFT UPDATE INCONSISTENCY -281004955507613 BAD I=29393063 UNEXPECTED SOFT UPDATE INCONSISTENCY EXCESSIVE BAD BLKS I=29393063 CONTINUE? [yn] INCORRECT BLOCK COUNT I=29393063 (2153728 should be 263040) CORRECT? [yn] ** Phase 2 - Check Pathnames DUP/BAD I=29393063 OWNER=lissyara MODE=100644 SIZE=1102141440 MTIME=May 12 16:31 2010 FILE=/tmp/src.tar UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? [yn] ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts UNREF FILE I=3085332 OWNER=root MODE=100555 SIZE=362096 MTIME=Jun 15 09:23 2010 CLEAR? [yn] UNREF FILE I=3085355 OWNER=root MODE=100555 SIZE=137472 MTIME=Jun 15 09:23 2010 CLEAR? [yn] UNREF FILE I=4922372 OWNER=root MODE=100555 SIZE=9168 MTIME=Jun 15 09:24 2010 CLEAR? [yn] UNREF FILE I=4922398 OWNER=root MODE=100555 SIZE=438280 MTIME=Jun 15 09:24 2010 CLEAR? [yn] UNREF FILE I=4922403 OWNER=root MODE=100555 SIZE=89184 MTIME=Jun 15 09:24 2010 CLEAR? [yn] UNREF FILE I=7561814 OWNER=root MODE=140666 SIZE=0 MTIME=Jun 15 14:45 2010 CLEAR? [yn] UNREF FILE I=13566043 OWNER=root MODE=100644 SIZE=69 MTIME=Jun 15 15:06 2010 CLEAR? [yn] UNREF FILE I=22138926 OWNER=root MODE=100444 SIZE=38016 MTIME=Jun 15 09:23 2010 CLEAR? [yn] UNREF FILE I=22139000 OWNER=root MODE=100444 SIZE=20472 MTIME=Jun 15 09:23 2010 CLEAR? [yn] UNREF FILE I=22139005 OWNER=root MODE=100444 SIZE=21088 MTIME=Jun 15 09:23 2010 CLEAR? [yn] UNREF FILE I=22139052 OWNER=root MODE=100444 SIZE=40600 MTIME=Jun 15 09:23 2010 CLEAR? [yn] UNREF FILE I=22139096 OWNER=root MODE=100444 SIZE=38872 MTIME=Jun 15 09:23 2010 CLEAR? [yn] UNREF FILE I=22139109 OWNER=root MODE=100444 SIZE=5800 MTIME=Jun 15 09:23 2010 CLEAR? [yn] UNREF FILE I=22139118 OWNER=root MODE=100444 SIZE=8160 MTIME=Jun 15 09:23 2010 CLEAR? [yn] UNREF FILE I=22139120 OWNER=root MODE=100444 SIZE=9736 MTIME=Jun 15 09:23 2010 CLEAR? [yn] UNREF FILE I=22139122 OWNER=root MODE=100444 SIZE=6872 MTIME=Jun 15 09:23 2010 CLEAR? [yn] UNREF FILE I=22139124 OWNER=root MODE=100444 SIZE=7080 MTIME=Jun 15 09:23 2010 CLEAR? [yn] UNREF FILE I=22139127 OWNER=root MODE=100444 SIZE=6840 MTIME=Jun 15 09:23 2010 CLEAR? [yn] UNREF FILE I=22139131 OWNER=root MODE=100444 SIZE=5320 MTIME=Jun 15 09:23 2010 CLEAR? [yn] UNREF FILE I=22139139 OWNER=root MODE=100444 SIZE=5352 MTIME=Jun 15 09:23 2010 CLEAR? [yn] UNREF FILE I=22139142 OWNER=root MODE=100444 SIZE=5888 MTIME=Jun 15 09:23 2010 CLEAR? [yn] UNREF FILE I=22139144 OWNER=root MODE=100444 SIZE=5624 MTIME=Jun 15 09:23 2010 CLEAR? [yn] UNREF FILE I=22139151 OWNER=root MODE=100444 SIZE=13752 MTIME=Jun 15 09:23 2010 CLEAR? [yn] UNREF FILE I=22139155 OWNER=root MODE=100444 SIZE=35840 MTIME=Jun 15 09:23 2010 CLEAR? [yn] UNREF FILE I=22139174 OWNER=root MODE=100444 SIZE=4 MTIME=Jun 15 09:23 2010 CLEAR? [yn] UNREF FILE I=22139214 OWNER=root MODE=100444 SIZE=63128 MTIME=Jun 15 09:23 2010 CLEAR? [yn] UNREF FILE I=22139223 OWNER=root MODE=100444 SIZE=35712 MTIME=Jun 15 09:23 2010 CLEAR? [yn] UNREF FILE I=22139256 OWNER=root MODE=100444 SIZE=293128 MTIME=Jun 15 09:24 2010 CLEAR? [yn] UNREF FILE I=22139328 OWNER=root MODE=100555 SIZE=151784 MTIME=Jun 15 09:24 2010 CLEAR? [yn] UNREF FILE I=22139335 OWNER=root MODE=100444 SIZE=108320 MTIME=Jun 15 09:23
Re: SC_PIXEL_MODE in GENERIC on i386/amd64?
08.05.2010 20:31, Anonymous пишет: - jfbterm - boot splash - apps that use libvgl (e.g. mplayer) - other uses for graphic modes Is there a way to avoid recompiling kernel just to use them? may be need include SC_PIXEL_MODE into GENERIC for amd64 and i386? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: xorg hangs after last commits
27.04.2010 18:13, Robert Noland пишет: Alex Keda wrote: 27.04.2010 17:55, Robert Noland пишет: Alex Keda wrote: Following recent changes in dri, xorg server freezes after 20-30 seconds of work. mouse works, but the image does not change. process xorg get 100% cpu if I delete/rename drm.ko - all OK (but, very slow) vgap...@pci0:1:5:0: class=0x03 card=0x12ff103c chip=0x791e1002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'ATI RADEON X1200 Series (RS690)' class = display subclass = VGA bar [10] = type Prefetchable Memory, range 64, base 0xd000, size 134217728, enabled bar [18] = type Memory, range 64, base 0xd850, size 65536, enabled bar [20] = type I/O Port, range 32, base 0x1100, size 256, enabled bar [24] = type Memory, range 32, base 0xd840, size 1048576, enabled cap 01[50] = powerspec 2 supports D0 D1 D2 D3 current D0 cap 05[80] = MSI supports 1 message, 64 bit Ok, does this patch help? yes. I work without freeze more than 3 minutes =)) How about this one? I reverse previous and apply it patch working time more than without it (without ~1 minutes, with last patch ~2-3 minutes), but - one final - Xorg get 100% CPU and freeze ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
xorg hangs after last commits
Following recent changes in dri, xorg server freezes after 20-30 seconds of work. mouse works, but the image does not change. process xorg get 100% cpu if I delete/rename drm.ko - all OK (but, very slow) vgap...@pci0:1:5:0: class=0x03 card=0x12ff103c chip=0x791e1002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'ATI RADEON X1200 Series (RS690)' class = display subclass = VGA bar [10] = type Prefetchable Memory, range 64, base 0xd000, size 134217728, enabled bar [18] = type Memory, range 64, base 0xd850, size 65536, enabled bar [20] = type I/O Port, range 32, base 0x1100, size 256, enabled bar [24] = type Memory, range 32, base 0xd840, size 1048576, enabled cap 01[50] = powerspec 2 supports D0 D1 D2 D3 current D0 cap 05[80] = MSI supports 1 message, 64 bit ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Something wrong with TCP connections in recent -current
27.04.2010 16:35, Andrey Chernov пишет: See subj. They appears to work for ~10 minutes then all hangs deadly. No one TCP service responds, but ICMP and UDP goes normally. The machine is x86 Pentium 4 IPv4-only, IPv6 is turned off in every place. Last kernel I have that works nice compiled at Mar 19. Ethernet info: fxp0:Intel 82559 Pro/100 Ethernet port 0xc000-0xc03f mem 0xed10-0xed100fff,0xed00-0xed0f irq 11 at device 11.0 on pci1 miibus0:MII bus on fxp0 inphy0:i82555 10/100 media interface PHY 1 on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto This is remote machine, so I don't have console access. I too have it bug but, time 2-3 hours. lissyara$ ifconfig bge0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric 0 mtu 1500 options=c0098VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,VLAN_HWTSO,LINKSTATE ether 00:1c:c4:98:77:a8 inet 172.17.4.127 netmask 0xff00 broadcast 172.17.4.255 media: Ethernet autoselect (100baseTX full-duplex) status: active lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=3RXCSUM,TXCSUM inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL tap0: flags=8902BROADCAST,PROMISC,SIMPLEX,MULTICAST metric 0 mtu 1500 options=8LINKSTATE ether 00:bd:3c:81:00:00 bridge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 42:16:df:e5:3c:68 id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: tap0 flags=143LEARNING,DISCOVER,AUTOEDGE,AUTOPTP ifmaxaddr 0 port 3 priority 128 path cost 200 member: bge0 flags=143LEARNING,DISCOVER,AUTOEDGE,AUTOPTP ifmaxaddr 0 port 1 priority 128 path cost 55 gif0: flags=8051UP,POINTOPOINT,RUNNING,MULTICAST metric 0 mtu 1280 tunnel inet 172.17.4.127 -- 172.29.200.25 inet 10.10.20.26 -- 10.10.10.16 netmask 0x options=1ACCEPT_REV_ETHIP_VER lissyara$ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Something wrong with TCP connections in recent -current
27.04.2010 16:54, Alex Keda пишет: 27.04.2010 16:35, Andrey Chernov пишет: See subj. They appears to work for ~10 minutes then all hangs deadly. No one TCP service responds, but ICMP and UDP goes normally. The machine is x86 Pentium 4 IPv4-only, IPv6 is turned off in every place. Last kernel I have that works nice compiled at Mar 19. Ethernet info: fxp0:Intel 82559 Pro/100 Ethernet port 0xc000-0xc03f mem 0xed10-0xed100fff,0xed00-0xed0f irq 11 at device 11.0 on pci1 miibus0:MII bus on fxp0 inphy0:i82555 10/100 media interface PHY 1 on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto This is remote machine, so I don't have console access. I too have it bug but, time 2-3 hours. lissyara$ ifconfig bge0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric 0 mtu 1500 options=c0098VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,VLAN_HWTSO,LINKSTATE ether 00:1c:c4:98:77:a8 inet 172.17.4.127 netmask 0xff00 broadcast 172.17.4.255 media: Ethernet autoselect (100baseTX full-duplex) status: active lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=3RXCSUM,TXCSUM inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL tap0: flags=8902BROADCAST,PROMISC,SIMPLEX,MULTICAST metric 0 mtu 1500 options=8LINKSTATE ether 00:bd:3c:81:00:00 bridge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 42:16:df:e5:3c:68 id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: tap0 flags=143LEARNING,DISCOVER,AUTOEDGE,AUTOPTP ifmaxaddr 0 port 3 priority 128 path cost 200 member: bge0 flags=143LEARNING,DISCOVER,AUTOEDGE,AUTOPTP ifmaxaddr 0 port 1 priority 128 path cost 55 gif0: flags=8051UP,POINTOPOINT,RUNNING,MULTICAST metric 0 mtu 1280 tunnel inet 172.17.4.127 -- 172.29.200.25 inet 10.10.20.26 -- 10.10.10.16 netmask 0x options=1ACCEPT_REV_ETHIP_VER lissyara$ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org forget. if I attempt local login to machine, I can type root, Enter - and finish - cursor get to line down and nothing. (root without password) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: xorg hangs after last commits
27.04.2010 17:55, Robert Noland пишет: Alex Keda wrote: Following recent changes in dri, xorg server freezes after 20-30 seconds of work. mouse works, but the image does not change. process xorg get 100% cpu if I delete/rename drm.ko - all OK (but, very slow) vgap...@pci0:1:5:0: class=0x03 card=0x12ff103c chip=0x791e1002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'ATI RADEON X1200 Series (RS690)' class = display subclass = VGA bar [10] = type Prefetchable Memory, range 64, base 0xd000, size 134217728, enabled bar [18] = type Memory, range 64, base 0xd850, size 65536, enabled bar [20] = type I/O Port, range 32, base 0x1100, size 256, enabled bar [24] = type Memory, range 32, base 0xd840, size 1048576, enabled cap 01[50] = powerspec 2 supports D0 D1 D2 D3 current D0 cap 05[80] = MSI supports 1 message, 64 bit Ok, does this patch help? yes. I work without freeze more than 3 minutes =)) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: xorg hangs after last commits
27.04.2010 18:13, Robert Noland пишет: Alex Keda wrote: 27.04.2010 17:55, Robert Noland пишет: Alex Keda wrote: Following recent changes in dri, xorg server freezes after 20-30 seconds of work. mouse works, but the image does not change. process xorg get 100% cpu if I delete/rename drm.ko - all OK (but, very slow) vgap...@pci0:1:5:0: class=0x03 card=0x12ff103c chip=0x791e1002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'ATI RADEON X1200 Series (RS690)' class = display subclass = VGA bar [10] = type Prefetchable Memory, range 64, base 0xd000, size 134217728, enabled bar [18] = type Memory, range 64, base 0xd850, size 65536, enabled bar [20] = type I/O Port, range 32, base 0x1100, size 256, enabled bar [24] = type Memory, range 32, base 0xd840, size 1048576, enabled cap 01[50] = powerspec 2 supports D0 D1 D2 D3 current D0 cap 05[80] = MSI supports 1 message, 64 bit Ok, does this patch help? yes. I work without freeze more than 3 minutes =)) How about this one? it use with previous patch, or without it? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
HEADS UP: SUJ Going in to head today
try in single user mode: tunefs -j enable / tunefs: Insuffient free space for the journal tunefs: soft updates journaling can not be enabled tunefs -j enable /dev/ad0s2a tunefs: Insuffient free space for the journal tunefs: soft updates journaling can not be enabled tunefs: /dev/ad0s2a: failed to write superblock on / (/dev/ad0s2a) ~40Gb free. dc7700p$ uname -a FreeBSD dc7700p.lissyara.su 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r207156: Sun Apr 25 00:04:24 MSD 2010 lissy...@dc7700p.lissyara.su:/usr/obj/usr/src/sys/GENERIC amd64 dc7700p$ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newsyslog patch implementing file includes
22.04.2010 07:55, Gordon Tetlow пишет: I wanted the ability for a port to have a rotating log policy so I wrote a patch for newsyslog to implement includes of other newsyslog.conf style files. Please find the patch at: http://people.freebsd.org/~gordon/patches/newsyslog.diffhttp://people.freebsd.org/%7Egordon/patches/newsyslog.diff Format for the include line in /etc/newsyslog.conf is: include /etc/defaults/newsyslog.conf Here's a quick overview of the changes: Convert the conf_entry struct from using a home rolled linked list to the queue(3) macros. Add a STAILQ to process include files. Add support forinclude tag to specify include files. Globbing is supported ininclude statements. Properly detect circular include loop dependencies. Please take a look and send me any comments you might have. It's need feature. I test patch - it work for me (CURRENT, amd64) Can I use some as: include /path/to/dir/*.conf ? and can I create recursive include? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFT]: ClangBSD is selfhosting, we need testers now
16.04.2010 20:08, Roman Divacky пишет: Hi, ClangBSD is a branch of FreeBSD that aims at integrating clang (clang.llvm.org) into FreeBSD, replacing GCC as a system compiler. Recently, we've achieved the state when clang can compile all of FreeBSD world on i386/amd64 platforms (including all the C++ apps we have and itself) and a bootable kernel. Thus we feel that the time has come to ask the FreeBSD community for wider testing on i386/amd64 (you sure can help with other platforms too :)). I accidentally install world to / it's not bootable - loader error I'm copy /boot/boot* /boot/loader from 8 - it successfully boot. kernel not build, with error: dc7700p# make buildworld Makefile, line 111: warning: /usr/bin/env -i PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin make __MAKE_CONF=/etc/make.conf -f /dev/null -V MAKEOBJDIRPREFIX dummy returned non-zero status Segmentation fault (core dumped) /usr/src/Makefile, line 111: warning: /usr/bin/env -i PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin make __MAKE_CONF=/etc/make.conf -f /dev/null -V MAKEOBJDIRPREFIX dummy returned non-zero status -- Building an up-to-date make(1) -- /usr/obj/usr/src/make.amd64/usr/src/usr.bin/make created for /usr/src/usr.bin/make Segmentation fault (core dumped) *** Error code 139 Stop in /usr/src. *** Signal 11 Stop in /usr/src. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFT]: ClangBSD is selfhosting, we need testers now
18.04.2010 12:04, Alex Keda пишет: 16.04.2010 20:08, Roman Divacky пишет: Hi, ClangBSD is a branch of FreeBSD that aims at integrating clang (clang.llvm.org) into FreeBSD, replacing GCC as a system compiler. Recently, we've achieved the state when clang can compile all of FreeBSD world on i386/amd64 platforms (including all the C++ apps we have and itself) and a bootable kernel. Thus we feel that the time has come to ask the FreeBSD community for wider testing on i386/amd64 (you sure can help with other platforms too :)). I accidentally install world to / it's not bootable - loader error I'm copy /boot/boot* /boot/loader from 8 - it successfully boot. my system is: FreeBSD dc7700p.lissyara.su 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r206420: Fri Apr 9 20:59:48 MSD 2010 lissy...@dc7700p.lissyara.su:/usr/obj/usr/src/sys/GENERIC amd64 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFT]: ClangBSD is selfhosting, we need testers now
18.04.2010 13:49, Roman Divacky пишет: On Sun, Apr 18, 2010 at 12:04:16PM +0400, Alex Keda wrote: 16.04.2010 20:08, Roman Divacky ?: Hi, ClangBSD is a branch of FreeBSD that aims at integrating clang (clang.llvm.org) into FreeBSD, replacing GCC as a system compiler. Recently, we've achieved the state when clang can compile all of FreeBSD world on i386/amd64 platforms (including all the C++ apps we have and itself) and a bootable kernel. Thus we feel that the time has come to ask the FreeBSD community for wider testing on i386/amd64 (you sure can help with other platforms too :)). I accidentally install world to / it's not bootable - loader error I'm copy /boot/boot* /boot/loader from 8 - it successfully boot. strange.. I have reports that clangbsd world+kernel compild with clang boots in vmware what was the exact problem with your booting? I don't remember and not save old boot* now, I cannot build world or kernel =) kernel not build, with error: dc7700p# make buildworld Makefile, line 111: warning: /usr/bin/env -i PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin make __MAKE_CONF=/etc/make.conf -f /dev/null -V MAKEOBJDIRPREFIX dummy returned non-zero status Segmentation fault (core dumped) /usr/src/Makefile, line 111: warning: /usr/bin/env -i PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin make __MAKE_CONF=/etc/make.conf -f /dev/null -V MAKEOBJDIRPREFIX dummy returned non-zero status -- Building an up-to-date make(1) -- /usr/obj/usr/src/make.amd64/usr/src/usr.bin/make created for /usr/src/usr.bin/make Segmentation fault (core dumped) *** Error code 139 Stop in /usr/src. *** Signal 11 Stop in /usr/src. what exactly is crashing here? dc7700p$ ll /usr/src| grep core -rw---1 root wheel 6,8M 18 апр 12:03 make.core dc7700p$ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFT]: ClangBSD is selfhosting, we need testers now
18.04.2010 13:49, Roman Divacky пишет: On Sun, Apr 18, 2010 at 12:04:16PM +0400, Alex Keda wrote: 16.04.2010 20:08, Roman Divacky ?: Hi, ClangBSD is a branch of FreeBSD that aims at integrating clang (clang.llvm.org) into FreeBSD, replacing GCC as a system compiler. Recently, we've achieved the state when clang can compile all of FreeBSD world on i386/amd64 platforms (including all the C++ apps we have and itself) and a bootable kernel. Thus we feel that the time has come to ask the FreeBSD community for wider testing on i386/amd64 (you sure can help with other platforms too :)). I accidentally install world to / it's not bootable - loader error I'm copy /boot/boot* /boot/loader from 8 - it successfully boot. strange.. I have reports that clangbsd world+kernel compild with clang boots in vmware what was the exact problem with your booting? I build world, build kernel, install kernel, install world - all to / Now, I working with: FreeBSD dc7700p.lissyara.su 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r206791: Sun Apr 18 20:37:09 MSD 2010 lissy...@dc7700p.lissyara.su:/usr/obj/usr/src/sys/GENERIC amd64 all working (without 'make'). Again, I have boot error: BTX loader 1.00 BTX version is 0.00 Error: Client format not supported. if I copy /boot/boot* and /boot/loader from working system (i have only 8.0 amd64) - boot OK ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ipfw bug on i386
12.04.2010 10:07, Hizel Ildar пишет:
В Sun, 11 Apr 2010 11:23:59 +0400
Alex Kedaad...@lissyara.su пишет:
srv5# more /tmp/a.sh
table=24
ipfw table $table flush
for octet3 in `jot - 1 60`
do
for octet4 in `jot - 1 254`
do
echo table $table add 192.168.$octet3.$octet4 /tmp/$$.txt
done
done
ipfw /tmp/$$.txt
rm -f /tmp/$$.txt
effect:
srv5# sh /tmp/a.sh
Abort trap (core dumped)
srv5#
srv5# ll ipfw.core
-rw--- 1 root wheel - 1,9M 11 апр 11:22 ipfw.core
srv5#
Tested on 8,9 i386 - core dump, amd64 - all OK
7 - all OK
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
freebsd-current-unsubscr...@freebsd.org
Hey! I'm fix this bug :D
patch:
foo# diff -ruN main.c~ main.c
--- main.c~ 2010-03-04 19:54:56.0 +0300
+++ main.c 2010-04-12 09:37:21.0 +0400
@@ -553,7 +553,7 @@
}
while (fgets(buf, BUFSIZ, f)) { /* read commands */
- char linename[10];
+ char linename[11];
char *args[2];
lineno++;
so, it limit 100k addresses in table?
with 7-STABLE I have more than 100k IP and all work correct
srv1# ipfw table 25 list | wc -l
104294
srv1# uname -a
FreeBSD srv1.host-food.ru 7.2-STABLE FreeBSD 7.2-STABLE #0: Sun Oct 4
01:38:34 MSD 2009
lissy...@srv.host-food.ru:/home/obj/usr/src/sys/HOST-FOOD i386
srv1#
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
ipfw bug on i386
srv5# more /tmp/a.sh table=24 ipfw table $table flush for octet3 in `jot - 1 60` do for octet4 in `jot - 1 254` do echo table $table add 192.168.$octet3.$octet4 /tmp/$$.txt done done ipfw /tmp/$$.txt rm -f /tmp/$$.txt effect: srv5# sh /tmp/a.sh Abort trap (core dumped) srv5# srv5# ll ipfw.core -rw--- 1 root wheel - 1,9M 11 апр 11:22 ipfw.core srv5# Tested on 8,9 i386 - core dump, amd64 - all OK 7 - all OK ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
load ipfw table addresses from file
hi! is there any plans to implement such opportunities? for large files (we have 60k lines) it's very slow work srv1# sh -E # wc -l /root/scripts/db/table.25.txt 61073 /root/scripts/db/table.25.txt # date for i in `cat /root/scripts/db/table.25.txt`; do ipfw table 25 add $i; done date пятница, 9 апреля 2010 г. 10:42:01 (MSD) пятница, 9 апреля 2010 г. 10:52:43 (MSD) # it took more than 10 minutes on busy server =( ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: load ipfw table addresses from file
09.04.2010 11:14, Hizel Ildar пишет: В Fri, 09 Apr 2010 10:57:31 +0400 Alex Kedaad...@lissyara.su пишет: hi! is there any plans to implement such opportunities? for large files (we have 60k lines) it's very slow work srv1# sh -E # wc -l /root/scripts/db/table.25.txt 61073 /root/scripts/db/table.25.txt # date for i in `cat /root/scripts/db/table.25.txt`; do ipfw table 25 add $i; done date пятница, 9 апреля 2010 г. 10:42:01 (MSD) пятница, 9 апреля 2010 г. 10:52:43 (MSD) # it took more than 10 minutes on busy server =( ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org my variant: s...@serv4 ~wc -l ip2.txt 65536 ip2.txt s...@serv4 ~sudo ipfw table 25 flush s...@serv4 ~sudo time ipfw /home/se/ip2.txt 0.94 real 0.54 user 0.39 sys s...@serv4 ~sudo ipfw table 25 list | wc -l 65536 but file like: table 25 add 192.168.0.36 table 25 add 192.168.0.37 table 25 add 192.168.0.38 thanks, it is faster, but - this is a crutch =) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: A tool for remapping bad sectors in CURRENT?
08.03.2010 13:29, Eugeny N Dzhurinsky пишет: Hello, all! Recently I've started to see the following logs in messages: Mar 8 12:00:24 localhost smartd[795]: Device: /dev/ad4, 2 Currently unreadable (pending) sectors Mar 8 12:00:24 localhost smartd[795]: Device: /dev/ad4, 2 Offline uncorrectable sectors smartctl did really show that something is wrong with my HDD, but still no remaps - just read errors. SMART Self-test log structure revision number 1 Num Test_DescriptionStatus Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offlineCompleted: read failure 60% 1198 222342559 # 2 Extended offlineCompleted: read failure 60% 1187 222342557 # 3 Extended offlineCompleted: read failure 60% 1180 222342559 # 4 Short offline Completed without error 00% 1178 - # 5 Extended offlineAborted by host 90% 1178 - and ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE ... Reallocated_Sector_Ct 0x0033 100 100 036Pre-fail Always - 0 ... Now can I find out which file owns the LBAs 222342557 and 222342559 ? How do I force remapping of these sectors? I assume that I have to write something directly to the sectors? use mhdd ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: propose: all arch move into a separate dir
On 05.03.2010 12:17, Robert Watson wrote: consumers like Isilon, NetApp, Juniper, and many others thus, it is not 'Free', this managed by 'consumers like Isilon, NetApp, Juniper, and many others'? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: propose: all arch move into a separate dir
On 05.03.2010 12:45, Doug Rabson wrote: On 5 Mar 2010, at 09:30, Alex Keda wrote: On 05.03.2010 12:17, Robert Watson wrote: consumers like Isilon, NetApp, Juniper, and many others thus, it is not 'Free', this managed by 'consumers like Isilon, NetApp, Juniper, and many others'? It might be helpful to think of them as 'customers' who are using our 'product' and paying for it by feeding back patches and employing FreeBSD developers. Normal business practice doesn't include intentionally making your customers' lives difficult - if you make a habit of it they tend to go elsewhere. It seems to me, business and freedom - are mutually exclusive things. or you can choose the path of development, or who pays - giver commands to community. no freedom there. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: propose: all arch move into a separate dir
On 05.03.2010 12:59, Doug Rabson wrote: On 5 Mar 2010, at 09:56, Alex Keda wrote: On 05.03.2010 12:45, Doug Rabson wrote: On 5 Mar 2010, at 09:30, Alex Keda wrote: On 05.03.2010 12:17, Robert Watson wrote: consumers like Isilon, NetApp, Juniper, and many others thus, it is not 'Free', this managed by 'consumers like Isilon, NetApp, Juniper, and many others'? It might be helpful to think of them as 'customers' who are using our 'product' and paying for it by feeding back patches and employing FreeBSD developers. Normal business practice doesn't include intentionally making your customers' lives difficult - if you make a habit of it they tend to go elsewhere. It seems to me, business and freedom - are mutually exclusive things. or you can choose the path of development, or who pays - giver commands to community. no freedom there. Someone always pays. If this project didn't have sponsors like Isilon, NetApp, Juniper, Yahoo, and many others it simply would not exist. then can a more correct name of the project or ClosedBSD or ManagedBSD? =) or something abstract? == I love FreeBSD, but then having to follow the guidance of someone even though everyone understands what you can do better - depressing. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: propose: all arch move into a separate dir
On 05.03.2010 13:59, Poul-Henning Kamp wrote: In message4b90e171.2040...@lissyara.su, Alex Keda writes: then can a more correct name of the project or ClosedBSD or ManagedBSD? =) or something abstract? You are free to use any other operating system of your choice, if you are not happy with FreeBSD. Don't let the door hit you on the way out. I'm not going anywhere, not even hope for it =) I'm trying to make FreeBSD a better, more logical. Maybe that's not very successful, but judging by the number of responses, it hurt many, and made to think even more people. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: propose: all arch move into a separate dir
On 05.03.2010 14:16, Doug Rabson wrote: On Fri, 05 Mar 2010 14:10:43 +0300, Alex Kedaad...@lissyara.su wrote: On 05.03.2010 13:59, Poul-Henning Kamp wrote: In message4b90e171.2040...@lissyara.su, Alex Keda writes: then can a more correct name of the project or ClosedBSD or ManagedBSD? =) or something abstract? You are free to use any other operating system of your choice, if you are not happy with FreeBSD. Don't let the door hit you on the way out. I'm not going anywhere, not even hope for it =) I'm trying to make FreeBSD a better, more logical. Maybe that's not very successful, but judging by the number of responses, it hurt many, and made to think even more people. I think you misunderstand. Some of us old-timers have been having this discussion repeatedly for well over ten years. It always ends up the same way - a re-org might make the source tree marginally prettier but the consequences for long-term maintenance and supporting downstream contributors outweigh any possible benefit. Having the same conversation every two years with the same outcome gets annoying. And the fact that this issue was raised with enviable regularity - not make you think that it really needs to be done? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: propose: all arch move into a separate dir
On 05.03.2010 14:16, Doug Rabson wrote: On Fri, 05 Mar 2010 14:10:43 +0300, Alex Kedaad...@lissyara.su wrote: On 05.03.2010 13:59, Poul-Henning Kamp wrote: In message4b90e171.2040...@lissyara.su, Alex Keda writes: then can a more correct name of the project or ClosedBSD or ManagedBSD? =) or something abstract? You are free to use any other operating system of your choice, if you are not happy with FreeBSD. Don't let the door hit you on the way out. I'm not going anywhere, not even hope for it =) I'm trying to make FreeBSD a better, more logical. Maybe that's not very successful, but judging by the number of responses, it hurt many, and made to think even more people. I think you misunderstand. Some of us old-timers have been having this discussion repeatedly for well over ten years. It always ends up the same way - a re-org might make the source tree marginally prettier but the consequences for long-term maintenance and supporting downstream contributors outweigh any possible benefit. Having the same conversation every two years with the same outcome gets annoying. how many architectures supported 10 years ago? Two? It currently supports 11 or 12 - do not even know for sure. So make the transfer was 5 times harder. Let's wait another 10 years, and, coming at last to understand that this must be done, and do it was 20 times harder. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
