Epic5-0.3.1 ruby support and FreeBSD AMD64 problem

2006-11-12 Thread Josh Paetzel
I'm the port maintainer for irc/epic4 and irc/epic5 and try to liason 
with the developers as much as possible.  I've received a request 
from the Epic developers that I can't really help with and I'm 
wondering if someone would be willing to be able to lend them a hand.

Epic5-0.3.1 includes optional ruby support.  When ruby support is 
compiled in on an AMD64 box attempting to use gdb on it 
spontainiously reboots the box, no panic, no hang, just a hard reset.  
The problem has been verified to occur on 5-STABLE and 6-STABLE on 
multiple machines.  It does not occur if the gdb from devel/gdb6 is 
used.

At the moment I'm dealing with the situation by keeping the port at 
5.0.2.0 but I'm getting more and more requests to get 0.3.1 into the 
tree.  Given the nature of the problem doing so at this point means 
either not having the ruby support in the port or marking it broken 
for AMD64, neither of which are particularly attractive.

Any level of help would be appreciated, whether it's just a 'here's 
what I would look for first all the way up to digging into some 
code.  I'd rather not post email addresses to the list but if a kind 
soul wishes to get in contact with the epic team I can give contact 
info out privately.

Another (possibly useful) data point that occurs to me is that it 
hasn't been tested on any sort of 64 bit linux at all, so it's really 
unknown if this is FBSD specific.

-- 
Thanks,

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


Re: Epic5-0.3.1 ruby support and FreeBSD AMD64 problem

2006-11-12 Thread Josh Paetzel
On Sunday 12 November 2006 15:13, Mike Meyer wrote:
 In [EMAIL PROTECTED], Josh Paetzel 
[EMAIL PROTECTED] typed:
  I'm the port maintainer for irc/epic4 and irc/epic5 and try to
  liason with the developers as much as possible.  I've received a
  request from the Epic developers that I can't really help with
  and I'm wondering if someone would be willing to be able to lend
  them a hand.
 
  Epic5-0.3.1 includes optional ruby support.  When ruby support is
  compiled in on an AMD64 box attempting to use gdb on it
  spontainiously reboots the box, no panic, no hang, just a hard
  reset. The problem has been verified to occur on 5-STABLE and
  6-STABLE on multiple machines.  It does not occur if the gdb from
  devel/gdb6 is used.
 
  At the moment I'm dealing with the situation by keeping the port
  at 5.0.2.0 but I'm getting more and more requests to get 0.3.1
  into the tree.  Given the nature of the problem doing so at this
  point means either not having the ruby support in the port or
  marking it broken for AMD64, neither of which are particularly
  attractive.

 Why not test for both conditions? I.e. - if ruby support is
 included (you did say it was optional) AND if you're on amd64, then
 mark the port as broken? Better yet, since using devel/gdb6 seems
 to fix the problem, use devel/gdb6 under those conditions. Or - to
 keep it simple - always use devel/gdb6.

 Note that getting this problem fixed won't meean you can ignore it.
 If you want to avoid building with the workaround (whatever that
 may be) on amd64 after the fix has been committed, you'll have to
 check the OS version, and optionally build with the workaround if
 someone is installing the fix on an earlier version of FreeBSD.

   mike

You're right.  The workaround could be more sophisticated.  Thanks for 
pointing that out.  I guess my perspective is that this issue is 
being caused by a problem in the code for epic, not a bug in FBSD.  
From the wording of your email I sort of get the impression you are 
thinking along the lines of it being a FreeBSD bug?  

My main plea is for someone familiar with FBSD to volunteer to give 
these guys a hand in tracking this down. :)

-- 
Thanks,

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


Re: FreeBSD-6.1/amd64 bge(4) driver performance problems

2006-11-29 Thread Josh Paetzel
On Tuesday 28 November 2006 12:47, Vladimir Terziev wrote:
   Hi,

   i have a machine with Pentium 4-D processor utilizing
 FreeBSD-6.1-RELEASE-p10/amd64.

   The machine is running SMP kernel.

   The machine has 2 on-board Broadcom BCM5721 NICs, which are
 handeled by the bge(4) driver and 4 D-Link DL10050 NICs, which are
 handeled by the ste(4) driver. Machine is targeted for a
 gateway/firewall and will handle a big amount of network traffic.

   It seems the bge(4) driver has severe performance problems (may be
 especially in my configuration). I tried test scp(1) to a remote
 machine, using one of the BCM5721 NICs. The average speed which has
 been reached was 200kBps.

   Just for comparison, when i tryed the same test scp(1), to the
 same remote machine, but using one of the D-Link DL10050 NICs, the
 average speed which has been reached was 10MBps.

   Could someone point me to a good performance tuning document for
 bge(4) handeled NICs, under SMP kernel or at all?

   Thanks in advance!

   Vladimir

So you have 2 gig-E and 4 100tx interfaces on the same PCI bus?  If so 
you're going to run into bus saturation long before you're able to 
max out the throughput on the NICs.

Which isn't to say that 200 kBps isn't a problem, but perhaps you are 
dealing with a bad cable or switchport.

-- 
Thanks,

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


Re: can't connect to cvsup.freebsd.org

2006-12-06 Thread Josh Paetzel
On Tuesday 05 December 2006 16:34, Steven Friedrich wrote:
 but I'm able to connect to cvsup5 and cvsup6.

 The main ftp site says: Cannot connect to data port: Connection
 refused

 This started around the time of the cut-overs.

*default host=cvsup.FreeBSD.org


gimpy# csup /usr/local/etc/ports-supfile 
Connected to 198.104.69.57
Updating collection ports-all/cvs
 Edit ports/LEGAL
...

gimpy# dig a ftp.freebsd.org
...
ftp.freebsd.org.180 IN  A   62.243.72.50
ftp.freebsd.org.180 IN  A   204.152.184.73


gimpy# dig a cvsup.freebsd.org
.
cvsup.freebsd.org.  3535IN  CNAME   n.cwu.edu.
n.cwu.edu.  86335   IN  A   198.104.69.57


My point, in case you don't understand the ouput of all these commands 
is that cvsup.freebsd.org and ftp.freebsd.org are presumably two 
different machines, and it's entirely possible that ftp.freebsd.org 
isn't a cvsup server.

-- 
Thanks,

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


Re: ad0: WARNING - removed from configuration (atacontrol and gmirror relationship?)

2007-11-27 Thread Josh Paetzel
On Tuesday 27 November 2007 01:08:49 pm [EMAIL PROTECTED] wrote:
 This just happened on my server:

 Nov 22 03:21:11 sockeye kernel: ad0: TIMEOUT - WRITE_DMA retrying (2
 retries left) LBA=28892960
 Nov 22 03:21:11 sockeye kernel: ad0: WARNING - removed from configuration
 Nov 22 03:21:11 sockeye kernel: GEOM_MIRROR: Device gm0s1: provider ad0
 disconnected.
 Nov 22 03:21:11 sockeye kernel: GEOM_MIRROR: Request failed (error=6).
 ad0[WRITE(offset=13881704448, length=12288)]
 Nov 22 03:21:11 sockeye kernel: GEOM_MIRROR: Request failed (error=6).
 ad0[WRITE(offset=14795718656, length=2048)]
 Nov 22 03:21:11 sockeye kernel: GEOM_MIRROR: Request failed (error=6).
 ad0[WRITE(offset=770891776, length=16384)]
 Nov 22 03:21:11 sockeye kernel: ata0-master: FAILURE - WRITE_DMA timed out
 Nov 22 03:21:11 sockeye kernel: GEOM_MIRROR: Request failed (error=5).
 ad0[WRITE(offset=14793195520, length=2048)]

 Now the ad0 Master drive no longer exists:

 -su-2.05b$ sudo atacontrol list
 ATA channel 0:
 Master:  no device present
 Slave:  acd0 SONY CD-ROM CDU5212/5YS1 ATA/ATAPI revision 5
 ATA channel 1:
 Master:  ad2 WDC WD800JB-00JJA0/05.01C05 ATA/ATAPI revision 6
 Slave:   ad3 WDC WD400BB-75FRA0/77.07W77 ATA/ATAPI revision 6


 What is the relationship between atacontrol and gmirror?


 Why was the device removed completely?


 Can I simply do this?  (want to be sure as this box is remote)

 gmirror forget data

 atacontrol attach ata0

 gmirror insert data ad0

IDE devices generally aren't hot swappable, so you're going to have to take 
the box down to replace the failed drive (that's why it detached from the 
bus).  Once you do that you can rebuild the gmirror.

-- 
Thanks,

Josh Paetzel

PGP: 8A48 EF36 5E9F 4EDA 5A8C 11B4 26F9 01F1 27AF AECB


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


Re: SSH Must Die

2001-05-12 Thread Josh Paetzel

On Saturday 12 May 2001 18:40, Terry Lambert wrote:
 j wrote:
  On Saturday 12 May 2001 06:24, Terry Lambert wrote:
   This whole ssh B.S. is very annoying.
  
   After an upgrade from 4.2 to 4.3 using a CDROM boot plus
   upgrade menu option, SSH stops working, for no good reason
   (_any_ reason is no good).
 
  You did make the needed additions to /etc/pam.conf, didn't you?

 What additions are necessary between 4.2 and 4.3?  I was
 under the impression that sysinstall was supposed to
 just do the right thing, and don't hassle me?

 If you have a dead chicken I should wave over my keyboard,
 hand it over!  8-).

Make sure you have these lines in /etc/pam.conf
sshdauthsufficient  pam_skey.so
sshdauthrequiredpam_unix.so try_first_pass
sshdsession requiredpam_permit.so

These lines are not in 4.2-rel and they are needed in 4.3-rel.

Have fun.
Josh


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message



Re: Installation Problems on Dell PowerEdge 6100/200

2000-08-08 Thread Josh Paetzel


- Original Message -
From: "Daniel Lang" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Tuesday, August 08, 2000 9:42 AM
Subject: Installation Problems on Dell PowerEdge 6100/200


 Hi,

 we've got a Dell PowerEdge 6100/200 here, which is an older
 SMP server, featuring 4 PPro 200 CPU's two internal AIC7880
 channels and an Adaptec 2940UW PCI controller. One of the
 AIC's is connected to a SCA Backplane that holds 4 disks.

 Now before even having a chance to see if FreeBSD-SMP
 works with this box, I didn't manage to install FreeBSD
 (4.1) correctly. Well, installation seems to go well in
 any attempt:

 - Floppy boots, Kernel finds all ahc's and disks
 - Installation seems to succeed (Partitioning, installation, etc)

 But then, the machine won't boot. It seems to happen, that the
 MBR of the target device (da0, which is the first disk on the
 second controller, channel A of internal AIC's) is found, but
 the next stage of the bootstrapping process cannot be found.
 I played also around using boot0 and installing on other disks,
 this is like what I got:

 Standard MBR and System on da0: - Missing operating system
 boot0 MBR and System on da0:- F1 - *beep* (nothing else)
 boot0 MBR (and old System) on da0, standard MBR and System on da1:
 booting from da0: F1 - *beep*, F5 (disk2) - Missing operating system
 booting from da1: - Missing operating system

 So it seems no boot-block after the MBR can be found.

 I tried: - installing and booting from different disks on internal ahc
  - disabling some of the controllers
  - installing and booting from a disk on the 2940,
as well while disabling the others

 It all had no effect.

 All adaptec's BIOS has Disks  1GB and INT13 enabled (of course the
 BIOS itself is enabled, too)

 Previously Solaris 7/x86 was running on this machine, there
 were no such problems, but we don't really want to run Solaris... :-}

 Any clue ?


If it is worth anything, I tried installing on a poweredge 2450 once and to
make a long story short couldn't get the onboard RAID to work or the SMP to
work.  I hear it got sent back for something else (that wasn't a dell!)

Josh

 Many thanks,
  Daniel
 --
 IRCnet: Mr-Spock  - My name is Pentium of Borg, division is futile, you
 will be approximated. -
 *Daniel Lang * [EMAIL PROTECTED] * +49 89 289 25735 * http://www.leo.org/~dl/*

 --
 IRCnet: Mr-Spock  - May His Shadow fall upon thee -
 *Daniel Lang * [EMAIL PROTECTED] * +49 89 289 25735 * http://www.leo.org/~dl/*


 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-questions" in the body of the message




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: FreeBSD performing worse than Linux?

2001-11-28 Thread Josh Paetzel

On Wed, Nov 28, 2001 at 06:35:48PM +, John Vinters wrote:
 
 I've (reasonably) recently installed 4.3-Release on a system running
 Samba and a few light telnet apps, and noticed similar performance
 problems.
 
 The SMB sessions would randomly change speed, and telnet sessions would
 suffer from occasional  hesitation (this is on a Dual PIII-700 MHz
 machine with 1 Gb of RAM, which is currently very lightly loaded).
 
 I managed to track the problem down to the duplex settings on both the
 Ethernet cards (AT-2500 TX, Realtek 8139 based, AFAIK) and the 10/100
 Switch.  Forcing both the cards and the switch to particular settings
 cured the problem, and lead to a massive performance increase.
 
 FTP seems to be particularly badly affected by the constant collisions
 (causing backoff).  The problem can be tricky to find as the switch
 wasn't perceptably showing collisions on the collision LED, but viewing
 the switch stats showed a different story!
 
 I've noticed similar problems with Linux and certain cards (it was a
 while ago).
 
 
 John Vinters
 [EMAIL PROTECTED]
 

Well, I am seeing dismal ftp performance on my 4.x boxes.  I have a 
network of 4 machines, three of which are running -STABLE from Nov 
22.  The other machine is running NetBSD 1.5.2 Release.  One of the 
FreeBSD machines has a  base 10 cards in it and has reasonable 
performace with ftp transfer rates around 1.1Megs/sec.  The NetBSD 
machine is a sparcstation 10 with an onboard intel base 10 adapter, 
and it too sees reasonable ftp performance.  The other two -STABLE 
boxes have 100tx cards in them.  One is a Linksys LNE100TX, and the 
other is an intel Pro 10/100B/100+.  The hub for this network is an 8 
port SOHOware autosensing affair.  Both of the 100 cards 
auto-negotiate to 100tx half-duplex.  I can get appoximately 
1.5Megs/sec out of them using ftp.  I have tried swapping cables, 
swapping ports, and replacing the hub with a crossover cable and 
manually configuring the cards for either full or half duplex 
operation.  None of these steps makes any difference at all.  I can 
reliably duplicate my transfer speeds on a 600 meg file with a std. 
deviation of less than a half a second no matter what network 
configuration I use.  My next step will be to try some different NICs, 
but I don't have anything here that is 100tx based to swap with.  I 
have gotten proper transfer rates out of these machines in the past, 
but I don't remember if the network cards have changed since then.  I 
rarely move large files around at all, and so only looked into this as 
a curiosity when seeing this thread.  I also intend to try some NFS 
mounts out to see if this is a protocol issue or not.

Josh


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message



Re: FreeBSD performing worse than Linux?

2001-11-29 Thread Josh Paetzel

On Thu, Nov 29, 2001 at 10:09:58AM -0700, Nate Williams wrote:
  I started noticing some TCP weirdness when I moved my bandwidth
  stats site from my office to my colo facility last week.  The colo
  is five miles away by road and 1200 miles away by network.  Netscape
  would stop for seconds at a time while loading the graph images but
  there was no consistency.  Worked properly sometimes and sometimes
  not.
 
 Thanks for the much more detailed bug report vs. mine.  Can you try
 disabling delayed acks to see if that helps, per another poster's
 response to this thread?
 
 sysctl net.inet.tcp.delayed_ack=0
 

I tried this out and it made no difference whatsoever.  I also tried 
out moving the same file via NFS and get transfer times that are 
within 5 seconds of the FTP times.  I am beginning to suspect that I 
have a hardware issue here. 

Josh


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message



Re: FreeBSD performing worse than Linux?

2001-11-29 Thread Josh Paetzel

On Fri, Nov 30, 2001 at 01:03:54AM +0100, Pierre Beyssac wrote:
 On Thu, Nov 29, 2001 at 12:42:34AM -0500, John Capo wrote:
  sent.  find / -print | dd obs=1 will screw up within a few seconds
  and stay that way.  Netstat in another ssh session shows data ready
  to go:
 
 Hmm, some ssh versions tend to hang randomly on lossy links (in the
 protocol perhaps, but I haven't ever tried to investigate this).
 
 Could you try the same in a telnet or rsh connection? I bet it will
 work.
 
 Pierre

This gives me the same 1.5megs/sec I am getting with ftp.  Doesn't 
matter whether I use ssh or telnet. 

Josh


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message



Re: dhcpd problem

2001-12-06 Thread Josh Paetzel

On Thu, Dec 06, 2001 at 07:57:02AM +, Mike D wrote:
 I'm having trouble configuring my dhcpd.
 
 This is the config file I've nocked up:
 
  start config file --
 default-lease-time 3600;
 max-lease-time 9;
 ddns-update-style ad-hoc;
 option subnet-mask 255.255.255.0;
 option broadcast-address 192.10.10.255;
 option domain-name-servers 194.168.8.100,194.168.4.100;
 option domain-name dolphintime;
  end config file --
 
 When I try to start dhcpd (by running /usr/local/etc/rc.d/dhcpd) I get the 
 following error:
 
  start error message --
 No subnet declaration for xl1 (80.x.x.x).
 ** Ignoring requests on xl1.  If this is not what
you want, please write a subnet declaration
in your dhcpd.conf file for the network segment
to which interface xl1 is attached. **
 
 No subnet declaration for xl0 (192.10.10.4).
 ** Ignoring requests on xl0.  If this is not what
you want, please write a subnet declaration
in your dhcpd.conf file for the network segment
to which interface xl0 is attached. **
 
 Not configured to listen on any interfaces!
  end error message --

DHCPD wants to know about your subnets.  The way to tell it about them 
is with a section like this:

subnet 192.10.10.0 netmask 255.255.255.0 {
  range 192.10.10.10 192.10.10.90;
}

There's more you can do than that, but I think seeing this will ring 
your bell, especially if you are looking in the man pages.

Josh

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message



Re: Multilink DSL

2001-12-20 Thread Josh Paetzel

On Thu, Dec 20, 2001 at 10:48:10AM -0500, Ted Sikora wrote:
 Anyone know how or a link for setting up MP 'multilink' PPPoe DSL on
 FreeBSD. I have PPPoe on FreeBSD-STABLE with 2 cards and DSL lines. How
 can I connect the second modem on dc1 and join the packets to dc0?
 
 --
 Ted Sikora
 [EMAIL PROTECTED]
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-hackers in the body of the message

Well, for starters, you are going to need support on your ISP's end of 
things to make that go.  Do you have it?

Josh


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message



Re: Discussion on the future of floppies in 5.x and 6.x

2004-01-09 Thread Josh Paetzel
  There are several documents linked off of http://www.freebsd.org/releng
  that describe how to build a release.  It's not nearly as arcane of a
  process as it used to be 5 years ago.  The biggest barrier to entry is
  probably disk space.  You'll need a good 5GB free to hold the CVS repo,
  chroot environment, and resulting bits.
 
 Well, I've got the CVS repo, though boy, has *THAT* ever grown since I
 built this system; I had to trim it down to only src and ports, and even
 so:
 /dev/da1s1e 2032623 1769089 10092595%/usr/cvs
 
 Of course, I left out the ports and docs parts of the release last time I
 tried (which was in fact about 5 years ago ;), though I had all kinda of
 troubles with parts of THAT, too.  But still, I don't have even a tenth
 that much hard drive space around.
 
 
  Yes, to build the floppies you need to build most of the release, but
  once you've built the release, you can back-step and rebuild the
  floppies at will.
 
 And building the whole release is quite an ordeal on a Pentium Pro  :)
 
 
 Still, I'm willing to donate some time and brain to the problem, since
 apparently I kinda care about it.  It seems to me that the probing
 problem above is the biggest problem from a real coding POV; the rest is
 mostly just a whole heck of a lot of implementation, and inconvenience
 from the usability standpoint.  That's a breaking point.
 
 

I'll donate the disk space and CPU time if you want to run with this.  I 
have an interest in keeping floppies around, but not much ability to help out.
  
Josh Paetzel


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


Re: IPDIVERT, having issues? [Moved to -questions]

2002-08-18 Thread Josh Paetzel

On Sun, 2002-08-18 at 06:20, Devon Stark wrote:
 Greetings!
 I am having a problem trying to get IPDIVERT to take..
 I have setup my kernel conf to include the following lines
 
 options IPFIREWALL
 options IPDIVERT
 
 I have the nic configured and running just fine, for both local LAN and for internet 
(both of my NICs are plugged into the same switch for now)
 
 My /etc/rc.conf has 
 gateway_enable=YES
 firewall_enable=YES
 natd_enable=YES
 
 Every time I boot the server I get a message saying that IP Packet filtering is 
enabled, along with any other configuration I specified (logging and such), but 
divert is always set to disabled!?
 I have gone to the point of building the kernel with '-DIPDIVERT' and still getting 
the same results...
 The main effect of this problem is of course that I get an error when I try to apply 
the following rule to my firewall
 
 'ipfw add divert natd all from any to any via fxp0'
 The error is...
  
 ip_fw_ctl: invalid command
 ipfw: getsockopt(IP_FW_ADD): Invalid argument
 
 I have checked and natd is in the services list and seems to be configured properly.
 
 I have been searching for the answer for about 3 days now with little luck finding 
the answer. 
 
 The only thing I can think of is that there is some other kernel option that I am 
enabling that is causing this problem, or perhaps that there is something that I am 
missing?
 
 I have included my config files here for review... 
 
 Kernel config file (I striped out all of the comments for the sake of this post)
 
 machine i386
 cpu I686_CPU
 ident   THE-SERVER
 maxusers256
 options MATH_EMULATE
 options INET
 options FFS 
 options FFS_ROOT
 options SOFTUPDATES 
 options UFS_DIRHASH 
 options MFS 
 options MD_ROOT 
 options NFS 
 options NFS_ROOT
 options MSDOSFS 
 options CD9660  
 options CD9660_ROOT 
 options PROCFS  
 options COMPAT_43   
 options SCSI_DELAY=1000 
 options UCONSOLE
 options USERCONFIG  
 options VISUAL_USERCONFIG   
 options KTRACE  
 options SYSVSHM 
 options SYSVMSG 
 options SYSVSEM 
 options P1003_1B
 options _KPOSIX_PRIORITY_SCHEDULING
 options ICMP_BANDLIM
 options KBD_INSTALL_CDEV
 options IPFIREWALL
 options IPDIVERT
 options IPFIREWALL_FORWARD
 options IPFIREWALL_VERBOSE
 options IPFIREWALL_VERBOSE_LIMIT=50
 options BRIDGE
 options IPSTEALTH
 options TCP_DROP_SYNFIN
 options SMP 
 options APIC_IO 
 device  isa
 device  eisa
 device  pci
 device  fdc0at isa? port IO_FD1 irq 6 drq 2
 device  fd0 at fdc0 drive 0
 device  ata0at isa? port IO_WD1 irq 14
 device  ata1at isa? port IO_WD2 irq 15
 device  ata
 device  atadisk 
 device  atapicd 
 device  atapifd 
 options ATA_STATIC_ID   
 device  ahb 
 device  ahc 
 device  amd 
 device  isp 
 device  ncr 
 device  sym 
 options SYM_SETUP_LP_PROBE_MAP=0x40
 device  adv0at isa?
 device  adw
 device  bt0 at isa?
 device  aha0at isa?
 device  aic0at isa?
 device  scbus   
 device  da  
 device  sa  
 device  cd  
 device  pass
 device  asr 
 device  atkbdc0 at isa? port IO_KBD
 device  atkbd0  at atkbdc? irq 1 flags 0x1
 device  psm0at atkbdc? irq 12
 device  vga0at isa?
 pseudo-device   splash
 device  sc0 at isa? flags 0x100
 device  npx0at nexus? port IO_NPX irq 13
 device  apm0at nexus? disable flags 0x20 
 device  sio0at isa? port IO_COM1 flags 0x10 irq 4
 device  sio1at isa? port IO_COM2 irq 3
 device  ppc0at isa? irq 7
 device  ppbus   
 device  lpt 
 device  miibus  
 device  fxp 
 pseudo-device   loop
 pseudo-device   ether   
 pseudo-device   pty 
 pseudo-device   md  
 pseudo-device   bpf 
 device  

Re: Interesting sysctl variables in Mac OS X with hw info

2002-03-15 Thread Josh Paetzel

On Wed, Mar 13, 2002 at 08:46:46PM -0800, Terry Lambert wrote:
 Matthew Emmerton wrote:
 This was actually discussed a while back (a month or two ago).

 It got really bogged down when someone pointed out that
 they were running CPUs with different clock rates in their
 SMP box, just to see what the net effect would be.  THe
 problem was, of course, which one do you report, when the
 numbers don't match exactly, and/or how do you report both
 (or N)?
  
  I thought it was a real bad thing to run CPUs in SMP systems at different
  clock rates.  In fact, I never thought it was possible.  I know I can't on
  my old 2-way P166 box, but things have changed a lot since '91.
 
 It depends on the stepping, and that the external interfaces
 are all the same (voltage, clock speed for memory and I/O,
 etc.).
 
 PIII's can run this way, for sure.

This is a perfect example of, Just because you can do something, 
doesn't mean you should.

I wouldn't see anything wrong with grabbing the clock frequency of the 
first cpu in the system and noting in the man page that if you have 
multiple cpus and you aren't running them at the same frequency, then 
the reported value is applicable only to the first cpu.

This would save a ton of time in implementing Jordan's ideas, at the 
cost of not being able to deal correctlywith a situation that 
(hopefully) isn't too common in the field.  The other less tangible
 disadvantage to my suggestion is that it takes us one step further in our 
single-cpu-centric userland, ala top, uptime, and so forth only 
displaying stats for one cpu.

Josh
 
  If you want to find out who's doing it, you only need to search
 the SMP list archives; it wasn't important enough for me to commit
 the message to memory, I only remember the fact that someone was
 doing it successfully.
 
 -- Terry
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-hackers in the body of the message

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message



Re: Interesting sysctl variables in Mac OS X with hw info

2002-03-15 Thread Josh Paetzel

On Fri, Mar 15, 2002 at 10:27:22AM -0800, Terry Lambert wrote:
 Josh Paetzel wrote:
  This is a perfect example of, Just because you can do something,
  doesn't mean you should.
  
  I wouldn't see anything wrong with grabbing the clock frequency of the
  first cpu in the system and noting in the man page that if you have
  multiple cpus and you aren't running them at the same frequency, then
  the reported value is applicable only to the first cpu.
  
  This would save a ton of time in implementing Jordan's ideas, at the
  cost of not being able to deal correctlywith a situation that
  (hopefully) isn't too common in the field.  The other less tangible
   disadvantage to my suggestion is that it takes us one step further in our
  single-cpu-centric userland, ala top, uptime, and so forth only
  displaying stats for one cpu.
 
 Incorrect information is always worse than no information.
 
 -- Terry

Yeah, you're right.  Six hours of contemplation and I've changed my 
tune.  If it's going to be done, should be done right. 

Josh



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message



Re: idprio

2002-03-31 Thread Josh Paetzel

On Tue, Mar 26, 2002 at 09:21:57PM -0800, Terry Lambert wrote:
 Alfred Perlstein wrote:
   But if system calls aren't preempted under what circumstances can a
   process hold a vnode lock and then be usurped for processor?
  
  While sleeping for IO.
 
 Ideal systems release and reacquire locks when they are going
 to suspend for a long time (Djikstra's Banker's Algorithm).
 
 -- Terry
 

Of course, the downside of this is that a low priority process that 
needs a lot of resources may never be able get all of the resources 
that it needs.  :)

Josh

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message



Re: incorrect information in ata(4)?

2002-03-31 Thread Josh Paetzel

On Fri, Mar 29, 2002 at 03:01:04PM +1100, Andrew wrote:
 
 
 On Thu, 28 Mar 2002, Eric Melville wrote:
 
  staralfur% sysctl kern.osrevision
  kern.osrevision = 199506
 
 snip
 
  I couldn't tell you what it means, though.
 
 That both OSs are based on 4.4BSD-Lite2 I believe.
 
 Andrew
 

Well isn't NetBSD as well?

===root@sun ('tty') /home/jpaetzel - sysctl kern.osrevision
kern.osrevision = 105000200

===root@sun ('tty') /home/jpaetzel - uname -a
NetBSD sun.vladsempire.net 1.5.2 NetBSD 1.5.2 (SUN) #0: Sat Feb  9 
15:20:35 CST 2002 
[EMAIL PROTECTED]:/usr/src/sys/arch/sparc/compile/SUN sparc

Josh



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message



Re: ATAPI dvdreader always fails on a particular DVD movie title

2008-01-19 Thread Josh Paetzel
On Saturday 19 January 2008 12:30:06 pm Joshua Isom wrote:
 On Jan 19, 2008, at 10:03 AM, Doug Barton wrote:
  Yuri wrote:
  I tried to make a backup copy of one DVD that I own and 'dvdbackup'
  always fails at a particular point.
 
  Would the dvds in question happen to be Sony movies? If so a web
  search might be useful to you.
 
  Doug

 Not only that, but do you actually see a DVD logo?  Disney movies use
 Disney DVD which is incompatible with the DVD specification.


Sony isn't the only maker of DVDs that has goo in them that will confuse 
libdvdcss.  

In a nut shell, in many places it's illegal to use 'nonauthorized' tools (like 
libdvdcss) to decrypt DVDs for any purpose (including playback).  On top of 
that, the underlying tool used by nearly everything that reads movie DVDs on 
FreeBSD (libdvdcss) is unmaintained by anyone upstream, as time goes on more 
and more dvds are released that it either can't decrypt or are able to choke 
it.


-- 
Thanks,

Josh Paetzel (wearing libdvdcss port maintainer hat)

PGP: 8A48 EF36 5E9F 4EDA 5A8C 11B4 26F9 01F1 27AF AECB


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


Re: Scripting sysinstall(8) to create use multiple slices on a disk?

2010-03-05 Thread Josh Paetzel
On Friday 05 March 2010 07:01:00 John Baldwin wrote:
 On Thursday 04 March 2010 4:33:29 pm David Wolfskill wrote:
  For reasons that may well be idiosyncratic, I like to set up FreeBSD
  machines to have at least 2 bootable slices -- e.g., one can act as a
  fallback if an attempted software upgrade proves to have been ill-timed.
  
  In the past, I've done this manually; while a bit tedious  fairly
  target-rich with opportunities for human error, it's something that is
  typically done infrequently (i.e., once) in the life of a machine (or at
  least its boot drive).
  
  At work, the IT folks use a scripted sysinstall(8) to set machines up;
  to increase the probability that I'll be able to get 3 special
  machines set up the way I want, I'm trying to set up a sysinstall config
  file to make this as painless as possible.
  
  I managed to get a copy of the config script IT uses, so I had a
  starting-point ... but they were setting the machines up with
  
  partition=exclusive
  
  which doesn't seem like a good choice for what I'm doing.  :-}
  
  
  After my first attempt failed, I poked around on the Net  found
  http://www.nntpnews.net/f2458/what-proper-install-cfg-configuring-multip
  le-
 
 slices-4387807/,
 
  (dated 18-11-08, 10:40 PM ), in which Peter Steele describes something
  
  similar to what I was about to try next, and writes:
  | My intent here is to create three slices-one 6GB in size, another 1GB
  | in size, and the third sized to consume the remaining free space. When
  | I run this through sysinstall, it complains that it can't find the
  | space for the partitions. It even complains that it can't find any
  | free space. Because the slices don't get created, the subsequent label
  | assignments fail as well. What is the proper commands for creating
  | multiple slices in install.cfg?
  
  In a foillowup, he writes:
  | After a lot of experimenting, my impression is that sysinstall simply
  | doesn't support multiple slice installations. It works to a point, but
  | I get some unexpected errors, e.g.
  | 
  | Unable to make device node for /dev/ad0s1a in /dev
  
  which doesn't seem very encouraging.
  
  
  Would someone please either confirm the limitation or provide a
  suitable excerpt from a sysinstall config script to demonstrate
  that it is actually possible?  (Or show me where it's spelled out in the
  man page)
  
  (I'm using 7.x sysinstall, if that matters.)
 
 If you are doing a fully scripted install you may be better off just using
 a dedicated shell script to format your disks and mount them and then use
 the various *-install.sh scripts from the release distributions to install
 the code.  You could still do this via sysinstall by sticking your shell
 script in /stand in the MFS root and having your sysinstall script just
 run that script. You might want to build a custom mfsroot to add some more
 useful tools though.
 
 I really think sysinstall needs to support a disk backdoor whereby the
 user can either manually partition disks and then mount them at /mnt (or
 have a script do it), and tell sysinstall to just skip the disk stuff and
 assume /mnt is mounted.

David,

I second the ditching sysinstall for a shell script idea.  A shell script that 
replaces sysinstall is nearly as short as the install.cfg and a lot easier to 
figure out.  I've written a half dozen auto installers for FreeBSD, from 
trivial to complex and would be more than willing to help you get something 
set up.  I can send you code if you want as well.

-- 
Thanks,

Josh Paetzel
FreeBSD -- The power to serve


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


Re: Scripting sysinstall(8) to create use multiple slices on a disk?

2010-03-06 Thread Josh Paetzel
On Saturday 06 March 2010 02:41:30 Garrett Cooper wrote:

 (Attempts to avoid shoe flying in his direction from randi@ :/),
 
 FWIW, sysinstall(8) is a good starter tool and it has a lot of the
 information that you need in order to complete an install (especially
 if you're doing it from scratch), but the amount of effort for using
 sysinstall(8)'s install.cfg, etc has the greater potential to change
 in the future when compared with a shell scripted method which is less
 likely to change; granted gpart vs fdisk is in transition, but the
 number of steps and the simplicity required to get everything up and
 going is trivial, and I did so in  100 lines of bourne shell.
 
 I'd be happy to share my custom script if desired as well to provide
 you a general idea of what could be done to solve your problem.
 
 Cheers,
 -Garrett

One of my main issues with using sysinstall comes from an intersection of it's 
lack of documentation, and the way it can arbitrarily change over time.  For 
instance, this week I was working on an install for a number of machines that 
had to be imaged with an early 7.x version of FreeBSD, and were specified to 
be installed with distSet${OBFUSICATED}  In order to determine what 
distSet${OBFUSICATED} installs on 7.${EARLY} involves either installing a 
system via sysinstall and noting what it installs, or reading the source code.  
Where this becomes an issue is sysinstall changes over time, 
distSet${OBFUSICATED} is not necessarily the same between 7.${EARLY} and say 
8.0.  Since there is no documentation you either end up tracking the changes 
to sysinstall, or sorting it out at upgrade time.

I'd also like to mention John saying you can build a custom mfsroot to use 
additional tools during install...I go a different tack on this.  I'm a huge 
fan of python, and like to use it for installers.  Rather than build a custom 
mfsroot with python what I prefer to do is build a chroot that the target 
machine boots diskless off.  Then I chroot into that directory and install 
whatever tools I want using ports/packages.  I find that getting FreeBSD to 
boot diskless is so easy that I've had it accidentally happen more than once 
when I wanted something else to happen.  Installing ports in a chroot is also 
pretty trivial.  Building a custom mfsroot has a bit of a learning curve with 
a fairly expensive trial and error penalty.

At any rate.  There are a lot of compelling reasons to not use sysinstall for 
automated installs.  And while there are compelling reasons to use sysinstall 
for this task, most of them involve things like I'm a masochist. or It was 
there so I thought I'd use it.

-- 
Thanks,

Josh Paetzel
FreeBSD -- The power to serve


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


txt-sysinstall scrapped

2010-11-05 Thread Josh Paetzel
It's been incredibly busy for us in iXsystems land, with a lot of irons in the 
fire.

One of the many things we've been working on is a new installer.  Several 
months ago pc-sysinstall was imported into HEAD from the PC-BSD project.  

pc-sysinstall is a fine tool, and very useful as the backend for doing 
scripted installs.  If you're using scripted sysinstall I recommend you check 
it out, it's a lot easier to use and configure than sysinstall, the 
documentation is much better, and reasonable requests for functionality can 
and will be brought in.

This is all fine and good, but without a front end to generate the config 
files pc-sysinstall needs it's not much use to an end user for doing installs.  
We (and by we I mean the forces at iXsystems) have been working on txt-
sysinstall, which is a front end for pc-sysinstall using curses and dialog to 
generate a pc-sysinstall config file from user input.  What we've encountered 
is that doing disk configuration in dialog isn't possible, and we started down 
the road of using cursesbut we already have a curses and dialog based 
installer, and wouldn't it be neat if we could use the disk configuration tool 
we are writing for FreeNAS, too bad it's a web app.

But if the installer just launched a web server.

Ok, wait a minute, that couldn't work...how would you configure networking?  
Oh wait, that's already solved in FreeNAS, before you access the system you 
use a console/CLI app to configure the network.  Ok, but people do installs 
over serial portsoh wait, you could run lynx from the console too...

We quickly realized that the objections we could come up with were easily 
overcome, and the more we talked to people here at MeetBSD the more we 
realized it was a viable (and good) idea.  People quickly came up with 
improvements.

This gets us the best of both worlds.  Want a super fancy GUI installer, just 
hit the box with firefox or whatever from a full desktop, want a text 
interface that's simple, need low bandwidth, running over a serial port, use 
the embedded lynx browser.  Installing in a remote vm/cloud, just configure 
the ip and hit it with a browser (yes, we're dreaming up ways to do it over 
ssl and such)

I'll do a better write-up very soon, I'm pretty tired now and have a long 
weekend looming, but just wanted to get the word out.

Just to give credit where credit is due, this all started with Warner Losh 
saying, Can you listen to a crazy idea I had?   It didn't take long to 
realize that it wasn't crazy, it was a stroke of genius.

Secondary props go to Philip Paeps and Kris Moore for implementation details, 
Matt Olander for recognizing the benefits and approving the change in focus, 
John Hixson for the priceless look on his face when he realized we were 
serious about changing (He's done the bulk of the work on txt-sysinstall) the 
random NetBSD user here at MeetBSD (sorry I don't know his name) who said it 
was a horrible idea because it would bloat the installer way too much (I'm 
still laughing at that, he was saying something about floppies too, I guess 
we're locking out people using 386's or something.) and quite a few other 
people who are too countless to mention but offered random advice or 
encouragement.
 
-- 
Thanks,

Josh Paetzel
FreeBSD -- The power to serve


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


Re: txt-sysinstall scrapped

2010-11-05 Thread Josh Paetzel
On Friday, November 05, 2010 11:48:27 pm Garrett Cooper wrote:
 
 Just to add to that (because I do find it a novel idea), 1) how
  are you going to properly prevent man in the middle attacks (SSL, TLS,
  etc?), and 2) what webserver would you use?
 I bring up the former item because I wouldn't want my data going
  unencrypted across any wire, and what BSD compatible web servers did
  you guys have in store and who would maintain the server, and what
  kinds of vulnerabilities would you be introducing by adding a service
  which would be enabled by default at runtime?
 
 Sorry -- missed the SSL note. Other questions still outstanding :).
 
 Thanks!
 -Garrett

Without putting much analysis into it, we talked about using lighttpd, which 
is BSDL.  As far as another service, it would be running for the install only 
which is in most circumstances something that happens locally.

-- 
Thanks,

Josh Paetzel
FreeBSD -- The power to serve


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


Re: LSI mps(4) driver issues with PIKE 2008/IMR (LSI SAS2008)

2012-03-27 Thread Josh Paetzel
On 03/27/2012 10:54, Desai, Kashyap wrote:
 
 
 -Original Message-
 From: owner-freebsd-s...@freebsd.org [mailto:owner-freebsd-
 s...@freebsd.org] On Behalf Of Kenneth D. Merry
 Sent: Friday, March 23, 2012 3:49 AM
 To: Jake Smith
 Cc: freebsd-s...@freebsd.org; freebsd-hackers@freebsd.org; freebsd-
 hardw...@freebsd.org
 Subject: Re: LSI mps(4) driver issues with PIKE 2008/IMR (LSI SAS2008)

 On Thu, Mar 22, 2012 at 16:24:16 +0100, Jake Smith wrote:
 Hello,

 I am trying to get the latest mps(4) driver in FreeBSD 9-STABLE
 working
 with am LSI SAS2008 variant from ASUS, they call it PIKE 2008/IMR.
 Link
 http://www.asus.com/Server_Workstation/Accessories/PIKE_2008IMR/

 From what I can see this card should be compatible with the mps(4)
 driver MFC'd to 9-STABLE about 6 weeks ago.

 # uname -a
 FreeBSD xxx 9.0-STABLE FreeBSD 9.0-STABLE #3 r233304M: Thu Mar 22
 12:53:17 GMT 2012 root@xxx:/usr/obj/usr/src/sys/GENERIC  amd64

 Revision: 233304

 Initially the card is not seen at all by the driver, however pciconf
 shows us why that is.

 mps0@pci0:2:0:0:class=0x010700 card=0x843b1043 chip=0x00731000
 rev=0x03 hdr=0x00
 vendor = 'LSI Logic / Symbios Logic'
 device = 'MegaRAID SAS 9240'
 class  = mass storage
 subclass   = SAS

 It seems on other models of LSI SAS2008 the chip device ID is 0x0072,
 however for some reason this card has 0x0073. So I patched the mps(4)
 driver and recompiled.

 diff -ruN mps.orig/mpi/mpi2_cnfg.h mps/mpi/mpi2_cnfg.h
 --- mps.orig/mpi/mpi2_cnfg.h2012-03-22 14:50:53.0 +
 +++ mps/mpi/mpi2_cnfg.h 2012-03-22 14:52:23.0 +
 @@ -416,7 +416,8 @@

  /* SAS */
  #define MPI2_MFGPAGE_DEVID_SAS2004  (0x0070)
 -#define MPI2_MFGPAGE_DEVID_SAS2008  (0x0072)
 +#define MPI2_MFGPAGE_DEVID_SAS2008_1(0x0072)
 +#define MPI2_MFGPAGE_DEVID_SAS2008_2(0x0073)
  #define MPI2_MFGPAGE_DEVID_SAS2108_1(0x0074)
  #define MPI2_MFGPAGE_DEVID_SAS2108_2(0x0076)
  #define MPI2_MFGPAGE_DEVID_SAS2108_3(0x0077)
 diff -ruN mps.orig/mps_pci.c mps/mps_pci.c
 --- mps.orig/mps_pci.c  2012-03-22 14:48:41.0 +
 +++ mps/mps_pci.c   2012-03-22 14:51:59.0 +
 @@ -99,7 +99,9 @@
  } mps_identifiers[] = {
 { MPI2_MFGPAGE_VENDORID_LSI, MPI2_MFGPAGE_DEVID_SAS2004,
 0x, 0x, 0, LSI SAS2004 },
 -   { MPI2_MFGPAGE_VENDORID_LSI, MPI2_MFGPAGE_DEVID_SAS2008,
 +   { MPI2_MFGPAGE_VENDORID_LSI, MPI2_MFGPAGE_DEVID_SAS2008_1,
 +   0x, 0x, 0, LSI SAS2008 },
 +   { MPI2_MFGPAGE_VENDORID_LSI, MPI2_MFGPAGE_DEVID_SAS2008_2,
 0x, 0x, 0, LSI SAS2008 },
 { MPI2_MFGPAGE_VENDORID_LSI, MPI2_MFGPAGE_DEVID_SAS2108_1,
 0x, 0x, 0, LSI SAS2108 },

 After reboot it now loads the mps(4) module and attempts to init the
 card but fails.

 # dmesg | grep mps
 mps0: LSI SAS2008 port 0xd800-0xd8ff mem
 0xfbd7c000-0xfbd7,0xfbdc-0xfbdf irq 16 at device 0.0 on
 pci2
 mps0: Doorbell failed to activate
 device_attach: mps0 attach returned 6

 From this point I'm stuck on what to try next, google does not provide
 any answers for this situation. Does any one have any advice or ideas
 as
 to why this is not working?
 I am able to provide ssh access to the server if any one wants to log
 on and have a look at it.

 In looking at the specs, that card supports RAID-5 and RAID-50.  That
 means
 it isn't a SAS card supported by mps(4), but rather a MegaRAID card.
 
 This is Megaraid card. And it should not be supported by mps. Again, Just 
 adding 0x73 in your pci list in mfi driver will not solve your problem.
 Please Check with Megaraid FreeBSD drivers.
 
 ~ Kashyap
 

 It should be supported by mfi(4).  Try adding the PCI ID to that
 driver and see if that works.  Or you can grab the driver from the
 head_mfi branch, it looks like it already supports that card.  Here's
 the
 mfi_pci.c file, you can see the PCI ID in there:

 http://svnweb.freebsd.org/base/projects/head_mfi/sys/dev/mfi/mfi_pci.c?r
 evision=232888view=markup

 Ken
 --
 Kenneth Merry
 k...@freebsd.org

The FreeBSD mfi will not support that card.  The LSI mfi will, but they
aren't done with it as far as I know (spoke with their driver team a few
weeks ago)

The slightly riskier option is to flash the card with IR firmware for a
9211, the MegaRAID component of that card is purely software and the
underlying hardware is supported by mps.  Of course a firmware flash
gone bad will turn it into an expensive chunk of fiberglass, but if you
google around you'll find people who have done so successfully.


-- 
Thanks,

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