Re: Detecting CPU throttling on over temperature
I don't know whether there is a more convenient way, but you could definitely check the current CPU frequency to detect whether it changed from the previous one or not. There are several ways to this, depends on the CPU. You can try messing with cpufreq(4). On Tue, Sep 8, 2009 at 2:39 PM, Daniel O'Connordocon...@gsoft.com.au wrote: Hi, I recently discovered a system where the floppy drive cable was intermittently fouling the CPU fan - I believe this caused the CPU to overheat and then get throttled by the BIOS. Does anyone know if it is possible to determine if this is the case? ie is there a way to be informed if throttling has occurred? Thanks. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ 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: fun with if_re
As I don't own that server anymore, I'm afraid I can't tell you whether it's working now. :( On Thu, Feb 05, 2009 at 10:31:47AM +0900, Pyun YongHyeon wrote: On Wed, Feb 04, 2009 at 06:37:53PM +0100, Henrik Friedrichsen wrote: Hey. I have had similar symptoms on a dedicated server with the re driver. What I did was grab more recent drivers (which might be redundant now) and disable a set of features that weren't stable at the time. re(4) had several issues for PCIe based controllers on 7.0-RELEASE and I believe most issues were resolved in HEAD/stable so I think you can safely turn checksum offloading, VLAN hardware assistance features. You can also enable TSO(default off) but I remember some users reported issues for TSO, I didn't encounter TSO issues though. If you can still reproduce the issue please let me know. Please have a look at this PR that I submitted back then: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/125805 ___ 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: fun with if_re
Hey. I have had similar symptoms on a dedicated server with the re driver. What I did was grab more recent drivers (which might be redundant now) and disable a set of features that weren't stable at the time. Please have a look at this PR that I submitted back then: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/125805 On Wed, Feb 04, 2009 at 10:05:07AM +0100, Gerrit Kühn wrote: Hi folks, I have several routers here which are based on Jetway J7F4 ITX boards that come with two onboard re-interfaces. I run 7-stable on them via nanobsd and update them about once in three or four months. After the last update (11th December 2008) I have noticed the following strange behaviour on at least two machines (identical hard- and software): After weeks of flawless operation, the network connection on both interfaces suddenly starts to mangle packages. Even a simple ping can show up to 50% or so package loss. The machine is mostly unreachable via net. ifconfig up/down did not cure this, turning off checksum-offloading and stuff did not help. Even simply rebooting the machine did not make the problem go away! I had to power-cycle them by unplugging all cables to get back to normal operation. I have seen this behaviour on two different machines, so I can most probably rule out a hardware issue. It does not appear to happen often, though. I did not see this with an earlier image of 7-stable from June 2008, and probably even an image from early September was working fine (although I did not use that one for such a long time). Visiting the webcvs I noticed that there are a lot of patches for if_re in December 2008 and January 2009. The revision I'm having problems with is tagged 1.95.2.37 2008/12/09 11:01:17. Does anyone have an idea what broke if_re for me, and how I can get back to stable operation? Is it possible to use if_re from head as drop-in replacement to test the patches available after 12/09? I would prefer not to move the machines completely from -stable to -current. Here some further information about the NICs: ---pciconf--- r...@pci0:0:9:0: class=0x02 card=0x10ec16f3 chip=0x816710ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8169/8110 Family Gigabit Ethernet NIC' class = network subclass = ethernet r...@pci0:0:11:0:class=0x02 card=0x10ec16f3 chip=0x816710ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8169/8110 Family Gigabit Ethernet NIC' class = network subclass = ethernet --- ---dmesg--- re0: RealTek 8169SC/8110SC Single-chip Gigabit Ethernet port 0xf000-0xf0ff mem 0xfdfff000-0xfdfff0ff irq 10 at device 9.0 on pci0 re0: Chip rev. 0x1800 re0: MAC rev. 0x miibus0: MII bus on re0 rgephy0: RTL8169S/8110S/8211B media interface PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: 00:30:18:ab:d0:19 re0: [FILTER] re1: RealTek 8169SC/8110SC Single-chip Gigabit Ethernet port 0xf200-0xf2ff mem 0xfdffe000-0xfdffe0ff irq 10 at device 11.0 on pci0 re1: Chip rev. 0x1800 re1: MAC rev. 0x miibus1: MII bus on re1 rgephy1: RTL8169S/8110S/8211B media interface PHY 1 on miibus1 rgephy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re1: Ethernet address: 00:30:18:ab:d0:1a re1: [FILTER] --- cu Gerrit ___ 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-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: re0 problem
On Wed, Dec 03, 2008 at 07:23:35PM +0300, Ilya Bakulin wrote: On Thu, 30 Oct 2008 14:10:17 +0900 Pyun YongHyeon [EMAIL PROTECTED] wrote: Please make sure you've (cold/warm) rebooted several times with this patch. Just applying the patch and using it without reboots doesn't necessary mean a working fix. Since it's hard to reproduce the issue even on a system with problematic controllers I'd like to have confidence in the patch. -- Regards, Pyun YongHyeon I've been using patched driver for a month, without any problems. Cold/warm reboots, panics, shutdowns occured regularly, but - no problems. Yesterday I've updated kernel to latest 7-STABLE forgot to apply patch, and errors are here :-) Applying patch once more fixed problems. I think that perfect working of patched driver during past month definitely proves that your patch corrects incorrect behavior of re(4). Thank you very much! -- Ilya Bakulin [EMAIL PROTECTED] Here's another proof: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/125805 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB detach/attach hangs with 7.0-RELEASE and 7.1-PRERELEASE
USB support in the BIOS? What kind of support does the BIOS provide that you can disable? I'm only able to disable the USB device, but that'd turn it off completely :( Henrik. On Mon, Sep 29, 2008 at 10:05:02PM +0200, Ronald Klop wrote: On Mon, 29 Sep 2008 02:46:15 +0200, Bruce M Simpson [EMAIL PROTECTED] wrote: Hi, I've noticed some general instability with plugging in or removing USB devices with FreeBSD 7.x, even when the devices are not actively in use. I had this happen with umass and ucom devices 3 times today. The machine hangs solid, there are no obvious signs of a panic or trap to DDB. I can't provide backtraces unfortunately -- these hangs happen on both my laptop and desktop, and I usually have X running -- if I had more specific information, I'd open a PR. Again, there seems to be no reason why this should happen, the devices are off-the-shelf consumer items known to work with existing drivers, and have been repeatedly used in other OSes without these hangs happening; consider this an anecdotal report. [For some reason my IBM laptop will often not allow me to break into DDB on a driver related panic, and will just immediately reboot -- I lack free time to track down exactly why this could be. My desktop has a USB keyboard and this appears not to be supported by DDB, I ordered a PS/2 keyboard which hasn't arrived, but that's another story.] thanks BMS On my computer I had to disable USB support in the BIOS because it 'conflicted' with USB support of FreeBSD. FreeBSD still detects USB and all connected devices. Maybe this helps on your computer also. Ronald. ___ 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: USB detach/attach hangs with 7.0-RELEASE and 7.1-PRERELEASE
On Mon, Sep 29, 2008 at 01:46:15AM +0100, Bruce M Simpson wrote: Hi, I've noticed some general instability with plugging in or removing USB devices with FreeBSD 7.x, even when the devices are not actively in use. I had this happen with umass and ucom devices 3 times today. The machine hangs solid, there are no obvious signs of a panic or trap to DDB. I can't provide backtraces unfortunately -- these hangs happen on both my laptop and desktop, and I usually have X running -- if I had more specific information, I'd open a PR. Again, there seems to be no reason why this should happen, the devices are off-the-shelf consumer items known to work with existing drivers, and have been repeatedly used in other OSes without these hangs happening; consider this an anecdotal report. [For some reason my IBM laptop will often not allow me to break into DDB on a driver related panic, and will just immediately reboot -- I lack free time to track down exactly why this could be. My desktop has a USB keyboard and this appears not to be supported by DDB, I ordered a PS/2 keyboard which hasn't arrived, but that's another story.] thanks BMS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] Hey, I can confirm those problems, however I can't provide dumps either. I remember the kernel panicing with PAGE_FAULT errors though. Good to know, that I'm not the only one with those problems though. Henrik. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
