Re: Temperature/fan monitoring on a Supermicro P8SCT
On Wednesday 10 January 2007 14:08, Bruno Ducrot wrote: From the OP, I think the processor is an AMD 64 bits of some sort. From BIOS and Kernel Developer's Guide for AMD NPT Family 0Fh Processors, available at The P8SCT is an Intel S775 board so AMD specific things are unlikely to work :) I was basically wondering if anyone had patches or similar to mbmon/healthd I could use. Failing that I will try and generate some myself (when I get some time, ho ho ho). -- 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 pgpLs11h8MsZU.pgp Description: PGP signature
Any way to solve watchdog timeout on network-IF?
Hi. I'm using FreeBSD/i386 6-stable on HP DL360G5 server, and getting Watchdog timeout link state changed to DOWN/UP messages shown below. bce0: /usr/src/sys/dev/bce/if_bce.c(5000): Watchdog timeout occurred, resetting! bce0: link state changed to DOWN bce0: link state changed to UP [System I'm using:] * CPU Xeon 51xx, * Intel 5000X chipset * NIC: bce (1.2.2.6 2006/10/24) bce0: Broadcom NetXtreme II BCM5708 1000Base-T (B1), v0.9.6 mem 0xf800-0xf9ff irq 16 at device 0.0 on pci3 bce0: ASIC ID 0x57081010; Revision (B1); PCI-X 64-bit 133MHz miibus0: MII bus on bce0 brgphy0: BCM5708C 10/100/1000baseTX PHY on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bce0: Ethernet address: 00:18:71:73:c5:5a [Tests] Give UDP generating load (ports/net/rude was used). Test configuration: [FreeBSD]-(bce)--- 100BaseTX-switch ---(em)[FreeBSD] packet genarator --packet receiver 70Mbps UDP, 1400Byte packet * 6000pps. Then, the above Watchdog timeout message occurs _SOMETIMES_. Maybe once a week, sometimes 10times/day. I've tested with 3 hardware(all HP DL3x0 server with BCM5708 chip), and all of them seems to suffer with this. I've suspected new bce-NIC, and tried with bge cards (also with FreeBSD 6-stable). However, similar message also happens with bge(other network IFs also). Next, I've tried with other cable, other ether-switch, but they still seems to happen _sometimes_. Are these Watchdog timeout events common and happening everywhere else? Or am I doing something wrong? Searching the -stable archive, there seems some other people suffering with this: 2006.11.29 [Re: Dell PE 1950 bce NICs revisited] http://lists.freebsd.org/pipermail/freebsd-stable/2006-November/031116.html 2006.12.14 [em watchdog timeout] http://lists.freebsd.org/pipermail/freebsd-stable/2006-December/031416.html Thank you. -- KAWAGUTI Ginga ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.x loosing record of free space after filesystem fills?
Guy Helmer wrote: Oliver Fromme wrote: Why are you using those blocksize and fragsize settings? (If you store large files, then you should at least also decrease the inode density, using the -i option.) These settings were chosen to optimize I/O throughput for Postgresql on the theory that a 64KB block size would maximize disk throughput in the general case (especially for a RAID 10 system) and an 8K frag size would match Postgresql's page size. I don't think that that theorie holds true in reality. Did you perform any benchmarks to verify it? In fact, I would expect the performance to be better when using a block size of just 8KB and a frag size of 1 KB. By the way, this is an excerpt from the tuning(7) manpage: | FreeBSD performs best when using 8K or 16K file system block | sizes. The default file system block size is 16K, which provides | best performance for most applications, with the exception of | those that perform random access on large files (such as database | server software). Such applications tend to perform better with | a smaller block size, although modern disk characteristics are | such that the performance gain from using a smaller block size | may not be worth consideration. Using a block size larger than | 16K can cause fragmentation of the buffer cache and lead to | lower performance. Guy Helmer wrote: I wasn't aware of any known regressions in 6.x regarding large filesystem block sizes... I'm not aware of any regressions either. 64 KB bsize and 8 KB fsize didn't work reliable in 4.x, and the situation doesn't seem to have gotten worse (maybe it has gotten better with UFS2, but I didn't perform extensive tests with it because the non-standard bsize/fsize pessimize performance anyway). Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. That's what I love about GUIs: They make simple tasks easier, and complex tasks impossible. -- John William Chambless ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.x loosing record of free space after filesystem fills?
Jeremy Chadwick wrote: Oliver Fromme wrote: Guy Helmer wrote: I think we've finally found the cause of the problem - it wasn't just occurring after heavy use, but was visible right after filesystem creation! We regularly built new filesystems with newfs -U -O 1 -b 65536 -f 8192 Why are you using those blocksize and fragsize settings? (If you store large files, then you should at least also decrease the inode density, using the -i option.) Hmm... that begs the question: how do newfs -i and tunefs -f associate with one another? Not at all. newfs -i specifies the inode density of the new file system, and it cannot be changed later on with tunefs. (There are file systems that allocate inodes dynamically, but our UFS isn't one of them.) So this puts a hard limit on the number of files that can be stored on the file system. The tunefs -f option (equivalent to newfs -g) can be used to optimizes the way file data blocks are distributed across cylinder groups. The purpose is to minimize frag- mentation and seek times. It does not change the number of inodes at all. Shouldn't we document this somewhere? Some places I can think of, off the top of my head: I think the most important settings (-i, -b, -f) are already sufficiently documented in the tuning(7) manpage. A link to tuning(7) should probably be included in the newfs(8) and tunefs(8) manpages. I haven't examined what the Handbook says about all of this, but I don't think that it makes sense to duplicate the manpage to the handbook. Instead, it would be helpful to include a pointer to the tuning(7) manpage there, too. Just my two cents. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. Documentation is like sex; when it's good, it's very, very good, and when it's bad, it's better than nothing. -- Dick Brandon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
booting question
Hi I got hit with the fatal trap problem in the prerelease kernel. Li Xin suggested that I unload, load kernel.old and re-boot. When I did that it hung during the boot process, just after the pci message. I did get the system to re-boot using kernel.GENERIC, but was wondering why kernel.old hung since it was a bootable kernel. Is this just a gee it would be nice to know item, or something more critical? Thanks Jim Ballantine ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Temperature/fan monitoring on a Supermicro P8SCT
On Wed, Jan 10, 2007 at 06:46:10PM +1030, Daniel O'Connor wrote: On Wednesday 10 January 2007 14:08, Bruno Ducrot wrote: From the OP, I think the processor is an AMD 64 bits of some sort. From BIOS and Kernel Developer's Guide for AMD NPT Family 0Fh Processors, available at The P8SCT is an Intel S775 board so AMD specific things are unlikely to work :) Ermm, yes. Indeed this wont work. Sorry for the noise. I was basically wondering if anyone had patches or similar to mbmon/healthd I could use. Failing that I will try and generate some myself (when I get some time, ho ho ho). Well, from http://www.supermicro.com/support/faqs/faq.cfm?faq=3099 you pointed out, I think the sensor where fan, temp and so on is the W83792D and not the W83627HF. That's one is probably not yet supported by healthd nor mbmon, and a quick and the spec show that you can access it only via SMBus. Cheers, -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
acpi_bus_number: can't get _ADR
Hi! I get this message when I booted my FreeBSD 6.2-PRERELEASE: acpi0: A M I OEMRSDT on motherboard ACPI-0438: *** Error: Looking up [OC06] in namespace, AE_NOT_FOUND SearchNode 0xc21982a0 StartNode 0xc21982a0 ReturnNode 0 acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 cpu0: ACPI CPU on acpi0 acpi_throttle0: ACPI CPU Throttling on cpu0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge irq 16 at device 1.0 on pci0 pci3: ACPI PCI bus on pcib1 pci3: display, VGA at device 0.0 (no driver attached) pci3: display at device 0.1 (no driver attached) pcib2: ACPI PCI-PCI bridge irq 16 at device 28.0 on pci0 pci2: ACPI PCI bus on pcib2 Does anyone know what this means? My motherboard is ASUS P5GPL-X. Cheers, XiXi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: acpi_bus_number: can't get _ADR
`On Wed, Jan 10, 2007 at 08:10:46PM +0800, huangxi wrote: Hi! I get this message when I booted my FreeBSD 6.2-PRERELEASE: acpi0: A M I OEMRSDT on motherboard ACPI-0438: *** Error: Looking up [OC06] in namespace, AE_NOT_FOUND SearchNode 0xc21982a0 StartNode 0xc21982a0 ReturnNode 0 acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 cpu0: ACPI CPU on acpi0 acpi_throttle0: ACPI CPU Throttling on cpu0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge irq 16 at device 1.0 on pci0 pci3: ACPI PCI bus on pcib1 pci3: display, VGA at device 0.0 (no driver attached) pci3: display at device 0.1 (no driver attached) pcib2: ACPI PCI-PCI bridge irq 16 at device 28.0 on pci0 pci2: ACPI PCI bus on pcib2 Does anyone know what this means? My motherboard is ASUS P5GPL-X. Regarding the ACPI-0438: *** Error message -- no idea. That looks like, possibly, some bad ACPI configuration data. Regarding the can't get _ADR messages: I have Asus AMD-based boards, Gigabyte Intel-based boards, Tyan boards, Supermicro boards, and true Intel boards all which do this. What it means and why it's printed, I don't know -- thus I've concluded, generally speaking, it's a harmless kernel message. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networkinghttp://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: acpi_bus_number: can't get _ADR
Could this message have something to do with the fact that it can not use ACPI to shut down,though not very often. I use FreeBSD as my desktop os. I must shutdown my x86 box when I finish my work. So it is troublesome. 2007/1/10, Jeremy Chadwick [EMAIL PROTECTED]: `On Wed, Jan 10, 2007 at 08:10:46PM +0800, huangxi wrote: Hi! I get this message when I booted my FreeBSD 6.2-PRERELEASE: acpi0: A M I OEMRSDT on motherboard ACPI-0438: *** Error: Looking up [OC06] in namespace, AE_NOT_FOUND SearchNode 0xc21982a0 StartNode 0xc21982a0 ReturnNode 0 acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 cpu0: ACPI CPU on acpi0 acpi_throttle0: ACPI CPU Throttling on cpu0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge irq 16 at device 1.0 on pci0 pci3: ACPI PCI bus on pcib1 pci3: display, VGA at device 0.0 (no driver attached) pci3: display at device 0.1 (no driver attached) pcib2: ACPI PCI-PCI bridge irq 16 at device 28.0 on pci0 pci2: ACPI PCI bus on pcib2 Does anyone know what this means? My motherboard is ASUS P5GPL-X. Regarding the ACPI-0438: *** Error message -- no idea. That looks like, possibly, some bad ACPI configuration data. Regarding the can't get _ADR messages: I have Asus AMD-based boards, Gigabyte Intel-based boards, Tyan boards, Supermicro boards, and true Intel boards all which do this. What it means and why it's printed, I don't know -- thus I've concluded, generally speaking, it's a harmless kernel message. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networkinghttp://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ 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: Any way to solve watchdog timeout on network-IF?
KAWAGUTI Ginga wrote: Hi. I'm using FreeBSD/i386 6-stable on HP DL360G5 server, and getting Watchdog timeout link state changed to DOWN/UP messages shown below. bce0: /usr/src/sys/dev/bce/if_bce.c(5000): Watchdog timeout occurred, resetting! bce0: link state changed to DOWN bce0: link state changed to UP [System I'm using:] * CPU Xeon 51xx, * Intel 5000X chipset * NIC: bce (1.2.2.6 2006/10/24) bce0: Broadcom NetXtreme II BCM5708 1000Base-T (B1), v0.9.6 mem 0xf800-0xf9ff irq 16 at device 0.0 on pci3 bce0: ASIC ID 0x57081010; Revision (B1); PCI-X 64-bit 133MHz Try this patch, it solved some problems we have observed in China community. For -CURRENT: http://people.freebsd.org/~delphij/for_review/patch-bce-watchdog-rewrite-HEAD.20070109 For -STABLE: http://people.freebsd.org/~delphij/misc/patch-bce-watchdog-rewrite Note that the -STABLE version is an old, but tested one. The -CURRENT version is optimized, but I have not stress tested yet. Both should apply to the different branch cleanly, though. I would appreciate if you would test the -HEAD patch, even with RELENG_6 and report if it solves your problem. But if the server is important to you then just use the latter. Cheers, -- Xin LI [EMAIL PROTECTED] http://www.delphij.net/ FreeBSD - The Power to Serve! signature.asc Description: OpenPGP digital signature
Re: GA-7VKMP: apci suspend leads to reboot
On Mon, 8 Jan 2007, Dmitry Morozovsky wrote: DM Dear colleagues, DM DM on Gigabyte GA-7VKMP (SocketA) with the last (f5) BIOS and fresh RELENG_6_2 DM suspending leads to hard reboot on resume. M$ WinXP suppends and resumes DM normally. DM DM acpi-related lines from verbose dmesg: DM DM [EMAIL PROTECTED]:~# dmesg | grep -i acpi DM Preloaded elf module /boot/kernel/acpi.ko at 0xc0762188. DM MADT: Found CPU APIC ID 0 ACPI ID 1: enabled DM ACPI APIC Table: AMIINT AMIINI09 DM APIC: CPU 0 has ACPI ID 1 DM acpi0: AMIINT AMIINI09 on motherboard DM acpi0: [MPSAFE] DM AcpiOsDerivePciId: bus 0 dev 17 func 0 DM AcpiOsDerivePciId: bus 0 dev 17 func 0 DM acpi0: Power Button (fixed) DM acpi0: wakeup code va 0xd867e000 pa 0x9e000 DM AcpiOsDerivePciId: bus 0 dev 0 func 0 DM ACPI timer: 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 - 10 DM Timecounter ACPI-fast frequency 3579545 Hz quality 1000 DM acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 DM cpu0: ACPI CPU on acpi0 DM acpi_button0: Power Button on acpi0 DM pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 DM pci0: ACPI PCI bus on pcib0 DM acpi_button1: Sleep Button on acpi0 DM sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 DM psmcpnp0: PS/2 mouse port irq 12 on acpi0 DM atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 FWIW, -current from 20070108 does exactly the same: it suspends, and after keypress (resume from S3 on keyboard in enabled) reset hard. 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]
saving power in a Dell Poweredge 750.
I'm setting up a Dell Poweredge 750 1U server. A friend is loaning me space in his rack and since his rack usage is limited by power I'd like to be as thrifty as possible. I hooked my kill-a-watt meter up and ran the machine for a couple of days and it uses 88 watts (3.90KWH/44.01H). Then I kldloaded cpufreq and enabled powerd and it still uses 88 watts (8.35KWH/93.47H). That surprised me a bit, and seems to suggest that it's spending most of its energy spinning fans or something. Is anyone familiar with the poweredge 750 and freebsd-stable? I can't find anything in the bios that suggests fans control, although I guess it's possible that they're running efficiently by default and I just haven't caused them to *really* run. Any other suggestions to help economize? Thanks, g. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Marvell 8053 support?
On 1/10/07, Bruce A. Mah [EMAIL PROTECTED] wrote: If memory serves me right, LI Xin wrote: Not sure if the snapshot contained the changes, though... IIRC the January snapshot is not released yet? The January CURRENT snapshots are being built and uploaded now. The mirrors might have some of the architectures, but an announcement will come only after everything's been uploaded (and had a little while to propagate). I just booted the january/amd64 snapshot ISO and it detects it fine: pcib3: ACPI PCI-PCI bridge irq 16 at device 28.4 on pci0 pcib3: secondary bus 3 pcib3: subordinate bus 3 pcib3: I/O decode0x9000-0x9fff pcib3: memory decode 0xf900-0xfaff pcib3: no prefetched decode pci3: ACPI PCI bus on pcib3 pci3: physical bus=3 found- vendor=0x11ab, dev=0x4362, revid=0x22 bus=3, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 powerspec 2 supports D0 D1 D2 D3 current D0 VPD Ident: Marvell Yukon 88E8053 Gigabit Ethernet Controller PN: Yukon 88E8053 EC: Rev. 2.2 MN: Marvell SN: AbCdEfG83CD03 CP: id 1, BAR16, off 0x3cc RV: 0x6c MSI supports 2 messages, 64 bit map[10]: type 1, range 64, base 0xfa00, size 14, enabled pcib3: requested memory range 0xfa00-0xfa003fff: good map[18]: type 4, range 32, base 0x9000, size 8, enabled pcib3: requested I/O range 0x9000-0x90ff: in range pcib3: matched entry for 3.0.INTA pcib3: slot 0 INTA hardwired to IRQ 16 mskc0: Marvell Yukon 88E8053 Gigabit Ethernet port 0x9000-0x90ff mem 0xfa00-0xfa003fff irq 16 at device 0.0 on pci3 mskc0: Reserved 0x4000 bytes for rid 0x10 type 3 at 0xfa00 mskc0: MSI count : 2 mskc0: attempting to allocate 2 MSI vectors (2 supported) mskc0: using IRQs 258259 for MSI mskc0: RAM buffer size : 48KB mskc0: Port 0 : Rx Queue 32KB(0x:0x7fff) mskc0: Port 0 : Tx Queue 16KB(0x8000:0xbfff) msk0: Marvell Technology Group Ltd. Yukon EC Id 0xb6 Rev 0x02 on mskc0 msk0: bpf attached msk0: Ethernet address: 00:16:e6:83:cd:03 miibus0: MII bus on msk0 e1000phy0: Marvell 88E Gigabit PHY on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto mskc0: [MPSAFE] mskc0: [FAST] +++ Thanks. Bruce. cheers mars ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: saving power in a Dell Poweredge 750.
On Wednesday, 10. January 2007 19:34, George Hartzell wrote: I'm setting up a Dell Poweredge 750 1U server. A friend is loaning me space in his rack and since his rack usage is limited by power I'd like to be as thrifty as possible. Any other suggestions to help economize? edit /etc/rc.conf: powerd_enable=YES powerd_flags=-a adaptive -b adaptive ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: saving power in a Dell Poweredge 750.
On Wed, 2007-Jan-10 09:34:21 -0800, George Hartzell wrote: I hooked my kill-a-watt meter up and ran the machine for a couple of days and it uses 88 watts (3.90KWH/44.01H). What was it doing for those couple of days? If it was just sitting idle then I would expect the power consumption to be fairly close to what you get with powerd. If you want to see peak power consumption, try running a buildworld, something very FP intensive and something that is thrashing the disk(s) (lots of seeks and writes), all in parallel. Then I kldloaded cpufreq and enabled powerd and it still uses 88 watts (8.35KWH/93.47H). I presume you confirmed that cpufreq/powerd was actually functioning (ie the CPU frequency was being changed). That surprised me a bit, and seems to suggest that it's spending most of its energy spinning fans or something. PSU overheads, fans, northbridge, video, RAM, disk, ... it all adds up. I can't specifically help with the Dell. -- Peter Jeremy pgpbxuESZuYiO.pgp Description: PGP signature
6.2 Release
Does anyone know if the Release is still going to happen today? -- Scott T. Hildreth [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: saving power in a Dell Poweredge 750.
Peter Jeremy writes: On Wed, 2007-Jan-10 09:34:21 -0800, George Hartzell wrote: I hooked my kill-a-watt meter up and ran the machine for a couple of days and it uses 88 watts (3.90KWH/44.01H). What was it doing for those couple of days? [...] It's a small time mail server and web host. It was running under its real world load. I presume you confirmed that cpufreq/powerd was actually functioning (ie the CPU frequency was being changed). Yep, or at least I confirmed that powerd -v from a shell cycled up and down w/ demand, then I configured it to run as a daemon and confirmed that was cpufreq was loaded and that powerd was running in the background. That surprised me a bit, and seems to suggest that it's spending most of its energy spinning fans or something. PSU overheads, fans, northbridge, video, RAM, disk, ... it all adds up. That's sort of what I was figuring, it is/was just that my laptop experience with powerd and battery life suggested that there would be more of a difference. I can't specifically help with the Dell. Thanks for the thoughts! g. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.2 Release
Scott T. Hildreth wrote: Does anyone know if the Release is still going to happen today? The release is not going to happen today, but will be very soon. My guess is that builds and mirroring will happen over the weekend and the release announcement will go out on Monday or Tuesday depending upon your time zone. Colin Percival ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: booting question
Date: Wed, 10 Jan 2007 06:53:36 -0500 From: J. W. Ballantine [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] Hi I got hit with the fatal trap problem in the prerelease kernel. Li Xin suggested that I unload, load kernel.old and re-boot. When I did that it hung during the boot process, just after the pci message. I did get the system to re-boot using kernel.GENERIC, but was wondering why kernel.old hung since it was a bootable kernel. Don't unload. Assuming that you use loader, let the system proceed to the count-down and press any key except ENTER. Then enter the command: boot kernel.old If you want to boot with options, place them at the end. (E.g. boot kernel.old -s Otherwise you get into issues with module/kernel comparability. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgpLW33yXfQUA.pgp Description: PGP signature
Re: FreeBSD 6.2-RC2 Available - networking zoneli freeze problem still exist.
Bruce A. Mah wrote: If memory serves me right, LI Xin wrote: Ken Smith wrote: On Thu, 2006-12-28 at 16:01 +0100, Thomas Herrlin wrote: It still runs networking daemons into a frozen zoneli state on heavy/(D)DOS network loads. Such processes cant be kill-9ed so there is no way to recover from it. (think frozen sshd and a very remote/headless server). See the stress test panic called 'Ran out of 128 Bucket http://people.FreeBSD.org/%7Epho/stress/log/cons210.html' on the 6.2 todo list and my own latest test here: http://www.maniacs.se/~junics/temp/vmstat-z.txt This test was on a new 6.2-RC2 install with no zone limit tweaks nor any sbsize limits in /etc/login.conf. I just made a vm disk image with replication instructions, however Peter Holm have replicated it with his own tools so i have not bothered with it until now. That problem is being worked on but won't be fixed for 6.2-REL. Depending on how complex the fix winds up being it may be an Errata candidate when the time comes. Perhaps we should mention some known workarounds in the errata documentation. E.g. raising nmbclusters limit, etc.? That's a good idea. Do you have more specifics (e.g. any particular nmbclusters value, other workarounds, etc.)? Thanks, Bruce. The most reliable way of avoiding zoneli according to my tests is setting an sbsize limit in /etc/login.conf to a value lower than the mbuf_cluster zone size limitation, note that there are 2048 bytes per cluster. (See vmstat -z for details) Or set the login.conf sbsize to a fraction of available RAM and combine this with the 0/unlimited setting as some recommend. Combining these two workarounds would probably be best, as setting mbuf to use unlimited ram for networking would cause a panic or freeze sooner or later anyway. I have not tested combining this yet as my system has been running stable for some time now with my current workarounds. Problems with sbsize limit: Setting sbsize in login.conf will lead to that some processes will run into a problem that they cannot allocate socket buffers in some extreme cases, however this will not affect overall system stability and that is my first priority. I have also thrown together a small executable that attempts local connection to its sshd with a the preliminary ssh handshake and that can be used with watchdogd -e parameter to reboot the box. This is mainly for headless/remote servers that MUST NOT have its sshd frozen. You can also read my mail to the fbsd-current list with the subject Re: zonelimit livelock, some possable workarounds /Thomas Herrlin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: booting question
Don't unload. Assuming that you use loader, let the system proceed to the count-down and press any key except ENTER. Then enter the command: boot kernel.old If you want to boot with options, place them at the end. (E.g. boot kernel.old -s that is very nice to know. I ran into the very same problem recently. what I used to do was: at counting down, press SPACE bar, unload, load /boot/kernel.old/kernel, boot. At least this order worked in the past. Something must have changed at some point. Chen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.2 Release
Colin Percival wrote: Scott T. Hildreth wrote: Does anyone know if the Release is still going to happen today? The release is not going to happen today, but will be very soon. My guess is that builds and mirroring will happen over the weekend and the release announcement will go out on Monday or Tuesday depending upon your time zone. Colin Percival This is good news. I have 5 new servers I have been testing 6.2 on since BETA-3, itching to put these into production :) Cheers, Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: booting question
Date: Wed, 10 Jan 2007 14:54:09 -0500 From: Chen Xu [EMAIL PROTECTED] Don't unload. Assuming that you use loader, let the system proceed to the count-down and press any key except ENTER. Then enter the command: boot kernel.old If you want to boot with options, place them at the end. (E.g. boot kernel.old -s that is very nice to know. I ran into the very same problem recently. what I used to do was: at counting down, press SPACE bar, unload, load /boot/kernel.old/kernel, boot. At least this order worked in the past. Something must have changed at some point. This may or may not work depending on modules loaded (note that unload will unload all modules already loaded by the loader, not just the kernel) and whether any modules are loaded later in the boot process. While I have not check in quite a while, at one time this would result in modules still being loaded from /boot/kernel and these might not be compatible with the old kernel. It is quite possible that these issues have now been resolved and that both methods will produce identical results. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgp3KYhQguC8u.pgp Description: PGP signature
Re: 6.2 Release
On 1/10/07, Colin Percival [EMAIL PROTECTED] wrote: Scott T. Hildreth wrote: Does anyone know if the Release is still going to happen today? The release is not going to happen today, but will be very soon. My guess is that builds and mirroring will happen over the weekend and the release announcement will go out on Monday or Tuesday depending upon your time zone. Colin Percival You guys ROCK :) Hope this means I get a new current snapshot too? Thanks Colin, Jack ___ 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.2-PRERELEASE with bge on amd64
Bruce Evans presumably uttered the following on 01/09/07 21:42: On Tue, 9 Jan 2007, John Baldwin wrote: On Tuesday 09 January 2007 09:37, Sven Willenberger wrote: On Tue, 2007-01-09 at 12:50 +1100, Bruce Evans wrote: Oops. I should have asked for the statment in bge_rxeof(). #7 0x801d5f17 in bge_rxeof (sc=0x8836b000) at /usr/src/sys/dev/bge/if_bge.c:2528 2528m-m_pkthdr.len = m-m_len = cur_rx-bge_len - ETHER_CRC_LEN; (where m is defined as: 2449 struct mbuf *m = NULL; ) It's assigned earlier in between those two places. Its initialization here is just a style bug. Can you 'p rxidx' as well as 'p sc-bge_cdata.bge_rx_std_chain[rxidx]' and 'p sc-bge_cdata.bge_rx_jumbo_chain[rxidx]'? Also, are you using jumbo frames at all? Also look at nearby chain entries (especially at (rxidx - 1) mod 512)). I think the previous 255 entries and the rxidx one should be non-NULL since we should have refilled them as we used them (so the one at rxidx is least interesting since we certainly just refilled it), and the next 256 entries should be NULL since we bogusly only use half of the entries. If the problem is uninitialization, then I expect all 512 entries except the one just refilled at rxidx to be NULL. Bruce ___ (kgdb) p sc-bge_cdata.bge_rx_std_chain[rxidx] $1 = (struct mbuf *) 0xff0097a27900 (kgdb) p rxidx $2 = 499 since rxidx = 499, I assume you are most interested in 498: (kgdb) p sc-bge_cdata.bge_rx_std_chain[498] $3 = (struct mbuf *) 0xff00cf1b3100 for the sake of argument, 500 is null: (kgdb) p sc-bge_cdata.bge_rx_std_chain[500] $13 = (struct mbuf *) 0x0 the indexes with values basically are 243 through 499: (kgdb) p sc-bge_cdata.bge_rx_std_chain[241] $30 = (struct mbuf *) 0x0 (kgdb) p sc-bge_cdata.bge_rx_std_chain[242] $31 = (struct mbuf *) 0x0 (kgdb) p sc-bge_cdata.bge_rx_std_chain[243] $32 = (struct mbuf *) 0xff005d4ab700 (kgdb) p sc-bge_cdata.bge_rx_std_chain[244] $33 = (struct mbuf *) 0xff004f644b00 so it does not seem to be a problem with uninitialization. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
ng_ubt(?) related kernel panic on 6.2-PRE
hi all. i got a panic when attached and then detached the ubt0 device just after a few seconds. Actually, it is a built-in bluetooth device in my laptop, operated with the Fn key. The module was loaded via ng_ubt_load=YES in loader.conf FreeBSD notebook.h3 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #13: Wed Jan 3 16:04:04 MSK 2007 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/MYKERNEL i386 part of dmesg: ubt0: vendor 0x413c product 0x8000, rev 2.00/12.66, addr 2 ubt0: vendor 0x413c product 0x8000, rev 2.00/12.66, addr 2 ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=49; nframes=6, buffer size=294 ... Jan 10 22:29:44 notebook savecore: reboot after panic: page fault kgdb bt shows: #0 0xc04f663c in doadump () #1 0xc04f6bbd in boot () #2 0xc04f7193 in panic () #3 0xc0672044 in trap_fatal () #4 0xc06722fb in trap_pfault () #5 0xc06726f0 in trap () #6 0xc065f62a in calltrap () #7 0xc049ccc9 in uhci_device_bulk_start () #8 0xc04a72e6 in usb_transfer_complete () #9 0xc049c6ac in uhci_idone () #10 0xc049c879 in uhci_softintr () #11 0xc049c500 in uhci_intr1 () #12 0xc04dee8e in ithread_loop () #13 0xc04dda2d in fork_exit () #14 0xc065f68c in fork_trampoline () Since ng_ubt is a BT-USB interface, there is nothing extraordinary in the above, i think. Though, maybe it is related to usb, not ubt. This is the first time i got this panic. Usually (i.e. until this time) there was no panic related to ubt0. So, probably it is not reproduceable :( Unfortunately, the kernel didn't have any debug options when it occurred. thanks. pluknet dmesg Description: Binary data ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
documentation for make targets
Can someone point to documentation for all the make targets in used in the /usr/src/Makefile. I am not looking for full documentation of each target, once I narrow down what targets I want I can get what need by walking the make files, but what I am looking for is a document that has a brief (short paragraph) of for each make target, describing its general purpose/function. Thanks, Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Panic/RELENG_6...
# kgdb -c vmcore.1 /usr/obj/usr/src/sys/THEBIGHONKER/kernel.debug
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Unde
fined 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 amd64-marcel-freebsd.
Unread portion of the kernel message buffer:
Slab at 0x81fc7d88, freei 43 = 0.
panic: Duplicate free of item 0x81fc7810 from zone
0xff00bff6d340(PV
ENTRY)
cpuid = 1
KDB: stack backtrace:
panic() at panic+0x253
uma_dbg_free() at uma_dbg_free+0x188
uma_zfree_arg() at uma_zfree_arg+0x60
pmap_remove_pages() at pmap_remove_pages+0x1d1
vmspace_exit() at vmspace_exit+0x9a
exit1() at exit1+0x38f
sys_exit() at sys_exit+0xe
syscall() at syscall+0x4d1
Xfast_syscall() at Xfast_syscall+0xa8
--- syscall (1, FreeBSD ELF64, sys_exit), rip = 0x80146777c, rsp =
0x7fffe52 8, rbp =
0x572000 ---
Uptime: 10d17h24m40s
Physical memory: 4087 MB
Dumping 598 MB: 583 567 551 535 519 503 487 471 455 439 423 407 391 375 359 343
327 311 295 279 263
247 231 215 199 183 167 151 135 119 103 87 71 55 39 23 7
#0 doadump () at pcpu.h:172
172 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) bt
#0 doadump () at pcpu.h:172
#1 0x80296699 in boot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:409
#2 0x8029612b in panic (
fmt=0x804c47a8 Duplicate free of item %p from zone %p(%s)\n)
at /usr/src/sys/kern/kern_shutdown.c:565
#3 0x803d8c58 in uma_dbg_free (zone=0xff00bff6d340,
slab=0x81fc7d88, item=0x81fc7810)
at /usr/src/sys/vm/uma_dbg.c:302
#4 0x803d6950 in uma_zfree_arg (zone=0xff00bff6d340,
item=0x81fc7810, udata=0x0) at /usr/src/sys/vm/uma_core.c:2276
#5 0x80423e31 in pmap_remove_pages (pmap=0xff00a576fe20, sva=0,
eva=140737488355328) at /usr/src/sys/amd64/amd64/pmap.c:2597
#6 0x803e0fba in vmspace_exit (td=0xff00ac8954c0) at vm_map.h:251
#7 0x8027bf3f in exit1 (td=0xff00ac8954c0, rv=0)
at /usr/src/sys/kern/kern_exit.c:295
#8 0x8027cace in sys_exit (td=0x0, uap=0x0)
at /usr/src/sys/kern/kern_exit.c:99
#9 0x80429dd1 in syscall (frame=
{tf_rdi = 0, tf_rsi = 0, tf_rdx = 34381131040, tf_rcx = 8, tf_r8 = 0, tf_r
9 = 0, tf_rax = 1, tf_rbx = 0, tf_rbp =
5709824, tf_r10 = 0, tf_r11 = 0, tf_r12
= 5677056, tf_r13 = 15, tf_r14 = 35, tf_r15 = 140737488348784, tf_trapno = 12, t
f_addr = 34382333184, tf_flags =
102739200, tf_err = 2, tf_rip = 34381133692, tf
---Type return to continue, or q return to quit---
_cs = 43, tf_rflags = 514, tf_rsp = 140737488348456, tf_ss = 35})
at /usr/src/sys/amd64/amd64/trap.c:792
#10 0x80414d68 in Xfast_syscall ()
at /usr/src/sys/amd64/amd64/exception.S:270
#11 0x00080146777c in ?? ()
Previous frame inner to this frame (corrupt stack?)
(kgdb)
What can I do to help?
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 512-248-2683 E-Mail: ler@lerctr.org
US Mail: 430 Valona Loop, Round Rock, TX 78681-3893
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: documentation for make targets
On Jan 10, 2007, at 1:53 PM, Jeffrey Williams wrote: Can someone point to documentation for all the make targets in used in the /usr/src/Makefile. I am not looking for full documentation of each target, once I narrow down what targets I want I can get what need by walking the make files, but what I am looking for is a document that has a brief (short paragraph) of for each make target, describing its general purpose/function. You could start with head -18 /usr/src/Makefile... -- -Chuck ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: saving power in a Dell Poweredge 750.
On Jan 10, 2007, at 9:34 AM, George Hartzell wrote: I'm setting up a Dell Poweredge 750 1U server. A friend is loaning me space in his rack and since his rack usage is limited by power I'd like to be as thrifty as possible. I hooked my kill-a-watt meter up and ran the machine for a couple of days and it uses 88 watts (3.90KWH/44.01H). Then I kldloaded cpufreq and enabled powerd and it still uses 88 watts (8.35KWH/93.47H). That surprised me a bit, and seems to suggest that it's spending most of its energy spinning fans or something. There isn't going to be nearly as much power savings running powerd with a desktop or rackmount equipment than with a laptop-- the latter are designed with a low-power mode of operation as a priority due to limited battery life. Also, I think that powerd also doesn't help that much compared with the HLT in the idle task approach that has been used previously, but YMMV. Also note that most power supplies are rated for around 80 - 90% efficiency, which means that a 400W power supply under full design load would be be drawing 440 to 480 W. However, even under zero load, they'll still eat a few watts. Unless you replace the machine with something like a VIA EPIA or a Soekris 45xx/48xx using very low power components, you're going to have a tough time getting your power draw down much lower than the ~90 W. -- -Chuck ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: booting question
On Wed, 10 Jan 2007 12:26:00 -0800 Kevin Oberman [EMAIL PROTECTED] wrote: This may or may not work depending on modules loaded (note that unload will unload all modules already loaded by the loader, not just the kernel) and whether any modules are loaded later in the boot process. While I have not check in quite a while, at one time this would result in modules still being loaded from /boot/kernel and these might not be compatible with the old kernel. FWIW, I had to boot a machine with the install CD (6.2-RC2, cd1) the other day, because FreeBSD's boot manager was hosed, erm, overwritten by Linux (which I had installed on another partition. Not my fault that the Linux installation program didn't ask me hwere to put grub, oh well) What I wanted was to use boot0cfg to write FreeBSD's boot manager back onto the MBR, but since I didn't have a rescue CD, I had to boot the machine with CD1, and then make it get everything from the hard drive and boot from there. I knew that may FreeBSD installation was on disk0, slice 1. What I did was the following (IIRC): 1) boot from CD1 2) select command line from boot menu 3) unload 4) set currdev=disk0s1 5) load kernel 6) boot (actually, I think I used boot -a, but I don't know if that is necessary) HTH -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: documentation for make targets
Thanks Chuck, But I got those, sorry I should have been more clear, the ones I want to see documentation on are the ones less commonly used like: buildenv check-old checkdpadd distribute distributeworld distrib-dirs distribution hierarchy regress release rerelease for instance make distribution is used in setting up jails (per the jail man page), but no where can I find a description of what it actually does, I tried following it through the make file chain but wasn't able to quickly determine what exactly it does. In must be something exclusive of make world, because it follows that command in the jail setup instructions. By the I have tried google, handbook, mailing list, and faq for these but the most I have been able to find are rote use of these in howto's, like the make distribution example above, but no descriptions of what they do. Thanks Jeff Chuck Swiger wrote: On Jan 10, 2007, at 1:53 PM, Jeffrey Williams wrote: Can someone point to documentation for all the make targets in used in the /usr/src/Makefile. I am not looking for full documentation of each target, once I narrow down what targets I want I can get what need by walking the make files, but what I am looking for is a document that has a brief (short paragraph) of for each make target, describing its general purpose/function. You could start with head -18 /usr/src/Makefile... ---Chuck ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ng_ubt(?) related kernel panic on 6.2-PRE
I can't help you, but you might also send this to the freebsd-bluetooth mailinglist. Ronald. On Wed, 10 Jan 2007 22:34:27 +0100, pluknet [EMAIL PROTECTED] wrote: hi all. i got a panic when attached and then detached the ubt0 device just after a few seconds. Actually, it is a built-in bluetooth device in my laptop, operated with the Fn key. The module was loaded via ng_ubt_load=YES in loader.conf FreeBSD notebook.h3 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #13: Wed Jan 3 16:04:04 MSK 2007 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/MYKERNEL i386 part of dmesg: ubt0: vendor 0x413c product 0x8000, rev 2.00/12.66, addr 2 ubt0: vendor 0x413c product 0x8000, rev 2.00/12.66, addr 2 ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=49; nframes=6, buffer size=294 ... Jan 10 22:29:44 notebook savecore: reboot after panic: page fault kgdb bt shows: #0 0xc04f663c in doadump () #1 0xc04f6bbd in boot () #2 0xc04f7193 in panic () #3 0xc0672044 in trap_fatal () #4 0xc06722fb in trap_pfault () #5 0xc06726f0 in trap () #6 0xc065f62a in calltrap () #7 0xc049ccc9 in uhci_device_bulk_start () #8 0xc04a72e6 in usb_transfer_complete () #9 0xc049c6ac in uhci_idone () #10 0xc049c879 in uhci_softintr () #11 0xc049c500 in uhci_intr1 () #12 0xc04dee8e in ithread_loop () #13 0xc04dda2d in fork_exit () #14 0xc065f68c in fork_trampoline () Since ng_ubt is a BT-USB interface, there is nothing extraordinary in the above, i think. Though, maybe it is related to usb, not ubt. This is the first time i got this panic. Usually (i.e. until this time) there was no panic related to ubt0. So, probably it is not reproduceable :( Unfortunately, the kernel didn't have any debug options when it occurred. thanks. pluknet -- Ronald Klop Amsterdam, The Netherlands ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: documentation for make targets
By the I have tried google, handbook, mailing list, and faq for these but the most I have been able to find are rote use of these in howto's, like the make distribution example above, but no descriptions of what they do. The build(7) manual page documents some of the make targets meant for 'public consumption'. -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
ACPI resume event and devd
Hello On my notebook (Compaq Armada M700, 6.1), after sleep state mouse freeze. So, I added in devd.conf action for restart moused. But, as I can see, devd don't catch ACPI Button 0x00 event (run him with -Dd flags and don't see any new strings at all), but kernel write wakeup from sleeping state (slept 00:00:31) in logger right. Also, devd catching and working on with all other ACPI event's correctly (Button 0x01, Lid, etc). Searched some info on the web, try some tips, but any luck... Close to my problem discussion here: http://www.daemonnews.org/mailinglists/FreeBSD/freebsd-acpi/msg02409.html But in 6.1 no such staff, like maybe present in CURRENT. With resume log string I see other: kernel: pci0: Failed to set ACPI power state D2 on \_SB_.C005.C1CA: AE_BAD_PARAMETER But I believe, this is something related to ESS card. Any help, please?... ;) Thx. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
