similar to: Problem during "make" with the devel version R-2.3.0 under Sun OS

Hello, I am working on an unix SunOS machine ( sun4u sparc) and since the last release of R -R version 2.5.0 (2007-04-23) - , I have got troubles during the execution of batch command. For example with the instruction file multic.in >cat multic.in install.packages("multic","/bge/penel/R_install/R_2.5.0/lib/R/library",repos="http://cran.at.r-project.org")

Hi, between March 16 and now, bge on a Sun X2200 stopped working, turning off msi (via hw..pci.enable_msi=0) got it working again. I tried first replacing bge with an older version but that did not help. please advice :-) Danny

I opened a bug report earlier today but it doesn''t seem to have been added to the bugs database. I''m posting here in case one of the Crossbow developers might see it and confirm this behavior. Description Duplicate packets are generated whenever an aggregate is introduced into the network configuration. We''ve ruled out switch ports and physical bge interfaces as

Hello! I have Compaq DL360G2 with Broadcom BCM5701 Gigabit Ethernet and FreeBSD 5.1R installed. There are no problems if I use bge as usual network card, but when I try to use 802.1Q vlans, I can't receive (only receive, sending is ok) packets more then 1456 bytes! What is the problem? BGE driver, VLAN driver or my network configuration? Best wishes, Boris

Hi. I got this on today's RELENG_6 with Broadcom BCM5722 A0, ASIC rev. 0xa200. >From dmesg (bge related): bge0: <Broadcom BCM5722 A0, ASIC rev. 0xa200> mem 0xe8400000-0xe840ffff irq 16 at device 0.0 on pci2 bge0: firmware handshake timed out, found 0x4b657654 bge0: firmware handshake timed out, found 0x4b657654 bge0: EEPROM read timed out bge0: failed to read EEPROM device_attach:

Hi, I'm having lots of difficulties with BCM5719, which is the default network card of HP Proliant DL 360 G8 servers. I can get a few ping replies before I get a couple of these: bge0: watchdog timeout -- resetting bge0: watchdog timeout -- resetting Then everything hangs. Can not log in using ssh.

I have a back end which has both scalar and vector registers that alias each other. I'm having a problem generating the ISel from tablegen that appears only when a vector register class is declared to contain integer vectors. At that moment tablegen doesn't seem to be able to infer integer types in patterns that it was able to before, but I'm not clear on why that's the

Dear All, I have a FreeBSD box running 5.4-RELEASE-p8. Two interfaces: fxp0 - internet, SKA4 internal interface fxp0: <Intel 82559 Pro/100 Ethernet> bge0 - internal with 30 vlans on it, old bge Gigabit 64/32 PCI-2.1 adapter. bge0: <Altima AC1002 Gigabit Ethernet, ASIC rev. 0x105> Firewall is pf with about 5000 rules. A week ago it was working just properly, but after adding more RAM

How do I create a vnic that represents the factory assigned MAC address of my physical nic? The bge device in my system (x2100) appears to support 4 MAC addresses. The driver reserves the first as the ''primary/default'' address and allows manipulation of the other three via the MAC_CAPAB_MULTIADDRESS interface. I''d like to use vnics on this system, as I have Xen guest

On Sun, 22 Apr 2007, Christopher Lamb wrote: > I have a back end which has both scalar and vector registers that > alias each other. I'm having a problem generating the ISel from > tablegen that appears only when a vector register class is declared > to contain integer vectors. At that moment tablegen doesn't seem to > be able to infer integer types in patterns that it was

I'm trying to understand the newbus and acpi interactions on this Dell R620 that result in the Broadcom adapter board being probed "backwards" or just plain out of order in comparison to the connector layout and the linux tg3 driver. We seem to be detecting PCI0:2:0 before PCI0:1:0. This seems odd to me. When I replace the broadcom daughter card with an intel daughter card, this

Hi, this server, a Dell R720 has 4 bge on board, Broadcom NetXtreme Gigabit Ethernet, ASIC rev. 0x5720000 bge0: APE FW version: NCSI v1.1.7.0 bge0: CHIP ID 0x05720000; ASIC REV 0x5720; CHIP REV 0x57200; PCI-E miibus0: <MII bus> on bge0 ... I have connected the ethernet to port labeled 0, but it appears as bge2, how can this be corrected? thanks, danny

I just BFU''ed up to B61 and started to play with IP Instances. I''m having trouble making my zone happy: root at aeon zones$ zoneadm -z testing1 boot zoneadm: zone ''testing1'': WARNING: unable to hold network interface ''skge0''.: Invalid argument root at aeon zones$ dladm show-dev nge0 link: up speed: 100Mb duplex: full

Dear R developers I am currently working on the seqinR package. The seqinR package allows a remote access to biological databases via a socket connection. We are using the functions socketConnection, writeLines and readLines to open the socket, send request to the server and receive response from the server respectively. Recently, a new function implemented in the socket server allows

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm trying to run a QEMU VM on top of a FreeBSD 7.x server ... I've tried the exact same setup on my desktop, using 192.168.1.x and an fxp device, and it all works perfectly, but as soon as I do this on another machine on a public IP, I'm not getting any routing, I can't even ping it from the same machine ... My first thought was

The log message for revision 122213 says: > Change the X86 backend to stop using the evil ADDC/ADDE/SUBC/SUBE nodes (which > their carry depenedencies with MVT::Flag operands) and use clean and beautiful > EFLAGS dependences instead. (MVT::Flag has since been renamed to MVT::Glue.) That revision made bug 8404 go away. Am I right in thinking that one of the problems with MVT::Glue is

Sorry for the cross-post, but this could be either lists problem. I have 2 boxes running 7-STABLE as of 20081130, both i386 SMP. One is running ISC DHCPD 3.0.x from recent ports, and the other dhclient from make world. The server is refusing to answer the DISCOVER request, as it thinks the IP checksum is wrong, which tcpdump also confirms. Other DHCP clients are working fine on this network,

I have a brand new poweredge 2900 with 10 SAS drives configured in two arrays via the built-in PERC 5 raid controller as: raid 1: 2x73GB raid 10: 8x300GB It's got 4GB of ram, and it's intended to be an NFS filestore. For some strange reason, logging in with ssh works great, it returns a prompt, all seems well. I go to run a simple command like 'top' or 'yum -y install

latest pxeboot (7.1): mother-board NIC/LOM CPU ------------- ------- --- Intel SWV25 em xeon works fine SUN X2200 bge amd works fine DELL PE 2950 bce xeon failes 95% of the times hangs or goes into btx dump regs. mode :-) Intel SE7320VP21 msk xeon failes 50% of the times - hangs pxeboot with btx.S 1.45 2008/02/27 23:35:39, works fine. so it seems that changes since 1.45 have

I'm experiencing similar problems with a 3C996-T under 4.8-REL. In particular, connecting a 4.8-REL machine to a 5.1-REL machine leads to some interesting situations: I can do simple pings across the link, but ssh fails, and heavy pings crash the 4.8 machine. Similarly changing the interface configuration with ifconfig tends to crash the 4.8 machine (mtu, link0, up/down, etc). The