Re: ls colour (COLORTERM / CLICOLOR)

[James Wright]

On 20/07/2020 14:26, Kyle Evans wrote:

On Sat, Jul 18, 2020 at 7:51 PM James Wright
 wrote:


 Updated to 12.1-STABLE r363215 a few days ago (previous build was
circa 1st June)
but seem to have lost "ls" colour output with "COLORTERM=yes" set in my env.

Setting "CLICOLOR=yes" seems to enable it again, however the man page
states that
setting either should work?


Hi,

Indeed, sorry for the flip-flopping. The short version of the
situation is that I had flipped ls(1) to --color=auto by default based
on a misunderstanding of defaults elsewhere due to shell aliases that
I hadn't realized were in use. The ls(1) binary is historically and
almost universally configured for non-colored by default where color
support exists, and you should instead use appropriate shell alias for
ls=`ls -G` or `ls --color=auto`.

I can see where the manpage could describe the differences a little
better. CLICOLOR (On FreeBSD) historically meant that we'll enable
color if the terminal supports it, and setting it would have the same
effect as the above shell alias. COLORTERM is less aggressive and
won't imply any specific --color option, you would still --color=auto
to go with it for it to have any effect.

Thanks,

Kyle Evans


Thank you for the clarifying the diferences between CLICOLOR and COLORTERM,
that makes sense to me now. I'll set the shell alias and remove COLORTERM.
Only raised this in case it was an unintended consequence of recent 
changes. :-)



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

ls colour (COLORTERM / CLICOLOR)

[James Wright]

   Updated to 12.1-STABLE r363215 a few days ago (previous build was 
circa 1st June)

but seem to have lost "ls" colour output with "COLORTERM=yes" set in my env.

  Setting "CLICOLOR=yes" seems to enable it again, however the man page 
states that

setting either should work?

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

Re: Random system lockups with 12.1-STABLE r354241 amd64

[James Wright]

  Yesterday evening I fetched the lastest from svn stable (r354662), 
created a custom kernel configuration with the following options, and 
rebuilt everything;


>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
include GENERIC
ident MACBOOK

# For full debugger support use (turn off in stable branch):
options BUF_TRACKING    # Track buffer history
options DDB # Support DDB.
options FULL_BUF_TRACKING   # Track more buffer history
options GDB # Support remote GDB.
options DEADLKRES   # Enable the deadlock resolver
options INVARIANTS  # Enable calls of extra sanity 
checking
options INVARIANT_SUPPORT   # Extra sanity checks of 
internal structures, required by INVARIANTS
options WITNESS # Enable checks to detect 
deadlocks and cycles
options WITNESS_SKIPSPIN    # Don't run witness on spinlocks 
for speed

options MALLOC_DEBUG_MAXZONES=8 # Separate malloc(9) zones
options VERBOSE_SYSINIT=0   # Support debug.verbose_sysinit, 
off by default


<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

  Then this evening, another system hang, no debugger messages or any 
sort of output whatsoever! :-( The only upside is that I'm experiencing 
these hangs almost daily now, so going to try a process of elimination. 
The hangs generally seem to occur when I'm working using Sublime Text 3 
(via the linuxulator), with an open xterm window or two with X11 
(currently using the Intel video driver). So might try switching to 
modesetting video driver, or using an editor that is native, or ditch 
the graphical environment altogether and see if I still get issues 
working on the console.


  If anyone has any ideas on how else I may be able to track down the 
issue, please let me know! :-)



Thanks,
James


On 07/11/2019 21:21, James Wright wrote:


On 06/11/2019 23:42, Julian Elischer wrote:

On 11/6/19 2:58 PM, James Wright wrote:

Hi,

[...]

  Can anyone offer some advice as to how I can track down this issue?
The first question which I couldn't see from your dmesg is "do you 
have ht krnel debugger configured into your kernel?"




  Nope it isn't, I will build it in, is it just adding options KDB and 
DDB?


  Another problem I have is I don't seemt to get any crash dumps even 
though I have 'dumpdev="AUTO"' in my /etc/rc.conf, could this be due 
to my system using a swap file (md) rather than a dedicated swap 
partition?





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

Re: Random system lockups with 12.1-STABLE r354241 amd64

[James Wright]

On 06/11/2019 23:42, Julian Elischer wrote:

On 11/6/19 2:58 PM, James Wright wrote:

Hi,

[...]

  Can anyone offer some advice as to how I can track down this issue?
The first question which I couldn't see from your dmesg is "do you 
have ht krnel debugger configured into your kernel?"




  Nope it isn't, I will build it in, is it just adding options KDB and DDB?

  Another problem I have is I don't seemt to get any crash dumps even 
though I have 'dumpdev="AUTO"' in my /etc/rc.conf, could this be due to 
my system using a swap file (md) rather than a dedicated swap partition?



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

Random system lockups with 12.1-STABLE r354241 amd64

[James Wright]

Hi,

   Since upating to r354241 a few days ago I've been experiencing more 
frequent complete system lockups, with around 4 happening over the last 
couple of days. Prior to this I would get the occasional lockup, perhaps 
once a month on my laptop which is used daily.


  I'm finding it hard to determine the issue as it seems completely 
random, and the only course of action left open once it occurs is to 
hard power down the machine, which *always* seems to lead to filesystem 
inconsistencies upon restarting, (the file system is UFS with SU+J).


  Can anyone offer some advice as to how I can track down this issue?

# uname -a
FreeBSD macbook 12.1-STABLE FreeBSD 12.1-STABLE r354241 GENERIC amd64


# dmesg
---<>---
Copyright (c) 1992-2019 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 12.1-STABLE r354241 GENERIC amd64
FreeBSD clang version 8.0.1 (tags/RELEASE_801/final 366581) (based on 
LLVM 8.0.1)

VT(efifb): resolution 1440x900
CPU: Intel(R) Core(TM) i7-5650U CPU @ 2.20GHz (2200.05-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x306d4  Family=0x6  Model=0x3d Stepping=4
Features=0xbfebfbff
Features2=0x7ffafbff
  AMD Features=0x2c100800
  AMD Features2=0x121
  Structured Extended 
Features=0x21c2fbb

  Structured Extended Features3=0x9c000400
  XSAVE Features=0x1
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
  TSC: P-state invariant, performance statistics
real memory  = 8589934592 (8192 MB)
avail memory = 8154464256 (7776 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: 
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 hardware threads
random: unblocking device.
ioapic0  irqs 0-39 on motherboard
Launching APs: 1 2 3
Timecounter "TSC-low" frequency 1100025386 Hz quality 1000
random: entropy device external interface
kbd0 at kbdmux0
000.23 [4336] netmap_init   netmap: loaded module
[ath_hal] loaded
module_register_init: MOD_LOAD (vesa, 0x81131fa0, 0) error 19
random: registering fast source Intel Secure Key RNG
random: fast provider: "Intel Secure Key RNG"
nexus0
efirtc0:  on motherboard
efirtc0: registered as a time-of-day clock, resolution 1.00s
cryptosoft0:  on motherboard
acpi0:  on motherboard
acpi_ec0:  port 0x62,0x66 on acpi0
acpi0: Power Button (fixed)
hpet0:  iomem 0xfed0-0xfed03fff irq 0,8 
on acpi0

Timecounter "HPET" frequency 14318180 Hz quality 950
Event timer "HPET" frequency 14318180 Hz quality 550
Event timer "HPET1" frequency 14318180 Hz quality 440
Event timer "HPET2" frequency 14318180 Hz quality 440
Event timer "HPET3" frequency 14318180 Hz quality 440
Event timer "HPET4" frequency 14318180 Hz quality 440
cpu0:  on acpi0
atrtc0:  port 0x70-0x77 on acpi0
atrtc0: registered as a time-of-day clock, resolution 1.00s
Event timer "RTC" frequency 32768 Hz quality 0
attimer0:  port 0x40-0x43,0x50-0x53 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1808-0x180b on acpi0
pcib0:  port 0xcf8-0xcff on acpi0
pci0:  on pcib0
vgapci0:  port 0x3000-0x303f mem 
0xc000-0xc0ff,0xb000-0xbfff at device 2.0 on pci0

vgapci0: Boot video device
hdac0:  mem 0xc161-0xc1613fff at 
device 3.0 on pci0
xhci0:  mem 
0xc160-0xc160 at device 20.0 on pci0

xhci0: 32 bytes context size, 64-bit DMA
xhci0: Port routing mask set to 0x
usbus0 on xhci0
usbus0: 5.0Gbps Super Speed USB v3.0
pci0:  at device 22.0 (no driver attached)
hdac1:  mem 0xc1614000-0xc1617fff at 
device 27.0 on pci0

pcib1:  at device 28.0 on pci0
pci1:  on pcib1
pcib2:  at device 28.1 on pci0
pci2:  on pcib2
pci2:  at device 0.0 (no driver attached)
pcib3:  at device 28.2 on pci0
pci3:  on pcib3
pci3:  at device 0.0 (no driver attached)
pcib4:  at device 28.4 on pci0
pci4:  on pcib4
pcib5:  at device 28.5 on pci0
pci5:  on pcib5
ahci0:  mem 0xc130-0xc1301fff at device 0.0 on 
pci5

ahci0: AHCI v1.30 with 1 6Gbps ports, Port Multiplier not supported
ahcich0:  at channel 0 on ahci0
isab0:  at device 31.0 on pci0
isa0:  on isab0
battery0:  on acpi0
acpi_acad0:  on acpi0
acpi_lid0:  on acpi0
acpi_button0:  on acpi0
acpi_button1:  on acpi0
asmc0:  port 0x300-0x31f 
iomem 0xfef0-0xfef0 irq 6 on acpi0

uart0: <8250 or 16450 or compatible> at port 0x3f8 irq 4 flags 0x10 on isa0
uart0: non-PNP ISA device will be removed from GENERIC in FreeBSD 12.
coretemp0:  on cpu0
est0:  on cpu0
Timecounters tick every 1.000 msec
hdacc0:  at cad 0 on hdac0
hdaa0:  at nid 1 on hdacc0
pcm0:  at nid 3 on hdaa0
hdacc1:  at cad 0 on hdac1
hdaa1:  at nid 1 on hdacc1
pcm1:  at nid 18,16 and 24 on 
hdaa1

ugen0.1: <0x8086 XHCI root HUB> at usbus0
uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 

Companies using Microsoft Azure and Amazon AWS Install Base

[danielle . james]

Hi,

I was wondering if you would be interested in the updated contact
information from the below mentioned applications users and *MSP’s, MSSP’s,
ISV’s, SI’s* and *CSP’s *for your Channel Marketing Strategy.

*Significant users list includes:*

*Technology*

*Category*

*Amazon Web Services*

*PaaS Clouds*

*Microsoft Azure*

*Cloud Software Defined Storage*

*Google Cloud Platform*

*Cloud Storage Gateways*

*Adobe*

*Cloud Management*

*VMware*

*Cloud Access Security Brokers*

*IBM Cloud*

*Converged Infrastructure*

*Rackspace*

*Infrastructure as a Service Clouds (IaaS)*

*Red Hat*

*Contact Center as a Service (CCaaS)*

*Salesforce*

*Cloud ERP*

*Oracle Cloud*

*Cloud Storage*

*SAP*

*Cloud Backup*

*Verizon Cloud*

*Cloud HCM*

*Navisite*

*Cloud Analytics*

*Dropbox*

*Cloud Security Services*

*Egnyte*

*Cloud Workload Security*

*Workday*

*Cloud Data Integration*

*Citrix*

*Cloud Monitoring Software*

*Huawei*

*Identity and Access Management as a Service (IDaaS)*

*Dell EMC *

*Cloud and Data Center Security*

*Cisco*

*Hosted and Cloud Based VoIP*

Our *terms of business* are simple.

· Customized lists as per your requirements

· Upfront guarantees and refund policies (in case of
dissatisfaction)

· Timely and seamless delivery

· Continued customer support

Thanks,

*Danielle James| **Software Intelligence Data Specialist*

*Data Coverage- Global (North America, EMEA, APAC & LATAM)*



*If you wish to not to receive further emails, change the subject line to
Unsubscribe*
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Random panics in 11.0 and 12.0 on J1900

[James Snow]

Hi Marco and Adam,

Thanks for the responses. Answers to your questions are inline

On Sat, Jul 20, 2019 at 06:56:19PM +0200, Marco Steinbach wrote:

> I've outfitted all of them with 4-port Intel PRO/1000 PCIe driven by
> igb(4), and am not using the onboard re(4) NICs.

We use the onboard re(4) NICs and they have been their own problem. It's
possible they are implicated here.

> I can't recall ever seeing a panic like you described. Could you share
> a full dmesg and what mainboard(s) you are using ?

/var/run/dmesg.boot from the 12.0 host that panicked is included below.
The board is a "Q1900G2-M V2.0".


On Wed, Jul 24, 2019 at 07:53:54PM -0500, Adam wrote:

> What is the size of this J1900 set?

Large enough that 1% panicking daily means I'm seeing multiple panics
per day.

> Do you also have J1900 which do not exhibit the problem?

I do have a small set which have not exhibited the problem. They are
about 2.5-3% of the fleet. What makes them unique is they are running 10.3.

There are also some 11.0s which have not panicked, but given that we've
seen hosts go ~620 days before a panic, it's possible they just haven't
panicked yet; they are also a minority of the 11s. (It's also possible
the 10.3s just haven't panicked yet, but as they have been deployed the
longest, that seems less probable with each passing day.)

Personally, I believe this is a hardware problem, but these 10.3s that
don't panic are a big hole in that theory.

> memtest cannot conclusively confirm dimm is good, it is only conclusive on
> bad ones.  You can find more info about others learning this lesson
> here(see extended comments):
> 
> https://superuser.com/questions/547822/how-many-passes-are-enough-with-memtest
> 
> 
> > Two, a small number of systems on the same hardware are running
> > 10.3-RELEASE, and have experienced no panics in their history. Panics
> > have only happened on 11s, and now 12.
> >
> 
> Once upon a time in a hypothetical universe, I had a stick of ram which
> would run on Win98 for very long periods without issue.  It wouldn't even
> boot with Win NT.  After the manufacturer sent the same one back twice, I
> tased it and RMA'd again.  This time, I got a new stick and all was good.
> 
> The point is memory issues can be very subtle and replacing with known good
> modules is the easiest way to be sure.

Duly noted, and I don't disagree, but given your comments about memtest
and confirming memory to be good, how do you get to "known good?"

Thanks for the input. dmesg output follows below.


-Snow


---<>---
Copyright (c) 1992-2018 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 12.0-RELEASE r341666 GENERIC amd64
FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM 
6.0.1)
CPU: Intel(R) Celeron(R) CPU  J1900  @ 1.99GHz (2000.06-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x30678  Family=0x6  Model=0x37  Stepping=8
  
Features=0xbfebfbff
  
Features2=0x41d8e3bf
  AMD Features=0x28100800
  AMD Features2=0x101
  Structured Extended Features=0x2282
  Structured Extended Features3=0xc00
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
  TSC: P-state invariant, performance statistics
real memory  = 8589934592 (8192 MB)
avail memory = 8089657344 (7714 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: 
WARNING: L1 data cache covers fewer APIC IDs than a core (0 < 1)
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 4 core(s)
random: unblocking device.
Firmware Warning (ACPI): 32/64X length mismatch in FADT/Gpe0Block: 128/32 
(20181003/tbfadt-748)
ioapic0  irqs 0-86 on motherboard
Launching APs: 3 2 1
Timecounter "TSC" frequency 256560 Hz quality 1000
random: entropy device external interface
kbd1 at kbdmux0
netmap: loaded module
[ath_hal] loaded
random: registering fast source Intel Secure Key RNG
random: fast provider: "Intel Secure Key RNG"
nexus0
cryptosoft0:  on motherboard
acpi0:  on motherboard
acpi0: Power Button (fixed)
unknown: I/O range not supported
cpu0:  on acpi0
atrtc0:  port 0x70-0x77 on acpi0
atrtc0: Warning: Couldn't map I/O.
atrtc0: registered as a time-of-day clock, resolution 1.00s
Event timer "RTC" frequency 32768 Hz quality 0
hpet0:  iomem 0xfed0-0xfed003ff irq 8 on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 950
Event timer "HPET" frequency 14318180 Hz quality 450
Event timer "HPET1" frequency 14318180 Hz quality 440
Event timer "HPET2" frequency 14318180 Hz quality 440
attimer0:  port 0x40-0x43,0x50-0x53 irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
Timecounter "ACPI-safe" frequency 3579545 Hz quality 850
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
pcib0:  port 0xcf8-0xcff on acpi0
pci0:  on pcib0
vgapci0:  port 0xf080-0xf087 mem 

Random panics in 11.0 and 12.0 on J1900

[James Snow]

I have a set of J1900 hosts running 11.0-RELEASE-p1 that experience
seemingly random panics. The panics are all basically the same:

Fatal trap 12: page fault while in kernel mode
fault code = supervisor read data, page not present

Adding workloads to the hosts seems to increase panic frequency, but the
panics have also occurred on completely idle hosts. Similarly, uptime
when panicking has been as low as minutes, and as high as ~620 days.

For reasons, it has not been possible to extract a coredump from these
hosts, nor practical to run memtest on them or upgrade them to a newer
release. About 1% of our hosts are affected each day, so we've just been
living with the problem.

However, while testing 12.0 on the same hardware, I encountered the same
panic and was able to capture the core dump. (See below.)

All of my Google-fu on this panic has turned up threads suggesting the
problem is hardware, but there are two problems with that idea...

One, memtest has turned up no errors on 12.0 host I witnessed the panic
on.

Two, a small number of systems on the same hardware are running
10.3-RELEASE, and have experienced no panics in their history. Panics
have only happened on 11s, and now 12.

kgdb output from the panic follows. (This particular host was in the
middle of rebooting when it panicked.)

Hoping someone here has some insight. My uninformed wild-ass guess is
something relating to spectre/meltdown fixes.

Thanks,


-Snow



root@j1900_12:~ # kgdb /boot/kernel/kernel /var/crash/vmcore.0
GNU gdb (GDB) 8.3 [GDB v8.3 for FreeBSD]
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-portbld-freebsd12.0".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /boot/kernel/kernel...
Reading symbols from /usr/lib/debug//boot/kernel/kernel.debug...

Unread portion of the kernel message buffer:
<118>.
<118>Terminated
<118>Jul 10 07:03:50 j1900_12 syslogd: last message repeated 9 times
<118>Jul 10 07:04:08 j1900_12 syslogd: exiting on signal 15
Waiting (max 60 seconds) for system process `vnlru' to stop... done
Waiting (max 60 seconds) for system process `syncer' to stop...
Syncing disks, vnodes remaining... 0 0 0 0 done
Waiting (max 60 seconds) for system thread `bufdaemon' to stop... done
Waiting (max 60 seconds) for system thread `bufspacedaemon-0' to stop... done
Waiting (max 60 seconds) for system thread `bufspacedaemon-1' to stop... done
Waiting (max 60 seconds) for system thread `bufspacedaemon-2' to stop... done
Waiting (max 60 seconds) for system thread `bufspacedaemon-3' to stop... done
All buffers synced.
Uptime: 23h22m43s
umass0: detached
ukbd0: detached
uhid0: detached
uhub3: detached
uhub2: detached


Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x3201c450
fault code  = supervisor read data, page not present
instruction pointer = 0x20:0x80b7ad1d
stack pointer   = 0x28:0xfe003f231820
frame pointer   = 0x28:0xfe003f231890
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 1 (init)
trap number = 12
panic: page fault
cpuid = 0
time = 1562742255
KDB: stack backtrace:
#0 0x80be7977 at kdb_backtrace+0x67
#1 0x80b9b563 at vpanic+0x1a3
#2 0x80b9b3b3 at panic+0x43
#3 0x8107496f at trap_fatal+0x35f
#4 0x810749c9 at trap_pfault+0x49
#5 0x81073fee at trap+0x29e
#6 0x8104f1d5 at calltrap+0x8
#7 0x808a6029 at re_shutdown+0x99
#8 0x80bd878a at bus_generic_shutdown+0x5a
#9 0x80bd878a at bus_generic_shutdown+0x5a
#10 0x80bd878a at bus_generic_shutdown+0x5a
#11 0x80bd878a at bus_generic_shutdown+0x5a
#12 0x80bd878a at bus_generic_shutdown+0x5a
#13 0x80452a8d at acpi_shutdown+0xd
#14 0x80bd878a at bus_generic_shutdown+0x5a
#15 0x80bd878a at bus_generic_shutdown+0x5a
#16 0x80bdbb6e at root_bus_module_handler+0x11e
#17 0x80b7a86f at module_shutdown+0x6f
Uptime: 23h22m44s
Dumping 494 out of 7976 MB:..4%..13%..23%..33%..43%..52%..62%..72%..81%..91%

__curthread () at ./machine/pcpu.h:230
230 ./machine/pcpu.h: No such file or directory.
(kgdb) bt
#0  __curthread () at ./machine/pcpu.h:230
#1  doadump (textdump=) at 

Re: boot/pxeboot broken in freebsd-12?

[James Snow]

Thanks Warner...

On Tue, Mar 19, 2019 at 05:14:15PM -0600, Warner Losh wrote:

> You need to set the NFS mount point properly.

I think I have? The 12.0 environment was basically a copy of a
functioning 11.0 PXE environment, and 12 worked fine with 11's pxeboot.

Regardless, turns out neither 12 nor 13 will boot on my hardware under
UEFI, so PXE woes are less of a concern now. I'm running J1900s; they
seem to have a history.


-Snow

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

boot/pxeboot broken in freebsd-12?

[James Snow]

Hello -stable,

We have a PXE environemt that builds FreeBSD-11 boxes. We've started
to dip our toes into the 12.x waters, but have had trouble getting
FreeBSD-12 to pxeboot. It would crash and burn like so:

Startup error in /boot/lua/loader.lua:
LUA ERROR: cannot open /boot/lua/loader.lua: device not configured

On a whim, I pulled the boot/pxeboot binary from our FreeBSD-11
environment into the new FreeBSD-12 environment, and PXE clients started
coming right up.

Is FreeBSD-12's pxeboot broken or have I missed something?


-Snow

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

NDI[VN]: JKT: Blsvn: JV Invite

[James Kitula]

 - This mail is in HTML. Some elements may be ommited in plain text. -

Hello,
This is a follow up of the message we previously sent to you..
We are international project financiers and we specialize in both start up 
projects and existing businesses needing funding or Loan for expansion. We are 
committed to helping businesses develop and succeed.
We will like to partner with you/your company should you be interested or may 
require funding for the expansion of your business. We will be glad to 
receiving your terms and condition before proceeding further.
This is my personal email:

jamkit...@outlook.com
Looking forward to hear from you.
Sincere regards,
James Kitula.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Promise Her Anything But Give Her Brand Watch

[James Hill]

  
  Fund your favorite watch
 
   



If you no longer wish to receive mail from us, you can  Unsubscribe here


View Online







World of Top Brand Watches


New watches arrived, and all new styles we thought youd love! New watches 
with amazing prices. Dont miss it. Get extra 10% off for the first 21 
clients.No shipping cost on order over $50.















  VIEW MORE  




Our Promises:
- Complete safety PayPal payment
- Fast delivery and returns with no minimum limited
- 21 days to return or exchange an item
- Complete safety with 100% secure order processing
- Customer satisfaction is our top priority



© 2018 TFB Brand Store
  802 Street, Suite 802,
tfzdozi, Indonesia

If you are EU citizens you will have full rights to take control of your 
personal data. Here are the most important user rights that fully compliance 
with GDPR

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

Re: jail related inconsistencies in FreeBSD tools parameters

[James Gritton]

On 2018-06-23 12:58, Eitan Adler wrote:

On 23 June 2018 at 08:50, James Gritton  wrote:

On 2018-06-23 09:45, Eitan Adler wrote:


On 23 June 2018 at 08:30, James Gritton  wrote:


On 2018-06-22 16:03, Miroslav Lachman wrote:



Chris H wrote on 2018/06/22 23:46:



On Fri, 22 Jun 2018 23:13:17 +0200 "Miroslav Lachman"
<000.f...@quip.cz>
said

I don't know if it is better to discuss it in jail@ or stable@ 
list so

a
do cross-post.

FreeBSD has many jail aware utilities but they are inconsistent 
in

taking JID as parameter.

For example "sockstat" takes -j JID "Show only sockets belonging 
to

the
specified jail ID" and it means numeric ID only.
On the other hand "ps" takes -J JID "This may be either the jid 
or

name
of the jail.  Use -J 0 to display only host processes."
The same apply for "top", it understands jid as a number or name 
of

the
jail too.
Then again "cpuset" takes only numerical ID of the jail...

Shouldn't it be consistent across all FreeBSD base utilities so 
all of

them can use numerical ID and name?



Good idea! Are you offering to create a patch? ;-)
It'd be my guess that given they weren't all created at the same 
time,

nor
the same individual; that (quite probably?) the "jail" additions 
were

also
added at different times, and by different people. So I'd imagine 
that
unless someone with a commit bit decides one day they'd like to 
take

that
on. Someone(tm) maybe you? will need to propose a patch. :-)




If I can understand C sources I will create the patch by myself
instead of just posting here. Unfortunately I am able to code in 
sh,

php and a bit of javascript and perl but no C. :)

Miroslav Lachman




Sure, a PR would be handy for this - it's a pretty simple thing to 
add,

and
consistency would indeed be a good move.



Agreed. I'll review and commit such patches. I'd like to see a single
function for taking a "id or name". Ideally it would live in a
library, perhaps libjail?



It already lives there: jail_getid(3)


I was thinking of a more generic one that does id or name. Now that I
think about it a bit more, C makes this kind of thing impossible to do
usefully.

That said, I'll still review and commit any patches to existing tools
to make them behave consistently.


Yes, jail_getid(3) works with either a numeric ID or a name.

I've added a patch to 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229266 for the four 
programs I've found that need help.  I've tested the easy ones (cpuset 
and sockstat).


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

Re: jail related inconsistencies in FreeBSD tools parameters

[James Gritton]

On 2018-06-23 09:45, Eitan Adler wrote:

On 23 June 2018 at 08:30, James Gritton  wrote:

On 2018-06-22 16:03, Miroslav Lachman wrote:


Chris H wrote on 2018/06/22 23:46:


On Fri, 22 Jun 2018 23:13:17 +0200 "Miroslav Lachman" 
<000.f...@quip.cz>

said

I don't know if it is better to discuss it in jail@ or stable@ list 
so a

do cross-post.

FreeBSD has many jail aware utilities but they are inconsistent in
taking JID as parameter.

For example "sockstat" takes -j JID "Show only sockets belonging to 
the

specified jail ID" and it means numeric ID only.
On the other hand "ps" takes -J JID "This may be either the jid or 
name

of the jail.  Use -J 0 to display only host processes."
The same apply for "top", it understands jid as a number or name of 
the

jail too.
Then again "cpuset" takes only numerical ID of the jail...

Shouldn't it be consistent across all FreeBSD base utilities so all 
of

them can use numerical ID and name?


Good idea! Are you offering to create a patch? ;-)
It'd be my guess that given they weren't all created at the same 
time,

nor
the same individual; that (quite probably?) the "jail" additions 
were

also
added at different times, and by different people. So I'd imagine 
that
unless someone with a commit bit decides one day they'd like to take 
that

on. Someone(tm) maybe you? will need to propose a patch. :-)



If I can understand C sources I will create the patch by myself
instead of just posting here. Unfortunately I am able to code in sh,
php and a bit of javascript and perl but no C. :)

Miroslav Lachman



Sure, a PR would be handy for this - it's a pretty simple thing to 
add, and

consistency would indeed be a good move.


Agreed. I'll review and commit such patches. I'd like to see a single
function for taking a "id or name". Ideally it would live in a
library, perhaps libjail?


It already lives there: jail_getid(3)

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

Re: jail related inconsistencies in FreeBSD tools parameters

[James Gritton]

On 2018-06-22 16:03, Miroslav Lachman wrote:

Chris H wrote on 2018/06/22 23:46:
On Fri, 22 Jun 2018 23:13:17 +0200 "Miroslav Lachman" 
<000.f...@quip.cz> said


I don't know if it is better to discuss it in jail@ or stable@ list 
so a do cross-post.


FreeBSD has many jail aware utilities but they are inconsistent in 
taking JID as parameter.


For example "sockstat" takes -j JID "Show only sockets belonging to 
the specified jail ID" and it means numeric ID only.
On the other hand "ps" takes -J JID "This may be either the jid or 
name of the jail.  Use -J 0 to display only host processes."
The same apply for "top", it understands jid as a number or name of 
the jail too.

Then again "cpuset" takes only numerical ID of the jail...

Shouldn't it be consistent across all FreeBSD base utilities so all 
of them can use numerical ID and name?

Good idea! Are you offering to create a patch? ;-)
It'd be my guess that given they weren't all created at the same time, 
nor
the same individual; that (quite probably?) the "jail" additions were 
also

added at different times, and by different people. So I'd imagine that
unless someone with a commit bit decides one day they'd like to take 
that

on. Someone(tm) maybe you? will need to propose a patch. :-)


If I can understand C sources I will create the patch by myself
instead of just posting here. Unfortunately I am able to code in sh,
php and a bit of javascript and perl but no C. :)

Miroslav Lachman


Sure, a PR would be handy for this - it's a pretty simple thing to add, 
and consistency would indeed be a good move.


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

Re: when the sshd hits the fan

[James Snow]

On Wed, Sep 23, 2015 at 01:37:30PM +0100, Matt Smith wrote:

> If this type of thing is being done on the base system sshd it would 
> also be useful to look at the port version of ssh as well? I use the 
> port and it has always annoyed me that I get constant "connection 
> refused" whilst I'm waiting for the server to fully boot up!

Tangential, but in case it's useful to anyone else:

  until ssh -o ConnectTimeout=2 $host; do sleep 1; done

I do this all the time for hosts where I'm waiting on boot. The timeouts
and connection refused messages serve as counters so I can do other
things while waiting and have an objective measure of whether or not
I've waited too long for a host to come up. Also handy is that it will
automatically reconnect on anything other than a deliberate log out.


-Snow

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

Re: jail: /etc/rc: cannot create /dev/null: Operation not supported

[James Gritton]

On 2015-07-17 11:26, Per olof Ljungmark wrote:

On 2015-07-17 01:41, James Gritton wrote:

On 2015-07-15 13:52, Per olof Ljungmark wrote:

FreeBSD 10.2-PRERELEASE #0 r284949

The jail can be started, but when /etc/rc is executed:

root@mar:/ # sh -x /etc/rc
+ stty status ^T
/etc/rc: cannot create /dev/null: Operation not supported
+ trap : 2
+ trap 'echo '\''Boot interrupted'\''; exit 1' 3
+ HOME=/
+ PATH=/sbin:/bin:/usr/sbin:/usr/bin
+ export HOME PATH
+ [ '' = autoboot ]
+ autoboot=no
+ _boot=quietstart
+ /sbin/sysctl -n vfs.nfs.diskless_valid
/etc/rc: cannot create /dev/null: Operation not supported
...

I have done the procedure several times before but never saw this one
before and don't know how to get around it.

Ideas anyone? Any recent changes that can show up like the above?

Thanks!


If it's trying to create /dev/null, I assume that the jail's /dev 
isn't

mounted when /etc/rc is running.  Do you have mount.devfs set in the
jail.conf, or jail_foo_devfs_enable in rc.conf (depending on your
configuration)? For that matter, can you tell if the jail's /dev is
mounted?


Yes, it's mounted.

Because I can set up jails with an identical procedure on other boxes 
we

run I suspect something is wrong with the install so I am starting from
scratch with this one.

While doing that, I am trying to sort another problem, namely to boot
zfs on root on a HP Proliant with a P410 controller, but that is 
another

story.

You know, if it was easy it would not be interesting...

Thanks!


So maybe a little late since you're starting over, but another 
possibility

is the devfs ruleset.  If something went wrong in setting that up, you
could well have a devfs mounted that shows no devices.

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

Re: jail: /etc/rc: cannot create /dev/null: Operation not supported

[James Gritton]

On 2015-07-15 13:52, Per olof Ljungmark wrote:

FreeBSD 10.2-PRERELEASE #0 r284949

The jail can be started, but when /etc/rc is executed:

root@mar:/ # sh -x /etc/rc
+ stty status ^T
/etc/rc: cannot create /dev/null: Operation not supported
+ trap : 2
+ trap 'echo '\''Boot interrupted'\''; exit 1' 3
+ HOME=/
+ PATH=/sbin:/bin:/usr/sbin:/usr/bin
+ export HOME PATH
+ [ '' = autoboot ]
+ autoboot=no
+ _boot=quietstart
+ /sbin/sysctl -n vfs.nfs.diskless_valid
/etc/rc: cannot create /dev/null: Operation not supported
...

I have done the procedure several times before but never saw this one
before and don't know how to get around it.

Ideas anyone? Any recent changes that can show up like the above?

Thanks!


If it's trying to create /dev/null, I assume that the jail's /dev isn't
mounted when /etc/rc is running.  Do you have mount.devfs set in the
jail.conf, or jail_foo_devfs_enable in rc.conf (depending on your
configuration)? For that matter, can you tell if the jail's /dev is
mounted?

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

ifconfig VLAN cloning, renaming, configuring in rc.conf.local

[James Long]

[Please CC: me on any replies, as I check my inbox more frequently
than I check this list.]

I have three servers running 9.3-STABLE which are designed to be
able to exchange jails so that a virtual host can be readily moved
to a different physical host.  Because physical NIC names could
differ, the ezjail config files are set up to use an interface name
of 'public' or 'private' depending on which of the two physical NICs
each jail wants to use, and the rc.conf system is responsible to
configure the physical NICs with the correct 'public' and 'private' 
NICknames (pardon the expression).

The hitch is that one of the three machines is on a trunked switch
port, so that it can access multiple (two) VLANs through a single
physical NIC.

This works fine once I manually configure it, but I can't find a way
to adapt my rc.conf.local model to handle the VLAN setup
automatically at boot time.  I want to end up with a 'public'
interface on vlan 1 of the main physical NIC (and multiple IPs
configured), a 'vlan100' interface on vlan 100 of the main physical
NIC (with IPs configured), and a 'private' interface on the
secondary physical NIC (with IPs configured).

I use an identical rc.conf on the servers, and keep the nitty gritty
details in rc.conf.local, as follows:


rc.conf:

# most machine-specific stuff is in rc.conf.local
#
# these settings are common to all
#
moused_enable=YES
gateway_enable=YES
inetd_enable=YES
sshd_enable=YES
sshd_flags='-o PermitRootLogin=without-password -o ListenAddress=$IP:22'
zfs_enable=YES
ezjail_enable=YES
##eof##

Here is the problematic rc.conf.local:

hostname=trunked-server.example.com

# vlan trunking on interface bce0:
# physical interface bce0 just needs to be up
ifconfig_bce0=up

# We will clone two vlan interfaces:
cloned_interfaces=vlan1 vlan100

# The details for those two cloned interfaces:
ifconfig_vlan1=vlan 1 vlandev bce0
ifconfig_vlan100=vlan 100 vlandev bce0

# Some interfaces get renamed, so that jails can find
# the public and private interfaces:
ifconfig_vlan1_name=public
ifconfig_bce1_name=private

# primary public IP:
IP=10.158.10.18
MASK=/25
defaultrouter=10.158.10.1

# public interface IPs:

ipv4_addrs_public=
${IP}${MASK}
10.158.10.10/32
10.158.10.31-47/32


ipv4_addrs_vlan100=
10.158.2.5/27


# private interface IPs:

#ipv4_addrs_private=10.0.0.7/24

firewall_enable=YES# Set to YES to enable firewall functionality
firewall_script=/root/fw.sh

# jail settings:
jail_set_hostname_allow=NO 
# jail_jail1_parameters=allow.raw_sockets=1 allow.sysvipc=1
jail_parameters=
allow.raw_sockets=1
allow.mount.devfs=1
allow.set_hostname=0

##eof##

Some things I have found:

As given above, the vlan interfaces don't get set up the way I want
them.  public gets created and has all the IPs, but is on vlan 0
with no parent device:

bce0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500

options=c01bbRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO,LINKSTATE
ether 00:1f:29:e1:22:f6
inet6 fe80::21f:29ff:fee1:22f6%bce0 prefixlen 64 scopeid 0x1 
nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL
media: Ethernet autoselect (100baseTX full-duplex)
status: active
private: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500

options=c01bbRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO,LINKSTATE
ether 00:1f:29:e1:22:f4
nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL
media: Ethernet autoselect
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384
options=63RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6
inet6 ::1 prefixlen 128 
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x9 
inet 127.0.0.1 netmask 0xff00 
nd6 options=21PERFORMNUD,AUTO_LINKLOCAL
public: flags=8003UP,BROADCAST,MULTICAST metric 0 mtu 1500
ether 00:00:00:00:00:00
inet 10.158.10.18 netmask 0xff80 broadcast 10.158.10.127
inet 10.158.10.10 netmask 0x broadcast 10.158.10.10
inet 10.158.10.31 netmask 0x broadcast 10.158.10.31
inet 10.158.10.32 netmask 0x broadcast 10.158.10.32
inet 10.158.10.33 netmask 0x broadcast 10.158.10.33
inet 10.158.10.34 netmask 0x broadcast 10.158.10.34
inet 10.158.10.35 netmask 0x broadcast 10.158.10.35
inet 10.158.10.36 netmask 0x broadcast 10.158.10.36
inet 10.158.10.37 netmask 0x broadcast 10.158.10.37
inet 10.158.10.38 netmask 0x broadcast 10.158.10.38
inet 10.158.10.39 netmask 0x broadcast 10.158.10.39
inet 10.158.10.40 netmask 0x broadcast 10.158.10.40
inet 10.158.10.41 netmask 0x broadcast 10.158.10.41
inet 10.158.10.42 netmask 0x broadcast 10.158.10.42
inet 10.158.10.43 netmask 0x 

i915kms, Xorg, and Power management discrepency error

[Bigby James]

Ever since rebuilding world from commit r208369 (merging the newer i915kms from
HEAD) I've continually received this error in my stdout/logs:

 kernel: error: [drm:pid1228:gen6_sanitize_pm] *ERROR* Power management 
 discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 1a0d, was 1a00

The only thing that ever changes is the PID of the process, which always points
to Xorg. Under most typical production use this doesn't seem to have any effect,
but anytime I watch any sort of video on my production laptop the CPU/GPU temp
in my laptop very quickly climbs above 80 degrees celsius. On my multi-purpose
server/HTPC, starting an XBMC/Kodi session has the same effect, even if the
system is idling (just sitting at the main menu with nothing playing at all).
This doesn't stop until I cease video playback on my laptop or kill the Kodi
session on the server. Note that the hardware in both machines is identical
(yes, the server is a laptop), and they're base systems and kernels are
synchronized, so whatever is affectng one should be what's affecting the other.

I came across an older mailing list thread from February[1] on this same basic
subject that didn't seem to go anywhere, but it had the implication that the
i915kms module was the cause. That precisely this same error message is present
on various Linux forums bolsters  the notion that the video driver might be to
blame. If anyone has any insight into how to begin debugging this, I'd be
grateful. Thanks in advance.

- Bigby

[1]: 
http://freebsd.1045724.n5.nabble.com/Weird-ACPI-DRM-messages-on-current-td5986712.html

-- 
A common mistake that people make when trying to design something completely
foolproof is to underestimate the ingenuity of complete fools. - Douglas Adams

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

Re: On-going laptop brightness issues

[Bigby James]

I just saw that this feature got MFC'd in revision r280369 this afternoon. I've 
been
keeping an eye on it, as it's pretty much the only feature that hasn't worked
properly on my laptop and so the last remaining bit I needed for the Golden
FreeBSD Experience. I want to give my thanks to the developers involved, as 
well
as to Kevin, who's been following this longer---and done more about
it---than I have. Just another reason to love this OS, its community and its
hard-working contributors. I've yet to update my systems in response to the
OpenSSL security advisory, so I'll back up my local source tree and start with a
clean pull this evening, and check back in a few days to report how things are
working. Thanks again, all. Take care.

-- 
A common mistake that people make when trying to design something completely
foolproof is to underestimate the ingenuity of complete fools. - Douglas Adams

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

Re: CLANG 3.2 breaks security/pam_ssh_agent_auth on stable/9

[James]

Hi Kimmo. Thanks for this. Your patch works great in stable/9.

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

Re: CLANG 3.2 breaks security/pam_ssh_agent_auth on stable/9

[James]

I was able to correct the problem as well by prefixing strnvis, avoiding
the symbol collision. I also found PR: ports/172941 which also has a fix.

Using my patch or the patch in ports/172941 fixes the segfault for me in
stable/9. However, I quickly ran into another problem. I can't remember the
error message exactly, it was something like Unable to initialize PAM:
Unknown file descriptor. A ktrace didn't reveal anything obvious. I'll try
to test it out tomorrow.

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

Re: buildworld fails on recent stable

[James]

Thanks Dimitry. Confirmed successful build here, too.

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

Re: Checksum errors across ZFS array

[James Snow]

On Fri, Jul 20, 2012 at 04:09:28PM +0100, Dr Josef Karthauser wrote:

 Take care though, my system which had been working fine for about
 a year when I noticed the ZFS rot (which all appears to be recent
 in time). I ran memcheck+ on it for 8 hours or so, and it showed no
 errors at all. However, when I replaced the memory with a different
 vendor the problems went away. (Reboots and power off/on restarts
 hadn't fixed the problem before!).

 So, take care if the memory doesn't report any failures, it might
 still be faulty.

I've run memtest for about 20 hours now (13 hours in one pass, 7 and
counting on the second) and seen no errors. Hrm.

 p.s. It was my fault that I wasn't running ECC memory on the system!

I am running ECC memory though. If you'd had ECC memory to start do you
think you might have seen a different result?

In my case, replacing all the RAM and getting a 2nd controller are
almost the same cost. Since a second controller will give me the best
visibility - or long-term expandability if it turns out not to be the
controller - I've gone ahead and ordered one.

If I move half the disks to the new controller and continue to see the
problems only on the old controller, I know it's the controller or the
slot on the motherboard. If the problem continues without any change, I
can replace RAM, and then the motherboard.


-Snow

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

Re: Checksum errors across ZFS array

[James Snow]

On Fri, Jul 20, 2012 at 03:46:21PM -0700, Doug Barton wrote:
 
 You probably know this already, but just in case ... Software memory
 tests cannot tell you conclusively that memory is good, only that it's
 bad. 

I may have known that in a past life but certainly wasn't thinking about
it now.

 To make sure it's good you need a hardware tester.

Is there one you'd recommend?


-Snow

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

Checksum errors across ZFS array

[James Snow]

I have a ZFS server on which I've seen periodic checksum errors on
almost every drive. While scrubbing the pool last night, it began to
report unrecoverable data errors on a single file.

I compared an md5 of the supposedly corrupted file to an md5 of the
original copy, stored on different media. They were the same, suggesting
no corruption.

A large file was being written to the pool while the scrub was in
progress, and the entire array became unresponsive. The OS was still up,
but 'zpool status' showed the scrub progress stuck at the same spot,
with the throughput rate falling. 'shutdown -r now' stalled. Eventually
I hard power cycled the system.

Now, attempting to read the file that ZFS reports errors on yields
Input/output error. The scrub completed, with the following result:

NAME STATE READ WRITE CKSUM
tank ONLINE   0 0 7
  mirror-0   ONLINE   0 0 0
aacd0p1  ONLINE   0 0 0
aacd4p1  ONLINE   0 0 1
  mirror-1   ONLINE   0 0 0
aacd1p1  ONLINE   0 0 0
aacd5p1  ONLINE   0 0 0
  mirror-2   ONLINE   0 014
aacd2p1  ONLINE   0 014
aacd6p1  ONLINE   0 014
  mirror-3   ONLINE   0 0 0
aacd3p1  ONLINE   0 0 0
aacd7p1  ONLINE   0 0 0

The system configuration is as follows:

Controller:  Adaptec 2805 
Motherboard: Supermicro X8STE
Drive Cage:  2x Supermicro CSE-M35T-1
Memory:  2x Kingston 12GB ECC (KVR1066D3E7SK3/12G)
PSU: Nexus RX-7000
OS:  9.0-RELEASE-p3
ZFS: ZFS filesystem version 5, ZFS storage pool version 28


The Adaptec card has 2 ports, each of which uses a 4-port fan-out cable.
The cables are routed as shown:

  /--- aacd0 (ST1000DM003-9YN1 CC4D)
 / /-- aacd1 (ST1000DM003-9YN1 CC4D)
p1-
 \ \-- aacd2 (WDC WD1001FALS-0 05.0)
  \--- aacd3 (WDC WD1001FALS-0 05.0)

  /--- aacd4 (ST1000DM003-9YN1 CC4D)
 / /-- aacd5 (ST1000DM003-9YN1 CC4D)
p2-
 \ \-- aacd6 (WDC WD1002FAEX-0 05.0)
  \--- aacd7 (WDC WD1002FAEX-0 05.0)

You can see that each ZFS mirror device is comprised of one drive from
each drive carrier, on separate ports, on separate cables.

Since I have seen periodic checksum errors on almost every drive but the
only common component is the Adapter controller and the motherboard, I
suspect the controller. (Or the motherboard, but I'm starting with the
controller since it's much simpler to swap out.)

Could it be something else? What else I should be looking at? Any input
greatly appreciated.


-Snow

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

Re: Checksum errors across ZFS array

[James Snow]

On Thu, Jul 19, 2012 at 06:05:32PM +0100, Dr Joe Karthauser wrote:

 Hi James,

 It's almost definitely a memory problem. I'd change it ASAP if I were
 you.

 I lost about 70mb from my zfs pool for this very reason just a few
 weeks ago. Luckily I had enough snapshots from before the rot set in
 to recover most of what I lost.

Thanks for the input. I will run a memory test against it.

If I may, why almost definitely a memory problem and not an issue with
the controller? (Or did you mean the controller memory?)


-Snow

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

Possible Clang regression - object files are always mode 0600

[James]

Hi all. I've come across a possible Clang regression that recently
crept into stable/9. I'd like to check to see whether it's a true bug
or if I jacked something up. It appears all object files are created
with mode 0600 rather than honoring umask. This breaks installworld
for me. I use a centralized src/obj over NFS configuration and
installing to the target system fails with a permission denied error.

Using obj/[SNIP]/src/cddl/lib/drti as an
example:

Clang:
-rw-r--r--   1 jjk  users  7731 May 24 15:05 .depend
-rw---   1 jjk  users  8496 May 24 15:05 drti.o

GCC:
-rw-r--r--   1 jjk  users  7731 May 24 20:54 .depend
-rw-r--r--   1 jjk  users  8808 May 24 20:54 drti.o

I tested on May 24th (with 3.1 prerelease MFC) as well as the 3.1
release after it was MFC'd on Sunday.

TIA!

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

Re: Possible Clang regression - object files are always mode 0600

[James]

On Tue, May 29, 2012 at 11:59 AM, Dimitry Andric dimi...@andric.com wrote:

 Just so you know, this is indeed a regression that has crept into
 clang, and even into the 3.1 release. :(

 I'm working on fixing it in head, then I will merge the fix to
 stable/9 in a few days.

Cool. Thanks much for fixing it, Dimitry.

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

Re: Stable buildkernel warning: no previous prototype for legacy_pcib_map_msi

[James Hall]

I discovered that my copy of src/sys/amd64/include/legacyvar.h does not
include the two lines

60| int legacy_pcib_map_msi(device_t pcib, device_t dev, int irq,
61| uint64_t *addr, uint32_t *data);

which is in the stable sources available through svn at
http://svnweb.freebsd.org/base/stable/9/sys/amd64/include/legacyvar.h?revision=234150view=markuppathrev=234872.
I guess I have a bad mirror or something...

--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/Stable-buildkernel-warning-no-previous-prototype-for-legacy-pcib-map-msi-tp5678227p5678391.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Stable buildkernel warning: no previous prototype for legacy_pcib_map_msi

[James Hall]

On May 1, 2012 11:32 AM, John Baldwin j...@freebsd.org wrote:

 On Tuesday, May 01, 2012 12:22:17 pm James Hall wrote:
  I discovered that my copy of src/sys/amd64/include/legacyvar.h does not
  include the two lines
 
  60| int legacy_pcib_map_msi(device_t pcib, device_t dev, int irq,
  61|   uint64_t *addr, uint32_t *data);
 
  which is in the stable sources available through svn at
 

http://svnweb.freebsd.org/base/stable/9/sys/amd64/include/legacyvar.h?revision=234150view=markuppathrev=234872
.
  I guess I have a bad mirror or something...

 Did you use cvsup10?  I've had one other report of that mirror being stale
 specifically in regards to this change.

 --
 John Baldwin

Yes, I was originally using cvsup10.

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

RE: FreeBSD 8.3-R sysinstall does not see disks that are recognized during boot

[Harris, James R]

-- Forwarded message --
Date: Tue, 17 Apr 2012 18:02:31 -0400 (EDT)
From: Andy Dills a...@xecu.net
To: freebsd-stable@freebsd.org
Subject: FreeBSD 8.3-R sysinstall does not see disks that are recognized
during boot


I've got a new supermicro server I'm trying to get FreeBSD on. It uses the
Intel c602 chipset, and it's my understanding that support for that
chipset (c60X) was recently added via the isci driver. Ok, great, that
explains why 8.2-R and 9.0-R didn't see the drives.

So, I grabbed the memstick image of 8.3-RELEASE that is on the ftp server,
booted it up, and sure enough, as the dmesg scrolls I see it now properly
recognizes da0 and da1, as it should (the memstick is da2). It sees the
disks fine at this point, everything looks good.

However, once the system finishes booting and loads into sysinstall, and I
go to partition the drives, I get No disks found! Please verify that your
disk controller is being properly loaded at boot time.

Any suggestions for avenues to troubleshoot this?  I have pictures to
document if it helps.

Seems very odd. I confirmed the behavior with the SATA set to IDE, AHCI,
and RAID modes. (The drives were recognized as da0 and da1 during bootup
in all three modes, but not by sysinstall.)

Andy and I worked this out offline - workaround was to go to Options|Re-scan 
which caused the devices to show up in the sysinstall menu.  I'm adding details 
here for future reference.

1) C60x chipsets have the 6 traditional SATA ports, plus 4 or 8 SAS ports.  
Only the latter are controlled by the isci(4) driver.
2) The IDE/AHCI/RAID modes apply only to the traditional SATA ports.
3) In Andy's case, going to Options|Re-scan Devices caused the disks to show 
up.  This problem seems to be system or platform-dependent, as I was not able 
to reproduce with 8.3 memstick image on my C600 systems.
4) There was a problem with initial device scan using isci(4) on 7-STABLE, 
which necessitated r233371.  This was MFC'd back to 8-STABLE, but after 8.3 was 
released.  I'm fairly convinced this is the root cause of Andy's problem, but 
don't have any easy way to verify.


Thanks,
Andy

---
Andy Dills
Xecunet, Inc.
www.xecu.net
301-682-9972
---
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: smartctl / mpt on 9.0-RC1

[James]

On Thu, Nov 3, 2011 at 12:12 PM, Alex Samorukov m...@os2.kiev.ua wrote:
 I am smartmontools developer and FreeBSD port maintainer. If you
 could provide shell access to the affected system i can try to debug
 issue. I have no access to the mpt devices myself and it is unclear
 what going on from provided backtrace.

Hi Alex. If you're unable to get shell access from Frank, I'd be
glad to help out. I have mps(4) and mpt(4) hardware available and
experience the same bug.

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

Re: smartctl / mpt on 9.0-RC1

[James]

On Thu, Nov 3, 2011 at 1:52 PM, Alex Samorukov m...@os2.kiev.ua wrote:
 Thank you. I currently got shell, but user-only, what is useless for
 me ;-) (All ioctl/cam commands require superuser)

 I asked for the root and now waiting for it. You can also provide
 shell so i will have more boxes to test. I am expecting some very
 trivial bug caused by some wrong data returned from the driver
 without strict check in smartctl.

No problem. Send me your public key privately and I'll set you up.

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

Re: smartctl / mpt on 9.0-RC1

[James]

On Thu, Nov 3, 2011 at 3:09 PM, Alex Samorukov m...@os2.kiev.ua wrote:
 Could you please try to build latest svn version (see [1]) ? I think
 i fixed this bug.

Thanks, Alex. Looks like you fixed it. smartctl no longer
segfaults.

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

FreeBSD 8.1 make world FAILED!

[James Chang]

Dear Sir,

 I install FreeBSD 8.1 RELEASE today and want use make world to
upgrade to 8.1-STABLE,
But It show me the following ERROR messages :
=
FreeBSD81# make installworld
mkdir -p /tmp/install.pMB8TADB
progs=$(for prog in [ awk cap_mkdb cat chflags chmod chown  date echo
egrep find grep install-info  ln lockf make mkdir mtree mv pwd_mkdb rm
sed sh sysctl  test true uname wc zic; do  if progpath=`which $prog`;
then  echo $progpath;  else  echo Required tool $prog not found in
PATH. 2;  exit 1;  fi;  done);  libs=$(ldd -f %o %p\n -f %o
%p\n $progs 2/dev/null | sort -u |  while read line; do  set --
$line;  if [ $2 $3 != not found ]; then  echo $2;  else  echo
Required library $1 not found. 2;  exit 1;  fi;  done);  cp $libs
$progs /tmp/install.pMB8TADB
cp -R ${PATH_LOCALE:-/usr/share/locale} /tmp/install.pMB8TADB/locale
cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj  MACHINE_ARCH=amd64
MACHINE=amd64  CPUTYPE=nocona
GROFF_BIN_PATH=/usr/obj/usr/src/tmp/legacy/usr/bin
GROFF_FONT_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/groff_font
GROFF_TMAC_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/tmac
PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/tmp/install.pMB8TADB
 LD_LIBRARY_PATH=/tmp/install.pMB8TADB
PATH_LOCALE=/tmp/install.pMB8TADB/locale make -f Makefile.inc1
__MAKE_SHELL=/tmp/install.pMB8TADB/sh reinstall;
MAKEOBJDIRPREFIX=/usr/obj  MACHINE_ARCH=amd64  MACHINE=amd64
CPUTYPE=nocona  GROFF_BIN_PATH=/usr/obj/usr/src/tmp/legacy/usr/bin
GROFF_FONT_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/groff_font
GROFF_TMAC_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/tmac
PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/tmp/install.pMB8TADB
 LD_LIBRARY_PATH=/tmp/install.pMB8TADB
PATH_LOCALE=/tmp/install.pMB8TADB/locale rm -rf /tmp/install.pMB8TADB
--
 Making hierarchy
--
cd /usr/src; make -f Makefile.inc1 hierarchy
cd /usr/src/etc;make distrib-dirs
mtree -eU  -f /usr/src/etc/mtree/BSD.root.dist -p /
mtree -eU  -f /usr/src/etc/mtree/BSD.var.dist -p /var
mtree -eU  -f /usr/src/etc/mtree/BSD.usr.dist -p /usr
mtree -eU  -f /usr/src/etc/mtree/BSD.include.dist  -p /usr/include
mtree -deU  -f /usr/src/etc/mtree/BIND.chroot.dist  -p /var/named
mtree -deU  -f /usr/src/etc/mtree/BSD.sendmail.dist -p /
cd /; rm -f /sys; ln -s usr/src/sys sys
cd /usr/share/man/en.ISO8859-1; ln -sf ../man* .
cd /usr/share/man/en.UTF-8; ln -sf ../man* .
cd /usr/share/man;  set - `grep ^[a-zA-Z] /usr/src/etc/man.alias`;
while [ $# -gt 0 ] ;  do  rm -rf $1;  ln -s $2 $1;  shift;
shift;  done
cd /usr/share/openssl/man;  set - `grep ^[a-zA-Z]
/usr/src/etc/man.alias`;  while [ $# -gt 0 ] ;  do  rm -rf $1;  ln
-s $2 $1;  shift; shift;  done
cd /usr/share/openssl/man/en.ISO8859-1; ln -sf ../man* .
cd /usr/share/nls;  set - `grep ^[a-zA-Z] /usr/src/etc/nls.alias`;
while [ $# -gt 0 ] ;  do  rm -rf $1;  ln -s $2 $1;  shift;
shift;  done

--
 Installing everything
--
cd /usr/src; make -f Makefile.inc1 install
=== share/info (install)
=== lib (install)
=== lib/csu/amd64 (install)
install -o root -g wheel -m 444  crt1.o crti.o crtn.o Scrt1.o gcrt1.o /usr/lib
=== lib/libc (install)
install -C -o root -g wheel -m 444   libc.a /usr/lib
install -C -o root -g wheel -m 444   libc_p.a /usr/lib
install -s -o root -g wheel -m 444   -fschg -S  libc.so.7 /lib
install: rename: /lib/i...@dhuu to /lib/libc.so.7: Operation not permitted
*** Error code 71

Stop in /usr/src/lib/libc.
*** Error code 1

Stop in /usr/src/lib.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.

Are there smothing wrong?
Could someone give me a hand?

Best Regards!

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

USB UPS detached and cannot reattach (could not allocate new device)

[James Seward]

Hello,

On my 8.0-RELEASE machine running GENERIC this happened this afternoon:

Mar 28 17:48:13 yomi apcupsd[969]: UPS Self Test switch to battery.
Mar 28 17:48:17 yomi kernel: ugen0.2: American Power Conversion at
usbus0 (disconnected)
Mar 28 17:48:18 yomi kernel: usb_alloc_device:1586: set address 2
failed (USB_ERR_STALLED, ignored)
Mar 28 17:48:18 yomi kernel: usb_alloc_device:1624: getting device
descriptor at addr 2 failed, USB_ERR_STALLED!
Mar 28 17:48:19 yomi kernel: usbd_req_re_enumerate:1539: addr=2, set
address failed! (USB_ERR_STALLED, ignored)
Mar 28 17:48:19 yomi kernel: usbd_req_re_enumerate:1553: getting
device descriptor at addr 2 failed, USB_ERR_STALLED!
Mar 28 17:48:20 yomi kernel: usbd_req_re_enumerate:1539: addr=2, set
address failed! (USB_ERR_STALLED, ignored)
Mar 28 17:48:20 yomi kernel: usbd_req_re_enumerate:1553: getting
device descriptor at addr 2 failed, USB_ERR_STALLED!
Mar 28 17:48:20 yomi kernel: ugen0.2: (null) at usbus0 (disconnected)
Mar 28 17:48:20 yomi kernel: uhub_reattach_port:435: could not
allocate new device!
Mar 28 17:48:27 yomi apcupsd[969]: Communications with UPS lost.

Unplugging the UPS and replugging it doesn't seem to help, even in a
different port. My UPS is a Smart-UPS 750 and my apcupsd is 3.14.5
(10 January 2009) freebsd.

ugen0.1: UHCI root HUB VIA at usbus0, cfg=255 md=HOST spd=FULL (12Mbps) pwr=ON
ugen1.1: UHCI root HUB VIA at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON

dev.usbus.0.%desc: VIA 83C572 USB controller
dev.usbus.1.%desc: VIA 83C572 USB controller

I'm happy to provide more info if someone sufficiently clueful can
tell me where to look :)

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

Re: 8.0-RELEASE/amd64 - full ZFS install - low read and write disk performance

[James R. Van Artsdalen]

Dan Naumov wrote:
 [j...@atombsd ~]$ dd if=/dev/zero of=/home/jago/test2 bs=1M count=4096
 4096+0 records in
 4096+0 records out
 4294967296 bytes transferred in 143.878615 secs (29851325 bytes/sec)

 This works out to 1GB in 36,2 seconds / 28,2mb/s in the first test and
 4GB in 143.8 seconds / 28,4mb/s
For the record, better results can be seen.  In my test I put 3 Seagate
Barracuda XT drives in a port multiplier and connected that to one port
of a PCIe 3124 card.

The MIRROR case is at about the I/O bandwidth limit of those drives.

[r...@kraken ~]# zpool create tmpx ada{2,3,4}  
[r...@kraken ~]# dd if=/dev/zero of=/tmpx/test2 bs=1M count=4096
4096+0 records in
4096+0 records out
4294967296 bytes transferred in 20.892818 secs (205571470 bytes/sec)
[r...@kraken ~]# zpool destroy tmpx
[r...@kraken ~]# zpool create tmpx mirror ada{2,3}
[r...@kraken ~]# dd if=/dev/zero of=/tmpx/test2 bs=1M count=4096
4096+0 records in
4096+0 records out
4294967296 bytes transferred in 36.432818 secs (117887321 bytes/sec)
[r...@kraken ~]#

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

Re: FreeBSD 7.2-STABLE make installworld ERROR

[James Chang]

Thanks Yuri.
It solve my problem :)

Best Regards!

2009/12/22 Yuri Pankov yuri.pan...@gmail.com:
 On Tue, Dec 22, 2009 at 01:52:14PM +0800, James Chang wrote:
 Dears,

     Today, I use ctm upgrade my FreeBSD source code to src-7 859
 When I try to make world, in make buildworld stage it show me World
 build completed on Tue Dec 22 12:57:30 CST 2009
 But when I execute make installworld it show me the following ERROR 
 message:

 === sys/boot/i386/btx (install)
 === sys/boot/i386/btx/btx (install)
 === sys/boot/i386/btx/btxldr (install)
 === sys/boot/i386/btx/lib (install)
 === sys/boot/i386/boot2 (install)
 cc -Os  -fno-guess-branch-probability  -fomit-frame-pointer
 -fno-unit-at-a-time  -mno-align-long-strings  -mrtd  -mno-mmx
 -mno-3dnow -mno-sse -mno-sse2 -mno-sse3  -DUFS1_AND_UFS2  -DFLAGS=0x80
  -DSIOPRT=0x3f8  -DSIOFMT=0x3  -DSIOSPD=9600
 -I/usr/src/sys/boot/i386/boot2/../../common
 -I/usr/src/sys/boot/i386/boot2/../btx/lib -I.  -Wall
 -Waggregate-return -Wbad-function-cast -Wcast-align
 -Wmissing-declarations -Wmissing-prototypes -Wnested-externs
 -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings  -Winline
 --param max-inline-insns-single=100 -ffreestanding
 -mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow -mno-sse -mno-sse2
 -mno-sse3 -m32 -march=i386  -S -o boot2.s.tmp
 /usr/src/sys/boot/i386/boot2/boot2.c
 sed -e '/align/d' -e '/nop/d'  boot2.s.tmp  boot2.s
 rm -f boot2.s.tmp
 as  --32 -o boot2.o boot2.s
 ld -static -N --gc-sections -nostdlib -m elf_i386_fbsd -Ttext 0x2000
 -o boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o
 boot2.o sio.o
 objcopy -S -O binary boot2.out boot2.bin
 btxld -v -E 0x2000 -f bin -b
 /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr  -o
 boot2.ld -P 1 boot2.bin
 btxld:No such file or directory
 *** Error code 1

 Stop in /usr/src/sys/boot/i386/boot2.
 *** Error code 1

 Stop in /usr/src/sys/boot/i386.
 *** Error code 1

 Stop in /usr/src/sys/boot.
 *** Error code 1

 Stop in /usr/src/sys.
 *** Error code 1

 Stop in /usr/src.
 *** Error code 1

 Stop in /usr/src.
 *** Error code 1

 Stop in /usr/src.
 *** Error code 1

 Stop in /usr/src.

 =
 PS. My uname -a before make installworld
 FreeBSD db1.books.com.tw 7.2-STABLE FreeBSD 7.2-STABLE #1: Thu Dec  3
 23:08:26 CST 2009
 r...@db1.books.com.tw:/usr/obj/usr/src/sys/GENERIC  amd64


 Best Regards!

 Looks like 
 http://lists.freebsd.org/pipermail/freebsd-stable/2006-September/028377.html


 Yuri

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

FreeBSD 7.2-STABLE make installworld ERROR

[James Chang]

Dears,

Today, I use ctm upgrade my FreeBSD source code to src-7 859
When I try to make world, in make buildworld stage it show me World
build completed on Tue Dec 22 12:57:30 CST 2009
But when I execute make installworld it show me the following ERROR message:

=== sys/boot/i386/btx (install)
=== sys/boot/i386/btx/btx (install)
=== sys/boot/i386/btx/btxldr (install)
=== sys/boot/i386/btx/lib (install)
=== sys/boot/i386/boot2 (install)
cc -Os  -fno-guess-branch-probability  -fomit-frame-pointer
-fno-unit-at-a-time  -mno-align-long-strings  -mrtd  -mno-mmx
-mno-3dnow -mno-sse -mno-sse2 -mno-sse3  -DUFS1_AND_UFS2  -DFLAGS=0x80
 -DSIOPRT=0x3f8  -DSIOFMT=0x3  -DSIOSPD=9600
-I/usr/src/sys/boot/i386/boot2/../../common
-I/usr/src/sys/boot/i386/boot2/../btx/lib -I.  -Wall
-Waggregate-return -Wbad-function-cast -Wcast-align
-Wmissing-declarations -Wmissing-prototypes -Wnested-externs
-Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings  -Winline
--param max-inline-insns-single=100 -ffreestanding
-mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow -mno-sse -mno-sse2
-mno-sse3 -m32 -march=i386  -S -o boot2.s.tmp
/usr/src/sys/boot/i386/boot2/boot2.c
sed -e '/align/d' -e '/nop/d'  boot2.s.tmp  boot2.s
rm -f boot2.s.tmp
as  --32 -o boot2.o boot2.s
ld -static -N --gc-sections -nostdlib -m elf_i386_fbsd -Ttext 0x2000
-o boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o
boot2.o sio.o
objcopy -S -O binary boot2.out boot2.bin
btxld -v -E 0x2000 -f bin -b
/usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr  -o
boot2.ld -P 1 boot2.bin
btxld:No such file or directory
*** Error code 1

Stop in /usr/src/sys/boot/i386/boot2.
*** Error code 1

Stop in /usr/src/sys/boot/i386.
*** Error code 1

Stop in /usr/src/sys/boot.
*** Error code 1

Stop in /usr/src/sys.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.

=
PS. My uname -a before make installworld
FreeBSD db1.books.com.tw 7.2-STABLE FreeBSD 7.2-STABLE #1: Thu Dec  3
23:08:26 CST 2009
r...@db1.books.com.tw:/usr/obj/usr/src/sys/GENERIC  amd64


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

Re: FreeBSD 7.2-STABLE make installworld ERROR

[James Chang]

Dear Sir,
  My update steps as following:
1.ctm to the latest source
2.rm -rf /usr/orb/*
3.cd /usr/src
4.make buildworld
5.make buildkernel
7.make installkernel
8.make installworld
9.FAILED :

Best Regards!

  James Chang

2009/12/22 Andriy Gapon a...@icyb.net.ua:
 on 22/12/2009 07:52 James Chang said the following:
     Today, I use ctm upgrade my FreeBSD source code to src-7 859
 When I try to make world, in make buildworld stage it show me World
 build completed on Tue Dec 22 12:57:30 CST 2009
 But when I execute make installworld it show me the following ERROR 
 message:

 === sys/boot/i386/btx (install)
 === sys/boot/i386/btx/btx (install)
 === sys/boot/i386/btx/btxldr (install)
 === sys/boot/i386/btx/lib (install)
 === sys/boot/i386/boot2 (install)
 cc -Os  -fno-guess-branch-probability  -fomit-frame-pointer
 -fno-unit-at-a-time  -mno-align-long-strings  -mrtd  -mno-mmx
 -mno-3dnow -mno-sse -mno-sse2 -mno-sse3  -DUFS1_AND_UFS2  -DFLAGS=0x80
  -DSIOPRT=0x3f8  -DSIOFMT=0x3  -DSIOSPD=9600
 -I/usr/src/sys/boot/i386/boot2/../../common
 -I/usr/src/sys/boot/i386/boot2/../btx/lib -I.  -Wall
 -Waggregate-return -Wbad-function-cast -Wcast-align
 -Wmissing-declarations -Wmissing-prototypes -Wnested-externs
 -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings  -Winline
 --param max-inline-insns-single=100 -ffreestanding
 -mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow -mno-sse -mno-sse2
 -mno-sse3 -m32 -march=i386  -S -o boot2.s.tmp
 /usr/src/sys/boot/i386/boot2/boot2.c
 sed -e '/align/d' -e '/nop/d'  boot2.s.tmp  boot2.s
 rm -f boot2.s.tmp
 as  --32 -o boot2.o boot2.s
 ld -static -N --gc-sections -nostdlib -m elf_i386_fbsd -Ttext 0x2000
 -o boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o
 boot2.o sio.o
 objcopy -S -O binary boot2.out boot2.bin
 btxld -v -E 0x2000 -f bin -b
 /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr  -o
 boot2.ld -P 1 boot2.bin
 btxld:No such file or directory

 Have you, by a chance, updated/modified your sources between buildworld and
 installworld attempt?

 --
 Andriy Gapon

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

Order To New Zealand

[Bryan James]

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

issues with Intel Pro/1000 and 1000baseTX

[James Tanis]

I have a FreeBSD v7.0 box it has two Intel Pro/1000 NICs, the one in 
question is:


em1: Intel(R) PRO/1000 Network Connection Version - 6.7.3 port 
0x2020-0x203f mem 0xd806-0xd807,0xd804-0xd805 irq 19 at 
device 0.1 on pci4


what we get after boot is:

em1: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric 0 
mtu 1500

   options=19bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4
   ether 00:30:48:xx:xx:xx
   inet 192.168.1.1 netmask 0xff00 broadcast 192.168.1.255
   media: Ethernet autoselect (100baseTX full-duplex)
   status: active

The problem is that the NIC refuses to connect at 1000baseTX.

It's connected to a HP Procurve 1700-24 switch which supports 1000baseTX 
on ports 23 and 24. This particular computer is connected on port 24. I 
have a much older end user system which uses the same card (but earlier 
revision), runs Windows XP and is plugged in to port 23. The end user 
system has no problem connecting at 1000baseTX. I have of course tried 
switching ports.


Attempting to force 1000baseTX via:

ifconfig em1 media 1000baseTX mediaopt full-duplex

gets me:

status: no carrier

After forcing the NIC to go 1000baseTX the LEDs on the backpane are both 
off. I can only come to the conclusion that this is a driver issue based 
on previous experience and the simple fact that the end user system is 
capable of connecting at 1000baseTX. Anybody have any suggestions? I'm 
hoping I'm wrong. I'd rather not do an in-place upgrade, this is a 
production system and the main gateway for an entire school, when I do 
not even know for sure whether this will fix the problem. It's worth it 
to me though, having a 1000baseTX uplink from the switch would remove a 
major bottleneck for me.


Any help would be appreciated.

--
James Tanis
Technical Coordinator
Computer Science Department
Monsignor Donovan Catholic High School

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

Re: issues with Intel Pro/1000 and 1000baseTX

[James Tanis]

Bill Moran wrote:

In response to James Tanis jta...@mdchs.org:


  

.. snip ..
Attempting to force 1000baseTX via:

ifconfig em1 media 1000baseTX mediaopt full-duplex

gets me:

status: no carrier

After forcing the NIC to go 1000baseTX the LEDs on the backpane are both 
off. I can only come to the conclusion that this is a driver issue based 
on previous experience and the simple fact that the end user system is 
capable of connecting at 1000baseTX. Anybody have any suggestions? I'm 
hoping I'm wrong. I'd rather not do an in-place upgrade, this is a 
production system and the main gateway for an entire school, when I do 
not even know for sure whether this will fix the problem. It's worth it 
to me though, having a 1000baseTX uplink from the switch would remove a 
major bottleneck for me.



Try forcing on both ends (I assume the Procurve will allow you to do that).
One thing I've seen consistently is that if you force the speed/duplex on
one end, the other end will still try to autoneg, and will end up with
something stupid like 100baseT/half-duplex, or will give up and disable
the port.
  
Ok, I just did that -- I have now attempted to force 1000baseTX on both 
sides and on one side while the other was left auto, all three possible 
combinations resulted in the same behavior (no carrier).

Also, try autoneg on both ends.  Make absolutely sure the Procurve is set
to autoneg.
  
This was the original set up. It is also how I have it set up currently, 
it results in 100baseTX full-duplex on both sides.

Replace the cable.  If the cable is marginal, autoneg will downgrade the
speed to ensure reliability.  Use a cable that you know will produce
1000baseTX because you've tested it on other systems.
  
Well, I don't have any verified working cable of the appropriate length 
so I simply switched out the cables for the main server and the backup 
server. They are both cat6 cables crimped with cat5e modules by me. For 
what reason (bad crimp job?) that seemed to fix the issue.


Thanks for the advice!

--
James Tanis
Technical Coordinator
Computer Science Department
Monsignor Donovan Catholic High School

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

Re: [PANIC] recent 7.2-STABLE when probing drm

[Jimmie James]

On Tue, 2009-05-05 at 13:06 +0200, Guido Falsi wrote:

Hi!

I'm using FreeBSD/i386 stable on a HP DC7800 PC.

It has an Intel Q35 graphic chip.

After upgrading to a recent stable I experienced a pani on boot, just
after probing drm.

I investigated a little and found out that reverting the file

src/sys/dev/pci/pci.c

to rev. 1.355.2.9 (SVN Rev 190092) solves the crash.

I could not investigatte urther right away, but some regression was
introduced with this rev.

Is any more information needed?


I want to add a me too. I can't compile in a debugger as my sources 
are updated to 7.2, and any kernel built panics with the same message.
I did find this on the CURRENT mailing list, but it wont apply cleanly: 
http://www.mailinglistarchive.com/freebsd-curr...@freebsd.org/msg26975.html



vgap...@pci0:0:2:0: class=0x03 card=0x25821043 chip=0x25828086 
rev=0x04 hdr=0x00

vendor = 'Intel Corporation'
device = '82915G/GV/GL, 82910GL Integrated Graphics Device'
class  = display
subclass   = VGA
vgap...@pci0:0:2:1: class=0x038000 card=0x25821043 chip=0x27828086 
rev=0x04 hdr=0x00

vendor = 'Intel Corporation'
device = '82915G Graphics device: 82915G/GV/910GL Express 
Chipset Family'

class  = display

From a 7.2-PRERELEASE kernel.

vgapci0: VGA-compatible display port 0x6800-0x6807 mem 
0xcfd8-0xcfdf,0xd000-0xdfff,0xcfe8-0xcfeb at 
device 2.0 on pci0

agp0: Intel 82915G (915G GMCH) SVGA controller on vgapci0
drm0: Intel i915G on vgapci0
vgapci0: child drm0 requested pci_enable_busmaster
vgapci1: VGA-compatible display mem 0xcfe0-0xcfe7 at device 
2.1 on pci0

vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
drm0: Intel i915G on vgapci0
vgapci0: child drm0 requested pci_enable_busmaster
info: [drm] AGP at 0xd000 256MB
info: [drm] Initialized i915 1.6.0 20080730
drm0: [ITHREAD]
drm0: [ITHREAD]

--
Over the years I've come to regard you as people I've met.

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

Re: watchdog timeout

[James Wyatt]

On Fri, 10 Apr 2009, Pyun YongHyeon wrote:

On Wed, Apr 08, 2009 at 10:41:44AM +0200, xer wrote:

Hello
I have some problems with 3Com nics, after a upgrade from 5.5-STABLE to
6.4-STABLE.

This machine has two 3com nics (one is LAN other is WAN) and i see too much
watchdog timeout on both cards.
This on/off up/down on cards, affect the interrupt to clients that are
downloading from apache web server, especially on large files.


xer:/root# dmesg
xl1: watchdog timeout
xl1: link state changed to DOWN
xl1: link state changed to UP
xl1: watchdog timeout
xl1: link state changed to DOWN
xl1: link state changed to UP
xl1: watchdog timeout
xl1: link state changed to DOWN
xl1: link state changed to UP
-

[ . . . ]

As you can see, the cards are 3c905C-TX model.
Someone told me to change drivers, but i cannot understand this advice.
I got same errors with same cards but with another mainboard, same problem,
watchdog appears after an upgrade from 5.4-STABLE to 6.4-STABLE.

I don't think that to change nic's pci slots, will solve the problem, i
think that maybe change the nics would resolve the matter, but i cannot
access to both FreeBSD phisically, cause the boxes are too far from me
(about 3500 km).

I'm asking you some advices, and i can i fix this problem.
p.s. with both 5.4 or 5.5 old kernel, the nics was fine.


I vaguely remember there were a couple of reports on xl(4) watchdog
timeouts. I'm not sure this came from missing Tx interrupts but
would you try attached patch?
Note, it was generated against HEAD and you should experiment the
attached patch on local box prior to applying to your production
server.


Perhaps the case can convey the amount of hair I lost over this: HAVE YOU 
CHECKED YOUR BIOS AND ONBOARD IO SETTINGS?  I have been swapping boards 
for days for another firewall project and finally figured it out last 
night.  I would get messages like these, depending on the 3rd card used:


xl0: Watchdog Timeout
pcn0: Watchdog timeout

Finally the Sierra Nevada Porter kicked-in and an old idea came back to 
me: I was running out of interrupts!  1/2 (^_^)  The hint was from a 
combination of having the earlier advice of set the 'PNP OS' to false 
fail and a Tom's Hardware mobo review complaint about 5-slot PCI mobos 
having IRQ sharing issues.  Thanks to you both wherever you are!


Finally I went in and disabled all the onboard IO I wasn't using to free 
up IRQs.  Disable the onboard serial if you aren't using them.  If you 
are, then an 8-port board or USB serial, can save COM1 and COM2 IRQs.  No 
video IRQ needed for simple console work.  No parallel needed, so saved 
that one.  No floppy nowadays, either.  Lots of options for you!


Thinking I hadn't had IRQ issues in 15 years or so, it sure reminded me 
that we still have the legacy x86 IRQ limitations.  This has pushed me to 
thinking more about shifting to trunked VLANs to save ENet ports and make 
recovery easier.


FWIW: I tend to use different cards so the network ports don't float to 
other numbers if one dies.  This made the problem worse because the 
drivers assign IRQs when they load, so it looked like xl0 cards were the 
issue when 'de*' and 'dc*' worked.  Changing slots changed things too! 
This explains some of what you're experience shows.


There is no way I can give back to this list what it's given me in 
technical support, but if this makes things work for you, then I've given 
*something* back and it really is a Good Friday - Jy@

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

Upgrading from 7.0 to 7.1

[James Wu]

Hi all,

I'm brand new to the list so forgive me if this has been answered. I 
tried searching the archives and tried googling and didn't come up with 
any results.


I've been wanting to play with setfib multi-routing tables in 7.1, 
however, we have a bunch of 7.0 machines. I thought I'd take a test 
machine and upgrade it to 7.1. Everything went smoothly at first. I 
compiled a custom 7.1 kernel and installed it just fine. Afterwards, I  ran:


freebsd-update fetch
freebsd-update install
to upgrade to the latest 7.0

then:
freebsd-update upgrade -r 7.1-RELEASE
freebsd-update install -r 7.1-RELEASE
freebsd-update fetch
to upgrade to 7.1

now when I do a
uname -a,
I get FreeBSD 7.1-RELEASE-p3 which looks right to me

The problem I'm running into though is that the setfib binary doesn't seem to been added during the upgrade as I don't see it anywhere. 
I took a fresh install of 7.1 and do see it /usr/sbin/, but it's not there for the upgraded version of 7.1. 

I guess at this point, I would like to do a reinstall of the sbin folder if it is possible or somehow get a clean copy of the /usr/sbin/ folder into my upgraded machine. 
Any hints on how to do that?


James

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

Re: Upgrading from 7.0 to 7.1

[James Wu]

Ricardo Jesus wrote:

James Wu wrote:

Hi all,

I'm brand new to the list so forgive me if this has been answered. I 
tried searching the archives and tried googling and didn't come up 
with any results.


I've been wanting to play with setfib multi-routing tables in 7.1, 
however, we have a bunch of 7.0 machines. I thought I'd take a test 
machine and upgrade it to 7.1. Everything went smoothly at first. I 
compiled a custom 7.1 kernel and installed it just fine. Afterwards, 
I  ran:


freebsd-update fetch
freebsd-update install
to upgrade to the latest 7.0

then:
freebsd-update upgrade -r 7.1-RELEASE
freebsd-update install -r 7.1-RELEASE
freebsd-update fetch
to upgrade to 7.1

now when I do a
uname -a,
I get FreeBSD 7.1-RELEASE-p3 which looks right to me

The problem I'm running into though is that the setfib binary doesn't 
seem to been added during the upgrade as I don't see it anywhere. I 
took a fresh install of 7.1 and do see it /usr/sbin/, but it's not 
there for the upgraded version of 7.1.
I guess at this point, I would like to do a reinstall of the sbin 
folder if it is possible or somehow get a clean copy of the 
/usr/sbin/ folder into my upgraded machine. Any hints on how to do that?


James

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


The problem is you are mixing custom kernels with freebsd-update. 
freebsd-update only works for binary updates (kernel + userland).


So either stick will freebsd-update or use csup and compile custom 
kernel and world.


I should probably clarify what I meant by custom kernel. It's the 7.1 
kernel with a patch for a driver that the hardware needs. Otherwise, it 
is the vanilla 7.1 kernel.


I just tried to do a freebsd-update rollback and then did a 
freebsd-update fetch again.

This is what I get:

The following files will be updated as part of updating to 7.1-RELEASE-p4:
/usr/bin/dig
/usr/bin/host
/usr/bin/nslookup
/usr/bin/nsupdate
/usr/bin/openssl
/usr/lib/libssl.a
/usr/lib/libssl.so.5
/usr/lib/libssl_p.a
/usr/libexec/lukemftpd
/usr/libexec/telnetd
/usr/sbin/dnssec-keygen
/usr/sbin/dnssec-signzone
/usr/sbin/lwresd
/usr/sbin/named
/usr/sbin/named-checkconf
/usr/sbin/named-checkzone
/usr/sbin/named-compilezone
/usr/sbin/ntpd
/usr/sbin/rndc-confgen
/usr/src/contrib/lukemftpd/src/ftpd.c
/usr/src/contrib/telnet/telnetd/sys_term.c
/usr/src/sys/conf/newvers.sh
/usr/src/sys/kern/kern_environment.c
/usr/src/sys/kern/kern_time.c

It seems to be updating the various binaries in /usr/sbin just fine. 
However, there is no reference to setfib.

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

FreeBSD 7.1-Stable only support 16 CPUs !?

[James Chang]

Dear all,

Does any ever try FreeBSD 7.1-stable on box that has more than 16 CPU?

I got a HP ProLiant DL 785 G5 with 32 core (Quad-Core AMD Opteron(tm)
Processor 8356 (2300.10-MHz K8-class CPU) and 256G memory.
When I boot this machine, it could detect 32 core, but only 16 core
could be uesd!?

What should I do to get FreeBSD 7.1-stable work with 32 core?
Or, FreeBSD 7.1 only support 16 Core Max ?


Best Regards!


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

Re: 7.x and multiple IPs in jails

[James Gritton]

Bjoern A. Zeeb wrote:

The plan as the status report will say is to get this in, merge it to
stable/7 before 7.2  and keep it in 8.

8 will also have vimages and ideally I'd like to see this entire jail
IP hacks be gone for 9, when vimage will provide the infrastructure,
etc.  This means that 8 would be the transition period. But that's
just me and my ideas - we'll see how it'll go.


I'm not convinced vimage is the only kind of network virtualization we 
want to give the option of.  The IP addresses assigned to jails seems a 
lighter weight alternative, and allows some things that vimage doesn't 
do easily, such as system processes that listen on the virtual addresses 
for some services, leaving the jail to handle others.


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

Re: FreeBSD 6.3 deadlock (vm_map?) with DDB output

[James Gritton]

John Baldwin wrote:

On Thursday 19 June 2008 11:57:51 am James Gritton wrote:
  

John Baldwin wrote:


On Sunday 15 June 2008 07:23:19 am Stef Walter wrote:
  
  

I've been trying to track down a deadlock on some newish production
servers running FreeBSD 6.3-RELEASE-p2. The deadlock occurs on a
specific (although mundane) hardware configuration, and each of several
servers running this hardware deadlock about once per week.

Although I suspect that this is not hardware related, from a (naive)
perusal of the attached stack traces.

Forgive me if my interpretation of this is all wrong, but I'm pretty
desperate for help. So here's my basic understanding of the deadlock:

These processes seem to be waiting on the page queue mutex:
 sendmail (in vm_mmap  vm_map_find  vm_map_insert  vm_map_pmap_enter)
 bsnmpd (in malloc, uma_large_malloc  page_alloc  kmem_malloc)
 httpd (in trap  trap_pfault  vm_fault)
 [g_up] (in g_vfs_done  bufdone)

The page queue mutex is held by rsync process:
 rsync (in trap  trap_pfault  vm_fault  pmap_enter)

Rsync kernel process (in pmap_enter) was interrupted while holding the
page queue lock?


Giant is enabled in loader.conf due to the needs of the pf firewall when
dealing with user credentials lookups. I do not believe that Giant plays
into this deadlock. Kernel config attached.

Any and all help or info is welcome. Thanks in advance.



Try this change:

jhb 2007-10-27 22:07:40 UTC

  FreeBSD src repository

  Modified files:
sys/kern sched_4bsd.c
  Log:
  Change the roundrobin implementation in the 4BSD scheduler to trigger a
  userland preemption directly from hardclock() via sched_clock() when a
  thread uses up a full quantum instead of using a periodic timeout to 
  

cause
  

  a userland preemption every so often.  This fixes a potential deadlock
  when IPI_PREEMPTION isn't enabled where softclock blocks on a lock held
  by a thread pinned or bound to another CPU.  The current thread on that
  CPU will never be preempted while softclock is blocked.

  Note that ULE already drives its round-robin userland preemption from
  sched_clock() as well and always enables IPI_PREEMPT.

  MFC after:  1 week

  Revision  ChangesPath
  1.108 +8 -29 src/sys/kern/sched_4bsd.c

We use it at work on 6.x.  W/o this fix, round-robin stops working on 4BSD 
when softclock() (swi4: clock) blocks on a lock like Giant.
  
  
I've been seeing similar troubles on 6.2 and I'll have to give this a 
try as we upgrade to 6.3.  I notice MFC after: 1 week in the log; it's 
been a week - any chance of seeing this fix rolled into 6.x?



If people confirm it fixes issues I will MFC it.  There was some pushback when 
I first committed it so I waited on the MFC.


I can confirm that on 6.3 I can recreate the deadlock without the patch, 
and can't recreate it with the patch.

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

Re: FreeBSD 6.3 deadlock (vm_map?) with DDB output

[James Gritton]

John Baldwin wrote:

On Sunday 15 June 2008 07:23:19 am Stef Walter wrote:
  

I've been trying to track down a deadlock on some newish production
servers running FreeBSD 6.3-RELEASE-p2. The deadlock occurs on a
specific (although mundane) hardware configuration, and each of several
servers running this hardware deadlock about once per week.

Although I suspect that this is not hardware related, from a (naive)
perusal of the attached stack traces.

Forgive me if my interpretation of this is all wrong, but I'm pretty
desperate for help. So here's my basic understanding of the deadlock:

These processes seem to be waiting on the page queue mutex:
 sendmail (in vm_mmap  vm_map_find  vm_map_insert  vm_map_pmap_enter)
 bsnmpd (in malloc, uma_large_malloc  page_alloc  kmem_malloc)
 httpd (in trap  trap_pfault  vm_fault)
 [g_up] (in g_vfs_done  bufdone)

The page queue mutex is held by rsync process:
 rsync (in trap  trap_pfault  vm_fault  pmap_enter)

Rsync kernel process (in pmap_enter) was interrupted while holding the
page queue lock?


Giant is enabled in loader.conf due to the needs of the pf firewall when
dealing with user credentials lookups. I do not believe that Giant plays
into this deadlock. Kernel config attached.

Any and all help or info is welcome. Thanks in advance.



Try this change:

jhb 2007-10-27 22:07:40 UTC

  FreeBSD src repository

  Modified files:
sys/kern sched_4bsd.c
  Log:
  Change the roundrobin implementation in the 4BSD scheduler to trigger a
  userland preemption directly from hardclock() via sched_clock() when a
  thread uses up a full quantum instead of using a periodic timeout to cause
  a userland preemption every so often.  This fixes a potential deadlock
  when IPI_PREEMPTION isn't enabled where softclock blocks on a lock held
  by a thread pinned or bound to another CPU.  The current thread on that
  CPU will never be preempted while softclock is blocked.

  Note that ULE already drives its round-robin userland preemption from
  sched_clock() as well and always enables IPI_PREEMPT.

  MFC after:  1 week

  Revision  ChangesPath
  1.108 +8 -29 src/sys/kern/sched_4bsd.c

We use it at work on 6.x.  W/o this fix, round-robin stops working on 4BSD 
when softclock() (swi4: clock) blocks on a lock like Giant.
  


I've been seeing similar troubles on 6.2 and I'll have to give this a 
try as we upgrade to 6.3.  I notice MFC after: 1 week in the log; it's 
been a week - any chance of seeing this fix rolled into 6.x?


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

Re: BTX loader hangs after version info

[James Seward]

`On Fri, May 23, 2008 at 11:11 PM, John Baldwin [EMAIL PROTECTED] wrote:
 [patch]

I have not yet tried this patch, but here is my progress so far:

* Rolling back to 7.0-RELEASE made it worse - now after choosing
FreeBSD from grub the machine would immediately reboot.
* I booted with the CD again and came forward to RELENG_7. This still
caused an immediate reboot.
* I booted with the CD and replaced grub with boot0cfg -B (bsdlabel,
which I tried earlier, had no effect). This fixed it, mostly.

My desktop now boots fine and completes normal startup. It even starts
X. However, from the moment I press F1 to choose FreeBSD to the moment
it's done booting, all I see on the screen is BTX loader 1.00 BTX
version is 1.02 and the cursor blinking below it. My only clues that
it's booting at the time are disk activity, and the cursor changing
from a flashing underline to a solid block (which it always has as the
kernel proper takes over).

The next thing I see is FreeBSD/i386 (hostname.goes.here) (ttyv0). I
have also noticed that I don't get any output when I restart - no rc.d
scripts telling me things are stopping, no vnodes syncing, nothing.
It's apparently happening though, as everything is
starting/stopping/umounting correctly.

I don't see that I have anything configured to boot to serial rather
than the console, but is there anything I can do/check to make sure
this definitely isn't happening? Unfortunately, putting a cable on the
serial port is not an option as I currently do not own one suitable :)

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

Re: BTX loader hangs after version info

[James Seward]

On Fri, May 23, 2008 at 1:29 PM, John Baldwin [EMAIL PROTECTED] wrote:
 If you update boot2 and it breaks you can't fix that w/o booting off of some
 other media such as a CD.

This is where I'm at anyway :)

Oh, I forgot to mention I'm booting with grub (which then hands over
to BTX if I choose my FreeBSD option). I guess I should try getting
rid of that temporarily.

Jeremy, I do have a couple of lines in loader.conf but off hand I
can't remember what precisely. I think it's a DMA hint, and disabling
AGP (a solution I think sos@ came up with for problem I had some time
during 6.2's release cycle). Unfortunately I was busy last night so
couldn't try anything further, but I should be able to tonight and
over the weekend.

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

BTX loader hangs after version info

[James Seward]

Hello,

Two days ago I csup'd my desktop at home, which was running RELENG_7
from about 7.0-RELEASE time, to bring it up-to-date (still on
RELENG_7). I followed my usual buildkernel/world procedure (the usual
one) which has worked fine all the way since 5.x. After installing
kernel and restarting in single user, it was working fine. However,
following installworld it will not boot.

It stops immediately after BTX loader 1.00 BTX version 1.02, but
with the cursor on the line *above* the first B. Nothing futher
happens, but the system responds to Ctrl-Alt-Del.

I have managed to start it using the install CD and csup'd back to a
version just before the commit to BTX that moved it to 1.02 (March
18th, I think). However, that version too hangs after BTX loader 1.00
BTX version 1.01.

My desktop is currently building RELENG_7_0 to see if that will work,
but I won't know that until later as I'm at work and it is at home :)

The install CD (BTX 1.00/1.01) boots fine. Nothing else changed on my
system between the last successful boot and the unsuccessful one.

Any suggestions/advice for what I can try next, or what I can do to
help the troubleshooting process?

My desktop is an Athlon64 but I am using i386, on an Asus A8V-E Deluxe board.

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

Re: BTX loader hangs after version info

[James Seward]

On Thu, May 22, 2008 at 1:24 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote:
 http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues

My problem doesn't match the description of screen continually
scrolls registers or dumps registers then reboots; it just freezes.

While looking at the code for btx/btxldr I did notice a debug knob in
the Makefile; should I turn this on? (And do I have to rebuild all of
world to encourage it to update BTX? Presumably I can build/install a
subset of it to save time?)

 After installworld, did you happen to use bsdlabel -B?

No, my procedure was: make buildkernel buildworld, make installkernel,
reboot (to single user), mergemaster -p, make installworld,
mergemaster (installed everything but passwd/group), reboot. This is
the point where it broke :)

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

Re: Suspend/resume on IBM X31

[James Butler]

On Mon, May 19, 2008 at 10:24 PM, James Butler
[EMAIL PROTECTED] wrote:
 Greetings

 I am having trouble with suspend/resume on my Thinkpad X31, running
 7.0-STABLE as of April 23. Any help would be appreciated.

 First problem: When I run acpiconf -s3 from mulituser mode, the
 system suspends immediately, without executing /etc/rc.suspend (which
 has mode 755); then on resume, I get a panic.
[...]

I just discovered:
http://lists.freebsd.org/pipermail/freebsd-acpi/2008-April/004806.html
which fixes the problem for me.

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

Re: Suspend/resume on IBM X31

[James Butler]

On Mon, May 19, 2008 at 11:15 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote:
 On Mon, May 19, 2008 at 10:24:43PM +1200, James Butler wrote:
 Second problem: When the system panics, I don't get a dump (or
 textdump for that matter, when I turn them on); in the boot messages,
 I see kernel dumps on /dev/ad0s2b and then later (from memory),
 Looking for core dumps on /dev/ad0s2b savecore: no dumps found
 or somesuch. I know from trying out textdumps that dumping works in
 other circumstances.

 This is a known problem, but is difficult to solve (chicken-and-egg
 situation).  There's an open PR for it.

 http://www.freebsd.org/cgi/query-pr.cgi?pr=conf/118255

 --
 | Jeremy Chadwickjdc at parodius.com |
 | Parodius Networking   http://www.parodius.com/ |
 | UNIX Systems Administrator  Mountain View, CA, USA |
 | Making life hard for others since 1977.  PGP: 4BD6C0CB |



Thanks for the pointer, but this doesn't seem to exactly match my
situation. I can boot to single-user after a panic, no swap, and
savecore still tells me that there's no dump present; conversely (I
should have made this clearer) kernel dumps work for me when the panic
is triggered in other ways (eg. by switching vt's too quickly from X -
don't know why).

Maybe tomorrow I'll try manually transcribing some DDB output, but for
me the more interesting problem is why /etc/rc.suspend is not
executed. I haven't even thought about /etc/rc.resume yet :-)

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

Suspend/resume on IBM X31

[James Butler]

Greetings

I am having trouble with suspend/resume on my Thinkpad X31, running
7.0-STABLE as of April 23. Any help would be appreciated.

First problem: When I run acpiconf -s3 from mulituser mode, the
system suspends immediately, without executing /etc/rc.suspend (which
has mode 755); then on resume, I get a panic.

Second problem: When the system panics, I don't get a dump (or
textdump for that matter, when I turn them on); in the boot messages,
I see kernel dumps on /dev/ad0s2b and then later (from memory),
Looking for core dumps on /dev/ad0s2b savecore: no dumps found
or somesuch. I know from trying out textdumps that dumping works in
other circumstances.

These issues together make it hard to debug further, but I did a few
tests in single-user mode. First, with no services running, acpiconf
-s3 seems to work OK (although /etc/rc.suspend is still not executed)
- I can suspend and resume and the machine keeps working. See:
http://homepages.ihug.co.nz/~sweetnavelorange/dmesg.1
for my dmesg after one successful cycle - there are a few warnings to
do with firewire. However if I start powerd before suspending, I get
the following extra kernel messages (hand transcribed):
acpi_ec0: warning: EC done before starting event wait
subdisk0: detached
ad0: detached
and any subsequent attempts to access the disk (eg. dmesg/some/file,
kldstat) produce errors of the form:
g_vfs_done(): ad0s2e[READ(offset=8478572544, length=16384)] error=6
and eventually another panic.

Of course if /etc/rc.suspend worked, I could disable powerd before
suspending :-/. If anyone has any ideas, I'd love to hear them, and
I'll provide any more info that's needed. Other than this, I'm really
pleased with FreeBSD 7 - thanks all!

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

Re: ZFS Bittorent - Hang?

[James Snyder]

No problem.  I've filed a PR:
http://www.freebsd.org/cgi/query-pr.cgi?pr=122888

This doesn't seem to be a volume-of-data thing, not sure if it is
related to using raidz or not.  I don't have another spare disk in the
machine I tested on to pare things down.

Otherwise, seems to be pretty stable.  I've been knocking on it for
some time with no other troubles.  Prefetch seems to me to be a little
less than ready for prime-time.  I seem to recall on a 32-bit machine
as well that pkg_delete would run terribly slowly with prefetch on,
and things got better when I re-enabled the zil and turned prefetch
off.  Not sure whether the zil just helped a lot there or if the
problem was prefetch.

I'm using ZFS on my Mac OS X laptop as well, that's been pretty good
too.  Latest build (111 on zfs.macosforge.org) has fixed mmap
coherency, and a bunch of other things.

On Fri, Apr 18, 2008 at 1:03 PM, Claus Guttesen [EMAIL PROTECTED] wrote:
   OK.  I've been able to reproduce the issue.
  
Conditions:
- Stock shipped kernel and modules from RELENG 7.0
  
loader.conf settings:
- zfs prefetch enabled
- zfs zil disabled
- vm.kmem_size_max=1073741824
- vm.kmem_size=1073741824
  
AMD64 on Core 2 Duo w/ 4 GB RAM
  
raidz across 4 disks, using root on zfs (also experienced this hang with 
 zfs
just on /usr)
  
How To Reproduce
- install transmission-daemon, run transmission-daemon (it will daemonize,
automatically backgrounding)
- grab a torrent, such as KNOPPIX (http://torrent.unix-ag.uni-kl.de/)
- transmission-remote -a torrentfile (add the torrent)
- transmission-remote -s all  (start all the torrents)
  
wait hours to a day or so with whatever you want logging things running 
 and
active since anything that hits disk after the hang will get hung as well
  
I've just done this twice.  It doesn't seem to happen with zil enabled and
prefetch off.
  
Expected Behavior
No hang.

  Thank you for spending time on this. I'm getting some jbod-storage in
  a few weeks and will spend some time using various block-sizes and
  share partitions across nfs. I'm somewhat confident that zfs on
  FreeBSD will work fine but Solaris is (of course) also an option. This
  will be approx. 7 TB to begin with and growing upwards to some two
  digit TB's.

  What is the largest storage zfs on FreeBSD has been used on? I tried
  it for some month on 8 TB.

  --


 regards
  Claus

  When lenity and cruelty play for a kingdom,
  the gentlest gamester is the soonest winner.

  Shakespeare




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

Re: ZFS Bittorent - Hang?

[James Snyder]

Thanks for the followup.  I have not yet gotten a reliable test case
to reproduce the problem. I've done a number of tests with the zil
and/or prefetch on with no hangs.  I will be collecting some more data
later this week.

If anyone knows a source of consistently slow but large torrents (I
suppose I could artificially limit bandwidth, or connection states at
my router which is running pfSense), that might help for testing.  The
process that triggered things before was about a gigabyte or two but
took around 12 hours to complete.

Here's the overall group of variables I'm experimenting with.

Stock Kernel vs Recompiled Kerel w/ ULE (stock sources otherwise)
ZIL on and off
prefetch on and off

Should I add or remove anything?  I have no idea if ULE may or may not
play a role here, but my original failing condition had the zil off,
prefetch on, ule for the scheduler.

I also had:
vm.kmem_size_max=1073741824 (loader.conf)
vm.kmem_size=1073741824 (loader.conf)

Any recommendations on what to leave running to record what zfs is
getting hung on, beside watching states?  Since I can fire up things
prior to the hang, and they'll keep running if disk isn't hit, I could
leave some diagnostics running to display what's blowing up.

Thanks!

On Tue, Apr 15, 2008 at 4:44 AM, Claus Guttesen [EMAIL PROTECTED] wrote:
http://wiki.freebsd.org/ZFSKnownProblems

 This looks like #1.

  
Hmm.. I don't think there's a large amount of transfer between UFS  ZFS,
unless the client is using /tmp a lot, it should all be on ZFS.
  
I noted #4 as well, and therefore tried disabling prefetch.  I can't seem 
 to
get it to hang now.  I queued up a bunch of different torrents (full 
 freebsd
7 amd64  i386, some other random things), and they all completed without
leading to me being locked out or any processes waiting on zfs.
  
I'll try some testing this weekend to see if I can reproduce the lock-up
again by re-enabling prefetch.  Perhaps we can confirm that issue?  
 Should I
bother with trying to run CURRENT or should any testing I do be done with
STABLE.  I don't see any indication that there might be experimental 
 patches
for dealing with this or related issues.

  Were you able to reproduce the lock-up by re-enabling prefetch?

  --
  regards
  Claus

  When lenity and cruelty play for a kingdom,
  the gentlest gamester is the soonest winner.

  Shakespeare




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

Re: kernel backup on 7.0

[James López (BLuEGoD)]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Ivan Voras escribió:
| James López (BLuEGoD) wrote:
| Hello,
|
| I have FreeBSD 7.0 on my server but due to troubles with sendfile (I
| don't know why, but when I run a configure script checking for that
| function it shows a segmentation fault and I can't make my web server
| run well), also because of some accidentally I will reinstall freebsd.
|
| So I would like to know if I can make some kind of backup to the kernel
| because it was modified and recompiled, so perhaps if I backup the boot
| files wouldn't need to compile it again... How can I do that? is
| possible? Its a matter of time.. I will have a short time to do the
| reinstall :S
|
| If I understand you correctly, you're asking if you can have a backup
| kernel when you build a new one?
|

Not exactly.. What I mean is that I want to reinstall FreeBSD due to
some accidentally deleted files and a behavior on sendfile :S
So I would like to know if I can backup /boot and the overwrite it once
I have freebsd installed again...

| Yes, and it's the default behaviour. Every time you do a make
| installkernel (it's integrated into make kernel), the old kernel gets
| saved in /boot/kernel.old with all its modules. In addition to that, you
| can have an arbitrary number of different kernels in the root/boot file
| system. To switch between the kernels, escape to loader prompt on the
| boot menu, type help to see available commands (you'll probably use
| unload, load and boot, in this order).
|
|


- --
~ ___  _ ___  ___   ___ _ _  ___
~ | . | |  _ _ | __/  _ ___ | . \   | \ | ___|_ _|
~ | . \| |_| | || _ |_/\/ . \| | | _ |   |/ ._| |
~ |___/|___|___||___/\___/|___/_|_\_|\___.|_|
~ -- BLuEGoD (James LÛpez) [EMAIL PROTECTED] ---
~ -- Public Key: Search 'BLuEGoD' on www.keyserver.net
~ --- WwW.BLuEGoD.NeT 

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFHz+ODACIwOm/T2YIRAgDHAKCmsERTlXYCWnGNLlEzay4UFEvFvgCfehvt
eimPit/5o9QyLn+ooVFQcwI=
=4nm0
-END PGP SIGNATURE-
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: kernel backup on 7.0

[James López (BLuEGoD)]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Ivan Voras escribió:
| Jeremy Chadwick wrote:
| On Thu, Mar 06, 2008 at 01:58:08PM +0100, Ivan Voras wrote:
| James López (BLuEGoD) wrote:
|
| Not exactly.. What I mean is that I want to reinstall FreeBSD due to
| some accidentally deleted files and a behavior on sendfile :S
| So I would like to know if I can backup /boot and the overwrite it once
| I have freebsd installed again...
| Yes. If you don't change FreeBSD versions or hardware, this will work.

In my case I have FreeBSD 7.0 and I will reinstall the same version :)

Thanks for all :)

| Clarification: it _might_ work.
|
| You need to keep in mind that the kernel/modules he's backing up will
| very likely *not* match all the binaries he has on his disks, library
| calls, possibly system calls, etc. etc...  This is why building world
| includes both all the binaries *as well* as the kernel.
|
| I agree, but I think this is covered by not changing FreeBSD versions :)
|
| The reason I point this out is, when certain things in kernel-land
| change which certain programs rely upon (but haven't been recompiled to
| be aware of that change), odd things can happen.  The most famous of
| the bunch is when top(1) or ps(1) start failing in bizarre ways.
|
| Thus, my point: it *probably* will work, but DO NOT assume that it will.
|
| To be even more precise, it will probably (with very high certainty)
| work for two FreeBSD versions x1.y1 and x2.y2 if x1 == x2 and y1 = y2.
| It will probably also work for any combination of y1 and y2 as long as
| x1 == x2. It will probably fail if x1 != x2.
|


- --
~ ___  _ ___  ___   ___ _ _  ___
~ | . | |  _ _ | __/  _ ___ | . \   | \ | ___|_ _|
~ | . \| |_| | || _ |_/\/ . \| | | _ |   |/ ._| |
~ |___/|___|___||___/\___/|___/_|_\_|\___.|_|
~ -- BLuEGoD (James LÛpez) [EMAIL PROTECTED] ---
~ -- Public Key: Search 'BLuEGoD' on www.keyserver.net
~ --- WwW.BLuEGoD.NeT 

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFHz/hGACIwOm/T2YIRAvqNAKCkur2HdtKyuoilU9Q3i215H1IeuACePOdn
+coxVhSAPeKfsnqi3rIQHow=
=QmU2
-END PGP SIGNATURE-
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

kernel backup on 7.0

[James López (BLuEGoD)]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello,

I have FreeBSD 7.0 on my server but due to troubles with sendfile (I
don't know why, but when I run a configure script checking for that
function it shows a segmentation fault and I can't make my web server
run well), also because of some accidentally I will reinstall freebsd.

So I would like to know if I can make some kind of backup to the kernel
because it was modified and recompiled, so perhaps if I backup the boot
files wouldn't need to compile it again... How can I do that? is
possible? Its a matter of time.. I will have a short time to do the
reinstall :S
Thanks!

- --
~ ___  _ ___  ___   ___ _ _  ___
~ | . | |  _ _ | __/  _ ___ | . \   | \ | ___|_ _|
~ | . \| |_| | || _ |_/\/ . \| | | _ |   |/ ._| |
~ |___/|___|___||___/\___/|___/_|_\_|\___.|_|
~ -- BLuEGoD (James LÛpez) [EMAIL PROTECTED] ---
~ -- Public Key: Search 'BLuEGoD' on www.keyserver.net
~ --- WwW.BLuEGoD.NeT 


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFHzmxrACIwOm/T2YIRAnhBAKCSDZS4yBYNoxwf1nuPfm5Pyn5NpACgoK4l
bF1t7DiS0IJiT7gjNq6BPgM=
=f6DH
-END PGP SIGNATURE-
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portupgrade, recommended by 7 release notes, breaks perl

[James]

On Sat, 2008-03-01 at 14:53 +0100, Kris Kennaway wrote:
 Steven Hartland wrote:
  Seems portupgrade can easily break the perl install.
  
  How? Well there are various modules which can be updated
  but are also part of the base perl and are hence required.
  
  A good example of this is ExtUtils::MakeMaker. If you
  uninstall any version of this port your done for, as
  trying to build it requires ExtUtils::Command which in
  turn requires ExtUtils::MakeMaker which was just deleted.
  
  This circular dependency would not be an issue if the
  uninstall somehow knew that the files where required
  by perl, and hence didn't break the base port ( perl )
  by removing them.
 
 I think something is not quite right in your analysis, because perl does 
 not depend on any external perl modules (it cannot, by definition).
 
 Kris
 
Just to chime in, I don't have MakeMaker installed, but I *do* have perl
installed.

[EMAIL PROTECTED] ~]$ pkg_info | grep -i perl
p5-Archive-Tar-1.38 Perl module for creation and manipulation of tar
files
p5-Authen-SASL-2.10_1 Perl5 module for SASL authentication
p5-Compress-Zlib-2.008 Perl5 interface to zlib compression library
p5-Date-Manip-5.44  Perl5 module containing date manipulation routines
p5-Digest-HMAC-1.01 Perl5 interface to HMAC Message-Digest Algorithms
p5-Digest-MD5-2.36  Perl5 interface to the MD5 algorithm
p5-Digest-SHA1-2.11 Perl interface to the SHA-1 Algorithm
p5-Error-0.17009Perl module to provide Error/exception support for
perl: Er
p5-ExtUtils-CBuilder-0.22 Compile and link C code for Perl modules
p5-ExtUtils-ParseXS-2.19 Converts Perl XS code into C code
p5-GSSAPI-0.25  Perl extension providing access to the GSSAPIv2
library
p5-HTML-Parser-3.56 Perl5 module for parsing HTML documents
p5-IO-Compress-Zlib-2.008 Perl5 interface for reading and writing of
(g)zip files
p5-IO-Socket-INET6-2.52 Perl module with object interface to AF_INET6
domain socket
p5-IO-Socket-SSL-1.13 Perl5 interface to SSL sockets
p5-IO-String-1.08   Simplified Perl5 module to handle I/O on in-core
strings
p5-IO-stringy-2.110 Perl5 module for using IO handles with non-file
objects
p5-MIME-Base64-3.07 Perl5 module for Base64 and Quoted-Printable
encodings
p5-Mail-Tools-1.77  Perl5 modules for dealing with Internet e-mail
messages
p5-Module-Build-0.28.08 Build and install Perl modules
p5-Net-1.22,1   Perl5 modules to access and use network protocols
p5-Net-CIDR-Lite-0.20 Perl extension for merging IPv4 or IPv6 CIDR
addresses
p5-Net-DBus-0.33.5  Perl extension for the DBus message system
p5-Net-DNS-0.62 Perl5 interface to the DNS resolver, and dynamic
updates
p5-Net-IP-1.25  Perl extension for manipulating IPv4/IPv6 addresses
p5-Net-SSLeay-1.30_1 Perl5 interface to SSL
p5-Parse-Syslog-1.10 Perl5 routines that present a simple interface to
parse sys
p5-PathTools-3.2701 A Perl module for portably manipulating file
specifications
p5-SGMLSpm-1.03 Perl module for postprocessing the output from sgmls
and ns
p5-Scalar-List-Utils-1.19,1 Perl subroutines that would be nice to have
in the perl cor
p5-Spiffy-0.30  Spiffy Perl Interface Framework For You
p5-Test-Harness-3.09 Run perl standard test scripts with statistics
p5-Test-Simple-0.74 Basic utilities for writing tests in perl
p5-Text-Iconv-1.7   Perl interface to iconv() codeset conversion
function
p5-Tie-IxHash-1.21  Perl module implementing ordered in-memory
associative arra
p5-Time-HiRes-1.9711,1 A perl5 module implementing High resolution time,
sleep, an
p5-URI-1.35 Perl5 interface to Uniform Resource Identifier (URI)
refere
p5-XML-Grove-0.46.a Perl-style XML objects
p5-XML-Handler-YAWriter-0.23 Yet another Perl SAX XML Writer
p5-XML-Parser-2.36  Perl extension interface to James Clark's XML
parser, expat
p5-YAML-0.66YAML implementation in Perl
p5-libwww-5.805 Perl5 library for WWW access
p5-libxml-0.08  Collection of Perl5 modules for working with XML
pcre-7.6Perl Compatible Regular Expressions library
perl-5.8.8_1Practical Extraction and Report Language
[EMAIL PROTECTED] ~]$ 


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

RE:Can't build graphviz

[Jimmie James]

lgj:/usr/ports/graphics/graphviz# make build
/usr/ports/Mk/bsd.gnome.mk, line 643: Malformed conditional 
(${_USE_GNOME_ALL:Mpango}==)
/usr/ports/Mk/bsd.port.mk, line 6147: if-less endif
make: fatal errors encountered -- cannot continue


Copy your /var/db/ports/graphviz/options to somewhere safe, cd 
/usr/ports/graphviz  make rmconfig (as mentioned on ports- mailing list)


That was worked for a number of people.

HTH

--jimmie

--
If you can't beat your computer at chess, try kickboxing.
--- --- ---
Solving Today's Problems Tomorrow
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

/dev/ppi Files aren't there! Parallel port problems.

[James Sarasin]

Hello there. I'm interesting in developing with the usermode ppi interface.
How ever on a fresh install of the latest FreeBSD Iso images I don't have
any ppi devices in /dev. From what I can tell it isn't using the correct
settings for the parallel port.
I have made sure that my parallel port is enabled in BIOS.

Thanks
James Sarasin


  My system information
Toshiba TE2000 Laptop

# uname -a
FreeBSD .ab.hsia.telus.net 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12
11:05:30 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP
i386

  A verbous boot dump has the following in it:
ppc0: parallel port not found.
ppc0: parallel port not found.
unknown: status reg test failed ff
unknown: status reg test failed ff
unknown: status reg test failed ff
unknown: status reg test failed ff
unknown: status reg test failed ff
unknown: status reg test failed ff

ppc0: parallel port not found.
ppc0: Parallel port failed to probe at irq 7 on isa0


  When I try to load the ppi module after the systems running
# kldload ppi
kldload: can't load ppi: File exists

  On system startup it says this
# grep ^ppc /var/run/dmesg.boot
ppc0: parallel port not found.


 When I call dmidecode  i get the following relavent to the parallel
port:
Handle 0x0016, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator:
Internal Connector Type: None
External Reference Designator: PARALLEL PORT
External Connector Type: DB-25 female
Port Type: Parallel Port ECP
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: impossible rc.d ordering problem with stf and pf ?

[James Long]

On Wed, Jan 31, 2007 at 09:30:56AM +0200, Stefan Lambrev wrote:
 Hello,
 
 pass out on (stf0) inet6 from any to any keep state
 
 
 Just for my edification, what is the point of keep state on an
 any-to-any rule?
 
   
 imagine that you have only 2 rules -
 block in on $if all
 pass out on $if from any to any keep state
 
 - with keep state you have internet, without it you do not have ;)

Thank you.

I must read more closely.  I did not grok the out.


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

Re: impossible rc.d ordering problem with stf and pf ?

[James Long]

 Date: Mon, 29 Jan 2007 12:02:52 +
 From: Pete French [EMAIL PROTECTED]
 Subject: Re: impossible rc.d ordering problem with stf and pf ?
 To: freebsd-stable@freebsd.org, [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
 Message-ID: [EMAIL PROTECTED]
 
  1) You use the interface name as address w/o dynamic lookup.
  i.e. ... from stf0 ...
 
 Yes, thats it - I hadn't come across this 'dynamic lookup' thing before 
 though, so I didn't realise what it was. I still cant find it in the PF
 manual, aside from a reference that you need to do it for NAT.
 
  To 1 and 2 there is a simple sollution: Don't do that then!  1 can easily=20
  be defused by adding parentheses. i.e. ... from (stf0) 
 
   pass out on (stf0) inet6 from any to any keep state

Just for my edification, what is the point of keep state on an
any-to-any rule?


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

Re: Failover-HA-Setup

[James Long]

 Date: Wed, 17 Jan 2007 13:47:37 +0100
 From: Richard [EMAIL PROTECTED]
 Subject: Failover-HA-Setup
 To: freebsd-stable@freebsd.org
 Message-ID: [EMAIL PROTECTED]
 Content-Type: text/plain
 
 Hi there!
 
 I am looking for a solution for a small problem regarding a high
 availability setup.
 I am running heartbeat on a STABLE-system, the failover works fine for
 IP-adresses and I am able to see that a
 '/usr/local/etc/rc.d/mysql-server start' statement is issued. BUT since
 the variables for mysql are not set in rc.conf (Otherwise it would be
 started at startup), it isn't starting at all.
 
 So my question: How to set those rc.conf-variables in order to start
 services in such an setup? Or is there a better solution?
 
 
 cu!
 
 Richard

export mysql_enable=YES  /usr/local/etc/rc.d/mysql-server start
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: loader freezes system during timer autoboot

[James Long]

 Date: Sun, 17 Dec 2006 13:44:05 +0100 (CET)
 From: patrick [EMAIL PROTECTED]
 Subject: loader freezes system during timer autoboot
 To: [EMAIL PROTECTED]
 Message-ID: [EMAIL PROTECTED]
 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
 
 
 Hi,
 
 I have a supermicro system which freezes during the timer before autoboot.
 It freezes most of the times.
 
 System  : Supermicro 5014C-T
  : Super P8SCi
  : P4 630 / 3.0 GHz / 2MB cache - 2 Logical CPUs
  : 2048 (2x1GB) PC2-400 ECC REGISTERED
  : Broadcom BCM5721 Dual Gigabit Ethernet
  : 3ware 3W8006-2LP Storage Controller
 
 6.2-RC2, cvsup'd 17 dec 1200 CEST running GENERIC kernel
 
 setting autoboot_delay=-1 and beastie_disable=YES in loader.conf make the 
 system most of 
 the time boot correctly, but sometimes also freezes but then directly after 
 start of the autoboot/kernel boot.
 
 I have an identical system running 6.1 without this problem.
 
 Anyone have any suggestions?

My suggestion would be to try some elementary troubleshooting.

Swap the disk arrays between the two machines, for instance.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Large msdosfs disk will not mount on RELENG_6

[James Wyatt]

On Mon, 27 Nov 2006, Brandon S. Allbery KF8NH wrote:

On Nov 27, 2006, at 1:09 , Clayton Milos wrote:
I just bought a large external hard drive for home backups (500g Western 
Digital My Book).  When I plug it in to my machine (RELENG_6 from about a 
week ago), the system sees the device just fine:


I am very suprised at all that windows would allow you to format a 500G 
drive into a single 500G FAT32 partition.


As far as I am aware windows 2000 and xp will only allow you to format up 
to a 32G dive with FAT32. Any bigger and it will force you to use NTFS. The 
other strange thing is tht you are trying to mount /dev/da0 and not 
/dev/de0s1.


How did you format this drive ?


It comes formatted FAT32.  I bought one last week as well, and tried to mount 
it to extract the included software before repartitioning.  I finally mounted 
it on an OSX box to copy the software to CDR.

[ ... ]

I had the same issue with a Fry's $99 special 320GB USB2/FW exernal HDD. 
Since I need to mount it with WinXP, Linux, and GENERIC FreeBSD, I was 
somewhat stuck. The way I got around it was to reformat it to ext2 and use 
the Win32 ext2fs driver from SourceForge.  I considered NTFS, but the 
FreeBSD support for NTFS didn't look practical to use at the time - Jy@

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

Re: Large msdosfs disk will not mount on RELENG_6

[James Wyatt]

On Mon, 27 Nov 2006, James Wyatt wrote:

On Mon, 27 Nov 2006, Brandon S. Allbery KF8NH wrote:

On Nov 27, 2006, at 1:09 , Clayton Milos wrote:
I just bought a large external hard drive for home backups (500g Western 
Digital My Book).  When I plug it in to my machine (RELENG_6 from about a 
week ago), the system sees the device just fine:


I am very suprised at all that windows would allow you to format a 500G 
drive into a single 500G FAT32 partition.


As far as I am aware windows 2000 and xp will only allow you to format up 
to a 32G dive with FAT32. Any bigger and it will force you to use NTFS. 
The other strange thing is tht you are trying to mount /dev/da0 and not 
/dev/de0s1.


How did you format this drive ?


It comes formatted FAT32.  I bought one last week as well, and tried to 
mount it to extract the included software before repartitioning.  I finally 
mounted it on an OSX box to copy the software to CDR.

[ ... ]

I had the same issue with a Fry's $99 special 320GB USB2/FW exernal HDD. 
Since I need to mount it with WinXP, Linux, and GENERIC FreeBSD, I was 
somewhat stuck. The way I got around it was to reformat it to ext2 and use 
the Win32 ext2fs driver from SourceForge.  I considered NTFS, but the FreeBSD 
support for NTFS didn't look practical to use at the time - Jy@


Sorry to reply to myself, but I forgot to mention that if you're doing 
tar/zip backups, then FAT32 may be worth the extra memory.  If you are 
doing file backups, then ext2 will better preserve the metadata you want 
like UID, GID, permissions, etc... as well as avoiding the waste of small 
files stored in mega-clusters.  The ext2fs WinXP driver defaults to having 
the write-cache disabled, so it's not a high-performance approach - Jy@

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

Kernel crashes in current 6.2-PRERELEASE

[James Housley]

My router running FBSD 6.1-RELEASE, 6.1-STABLE and now 6.2-PRERELEASE  
periodically would reboot.  It would always have the same basic  
information in the kernel panic.  I have finally gotten it setup for  
a debug kernel and a place to store the crash.


Here is the information, what are my next steps.

Jim

Script started on Thu Oct 26 14:28:46 2006
router# kgdb kernel.debug /var/crash/vmcore.0
kgdb: kvm_nlist(_stopped_cpus):
kgdb: kvm_nlist(_stoppcbs):
[GDB will not be able to debug user-mode threads: /usr/lib/ 
libthread_db.so: Undefined symbol ps_pglobal_lookup]

GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and  
you are
welcome to change it and/or distribute copies of it under certain  
conditions.

Type show copying to see the conditions.
There is absolutely no warranty for GDB.  Type show warranty for  
details.

This GDB was configured as i386-marcel-freebsd.

Unread portion of the kernel message buffer:
kernel trap 12 with interrupts disabled


Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0x1104768
fault code  = supervisor read, page not present
instruction pointer = 0x20:0xc04e50a1
stack pointer   = 0x28:0xcc680b08
frame pointer   = 0x28:0xcc680b0c
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= resume, IOPL = 0
current process = 3690 (ifconfig)
trap number = 12
panic: page fault
Uptime: 5h36m14s
Dumping 126 MB (2 chunks)
  chunk 0: 1MB (160 pages) ... ok
  chunk 1: 126MB (32240 pages) 110 94 78 62 46 30 14

#0  doadump () at pcpu.h:165
165 __asm __volatile(movl %%fs:0,%0 : =r (td));
(kgdb) list *0xc04e50a1
0xc04e50a1 is in turnstile_setowner (/usr/src/sys/kern/ 
subr_turnstile.c:433).

428
429 mtx_assert(td_contested_lock, MA_OWNED);
430 MPASS(owner-td_proc-p_magic == P_MAGIC);
431 MPASS(ts-ts_owner == NULL);
432 ts-ts_owner = owner;
433 LIST_INSERT_HEAD(owner-td_contested, ts, ts_link);
434 }
435
436 /*
437  * Malloc a turnstile for a new thread, initialize it and  
return it.

(kgdb) bt
#0  doadump () at pcpu.h:165
#1  0xc04c4b02 in boot (howto=260) at /usr/src/sys/kern/ 
kern_shutdown.c:409

#2  0xc04c4d98 in panic (fmt=0xc06683c3 %s)
at /usr/src/sys/kern/kern_shutdown.c:565
#3  0xc0647000 in trap_fatal (frame=0xcc680ac8, eva=17844072)
at /usr/src/sys/i386/i386/trap.c:837
#4  0xc06467e2 in trap (frame=
  {tf_fs = -1060962296, tf_es = -865599448, tf_ds = -1067515864,  
tf_edi = -1067971588, tf_esi = -1050101120, tf_ebp = -865596660,  
tf_isp = -865596684, tf_ebx = -1050353088, tf_edx = -1050353088,  
tf_ecx = 17843956, tf_eax = -1050101088, tf_trapno = 12, tf_err = 0,  
tf_eip = -1068609375, tf_cs = 32, tf_eflags = 65543, tf_esp =  
-1050101120, tf_ss = -865596624})

at /usr/src/sys/i386/i386/trap.c:270
#5  0xc0635a9a in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#6  0xc04e50a1 in turnstile_setowner (ts=0xc164e240, owner=0x11046f4)
at /usr/src/sys/kern/subr_turnstile.c:432
#7  0xc04e5398 in turnstile_wait (lock=0xc0580e5c, owner=0x11046f4)
at /usr/src/sys/kern/subr_turnstile.c:591
#8  0xc04bb284 in _mtx_lock_sleep (m=0xc0580e5c, tid=3244866176, opts=0,
file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:579
#9  0xc05327df in if_delmulti (ifp=0xc0580bfc, sa=0x262beca)
at /usr/src/sys/net/if.c:2083
#10 0xc0581783 in in6_delmulti (in6m=0xc1980980)
at /usr/src/sys/netinet6/mld6.c:649
#11 0xc05731c0 in in6_ifdetach (ifp=0xc15ba400)
at /usr/src/sys/netinet6/in6_ifattach.c:806
#12 0xc05301f4 in if_detach (ifp=0xc15ba400) at /usr/src/sys/net/if.c: 
665
#13 0xc0535508 in gif_destroy (sc=0xc19a3900) at /usr/src/sys/net/ 
if_gif.c:209

#14 0xc05355ba in gif_clone_destroy (ifp=0xc168baa0)
at /usr/src/sys/net/if_gif.c:226
#15 0xc0533aca in ifc_simple_destroy (ifc=0xc06a3520, ifp=0x11046f4)
at /usr/src/sys/net/if_clone.c:478
#16 0xc0533109 in if_clone_destroy (name=0xc18e8140 gif0)
at /usr/src/sys/net/if_clone.c:172
---Type return to continue, or q return to quit---
#17 0xc0531cb8 in ifioctl (so=0xc19c52c8, cmd=2149607801,
data=0xc18e8140 gif0, td=0xc168ba80) at /usr/src/sys/net/if.c: 
1533
#18 0xc04ec9bf in soo_ioctl (fp=0xc168baa0, cmd=2149607801,  
data=0xc18e8140,

active_cred=0xc14fad00, td=0xc168ba80)
at /usr/src/sys/kern/sys_socket.c:214
#19 0xc04e7089 in ioctl (td=0xc168ba80, uap=0xcc680d04) at file.h:264
#20 0xc0647317 in syscall (frame=
  {tf_fs = 59, tf_es = 59, tf_ds = 59, tf_edi = 134571680,  
tf_esi = 1, tf_ebp = -1077942312, tf_isp = -865596060, tf_ebx =  
-1077941000, tf_edx = 134583517, tf_ecx = 0, tf_eax = 54, tf_trapno =  
12, tf_err = 2, tf_eip = 672448383, tf_cs = 51, tf_eflags = 646,  
tf_esp = -1077942340, tf_ss = 59})

at /usr/src/sys/i386/i386/trap.c:983

Re: 6.1-RELEASE: TIMEOUT - WRITE_DMA retrying

[James Seward]

On 8/16/06, Vlad [EMAIL PROTECTED] wrote:

I get this type of messages in on my FreeBSD.
ad4: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=70938623
Under steady IO load it panics, that started when we changed SATA
controller (FreeBSD detects it as SiI 3512). I've tried to switch
ports, cable, move card into a different PCI slot, disable ata dma in
/boot/loader.conf - nothing helps.


I had similar problems under 5.x and 6.x with a SI3112. My testing and
investigations back then suggested that some combinations of hardware
and the SI3112 just don't get along and I solved it by getting rid
of it.

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

Re: Sun X86 servers

[James O'Gorman]

On Sat, Jul 22, 2006 at 02:23:36PM -0400, Robert Blayzor wrote:
 I'd like to know if anyone is using the Sun X86 servers with 6.x.  If
 so, how is it preforming?  I'm looking at possibly using them in a
 diskless environment (and a couple possibly with disks)  I've read in
 the past that the disk controllers were not supported yet, I'm not sure
 if that's changed (or changing).  What about network controllers?
 
 Please contact me off-list (unless others are interested as well).

Actually I'd be quite interested to know how they perform as well. I've
been contemplating the new Ultra 20 workstation to try and learn Solaris
on (but be able to run FreeBSD as well).

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

Re: reading process memory

[James Riendeau]

How are you defining assuming right privileges?  The only way  
you're going to be able to read another processes address space is in  
the kernel.  Even a process running as root is not able to read  
another process's data.  One of the principle responsibilities of the  
OS is to manage the private memory space of each process, and I  
emphasize private.  The last thing you would want on a secure system  
is the ability of other processes to read or write to another  
process's address space.  Even a parent process should not be able to  
read a child's address space, as the fork logically duplicates their  
address space and they go their separate ways.  An attempt to read  
another processes address space should trap to the kernel and the  
kernel should kill the process immediately.  There is one exception  
to this:  you can setup a pipe or memory share between two processes,  
however, both processes have to agree to share some memory or connect  
via a pipe.  I'm not going to give you a howto via email as the  
subject usually fills a solid chapter in most OS books.


James Riendeau
MMI Computer Support Technician
1300 University Ave
Rm. 436, Dept. of MedMicro
Madison, WI  53706

Phone: (608) 262-3351
After-hours Phone: (608) 260-2696
Fax: (608) 262-8418
Email: [EMAIL PROTECTED]



On Jun 7, 2006, at 4:49 AM, Tofik Suleymanov wrote:


Hello, folks

I believe that it is possible to read contents of the memory used/ 
utilized by a process (assuming right privileges).
First i've tried to do this through procfs by reading 'mem'  
property of the given process, but no success.

Maybe there is another way of doing such things ?
Any clue would be appreciated.

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


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

Re: CPUTYPE=athlon-xp and loader

[James Long]

 Date: Sun, 16 Apr 2006 17:43:58 +0300
 From: Evren Yurtesen [EMAIL PROTECTED]
 Subject: CPUTYPE=athlon-xp and loader
 To: freebsd-stable@freebsd.org
 Message-ID: [EMAIL PROTECTED]
 
 Hello,
 
 I have a problem which I have found out from mailing lists that some 
 other people had. However there is no clear solution.
 
 The CPUTYPE=athlon-xp in make.conf breaks /boot/loader that system 
 instant reboots. I am using 6-stable and from what I can see the problem 
 goes back till about 5.3... Sometime between Oct 12-15, 2005
 
 http://archive.netbsd.se/?ml=freebsd-currenta=2004-10m=435817
 
 I wonder if this will ever be fixed or I shouldnt use CPUTYPE=athlon-xp 
 anymore on FreeBSD because of this?
 
 Thanks,
 Evren

I don't propose this as a solution, but as far as I know, the best practice 
is:

CPUTYPE?=athlon-xp


Note the question mark.

I don't know that this will solve your problem, just pointing out
the correct syntax, for whatever CPUTYPE you decide to use.

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

Re: kernel panic in 6.1 - does no one care?

[James Gallagher]

On Thu, 23 Mar 2006 22:39:56 -0600, [EMAIL PROTECTED] (Mark Linimon) wrote:
 On Thu, Mar 23, 2006 at 11:22:37PM -0500, Surer Dink wrote:
 Two days ago I reported a panic here

 (http://lists.freebsd.org/pipermail/freebsd-stable/2006-March/023748.html)
 on a freshly cvsuped releng_6 generic kernel.  I have heard no
 responses at all - does this mean I am posting in the wrong place, or
 does no one care about 6.1?
 
 Neither.  It means that the volunteers are incredibly busy testing as
 many things as they can for the simultaneous 5.5/6.1 release, and not
 everything can be gotten to.
 
 mcl
I also wonder if this would be better reported on -current rather than -stable 
as the concerned version, 6.1, is pre-release/Beta?

James

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

Re: Still can't boot on 6.0-STABLE Nov 2005 or 6.1-BETA

[James Seward]

On 3/15/06, James Seward [EMAIL PROTECTED] wrote:
 Hello folks,
 [booting problems with newer kernels]

Replying to myself in case this is of use to anyone else.

After some tinkering this evening, I had determined that unplugging
all my PATA devices (leaving just the SATA ones, where FreeBSD lives)
allows a normal boot, although this isn't acceptable as I need my DVD
drives.

Disabling APIC in the BOIS with the PATA drives plugged in allows
booting. I tried booting with it enabled and telling FreeBSD not to
use ACPI but that didn't help.

Mark Linimon asked me to check to see if my PR was showing up now and
if not resubmit it, so I shall do that too.

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

Still can't boot on 6.0-STABLE Nov 2005 or 6.1-BETA

[James Seward]

Hello folks,

A while back (January) I posted to the list about a problem I had
booting 6.0-STABLE built with sources after about November 2005 on my
workstation.

Since that point, and including (I have now discovered) 6.1-PRERELEASE
(as my freshly built kernel identified itself just now), I can't boot.
At the point where the kernel should mount my root fs and continue
booting, it decides it can't see any disks other than fd0, and
presents me with a mountroot prompt.

Looking through the scrollback, it correctly identifies my ata
controllers earlier in the boot process.

A boot -v (captured over serial) is available here:
http://sakaki.jamesoff.net/~james/dmesg-broken.txt

A successful boot is available here:
http://sakaki.jamesoff.net/~james/dmesg-working.txt

When I get to the mountroot prompt, my IDE light is stuck on solid.

At the time I initially reported this problem I was running amd64. I
have since moved back to i386 (mainly for things like nvidia-driver
and win32-codecs), but the problem persists :(

My motherboard is an A8V-E Deluxe, and my disks are on both IDE and
SATA; the IDE disk plays no role in my FreeBSD boot (it has WinXP on
it). FreeBSD lives on my SATA drives. 5.3 and 5.4, as well as WinXP,
have no problems with the disks. I'm not doing anything funky like
RAID or geom.

I did try posting a PR for this a while back, but it never even seemed
to be recorded.

If I'm sending this request the wrong way, please let me know! I'd
love to help get this fixed so I can take advantage of the latest and
greatest on this machine :)

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

Re: New ports on older stable (4.11)

[James Long]

 Date: Wed, 01 Mar 2006 11:05:13 +
 From: Pete French [EMAIL PROTECTED]
 Subject: New ports on older stable (4.11)
 To: freebsd-stable@freebsd.org
 Message-ID: [EMAIL PROTECTED]
 
 I dont know how backward compatible ports are ggenerally, but I
 have a 4.11 machine that I really want to upgrade the ports on.
 But I dont know if they will alla ctually compile, and I dont wnat to
 start doing the process only to find that I cant build one of them
 possibly. Does anybody know if this is likely to work, or is it
 simply unsupported ?
 
 I;d love to upgrade the machine to 6.1 - but I have no physical access to
 it, nor am I likely to get any for the forseeable future, and upgrading
 across the 4/5 boundary isn't something I would be happy doing remotiley
 in multi-user mode (if it's even possible!)
 
 -pcf.

This is rather a case of the extremely near-sighted leading the blind,
but I recently inherited the care of some older boxen, and in fact,
recently deployed a new 4.11 installation, and proceeded to build
up-to-date ports on it.

I still share a part of your trepidation about getting oneself into
a bind with uncooperative dependencies, etc.  However, I have had
more success than I would have imagined.

Here are some suggestions, and I certainly welcome corrections to
my advice from more expert sources.

Start by backing up your /usr/ports and your /var/db/pkg and 
/var/db/ports and anything else you can think of.  Heck, back up the 
whole samn dystem if you can.  To paraphrase Douglas Adams, the 
universe is a lot safer if you have a backup.

I should think portaudit would be the first thing you'd want to 
install, so that you can find out if other ports have security 
problems.

Go slow, read Makefiles first, that sort of thing.  You can probably 
install portupgrade without too much trouble, as it doesn't have a lot 
of dependencies.  Then a lot of use of portupgrade -nR (portname) will 
tell you which ports have the fewest dependencies, and -nr (portname) 
will tell you which ports depend on any given port you may be thinking 
about upgrading.

Just for prurient interest, would you care to post your pkg_info?  If
you have portupgrade installed, or can install it, how about the output
from portupgrade -na also.


Jim

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

Re: Ifconfig with rc.conf Broken

[James Wyatt]

Don't alias interfaces have to be added to the network_interfaces= line? 
I thought only real interfaces were autodetected...


On Mon, 20 Feb 2006, MC wrote:

Date: Mon, 20 Feb 2006 11:20:21 -0800
From: MC [EMAIL PROTECTED]
To: freebsd-stable@freebsd.org
Subject: Ifconfig with rc.conf Broken

Bizarre behavior with configuring the main interface IP with rc.conf:

ifconfig_bge0=inet 10.0.0.15  netmask 0xff00
ifconfig_bge0_alias0=inet 10.0.0.16 netmask 0x # Sample alias entry.
defaultrouter=10.0.0.10

Doesn't configure the bge0 interface!  But:

ifconfig bge0 10.0.0.8 netmask 0x alias

works fine in rc.local.  Also configuration from command line in
multiuser mode works fine, although I notice messages about bge0 going
down, then another about it coming back up upon adding the main IP

I apparently have identical behavior from another machine with an fxp0
interface, from 6.1-PRERELEASE cvsuped on Sunday
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]



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

Re: RELENG_6 weird '..' permission troubles

[James Wyatt]

I've seen something very similar when the permissions of the mount point's 
underlieing subdirectory wasn't 777. Really strange to see, but it was a 
fallout from a company-wide change to make umask and directory permissions 
that wasn't quite implemented correctly.  Hope this helps - Jy@


On Thu, 16 Feb 2006, Dmitry Morozovsky wrote:

Date: Thu, 16 Feb 2006 16:23:38 +0300 (MSK)
From: Dmitry Morozovsky [EMAIL PROTECTED]
To: freebsd-stable@freebsd.org
Subject: RELENG_6 weird '..' permission troubles

Dear colleagues,

I have misterious permission troubles on rather fresh RELENG_6:

from root everything's ok:

[EMAIL PROTECTED]:/usr# ls -la /usr/
total 48
drwxr-xr-x  13 root  wheel  512 Feb  2 20:59 ./
drwxr-xr-x  20 root  wheel  512 Feb 16 14:37 ../
drwxrwx---   2 root  operator   512 Feb 16 15:58 .snap/
drwxr-xr-x   3 root  wheel  512 Feb  2 16:08 X11R6/
...

from myself too:

[EMAIL PROTECTED]:~ ls -la /usr/
total 48
drwxr-xr-x  13 root  wheel  512 Feb  2 20:59 ./
drwxr-xr-x  20 root  wheel  512 Feb 16 14:37 ../
drwxrwx---   2 root  operator   512 Feb 16 15:58 .snap/
drwxr-xr-x   3 root  wheel  512 Feb  2 16:08 X11R6/
...
[EMAIL PROTECTED]:~ id
uid=268(marck) gid=268(marck) groups=268(marck), 0(wheel), 5(operator)

but from really unprivileged user:

%id
uid=1008(nata) gid=1008(nata) groups=1008(nata), 24(samba)
%ls -la /usr
ls: ..: Permission denied
total 46
drwxr-xr-x  13 root  wheel  512 Feb  2 20:59 .
drwxrwx---   2 root  operator   512 Feb 16 15:58 .snap
drwxr-xr-x   3 root  wheel  512 Feb  2 16:08 X11R6
...

The same on other mountpoints. fsck is ok.

Any hints?


Sincerely,
D.Marck [DM5020, MCK-RIPE, DM3-RIPN]

*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] ***

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


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

Re: Trouble with mounting USB stick as user

[James Long]

 Date: Wed, 8 Feb 2006 06:46:37 -0600
 From: Michael Ekstrand [EMAIL PROTECTED]
 Subject: Re: Trouble with mounting USB stick as user
 To: freebsd-stable@freebsd.org
 Message-ID: [EMAIL PROTECTED]
 Content-Type: text/plain; charset=US-ASCII
 
 On Wed, 8 Feb 2006 22:40:04 +1100
 Rob [EMAIL PROTECTED] wrote:
  Can anyone shed some light on what is happening here?
 
 AFAIK, only root can mount things under FreeBSD, period. I could be
 wrong on this... but I looked around a while ago for something to do
 the job of the Linux 'user' option, and found nothing. I kinda remember
 trying changing permissions too.
 
 If I'm wrong, I'd love to be corrected :-).
 
 - Michael

# portupgrade -N security/sudo
# man sudo

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

Re: Panic in 6-RELEASE-p4 with if_bridge and pf

[James Seward]

On 2/2/06, Andrew Thompson [EMAIL PROTECTED] wrote:
 This is a known problem with 6.0R, see the 2005/11/16 entry in
 http://www.freebsd.org/releases/6.0R/errata.html.

 You should either upgrade to 6-STABLE or you can apply this patch to fix
 the problem.

Arrgh, I forgot to check the errata (slap wrist) and Googling didn't
find it; thanks!

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

Panic in 6-RELEASE-p4 with if_bridge and pf

[James Seward]

 =
-1067474263, tf_cs = 32, tf_eflags = 590338, tf_esp = 4, tf_ss =
-1050896896})
at /usr/src/sys/i386/i386/trap.c:432
#6  0xc05fc89a in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7  0xc05fa2a9 in bus_dmamap_load (dmat=0xc1845980, map=0x122b0,
buf=0x122b0207, buflen=2046, callback=0xc046c4d8 em_dmamap_cb,
callback_arg=0xd54c4c74, flags=0) at pmap.h:200
#8  0xc046cdc2 in em_get_buf (i=11, adapter=0xc164c800, nmp=0x0) at
/usr/src/sys/dev/em/if_em.c:2474
#9  0xc046d593 in em_process_receive_interrupts (adapter=0xc164c800,
count=-2) at /usr/src/sys/dev/em/if_em.c:2797
#10 0xc046a7ed in em_intr (arg=0xc164c800) at /usr/src/sys/dev/em/if_em.c:992
#11 0xc04c85b5 in ithread_loop (arg=0xc1586580) at
/usr/src/sys/kern/kern_intr.c:547
#12 0xc04c783c in fork_exit (callout=0xc04c845c ithread_loop,
arg=0xc1586580, frame=0xd54c4d38) at /usr/src/sys/kern/kern_fork.c:789
#13 0xc05fc8fc in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:208



Now I look at it, the two panics are quite dissimilar. Should I
suspect the network cards?

Another dump previous to that one occured in irq18: fxp0. Now I'm
suspicious. (Excuse my thinking out loud.)

Other than pulling cards and seeing which ones stop it panicing, can
anyone suggest things that may be going wrong? Is the combination of
if_bridge and pf used in this fashion valid?

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

Re: nVidia RAID + FreeBSD 6.0

[James Long]

 Date: Sun, 29 Jan 2006 15:08:21 + (GMT)
 From: Gavin Atkinson [EMAIL PROTECTED]
 Subject: Re: nVidia RAID + FreeBSD 6.0
 To: Christian Brueffer [EMAIL PROTECTED]
 Cc: freebsd-stable@freebsd.org, [EMAIL PROTECTED]
 
 On Sun, 29 Jan 2006, Christian Brueffer wrote:
  On Sun, Jan 29, 2006 at 04:46:52PM +1030, Daniel O'Connor wrote:
  I am looking at getting a motherboard based on nForce 3 or 4, and I am
  wondering if the RAID will be usable?
  
  Be aware though that there have been reports on the lists of data loss
  in connection with NVIDIA RAIDs.  This seems to also happen on other
  operating systems.
 
 In my experience, they seem to be reliable while both disks work, but when 
 a disk needs to be rebuilt the RAID BIOS seem to pick the source disk at 
 random, as opposed to something radical like using the only valid disk as 
 the source.

Gee, no RAID at all is reliable when both disks work!  A RAID solution 
that has problems when one disk fails is pretty darn worthless as a 
RAID solution.

...
 Indeed, on the hardware I was using (a Sun X2100 server), Solaris had the 
 same problem, and about 50% of the time you'd end up with corrupted or 
 blank disks after a rebuild.  Sun have now stopped claiming in the 
 specifications that these machines support RAID 
...

Doctor Sun, it hurts when I do this.
Well, don't do that.

Not the best response one might hope for.


Regards,

Jim

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

How to get custom release CD to boot without floppies?

[James Long]

I am trying to create bootable installation media for 6.0-RELEASE.  
This is my first attempt at doing this, so I am learning a lot and
fumbling even more as I go.

First, I wish to thank Masafumi Watari for his helpful step-by-step
procedure, based on RELENG_4, found at
http://www.sfc.wide.ad.jp/~watari/FreeBSD/boot.html.  It has gotten 
me much farther than any other resource that I've found on the web.

Actually, I think I'm building a snapshot release of 6-STABLE, since 
I started by cvsup-ing:

cvsup -g cvs-supfile

with this cvs-supfile:
--- snip
*default host=cvsup4.FreeBSD.org
*default base=/var/db
*default prefix=/home/ncvs
*default release=cvs
*default delete use-rel-suffix

*default compress

src-all

cvsroot-all
--- snip

I am intentionally omitting ports and docs because I believe I do
not require them for my purposes.

I then went into /usr/src and did 'make -j4 buildworld' which ran 
without errors.

The 'make release' was done thus:

export NODOC=1
export NOPORTS=1

cd /usr/src/release
make release CHROOTDIR=/usr/tmp/CHROOTDIR BUILDNAME=6.0-REL-TEST 
CVSROOT=/usr/home/ncvs RELEASETAG=RELENG_6


Watari's document talks about customizing install.cfg, but in my
limited understanding, this file automates installation tasks.
I don't think I need this.  I will be happy to just have a custom
release which boots into a standard sysinstall.

Watari also discusses modifying sysinstall itself, again, beyond the
scope of my needs.

So I proceeded directly to burning the CD-R.  I don't have a burner
on the build machine, nor do I have mkisofs installed.  So I tarred
up the release CHROOTDIR:

cd /usr/tmp
tar cf CHROOTDIR.tar CHROOTDIR

and un-tarred on my burner-equipped machine:

cd /work/
tar xpf ~/CHROOTDIR.tar

Finally, I made an ISO image:

cd CHROOTDIR
export CHROOTDIR=.
mkisofs -d -D -N -R -T -V FreeBSD6.0-RELEASE \
-P Test Distribution \
-o ~/tinn.iso -b floppies/boot.flp \
-c floppies/boot.catalog $CHROOTDIR/R/cdrom/disc1

# /* -V is your CD name */
# /* -P is for some comments */
# /* -o is your image name */
# /* -b and -c should be left how it is. It's set for auto boot. These paths 
should not be a full path */


I then took an md5 of the iso file, burned it to disc, and got
a disc with the same md5 value.

The disc does boot, but asks for kernel floppies:

Insert disk labelled Kernel floppy 1 and press any key...

I want to make a CD which doesn't require floppies to boot.  In 
diff'ing the CD against a genuine 6.0-RELEASE I find that the 
boot.catalog didn't make it on the disc (apparently because there 
just plain isn't one anywhere in the CHROOTDIR tree I built), but 
I can't find anything by Googling that definitively points to that 
being the problem.  I have compared some files between my release 
and 6.0-RELEASE (/boot/*boot*, /boot/defaults/loader.conf, 
/boot/loader.rc, etc.), and in general, binaries are the same size, 
and text files have trivial differences.  But perhaps I have 
overlooked some key files somewhere.

The mkisofs option -b floppies/boot.flp makes me squint a lot,
but my searches haven't led me to a file which seems a more likely
El Torito boot image.

So

I'm going to go rustle up some floppies -- I don't think I have any
around -- and  see if my release at least does boot via the floppy
method.  That will be valuable knowledge to have before attempting
a second release candidate.  I should make diskettes from the images
$CHROOTDIR/R/cdrom/disc1/floppies/kern1.flp and kern2.flp, yes?

In the meantime, can anyone shed light on why my CD asks for floppies
in the first place?  If it is the lack of the boot.catalog file, can
I simply copy the boot.catalog from the official 6.0-RELEASE disc,
and place it in $CHROOTDIR/floppies/ as per where mkisofs was told
to find it?  If it is the wrong choice of boot image with the -b
switch, which file should I use instead?

In case it helps,

$(ls -lR) of $CHROOTDIR is at: 
ftp://www.umpquanet.com/pub/make-rel-chrootdir-ls-lR.txt
$(ls -lR) of burned CD is at: ftp://www.umpquanet.com/pub/make-rel-cd-ls-lR.txt


Thank you very much!


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

Re: rpcbind lingering on IP no longer specified on command line

[James Long]

 Date: Thu, 5 Jan 2006 10:31:33 -0500
 From: Vivek Khera [EMAIL PROTECTED]
 Subject: Re: rpcbind lingering on IP no longer specified on command
   line
 To: [EMAIL PROTECTED]
 Message-ID: [EMAIL PROTECTED]
 Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
 
 
 On Jan 5, 2006, at 6:06 AM, Gavin Atkinson wrote:
 
  Can anyone explain why rpcbind will still bind to all tcp interfaces?
 
  Although I believe this is a bug, it is actually working as  
  documented:
 
  from rpcbind(8):
   -h bindip
   Specify specific IP addresses to bind to for UDP  
  requests.
 
 Yeah, I noticed that little tiny UDP requests note in the -h docs  
 too.  There's no reason to bind to all tcp addresses, and it is  
 causing me heartburn for getting the server certified...

Good grief, why not just firewall off the undesired UDP ports and call
it good?

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

Re: rpcbind lingering on IP no longer specified on command line

[James Long]

On Fri, Jan 06, 2006 at 10:22:43AM -0500, Vivek Khera wrote:
 
 On Jan 6, 2006, at 4:40 AM, James Long wrote:
 
 Yeah, I noticed that little tiny UDP requests note in the -h docs
 too.  There's no reason to bind to all tcp addresses, and it is
 causing me heartburn for getting the server certified...
 
 Good grief, why not just firewall off the undesired UDP ports and call
 it good?
 
 I guess we could take that band-aid approach... however, how do you  
 know what port RPC decides to listen on other than the 111 port?  It  
 is more or less random.  That makes it very difficult to firewall.

P-shaw.  If you're enduring heartburn for getting the server
certified then firewall off the rpcbind service from unwanted 
IPs and voila, you get your get your server certified and business
goes on.  Then you'll have the luxury of time to debug the true 
problem with rpcbind, and your testing is done behind the privacy 
of your firewall.

As far as unpredictable listening ports opened by rpc, that is exactly
why a secure firewall opens only selected ports on selected IPs, and 
blocks everything else.  It doesn't matter if it listens on port X of
IP y when your firewall doesn't permit incoming connections on that 
port and IP in the first place.

Jim


# sockstat | grep rpcbind
root rpcbind11382 5  stream /var/run/rpcbind.sock
root rpcbind11382 6  dgram  - /var/run/logpriv
root rpcbind11382 7  udp4   127.0.0.1:111 *:*
root rpcbind11382 8  udp4   192.168.100.200:111   *:*
root rpcbind11382 9  udp4   *:664 *:*
root rpcbind11382 10 tcp4   *:111 *:*


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

Re: SSH login takes very long time...sometimes

[James Tanis]

I wouldn't be surprised if there is actually more going on, their were
times before I entered my local network into my hosts file that
authentication would completely time out and drop the client. It
usually only happened when using my ISP's dns server and not my local
caching server, but still, their dns server isn't *that* slow :P.

On 12/25/05, Rostislav Krasny [EMAIL PROTECTED] wrote:
 Hi,

 I had submitted a bin/62139 PR because of the same problem about a
 year ago. I still think there is a bug somewhere in a resolver(3)
 library or in libc functions like gethostbyname(). Because of this bug
 the gethostbyname() doubles the number of its reverse resolving
 requests, in a case the DNS server isn't responding. The other reason
 for very long waiting is a default configuration of resolver(5). In
 most other systems RES_DFLRETRY is defined as 2, but in FreeBSD it is
 defined as 4. In a case the DNS server isn't responding the
 gethostbyname() makes 8 (eight!) reverse resolving attempts for one
 (!) non-responding DNS server before it returns error. And this is by
 default. All that is still true for my current 6.0-STABLE.

 http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/62139

 As a workaround I may suggest addind options attempts:2 or even
 options attempts:1 line to the /etc/resolver.conf
 ___
 freebsd-stable@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-stable
 To unsubscribe, send any mail to [EMAIL PROTECTED]



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

Re: SSH login takes very long time...sometimes

[James Tanis]

 you can fake your IP and you can fake your hostname, but exactly for security
 reasons, since we believe that beeing a a network admin is not because of
 luck but knowledge, and we also believe that this person has a certain
 responsibility and so he will probably not set up false dns reverse data.

 so when I check your IP and hostname you send me and when this do not match
 the reverse info I get I can suppose you do not have good intentions or you
 do not have the knowledge to set your network up. Both cases may not be
 welcome on my network and you get kicked out. Like you see here the decision
 is the owner's one who can or not enter his home.

If you truly believe one can easily fake their IP then a
reverse-lookup is even more irrelevant because it doesnt take a genius
to choose an ip and hostname that match. From what your saying
falsifying the actual reverse-lookup record need not even be
considered. I don't pretend to be any kind of hacker or security
professional, I have no idea how involved spoofing a valid (not
local-only) ip is or if it is indeed possible, but it seems to me that
this ability would only make the reverse-lookup less reliable.


 so reverse dns is a absolute valid check - what never was so important as
 today since each newborn already knows how to fake IP's

 and when your residential Ip provider do not has a correct reverse DNS get
 yourself a more serious one

A good many large ips do not assign a reverse lookup as that would
also require a hostname. Since most residential users do not need a
host name it isn't necessarily standard procedure to give them one.

Isp that assign reverse lookup cause an even bigger problem because no
one want to name their computers according to their isp,  for instance
Charter likes to assign hostnames like:
xxx-xxx-xxx-xxx.dhcp.xxx.xx.charter.com

Which is very basically a hyphen delimited ip followed by an
abbreviated city and state. Nothing wrong with the scheme but I don't
really care to name my firewall that, I much prefer loki.pycoder.org.
This in itself is not a sign of ill intent. Most residential users,
whether they are knowledgeable or not will not all make sure to have
their computers all reporting the hostname
xxx-xxx-xxx-xxx.dhcp.xxx.xx.charter.com yet they have no ill intent. 
Clearly then reverse dns lookup is only desireable in specific
situations where you know exactly where you'll be getting remote
connections from and can accomodate if they do not have properly set
reverse-lookup entries.


 anyway, you are mixing things up since you do not need a valid reverse dns to
 configure your sshd, the server admin can disable this lookup or use the
 local host file - or you may like the clever way and forget to set or
 delete your resolv.conf

Exactly the point I was trying to argue. I've been using FreeBSD long
enough to know my way around /etc as well as hold my own with BIND.. I
was more than able to diagnose/fix the problem. That does not change
the fact though that not everyone is able to administer their own dns,
not because they do not know how, but because they do not have the
right. How does this affect FreeBSD? Not at all, I'd just wish it
didn't have to be in the default setup, but I've already lost interest
in the subject as its really just an insignificant point that really
didn't deserve this long of an email :P.



 João







 A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura.
 Service fornecido pelo Datacenter Matik  https://datacenter.matik.com.br
 ___
 freebsd-stable@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-stable
 To unsubscribe, send any mail to [EMAIL PROTECTED]



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

Re: SSH login takes very long time...sometimes

[James Tanis]

For whatever reason, I have had a similar problem which was solved by
entering the machines that you are logging in from into the hosts
file. I'm guessing it attempts a reverse lookup and your (as well as
my) dns/hostname does not match its reverse lookup entry.

On 12/23/05, Michael A. Koerber [EMAIL PROTECTED] wrote:
 All,

   I have three machines that have had 5.4 and 6.0 installed.  Two of the 
 three machines have very
 well behaved ssh.  However, the machine (laptop) named OBOE does not.

   Specifically ssh oboe will (most of the time) hang for around one minute 
 before asking for a
 prompt.  However, if I'm logged into OBOE and ssh BSD (one of the other 
 machines) a password is
 requested within a couple seconds.  (I said most of the time, since on 
 occasion I can reboot OBOE
 and ssh will work just fine...hmmm.)

   I have looked through the /var/log files for clues and skimmed man ssh 
 for time out related
 stuff, but no luck.

   Where should I start looking for clues?

   All machines have had clean installs from newfs'd drive under both 5.4 
 and 6.0 so I'm sure no
 left over configs are getting propagated.
 --
 -
 Dr Michael A. Koerber
 x3250
 ___
 freebsd-stable@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-stable
 To unsubscribe, send any mail to [EMAIL PROTECTED]



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

Re: SSH login takes very long time...sometimes

[James Tanis]

What reason is that? A reverse-lookup is no longer really a valid way
of filtering out the undesireable unless your lucky enough to be
dealing only with those who have the knowledge and ability to control
those entries. Most residential ips either have no reverse-lookup or
it's set to some long painful textual conglomeration devised by the
isp (although at the isp I work at we will set it per some users
requests..). Anyway, to make a long story short, you end up locking
out or at the very least delaying (for up to several minutes) the very
people who use it. I can definately see the sysadmin side of it though
were its used perhaps to remotely access a data center from a
satellite location -- you don't much want or care that a residential
ip has problems connecting to the server. It just definately doesn't
seem to me a last resort option, at the drop of a hat someone can
change their hostname to match their reverse dns and back again --
setting up a good packet filter to filter out all but the desired ip
ranges seems a much more reliable method.

On 23 Dec 2005 09:30:56 -0500, Lowell Gilbert
[EMAIL PROTECTED] wrote:
 Marian Hettwer [EMAIL PROTECTED] writes:

  Hej there,
 
  Kobi Shmueli wrote:
   Try checking /etc/resolv.conf on oboe first, adding a static entry to
   /etc/hosts of the remote ip/host should speed dns checks as well.
   You can also run ssh in verbose mode (ssh -v oboe) or/and run sshd in 
   debug
   mode (sshd -d).
  
  alternativly to check out wether it's dns related, you use set the
  Option UseDNS no in your sshd_config, so sshd won't try a reverse
  dns lookup.
  Give it a shoot. Usually ssh timeouts are related to DNS...

 That should be a last resort; the hostname checks are there for a
 reason...
 ___
 freebsd-stable@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-stable
 To unsubscribe, send any mail to [EMAIL PROTECTED]



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

Reboots under 6.0 while exercising md device

[James Long]

For some reason, this script:

#!/bin/sh

DEV=$(md_config -a -t malloc -s 500m)
newfs -i 512 -U /dev/$DEV

mount /dev/$DEV /mnt
cp -Rp /usr/src /mnt/


will kill my machine.  I get zillions (well, hundreds at
least, without a serial console I can't count them)
of:


Dec 21 19:16:27 test kernel: g_vfs_done():md0[WRITE(offset=352649216, 
length=16384)]error = 28
Dec 21 19:16:27 test kernel: g_vfs_done():md0[WRITE(offset=352665600, 
length=12288)]error = 28

with varying offsets and lengths, but seemingly always error 28

The system does not panic orderly, but rather spontaneously reboots after
spewing a lot of the above error messages (5-20 secs worth).

This is on a Compaq Proliant ML370 with 1 GB RAM, dmesg below.


What do I need to fix to be able to use a RAM-backed filesystem?


Jim

FWIW, this script does not seem to freak out my machine,  This led
me to consider inode starvation, but '-i 512' results in over 6 
inodes for what I estimate to be  4 files in /usr/src.

#!/bin/sh

DEV=$(mdconfig -a -t malloc -s 500m)
newfs -i 512 -U /dev/$DEV

mount /dev/$DEV /mnt

dd if=/dev/zero of=/mnt/1M bs=1024 count=1024

for j in $(jot 450); do {
  cp -p /mnt/1M /mnt/1M.$(printf %03d $j)
} done


After that, df -h /mnt shows:

/dev/md0 484M458M-13M   103%/mnt


Here's the dmesg:


Copyright (c) 1992-2005 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 6.0-RELEASE #0: Wed Dec 21 15:40:38 PST 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: Intel Pentium III (996.85-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0x686  Stepping = 6
  
Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
real memory  = 1073725440 (1023 MB)
avail memory = 1041682432 (993 MB)
MPTable: COMPAQ   PROLIANT
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): APIC ID:  1
 cpu1 (AP): APIC ID:  0
ioapic0: Changing APIC ID to 8
ioapic0: Assuming intbase of 0
ioapic0 Version 1.1 irqs 0-34 on motherboard
npx0: [FAST]
npx0: math processor on motherboard
npx0: INT 16 interface
cpu0 on motherboard
cpu1 on motherboard
pcib0: ServerWorks NB6635 3.0LE host to PCI bridge pcibus 0 on motherboard
pci0: PCI bus on pcib0
sym0: 1510d port 0x2000-0x20ff mem 
0xc6effc00-0xc6ef,0xc6efe000-0xc6efefff irq 11 at device 1.0 on pci0
sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking
sym0: [GIANT-LOCKED]
sym1: 1510d port 0x2400-0x24ff mem 
0xc6efdc00-0xc6efdfff,0xc6efc000-0xc6efcfff irq 15 at device 1.1 on pci0
sym1: No NVRAM, ID 7, Fast-40, LVD, parity checking
sym1: [GIANT-LOCKED]
fxp0: Intel 82559 Pro/100 Ethernet port 0x2800-0x283f mem 
0xc6efb000-0xc6efbfff,0xc6d0-0xc6df irq 5 at device 2.0 on pci0
miibus0: MII bus on fxp0
inphy0: i82555 10/100 media interface on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp0: Ethernet address: 00:02:a5:64:d5:4e
pci0: display, VGA at device 3.0 (no driver attached)
pci0: base peripheral at device 4.0 (no driver attached)
isab0: PCI-ISA bridge at device 15.0 on pci0
isa0: ISA bus on isab0
atapci0: ServerWorks ROSB4 UDMA33 controller port 
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x3000-0x300f at device 15.1 on pci0
ata0: ATA channel 0 on atapci0
ata1: ATA channel 1 on atapci0
pcib3: ServerWorks NB6635 3.0LE host to PCI bridge pcibus 3 on motherboard
pci3: PCI bus on pcib3
ida0: Compaq Smart Array 431 controller port 0x4000-0x40ff mem 
0xc6fff000-0xc6ff irq 10 at device 6.0 on pci3
ida0: [GIANT-LOCKED]
ida0: drives=1 firm_rev=1.18
idad0: Compaq Logical Drive on ida0
idad0: 17363MB (35561280 sectors), blocksize=512
eisa0: EISA bus on motherboard
mainboard0: CPQ0690 (System Board) on eisa0 slot 0
eisa0: unknown card @@D9004 (0x00049004) at slot 2
pmtimer0 on isa0
orm0: ISA Option ROMs at iomem 
0xc-0xc7fff,0xc8000-0xcbfff,0xe8000-0xedfff,0xee000-0xe on isa0
atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0
atkbd0: AT Keyboard irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
psm0: PS/2 Mouse irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: model IntelliMouse, device ID 3
fdc0: Enhanced floppy controller at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: [FAST]
fd0: 1440-KB 3.5 drive on fdc0 drive 0
ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
ppbus0: Parallel port bus on ppc0
plip0: PLIP network interface on ppbus0
lpt0: Printer on ppbus0
lpt0: Interrupt-driven port
ppi0: Parallel I/O on ppbus0
sc0: System console at flags 0x100 on isa0
sc0: VGA 16 virtual consoles, flags=0x300
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
Timecounters tick every 1.000 msec
acd0: CDROM COMPAQ 

Re: puzzling ipfw show output

[James Long]

 Date: Mon, 12 Dec 2005 09:39:44 +0100 (CET)
 From: Trond Endrest?l [EMAIL PROTECTED]
 Subject: Re: puzzling ipfw show output
 To: FreeBSD stable freebsd-stable@freebsd.org
 Message-ID: [EMAIL PROTECTED]
 Content-Type: TEXT/PLAIN; charset=ISO-8859-1
 
 On Mon, 12 Dec 2005 19:09+1100, Graham Menhennitt wrote:
 
 One last question:
 
 Why do you need rule 65530 when the built-in rule 65535 does the same
 job?

Having rule 65530 there allows the ruleset to function consistently
on systems configured to accept by default or deny by default.

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

xorg-clients conflicts with xterm (patch)

[James Long]

After hours of head-banging over the past couple of days,
I have finally succeeded in installing EITHER 
xorg-clients-6.8.2_1 OR xterm-206_1.  Previously,
installing either port told me that it conflicted
with the other, in spite of having cvsupped my 
ports tree twice to ensure I was getting the most
recent version of the ports, hopefully including a
fix to the chicken-and-egg problem noted in 
/usr/ports/UPDATING

Once I spotted an odd bit of output in the portupgrade
dialogue, I made a change to xorg-clients Makefile 
which allowed everything to install.  pkgdb -F afterwards
and all my dependencies are tidied up.

May I suggest the following patch to 
/usr/ports/x11/xorg-clients/Makefile:


--- MakefileSun Nov 13 21:47:34 2005
+++ foo Tue Nov 15 19:19:37 2005
@@ -18,7 +18,7 @@
 MAINTAINER=[EMAIL PROTECTED]
 COMMENT=   X client programs and related files from X.Org
 
-RUN_DEPENDS=   xterm0:${PORTSDIR}/x11/xterm
+RUN_DEPENDS=   xterm:${PORTSDIR}/x11/xterm
 LIB_DEPENDS=   png.5:${PORTSDIR}/graphics/png \
Xft.2:${PORTSDIR}/x11-fonts/libXft
 
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: xorg-clients conflicts with xterm (patch)

[James Long]

On Tue, Nov 15, 2005 at 07:32:45PM -0800, David Wolfskill wrote:
 On Tue, Nov 15, 2005 at 07:26:16PM -0800, James Long wrote:
  After hours of head-banging over the past couple of days,
  I have finally succeeded in installing EITHER 
  xorg-clients-6.8.2_1 OR xterm-206_1.  Previously,
  installing either port told me that it conflicted
  with the other, in spite of having cvsupped my 
  ports tree twice to ensure I was getting the most
  recent version of the ports, hopefully including a
  fix to the chicken-and-egg problem noted in 
  /usr/ports/UPDATING
 
 It mentioned a conflict; I don't recall a chicken-and-egg issue.

Forgive me for not including enough background.

Due to an improper procedure on my part in converting from
XFree86 to Xorg, plus a complete rebuild of all ports as
part of upgrading to 6.0-STABLE, and a bit of ignorance on
my part, I wound up in a situation where I had pkg_deleted
both xorg-clients and xterm.  I was then in a situation
where I couldn't install xorg-clients because it depended
on xterm, but xterm couldn't be installed because it con-
flicted with xorg-clients.  That was my 
chicken-and-egg dilemma.  pkgdb -F was dutifully showing 
several packages with dangling dependencies to those two, 
but I couldn't install either of them.  cvsupping to the most 
recent ports tree didn't change the problem.  

Then I noticed:

===   xorg-clients-6.8.2_1 depends on package: xterm0 - not found

and investigated the Makefile to find why the odd package
name of xterm0.

I then patched the Makefile as I posted, and I was able to
make install in xorg-clients and pkgdb -F and everything
installed.

Further documentation of the state of my pkg_info and 
dependencies is below.


Jim



[pkg_info | egrep xorg|xterm # note lack of xorg-clients and xterm]
t21 : 19:04:41 /root# pkg_info | egrep xorg|xterm
xorg-6.8.2  X.Org distribution metaport
xorg-documents-6.8.2 Documentation of X11 protocol and libraries from X.Org
xorg-fonts-100dpi-6.8.2 X.Org 100dpi bitmap fonts
xorg-fonts-75dpi-6.8.2 X.Org 75dpi bitmap fonts
xorg-fonts-cyrillic-6.8.2 X.Org Cyrillic bitmap fonts
xorg-fonts-encodings-6.8.2 X.Org font encoding files
xorg-fonts-miscbitmaps-6.8.2 X.Org miscellaneous bitmap fonts
xorg-fonts-truetype-6.8.2 X.Org TrueType fonts
xorg-fonts-type1-6.8.2 X.Org Type1 fonts
xorg-fontserver-6.8.2 X font server from X.Org
xorg-libraries-6.8.2 X11 libraries and headers from X.Org
xorg-manpages-6.8.2 X.Org library manual pages
xorg-nestserver-6.8.2 Nesting X server from X.Org
xorg-printserver-6.8.2_2 X Print server from X.Org
xorg-server-6.8.2_6 X.Org X server and related programs
xorg-vfbserver-6.8.2 X virtual framebuffer server from X.Org

[Initial state of ports dependencies:]
[EMAIL PROTECTED] pkgdb -F
---  Checking the package registry database
Stale dependency: kde-3.4.2 - xorg-clients-6.8.2_1 (x11/xorg-clients):
xorg-vfbserver-6.8.2 (score:27%) ? ([y]es/[n]o/[a]ll) [no]
New dependency? (? to help):
Skip this? ([y]es/[n]o/[a]ll) [yes]
Skipped.
Stale dependency: kde-3.4.2 - xterm-205_1 (x11/xterm):
New dependency? (? to help):
Skip this? ([y]es/[n]o/[a]ll) [yes]
Skipped.
Stale dependency: kdeadmin-3.4.2 - xterm-205_1 (x11/xterm):
Skip this? ([y]es/[n]o/[a]ll) [yes]
Stale dependency: kdeadmin-3.4.2 - xorg-clients-6.8.2_1 (x11/xorg-clients):
Skip this? ([y]es/[n]o/[a]ll) [yes]
Stale dependency: kdebase-3.4.2_2 - xterm-205_1 (x11/xterm):
Skip this? ([y]es/[n]o/[a]ll) [yes]
Stale dependency: kdebase-3.4.2_2 - xorg-clients-6.8.2_1 (x11/xorg-clients):
Skip this? ([y]es/[n]o/[a]ll) [yes]
Stale dependency: kdegames-3.4.2_1 - xterm-205_1 (x11/xterm):
Skip this? ([y]es/[n]o/[a]ll) [yes]
Stale dependency: kdegames-3.4.2_1 - xorg-clients-6.8.2_1 (x11/xorg-clients):
Skip this? ([y]es/[n]o/[a]ll) [yes]
Stale dependency: kdelibs-3.4.2_1 - xterm-205_1 (x11/xterm):
Skip this? ([y]es/[n]o/[a]ll) [yes]
Stale dependency: kdelibs-3.4.2_1 - xorg-clients-6.8.2_1 (x11/xorg-clients):
Skip this? ([y]es/[n]o/[a]ll) [yes]
Stale dependency: kdemultimedia-3.4.2_1 - xterm-205_1 (x11/xterm):
Skip this? ([y]es/[n]o/[a]ll) [yes]
Stale dependency: kdemultimedia-3.4.2_1 - xorg-clients-6.8.2_1 
(x11/xorg-clients):
Skip this? ([y]es/[n]o/[a]ll) [yes]
Stale dependency: kdemultimedia-akode-3.4.2 - xterm-205_1 (x11/xterm):
Skip this? ([y]es/[n]o/[a]ll) [yes]
Stale dependency: kdemultimedia-akode-3.4.2 - xorg-clients-6.8.2_1 
(x11/xorg-clients):
Skip this? ([y]es/[n]o/[a]ll) [yes]
Stale dependency: kdemultimedia-mpeglib_artsplug-3.4.2 - xterm-205_1 
(x11/xterm):
Skip this? ([y]es/[n]o/[a]ll) [yes]
Stale dependency: kdemultimedia-mpeglib_artsplug-3.4.2 - xorg-clients-6.8.2_1 
(x11/xorg-clients):
Skip this? ([y]es/[n]o/[a]ll) [yes]
Stale dependency: kdetoys-3.4.2 - xterm-205_1 (x11/xterm):
Skip this? ([y]es/[n]o/[a]ll) [yes]
Stale dependency: kdetoys-3.4.2 - xorg-clients-6.8.2_1 (x11/xorg-clients):
Skip this? ([y]es/[n]o/[a]ll) [yes]
Stale dependency: koffice-1.4.1_1,1 - xterm-205_1 (x11/xterm):
Skip this? ([y]es/[n]o/[a]ll) [yes