Broadcom NetXtreme bcm5720 in the 9.1 beta
Team I have a Dell PowerEdge R720xd, with the Broadcom NetXtreme bcm5720. I found the following thread: http://forums.freebsd.org/showthread.php?t=31769 I find I am unable to use the NIC's (there are 4 on the server). When we put a cable into it we get a "watchdog timeout -- resetting" error, and the machine will pause for 5 or so seconds. IP may or may not come up randomly. eg. pings will work for 10 seconds and then it will pause and stop. It is hard for me to get you some decent output because no networking works. I need to get this puppy on the network, any suggestions? Will it be resolved in RC1, when can I expect it? Thanks Jurgen -- Jurgen Weber Systems Engineer IT Infrastructure Team Leader THE ICONIC | E jurgen.we...@theiconic.com.au | www.theiconic.com.au ___ 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"
local APIC error 0x40
Running FreeBSD 8.3 -- and updating sources on a daily base and building everything -- I found a new APIC/ACPI problem introduced in the past week. I have a Toshiba Satellite U205 with an Intel Core Duo (not a Core 2). It used to work fine with both cores but then sometime in on the road to BSD 8.0 the machine began hanging. So I added to /boot/loader.conf hint.apic.0.disabled="1" and the machine only had one core but it went back to being reliable. The laptop sits idle a lot, so I also have in /etc/rc.conf performance_cx_lowest="LOW" and the fans stay off unless I am doing a build. Everything was good. I went away on a trip last week for five days, came home, did a csup to RELENG_8 and rebuilt the world, as usual, and now the fans are always running full! If I comment out hint.apic.0.disabled="1" from /boot/loader.conf and reboot, the results are a mixed bag: 1) I get my 2nd core back, and it no longer hangs! Hurray. 2) The fans go back to usually being off and silent. Hurray! 3) I get zillions of error messages streaming saying: CPU0: local APIC error 0x40 CPU1: local APIC error 0x40 No good! I am sitting at a prompt, no X-Windows, no apps running (other than the usual demons), and every few seconds I get another pair of these error messages. 4) The error appears benign other than flooding the console. Everything works, nothing hangs, I can build the OS and everything appears fine. So how do I get rid of these messages? What does error 0x40 mean? Thanks, Dan Allen ___ 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: Intel D2500cc video problem: no scrolling
On 07/23/2012 23:24, Dmitry Morozovsky wrote: On Mon, 23 Jul 2012, Frank Reppin wrote: Both stable/9 and head suffer from no scrolling issue: from the beginning of booting the kernel, all output overrides the last line on the screen, while others keep the loader phase. just catched up with older mails on -current... ... it looks like PHK has already committed a fix into current: http://svnweb.freebsd.org/base/head/sys/dev/fb/fbreg.h?view=log&pathrev=237223 MFCed on July 17 by kib@ r238555 for stable/9 r238556 for stable/8 Thanks a lot! Somehow google results does not show this even when phk has exactly the same mobo... I'll try contemporary -current tomorrow. ___ 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: Intel D2500cc video problem: no scrolling
On 23.07.2012 23:24, Dmitry Morozovsky wrote: [...] Thanks a lot! Somehow google results does not show this even when phk has exactly the same mobo... I'll try contemporary -current tomorrow. stable/9 got this as MFC'ed as well in r238555 a week ago. As such - a recent snapshot build (https://pub.allbsd.org/FreeBSD-snapshots/) should be good to go (in case you want to avoid -current). cheers, frank\ -- 43rd Law of Computing: Anything that can go wr fortune: Segmentation violation -- Core dumped ___ 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: Intel D2500cc video problem: no scrolling
On Mon, 23 Jul 2012, Frank Reppin wrote: > > Both stable/9 and head suffer from no scrolling issue: from the beginning of > > booting the kernel, all output overrides the last line on the screen, while > > others keep the loader phase. > just catched up with older mails on -current... > ... it looks like PHK has already committed a fix > into current: > > http://svnweb.freebsd.org/base/head/sys/dev/fb/fbreg.h?view=log&pathrev=237223 Thanks a lot! Somehow google results does not show this even when phk has exactly the same mobo... I'll try contemporary -current tomorrow. -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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: Intel D2500cc video problem: no scrolling
Hi Dmitry, On 23.07.12 17:22, Dmitry Morozovsky wrote: [...] Both stable/9 and head suffer from no scrolling issue: from the beginning of booting the kernel, all output overrides the last line on the screen, while others keep the loader phase. just catched up with older mails on -current... ... it looks like PHK has already committed a fix into current: http://svnweb.freebsd.org/base/head/sys/dev/fb/fbreg.h?view=log&pathrev=237223 cheers, frank\ -- 43rd Law of Computing: Anything that can go wr fortune: Segmentation violation -- Core dumped ___ 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: pxeboot with jumbo frame network
I know I have this working, however I don't remember what I did. I know I can pxeboot and install RHEL on a 9K frame network from a FreeBSD tftp server/NAT gateway. I do know the first thing in my RHEL install script is to set the MTU to 9K. If I have a chance later today, I'll dig into one of my install servers and try to figure out what options I used with DHCP to get it working. Sorry I can't be of more help than to say its possible. Bob Healey Systems Administrator Biocomputation and Bioinformatics Constellation and Molecularium hea...@rpi.edu (518) 276-4407 On 7/23/2012 1:31 PM, Robert Blayzor wrote: Is it possible to PXEboot a diskless client with an MTU higher than 1500 (Ie: 9k) ? The network we currently boot several diskless machines from has a lot of NFS traffic and we'd like to enable them all for larger MTU's however the one thing stopping us is the issue with initial boot seemingly only supporting an MTU of 1500. I know we can set the MTU later (post boot) on the diskless machines, but it doesn't seem we can run a higher MTU on the TFTP server as we'd have TFTP UDP traffic with mis-matched frame sizes at that point. ___ 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"
pxeboot with jumbo frame network
Is it possible to PXEboot a diskless client with an MTU higher than 1500 (Ie: 9k) ? The network we currently boot several diskless machines from has a lot of NFS traffic and we'd like to enable them all for larger MTU's however the one thing stopping us is the issue with initial boot seemingly only supporting an MTU of 1500. I know we can set the MTU later (post boot) on the diskless machines, but it doesn't seem we can run a higher MTU on the TFTP server as we'd have TFTP UDP traffic with mis-matched frame sizes at that point. -- Robert Blayzor INOC, LLC rblay...@inoc.net http://www.inoc.net/~rblayzor/ ___ 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: Intel D2500cc video problem: no scrolling
Hi Dmitry, On 23.07.12 17:22, Dmitry Morozovsky wrote: [...] Both stable/9 and head suffer from no scrolling issue: from the beginning of booting the kernel, all output overrides the last line on the screen, while others keep the loader phase. most likeley the same issue I've reported earlier as seen on an Intel DN2800MT: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/166262 cheers, frank\ -- 43rd Law of Computing: Anything that can go wr fortune: Segmentation violation -- Core dumped ___ 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"
Intel D2500cc video problem: no scrolling
Dear colleagues, in the process of upgrading my home router I'm trying to utilise Intel D2500CC mini-ITX motherboard[1]. Both stable/9 and head suffer from no scrolling issue: from the beginning of booting the kernel, all output overrides the last line on the screen, while others keep the loader phase. Provided the board has multiple serial ports and the final target (headless machine), I suppose it is not too big problem to finish install, but it would be great the issue to be fixed ;) Any hints? [1]: http://ark.intel.com/products/56462/Intel-Desktop-Board-D2500CC -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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: Compiling 8.3 kernel
On 7/23/12 2:37 PM, Gót András wrote: > Dear All, > > In the weekend I tried to compile a custom AMD64 8.3 kernel. It started > as a normal buildworld + buildkernel update from 8.3 and it turned out > that without the FREEBSD_COMPAT6 and maybe LIB32 kernel config option > the system won't boot into multiuser. It was mount and something else > that crashed with a sig11 and therefore I left in single user mode. > Somehow I left FREEBSD_COMPAT7 also in the config, but I'd sort that out > also if possible. Of course the machine booted with the GENERIC kernel > even after installworld which went fine in single user mode. > > I've found the following in the handbook, regarding the : > "This option is required to support applications compiled on FreeBSD 6.X > versions that use FreeBSD 6.X system call interfaces." > > I thought it won't be needed by default. There's nothing special in the > kernel config file. I just sorted out unwanted devices (e.g: bluetooth, > wifi, non-gbit nics etc.) and options from the GENERIC config file. If > the new config or any other machine details needed please let me know. > > Regards, > Andras Got Keep the COMPAT options to avoid running into problems. Also, regarding the customization of configuration files, see this article from Warren Block: http://www.wonkity.com/~wblock/docs/html/kernelconfig.html ___ 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: ZFS causing panic
> Hi guys > > I've had an issue for some time now. When I'm copying a lot of files over to > ZFS usually using SMB it causes a panic and locks up the server. > I'm running FreeBSD 9.0-RELEASE with a custom kernel. I've just pulled > unnecessary drivers out of the config and added: > cpu HAMMER > device pf > device pflog > options DEVICE_POLLING > options HZ=1000 > > For full disclosure I am getting these errors in the syslog which means > there's an ECC error occurring somewhere which I am trying to locate. I have > replaced both of the CPU's and all of the RAM and am still getting it so > perhaps the north bridge has bought the farm. We have some similar HW here and we suspect either CPU or Northbridge too, we where seeing day to day panics and a scrub would pretty much guarantee a panic. We also replaced the CPU's with no joy but found disabling the cores of the CPU in the second socket made the issues go away so strengthening the Northbridge theory. Try disabling the cores with the following and see if it helps:- /boot/loader.conf hint.lapic.1.disabled="1" hint.lapic.2.disabled="1" Unfortunately if you have perceived corruption due to this type of issue there's no guaranteeing what state your data is really in :( Regards Steve This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmas...@multiplay.co.uk. Thanks Steve I'm giving that a try now. Luckily all of the data is backed up so I don't mind copying it back until it panics again :) //Clay ___ 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: ZFS causing panic
- Original Message - From: "Clayton Milos" Hi guys I've had an issue for some time now. When I'm copying a lot of files over to ZFS usually using SMB it causes a panic and locks up the server. I'm running FreeBSD 9.0-RELEASE with a custom kernel. I've just pulled unnecessary drivers out of the config and added: cpu HAMMER device pf device pflog options DEVICE_POLLING options HZ=1000 For full disclosure I am getting these errors in the syslog which means there's an ECC error occurring somewhere which I am trying to locate. I have replaced both of the CPU's and all of the RAM and am still getting it so perhaps the north bridge has bought the farm. We have some similar HW here and we suspect either CPU or Northbridge too, we where seeing day to day panics and a scrub would pretty much guarantee a panic. We also replaced the CPU's with no joy but found disabling the cores of the CPU in the second socket made the issues go away so strengthening the Northbridge theory. Try disabling the cores with the following and see if it helps:- /boot/loader.conf hint.lapic.1.disabled="1" hint.lapic.2.disabled="1" Unfortunately if you have perceived corruption due to this type of issue there's no guaranteeing what state your data is really in :( Regards Steve This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmas...@multiplay.co.uk. ___ 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"
ZFS causing panic
Hi guys I've had an issue for some time now. When I'm copying a lot of files over to ZFS usually using SMB it causes a panic and locks up the server. I'm running FreeBSD 9.0-RELEASE with a custom kernel. I've just pulled unnecessary drivers out of the config and added: cpu HAMMER device pf device pflog options DEVICE_POLLING options HZ=1000 For full disclosure I am getting these errors in the syslog which means there's an ECC error occurring somewhere which I am trying to locate. I have replaced both of the CPU's and all of the RAM and am still getting it so perhaps the north bridge has bought the farm. I don't think that this is the issue though because I was getting panics before on other hardware. Current hardware is an 80G OS drive, 2x Opteron 285's and 16G (8x2G) of RAM on a Tyan 2892 motherboard. Raid card is an Areca 1120. I am running 2 pools. Both of them are 4 drive hardware RAID5. The one I'm having issues with is 4x3TB drives seen as a 9TB scsi drive: da0 at arcmsr0 bus 0 scbus6 target 0 lun 0 da0: Fixed Direct Access SCSI-5 device da0: 166.666MB/s transfers (83.333MHz, offset 32, 16bit) da0: Command Queueing enabled da0: 8583068MB (17578123776 512 byte sectors: 255H 63S/T 1094187C) This is encrypted with GELI to make /dev/da0.eli upon which the pool is created. It looks like it's lost the pool now since the last panic: pool: homer state: FAULTED status: The pool metadata is corrupted and the pool cannot be opened. action: Destroy and re-create the pool from a backup source. see: http://www.sun.com/msg/ZFS-8000-72 scan: scrub repaired 0 in 7h0m with 0 errors on Mon Jul 23 05:25:27 2012 config: NAMESTATE READ WRITE CKSUM homer FAULTED 0 0 2 da0.eli ONLINE 0 0 8 Also I was running a script to check the kernel memory every 2 seconds. It appears that it was well within the 1G I have assigned it in /boot/loader.conf: TOTAL=695217852, 663.011 MB TOTAL=695217852, 663.011 MB TOTAL=695217852, 663.011 MB TOTAL=695219900, 663.013 MB TOTAL=695219900, 663.013 MB TOTAL=695345852, 663.133 MB TOTAL=695412412, 663.197 MB TOTAL=695228092, 663.021 MB TOTAL=695228092, 663.021 MB TOTAL=695226044, 663.019 MB My /boot/loader.conf contains: ng_bpf_load="YES" amdtemp_load="YES" ubsec_load="YES" vm.kmem_size="1024M" vm.kmem_size_max="1024M" vfs.zfs.arc_max="600M" vfs.zfs.vdev.cache.size="8M" vfs.zfs.txg.timeout="5" kern.maxvnodes="25" This system is a home server so I can run a debug kernel if required and crash it again. My first question is am I doing something wrong? I think the values I've put in are sufficient but I could well have done it wrong. The server is also not writing the crash dump out by the looks. It hung on 1% and I had to power cycle it. This is the panic: panic: solaris assert: 0 == zap_increment_int(os, (-1ULL), user, delta, tx) (0x0 == 8x7a), file: /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/dm u_object.c, line: 1224 cpuid = 3 KDB: stack backtrace #0 0x8055b74e at kdb_backtrace+0x5e #1 0x80525c47 at panic+0x187 #2 0x80e71b9d at do_userquota_update+0xad #3 0x80e71dae at dmu_objset_do_userquota_updates+0x1de #4 0x80e882af at dso_pool_sync+0x11f #5 0x80e976e4 at spa_sunc+0x334 #6 0x80ea7ed3 at txg_sync_thread+0x253 #7 0x804f89ee at fork_exit+0x11e #8 0x8075847e at fork_trampoline+0xe Uptime: 14h31m10s Dumping 2489 out of 16370 MB:..1% Thanks for any help. //Clay ___ 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"
Compiling 8.3 kernel
Dear All, In the weekend I tried to compile a custom AMD64 8.3 kernel. It started as a normal buildworld + buildkernel update from 8.3 and it turned out that without the FREEBSD_COMPAT6 and maybe LIB32 kernel config option the system won't boot into multiuser. It was mount and something else that crashed with a sig11 and therefore I left in single user mode. Somehow I left FREEBSD_COMPAT7 also in the config, but I'd sort that out also if possible. Of course the machine booted with the GENERIC kernel even after installworld which went fine in single user mode. I've found the following in the handbook, regarding the : "This option is required to support applications compiled on FreeBSD 6.X versions that use FreeBSD 6.X system call interfaces." I thought it won't be needed by default. There's nothing special in the kernel config file. I just sorted out unwanted devices (e.g: bluetooth, wifi, non-gbit nics etc.) and options from the GENERIC config file. If the new config or any other machine details needed please let me know. Regards, Andras Got ___ 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"
